Related
Being stupid and mildly curious, I formatted the system partition and now the phone won't boot passed the model screen, not the galaxy s logo, but the first screen that I would call the manufacture splash screen.
Serves me right for being curious.
Recovery mode is disabled on this phone and cannot use odin since the computer doesn't see the device.
The viable solution is to have it re-flashed at samsung repair center and learn from my mistake, but I was also wondering about the boot process.
In traditional computers, the bios will search for bootable media in the order set in the bios. The question is, does the android boot process do the same? Has anyone tried? I was thinking of making the micro SD bootable with the android system volume on it, hoping that the phone will see the system on the external sd, for which then I can then mount and restore the system on the internal SD.
Is this possible?
you might be able to get the 3buttons working by heating up the phone with a hair dryer trick
remove battery, sim card, and SD card
then heat up the phone, and try to power it up with the 3 button download mode
never heard of such a thing, but what do I have to lose...other than a 560.00 phone.
AllGamer said:
you might be able to get the 3buttons working by heating up the phone with a hair dryer trick
remove battery, sim card, and SD card
then heat up the phone, and try to power it up with the 3 button download mode
Click to expand...
Click to collapse
lol, would you mind explaining a bit how this is even rational?
it's not rational at all, even i was skeptical about it at first
but many have got it to work that way, and that's more than enough proof
even if it's not logical at all
abd reboot recovery
I've had the same issue with an unsuccesfull lagfix.
No 3 button recovery.
I've connected the phone to my computer (I have the android sdk installed) and I ran "abd reboot recovery". The phone rebooted in recovery and i did a factory restore.
It went great.
Try this. Good luck.
that doesn't work if they are bricked already
Well I don't know what I did but this morning when my nookie froyo emmc was at 20 percent it decided to turn off and not turn on and won't turn on when charged and will not boot any sd cards. I feel stupid but after my nook working on emmc froyo for a week and now its not even turning on I feel very stupid. All help is appreciated, thanks!
Sent from my ADR6300 using Tapatalk
Have you tried booting to the CWR card yet? And using Samuelhalff's zip that restores the stock partitions? This seems to have worked for many people experiencing the fatal Froyo crash. Take a look at the 'Easily Restore to Stock" thread found here in the Nook forums. And in the end if your device truly won't turn on, then chances are the guys down at B&N won't be able to either. *Warranty*
Well I have tried monster root pack as a card but I haven't tried stock partitioning,i dont know where the thread is. But will this let me even boot an sd card ?
Sent from my ADR6300 using Tapatalk
RileyGrant said:
Were you running froyo off emmc? If so:
http://forum.xda-developers.com/showthread.php?t=931720
I recommend flashing this ROM instead though (pre-rooted 1.1):
http://forum.xda-developers.com/showthread.php?t=932145
And yes if you insert the CWR sdcard into the nook and hold the power button, it will power on. The reason it isnt powering on currently is because your froyo boot partition is corrupted, not because of the nook itself. The CWR sdcard has a different boot partition that your nook will see and boot to when you hold the power button down with the CWR sdcard in.
Click to expand...
Click to collapse
Thats my post from an earlier thread with someone having the same issues. It worked for him, it should work for you. Just make sure you follow the steps right and especially make sure your burning the Clockwork image to your SDcard correctly that way it will boot into Clockwork instead of staying black.
I'm gonna have to give these steps a whirl. The downloads are taking foreeeever.
Also had Froyo installed with CWM and just got finished installing gapps. I went to format an SD card, had no luck, and tried to reboot. Ol' Nookie decided not to come back to life after that.
edit: wait, instead of flashing the stock rom can I flash the pre-rooted 1.1 rom?
Just read this over on android central (in a thread about flashing honeycomb). I believe it is what I did and why my nook won't boot:
****While running Honeycomb from Internal Memory NEVER choose the option to format your SD Card from within Honeycomb. The files that were altered to let HC run internally will lead the OS to actually format your boot partition instead of your SD. If you need to format an SD, do it on your computer or in an Android phone, etc.*****
Click to expand...
Click to collapse
Drat. Just got my CWM image on my sd card. Here goes nothin! Will report back
OK, I have CWM booting off the SD card, i'm formatting system and data under mounts and storage, and then i'm installing the 1.0.1 complete restore. It goes through and then I got to reboot system. Then...nothing. Back to black screen. Help please!
I can pop the SD card back in and boot back to CWM. I've tried several times now with no luck
samuelhalff has a flashable zip that restores the boot partition for situations like this. Go look for it in the development forum. you should be able to flash it using CWR and your NC ought to boot.
eyecrispy, thank you! samuelhalff's boot zip followed by his 1.0.1 complete restore zip did the trick.
RileyGrant, thank you for your post as well. Much obliged!!
Mine just shows a blank screen. All I did was boot into ClockwordMod Recovery, make a backup, then reboot. I was going to flash the Honeycomb Rom, but decided to give it some more thought first. Now All I get is the blank screen, it won't power all the way off, and it won't power on or anything
EDIT: Managed to get it to turn off, but when I turn it back on it boots into recovery. I select Reboot System now, and it reboots back into recovery. Forgive me, I'm so new to this Nook Color thing lol
EDIT AGAIN: Tried using the Monster Pack or whatever, flashed the removeclockwork.zip, followed by the installclockwork.zip, then removed the SD card, rebooted, and went right back into Clockwork Recovery. What gives?
YUP Same thing happened to me. I have read all the posts in this thread and i did try to format the card i had in my nook in the brand new phiremod froyo rom. Now it wont boot at all. I have a CRW card on hand and it wont even boot that. Idk right now, nothing is working.
Try reading through the Dummies Guide to Fixing 'My Nook Won't Boot'.
I did it last night and I'm back up and running again. Here's my post for an abridged version of what I did last night: http://forum.xda-developers.com/showpost.php?p=11374824&postcount=29
I had the same problem until I flashed the repartition fix.
Give that a try
I've got the exact same problem as the OP. Running Froyo on EMMC with no problems for a few days, then I left it for a while and now it wont turn back on or boot from uSD.
I've tried long presses on the power key, usb cable power up, but nothing works. I've tried the v4 HC image and the clockwork recovery image and neither are booting.
I verified the CWR image on my android phone and it does boot on my phone, so the image is definitely okay.
Hate to think it, but could this be a battery management issue in the 0.6.7 image and the battery is now screwed? Doesn't seem like boot partition corruption to me.
Any comments or suggestions are welcomed
ChrisAC84 said:
Mine just shows a blank screen. All I did was boot into ClockwordMod Recovery, make a backup, then reboot. I was going to flash the Honeycomb Rom, but decided to give it some more thought first. Now All I get is the blank screen, it won't power all the way off, and it won't power on or anything
EDIT: Managed to get it to turn off, but when I turn it back on it boots into recovery. I select Reboot System now, and it reboots back into recovery. Forgive me, I'm so new to this Nook Color thing lol
EDIT AGAIN: Tried using the Monster Pack or whatever, flashed the removeclockwork.zip, followed by the installclockwork.zip, then removed the SD card, rebooted, and went right back into Clockwork Recovery. What gives?
Click to expand...
Click to collapse
how did you get yours to turn off, my screen says loading... and is stuck there. any help in getting mine to shut off would be helpful
Does holding power button for a few seconds turn it off?
Same thing happened to me, this fixed my problem: http://forum.xda-developers.com/showthread.php?t=986977
Sorry for asking what's probably a silly question, but I haven't seen an answer. Is this known to the Nookie dev(s) and being addressed? Just had it happen running Nookie 0.6.8 off the SD card. I was really enjoying it and just telling the wife how I think I'll flash it to the eMMC, but I might have to reconsider if this might occur. Battery was ~80%, no goof-ups reformatting anything. Locked the screen around 1:10 this afternoon & hadn't touched it since. Got home about an hour ago to turn it on, nothing. Disappointing, Nookie is pretty good!
nook color wont turn on
so what to do if i dont have a sd card with cwr or honeycomb (what i was trying to run)ive already called for the replacement, but i would still like to know what to do.
I found this thread after suffering the same or similar problem to everyone else. I turned off the screen and set my nc aside for a few minutes, then it would no longer boot. Screen just stayed black and was completely unresponsive to any input. Working my way through some troubleshooting, I plugged the nc into my computer via USB and it booted into CM7 instantly. I have no idea why this happened, but it's working fine now.
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.
Not sure what I did while in recovery, but it was looping after trying to update Phiremod with a auto update. Screen went black and ever since my pc with not recognize the nook being plugged in nor will it boot into recovery with the appropriate zip and image on my sd card.
Any clues would be much appreciated
PapaMag said:
Not sure what I did while in recovery, but it was looping after trying to update Phiremod with a auto update. Screen went black and ever since my pc with not recognize the nook being plugged in nor will it boot into recovery with the appropriate zip and image on my sd card.
Any clues would be much appreciated
Click to expand...
Click to collapse
There's no way you bricked an "unbrickable" device. You may just have to create a CWM SD and restore your previous Phiremod ROM.
P.S. SD boot priority ROCKS!!
natoe33 said:
There's no way you bricked an "unbrickable" device...
Click to expand...
Click to collapse
Challenge Accepted!
The first thing to try if you're getting no response is to hold down 'n' while powering on and see what happens. Otherwise, hit the pinned "My Nook won't boot" thread in General.
Try booting with no SD card in. If that works some Androids I have played with don't like to boot with the ROM zip on the root. The nook especially gets stuck trying to boot from the SD when there is nothing to boot on it.
Sent from a CM7 DInc2
I am just saying I have tried all of the above and there is no response from my nook. I have the CMW SD and nothing, I have tried holding down the n while powering on, nothing I have tried booting with no SD, nothing. I have been all though the Pinned thread my nook won't boot, tried it all, even bought a new sd card just in case, nothing
PapaMag said:
I am just saying I have tried all of the above and there is no response from my nook. I have the CMW SD and nothing, I have tried holding down the n while powering on, nothing I have tried booting with no SD, nothing. I have been all though the Pinned thread my nook won't boot, tried it all, even bought a new sd card just in case, nothing
Click to expand...
Click to collapse
What program are you using to burn the clockwork card?
Sent from my LG Optimus V using Tapatalk
Win32Diskimager, I think I'm stuck until my pc with recognize the device. The light on the Nook Power Cord changes from yellow to green like it's supposed to. Can't imagine the port on the nook just going bad at the same time but maybe that's the case.
just got back from Barnes and Noble, they could not get the Nook to be recognized on their computer with a new cord either
PapaMag said:
Win32Diskimager, I think I'm stuck until my pc with recognize the device. The light on the Nook Power Cord changes from yellow to green like it's supposed to. Can't imagine the port on the nook just going bad at the same time but maybe that's the case.
Click to expand...
Click to collapse
Did you make sure to run as admin and check the MD5?
Sent from my LG Optimus V using Tapatalk
yes everything has been done over and over, the nook is not recognized by the pc which in turn won't allow me to boot to anything.
wonder if the screen went bad
but then again, if it is powering on and the screen is bad, you should see it via adb
if the port and the screen went bad, then you didnt brick it per say, but its just hardware failure.
if its under warranty and registered, id say try to get it rma'd
if it is truely dead, they cant say that you voided the warranty
The sdcard adapter being used to burn the cwm or cyanogenmod install can influence whether or not the nook will boot from it.
Try burning the sdcard using a different adapter. I ended up using both the nook itself as well as my phone plugged into my PC as any attempt to boot from an sdcard burnt from the adapter that came with it will not even power on when inserted into the nook.
Hope this helps.
Sent from my NookColor using XDA Premium App
After several attempts and a few SD Cards I am back up and running. Thanks for all the advice and help. I believe it was a bad image, finally got it restored, rooted and running cynogenmod once again
I saw in the other forum. Glad you got it working.....
While I was DE-registering my NOOK HD+ I pull the SD card. It pop up a dialogue box saying something has crashed. I dismissed it and proceeded the process again. Now my NOOK stuck at the NOOK logo. When I put in a SD card with CWM it does not get pass cyanoboot logo. How have a CWM backup for my nook but since it can't load CWM I can't do any restore. Please help.
Zxa329 said:
While I was DE-registering my NOOK HD+ I pull the SD card. It pop up a dialogue box saying something has crashed. I dismissed it and proceeded the process again. Now my NOOK stuck at the NOOK logo. When I put in a SD card with CWM it does not get pass cyanoboot logo. How have a CWM backup for my nook but since it can't load CWM I can't do any restore. Please help.
Click to expand...
Click to collapse
Try doing a 8 failed boot reset. Interrupt the boot without the SD in 8 times in a row. Just hold the power button for a few seconds after each boot try. It will format everything and install the factory rom. Then maybe you can boot the CWM SD and restore.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Try doing a 8 failed boot reset. Interrupt the boot without the SD in 8 times in a row. Just hold the power button for a few seconds after each boot try. It will format everything and install the factory rom. Then maybe you can boot the CWM SD and restore.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Dear Leapinlar,
Thank you very much for your advise. Have already done many power down and up etc. Just tried it again, see the Nook logo, press the power button until it disappear, press the button until it appear etc. Done more than 8, no luck. Is there some timing requirement? How does the home button come into play concerning some low level signal to which code? Tech support guy from BnN asked me to hold the two buttons for 30-40s, no luck there.
The fact that cyanoboot logo appear with the CWM does that mean code introduced by the SD card is gaining control but was stuck looking for something that was not there? Is there a version that can just boot up and let me do some restoring?
Zxa329 said:
Dear Leapinlar,
Thank you very much for your advise. Have already done many power down and up etc. Just tried it again, see the Nook logo, press the power button until it disappear, press the button until it appear etc. Done more than 8, no luck. Is there some timing requirement? How does the home button come into play concerning some low level signal to which code? Tech support guy from BnN asked me to hold the two buttons for 30-40s, no luck there.
The fact that cyanoboot logo appear with the CWM does that mean code introduced by the SD card is gaining control but was stuck looking for something that was not there? Is there a version that can just boot up and let me do some restoring?
Click to expand...
Click to collapse
Without the SD in, the booting to n logo and powering off many times should kick in the reset. Maybe you are powering off when it is trying to reset. Let it go with booting for a few seconds before you power off, to make sure it is not in the reset mode.
EDIT: Wait till the n dims (or even a little longer) each time before you power off. That way you are sure it is not in the reset mode.
Sent from my Nook HD+ running CM10 on Hybrid SD
Try pressing N (or it could've been N + power button) without the SD card in, right after switching on the device. You should have a menu appear to hard reset the device.
EDIT: Actually, you might need to press N before turning on the device. I definitely seen this menu while playing around with the buttons.
leapinlar said:
Without the SD in, the booting to n logo and powering off many times should kick in the reset. Maybe you are powering off when it is trying to reset. Let it go with booting for a few seconds before you power off, to make sure it is not in the reset mode.
EDIT: Wait till the n dims (or even a little longer) each time before you power off. That way you are sure it is not in the reset mode.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Tried, still no luck. Notice that dimming does not happen any more. Nook logo stay at the same brightness forever.
Zxa329 said:
Tried, still no luck. Notice that dimming does not happen any more. Nook logo stay at the same brightness forever.
Click to expand...
Click to collapse
Sounds like a hardware failure. I suggest a warranty exchange.
Sent from my Nook HD+ running CM10 on Hybrid SD
I say you can try put CWM on diff card and try booting off diff card. At least that's one last thing you haven't try. Still, that's not gonna fix your stock nook, unless you made a backup.
Zxa329 said:
When I put in a SD card with CWM it does not get pass cyanoboot logo. How have a CWM backup for my nook but since it can't load CWM I can't do any restore. Please help.
Click to expand...
Click to collapse
I was a bit hasty posting that, but now that I can see that you can see 'cyanoboot' logo, it appear that it does boot from sd card, just not a successful one. So, at least it seem the bootloader partition on the nook isn't corrupt. So, I'm pretty sure trying a diff card should work. We have at least a few people confirming to have similar problem after running CM10.1 on the HD+.
someone0 said:
I say you can try put CWM on diff card and try booting off diff card. At least that's one last thing you haven't try. Still, that's not gonna fix your stock nook, unless you made a backup.
I was a bit hasty posting that, but now that I can see that you can see 'cyanoboot' logo, it appear that it does boot from sd card, just not a successful one. So, at least it seem the bootloader partition on the nook isn't corrupt. So, I'm pretty sure trying a diff card should work. We have at least a few people confirming to have similar problem after running CM10.1 on the HD+.
Click to expand...
Click to collapse
He said he had a backup. But even if he did not, and he got a new CWM SD to work, he could flash my plain 2.0.0 stock zip linked in my HD/HD+ CWM thread.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
He said he had a backup. But even if he did not, and he got a new CWM SD to work, he could flash my plain 2.0.0 stock zip linked in my HD/HD+ CWM thread.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I tried making another SD from the image that was proven to work before. The result is the same. See the logo and it stops there.
Zxa329 said:
I tried making another SD from the image that was proven to work before. The result is the same. See the logo and it stops there.
Click to expand...
Click to collapse
Still sounds like a hardware failure to me.
Sent from my Nook HD+ running CM10 on Hybrid SD
Have you tried booting while the USB power plug in?