Today, I fixed issue of kernel panic when magisk installed on latest Ressurection Remix
This is tested once and stopped after installing module "Viper4Android"
This was kernel issue of secureboot, we don't tested it on stock rom, but feel free to experiment with my fixed kernel
LINK: https://mega.nz/#!eGBlVaqS!3scLMy7kZUcjLCHk7jL86OEM3tBTAwwGoEQLwUdBVbE
UPDATE: One user tried root with stock kernel and bootloop, when root work with mine kernel and zip install method, this needs more tests but give us a chance
Related
I am currently running Resurrection Remix ics v1.7 with thoravukk kernal 2.48. I am looking to update to Resurrection Remix ics v1.8.1. I also want to flash the latest thoravukk kernal and the tablet mod as well. After i install v1.8.1 should i install the kernal first then mod or the other way around. I also have my phone undervolted so do i need to set the voltage back to the orginal settings as well?
normally Kernel can be flashed either before or after flashing the MOD, no difference.
still better to ask the dev of the MOD, whether the MOD required a specific Kernel first or not?.
Your undervolt setting will be automaticaly reset when you flash the Kernel, no problem you can set it again after flashing the Kernel.
Hi,
Kinda new to all this so bear with me, I installed the custom ROM ViperX+ 1.0.3, which is working without any problems. I've currently got the stock kernel flashed and was thinking of changing it but theres two that I can choose from nik3r's Elite kernel or the repacked version. however I was wondering does the repacked version get updated as soon as nik3r's is becasue is updated often.
Thanks
My favorite custom kernel is the EliteKernel by nik3r.
http://forum.xda-developers.com/showthread.php?t=2012320
It runs smooth, stable and I never got any kind of error.
I use repacked version and very smooth and stable, don't worry, elite kernel is very stable and I dont think there will be an update shortly.
I'm trying to install AJK Kernel 4.9 AOSP on Hellybean 4.3 and also tried on Carbon Rom 4.3. I use a kernel cleaning script, flash the kernel, reboot recovery, reset stweaks profiles, and have tried fix permissions also. Each time the phone starts up on reboot i get fc's on phone.android.com and others. Does anyone know what I'm doing wrong here? I have read where others have installed this kernel on these roms with out any trouble. BTW, the AJK thread is closed so I posted here.
Thanks
Probably because those roms are based after the "ramdisk" update issue. Basically, most (if not all) AOSP-based roms after a specific update (can't remember the exact date or month, think it's October, though) no longer allow the use of custom kernels unless they feature an updated ramdisk.
AJK doesn't have this yet, but AJ is working on 5.0 - that will solve the problem.
Hey Guys,
first things first: I am Using a European Droid Razr (xt910).
ROM: cm-11-20140627-NIGHTLY-umts_spyder
Gapps: gapps-kk-20131208-no_set_metadata
Kernel: JBX-Kernel-3.3-Hybrid-Spyder-4.4_2014-06-16
Today i rooted my razr and tried to install a custom rom with safestrap. I Did everything like it was explained in this GUIDE and it worked fine. The rom worked but i noticed a faster battery drain.
To fix this i tried to install this KERNEL but after installing it with safestrap the OS (Cm11) i installed before was gone. I am pretty new at this stuff and couldnt find a solution so far.
I wiped my phone a couple of times and everytime i tried to install the Kernel after CM11, my fresh CM11 was gone so i had to install CM11 again and afterwards JBX was gone. Pretty sad :c
CM11 itself is working fine and the installation of JBX-Kernel Hybrid worked fine too, but with the new Kernel my OS/CM11/ROM is gone.
I hope you can help me, i couldnt ask my question in the developers forum cause i just created this account.
You are not wiping your system in the process. Are you?
I have been downloading and installing and downloading..... Reading and researching!!! I have an unlimited data plan so let's face it I kick the hell out of it. I like to watch movies a lot on showbox or on cartoon HD threw mhl HDMI to my TV (mirrored). I can't stand touchwiz ROMs and I also like to have the latest even if its on my sgs3. I love this phone. Anyways after loads of messing around installing loads of different ROMs I realized the truth is that only Sammy tw ROMs have the USB drivers. This was all because I read on some post somewhere that said they had a custom ROM and a touchwiz launcher and to use mhl they simply boot the tw launcher for mhl use only and then back to Google launcher as a daily driver. Post didn't say which custom ROM they where using and/or if they had a custom kernel installed. So that's what set me of trying to conker making it work and my solution to this problem is "arter97 kernel" plus dual boot.zip plus back to noot ROM and I really do like the resurrection remix ROMs. I like the new marshmallow 6.1 but the arter97kernel doesn't support this so I settled for RR lollipop 5.1.1 v5.5.9 as the first ROM. installed this as per normal protocol and then flash the arter97 kernel using twrp recovery. I used v4.1 kernel because it has load more customizations than v5 for ex. Over clocking to 1800mhz and more Governors etc. Now arters back to noot kitkat 4.4.4 is very stable very good ROM. So once the first aosp ROM is OK and stable with the kernel (make sure you flash superSU) boot back into recovery and flash the dual boot zip and anything flashed during that visit to the recovery goes to the 2nd ROM partition. Next flash the back to boot ROM and superSU and boot back into 1st ROM (automatically) but don't wipe cache/dalvic/data (this will just wipe from the 1st ROM). Now the aswitch app will work to boot into the 2nd ROM. And because you flashed the superSU into 2nd ROM the aswitch will work to allow you back to the 1st ROM!!!! Every time you want to flash to 2nd ROM use the dual boot zip first. Because the back to boot kk 4.4.4 ROM already has arter97 kernel don't flash the kernel zip just leave it and it will have the same arter97 kernel once booted. If you flash the kernel to 2nd ROM it will just cause lag and instability The only problem I have had is whilst using this whole configuration is when inserting the mhl lead into sgs3 it freezes and/or shutdown. After a little tweaking I figured out it was a CPU issue and to enable the mhl and showbox use I used atweaks config app and changed Max over clock CPU to 1704mhz and governor setting to performance!!! Now this profile makes the CPU stick at 1704mhz permanently. This method works but unfortunately also creates massive battery drain so I have also been messing with the USB charge/power variables. But do be careful if you follow any instructions on this post as I am not responsible for a bricked divice so make sure you do your homework. This arter97 kernel is EOL @v5 for the sgs3 so versions 4.1 and 5 are only compatible for lollipop 5.1.1 so always read changelogs. Many thanks to arter97 for this dual boot and customisable kernel and ported ROM.