Database Users

Magisk with android 9

I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?

xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Not the way you are doing it. I boot to TWRP, without installing it and have TWRP install the full zip.

Hm I'll try this. Used to the boot patching.

xringo said:
Hm I'll try this. Used to the boot patching.
Click to expand...
Click to collapse
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.

lorax70 said:
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
Click to expand...
Click to collapse
You can give link file magisk for use on android 9.

newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Fwiw. I've been using this magisk version for dp3-5, but there are newer versions, but 16.4 works for me...
https://thedroidarena.com/download-magisk-16-4-beta/
I may try a newer version at some point, but I'm in no rush.

newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Got this from the Flash kernel thread. It works fine on Pie :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk

xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Make sure your using 16.7 you have to change in setting to beta. Same thing happened to me trying to use 16.0

I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674

After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?

I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Airpil said:
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Don't wipe your phone! Just flash the new boot.img from the image file (not OTA file) and you will be able to go back to your Android system and disable the pin. After disable the pin, boot into TWRP and flash the Magisk from here https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Hope this helps!

madmuthertrucker said:
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
Click to expand...
Click to collapse
Use magisk uninstall first and this should solve the issue.

lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP

Brakiss said:
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Click to expand...
Click to collapse
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.

Badger50 said:
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Click to expand...
Click to collapse
Where did you see this? I have pattern and would like to keep it.

Brakiss said:
Where did you see this? I have pattern and would like to keep it.
Click to expand...
Click to collapse
One of the other threads. Here's the twrp version though. https://dl.twrp.me/taimen/

Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?

pr1vate piles said:
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
Click to expand...
Click to collapse
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk

Badger50 said:
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Your not wrong there. Tried it as you suggested, same thing, hanging at the G logo page with the bar animation under it. Had to run the uninstaller to get back into my phone. Very odd

[GUIDE] How to root Stock Oreo 8.1 soak test with magisk

I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
INSTALLATION
1.back up your system, data and boot partition. If the process fails restoring those will revert the changes.
2.Download and flash Magisk 15.3 (later versions didn't work for me, phone wouldn't boot at all) through twrp.
3.Flash the latest f2fs loop back work around.
4. Flash magisk manager for recovery (mm-2018.8.1.zip attached below)
5.Boot your phone
UPDATING TO MAGISK 16.0
Once the phone has booted:
1.install magisk manager 5.8.3 (attached below)
2.Open magisk manager
3.if any update is available for magisk manager, install it.
4.click on the button that tells you to update magisk to latest version.
IMPORTANT:
5. Select the direct installation method. Flashing the update through recovery will render the phone unable to boot again.
That's it, thanks.
=======
Downloads:
Magisk 15.3
f2fs-loopback-bug-workaround-2018.8.1.zip
mm-2018.8.1.zip
Magisk Manager v5.8.3.apk

freeZbies said:
I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
....snip
Click to expand...
Click to collapse
Interesting.
For what is the magisk manager for recovery needed?

Wolfcity said:
Interesting.
For what is the magisk manager for recovery needed?
Click to expand...
Click to collapse
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
EDIT: Mm for recovery is actually a module that allows you to list and Uninstall modules from Twrp in case your phone no longer boots after flashing a module.
and you're correct, magisk 15.3 does include magisk manager and will install it. the problem I had is that I flashed magisk 15.3 over a system where either the boot.img was already patched, and I experienced that magisk manager sometimes wont be installed in these cases
Sent from my Moto G (5) using Tapatalk

freeZbies said:
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
Click to expand...
Click to collapse
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.

nicolap8 said:
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
Click to expand...
Click to collapse
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.

freeZbies said:
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
Click to expand...
Click to collapse
At least it's inside the official 15.3. But I remember that MM was often not installed in earlier builds.
Sent from my Moto G5 Plus using XDA Labs

I Got Another Method Also
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy

Sonisudhanshu said:
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Click to expand...
Click to collapse
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Sent from my Moto G (5) using Tapatalk

freeZbies said:
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Click to expand...
Click to collapse
I'm on 3.2.2.0 and it offers the ability to backup EFS, 3.2.1.0 also.
As said, for persist there are several unofficial builds but you can back it up with those commands in TWRP terminal:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
for backup and
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
for restore.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
1. Because I didn't have any option to backup efs in twrp.32.bit
2. I was not sure but I just flashed it so that no problem occurs like booting issue..
Hope this helps

Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming..... If this helped , i would be gladed

Do the magisk modules work ?

llucas_br said:
Do the magisk modules work ?
Click to expand...
Click to collapse
Which magisk module?
Sent from my Moto G5 Plus using XDA Labs

TWRP flashable Oreo 8.1 OTA updates
Sonisudhanshu said:
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming.....
Click to expand...
Click to collapse
There are already TWRP flashable Oreo 8.1 OTA updates available.
https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913

thanks

Chekm8Qc said:
I just installed magisk 17.1 and it worked right away. Even safety net passes.
Click to expand...
Click to collapse
Chekm8Qc confirmed here https://forum.xda-developers.com/showpost.php?p=77906610&postcount=56 that he could directly install the latest Magisk version (currently 17.1) on Oreo 8.1 OPP28.85-16 eliminating the need to install an older version first as recommended in this thread.

I can also confirm, installed straight away 17.1 and worked flawlessly, no bootloop and safety net passed.

Please Update!
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080

G5-User7080 said:
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
Click to expand...
Click to collapse
in oreo stock you dont need f2fs bug module, because is working without it

{SOLVED} Lost root after update and succesfull magisk flash

Hey guys,
Just flashed the latest Oxygen update the way i always do but this time i lost root.
Running stock rom with root (Magisk) and TWRP.
Flashed update
Cleaned dalvik/cache
Flashed Magisk.zip
Cleaned dalvik/cache again
Reboot
Twrp is still there, bootloader unlocked, magisk manager works to...... But no root, magisk manager says "magisk is not installed"
Never had this issue before....

g-member said:
Hey guys,
Just flashed the latest Oxygen update the way i always do but this time i lost root.
Running stock rom with root (Magisk) and TWRP.
Flashed update
Cleaned dalvik/cache
Flashed Magisk.zip
Cleaned dalvik/cache again
Reboot
Twrp is still there, bootloader unlocked, magisk manager works to...... But no root, magisk manager says "magisk is not installed"
Never had this issue before....
Click to expand...
Click to collapse
Which oxygenOS? Which magisk version? Did you tried to flash magisk uninstaller before flashing the oxygenOS update and go ahead with the further steps?

Latest Oxygen, and no dit not uninstall magisk before flashing the update, never did and worked fine....
Using Magisk 17.00 latest

g-member said:
Latest Oxygen, and no dit not uninstall magisk before flashing the update, never did and worked fine....
Using Magisk 17.00 latest
Click to expand...
Click to collapse
Which oxygenOS(stable or beta)? Try to install magisk again, use v17. 3 if not working, flash uninstaller as mentioned before

That did the trick, thnx

g-member said:
That did the trick, thnx
Click to expand...
Click to collapse
Which one? To help others you can mark the thread as [SOLVED] in the headline:good:

First flashed the uninstaller and reflashed 17.3 Magisk.
How do i mark this post?

g-member said:
First flashed the uninstaller and reflashed 17.3 Magisk.
How do i mark this post?
Click to expand...
Click to collapse
Edit the title and add [SOLVED] at the beginning.

updated to 9.0.11 official. can't root now

I updated to OOS 9.0.11. i was using root before the update. But this update just unrooted my one plus 6t. And now i get to root it with magisk. I installed TWRP through ADB. It worked but when i tried to flash magisk in twrp. I couldn't find the magisk file in twrp.please help me.

swahmad76 said:
I updated to OOS 9.0.11. i was using root before the update. But this update just unrooted my one plus 6t. And now i get to root it with magisk. I installed TWRP through ADB. It worked but when i tried to flash magisk in twrp. I couldn't find the magisk file in twrp.please help me.
Click to expand...
Click to collapse
Let's see if we can help you But first, just an FYI, you have posted in the wrong section, you should have posted in the Question and Answer section....
Moving on, what version of TWRP did you flash?
follow the TWRP guide here and use Magisk version 18.0
TWRP https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Stable version. Then you should be fine.
Sent from my ONEPLUS A6013 using Tapatalk

phillymade said:
Let's see if we can help you But first, just an FYI, you have posted in the wrong section, you should have posted in the Question and Answer section....
Moving on, what version of TWRP did you flash?
follow the TWRP guide here and use Magisk version 18.0
TWRP https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Stable version. Then you should be fine.
Click to expand...
Click to collapse
Did you root yours while on on OOS 9.0.11?

swahmad76 said:
Did you root yours while on on OOS 9.0.11?
Click to expand...
Click to collapse
I have two 6Ts on 9.0.11 rooted. Magisk 18.0, no issues.

OhioYJ said:
I have two 6Ts on 9.0.11 rooted. Magisk 18.0, no issues.
Click to expand...
Click to collapse
I installed the stable magisk. But no luck so far. The problem is that i can't find magisk zip in twrp recovery mode to flash it.

phillymade said:
Let's see if we can help you But first, just an FYI, you have posted in the wrong section, you should have posted in the Question and Answer section....
Moving on, what version of TWRP did you flash?
follow the TWRP guide here and use Magisk version 18.0
TWRP https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Stable version. Then you should be fine.
Click to expand...
Click to collapse
And i flashed fajita version.

You need to fastboot boot twrp image and then sideload twrp installer, then magisk 18 on top of that.

BIGWORM said:
You need to fastboot boot twrp image and then sideload twrp installer, then magisk 18 on top of that.
Click to expand...
Click to collapse
I did that in the first place. As i said i had root on the previous version. But after update. I just couldn't find magisk file in twrp recovery mode to flash it for root.

swahmad76 said:
I did that in the first place. As i said i had root on the previous version. But after update. I just couldn't find magisk file in twrp recovery mode to flash it for root.
Click to expand...
Click to collapse
Updating removes root, so you have to do it all over again. It's what has to be done with A/B partitions (unless flashing full update from twrp or going the uninstall/restore images magisk-flash to other slot route).

sssarg said:
Updating removes root, so you have to do it all over again. It's what has to be done with A/B partitions (unless flashing full update from twrp or going the uninstall/restore images magisk-flash to other slot route).
Click to expand...
Click to collapse
Then tell me what to do all over again?

Why don't you just download Magisk.zip again. Boot back to TWRP and flash
Sent from my OnePlus6T using XDA Labs

swahmad76 said:
Did you root yours while on on OOS 9.0.11?
Click to expand...
Click to collapse
No, I rooted on 9.0.7
Sent from my ONEPLUS A6013 using Tapatalk

Koont said:
Why don't you just download Magisk.zip again. Boot back to TWRP and flash
Click to expand...
Click to collapse
Did that... 100 times bro

Koont said:
Why don't you just download Magisk.zip again. Boot back to TWRP and flash
Click to expand...
Click to collapse
I just can't find any zip file in twrp! That's the issue.

sssarg said:
Updating removes root, so you have to do it all over again. It's what has to be done with A/B partitions (unless flashing full update from twrp or going the uninstall/restore images magisk-flash to other slot route).
Click to expand...
Click to collapse
You mean like unlock bootloader again? And then twrp and magisk?

swahmad76 said:
You mean like unlock bootloader again? And then twrp and magisk?
Click to expand...
Click to collapse
After unlocking bootloader.
Sent from my OnePlus 6T using XDA Labs

swahmad76 said:
I did that in the first place. As i said i had root on the previous version. But after update. I just couldn't find magisk file in twrp recovery mode to flash it for root.
Click to expand...
Click to collapse
Are you serious right now? Your can't find it either because your haven't downloaded it or haven't looked in the right directory for the zip. Download magisk boot into TWRP choose install navigate to the directory the zip is stored in then choose it and swipe to flash. And FYI anything you download normally goes to the Download folder.

Use one of the rooting tools it will do all for you, more simple.
9.0.11 don't prevent any method of rooting, it's in your side that something is wrong

Striatum_bdr said:
Use one of the rooting tools it will do all for you, more simple.
9.0.11 don't prevent any method of rooting, it's in your side that something is wrong
Click to expand...
Click to collapse
Which tool specifically?

Man, stop, I don't know, try them all

G4 plus is bricking after installing Magisk?

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.