Database Users

Restore LG US996 back to Stock

Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!

darkghost568 said:
Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!
Click to expand...
Click to collapse
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono

OneDon said:
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono
Click to expand...
Click to collapse
Thanks!

deleted

Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.

DrPhant0m said:
Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.
Click to expand...
Click to collapse
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.

McNutnut said:
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.
Click to expand...
Click to collapse
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!

DrPhant0m said:
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!
Click to expand...
Click to collapse
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.

McNutnut said:
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.
Click to expand...
Click to collapse
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.

DrPhant0m said:
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.
Click to expand...
Click to collapse
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.

McNutnut said:
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.
Click to expand...
Click to collapse
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions

DrPhant0m said:
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions
Click to expand...
Click to collapse
You're welcome! Sorry it didn't work. I do know it takes a few minutes for it to boot up the first time, but I imagine you waited pretty long. I have heard of phones taking 10-15 minutes to boot up after flashing.
I did add US99610h stock firmware to my thread at https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573 if you want to return to the newest stock firmware of the US996.
I hope you are able to get Magisk installed as it's nice to get past SafetyNet. Good luck!

Root not sticking! Need professional help.

Good evening ladys and gentlemen,
hoping you can help me with my root-not staying-problem.
I have the A2017G B09 version. I already managed to unlock my device and I had root with xposed installed.
Sounds good so far, right?
Well my problem is that after the restart that is needed to activate my xposed modules, my root went away and I couldn't get it back. After that I tried to do it again but root wouln't stick no matter what.
And yes, I did use the "reboot disemmcwp" command.
I tried to root by flashing the newest chainfire supersu 2.79, since I have newest twrp 3.0.3-1.
It would be great if you would be able to help me on my journey and maybe explain to me the difference between systemless and normal, and what magisk is since I saw that op up a few times.
Oh and please tell me from where I should start if I want to work on everything android related (roms, kernel, apps) since my semsester is nearing its end.
Thanks in advance.

Systemless root means that the /system partition is not modified, however the boot image is altered. There is much hype on this, however there still are many mods out there requiring modifications of /system. I personally do not see any advantage of it, probably because I have been using custom ROMs for years, and custom ROMs has many alterations to the /system compared to stock or pure CM or AOSP roms. However it is clear that the future goes that way and eventually most of the mods will be systemless. The advantage is that you will supposedly be able to flash OTA upgrades, however if the OTA is also modifying the boot partition, then it doesn't matter, you will not be able to flash the OTA upgrade. So the benefits of systemless mods are arguable.
Magisk is an open root. it is systemless from the beginning and any module under Magisk framework will be systemless. So far no official Magisk release (latest at this time is v10.2) is compatible with the Axon stock ROM. However, the latest v10.3-beta2 seems to fix the root injection problem. It is included in the Bad Boyz custom ROM.
There are some apps not working on root devices. They use a SafetyNet procedure to check for that, such as Android Pay or Pokemon Go. However there are ways to overcome this security check and you can enjoy root and SafetyNet compatibility either using SuperSU or Magisk, system or systemless root. the issue becomes a little tricky when adding Xposed mod framework to the mix, since the procedures to have all 3 (root, SafetyNet and Xposed) working is not that straightforward. However this is possible in the Axon 7. You can find one of my guides in the links in my signature.
Enjoy!!!!

Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.

Try reflashing supersu don't reboot, then use terminal in TWRP to do reboot disemmcwp and see if it works. I usually use root Explorer to see if I can change /system to r/w. If it did not work go back to terminal in TWRP and try again. I have had to do it a few times to get it to work. Using adb terminal seems to work first time, terminal apps have not worked for me.

Yuujinz said:
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Click to expand...
Click to collapse
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.

Oki said:
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Click to expand...
Click to collapse
Wouldn't it brick my european device?

Yuujinz said:
Wouldn't it brick my european device?
Click to expand...
Click to collapse
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484

Oki said:
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Ok thanks I'll do it this evening
Or maybe not, to risky.

Most Simple Way to Upgrade to Nougat? + Other Questions

I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?

Read the nougat thread in general.

lafester said:
Read the nougat thread in general.
Click to expand...
Click to collapse
I have seen this thread: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
But I was wondering there was a more simple or directly method which doesn't involve EDL mode?
Edit: Nevermind, I don't know why I was expecting a more simple method, nothing on the A7 is more straightforward than that. I'd still like to know if I should be expecting any issues and if a full wipe is needed. For that matter will my phone be wiped anyway if I install that ROM?

Cyrus D. said:
I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?
Click to expand...
Click to collapse
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.

bluestudy said:
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.
Click to expand...
Click to collapse
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go to prevent any possible mistakes.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.

Cyrus D. said:
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method which installs the bootstack + ROM + TWRP from one package and can recover a brick.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go so I don't have to do a song and dance every time I want to change my ROM. But I don't know if I can just do that with jcadduono's package because IIRC TWRP doesn't automatically install things to where they should be, you have to manually select it (recovery, etc) and that package needs to be installed to multiple locations. Or maybe I have no idea what I'm talking about it.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.
Click to expand...
Click to collapse
Have been able to play Pokemon Go (my son, lol) and Fire Emblem on several Lineage based ROMs using Magisk. Can also get Android Pay to work (except for my bank currently not supporting it, but it doesn't show that I'm running any third party ROM or have my bootloader unlocked.) So, that might be the way for you to go, if you decide to try it out. As far as the EDL method, I've never tried it, but it does seem like an extremely useful tool.

Sorry went back and edited my post. It seems I was mistaken and I'd have to at least flash 2 packages by the EDL method, the TWRP package isn't the full ROM, just the bootloader and recovery. The only thing I can get working is Pokemon Go if I switch off root. Is Magisk working on the stock Nougat ROM as well?

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

My approach to rooting 7.1.1

Hey all,
After my rooting experience with marshmallow, I used that with 7.1.1 and have had no issues. MODS: This was my approach to rooting 7.1.1. I apologize in advance for creating this thread if it's not necessary yet since XDA has given me so much help, I'm returning the favor.
NOTE: for those that want to roast me on this thread and/or flame me, don't do it. We are all noobs at one point or another. I have provided no links but have supplied the filename to the best in my capacity.
XDA gang,
After numerous attempts to root nougat, I tried this approach. This was the same approach I took w/ marshmallow.
I used Odin3_v3.12.3
selected 7.1.1 – look for filename j700tuvu3bqi5 NOTE: uncheck auto reboot. I do\did because in my experience, I encountered a boot loop.
after odin processes the flash, I disconnected the usb cable and did a battery pull.
Boot up your phone and let your phone build the recovery. After your phone reboots after the recovery, do a battery pull when the samsung splash screen starts to display itself.
Enter stock recovery and perform a cache, dalvik, and factory reset. Reboot from recovery.
Do a battery pull when the samsung splash screen starts to display itself. Boot back into download mode while holding volume down, home button, and power button. Let go of the buttons when the download mode screen comes up.
Use odin again and click on the AP button – select twrp_3.0.3-1_sm-j700t_23217. I found and downloaded this from XDA. Click start on odin and let odin do it thing. Disconnect the usb cable and do a battery pull.
Enter twrp recovery while holding volume up, home button and power button. Release buttons when twrp comes up.
Here, you will need to flash the latest supersu. I used v2.82-SR5. Also download no-verity-no-encrypt-ashyx.zip (big ups to ashyx for creating this)
Install these 2 files and reboot. NOTE: your phone will reboot twice – no cause for alarm.
After your phone boots up into nougat, go through the setup and reboot your phone.
After doing all of this, I've had zero issues. It may seem arduous but I found it necessary for my goal.

Did you have any issues with unlock screen lag on pin;/pattern?
There are reports and my own experience with this on a 7.0.0 version of otherwise identical process as yours to root. conclusion seems to be the no-verity-no-encrypt patch causes this, and that this patch (or something functionally identical) is integrated into supersu 2.82 versions.
edit - what model phone did you do this one? 7.1.1 not available for the j730g yet, unfortunately.

im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.

leo31 said:
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
Click to expand...
Click to collapse
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well

DullPeon said:
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
Click to expand...
Click to collapse
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?

leo31 said:
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
Click to expand...
Click to collapse
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.

fullofhell said:
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
Click to expand...
Click to collapse
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?

leo31 said:
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
Click to expand...
Click to collapse
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too

fullofhell said:
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
Click to expand...
Click to collapse
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.

leo31 said:
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
Click to expand...
Click to collapse
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.

fullofhell said:
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
Click to expand...
Click to collapse
this is the 2nd time i root my device.
the first time i rooted my a3, i didn't face any lag and never laggy while unlocking screen.
but the problem is i forgot how i rooted it. which files did i flashed. which tutorial did i follow.
but no problem so far , because the fingerprint unlock does not give any lag.