Related
Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.
Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.
So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?
I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.
Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?
Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.
i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique
Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.
Did you run the stage1 and stage2 bats while in recovery?
dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?
jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.
Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?
Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?
Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App
EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.
jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!
Hi guys, i'm new here and a bit of a noob to the whole Android world.
I got my a500 about a month ago and loving it, Rooted it and got rid of all the bloat ware and is running like a dream.... love it....
A couple of days ago, i got an update: System Update 1.139,05, downloaded it and went to install, rebooted but nothing, Update failed!
I already have Android version 3.0.1 and Kernel version 2.6.36.3.
Is it me doing some thing wrong? Is it because its rooted? Do i need the update, please help, just want it to be up to date. Love the forum, thanks
chickin2000 said:
Hi guys, i'm new here and a bit of a noob to the whole Android world.
I got my a500 about a month ago and loving it, Rooted it and got rid of all the bloat ware and is running like a dream.... love it....
A couple of days ago, i got an update: System Update 1.139,05, downloaded it and went to install, rebooted but nothing, Update failed!
I already have Android version 3.0.1 and Kernel version 2.6.36.3.
Is it me doing some thing wrong? Is it because its rooted? Do i need the update, please help, just want it to be up to date. Love the forum, thanks
Click to expand...
Click to collapse
I've seen that some other users have had issues with the update if they removed the bloatware. Have you put it back before you attempted the update? If not, you'll have to put everything you've removed back and if you've edited any of the system files like build.prop, etc..you'll have to put it back to original also.
Thanks for the reply JackMetal! ERRRRRMMMM Q: is this a big update and if so then how would i put everything back, would it be factury settings? and if i do need to put everything back on why did i root it? lol sorry for being suck a noob! )
chickin2000 said:
Thanks for the reply JackMetal! ERRRRRMMMM Q: is this a big update and if so then how would i put everything back, would it be factury settings? and if i do need to put everything back on why did i root it? lol sorry for being suck a noob! )
Click to expand...
Click to collapse
LOL - yeah, I know..it's kind of a sucky move on Acer's part to force that. ;-) How did you remove them? Did you just delete them or freeze them within Titanium Backup? If deleted, did you happen to make a backup of them first so you could restore them now.
You can look at /cache/recovery/last_log and see exactly what it's complaining about. If you don't have the files you deleted, you can ask in the forum to see if another user can send them to you. I'd be glad to send mine, but I would imagine mine probably wouldn't help you since they are from 'after' the update and the checksum would still fail since they're changed. We could give it a shot though, and if it doesn't work you can see if someone that hasn't updated or happens to have the previous versions backed up, could send you the files.
---edit
Actually, I've got a few Titanium Backups from before the update, so I may just have the files you need!
Sweet dude, right will have to give it a look as i deleted them, noob thing to do i know lol still learning, thanks again for the super quick reply!
Same thing happened to me and this was after I restored my A500 to factory stock. I re-started the update download from the settings/info menu and this time it went without a hitch. I now have the updated A500, rooted it and am ready to go.
Advice for those people rooting their tablets. Don't just delete any .apks you don't want; move them to a folder on the internal sd card instead so whenever you need to restore them it's a simple matter of just moving them back).
Right, just an update.......
don't laugh, but i did try to put back all of the bloat ware!!!!! However, i replace some things and got rid of others, NOT GOOD! " HOME NOT WORKING ", yes thats what it said or words to that effect! Restarted as i thought that would help! OMG BOOT LOOP! Phone acer and sent it back for repair, UPS picked it up and acer received it this morning, and 30 mins again i got a text message with it done you douche bag, well they didn't say douche bag, but hay they should have done! Yes i'm a noob at all this, but i have learnt my lesson. Must say thanks for the help anyway from the forum!
P.S UPS SUCK BALLS, they are rude and v unprofessional! (had problems with them picking up the tablet).
P.P.S Back up everything and the back it up again! And DONT get rid of any system file or anything, to quote someone from the forum, " you have plenty of room! ", I have the 32Gb so yes i have the room lol!
O and just one more thing............ BACK THING UP NOOBS !!!!!!! )
Or Rename!
iCurmudgeon said:
Same thing happened to me and this was after I restored my A500 to factory stock. I re-started the update download from the settings/info menu and this time it went without a hitch. I now have the updated A500, rooted it and am ready to go.
Advice for those people rooting their tablets. Don't just delete any .apks you don't want; move them to a folder on the internal sd card instead so whenever you need to restore them it's a simple matter of just moving them back).
Click to expand...
Click to collapse
Also to make easy, just rename the .apk's to .bak or freeze them in Titanium backup!
Not to sound like a smartass but you know you could have done it yourself? Flash the device i mean.
What you do is you look for the boot.img and system.img and update.zip files in this forum or somewhere.
First the chinese one that you can just place in your External SD card and press Power+Vol- when device is turned of.
Then proceed to look for the American version, or whatever you wish if it's available.
Then you do this: place the boot.img and system.img in the root internal memory called Sdcard and place the update.zip in your EXTERNAL MicroSDcard.
Install Terminal emulator and push the boot and system img's 1st boot, 2ndSystem. Have superuser installed to.
After that when the images are pushed (usually the tablet would freeze after the system.img)
Then you force stop and power up the unit by holding Power button + Vol-
and that's it! No need to send to repair and pay money perhaps.
I see many people having issues that are new to this kind of thing and here is a fairly simple troubleshooting guide that I have compiled that I think will help many of you get through rooting, Installing the Market, and installing twrp with no problems. This is a complete video walk through for those of you find the videos easier. I recommend that you watch the videos thoroughly before attempting this so that you can be sure that you make no mistakes…!!!
• Start off with a stock Kindle on original 6.2.1fw
• Go to this link for a video walkthrough to root the Kindle with Jcase’s Burrito root. All of the links are in the description of this video to do so. http://www.youtube.com/watch?feature=player_embedded&v=KapnjR89ICA
• Now to install the android Market this is another video walkthrough that is from the same person once again all of the links are in the video description for downloading what it is that you need to perform this action http://www.youtube.com/watch?featur...tion_598718&src_vid=KapnjR89ICA&v=rTkegVrnAvA
• Now to install a custom recovery (aka twrp2.0) this is also another video walkthrough also made from the same individual. Once again all of the files needed are in the video description http://www.youtube.com/watch?annota...&src_vid=KapnjR89ICA&feature=iv&v=JqKZLMaRSgc
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB to get into adb shell
adb devices to make sure your kindle is connected properly
adb root to get proper permissions
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
• I have also noticed that some people also get stuck at 3:55 in this video at the firefire triangle. The fix for this is fairly easy and is explained in the video if you need a walkthrough step by step for doing this (Updating the drivers)here you go:
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
• If you also need a link for installing cm7 here is another video to do so also by the same individual. I do not recommend this as of yet until all of the bugs are worked out in this as I have heard many people have had problems with video playback or sound (mainly in ics) and usually end up flashing back to a custom rom anyway. It is your device though so it is completely up to you
http://www.youtube.com/watch?featur...tion_828059&v=L-zTJWY3CRc&src_vid=JqKZLMaRSgc
UPDATE JANUARY 3rd 2012
• Here is a link for a newer rom install called MIUI. This Rom is very smooth and the only thing confirmed not working at the moment (January 2, 2012 is video playback. There are however some individuals working on this issue and will hopefully have video working soon. Thanks to leeech for the MIUI port and nat3mil for the video. Here is the link for the easy to follow video tutorial.
http://www.youtube.com/watch?feature=endscreen&v=OqiX-If5w_4&NR=1
• Here is link on how to resize your internal storage (aka custom partitioning). This is called FireParted made by eldarerathis. This is good for those of you that think that they have too much storage in one place and not enough in another. Playing with partitions can cause you to lose data that is not backed up previously to editing partitions, so use at your own risk. I myself am going to use this to expand the storage on my sd card. Here is the easy to follow video tutorial.
http://www.youtube.com/watch?v=Bkff-bI-FrY
Big thanks for every one of these videos, made by nat3mil. So be sure to thank him and subscribe to his channel for all the latest easy to follow videos!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update January 7th 2012 This is a program to fix boot loop Problems easily (For Windows Only)
I noticed that many people are still having problems with getting stuck in a recovery boot loop, firefirefire boot loop (Yellow Triangle), Or even the kindle fire boot loop. This is a program to fix it automatically like the kindle fire Utility. I believe that it was made by Zombiepiratez, and he made this to change all of the headaches that many people are having with bootloop problems, proper file permission problems, and bricking problems, so be sure to thank him if this helps you. Once again this is a batch file made only for windows so for those of you that are not on windows, I will leave the common manual fixes below. Here is the link to his thread and download for the Fire Utility Unbrick:
http://forum.xda-developers.com/showthread.php?t=1428428
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Also for people getting caught in a recovery boot (whenever they turn on their kindle they boot into recovery without hitting the power button do this in your cmd:
adb shell
su
idme bootmode 4000
reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope that this clears up a lot of confusion for some of you weary of trying to do this to your kindle fire. I did all of this manually with my first Kindle. I have also used this method to be sure that it works and any problems that might come about when using this method and I have confirmed this to be successful. I really wanted to post this guide because I know that it is easier for some of you people new to this to follow along with a video. I know that some people say well there are a lot of tutorials out there but not one with a step by step and video links for a walk-through to do this whole procedure. If a mod could please sticky this I am sure that many would be greatful!!!
Remember that there is a thanks button…
DO not forget those who made this all possible:
Thanks to Jcase for Burrito Root & Vashypooh For KFU v.0.9.1 I would recommend that any of you that enjoy this and would like to see more mods such as these come out, to donate to these devs..
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
I was worried about doing this but now that I read your guide and seen the videos I am going to give this a try when I get settled in. Thank You!
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
You have to root the kindle before you can install the TWRP. the twrp 2.0 is used when you want to flash a rom and a few other things, (i think) you wont be able to install the twrp with out rooting first
babbabooey97 said:
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
Click to expand...
Click to collapse
I do believe that how to make a backup is on the install twrp2.0 video (the third one). I do not believe that you will have to install titanium backup like you do on your phone. I also do not believe that the sd card gets touched in the flashing process...
zwanzig said:
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
Click to expand...
Click to collapse
If you follow this guide in the order which was given everything will work out great after the first video your kindle will be Rooted. Twrp is really for creating a backup of your kindle in the current state and flashing different roms such as cm7 or ics... There are many things that you can do with a rooted Kindle really too many to name. You can run different market for starters which will give you more of a selection than what amazon has to offer. I did not mean to sound as if cm7 is not a good thing to use it is just not as stable as it could be and ics is still in the process of being worked on. I will be flashing to a different rom myself such as cm7 or cm9 or ics once they are stable with little or no bugs...
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
babbabooey97 said:
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
Click to expand...
Click to collapse
From what I understand if you are on a different rom such as cm7 you will not recieve a ota update, i could be wrong so do not quote me on that. I have however heard of people installing a modified 6.2.1 update that will help them update from the old fw to the previous one, so for them to have not gotten the update they must have either been using cm7 or turned their wifi off completely until they found a sure fix. Do a little searching on older threads you might find something when you do post back to this thread but make sure that you are sure that it does work as I would not like to have any mis-information in this thread... Thanks
[-_-] said:
From what I understand..... I would not like to have any mis-information in this thread... Thanks
Click to expand...
Click to collapse
Edited the quote for my own amusement.
What all do you use your KF for? I use mine while at work to keep from lugging my Mac around. Also for the occasional updates (socialnetworking=SN) and emailing.
Another question I would like to know is the types of differences there are when running alternatives in the ROM Dept.....fluid transitions, non changing wallpapers, and the like?
Can't give you a thanks yet because of low post count, but this is exactly the sort of thing someone needed to do.
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
guides and explanations
Its good to see your hints, because all those really awsome videos have their traps and you can easily get trapped on it, as i did and i had a hard time to find the right way.
My secret for this is to fully understand why you have to do this and that, and here all the guides lack, because there is no explanation WHY you have to do this.
This needs more love. I was successful, because i know from my old background how a chmod works, why i had to install the drivers again and so on but it really took me a while to get this all done, because i didnt read this thread in time.
I also understand that developers are excited about their custom roms and the cyanogenMod, but really who wants to have a kindle fire without sound and a mod with so many bugs ?
I am so happy to have my kindle fire rerooted again after the latest update without opening it or using a special cable.
So this all works quite well, but the guides really need some more explanations to get a deeper understanding about what we are doing here.
I am still working on that, to learn the details.
I want to say a big thank you to all who invested their free time and to spread the knowledge about this awsome device and make the kindle fire a really usefull tablet.
Please keep on the good work ! And have fun with a fully rooted device. There are so many possibilities now !
JoshuaLintag said:
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
Click to expand...
Click to collapse
You are very welcome I am glad to see that this guide helped you to get this accomplished!
Don't forget to give a big thanks to Jcase for Burrito Root and Vashypooh for Kindle Fire Utility!
BeerRunJoe said:
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Click to expand...
Click to collapse
I am glad to see that you got through this flawlessly. This thread was made just for that very reason to help the lesser experienced user with any issues they might encounter without having to post threads that may get lost in all of the other "Help Me" threads...
If there is a mod that could please sticky this thread I do believe this will answer many questions for individuals and help new users pull off a flawless root, recovery, etc...
+1 on stickying this thread. I have just been pointing people having the same basic problems here. This thread (especially the OP) seems to be helping a lot of people who need help "filling in the blanks".
Good job [-_-]!
I have also directed many of my friends to this thread and they have also gotten through their minor problems. It is kind of funny because a lot of my friends tell me I think my kindle is bricked I just laugh say I doubt it and send them here. Can you also make a guide about going from cm7 back to a the amazon rom please. I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
BeerRunJoe said:
I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
Click to expand...
Click to collapse
Yes this will work...
1.Plug in USB cable to Kindle Fire on TWRP Recovery mode.
2.Bring up Command Prompt.
3.Key in adb shell.
4.Key in idme bootmode 4000.
5.Finally, key in reboot.
There you go..!!!
Great tutorial setup. Rooted, installed Android Market as mentioned without any issues. Have not installed the Recovery yet though.
Thanks for this thread.
I have an Acer 500a I just bought off carigslist. Initially I thought it would be fine but then I realized I was inheriting someone elses problems. I hope someone may be able to help.
Within the first few hours I was noticing google Play crashed a number of times and struggled to update from Market. Somehow the update went through but now there is a system update that won't go through. I'm able to down load it and when i restart the computer to complete installation the screen goes black and says: booting recovery kernel in the corner. I then see a picture of an android and a load bar which after 2-4 seconds the android is on his back and an exclaimation mark is coming out of his belly.
My android version is 3.2
Kernel version
2.6.36.3+
Build number
Acer_a500_7.006.01_COM_GEN2
I'm pretty sure its rooted and i think that might be why its not playing nice with google market and system updates. I called the old owner and explained the problem and he just said he had it rooted and he thought he unrooted it. There is an ap called superuser in aps. (although if it were rooted would'nt I be able to uninstal some of thecrap software it comes with like GOLF HD? -- it won't let me).
The system update is for Acer_a500_7.014.01_COM_GEN2 8.88mb
My problem is all of the force closes I'm getting and the inability to update the system. Any thoughts? I don't have a usb cord to connect it to a desktop either =(
I am a bit out of practice, but...
Should be pretty simple to fix. From what I am seeing, you are running a stock rom. Just because the superuser.apk is installed on the system does not mean it is rooted, but it probably is.
Hit the market, grab "Root Checker" - simple tiny program to let you know for sure if your tab is rooted or not.
https://play.google.com/store/apps/details?id=burrows.apps.rootchecker&hl=en
From what I understand - automatic system updates will fail when trying to apply them to a rooted or modded system. Probably why you cannot auto-update.
My advice at this point would be to:
1) Since you just bought it, just do a factory wipe on it. That will remove all the stuff the prior owner had running on it and will result in a unrooted tab that should be able to get auto updates without a problem.
2) Un-Root it. Once the tablet is unrooted, the system should update without any issue.
As for your Play Store issues - I have never heard of or personally seen any issues caused with installing apps from the store on a rooted device. I have seen a few apps that will refuse to run on a rooted device - but that does not sound like your problem.
I would go with option 1 - just factory wipe the thing. Prior owner may have made tons of changes to the OS that we will never know about, and may have handed you a unstable system. Start fresh. Wipe it out.
Hope this helps you out! Let me know if I can answer any questions.
k thank you so much for the quick reply! I downloaded the root checker and it Is rooted. I did a factory wipe as found in the settings privacy tab when I bought it. That factory reset did not unroot and only cleaned out some of the aps on the device. Is there a better or more surefire way to unroot it? If I reset with the volume down key will it hard reset it?
Thank you for you help!
Draight
Okay.
I am about a year out of practice with my a500 - but from what I am think, if a factory reset still results in a rooted device - the prior user installed a stock ROM that comes pre-rooted.
I highly doubt being rooted is causing the issues you are running into.
At this point if you just want to get back to stock you can probably just install the Acer Recovery Manager from the market and use it to reflash a stock unrooted ROM. Or I see a few guides about how to manually restore back to stock over in the dev section for the a500.
Others will correct me if I am wrong, but I think Acer Recovery Manager should take care of your problem.
Hope this helps!
(Edit: Or you can just download the official stock 4.x rom (ICS) from the dev section and flash that. 3.2 is pretty slow and wonky in my experience, you should be able to just download a 4.x ROM and flash, since you are rooted. Again, I am way out of practice. Don't do anything before reading up!)
(Edit again: I think I was making this harder then needs be. Just flash any stock 3.2 unrooted ROM, done. After you do that the automatic on the air update should kick in for you and update you to ICS)
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
draight said:
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
Click to expand...
Click to collapse
Hmmm..
Try the thread I linked two in my second edit of my last post. You just need to grab the stock and unrooted 3.2 - put it on a MicroSD card as update.zip - then reboot with vol rocker and power switch to get the system to flash the update.
That *should* work just fine.
(Edit: Forgot the link! http://forum.xda-developers.com/showthread.php?t=1839313 - there you go)
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
draight said:
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
Click to expand...
Click to collapse
Nope. Just snag the stock unrooted 3.2 ROM - place it in the root of the MicroSD card as update.zip
Power down.
Power up with VOL + and POWER key held at the same time (you can let the vol rocker go when you see text appear in the upper left corner)
Should be all you need to do. Worst case; it does not work and returns you back to where you are now. Worth a shot.
If that does not work, let me know so I can do a few mins of homework and help you further. Been a long time since I have changed ROMS or had any issues with my a500.
I have bricked it twice by not following directions all the way or just making simple mistakes, but from what I have found there is always a way to recover.
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
draight said:
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
Click to expand...
Click to collapse
Hmmm. Odd.
Like I said, I am rather out of practice.
Someone more experienced them me: please help me point Draight in the right direction here?
Thanks for trying to help. =(
I wish that my tablet wasn't having such issues. I;m going to try to scramble around the forums and see if I can find some advice...If anyone has a suggestion please let me know.
Thanks again entropy,
Draight
Update:
So I've been tinkering around with it a bit more and I found a usb cord that plugs it into my computer. I keep finding boken links on this site so Im struggling to find an update I can use to flash to. I downloaded a different super user program which allowed me to temporarily unroot my device. I then restarted it and no root checker says its no rooted and I cannot find the superuser program. I think I have somewhat unrooted it -- but I think the real issue now is the recovery tool. I keep reseting it - hard reset, or factory reset and it wipes everything away but when i try to update it gets about 1/3 of the way up the bar then it stops with an '!' Mark above the droid. Im kind of annoyed at this point and hoping for some new links or some ideas on how to repair the recovery piece.
Draight
Go to the Dev section, and grad a couple of the ICS Update roms. You will see them listed for the a500. Make sure they are the FULL update roms. Should be about 3-400mb. These contain a FULL ICS Update Rom, and not a patch file.
http://forum.xda-developers.com/showthread.php?t=1816560
Then, go to the Themes and apps forum. You'll see a sticky that has the Acer Update Decrypter.
http://forum.xda-developers.com/showthread.php?t=1869505
Now, unpack the decrypter, and select one of the ICS Updates. Then hit Start. Take a couple minutes, but you will have a duplicate file with the word "decrypted" added to it.
Wait, you are not done yet.
Using a program like 7zip, or even Winzip, open the decrypted file. DO NOT EXTRACT, just open it and pull the update.zip to your PC's desktop.
Copy that update.zip file to your Ext SD Card of the tablet. Don't be putting it in any folder, just copy it to the root of the card.
Now, you still ain't done.
With the tablet off. Press and hold Vol+ and then PWR. Hold them both untill you start to see text about installing blah blah blah, then release the buttons.
If it completes, and you can reboot into ICS, then you are good to go.
If something fails during installation, then decrypt the other update Rom file you downloaded, and do the same procedure. Usually one of the 2 or three should work for you.
Note these are for the a500, and not the a501.
One more thing. It's advisable you get your UID number before doing these things. You probably won't need it, but it's nice to have written down in case you need it in the future. Inf to get it is at;
http://forum.xda-developers.com/showthread.php?t=1624645
MD
Thanks! I am downloading a few of the FULL ICS roms:
*Acer_A500_1.031.00_WW_GEN1 : http://d-h.st/uAy
Acer_A500_1.031.00_PA_CUS1: http://d-h.st/idO
Acer_A500_1.041.00_WW_CUS1: http://d-h.st/Yt5
*Acer_AV041_1.054.00_WW_GEN1: http://www.theandroidcollective.org/...00_WW_GEN1.zip
*Acer_A500_7.014.16_041.206.01_COM_GEN1: https://docs.google.com/file/d/0B_bk...hVc1RVcHc/edit
The I downloaded the ones ending with Gen1. Once they are downloaded I will continue with the instructions. Thank you so much for your help! I will post how it goes later tonight.
Draight
I just decrypted both:
*Acer_AV041_1.054.00_WW_GEN1:
*Acer_A500_1.031.00_WW_GEN1
Both get get to the third bullet quickly and the bottom says DONE! It takes like 4 seconds. I don't think the Decryption key of $12 is working
[*] Opening file: Acer_A500_1.031.00_WW_GEN1.zip
[*] Decrypting using key $12
[*] Writing decrypted file: Acer_A500_1.031.00_WW_GEN1_decrypted.zip
I try to extract something from the decrypted file and it says the file was not downloaded properly and I should try redownload it...it says its not a proper archive
wahoo!
So that worked! I down loaded the file Acer_AV041_A500_1.033.00_PA_CUS1 and extracted the update. I palced the update on the sd card and booted with the power and sound volume pressed down. it went through the installation procedure and restarted twice before saying it was upgrading my aps and BOOM its got ICS and everything looks great. Thank you so much for your help and I hope that this paper trail is able to help someone in the future
My problem is that I'm on ICS and I'm rooted, but I just can't download a custom recovery. I've tried, and I haven't gotten anywhere
Sent from my SPH-L710 using Tapatalk 2
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.
Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.
Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.
What ROM was on it before you flashed B09?
Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!