Related
Hey Guys
My Nexus one hangs at the startup screen and I can't seem to get it to start. So far, I have tried going into the quick boot screen and clearing the factory settings (i.e hard reset) but it did not change anything. I am bit out of ideas.
Did you do a nandroid, if so revert back to it and proceed forward from there.
sorry, I didn't do an nandroid. Can I do that now?
alright, I installed a recovery image and can enter the menu listed here.
Cyanogen's recovery source based on Amon_RA's post.
I restore the setting just fine but then when I reboot the phone still hangs. Is there another step I am missing? Is just having the recovery tool not enough? How do I restore the original settings?
same problem here did you manage to fix it ?
Same problem here. I have tried everything but I cant make it past the " X " - looking splash screen. If its of any help, the splash screen is STATIC.
Thanks in advance.
it almost sounds like either a bad flash or a bad wipe, if you made a nandroid, try resotring it. If you have not rooted or loaded any roms then the problem may be hardware side.
think the mobo is acting funny, i sent mines in for repair due to t his issue, but unlocked bootloader makes me pay $194..... im trying to figure it out before i pay as a last resort!
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 dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Don't get too upset. You can still boot from SD. At worst, you may have to (re)install some firmware. If you want the B&N firmware, you can reinstall B&N 1.3 and update, or stay at 1.3 if you prefer.
It's hard to totally brick a NC.
Take a look at the restoring to stock section of the guide in my sig
Sent from space
Listen to the two people above this post. They are right. It is nearly impossible to completely brick it. Trust me I've tried.:what:
Seems no matter what I do to it, short of kick boxing it, I've always been able to start from a brand new running nook. Just by reading many posts and the great help from everyone on this forum, who have usually, "been there, done that.", folks.
I'm sure this will work out and everything will be fine, but then you'll be able to help someone else too.
Sent from my GT-P7510 using Tapatalk
i just use this command "fdisk /dev/block/mmcblk0 -l"
i think it was to see the partitions and they dissapeared just chek the image ;(
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
bobtidey said:
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
Click to expand...
Click to collapse
Nope... you can see he's looking at /dev/block/mmcblk0... that is internal.
Need to find the thread about the nook color partitions and create partitions 5-8 then dd the images to them.
i already fixed ! its working again
i can´t believe,
i was thinking about doing a tutorial in how to soft unbrick your nook, i´m not an expert but is a lot of people with the same problem as mine
basically when i enter in recovery receive errors in logs and he dont let me mount or format any of mine partitions(except boot and sdcard), a lot of people are having the same issues and i was thinking about doing a tutorial in how to do it.
should i do it??
thanks everybody
More tutorials are always good. One thing to remember though, is that if someone is looking for a tutorial that means they are usually starting with a small knowledge base. You not only need to be clear, you need to be right.
All I am saying is an underinformed/incorrect tutorial is worse than no tutorial at all. The information is out there, but can be hard to find. If you know your stuff, and have a place to present it where it doesn't already exist, then sure, people will benifit from your knowledge.
Just a guess, but problems mounting within CWM tend to come from old and/or incompatible versions of Clockwork. Is that where you had your problem? I definitely wished that had been stressed on the tutorial I first followed. Would have saved me untold hours of pointless reflashing.
you are right but in my case and i think that is the same of a lot of people (who follow this tutorial http://www.youtube.com/watch?v=szlGSBtWbKY) i tried about 7 to eight diferent versions of clockworkmod and including change of sdcard, i also tried DD the images of the boot and system, when nothing of this works we start get in panic, with no necessity because its only a partition problem, i fixed my 4 partition and he started working
Yeah, I can see where you are coming from. I followed an older tutorial as well, and never saw anything to indicate the link to the CWM image might be outdated.
For sure, that info should be wider spread.
Good luck on your video (?)
hackerse7en said:
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Click to expand...
Click to collapse
I am not sure where to ask for help. I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install, I power off forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. Am I bricked my nook?? please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stacked at the cw recovery screen. Help...
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.
OK, so I wasn´t paying much attention and instead of formatting the system, I formatted the boot of my Nook. After that my Nook wouldn´t boot into EMMC CM7 nor EMMC CWM.
After creating a bootable sd-card I manage to get the EMMC CWM going but, no matter what ROM I tried, or what I wiped, I can´t boot on CM7.
I tried reading every guide and post that would suggest a solution to my Nook but every time i try to download something that is supposed to work I get a broken link. I even try to go back to stock but I cant find a working link for that either.
Anyway, I dont want to go back to stock. I want to get the CM7 going again.
Can anyone help me here?
I got it working again!!!
So, in a overtime hail mary moment, i got it working again. Thank you, xawen!!
Here is how I did it:
I downloaded the "RecoveryFix_3.0.2.8.zip" file from xawen´s post (http://forum.xda-developers.com/showthread.php?t=958748) and install it with the bootable sd-card CWM I had created.
After that, I removed the sd-card and reboot.
This time the Nook showed the "Touch the future of reading" screen (not the Cyanogen screen) and entered into EMMC CWM. I install the "update-cm-7.2.0-RC1-encore-signed.zip" file and reboot. I didn´t wipe anything this time (because I had wiped everything over and over again so I bother).
After the cyanogen screen everything went black and I waited. It took a while, but then, all of a sudden, that little blue fellow showed up. It had never made me happier!
I hope this can help someone else.