Related
I have a NC 1.2. I am able to root using a CWM 3.0.2.8 Msd card with Manual Nooter no problem. The problem occurs when I shut it off and then reboot. It gets to the part where the words "Nook Color" start scrolling across the screen. "Nook Color" completes one time successfully and when it starts scrolling again, it stops halfway through the first "o" in "Color", and just repeats indefinitely. The only thing I could do is completely reset, eight failed boots. At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off. Any ideas would be greatly appreciated.
reebz said:
I have a NC 1.2. I am able to root using a CWM 3.0.2.8 Msd card with Manual Nooter no problem. The problem occurs when I shut it off and then reboot. It gets to the part where the words "Nook Color" start scrolling across the screen. "Nook Color" completes one time successfully and when it starts scrolling again, it stops halfway through the first "o" in "Color", and just repeats indefinitely. The only thing I could do is completely reset, eight failed boots. At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
What version MN are you using? You’re not wiping anything when you flash MN, right?
reebz said:
…At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off.
Click to expand...
Click to collapse
Are you saying that after you flash MN, you remove the SD card, it will fully boot up into the OS, then when you turn off the device and try to turn it back on, it will then not boot up? Or, are you saying that after you flash MN, you remove the SD card, and then the device fails to boot?
It sounds to me like you are wiping the system before you flash MN, but until I get the answers to the above questions, I can’t say for sure. MN is a add on pack for the stock OS, not a full rom, so you don’t wipe before you flash.
I have latest version of MN. I do not wipe anything. I boot into CWM and install MN with a msd card. Upon successful installation of MN, I remove msd card and reboot successfully that one time into a rooted NC. I can use Gmail app, download and install from both Android and Amazon markets. However, if I power down completely and reboot, it loops as explained in my OP.
reebz said:
I have latest version of MN. I do not wipe anything. I boot into CWM and install MN with a msd card. Upon successful installation of MN, I remove msd card and reboot successfully that one time into a rooted NC. I can use Gmail app, download and install from both Android and Amazon markets. However, if I power down completely and reboot, it loops as explained in my OP.
Click to expand...
Click to collapse
Are you updating Adobe Flash? You can't directly update Adobe Flash from the Nook Color. The most common issues that will cause a boot loop on a NC after having a fully working device, are installing the wrong kernel, and updating Adobe Flash from the Market. If you updated Adobe Flash, download the attached file, and flash with CWM. The file should delete the old flash player, and install the updated one. This should give you a working device again. If it does work for you, please report back here so others will know what the fix it.
GMPOWER said:
Are you updating Adobe Flash? You can't directly update Adobe Flash from the Nook Color. The most common issues that will cause a boot loop on a NC after having a fully working device, are installing the wrong kernel, and updating Adobe Flash from the Market. If you updated Adobe Flash, download the attached file, and flash with CWM. The file should delete the old flash player, and install the updated one. This should give you a working device again. If it does work for you, please report back here so others will know what the fix it.
Click to expand...
Click to collapse
I have updated Flash Player from the Market after rooting. If I remember correctly, I've powered down after rooting and installing numerous apps, including Flash, and rebooted . Maybe that's the culprit. I have not installed a different kernel. I'll go ahead and install the attached zip, with much thanks, but I don't know if I want to power off and reboot, for fear of dreaded boot loop.
Ok, I installed Flash Fix and rebooted, and the same boot loop is occurring. Looks like time to reset and reroot, and for now, never turn it off.
reebz said:
I have updated Flash Player from the Market after rooting. If I remember correctly, I've powered down after rooting and installing numerous apps, including Flash, and rebooted . Maybe that's the culprit. I have not installed a different kernel. I'll go ahead and install the attached zip, with much thanks, but I don't know if I want to power off and reboot, for fear of dreaded boot loop.
Ok, I installed Flash Fix and rebooted, and the same boot loop is occurring. Looks like time to reset and reroot, and for now, never turn it off.
Click to expand...
Click to collapse
I just realized that I missed a step in the install script for that file, that is why it did not work for you. Yes, adobe flash is your problem. To update Adobe Flash on the nook color, you have to uninstall the old version, and then install the new adobe flash.
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Ok, thanks, I will reluctantly give this a try when I get home from work.
Edit: Ok, now. I'm trying to uninstall Flash Player and having difficulties. It doesn't show up in the app drawer, so I go to Market to see if there is an uninstall option, but there is only an update option, so I updated, and then uninstalled to see if that would work, but it still showed up in "my apps", in market. I opened up app drawer and selected manage apps and found it, but selecting the uninstall button does nothing. I then tried installing Titanium Backup and after installing, Titanium Backup won't open and doesn't even show up in my app drawer. So, I'm a little stymied now. Unsure what to do next
reebz said:
Ok, thanks, I will reluctantly give this a try when I get home from work.
Edit: Ok, now. I'm trying to uninstall Flash Player and having difficulties. It doesn't show up in the app drawer, so I go to Market to see if there is an uninstall option, but there is only an update option, so I updated, and then uninstalled to see if that would work, but it still showed up in "my apps", in market. I opened up app drawer and selected manage apps and found it, but selecting the uninstall button does nothing. I then tried installing Titanium Backup and after installing, Titanium Backup won't open and doesn't even show up in my app drawer. So, I'm a little stymied now. Unsure what to do next
Click to expand...
Click to collapse
Titanium Backup is going to be your best bet to do the uninstall process. When you selected update Flash from the market, then went and uninstalled it, you were only uninstalling the update. If TB installed, then it should show up in the app drawer of Zeam launcher. You can go into the market, and select to open it from there. Sometime it will not open on first attempt, because it is trying to ask you to give it root permission. If you still have trouble with it not opening, then uninstall it, and try to install it again. You can also open up the “Superuser” app to make sure that it has not been denied root permission.
TB definitely didn't appear in Zeam app drawer. I'm charging now and give it another shot in a bit.
Edit: Success. I got TB installed. I made a stupid error. I only installed the paid app, not the free also. I got Flash uninstalled and installed your Flash Fix.zip with numerous reboots with no boot loops.
GMPOWER, Thanks for your assistance
GMPOWER said:
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Click to expand...
Click to collapse
I don't normally bump old threads, but this just saved me
Thanks a lot, I was at wits end figuring out why it was boot looping.
dreadwing said:
I don't normally bump old threads, but this just saved me
Thanks a lot, I was at wits end figuring out why it was boot looping.
Click to expand...
Click to collapse
Same here. Big thanks to GMPower! (My first post here, now I can use the Thanks button!)
Total noob question. This is my first time rooting. I got the root to work fine but updated Flash before finding out about the loop. I'm not sure what I'm supposed to do to fix this problem. OP in this thread said he reinstalled MN 4.6.16 via bootable SD with CWM and could get his nook to boot up. I tried that and rebooted but I'm still getting stuck in the loop.
Do I need to wipe my nook before reapplying MN?
dahcheet said:
Total noob question. This is my first time rooting. I got the root to work fine but updated Flash before finding out about the loop. I'm not sure what I'm supposed to do to fix this problem. OP in this thread said he reinstalled MN 4.6.16 via bootable SD with CWM and could get his nook to boot up. I tried that and rebooted but I'm still getting stuck in the loop.
Do I need to wipe my nook before reapplying MN?
Click to expand...
Click to collapse
Use the zip file in post #7 (in this thread). Drop it onto the same SD card you used to load MN 4.6.16. Put the SD card in and it'll boot to CWM....then flash that zip file the same way you flashed MN. Then, power off the NC, remove the CWM SD card and put in your regular SD and turn the NC back on. That should be it...no more boot loop.
I've got the same issue as the thread started and I downloaded the zip from post 7 and flashed it just like I flashed MN, but it's still boot looping. It gets a bit farther into the "Nook Color" logo but keeps repeating.
Boot Loops NC 1.3
GMPOWER said:
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Click to expand...
Click to collapse
This problem started for me on Rooted 1.3. October 5th, Applied this fix.
Thanks GMPOWER
I figure I will explain my problem in more detail. I am working with my girlfriend's Nook trying to get it rooted. The first time I did she had 1.2 stock and I rooted it successfully. She updated flash not knowing that it would cause a boot loop. I had no idea how to fix it so she set it back to factory settings and procedded to update to 1.3 to see if that would solve the boot loop. I rooted it again and it started boot looping again. I found this thread and the flash fix. I flashed it onto the Nook and it fixed the loop problem.
Well she found out that the marketplace has limited visibility with 1.3 and wanted to go back to 1.2 to have her full visibility back. So she factory reset it again, I rooted it again and it started boot looping again. This time though the fix from post 7 isn't helping. I flash it and then reboot and it loads the "Nook Color" logo once fully and then stops and starts it over again and gets stuck at "Nook Col".
Is there anyone who might be able to help me with what the problem is, or am I gonna have to reset it back to stock, use Titanium Backup to remove flash and then use the zip from post 7? I know that it's not a root problem because I successfully rooted my mom's Nook before my girlfriends and her's is working fine.
Followed your instructions and my problem solved, many thanks!
johnny15 said:
Use the zip file in post #7 (in this thread). Drop it onto the same SD card you used to load MN 4.6.16. Put the SD card in and it'll boot to CWM....then flash that zip file the same way you flashed MN. Then, power off the NC, remove the CWM SD card and put in your regular SD and turn the NC back on. That should be it...no more boot loop.
Click to expand...
Click to collapse
my first post. thanks GMpower
just had this happen to me too. I've tried the flash update, and I get slightly more of the nook color boot graphic but it still hangs.
any thoughts?
Update 20111117: Updated .zip file to Adobe Flash 11.1 and AIR 3.1.
Update 20111020: Updated .zip file to reinstall Flash and AIR, previous version didn't properly fix AIR.
Steps I used to update Adobe Flash (to version 11.0) and AIR (version 3.0) so it doesn't update automatically and thus get me back into the boot loop cycle (again):
Go to Titanium Backup ( Pro )
You need to uninstall with this since these are system apps
Buy a Pro key and keep it on your SD card root, since this app will save your bacon
Uninstall Adobe AIR and Adobe Flash Player from Titanium Backup
It will warn you that you are uninstalling a system app, that's OK
I think that is why the update through Market isn't working
Open Market, Install Adobe Air (3.1.0.488 as of this post) and Adobe Flash Player (version 11.1 11.1.102.59 as of this post)
Nook seems to be working after several reboots. Also, note that Adobe updated their apps. After following the procedure above, I was able to update via Market without any problems with bootlooping.
Obviously, the above steps only work BEFORE Adobe gets auto-updated and you get in the boot loop cycle. If you are already in the boot loop cycle, download this file (Updated link, should work better this time):
FlashPlayer11.1_AIR3.1_Update_Fix_20111117
and install it using a ClockworkMod Recovery SD card.
Get a ClockworkMod Recovery SD card
http://forum.xda-developers.com/showthread.php?p=11987469
Put the zip from the above post on the SD card
Reboot your Nook with the SD card inserted
Install from Zip, Select zip from SD card, select the flash update
This basically will uninstall flash and air as system apps and install as a user apps. This is based on the zip from GMPOWER which updated flash to 10.3, which worked for some but not others, perhaps because it didn't touch Air:
http://forum.xda-developers.com/showpost.php?p=16526691&postcount=7
Also note, I have been through several cycles of restoring backups, restoring to factory, re-rooting, etc. this last week, so I was getting very annoyed and cautious. I think I was able narrow it down to just the Adobe updates causing my problems. I have been able to update ROM Manager, Superuser, and just about everything else with updates; and besides the Adobe updates, everthing worked, and I don't currently have a boot loop problem.
Note, I didn't update Superuser or ROM Manager until after I applied the above updates to Flash and AIR. After several reboots, my Nook is still working fine.
For those of you who are still having trouble getting your Nook back, and the attached zip doesn't work for you, you can do the following. Using the instructions on this site, I got my Nook back up and running to factory new condition:
http://mrm3.net/nook-color-recover-any-bricked-device/
(Quick method at top, not older methods below; instructions slimmed down from several posts here at XDA, updated for stock 1.2) also here on XDA:
http://forum.xda-developers.com/showthread.php?t=914690 (original restore to stock post)
http://forum.xda-developers.com/showthread.php?t=1050520 (update for stock rom 1.2)
Then, I registered my Nook (again).
At this point, I could have tried to update to 1.3, but my patience was a bit low, so I didn't go for it. If you do, be sure to follow the appropriate ManualNooter instructions here:
http://forum.xda-developers.com/showthread.php?t=1054027
Since I was still on Stock 1.2, I rooted using ManualNooter 4.6.16
(while in CMR, after running ManualNooter, I also applied update-Froyo1.2-dalingrin-OC-emmc-090111.zip, and that seemed to work without a hitch)
Then I reinstalled all the other apps I wanted on my Nook,
=== BUT DID NOT YET UPDATE ADOBE FLASH OR AIR ===
Flashed ClockworkMod Recovery, updated a lot of my apps using Market and Amazon Appstore, restored data and other apps from Titanium Backup,
Then I made a full backup of my Nook using CMR. (still booting normal, running fast and clean)
After confirming my Nook was as I wanted it, and that I had a good backup, I did the steps at the top of this post to update Adobe Flash and AIR.
After confirming that was working, and getting another backup on my SD. I then did the updates to ROM Manager and Superuser. It seemed like those updates happened at the same time as the boot loop, so I was cautious. My Nook is still working well without boot loops as of yet.
Results:
Kernel: Stock 1.2
Rooted with: ManualNooter 4.6.16
Additional Mods:
update-Froyo1.2-dalingrin-OC-emmc-090111.zip,
ClockworkMod Recovery 3.2.0.1,
ROM Manager 4.5.0.1, Titanium Backup 4.5.2,
Adobe Flash 11.1, Adobe AIR 3.1 (uninstalled system app, reinstalled via Market, updated via Market)
[Update Zip] CMR zip to update Flash Player and Air
I updated the original post with a link to the zip to fix the FlashPlayer and Air apps. I had intended to post it here, but since I'm new, I can't link externally in a reply.
Please let me know if there are any problems with the zip and I will get it updated. It worked on my Nook.
I updated the zip file 20111020 to fix a problem with the AIR reinstall.
Wow, thank you so much for this! I wish I had known this on the weekend when I was gong crazy trying to figure out why I was getting bootloops over and over. I can't seem to give you thanks though (probably because I never post, just lurk).
So far I haven't done the uninstall/re-install with TB. I am just making sure my Adobe air and Flash don't update, and when Air did I went into Nook Color Tools and uninstalled the update to set it back to what it was originally. That worked but it is a pain if it keeps happening. I will try the TB to uninsall the programs.
I too did a update on ROM Manager and Superuser (and a binary update), and all is still well. No bootloops. I hold my breath though every time my NC gets to the "color" part until the N appears and it all disolves.
thanks for this!!! this was really getting very frustrating.
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Thanks for this information. My nc is currently in a bootloop and won't load CWR. It shuts off before getting to that point (my bootloop is adobe air related). None of the restore to stock via SD card have worked for me. I'm now looking at ADB options, the post you referenced with the fix has some instructions for that. Did you use the ADB or the SD card instructions? I was actually rooted with CM7 before the bootloop.
Thanks,
shy guy1 said:
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Click to expand...
Click to collapse
I realized that my zip was not working to uninstall and reinstall Air properly. Try the updated zip file in the post.
shelly29 said:
Did you use the ADB or the SD card instructions?
Click to expand...
Click to collapse
I used the SD card instructions. Unless you have done something strange to your nook (not sure what), it should always boot from the SD card first, so you should never have problems booting into CMR from an SD card.
If the link in the original post doesn't work for you to get a CMR SD card, try the instructions here:
http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/
If you have a newer Nook, you may need to repartition your Nook's internal memory and use CMR version 3.2.0.1. See details here (this guy just condenses the instructions you can find on various posts on XDA, and tries to keep it up-to-date)
http://mrm3.net/nook-color-how-to-blue-dot-nook-color/
Also note that I updated the zip file in the post to correctly uninstall and reinstall Flash. I re=bootlooped my nook, and after applying the new zip, my nook was working.
Just an update....
I wanted to let U guys know that I had updated Adobe Flash, Air and Super Users and this has worked for me. I also went to double check the versions of both Flash an Air and they are the newest versions!? I still went to uncheck the "Update Automatically" setting in the market for them both just in case for future updates for the time being. Back up and Running! Thanks Again to ALL involved who put contributions to this
This may have worked for me
I tried the updated fix posted here, and the Nook booted properly. Thank you for this fix; I hope it continues to work for me.
I will have to locate the automated back up mentioned here (Titanium), and I will see how this works. I had been leaving my Nook on at all times to avoid the reboot until I turned it off yesterday, forgetting that I did not want to do that.
Awesome post.
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Thanks!!!! You are my new best friend. XD I ended up reflashing several times before I found this post. Followed the instructions and my Nook is happily running Android again without reinstalling (again!). I thank you. My Nook thanks you. And the Angry Birds who would have had to start from scratch thank you.
Thank you! It appears to work now. I've restarted a few times with success!
Took me about an hour to find this thead. I knew there would be an easier fix than starting from scratch. The zip worked on my rooted 1.2
Thanks! Keep up the good work
Thanks! That worked for me.
Stagnation1 said:
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Click to expand...
Click to collapse
From my previous searches, it seems the boot loop is usually caused by either an incompatible installation of Adobe flash, or an incompatible kernel (central part of the ROM). Hopefully the OP zip will fix the first, but I'm not sure of another way to fix the second, other than reflashing and rerooting. How far in the reflash/reroot process do you get before it boot loops again?
mastigia said:
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
Click to expand...
Click to collapse
Hmm, haven't seen that error. I'm not sure whether its related to the same problem. It sounds like you might need to re-register your nook with B&N. I'm not sure if you can do this without restoring to stock. Not much help, sorry.
I can't post a reply to this ([NC][1.2][1.3] ManualNooter 4.6.16) thread yet - Still new to these forums... I was one of the many in that thread who had installed ManualNooter 4.6.16 on Nook Stock 1.3 only to end up with a boot loop.
Wish I had found this thread last week - would have saved me a lot of headaches!
It's okay though - every boot loop is another opportunity to learn something new.
Thanks much for the easy walkthrough and I hope others find their way here too.
Just saw another new update for Flash & Air .. released yesterday I believe. Has anyone try them yet ? Just don't want to was my time getting into a boot loop again by updating it.
--
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
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Okaay said:
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Click to expand...
Click to collapse
root the tablet
then install ROM manager and flash the official recovery from there
works perfect
The bug is that you cannot boot into any recovery (cwm/twrp/stock) from bootloader unless you are plugged into you computer via a usb cable. The only other way to boot is to use a script but that requires a working system partition.
Sent from my Nexus 7
I have the same problem and I flashed the official CWM from Rom Manager. I made a nandroid before I messed with it and when I went to change the LCD Density, I don't know what happened but now it won't boot. I can't get into CWM either. I figure I'll use ADB when I get home to try and reboot into recovery, if not I'll search the forums for the stock image and reflash. If there is a HW workaround to get booted into it from the device itself that would be awesome. I had to do a battery pull to keep it from rebooting itself and killing the battery.
I've always had Rom Manager Pro and immediately after rooting, used it to flash backups, update to 6.0 cwm, etc. If your rooted you must have that or Goo Manager for TWRP flashing anyway. Might as well start immediately.
There is a thread somewhere here dealing with changing density. The Nexus7 has problems when you simply use a density changing app.. You must change density by modifying prop.build. You can do this using a root explorer app, or by using Rom Toolbox Pro. I use Rom Toolbox and it worked perfect.
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
jmhalder said:
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
Click to expand...
Click to collapse
Will that command allow me to access recovery to restore my backup?
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
yeahthatsme said:
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
Click to expand...
Click to collapse
I believe you need to be on the bootloader screen? I haven't flashed anything from Asus in a while, not since my original Transformer.
chrisjm00 said:
Will that command allow me to access recovery to restore my backup?
Click to expand...
Click to collapse
Code:
fastboot boot recovery.img
where recovery.img is a CWM image, should allow you to get into the recovery to fix whatever you messed up. Note that ADB is only functional if you already have CWM or Android booted... in the bootloader, fastboot is all that's available.
I have the same issue. Stuck at the Google logo with a padlock at the bottom. I didn't flash anything with ROM Manager just the recovery.img through fastboot, then did a fastboot reboot. Now I'm lucky if I can get the thing to stay off when I hold the power button it just pops back up to the padlock with Google logo.
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
CooLoserTech said:
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
Click to expand...
Click to collapse
Has anyone figured a way to access recovery using the buttons only? I've tried TWRP 2.2 and the newest cwm, and on a cold start from power off, it sticks at the Google logo. During a bootloop you are screwed unless you have a laptop within arms reach. Until this is rectified I'm leery of flashing anything. The whole point is being able to restore a nandroid in a crisis. I haven't found that ability yet. If anyone knows a way, please educate me!
Guess we can just wait. Besides there's not much development yet anyways. Would love to use AdFree and root explorer though.
Sent from my Nexus 7
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
Recommend downloading quickboot. It is a paid app but it boots you to recovery no hassles with the buttons
Sent from my Nexus 7 using Tapatalk 2
Ya i have tried several version of CWM and TWRP and manually reinstalled cwm via adb. but all of them don't let me boot from the bootloader, i get the google logo like everyone else. Not sure what else to try, need to not take any risks until there is a fix i guess ^_^ hope someone gets some ideas
I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?
phisher177 said:
I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?
Click to expand...
Click to collapse
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.
xxaddictedxx said:
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.
Click to expand...
Click to collapse
CM10's built in SU didn't seem to think the binaries needed updated, installed chainfire's SU and it wanted to update CWM.
it asked me about disabling recovery flash, to which i said yes. Its not the root im having an issue with though, its getting stuck at a black screen.
either way, update didn't work.
Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.
phisher177 said:
Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.
Click to expand...
Click to collapse
did you try one of the roms on xda? if MD5 dosent match then thats your problem