Database Users

lgd800 to cwm13 with + magisk

Hey I'm looking around and found 2 interesting posts.
http://forum.xda-developers.com/lg-...fficial-cyanogenmod-13-lg-g2-t3264508/page422
http://forum.xda-developers.com/lg-g2/help/starting-root-recovery-custom-rom-t3440752/page1
Click to expand...
Click to collapse
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?

andrew2432 said:
Hey I'm looking around and found 2 interesting posts.
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?
Click to expand...
Click to collapse
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Code:
su
mount -o remount,rw /system
rm /system/xbin/su
rm /system/bin/su
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.

blastagator said:
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe everything
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.
Click to expand...
Click to collapse
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?

andrew2432 said:
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?
Click to expand...
Click to collapse
Recovery lives in /recovery partition, so I guess I should clarify, don't wipe EVERYTHING, lol. I can't remember if I enabled ability to wipe recovery, DONT DO THAT :silly:
edit: Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
But, as for everything else, recovery will live through wiping /system /data, etc. You need to backup anything you want to save though. Wipe will destroy everything.
Other than that, you pretty much got the rest.
edit 2: http://download.cyanogenmod.org/?device=d800
See image for ROM vs CM Recovery.
CWM = Clockwork Mod (a different recovery)
CM = CyanogenMod (a ROM)
.

@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
EDIT: awesome, I have to run all Internet functions off of the sprint lte network and was downloading one of those behemoths during that posts....that let's me know my efforts aren't in vain

andrew2432 said:
@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
Click to expand...
Click to collapse
Please read my edits and don't kill your phone. I am not always so timely in my responses :good:
Other than that, good luck!
There are tons of posts that go into more detail about what I wrote. Just make sure you have a plan before you do it. Think: Measure twice, cut once.

This g2 I found service locked while cleaning out a rental property. I have a galaxy s5 stupid sprint for my primary. I use the g2 for...well everything game and other related. until my Hotspot mod on my galaxy suddenly stopped working on lp. I blame the man
Äptiva is the one I read about a gutted 802 into an 800 or something, got you guys confused!!

@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo

andrew2432 said:
@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo
Click to expand...
Click to collapse
CM13.
If you're trying to get safety net to work, you have to enable magisk hide (in the magisk app)
Also, if you're using xposed, you can't use safety net.

@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800

andrew2432 said:
@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800
Click to expand...
Click to collapse
If the safety net test app passes, it should be working. perhaps downgrade your pogo a version or two, maybe they added something else.

Well, it's on a WiFi only, no SIM device...
I'm thinking this is the issue I'm experiencing now. Which may stem from an update. An older apk is a good idea, I was able to log on with magisk v6 a bit a go and when magisk 7 and 8 first came out I could.

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!

MAGISK root for sprint htc 10?

I have been using TWRP+SuperSU on my HTC 10 (sprint). However, I am not happy not being able to use Android Pay due to root. I searched and found a MAGISK root can do the trick.. I searched and was surprise to find not much of info on this variant.
I only found this: [ROOT] Magisk AutoRoot: Magisk + phh's SuperUser for Nougat (No TWRP required). But that's for the Unlocked version:
Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zip
I assume I cannot use above boot image for Sprint variant. My question is, where to get this prebuilt boot image for Sprint?
I am on Android 7.0 (2.42.651.6).
Thanks!!

ctzw said:
I have been using TWRP+SuperSU on my HTC 10 (sprint). However, I am not happy not being able to use Android Pay due to root. I searched and found a MAGISK root can do the trick.. I searched and was surprise to find not much of info on this variant.
I only found this: [ROOT] Magisk AutoRoot: Magisk + phh's SuperUser for Nougat (No TWRP required). But that's for the Unlocked version:
Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zip
I assume I cannot use above boot image for Sprint variant. My question is, where to get this prebuilt boot image for Sprint?
I am on Android 7.0 (2.42.651.6).
Thanks!!
Click to expand...
Click to collapse
That's old info for Magisk, the main Magisk thread has all the up to date files...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my Sprint HTC Bolt using XDA Labs

OMJ said:
That's old info for Magisk, the main Magisk thread has all the up to date files...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my Sprint HTC Bolt using XDA Labs
Click to expand...
Click to collapse
Thank you. I am following the guide you provided..
"If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
"​
Can you please let me know how to Flash Magik zip? I am on Stock Android 7.0 by RUU. Custom Recovery (TWRP) is gone... Downloading to download mode does not have an option to install zip.... Install Magisk Manger gives me this.. Still requires boot image? Thanks.

ctzw said:
Thank you. I am following the guide you provided..
"If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
"​
Can you please let me know how to Flash Magik zip? I am on Stock Android 7.0 by RUU. Custom Recovery (TWRP) is gone... Downloading to download mode does not have an option to install zip.... Install Magisk Manger gives me this.. Still requires boot image? Thanks.
Click to expand...
Click to collapse
You flash Magisk v11.1 zip via TWRP.

JediMindTrixx said:
You flash Magisk v11.1 zip via TWRP.
Click to expand...
Click to collapse
He just said he doesn't have TWRP.
ctzw said:
Thank you. I am following the guide you provided..
"If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
"​
Can you please let me know how to Flash Magik zip? I am on Stock Android 7.0 by RUU. Custom Recovery (TWRP) is gone... Downloading to download mode does not have an option to install zip.... Install Magisk Manger gives me this.. Still requires boot image? Thanks.
Click to expand...
Click to collapse
Try my post from the Bad Boyz ROM thread. I'm pretty sure that covers it all. If you're already RUU'd you can skip that part, but you will need to unlock your bootloader if you haven't already. I think that factory resets the phone. There's another thread on how to do that via HTCDev that should be stickied, but the process is easy.
https://forum.xda-developers.com/showpost.php?p=71341441&postcount=593
Edit: I see you're already in the process on the other thread. Good luck!

MagisK v11.6 update looped my phone at white screen when taking update from app prompt...

kaw900r said:
MagisK v11.6 update looped my phone at white screen when taking update from app prompt...
Click to expand...
Click to collapse
Worked fine for me.

Update boxes
SilverZero said:
Worked fine for me.
Click to expand...
Click to collapse
There were 2 boxes that could be checked did you check either of them? I checked both and was going to try without checking them but also figured they would update the rom soon and it would be in there. t/u

Hello I'm on 6.0.1 Bad Boyz and I flash this but it doesnt root my phone, I used un-su.zip beforehand
Edit nevermind I RUU'd to Android 7.0 and flashed Bad Boyz Magisk!!!

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

No OS installed. TWRP cannot flash new custom ROM

Hello,
I have a big problem. I don't know what to do.
I wanted to make a clean install of OxygenOS 4.5.8 and so i downloaded it, did it on SD card together with Magisk and no_verity_op5.zip (because i read that this decrypt the data).
So i cleand data and installed no_verity_op5.zip via TWRP, but when i wanted to reboot it takes way to long (i waited 30minutes but it stays on boot circle)
After that i booted into TWRP and decided to made a factory reset and to install OxygonOS 4.5.8 in a clean version. But it was not possible anymore!
When i want to install the .zip it says Patching system image unconditionally... and it loads. after the blue is full it says:
writing static_nvbk image...
patching firmware images...
script succeeded: result was [1.000000]
And when i want to boot into system it says no OS installed.
I tried also to flash this rom or even any other custom rom through ADB Sideload but it does not work. Same like above..
What can i do? I do not know what to do
I hope my phone is not bricked.
Thank you for any suggestion.

Go to oneplus 5 official download page, download stock recovery and latest stock firmware and follow instructions on the download page.... But first with TWRP take a backup of all your data because restoring stock firmware will ERASE everything... Don't panic it will works

First off, don't panic! you're not bricked as long as you can reach your bootloader and recovery.
This happened to me as well and luckily the fix is easy!
You probably tried to flash the OxygenOS build from the Oneplus downloads right?
Somehow these won't flash properly through TWRP and you must therefore also flash the Oxygen recovery image listed in the downloads.
Here are some steps that'll fix your problem.
1 - Backup all of your private data from internal storage because flashing OxygenOS will WIPE/ENCRYPT all data on your device.
2 - Go to the Oneplus download center and download both the latest OxygenOS and it's appropriate recovery:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8
3 - Boot into your bootloader and flash the stock recovery you just downloaded. (fastboot flash recovery <recovery>.img)
4 - Boot into the Oxygen recovery and flash OxygenOS.
This should get you up and running again.
Once you get tired of OxygenOS simply reboot back into your bootloader and flash TWRP and any rom of your liking.
In the future if you want to flash OxygenOS from TWRP you have to grab a build from XDA I guess. I'm not entirely sure why flashing from within TWRP won't work with stock OOS but I believe it expects to be flashed from withing the stock recovery.
I'm pretty confident this will solve your problems.
Please backup your data first though, don't want anything to get messed up in there!
Good luck!

Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?

manuelbvb said:
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
Click to expand...
Click to collapse
It is possible to have both OxygenOS and TWRP for sure!
Only a clean flash from a non-encrypted state in TWRP seems to break stuff. You can use a modified OOS build from the forums.
TWRP can indeed backup your OOS install so that shouldn't be a problem.
The only exception seems to be flashing a clean install of OxygenOS (from Oneplus Download center) through TWRP.
Other than that everything works as expected.

Ok thank you.
So i will follow you instructions and i hope it will work.
And i think so.
And after it i will install TWRP again (because i need the backup tool), i will install magisk. will this work?
So i can use everything as in a custom rom, but cannot make a clean install? So official Oneplus OTA will work with TWRP or not?
Thank you soooo much!

Also, Magisk/root works just fine on OxygenOS.
Once you flashed OOS from the stock recovery and have everything set up simply boot into your bootloader and flash TWRP.
From there you flash Magisk and everything should be fine.
OTA's from Oneplus also install fine through TWRP as long as you go into Magisk and uninstall 'root' first. When OxygenOS tells you there's an update simply remove Magisk as I said above and it'll update fine.

Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?

manuelbvb said:
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
Click to expand...
Click to collapse
First off! YAY!! glad it worked out!
Be sure to use the TWRP build from the twrp.me website. The one listed on these forums are 'unofficial'. Not saying those are bad, but the official one has a pretty impressive track-record.
After flashing Magisk you are root-enabled so yeah, congrats you are now root! In order to pass safetynet you must enable 'magisk hide' in the magisk manager (the app that should now be installed on your phone).
If you do not have an app called 'magisk manager' then you can download this app from the magisk forums. It should however install itself while flashing the Magisk zip. So assuming you have it installed find the 'magisk hide' service and enable it.
From my experience you sometimes need to reboot in order for it to pass safetynet check.
Glad it all worked out for you!

Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero

manuelbvb said:
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
Click to expand...
Click to collapse
That's great to hear!
Enjoy and take care!

no os
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]

xda___ said:
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
Click to expand...
Click to collapse
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP

Zocker1304 said:
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Click to expand...
Click to collapse
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)

xda___ said:
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
Click to expand...
Click to collapse
Well just flash a different twrp via fastboot flash recovery *path to file*