I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Same question here
Sent from my A500 using XDA
3d0rr said:
Same question here
Sent from my A500 using XDA
Click to expand...
Click to collapse
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
tu3218 said:
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
Click to expand...
Click to collapse
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
Yeah I think so as well. I flashed stock via the Acer recovery tool but I get nothing when I boot into recovery except what I stated above. I'm not sure if that's right or not.
Sent from my Galaxy Nexus using XDA
I was happily running timmydean's rooted 3.2.1 based on the leaked OTA. The ICS upgrade came through and installed just fine. No loss of data and the programs I tried all worked. I was on stock 4.0.4 unrooted.
However, I'm now borked. I rebooted into recovery (Power, Vol -) to see about rooting via the backdoor I'd installed. I had thor's 1.7 Touch CWM recovery installed. I got some weird message that recovery was broken. (Don't recall the exact msg.)
After that, it hung on the "android" screen. Soft-bricked.
So I did a factory reset (Power, vol+, rock screen switch) and ended up back on 3.2.1. Now, the Settings > About > Check update results in the "Network coverage is currently poor. Please move to a location with better coverage to continue." message.
My WiFi is fine, speedtest.net reports a 20 Mbps download. All other apps function well. I'm pulling a DCHP address from my router.
I'm fairly sure this is a badly-worded error message from Acer and actually refers to server overload or some other issue on their end.
Also, installing the latest Acer Iconia Update preps the system for ICS. At one point, installing it allowed the update to proceed, but not to ICS. Uninstalling/reinstalling that update seemed to jog the system at one time.
So I tried wiping data/cache/dalvik and went back to stock 3.2. Same error message when updating. Wiped again and went back to stock 3.0.1. Same error message.
So I'm stuck and am going to give it a few days to see if Acer can sort out their upgrade path. If not, I will probably load CM9 or Thor's ICS ROM. (I do have a Nandroid, so I can get back to where I was pre-ICS.)
All in all, I'm very disappointed in Acer for borking my tablet.
________
Update: So now a day later, the "poor coverage" message was replaced by an "update available". Installed A500_7.014.03_com_gen1, after reboot, another update A500_7.014.15_com_gen1 installed. I am now on stock 3.2.1.
System update shows "Your device is up to date".
Will see what tomorrow brings, but this is certainly frustrating.
thorne75 said:
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
********************************************
Could you guys running the backdoor and still rooted please try this:
1) Try and capture the build no. of the update
2) See if the update will download BUT do not install yet
3) Go to /cache/fota/ and find the zip -
4) copy it to yr external sd
5) post back the build no.
thanks!!!
Procedure for manual install:
1/ rename the file as : update.zip
2/ place the file on the micro sd card
3/ turn off the tablet
4/ press the down volume key and the power button at the same time untill the tablets turns on
5/ the iconia will start the upgrade process by itself.
OR just redownload the update and it install
*********************************************
I had trouble when i reverted to stock in the weekend
and it was a bit of a process to get the OTA's to 3.2.1.
I did manage to hold "full root" but had to revert a couple of times
by putting stock recovery back and using backdoor .
I accidentally factory reset and everything went a bit pear shaped from there...oops!!
Im still waiting for the OTA ICS - getting network coverage error -one good thing
is my partners tab is only 5 days old and still pure factory,
her tab shows same error so at least we know its not root/backdoor problem
So yeah if u gonna take the OTA best to get rid of the backdoor unless you wanna play guinea pig for us all>>>>
dunno why we aint found one of those yet
I dont think you can cause too much of a problem where a "hard reset" pwr/vol -/rotation lock/ combo wont fix...you can then root from there.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
dibb_nz said:
********************************************
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
Click to expand...
Click to collapse
Dibb_nz, I was stock gen 2. I don't wanna take OTA until be sure it's safe. Unless now I know that a hard factory reset may save my tab if something happen.
Can you tell us where did you read that post about 'gens'? I still a little confuse about that
Sent from my A500 using XDA
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
3d0rr said:
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
Click to expand...
Click to collapse
oh sounds promising, although I just read another post from someone across the ditch in OZ he reckoned acer said they were working on a patch for the problems theyre havin with the first update...who knows
now m8, sorry to confuse you, that wasnt my intention, but i try to make sure that i;m not suggesting things which may end with you or others borkin or brickin yr tab. Ive spent the last few days reading thousands of posts (just like everyone else) thankfully we are fortunate in being able to learn from the mistakes of others I know a bit more about ics than i did 3 days ago let me tell you, lol.
i just finished helpin out a fellow "timmy-ite" stuck with no way of getting in to apx mode to get un-borked...well didnt really help just a sounding board more than anything
he got himself up and running, used the apx tool in my sig, unlocked the bootloader, rooted, flashed custom recovery did a nand and is now running flexreaper - with the tools and knowledge he gained he now has the choice to go back to HC to get the OTA or not....he's one happy camper!!!
Have a read have a read thru the threadhere. ask him a question or two if you want - but dont get too hung up "maybe doing something wrong" you won't be the only person ever to experience that uhh-ohh sinking feeling when you know you shouldnt have just done whatever it was that u just did
Theres always someone round here who will help - usually cos they done the same silly lthings themselves - why ya think i'm always posting
what is the backdoor program you guys talk about?
tu3218 said:
what is the backdoor program you guys talk about?
Click to expand...
Click to collapse
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
jpinsl said:
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
Click to expand...
Click to collapse
timmyDean How to root stock 3.2.1
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Click to expand...
Click to collapse
beat me to it
its a completely stock gen2 rooted and cwm - you can use to unbrick, or go back to stock. only for HC bootloaders though.....
This worked to me
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method.
1) Go to play market and install Acer Recovery Installer.
2) Open Acer Recovery and verify with recovery do you have. In my case it was CWM recovery by thor2002ro 1.5
3) Install stock recovery. Make a backup of your old recovery when ask.
4) Factory reset: in my case, I made a backup of all my data and used Titanium to backup some apps. Then I harded reset my tab by turning it off and the combo pwd + vol(+) then lock-unlock switch 3 times until I saw "eraing user data" in the top-left corner.
5) turn on the tab and go to google play. Search for acer and install Update enhancement.
6) Go to settings-> about-> system update and aply the OTA update.
You will lost root, but everything should work fine.
To gain root access again, you can follow this thread -> http://forum.xda-developers.com/showthread.php?t=1546593
Now I have rooted stock ICS and I'm so happy
Hey great write up, will try this as soon as I'm off work. Anyway to confirm stock recovery is installed? Because I have done what you said(just the flash stock recovery part) an when I boot into recovery I just get a triangle an exclamation point. Not sure if thats right or not. But I will definitely give this a go since you were running exactly what I'm running now.
Sent from my Galaxy Nexus using XDA
3d0rr said:
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method...
...To gain root access again, you can follow this thread - ...xda-developers.com/showthread...
Now I have rooted stock ICS and I'm so happy
Click to expand...
Click to collapse
yay for 3d0rr you finally took the plunge congrats!!!!!
@tu3218
That download link is no longer available
instead download blackthund3r's one-click-root,
google "ICS Root for Windows"
At step 3 - After you have backed up -
Copy the uid.txt file from the backup folder - this holds your cpu id -
you're probably gonna need it at sum stage
I followed your instructions and it went perfect!!! Rocking ics now. Thanks for the help. First thing I notice, soooo much faster an full of butter.
Sent from my Galaxy Nexus using XDA
Related
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
hi guys,
i want to root and flash custom rom on my acer iconia with 3.2 OTA.
Correct me if i'm wrong...
i understand that i have to:
1. revert to 3.0.1 via http://forum.xda-developers.com/showthread.php?t=1276227
2. root my iconia via http://forum.xda-developers.com/showthread.php?t=1055354
then i don't know whats next? can i already install custom rom after root?
or do i need to install some kind of recovery to flash this custom roms..
Please help.. thanks!
exactly my friend revert first then root, then download acer recovery app install recovery start flashin
jhannbernas said:
hi guys,
i want to root and flash custom rom on my acer iconia with 3.2 OTA.
Correct me if i'm wrong...
i understand that i have to:
1. revert to 3.0.1 via http://forum.xda-developers.com/showthread.php?t=1276227
2. root my iconia via http://forum.xda-developers.com/showthread.php?t=1055354
then i don't know whats next? can i already install custom rom after root?
or do i need to install some kind of recovery to flash this custom roms..
Please help.. thanks!
Click to expand...
Click to collapse
Once you root install this:
Acer Recovery Installer
That will install CWM (recovery).
thanks for you both. i will try all of this on weekend.
but before doing this.. how can i backup my current rom? it is possible? thanks
You should install the Acer recovery installer first, then boot into CWM. When you are in there you will have the option to perform a full backup. This backup function will become your best friend.
thanks.. can't wait for the weekend to do this.
lastly, can anyone give me suggestion on what rom should i try in our opinion? thanks
jhannbernas said:
thanks.. can't wait for the weekend to do this.
lastly, can anyone give me suggestion on what rom should i try in our opinion? thanks
Click to expand...
Click to collapse
IMHO the stock based ROMs are the most stable, and trouble free. Head over to the DEV section and pick one out
There are plenty of ROMS to choose from. Some are better than others, and some work better for others. Taboonay seems to be the most popular. I liked Lightspeed because it basically removed EVERYTHING that I didn't need. Citvao seems to be gaining momentium. There is also another guy by the name of THOR who created a custom ROM that incorporates some files from the transformer stock ROM that is pretty good too.
I'd try them all and see what one you like best
Steps to using CWM?
If there's a thread to using CWM please direct me to it.
I have taken a short cut in using it by watching a YouTube video for installing a custom ROM and not learned all the in's and out's of using CWM.
I had installed the OTA HC 3.2 over a rooted 3.1 and lost my rooting as I expected. I decided I wanted to have root capabilites but with HC 3.2, so I found the (Oct 5 )version here and started over again.
I started with the Method 2 approach to install HC 3.2 update (that was already rooted here on this web site) to get to HC 3.0.1. However, initially when I got to installing the HC 3.2 zip it just booted afterwards and then went to a blank screen. So I tried it again only not doing all the clearing of user data, caches, etc., that was mentioned in the YouTube Video for installing a custom ROM. That worked. I now have a Acer Iconia 16 GB A500 rooted with HC 3.2 on it which what I wanted.
I would like to try some other ROMs and still go back if I could but I'm not sure about what exactly has to be cleared every time you load a new ROM. I don't want to have it hang again to a blank screen and maybe screw it up so I can't fix it.
Any directions?
Oh, BTW, when I installed the HC 3.0.1 from Method 2, it was so unstable that I couldn't make a WIFI connection. I had to go right to 3.1 to be able to use WIFI and get Acer Recovery Installer and continue on to installing HC 3.2 rooted.
Thanks
Redevil06 said:
If there's a thread to using CWM please direct me to it.
I have taken a short cut in using it by watching a YouTube video for installing a custom ROM and not learned all the in's and out's of using CWM.
I had installed the OTA HC 3.2 over a rooted 3.1 and lost my rooting as I expected. I decided I wanted to have root capabilites but with HC 3.2, so I found the (Oct 5 )version here and started over again.
I started with the Method 2 approach to install HC 3.2 update (that was already rooted here on this web site) to get to HC 3.0.1. However, initially when I got to installing the HC 3.2 zip it just booted afterwards and then went to a blank screen. So I tried it again only not doing all the clearing of user data, caches, etc., that was mentioned in the YouTube Video for installing a custom ROM. That worked. I now have a Acer Iconia 16 GB A500 rooted with HC 3.2 on it which what I wanted.
I would like to try some other ROMs and still go back if I could but I'm not sure about what exactly has to be cleared every time you load a new ROM. I don't want to have it hang again to a blank screen and maybe screw it up so I can't fix it.
Any directions?
Oh, BTW, when I installed the HC 3.0.1 from Method 2, it was so unstable that I couldn't make a WIFI connection. I had to go right to 3.1 to be able to use WIFI and get Acer Recovery Installer and continue on to installing HC 3.2 rooted.
Thanks
Click to expand...
Click to collapse
This has been posted in another thread by another member, and I saved it. I just can't remember who posted it again.
It's how I do EVERY flash and NEVER have problems.
"Before installing:
Boot into CWM
1/wipe cache
2/wipe data/factory reset
Advanced Menu:
3/wipe dalvik
4/wipe battery stat
Mount and Storage Menu
5/format (system, data, cache )... leave SD card alone.
install the zip ( new rom ) file !
Once done installing... repeat steps #1 - #4 only ( this is to assured that you are cleaned 110% in regard to the NEW rom that you have just installed )
DO NOT DO THE STEP #5 AFTER THE INSTALLATION !
Reboot system into initial Android greeting screen."
Some would say it's a bit on the "overkill" side, but better safe than sorry.
Thanks for the quick reply.
I think I also found where some of the information I wanted was in:
http://forum.xda-developers.com/showthread.php?t=1205204
I should have done more searching.
Thanks again
Oh, BTW, I have read your other posts on this site and like what you have to say. Also, the last step you have, Step 5, isn't in the YouTube video. Maybe that's where I fouled up and somehow recovered by doing again without some of the clearing. I think I just lucked out and got it working. Initially, without WIFI, I was stuck on how can you install Acer Recovery Installer without going to the "Market"? I had to go to 3.1 to get WIFI and then install it from the Market. I searched the internet with a computer for it, but couldn't find the apk to download so I could move it to a SD card and the Acer. Anyway it's working now and looking forward to more new ROMs and maybe Ice Cream if that's going to be the way to go in the future.
hardslog said:
You should install the Acer recovery installer first, then boot into CWM. When you are in there you will have the option to perform a full backup. This backup function will become your best friend.
Click to expand...
Click to collapse
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Right on!
drkalo said:
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Click to expand...
Click to collapse
+1
Some people don't read before posting
kjy2010 said:
+1
Some people don't read before posting
Click to expand...
Click to collapse
MY BAD!
I thought I read that he rooted it already and wanted to make a backup of that......
drkalo said:
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Click to expand...
Click to collapse
got it. thanks!
Somebody, please. I've had my tablet running rooted versions of Thor's rom, I'm currently running the ICS one...and honestly, it's too much. I just really want to go back...to how the thing was when I bought it. Then I'll just OTA to the newest OS available. Somebody please help
What do you mean it's too much?
Wish I could help though, I'm not into ROMing so I have no info but I'm sure someone will come along or you can try using the search [if you haven't already]. I'm pretty sure you're not the first person who's come along wanting to revert back to stock.
Like all the little glitches and things in the ROMs really add up...I just want stock back and I'll wait for ICS. It was fun while it lasted but now I'm into hardware modding.
You should try the search function within the forums to help with this. There are several threads on this already. Here is one for starters;
http://forum.xda-developers.com/showthread.php?t=1420358&highlight=stock
Bill
You are running experimental version of Thor's ROM, of course there would be a lot of glitches. I've tried almost all HC ROMs out there and the one I'm sticking with is Thor 14.2, only glitch in that ROM is that the rotate lock switch does not work.
Note: Reason I'm using 14.2 is because that is the only ROM that play nice with my GPS.
Run Acer recovery installer, load Acer recovery, run iconia root and remove root. Put the Chinese 3.0.1 unsecured kernel on your SD card, should be named update.zip.
Reboot to recovery, It will automatically run the update.
When you have 3.0.1 on your tab, go to settings>about>updates and let it update to the latest version of android, you may need to do this a couple of times as it seems to only go up to the next release of android.
All fixed, back on stock android and no root....
Cant you just boot into CWM. And restore the anand backup that you created before flashing any roms.. Then boot load acer recovery installer and use it to install STOCK RECOVERY..
.
Im sure as such a intelligent person that you are . YOU DID Make and save a backup. as every rom on XDA Tells you to do so before flashing...
If not just look for a full STOCK ROM And flash it...
Good Luck
To be honest, the ONLY way to get a nandroid backup of 3.2 for me was to go ack to 3.0.1... At this point I no longer can get a backup of my stock rom... So was pointless making a nandroid backup of the buggy OS that the unsecured 3.0.1 rom is....
I don't know if anyone else had this problem but it was a pain in the arse for me....
erica_renee said:
Cant you just boot into CWM. And restore the anand backup that you created before flashing any roms.. Then boot load acer recovery installer and use it to install STOCK RECOVERY..
.
Im sure as such a intelligent person that you are . YOU DID Make and save a backup. as every rom on XDA Tells you to do so before flashing...
If not just look for a full STOCK ROM And flash it...
Good Luck
Click to expand...
Click to collapse
Yeah, I have my 3.2 nandroid that just has the root?
ultramag69 said:
Run Acer recovery installer, load Acer recovery, run iconia root and remove root. Put the Chinese 3.0.1 unsecured kernel on your SD card, should be named update.zip.
Reboot to recovery, It will automatically run the update.
When you have 3.0.1 on your tab, go to settings>about>updates and let it update to the latest version of android, you may need to do this a couple of times as it seems to only go up to the next release of android.
All fixed, back on stock android and no root....
Click to expand...
Click to collapse
Do what ultramag69 said, and you will have an unrooted up to date A500!
Btw, my A500 works great whith Thor's 14.2 Rom...especially 3G
I'm no longer providing support for this thread due to time constrains with school, thank you for your support and it been nice sharing this method with you all. I may be gone but this method has still been reported as working, but it is possible that the next updates pushed to your phone might break the rooting and this method might not work anymore. But there is no harm in trying, at most you get an error in recovery saying file is invalid.
This method works on the released ICS rom from Germany and I would expect it to work for the rest of the ICS roms due for release..
This method does not increase the binary counter or causes a yellow exclamation mark
Update :
Due to rising numbers of phone being bricked based on rumors and stuff, I strongly suggest NOT trying to use any nandroid backup or restore on this CWM and it is best we keep CWM out of our devices to do major I/O stuff. So far I have never seen anyone bricked their devices on this small rooting/unrooting process but JUST DO NOT MAKE BACKUPS OR RESTORES!
Rooting
Download the Files first and put in your EXTERNAL SD
Reboot to stock recovery. - Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage. - Touch the screen as if you are using the phone to choose the options.
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Unroot
Download this File first and put in your EXTERNAL SD
Reboot to recovery.- Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage.- Touch the screen as if you are using the phone to choose the options
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from External SD
Choose and Install SU-Uninstaller-Signed.zip
Reboot
You are done and now your device is Unrooted
Partial Root
Alright i managed to obtain partial root myself and a fix for the Partial root is quite simple. You can install SuperSU by Chainfire and update the root. would fix the Partial root. Once you install this.. DO NOT USE the Superuser app and DO NOT uninstall the SuperUser app. Use SuperSU from now.
SuperSU - https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
MOD Edit: cwm.zip removed from the attachments, read Entropy512's post.
Thanks, but does this install CWM as well? id like to know so that I can go straight to flashing roms from it
are you sure this works ? can anyone confirm ?
nightfox11 said:
are you sure this works ? can anyone confirm ?
Click to expand...
Click to collapse
Works perfectly. Just rooted stock ICS.
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
kvanlier said:
Works perfectly. Just rooted stock ICS.
Click to expand...
Click to collapse
thanks man!
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
akenis said:
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yes you will end up with the same result if you take either one of the 2 ways to root
Binary counter is a Samsung measurement of how many times you flashed custom firmwares using PC Odin, and the yellow (not red ) triangle is just a logo to further show that you indeed flashed custom firmware
However, the binary counter will not increase (and therefore no yellow triangle will appear) if you:
1. Flash stock firmware with PC Odin
2. Flash using Mobile Odin app by ChainfireXDA
3. Flash using CWM recovery
I got binary counted to 1 with yellow triangle after flashing ics stock from alba.can i use this method to erase counter and triangle?
Sent from my GT-N7000 using Tapatalk 2
So this gives cwm too looks easy
Sent from my GT-N7000 using Tapatalk 2
Drat?
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
victorator said:
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Click to expand...
Click to collapse
LordManhattan said:
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
Click to expand...
Click to collapse
Not many ways to have a drastic difference from the method but hey it works well.
p51d007 said:
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
Click to expand...
Click to collapse
This method works as long as you are on Stock ICS.. Can't really go wrong really.
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
how come i only got partial root? i cannot paste into system
deathst said:
This method works as long as you are on Stock ICS.. Can't really go wrong really.
Click to expand...
Click to collapse
You are right, finally got my root back ICS, after the 2.3.6 update, been a while, now I have to remember how to use the freeze program, LBE security etc...all over again LOL. THANKS!
elijahtan said:
how come i only got partial root? i cannot paste into system
Click to expand...
Click to collapse
Try rooting again.. Are you sure your file manager app was given permission? Cause this thing is practically fool proof.
nandihno said:
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
Click to expand...
Click to collapse
Glad it works for you Yes I wonder why is not many people taking notice.. :S
...and i thought I was screwed
THANKS MAN. works perfect. much faster than having to redownload the odex vrs
Worked perfectly thanks !
Sent from my HTC One X using xda premium
hmmm.... didn't work for me. CWM looks for update.zip so i renamed it as such. installed and rebooted to CWMR, no touch menu. same old blue colored menu. install su-binary, stuck at unmounting /system = not rooted.
I just got the OTA update to Android 4.4, and being eager to get it installed, hit the install button right away. I told a few people I was going to be a few minutes while installing the update... and tapped the button.
That was three hours ago, roughly.
I'm on a rooted nexus 4 with CWM Touch edition installed as a recovery. I don't know exactly what version right now but it was the latest when I installed it a few months ago.
The install launched CWM, and I waited as the loading bar filled. Right at the end it gave an error message - in a panic I didn't take note of what it was, hit the onscreen buttons and went through a window telling me I might have lost SU permissions - which I told it to fix. The startup animation (with four dots, the new 4.4 animation I guess?) started... and continued for more than five minutes.
I was still panicking and instantly launched back into CWM, downloaded a (I think correct, checked it multiple times, as on does...) update zip from the web, and flashed it via adb sideload. This gave me an "Error 7" and a failed install. I tried again, same result. Then gave up and hit the restart button in the hope that one of the attempts had indeed worked...
I now have a Nexus 4 sitting on my desk playing a nice dotty animation, and it's been doing that for fifteen minutes as of now. I'm intending to leave it as such hoping that it will actually turn on and it's just having a very long boot.
So, the question. Anyone have any ideas how to save my Nexus?
I'd rather like to end up with the data on the device intact (stupidly did not back up before installing and can't get any files off it until an install works) and possibly with Android KitKat running on it, as was the original aim of tonight, but if neither are possible, I'd at least like to end up with a functioning phone... just with any stock rom.
Thanks in advance.
P.S. I'm not new to flashing ROMs manually - my last phone was a ZTE Blade which never ran any ROM well, so I must have flashed on that phone at least ten times, including via ADB.
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
totally-not-me said:
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
Click to expand...
Click to collapse
Your post saved me from a complete wipe and reinstall, so thank you for sharing your fix. I had a very similar issue but my Status 7 appeared to be because of my previous root and the new install not being able change the permissions on some /system files.
Now I just need to re-enable root via the NRT.
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
dethrat said:
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
Not blaming you xda has almost become useless in terms of finding real info in the past week. Bombardment of repeated posts about 4.4
Sent from my Nexus 4 using Tapatalk
Lokitez said:
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
Click to expand...
Click to collapse
Sideloading is only for flashable zip packages, not official factory images that required using fastboot. Use the guide links in my signature for instruction to flash factory image.
Or you can use sideload to flash flashable stock roms: http://forum.xda-developers.com/showthread.php?t=2527806
Unless your wife is really into flashing, I suggest just leaving it everything stock.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
RickyBO89 said:
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
Click to expand...
Click to collapse
It will softbrick the device, or atleast fail. I don't even have to try CWM, but with TWRP, if I make any changes to the /system partition it failed. I suggest you just flash a stock 4.4 rom: http://forum.xda-developers.com/showthread.php?t=2010887