Database Info

Kernel for JB

Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!

devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
I can't use Adam's Jelly Belly rom, as I have a NS4g, but I do follow his work. I believe that his rom comes with Thalamus kernel, and if you want to flash a different kernel, there is a file which needs to be deleted before doing so. There was quite a discussion about all this in his thread in the development forum. That's where you can figure it out ... good luck!

same for me
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.

There's a script you must delete in the init.d to use another kernel in Jelly Belly 0.1.5
Otherwise, your phone will poweroff

panks_4ever said:
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
Click to expand...
Click to collapse
i have also a i9023 and i have allredy flashed bedalus kernel, thalamus and air kernel also matrix and vta2 worked for me..
i use JRO03E DX stock ROM..never had a problem
S.R.

(I use stock JB with Air #153, and got i9023. No OC, no NSTools, yet. I have no problem.)
On stock:
Try to do a factory reset/wipe data, or reflash the OS from scratch using factory images. And right after flashing the rom, flash the kernel. Even before installing any apps.
On JBelly:
For this, I think the Thalamus kernel is the best, the rom is come with it, so they made for each other If this kernel works with it, i think it is unnecessary to switch to another kernel right now.
Because JB kernels are not final yet, are "immature", there can be compatibility issues, collisions between (certain functions of) roms and kernels.
After a 2 or 3 releases, both on rom and kernel side, there will be more complete and stable versions.

Have you tried to fix permissions ?

Go to /etc/init.d/ folder and delete a file called 'kernel'. You can read it first if you want.
This is basically a hack that AdamG added to avoid everyone changing kernels and reporting problems about the ROM. He only allows thalamus kernel.

Can please provide me detailed steps of how to flash a thalamus kernel on stock jb because i think the procedure is wrong. I did the following steps:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
And after i tried restarting my phone but it hanged up on the boot screen.
Please someone advise me the correct steps if this is wrong
. Thanks in advance
Sent from my Nexus S using xda app-developers app

panks_4ever said:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
Click to expand...
Click to collapse
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.

devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
To not have to deal with third party kernel support there is /system/etc/init.d/00kernel that simply powers off your phone if you flash another kernel.
Flash the rom to boot it, delete the file, then flash any kernel you want as you usually would.

charchuck said:
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
Click to expand...
Click to collapse
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.

so this are the final steps...
shivasrage said:
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
Click to expand...
Click to collapse
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)

panks_4ever said:
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
Click to expand...
Click to collapse
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.

Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.

thank you
shivasrage said:
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
Click to expand...
Click to collapse
DeuXGod said:
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Click to expand...
Click to collapse
Thank you shivasrage and DeuXGod. I am surely goona try out this, i am being eagerly waiting to flash a custom kernel because as compared to ICS i feel JB is eating up more battery. Thank you so much:good:

[Q] aroma

Hi
Everyone is talking about this aroma something to wipe before flashing new roms
I googled it, but i found there are 2 aromas, installer and file manager
Which one is used to do the full wipe?
Do i need both software?
Thank you
Sent from my GT-N8000 using xda app-developers app

bombamanz said:
Hi
Everyone is talking about this aroma something to wipe before flashing new roms
I googled it, but i found there are 2 aromas, installer and file manager
Which one is used to do the full wipe?
Do i need both software?
Thank you
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
Aroma is a dev tool allowing a graphical user interface for users installing custom roms. It is customized by a dev to allow users the ability to add/change/modify rom features and settings. For our device there are 3 roms installed through aroma though only 2 give us the option to perform a wipe android revolution hd by mike1986 and omega by indie when running the script from your recovery it launches aroma installer and both of the mentioned roms give you the option of wiping your device before continuing with setup. Be careful of which recovery you use, most users agree the newer cwm recoveries dont like aroma and freeze on some screens. Not a huge deal as this just requires a reboot which will bring you back to cwm. The original high on android from the android dev how to root guide by zedomax seems to work well and from personal experience i can tell you twrp works as well. Hope this helps

Specialp said:
Aroma is a dev tool allowing a graphical user interface for users installing custom roms. It is customized by a dev to allow users the ability to add/change/modify rom features and settings. For our device there are 3 roms installed through aroma though only 2 give us the option to perform a wipe android revolution hd by mike1986 and omega by indie when running the script from your recovery it launches aroma installer and both of the mentioned roms give you the option of wiping your device before continuing with setup. Be careful of which recovery you use, most users agree the newer cwm recoveries dont like aroma and freeze on some screens. Not a huge deal as this just requires a reboot which will bring you back to cwm. The original high on android from the android dev how to root guide by zedomax seems to work well and from personal experience i can tell you twrp works as well. Hope this helps
Click to expand...
Click to collapse
First off, I have the N8013, not sure what you have. I found your post because i couldn't figure out what this damn aroma thing everyone is talking about is. so thanks for your response on that.
But i have a question, what version on TWRP are/were you using? Did you just install it from goomanager or rommanager(clockwork) or did you have to flash from odin?
I'm not excited about using this high on android recovery, so when you said you used twrp i figured i would ask.

Best recovery is:
eggwardo said:
First off, I have the N8013, not sure what you have. I found your post because i couldn't figure out what this damn aroma thing everyone is talking about is. so thanks for your response on that.
But i have a question, what version on TWRP are/were you using? Did you just install it from goomanager or rommanager(clockwork) or did you have to flash from odin?
I'm not excited about using this high on android recovery, so when you said you used twrp i figured i would ask.
Click to expand...
Click to collapse
Some RECOVERY had problems with aroma instaler. I tried a lot of them CWM, TRW etc. but only one of them have no problem when I instaling something where was the aroma been. This Recovery is in my signature. Here : HighOnAndroid Recovery
Even KitKat custom ROMs I flashed without problem.
It's my opinion only, but I'm very satisfied with it! Peter

[Q] Changing Stock kernels

Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.

if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.

DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.

im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.

DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?

strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.

DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..

also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.

DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.

strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.

DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.

well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0

NC1 flasher. No need for Odin to get into Safestrap.

Hi all,
This is an app by which you can flash the NC1 stock KK kernel(while on lollipop OC3) that is Safestrap friendly. Then you can enter to SS recovery and flash whatever you need onto your LP ROM. As we all know that SS won't work after flashing a lollipop ROM using muniz_ri method, unless you Odin a KK kernel. All you have to do is download the app and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish without having to be stuck or having to use Odin to flash the KK kernel. We are not always home by the PC to use Odin. After done flashing your files MAKE SURE TO FLASH THE I337_OC3_Stock_KERNEL_Recovery-Flashable before you reboot in order for your phone to boot up.
(NOTE: OC4 recovery flashable kernel is located here for those who need it. Thanks to Carl again)
-I did NOT make this app and I take absolutely no credit for it. All thanks go to @benwaffle the original creator of this app for our AT&T Note 3 and @carl1961 for remaking it for the S4.
If you have any questions, please let me know.
-Please note that the purpose of this thread is only to help users. No donations needed. A "thank you" is more than enough
Hope this will help.
WARNING: it may or may not work for some of you. It DID work for me with no problem, so use it at your own risk.

K-alz said:
Hi all,
This is an app by which you can flash the NC1 stock KK kernel(while on lollipop OC3) that is Safestrap friendly. Then you can enter to SS recovery and flash whatever you need onto your LP ROM. As we all know that SS won't work after flashing a lollipop ROM using muniz_ri method, unless you Odin a KK kernel. All you have to do is download the app and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish without having to be stuck or having to use Odin to flash the KK kernel. We are not always home by the PC to use Odin. After done flashing your files MAKE SURE TO FLASH THE I337_OC3_Stock_KERNEL_Recovery-Flashable before you reboot in order for your phone to boot up.
-I did NOT make this app and I take absolutely no credit for it. All thanks go to @benwaffle the original creator of this app for our AT&T Note 3 and @carl1961 for remaking it for the S4.
If you have any questions, please let me know.
-Please note that the purpose of this thread is only to help users. No donations needed. A "thank you" is more than enough
Hope this will help.
WARNING: it may or may not work for some of you. It DID work for me with no problem, so use it at your own risk.
Click to expand...
Click to collapse
Sound Fantastic! Lets see if I got it straight: 1. Using the Safestrap/Odin method get into LP. 2. Then install the NC1 app to get SS. 3. Flash the file you want then Flash I337 OCS Stock Kernel and the reboot.
Sound right?

Source is here https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher

rfb813 said:
Sound Fantastic! Lets see if I got it straight: 1. Using the Safestrap/Odin method get into LP. 2. Then install the NC1 app to get SS. 3. Flash the file you want then Flash I337 OCS Stock Kernel and the reboot.
Sound right?
Click to expand...
Click to collapse
Yup, you got it. I was actually worried that I didn't make sense. LOL
From my Allianced S5!

benwaffle said:
Source is here https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher
Click to expand...
Click to collapse
Thank you so much, man.
From my Allianced S5!

Used this to make a backup in safestrap just to test it out. Worked great, so I plan on trying to flash the Imperium ROM when I gat a chance. This will be very useful since Flahfire doesn't work with aroma yet. Thanks for this.

Cats_PJs said:
Used this to make a backup in safestrap just to test it out. Worked great, so I plan on trying to flash the Imperium ROM when I gat a chance. This will be very useful since Flahfire doesn't work with aroma yet. Thanks for this.
Click to expand...
Click to collapse
Thank you for confirming, bro. I'm glad it's helping. And what ROM are you talking about? Can't find it in the development section. I want to flash it, too!

K-alz said:
Thank you for confirming, bro. I'm glad it's helping. And what ROM are you talking about? Can't find it in the development section. I want to flash it, too!
Click to expand...
Click to collapse
It's in the 9505 forum. I know that those ROMs worked on our phones on 4.4.2 so I thought they may still work, but I'm not guaranteeing anything.

Cats_PJs said:
It's in the 9505 forum. I know that those ROMs worked on our phones on 4.4.2 so I thought they may still work, but I'm not guaranteeing anything.
Click to expand...
Click to collapse
Well, I think you should ask in the thread first. Just in case the ROM comes with any other kernel then give it a try.
from my lollipoped Alianced N3!

K-alz said:
Well, I think you should ask in the thread first. Just in case the ROM comes with any other kernel then give it a try.
from my lollipoped Alianced N3!
Click to expand...
Click to collapse
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.

Cats_PJs said:
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Click to expand...
Click to collapse
That's an easy one. If you can sideload nova launcher, I think that message won't pop up. Unless, it's constant.
Could you give me the link for the thread?

Cats_PJs said:
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Click to expand...
Click to collapse
Or maybe you did a dirty flash? Did you wipe system along with caches and internal in safestrap?

K-alz said:
Or maybe you did a dirty flash? Did you wipe system along with caches and internal in safestrap?
Click to expand...
Click to collapse
I always clean flash, here's the link. Good luck, I would have looked into it more but I need my phone for tomorrow and it's time to call it a day .http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889

Cats_PJs said:
I always clean flash, here's the link. Good luck, I would have looked into it more but I need my phone for tomorrow and it's time to call it a day .http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889
Click to expand...
Click to collapse
Thanks. I won't flash it now. I'll wait for tomorrow as well. ?
from my lollipoped Alianced N3!

I updated to OC3 via the safestrap method muniz_ri posted. I completely debloated my phone and decided to play a bit. Thinking hey I need a backup! So I downloaded this NC1 flasher granted it root access and let it flash the NC1 kernel then hit the reboot button. Safestrap is alive. I made a backup of my now debloated rooted OC3 S4. Just to check I then in safestrap restored the backup I just made and flashed the recovery flashable OC3 kernel. While still in safestrap I wiped dalvik and cache then rebooted the phone. It went through the usual barrage of safestrap screens until the Ole Sammy logo finally showed up. When the phone booted I was greeted with nothing but force closes. No home screen nothing. Everything forced closed. Thinking the backup failed I first decided to boot stock recovery and delete the cache there. Upon reboot a bunch of safestrap screens then it booted up as usual. No force closes! The backup flashed fine and now have a slim working fall back of OC3. Thanks to everyone who has contributed here on xda. Without these forums my I337 would be att junk lol.

I flashed NC1 apk after installing safestrap and busybox on my Rom which had been flashed with The safestrap method. Flash worked great and then I backed up the Rom. I then flashed another Rom which I decided against and rebooted into safestrap and restored my original Rom. Perfect! I then tried to reboot into Safestrap with the NC1 apk and nothing happened it just rebooted into the Rom. I removed and reinstalled Safestrap and the NC1 apk and tired again. Nothing. Any Ideas?

Did you reinstall recovery thru safestrap too?

macasus76 said:
I updated to OC3 via the safestrap method muniz_ri posted. I completely debloated my phone and decided to play a bit. Thinking hey I need a backup! So I downloaded this NC1 flasher granted it root access and let it flash the NC1 kernel then hit the reboot button. Safestrap is alive. I made a backup of my now debloated rooted OC3 S4. Just to check I then in safestrap restored the backup I just made and flashed the recovery flashable OC3 kernel. While still in safestrap I wiped dalvik and cache then rebooted the phone. It went through the usual barrage of safestrap screens until the Ole Sammy logo finally showed up. When the phone booted I was greeted with nothing but force closes. No home screen nothing. Everything forced closed. Thinking the backup failed I first decided to boot stock recovery and delete the cache there. Upon reboot a bunch of safestrap screens then it booted up as usual. No force closes! The backup flashed fine and now have a slim working fall back of OC3. Thanks to everyone who has contributed here on xda. Without these forums my I337 would be att junk lol.
Click to expand...
Click to collapse
I'm thinking the force closes happened because you restored your back up without a clean wipe, but that's just a guess, though.
rfb813 said:
I flashed NC1 apk after installing safestrap and busybox on my Rom which had been flashed with The safestrap method. Flash worked great and then I backed up the Rom. I then flashed another Rom which I decided against and rebooted into safestrap and restored my original Rom. Perfect! I then tried to reboot into Safestrap with the NC1 apk and nothing happened it just rebooted into the Rom. I removed and reinstalled Safestrap and the NC1 apk and tired again. Nothing. Any Ideas?
Click to expand...
Click to collapse
First of all, if you have used the safestrap method to upgrade to OC3, then you don't need to reinstall SS and busybox again. They're both there already. It's just that SS isn't compatible with the OC3 kernel and that's why it doesn't show up and only shows up when you flash NC1 back (because it works with NC1).
Secondly, I remember that on KitKat, when having trouble with SS installing it was recommended to download SElinux changer and change the SElinux to permissive instead of enforcing. I don't know if this method would work with Lollipop and never actually tried it. Do you wanna try that and see? Do it on your own risk, though. Lol
If not then just install SS again and uninstall recovery and reinstall it again and try.

Let me see if i got it right
1. Extract the .zip file and intall the app
2. Flash the nc1 kernel using the app
3. Boot to ss
4. Install the rom
5. Flash the oc3 kernel using ss
Is that right?

7mada said:
Let me see if i got it right
1. Extract the .zip file and intall the app
2. Flash the nc1 kernel using the app
3. Boot to ss
4. Install the rom
5. Flash the oc3 kernel using ss
Is that right?
Click to expand...
Click to collapse
Yes. But if you're already on a KK ROM, you don't need it. This is only for those who are on a Lollipop ROM and want to reboot into SS.
Also, if you want to flash a ROM, like you said, make sure to wipe your phone first so you don't a ton of FCs.

Can't have root and custom kernel at the same time.

As the title would imply, every time I install either a custom kernel, or root, it will remove the other. I have a google pixel (verizon model, unsure if this matters) that will work fine with either one by itself, but I cant have both. ElementalX is the only kernel that seems to work, but it won't really cohabit with either Magisk or SuperSU. Any help or ideas would be appreciated.

JadeTank said:
As the title would imply, every time I install either a custom kernel, or root, it will remove the other. I have a google pixel (verizon model, unsure if this matters) that will work fine with either one by itself, but I cant have both. ElementalX is the only kernel that seems to work, but it won't really cohabit with either Magisk or SuperSU. Any help or ideas would be appreciated.
Click to expand...
Click to collapse
How is your flashing process? You're supposed to flash kernel and then magisk straight after and then reboot into system. If you do it the other way around then the kernel overwrites magisk as magisk will patch the previous version first. So in short flash kernel and then magisk after that reboot into system.

Arju said:
How is your flashing process? You're supposed to flash kernel and then magisk straight after and then reboot into system. If you do it the other way around then the kernel overwrites magisk as magisk will patch the previous version first. So in short flash kernel and then magisk after that reboot into system.
Click to expand...
Click to collapse
I managed to get magisk running with a kernel, but it was only after having to factory reset. For some reason, when I was trying it before Magisk didnt work. But I did follow the steps you said and it worked, so thanks for the tip. If you know btw, is there a reason SuperSU wont work with a custom kernel? Im relatively new to this kind of stuff, and was wondering if it wont work that way.

JadeTank said:
I managed to get magisk running with a kernel, but it was only after having to factory reset. For some reason, when I was trying it before Magisk didnt work. But I did follow the steps you said and it worked, so thanks for the tip. If you know btw, is there a reason SuperSU wont work with a custom kernel? Im relatively new to this kind of stuff, and was wondering if it wont work that way.
Click to expand...
Click to collapse
I wouldn't recommend SuperSU anymore. Magisk hides root from apps so that apps that search for root would work. With SuperSU you won't find that. SuperSU is pretty much outdated.

JadeTank said:
I managed to get magisk running with a kernel, but it was only after having to factory reset. For some reason, when I was trying it before Magisk didnt work. But I did follow the steps you said and it worked, so thanks for the tip. If you know btw, is there a reason SuperSU wont work with a custom kernel? Im relatively new to this kind of stuff, and was wondering if it wont work that way.
Click to expand...
Click to collapse
To add to what @Arju said, no version of SuperSU works on with Android 8.1 on the 2016 Pixel.

Arju said:
How is your flashing process? You're supposed to flash kernel and then magisk straight after and then reboot into system. If you do it the other way around then the kernel overwrites magisk as magisk will patch the previous version first. So in short flash kernel and then magisk after that reboot into system.
Click to expand...
Click to collapse
If it's an AnyKernel2 kernel, it doesn't matter what order you flash them in since only ramdisk modifications are made. I prefer flashing Magisk first so it backs up the stock boot.img.