so recently i flashed the new cyanogen mod 6 rc1 and tested it out but it didnt quite please me just yet so i wanted to go back to my cyanogen mod 5. i went to fastboot did system wipe and all that then went to recovery and restored my nandroid backup and when i tried to boot it up its been stuck on the boot animation for about an hour. so is there a way to fix this?
also while i was on cyanogen 6 rc1 i applied this mod http://forum.xda-developers.com/showthread.php?t=722861 so that i could to apps to ext could this have caused the problem?
EDIT:
Nevermind i figured it out i just ran logcat and found out it was getting stuck when trying to identify my apps on my sdcard so i just took it out rebooted then when all seemed good i just put my sdcard back in rebooted and alls good!
I rooted my 1.0.0 NC, worked great. Overclocked it using the 1000mhz kernel, worked great. Installed Rom Manager using adb, clockwork recovery, and sideloaded 1.1 update, still worked great. Decided to try out Froyo...I was a big dummy and didn't create a backup...it installed, then I felt it was slow so decided to try an updated froyo (nookie-froyo 5) works great. But now I'm having a problem where it is only booting from the SD card. I tried everything but nothing is working. I tried doing the copy2emmc.sh, didn't work. Tried running CWR and flashing the stock 1.0.0, doesn't boot up when I remove the SD card and click reboot now. Any ideas? Please help. I would like to boot from the emmc so if I can either get froyo installed on it or go back to stock and just stick with the 1.1 I'll be happy either way.
have you tried these methods?:
hxxp://nookdevs.com/Flash_back_to_clean_stock_ROM
Sorry for the hxxp, don't have enough posts to link yet.
Good news, I flashed it with the repartition-boot-with-stock.zip and now it boots up but just stuck in a loop. I tried doing the 8 boot step but can't get the timing down...
Finally restored!
So I tried to do the restore again but this time I tried the 1.0.1 instead of the 1.0.0 and it worked!! Thanks everyone!
I recently decided that I wanted to do a fresh install of CM7 using the latest nightly. I wiped everything, including boot (which I think is the problem). I made a bootable CWR SD card and installed the latest nightly and gapps. Everything booted up fine and ran great, until I tried to use ROM Manager. Every time I try to boot into recovery, the Nook hangs at the "ReadForever" screen. It was hanging at the new Cyanogen boot logo, but in an attempt to correct the issue, I flashed the stock 1.2 uboot. I have also noticed that several apps are now showing up at phone size when they were fine before running the same setup. I am running n87, 5/23/11 OC, and the stock 1.2 uboot. Does anyone have any idea what the problem might be?
You can try to disable the "compatibility mode" in order to try and get the apps to use the full screen. Regarding the Clockwork recovery issue, I have no idea - sorry!
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.
Last night I restored my NC to stock using CWM and nook color 1.4.1 update.
It worked, and I was back at 1.0.0
I had planned on doing an upgrade to the latest B&N version this morning.
When I got up, the NC was in a boot loop installing the stock recovery, again and again.
If this had happened when I did the restore last night, it would make a little sense, but it was working last night.
I'm guessing it's stuck in 8 reboot mode and I don't know:
How it happened
or
What to do about it.
Help....
thanks,
Bob
bigkid52 said:
Last night I restored my NC to stock using CWM and nook color 1.4.1 update.
It worked, and I was back at 1.0.0
I had planned on doing an upgrade to the latest B&N version this morning.
When I got up, the NC was in a boot loop installing the stock recovery, again and again.
If this had happened when I did the restore last night, it would make a little sense, but it was working last night.
I'm guessing it's stuck in 8 reboot mode and I don't know:
How it happened
or
What to do about it.
Help....
thanks,
Bob
Click to expand...
Click to collapse
I don't quite understand all of your post. You said you restored to 1.4.1 with CWM, yet you said it booted to 1.0.0.
In any case you can run my romrestore zip from my tips thread linked in my signature. That should reset the 8 failed boot counter and then you can flash stock 1.4.3 linked also in my tips thread with CWM and all should be ok. You may need to flash my format 5, 6, and 7 zip before you flash the stock rom.
Got it working.
Apparently the flash was incomplete, not sure why that happened.
I redid it, and it came back to stock.
Thanks for your reply.