Probably a pretty stupid question but I'm doing some flashing today and I'm curious. Does it matter which order I flash the Rom and Kernel in? Or should the Kernel come first?
ROMs usually have a kernel with them, so install the rom, then the custom kernel you want.
HideYoKids said:
Probably a pretty stupid question but I'm doing some flashing today and I'm curious. Does it matter which order I flash the Rom and Kernel in? Or should the Kernel come first?
Click to expand...
Click to collapse
Rom first, Kernel second! I don't know if it matters but I have never done it the other way. I always allow a boot up first when the rom installs and then reboot into recovery again and install the kernel Good luck.
jd1001 said:
Rom first, Kernel second! I don't know if it matters but I have never done it the other way. I always allow a boot up first when the rom installs and then reboot into recovery again and install the kernel Good luck.
Click to expand...
Click to collapse
Thanks, guy!
Will do.
when you install a new kernal, is there anything you need to do or does it replace the old one and most things should just work?
droidmarc said:
when you install a new kernal, is there anything you need to do or does it replace the old one and most things should just work?
Click to expand...
Click to collapse
Provided you installed the correct one fo your phone it should work fine. You may notice things like longer battery life, enhanced speed on mobile networks and also the ability to change the frequency of the phones processor. I use an apex kernel on my GNex and it is really good.
If you install a kernel and then a rom, your kernel will be overwritten considering roms come with kernels
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
If you install a kernel and then a rom, your kernel will be overwritten considering roms come with kernels
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Good point! DIDn't think of that!
jd1001 said:
Good point! DIDn't think of that!
Click to expand...
Click to collapse
Install rom. Wipe Dalvik Cache before installing your kernel. Install kernel. Profit!
thanks
After installing rom, gapps, then kernel..it hangs at the HTC boot screen...
I did all in the correct order. wiped dalvik cache and then installed kernel..
S-off
Rooted
Htc One S (ville)
hboot 2.15
im installing pac rom and elementalx kernel.
im posting this here in a 2 year old thread,,because i had the same question. anyways any ideas as to whats wrong?
ive let it sit waiting for about 20+ minutes before and it still didnt boot.
thanks!
Sailor spinach said:
After installing rom, gapps, then kernel..it hangs at the HTC boot screen...
I did all in the correct order. wiped dalvik cache and then installed kernel..
S-off
Rooted
Htc One S (ville)
hboot 2.15
im installing pac rom and elementalx kernel.
im posting this here in a 2 year old thread,,because i had the same question. anyways any ideas as to whats wrong?
ive let it sit waiting for about 20+ minutes before and it still didnt boot.
thanks!
Click to expand...
Click to collapse
Not only in a old thread but in a section for a completely diffrent device too. This is the Galaxy Nexus forum
Sent from my Galaxy Nexus using XDA Free mobile app
Related
Hey guys I have some knowledge about rooting (rooted the G1 first- the good ol days haha). My question is about flashing new roms. Currently I have the juggernaut rom and was curious as to understand what steps do I need to take to flash another rom? Do a fullwipe then simply install the rom? My second question deals with kernels. If I want to flash a rom and on the thread it gives me a kernel to flash as well is this what i do? Wipe everything, then flash the rom, then reboot, then go back and flash the kernal? Thank you guys for your help!!
I always do a wipe before flashing a new rom. Not sure if it really matters and I usually flash a rom and then flash a kernel without leaving cwm or rebooting.
Sent from my SGH-T989 using xda premium
So you flash the rom, then if given the kernel during recovery mode then reboot?
Exodian said:
I always do a wipe before flashing a new rom. Not sure if it really matters and I usually flash a rom and then flash a kernel without leaving cwm or rebooting.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, make sure you flash the kernel before you reboot, but after the you flash the rom
There is enough hate in the world. Why can't we all get along here ...?
Okay thanks guy!!
Sorry for double posting, but does anyone gotten voodoo sound to work on the t-mobile SG2??
HI. I AM FAIRLY NEW TO THE ROM FLASHING SCENE. HAVE BEEN SUCCESSFUL FOR THE LAST FEW MONTHS AT FLASHING ROMS. THEN I THINK I STEPED OUT OF BOUND AND BEGAN TO TRY FLASHING NEW KERNELS. HAVE BEEN SEARCHING WEB ALL DAY ON WHAT COULD HAVE HAPPENED. FROM WHAT I HAVE READ I MAY HAVE FLASHED A KERNEL FROM ONE MOD TO ANOTHER. OR POSSSIBLY INTERRUPTED THE ZIP INSTALL OR FLASH. NOW WHEN I TRY TO FLASH BACK UP ROMS THEY BOOT LOOP OR JUST STAY ON BOOT SCREEN. SAYS NO PC36IMG at the hboot screen. please help.
Are you using the newest HBOOT from HTC? I heard that you can't flash kernels on it...
Maybe the .zip didn't download completely. What kernel did you try to flash, can you even access recovery?
HBOOT 6.16.1002. i was flashing a tiamat kernel. didnt like it and when i tried another one is when it happened. not sure if i did all the wipes. was late and was getting tired
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
well tiamat will not work on any mik rom that i know of because (all?) mik roms are sense roms. if its a sense rom then you need a sense kernel. aosp rom needs aosp kernel. go into recovery and flash a sense kernel. that should fix your bootloop
Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out
trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium
-EViL-KoNCEPTz- said:
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?
Damn it. So am i screwed or is their a solution
trevanti00 said:
Damn it. So am i screwed or is their a solution
Click to expand...
Click to collapse
did your s turn back on after the bootloop ?
What did he do to fix it. Do you have a thread on that
I am s off
No it is still off
trevanti00 said:
No it is still off
Click to expand...
Click to collapse
then TWRP most likely didnt cause it. His situation was different from what your experiencing so what he did will most likely will be different from what youll have to do. Also if TWRP caused it you would be back to s-on
Well could you give it a shot and trouble shoot with me. I been at it eveery since last night
trevanti00 said:
Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out
Click to expand...
Click to collapse
here is one...http://forum.xda-developers.com/showthread.php?t=1496488
Flash amon ra in hboot and get off of twrp b4 u end up screwed first and foremost then try wiping everything in amon ra except sdcard and battery stats and flash a new rom and see if it will boot up if you can't get recovery to load you may need to try running an ruu and starting from scratch
Sent from my PC36100 using xda premium
evo4gnoob said:
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?
Click to expand...
Click to collapse
Ppl not reading enough or rushing thru things is my guess *shrugs*
Sent from my PC36100 using xda premium
ok trying that now.
problem solved. thank you guys a million times. i knew i would run into a brick sooner or later. lesson learned. i have always read all the post before flashing but was tired and got lazy. will never happen again. again THANK YOU GUYS.
I rooted my Gnex GSM yesterday using Nexus Root Toolkit. After doing this I found that my pull down menu lags annoyingly when I'm in an app. Does anyone have any idea what the problem could be. I've cleared my cache and dalvik cache as instructed by my friend. But that hasn't done anything to my phone really. Thanks:good:
First, post in the right section.
Superuser/root access has nothing to do with "lag".
a maguro wrote this.
beekay201 said:
First, post in the right section.
Superuser/root access has nothing to do with "lag".
a maguro wrote this.
Click to expand...
Click to collapse
what section would that be? I didn't see a rlevant section so I just posted in the general section. So how would one explain that before I rooted, my pull down menu was a smooth transition, and after rooting it isn't?
The Q&A section obviously since your asking a question.
Sent from my Galaxy Nexus using xda premium
And now comes that part: OP, are you using superuser or supersu?
a manta wrote this.
beekay201 said:
And now comes that part: OP, are you using superuser or supersu?
a manta wrote this.
Click to expand...
Click to collapse
wouldnt know, used a toolkit.
I'n using SuperSU. It is really annoying to see that when I use my pull down menu that it's not a smooth transition
I have same problem many times, than i wiped all even system and flash custom ROM. After few months and few flashing problem was back. So wipe all internal memory if you ask me. Install custom ROM. If you wipe all andcan`t boot phone use QtADB while in recovery to copy zip and gapps to your phone. Google it...
Alienns said:
I have same problem many times, than i wiped all even system and flash custom ROM. After few months and few flashing problem was back. So wipe all internal memory if you ask me. Install custom ROM. If you wipe all andcan`t boot phone use QtADB while in recovery to copy zip and gapps to your phone. Google it...
Click to expand...
Click to collapse
thanks but this process seems so long. there must be a direct thing that's affecting it
I flashed JDQ39 through fastboot, rooted it, I see no such lag.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
beekay201 said:
I flashed JDQ39 through fastboot, rooted it, I see no such lag.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, I flashed that too and rerooted. Still there, but it's less frequent. I'll see what happens
Tez_Nexus said:
Yeah, I flashed that too and rerooted. Still there, but it's less frequent. I'll see what happens
Click to expand...
Click to collapse
I guess the real question is what ROM you flashed and what Kernel is running.
Some ROM's run faster on Gnex than others.
Personally I have been running AOKP and XenonHD back and forth for some time and have a little lag here and there, but that is because I am able to add and change so much on the ROM. Sometimes changing the kernel helps as well.
At the end of the day it's all about what you are doing and what ROM/Kernel combination give you the user experience you like.
Sorry to say, what you are asking is more of an Art than an exact science when it comes to use and feel.
I recently bought, and finally rooted my sprint sph-l710. I have flashed two roms, hyperdrive, and moar roms. My problem is that i cant flash anything else, only those two roms. Is there a fix?
bigchuq said:
I recently bought, and finally rooted my sprint sph-l710. I have flashed two roms, hyperdrive, and moar roms. My problem is that i cant flash anything else, only those two roms. Is there a fix?
Click to expand...
Click to collapse
What do you mean you can't flash anything else? When you flash, are you wiping everything clean each time before flashing ROMs or are you dirty flashing?
tkepk181 said:
What do you mean you can't flash anything else? When you flash, are you wiping everything clean each time before flashing ROMs or are you dirty flashing?
Click to expand...
Click to collapse
yes, i'm wiping everything, whenever i try to install any other rom i have some type of error. i'm new to this so please excuse my noobness. i've tried to flash a stable cm10, among others with no luck.
Do you have the md4 boot loader?
Sent from my SPH-L710 using xda app-developers app
The new S3 have been modded by Sprint /Samsung and require a modded recovery in order to mount storage. The other issue is that you can not flash an aosp style rom. You should be able to flash any TW rom but it won't allow aosp roms to flash. None of the developers have a new S3 so until someone gets one ir someone volunteers one this won't be solved.
Remember search is your best friend, Have a great day!
IDontKnowMang said:
Do you have the md4 boot loader?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I believe so, but i'm not sure is that @ the end of the build number? If so, yes
bigchuq said:
I believe so, but i'm not sure is that @ the end of the build number? If so, yes
Click to expand...
Click to collapse
If your getting a status 7 error that is the bootloader error flash this in recovery it will update all your firmware and bootloader. http://db.tt/Qt6NcH0a
After flashing this make sure you reboot the phone then try going back into recovery and flashing the rom you want.
Remember search is your best friend, Have a great day!
Is this still a legit fix even after the 4.3 upgrade?
I just tried this and now my phone wont even power on.
Well last 3 ICS roms I used were getting bootloops after a while. My phone was rebooting a few times (I think it is because of SD card), but that was normal with most of ROMs I used. However on my last 3 ROMs after few restarts phone just got into a bootloop. I used HoNo's v20f, Nitro TnT, and v20f by altvolt74. I also used wind kernel 3.7 with it. The only thing that could get me back to normal was factory reset, but I don't want to do it every time it boot loops. Any way I can fix these bootloops?
PS I am unbricking and rooting the phone again now...
Are you using the latest CWM recovery? Are you doing a full wipe between roms (cache, Dalvik, data, system)?
audit13 said:
Are you using the latest CWM recovery? Are you doing a full wipe between roms (cache, Dalvik, data, system)?
Click to expand...
Click to collapse
Yeah I am using CWM 6.0.1.5 and I am doing full wipes.
kirov37 said:
Yeah I am using CWM 6.0.1.5 and I am doing full wipes.
Click to expand...
Click to collapse
6.0.4.5 is the latest version.
http://www.clockworkmod.com/rommanager
audit13 said:
6.0.4.5 is the latest version.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
By the way, I've had a few random reboots today, which would have normally caused bootloop, but my phone didn't loop now. I think it might be something with the kernel. When I was getting those bootloops I've been using wind kernel 3.7, now I flashed 3.5... Maybe the kernel caused problems?
Oh and by the way thanks for that link!
Why not try one of the newer ROMs based on 4.2.2, 4.3, and 4.4?
I find the colours and text to be much better on these newer ROMs.
audit13 said:
Why not try one of the newer ROMs based on 4.2.2, 4.3, and 4.4?
I find the colours and text to be much better on these newer ROMs.
Click to expand...
Click to collapse
I'm not using the newer ROMs because the games don't work on them. For example on CM 10.1.3 games work really really slow... If you know any good new ROM which has games working, recommend me please.
Oh and by the way, do I have to go through unbricking and rooting process again to install newer recovery, or can I simply push it with adb now?
kirov37 said:
I'm not using the newer ROMs because the games don't work on them. For example on CM 10.1.3 games work really really slow... If you know any good new ROM which has games working, recommend me please.
Oh and by the way, do I have to go through unbricking and rooting process again to install newer recovery, or can I simply push it with adb now?
Click to expand...
Click to collapse
I agree with you, only the ROMs based on stock are suitable fir games. In regards to recovery, just use adb. BTW, if you want to try a newer ROM that would be good for games, try one of the SphinX ROMs.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
I agree with you, only the ROMs based on stock are suitable fir games. In regards to recovery, just use adb. BTW, if you want to try a newer ROM that would be good for games, try one of the SphinX ROMs.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I used 720's Sphinx ROM it could run games, but sometimes it could get choppy and the ROM wasn't as stable as ICS for me.