I flashed a froyo 1100 kernel. Now the nc starts gets to the lockscreen then either restarts or lets me unlock and powers off. I made a cwm backup right before but it doesnt give enough time to get to cwm.
am I screwed?
You need to make a bootable CWM sd card with the stock kernel on it (available in the same thread you got the OC kernel from) and flash it. Perhaps your nook is one of the few that just can't handle the 1.1ghz OC. Or, If you're really gun-ho about overclocking it, I would try redownloading and reflashing the OC kernel. It may have been either a bad download or flash.
Ok, found out holding the N and power allowed me to restore my backup. Then found another kernel that actually worked. Now if i could only find the bes browser, this thing would be perfect.
Dolphin Mini is awesome on my DX. Dolphin HD is ok too.
Some like Xscope.
I kinda liked opera mobile and firefox is cool but no flash support yet
Related
Having an issue with retaining my oc' in CM7/Phiremod. I have Dalingrin's Froyo/CM7 eMMC kernel flashed. In CM7 under CyanogenMod Settings I can choose 1000/1100 and everything runs fine, however when I reboot it does not retain the OC'. It reverts back to 800mhz default. This is with "Set on Boot" Checked or unchecked.
Can anyone comment on this? Thanks guys.
Wasn't have luck in any of the other threads. Figured I would try this here.
are you using the 2/23/11 oc kernel or an older one?
Did you flash the OC using the CWM on the sd card, or flash via Rom manager's CWM? It needs to be flashed via CWM on the ext4 sd card that you used to flash phiremod.
I've had no issues OC'ing this way...
Sent from my DX to the interwebs
ataprime said:
are you using the 2/23/11 oc kernel or an older one?
Click to expand...
Click to collapse
I am using the latest 022311.
C Dippa said:
Did you flash the OC using the CWM on the sd card, or flash via Rom manager's CWM?
Click to expand...
Click to collapse
I used thecubed's ext4 bootable CWM SD card to flash the kernel.
I can OC the nook just fine. It runs stable at 1000/1100. However when I reboot it, it reverts back to stock clocking.
bump up...
Anyone else having issues with oc'ing their nook?
no problems
ive been running the overclock kernel for about 24 hours now and i havnt had any major problems. only rebooted on me once but other than that all good. maybe try flashing the kernel again...
I'm having some random reboots with this kernel but otherwise the setting persists after reboot.
I flashed dalingrin's OC kernel for my NC running rooted stock 2.1. CWR said the flash was successful but when I open SetCPU the slider will only go up to 800. It won't let me overclock past that value. Can anyone help me troubleshoot this so I can ramp things up a little bit. Is there a way to check the files with Root Explorer to see if the kernel "took"? Thanks.
Ok I figured it out on my own. I went into the Rom manager app and pressed 'Flash ClockworkMod Recovery' and the option came up for either Nook Color (old) or NookColor. I had read in another thread to chose the old version (which I had done first) but "nemith" here on XDA said to always pick the one that says NookColor. So I flashed that one, rebooted into Recovery, wiped the dalvik and cache, and flashed the OC kernel .zip again and voila!, I can now overclock up to 1100.
Did you read the bit that said clockwork recovery won't work for backups if you flash it through ROM Manager?
You probably want the flashable clockwork recovery from here, so that you can make backups, etc?
http://forum.xda-developers.com/showthread.php?t=971197
Sent from my Nexus One using XDA Premium App
im running the stable version of CM7 and i flashed the oc kernel for CM7 and when i went to reboot it i got stuck in a bootloop! please help me!
when you moved from the nookie comb to cm7, there are two things you absolutely must have done:
1. made sure you flashed cm7 using an ext4 clockwork mod example 3.0.0.6
2. made sure you formatted system, data and cache. all three are a must.
having said that, some people have been stuck on the cm7 bootscreen for as much as 20 mins before it loaded. hope that isnt the case here as mine always loads within two mins during the first boot.
dpakrr said:
when you moved from the nookie comb to cm7, there are two things you absolutely must have done:
1. made sure you flashed cm7 using an ext4 clockwork mod example 3.0.0.6
2. made sure you formatted system, data and cache. all three are a must.
having said that, some people have been stuck on the cm7 bootscreen for as much as 20 mins before it loaded. hope that isnt the case here as mine always loads within two mins during the first boot.
Click to expand...
Click to collapse
i did, i was running cm7 for an hour then tried to flash the kernel. should i reflash cm7?
Which kernel did u flashed and is it designed for Desire? Try flashing another kernel maybe
Sent from my HTC Desire using XDA App
no dont reflash cm7. just force shut down and boot into recovery and make sure you flashed the proper kernel.
should have been this one (assuming u have cm7 on your emmc).
http://nook.handhelds.ru/dalingrin/kernels/040411/update-CM7-dalingrin-OC-emmc-040411.zip
flash that. if it still bootloops then reflash cm7 and flash the kernel right after
dpakrr said:
no dont reflash cm7. just force shut down and boot into recovery and make sure you flashed the proper kernel.
should have been this one (assuming u have cm7 on your emmc).
http://nook.handhelds.ru/dalingrin/kernels/040411/update-CM7-dalingrin-OC-emmc-040411.zip
flash that. if it still bootloops then reflash cm7 and flash the kernel right after
Click to expand...
Click to collapse
alright will try this
Edit: no luck. time to reflash...
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.
Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
samcool55 said:
Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
Click to expand...
Click to collapse
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
rog_star said:
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
Click to expand...
Click to collapse
Tried that, but UKF says device unsupported, don't know why... I have used it before and it worked then.
Any other options?
I got it fixed. But tbh i still don't understand how. I flashed JB stock with odin and when it rebooted, i got automaticly into CWM weirdly enough... Wasn't going to waste my maybe only chance so i flashed the custom rom, wiped everything again, reboot, went again automaticly into CWM. anyway i was third time lucky and it booted as it should. Everything is working now! Anyway thanks for trying to help.