Hello! I want to install Extreme Kernel on stock ROM, but I want to backup stock kernel in order to get OTAs (everytime I received an update, I would install/restore stock kernel). How can I do that? Thanks!
The easiest way is to use Magisk Manager.
Stock system -> install Magisk (it automatically creates backup of currently flashed kernel) -> install custom kernel. When OTA arrives, restore stock boot.img from withing Magisk Manager, install OTA, reboot, install Magisk, install custom kernel.
Doublecheck if custom kernel uses only stock Wifi drivers. Some kernels install custom driver in system partition, breaking OTA.
_mysiak_ said:
The easiest way is to use Magisk Manager.
Stock system -> install Magisk (it automatically creates backup of currently flashed kernel) -> install custom kernel. When OTA arrives, restore stock boot.img from withing Magisk Manager, install OTA, reboot, install Magisk, install custom kernel.
Doublecheck if custom kernel uses only stock Wifi drivers. Some kernels install custom driver in system partition, breaking OTA.
Click to expand...
Click to collapse
Does it work in all custom kernels except Void which indicated it won't? If I remember correctly it only works with Franco.
whrynox said:
Does it work in all custom kernels except Void which indicated it won't? If I remember correctly it only works with Franco.
Click to expand...
Click to collapse
I've been using it personally with Franco kernel, but in theory should be fine with any kernel. But I didn't try other kernels, because most of them break OTA..
Related
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Nope. Cant with custom recovery..
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Click to expand...
Click to collapse
Your phone will boot loop if you don't go back to stock recovery first. I tried just to see what would happen and that's what happened. People who tried to flash it with Flashify reported no success.
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery. Thanks
Click to expand...
Click to collapse
Stock ROM? Important information you omitted. From a guy who always runs the latest stock ROM rooted and custom recovery here's how you do it: You do not have to remove them first, and although they (SU & kernel) will be overwritten with the new boot.img, it is very easy and straightforward. You need the TWRP flashable (beta) OTA zip file, in the OP here. Put the latest SU and your custom kernel on the device root, or wherever. (should already be there) and then reboot to TWRP recovery. Select "Install" and then select the OTA you downloaded above, and tap "Add more zips". Next you want to add the latest SU zip (2.79 SR3) and last add your kernel. Mine is EX. Once you have queued all 3 zips, in less than a minute you will be back up and running 7.1.2 , rooted and with kernel. Even if you flash each file individually you will still be ok. (OTA, SU, Kernel). See the same thread further down... Credit for the TWRP flashable OTA goes to @Displax.
Hi, i am rooted with supersu since i have my oneplus 5. i have a kernel installed on stock OOS. But now i want to try Magisk. What is the way to uninstall properly supersu and flash magisk please? thanks for your help
edit: i already tried to supress the root with supersu option ang got a bootloop after...
Uninstall SuperSU (there should be an unroot option somewhere) and flash Magisk.
Or flash the stock OxygenOS kernel, that should remove root.
are you sure flashing stock kernel remove root...? (i have a backup of the sock kernel just in case of..)
brunsman6229 said:
are you sure flashing stock kernel remove root...? (i have a backup of the sock kernel just in case of..)
Click to expand...
Click to collapse
Yes it will remove root, but not very cleanly. Some files will be left over (/data/su.img and /data/stock_boot*). These leftover files shouldn't cause any harm except eating disk space, but you may want to remove them if you want to re-root from a clean slate.
As I said, SuperSU should have a "full unroot" option somewhere in its settings. Use that, reboot; flash Magisk.
Hey everyone,
I tried installing magisk 16.0
firstly i did ,
unlocked bootloader,
then installed twrp recovery 3.2.1
booted the phone installed magisk manager,
then again in twrp recovery
i tried flashing the magisk 16.0,the magisk gets flashed but the phone does not boot up to system,
i dont get what mistake i am doing,
i want to use the 'CAMERA2 API' on my moto g4 plus,
and nothing else
But they say you need to root for that,
so i am trying
Please help me with this...
You need to flash a custom kernel (ElementalX) before rooting your device when using stock firmware.
In addition to thorin0815's message, you cannot root on the stock Motorola kernel - attempting to root on the hudsoncm kernel causes bootloops. You may be able to reboot to TWRP, restore your TWRP backup (you did make a backup, right?) then flash ElementalX, then magisk. If you're still bootlooping, you may have to re-flash the stock ROM then try again.
thorin0815 said:
You need to flash a custom kernel (ElementalX) before rooting your device when using stock firmware.
Click to expand...
Click to collapse
Thankyou I'll try this also..
echo92 said:
In addition to thorin0815's message, you cannot root on the stock Motorola kernel - attempting to root on the hudsoncm kernel causes bootloops. You may be able to reboot to TWRP, restore your TWRP backup (you did make a backup, right?) then flash ElementalX, then magisk. If you're still bootlooping, you may have to re-flash the stock ROM then try again.
Click to expand...
Click to collapse
Is this the convenient way or shall I use the apps like one click rooting ? Kingroot something..?
PushkarajK said:
Is this the convenient way or shall I use the apps like one click rooting ? Kingroot something..?
Click to expand...
Click to collapse
I'm not sure if king root or the one click root would work, if they don't flash the custom kernel first you'd be back with a non booting device. Best to flash root yourself, that way you'll also learn the process too
echo92 said:
I'm not sure if king root or the one click root would work, if they don't flash the custom kernel first you'd be back with a non booting device. Best to flash root yourself, that way you'll also learn the process too
Click to expand...
Click to collapse
Yes got it ,thankyou for the help:good:
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
What firmware or ROM are you currently running, and what version of magisk are you using?
kwebber321 said:
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
Click to expand...
Click to collapse
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
ALPH000 said:
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
Click to expand...
Click to collapse
Is there a custom kernel known to be compatible with the stock Pie ROM?
harryspar said:
Is there a custom kernel known to be compatible with the stock Pie ROM?
Click to expand...
Click to collapse
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
echo92 said:
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
Click to expand...
Click to collapse
For Nougat, stock kernel is not rootable.
You have to replace it with elementalx kernel and then flash magisk.
However, when talking about Oreo stock firmware,
Situation gets inverted.
When flashed magisk with ElementalX 3.0.1, phone will not boot up.
And, stock kernel can be easily rooted by simply flashing magisk.
So, there is no need of ElemenralX kernel for rooting Oreo stock ROM unless you need it.
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
harryspar said:
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
Click to expand...
Click to collapse
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
echo92 said:
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
Click to expand...
Click to collapse
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
harryspar said:
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
Click to expand...
Click to collapse
I hope you get xposed working on Oreo - if you do get magisk functioning, maybe this xposed plugin could work? https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Else there's edxposed https://forum.xda-developers.com/xposed/list-xposed-modules-android-pie-ed-t3892768 though I have no idea if xposed functions on stock Oreo.
Hey guys,
So I grabbed the latest factory image, patched boot with Magisk, and flashed it to the phone. Works great.
But now I want to use TWRP. I can't figure out how to get TWRP on this device.
It seems there's no recovery partition, so I can't use fastboot flash recovery twrp.img. I know I can flash arter97's kernel, which has TWRP baked-in, but I'm trying to figure out how to do it with the stock-Magisk-patched kernel.
Can someone please hit me with a clue-stick?
-edison
get the razer phone 2 arter97 kernel and flash to boot. twrp will be installed.
Marcos8760 said:
get the razer phone 2 arter97 kernel and flash to boot. twrp will be installed.
Click to expand...
Click to collapse
I'm on the PSMR3-RC002 version. Which version of Arter97 kernel works and is stable? Also, does this effect the Magisk root availability, or do I need to run Magisk patch on Arter's Kernel? I had used R12 in the past, prior to the new Magisk Boot-patch scheme, and also lost TWRP afterwards. I haven't gone and tried to reflash Arter97-R12 since I didn't want to bork anything and couldn't find an definitive answer.
MoPhoMike said:
I'm on the PSMR3-RC002 version. Which version of Arter97 kernel works and is stable? Also, does this effect the Magisk root availability, or do I need to run Magisk patch on Arter's Kernel? I had used R12 in the past, prior to the new Magisk Boot-patch scheme, and also lost TWRP afterwards. I haven't gone and tried to reflash Arter97-R12 since I didn't want to bork anything and couldn't find an definitive answer.
Click to expand...
Click to collapse
@MoPhoMike,
I use arter kernel v12.0, seems to be as stable as can be, no hiccups or issues with 12 for me and have been running 12 for about a year.
Flash arter kernel to boot "fastboot flash boot arterxxx.img" xxx is for whichever version you flash or how you named the img.
Once the arter kernel is flashed, i then boot into TWRP. Either from bootloader on your phone, select recovery or use fastboot commands.
Then you can flash magisk from TWRP.
.
NOTE, i have some posts where folks say to boot up the phone after flashing arter kernel, then reboot to recovery and flash magisk. I do it the way i noted above and never had issues.
****No need to patch Magisk that I'm aware of****
Hope this helps...
The new version of Magisk doesn't install via recovery, but from Magisk Manager, and in doing so, it patches the boot.img from the app, then reboots, which then removes TWRP. I may just try to flash arter12 and see what happens. It sucks, because I don't have TWRP installed, and therefore can't make a nandroid backup.