[Q] After first boot can't boot again - Barnes & Noble Nook Tablet

Hi. I'm running a nook tablet 16gb with latest TWRP recovery and the cyanoboot bootloader (revision nov 23 2012).
I can always reboot the tablet into recovery, fastboot, or just sit on the bootloader screen.
After first installing a rom (either sideload or off sd card) it'll boot into the rom for the first time fine, configure everything, and will work perfectly.
But as soon as I reboot the tablet, the next time the bootloader attempts to load eMMC Normal (the rom) I'll get a black screen with just the backlight on. It will sit on this forever (I've waited about 30 minutes) until the power button is held for about 10 seconds forcing a shutdown.
I have tried booting both with and without an SD card inserted. I've tried installing the rom both with and without an SD card inserted. I've used both CWM recovery and now currently the TWRP recovery. And I've tried a multitude of officially supported CM 10.2 nightlies.

Consider this resolved. I managed to locate a different revision of cyanoboot (even though the original thread no longer contains download links)

Related

NT factory reset screen with SD CWM

Bought 2 16GB Nook tablets last week (one for wife) - used indirects method to boot CWM from SD http://forum.xda-developers.com/showthread.php?t=1466583 however got same error as Land Master and a few others where instead of booting CWM the unit booted a factory reset prompt instead. The suggested workaround is to boot while plugged into a computer however this did not work for me. In the end I did get CWM to boot and installed CM7 which is going great on both tablets (I'm in the UK so could not register or use the stock OS).
The workaround for me was, from a failed CWM boot that has gone through a factory reset screen (which is declined) to boot the stock OS,
1 eject SD properly, plug into Mains and reboot then turn off normally (i.e the nook has now been turned off from stock OS without booting from the CWM SD first)
2 re make the SD ( it seems booting into the stock OS with it inserted changed it in some way, no idea how)
3 turn on nook holding n and power button until nook turns - this is standard step
4 insert SD and turn on while still plugged into Mains (nook should have been plugged into Mains from step one)
This worked on both nooks, 1.4.1 out of box with oobe skipped, I swapped the SD after CWM booted for one with CM7, updated from this, wiped data rebooted and have not looked back since.

After installing CM 10.1, Screen Issues

After flashing the latest version of CM 10.1 for the Atrix 4G, the bootloader comes up, and then the screen goes blank while trying to boot into the first instance of CM. Pull the battery, and it does the same thing. I am able to boot into recovery. Have tried reflashing from the same package, reintalling + factory reset, reinstalling + factory reset + no gapps, and same thing.
What's the problem? Moreover, how do I get stuff onto the internal SD card if I cannot boot into the OS?
I should also mention that the touch sensitive buttons light up and respond to touch via vibration after a point upon booting up, which tells me that it's booting to the OS, but the screen is remaining blank for some reason. Could be a kernel problem?
In any case, I'm going to have to push a new ROM onto the device and I have no idea how to do that in it's present state.
EDIT: Solved the above problem, ADB pushed an older version of CM 10.1 and I have the screen working again! Please close this topic.

Unbrick without SD Card Boot?

So I have one of those super special 16GB Nook Tablets that refuses to boot to an SD card no matter what you do (see http://forum.xda-developers.com/showthread.php?t=1515761). Since I couldn't use the method of flashing recovery I used on my other two NTs (booting to SD recovery and flashing) I tried using Indirect's recovery flasher (http://forum.xda-developers.com/showthread.php?t=1458630) flashed it, and hit the reboot to recovery button. Now after the initial normal Nook logo on boot a larger one appears and then the screen goes black, I've let it sit for a good 30 minutes and nothing comes up after that (in fact the tablet seems to turn off after a while). I have no access to ADB or fastboot at that point either. Does anyone have any ideas how I can fix this or am I screwed?
Erf, and I made this in the wrong forum... could a mod please move me to the Q&A\Help section?
FergyA said:
So I have one of those super special 16GB Nook Tablets that refuses to boot to an SD card no matter what you do (see http://forum.xda-developers.com/showthread.php?t=1515761). Since I couldn't use the method of flashing recovery I used on my other two NTs (booting to SD recovery and flashing) I tried using Indirect's recovery flasher (http://forum.xda-developers.com/showthread.php?t=1458630) flashed it, and hit the reboot to recovery button. Now after the initial normal Nook logo on boot a larger one appears and then the screen goes black, I've let it sit for a good 30 minutes and nothing comes up after that (in fact the tablet seems to turn off after a while). I have no access to ADB or fastboot at that point either. Does anyone have any ideas how I can fix this or am I screwed?
Erf, and I made this in the wrong forum... could a mod please move me to the Q&A\Help section?
Click to expand...
Click to collapse
Apparently this tablet is just super super picky about booting to SD cards... Was able to boot and restore to 1.4.2 using repart.img (mind you it took 5 attempts on 5 different SD cards to do so).

Nook tablet restarts again & again

I wanted to try TWRP recovery. I installed rashr app and installed TWRP latest on sd card then rebooted the tablet. It showed me N logo for a few seconds then turned off itself.
Now whenever i turn it on, it shows that N logo for like 5 seconds and turns off. When connected with USB, it keeps restarting. I tried removing the sd card, but no change at all.
Please tell me how to fix this.
Update
i got into clockworkmod 5.0.x recovery (made a bootable sd card) and installed old CM10. But still it keeps flashing only the Nook N logo & restarting forever. I guess my tablet is badly bricked. Is there any other way to fix this?
You need a version of CWM between 6.0.1.x through 6.0.3.x to flash CM10. See http://forum.xda-developers.com/showthread.php?p=51377882#post51377882 for additional info/pointers on how to install CM10.x on emmc.

New Post ... Old Nook HD+ Boot Problem

My Nook HD+ bootloader won’t launch the installed OS, CM 13. The Nook screen appears, and then gives way to the Cyanogenmod Universal Bootloader. After a bit the blue android image appears. It pulses normally at first, then the pulsing pauses, and finally the process starts all over … and over, and over, and over!
At first I thought there was a problem with the OS, so I booted into recovery (TWRP 3.1.1-0) and tried to flash CM 13 for ovation. That didn’t work, so I tried flashing other ovation ROMs. None will install. They all report an ERROR 7. I’ve attempted to work around that error, but none of the methods I’ve found made any difference.
It seems that I may have to reinstall the factory/stock ROM, and I’m okay with that. But it seems I can’t do that either. The stock rom download is in a CWM backup format, and I have TWRP, not CWM. So I tried to flash CWM with TWRP, but in order to make that work one has to reboot into recovery via TWRP, The problem here is that the TWRP boot menu has just two options … System and Power Off. The Recovery option that is supposed to be there isn’t!
So I tried to replace TWRP with CWM via ADB. I can sideload a CWM zip without a problem. I then issue an ADB Reboot Recovery command. But, instead of rebooting into recovery, the bootloader launches instead. As a result, when I go into recovery it’s still TWRP. I’ve also tried powering on with the CWM bootable image file on an sd card, but no matter how many times I power off and back on, my tablet never recognizes that the file is there and my problem persists.
Is there a way to boot into CWM or swap CWM for TWRP in a situation like this? I’ve seen postings that suggest fastboot may the be solution, but that requires that debugging be enabled, and it was not enabled when my problems began. Apparently there is no way to enable debugging without launching the OS.
Help!
Update:
My Nook HD+ has not rewarded my attempts to bring it back to life Perhaps I’ve made things worse. I certainly haven’t made things better. Here’s the latest.
When booted up, little or nothing has changed. At bootup the Nook screen is followed by the Cyanoboot Universal Bootloader screen. Sometimes it gets no further, and reboots. More often the android image appears with a halo pulsing in the background. Sometimes the halo pulses a couple of times before the device reboots. Sometimes is pulses a bit longer before rebooting. Sometimes it never stops pulsing (until I press and hold the power button to shut the bloody thing down, that is).
Thinking the problem was related to the OS (I had been running android 7.1.1 (an unofficial HD+ release, but from a very reliable source), I've tried in vain to flash another OS. I've tried multiple android releases, from 7.1.1 down to 4.4.4. I've also tried flashing several versions of the HD+ factory stock OS. I’ve done all this using TWRP, and also by booting CWM from an sd card. No matter which recovery I've used or which OS I've attempted to install, the process always ended with an ERROR: 7.
So, I got my hands on a good Nook HD+ running android 5.1.1. I made unbundled TWRP backups of the System, Boot, and Apps partitions using release 3.1.1-0. The System and Boot partitions each restored without a problem. The Apps would not restore, ending with “extractTarFork() process ended in ERROR: 255." That error probably isn’t related to my problem, which is that I can’t get the system to boot up. More telling is the fact that after successfully restoring the System and Boot partitions using the backup from a good HD+, when I power up the device appears to be launching 7.1.1, not 5.1.1. The android image displays in portrait mode on the good HD+ running 5.1.1, but displays in landscape mode on my HD+ ... and the boot loop continues, of course.
At this point, at the $7.25/hour minimum wage rate I’ve spent enough time that I could have earned many times the original cost of the HD+. So, am I giving up? HELL NO! Now it’s personal!!
My HD+ boots into TWRP flawlessly, so I still have that going for me. My HD+ is not rooted and did not have USB Debugging enabled when it crashed, so any solution requiring SU or flashboot is a non-starter. Otherwise, I’m willing to give anything a try. Maybe I should be looking for an exorcist?
Thanks for reading this, and for your suggestions, words of encouragement, and expressions of sympathy.

Categories

Resources