Hey all I'm thinking of going from the Sky ICS ROM (Android 4.0.4) to CM9 but wondering if there would be any issues, for example with the kernel, etc. I wouldn't think so since they're both ICS ROMs.
Another question is which version of ICS is CM9? I searched the net and no details were given if it's 4.0, 4.0.1, 4.0.4, etc. Thanks.:highfive:
They are different kernels but it doesn't matter cm comes with its own kernel unless you'd like to install instigatorX (which most of us recommend... And use Badass governor for better battery)
Just wipe wipe wipe cache, data, system .use uclf6 if your not already on it .then flash ROM, kernel, and gapps. Fix permissions and voila cm9 from anything
CM9 Skyrocket
Related
A little new here. I just installed the Infuse custom rom and am looking to flash a different kernal onto my phone. How would I go about doing this?
the same way you flashed a custom rom. though, if you are running a custom rom, you are most likely running the custom kernel it came with. for example, gtg465x's infused rom includes gtg365x's voodoo kernel, and the refuse rom includes the defuse kernel. you can still flash the zip of any kernel you like for the infuse if you dont want the rom's default kernel.
Hey guys,
Ive been out of the loop for a bit and it looks like a lot has changed. I am currently running a US WiFI only Xoom with Tiamat 2.2.2 "Moray". I know that ICS is available for our devices... Can I go right from 2.2.2 to say, Team Eos ICS 1.0.0 or is their a better way? I am planning on using the below link but Ive also seen posts for others ROMS that required steps be taken prior to going to ICS.
http://forum.xda-developers.com/showthread.php?t=1484770
As always, any help is appreciated.
Thanks!!
You should be able to flash the rom and gapps and then boot fine, but I would do a nandroid first just in case.
The EOS release is a full ROM, not just an update. Should be fine. Have fun with your 'brand new' Xoom!
Thanks guys. I will give it a go after work today. Cant wait!
do a nandroid
wipe data, cache, dalvik
flash eos ics 1.0 in cwm -> flash gaps in the same cwm session!!! -> reboot
now u r on eos ics 1.0
As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?
Fulvio93 said:
As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?
Click to expand...
Click to collapse
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?
rzr86 said:
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?
Click to expand...
Click to collapse
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.
Fulvio93 said:
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.
Click to expand...
Click to collapse
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897
android1234567 said:
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897
Click to expand...
Click to collapse
Yeah well, I was looking at the title of that kernel thread while I realized which was the problem, I'm glad to tell you that I flashed your kernel last night (I'm Italian) and after a whole day using it I have to say that I really like it (even if I've to settle with all the differences between the governors and the best way to set them with aroma).
Thank you!
I am trying to install KT 747 Jellybean Kernel on my VZW SCH-i535 Galaxy S3. I'm on a rooted stock rom ( root66_VZW_I535VRBMA2) 4.1.2 I flashed through ODIN. I unlocked via EZUnlock 1.2 , downloaded the 4.1 AOSP Jellybean Kernel and flashed the kernel through CWM v6.0.1.0
After it is complete I wipe cache, dalvik cache, and fix permissions. My phone will not boot. It vibrates goes to Samsung, then the Galaxy S III logo appears, and the phone becomes unresponsive until I remove the battery. I am still able to access recovery; however, I'm unable to boot. Also when I plug it into the charger no indicator comes on nor any lights, it's as if it was off.
The ROM works fine until I try to install the kernel. What am I doing wrong? Any help would be appreciated, thank you!
If you are on a stock ROM, you need the TOUCHWIZ KT747 KERNEL, not the AOSP one. That one is for custom roms based on the open source platform like Cyanogenmod.
Use this > http://www.mediafire.com/?d00ake0isj671hr
siriusgamer said:
If you are on a stock ROM, you need the TOUCHWIZ KT747 KERNEL, not the AOSP one. That one is for custom roms based on the open source platform like Cyanogenmod.
Use this > http://www.mediafire.com/?d00ake0isj671hr
Click to expand...
Click to collapse
Sweet it worked. Idk why I thought I remembered reading an article that new android releases are AOSP...must have been too baked. Anyways thanks a lot it's working great!
Sorry if this has already been asked before. If you already have a custom ROM with stock kernel, and now you want to install a custom kernel, would you just boot into custom recovery then flash it on top of the existing ROM just like flashing Gapps? or do you have to wipe the ROM first, flash the kernel then ROM after that? Here's another question. Custom ROMs come with their own kernels, would my custom kernel get overwritten when I upgrade my ROM to a newer version (for example from cm10.1-20130226 to cm10.1-20130309?
k20- said:
Sorry if this has already been asked before. If you already have a custom ROM with stock kernel, and now you want to install a custom kernel, would you just boot into custom recovery then flash it on top of the existing ROM just like flashing Gapps? or do you have to wipe the ROM first, flash the kernel then ROM after that? Here's another question. Custom ROMs come with their own kernels, would my custom kernel get overwritten when I upgrade my ROM to a newer version (for example from cm10.1-20130226 to cm10.1-20130309?
Click to expand...
Click to collapse
Correct just copy the kernel to your sdcard clear cache in recovery and flash away.
I tried your ROM and rebooted twice and still looking good. Hope it'll still survive after the 3rd reboot. However, I notice some delay before the first ring back, probably due to weak signal in my area. I'll try more at different locations in the next few days to see how it goes. I really appreciate your contribution and all coders with TeamChopsticks who have nailed down the root cause of audio loss in the cm10.1 nightlies for skyrocket.
I'm having problem with Carbon ROM. My video doesn't playback I only see purple screen. However taking pictures is fine but both the qualities are low. I already set to HD. I flashed AOKP from toyes and REVOLT they had no problems with the video.
sent from Skyrocket