Like the title says, I flashed RC2 (coming from RC1 so no wipe). Got a force close so I fixed permissions in ROM manager but the phone stopped responding after 5-10 minutes. Gave it another 5 minutes before I rebooted (using home + menu + hang up) and the phone freezes now on the first splash screen. Can't boot into recovery either. I can make it to the bootloader and tried restoring a nandroid back up but it always freezes midway (left it for a full hour and it was still frozen).
What else can I do in fastboot that may help? Any other options? Thanks.
EDIT
Cyanogen wrote on twitter that it might've been my SD card crapping out on me, so I replaced the SD card and reflashed recovery in fastboot and everything is working. However, I tried the same thing with the "bad" SD card (reflashed recovery) and it now works as well. I didn't realize it at the time but I think the actual culprit was when I updated Clockwork Recovery through ROM manager. Did it before fixing permissions and I'm guessing something went wrong when I updated and it was only after something also went wrong when fixing permissions that the problem surfaced.
Related
I just tried to flash Darky's 7.5 ROM [wiped] and bad things happened. I booted into Clockwork Recovery and selected the rom zip file. It looked like everything was going well, but it stopped on 'Copying Files...' and gave some error about line 85. So I tried again with the same result. I rebooted to see what would happen and it boots past the 'S' loading screen and then nothing. The screen remains black and seems to vibrate every few seconds. I suspect the ROM file I had was bad. How can I fix this? I can still boot to recovery. Is there a way to flash a ROM from the external SD card?
Thanks for any help.
hobbes487 said:
I just tried to flash Darky's 7.5 ROM [wiped] and bad things happened. I booted into Clockwork Recovery and selected the rom zip file. It looked like everything was going well, but it stopped on 'Copying Files...' and gave some error about line 85. So I tried again with the same result. I rebooted to see what would happen and it boots past the 'S' loading screen and then nothing. The screen remains black and seems to vibrate every few seconds. I suspect the ROM file I had was bad. How can I fix this? I can still boot to recovery. Is there a way to flash a ROM from the external SD card?
Thanks for any help.
Click to expand...
Click to collapse
You didn't factory reset before flashing.. Mount from CWM to put a different Rom on. ... This question should have been asked in Darkys thread.
ok so weird problem here..
my NC is fine besides this one problem.
ive rooted with autonooter to 1.0.1
if i turn my NC completely off and leave it all night, when i wake up in the morning it gets stuck on the "touch of... " screen. The only way to get past this is to reboot to recovery and select reboot..
any idea why this happens? if i just restart the NC, or just let it go to sleep this doesnt happen, only when its been fully off for a couple hours.
ive tried reverting to stock/rerooted all that to fix it, but nothing seems to work.
i know i can just let it sleep and problem solved, but id like to know why this happens or if anyone experienced anything like this before.. thanks!
Try holding down the "n" button while turning on the unit...
Other wise you might have messed up your boot partition, go to development and search for samelhaff's thread on a flashable zip where you can fix the boot.
it reboots to recovery (power+n) just fine... just doesnt reboot normally (just pressing n) .. gets stuck on touch of.. screen
after getting into CWR and selecting reboot it then boots up correctly..
dont know why it just wont reboot normally to begin with.
Same problem here.
After some testing with HC and CM7 roms i recovered to the 1.0.1 Eclair rooted with autonooter version. I turn it off and on some times and everything worked allright. Left it all night off and when i turn it on in the morning i was stuck at the "Touch the future...".
I flashed the stock boot repartition and it started normaly.
Yesterday i flashed the custom Froyo 0.6.8 and everything was allright untill the morning when i stuck again athe " touch..." screen.
I booted with CW and rebooted normally.
Same thing has happened to me twice. I've only been able to get it to boot by booting from my bootable cwr and selecting restart.
Also been noticing some oddities with it charging fully, sometimes while plugged in the status is simply "not charging", not "charging" or "dischargin" and the N symbol on the end of the cable is yellow, not green.
Now it's even worst. Every time i try to boot i get stuck in the "Touch..." screen and i can only boot through CW recovery.
Any ideas?
Glad I finally found some people with the same problem
So initially I took my stock nook (1.0.1) and ran autonooter. Worked great but I noticed it would randomly reboot. Also , same as the other posters, if I powered it all the way down it liked to automatically power up and get stuck on the boot screen. Only way to reset was boot into CWR and select the reboot option from there. I loaded CM7 and same problems so i thought it may be some kind of hardware issue.
Reverted to stock, no problems.
Back to autonooter and this time ran dual boot from EMMC with stock as main partition and HC v4 on second partition. So i don't have CWR anymore but have my SD card handy in case I need it.
Well after a couple days of normal usage the random reboots are gone. Left the unit on during the whole time. Last night I turned it off to apply my Phamtomskin and this morning woke up to find it stuck on the boot screen. Must have been doing that for a while because when i stuck in the SD card for CWR it gave me the low battery warning. After 15 minutes it rebooted to CWR and i was able to reboot normal from there.
Hopefully since a couple of us got the problem we can find some sort of fix. I would like to know if it is some kind of hardware issue or as poster #2 suggested its a simple matter of flashing the boot file. Would I loose my dual boot partition if I flash this zip? Any help appreciated and thanks what a great XDA community.
I think that it has to do with CW and boot. Can i remove CW recovery without affecting my configuration?
no change.
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
bump this?
pilotbluemike said:
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
Click to expand...
Click to collapse
Just get the bootable cwr, then you'll always have it handy. The stuck at touch of reading screen has happened to me twice, pulled out my bootable cwr, selected restart and all was well.
I've never heard of anyone having this problem with V 1.0.1. I know that a lot of people are having this same problem with V1.1. Apparently CWR and V1.1 don't coexist well. I had this problem after doing Stock Nook 1.0.1 --> Autonooter 2.12.25 --> Sideload to rooted V1.1. Some people also have the problem when going from stock V1.1 and using Autonooter 3.0. The fix in both cases is to uninstall CWR using the CWR removal tool mentioned here:
androidtablets.net/forum/nook-color-technical/6386-how-installing-using-clockworkmod-rom-manager-nandroid-backup-custom-kernels-20.html#post48469
(sorry, I can't post links yet.) It leaves the device rooted. It worked for me.
Can anyone give me a hand with this?
I was running CM7 n40 with ALSA and dalingrin's 0413a kernel. Watching videos in vevo when the nook froze and reset itself and got stuck looping at the CM7 animation.
I've rebooted into CWR, tried first wiping Dalvik cache, it didn't seem to make a difference. I then tried formatting /cache and reinstalling n40 and dalingrin's 0404 kernel. No joy either.
Short of reinstalling everything, is there anything else I can try?
If you are running from an SD card then your problem is likely the card. If you aren't running from an SD card then... Maybe someone else can help you.
Forgot to add, running from eMMC.
I had the same thing, only with CM stable...ended up having to rebuild my / boot with the file here.... http://forum.xda-developers.com/showthread.php?t=914690.
Very last file in first post. Had to flash it then start all over....
Sent from my NookColor using XDA Premium App
You are not alone, mine just did this after updating to the latest nightly and restoring with Titanium Backup. I did not flash a kernel, just the nightly using Rom Manager.
My symptoms were that it seemed to run OK, then I opened the gallery to set a different wallpaper and got constant FCs, so then I restarted. Now I'm watching the circle go round and round.
OK, back to previous, just restored the nandroid backup Rom Manager made prior to the update. Seems to be working fine.
I flashed n40 and dalingrin's oc kernel 0404. Stable and happy as can be.
I'm thinking the issue was with ALSA and experimental kernel 0413a, which has been reported to crash video playback in some cases. Don't know how or why it would corrupt my install though.
Let me just mention a lot of people are claiming false boot loops lately. Sometimes it just takes a long time to reboot, especially after it froze. I've had it take up to 20mins before with the little skateboard android.
So next time unless it's giving you "Touch The Future" and then the CWM treatment, give it a bit to load and see if it does after 10 mins or so. (Usually just after the screen dims, my nook loads up just fine)
No that's unacceptable. Considering the amount of data it should be loading, something is very wrong with your nook if it takes more than 5 minutes to boot.
And yes it was boot looping, the animation restarted itself repeatedly (wasn't just the arrow spinning).
Can't help at all but to offer another data point: I was on nightly 39, ALSA update, and kernel 0413a. Was flicking between homescreens when it locked up, forcing a hard shutdown. When I booted back up, it was stuck in a bootloop. Tried all the usual paths to recovery, but had to resort to a backup.
Moved on to n41 (ALSA included) and kernel 0418c. Stable in every case so far.
I'm having same issue and mine is still not working no matter what I did.
I even tried to restore it back to stock - Format/ Fdisk / DD / etc... tried everything I could find. I even had my back up but couldn't restore. I think I created more problem while I was trying to fix it.
Now I can only boot from SD. So I was not the only one.
Eww, I would never touch any sort of partition change with eMMC installs. Usually I just go back to stock or latest backup. Found out there may be an issue with backups created from CWR flashed to eMMC (MD5 check failure). SO anyone who's made a backp from that, do yourself a favor and boot off a CWR SD and do a backup onto that just to be safe.
Sorry about your troubles, hope you get it sorted. Guess I got away easy with just format and nightly re-flash.
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
I finally upgraded my wife's Verizon Tab to the 7/25/12 CM9 nightly four days ago. In that time, she's experienced two random sleep-of-death instances, from which I succesfully recovered. Today, however, she put her Tab down after using it for a bit, went back to it later, and it was off again, and very warm. She plugged it in and tried to re-start it, but it would hang on the CM9 splash screen forever.
I tried to re-start it and got the same results.
Then I tried booting into CWM Recovery to reboot from there, but got the same results.
I tried to fix permissions in CWM, but CWM became unresponsive.
I rebooted into CWM again and tried to restore a nandroid, but it failed since /data couldn't be mounted.
I then tried to flash the 7/28 nightly, but it couldn't mount /data either.
I used Heimdall to reflash Recovery and kernel (5.0.2.7 if I remember correctly) I had used to upgrade to CM9, and then tried to flash the 7/28 CM9 again. This time, after a very quick flash sequence, and a very long time (20 minutes) on the CM9 splash screen, it finally moved on to the boot animation, and eventually booted...right into a screen that said "Encryption Unsuccesful."
Per that screen's instructions, I elected to do a factory reset and reboot. After a very long time, the Tab rebooted to the same error screen.
Bottom line is, I've since learned the "Encryption Unsuccesful" bug is an ICS one (especially with unofficial ROMs), and it does a number on your internal and external data partitions/SD card. I was lucky in that the SD card didn't get wiped, but my Tab is unrecoverable. My latest attempt is to load a rooted stock Verizon ROM/recovery/kernel using Heimdall, but after almost an hour, I've just made it to the "Verizon Wireless" boot animation. Most threads I've read on this issue end up in dead-ends, and I couldn't find a single one that pertained to the Original Galaxy Tab, much less Verizon's.
Does anyone have any ideas as to what else I can do?