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...
Related
I tried to install CM7 right out of the box and now I have read and tried every option to try to get my nook back to at least stock.
I'm coming from the Nexus S scene where a good fresh nandroid back up work like a charm.
I'm thinking it might not be so easy with my nook color, but I figured it's worth a shot.
If any one has a nandroid back up stock or a fresh CM7 install, I would love to give it a try because the only thing I can do with my nook is boot into Clockwork from an SD card!!!!!
Any help would be great, I have been reading an searching, maybe I'm just missing something.
What?
You're crazy.
Use and SD image of clockwork.
Download CM7, gapps, OC'd kernel to it
format system, data, cache.
Flash CM7, gapps, OC'd kernel.
Reboot.
kmmxracer said:
I tried to install CM7 right out of the box and now I have read and tried every option to try to get my nook back to at least stock.
I'm coming from the Nexus S scene where a good fresh nandroid back up work like a charm.
I'm thinking it might not be so easy with my nook color, but I figured it's worth a shot.
If any one has a nandroid back up stock or a fresh CM7 install, I would love to give it a try because the only thing I can do with my nook is boot into Clockwork from an SD card!!!!!
Any help would be great, I have been reading an searching, maybe I'm just missing something.[/QUOTE/]
You have a couple of options. You can flash the latest nightly from recovery using your sd card follow instructions for that.(must use 3.0.1.0). Remove the card before you reboot. Also, if you want clockwork internally, grab the 3.0.1.0 from the link below and flash it with your sd card, then the rom. If you are flashing something stock, you would need to use clockwork 3.0.0.5.
forum.xda-developers.com/showthread.php?t=958748
Click to expand...
Click to collapse
ace7196 said:
What?
You're crazy.
Use and SD image of clockwork.
Download CM7, gapps, OC'd kernel to it
format boot, system, data, cache.
Flash CM7, gapps, OC'd kernel.
Reboot.
Click to expand...
Click to collapse
Do NOT NOT NOT format /boot while prepping for CM7 installation!!!
RoboRay said:
Do NOT NOT NOT format /boot while prepping for CM7 installation!!!
Click to expand...
Click to collapse
Hehe. My bad. Came from formatting my gf's Gtab. Had to do it to get 2.3 AOSP on there.
bdcrim said:
kmmxracer said:
I tried to install CM7 right out of the box and now I have read and tried every option to try to get my nook back to at least stock.
I'm coming from the Nexus S scene where a good fresh nandroid back up work like a charm.
I'm thinking it might not be so easy with my nook color, but I figured it's worth a shot.
If any one has a nandroid back up stock or a fresh CM7 install, I would love to give it a try because the only thing I can do with my nook is boot into Clockwork from an SD card!!!!!
Any help would be great, I have been reading an searching, maybe I'm just missing something.[/QUOTE/]
You have a couple of options. You can flash the latest nightly from recovery using your sd card follow instructions for that.(must use 3.0.1.0). Remove the card before you reboot. Also, if you want clockwork internally, grab the 3.0.1.0 from the link below and flash it with your sd card, then the rom. If you are flashing something stock, you would need to use clockwork 3.0.0.5.
forum.xda-developers.com/showthread.php?t=958748
Click to expand...
Click to collapse
Thank you. Sorry for the delay but I'm sure the problem was I was following a guide that linked and old version of Clockwork.
It all worked perfect once I had 3.0.1.0
Click to expand...
Click to collapse
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
+1 get clockwork recovery...you need to make sure the rom you are flashing is compatible with the version of CWR you are using.
For example a rom that needs to be installed with CWR3 you will need to install the zip presumably from CWR2. Pull the battery and reboot back to recovery - you should now be in the updated version of CWR. Then for safety sake - re install your zip.
Reboot and you should be all set.
I had lots of trouble going from 2.2 to 2.3. Flashing between 2.3 roms is very easy comparatively
milkytron said:
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
pwnerman said:
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
Click to expand...
Click to collapse
I did have the bootloaders, I went back to stock before I did anything just to be safe. I'm gonna try what the other guys said though right now, wish me luck haha
jmtheiss said:
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
Click to expand...
Click to collapse
Alright so I have Andromeda 2.1 which is a froyo rom. Which method should I use to get to stock GB?
use Odin to flash gingerbread bootloaders then flash gingerbread roms
howtomen said:
use Odin to flash gingerbread bootloaders then flash gingerbread roms
Click to expand...
Click to collapse
I flashed the gingerbread stock rom and have it rooted with xcal's kernel, but when i flashed mosaic IV it got stuck at formatting partitions and i pulled the battery after about 15 minutes and then restarted my phone to find it stuck in a bootloop. So i had to start from stock again and now im back to gingerbread stock with root. I'm kinda scared to try again because it takes me like 30 minutes to get back to gingerbread stock with root. I think ill just stick with stock for a little bit
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.
I tried to install the illuminance Rom last night, and it kept getting stuck at the ATT logo. I reflashed back to stock did a master clear, flashed a stock 2.3.5 uckj3 gingerbread Rom with corn kernel v307 also ATT gingerbread boot loaders. I used CWM to install the ROM, it'll restart then get stuck and get stuck at the ATT logo....is there something I'm missing? I've installed other ROM and have had no issues until now?!?!
If you used Corn kernel, are you sure you where on RFS format and not ex4?
it was rfs format before I tried to install
Did you make the file (don't remember exactly wich) that disable Voodoo. There is no reason for it to bootloop. After you flashed stock did you let it boot up? Maybe try with Boog kernel to flash then flash wich ever kernel you want to use?
I'll try the boog kernel.....I also ensured that the lagfix for system and data was disabled through CWM recovery ....in the install instructions it stated that it would take awhile to boot, I let it set for two hours. One thing I noticed is that 150 jpegs were installed
Sent from my SAMSUNG-SGH-I897 using xda premium
Doubt this might be it but, If you set it on CWM to disable lag fix reboot in cwm then flash. Random thought.
LOL....did that also.
Sent from my SAMSUNG-SGH-I897 using xda premium
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
lilbigdude1 said:
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
Click to expand...
Click to collapse
My boot getting stuck got fixed after Wipe data/factory reset in CWm, wipe cache, wipe Dalvik cache, - all three -then install illuminance. Tried that ? Starting from stock KJ3 no bootloaders.
Importantly: Can you boot with just Illuminance boog kernel (the one that comes wiht the ROM, no other kernel flashed)? I presume you cannot boot a fresh Illuminance install............if this is the case wiping as above should help.
I finally got illuminance to install, and is working great.
this may seem like over kill but everytime I flash a new ROM I start from scratch and flash to stock and master clear and then build from therethis is the first time that I ever had any issues by doing it this way. usually I have it setup up in 10 to 15 minutes it seems to save any issues later down the road as far as being buggy.
Glad to hear it
Hi, I tried to install Illuminance 1.1, but I think the file is corrupted. I downloaded it twice, from different locations, and its the same zip file.
I tried to decompress it before installing it, just to check file consistency, but lots of files canĀ“t be decompressed.
Anyone had this problem? If not, any way /any where to safely download it?
Thanks!
In the Illuminance Rom Thread, in the OP, there is a link to IlluminatedOne's website, where u can find a good non-corrupted download and u will also find the installation instructions.
Not sure why u think u had a corrupted download ?? But u should b good to go once u get to the website.
As of this version 1.1 release, u should only be downloading the Illuminance Rom from said website.
Sent from i897uckj3
I downloaded my version from Mega-upload. I tried it again last night just for...you know....and received the same results of being stuck on the att logo for hours. as usual i flashed to stock and master cleared, GB boot loaders, reinstalled stock 2.3.5 and reinstalled luminance and before i rebooted i installed the samurai kernel, then rebooted and everything worked as normal....so being fairly new to the whole Dev scene i don't know why that would make a difference, but it works fine and it didn't get stuck on the att logo.
oh and thanks twin I'll try and go to the website and check it out
Before I used CM10 i just used the stock (flashed latest GB) that came with my phone. So I flashed CWM5 and cleared all the three stuff I was supposed to. I installed the CM10 zip and since then its been stuck on the boot animation, not even a loop. Just the animation.
Any ideas whats wrong?
Thanks in advance
JellyBean 4.1.1 said:
Before I used CM10 i just used the stock (flashed latest GB) that came with my phone. So I flashed CWM5 and cleared all the three stuff I was supposed to. I installed the CM10 zip and since then its been stuck on the boot animation, not even a loop. Just the animation.
Any ideas whats wrong?
Thanks in advance
Click to expand...
Click to collapse
Well happened with me once when I had put AOKP ROM in my Galaxy Note.
Here is what I did:
Go to Recovery.
Wipe Cache.
Try reboot
No results?
Recovery again.
WIpe Dalvik Cache Also
Try reboot.
Still no results?
Try to wipe data/fac reset and re flash some other ROM as of now (which you are confident about that it will work)
Now go ahead and let the old ROM boot. (Surely it will, as you would have used prior)
Now, go connect USB and check MD5 of the file you had kept on SD Card (I mean the CM10 file)
I found that my MD5 didnt match.
If you think it didnt match download again.
If you know it matches then go for reflash.
But this time before flashing the new ROM just use some cleaning script such as Ultimate KErnel Cleaning Script. In Galaxy Note I used Jbroid Kernel Script. I aint sure now if you can use Jbroid in Ace.
Goof luck!
Press Thanks
I got it working, what I had to do was flash CM7, then CM9 then CM10 :/ after that it was fine Thanks for the help
Welcome
The problem was with the kernel being different in CM10 and official version.
realzahed said:
The problem was with the kernel being different in CM10 and official version.
Click to expand...
Click to collapse
Please ask CM9 and CM10 questions here:
http://forum.xda-developers.com/showthread.php?t=1742844