Quote:
Originally Posted by zartemis
The CWM bootloop is very odd -- since it must mean that something in the way the regular (rooted) BN OS boots is triggering a fall-back to a recovery boot. You normally can't get a recovery boot without doing something 'special', either a hardware button trigger or boot off of SD. One would need more details about the stock BN boot routines to debug this fully. Even unrooted Nooks have sometimes booted to their recovery unexpectedly and caused an unwanted restore-to-stock wipe -- so there is some sort of a test or failure case that can trigger it. At least with CWM, merely launching the recovery boot doesn't wipe your device like the BN recovery does (I must admit that's the biggest reason I'm glad to have the BN recovery off my device).
Thankfully there is an easy fix (you don't even have to restore to stock) -- just restore BN recovery boot with the monster rootpack and you're rolling again.
There is also one report that even after getting CWM installed correctly on rooted 1.1 that using ROM Manager to reboot into recovery will re-trigger the bootloop. Curious about that, I just tried on my rooted 1.1 device. No issues. I rebooted into CWM from ROM Manager and then rebooted and it came up into the OS normally.
Oh, and you and I rooted slightly differently. I installed CWM on a rooted 1.0.1 device and then used that to apply the pre-rooted update zip. Sounds like you used CWM on an SD to apply the zip and then installed CWM. A minor difference that may be all the difference?
|
I agree its a very odd thing, but i have faith that the Devs will figure it out, untill then I just keep CWR off my nook and safe on a SD card. I'm really just waiting for CM7 anyway
