Database Users

Help needed: New User

I just bought my Epic 4G a few days ago and quickly discovered the existence of rooting and custom ROMS. Needless to say I took the plunge the other day.
I attempted to install the Epic Experience Froyo yesterday but it doesn't seem to load up properly.
Seemed simple enough. I boot into clockwork, I cleared data/factory cache, cache partition, and davnik cache three times each. I installed the ROM from my SD card, install says it's successful, so I hit the reboot.
After this I expect my new rom to load up but all that happens is the samsung logo comes up for about a minute, phone reboots again and goes into the factory Android system recovery utility.
Any ideas? Please help, my phone is inoperable at the moment.
-Dennis

Sounds like kernel. Dl a costume kernel and flash it thru cwm.
Sent from my SPH-D700 using Tapatalk

I'll have to apologize ahead of time because I'm completely new to rooting.
Which kernel should I use (a link to one with instructions would be helpful), and how do I get it on my SD card if it isn't booting up? (my pc doesn't have an SD card reader)

Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209

So, flash Odin/DK17 and then flash Epic Experience over this?

Ya also did you first do the one click root method to make sure you are definitely rooted? If you press. Volume down + camera button + power when booting and the letters are blue you are NOT rooted. If they are green then you are rooted. Sometimes when you install a rom it might take away your root so you might try doing it in the order of this:
1. Flash back to stock 2.1
2. Do theone click root method
3. Flash DK17 modem through odin
4. Install Epic Exprience

hgvidal said:
Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209
Click to expand...
Click to collapse
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?

idontwanttostudy said:
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?
Click to expand...
Click to collapse
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.

hgvidal said:
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.
Click to expand...
Click to collapse
I just did it today with the newest froyo version out by chance would it come with them? If not where can i get them? I cant seem to find the modem to dl

How can i tell by looking in my phone if i have it or not?

idontwanttostudy said:
How can i tell by looking in my phone if i have it or not?
Click to expand...
Click to collapse
Go to settings -> about phone and then check where it says "Baseband version" it should say DK17 in there. If it doesnt follow these instructions to download the files you need. It has step by step directions
http://www.nomie.mobi/how-to-install-dk17-modem-samsung-epic/

I assume this is the rom you flashed:
http://forum.xda-developers.com/showthread.php?t=856715
In the first post it has a link to the instructions to properly flash the rom. You can use those instructions to flash the modem and see if it fixes your problem. You might be better off just flashing everything again. It would mean downloading odin and the files to your pc and flashing them to your phone from your pc. The simplest way to do this is follow this thread
http://forum.xda-developers.com/showthread.php?t=853209
Follow the instructions carefully and when your done you have the new modem, the froyo rom, clockwork recovery, and be rooted.

I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?

idontwanttostudy said:
I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?
Click to expand...
Click to collapse
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App

raylusk said:
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ok I finally have it all worked out thanks a lot!

hgvidal said:
1. Flash back to stock 2.1 [through odin]
3. Flash DK17 modem through odin
4. Install Epic Exprience
Click to expand...
Click to collapse
I actually skipped step 2 and everything went fine for me. My laptop was being an asshole and not seeing the phone, so the 1 click root script simply wasn't working.. but then I realized that the DK17 flash via Odin that I got form the epic experience thread included clockworkmod and was pre-rooted and everything so I saw that step as unnecessary.

[RESOLVED] WIFI ERROR after unlock/root. Camera also not working

Wifi no longer works on my 2.3.1 Nexus S after rooting. Can anyone please help? I see possible driver solutions to the same problem under Nexus S, but assume the driver for Nexus S is not the same. When I try to enable wifi it says ERROR. I just discovered the camera also is not working.
Edit: Momohamed20's stock NAND fixed all my problems YAY!!

I've seen Wifi not work on mine running 2.3.1, I haven't rooted, usually it's after I try to turn on Wifi Hotspot and get the "Error" message, then Wifi won't work again until I reboot.

well i've rebooted and gone to fastboot and restore boot many times ... no difference

heinrich said:
well i've rebooted and gone to fastboot and restore boot many times ... no difference
Click to expand...
Click to collapse
A friend of mine just returned his to Best Buy because he was having the same issues. His new one doesn't have the issue

Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it

heinrich said:
Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it
Click to expand...
Click to collapse
Have you flashed either the MCR or CM7 ROMs in the Development section and still had the same problem?
Or the stock 2.3.1 NAND backup floating around in there too.

I just got my NS today its rooted with working camera and wifi, I'm also on 2.3.1. What I did was unlock the bootloader and rooted using the superboot method. You don't have to mess with anything else. I've read in several posts if you use other methods it can cause the issues your having
Sent from my Nexus S using XDA App

I just flashed the boot image from http://forum.xda-developers.com/showthread.php?t=884194 and the camera now works again, but not wifi. I can't find the stoclk NAND or I'd flash that. I see a link to the stock system.img in the thread I link to in this post, but it's a broken link

No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.

heinrich said:
No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.
Click to expand...
Click to collapse
Ah, okay, MCR is Modaco Custom Rom and CM7 is Cyanogenmod 7. They're both very good custom ROMS based on Android 2.3.1 with some added features and/or other changes. MCR is closer to stock, imo, if that's something you're interested in.
In order to flash them to your device you need to be rooted(which you said you are), and be able to flash Clockwork Recovery via fastboot or ROM Manager. If you're not familiar with Clockwork recovery/ROM Manager, check out this thread before proceeding: http://forum.xda-developers.com/showthread.php?t=875875

yep I have clockwork recovery and rom manager and all that

If someone can help me find the stock system rom I think it will fix tghe wifi problem .... camera now works.

Oh my goodness isn't there someone who knows how to get wifi working again?

RESOLVED
Momohammed20 resolved my issue with his full restore stock image and excellent write-up here: http://forum.xda-developers.com/showthread.php?t=884093

Help! stuck in boot animation after trying to update to 3.2

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.

For what it's worth my (manual) upgrade to ICS was smooth - process - stock i9020T

Hi All, am now using ICS 4.0.3 with no problems (bar a bit more battery use of course)
This is what *I* personally chose to do, based on what I'd read so far, on my stock 2.3.6 handset, to minimise hassle and risk;
Downloaded and renamed ZD3PyN0t.zip to update.zip
Full system wipe including the SDcard, rebooted, then copied update.zip to the SD
Switched off and booted to recovery mode, wiped cache just for completeness.
Rebooted again into recovery mode. Selected update.zip
Applied the update, then when finished, went back to recovery mode and wiped cache and factory reset again.
So far - Wireless works fine, phone works fine, 3g settings detected automatically from the SIM and works fine, very nice interface.
B

Can you go directly from 2.3.1 to 4.0.3 or would it be safer to go from 2.3.6 to 4.0.3
Thanks!
Sent from my Nexus S using XDA App

LegendSam said:
Can you go directly from 2.3.1 to 4.0.3 or would it be safer to go from 2.3.6 to 4.0.3
Thanks!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1063664 doesn't suggest a problem with doing that.. but I don't 100% know. I can't forsee a problem tho! Good luck.

personally i have had no problems following the same process which is also mentioned in the guides. have not even seen the power drain or wifi bug.

hey i am a complete noob at flashing...
so can i please know how to flash the 4.0.3 onto my 9020T??
http://forum.xda-developers.com/showthread.php?t=1063664
can i use the above link

roshan567 said:
hey i am a complete noob at flashing...
so can i please know how to flash the 4.0.3 onto my 9020T??
http://forum.xda-developers.com/showthread.php?t=1063664
can i use the above link
Click to expand...
Click to collapse
Hi there, yes this is the one I used - http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip for my i9020T

hey...see im facing a small problem...when i upgraded my nexus s manually using the file VQ8PQk_V...it worked for a few days and suddenly it stopped catching network...
then when i booted i found the lock state as locked and the carrier info to be TMB(im assuming to be T-mobile)...
jus for your information im in india and i use the airtel network...
so if i follow ur process should it start working again?

roshan567 said:
hey...see im facing a small problem...when i upgraded my nexus s manually using the file VQ8PQk_V...it worked for a few days and suddenly it stopped catching network...
then when i booted i found the lock state as locked and the carrier info to be TMB(im assuming to be T-mobile)...
jus for your information im in india and i use the airtel network...
so if i follow ur process should it start working again?
Click to expand...
Click to collapse
Hi Roshan, first of all I'm not really sure - so hop on google and do some searching - but I did also come across that file and avoided it as It was 1) supposed to be for Tmobile only and 2) smaller than the file I and others have used referenced above. So maybe that's some kind of incremental update.

hey...thanks for the information....in the below link..the file which you used is under FLASHABLE ROMS.
http://forum.xda-developers.com/showthread.php?t=1063664
so ill try it out with this one...
also how do i flash roms on the nexus s

Running Rooted 3.2.1 to ICS? Do I unroot?

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