I am currently running CleanROM 2.5 w/ CleanKernel running TWRP. What is the best method to make the transition to CleanROM 5.5.1. Also what kernel does everyone run. What launcher do people like best?
Gunnett said:
I am currently running CleanROM 2.5 w/ CleanKernel running TWRP. What is the best method to make the transition to CleanROM 5.5.1. Also what kernel does everyone run. What launcher do people like best?
Click to expand...
Click to collapse
I used latest TWRP, Data Wipe/Cache Wipe/Dalvik Cache Wipe.
Flash CleanRom 5.5.1
Reboot!
There is no CleanKernel for the latest CleanRom's, but LeanKernel 1.1 Should work fine. Don't forget to make backup first.
I haven't seen any advantage in OCing or leankernel over the stock kernel in Cleanrom for day to day stuff, but YMMV.
Good Luck!
dark_system said:
I used latest TWRP, Data Wipe/Cache Wipe/Dalvik Cache Wipe.
Flash CleanRom 5.5.1
Reboot!
There is no CleanKernel for the latest CleanRom's, but LeanKernel 1.1 Should work fine. Don't forget to make backup first.
I haven't seen any advantage in OCing or leankernel over the stock kernel in Cleanrom for day to day stuff, but YMMV.
Good Luck!
Click to expand...
Click to collapse
Will it automatically flash the stock kernel over the old CleanKernel?
Backup your apps with titanium backup. I also flashed the new RPM and modem. I realize these are debatable but it does seem to have improved my battery life. YMMV.
Gunnett said:
It will automatically flash the stock kernel over the old CleanKernel.
Click to expand...
Click to collapse
Yes. The kernel is included in the rom.
Related
Im running cm9 nightly from may 13 I tired to flash guevor's kernel(tried v19.2 then tried 17c because i read that it was the most stable) and Wi-fi was stuck on "turning on wi-fi" the same thing with testymeh kernel. Is there a fix or am I stuck with stock kernel? Before flashing each kernel I make sure wipe cache x3 and wipe dalvik x3.
Kagenui said:
Im running cm9 nightly from may 13 I tired to flash guevor's kernel(tried v19.2 then tried 17c because i read that it was the most stable) and Wi-fi was stuck on "turning on wi-fi" the same thing with testymeh kernel. Is there a fix or am I stuck with stock kernel? Before flashing each kernel I make sure wipe cache x3 and wipe dalvik x3.
Click to expand...
Click to collapse
I think it's CM9 compatibility issue to these custom kernels. The only fix is you just rise your issue in CM9 thread and see if the developer can do something about it. And wiping cache and dalvik is not a must in flashing custom kernel. It doesn't touch anywhere near there but it's still individual opinions here..
Which roms are most compatible the OC kernels?
Kagenui said:
Which roms are most compatible the OC kernels?
Click to expand...
Click to collapse
The new CM9 nightlies breaks compatibility with guevor lastest kernels.
Use this link, should work.
http://www.xdafileserver.nl/index.php?dir=ASUS/Asus+Transformer+(TF101)/ROMS/Megatron/Kernels
linuques said:
The new CM9 nightlies breaks compatibility with guevor lastest kernels.
Use this link, should work.
http://www.xdafileserver.nl/index.php?dir=ASUS/Asus+Transformer+(TF101)/ROMS/Megatron/Kernels
Click to expand...
Click to collapse
I was coming here to say that, but it seems that you already did it
I have read through every page of the Cleanrom thread and I think I have the right sequence of steps to flash my TF700 (just got it - I am impressed!!)
Current state/what I have done so far:
Flashed ASUS 10.4.4.20 US
Flashed TWRP 2.3.3.0
Flashed Supersu - v0.99
Flashed Cleanrom 2.7 ODEX
Flashed CROMI 2.7.2 patch
The tablet is working great and getting 5145 quadrant score. No problems experienced.:victory:
Objective: Get tablet to CROMI 3.0.4
Based on what I have read in the thread are these the correct next steps???:
1. Do a backup of the ROM in TWRP
2. Flash Cleanrom 3.0.3 (wipe Dalvik and cache before and after)
3. Flash CROMI 3.0.4 (wipe Dalvik and cache before and after)
4. Enjoy!
Just want to make sure I have the sequence right.
The biggest question I have is "Do I have to upgrade to the US 10.4.4.23 firmware before flashing the 3.0.3 and 3.0.4 Cleanrom???"
TIA to all
toolmanz said:
I have read through every page of the Cleanrom thread and I think I have the right sequence of steps to flash my TF700 (just got it - I am impressed!!)
Current state/what I have done so far:
Flashed ASUS 10.4.4.20 US
Flashed TWRP 2.3.3.0
Flashed Supersu - v0.99
Flashed Cleanrom 2.7 ODEX
Flashed CROMI 2.7.2 patch
The tablet is working great and getting 5145 quadrant score. No problems experienced.:victory:
Objective: Get tablet to CROMI 3.0.4
Based on what I have read in the thread are these the correct next steps???:
1. Do a backup of the ROM in TWRP
2. Flash Cleanrom 3.0.3 (wipe Dalvik and cache before and after)
3. Flash CROMI 3.0.4 (wipe Dalvik and cache before and after)
4. Enjoy!
Just want to make sure I have the sequence right.
The biggest question I have is "Do I have to upgrade to the US 10.4.4.23 firmware before flashing the 3.0.3 and 3.0.4 Cleanrom???"
TIA to all
Click to expand...
Click to collapse
No you don't need to upgrade first you have it perfect. Almost.
You can flash 3.0.3 and then 3.0.4 without any wipes but do dalvik and regular cache after. Doing before and after makes no difference. :good:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?
sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do
I've installed Tachi91 JB deodexed rom a while ago.
http://forum.xda-developers.com/showthread.php?t=2055490
Can I install ViperXL rom JB 3.1.0 over it without wiping?
http://forum.xda-developers.com/showthread.php?t=1868236
Thanks
etai-ab said:
I've installed Tachi91 JB deodexed rom a while ago.
http://forum.xda-developers.com/showthread.php?t=2055490
Can I install ViperXL rom JB 3.1.0 over it without wiping?
http://forum.xda-developers.com/showthread.php?t=1868236
Thanks
Click to expand...
Click to collapse
NO you don't HAVE to wipe but I would recommend it. Gives you a good clean fresh start. Just back up your user data with titanium or whatever your favorite backup app is and restore it after you reflash. Just don't restore system apps or data.
ImagioX1 said:
NO you don't HAVE to wipe but I would recommend it. Gives you a good clean fresh start. Just back up your user data with titanium or whatever your favorite backup app is and restore it after you reflash. Just don't restore system apps or data.
Click to expand...
Click to collapse
I second this based on the number of people in the Viper XL thread who didn't wipe beforehand and ultimately had to go back and wipe after facing reboot issues, issues with apps crashing, and other issues of sorts. The best way to guarantee a stable install is just start fresh and restore user apps as mentioned.
Hi Guys,
I'm about to flash the xenogenesis rom. I already have the right bootloader and the right TWRP, But I keep on getting errors during boot. Do i need to uninstall my data2sd?
lasallegreen said:
Hi Guys,
I'm about to flash the xenogenesis rom. I already have the right bootloader and the right TWRP, But I keep on getting errors during boot. Do i need to uninstall my data2sd?
Click to expand...
Click to collapse
No, you don't need to uninstall data2sd as long as you are not using data2sd kernel (_that or hunds data2sd kernel). If you still having issue with boot, you may need to do a full wipe. (twrp--> advance-> select to wipe everything except for external sdcard) then re install cromi.
buhohitr said:
No, you don't need to uninstall data2sd as long as you are not using data2sd kernel (_that or hunds data2sd kernel). If you still having issue with boot, you may need to do a full wipe. (twrp--> advance-> select to wipe everything except for external sdcard) then re install cromi.
Click to expand...
Click to collapse
Thank you. I managed to solve my own problem. I just installed a fresh CROMi 3.2.2 first before upgrading to Xenogenesis RC2 to solve my booting issue.
Anyway, is there a stable release of a Data2SD kernel for Xenogenesis RC2? I didn't choose the Data2SD kernel during the installation because It says "experimental". I didn't want to gamble on its reliability first.
lasallegreen said:
Anyway, is there a stable release of a Data2SD kernel for Xenogenesis RC2? I didn't choose the Data2SD kernel during the installation because It says "experimental". I didn't want to gamble on its reliability first.
Click to expand...
Click to collapse
Data2SD is now an add-on, not a separate kernel - see my kernel thread.
_that said:
Data2SD is now an add-on, not a separate kernel - see my kernel thread.
Click to expand...
Click to collapse
Ok. Thanks _that ! will read it first
_that said:
Data2SD is now an add-on, not a separate kernel - see my kernel thread.
Click to expand...
Click to collapse
_that can I just install the add on zip over the CROMi xenogenesis RC2? I chose the modded stock kernel V2 during installation. Is there anything i need to do before installing the zip?
lasallegreen said:
_that can I just install the add on zip over the CROMi xenogenesis RC2? I chose the modded stock kernel V2 during installation. Is there anything i need to do before installing the zip?
Click to expand...
Click to collapse
Should work. I've never tried to set up a fresh Data2SD installation from scratch (I started with a copy of my existing /data partition), but others have done it successfully.