[Q] NC: Newbie Information Overload - Needs Direction - Nook Color Q&A, Help & Troubleshooting

Hello,
I used to have a NC successfully running CM7 until it crashed a few weeks ago.
After the crash, in my enthusiasm to fix it, I MUCKED IT UP royally. It tried to boot showing the CWM logo for a moment, then went to black screen.
I tried following the forums to fix the issue, but I only made it worse. Long story short, I may have deleted all my partitions, including partition 3; but, with Leapinlar's help (thanks so much to you for your patience) I was able to flash partitions 1,4,5,6,7,8. Then partition2 with a specially written zip file (again, thanks Leapinlar). At this point, my NC boots directly to CWM 5.5.0.4 on the emmc.
I am ready to try and rebuild, but I am on information overload. I want to know:
1. Which set of files (boot, cwm, cm10 and gapps) works together for a relatively seamless install?
2. Can these files be loaded on a blank NC. Meaning, do I need to get it back up to factory settings before I can modify it again?
3. Should I donate it to one of you to use as a tester and just buy a Google 10 or ASUS Infinity?
I plan on deleting all files except the latest ones I got from Leapinlar's post. I am not asking to reinvent the wheel at this post, just that I be directed to where the best option rests.
Thanks for you help,
Gilligan's sister - Ms. Y

OK, I recommend the 04/21 version of CM10 which you can get here. And for gapps, you need the 20121011 version here. And for emmc CWM, I recommend the 5.5.0.4 version you can get here. Just flash all of these with the 5.5.0.4 you currently have on emmc. Do all three before you reboot. No need to do any wiping or anything else. Hopefully our partition repairs did everything right and it boots to the new CM10.
As far as getting another device, I would wait until you see how you like this repaired one. If it does not work or you are not happy with it, then consider another device. As far as another device, I like the new Nook HD+, but I don't know how it compares with the others you mentioned.

Flash Order
leapinlar said:
OK, I recommend the 04/21 version of CM10 which you can get here. And for gapps, you need the 20121011 version here. And for emmc CWM, I recommend the 5.5.0.4 version you can get here. Just flash all of these with the 5.5.0.4 you currently have on emmc. Do all three before you reboot. No need to do any wiping or anything else. Hopefully our partition repairs did everything right and it boots to the new CM10.
As far as getting another device, I would wait until you see how you like this repaired one. If it does not work or you are not happy with it, then consider another device. As far as another device, I like the new Nook HD+, but I don't know how it compares with the others you mentioned.
Click to expand...
Click to collapse
Does flashing order matter?
CM10 -> GApps -> 5.5.0.4

msy4moment said:
Does flashing order matter?
CM10 -> GApps -> 5.5.0.4
Click to expand...
Click to collapse
No, but do it in that order.
Sent from my Nook HD+ running CM10 on Hybrid SD

Files Flashed Successfully - BUT - NC Won't Boot Correctly
leapinlar said:
No, but do it in that order.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Flashed files in order suggested (all files flashed successfully.)
Removed SDCard
Rebooted System
NC starts to boot
Gets to Cyanoboot - Universal Bootloader
Attempts automatic reboot three(3) times
Stalls at black screen

msy4moment said:
Flashed files in order suggested (all files flashed successfully.)
Removed SDCard
Rebooted System
NC starts to boot
Gets to Cyanoboot - Universal Bootloader
Attempts automatic reboot three(3) times
Stalls at black screen
Click to expand...
Click to collapse
Any messages during the three reboots? Or does it just say loading... and reboots to cyanoboot? And the last time when it goes to black screen, does it say loading... first?
Sent from my Nook HD+ running CM10 on Hybrid SD

Messages during auto reboot
leapinlar said:
Any messages during the three reboots? Or does it just say loading... and reboots to cyanoboot? And the last time when it goes to black screen, does it say loading... first?
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
* There are no messages during the reboots
* Just says loading before reboots to cyanoboot
* Yes, does say loading before it goes to black screen
(Screen Shot)
EMMC 01 (Upper Left Hand Corner)
cyanoboot
universal bootloader (middle of screen)
Loading...(middle of screen)

msy4moment said:
* There are no messages during the reboots
* Just says loading before reboots to cyanoboot
* Yes, does say loading before it goes to black screen
(Screen Shot)
EMMC 01 (Upper Left Hand Corner)
cyanoboot
universal bootloader (middle of screen)
Loading...(middle of screen)
Click to expand...
Click to collapse
Did you try holding the n button during the first time the cyanoboot logo showed? That should bring up the boot menu. Then select emmc recovery and see if CWM comes up. If it does try doing a "wipe data/factory reset". The reboot and see what you get. If it still hangs, boot back to CWM and reflash CM10 and boot again.
Sent from my Nook HD+ running CM10 on Hybrid SD

Boot in NC Boot Menu
leapinlar said:
Did you try holding the n button during the first time the cyanoboot logo showed? That should bring up the boot menu. Then select emmc recovery and see if CWM comes up. If it does try doing a "wipe data/factory reset". The reboot and see what you get. If it still hangs, boot back to CWM and reflash CM10 and boot again.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
* Held "n" to boot into Boot Menu
* Selected EMMC Recovery
NC rebooted into CWM
* Selected Wipe Data/Factory reset
(Start Screen Shot)
CWM-based Recovery v5.5.0.4
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
(End Screen Shot)
* Selected reboot system now
Attempted to boot
loading...
black screen
* Booted into CWM
* Flashed CM10
Rebooted System
Tries to load multiple times
Stuck on black screen
** Tried the steps again and the NC booted back in to CWM Recovery after multiple reboots**

Try redownloading the CM10 zip and reflashing. Maybe even the 4/14 version.
Sent from my Nook HD+ running CM10 on Hybrid SD

Download CM10 again and Reflash
leapinlar said:
Try redownloading the CM10 zip and reflashing. Maybe even the 4/14 version.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I downloaded cm-10-20130421-Nightly-encore.zip again
Did wipe data/factory reset
Flashed file
RESULT: Boot loops, then Black screen
I downloaded cm-10-20130414-Nightly-encore.zip
Did wipe data/factory reset
Flashed file
Result: Boot loops, then Black Screen
Does the fact that I am using two (2) 16g SanDisk SDCards make a difference? I could not load the zip files on SDCard 1 because there was not enough space.
SDCard 1 -
boot files
cwm 5.5.0.4 zip
SDCard 2 -
cm-10-20130421-Nightly-encore.zip
cm-10-20130421-Nightly-encore.zip
gapps-lb-20121011-signed.zip
update-encore-cwm.5.5.0.4-emmc-racks.zip

msy4moment said:
I downloaded cm-10-20130421-Nightly-encore.zip again
Did wipe data/factory reset
Flashed file
RESULT: Boot loops, then Black screen
I downloaded cm-10-20130414-Nightly-encore.zip
Did wipe data/factory reset
Flashed file
Result: Boot loops, then Black Screen
Does the fact that I am using two (2) 16g SanDisk SDCards make a difference? I could not load the zip files on SDCard 1 because there was not enough space.
SDCard 1 -
boot files
cwm 5.5.0.4 zip
SDCard 2 -
cm-10-20130421-Nightly-encore.zip
cm-10-20130421-Nightly-encore.zip
gapps-lb-20121011-signed.zip
update-encore-cwm.5.5.0.4-emmc-racks.zip
Click to expand...
Click to collapse
There still may be something wrong with your emmc partitions. Why don't you try an NC SD install per my thread linked in my signature.
Sent from my Nook HD+ running CM10 on Hybrid SD

Related

[Q] NC 1.2.0 bricked. Need to restore and start over.

I just bought an NC 1.2.0
no need to bore anyone with details but it is safe to say that it is virtually bricked. i would love a surefire way to get it completely back to the stock to start all over again.
i tried the repartitioning and reformatting technique using cm7 without any luck whatsoever. when i boot the device gets to the big N and "contains Reader mobile technology..." screen and never fully boots.
does anyone have a solution?
Presumably, one of those boring details involved writing an image to an SDcard:
eyeballer said:
Download 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image ... no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Click to expand...
Click to collapse
There's a decent chance the problem with your install is that you were using an older version of CWM on a newer NC, and it didn't write all the partitions correctly. Regardless, get the current version now.
Grab a B&N 1.2 image:
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
and install zip from sdcard > choose zip from sdcard in CWM.
Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.
mvnsnd said:
Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.
Click to expand...
Click to collapse
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.
Taosaur said:
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.
Click to expand...
Click to collapse
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.
mvnsnd said:
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.
Click to expand...
Click to collapse
It does if you flash it from ROM Manager, regardless of whether you have ROM Manager running internally or on a CM7 SD install. If he hasn't done that, 8 failed boots should work, but I'm not 100% sure on a repartitioned device.

[Q] lost cm7 sd install!

I had CM7 SD running on my 4gb sandisk. today I decided to try MIUI on emmc. to install it I did wipe/factory reset. now my CM7 SD doesn't run after the green logo.
on mounting I saw the following:
mmcblk1p1: all boot files present (THIS IS SDCARD ON MIUI)
mmcblk1p2:EMPTY
mmcblk1p3:EMPTY
mmcblk1p4: CM7 sdcard files present.
I did saw it show "formatting sd-ext" in CWM when doing factory reset.
now I don't have any SD card reader. is there any way to copy files of verygreens method back to sdcard from within MIUI as all partitions are already present.
Please help! my dad works on this nook. :|
P.S. through miui I'm also unable to boot into CWM emmc. tried using reboot into recovery and 5sec home button method.
thanks again. without you guys I'm pretty doomed.
UPDATE
I thought flashing MIUI caused problems with CWM so I tried to install CWM using ROM manager in MIUI but it cannot flash.
Looks like you wiped ur /system and /data partitions on ur SDcard rom. Only suggestion is to reinstall ur CM7 setup from scratch using verygreens method. It seems that your boot partition is still intact so you should be able to reinstall your CM7 through recovery mode as stated in his thread here http://forum.xda-developers.com/showthread.php?t=1000957
How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see below) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.
Insert the uSD card back into the NOOK and boot into "Recovery mode" (hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long).
Alternatively if you do not want to fight the timing, boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.
How to install market and gapps:
After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
Go to http://wiki.cyanogenmod.com/index.ph...Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
shutdown your nook and take the SD card out, insert it into your computer.
Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name. And boot into "recovery mode" (see above)
Click to expand...
Click to collapse
Just boot into your MIUI rom and mount the /boot partition of the SDcard rom, which would be SDcard in MIUI to your PC/Mac/Linux and follow the directions above to reinstall your CM7-SDrom using verygreens method.
-Racks
Thank you!
I got it to work using your steps.
But there's a weird thing. Even though the mmcblk1p2/p3 partitions were empty when I mounted them in MIUI, but my settings/apps/launcer/widgets were all intact. And its not like I just booted into CM7. I did see that tux penguin install script (verygreen) install CM7.
Anyways, thanks again.
Sent from my MB502 using XDA App
I think I blabbered too fast.
Today I found out that even though the wallpaper/apps were the same, I lost the app data and had to again add my Google acc.
Any idea which partition mmcblk1p2 or mmcblk1p3 was wiped out? Just curious to know what does CWM wipe out when it says "wiping sd-ext"?
Sent from my MB502 using XDA App

[Q] Can only boot to CWM

I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
bluevolume said:
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
Click to expand...
Click to collapse
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
bluevolume said:
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
Click to expand...
Click to collapse
Then it is the set flag issue I mentioned in the first part of my post. Not sure how to get it cleared. Just exercising CWM? Try flashing something else. Gapps again maybe. It won't hurt to flash them twice.
Edit: btw, what version of CWM are you running?
Sent from my Nook Color running ICS and Tapatalk
CWM v3.2.0.1
I installed gapps again, same problem. Gremlins!
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
cmendonc2 said:
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
Click to expand...
Click to collapse
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
leapinlar said:
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
Click to expand...
Click to collapse
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
Yes, I've had CWM flashed into the emmc for a while. So I could use the boot menu utility to boot to CWM if needed.
BTW - this is the ROM i'm using: http://forum.xda-developers.com/showthread.php?t=1344873
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
Click to expand...
Click to collapse
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue. I'll revisit that later today.
bluevolume said:
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue.
Click to expand...
Click to collapse
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
leapinlar said:
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
Click to expand...
Click to collapse
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I'm not that comfortable with adb commands so I starting looking for other solutions. Since you mentioned that its the actual boot files that are missing/corrupted, I searched around and found this:
http://forum.xda-developers.com/showthread.php?t=958748
I loaded the RecoveryFix.zip on my SD card and flashed it with CWM. Rebooted, and I was back to the 'Future of reading..." boot logo, but it still went straight to CWM. So I flashed the ROM again (the ROM I listed earlier in the thread), wiped cache, fixed permissions. Rebooted, and the "Cyanogenmod" boot logo was back. And instead of going right to CWM, the screen was blank for quite a while then I saw the little Android guy skate by... And I'm back in business.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
bluevolume said:
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
Click to expand...
Click to collapse
The next step I was going suggest if you could not fix it was to flash a new CWM to your boot files. Good job finding that.
Glad you got it running. I learned a lot myself and maybe that info will help others.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Click to expand...
Click to collapse
Got it, thanks m8
That clears up my mind.
I had the same problem, followed the thread you found. Did the same thing, now I'm back in business too. Thanks!
Just wanted to say thanks for figuring this out! I was in a similar situation after downgrading from cm9 back to cm7. Installed CWM using recoveryfix_3.0.2.8.zip from the thread above, and was back up and running after a restore of a cwm backup. Headed on vacation tomorrow and the wife would have had my head for being such an FW... you're a lifesaver!

[Q] Borked dual boot Nook

I inherited a failed dual-boot install, Nook BNRV200-A.
It starts and runs perfectly from SD card. But nothing successfully starts and runs from internal; mostly just boot loops. When I try to get into recovery, I get the dual-boot selector menu. This works OK, but if I select to boot recovery through it, no recovery comes up. If I try the trick with holding down both volume + and volume -, it just boot loops.
I would like to completely blow away all the internal partitions, recreate them and then restore standard boot, some ROM and CWM recovery. Is there a (current) procedure out there to do this? Happy to do this through ADB if somebody could tell me what to type.
The main thing is the dual-boot menu itself. I have tried reformatting /boot from CWM, but the durned thing still comes back.
(Wish we had something like the RUU or NVFlash utilities...)
TIA,
glg
Possible solution
Try following this guide ...( http://forum.xda-developers.com/showthread.php?t=1275859 )(eMMC 2/22 Dual Boot Guide 2.0 ) make sure you download all the needed files too.. It will allow you to wipe and repartition the internal eMMC .... then sets up a dual boot internal for you. Works slick and easily... Takes 20 - 30 min to do and is rock solid.
I used it and I am running CM7.2 (Mirage) on primary and B&N 1.4.1 on Alt boot... works great and is soooo fast (works great using Nook Tweaks to overclock to 1300)
Try it ... I think it will work fine
Tinpau
tinpau60 said:
Try following this guide (eMMC 2/22 Dual Boot Guide 2.0 )
Tinpau
Click to expand...
Click to collapse
Thanks for the quick reply. I did try that (at least the part about Revert from Dual-boot. I don't want a dual-boot setup).
So far, I have a working CM9 setup that successfully reboots and will now boot into recovery. But, for some reason, it doesn't recognize the SD card. I think it still has something to do with the partition table being messed up.
glg
I recently went from a dual boot back to single boot. I *think* this is what I did:
Ran revert dual boot zip
Rebooted into recovery. Important to reboot!
Ran repartition zip to 2 GB data/4 GB media (you can go back to stock 1 GB/5 GB if you prefer)
Did the usual wipe everything, clear caches
Installed rom of choice
Reboot
Worked just fine for me.
Sent from my NookColor using xda premium
Problem solved
k8108 said:
I recently went from a dual boot back to single boot. I *think* this is what I did:
Ran revert dual boot zip
Rebooted into recovery. Important to reboot!
Ran repartition zip to 2 GB data/4 GB media (you can go back to stock 1 GB/5 GB if you prefer)
Did the usual wipe everything, clear caches
Installed rom of choice
Reboot
Worked just fine for me.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
These steps were very helpful. I had an additional problem where the SDcard I was trying to use was formatted oddly. Instead of a single Primary partition, it was a /logical/ partition on an extended partition. Probably the vendor loaded some crapware on there in the empty space. So it never was seen by the Nook. When I deleted the logical and extended partitions and created a single 8GB primary partition, and formatted it as FAT32, the card was usable. Totally up and running.
Thanks,
glg

Nook color boot loop

Specs:
Nook Color Tablet bought off of ebay with CM10 on the internal memory (that "didn't work") and ClockworkMod Recovery v3.2.0.1
2gb bootable CM10 card
What i've done:
wiped the 2gb CM10 sd card.
Flashed internal memory (via the youtube tutorial) and put cm10 nightly from 03132013 and gapps
Installed netflix and hulu plus
Installed a blank 8gb sd card for apps and storage
So here's the problem. Last weekend I was watching a tv series on netflix. Drained the battery completely. Plugged it up for about two hours to recharge. Apparently When I plugged it up it decided to boot. >at this point it should be noted that the properly formated 8gb sdcard was in it, and not the bootable recovery sd card that was at the house<. When it booted it went straight into the ClockworkMod Recovery v3.2.0.1 menu. When I got back from the run we were on I tried rebooting it. It came up with the cyanoboot universal bootloader main screen, screen flashed and it went straight into the ClockworkMod Recovery v3.2.0.1 menu again. I tried rebooting several times. Same thing.
So tonight I got online, did a search, didn't find the answers i was looking for and settled on installing [ROM][JB 4.1.2][04MAR13 v1.20] SCHIZOID all-in-one (CM10+AOKP M1+PA 2.55). I flashed the /system, /data and /cache. Installed the new rom. Used the nook button + power to power it down, removed the boot card, and rebooted. Can you guess what it did? (see above).
So now i'm stuck. I DO NOT want to use a sd card to boot my nook. I want the OS in the main memory. Suggestions?
it should be noted, as i left this out of my OP, that I had tried to reflash CM10 back onto it. after that didn't work I tried the other rom. I've now tried reflashing CM10 and NOTHING is working.
vikingmedic said:
Specs:
Nook Color Tablet bought off of ebay with CM10 on the internal memory (that "didn't work") and ClockworkMod Recovery v3.2.0.1
2gb bootable CM10 card
What i've done:
wiped the 2gb CM10 sd card.
Flashed internal memory (via the youtube tutorial) and put cm10 nightly from 03132013 and gapps
Installed netflix and hulu plus
Installed a blank 8gb sd card for apps and storage
So here's the problem. Last weekend I was watching a tv series on netflix. Drained the battery completely. Plugged it up for about two hours to recharge. Apparently When I plugged it up it decided to boot. >at this point it should be noted that the properly formated 8gb sdcard was in it, and not the bootable recovery sd card that was at the house<. When it booted it went straight into the ClockworkMod Recovery v3.2.0.1 menu. When I got back from the run we were on I tried rebooting it. It came up with the cyanoboot universal bootloader main screen, screen flashed and it went straight into the ClockworkMod Recovery v3.2.0.1 menu again. I tried rebooting several times. Same thing.
So tonight I got online, did a search, didn't find the answers i was looking for and settled on installing [ROM][JB 4.1.2][04MAR13 v1.20] SCHIZOID all-in-one (CM10+AOKP M1+PA 2.55). I flashed the /system, /data and /cache. Installed the new rom. Used the nook button + power to power it down, removed the boot card, and rebooted. Can you guess what it did? (see above).
So now i'm stuck. I DO NOT want to use a sd card to boot my nook. I want the OS in the main memory. Suggestions?
Click to expand...
Click to collapse
You are in a recovery bootloop. Look at my NC Tips thread linked in my signature. See item A8 and A12. I suspect given your symptoms, you need to flash the romsrestore.zip file. It is trying to boot to stock recovery and repair itself.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
You are in a recovery bootloop. Look at my NC Tips thread linked in my signature. See item A8 and A12. I suspect given your symptoms, you need to flash the romsrestore.zip file. It is trying to boot to stock recovery and repair itself.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
flashed [romrestore-CWMflashable.zip - ] rebooted. same thing. straight back to the clockworkmod recovery menu.
created the CWM-5.5.0.4 bootable sd card and tried it that way. all that did was change the CWM menu blue instead of orange.
vikingmedic said:
flashed [romrestore-CWMflashable.zip - ] rebooted. same thing. straight back to the clockworkmod recovery menu.
created the CWM-5.5.0.4 bootable sd card and tried it that way. all that did was change the CWM menu blue instead of orange.
Click to expand...
Click to collapse
so here's a new one for you. I was going through the three finger salute method and screwed it up. low and behold I actually got to the cyanogenmod circle screen. Think we might be good to go.
vikingmedic said:
flashed [romrestore-CWMflashable.zip - ] rebooted. same thing. straight back to the clockworkmod recovery menu.
created the CWM-5.5.0.4 bootable sd card and tried it that way. all that did was change the CWM menu blue instead of orange.
Click to expand...
Click to collapse
I suggest you flash my zip for putting stock recovery back on the system. Then boot and let it do what it had been trying to do, whatever that is. It could be trying to do the 8 failed boot reset.Then when it has finished, put a new rom on it.
Either that or put stock on it (A15) and it will put everything back to virgin. Then you can put your own rom on it.
Sent from my Nook HD+ running CM10 on Hybrid SD

Categories

Resources