• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Anyway into CWR when in bootloop

K

Klauven

Member
I know I can do this by creating a bootable SD card, but I am away from home and could just restore my backup if I could get into CWR. I heard you can hold power and the N button, but its just not working for me.

I installed the 4/24 OC kernal over my CM7.03 and it gets into CM7 and then reboots or locks up within 5 seconds. It really sucks, I can almost get into ROM manager to reboot into CWM before it freezes, but not quite.

What the heck am I doing wrong with these Kernels? I am 0 for 2 trying to install a Dalingrin kernel. Was I supposed to wipe something before installing the kernel?
 
Now I am having trouble making a bootable SD card, process of writing it is too fast and then the card is not readable and needs to be formatted. Tried Win XP and Win 7, sheesh these things are testy. I am now trying the SD card from my droid, something has got to work.
 
Sounds like you're doing something wrong.

Did you remove and replace the sdcard before copying your file to it? Did you unzip the img file before flashing it? Did you follow my tutorial?
 
I have been having trouble OC'ing my nook. I used an app, no-frills CPU (free) https://market.android.com/details?id=it.sineo.android.noFrillsCPU&feature=search_result to oc but mine locked up at 1200mhz. I am not sure if it was the app or my nook but if you over clock with the app and it locks up you can just reboot and uninstall the app. I think somebody (hint, hint wink, wink @colchiro :D) should make a comprehensive guide on over clocking with a list of which kernels work with which ROMs. Only if they had time of course.
 
Guess you didn't see this: http://androidforums.com/nookcolor-all-things-root/357971-noob-questions.html#post2841862 :D

You don't need an overclock app with CM7, just go into settings and find CyangenMod settings. Phiremod renames that to Phiremod settings. Maybe your app is what locked your Nook? OTOH, not all cpu's like the extra speed.

Rooted stock 1.2 and Froyo also have their own OC kernels, and I suppose a Nook Color settings for changing them, but that's a guess since I don't run stock rom, even if it's overclocked. :D
 
Colchiro- You are a genius. Holding the N key for 5 seconds longer did the trick, was able to boot into CWR 2 out of 3 tries.

Ok, so now on to the kernel. I am confident my ROM is a .29. I am confident I have the appropriate dalingrin kernel. Here are my suspects.

Both times before, I did not uncheck "set on boot" in SetCPU
Both times I did not wipe anything, just did a straight install of the .zip (i did not unzip it)

Would either of those things be the culprit?
 
A general rule is to always uncheck 'set on boot' in SetCPU until you're SURE that the settings work for your device. If, for instance, the high setting is too high your device may go into a boot loop - and because you can't get to SetCPU you can't easily fix it. (Sound familiar? :) )

The following are instructions from Dalingren's kernel page, you should probably perform the wipes he recommends, in the way that he recommends them (not through ROM Manager).


If you have problems with force closing apps or poor performance, clear the dalvik cache and regular cache. DO NOT use the Rom Manager option to wipe data and cache. You do not want to wipe data. Just boot into CWR and wipe cache, then under advanced wipe dalvik cache.
Note that the first boot after clearing the caches will take longer than normal.
 
Yep, SETCPU was the culprit. So, now I got the kernel installed, reboots fine but its only 300/600/800/1200/1300 and I cant use 1200 (instant freeze). I thought dalgrins was 300/600/800/1100/1200, I was hoping to try the 1100. Guess I need to find a different kernel.

Are there any kernels out there that have 1000 and 1100 options that work on .29? I am starting to think I should plunge into a CM7.1.
 
Because you don't have 'set on boot' set, the settings in SetCPU aren't really doing anything, you'll need to go into SetCPU to make them 'work'. After that, until the next reboot your system is working using the SetCPU settings.

However, if I'm reading what you wrote correctly, it doesn't make sense.
If a high setting of 1200 locks your system then 1300 certainly should! You shouldn't be able to go 'up' from a problem setting and have the problem go away.
Basically what you do is play with the SetCPU settings until you find the highest speed that your system can maintain without having problems (Give it at least a day between reboots. Sometimes problems are slow to show themselves). After you've found your system's upper level you can select 'set on boot' without a problem. If, for instance, your system is OK at 1100 then a high setting of 1100 or anything lower will be OK.
 
So far I know 925mhz is stable and 1200 is instant crash, need to find a kernel with 1000 and 1100 options that works with CM 7.0.3 stable.

Update: Been doing some crude googling and such, is there anyone who makes kernels other than dalgrin?
 
Ok, since I was having such a hard time. I decided to ditch 7.0.3 and go for nightlies. Not only did 1100mhz work, so does 1200mhz. Quadrant scores (i know its not a good test) are through the roof and if feels much smoother. So far my only complaint is my wifi isn't working with the router at work. Woot!
 
Im probably late and everybody might know this already but there is a boot menu now. I am on one of the cm7 nightlies and when you power up the nook press and hold the n button as soon as you see the green cyanogenmod logo it will take you to blue boot menu. There you can chose to boot into recovery, boot off the sd card or emmc. This way if don't have a bootable CWR sd card handy and stuck in a boot loop you can get into recovery. Hope this helps somebody out there.
 
Doesn't help me. :D

No matter what I select, it does nothing. I can choose eMMC or Recovery then drop down to the third item and press "n" and it says it's booting, but never leaves that screen.

Not a big surprise tho b/c previous menus didn't work for me either.
 
You must log in or register to reply here.
Back
Top Bottom