View Single Post
Old 02-06-2011, 01:45 AM   #10
zartemis
Addict
zartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it iszartemis knows what time it is
 
zartemis's Avatar
 
Posts: 283
Karma: 2002
Join Date: Nov 2007
Device: Kindle3, Kindle2, Nook, NookColor
Quote:
Originally Posted by jasoraso View Post
It could be that CWR messed up wiping dalvick / caches after flashing the kernel. I have seen other instances where wiping dalvik doesn't finish cleanly. In fact, I remember now that it DIDN'T wipe dalvik cleanly; so after waiting 2 minutes, I forced a hard reboot ... and began an endless cycle of booting into cwr
Well, there IS a bug in the current CWM that can cause it to fail after wiping cache, requiring a hardboot (yes, it has happened for me, too -- although it was my understanding that it is able to wipe the cache, just that CWM doesn't continue to run after doing so without a hard boot). It should, (and in my case, does) then boot up to whatever OS is on your Nook (assuming there is no bootable partition on your SD).

It would be shocking to me if a working (menu nav and all) CWM was fully in dalvik cache and that is what runs on a reboot. I don't think it works quite like that. Dalvik cache is a bytecode optimizer (which is why first boot on a new ROM is slower and why you wipe it for a new ROM -- the dependency tree would be all wrong otherwise).

Last edited by zartemis; 02-06-2011 at 02:03 AM.
zartemis is offline   Reply With Quote