Related
Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.
you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.
thanks
Thanks for the quick response! I'll try that.
Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.
gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.
So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.
working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.
David, now that it is working, I would recommend updating your recovery to 1.5.2.
I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.
I have been working on this for the past few days and for the life of me cannot figure out the problem. I'll start by just laying out a sequence of events.
Bought A500 about a month ago. OTA'd to HC 3.1 4.010.13_com_gen2
Decided not to wait for OTA 3.2 and rooted with iconiabreak.
Did not do a backup (like an idiot, i know)
Flashed Taboonay 2.0 with Thor's 2.1 kernal.
Saw awesome post to get rid of cell standby by deleting phone.apk and telephony.apk....do i did that.
Realize i am an idiot and then run a Nandroid backup.
Was happy for a few weeks when i see that Vache had updated taboonay to 2.1b and decided i wanted to do that.
Downloaded the files and started to flash with CWM. Factory, cache, dalvik wipe. Run Taboonay zip.
Get stuck in bootloop at Taboonay boot screen. $#!t......
Think "it's ok, ill just do an update.zip and go back to 3.1"
Try almost all the files on Vache's full package and update thread.
I put each one on an ext sd card and throw it into recovery boot. The Android guy with gears shows up and it looks like it is going to work.
The progress bar gets about 90-95% of the way when everything just stops. Gears animation, progress, everything.
It then reboots and gets stuck in a bootloop at the android screen. Load a different update.zip and same thing happens each time.
I try to just do a normal recovery boot, but CWM isnt there anymore and i get the ! android.
Normal reboot gives me a bootloop.
So i am stuck and asking if it is the phone and telephony apks that caused everything? if that were the case, how would i be able to load them back up since im totally locked out. I havent tried adb since im out of town for a few days. Thanks for any help that anyone can lend me. Ill try to answer any questions for any information that might be needed.
bumping for great justice~
I've tried decrypting update.zip files and vice versa.
still no luck..
try the fall back to 3.0.1
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
rorohajj said:
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
Click to expand...
Click to collapse
Thanks for the reply.
I don't think that will be a viable option for me since i'm not able to get my UID. i've plugged my tablet into the computer and gotten the "hardware found" bubble. It prompts me to look for drivers (which i havent be able to find) and, i assume because it's in a bootloop, wont show up on the computer.
Does anyone know why the update.zip files would fail at 90%? I think that's really the thing that boggles my mind and is most frustrating.
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
jeffw111 said:
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
Click to expand...
Click to collapse
Unfortunately, no I never plugged my A500 into my computer.
quick update:
I was able to use a different computer and found something interesting.
While trying to transfer or open a decrypted update.zip file, i get an error message saying, "Please insert the last disk of the Multi-Volume set and click OK to continue". Clicking OK just brings it back and i am forced to click cancel.
Anyone have any idea what that would mean??? It doesnt happen when I open or transfer the non-decrypted file. Only the decrypted file using Thor's Acer Update Decrypter application on HC 3.1 and 3.2 files.
While loading the decrypted update.zip on the A500, it almost instantly shows the ! android guy, while the non-decrypted files go 90-95% and then reboot into bootloop.
Any help would be greatly appreciated!
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
erica_renee said:
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
Click to expand...
Click to collapse
Thanks for your reply, first off.
I'm sorry I didn't make it clear that I had done all of those things during the events of the first post EXCEPT try a different sd card.
So I went out today and bought a PNY 2GB sd card as opposed to the SanDisk 4GB i was using. I formatted it in my Atrix 4G and threw a full update.zip file in there. The first file I tried (from Vache's http://forum.xda-developers.com/showthread.php?t=1113878 thread) was Acer_A500_4.010.38_COM_GEN1 (HC 3.1). Since I was able to open the .zip without decrypting it I loaded it only the sd card. It did the same thing as before (loaded to about 90% then freeze, reboot) except this time I got a "Boot verification failed..." message in bright red letters up at the top left of the Acer screen. Since it didn't work, I loaded Acer_A500_7.006.03_COM_GEN2 (HC 3.2) onto the sd card. Again, since I was able to open the .zip file, I assumed that there was no need to decrypt it. Loaded the sd card and put the tablet into default recovery (not CWM recovery which I no longer have). The same problem keeps happening: it loads to 90%, freezes then reboots. This time, however, it went into a bootloop at the "android" screen.
I've tried decrypted versions of those files, but I always get an error message while trying to open them and when trying to flash them in default recovery, it almost instantly goes to the ! android guy since I'm assuming those files are already decrypted and decrypting them again is bad.
Hopefully if I try enough files, I'll find the one that works...
Until then, if anyone has any ideas as to what I might be doing wrong or should be doing differently, please let me know!
Thanks.
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
erica_renee said:
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
Click to expand...
Click to collapse
Thanks for your suggestion.
I was able to find my UID from an old CWM backup file and tried this method. I attempted it last night with no success. I was actually in the middle of making a reply saying how heartbroken I was and that I was basically giving up. I decided to try it one more time and made a slight adjustment from my method last night. In the UID file, I had my UID in there as 0x0blahblahblah and kept getting the incorrect UID error in the program. When I tried taking out the first 0x in the program, it gave me an incorrect format error. That is where I was messing up.
Instead of 0x0, all i needed was 0blahblahblah in the UID file.
Attempted the upgrade utility again, and viola! It worked like a champ.
So thanks again to all that helped out and offered suggestions and to all the Devs for their outstanding work. I've definitely learned a lot from this experience.
Hi everyone.
Just repeating again - the model I have is A501 on stock 3.2.1 Honeycomb - a more USEFUL tablet with 3G and WIFI capabilities...One would think it would be a much more popular model, but the A501 doesn't have its own board on XDA; its merged with this board for the less practical A500. Basically, I have created this thread as I don't want to take any 'extra' risks in successfully installing ROOT with the CORRECT ROM with the most updated version of Android available for this tab, for example Jellybean...
Another A501 user, beny9 posted:
http://forum.xda-developers.com/showthread.php?t=1745550
Following TimmyDean's method (thank you) I have now managed to install 3.2 Honeycomb A500 ROM with success after completing steps 1-15 inclusive from his README file. As you will know, I don't have 3G or GPS functionality, so I need a stock A501 ROM to install.
I have found:
http://forum.xda-developers.com/showthread.php?t=1113878
Is my best bet to install Acer_A501_1.309.02_4.031.24_COM_GEN1 : http://cdn.a1.futuredial.com/Acer_A5...2_35b68c5d.zip from that above link, which will keep me on HC 3.2 but now, it will be the ROM for the A501? As it seems the only other NEWER Acer updates for ICS are A500 only...
Can someone link me the a fully detailed video or post on here on installing the ROM i mentioned above (if that's the best one to go with, given what I'm on now; A500 3.2 and still keeping root), or to install some other A501 ROM which is for at least Jellybean or ICS?
http://forum.xda-developers.com/showthread.php?t=1828876
Per this link, shoukd i just use the update.zip (for the 3.2 HC A501 ROM) put it on the SD card then boot up holding POWER + VOL DOWN until the file auto-installs?
http://forum.xda-developers.com/showthread.php?t=1099673
Before I can try the above, I also have trouble after i download the ROM's zip file when I try to unzip. I have downloaded the Acer Update Decrypter, but AVG antiVirus will not allow me to run the EVE file even as an administrator. What should i do?
Thanks
RoOSTA
Your best bet is to install a good 501 HC 3.2 and get on HC for your 501.
The files are available. What you'll probably want is a full HC Update rom for the 501. Note that some of these Acer roms are encrypted, so you'll need to decrypt it first. You can find the decrypting tool in the Themes and Apps forum, as a "Sticky". After decrypting, you can pull the update.zip out of it, and copy to Ext SD (do not extract, just pull the update file out). Boot the tab holding Vol- and PWR I believe. Might be Vol+ but I can't remember. This should force the tab to look for update.zip on your SD and install it.
I would use this one;
Acer_A501_1.309.02_4.031.24_COM_GEN1
After it installs, and you get it set up, you need to get Acer Update Enhancer from the Play Store. This will allow your tab to get the ICS OTA.
Keep in mind, there is only 1 official ICS OTA update for the 501, so don't expect more. It may do it in 2 steps though.
If you want root on ICS, there is really only 1 way to get true root and adb system remounts. And that's to flash the V8 unlocked ICS Bootloader, and flash an insecure boot.image. There's currently a small package that'll give you somewhat root, but it's a pain and really doesn't do a good job. So it's better to get the V8 and unsecure boot image. Might be a good idea to also install CWM Recovery at the same time.
Get the correct rom installed first, then check back if you need help.
Oh yeah, one more thing. When you are on HC 3.2, get your UID number and write it down somewhere. You need this as a safety precaution. There's a good sticky thread on how to do it. Pretty simple really.
MD
Ugh. I have a pain in the A$$ version of AVG...even under advanced settings there was no disable options. Managed to figure it out to run the Acer Decrypter EXE and fix the image you have advised I should download and flash. Will give that a go now...
Thanks again!
Just to fill you in, this issue is solved.
1. Used TimmyDeans rollback V4 tool to a 500 rom
2. SD card was not recognized in CWM or Stock recovery. Was however recognized in the HC OS.
3. Formatted SD Card using Mini Tool formatting app. Format primary partition only to fat32 (defaults)
4. Decrypted and pulled update.zip from this 501 HC full update rom
Acer_A501_1.309.02_4.031.24_COM_GEN1
http://forum.xda-developers.com/showthread.php?t=1816560
5. Did OTA update to 3.2.1
6. No more OTA available, even after installing Acer Update Enhancment tool.
7. Downloaded and used Blackthund3rs Bootloader management app
http://forum.xda-developers.com/showthread.php?t=1622425
8.Downloaded V8 and CWM package, unzipped to the same folder as the tool
9. Ran the 500NVFlashapx app.
10. After completion, booted to CWM recovery, wiped and formatted, and install Moscow Desire's RaptorX almost stock ICS rom.
Works as advertised.
MD
Yep. All thanks to MD's patience and assistance throughout these steps..
Moscow Desire said:
Just to fill you in, this issue is solved.
1. Used TimmyDeans rollback V4 tool to a 500 rom
2. SD card was not recognized in CWM or Stock recovery. Was however recognized in the HC OS.
3. Formatted SD Card using Mini Tool formatting app. Format primary partition only to fat32 (defaults)
4. Decrypted and pulled update.zip from this 501 HC full update rom
Acer_A501_1.309.02_4.031.24_COM_GEN1
http://forum.xda-developers.com/showthread.php?t=1816560
5. Did OTA update to 3.2.1
6. No more OTA available, even after installing Acer Update Enhancment tool.
7. Downloaded and used Blackthund3rs Bootloader management app
http://forum.xda-developers.com/showthread.php?t=1622425
8.Downloaded V8 and CWM package, unzipped to the same folder as the tool
9. Ran the 500NVFlashapx app.
10. After completion, booted to CWM recovery, wiped and formatted, and install Moscow Desire's RaptorX almost stock ICS rom.
Works as advertised.
MD
Click to expand...
Click to collapse
Acer A501 OS refreshment
Moscow Desire said:
Your best bet is to install a good 501 HC 3.2 and get on HC for your 501.
The files are available. What you'll probably want is a full HC Update rom for the 501. Note that some of these Acer roms are encrypted, so you'll need to decrypt it first. You can find the decrypting tool in the Themes and Apps forum, as a "Sticky". After decrypting, you can pull the update.zip out of it, and copy to Ext SD (do not extract, just pull the update file out). Boot the tab holding Vol- and PWR I believe. Might be Vol+ but I can't remember. This should force the tab to look for update.zip on your SD and install it.
I would use this one;
Acer_A501_1.309.02_4.031.24_COM_GEN1
After it installs, and you get it set up, you need to get Acer Update Enhancer from the Play Store. This will allow your tab to get the ICS OTA.
Keep in mind, there is only 1 official ICS OTA update for the 501, so don't expect more. It may do it in 2 steps though.
If you want root on ICS, there is really only 1 way to get true root and adb system remounts. And that's to flash the V8 unlocked ICS Bootloader, and flash an insecure boot.image. There's currently a small package that'll give you somewhat root, but it's a pain and really doesn't do a good job. So it's better to get the V8 and unsecure boot image. Might be a good idea to also install CWM Recovery at the same time.
Get the correct rom installed first, then check back if you need help.
Oh yeah, one more thing. When you are on HC 3.2, get your UID number and write it down somewhere. You need this as a safety precaution. There's a good sticky thread on how to do it. Pretty simple really.
MD
Click to expand...
Click to collapse
I am embarking on a very crucial mission for my Acer A501 . Its tablet OS refreshment. I have spoken and written to Acer but all my pleas have fallen on deaf ears. At last i stumbled on this site and WOW ! I am downloading the Acer_A501_1.309.02_4.031.24_COM_GEN1 and will flash as per the instruction. But I am finding difficult to locate the "sticky" software for the decryption the above. can you please help me locate the same.
I really appreciate your help and thank you in advance
jonnybrave said:
I am embarking on a very crucial mission for my Acer A501 . Its tablet OS refreshment. I have spoken and written to Acer but all my pleas have fallen on deaf ears. At last i stumbled on this site and WOW ! I am downloading the Acer_A501_1.309.02_4.031.24_COM_GEN1 and will flash as per the instruction. But I am finding difficult to locate the "sticky" software for the decryption the above. can you please help me locate the same.
I really appreciate your help and thank you in advance
Click to expand...
Click to collapse
Here is the decryption tool. Located in themes and apps.
http://forum.xda-developers.com/showthread.php?t=1869505
Good Luck!
MD
Trouble installing update.zip for A501
Moscow Desire said:
Here is the decryption tool. Located in themes and apps.
http://forum.xda-developers.com/showthread.php?t=1869505
Good Luck!
MD
Click to expand...
Click to collapse
Hi MD,
I have Acer Iconia A501 tablet. My tablet suddenly showed andriod logo with exclamation mark when it was being used. Upon looking at your posts, I found the resolution which I tried. I am not expert in this all, but I tried running your ROM "41-124-01-A500-update" from one of your posts which was actually meant for A500. This resolved the issue successfully and tablet was up and running.
Then further I found full ROM for A501 as mentioned below and thought that I should try the ROM meant for the model of my tablet.
I successfully decrypted the ROM that you mentioned "Acer_A501_1.309.02_4.031.24_COM_GEN1"
When I tried to update it with the mentioned ROM update.zip, it did updated it from SD card and passed android symbol with those gears running. However, when it restarted the tablet by itself, it showed ACER logo and then it showed "ANDROID" (spelling in blue color) which kept on flikering slowly for long long time....for more than 30 minutes and did not moved further. Can you please let me know whats could be wrong?
I also tried ICS ROM, but that didn't worked (it failed). So after couple of trail and error, I moved back to A500 ROM update.zip which I knew that is installing successfully.
Can you please let me know what shall be done in case I want update.zip for A501? It will be highly appreciated if you can upload update.zip directly that I can use and that gets installed successfully.
Regards,
Muk
mukapril said:
Hi MD,
I have Acer Iconia A501 tablet. My tablet suddenly showed andriod logo with exclamation mark when it was being used. Upon looking at your posts, I found the resolution which I tried. I am not expert in this all, but I tried running your ROM "41-124-01-A500-update" from one of your posts which was actually meant for A500. This resolved the issue successfully and tablet was up and running.
Then further I found full ROM for A501 as mentioned below and thought that I should try the ROM meant for the model of my tablet.
I successfully decrypted the ROM that you mentioned "Acer_A501_1.309.02_4.031.24_COM_GEN1"
When I tried to update it with the mentioned ROM update.zip, it did updated it from SD card and passed android symbol with those gears running. However, when it restarted the tablet by itself, it showed ACER logo and then it showed "ANDROID" (spelling in blue color) which kept on flikering slowly for long long time....for more than 30 minutes and did not moved further. Can you please let me know whats could be wrong?
I also tried ICS ROM, but that didn't worked (it failed). So after couple of trail and error, I moved back to A500 ROM update.zip which I knew that is installing successfully.
Can you please let me know what shall be done in case I want update.zip for A501? It will be highly appreciated if you can upload update.zip directly that I can use and that gets installed successfully.
Regards,
Muk
Click to expand...
Click to collapse
Hey Muk, I can probably guess the ROM you installed doesn't do data wipes and such, so it caused an animation loop.
Try this one. It's an SD ROM, so it "should" wipe your Data, along with installing the ROM.
https://mega.co.nz/#!NZBlBSLQ!mOHICp7gbinkYeHCvrEz7aKXsWQjjquAWq_XC_lSQzk
As you probably discovered, Acer has pretty much removed almost all tablet ROMs. I snagged a few the other day, then checked yesterday, and they removed all from their support site.
I would guess they are getting out of the tablet business.
Also, they shut down their OTA Update servers for a few months now.
Acer A501
mukapril said:
Hi MD,
I have Acer Iconia A501 tablet. My tablet suddenly showed andriod logo with exclamation mark when it was being used. Upon looking at your posts, I found the resolution which I tried. I am not expert in this all, but I tried running your ROM "41-124-01-A500-update" from one of your posts which was actually meant for A500. This resolved the issue successfully and tablet was up and running.
Then further I found full ROM for A501 as mentioned below and thought that I should try the ROM meant for the model of my tablet.
I successfully decrypted the ROM that you mentioned "Acer_A501_1.309.02_4.031.24_COM_GEN1"
When I tried to update it with the mentioned ROM update.zip, it did updated it from SD card and passed android symbol with those gears running. However, when it restarted the tablet by itself, it showed ACER logo and then it showed "ANDROID" (spelling in blue color) which kept on flikering slowly for long long time....for more than 30 minutes and did not moved further. Can you please let me know whats could be wrong?
I also tried ICS ROM, but that didn't worked (it failed). So after couple of trail and error, I moved back to A500 ROM update.zip which I knew that is installing successfully.
Can you please let me know what shall be done in case I want update.zip for A501? It will be highly appreciated if you can upload update.zip directly that I can use and that gets installed successfully.
Regards,
Muk
Click to expand...
Click to collapse
A big thank you to Moscow. I have tried the above link but still no go.. I have seen on Acer website they have updated the OS but all Android 4.0 ICS and nothing with Honeycomb. The tablet was initially with Honeycomb. Please advice. Thank you and Best Regards.
Trouble installing ROM for A501
jonnybrave said:
A big thank you to Moscow. I have tried the above link but still no go.. I have seen on Acer website they have updated the OS but all Android 4.0 ICS and nothing with Honeycomb. The tablet was initially with Honeycomb. Please advice. Thank you and Best Regards.
Click to expand...
Click to collapse
Hi MD,
Thanks for your super fast response. I am downloading the ROM for A501 from the link provided by me. I will update you if it works in my tab.
I forgot to mention you about one message that I received once tablet is restarted. So, once ROM for A501 from SD card has performed its job successfully....that is that android symbol with gears in its tummy is successfully finished and tablet restarts. It shows "Acer" (spelling logo) and then after it gets stuck at "android" (spelling logo). Between these two, it displays two lines messages on top left corner for 2-3 seconds that the "blob is illegal - abort" and then gets stuck at "android" (spelling logo). I think this might be useful for you to identify something.
Another thing about wiping out the data, in starting when we press volume down and power button, it does display message about SD card (still not not sure about whether it might be wiping out the data or not....I believe you might be correct that it might not be wiping out the data).
Another thing, that I found in my backup is that when I purchased this tab (A501), I downloaded HoneyComb 3.2 Kernel Source Code from the Acer support site. Is this something that you can do magic with and provide me with update.zip? Please let me know....if you can do magic with this, then let me know how shall I share it with you.
Regards,
Muk
Trouble installing ROM for A501
Hi MD,
Thanks for your super fast response.
I tried downloading the ROM for A501 from the link provided by you. It downloaded it from the cloud, but at the very end it displayed message "Decryption Error". Still I tried extracting "update.zip" from the zip file, but it displayed message that the archive is corrupt and file is corrupt. Can you please check at your end and provide me with fresh link or directly with update.zip? For your reference I have attached screenshots of errors.
I forgot to mention you about one message that I received once tablet is restarted. So, once ROM for A501 from SD card has performed its job successfully....that is that android symbol with gears in its tummy is successfully finished and tablet restarts. It shows "Acer" (spelling logo) and then after it gets stuck at "android" (spelling logo). Between these two, it displays two lines messages on top left corner for 2-3 seconds that the "blob is illegal - abort" and then gets stuck at "android" (spelling logo). I think this might be useful for you to identify something.
Another thing about wiping out the data, in starting when we press volume down and power button, it does display message about SD card (still not not sure about whether it might be wiping out the data or not....I believe you might be correct that it might not be wiping out the data).
Another thing, that I found in my backup is that when I purchased this tab (A501), I downloaded HoneyComb 3.2 Kernel Source Code from the Acer support site. Is this something that you can do magic with and provide me with update.zip? Please let me know....if you can do magic with this, then let me know how shall I share it with you.
Regards,
Muk
Trouble installing ROM for A501
Hi MD,
Please read my earlier message and then read this one.
Thanks a lot....your answer about my first problem resolved everything.... (your answer was "that the ROM that I am trying to install is not clearing the data"...I verified that the ROM is clearing the cache, but not the user data. I can confidently say that you correctly identified the issue as when the ROM installation was stuck at "android"....I switched off my tablet and tried installing again the old ROM for A500 which I knew that it is working and instead of asking me to configure the tablet (i.e. time zone, date & time setup, etc.) after installation, it simply logged in and started my tablet as usual....that means that when I was trying to install ROM for A501, it was not clearing user data and was then hanging).
Now coming back to the link that you sent me in previous message, I was able to download the zip file successfully in the second attempt. I extracted the update.zip and it did not work. It showed the similar problem of getting stuck at "android". However, with your great answer that you gave me, I cleared the user data and cache manually by pressing vol up + power buttons simultaneously and then when "acer" symbol displays, releasing only power button and turning on and off the lock button. This cleared user data and cache. After that, since update.zip (that you provided) was already in my SD card, it installed the ROM and tablet works perfectly. Thanks a lot....:good:
One question, when it asked me about the zone, it had only few countries like US, UK, etc. I couldn't find Australia...is it because this ROM not for Australia? I understand that this is not an issue, but if you find anything for Australia, do send me.
Another thing, is this HoneyComb 3.2? Will 3G and GPS work in this one?
Do let me know if you can do some magic with HoneyComb 3.2 kernel source code that I have as mentioned earlier.
Regards,
Muk
mukapril said:
Hi MD,
Please read my earlier message and then read this one.
Thanks a lot....your answer about my first problem resolved everything.... (your answer was "that the ROM that I am trying to install is not clearing the data"...I verified that the ROM is clearing the cache, but not the user data. I can confidently say that you correctly identified the issue as when the ROM installation was stuck at "android"....I switched off my tablet and tried installing again the old ROM for A500 which I knew that it is working and instead of asking me to configure the tablet (i.e. time zone, date & time setup, etc.) after installation, it simply logged in and started my tablet as usual....that means that when I was trying to install ROM for A501, it was not clearing user data and was then hanging).
Now coming back to the link that you sent me in previous message, I was able to download the zip file successfully in the second attempt. I extracted the update.zip and it did not work. It showed the similar problem of getting stuck at "android". However, with your great answer that you gave me, I cleared the user data and cache manually by pressing vol up + power buttons simultaneously and then when "acer" symbol displays, releasing only power button and turning on and off the lock button. This cleared user data and cache. After that, since update.zip (that you provided) was already in my SD card, it installed the ROM and tablet works perfectly. Thanks a lot....:good:
One question, when it asked me about the zone, it had only few countries like US, UK, etc. I couldn't find Australia...is it because this ROM not for Australia? I understand that this is not an issue, but if you find anything for Australia, do send me.
Another thing, is this HoneyComb 3.2? Will 3G and GPS work in this one?
Do let me know if you can do some magic with HoneyComb 3.2 kernel source code that I have as mentioned earlier.
Regards,
Muk
Click to expand...
Click to collapse
I'm mobile right now, so can't go into big detail.
In your settings, about tablet, you can always find info on which specific OS you have. If you indeed have an A501 and the settings tells you that your tablet is a 501, then your 3g and GPS should function.
The only 2 differences between an A500 and an A501 is of course 3g. Also, they use different GPS radios. So you can install 500 Roms on a 501 and vice versa. Just the above 2 items won't work. Also, I believe I gave you a 3.2.x ROM. Getting it to ICS 4.0.4 may be a problem.
I revived my own 501 last night by putting the motherboard in the oven, but now it doesn't read my ext SD card, so I may be stuck on 3.2. Eh, no problem.
mukapril said:
Hi MD,
Please read my earlier message and then read this one.
Thanks a lot....your answer about my first problem resolved everything.... (your answer was "that the ROM that I am trying to install is not clearing the data"...I verified that the ROM is clearing the cache, but not the user data. I can confidently say that you correctly identified the issue as when the ROM installation was stuck at "android"....I switched off my tablet and tried installing again the old ROM for A500 which I knew that it is working and instead of asking me to configure the tablet (i.e. time zone, date & time setup, etc.) after installation, it simply logged in and started my tablet as usual....that means that when I was trying to install ROM for A501, it was not clearing user data and was then hanging).
Now coming back to the link that you sent me in previous message, I was able to download the zip file successfully in the second attempt. I extracted the update.zip and it did not work. It showed the similar problem of getting stuck at "android". However, with your great answer that you gave me, I cleared the user data and cache manually by pressing vol up + power buttons simultaneously and then when "acer" symbol displays, releasing only power button and turning on and off the lock button. This cleared user data and cache. After that, since update.zip (that you provided) was already in my SD card, it installed the ROM and tablet works perfectly. Thanks a lot....:good:
One question, when it asked me about the zone, it had only few countries like US, UK, etc. I couldn't find Australia...is it because this ROM not for Australia? I understand that this is not an issue, but if you find anything for Australia, do send me.
Another thing, is this HoneyComb 3.2? Will 3G and GPS work in this one?
Do let me know if you can do some magic with HoneyComb 3.2 kernel source code that I have as mentioned earlier.
Regards,
Muk
Click to expand...
Click to collapse
Hello mukapril .. may you provide me with the Honeycomb ROM which I might try ?
Thanking you and Best Regards
Trouble installing A501 ROM
Moscow Desire said:
I'm mobile right now, so can't go into big detail.
In your settings, about tablet, you can always find info on which specific OS you have. If you indeed have an A501 and the settings tells you that your tablet is a 501, then your 3g and GPS should function.
The only 2 differences between an A500 and an A501 is of course 3g. Also, they use different GPS radios. So you can install 500 Roms on a 501 and vice versa. Just the above 2 items won't work. Also, I believe I gave you a 3.2.x ROM. Getting it to ICS 4.0.4 may be a problem.
I revived my own 501 last night by putting the motherboard in the oven, but now it doesn't read my ext SD card, so I may be stuck on 3.2. Eh, no problem.
Click to expand...
Click to collapse
Hi MD,
Apologies for very long replies. Wanted to convey the message in detail how I did it so that it might help someone else like me.
Thanks for your response. I have tested it, 3G and GPS is working fine. I believe, before my tab encountered this problem, it was having version 4 which should be ICS. At that stage I didn't had any problem with my tab...I believe it was there for long time.
If you have good known ROM for ICS, please forward me I can try on my tab. If it doesn't work, then will re-install the Honeycomb that you sent earlier.
One more question....when I try to update the system from "About Tablet" in Settings, why it displays message the the "network is poor" and advices to move to better coverage? Though, I am just besides my WiFi modem and coverage is almost 100%.
And @jonnybrave: If you are referring to the ROM that I successfully installed which was sent by MD earlier, then it does not need any decryption. So you can use the link sent by MD earlier in this post. And if you are referring to the KernelSourceCode that I mentioned earleir, then it needs some kind of processing in Linux machine and then you can create some image.....this is was I know about it....sorry not an andrion guru. Please let me know what you are referring to.
Regards,
Mukesh
mukapril said:
One more question....when I try to update the system from "About Tablet" in Settings, why it displays message the the "network is poor" and advices to move to better coverage? Though, I am just besides my WiFi modem and coverage is almost 100%.
Click to expand...
Click to collapse
You get the message as do all 500/501 owners (it can change depending on version of Rom).
Acer no longer gives updates to any of their devices (regardless of age). These are otherwise known as OTA Updates. So they have closed their update servers, so now we get some "message" that absolutely means nothing.
I suppose Acer is getting out of the Android business and no longer supports anything. Nice job Acer.
As for updating to ICS (or any other version), I have a few update files. Generally though, the update files must be matched to the current version of your tablet. Sometimes you can run a "full update" and it will work.
The problem, is these tablets are getting old, and the nand memory can go bad. Running an update can cause a variety of problems such as "Stuck in APX" mode, stuck at bootloader, stuck at boot animation. Then we have to go back to the EUUS file, or an old SD ROM file. So you run the risk of doing things all over again, and the risk that it just won't work again. (I spent a couple hours last night, and was almost ready to throw it in the garbage)
For example, I'm pretty much stuck at 3.0.x or 3.2.x. I've already disassembled the tablet and put the mainboard in the oven, just to get it back to life! And after numerous attempts to get ICS on it, I've pretty much given up before it hard bricks again. In fact, I can't get a 3.2.x EUUS to work on it, so it is stuck at the 3.0.x ATT EUUS. Eh, it's my little girls tab, so as long as it gets You Tube and browser, it's pretty much ok.
Trouble installing A501 ROM
Hi MD,
I am in the same boat as you...lol...This tablet is mostly used by my daughter and as long as it is solving my daughter's purpose, we are happy
I was just curious about that message as to why that is happenning, but after your clarification, it is clear to me as to why it is happenning.
My tablet is working as normal and everything is working fine...so we are happy with what we have.
Thanks a lot!
Regards,
Muk
---------- Post added at 03:04 AM ---------- Previous post was at 02:48 AM ----------
jonnybrave said:
Hello mukapril .. may you provide me with the Honeycomb ROM which I might try ?
Thanking you and Best Regards
Click to expand...
Click to collapse
Hi Jonny,
If you are referring to the ROM that I successfully installed which was sent by MD earlier, then it does not need any decryption. So you can use the link sent by MD earlier in this post. And if you are referring to the KernelSourceCode that I mentioned earleir, then it needs some kind of processing in Linux machine and then you can create some image.....this is was I know about it....sorry not an andrion guru. Please let me know what you are referring to.
Regards,
Muk
< include generic disclaimer here >
TL;DR
Since update 3.1, Nvidia can force updates (such as the one that bricks your tablet) to be downloaded and installed silently. No guarantees, but:
If you're on stock, delete TegraOTA (/system/app/TegraOTA or /system/priv-app/TegraOTA if you're on 5.0 or newer, or /system/app/TegraOTA.apk if you're still on 4.4) before booting into Android (the attached ZIP file does this for you, but please check with the file manager in recovery before rebooting and let me know if it didn't work), then reboot
Note: you also will need to delete TegraOTA again if you ever install an OTA from Nvidia or a recovery image
If you're not on stock, you're probably safe
EDIT: The urgent OTA is currently not getting sent out to any devices anymore, not even to those who have been getting it before.
EDIT 2: The urgent OTA is now being delivered again, this time named "ST - yy"!
What if my tablet is already deactivated?
Unless you can still boot into fastboot mode (in which case your tablet isn't really deactivated yet), your tablet is probably gone for good. The only way to fix this would be through nvflash, and using it requires the SBK that is unique to each device and that only Nvidia knows, so it's pretty unlikely that we'll ever be able to fix these deactivated tablets.
What/why/how?
In the last OTA (Update 3.1), Nvidia has made some changes to their TegraOTA application. The most important/interesting/suspicious of which is the ability for them to mark OTAs as "urgent". What this means is that these updates will be downloaded without ever notifying the user, and they will be installed without asking the user for permission first. If this is how the kill switch is delivered, all users will see is the tablet randomly rebooting and installing an update, then the tablet would never boot again. As some of you might notice, this would match what has been happening to a few users already, both here and on reddit.
But that's not all. I've been connecting to the OTA servers using various serial numbers (both found and provided to me by a few people) in hopes of actually finding the update that bricks the device. The first serial number I've tried that wasn't mine was the serial number from the screenshot on the recall page. It revealed an interesting "urgent" OTA, named "SHIELD Tablet xx - LTE", which does nothing but flash a blob (which, among other things, contains the bootloader). Many more questions appear now, but the main one is: if this is nothing but a routine bootloader update, why is it marked urgent? And why is it not attached to any Android update? But this by itself is not enough to prove anything, as I could only obtain it with one serial number, so as far as I could have known, it might had just been an internal update or something similar. (update is linked and analysed in the second post below)
Today, however, one of the serial numbers I've been given by some of the people here (thanks for the help guys!) turned out to have the same update waiting for it the next time it connected to the Internet. This rules out the possibility of an internal update, so the next somewhat obvious possibility is that this is the kill switch. Mind you, I still have no direct way of proving this without flashing the ZIP to see what happens (which I'm not planning to do myself), but I will keep checking on the other serial numbers I've gotten to see if this update turns up for them too.
The same person who has given me this serial number has also tested running the old tablet on the latest stock Android version but with TegraOTA removed, and, as expected, the tablet is still working perfectly fine now. Your mileage may vary.
How can I know if the kill switch has been triggered for my tablet?
Go to http://shield.bogdacutu.me/ and enter the full serial number of your old tablet. If the next OTA returned is "SHIELD Tablet xx" "ST - yy", the kill switch has been triggered for your tablet.
Warning: the serial number from the box of the tablet and the one etched on the side of the tablet are not complete, as they only contain the first 13 characters of the full (20 characters) serial number. You can get the full serial number from Android (Settings -> About -> Status), from the bootloader (it will be on the screen when you boot into bootloader mode), or from your computer if the tablet is or (in some cases) if it was previously connected, using various tools such as USBDeview. Example: 0413714803249000a4cf (you can try this on the page and it will return that the kill switch is activated).
Why would I want to also do the fix on my new tablet too?
The update is signed by Nvidia, and communication with the OTA server does not use HTTPS, so, for example, a malicious WiFi network could MITM your connection and cause this update (as well as any other signed update) to be flashed to your new tablet without your permission, thus permanently disabling it too. If you have the stock recovery, only updates signed by Nvidia can run. The story might be slightly different if your recovery doesn't enforce signature verification (such as TWRP and CWM by default).
Can I still get updates from Nvidia after doing this?
Not directly, but people will post OTA download links here on xda when new updates get released. I'd personally recommend that you wait before flashing though until someone here checks the new update to confirm that there's no new way for Nvidia to kill your tablet.
Many hours of work have gone into investigating this. Even if it doesn't help your specific scenario, consider hitting that Thanks button, so that I can at least know it wasn't for nothing.
I'd also like to thank the people who have given me their serial numbers to use for testing again, this wouldn't have been possible without their help: @Beauenheim, @Jackill, and @runandhide05 (who has even volunteered to test removing TegraOTA with the latest update on his old tablet :highfive
Fragments of code from TegraOTA.apk
< screenshots temporarily removed >
Also, from what I've seen so far, the update isn't delivered instantly after activating the new tablet. I don't know exactly what the rule is, but out of the 4 serial numbers that I have, only 2 have this update waiting for them.
EDIT: One more serial number from the ones I have has gotten the xx update. Only one left...
EDIT 2: All the serial numbers I have have the urgent OTA waiting for them now.
"SHIELD Tablet xx" - Update Analysis
OTA URL: http://ota.nvidia.com/ota/data/post...wf-full_ota-32256_554.0168.20150624152335.zip
yy OTA URL: http://ota.nvidia.com/ota/data/posted-roms/uploaded/st---yy--092704233775---7294.20150819152732.zip (if you don't know what you're doing, DO NOT DOWNLOAD THIS, it's very likely that this will permanently brick your device upon flashing it!!!) - also attached to this post in case this link becomes invalid
updater-script is the first file we check:
Code:
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");
nv_copy_blob_file("blob", "/staging");
reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "");
Suspiciously enough, this only flashes a blob to the staging partition. But what exactly does this blob do, you might ask? Well, the blob actually contains data for 9 partitions, which are automatically replaced during the next boot (before the bootloader does anything else at all, so once you've rebooted, there's no going back) with the contents present in this blob. The 9 partitions are as follows (also detailing comparison with files from update 3.1):
BCT (Boot Configuration Table) - stores some information that is needed for the device to find the bootloader stored on the other partitions, initialize the RAM and some other stuff
Status after update: probably corrupted - the previous OTAs have binary BCTs, but this update replaces it with a text file (which, while it does contain somewhat relevant information, is likely not a valid format). If this is corrupted, it's enough for the device not to be able to boot anymore.
BMP (boot logo) - intact
DTB - intact
EBT (part of the bootloader) - has a zeroed out region
NVC (part of the bootloader) - intact
RBL (part of the bootloader) - has a zeroed out region
RP4 (landscape boot logo) - intact
TOS (Trusted OS - probably part of the bootloader too) - has a zeroed out region
WB0 (related to the boot process, source file is named "nvbootwb0.bin") - has a zeroed out region
The update also contains a few other files, but those are not used at all (probably leftovers from the 5.1 AOSP update template that they are using).
DO NOT DOWNLOAD THE ATTACHMENT IF YOU DON'T KNOW WHAT YOU'RE DOING. THIS IS THE XX OTA, NOT THE ZIP THAT REMOVES TEGRAOTA!
Just as I suspected!!
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
CWM and TWRP are both compatible with OTAs, so yes, it can. If you completely erase the recovery (fastboot erase recovery), the update can't get flashed, but the tablet will still reboot (which is at least annoying).
You can flash the provided ZIP through CWM or TWRP (but please check through the file manager if /system/app/TegraOTA still exists after installing it, the ZIP hasn't gone through a lot of testing so it might not work properly in all cases)
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
bluegizmo83 said:
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
Click to expand...
Click to collapse
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Bogdacutu said:
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Click to expand...
Click to collapse
Oh ok! Great explaination. Thanks for all your hard work on this! I'm flashing the zip now, i'll report back if it removes the file
Edit: Ok I flashed the zip, and TegraOTA is gone. Now I will finally turn on my new tablet and set it up!
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Great post. Hopefully that's as far as Nvidia is going to go. I flashed a custom rom on my old tablet. I'm keeping my new one stock but deleting the system app per your post. Just in case Nvidia is spiteful when I don't return the old tablet. I don't want to leave them any option of nuking the new one.
fkofilee said:
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Click to expand...
Click to collapse
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Bogdacutu said:
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Click to expand...
Click to collapse
I know fella I appreciate it. Could you check my second point? 2 x Nvidia Shields would be awesome! One for Work, One For Home
fkofilee said:
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Click to expand...
Click to collapse
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Bogdacutu said:
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Click to expand...
Click to collapse
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
fkofilee said:
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
Click to expand...
Click to collapse
As mentioned in the OP, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Bogdacutu said:
As mentioned in the first post, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Click to expand...
Click to collapse
Sorry fella missed that part, I will be donating some funds when i get paid later this month Mucho Gracias!
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
bluegizmo83 said:
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
Click to expand...
Click to collapse
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Bogdacutu said:
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Click to expand...
Click to collapse
AWESOME man, thank you!!
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!