Related
Edit: Solution found look below!!!
As I posted in a different thread:
I managed to do it, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
EDIT: The kernel is stock for ACER_A500_1.016.05_COM_GEN1
Take a look at the thread linked below, get the 1.016.05_COM_GEN1 files (system, flexrom, and boot). If you are not offered an online update (System>About>Check for updates), you need the official update.zip from Acer. Extract the update.zip from the official Acer update THAT MATCHES YOUR FLEX VERSION using the XOR 12 method (see here - http://forum.xda-developers.com/showthread.php?t=1065360&page=20 - note in that post the link is for 03_COM_GEN1, NOT 05_COM_GEN1. For 04_COM_GEN1 and 05_COM_GEN1 see here - http://forum.xda-developers.com/showpost.php?p=14052165&postcount=184. For 03 and 04 you will need to find system.img, flexrom.img and boot.img, for 05 they are linked in the thread below).
EDIT: The thread with the images for ACER_A500_1.016.05_COM_GEN1 is here:
http://forum.xda-developers.com/showthread.php?t=1086785
EDIT: You might pull this off for other flex versions as well, but you would need all the files (system.img, flexrom.img, boot.img AND update.zip) from those versions.
PLEASE NOTE THAT THIS ONLY WORKS IF YOU HAVE THE OFFICIAL UPDATE.ZIP FOR YOUR SPECIFIC FLEX VERSION
Wow, I was about to try that!!!
I'll do that now and see how it goes.
Thanks mate!
EDIT: Worked!
I would expect that the reason an update fails on the Chinese one is that it tries to patch the kernel (which is different from the one expected). The update is a bunch of diffs and patches, and almost no full files, so it cannot be applied over anything but the right files.
Yes that is true. The old kermel checksum check was failing.
huxflux2003 said:
EDIT: Worked!
Click to expand...
Click to collapse
Glad to hear it Take that, you sneaky Acer bastards!
adancau said:
As I posted in a different thread:
I managed to do it though, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
Take a look at the thread, get the 1.016 files, system, flexrom, and boot, and try it.
Click to expand...
Click to collapse
Ahhhh a true milestone, well done.........
Nice work! Two questions:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Thx
gingerbreak works
_motley said:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Click to expand...
Click to collapse
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
adancau said:
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Click to expand...
Click to collapse
Thanks guys, I did restore using the Chinese update.zip last week and I am currently sitting at kernel 2.6.36.3 with flashed system img=Acer_A500_1.104.05_COM_GEN1, but with recovered Chinese kernel modules for wifi etc. I also flashed a flexrom.img from this build as well. I didn't flash the boot.img from this build, but was thinking about it until huxflux2003 reported the check-sum failure.
So, I am trying to decide what I am going to do. It sounds easy enough to get back to stock now, but I may wait for the official update next month that has 3.1. At this point, I suppose we are assuming that it will be a full update.zip that will work on any tablet (god I hope so). It's about time they gave us a full recovery image...I will be beyond disappointed if they don't. Let's also just hope we can still gain root easily after this.
One more question, if I use all the images from ACER_A500_1.016.05_COM_GEN1 that were posted, does this have to match what I had originally had in any shape or form? It sounds like since all the pieces are from the same build, everything will be fine regardless of what you had to begin with. Is this right?
Thx
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
heyoh said:
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
Click to expand...
Click to collapse
To get back to stock you need the three images for your build - system, flexrom, and boot. If there is no online update available, you also need the update.zip for that build (extracted from an official acer update using the XOR 12 method - do a search).
Alternatively, I suppose you could switch to a new build for which you could find all the necessary files (but it hasn't been tried).
Flash system.img using dd. You might need to re-root. Reboot, flash flexrom.img. Reboot once more. Make sure your wifi works (you might need different kernel modules).
Look to see if there is an online update (Settings > About > Check for updates). If there is, cancel it. Flash boot.img on mmcblk0p2. DO NOT REBOOT.
If there was an online update available, now it's the time to perform it. After it's done you will get you back to stock 1.139.05.
If there isn't any update, make sure you have the update.zip on the root of your microSD. Turn off the tablet, then turn it back on holding the volume key closest to the power button. Do not let go of that button until you see some text in the corner. At that moment the update would begin. Once rebooted you will be back to stock.
Hope I've explained it better this time, and it works ok for you. If not, you need to go through the chinese update again. Good luck.
adancau said:
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
Click to expand...
Click to collapse
It worked for me too! Thanks again for the tip. I am now at the latest build and ahead of the US update schedule from what I can gather
It asked me to update after I flashed the ACER_A500_1.016.05_COM_GEN1 build system.img and flexrom.img. Even from the US it prompted just fine since I was on ACER_A500_1.016.05_COM_GEN1 build and not ACER_A500_1.104.05_COM_GEN1 as the former is what the differential patch targets.
I cancelled the update once I saw it presented and then blew on the boot.img from the ACER_A500_1.016.05_COM_GEN1 build. Then, without rebooting, I downloaded and applied the update (but with a little hiccup, see below). Now I am at Acer_A500_1.139.05_COM_GEN1 and didn't lose any user apps or settings etc.
Had a scary point though that I will share as it may help others. The first time I tried, the zip wouldn't downloadload and I was getting an HTTP 403 error. I cleared the systemupdater app and FWUpdateService data. I also killed the services and then I was stuck. Instead of conceding to reflashing the Chinese update.zip and starting over, I unzipped the Chinese update.zip and grabbed the boot.img from it. I then dd'ed that image back to the boot partition and rebooted again. It came back up and I this time I was able to do the system update successfully. Whew!
Followed instructions by OP and it worked perfectly! Back to stock and updated.
I think I'll be keeping these system images for next time I brick and have to flash the Chinese update.
Any chance of someone uploading the extracted update.zip for the new Acer_A500_1.139.05_COM_GEN1 so I can update manually using this method.
Thanks in advance
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
tianqi said:
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
Click to expand...
Click to collapse
If you directly flashed a 1.139.04 image your kernel has not been updated. You had to flash a 1.016.04 image, flexrom and boot, and then run the update.
You MIGHT have some luck regardless by running the update.zip now (I used it on mine one time when I updated like you did, and it seemed to work, but I have not noticed the kernel number). Be prepared to have to reflash if something goes wrong though.
I did reflash system, flexrom, and boot from 1.016.04...
Second time is still the same...
Kernel is still 2.6.36.3-00001-gf991e5d...
Hi all.
I did the manual update from 3.1 to 3.2 using the method based on the wifi files in the developer forum. I then proceeded to update to the latest Hammerhead ROM. Somewhere in there, I experienced an issue which causes wifi drop out which is driving me crazy. Of course before I did all this, I made a backup to my external SD Card - but also somewhere during this process my SD card became borked and unreadable - destroying my backup file(s) before I had a chance to upload them to a dropbox server or a desktop PC.
So - my question is this. On a 3.2 3G US Xoom - are there any files that are out there that would let me roll back to 3.1 and try all this again? Heck, I wouldn't even mind staying on 3.1 if there is a flaw in the 3.2 HC code that is causing the wifi dropouts. I've tried searching the forums and haven't found anything that deals with 3.2 or rolling back to a 3.1 state. Of course I am rooted, bootloader unlocked, etc. and can follow instructions pretty easily. If anyone has any tips or links - it would be greatly appreciated.
discstu37 said:
Hi all.
I did the manual update from 3.1 to 3.2 using the method based on the wifi files in the developer forum. I then proceeded to update to the latest Hammerhead ROM. Somewhere in there, I experienced an issue which causes wifi drop out which is driving me crazy. Of course before I did all this, I made a backup to my external SD Card - but also somewhere during this process my SD card became borked and unreadable - destroying my backup file(s) before I had a chance to upload them to a dropbox server or a desktop PC.
So - my question is this. On a 3.2 3G US Xoom - are there any files that are out there that would let me roll back to 3.1 and try all this again? Heck, I wouldn't even mind staying on 3.1 if there is a flaw in the 3.2 HC code that is causing the wifi dropouts. I've tried searching the forums and haven't found anything that deals with 3.2 or rolling back to a 3.1 state. Of course I am rooted, bootloader unlocked, etc. and can follow instructions pretty easily. If anyone has any tips or links - it would be greatly appreciated.
Click to expand...
Click to collapse
There may be another way to do this, but you may want to revert back to stock by flashing the proper stock images for your model from this thread: http://forum.xda-developers.com/showthread.php?t=1049485 . I believe it will unroot you and then you can get the OTA update(s) as you choose. You should not try to relock. That shouldn't affect your ability to get the updates. You could reroot at any point after that, of course.
I hope you are able to solve your wifi problem.
okantomi said:
There may be another way to do this, but you may want to revert back to stock by flashing the proper stock images for your model from this thread: http://forum.xda-developers.com/showthread.php?t=1049485 . I believe it will unroot you and then you can get the OTA update(s) as you choose. You should not try to relock. That shouldn't affect your ability to get the updates. You could reroot at any point after that, of course.
I hope you are able to solve your wifi problem.
Click to expand...
Click to collapse
Thanks for this thread - I was unable to find this, so I appreciate it. A follow up question (which you seem to infer is possible but just want to make sure): will flashing back to an earlier image potentially brick my device in any way since I'd be come from 3.2? Also - I am using the Tiamat OC kernal meant for 3.2, does reflashing the image ALSO reset the kernal or should I find a 'stock' kernal, load that first and THEN flash?
TIA!!!
discstu37 said:
Thanks for this thread - I was unable to find this, so I appreciate it. A follow up question (which you seem to infer is possible but just want to make sure): will flashing back to an earlier image potentially brick my device in any way since I'd be come from 3.2? Also - I am using the Tiamat OC kernal meant for 3.2, does reflashing the image ALSO reset the kernal or should I find a 'stock' kernal, load that first and THEN flash?
TIA!!!
Click to expand...
Click to collapse
If I not mistaken, reflashing the stock Rom will also reset the kernel.
As long as you choose the right stock image for your device you should not have to worry about bricking anything. To investigate where the wifi problem arose, you could just try going back to square one and taking incremental steps along the way. I think that you should flash the v3.2.0.0 R4c recovery image as soon as you can in your process so you can do incremental backups. And get a good sdcard and test it out if you can.
Good luck!
Thanks again. Yeah, I plan on doing the incremental upgrades but it definitely happened between 3.1 and 3.2 or 3.2 and loading the Hammerhead ROM (I've heard others say they've seen this issue on 3.2 stock and others are OK; others report issues with just the ROM itself so I don't know). As long as I have a working point between going back and forth in between 3.2 and 3.1 I can play with it from there since I know it worked there for sure.
I plan on flashing 3.1, rooting, getting CWR up and running and going from there.
I fixed the SD Card by reformatting it in my digicam (windows couldnt even recognize it) and all seems well with it now.
So first of all my tablet is brand new and not rooted and I don't want to root it.
When I got it I could update it instantly from 3.0.whateverwastheversionatthetime to android 3.2 (build 7.006.01_COM_GEN1) but it won't go from there to 3.2.1 which I hear is available for my location (France) The update tool tells me that my firmware is up to date.
I've tried a factory reset as advised by Acer customer care services but it wouldn't change. Also no matter what I do (empty cache etc.) the market won't update to Google Play Store and I think the two issues are related.
So I have two (or rather 3) questions:
1) Does anyone know a way around to force the update? (I doubt it's possible but hey "l'espoir fait vivre")
2) If not can I install a stock ROM without root and NOT compromise the warranty?
3) Where can I get such a ROM? I have searched here and here but 3.2.1 is not on the first thread and the links on the second thread are broken, plus I want to make sure that the ROM is the proper one for my region and that comes the ICS OTA update I will have no troubles doing the update.
Thanks in advance to those who will answer.
lunaticwraith said:
So I have two (or rather 3) questions:
1) Does anyone know a way around to force the update? (I doubt it's possible but hey "l'espoir fait vivre")
2) If not can I install a stock ROM without root and NOT compromise the warranty?
3) Where can I get such a ROM? I have searched here and here but 3.2.1 is not on the first thread and the links on the second thread are broken, plus I want to make sure that the ROM is the proper one for my region and that comes the ICS OTA update I will have no troubles doing the update.
Thanks in advance to those who will answer.
Click to expand...
Click to collapse
1) No you cannot force an OTA
2) It depends - others have reported returning there acer with no probs -, i think someone has even returned it rooted and been ok. These things are fairly bulletproof, and really hard to 'brick'. As long as you can read, follow a few steps you shouldnt have any probs. The worse thing you can do is try 2 or 3 different methods all at once because something isnt working right. You're best to pick one and stick with it, if you have probs ask for help in the thread you got the rom from or start your own like you have here
3) The update.zip method from the first link you posted "should" work. Did you "decrypt" the file you downloaded before extracting the update.zip??
You could try timmyDeans v4 method- it will install a stock 3.2.1, it is rooted but you can remove root using the tools he provides. Beware though this will wipe all data so backup anything essential.
The update.zip method will leave your data and settings intact
As always the choice is yours, there are some really excellent custom roms out there - I enjoy the best of both worlds with a backup of my trusty stock 3.2.1, I flash to my hearts content knowing I can always go back to it when the OTA update is out!!! Oh the joys of root priveleges
Thanks for your input, I'll make sure to try all this when I get back from work. I've a few additional questions:
1) If I install a custom rom, will the OTA work from this ROM or, comes the OTA, will I have to restore my actual Stock rom and then proceed with the OTA?
2) I haven't tried the rom on the first link I gave because it is modified and I was searching for the original, pristine, untouched stock ROM for 3.2.1
I've seen such roms around here on xda for 3.2 but none for 3.2.1, if anyone stumbles upon one please let me know.
3) Since I'm still looking for a pristine ROM before trying anything else, I have a friend whose tablet (same brand and model) safely updated to 3.2.1, is there a way to make a rom from is gear? If yes, how to?
4) (related to 3) how can I backup my actual ROM, do I have to be a root user to do so?
THX again!
lunaticwraith said:
Thanks for your input, I'll make sure to try all this when I get back from work. I've a few additional questions:
1) If I install a custom rom, will the OTA work from this ROM or, comes the OTA, will I have to restore my actual Stock rom and then proceed with the OTA?
2) I haven't tried the rom on the first link I gave because it is modified and I was searching for the original, pristine, untouched stock ROM for 3.2.1
I've seen such roms around here on xda for 3.2 but none for 3.2.1, if anyone stumbles upon one please let me know.
3) Since I'm still looking for a pristine ROM before trying anything else, I have a friend whose tablet (same brand and model) safely updated to 3.2.1, is there a way to make a rom from is gear? If yes, how to?
4) (related to 3) how can I backup my actual ROM, do I have to be a root user to do so?
THX again!
Click to expand...
Click to collapse
1. Typically, most people do not take OTA's when running a custom rom, as basically the OTA installs a totally fresh factory Rom. This is true with the 3.2.1 update, which contains a new bootloader. Usually, this means you lose root, and Recovery, then stuck with downgrading to get these things back.
Timmy Deans root tool supposedly maintains a back door method, which s supposed to protect root, in case of an OTA. No, I haven't used this method, as I run my own 501 roms.
2. Vache has a thread "full package and updates" in the 500 Dev forum. There are several factory Roms and Updates. You'll have to look. Chances are, he may not have the specific Com Gen version you want, but probably one close enough.
3. If your friend can get adb running, you can pull a "system dump", which will dump all files/folders in the system folder. The boot.img would be nice to get, but you can probably use the current one you have. Unfortunately, he already rebooted, so you probably can't get the original full update file. If he's rooted, you can use an app called Rom Factory, to get most of what you need. It's always a good time to become familiar with ADB.
4. Well, you can back it up internally, but it's sort of useless if you can't get into your OS You will need to Root, and install a custom recovery to keep your backup externally.
Moscow Desire said:
2. Vache has a thread "full package and updates" in the 500 Dev forum. There are several factory Roms and Updates. You'll have to look. Chances are, he may not have the specific Com Gen version you want, but probably one close enough.
Click to expand...
Click to collapse
ok, as Moscow has pointed out, in vaches thread not all roms are listed. My stock roms (1.016.01 and 1.139.04) for instance weren't - so I spent the last hour or two trying the "EUU gen1" listed at the bottom of the page. Well, it actually worked!! It gave me an OTA to 1.139.04 straight away. After that installed i got the 4.010.40 to 3.2 and then the next 2 for 3.2.1 - 7.006.03 and 7.014.15. So its given me the correct updates for my country AND kept my data and settings too.
SO, since you're on a Gen1 Rom this should work for you too, but still no gaurantee you will get the OTA to 3.2.1, no harm in trying though
btw timmydeans method is a gen2 rom so you can rule that out...
---------- Post added at 11:25 PM ---------- Previous post was at 11:16 PM ----------
just came across this link for an update to stock 3.2.1 build 7.014.14 here - orignal thread here but you need cwm to install it....
unless you can make it into an update.zip???
but thats way outta my league,
moscow may be able to suggest something though
Thank you very much, your answers help a lot! Just a few precisions and I'll stop being a pain in the ass!
1. Typically, most people do not take OTA's when running a custom rom, as basically the OTA installs a totally fresh factory Rom. This is true with the 3.2.1 update, which contains a new bootloader. Usually, this means you lose root, and Recovery, then stuck with downgrading to get these things back.
Click to expand...
Click to collapse
==> @ Moscow, when you say "lose recovery" does it mean I lose the green thingy with gears when I start with volume down and power pressed/ and when I reset to factory settings?
==> @dibb_nz your method is the closest to what I'm looking for, I also hope it will give me the correct updates for my country and since Vache is a fellow countryman it might just be ok.
Anyways thanks again, I'll give a thorough look to all of your solutions and try and do a few things tomorrow afternoon. I'll keep you posted in case this thread interests anyone else.
lunaticwraith said:
==> @ Moscow, when you say "lose recovery" does it mean I lose the green thingy with gears when I start with volume down and power pressed/ and when I reset to factory settings?
Click to expand...
Click to collapse
No, what I meant to say, is when you run a rooted "custom" Rom, and use a "custom" recovery such as RA Recovery or CWM, getting an OTA update, usually wipes that out, and installs the factory bootloader. Your factory recovery....cough cough.... will still be there.
If you are only concerned about stock factory, then don't worry about it. You;re ok. Your factory/stock recovery will be just fine
The reason we root and install custom recoveries, is so we can do 3 primary things.
1. Flash a custom rom
2. Create a complete system backup to our external SD card.
3. Get rid of pre-installed useless apps.
There are other things we can do with it, but these are the primary reasons.
When you have a default factory stock system, the only protection you have, is a factory reset (hope it works), and a couple other methods which require a touch more knowledge.
Anyhow, don't worry about your factory recovery. It's just fine.
1) Just for the sake of knowledge what's the difference between GEN_1 and GEN_2? (and GEN3 and CUS7 and EMEA_TMLP)?
2) @Dibb_nz when you tried with the stock rom from Vache, was it because you encountered the same no FOTA update problem as I did? Or just to try...?
3) Something's still unclear to me after browsing through the forums: If I get an unmodified stock ROM can I flash it with the stock recovery? (so without rooting) Or do I need CWM (so root is needed)
4) What's EUU? (on Vache's thread some roms are listed as EUU)
lunaticwraith said:
1) Just for the sake of knowledge what's the difference between GEN_1 and GEN_2? (and GEN3 and CUS7 and EMEA_TMLP)?
2) @Dibb_nz when you tried with the stock rom from Vache, was it because you encountered the same no FOTA update problem as I did? Or just to try...?
3) Something's still unclear to me after browsing through the forums: If I get an unmodified stock ROM can I flash it with the stock recovery? (so without rooting) Or do I need CWM (so root is needed)
4) What's EUU? (on Vache's thread some roms are listed as EUU)
Click to expand...
Click to collapse
1. The Gen's usually signify regional based roms. More specifically language support, sometimes a wifi tweak, and maybe a couple other things. Mostly though, ComGen1's are for the US and probably canada, and offer about 12 different languages. TMPL is for East Europe mostly, with polish as the default language. All roms contain the english language as far as I know.
3. You basically can't install a full rom on an unrooted tablet without CWM or RA Recovery. You will have to run the update (decrypt the file, remove the update.zip)
4. EUU is a pc based install. Plug in the USB, set your tab to APX mode and run the EUU.
If you did the root, and install a custom recovery, then you could run just about all the full roms. Your custom recovery would be overwritten, and you would lose root access. You would have a stock tablet with the version rom you selected.
You can always wait a week or so. Am sure if the update has been pushed to your country, it's just a matter of time till you get it. It's common for the update process for specific roms, to get fully done in 2-3 weeks. It took well over a week just for users in california to mostly start getting updates.
Well the official release date for the ICS FOTA in France is May 3rd, so I'll wait until then but having other options and the know-how to take actions is always a good basis. (plus I'm really not the patient type ^^)
Stupid question but I'm guessing EUU needs root too?
and also APX means rebooting while holding power and volume - right?
lunaticwraith said:
Well the official release date for the ICS FOTA in France is May 3rd, so I'll wait until then but having other options and the know-how to take actions is always a good basis. (plus I'm really not the patient type ^^)
Stupid question but I'm guessing EUU needs root too?
and also APX means rebooting while holding power and volume - right?
Click to expand...
Click to collapse
I tried the EUU just to see if it would keep me on my regions OTA upgrade path.
Sometimes you can have probs OTA'ing if you aren't using the rom from your region.
But in this case it gave me the correct OTA's.
APX is Acer Download mode, where the OTA upgrades are flashed - this EUU will do it via your PC. Button push method (power/reset button) not required.
No, the EUU does not need root which is why I tried it out for you
You will need to be on 3.2.1 before you will receive the ICS update
I used this EUU from vaches thread -
EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
late for work will check back later
That's really helpful thanks I'm downloading the same EUU you used and will try it today or tomorrow depending on how much time I have, will keep you posted!
Ok so I did the EUU install and it worked fine, the tablet then allowed me to upgrade to 3.01 and then 3.1 then 3.2 via FOTA without any problem. But once I reached 3.2, the update tool informs me that there's no update available and my gear is up to date
So my guess is Acer France are not pushing the 3.2.1 FOTA update anymore...
Any other explanation?
lunaticwraith said:
Ok so I did the EUU install and it worked fine, the tablet then allowed me to upgrade to 3.01 and then 3.1 then 3.2 via FOTA without any problem. But once I reached 3.2, the update tool informs me that there's no update available and my gear is up to date
So my guess is Acer France are not pushing the 3.2.1 FOTA update anymore...
Any other explanation?
Click to expand...
Click to collapse
Glad to hear u got thru the EUU process OK, not so great u still can't ota to 3.2.1
Others have reported similar issues not sure if/how they were ever resolved. As moscow posted earlier,ota,s are not made available to all users in all regions, all at once, so it may be just a matter of waiting for the next "push cycle" to roll round.
At least you know you can always get back to stock if you ever decide to root and go custom There no direct root method for 3.2, just use that same euu to get back to 3.1 and use iconia root and Acer recovery installer from the market and you're ready to flash your rom of choice
Pls post back if u do get the ota - best of luck
rgds Donna
Yeah I was just browsing the XDA forums, contemplating the idea to rollback and root and then installing this
I wonder if it's worth waiting for the OTA... as for what you said about waiting for the next "push cycle" I've been waiting since I got the tablet and the update hasn't come yet, which is strange because the ICS update is due on May 3rd in France and I'd guess they'd have everyone up to date and ready for the update by now!
Rooting seems pretty straightforward and much easier than what it was on my Samsung Galaxy Spica: I found this
, a file called iconiaroot.apk on the sdcard aswell, rebooting your tablet while pushing the volume down button so its starts flashing the buggy honeycomb version.
Then start up the tablet again, rush to the market, download some file manager, with that filemanager explore your sdcard, and install the iconiaroot.apk file, once thats done, rush back to the market and download and install acer recovery installer. At that point you will have CWM (clockworkmod) installed.
Click to expand...
Click to collapse
is that all there is to it?
In any case I'll keep you posted just so it can help anyone with the same issue!
alsoe FYI and just for the anecdote: the reason I'm so cautious about everything and scared ****less of rooting is that the tablet is a present from my girlfriend for my 30th birthday, and she'll hang me with my guts if I brick it.
Ok I rooted and flashed the above-mentioned rom and it works! I'm now under 3.2.1!
Thanks to everyone who helped me! When the ICS update comes I will post here to signal how the FOTA went.
Thanks again!
Lol, good onya for taking the plunge! Yeh acer recovery installer is brilliant, along with iconia root, makes the whole process stress free.
Will be interesting to see if you get a notification for ICS OTA with that rom.
Can always flash one of the leaks if u get impatient??
Glad everything's worked out and yr g/f still talking 2 u
rgds Donna
thx! I will post here when/if I get the OTA. and my love life is safe thanksnto iconia root
okay so the ota has been rolling for over a week and a half now and still nothing for me
Hi All,
I'm in a bit of a unique pickle. I have a Lenovo ThinkPad Tablet 1838-CTO, it is a US 32GB wifi-only tablet with all stock hardware (with disconnected keyboard folio).
I am running build number ThinkPadTablet_A310_02_0037_0075_US
It is not liking to play more than 5 minutes of a video before saying video cannot be played, video it played fine before. Tried all the standard steps, recopying, rebooting, etc etc. The device also sporadically reboots 20-30 minutes into use, sometimes. I have root, rootprotector, and I have CWR. I have not used my tablet since about a week after the first update from my current version above: my device went loopy, THEN the update failed, and I stuck it in a closet, $%^@%$*&@ed off at it for not working.
I want to either (depending on difficulty, and recommendations here) update my device to the latest Lenovo ICS *OR* Run a custom JB ROM (perhaps http://forum.xda-developers.com/showthread.php?t=1778375 though it is for ROW not US, unsure if that matters). Priority on maintaining root access, could care less about what recovery is used, etc.
OTA updates are failing since I had to get CWR , and I am not sure how to use CWR to manually patch/update.
As for the glitching and all that, I am fairly certain it has something to do with when I rooted it, I was a very early adopter of the first permaroot (I place no blame except myself for any and all issues, and muchly appreciate the efforts of others in allowing me to root my device, whether it bricks it or makes it 10x better). I just want to update my device to ICS and start using it again. I have done some searching but am finding that almost everyone is using 0089 or later with the same issue I have, trying to get back to stock bootloader. Honestly I would like to get it on Lenovo ICS, maintain root, and go from there.
I appreciate any and all advice, it's a personal device so I am fairly lenient on what I am willing to try.
Update: I would most appreciate a stock Lenovo ICS dump flashable from CWR if someone knows where to get one, again though any help at all is appreciated.
Update 2: CWM 5.5.0.4 unable to mount the SD card (/sdcard - not even sure if it is trying to mount internal or external, I have ALWAYS had nothing but issues with the external ALWAYS being write-protected no matter the position of the physical slider switch, though it always reads fine - Sandisk 32GB micro-SDHC with Sandisk MicroSD to SD adaptor), so flashing anything from CWM is a no-go. I want to take this thing and send it on a flying ride out the window, the only thing stopping me is it would probably survive just fine to spite and mock me. Sorry about being long winded, rather give you guys as much as possible info.
Is rooting the tablet all you've done? Did you remove any stock apps? I had the same problem with my TPT when I tried upgrading to ICS(from build 0089_US on wifi only 16GB)but only because I had a corrupt busybox file or something. Try going back to complete stock(NO recovery no root) and try to do an automatic OTA 2, then OTA 3. It should work.
How do I go back to stock recovery/bootloader? I rooted back when you had to swap in ClockworkMod Recovery, so my updates fail consistently when I have to reboot to apply, my guess is that the updater tries to pass calls to the lenovo bootloader that do not exist with CWR.
If there is a way to restore my bootloader then I should be all set, otherwise I think I need to find a good cooked rom
Get Some ICS
Sublime865 said:
...otherwise I think I need to find a good cooked rom
Click to expand...
Click to collapse
I posted an ICS Nandroid from a US 32GB TPT, exactly what you are looking for, here:
http://forum.xda-developers.com/showpost.php?p=28240019&postcount=14
It will return you to stock Restore, losing CWM, but you can reinstall a proper CWM for ICS afterwards. See the Development Forum for the updated CWM version that works in ICS/OTA3.
You will have root, but you must download and use OTA Rootkeeper to bring Superuser back (don't forget to download and open SuperUser from Play store).
Good luck!
pwstein said:
I posted an ICS Nandroid from a US 32GB TPT, exactly what you are looking for, here:
http://forum.xda-developers.com/showpost.php?p=28240019&postcount=14
It will return you to stock Restore, losing CWM, but you can reinstall a proper CWM for ICS afterwards. See the Development Forum for the updated CWM version that works in ICS/OTA3.
You will have root, but you must download and use OTA Rootkeeper to bring Superuser back (don't forget to download and open SuperUser from Play store).
Good luck!
Click to expand...
Click to collapse
Going to try it tonight/tomorrow. Updating my Vivid to a non-corrupt CWR then flashing HolICS 1.3 from 0.9b tonight. Oh the adventures I get myself into... XD
Thanks for the upload, I'll let you know if(when) it works, either way I appreciate the effort!
***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!
404 page not found on the first link?
ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies
thank you a lot! you saved me a lot of browsing! :good:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..
seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted
Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo
Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree
unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead