Im hoping someone can help me with my nook. I tried to flash froyo, made a wrong turn and now it wont boot. I rooted it just fine but before flashing froyo I wiped the system and it just went downhill from there. My guess is its not unfixable because I can boot clockworkmod from sd card but I can't seem to get the froyo rom on that same card. I flashed the sd card with clockwork but when I go to copy the froyo zip my pc says there isn't enough space. Its an 8 gig card formatted on windows fat32 default. The pc recognizes the card as 7.4 gigs after format. So it seems once I can get clockwork and froyo on the same card I should be able to flash. Anyone have any ideas as to what im doing wrong. I can provide more info once im back home and would really appreciate any help or direction. I did root my eris just fine and I look back and realize I shouldn't have wiped the nook before flashing froyo.
Sent from my nonsensikal froyo using XDA App
L o l relax bro you are not bricked... the reason you can't copy froyo is because the SD is partitioned when you write the image...
Do this.
Copy clockwork mod 3.0.1.0 update zip on the bootable cwm SD after you image it. The zip should be small enough to fit on the SD if not then have 2 SD cards on hand. Once you boot into the SD flash the recovery 3.0.1.0 zip you copied.
Then remove SD and reboot recovery to make sure it flashed cwm properly.
At this point reformat your SD card and copy the froyo zip onto it. Insert SD card into the nook.
On cwm go to mount and format data, system, and cache. After you have done this then proceed to flash the nookie froyo
You should be ok. Good luck and give thanks if this helps you.
Sent from my NookColor using Tapatalk
I was able to boot into CWM and flash the ClockWork Zip file then I removed the SD card and selected reboot system. It just ends up turning off and the power button wont turn it back on. Ive done this 3 times and the same happens. Should I be concerned with the CWM version numbers. The boot image is version 3.0.0.5.
Im clearly in over my head. I should have researched more before starting this project. LOL Im so confused Im second guessing everything now. Should I be using WIN32DiskImager or WinImage when making the Boot recovery disc. Maybe the Image I burn should be version 3.0.1.0 instead of 3.0.0.5. Maybe I need to just go back to factory and start over.
Sent you a pm
Sent from my NookColor using Tapatalk
Thank You ax0r! I cant thank you enough for the time you took in setting me straight. I was swimming in information and you threw me a life line. This thing is awesome! I have a little bit to go yet to get it the way I want but it should be all downhill from here. Thanks again and the moral of the story is to take your time and research before starting something like this. Something I took to heart when rooting and installing my ROM on my Droid Eris but didnt do with my NookColor.
If you fixed your issue maybe sharing how with other newbies would be of benefit.
I'm assuming you just burned a 3.0.1.0 CWR image, copied the CM7 zip to that, booted into CWR, wiped your boot, system, data, cache partitions, and installed the zip?
Your right Im sorry. Basically this is the gist of it. http://forum.xda-developers.com/showthread.php?t=938200
IFLATLINEI said:
Thank You ax0r! I cant thank you enough for the time you took in setting me straight. I was swimming in information and you threw me a life line. This thing is awesome! I have a little bit to go yet to get it the way I want but it should be all downhill from here. Thanks again and the moral of the story is to take your time and research before starting something like this. Something I took to heart when rooting and installing my ROM on my Droid Eris but didnt do with my NookColor.
Click to expand...
Click to collapse
Cool bro glad you are up and running. If you have any question feel free to hit me up.
Sent from my NookColor using Tapatalk
ax0r said:
Cool bro glad you are up and running. If you have any question feel free to hit me up.
Click to expand...
Click to collapse
It is kind folks like you that make all of this such a great success.
I'm headed out to purchase my Nook Color shortly and it's nice to know that there is an awesome community here to help. I don't actually suspect any problems, as I've been reading and learning for a couple weeks now. Plus, I've hacked my OG Droid to death, so I have some experience.
Anyway, thanks for your willingness to help. It's refreshing to see.
Glad you are back up and running. I've come to the conclusion that if I have bricked mine yet. Then this thing is unbrickable. I've messed up many a times.
You are rigth,
With a microSD card in good condition: CWM + kernel images you can always go on.
I mistakenyl updated to rom managers cm 7.1 on my noko color. As it installed it stopped at the ANDROID_ in blue letters on the left side of the screen (bottom if looking at it horizontally).
I dont know how to get out of this. I've tried to hold down the power button but that didnt work. Please help.
Thanks,
-Ryan
***EDIT****
The nook just turned off... but when i try to start recovery mode by pressing down the power button, it doesn't reboot into recovery. any help? I want to install a different ROM (a rom that actually works!). Anyone know how i can get it in recovery mode or install the room using my computer?
Thank you so much,
-Ryan
You mean the cm7 release candidate? It worked fine for me...
Google how to make a bootable cwm microsd card.
Sent from my NookColor using XDA Premium App
CM7 is as good as your going to get if your trying yo find a new rom. What you need to do is wipe everything and reinstall using a bootable SD card.
Sent from my LG Optimus V using Tapatalk
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 wanted to put this out there and see if anyone had any suggestions for a etneral loop Nook HD+
OK, so THe Nook HD+ SEEMS to charge fine (plug into wall ligbht goes green then orange then green again much later).
I plug it into a computer (windows 7) and it goes "Burrrip" but I can;t see it in the devices.
I have treid the hard reset (holding the power and "n" key for 20 to 30 seconds and then trying to restart but nothing.
The Nook just hangson the initial boot screen (white nook on a blck background).
Does anyone think that I might be able to get it to boot from SD? Just curious if the boot from SD would occur after where it is hanging or if it might work.
If the SD might work...what is the best option. Stock ROM would be fine.
Thanks for any help.
I know there are a few threads dedicated to SD cards, mainly seeing if it is worth the time to play.
Thanks.!
Yes, it should boot to a bootable SD. Go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD per item 1a. Then flash one of the plain stock zips I have in item 6. Also do a factory reset with the CWM.
Sent from my BN NookHD+ using xda premium
Thanks
leapinlar said:
Yes, it should boot to a bootable SD. Go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD per item 1a. Then flash one of the plain stock zips I have in item 6. Also do a factory reset with the CWM.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
Thanks. I will try that. Glad to hear it is not hopeless.
Still not working
I made the card per your instructions and it seemed to go fine. I placed it in the HD+ and turned it on and nothing. Now, I have a Lexar 6 card. Will that matter? I have seen where most people say to use 4s. Just happen to have that one on hand. Do you notice any better success when you burn an image as oppsed to the "new" method?
Just curious. Any other tips or tircks you can offer? What about opening it up and disconnecting the battery and letting it fully poser down?
Hoping it is not just bricked.
Thanks for the help.
Jason
Another card could help. And either method of making the card can work. Usually best to try one and if it does not work, try the other.
Sent from my BN NookHD+ using xda premium