Related
Ok. Let me start by saying, I'm obviously not an expert on hacking/developing and stuff like that. I just love to tinker stuff so I learn in the process. So definitely not an expert. Just posted this thread hoping that someone whose possibly a lot more knowledgeable than I am would notice it and hopefully shed a light on this question.
Is TWRP 2.0 which can be seen here, working/compatible/available/will be available on our beloved NookColor?
All we are using right now is the ClockWorkMod Recoveries, right? Which I believe the latest is 3.2.0.1. I'm not saying at all that CWM is not sufficient enough to do whatever it needs to do, I just thought it would be awesome to be able to get your recovery things done THAT MUCH COOLER, navigating the device via the touchscreen rather than hardware buttons.
Hope this sparks more awareness!
+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.
majorpay said:
+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.
Click to expand...
Click to collapse
Oooh, that's too bad. And scary. Makes you worry about doing something that's not tried on the NookColor before. I wont dive in unless the devs really says that it's safe.
Hey, about your NC being bricked. I had something pretty similar happened to my NookColor before. Got stuck into a boot loop. Now before, I had my TitaniumBackup folder stored in the eMMC and I didn't want to do anything that would delete it. What I did is, I had another microSD card and created a bootable CWM. I installed a CM7 nightly on the microSD. Upon booting to the microSD build, I went and have adb wireless transfer my eMMC files to my PC. Now that I've recovered my TitaniumBackup folder, I formatted everything on my NC using the bootable CWM. Then what I did is I flashed the stock NC Rom which was 1.2 version. I did a factory reset. After that I had everything back to normal again. I flashed the nightly build on the eMMC again and from then on, had my TitaniumBackup folder on the microSD. Have you tried creating a bootable microSD?
A little late...
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.
fr4nk1yn said:
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.
Click to expand...
Click to collapse
Same here, I put together a nookie froyo card, and got bootloops.I took the memcard out and still got bootloops. I put a cwm card in, and STILL got bootloops. Then I made a new cwm card, and it booted just fine.
I was in CWR and formating system, data and made a mistake and formatted boot. I rebooted and now the NC will not power up. I put in my usd card with eyballer's img on it hoping that life would breath again... not yet. What can I do?
Hoser88 said:
I was in CWR and formating system, data and made a mistake and formatted boot. I rebooted and now the NC will not power up. I put in my usd card with eyballer's img on it hoping that life would breath again... not yet. What can I do?
Click to expand...
Click to collapse
Go through this thread closely... I will bet your nook color is not a brick.
You're Right!
Well, it's back and breathing again. Now back to the original problem I posted here - http://forum.xda-developers.com/showpost.php?p=24118096&postcount=5
I'm now reading about how to use ADB to adjust a boot flag that may be set to always cause the NC to boot to Recovery? Wish me luck.
Hmmm, another CwMR flashed into eMMC issue?
Hate that.
I want to know how to remove CwMR too.
Well, after a few weeks of reading posts, even opening up the hardware and taking the nook apart, here I am asking a question. I figure I would go to the source rather than those other place I was reading and tryign to get info from (mot os those places link here anyway). I know that everyone says that the nook is "unbrickable;" while I want to believe it, I may be in a place where it may be true.
I do want to add a thanks as well, since the NC "tablet" has been very handy, and my wife and I have really enjoyed it. Wouldn't have happened without you all. I wish I had more time to participate in developing, but working 80+ hours/week in a hospital limits my free time, as you can imagine.
I rooted the NC and installed Cyanogenmod 7 back in July 2011. It was a 1.1 model (if I recall correctly). I installed the mod to EMMC, along with CWM. Things ran fine for 6 months. Literally no issues. Then, one night the battery was dead, so I plugged it into the computer USB to charge while the machine was off. Didn't touch it at all. When I went to turn it on again, I was stuck in a bootloop. It would go to the cyanogenmod screen and say "Loading" then would start over again. So, I naturally made a bootable SD card, and tried going into CWR to fix things. However, the SD card had the bootloop as well. It would get to the two skulls and "Loading", flash blank, then start over again.
That went on for a while. I couldn't boot into anything, not into recovery, alternate images, literally nothing. So, I tried different images --- nothing. Finally, I did the power+n and got into the only screen that wouldn't keep resetting. It has blue text and says "Entering boot menu". The menu says "Encore U-boot Menu by j4mmr. 1.2 port+ extras by fattire." From this screen, I can navigate and change the boot options. However, once again, whatever I try does not actually boot, regardless of what I set it to. The only thing that I got from getting here was no more boot loops. After getting it to this point, I can try loading anything, and it will start, then the screen goes black/blank, and nothing happens. Left it on for hours to test.
Since that point, I have switched cards (SanDisk 2 GB class 4, Patriot 8 GB and a generic 8 GB microSD). I know that cards work correctly because I got a hold of a second nook, and they work fine on it. Below are a list of all the images I have tried to run off the SD. Again, nothing will boot, not even clockwork recovery/clockworkmod.
128 mb rootpack (IOMonster)
clockwork 3.0.2.8
clockwork 3.2.0.1 eyeballer
Nooter
Mirage_CM7_ICS_CM9_DualbootSD (this card works great on the working NC)
TWRP 2.0 RC0
Generic SD
Clockwork 0.7 -> starts boot loops again
I also tried ADB, connecting to the computer and using putty over SSH. Didn't work. 8 interrupted boots with 9th holding power+n. Nope. I even took the nook apart and disconnected the battery. Still no go.
If I recall, I think I had CWM 3.0.0.5 installed to the card and to the emmc.
If anyone has any other ideas, I could really use the help. I consider myself pretty computer literate (build my machines, coded in my spare time in the past, hacked a lot of my electronics). I have read many guides/sites and even tried the outdated stuff. Once again, I cannot get into clockwork recovery, so any guide that says to do that as the first step will not work. I also cannot boot off of the SD on cards that I know function.
Would using an older version of CWM (prior to 3.0.0.5) work? I think I remember reading a bunch of stuff about problems people were having with that version. The thing is, I wasn't installing or flashing anything new. I wish I was, because then I would know what was happening when everything got screwed up.
Thanks a bunch in advance for your guy's (gals?) time. This has been really painful.
Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP
Yeah, it has been frustrating, especially not knowing what happened in the first place. I actually did try the version from that first link (where I put 3.0.2.8). Again, the big issue I am having is that I cannot even get into the CWM. If I could, I could fix it. I also saw and read through that xda thread you kinked to (open right now in my browser), but the problem remains that I cannot even get to the point where I can flash something.
Thanks at least for responding. I'll try a few more things and see if it works, but I am running out of ideas.
In theory creating a bootable CWM card will get you into recovery even though you can't access the Recovery on the internal. Once you reach Recovery from the SD card you can flash whatever you need. It is just a matter of making a bootable recovery card that boots far enough to get you there.
In theory, yes, but as I said in my first post, I tried all the bootable cards without any luck. When I try to set the SD card as primary boot from that one screen from fattire, it locks and never restarts.
J515OP said:
Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP
Click to expand...
Click to collapse
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.
DigitalMD said:
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.
Click to expand...
Click to collapse
How did you get it to boot into CWM in the first place in order to flash? That is my current problem. Any method of fixing relies on the ability to boot into CWM from the SD card, which (for whatever reason) isn't working at the moment.
Well, tried to use the native Nook u-boot. Get the "Touch the Future of Reading" screen, then black, just like with any of the other cards. On the good nook, it boots into a linux file and runs the recovery script, so it is not the card reader or the SD card.
Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.
czarofthefrozentundra said:
Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.
Click to expand...
Click to collapse
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.
leapinlar said:
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.
Click to expand...
Click to collapse
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.
czarofthefrozentundra said:
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.
Click to expand...
Click to collapse
It goes to the boot menu when you hold n with eyeballers image burned to SD? What happens when you select SD and normal? Just a hang? With 'loading' showing?
Edit: I just thought of another reason that could be causing this. There is a flag set in /rom that tells the system to try to boot into recovery. It tries no matter what you tell it to do in the boot menu. ROM Manager uses that flag to boot to recovery when you tell it to. Then after you successfully get into recovery and exit it by telling CWM to reboot, CWM clears that flag. If your recovery is borked up, you never get that flag cleared and it's an endless loop.
There are two solutions I can think of. First, use racks dual boot SD that you already have and go into the boot menu with that. Tell it to go to SD and recovery. Hopefully his recovery will load. Then immediately exit by the menu. That should clear the flag. If that fixes it and it boots to CM7, go to ROM Manager and flash a new CWM to emmc.
If that does not fix it search xda for 'fix recovery'. There is a nook thread telling how to fix the recovery on emmc.
Edit2: I just thought of a third way to try to get it to boot. Take eyeballers 3.2.0.1 CWM SD and put it in your PC. There should be two files there named uImage and uRamdisk. Make a copy of them on the SD and rename the copies to uRecImg and uRecRam. Then put back in nook and reboot to see what you get.
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
See my edit2 above for a third way to try to clear the flag.
Sent from my NookColor running ICS and Tapatalk
czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
Hello? Feedback?
Sent from my Nook Color running ICS and Tapatalk
Ha, I tried the quick reply function, and it didn't work. Here is what I wrote yesterday (verbatim, since I still had the window open):
"Well, so far no luck. Here is what I have tried, and the new information that I learned.
Used dual boot SD that I know works and booted into bootloader menu. Tried all different options on the SD card. What happens is that it thinks for a bit, then turns the screen black, but the boot screen never comes up (i.e. the Cyanogenmod logo that usually starts before things boot). So there must be some problem there.
If I hold down power, it will restart. Again, the screen turns black after the loading screen is on for a while (happens no matter which image I burned to the card).
I still need to try the other method (eyeballer one). I don't think the EMMC reset will work with my particular issue, as I had read that thread earlier."
czarofthefrozentundra said:
I still need to try the other method (eyeballer one).
Click to expand...
Click to collapse
If the problem is the recovery flag, the mods to the eyeballer CWM SD should work. If it does not work, it may be something else. If it does work you can flash a new CWM to emmc using another eyeballer zip. Get it here:
http://forum.xda-developers.com/showthread.php?p=21932561
You would want the first choice.
Sent from my Nook Color running ICS and Tapatalk
Cool. Will give it a try tonight and report back. Just have to find my spare SD card.
So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?
czarofthefrozentundra said:
So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?
Click to expand...
Click to collapse
I'm not sure what to tell you to do next. I guess I am going to send you to a post that tells pretty plainly how to do the 8 failed boots. I know you tried that, but timing is very critical with that procedure. Worth a try to me.
http://forum.xda-developers.com/showthread.php?p=25405429
How do you do the 8 failed boot deal with the cyanogenmod screen running. I am not sure about the timing of things. Also, which buttons? I have seen people do it with just the power button. Other places say with the power+n+vol up.
Hello everyone,
Im new to this forum but have lurked for a few years. I consider myself reasonably familiar with android and have installed custom roms on various devices in the past.
Yesterday I installed the latest CM10 Color Nook Rom to an micro SD and on to my wife's Nook Color. Install went great, Wifi up and working and I went to install Gapps via recovery. When it came back on the keyboard kept dying and I realized I had installed too new of Gapps. My bad. I shut off the nook and removed the micro SD with the intentions of wiping it out and starting fresh.
I put the nook off to the side and about 15 mins later went to install my fresh install of JB when I found the nook completely dead and unresponsive. The battery was at about 90% when i turned it off.
This was only supposed to be a install to the sd, I dont know why it's affecting the nook when theres no sd card in it.
So far I have tried:
pulling out the sd card
hard reset
creating a nook color restore micro sd and booting from that
charging
The nook remains completely dead and 100% unresponsive and I have no idea where to go from here! I keep reading its hard to brick these but im starting to think thats what happened!
I was thinking of taking off the cover and doing a battery pull. Any ideas?
If you truly have nothing happening, it certainly sounds like a hardware problem. Pulling battery to reset is worth a try. It's worked for me on several Android devices (never tried it with a Nook, though). Somewhere recently in the forum I read how to do a safe battery pull on a Noo, but don't recollect where. Search for it. If that fails, I'd say your Nook is kaput.
scthomps said:
Hello everyone,
Im new to this forum but have lurked for a few years. I consider myself reasonably familiar with android and have installed custom roms on various devices in the past.
Yesterday I installed the latest CM10 Color Nook Rom to an micro SD and on to my wife's Nook Color. Install went great, Wifi up and working and I went to install Gapps via recovery. When it came back on the keyboard kept dying and I realized I had installed too new of Gapps. My bad. I shut off the nook and removed the micro SD with the intentions of wiping it out and starting fresh.
I put the nook off to the side and about 15 mins later went to install my fresh install of JB when I found the nook completely dead and unresponsive. The battery was at about 90% when i turned it off.
This was only supposed to be a install to the sd, I dont know why it's affecting the nook when theres no sd card in it.
So far I have tried:
pulling out the sd card
hard reset
creating a nook color restore micro sd and booting from that
charging
The nook remains completely dead and 100% unresponsive and I have no idea where to go from here! I keep reading its hard to brick these but im starting to think thats what happened!
I was thinking of taking off the cover and doing a battery pull. Any ideas?
Click to expand...
Click to collapse
No, don't pull the cover. What happened is your boot files got corrupted on internal memory. It will not power on unless those files are there or a valid bootable SD is in the slot.
You need to get my bootable CWM SD from my tips thread linked in my signature. That should boot. Then you need to reinstall whatever ROM you had on internal memory. If it was stock you can get the CWM flashable version also from my tips thread.
Sent from my HD+ running CM10 on SD with XDA Premium
Thanks!
leapinlar said:
No, don't pull the cover. What happened is your boot files got corrupted on internal memory. It will not power on unless those files are there or a valid bootable SD is in the slot.
You need to get my bootable CWM SD from my tips thread linked in my signature. That should boot. Then you need to reinstall whatever ROM you had on internal memory. If it was stock you can get the CWM flashable version also from my tips thread.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
Im going to try your linked CWM and create the SD from your tips first. The last I saw the battery it said roughly 80% and assuming it wasn't stuck in some loop it should be still good.
If the battery IS actually dead will the nook charge with no OS installed? My charger cord came apart months ago and I have been charging (slowyly; lol) off a generic cord plugged into the computer. Will this make a difference or should I wait to try this when I have a proper charger cord?
Thanks for everyone's help! You guys are lifesavers!
scthomps said:
Im going to try your linked CWM and create the SD from your tips first. The last I saw the battery it said roughly 80% and assuming it wasn't stuck in some loop it should be still good.
If the battery IS actually dead will the nook charge with no OS installed? My charger cord came apart months ago and I have been charging (slowyly; lol) off a generic cord plugged into the computer. Will this make a difference or should I wait to try this when I have a proper charger cord?
Thanks for everyone's help! You guys are lifesavers!
Click to expand...
Click to collapse
It should charge slowly with that cable. Even if not booted to anything.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
leapinlar said:
It should charge slowly with that cable. Even if not booted to anything.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
Click to expand...
Click to collapse
I followed your instructions and the "battery too low to power on" message came up, which is the first sign of life I have seen out of the nook in a few days. Thanks!
leapinlar said:
No, don't pull the cover. What happened is your boot files got corrupted on internal memory. It will not power on unless those files are there or a valid bootable SD is in the slot.
You need to get my bootable CWM SD from my tips thread linked in my signature. That should boot. Then you need to reinstall whatever ROM you had on internal memory. If it was stock you can get the CWM flashable version also from my tips thread.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
My CM10 went completely dead last week. I put lepinlar's v6.0.1.2 Bootable CWM Recovery on and SD card and now have some sign of life.
I get to the cyanoboot universal bootloader screen, but it just sits with a Loading.... note. I've let it sit for about 10 minutes and nothing else happens. I also tried the N key and it does load the boot menu...but no option gets me past that initial screen...
should it just boot directly into CMW? any other suggestions would be appreciated!
ginhead said:
My CM10 went completely dead last week. I put lepinlar's v6.0.1.2 Bootable CWM Recovery on and SD card and now have some sign of life.
I get to the cyanoboot universal bootloader screen, but it just sits with a Loading.... note. I've let it sit for about 10 minutes and nothing else happens. I also tried the N key and it does load the boot menu...but no option gets me past that initial screen...
should it just boot directly into CMW? any other suggestions would be appreciated!
Click to expand...
Click to collapse
Not really sure what you mean. You say you put my bootable CWM on SD. You mean you burned the image to an SD? And it boots to the cyanoboot screen but gets stuck on loading...?
Does the cyanoboot screen have a small s0 in the upper left corner? If does that means it is trying to boot from the SD. It should boot directly into CWM by itself.
Try reburning it or use my 5.5.0.4 version. Once it gets to CWM, install a new ROM with it. The original reason it went dead was corrupted files on your internal boot partition. Reflashing the ROM should fix it.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Not really sure what you mean. You say you put my bootable CWM on SD. You mean you burned the image to an SD? And it boots to the cyanoboot screen but gets stuck on loading...?
Does the cyanoboot screen have a small s0 in the upper left corner? If does that means it is trying to boot from the SD. It should boot directly into CWM by itself.
Try reburning it or use my 5.5.0.4 version. Once it gets to CWM, install a new ROM with it. The original reason it went dead was corrupted files on your internal boot partition. Reflashing the ROM should fix it.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
thanks for the reply.
I've used Win32diskimager to burn both v6.0.1.2 and 5.5.04 to an SD card. I do see the S0 in the upper left corner, but the screen never moves past the initial Loading...screen.
I can get it to load clockworkmod using a '1gb_clockwork-3.0.1.0' recovery image (also tried 1gb_clockwork-3.2.0.1-eyeballer w/the same result). However, I get a message that states:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/loginterrrupt
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I then attempted to flash your Nook Color EMMC Partition Repair zips....The NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip will complete the 'repartitioning /boot /system /data /cache and media' step.
it sticks on the Repartitioning internal memory - be patient this may take a while'...i've let it sit for about 30+ minutes...how long should this take? My nook is currently sitting in this phase now...I guess I'll let it sit for a while and see if anything else happens.
thanks for the help with this...from what I've read, I'm hopeful there is a solution...
ginhead said:
thanks for the reply.
I've used Win32diskimager to burn both v6.0.1.2 and 5.5.04 to an SD card. I do see the S0 in the upper left corner, but the screen never moves past the initial Loading...screen.
I can get it to load clockworkmod using a '1gb_clockwork-3.0.1.0' recovery image (also tried 1gb_clockwork-3.2.0.1-eyeballer w/the same result). However, I get a message that states:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/loginterrrupt
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I then attempted to flash your Nook Color EMMC Partition Repair zips....The NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip will complete the 'repartitioning /boot /system /data /cache and media' step.
it sticks on the Repartitioning internal memory - be patient this may take a while'...i've let it sit for about 30+ minutes...how long should this take? My nook is currently sitting in this phase now...I guess I'll let it sit for a while and see if anything else happens.
thanks for the help with this...from what I've read, I'm hopeful there is a solution...
Click to expand...
Click to collapse
Which recovery are you using to flash the repair zips? It needs to be at least 3.2.0.1. Don't use that 3.0.1.0. Don't worry about those E: messages, it just means cache is not formatted.
It is sounding like the first step of the repartitioning is not taking. That is fixing partition one. I'll be right back with another zip to see if you can flash that.
Try the attached and see what happens. You can also try the bootable TWRP to flash rather than CWM. I have that linked in that partition fix thread.
Removed attachment.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Which recovery are you using to flash the repair zips? It needs to be at least 3.2.0.1. Don't use that 3.0.1.0. Don't worry about those E: messages, it just means cache is not formatted.
It is sounding like the first step of the repartitioning is not taking. That is fixing partition one. I'll be right back with another zip to see if you can flash that.
Try the attached and see what happens. You can also try the bootable TWRP to flash rather than CWM. I have that linked in that partition fix thread.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
thanks a lot!
I did try with the 3.2.0.1 recovery and the flash you posted above. It is still sticking at the 'repartitioning internal memory' step...I also tried your TWRP bootable, but that still sticks at the loading screen.
I can't find my external sd writer, so I've been writing/burning using in internal writer in two different laptops and a camera in mass storage mode. I ordered a SD writer from amazon...should get it on Wednesday. I wonder if my issues are just with writing/burning the SD card..
I'll report back when I get the new writer and guess I might as well try another card too.
ginhead said:
thanks a lot!
I did try with the 3.2.0.1 recovery and the flash you posted above. It is still sticking at the 'repartitioning internal memory' step...I also tried your TWRP bootable, but that still sticks at the loading screen.
I can't find my external sd writer, so I've been writing/burning using in internal writer in two different laptops and a camera in mass storage mode. I ordered a SD writer from amazon...should get it on Wednesday. I wonder if my issues are just with writing/burning the SD card..
I'll report back when I get the new writer and guess I might as well try another card too.
Click to expand...
Click to collapse
It is possible it is the card. It might be good enough to start the boot, but not good enough to read and write the files that are needed. Definitely try a different card.
EDIT: Now that I think about it, I am almost positive that is what is wrong. Try a SanDisk class 4.
Sent from my Nook HD+ running CM10 on Hybrid SD
scthomps, you could get a NC replacement charging cable from ebay, just do a search, it works good for me.
I'm actually running into this problem right now with two different nook color tablets.
One I've had CM10 installed to the EMMC for well over a month without any problems. The other Nook Color I followed the same procedure to install to the EMMC off a bootable SD card.
Regardless of how little or much power the Nook has, it will not even power on unless I have a bootable SD card installed.
Once I get to the menu, I can boot from the internal EMMC without any problems. Not sure what I did to correct the /boot partition on two different Nooks. Least of all one that's been working.
Going to try boot into recovery to see if I can fix whatever corruption got introduced.
phoenix1972 said:
I'm actually running into this problem right now with two different nook color tablets.
One I've had CM10 installed to the EMMC for well over a month without any problems. The other Nook Color I followed the same procedure to install to the EMMC off a bootable SD card.
Regardless of how little or much power the Nook has, it will not even power on unless I have a bootable SD card installed.
Once I get to the menu, I can boot from the internal EMMC without any problems. Not sure what I did to correct the /boot partition on two different Nooks. Least of all one that's been working.
Going to try boot into recovery to see if I can fix whatever corruption got introduced.
Click to expand...
Click to collapse
You need a complete set of boot files on the internal boot partition or it won't even try to turn on by itself without a bootable SD. You don't. It needs MLO, u-boot.bin, uImage and uRamdisk there. You obviously have the MLO or u-boot.bin missing or corrupted because uImage and uRamdisk must be there to boot from the SD menu.
This is all fixable by just flashing your ROM again. Those files all get put back on fresh.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Which recovery are you using to flash the repair zips? It needs to be at least 3.2.0.1. Don't use that 3.0.1.0. Don't worry about those E: messages, it just means cache is not formatted.
It is sounding like the first step of the repartitioning is not taking. That is fixing partition one. I'll be right back with another zip to see if you can flash that.
Try the attached and see what happens. You can also try the bootable TWRP to flash rather than CWM. I have that linked in that partition fix thread.
Removed attachment.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Hi leapinlar I think I have the same problem as this guy except its on a Nook HD +, becuase I get that same error message when I boot into a bootable cwm. Can you help me out please?
Hi all,
I bought my kids nooks for Christmas and rooted them all with cm7. Recently my oldest son decide he wanted to clear his nook and set it back to the factory state... (no idea why) regardless he decided to do it on his own which I only found out about after he had er bricked it. Here's a description of what he says he did.
1-Wiped the SD card
2-Copied the nook software to the sd card
3-rebooted into recovery mod
4-deleted anything he could delete? No idea, this is where I had to laugh
5-rebooted the nook, it didn't... Go figure
I'm not sure what version of recovery he had but it had to be an older version. I tried the various resets but I'm pretty sure the internals been wiped... now I did connect it to a PC and just cycled the power and it will chime recognition for a sec but then its still dead. Is there a way to create a new internal boot loader or is it spare parts?
Thanks either way, love the site
jgolds72 said:
Hi all,
I bought my kids nooks for Christmas and rooted them all with cm7. Recently my oldest son decide he wanted to clear his nook and set it back to the factory state... (no idea why) regardless he decided to do it on his own which I only found out about after he had er bricked it. Here's a description of what he says he did.
1-Wiped the SD card
2-Copied the nook software to the sd card
3-rebooted into recovery mod
4-deleted anything he could delete? No idea, this is where I had to laugh
5-rebooted the nook, it didn't... Go figure
I'm not sure what version of recovery he had but it had to be an older version. I tried the various resets but I'm pretty sure the internals been wiped... now I did connect it to a PC and just cycled the power and it will chime recognition for a sec but then its still dead. Is there a way to create a new internal boot loader or is it spare parts?
Thanks either way, love the site
Click to expand...
Click to collapse
You may want to try to boot ClockWorkMod off an sd card(here is a link to a forum post about it) and if that works then you will want to follow leapinlar's post to repair the partitions here
Your issue is he probably formatted /boot (older versions of CWM allow that). If he did that it will not turn on unless there is a bootable SD in the slot. The solution is to go to my partition repair thread as the last user recommended and follow the instructions there.
Sent from my Nook HD+ running CM10.1 on emmc.