My NC wont boot no matter what I do. When I connect it to my pc (windows xp) I get an RNDIS ethernet gadget in the new hardware notifications. The nook was rooted but I did a hard reboot before finishing the setup because it wouldn't connect to my google account. The NC wont even show the "touch the future of reading screen" and I cant get adb to find the device. I rooted when I had freshly wiped everything and downgraded to 1.0.0 then I upgraded to 1.0.1 then I rooted. It worked fine until after the hard reset.
HELP!!!!
FIX!
I'm sorry for the double post, but I want to make this clearly visible when someone else has this problem.
So, all you have to do to get it to boot is try to put the device into recovery mode. It won't actually go into recovery mode though, it will just boot into the regular os.
Clockwork Mod Recovery
I can't go into recovery. I have Clockworkmod installed.
bumpity bump,
Im back to this issue seems my fix up there wasn't right. I did a FULL wipe on the nook (/system, /data) and then proceeded to update and root. after rooting I rebooted the nook with the autonooter sd card still inserted and then the device wouldnt boot. I tried removing the sd card and still no luck. adb doesn't find it but it is detected as a "RNDIS/Ethernet Gadget" under windows. Is there a way for me to boot the nook?\
EDIT:
got it to boot by mashing the power button and putting nookie froyo inside :/ im not sure why but thats probably how I got it last time too.
Clockwork...did the same thing
pndo1 said:
I can't go into recovery. I have Clockworkmod installed.
Click to expand...
Click to collapse
Folks,
I've done the same thing. I backed up with Clockwork to the SD. The Nook would only boot into Clockwork. So, I recovered and now the device will not power up at all. I fear that I have bricked a wonderful device that I spent alot of time on. It will not boot at all, will not respond to the power button at all and I don't know what to do. Does anyone have any suggestions or am I screwed?
FG.
I have the same problem with Motitas and it was updated to 1.1 recently. Please help.
the screen stops to nook icon only. does it mean i have a brick now ? PLEASE Help.
Please read my threa a few threads down from this one, titled "dummies guide to my nook wont boot." it explains everything.
Ok guys heres the deal, i have been trying to reflash NC stock and to no avail i get the same issue everytime no matter what version i use, i have even tried ADB, and that does not work.
Ok my problem is this everytime i try to boot it it just loops at the barnes and noble nook color screen forever. When i tried ADB my computer would not even find the device but it found 2 which when i tried to uninstall them they install right after so i cannot use ADB(and yes i turned off automatic driver install). So here is where i land and my question. Do i have a 300 dollar paper weight or is their hope, and if so please explain what i am doing wrong. Thank you for your time
First off...
are you trying to flash the stock B&N?
how are you trying to flash it?
do you have CWM or TWRP on eMMC or stock recovery?
if you're trying to use cwm or twrp to flash stock rom... see the customizing rom thread in my signature for modifications required.
ok i am trying to flash to the stock bn, i am using cwm, but when i do that it just loops through, and adb now does not even recognize the device so i can tie them together so to speak.
Ok, i did everything that forum on your sig told me to do got it installed but it still loops at the "barnes and noble Nook Color" flash screen. Any Ideas?
Now that you have stock on the nook color... do the 8 failed boots to cause it to erase data and deregister the device... it should bring it back to factory and resolve the boot loop issue
Finally! thank you so much for your help been working on this issue for 3 or 4 months now, it works just need to get it charged and hopefully it will take a charge.
leapinlar: Ask the question on the forum. I don't like using PMs.
Recently the update allowing google play store somehow bypassed the anti-update thing on my nook, so now I can use play store on the nook home, but the update removed my root but kept the android system home.. It uses a lot of ram, which i'd rather have free to play games or other resource heavy apps on.
I know I have to get my nook to start unsuccessfully 8 times, but I don't know how I go about doing that, can I get some help?
flipperz said:
leapinlar: Ask the question on the forum. I don't like using PMs.
Recently the update allowing google play store somehow bypassed the anti-update thing on my nook, so now I can use play store on the nook home, but the update removed my root but kept the android system home.. It uses a lot of ram, which i'd rather have free to play games or other resource heavy apps on.
I know I have to get my nook to start unsuccessfully 8 times, but I don't know how I go about doing that, can I get some help?
Click to expand...
Click to collapse
If you want to do it the easy way, just interrupt the boot by turning it completely off (hold power button for a few seconds) while booting eight times in a row. It will take you back to some version of stock, usually 2.0.0 or 2.0.4 then upgrade again to 2.1.0 when you register again.
Sent from my Nook HD+ running CM10.1 on emmc.
Another way
leapinlar said:
... just interrupt the boot by turning it completely off (hold power button for a few seconds) while booting eight times in a row. It will take you back to some version of stock, ...
Click to expand...
Click to collapse
After my HD+ locked up when I created a "Guest" ("child") profile and I had to do the 8-reboot process, after upgrading to B&N v2.1.0, I experimented with alternate button combinations at power-on. If I held the "n" button when pressing "power", I got a prompt that allowed me to do a factory reset.
Whether that is part of a later B&N recovery module, I can't say.
DeanGibson said:
After my HD+ locked up when I created a "Guest" ("child") profile and I had to do the 8-reboot process, after upgrading to B&N v2.1.0, I experimented with alternate button combinations at power-on. If I held the "n" button when pressing "power", I got a prompt that allowed me to do a factory reset.
Whether that is part of a later B&N recovery module, I can't say.
Click to expand...
Click to collapse
That factory reset just wipes data, it does not reinstall the ROM. He probably needs to reinstall the ROM since some of the broken symlinks may still be in /system.
Power + n takes you to stock recovery, which, without other parameters being passed to it, asks if you want to factory reset.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
That factory reset just wipes data, it does not reinstall the ROM. He probably needs to reinstall the ROM since some of the broken symlinks may still be in /system.
Power + n takes you to stock recovery, which, without other parameters being passed to it, asks if you want to factory reset.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the help!
I'd like to return my Nook HD+ to stock, too. It has a Cyanogen mod that precedes that startup, and I think that's getting in the way of the 'eight reset' mechanism for a total factory reset to stock software.
Is there a bootloader, system, and gapps zip that I could just flash from an external SD card that would do the job? Seems like there was, at one time, but it's getting very difficult to find them. Any ideas for a quick factory reset (not a wipe, but a complete reset to original OS?).
[email protected] said:
I'd like to return my Nook HD+ to stock, too. It has a Cyanogen mod that precedes that startup, and I think that's getting in the way of the 'eight reset' mechanism for a total factory reset to stock software.
Is there a bootloader, system, and gapps zip that I could just flash from an external SD card that would do the job? Seems like there was, at one time, but it's getting very difficult to find them. Any ideas for a quick factory reset (not a wipe, but a complete reset to original OS?).
Click to expand...
Click to collapse
Go to my HD/HD+ CWM thread linked in my signature and flash the plain stock zip from item 6 there and follow that with a factory reset by CWM.
And it was not the cyanoboot that prevents the 8 reset, it is because when you originally installed CM you also replaced the stock recovery on internal memory with CWM. Stock recovery is needed for the 8 reset to work.
Sent from my BN NookHD+ using XDA Premium HD app
Thanks, that worked. I also tried the rooted version of stock, but it has a problem: "Unfortunately, Home has Stopped". Is there a workaround to this?
[email protected] said:
Thanks, that worked. I also tried the rooted version of stock, but it has a problem: "Unfortunately, Home has Stopped". Is there a workaround to this?
Click to expand...
Click to collapse
Don't use that version, I should remove it. If you want to root, do it per the thread with universal root rev 3.
Sent from my SCH-i705 using XDA Premium HD app
Hi there,
I have a device that is also candidate for unrooting to stock. The thing is that I have tried both CWM and TWRP on bootable SD to try and fix the situation tith the apropriate zips but unfortunately none of them can mount sd ot any internal memory for me to reset.
Maybe I should also add that the device is charging without turning on except if there is a proper bootable sd inserted.
I presume a rescue bootable SD of OEM type could bring the device back to life.
I`ll apreciate any help.
ValentinD said:
Hi there,
I have a device that is also candidate for unrooting to stock. The thing is that I have tried both CWM and TWRP on bootable SD to try and fix the situation tith the apropriate zips but unfortunately none of them can mount sd ot any internal memory for me to reset.
Maybe I should also add that the device is charging without turning on except if there is a proper bootable sd inserted.
I presume a rescue bootable SD of OEM type could bring the device back to life.
I`ll apreciate any help.
Click to expand...
Click to collapse
When you say a candidate for stock, why? Is there something else wrong with it? I am just trying to see if it is bricked.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
When you say a candidate for stock, why? Is there something else wrong with it? I am just trying to see if it is bricked.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Maybe Bricked is the situation. The device is charging (the green light is present when plugged to the charger or USB ) but the power button can no longer start any visible boot process on the screen.
The story of the device is nearly the following:
I was using the device for a long time rooted with installed CM updating even with over night builds from time to time.
Once I had a problem booting properly after update but easily booted to TWRP and restored the previouse update.
A week ago the same situation occured, after an update procedure I left the device plugged to the wall charger and on the morning it was stuck on the CYANOGEN universal boot logo. No way found to boot to recovery found.
I figured the recovery has gone bad. Started to prepare bootable SD to try and fox the mess somehow, but could not do the corect procedure of preparing a good bootable SD many times. The only time I successfuly booted CWM recovery from SD I tried to install a zip with CWM recovery and as far as I remember at that time the bootable recovery was able to mount another SD wile it was booted on the device and the zip installed with success according to the software. Sadly after a restart the device was as is, stuck on the bootloader logo.
After 2-3 times successfuly booting both CWM and TWRP recoveries from prepared SD card, doing nothing at all that can alter the device, just tried to see how to mount any usable memory, the device stopped visualy booting without an SD.
Thank you for the reply, hope you can add some wisdome to the happy end
ValentinD said:
Maybe Bricked is the situation. The device is charging (the green light is present when plugged to the charger or USB ) but the power button can no longer start any visible boot process on the screen.
The story of the device is nearly the following:
I was using the device for a long time rooted with installed CM updating even with over night builds from time to time.
Once I had a problem booting properly after update but easily booted to TWRP and restored the previouse update.
A week ago the same situation occured, after an update procedure I left the device plugged to the wall charger and on the morning it was stuck on the CYANOGEN universal boot logo. No way found to boot to recovery found.
I figured the recovery has gone bad. Started to prepare bootable SD to try and fox the mess somehow, but could not do the corect procedure of preparing a good bootable SD many times. The only time I successfuly booted CWM recovery from SD I tried to install a zip with CWM recovery and as far as I remember at that time the bootable recovery was able to mount another SD wile it was booted on the device and the zip installed with success according to the software. Sadly after a restart the device was as is, stuck on the bootloader logo.
After 2-3 times successfully booting both CWM and TWRP recoveries from prepared SD card, doing nothing at all that can alter the device, just tried to see how to mount any usable memory, the device stopped visualy booting without an SD.
Thank you for the reply, hope you can add some wisdom to the happy end
Click to expand...
Click to collapse
It sounds like it is bricked. If recovery said it installed successfully and it still will not boot normally, it is usually what that means. By bricking, I mean internal memory has become read only and nothing can successfully be written to it even if it said it was successful. Your probable only option is to use a noemmc version of SD CM. Search the dev forum for that term.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
It sounds like it is bricked. If recovery said it installed successfully and it still will not boot normally, it is usually what that means. By bricking, I mean internal memory has become read only and nothing can successfully be written to it even if it said it was successful. Your probable only option is to use a noemmc version of SD CM. Search the dev forum for that term.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Apart from the the. Is that a BN at a point of too much geting on or it has to deal with the overal life of surge protection meh a chip?
ValentinD said:
Apart from the the. Is that a BN at a point of too much geting on or it has to deal with the overal life of surge protection meh a chip?
Click to expand...
Click to collapse
No, it is probably from running CM11. That has a history of bricking devices with the faulty emmc chip due to applying trim automatically.
Sent from my BN NookHD+ using XDA Premium HD app
Hello. As per instructed, I have search the threads, but haven't found anything like the problem I'm facing. Most can get to recovery or hand on the cyanogen loading. As such I am posting this query to see if anyone can help me.
I have been using Cyanogen 10.1 emmc on my new B&N HD+ tablet for about a week now, installed by following the guide found here. I made sure to make back up at every step; before flashing Cyrogen, and after. Anyways Yesterday, the tablet refuses to boot. I can press the power button, the Nook hd+ and connect it using usb, but the screen remains blank (black). It never gets to the nook screen or the cyanogen loading screen. I have tried to restore a backup, but no matter what I do, I can't get the nook to boot into recovery mode. I have tried 3 different boot sd, but none bring up the loader, not even the one that work when I first installed Cyanogen.
I have drained the battery completely and recharge it about 2 times now and I have held down the N + Power methods. I installed TWRP as a replacement over stock recovery mode. Any help would be appreciated.
23Exploreus23 said:
I installed TWRP as a replacement over stock recovery mode. Any help would be appreciated.
Click to expand...
Click to collapse
Kind of out of my league, but search this thread - http://forum.xda-developers.com/showthread.php?t=2317500 for twrp. Reports of problems with backup/restore using twrp. Maybe try a bootable cwm card
Updated my CM10.2 mod to the snapshot daily last night, resulted in a massive boot loop. Couldn't get it to stop, restore didn;t work for some reason. So I tried to take it back to CM10.2 using a bootable sd card, it was updating then rebooted...and all I get now is a non working nook hd+. I can't get it to even power up connected to my PC. I did the power/home key combo and no results. I'm crushed. I don't know how to fix it. I have a $200 paperweight atm. :crying:
Please help!! Heck I'd be happy to get back to stock at this time, even though I can't stand it.
basilia said:
Updated my CM10.2 mod to the snapshot daily last night, resulted in a massive boot loop. Couldn't get it to stop, restore didn;t work for some reason. So I tried to take it back to CM10.2 using a bootable sd card, it was updating then rebooted...and all I get now is a non working nook hd+. I can't get it to even power up connected to my PC. I did the power/home key combo and no results. I'm crushed. I don't know how to fix it. I have a $200 paperweight atm. :crying:
Please help!! Heck I'd be happy to get back to stock at this time, even though I can't stand it.
Click to expand...
Click to collapse
You said you got it to boot to a bootable CWM SD. If you can still do that, go to my HD/HD+ CWM thread and flash a plain stock zip from item 6 there followed by a factory reset with CWM.
Sent from my BN NookHD+ using XDA Premium HD app
Any results?
Hey Basilla as someone trying to balance whether to root/install cyanogen, did you have positive results restoring to stock? Hope you did. Cheers.
It was quite easy AFTER if got the darn thing to boot into recovery mode. First I got it into recovery & immediately
installed the last stable version of CM. Then I rolled the stock ROM. After I registered my device etc again in went ahead & rooted it and put the stable CM 10 back on my device. East peasy, took about 15 minutes total after it booted to recovery mode. Will not update again until another stable version is released.
Basila
Thanks
Hey Basilla, thanks for the info on your success. Have a great day and I'm glad you got it working!