[Help needed!] Nook HD+ CM11 M12 cyanogen boot loop

[jonas_r]

Hi,

If anyone could help i'd be really grateful!

I've got a Nook HD+ which was happily running CM11 M12 installed on emmc, had been running fine for about 5 months. I let the battery completely die by accident, although this has happened on a number of occasions before and not been a problem.

Now when turned on it just went to the nook logo boot screen and no further. couldn't access recovery with power+n.
So i figured the emmc might have gotten corrupted somehow. So i made a new boot sd card as shown in leapinlar's sig - aiming to try and get it into recovery - put stock software on, then replace with CM11 again.

Here's the problem - have got the nook to boot to the Cyanoboot logo - but it will go no further - it never loads the recovery menu.

Any ideas?!

 

[Sinner75]

Hi,

If anyone could help i'd be really grateful!

I've got a Nook HD+ which was happily running CM11 M12 installed on emmc, had been running fine for about 5 months. I let the battery completely die by accident, although this has happened on a number of occasions before and not been a problem.

Now when turned on it just went to the nook logo boot screen and no further. couldn't access recovery with power+n.
So i figured the emmc might have gotten corrupted somehow. So i made a new boot sd card as shown in leapinlar's sig - aiming to try and get it into recovery - put stock software on, then replace with CM11 again.

Here's the problem - have got the nook to boot to the Cyanoboot logo - but it will go no further - it never loads the recovery menu.

Any ideas?!

Hi Jonas.

did you solve the problem and if how?

Cheers

Andreas

 

[jonas_r]

nope

Unfortunately not. I couldn't get it to go any further. Have you had any luck?

I ended up buying another nook (surprisingly cheap on ebay!) and using that instead. Would be keen to get that old tablet working though so i can give it to the other half, who's using a Kindle Fire HD which is also playing up!

Hi Jonas.

did you solve the problem and if how?

Cheers

Andreas

 

[rpadula]

i'm also having this issue. bootlooped during cm logo and now only boots to recovery, even after flashing a new rom.

 

[digixmax]

i'm also having this issue. bootlooped during cm logo and now only boots to recovery, even after flashing a new rom.

See http://forum.xda-developers.com/showpost.php?p=55582281&postcount=1459 for a potential cause/solution.

 

[rpadula]

@digixmax i've eventually solved it by flashing the stock recovery and then it proceeded to reinstall nook's stock rom.
do you believe that /bootdata was fixed by the stock recovery/rom?
that flashable fix is universal for HD/HD+?

 

[leapinlar]

@digixmax i've eventually solved it by flashing the stock recovery and then it proceeded to reinstall nook's stock rom.
do you believe that /bootdata was fixed by the stock recovery/rom?
that flashable fix is universal for HD/HD+?

Yes. I recommend that as a first step for those people with recovery bootloops.

Sent from my SM-T707V using XDA Premium HD app

 

[digixmax]

@digixmax i've eventually solved it by flashing the stock recovery and then it proceeded to reinstall nook's stock rom.
do you believe that /bootdata was fixed by the stock recovery/rom?

The stock ROM package which you reinstalled includes the BCB and BootCnt files (you can find them in the \system\bootdata\ folder of the romrestore.zip file inside the ROM package) so your /bootdata content is in effect fixed.

that flashable fix is universal for HD/HD+?

The BCB and BootCnt files are identical for the HD+ and for the HD (as well as the NT) but their installation scripts contain device-specific checks, so I created 2 separate flashable zip files for them -- respectively flashable_fix_bootdata-ovation.zip and flashable_fix_bootdata-hummingbird.zip (both of which can be downloaded from here).

I'd suggest you try this /bootdata fix method first if you ever again run into the "boot loop to recovery" problem and rather prefer to avoid if possible the hassle of having to start all over with installing stock recover & stock ROM.

 

[rpadula]

The stock ROM package which you reinstalled includes the BCB and BootCnt files (you can find them in the \system\bootdata\ folder of the romrestore.zip file inside the ROM package) so your /bootdata content is in effect fixed.

The BCB and BootCnt files are identical for the HD+ and for the HD (as well as the NT) but their installation scripts contain device-specific checks, so I created 2 separate flashable zip files for them -- respectively flashable_fix_bootdata-ovation.zip and flashable_fix_bootdata-hummingbird.zip (both of which can be downloaded from here).

I'd suggest you try this /bootdata fix method first if you ever again run into the "boot loop to recovery" problem and rather prefer to avoid if possible the hassle of having to start all over with installing stock recover & stock ROM.

ah, surely.
if i had know of the bootdata fix before i wouldn't took the stock rom route, but i was in hurry.
do you have any ideia why the cm roms bootloop after a while? they work fine for a time then one day it crashes during boot, sometimes i even see the unlock screen but usually it just crashes at the bootlogo.

also, your mediafire link goes straight to start screen...

 

[digixmax]

...
do you have any ideia why the cm roms bootloop after a while? they work fine for a time then one day it crashes during boot, sometimes i even see the unlock screen but usually it just crashes at the bootlogo.
...

It's most likely due to some incompatible system/app's settings or possibly incompatible apps

I'd suggest that you start with a clean install, re-install previous apps gradually, and don't restore any app data/settings from backup.

also, your mediafire link goes straight to start screen...

I can click through the link just fine, but I am attaching the two flashable zip files below.