Database Develop

Stumped....Maybe you guys can help. Or maybe not

I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue

oman0123 said:
I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue
Click to expand...
Click to collapse
You probably have the wrong bootloader and kernel...the newest cm7s are based on the 2.6.32, not the older 2.6.29 (or something), and the newest 1.2 bootloader..which you probably don't have if it's "been awhile"..lol...You have to upgrade your Cwm first, from 3.0.1.0 to 3.0.2.8, I think, then flash your Cwm to a nightly after 86??(Google to check), and it will change your boot partition to the correct one...If your nook still says "touch the future", you're on the wrong bootloader.....Also, quit using Phiremod.....it's a copy of Cm7 first of all, but by the time it's released, it's already outdated, it's not updated like it should be, and it's Douchey. Google the basics of what I described above if it sounds like that might be your problem and lmk how it works out for you....Btw....I used nightly 106 for this exact thing on another of my Nooks a few days ago and it worked flawlessly...There are newer nightlies out, but that one for sure worked.....
Sent from my NookColor using Tapatalk

I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?

Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above

DiDGR8 said:
I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?
Click to expand...
Click to collapse
Ive tried all of that. hopefull mazooks way works. Otherwise im out of ideas

oman0123 said:
Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above
Click to expand...
Click to collapse
If I remember correctly, you can't just jump from 3.0.0.6 or 3.0.1.0 to newest...there's one in between that transitions the upgrade in bootloaders...I'm pretty sure I went 3.0.1.0 to 3.0.2.8 to flashing Cm7 nightly 106...then to upgrade to Cwm 3.2.0.1 while in Rom manager, while using Cm7....leSigh....Clockworkmod is the only thing I can't stand about using my Nook....(though I rarely need it any more) AmonRa is such a better (and fully functional) recovery build...One thing I wish we had gotten.....
Sent from my NookColor using Tapatalk

What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?

oman0123 said:
What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?
Click to expand...
Click to collapse
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk

mazook98 said:
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Well Id love to try that but.....My nook wont turn on. It was fully charged today. Im either gonna make a bootable cwm or go back to stock and root again. I dont know if that will work though because its not even powering up.

Ok....i think im making progess....The newest nightly just goes into a bootloop. better than a clockwork bootloop i guess..... any advice on how to get it to install properly? i feel like im making progress. normal bootloops are better than what i was getting

Bueller............Bueller lmao.
Seriously though.....if anybody can figure this out it would make my year

Try this, install stock 1.2....
boot it up, go through the annoying setup, log into google apps, then power down.
Boot into CWR SD, this should have the os that you want already on it, and the google apps file.
THen click install from zip, choose zip, install the OS, after complete install google apps, then restart without sd
Do not format anything, it should do the trick.

Nook HD+ With CM 10.1 Hybrid Install - Reboot Problem

Hi all,
I've got a Nook HD+ running CM10.1 with the hybrid SD card installation (many thanks to everyone who helped develop this - it rocks! ),
and I'm having issues whenever I reboot the device.
When left alone, 9 times out of 10 it will just stay on the Cyanogenmod animation indefinitely (well 10 minutes is the most I've left it)....
It always seems to see the SD card as it never just reboots to stock (always see the Cyanogenmod boot logo) so I can get into CWM or boot the nook to stock.
The only way I seem to be able to get it to boot consistently is to boot into CWM is to re-flash the CM10.1 rom / load the converter zip and the reboot from CWM.
I've installed quick boot into CM10.1 but I've nat managed to get it to install into stock yet as I'm getting the 'Installation Blocked' message - So I'm guessing that I need to sideload that in from my PC (unless I'm missing an obvious way to install this via the stock Nook interface?)
Does everyone else have this issue?
It's not the end of the world as I'll probably only have to boot from cold if I have a crash, but it would be good to know if there are any more graceful solutions out there....?
Also, is there a way to get your PC (windows 7) to read the large partition on the SD card after it has been imaged (so you can write files to it directly)?
Thanks for you help
Macca

When it keeps getting stuck on the boot animation, try going to CWM and the advanced menu and wipe dalvik cache and see if it boots ok. If that does not work, just try flashing the converter without reflashing the CM.
To put quick boot on stock you need to root stock and add at least the extras zip so that unknown sources is authorized. But I recommend the whole gaps + extra zip. Quick boot will not work without root.
And no, there is no way for Windows to see the sdcard partition by directly inserting the card in the PC. You must leave the card in the Nook and use the USB cable.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
When it keeps getting stuck on the boot animation, try going to CWM and the advanced menu and wipe dalvik cache and see if it boots ok. If that does not work, just try flashing the converter without reflashing the CM.
To put quick boot on stock you need to root stock and add at least the extras zip so that unknown sources is authorized. But I recommend the whole gaps + extra zip. Quick boot will not work without root.
And no, there is no way for Windows to see the sdcard partition by directly inserting the card in the PC. You must leave the card in the Nook and use the USB cable.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Thanks for the quick reply mate,
I'll try just clearing the dalvik cache next time.
Thanks for clearing up the quick boot thing - I'll root the stock later tonight.
Cheers
Paul

leapinlar said:
When it keeps getting stuck on the boot animation, try going to CWM and the advanced menu and wipe dalvik cache and see if it boots ok. If that does not work, just try flashing the converter without reflashing the CM.
To put quick boot on stock you need to root stock and add at least the extras zip so that unknown sources is authorized. But I recommend the whole gaps + extra zip. Quick boot will not work without root.
And no, there is no way for Windows to see the sdcard partition by directly inserting the card in the PC. You must leave the card in the Nook and use the USB cable.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Hello again mate,
I might need a little more help it would seem.......
I had read a reply you had posted in another thread that I should be able to just boot into CWM and flash the stock Nook ROM with your zips (even though I already have hybrid CM10.1 installed.
So - I did just that....
Before doing any of this I did do a backup in CWM
I downloaded "NookHD-HDplus-Universal-Root-rev2-(02.02.13).zip" and "NookHD-HDplus-Gapps+Extras.zip" to my internal memory, booted into CWM and Flashed both zip files (universal root rev 2 first).
When I rebooted, I forgot to hold down the nook key to boot to stock and I ended up in CM10.1 but flashing the zips above seemed to have messed around with CM10.1 as I had no apps pinned and the dialogue box asking about which launcher I wanted popped up....?
So I went back into CWM did a restore and re-flashed CM10.1 / Converter.zip's and my CM10.1 installation is now back to normal.
However, it still looks like the stock is rooted as I get the launcher dialogue box and have assess to the google app store etc...
Quick boot still won't work though as it's saying that it can't detect that the device is rooted....
So, If you managed to make it through all that - What did I do wrong and how badly have I messed my nook up?
What do I need to do to successfully root my stock?
Thanks again for your help
Macca

I might have figured it out myself now...
I didn't remove the SD card from the nook after rooting stock before rebooting out of CWM.
I've just re-rooted stock, took the SD card out and then rebooted and it took me into the rooted stock without any issues (quick boot now works as well )
CM10.1 also seems to be happy so it looks like I'm golden (it booted 1st time after quick booting out of stock)
Cheers
Macca

[Q] [Panic] HD+ stuck in bootloop HELP!

So, I just got a HD+ and I was ready to try out CM10.1 emmc.
I got all the required files and such ready.
I booted into CWM sdcard, and I forgot to take a backup, and I flashed TWRP recovery. I rebooted and now when I remove the sd card, it's stuck in a boot loop.
The nook logo comes up, the screen dims after a few seconds, and then it reboots, and repeats forever.
I tried flashing stock recovery from another thread this file : http://forum.xda-developers.com/showpost.php?p=41392480&postcount=4
Still nothing.
I backed everything else up AFTER flashing recovery. So if I can just fix this, I can take a proper backup and proceed with the CM10.1 install.
Thanks

First off, if you are interested in using the emmc recovery for making backups and restores, don't use TWRP. That feature is broken in that version.
If you want to go back to stock first so you can back it up, go to my HD/HD+ CWM thread linked in my signature and get my plain stock 2.1.0 from item 6 and flash that with your bootable CWM SD. That will put everything back to stock, including recovery.
Then just start over again with your bootable CWM card. Backup, then flash the CWM emmc recovery, the CM10.1 zip and gapps, wipe data and reboot.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
First off, if you are interested in using the emmc recovery for making backups and restores, don't use TWRP. That feature is broken in that version.
If you want to go back to stock first so you can back it up, go to my HD/HD+ CWM thread linked in my signature and get my plain stock 2.1.0 from item 6 and flash that with your bootable CWM SD. That will put everything back to stock, including recovery.
Then just start over again with your bootable CWM card. Backup, then flash the CWM emmc recovery, the CM10.1 zip and gapps, wipe data and reboot.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Nevermind, I just tried something and it worked. (Complete accident btw didn't know what I was doing)
I long pressed hom button while it was booting, and the Adobe disclaimer from the bottom dissapeared a blue bar started loading under the Nook logo. It loaded twice and then it booted up
Any idea what just happened?

prabhjan said:
Nevermind, I just tried something and it worked. (Complete accident btw didn't know what I was doing)
I long pressed hom button while it was booting, and the Adobe disclaimer from the bottom dissapeared a blue bar started loading under the Nook logo. It loaded twice and then it booted up
Any idea what just happened?
Click to expand...
Click to collapse
Yes, you booted into stock recovery it repaired itself.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Yes, you booted into stock recovery it repaired itself.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Oh, cool. Well it appears to have been factory reset, and it seems to have gone down to 2.0.0 or something (even though it came with 2.1.0 out of the box). Now it's running 2.0.6. It told me that 2.1.0 is available to update, and I started it. But it doesn't appear to be moving forward. Will come back on the status of that in a bit again.

prabhjan said:
Oh, cool. Well it appears to have been factory reset, and it seems to have gone down to 2.0.0 or something (even though it came with 2.1.0 out of the box). Now it's running 2.0.6. It told me that 2.1.0 is available to update, and I started it. But it doesn't appear to be moving forward. Will come back on the status of that in a bit again.
Click to expand...
Click to collapse
Yes that is how it repairs itself. But it needs the stock recovery to do that. Once you put that back, it took over and proceeded to reset itself.
Just let it do its thing.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Yes that is how it repairs itself. But it needs the stock recovery to do that. Once you put that back, it took over and proceeded to reset itself.
Just let it do its thing.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Sweet. Okay, I'm back to how it was when I first bought it. Going to put CM10.1 now.
Okay, so I need to take a backup first, then flash CWM, CM10.1, and then GApps. That's it right?

prabhjan said:
Sweet. Okay, I'm back to how it was when I first bought it. Going to put CM10.1 now.
Okay, so I need to take a backup first, then flash CWM, CM10.1, and then GApps. That's it right?
Click to expand...
Click to collapse
Yes. Then wipe data/factory reset.
Sent from my Nook HD+ running CM10.1 on emmc.

Okay, btw. I took the backup, and I selected reboot, before I proceeded with the flashing.
It asked me if I should flash stock recovery and if I should enable root access (I selected no for both as selecting yes was the cause of the problem before)

prabhjan said:
Okay, btw. I took the backup, and I selected reboot, before I proceeded with the flashing.
It asked me if I should flash stock recovery and if I should enable root access (I selected no for both as selecting yes was the cause of the problem before)
Click to expand...
Click to collapse
Why did you reboot?
You lost me on that last statement. What asked if you should enable root access? Something in stock?
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Why did you reboot?
You lost me on that last statement. What asked if you should enable root access? Something in stock?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Okay basically. I made two SD cards with CWM. One which I'll leave as a permanent backup card, and another with the other packages (it kept formatting to 856MB after I made it a bootable card no matter how big the actual card is, and so I couldnt fit both the backup and the CM10.1+Gapps zips on a single card)
I first made the backup on one card, and I hit reboot system, to swap it for the other one.
But when I pressed reboot, it asked me this:
ROM may flash stock recovery on boot. Fix?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
-No
-No
-Yes- Disable recovery flash
-No
-No
-No
I hit no.
Then it followed up with this:
Root access is missing. Root Device?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
-No
-No
-Yes - Root device (/system/xbin/su)
-No
-No
-No
I hit no for this too, since it didn't quite make sense.
So yeah. I'm pretty confused. Never ran into anything like that before on other devices.

prabhjan said:
Okay basically. I made two SD cards with CWM. One which I'll leave as a permanent backup card, and another with the other packages (it kept formatting to 856MB after I made it a bootable card no matter how big the actual card is, and so I couldnt fit both the backup and the CM10.1+Gapps zips on a single card)
I first made the backup on one card, and I hit reboot system, to swap it for the other one.
But when I pressed reboot, it asked me this:
ROM may flash stock recovery on boot. Fix?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
-No
-No
-Yes- Disable recovery flash
-No
-No
-No
I hit no.
Then it followed up with this:
Root access is missing. Root Device?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
-No
-No
-Yes - Root device (/system/xbin/su)
-No
-No
-No
I hit no for this too, since it didn't quite make sense.
So yeah. I'm pretty confused. Never ran into anything like that before on other devices.
Click to expand...
Click to collapse
Go to my HD/HD+ CWM thread linked in my signature. See item 1a. There is a new procedure to make a bootable CWM SD on any size card. I suggest you use that. Then you have room for backups and zips. My card works equally well with verygreen's, but is bigger. You may have to use SDFormatter with size adjustment like I say in the thread to get your full size back from the verygreen SD.
Those CWM messages are harmless, just keep saying no. My cards give the first message, but I have never seen the second one before.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Go to my HD/HD+ CWM thread linked in my signature. See item 1a. There is a new procedure to make a bootable CWM SD on any size card. I suggest you use that. Then you have room for backups and zips. My card works equally well with verygreen's, but is bigger. You may have to use SDFormatter with size adjustment like I say in the thread to get your full size back from the verygreen SD.
Those CWM messages are harmless, just keep saying no. My cards give the first message, but I have never seen the second one before.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks, I finished installing CM10.1.
But there seems to be a bit of lag. When I tried it with the SD card boot (not emmc), I assumed that it was slow because of the SD card. But it's the same even on this. Anyway to speed things up?

prabhjan said:
Thanks, I finished installing CM10.1.
But there seems to be a bit of lag. When I tried it with the SD card boot (not emmc), I assumed that it was slow because of the SD card. But it's the same even on this. Anyway to speed things up?
Click to expand...
Click to collapse
You need to ask those kinds of questions on verygreen's thread.
Sent from my Nook HD+ running CM10.1 on emmc.

I'm in recovery bootloop hell!
I just received my Nook HD+ yesterday and immediately tried to root it using the Nook HD+ for dummies thread.
I used NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13) for my bootable SD card.
I added these files cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
cwm-recovery-ovation-2.zip
gapps-jb-20130301-signed.zip
(also used twrp on the first attempt but read about not being fully functional so I stopped using it)
I made a backup of the original ROM which I already registered with B&N.
Booted into CWM recovery and proceeded to wipe data/factory reset, flash cwm-recovery-ovation-2.zip, cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip, and gapps-jb-20130301-signed.zip in that order. Eject sd card and reboot.
Now all I get is four reboots and it goes back to CMW recovery everytime. I can restore back to stock (thankfully) if I want to but I really want to get this working. You think my partition 2 is damaged and needs repair?
Any help will be deeply appreciated!
BR

blackrain74 said:
I just received my Nook HD+ yesterday and immediately tried to root it using the Nook HD+ for dummies thread.
I used NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13) for my bootable SD card.
I added these files cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
cwm-recovery-ovation-2.zip
gapps-jb-20130301-signed.zip
(also used twrp on the first attempt but read about not being fully functional so I stopped using it)
I made a backup of the original ROM which I already registered with B&N.
Booted into CWM recovery and proceeded to wipe data/factory reset, flash cwm-recovery-ovation-2.zip, cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip, and gapps-jb-20130301-signed.zip in that order. Eject sd card and reboot.
Now all I get is four reboots and it goes back to CMW recovery everytime. I can restore back to stock (thankfully) if I want to but I really want to get this working. You think my partition 2 is damaged and needs repair?
Any help will be deeply appreciated!
BR
Click to expand...
Click to collapse
No, the partition 2 repair thing is for the Nook Color. I recommend redownloading the CM10.1 zip and try flashing again.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
No, the partition 2 repair thing is for the Nook Color. I recommend redownloading the CM10.1 zip and try flashing again.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
That did the trick!!! Wow, I even downloaded the file twice and it was corrupt!!! Third time was a charm!!! Development is way ahead on the HD + compared to the Fire 8.9! Thanks for the quick response!

leapinlar said:
If you want to go back to stock first so you can back it up, go to my HD/HD+ CWM thread linked in my signature and get my plain stock 2.1.0 from item 6 and flash that with your bootable CWM SD. That will put everything back to stock, including recovery.
Then just start over again with your bootable CWM card. Backup, then flash the CWM emmc recovery, the CM10.1 zip and gapps, wipe data and reboot.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for putting up this file. Great use in future if something gets bonked.

[Q] Resurrecting my Captivate, ONLY boots to CWM

I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?

jahfry said:
I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?
Click to expand...
Click to collapse
my advice is, go to stock GB, then flash ICS, flash a KitKat kernel, reboot recovery and then flash CM 11..
hope this works for you!

Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.

Stock Rom
jahfry said:
Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.
Click to expand...
Click to collapse
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!

asianlight said:
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!
Click to expand...
Click to collapse
Stickied threads: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Search goes a long way

Help! Stuck in recovery bootloop on HD+

My Nook HD+ keeps rebooting to my EMMC recovery (currently CWM 6.0.4.6) no matter what I try. It all started with a botched CM11 install from a while back. Since then I've tried installing CM11 M8 and CM10 RC2 through both the emmc recovery and the bootable sd card recovery. Even when the install goes smoothly, my Nook will just reboot back into whichever recovery I have installed.
Not sure what the problem is but would really appreciate any help. Thanks!

riceknight said:
My Nook HD+ keeps rebooting to my EMMC recovery (currently CWM 6.0.4.6) no matter what I try. It all started with a botched CM11 install from a while back. Since then I've tried installing CM11 M8 and CM10 RC2 through both the emmc recovery and the bootable sd card recovery. Even when the install goes smoothly, my Nook will just reboot back into whichever recovery I have installed.
Not sure what the problem is but would really appreciate any help. Thanks!
Click to expand...
Click to collapse
You need to go to my HD/HD+ CWM thread linked in my signature and make a new bootable CWM SD per item 1a and use that to flash a plain stock zip from item 6, followed by a system reset with CWM. That should get you going again and you can start over.
Sent from my SM-T900 using XDA Premium HD app

I got the similar problem on my nook hd (version : CM10.1). Someday, it automatically upgraded and i interrupt it, then a tragedy comes. It always get into cyanboot and recovery 6.0.4.6 when i rebooted. And i try flash newer CM, but it always reboot. Then i try many ways during several days.
When i just wanted to give up, the miracle showed. My nook was connected on PC with internet, the screen is stuck on cyanboot as usually. Then new screen pop up to ask me set language.
I quickly flash recovery, CM11 and google market. In this time, recovery 6.0.4.6 was worked but i didn't why and how. BUT when i reboot it, it still went into cyanboot and recovery 6.0.4.6. In recovery menu, i try advanced-->reboot to bootloader. Yes, i got into new CM11 :crying:
Now, although my nook get into recovery 6.0.4.6 when it rebooted, but tap advanced-->reboot to bootloader, which get 100% into CM11.
It really a tough work, and i still don't know how i solve it~~

See this thread http://forum.xda-developers.com/showthread.php?t=1444630 for an explanation of one common (but not the only possible) cause of the "recovery boot loop" problem. Although it was written for the Nook Tablet, the same mechanism also applies to the Nook Color, Nook HD/HD+.
For the Nook Tablet (not HD/HD+), there is a flashable_fix_bootloop.zip created by XDA developer succulent (and posted at his Blog http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/) that can be flashed (using CWM/TWRP) to reset the two files BCB and BootCnt and thereby getting the NT out of the recovery boot loop condition; with a little tweak this tool can be adapted for use with another Nook device type such as HD or HD+.