I am running CM-7.0.3 on sd. I have been trying to add OC kernel. I have tried several including, update-CM7-dalingrin-OC-sd-042411ext4, update-CM7-dalingrin-OC-sd-052311 and update-CM7-dalingrin-OC-sd-060911. I unzip the file and copy the uImage file to the sd card. When I reboot with the new kernel, it sys "loading", then the screen flashes, then goes black. I can copy the original uImage file back to the sd card and it works fine. I guess I should leave well enough alone, but it is bugging me that I can not get it too work. What am I doing wrong?
Which kernel should I use and how can I get it to load?
Thanks for any help.
I haven't flashed anything on my nook for a while, let alone a new kernel, but I don't believe you should be unzipping the file once downloaded. You should be able to download it straight on your nook, navigate to it through clockwork recovery, flash it, then reboot, and you should be good. There might need to be some wiping of cache and/or dalvik cache too, but I don't remember 100%
steve13 said:
I haven't flashed anything on my nook for a while, let alone a new kernel, but I don't believe you should be unzipping the file once downloaded. You should be able to download it straight on your nook, navigate to it through clockwork recovery, flash it, then reboot, and you should be good. There might need to be some wiping of cache and/or dalvik cache too, but I don't remember 100%
Click to expand...
Click to collapse
yup or flash it through Rom manager.
I tried flashing the zip. When it rebooted it would not load. I had to totally start over and reload everything. When, before or after flash, and how do you clear the cache and/or dalvik cache? I do not want to start over again.
Thanks
All three kernels that you have tried are not intented to be used on CM 7.0.3; In order to use any of those, you need to be running at least nighty 88. THis is due to the fact that these kernels are based on a newer build (.32), and CM7 had to be updated as well.
As it is, you really owe it to yourself to update to nightly 98, as alot of improvements have been added since 7.0.3...
Thanks for the reply s.
For those of you who are using CM-7.0.3 on a SD card, which OC are you using how did you get it to work?
Just get one of the archived ones Dal has (4/04 one?)
ace7196 said:
Just get one of the archived ones Dal has (4/04 one?)
Click to expand...
Click to collapse
At this point, he would be better off upgrading CM7...
Divine_Madcat said:
All three kernels that you have tried are not intented to be used on CM 7.0.3; In order to use any of those, you need to be running at least nighty 88. THis is due to the fact that these kernels are based on a newer build (.32), and CM7 had to be updated as well.
As it is, you really owe it to yourself to update to nightly 98, as alot of improvements have been added since 7.0.3...
Click to expand...
Click to collapse
I tried that but found I had a problem with WIFI. Have to reboot after waking up from battery charging.
I have been using 0404 with my CM 7.0.3
Related
Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim
Jimbo67 said:
Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim
Click to expand...
Click to collapse
Jim,
This question's been answered in other threads already, but here's the link to the one specifically regarding this problem. I included it in your response to this question on the other thread as well. Good luck....
http://forum.xda-developers.com/showthread.php?t=1068309
What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?
Jimbo67 said:
What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?
Click to expand...
Click to collapse
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.
First things first..... Don't panic. LOL
1. Power down.
2. Power up holding both the power button & the n button for 6 seconds.
Does that get you to recovery?
hockeyfamily737 said:
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.
Click to expand...
Click to collapse
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!
Jimbo67 said:
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!
Click to expand...
Click to collapse
First try booting into your EMMC recovery the way I just posted ( power & n button for 6 seconds).
If that works.... do a full wipe and restore your backup of 7.0.2 stable.
It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!
Jimbo67 said:
It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!
Click to expand...
Click to collapse
Ok.....Now it's time to use your recover SD. Put it in, boot to recover and do a full wipe (System, Data, Cache, & Dalvik). Then reflash CM7.0.2. When you're done and booted into CM7, report back for follow up instructions, so this doesn't happen to you again.
Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!
Jimbo67 said:
Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!
Click to expand...
Click to collapse
Yeah that's perfectly normal. Hard shutdown and boot right back to recovery. Flash the rom and gapps (no OC kernel yet....I'll explain once you're up and running again).
Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!
Jimbo67 said:
Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!
Click to expand...
Click to collapse
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent CWM update requires the use of a kernel with an updated ext.4 script, explained in the following link.......http://forum.xda-developers.com/showthread.php?t=925451&page=239
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik) for safety's sake.
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab
just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"
Jimbo67 said:
just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"
Click to expand...
Click to collapse
I'd wait on 7.0.3 to see what's up with it..... Some people were reporting the MD5 sums not matching. Stick with 7.0.2, follow the threads to see what's up with any rom you run, and then once you know all's well (from reading the posts).....then flash the update. Keep in mind it's always easier to read first and flash after, then to freak out thinking you bricked your device and spend 2 hours in a panic trying to fix it.
For the OC kernel boot into recovery (the one you should have flashed to EMMC from Rom Manager), and flash the 4/24 kernel with the updated script for ext. 4
hockeyfamily737 said:
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent nightly builds are Android 2.3.4 and require and ext 4 kernel..... available here in post 2382 of this thread......http://forum.xda-developers.com/showthread.php?t=925451&page=239
The stable builds are Android 2.3.3 which require the kernel you have been using right along (prob. the 4/24 1.3 GHz).
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik).
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab
Click to expand...
Click to collapse
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!
Jimbo67 said:
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!
Click to expand...
Click to collapse
http://www.unvisible.org/files/ext4-...mmc-042411.zip
Here you go.
My boot went corrupt with CM 7.0.2. I was able to restore to stock with no problem, but everytime I attempt to install CM 7 (stable or nightly), I get a black screen except for a little white/light blue line in the upper right corner.
I use the 3.0.0.5 Recovery with the directions in the following link.
http://forum.xda-developers.com/showthread.php?t=949699
Does anyone have an idea why this happens? I do remove the SD recovery card, and insert a blank SD card before rebooting.
Any help would be much appreciated!
Use 3.0.2.8 recovery
Thanks, I'll give that a shot right quick.
NewZJ said:
Use 3.0.2.8 recovery
Click to expand...
Click to collapse
Tried it and it boots back to the black screen with the line in the upper right corner.
Here's what I did.
Made the bootable sd card, copied over lastest build of cm7 and gapps.
Installed zips.
wiped data.
switch sd cards, rebooted
also tried it w/o wiping data.
Is there anything I'm doing wrong?
Wiping cache?
NewZJ said:
Wiping cache?
Click to expand...
Click to collapse
Should I do that before or after installing the zips?
wipe system, data, cache, then flash zips
NewZJ said:
wipe system, data, cache, then flash zips
Click to expand...
Click to collapse
Just tried that, no dice. It's still going back to the same screen.
Download the cm7 again, might be corrupt
NewZJ said:
Download the cm7 again, might be corrupt
Click to expand...
Click to collapse
Just downloaded a stable release, and it works. Is there any reason why the Nightly 80 wouldn't work, even after re-downloading it?
I'm also dealing with the same issue as well. The problem started when I tried to update from nightly 76 to 77. I also tried to flash to nightly 80, but no luck. I'm flashing a stable release now.
Edit: Flashing the stable release also worked for me. However, I wasn't able to flash the latest nightly over the stable build.
Yep.
Same problem here.
The stable works, boots fine, but the nightlies won't boot.
They go into the same flashing blue line.
I tried all the advice I could find, wipe system, cache, data and tried restoring to stock, still no dice.
I am using CWM 3.0.2.8.
I'm just a different flash method (verygreen's SD install), but found that nightlies beyond 75 won't boot without installing the .32 OC kernel. There's a discussion in both cyanogenmod experimental nook forum and in the dev forum here about it.
I guess I'll just wait until they resolve the issue then. I was really wanting to see how well the deep sleep worked.
Finally got the latest nightly from today with OC kernel and gapps. Running great so far. Just waiting on market being able to download.
I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!
1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?
andythegreenguy said:
1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?
Click to expand...
Click to collapse
1) no other tweaks. Just put Fresh 2.4 on and started using it.
2) In the ROM Manager I backed up after flashing to ClockworkMod. I've used that backup to get my phone working again. I also checked the boxes to wipe everything as I told it to install cyanogen from the SD card. I've also tried booting to recovery manually and scrolling to wipe/restore to factory before trying to install cyanogen from zip.
Make sure you wipe EVERYTHING
YoungSinema said:
Make sure you wipe EVERYTHING
Click to expand...
Click to collapse
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.
tunafishman said:
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.
Click to expand...
Click to collapse
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
Yup. Id agree.
#Root/Hack-Mod_Always*
MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
I've downloaded 7.0.3 twice and also 7.0.0 just for fun. All through my home internet onto a macbook pro and transferred via USB to the SD card.
I'll try again and make sure to only use the manual recovery. Also, thanks for the aosp suggestion!
It's a no-go on everything.
Formatted boot, system, data, and cache. Wiped dalvik cache and battery stats. Tried to install a fresh copy of CM7 and also tried AOSP 2.3.4 with same steps.
The only thing that doesn't stall at the boot screen is my backup.
There must be something about versions that is wrong here. Something isn't playing nice.
Excuse me sir. Don't mean to but in here. But I think you missed the part were matt suggested you reflash your recovery. Its good advice. Whatever your current recovery is try reflashing it, repeat the necessary wipes and flash your rom of choice. You can reflash your recovery threw adb or if your s-off threw an hercimg.zip or if you have a nand you can boot into you can do it threw terminal or rom manger.
#Root/Hack-Mod_Always*
Personally I bootload to flash any recovery but also I'm s-off. Its extremely easy and all you have to do is rename the file and move it to the root of the SD card. Using terminal emulator is also very easy if your not s-off. If your still unsure about some of this just keep asking us. More than willing to help. Here ill make it a little easier. Go find the s-off thread and make it happen. Ill throw you my renamed version of green lantern recovery. Trust me it works perfect. Still clockwork. Just different. Then all youll have to do is bootload the recovery then reboot to recovery. And you already know how to do that.
1st go to that s-off link
Dropbox link to greenlantern
http://db.tt/ORAwPdX
The file is named
greenlanternHERCIMG.zip, just delete the greenlatern part and it's good to go.
Heres the s-off thread. All you need is the zip in the bottom of the op. Then flash it through manual recovery as always now
Get the recovery working first then we can help fix the flashing rom if it continues
http://forum.xda-developers.com/showthread.php?t=759955
*I use bootloader just to be a dork really and watch it load for that 2 seconds it takes then reboot, but who's phone doesn't like a reboot .. honestly.
®patience is a virtue©
did the same thing bro
noob here
nandroid, nandroid , nandroid,,,got it?
wipe data,
wipe cashe,
wipe dalvic,
the only thing I do different sometimes ( when having trouble flashing)
format data,
formet cashe,
format system,
flash rom and enjoy
Learned this from a Dev that used to be here but is gone now. dont know why it works but it does.hope it helps
Update? Be nice to know what's happened
®patience is a virtue©
tunafishman said:
I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!
Click to expand...
Click to collapse
Try Using the Firerats Tweek for the Low Space Issue!
As for the other Issue Firerats may Also Fix that Problem!
*Sent on My*
Fast as its Ever Been....
"Sprint" Hero.... Running My, *ExEnHeroC* Rom, w/Kifno's Twist, Also The XDA-BLUE.apk!! "Page 10" of My Thread!!
http://forum.xda-developers.com/showthread.php?t=957867
http://www.megaupload.com/?d=WTMLMK6M
http://www.mediafire.com/?bb1axugm0bw7oro
http://m.youtube.com/index?desktop_uri=/&gl=US#/profile?user=PMGRANDS
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.
Hi everyone. I'm new to the touch pad, but I have a lot of experience with the Epic4G from Sprint using CWM and flashing zip files. I have preware installed in my webos, and I have CM9 installed as well.
I've spent a few days reading threads here, but haven't been able to flash anything. I think I must be missing something.
Nothing happens when I flash zip files in CWM. I reboot to recovery, flash the zip file, wipe caches, but nothing is changed when I reboot the system. Been trying to install the unofficial with the working camera, and the oc kernel.
Thanks for any help.
sent from a secret underground bunker
mjben said:
Hi everyone. I'm new to the touch pad, but I have a lot of experience with the Epic4G from Sprint using CWM and flashing zip files. I have preware installed in my webos, and I have CM9 installed as well.
I've spent a few days reading threads here, but haven't been able to flash anything. I think I must be missing something.
Nothing happens when I flash zip files in CWM. I reboot to recovery, flash the zip file, wipe caches, but nothing is changed when I reboot the system. Been trying to install the unofficial with the working camera, and the oc kernel.
Thanks for any help.
sent from a secret underground bunker
Click to expand...
Click to collapse
Did you check md5s on the zips? Also, is your recovery updated?
As soon as I post a request for help, it works. Of course. Lol.
Yeah, I'm not sure what worked this time, but since I posted previously I set manual flash override in ROM Manager and installed the CM9 unofficial preview 7, the preview 9 update, and gapps, all went. I also installed the kernel that I mentioned, but it got stuck in a boot loop after and had to do the ROM over again.
sent from a secret underground bunker