Database Users

Installing AutoMagisk with Nougat Update Device Won't Boot

So every time I try to install AutoMagisk on my freshly updated and reset Nougat install, the device won't boot at all. I have to keep restoring from my NAND in TWRP.
I've tried All the versions of Magisk from 12 to 9. Am I doing something wrong?

ZeroManArmy said:
So every time I try to install AutoMagisk on my freshly updated and reset Nougat install, the device won't boot at all. I have to keep restoring from my NAND in TWRP.
I've tried All the versions of Magisk from 12 to 9. Am I doing something wrong?
Click to expand...
Click to collapse
Did you try installing elementalX kernel first and then flashing Magisk? If you are on stock nougat use the kernel below.

Danny1976 said:
Did you try installing elementalX kernel first and then flashing Magisk? If you are on stock nougat use the kernel below.
Click to expand...
Click to collapse
Installing that Kernel then Magisk v12 worked! Thanks so much!

Root XT1644 on Nougat?

So I just updated to the latest xt1644 Nougat JP25.93.14-4 and am having an issue installing TWRP and getting it to stick. I installed it and even did a backup, but once I boot to System and then back to bootloader, and finally to recovery, it goes back to stock recovery. Also I am unsure of how to root this device now with Nougat. I've seen on a few sites differing methods. One site had a download for what they called a root package and it was a SuperSU 2.76 version. Another site said to use Phh SU and just install TWRP and then flash Phh. I don't want to mess anything up, can someone point me in the right direction since it seems everything in this forum is for a device other than the XT1644. Lastly, is it possible to revert back to Marshmellow using fastboot, or is that now not possible? I have unlocked my bootloader, obviously. Thanks.

After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.

tywinlannister7 said:
After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.
Click to expand...
Click to collapse
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.

robn30 said:
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.
Click to expand...
Click to collapse
try latest twrp 3.1.0

I got it working. I had originally set it to read only and I think that was the issue. Reinstalled it and mounted system and then choose to allow modifications. It then worked. Now onto root, we will see how that goes.
Sent from my XT1575 using Tapatalk

tywinlannister7 said:
try latest twrp 3.1.0
Click to expand...
Click to collapse
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk

robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information

robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:

echo92 said:
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information
Click to expand...
Click to collapse
Thanks for all the information, it is very much appreciated. Thanks to pastorbob62 as well. This information will be very useful.
Sent from my XT1575 using Tapatalk

pastorbob62 said:
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:
Click to expand...
Click to collapse
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk

robn30 said:
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk

robn30 said:
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
You are very welcome. Glad you got it figured out and all is working well. :good:

Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?

1emrys1 said:
Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?
Click to expand...
Click to collapse
Generally you'd have to revert back to a clean stock ROM, no TWRP, no ElementalX, no magisk. The stock ROM also needs to be in a read only state (no modifications allowed in TWRP) and cannot be debloated (OEM partition needs to be untouched).
You could revert back to a TWRP backup made before you flashed ElementalX, provided you did not let TWRP make modifications. You'd also have to find a stock recovery (if you flashed TWRP), and restore a stock logo.bin as well if you flashed a custom logo.bin to hide the bootloader warning. Then, you should be able to apply OTA/security updates. Attempts to apply OTA updates with TWRP on your device will likely fail and leave you in a soft bootloop unless you boot via the bootloader. You could try this to break the bootloop: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The easiest and safest method I've found is to re-flash the stock ROM you have. Ensure this is the same firmware as you currently have and the latest firmware that you've flashed onto your device (don't downgrade your firmware if possible). You can re-flash without erasing your data by omitting the fastboot erase userdata command. However, I would recommend you back up your device anyway (e.g. in TWRP) and any important files, as although this procedure should not affect your data with that command omitted, any firmware flash has the possibility of affecting your device stability. That may require a factory reset/device wipe to fix. Backing up your data should be standard policy when it comes to flashing anything affecting your device's system/underlying firmware.
After re-flashing the stock ROM, you should be able to apply the OTA update.

Thanks a lot for the detailed answer. I really appreciate people like you. [emoji3]
Sent from my Redmi Note 3 using Tapatalk

Pre-rooted ROM for XT1644?

Just updated xt1644 to June 2017 update+TWRP+ElementalX kernel. Having problem booting to system after Magisk v14 flash. Rolled back system and uninstalled all Magisk.
With no NFC and no future OTAs coming, I'm ready to try a pre-rooted ROM. Prefer one that is compatible with ElementalX but I can roll back to stock kernel. Also prefer support for E911 USA dialing. Any help appreciated.

Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The custom ROMs I've tested (Lineage, Invicta, RR) are compatible with ElementalX and others should be, a quick search of their support thread for ElementalX will reveal if others have tried it before.

echo92 said:
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.

mel2000 said:
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
Click to expand...
Click to collapse
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)

HueyT said:
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
Click to expand...
Click to collapse
Thanks HueyT, that looks like a good backup prospect. In the meantime I'll be doing some research on that ROM to see how well it fits.

G4 Plus loses Magisk after reboot

For some reason the phone loses Magisk after every reboot. I'm guessing there's a flashable zip somewhere to fix this or something?

Choose an username... said:
For some reason the phone loses Magisk after every reboot. I'm guessing there's a flashable zip somewhere to fix this or something?
Click to expand...
Click to collapse
which magisk version you flash ?

Blueman1990 said:
which magisk version you flash ?
Click to expand...
Click to collapse
16. It's not my phone, it's a friend's, so i haven't really read much here

Choose an username... said:
16. It's not my phone, it's a friend's, so i haven't really read much here
Click to expand...
Click to collapse
Any idea what ROM they're running?
You could try uninstalling magisk, then flash a clean kernel (either from a backup made before rooting or if your friend is running a custom ROM, they could dirty flash the custom ROM. If rooting on stock, flash a clean stock Motorola kernel before reflashing ElementalX or vegito), then re-flash magisk.
If there were other root managers installed before magisk, this should remove any traces of those root managers on the kernel - even after uninstalling the previous root manager, which can interfere with magisk. At any rate, that should also provide a clean slate to root on again.

echo92 said:
Any idea what ROM they're running?
You could try uninstalling magisk, then flash a clean kernel (either from a backup made before rooting or if your friend is running a custom ROM, they could dirty flash the custom ROM. If rooting on stock, flash a clean stock Motorola kernel before reflashing ElementalX or vegito), then re-flash magisk.
If there were other root managers installed before magisk, this should remove any traces of those root managers on the kernel - even after uninstalling the previous root manager, which can interfere with magisk. At any rate, that should also provide a clean slate to root on again.
Click to expand...
Click to collapse
Yes, I installed AICP on it first but for some weird reason the GPU usage would go up to about 80 or 90% on idle and the UI would get laggy as hell. I switched over to Pixel Experience now and it's fine. On AICP i also tried Waver kernel and it didn't retain magisk if that's what you are saying.

I would suggest to flash stock firmware. All those alpha Oreo builds still have lots of bugs, especially with memory management, camera stuff and they tend to produce laggy interfaces. With stock firmware you're on the safe side, everything works perfect and you'll even have better battery backup and overall better performance.
You can root it with Magisk (ElementalX kernel) aswell.

Choose an username... said:
Yes, I installed AICP on it first but for some weird reason the GPU usage would go up to about 80 or 90% on idle and the UI would get laggy as hell. I switched over to Pixel Experience now and it's fine. On AICP i also tried Waver kernel and it didn't retain magisk if that's what you are saying.
Click to expand...
Click to collapse
Honestly, nothing like this has happened on my device! have you given try to RR or lineage 15.1? Or any nougat custom ROMs? like RR or Invicta? Are you flashing any modules along with Magisk??

Feeling stoopid... [Magsk-patched boot + TWRP]

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.