• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Avail] [ROOT] EASIEST AVAIL ROOT METHOD--UPDATE.ZIP [no adb needed]

Status
Not open for further replies.
i think i've fixed the issue some of you were having.

one wrong line in the root_update.zip updater-script was calling busybox from a location it doesn't exist.

i fixed this issue. how it ever worked on my end i'm not sure seeing as busybox is not in that location on my phone either, but now it should work for everyone. that is, unless a problem exists on some builds of the phone that i'm not aware of.

so files have been updated, follow the directions and try again.

ENJOY
 
I've done everything as the directions stated.....but when I get into recovery mode it says Install from sd card....finding update package....opening update package...veifying update package....Installation aborted. what am I doing wrong??...any help would be greatly appreciated...Thank You in advance!!!
 
I've done everything as the directions stated.....but when I get into recovery mode it says Install from sd card....finding update package....opening update package...veifying update package....Installation aborted. what am I doing wrong??...any help would be greatly appreciated...Thank You in advance!!!


you're going to have to give more info than that if you want help...

re-download the files and re-copy to your sdcard--make sure you download them from a pc

1) this happens when you are in stock recovery or the temporary cwm recovery???

2) what's the status error when it says installation aborted???




 
Thanks boogie, the new file upload worked!

I removed all the att junk with titanium, moved a few apps to SD...but now the memory is SUPER low. Did I do something wrong?

2 questions to anyone while I'm already typing:

Any good and stable Roms for the avail?
Is Netflix working for anyone? (It worked when my mom first got the phone, then stopped about 3 weeks later (wont work on data or WiFi)
 
well, Like chris, I get the intallation aborted message. I did a factory wipe/reset and then followed the steps exactly. I don't understand the debugging part. If I set debug I can't copy files to sd card. When plugged into computer I unchecked it, copied file, then rechecked it. Also I can't boot into recovery while plugged into computer so I unplugged it to boot to recovery so what's the point of debug? Finally, I have no idea what a nandroid is so I can't give you one in my current state of ignorance but I'd be glad to once I'm enlightened. It's an ATT go phone zte z990 using a straight talk sim and every root procedure I've come across I have tried to no avail(pun intended).
 
well, Like chris, I get the intallation aborted message. I did a factory wipe/reset and then followed the steps exactly. I don't understand the debugging part. If I set debug I can't copy files to sd card. When plugged into computer I unchecked it, copied file, then rechecked it. Also I can't boot into recovery while plugged into computer so I unplugged it to boot to recovery so what's the point of debug? Finally, I have no idea what a nandroid is so I can't give you one in my current state of ignorance but I'd be glad to once I'm enlightened. It's an ATT go phone zte z990 using a straight talk sim and every root procedure I've come across I have tried to no avail(pun intended).


when the installation aborts in recovery it gives an error--post the error. it doesn't abort without saying why. it's usually a error (status #) post the error

did you rename the root-update.zip to update.zip like the directions clearly say to do?????

and you're wrong. when usb debugging is checked you can still transfer files to the sdcard through usb. you just drag the notification bar down and click transfer from usb (or whatever it's named), and it works like normal. if your phone doesn't do this it's messed up. get another.

and no one said it had to be plugged into the computer while you do this--where did you get this idea from???

to make a nandroid you need to install my recovery for unrooted phones http://androidforums.com/avail-all-...t-clockworkmod-recovery-non-rooted-avail.html
and boot into it and follow the menu to backup

PLEASE DO MAKE A NANDROID AND POST IT and i'll prove it works once again...
 
well, Like chris, I get the intallation aborted message. I did a factory wipe/reset and then followed the steps exactly. I don't understand the debugging part. If I set debug I can't copy files to sd card. When plugged into computer I unchecked it, copied file, then rechecked it. Also I can't boot into recovery while plugged into computer so I unplugged it to boot to recovery so what's the point of debug? Finally, I have no idea what a nandroid is so I can't give you one in my current state of ignorance but I'd be glad to once I'm enlightened. It's an ATT go phone zte z990 using a straight talk sim and every root procedure I've come across I have tried to no avail(pun intended).

If usb debugging and mass storage aren't working at the same time something is wrong. Captbryan was having the same problem and his adb wasn't working so I instructed him to do a reset with the small button next to the camera under the back cover. It solved his problem. But use at your own risk.
 
Good, first item of ignorance is now cleared up and I can now transfer files with debugging checked. Thanks. I assumed it was plugged in to the computer for the file transfer and no where did I see to unplug it, however, I did try it both ways after the file transfer. I did rename the file, as directed, and also tried it after a factory wipe. I even downloaded the file several times, each time deleting the old first. Nothing changed so I'll assume the file was not corrupted and it's on my end. I do not remember an error mentioned, just "installation aborted" and back to the menu, but I'll try again and look for one. Once I set up to make a nandroid I'll post it.
 
Just tried again. Fresh file transfer to sd root and renamed it. Turned phone off and rebooted to recovery. Chose "apply sdcard:update.zip" and got this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted

No error message. I'll try to get a nandroid posted later today
 
quick question, how do I know which file to use for the cwm recovery for unrooted phones? no idea if I'm fat32 or not

i'm pretty sure i edited it to say that either one will work for any user without an sd-ext partition

if you have an sd-ext partition, then use the one that supports the proper format of your sd-ext partition.

since you aren't familiar with the sd-ext, it's safe to say you can use either one. but in the event you partition your sdcard later, get the ext3 version because that is the most common format of sd-ext partitions.

and please get the nandroid up. i need it to figure out the problem, if there really is one, which i'm not convinced there is. i still think the problems are user error honestly, but i could be wrong.
 
very interesting. I tried it using your fat32 file and got the same sequence up to the installation aborted message. I'll take a break and see what ideas you guys post later today,

update: also tried it with the ext3 and got the same result. Either I or my phone are missing something
 
I followed those directions to the dot and after booting my phone back up i still dont have root access :(

You did install superuser right?
Did it give an error when you flashed it? Information would be real handy if you expect help. This habit people are in saying some variation of "I didn't do anything wrong, but it didn't work". And leaving it at that are very annoying. If you want help you must provide detailed information.

To quote Sherlock Holmes "Data data data, we cannot make bricks without clay!"
 
I followed those directions to the dot and after booting my phone back up i still dont have root access :(

download one of the cwm recovery images for stock phones from here
http://androidforums.com/avail-all-...t-clockworkmod-recovery-non-rooted-avail.html

follow the directions to install it, then make a nandroid of your system, zip it, and upload it to somewhere where i can download it and test what the problem is.

people keep complaining but they won't make a nandroid so i can see if there really is a problem or not, and if so fix it...
 
ran out of time yesterday to try anything, but will today. right now my problem is I can't boot into cwm to make a nandroid. seems to be the same problem of installation aborted that I'm having with trying to root. Thanks to stayboogy for patience and the private messages. once this backup finishes I'll start in on that process we discussed and if it works I'll post it.
 
for those of you following this saga, I tried a new approach today and reformatted my sd card and then put only the file "update.zip" on the card. Still no joy. Same old "installation aborted" message. I'll try a few versions of the recommended files, but have little hope for success going this route
 
for those of you following this saga, I tried a new approach today and reformatted my sd card and then put only the file "update.zip" on the card. Still no joy. Same old "installation aborted" message. I'll try a few versions of the recommended files, but have little hope for success going this route

Well you could always root manually like a lot of us did before boogy posted his release. http://rootzwiki.com/topic/27810-root-zte-z990g-aka-zte-merit/ you will need adb and usb debugging enabled.
 
I believe that is one of the processes that I failed to make work a while back, but I will certainly check it out to be sure. I'm convinced I have the one unrootable in existence and unfortunately that's all it's got in common with the Highlander. Sooner or later we'll crack it, which is why I got excited when I found this new post by stayboogy. Someday I'll be able to afford a newer better phone and stayboogy will find this one in his mailbox and probably curse me soundly both privately and in the forums, but until then I'll keep trying as long as you smarter folks keep posting suggestions.
 
I believe that is one of the processes that I failed to make work a while back, but I will certainly check it out to be sure. I'm convinced I have the one unrootable in existence and unfortunately that's all it's got in common with the Highlander. Sooner or later we'll crack it, which is why I got excited when I found this new post by stayboogy. Someday I'll be able to afford a newer better phone and stayboogy will find this one in his mailbox and probably curse me soundly both privately and in the forums, but until then I'll keep trying as long as you smarter folks keep posting suggestions.

You might have attempted the repost of these directions which were incomplete. I actually followed the repost when I rooted but since I had prior command line experience, I was able to sort out the miss printed directions and ultimately had success. All in all it only took about 10 minutes. With the original jcase method things should go much smoother for you as he actually knew what he was doing. Good luck! I'm fairly confident that you will succeed with the jcase method as long as you properly set up adb. Did you try the reset button under the battery next to the camera?

If you have problems with adb complaining the service is out of date consider using the reset button. As it miraculously solved a similar problem on captainbryans phone that I absolutely could not explain. Why the problem occurred to begin with or how the reset button fixed it is still an absolute mystery to me. It also fixed the usb debugging not being recognized when the phone was plugged in to the pc.
 
MY SINCEREST APOLOGIES TO THOSE I DOUBTED ABOUT THE UPDATE.ZIP NOT WORKING.

root for the Avail must be achieved by jcase's adb method.


it took me finding a stock nandroid and getting it to boot on the merit to find this out.


i am uploading the stock, rooted, Avail nandroid that has superuser already installed (that is the only thing done to it).



if i see this re-posted ANYWHERE, it will be promptly removed.

 
No go on the update.zip method on the avail eh? Interesting what ended up being the issue stopping it? And how did you manage to get the avail img to boot? What ended up being the problem with that?
 
Status
Not open for further replies.
Back
Top Bottom