Related
I setup my memory card through WinImage to install size agnostic 1.3. I put CM7 Nightly #177 on my Boot partition of memory card and then put memory card in Nook and it installed and shutdown when completed. I turn on my Nook and it begins with the Read Forever Logo and boots off emmc... It doesn't even try to boot of the Memory card.... I noticed this after I updated my stock Nook on the emmc to B&N 1.3??? Any Ideas why my nook wont boot up Cyanogenmod boot able card? Before B&N 1.3 I would see the Cyanogenmod Logo and I could hold the home key to boot up the boot menu and select either memory card or Stock... But I can't get it too from the memory card? Any Ideas?
Thanks In Advance,
Jer
Any Ideas or Suggestions... What if I copied the u-boot.bin from the boot of the sdcard to the emmc... maybe then I could get it to boot into the cyanogenmod boot and choose the sd to boot.... I don't understand it booted up on the sd card to install the nightly(for the first time that is) and then it just doesn't boot again... it just goes directly to the stock... I know the memory slot works because I used a different memory card and it installed the nightly.... I even tried a different nightly and it install just fine but it wont boot from the memory card again.???
Power the NC off, remove the uSD, insert it back in the NC again, power on.
Try a couple times.
If still having problem, do a fresh clean install again.
Tried what you said... it still shows "Read Forever" instantly after turning it on... no cyanogenmod logo... so it is obviously not even trying to load the SD card. When you say fresh clean install, on what do I do it on... A new memory card and install the latest nightly or Factory reset on stock nook?
votinh said:
Power the NC off, remove the uSD, insert it back in the NC again, power on.
Try a couple times.
If still having problem, do a fresh clean install again.
Click to expand...
Click to collapse
Press and hold the N button, then press the power button. Hold them until the green Cyangenmod logo shows AND "booting into recovery" shows up. Then release both.
It will explode CM7 the display will dim (around a 1 minute).
Watch the backlight and when it goes off, reboot the same way. It will flash the green Cyangenmod and the display will go back off (normal.)
Reboot again the same way and then instant you see the green Cyanogenmod logo release both buttons and let it boot up. It will take about 30 seconds for the CMy guy to show up and about a minute total to get to the main screen.
The problem still remains... I don't get to see the Cyanogenmod Logo... It shows the Read Forever logo and boots into Nook stock??? Its like I don't have a memory card in there.... When In stock nook it show the memory card logo in the bottom left and I can click on it it displays the files on it ... u-boot.bin file and all the others.... I just don't understand why it wont boot when turned on.
I wonder if it has anything to do with that I had Clockwork Mod on my emmc and I used the Clockwork Mod remover to get it back to stock recovery??? Maybe this messed up the boot sequence??? It s weird though when I put Cynogenmod on the memorycard the first time... it boots up the card correctly and begins the Linux Penguin install... So obvious it boots from the memory card.... I don't know what to do.
Help!!!
Just curious, but did you try to read the card in the card reader?
If you wrote it in Windows, you might have to check via disk management that a boot partition was made.
winimage sucks. Many, including myself, have had the same issue. Use win32diskimager instead. That's what worked for me.
Thank you Thank you
Win32Diskimager was the key... and too easy to use.... Thank you so much.... It took so long to find out the answer... Thanks to all that tried to help!!!
After several agonizing hours of writing image, formatting, reading, and panicking, I have finally installed CM7 via verygreen's method.
Thanks for the tip about win32diskimager. this made all the difference!
amp3d said:
After several agonizing hours of writing image, formatting, reading, and panicking, I have finally installed CM7 via verygreen's method.
Thanks for the tip about win32diskimager. this made all the difference!
Click to expand...
Click to collapse
Check your stock Nook. Did you end up with Clockwork Recovery on it?
how do i check?
as far as i know, there wasnt a CWM on verygreen's method, was there?
When I wrote the image using WinImage, the NC always booted up stock. nothing out of the ordinary.
When I wrote it with Win32, it immediately loaded the installer.
but now after turning the device off, taking out the sd, booting stock, and powering off to put the sd card in, cm7 can't seem to get a wifi connection... hope to find the answer soon
The Device:
Nookcolor Refurb - came with stock 1.2 installed. Rooted with CM7 - initially had boot partition problems and went back and did the fix for it. (was using an old CWR, so had to redo that, too). Worked mostly fine for a few weeks. Had a little trouble installing the recent cm7 stable update. But after clearing and redo, no problems. Then I updated Adobe flash to 10.3 through the market. bad, bad, bad. (I've discovered). It has gone into a bootloop, but it doesn't even get in far enough to bring up CWR either internally or on a bootable SD card. It brings up "loading" - whether in CM7 or CWR - then shuts itself off. I have tried the 3 button salute and 8 interrupted boots, but neither works in any way. Is there something else I can do?
Also, a side note, the device will not charge to green light - even if charging overnight. At first I thought it was a battery issue, but after a day of combing the boards, I'm thinking bootloop from hell.
Help!!!!
Are you running CM 7 internally or from a card? If internally, try making a bootable CM 7 card and booting from that.
I am running it internally. The device will not boot from a card or internally. It doesn't get far enough into the boot before it loops for CWR to start up - either internally or off the sd card. I can get to the boot menu (hold down n when it starts up), but it doesn't boot off any of the options there, just goes to black screen.
What happens when you do the 8 failed boots?
Nothing really happens with 8 failed boots. I think it terminates the boot process before it gets far enough along for it to "count". Loading comes up, I count one thousand one....all the way to one thousand seven. Then it shuts off, often reboots itself. Same deal with CWR. Loading comes up, count to 7, shuts off. I can get to the boot menu in CM7, but I it doesn't respond when I request any type of boot from anywhere. Either hangs or restarts.
I'm trying ADB, but it won't stay connected. Flicks on right at the end of the loading process and then shuts down. It really sucks.
Shelly, shoot me a pm... i'll give ya my phone number and we'll work on getting it going.
Sorry if this is redundant, but in very basic troubleshooting have you tried charging your Nook? It probably is more complicated/serious than a low battery, but it wouldn't hurt to rule it out.
I finally did get it to charge to green light. Didn't make a difference. I can get it to hang sometimes when it's trying to get into CWR. And it will stay on the Boot Menu.
Just a side note, I have another NC that I've had since Jan. Autonootered, Manual Nootered, CM7ed, brought back from the dead many a times.
Dizzy Den - am shooting you a message shortly. Thanks.
Has this been solved? If yes how?
Could you find a solution to your problem?
I'm having the same issue now. Bought a Nook Color in November, Autonooted, flashed recovery from ROM Manager, flashed CM 7.1.0 internally from downloaded ZIP files via ROM Manager, was working just fine for a week, stable, fast, perfect. Overclocked to 1200 MHz after a few days which made the experience even nicer.
Then installed and started Google Maps which didn't work - the Nook turned off on launch of Google Maps app.
I had set Wifi to "stay on all the time" beforehand (which might have been bad because it creates Sleep of Death syndrome as i now know).
Now when i turn it on it shows "Loading" for 7 seconds and then the screen turns off. This is when booting CM, when booting the internal recovery (shows "loading recovery" for 7 seconds) and when booting from any SD card image (i've tried at least 10 different bootable SD card images, different cards and different card readers).
It recognizes and tries to boot off SD cards - i get different "Loading" screens depending on the image, honey-colored for a honeycomb image, with two skulls for a recovery, ... So that works.
The nook seems to be in some kind of "on" state because i need to hold the power button to turn it off before i can get it to boot again.
I can get to the boot menu as you could, but booting from there doesn't do anything at all. So the hardware seems to be OK because the boot menu itself works well and for more than 7 seconds.
I can charge it and it goes to a green light so it's no battery issue.
The nook does not show up on USB - well once it did for a second but that was it.
I even tried to let the battery run completely empty so internal registers can get reset - didn't change anything.
Help! Is it bricked now?
Going to a B&N store isn't an option btw - the next one is 6500 km from here.
(This is the first time i ever ask for help on a forum. I am running a ZTE Blade with CM7 just fine, and I've been stuck often enough but always found a solution myself...)
Gunnar
Have you guys tried this:
http://forum.xda-developers.com/showthread.php?t=1308304
Or completely restoring it to stock:
http://mrm3.net/nook-color-recover-any-bricked-device/
Tried, can't get far enough
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
tralulu said:
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
Click to expand...
Click to collapse
When you overclocked it, did you notice it getting hotter than usual? I wonder if it was due to the overclocking. All the users I see with unrecoverable nooks is after they overclocked.
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
tralulu said:
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
Click to expand...
Click to collapse
I own 4 of them so I would prefer the term "Unbrickable", but at this point I'm not really sure.
Try 8 failed boots and see if you can get into recovery to reset to factory.
cant get it working
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
tntviper1 said:
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
Click to expand...
Click to collapse
how did you write the image to the SD card? you can't just do the write button in winimage, you have to use the "convert virtual hard disk image to drive" or something... really should be mentioned in the n00b guides.
Sequence in winimage:
Disk->Use disk (whatever your sd card is)
Disk->Restore virtual hard disk image on physical drive (select the image you're trying to write)
Click ok on the warning and you should have a boot disk
"Write disk" is prominent but just copies the files to the disk, not resize or make it bootable.
Nope - no change
DizzyDen, nope, 8 failed boots does nothing. Just fails 8 times, no restore.
I wanted to run a custom ROM on my A500 (first attempt at installing custom ROM), but i'm now stuck at the boot animation.
I downgraded my A500 to 3.0.1, rooted, installed clockwork mod, upgraded cwm to 1.5. So far so good.
Then i downloaded thor rom v12, copied it to the external sd card (by putting it on USB thumb drive, transfer to tablet, copy to external SD using file explorer - something tells me I'm going to need to pick up an sd card reader for my computer)
Rebooted into recovery, wiped everything (had nothing of value installed yet), and then chose to install zip file, chose thor_rom_v12.zip on external SD card, it started installing - looked like it succeeded.
Reboot tablet, and i've been staring at the boot animation (electric blue pulsating android with spinning gears on it) for about 45 minutes.
How should I proceed from here? Any idea what I did wrong?
Thanks
Hold the power button down and see if you can force it to shut down. I dont think itll turn off but its worth a try. You could also try the hard reset button (pin hole on the side of the tab) if the reset works than you should be able to boot back into recovery. If not than youll just have to wait till the battery dies.
Once you eventually get it turned off than try booting into recovery and do a full wipe and reflash the rom. I have a feeling the file you downloaded is corrupted though. if this is so than your tab probally wont boot up again.
At this point id redownload the thor or another rom and than try flashing that. You'd have to get an sd reader since you won't be able to transfer the files through your iconia again. If you can manage to get a clean download on your micro sd somehow than i'd skip straight to this step and start redownloading the rom right now.
BTW these are just the things i would try from knowing what I do about android. I haven't had any issues with my tab yet so I havent looked for solutions for this it, but ive dealt with other boot looped and soft bricked devices.
I'm sure if you do a search you'll find something.
How it started: I use a NC with mirage 7.2 flashed to the emmc in my car. It runs Torque to display engine data, and is switched in and out of sleep with the ignition. Two days ago I started the car and got the low-battery "exclamation point" icon thing, so I figured the charging cable must have come loose*. I took it all out and left it charging overnight, but when I went to boot it in the morning it was stuck in a cyanoboot loop. I couldn't power the device down or enter emmc recovery. When I completely unplug the NC I can't do anything, the screen remains black no matter what I press, except it flashes white every 5 seconds or so. If I manage to plug it on, get to the cyanoboot loading screen and unplug it while holding the power button down at the right time, I can sometimes get it to power off completely.
What I have done so far: Tried various recovery SD methods, none of which worked. Wiped cache/data/system, factory reset, tried loading 7.2 again over the top of whatever is left in there, lol. Basically after it first happened I probably made a big mess of the file system in a desperate attempt for some kind of stability. I tried this recovery SD: http://forum.xda-developers.com/showthread.php?p=25354258#post25354258 ; section A10, and managed to get into CWR. I've never felt such joy in my life.
What finally worked: I repaired the 2nd partition with the help of this thread: http://forum.xda-developers.com/showthread.php?t=1759558 . I did not repair or format any other partitions though. After repairing the partition, I did a factory reset and flashed mirage 7.2 and gapps back onto the emmc. Before I rebooted, I swapped a clean SD in but it still went back into the bootloop..BUT...when I put my recovery SD back in it booted into 7.2! I set everything up and was happy to have it running again. Battery level was at 88%.
What made it stop working: I was testing to make sure the NC would enter sleep mode when disconnected from power, so I unplugged it. Everything went black, no "sleeping" screen, just a hard shut-down. I powered it back on and I'm now back in a cyanomod boot loop.
So...any ideas? If there's a way to completely wipe and reinstall everything I'm OK with that. I've never used ADB before but I'll give it a shot if someone can lead me in the right direction. Thanks in advance.
*I'm using a 2amp USB car charger with a modified data-looped cable for a/c style charging in the car. I know the supplied nook cables are prone to going bad, and this may have happened with the vibration of the car and all. Not sure.
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
SPLEclipse said:
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
Click to expand...
Click to collapse
To completely wipe and reflash everything, do the other two zips that you said you did not do from my partition repair thread.
Sent from my Nook HD+ running CM10 on Hybrid SD
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Sounds like there might be some bad data in emmc, I had this problem before and fixed it by formatting everything , even emmc and wiping dalvik cache. Then boot off a SD card using the latest cwm.
Sent from my NookColor using xda app-developers app
SPLEclipse said:
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Click to expand...
Click to collapse
It is possible that your partition table is messed up. The only way to find out is to boot to recovery, connect your USB cable to the PC and run ADB. It is also possible to make a CM bootable SD and use terminal emulator to check it out.
Once you get ADB shell or terminal emulator working, type the following command:
fdisk -l /dev/block/mmcblk0
It should say 965 cylinders, 4 heads, 63 sectors.
If it does not, we need to do a manual repair.
You can also abandon emmc and just run off SD.
Sent from my Nook HD+ running CM10 on Hybrid SD
Summary:
I bricked my sister's Nook Color. She bought it refurbished at a pawn shop for cheap and everything was working until I told my sister that I could root the nook and put an android rom on it. My biggest mistake ever.
I looked at a lot of forums relating to the problem and it seems like there isn't a fix. So basically I got to the point of having CWM working.
All was going so well and I decided to flash eyeballer's cm-9-encore-20120904-0700-unofficial.zip on it. The one on Goo.im. After looking at screenshots of CM9 I was impressed.
I did the factory reset on it and wipe the cache, I flashed the CM9 and it was installing and it seem that it was taking a long time and then the nook turned off.
The biggest mistake that I made was that I formatted the boot , I'm a noob, I figured I wasn't the only one so I came across a thread here http://forum.xda-developers.com/showthread.php?t=949699
I thought that CM9 got installed and when I went to turn it on, nothing whatsoever... It doesn't boot no more.
I tried putting the 1gb bootable CWM on a 1gb sd card with Win32 Disk Imager and the Nook didn't boot from the SD card either and I also did the same with an 8gb.
When I go connect the Nook on the computer it searches for a driver called Omap3630 but it doesn't install and it seems to disconnect itself.
I am was looking for more threads and found out that I'm in a similar situation as a user called Jiv_au here,
http://forum.xda-developers.com/showthread.php?t=1146065
3rd post. I also tried what he did with the 8 boot attempts, pressing power button for 60 seconds and pressing the power on, the N and the volumes.
Seakuza said:
Summary:
I bricked my sister's Nook Color. She bought it refurbished at a pawn shop for cheap and everything was working until I told my sister that I could root the nook and put an android rom on it. My biggest mistake ever.
I looked at a lot of forums relating to the problem and it seems like there isn't a fix. So basically I got to the point of having CWM working.
All was going so well and I decided to flash eyeballer's cm-9-encore-20120904-0700-unofficial.zip on it. The one on Goo.im. After looking at screenshots of CM9 I was impressed.
I did the factory reset on it and wipe the cache, I flashed the CM9 and it was installing and it seem that it was taking a long time and then the nook turned off.
The biggest mistake that I made was that I formatted the boot , I'm a noob, I figured I wasn't the only one so I came across a thread here http://forum.xda-developers.com/showthread.php?t=949699
I thought that CM9 got installed and when I went to turn it on, nothing whatsoever... It doesn't boot no more.
I tried putting the 1gb bootable CWM on a 1gb sd card with Win32 Disk Imager and the Nook didn't boot from the SD card either and I also did the same with an 8gb.
When I go connect the Nook on the computer it searches for a driver called Omap3630 but it doesn't install and it seems to disconnect itself.
I am was looking for more threads and found out that I'm in a similar situation as a user called Jiv_au here,
http://forum.xda-developers.com/showthread.php?t=1146065
3rd post. I also tried what he did with the 8 boot attempts, pressing power button for 60 seconds and pressing the power on, the N and the volumes.
Click to expand...
Click to collapse
The problem is that you formatted boot, and CM does not include all of the needed boot files if you formatted boot. You will need to flash the stock firmware back onto the device, and then you can proceed to flash whatever ROM you want on the device, LINK.
I am not sure what version bootable CWM you are using, but download and flash this one,LINK. Since you saw the Omap3630 driver prompt, it does mean that it still is alive and attempting to go through the booting process. As for getting it to boot from this card, you will not get any visual indication that the device is on or not, the screen will stay dark if it’s on or off. Since the device might have been on this whole time I recommend that you fully charge the device before proceeding forward. With no USB cable connected to the device, press and hold the power button for 30 seconds, then insert the SD card, then press and hold the power button for 5 seconds to turn it on. It should boot into the CWM recovery, if it does not press the power button for 30 seconds and try again. It might take a couple attempts, but you should be able to get it. Once you get the device to boot, wipe data/cache, and flash the stock image, and reboot the device. Once you have a working device, you can then boot into the CWM card, and flash the ROM that you want.
GMPOWER said:
The problem is that you formatted boot, and CM does not include all of the needed boot files if you formatted boot. You will need to flash the stock firmware back onto the device, and then you can proceed to flash whatever ROM you want on the device, LINK.
I am not sure what version bootable CWM you are using, but download and flash this one,LINK. Since you saw the Omap3630 driver prompt, it does mean that it still is alive and attempting to go through the booting process. As for getting it to boot from this card, you will not get any visual indication that the device is on or not, the screen will stay dark if it’s on or off. Since the device might have been on this whole time I recommend that you fully charge the device before proceeding forward. With no USB cable connected to the device, press and hold the power button for 30 seconds, then insert the SD card, then press and hold the power button for 5 seconds to turn it on. It should boot into the CWM recovery, if it does not press the power button for 30 seconds and try again. It might take a couple attempts, but you should be able to get it. Once you get the device to boot, wipe data/cache, and flash the stock image, and reboot the device. Once you have a working device, you can then boot into the CWM card, and flash the ROM that you want.
Click to expand...
Click to collapse
You gave me a bit of hope but its not booting. The nook is dead... thanks for the help.
edit: I heard that pressing Power + N is like forcing a shut down so I hold those for 30 seconds and then put the SD card in it No boot.
I tried it again and put the Sd card in it and then press the power button still nothing. I believe this is definitely dead. I wish she had bought it at the B&N store. I think I'm getting her a Nook tablet. I owe it to her.