ROM Flashing and Kernel Flashing; Order of Operation? - Vibrant Q&A, Help & Troubleshooting

Hey guys, I've been flashing roms and kernals for a little while now and still I'm far from an expert. I've managed to brick my phone recover and do many other things from the help of this forums and I thank you. But I guess I never knew the answer to the following question.
Is it better to flash a rom then flash the kernel (Overstock, tigersblood etc) before loading the rom and waiting 10 mins or is it better to flash the rom, then load the rom wait ten mins or so then go back into CWM and flash the kernel and wait another 10 mins?
What makes for a more stable rom?

I always flash the rom, do a reboot recovery, flash the kernel then let the phone boot into android. Haven't had any issues.

Sdobron said:
I always flash the rom, do a reboot recovery, flash the kernel then let the phone boot into android. Haven't had any issues.
Click to expand...
Click to collapse
+1 same here rom first then kernel

Sdobron said:
I always flash the rom, do a reboot recovery, flash the kernel then let the phone boot into android. Haven't had any issues.
Click to expand...
Click to collapse
Flashing kernel first is dumb, because doesn't flashing the ROM replace the kernel????
Obviously.
1) Flash rom
2) any kernel if any at all
3) factory reset (depends on rom)
4) reboot
5) wait 10 minutes, and reboot and done.

I think he meant flash rom then flash kernel immediately or let rom boot, wait 10 then flash kernel...
Sent from my SGH-T959 using XDA App

You CAN flash the rom and then immediately do the kernel, BUT
I believe it is preferred/better to do the rom... let it sit for 10 minutes... reboot.... restore all your apps, reboot into recovery, flash the kernel, rejoice.
That is my preferred method.

Lol, this is a funny thread. But heres what i do.
- Flash ROM
- Boot (Let sit 15min) play blackops here
- Power off phone
- Power on phone
- Reboot recovery
- Flash kernel (usually OC)
- Restore setcpu
- OC system and begin restore process of titanium, sms, bookmarks and such.
Only reason i do this is personally i like to restore with the system OC but thats just me.
Sent from my SGH-T959 using XDA Premium App

Do you lose all settings/media on phone when flashing kernels like you do when you flash ROMs?

No you don't
Sent from my SGH-T959 using XDA App

Related

Real quick question that I can't figure out

OK, so it has been a while since I have had to flash recoveries etc... Anyway, I Odin'ed back to stock today because I had to go to the Verizon store to talk about my replacement phone so I wanted to have it unrooted. Anyway, now I am trying to get CM7 back on for the time being but I can't get in to CWM. I tried pushing the cwm_recovery_all tar file via ODIN and when I do the three finger boot, it still brings me to the stock recovery and when I hit apply update.zip it fails.
What the heck am I doing wrong? I figured I could just get recovery on there and not have to worry about "rooting" since all the ROM's have that built in anyway.
Any help is appreciated!
Nevermind, I think I figured it out
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Kevin Gossett said:
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Click to expand...
Click to collapse
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
xceebeex said:
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
Click to expand...
Click to collapse
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
efan450 said:
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
My point is that I was able to boot in to red recovery (2.5.1.x) BEFORE flashing any custom kernel. I understand that CM7 has a kernel built in, but I was able to boot in to both the red recovery and jt's cwm 4 fix (4.0.1.0) before flashing any ROMs/Kernels. I wasn't even rooted (flashing CM7 is what rooted me).
After re-reading what he wrote, the way he says it is correct. I must have read it wrong the first time. So I apologize for saying "Nope." For some reason I read it as if he was saying I had to flash a custom kernel before being able to boot in to any recovery. He is just saying that you can't let the phone fully boot after pushed the recovery (which is what I ended up doing in my steps).
Sorry for the confusion.
No problem...glad you didn't take offense I'm just nearly thinking of all the noobs that are just getting into this kind if stuff and when they read the thread they might be misinformed...
that being said I've been on cm7 for a while and I know not to flash with anything other than the included recovery, I can confirm power button menu gets you to the new blue recovery but if you three finger salute it (done on accident just out of habit) you will get to an older recovery! In my case the old red one....Weird having both on the phone simultaneously, but it's no prob as long as we only use the new recovery to flash anything.
Sent from my SCH-I500 using XDA App

Having many problems with Fascinate

I was sent a Fascinate as a Droid Incredible replacement. I was able to root it without a hitch but now my CWM can't mount anything. Won't mount anything can't bring up any logs. I am using the CM7 Clockwork and my phone is now bricked and I'm tired of using Odin to restore it and root it again then flash CWM and CM7, I lose all my games and free apps which I have to download again.
What am I doing wrong?
Also, are you using atlas.pit when odining to stock? After doing what does the phone stop working entirely (IE does the phone boot up CM7 and then brick, or can it not load CM7 at all)? Can you run stock without your phone breaking?
skafan2 said:
Also, are you using atlas.pit when odining to stock? After doing what does the phone stop working entirely (IE does the phone boot up CM7 and then brick, or can it not load CM7 at all)? Can you run stock without your phone breaking?
Click to expand...
Click to collapse
Yeah. I can work on stock just great.
What is the best rooting method to use if I plan on using CM7?
What I do is use Super One Click to root (http://forum.xda-developers.com/showthread.php?t=803682), then flash the custom CM7 CWM, and then flash CM7 in the custom recovery after wiping data, cache, and dalvik.
Use the CM7 from here: http://forum.xda-developers.com/showthread.php?t=1190668
Do I use the recovery in that thread? I've been using that one as well. I will re download the rom then.
Yes. Here are the exact steps from that thread after rooting with SuperOneClick:
Start with a rooted device (do not ask us how to do this).
Flash ClockworkMod Recovery attached to this post.
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Wipe Data! Seriously! Do it!
Install the ROM zip from sdcard
Install gapps package linked here (http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps)
Alright. Let me try that again now. I just put the Nightly #8 on my SDCARD
Flashed it through the recovery, it's at the Samsung logo now. I am going to leave it there for a bit and see if that changes.
Yeah. It's stuck at the logo. I reboot into recovery and I get the log errors. That's 6 Odin resets today.
Make sure you use atlas.pit when restoring to stock. If you are following those directions exactly, all I can say at this point is to try another ROM (maybe MIUI or OMGB) and see if that works, unless another poster wants to take a stab at this.
Yeah, I'm using the atlas 2.2.pit
I had it working yesterday but only if I flashed the rom using the orange recovery through ROM Manager. I might try that again.
Hyphnx said:
Alright. Let me try that again now. I just put the Nightly #8 on my SDCARD
Flashed it through the recovery, it's at the Samsung logo now. I am going to leave it there for a bit and see if that changes.
Click to expand...
Click to collapse
I think the nightly might be your problem?...my $.02...and there are a lot of extra steps but it works for me if I really can't get cm7 to load (I've done this more then once)
Odin eb01 with the atlas 2.2pit and reboot fully when odin is done.
Pull battery...Odin cwm 3/30 fix all..and when that's done, install battery and 3 finger salute into recovery....wipe everything and flash com rom 2.0 and reboot.
This is where you may have to try different recoveries, putting com rom on your phone gives you root, recovery and voodoo. So from here if your recovery doesn't properly flash cm7 you can simply pull the battery re odin a different recovery and try again, as long as you don't try to reboot the phone.
Make sure you are using the 7/17 build from, jt's pretty much official cm7 Thread, not the nightly. even if this is not what you want it should properly get you to mtd format, so another rom on an mtd build can just be flash the good old way.
I've had the cwm4.x.x.x work fine and then today it would not work after I flash a different kernel with out wiping anything...oops! I've had 3/30 fix all cwm give me the best results but even today would not work.
What did work was using the com rom recovery to flash times infinity's purple recovery zip...reboot recovery into the purple one, and then wipe everything and flash cm7 7/17...ugh finally! Once I was there just power button menu... reboot recovery to install gapps, and glitch. You could at this point wipe cache and dalvik and flash nightly if you wanted...hope some of this helps.
Sent from my SCH-I500 using XDA App
I've had the same problem tryin to flash all mtd based roms...it always sticks at the samsung logo when I three finger back to recovery. I get the error logs aswell...**** sucks lol. That's odining ed05, fully boot, odin cwm 4 fix for cm7, boot recovery, wipe data,cache, dalvick, install rom.zip, all for a samsung logo and log error lol. So instead of spending 5hrs trying to flash a rom, I spent 10min and flashed power wash ed05, works great!

[Q] Bricked Phone?

After installing the Bulletproof 2.4 rom i flashed kernal using flash kernal gui app and then restarted phone. Now phone only reboots into bootloader/recovery. Is there any possible fix? Thanks
Well you can reboot into recovery so why not just reflash the rom.
i did that and when i reboot phone after rom installation it just goes back to bootloader
Did you make a backup? If so restore it.
If you don't want to and want to continue to flash the rom, flash the kernel via easy kernel flasher twice while In bootloader. Then flash your rom in recovery, be sure to do a full wipe.
Sent from my HTC_Amaze_4G using XDA
thank you. i flashed the kernal twice and then installed the rom. Everything is back to normal. Thank you. Will i have to flash the kernal twice before every new rom installation? If so, why is that? Thanks again. I really appreciate the support

[Q] First time boot of cyanogen 9 taking 20+ minutes?

Just installed cyanogen 9 and started up my fun, and it's stuck on the boot screen. It's been looping the animation for a good 20-30 minutes now. Is this normal? Will it eventually stop and load up the OS? Should i reinstall the rom? I'm new to flashing roms, and honestly have no idea what to do.
I rooted the phone
installed mobile odin pro
flashed siyah v2.6.14
installed cyanogen 9 and gapps from recovery
started up the phone
like i said before, it's just looping the cyanogen mod 9 animation.
HELP!
csworldfan said:
Just installed cyanogen 9 and started up my fun, and it's stuck on the boot screen. It's been looping the animation for a good 20-30 minutes now. Is this normal? Will it eventually stop and load up the OS? Should i reinstall the rom? I'm new to flashing roms, and honestly have no idea what to do.
I rooted the phone
installed mobile odin pro
flashed siyah v2.6.14
installed cyanogen 9 and gapps from recovery
started up the phone
like i said before, it's just looping the cyanogen mod 9 animation.
HELP!
Click to expand...
Click to collapse
Did u use stock recovery or cwm? I hope read the stickies before u did anything
Sent from my SGH-I777 using XDA
Did you press wipe data/ factory reset in recovery? That'll do it.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Same thing happened to me. Install cyonagenmod9zip using CWM you have to do it 2 times in a row then do a factory reset and reboot the phone. After the reboot go into CWM mode and install the Googlezip apps and reboot sys againg.
Good luck and enjoy.
brandonarev said:
Did u use stock recovery or cwm? I hope read the stickies before u did anything
Click to expand...
Click to collapse
And how exactly could he use stock recovery after flashing Siyah? Clearly he read the stickies.
Pro tip:
- Don't try to say something authoritative if you don't really, really know what you're talking about.
OP, did you wipe data AFTER flashing ROM???
Thanks everyone for the help, i managed to get it up and running. I think I forgot to wipe after I installed everything.
csworldfan said:
flashed siyah v2.6.14
Click to expand...
Click to collapse
Did NONE of you notice he said "Siyah 2.6.14"? This is the reason you are getting bootloops. That is a Gingerbread kernel. You need Siyah version 3.x.x for an ICS ROM as it is an ICS kernel.

[RECOVERY][06.27.12] Three finger bootloop breaker [CWM4, CWM5 & CWM6]

I really don't know who to credit for this, so if your reading this Credits to you! Koush & CM obviously too!
I repacked CWM4 & CWM5 to solve the three finger recovery loop dilemma...
Flash cwm4-repack after each ROM flash to solve the three finger boot loop issue.
If you three fingered and need to flash a CM7 based ROM, you can simply wipe data and proceed to flash. If you need to flash a CM9 based ROM, simply flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM9 ROM. (Always Remember to flash cwm4-repack directly after to break the recovery loop..)
When you reboot it may take you to recovery, just choose reboot now and your ROM should continue booting!
With these two zips and your chosen ROM, you should be able to flash on the go again without fear or break your existing install!
Update:
It seems most of the newer CM7 builds will require the same procedure as flashing a CM9 ROM.. (flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM7 rom...)(Always Remember to flash cwm4-repack directly after to break the recovery loop..)
I have not tested any of the above combinations with twrp! Use at your own Risk! I also recall twrp having something about an injection feature of some kind that may be useful for that...
06/27/12
How to use these to upgrade from stock/rooted stock to ICS Rom of choice!
If pure stock you obviously need a CWM recovery installed so odin/heimdall cwm all or cwm4 fix!
Reboot recovery
wipe data
flash cwm4fix-no_assert
reboot
wait until samsung logo blinks, then pull battery
three finger into recovery
wipe again to be safe
install ICS Rom of choice
It will reboot twice, once to update recovery and proceed installing and once more when it's done!
09/30/12 (Mainly a JellyBean reference)
Easily switch between ROMS and the different partition layouts!
Reboot to recovery and flash cwm4-fix, power the phone down (might need to pull battery) and three finger back into recovery!
Wipe data, flash chosen GB,ICS, or any partion JB ROM from any order! (ie: downgrade or upgrade)
cwm4-repack Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)
cwm4-repack no asserts Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)(Allows force flashing)
aokp-cm9-recovery Contents:
Latest source built CWM Based 5.5.0.4 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
cwm6_recovery Contents:
Latest source built CWM Based 6.0.1.0 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery 4.50 MB - 06/06/12
cwm4-repack 5.83 MB - 06/06/12
cwm4-repack no asserts 5.83 MB - 06/27/12
cwm6-recovery (JB) - 5.15 MB - 07/29/2012
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Sent from my SCH-I500 using Tapatalk 2
sageDieu said:
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Click to expand...
Click to collapse
If you download, power off, three finger and flash cwm4-repack and reboot it should break the boot loop and continue booting your ROM (However sometimes when updating the recovery it will automatically reboot to recovery, reboot now if this happens). Assuming ICS...
Also if you power down, three finger, do nothing and reboot, your phone will actually reboot! Assuming you already flashed cwm4-repack...
Not to sound dirty but I was three fingering all day while doing yard work...
Back n forth from CM7,CM9 & AOKP Based!
notta said:
I really don't know who to credit for this, so if your reading this Credits to you! CM obviously too!
I repacked CWM4 & CWM5 to solve the three finger recovery loop dilemma...
Flash cwm4-repack after each ROM flash to solve the three finger boot loop issue.
If you three fingered and need to flash a CM7 based ROM, you can simply wipe data and proceed to flash. If you need to flash a CM9 based ROM, simply flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM9 ROM. (Always Remember to flash cwm4-repack directly after to break the recovery loop..)
When you reboot it may take you to recovery, just choose reboot now and your ROM should continue booting!
With these two zips and your chosen ROM, you should be able to flash on the go again without fear or break your existing install!
Update:
It seems most of the newer CM7 builds will require the same procedure as flashing a CM9 ROM.. (flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM7 rom...)(Always Remember to flash cwm4-repack directly after to break the recovery loop..)
I have not tested any of the above combinations with twrp! Use at your own Risk! I also recall twrp having something about an injection feature of some kind that may be useful for that...
cwm4-repack Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery Contents:
Latest source built CWM Based 5.5.0.4 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery 4.50 MB - 06/06/12
cwm4-repack 5.83 MB - 06/06/12
Click to expand...
Click to collapse
This is great....thanks. I'll give this a try on TWRP later (when I have access to ODIN just in case).
Nice dude! that's nice to keep on the Sd card.
Sent from my Glitched AOKP Unicorn.
will be sure to keep these on my sd card had to go back to stock to get out of the that boot loop it was horrible when i close my eyes i can still see images touchwiz
tetrismonkey said:
will be sure to keep these on my sd card had to go back to stock to get out of the that boot loop it was horrible when i close my eyes i can still see images touchwiz
Click to expand...
Click to collapse
The horror...
Sent from my Glitched AOKP Unicorn.
sageDieu said:
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
jmac9 said:
This is great....thanks. I'll give this a try on TWRP later (when I have access to ODIN just in case).
Click to expand...
Click to collapse
So am I to assume all is well with both scenarios...
notta said:
So am I to assume all is well with both scenarios...
Click to expand...
Click to collapse
Sorry....never went back to twrp. With the new devil kernal, I've been playing too much to want to try anything different. On a side note, I went back to the glitch kernal this morning (experiment) and had issues with trying to get the Rom to load and then actually had to go the three fingered route. This worked great once I followed your directions EXACTLY!
Note to anyone else.....if you are flashing a Rom that requires gapps, make sure you flash the cwm-4 repack right after the Rom....BEFORE the gapps. Loop doesn't break if you try to slip the gapps in there too soon I found.
WOW this will be super helpful.
what does it take to compile roms to be installed via CWM 4 or CWM 5 ?
SeatownGST said:
WOW this will be super helpful.
what does it take to compile roms to be installed via CWM 4 or CWM 5 ?
Click to expand...
Click to collapse
Not sure exactly what your asking but typically you would compile cm7 for cwm4 and cm9 for cwm5!
Or the answer for exactly how I read this:
A computer, some time and some knowledge...
notta said:
06/27/12
How to use these to upgrade from stock/rooted stock to ICS Rom of choice!
If pure stock you obviously need a CWM recovery installed so odin/heimdall cwm all or cwm4 fix!
Reboot recovery
wipe data
flash cwm4fix-no_assert
reboot
wait until samsung logo blinks, then pull battery
three finger into recovery
wipe again to be safe
install ICS Rom of choice
It will reboot twice, once to update recovery and proceed installing and once more when it's done!
Click to expand...
Click to collapse
It doesn't work for latest AOKP. Bootloops on samsung logo after flashing rom. I've had to go back and do it like always (CM9 b2 first).
SotYPL said:
It doesn't work for latest AOKP. Bootloops on samsung logo after flashing rom. I've had to go back and do it like always (CM9 b2 first).
Click to expand...
Click to collapse
Well, my apologies for mis-leading. However I did just repeat the above steps exactly, coming from Geewiz EH03 to a today built build 40! Perhaps a limitation against pure stock?
If this was stock and you are put in the position again, you could try flashing a non stock kernel after a odin/heimdall of cwm of course! I suppose this could be an issue... Maybe?
so, I've been searching around and apparently haven't found the right search term.
Why does the 3 finger boot screw things up in cwm 5?
How does one cold start into the recovery? I finally got ics on my trusty fascinate.
Sent from my SGH-T989 using Tapatalk 2
Izeltokatl said:
so, I've been searching around and apparently haven't found the right search term.
Why does the 3 finger boot screw things up in cwm 5?
How does one cold start into the recovery? I finally got ics on my trusty fascinate.
Click to expand...
Click to collapse
I'm not really sure! I was going to attempt a look but a short search came up empty for some older sources.
Speaking of, they need a smiley that is bashing his head against a wall in shame..
Clearly, Credits for this go to Koush! (And queue the above mentioned smiley)
notta said:
Not to sound dirty but I was three fingering all day while doing yard work...
Click to expand...
Click to collapse
LMAO!! Nice! And good guide btw, I still have no idea why three fingering does that :/
Sent from my SCH-I500(Fascinate)
It seems with the recovery wipe repack method, i get all the way to the point of the rom booting up, but it will just sit there and play the boot animation over and over and over.... how long is it supposed to take? I'm beginning to think i'm going to have to odin... ugh!
notta, you needta update this to cwm6 for jb, please & ty
ztotherad said:
notta, you needta update this to cwm6 for jb, please & ty
Click to expand...
Click to collapse
+1
Sent from my A500 using xda app-developers app
ztotherad said:
notta, you needta update this to cwm6 for jb, please & ty
Click to expand...
Click to collapse
lifeofcoding said:
+1
Click to expand...
Click to collapse
Technically it isn't needed! CWM4 is all I have been using for JB so far. Works perfect to break the 3 finger curse and also to downgrade the recovery for better JB flashing in some scenario's.
Truth be told I only need heimdall now once in a blue moon and that is always because of something I'm trying. :silly:
I still posted it though as I figure it may come in handy at some point or at least have an odin/heimdall alternative. In OP for those in seeking...
Also while getting this together for you guys, I noticed the files in the OP are pushing close to a 1,000 downloads. Yet only 9 people have thanked me.
Has this not been useful? Just Curious...

Categories

Resources