Related
I don't know whats going on. what buttons do I press to boot into stock os from cm7.2?
How did you install CM7?
Sent from my NookColor using xda app-developers app
dvrdwn said:
I don't know whats going on. what buttons do I press to boot into stock os from cm7.2?
Click to expand...
Click to collapse
Exactly. We can't help you if you don't give us more details since there are tons of different kinds of Installs you can do on the Nook Color. "Did you install CM7 to the SDcard? Did you use a Dual-Boot EMMC install?" You get the idea. If it's an SD install it can depend on what u-boot was supplied with the install you used, but the simplest way is to simply Turn Off your Nook and Remove the MicroSD card until the Nook boot's into Stock, reinsert card.
japzone said:
Exactly. We can't help you if you don't give us more details since there are tons of different kinds of Installs you can do on the Nook Color. "Did you install CM7 to the SDcard? Did you use a Dual-Boot EMMC install?" You get the idea. If it's an SD install it can depend on what u-boot was supplied with the install you used, but the simplest way is to simply Turn Off your Nook and Remove the MicroSD card until the Nook boot's into Stock, reinsert card.
Click to expand...
Click to collapse
Thanks for your help guys. I figured it out. I just upgraded to a newer version of cm7 with uboot I believe. This "new" way of booting between os's is alittle less straight forward than before.
If you see a logo saying Cyanoboot when you start up, you can try holding the n button when your Nook starts up.
I've been trying like crazy to make a bootable sd card to run cm9 with no success. the Cyanogen universal bootloader comes up, but when it goes to boot up the ROM it just sits on a black screen for about 15 seconds then reboots. I can't figure out what I'm doing wrong. Any suggestions would be greatly appreciated. Thanks
Sent from my NookColor using xda premium
It would be so much useful if you could also describe us which installation method did you follow.
Produced by NookColor at CM9 4.0.4
I followed verygreens method. Over the last 6 months, I've performed this method a good 30-40 times for cm7. From what I understand, I'm supposed to perform this same method for cm9. I've tried using both image installers just to make sure I was using the correct one
Sent from my NookColor using xda premium
purpleurkle said:
I followed verygreens method. Over the last 6 months, I've performed this method a good 30-40 times for cm7. From what I understand, I'm supposed to perform this same method for cm9. I've tried using both image installers just to make sure I was using the correct one
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
You need to rename the cm zip to begin with update-.
Or are you starting with a fresh SD burned with a new image? You should not get a cyanogen logo if you are. You should just get a loading followed by the penguin and some text. If you do not have the newest image, I think you can get it on leapinlar's tip thread.
I've tried it with the new image and the old one. I'm passed the penguin, it ran the text and shut off. When I turn it back on I get the cyano universal boot, then it goes to a black screen for about 10 or15 seconds then it reboots and will do this over and over again if I don't shut it down.
Sent from my NookColor using xda premium
Will it still boot to emmc when you select that with the boot menu?
Yes it does.
Sent from my NookColor using xda premium
purpleurkle said:
Yes it does.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Ok, that means you are not in a recovery bootloop. And you do not need to repair any partitions on emmc. And given the fact that it boots to cyanoboot bootloader rather than the little penguin means the rom flashed successfully. The only thing I can think of is a corrupted download file for CM. Try re-downloading.
ok, now when i'm in the penguin stage with text, it reaches a point were is says it cant find initial install files. which i assume means it cant find the rom. in know your first thought is going to be that i didnt rename the rom update-, but i did. I am just adding update- to the beginning of the file name right? I'm not supposed to take away the cm- all together am i? it reads update-cm-9.
purpleurkle said:
ok, now when i'm in the penguin stage with text, it reaches a point were is says it cant find initial install files. which i assume means it cant find the rom. in know your first thought is going to be that i didnt rename the rom update-, but i did. I am just adding update- to the beginning of the file name right? I'm not supposed to take away the cm- all together am i? it reads update-cm-9.
Click to expand...
Click to collapse
And it is on the boot partition, right? That name is OK.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
yes it is. i ran it again and it took it, but now its doing the same thing it was before were it goes from cyanoboot to a black sceen for 15 seconds or so then reboots. the thing is i got this rom from a different source this time samiam303. could i be doing something wrong when expanding the partition? im expanding it to around 1g.
purpleurkle said:
yes it is. i ran it again and it took it, but now its doing the same thing it was before were it goes from cyanoboot to a black sceen for 15 seconds or so then reboots. the thing is i got this rom from a different source this time samiam303. could i be doing something wrong when expanding the partition? im expanding it to around 1g.
Click to expand...
Click to collapse
Why are you expanding the boot partition so large? And how are you doing it? And you are doing it before you boot the first time, right? You may be confusing the verygreen script that partitions the rest of the SD. It may be that the other partitions are not created right. Then when you flash, the rom is not installed correctly.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
purpleurkle said:
yes it is. i ran it again and it took it, but now its doing the same thing it was before were it goes from cyanoboot to a black sceen for 15 seconds or so then reboots. the thing is i got this rom from a different source this time samiam303. could i be doing something wrong when expanding the partition? im expanding it to around 1g.
Click to expand...
Click to collapse
Are you expanding the boot partition prior to doing anything else?
It is important that if in windows... when you expand boot partition... do it before any other partition are on it... modifying ext partitions in windows will cause major issues... including moving them.
Also... how long are you waiting... initial boot after running the setup will have a black sceen for several minutes.
I'm expanding to1g because someone told me to do so. I'm expanding after restore to virtual hard drive, but before puting on cm9 file. Could it be because in expanding it to much? I'm using easy partition manger. I don't see a way to expand the partition before restore to virtual hard drive. In response to dizzyden, (like I said in my first post), after the cyanoboot screen it goes to the black screen for about 15 seconds or so then reboots and will continue to do so over and over until I hard power it. I'm aware that I'm coming off as an idiot but up until 6 months ago I'd never ever sat down at a computer. So thankyou for your patience
Sent from my NookColor using xda premium
purpleurkle said:
I'm expanding to1g because someone told me to do so. I'm expanding after restore to virtual hard drive, but before puting on cm9 file. Could it be because in expanding it to much? I'm using easy partition manger. I don't see a way to expand the partition before restore to virtual hard drive. In response to dizzyden, (like I said in my first post), after the cyanoboot screen it goes to the black screen for about 15 seconds or so then reboots and will continue to do so over and over until I hard power it. I'm aware that I'm coming off as an idiot but up until 6 months ago I'd never ever sat down at a computer. So thankyou for your patience
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
You should expand immediately after burning to the card. And 300Mb should be plenty for whatever you want to do. Anything more is just wasting your SD space. It is possible that having it so large did mess it up, but I don't know why it would. Just to be safe, I would boot without the zip on it and come back later after the first boot and it has partitioned the SD and put it on.
purpleurkle said:
I'm expanding to1g because someone told me to do so. I'm expanding after restore to virtual hard drive, but before puting on cm9 file. Could it be because in expanding it to much? I'm using easy partition manger. I don't see a way to expand the partition before restore to virtual hard drive. In response to dizzyden, (like I said in my first post), after the cyanoboot screen it goes to the black screen for about 15 seconds or so then reboots and will continue to do so over and over until I hard power it. I'm aware that I'm coming off as an idiot but up until 6 months ago I'd never ever sat down at a computer. So thankyou for your patience
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
No problem urkle... Personally, I'd install CM7 on the SD and if/when it boots correctly... update it to CM9
Leap... I've only seen the size issue when boot partition is 2GB or larger... and don't ask me why I tried that LOL
OK, so I should burn the installer image, then expand the partition, then boot, then go back and put the cm9 zip on?
Sent from my NookColor using xda premium
purpleurkle said:
OK, so I should burn the installer image, then expand the partition, then boot, then go back and put the cm9 zip on?
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Yes
Still no change. Im still able to make cm7 burn without a problem, the only thing I'm doing different with the cm9 burn is position expansion.
Sent from my NookColor using xda premium
Hmm, and it does do boot to emmc with the cyanogenmod boot menu? I suspect partition 2 issues on emmc, but it would not boot to emmc if that was messed up.
Edit: Why are you expanding the boot partition at all. To make CM9 fit? If that is the only reason, go get my version that has already been expanded. Your PC may be doing something to the card. You can get my version by visiting my tips thread linked in my signature.
So I am on my 4th nook. One for me, for my son, father and now i've aquired a 16gb for my wife. I have the original bootable sd card that i've used on all the other ones (successfully) to install cm10 alpha 1.
I've tried doing everything that i've done on the other ones, but i CANNOT get the 16gb to boot into recovery. i've tried the three finger reboot, i've tried restarting it 7 times, and i just cannot get it to boot into recovery / into the flash menu.
thoughts?
You are talking about a Nook Tablet, go here and try to set up CM10.1 on a SD card there.
Edit: Better link that goes directly to SD boot post
Sounds like a nook tablet, not a nook color. The same ROMs and recovery won't work
Sent from my NookColor using xda premium
rtotheichie said:
Sounds like a nook tablet, not a nook color. The same ROMs and recovery won't work
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
thanks ya'll
I have read everything I can find and I am still confused. I built a bootable CWM card for the HD+ using the root and extras thread and that works fine. I downloaded cwm-recovery-ovation-2.zip and using the aforementioned card wrote the new boot loader and it says it was successful yet I can't boot into recovery. Am I using the right file is there something else that needs to be done?
jpisini said:
I have read everything I can find and I am still confused. I built a bootable CWM card for the HD+ using the root and extras thread and that works fine. I downloaded cwm-recovery-ovation-2.zip and using the aforementioned card wrote the new boot loader and it says it was successful yet I can't boot into recovery. Am I using the right file is there something else that needs to be done?
Click to expand...
Click to collapse
How are you trying to boot to recovery? What commands are you using?
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
How are you trying to boot to recovery? What commands are you using?
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
OK maybe that is my issue. On my last tablet and my phone I hold down a couple of keys and I can get to CWM. I take it that is not true with the HD+?
jpisini said:
OK maybe that is my issue. On my last tablet and my phone I hold down a couple of keys and I can get to CWM. I take it that is not true with the HD+?
Click to expand...
Click to collapse
It is true, you just have to know which keys. Hold power and the n key together for a few seconds when it first starts booting. Release before it turns itself off and it should boot to recovery. If the flash took, it boots to CWM. If it did not take, it boots to stock recovery and asks if you want to clear data.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
...Release before it turns itself off and it should boot to recovery...
Click to expand...
Click to collapse
Ugh, I could have used this email bit of info a while ago I ended up setting up adb to boot into recovery... Couldn't figure out why the dang thing kept shutting off.
Sent from my Nook HD+ using Tapatalk 4 Beta
Excellent I will have to play with it. Tried a couple of times this morning but didn't get into anything. I have to go to work I will try later. Thanks man.
Sent from my Galaxy Nexus using xda app-developers app
Thanks again man! I got it. You have to turn it on first, then hold down the "n" key, then hold down power again for about 5 seconds. I am used to my other devices you start with the device off not booting up.
Hopefully this will help someone else. I am doing a backup now so I can start playing without worry.
CWM Boot
jpisini said:
Thanks again man! I got it. You have to turn it on first, then hold down the "n" key, then hold down power again for about 5 seconds. I am used to my other devices you start with the device off not booting up.
Hopefully this will help someone else. I am doing a backup now so I can start playing without worry.
Click to expand...
Click to collapse
Thanks from me too. Same problem and would never have found that particular key combination without your help.
Hey guys,
So I've had my nook HD+ for a few months and have been running various roms on it for a while. Most recently I've had the latest Slimbean rom on it for about a week, Yesterday I went to use it after it had been charging all night and found it to be off. When I turn it on, it will just sit at the initial nook screen or get to the cyanoboot splash screen and just sit. I cannot boot into EMMC TWRP as it does the same thing. When I try to boot TWRP from an SD card it will get to the TWRP splash screen and just sit there without actually getting into the recovery, and if I try to boot a CWM SD card it will just sit at the cyanoboot splash screen. Is there something I can do to fix it or is my device bricked? And if it is bricked is there any way I could go about getting it replaced with the warranty as it currently and obviously has a custom rom on it.
Thanks for any help you can give me guys.
alk195 said:
Hey guys,
So I've had my nook HD+ for a few months and have been running various roms on it for a while. Most recently I've had the latest Slimbean rom on it for about a week, Yesterday I went to use it after it had been charging all night and found it to be off. When I turn it on, it will just sit at the initial nook screen or get to the cyanoboot splash screen and just sit. I cannot boot into EMMC TWRP as it does the same thing. When I try to boot TWRP from an SD card it will get to the TWRP splash screen and just sit there without actually getting into the recovery, and if I try to boot a CWM SD card it will just sit at the cyanoboot splash screen. Is there something I can do to fix it or is my device bricked? And if it is bricked is there any way I could go about getting it replaced with the warranty as it currently and obviously has a custom rom on it.
Thanks for any help you can give me guys.
Click to expand...
Click to collapse
Did you try to boot to your internal TWRP but holding the n key and power key together from a power off situation? Be sure to release the power key after a few seconds so that it does not power itself back off.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Did you try to boot to your internal TWRP but holding the n key and power key together from a power off situation? Be sure to release the power key after a few seconds so that it does not power itself back off.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yeah I've tried that, it acts the same as it would if I hadn't held the n button and booted.
alk195 said:
Yeah I've tried that, it acts the same as it would if I hadn't held the n button and booted.
Click to expand...
Click to collapse
n or n + power?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
n or n + power?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I've tried n+power and released the power button after a few seconds before it turns off
alk195 said:
I've tried n+power and released the power button after a few seconds before it turns off
Click to expand...
Click to collapse
The bootable SDs, were they new or had they worked previously?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
The bootable SDs, were they new or had they worked previously?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I had one that I had used previously that I had written over and used for other things, I remade the bootable SD on that one and it didn't work. I also tried making 2 other bootable SDs following both methods (new and old) of the guide in this thread. My HD+ has never had a problem booting from bootable SDs before this happened, aside from taking a few reboots to actually get it to boot which I have read is common.
alk195 said:
I had one that I had used previously that I had written over and used for other things, I remade the bootable SD on that one and it didn't work. I also tried making 2 other bootable SDs following both methods (new and old) of the guide in this thread. My HD+ has never had a problem booting from bootable SDs before this happened, aside from taking a few reboots to actually get it to boot which I have read is common.
Click to expand...
Click to collapse
Since you have a custom ROM and a custom recovery on internal, it is hard to tell if the SDs are booting or not. Both cases look the same on the screen. I would bet they are not booting and it is always trying to boot to internal.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Since you have a custom ROM and a custom recovery on internal, it is hard to tell if the SDs are booting or not. Both cases look the same on the screen. I would bet they are not booting and it is always trying to boot to internal.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Well I can tell that the bootable TWRP SD card is at least trying to boot, as by just turning on the nook with that card in and not pressing the n button or anything will get it to the TWRP splash screen before it gets to the actual usable recovery screen. If i try to boot into the internal TWRP via n+power, it will either sit at the nook screen or the cyanoboot screen. I don't know if the CWM SD card that I tried was not working at all or just locking up on its own SD cyanoboot screen. Does that help at all?
alk195 said:
Well I can tell that the bootable TWRP SD card is at least trying to boot, as by just turning on the nook with that card in and not pressing the n button or anything will get it to the TWRP splash screen before it gets to the actual usable recovery screen. If i try to boot into the internal TWRP via n+power, it will either sit at the nook screen or the cyanoboot screen. I don't know if the CWM SD card that I tried was not working at all or just locking up on its own SD cyanoboot screen. Does that help at all?
Click to expand...
Click to collapse
I don't use TWRP so I don't know much about it. But both TWRP and CWM expect a working /cache partition on emmc. So that may be the issue. But unfortunately since you replaced stock recovery with TWRP, it cannot repair itself with the 8 failed boot procedure. You have to get an SD to boot to fix anything.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
I don't use TWRP so I don't know much about it. But both TWRP and CWM expect a working /cache partition on emmc. So that may be the issue. But unfortunately since you replaced stock recovery with TWRP, it cannot repair itself with the 8 failed boot procedure. You have to get an SD to boot to fix anything.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Alright, so I finally got a working CWM SD card using the img from this thread. Now when I boot into it it says:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
Then when I try to choose a zip from the sd card to flash stock recovery, it says E:Can't mount /sdcard/
Any ideas? Thanks so much for the help by the way!
alk195 said:
Alright, so I finally got a working CWM SD card using the img from this thread. Now when I boot into it it says:
Then when I try to choose a zip from the sd card to flash stock recovery, it says E:Can't mount /sdcard/
Any ideas? Thanks so much for the help by the way!
Click to expand...
Click to collapse
Yes the issue is that CWM is for installing CM to SD. That one will not find /sdcard because it is emulated and only is available after the ROM is installed.
You need to get a CWM working that is meant for installing things to emmc.
And those can't find /cache messages are worrisome.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Yes the issue is that CWM is for installing CM to SD. That one will not find /sdcard because it is emulated and only is available after the ROM is installed.
You need to get a CWM working that is meant for installing things to emmc.
And those can't find /cache messages are worrisome.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Are there any other CWM bootable SDs that I could try?
alk195 said:
Are there any other CWM bootable SDs that I could try?
Click to expand...
Click to collapse
You said you tried all of mine from my HD/HD+ CWM thread. Did you try my TWRP ones from that thread? The only other one I know is verygreen's early 2.1 from his emmc thread.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You said you tried all of mine from my HD/HD+ CWM thread. Did you try my TWRP ones from that thread? The only other one I know is verygreen's early 2.1 from his emmc thread.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yeah I've tried the TWRPs from your thread, I got verygreen's one from this page to boot with his alternate uImage further down the page. In there is says that I can push the stock recovery to the emulated SD card via ADB and install it from there. Problem is that I can't get the adb drivers to install while in CWM. Any thoughts?
alk195 said:
Yeah I've tried the TWRPs from your thread, I got verygreen's one from this page to boot with his alternate uImage further down the page. In there is says that I can push the stock recovery to the emulated SD card via ADB and install it from there. Problem is that I can't get the adb drivers to install while in CWM. Any thoughts?
Click to expand...
Click to collapse
No that is still one for an SD install. I meant the one on this thread:
http://forum.xda-developers.com/showthread.php?t=2263553
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
No that is still one for an SD install. I meant the one on this thread:
http://forum.xda-developers.com/showthread.php?t=2263553
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
That one hangs at the cyanoboot screen as well.
alk195 said:
That one hangs at the cyanoboot screen as well.
Click to expand...
Click to collapse
I think your emmc is borked, not allowing those SDs made for emmc installs to boot. Those /cache errors are telling. And since you have other than stock on there and it partially boots showing that, I think you are stuck.
I think your only recourse is to put the no-emmc version on SD and run it that way. Go to the verygreen thread just before the last one I pointed to and try getting a ROM to run on it. I know nothing about that so if you have trouble, ask in that thread.
Sent from my BN NookHD+ using XDA Premium HD app
Were you running a trim enabled kernel/rom? Do you know if you had the faulty emmc chip?
jpisini said:
Were you running a trim enabled kernel/rom? Do you know if you had the faulty emmc chip?
Click to expand...
Click to collapse
I do have the faulty chip, although its the rev6 version. I have tried my best to avoid running any trim enabled kernels. I don't know if Slimbean has trim enabled, I asked a couple times in the thread and never got a response, so I figured I'd try it and with the number of people using it I figured that it was disabled since I hadn't seen anyone having any trouble with it.
Sent from my XT907 using Tapatalk