I am currently running a Nexus 4 with PARANOIDANDROID 2.99b+ (Feb03) flashed with the Franco r53 kernel.
I wanted to try out the Matrix 6.5 kernel on my phone and was wondering if there is any step that I need to perform before flashing the new kernel. I found the following post that includes a cleaner script: http://forum.xda-developers.com/showthread.php?t=2121701
I was wondering if this is required or if we can simply flash the matrix kernel over the franco kernel. Would that be possible?
Also, would it be possible to flash the new PARANOIDANDROID release (assuming it includes a kernel) then flash the matrix kernel over that? Would this cause problems because the cleaner script was not run before flashing the new rom which has its own kernel?
Was not sure how it exactly works and was hoping that someone would be able to help me out and clarify the process.
Currently, I think your safest option is to flash the newest version of the PA rom and gapps and then flash the kernel that you want. Because a lot of the kernel developers are are making changes to things that may not be overwriten when flashing a kernel from a different developer. For example I think that franco makes changes to the ramdisk that some other kernel devs don't touch.
linelock said:
Currently, I think your safest option is to flash the newest version of the PA rom and gapps and then flash the kernel that you want. Because a lot of the kernel developers are are making changes to things that may not be overwriten when flashing a kernel from a different developer. For example I think that franco makes changes to the ramdisk that some other kernel devs don't touch.
Click to expand...
Click to collapse
Cool, so I guess when we flash the rom and gapps it resets any changes that may have been made by Franco's kernel (or any other kernel for that matter). Hence, running any cleaner script is not required. Is this true?
Also, when flashing the kernel I wipe cahce, wipe dalvik, flash kernel, reboot. I read in another post that you should let it run for 10-15 minutes then reboot again to let the kernel "settle in". Is this actually required?
if you are running franco kernel, you want to either reflash your rom then the kernel, or flash the roms boot.img then the kernel. coming from other kernels, just flash the new kernel on top. the reason being that franco kernel uses its own ramdisk(and you want your roms ramdisk).
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
jauwad.arshad said:
Cool, so I guess when we flash the rom and gapps it resets any changes that may have been made by Franco's kernel (or any other kernel for that matter). Hence, running any cleaner script is not required. Is this true?
Also, when flashing the kernel I wipe cahce, wipe dalvik, flash kernel, reboot. I read in another post that you should let it run for 10-15 minutes then reboot again to let the kernel "settle in". Is this actually required?
Click to expand...
Click to collapse
you do not wipe anything when flashing kernels, there is no need. wiping cache or dalvik has nothing to do with kernels, its just a misconception that keeps getting passed along.
simms22 said:
if you are running franco kernel, you want to either reflash your rom then the kernel, or flash the roms boot.img then the kernel. coming from other kernels, just flash the new kernel on top. the reason being that franco kernel uses its own ramdisk(and you want your roms ramdisk).
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
you do not wipe anything when flashing kernels, there is no need. wiping cache or dalvik has nothing to do with kernels, its just a misconception that keeps getting passed along.
Click to expand...
Click to collapse
Awesome, thanks for the info. So I guess it is a safe practice to flash the boot.img (or just update the rom if you were going to anyways) and then flash the kernel.
jauwad.arshad said:
Awesome, thanks for the info. So I guess it is a safe practice to flash the boot.img (or just update the rom if you were going to anyways) and then flash the kernel.
Click to expand...
Click to collapse
yup. i tell people to just reflash their rom(and gapps) with the kernel, then reboot if they were running franco kernel. but its safe to flash the stock or your roms boot.img also, then the kernel.
simms22 said:
then reboot if they were running franco kernel.
Click to expand...
Click to collapse
I am not sure what you meant by that.
What I get out of all of this, is that if I want to try a new kernel this is what I should do in recovery:
Factory reset + wipe cache + dalvik cache
Flash new rom (PA rom in my example)
Flash gapps
Flash custom kernel if desired (Franco's kernel in my example)
Reboot
Is that correct or am I missing a step/doing something extra?
You might notice if you update your ROM (e.g. the next time PA gets updated, or if you switch to CM nightlies) that during the flash, the kernel will be overwritten - no matter which kernel you are using.
For example, flashing CM installs the CM kernel - regardless of if I was running Franco's before that. This is why apps like CyanDelta (which supports incremental updates to the ROM, but also the flashing of zips *after* flashing the ROM) are so handy. Every three days, I flash the latest CM nightly, and then Franco's kernel. If I left Franco's kernel off the CyanDelta list, the phone would be using the latest CM kernel after the flash.
EDIT: Your steps look good, if not a little bit overly protective. For instance, I don't think a full factory reset is required to test out a different kernel, generally speaking. Obviously, it wouldn't hurt to do... just takes time.
twitchcity said:
You might notice if you update your ROM (e.g. the next time PA gets updated, or if you switch to CM nightlies) that during the flash, the kernel will be overwritten - no matter which kernel you are using.
For example, flashing CM installs the CM kernel - regardless of if I was running Franco's before that. This is why apps like CyanDelta (which supports incremental updates to the ROM, but also the flashing of zips *after* flashing the ROM) are so handy. Every three days, I flash the latest CM nightly, and then Franco's kernel. If I left Franco's kernel off the CyanDelta list, the phone would be using the latest CM kernel after the flash.
EDIT: Your steps look good, if not a little bit overly protective. For instance, I don't think a full factory reset is required to test out a different kernel, generally speaking. Obviously, it wouldn't hurt to do... just takes time.
Click to expand...
Click to collapse
That is pretty cool. Would that same app work on the PA rom or is it just for CM nightly builds?
Yeah, I am doing the factory reset because its a new version of the PA rom. I prefer not to simply flash over my current rom.
If you're running the latest PA on a mako, just get their 'contrasty' kernel and no need for your voodoo rituals
I am currently on franco kernel milestone 2 and want to try trinity kernel.
I have taken a 'back-up' of the stock kernel on the franco kernel updater app before i flashed franco.
Can I now restore my phone to stock kernel using this back-up and then flash trinity?
Will this work?
auto freak said:
I am currently on franco kernel milestone 2 and want to try trinity kernel.
I have taken a 'back-up' of the stock kernel on the franco kernel updater app before i flashed franco.
Can I now restore my phone to stock kernel using this back-up and then flash trinity?
Will this work?
Click to expand...
Click to collapse
you can. or you can just reflash your rom and trinity, dont wipe a single thing. just flash the rom, kernel, then reboot.
jauwad.arshad said:
I am not sure what you meant by that.
What I get out of all of this, is that if I want to try a new kernel this is what I should do in recovery:
Factory reset + wipe cache + dalvik cache
Flash new rom (PA rom in my example)
Flash gapps
Flash custom kernel if desired (Franco's kernel in my example)
Reboot
Is that correct or am I missing a step/doing something extra?
Click to expand...
Click to collapse
Only if you have franco now and switch to another kernel. So if you want to flash franco you don't have to wipe anything.
whats the quickest and easiest way to get rid of this error? Thanks in advanced
Flash a kernel that actually has the kexec-hardboot parch.
Sent from my Nexus 7 using Tapatalk
when i installed multiman i install it with a 'stock 4.1' is the stock referring to my android version?? If so i had android 4.2 at the time and just updated to android 4.3 so do i need to re install multiman? also will i need to use kexec hardboot patch 4.2 or does 4.2 only work on android version 4.2?? Sorry for all the question guys but thanks in advanced for the help.
If you use multirom to install the kernel, yes, choose the version of Android you're on.
You can also just flash a custom kernel yourself in recovery that has the patch and is compatible with your version of android. M-kernel, franco's kernel, oxydo, and faux's kernel i believe will all work.
I want to compile twrp 2.7 recovery for i9100g
I loved twrp in my omnirom and i want it in stock
Is there a way to port twrp 2.7 to i9100g?
3lo0sh said:
I want to compile twrp 2.7 recovery for i9100g
I loved twrp in my omnirom and i want it in stock
Is there a way to port twrp 2.7 to i9100g?
Click to expand...
Click to collapse
I don't own or have looked at that device, but [DEV]How to compile TWRP touch recovery should point you in the right direction, if you haven't seen it already.
3lo0sh said:
I want to compile twrp 2.7 recovery for i9100g
I loved twrp in my omnirom and i want it in stock
Is there a way to port twrp 2.7 to i9100g?
Click to expand...
Click to collapse
This isn't easy as it requires some ramdisk repacking magic.
(Problem is that I9100G, just like the I9100/N7000/I777 and original GalaxyS family, use a single image for both kernel and recovery. So it's really hard to change the kernel without changing recovery.)
I've been a mod head for many years and just got my Storm after many happy HTC years. I was just wondering is worth rooting the Storm as it is already running a customised OS. Any thoughts please?
I recomend you rooting . It is simple. Now we have TWRP so i believe custom roms like DU and others will be availble soon AS for now you can choose between COS 12.1.1 (Lollipop) and CM13(marshmallow) and i believe cm12.1 (lollipop). Shotly i recomend rooting.
aciupapa said:
I recomend you rooting . It is simple. Now we have TWRP so i believe custom roms like DU and others will be availble soon AS for now you can choose between COS 12.1.1 (Lollipop) and CM13(marshmallow) and i believe cm12.1 (lollipop). Shotly i recomend rooting.
Click to expand...
Click to collapse
Do you have to increase the size of the system partition to install CM13 (marshmallow) or simply flash the latest CM13 recovery and nightly for the storm(kipper) device.
You dont need to repartition. I recomend flash TWRP and then cm13, because i've had some problems with Cyanogen recovery
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
You dont need to repartition. I recomend flash TWRP and then cm13, because i've had some problems with Cyanogen recovery
Click to expand...
Click to collapse
OK thanks, I already have TWRP installed, so you can easily install the latest cm13 nightly using TWRP recovery, then an applicable gaps package.
Do you have drivers for the storm. If so post a link
Hi,
So i've been running OOS 3.0.2 Boeffla 2.0 and Super Su 2.74 without issues.
This morning I tried to flash Boeffla 2.1 Beta 1.
I followed steps from http://boeffla-kernel.de/index.php/69-new-concept-kernels-new-app as prescribed by @Lord Boeffla
flash rom
flash kernel
flash supersu (if required by your rom)
let it boot
enjoy
Click to expand...
Click to collapse
Unfortunately, the device stays on the OOS boot animation for ever.
The minute I flash back the stable kernel all is good in the world.
Any ideas on what could be causing the issue ?
Thanks
Couple of things:
Did you reflash the rom? If so, dirty or clean?
If dirty, did you wipe caches?
If clean, try reflashing OOS3 modded version of SU. https://www.androidfilehost.com/?fid=24591000424944601
Theberge43 said:
Hi,
So i've been running OOS 3.0.2 Boeffla 2.0 and Super Su 2.74 without issues.
This morning I tried to flash Boeffla 2.1 Beta 1.
I followed steps from http://boeffla-kernel.de/index.php/69-new-concept-kernels-new-app as prescribed by @Lord Boeffla
Unfortunately, the device stays on the OOS boot animation for ever.
The minute I flash back the stable kernel all is good in the world.
Any ideas on what could be causing the issue ?
Thanks
Click to expand...
Click to collapse
This is typically the case when SuperSu does not install in systemless mode.
You need a patched supersu version for OOS. Did you use that?
Hi,
Thanks for the answer. No I used the latest beta. Why does it work with the old kernel and not the new one?
Theberge43 said:
Hi,
Thanks for the answer. No I used the latest beta. Why does it work with the old kernel and not the new one?
Click to expand...
Click to collapse
Totally working for me, just flash the correct SuperSu zip