Database Users

Updating firmware and root?

Hi guys,
I know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
Sorry for the hassle I just want to make sure.
One more thing, in this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 at step 9, OP flashes the factroy img files separately (bootloader,radio,etc), is there a problem with using flashall.bat?
Thanks in advance and sorry for my noobish questions.

If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)

Enddo said:
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Click to expand...
Click to collapse
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again

mr.dj26 said:
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
Click to expand...
Click to collapse
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera

Enddo said:
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Click to expand...
Click to collapse
Thanks for the info

Help withAndroid N Preview 5

Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker

You have to flash another version of TWRP... But, dude, i'm on the exact same case, same preview, and i can't get it to work. TWRP doesn't seem to work :/ I always got the god damn "no command" even if i follow some of the tutorials here...
EDIT : Try flashing the 3.0.0 or 3.0.1, and when all will be working (if you achieve, tell me how xD) update it.
EDIT 2 : I may find something, i'll let you know !

TWRP doesnt work with the developer previews without modifying the boot image.
If you want to root, you can use CF-Auto root.
You will still have the stock recovery.

Taker18 said:
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
Click to expand...
Click to collapse
This is a known issue, Search the forum for the resolution. Basically TWRP won't work on the Android N on Encrypted device.

The solution is pretty simple. You need to decrypt your device's storage. TWRP currently doesn't work with encrypted N preview.
This could be easily done by flashing the modified boot image, that will disable forced-encryption. After that, you will need to format the current userdata partition to decrypt the storage.
Code:
fastboot format userdata
fastboot format cache
Once that is done, you can flash TWRP and then use SuperSU to root.
Another way to direct root is by using Cf-Auto-Root. But I am not sure about that specifically. While some users have succeeded, there are a few who have failed to root using Cf-Auto-Root.

Just use CF-Auto Root, it will do all the things.
Make sure you have unlocked your Bootloader and downloaded the good version of CF for your device.
Reboot your phone in bootloader mode, plug it to a computer, and just open the .bat (if you're on windows, or the equivalent for Mac / Linux). It will install SuperSU. When it's done, don't forget to download the TWRP Manager on the Playstore, and you'll have a working Recovery ! I did that, i know have a rooted nexus 6P on Android N preview 5
Also, lot's of Root's only apps will not work properly, because lots of changes took place on Android N. So make sure you follow some guide out there (exemple : Ex Kernel don't work if you don't tweak some things, same with Ad Away, so make sure you're googling)

I followed the premise of this thread here so all credits go to the OP http://forum.xda-developers.com/showthread.php?t=3410906 I flashed the latest Marshmallow vendor.img via fastboot, then flashed TWRP via fastboot. Booted into recovery from the bootloader then side loaded supersu using adb side load in TWRP. After that I rebooted to bootloader from TWRP and fastboot flashed the DP5 vendor.img and recovery.img. All is working well.

OP2 cannot upgrade from Oxygen OS 2.2.1/Cannot flash TWRP versions newer than 3.0.2-0

So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.

Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.

Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:

Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!

Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?

Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.

thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.

Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?

Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,

Motorola Moto X pure stuck on bootloop after failed root attempt, HELP!!

Hey everyone I just recently got a Moto X Pure with TWRP recovery already installed and the bootloader unlocked, unrooted. The phone was stuck on Marshmallow so I went to update and it would take me to TWRP recovery every time and when I reboot back into the system, I'm still stuck on Marshmallow. So I downloaded an app that would make me download OTA updates while still having TWRP recovery but it needed root access, which I didn't have. I tried all of the one-click root apps but non worked then I stumbled across an easy root method: ( oops it said I can't post links, but basically I downloaded a supersu zip and flashed it) which I followed very precisely and I'm pretty sure I did nothing wrong. But when I flashed the ZIP using TWRP and booted back into system it was stuck on the Motorola logo which I'm assuming is bootloop. I was going to download a stock recovery using fastboot but I discovered that it would relock the bootloader, which would render the device useless to me so I can't. I also tried wiping the Dalvrik Cache but it always failed. I'm new to all of this so please guys I'm desperate for help. Thanks in advance

You can flash with fastboot the newest stock(the same version or upper) without commands "...oem..." at start and the end.
Or
The newest downloadable without commands "..oem, bootloader, gpt, oem...". @Philo0o
BL will be still unlocked.

Do you have a tutorial on how to do that please?

https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 @Philo0o

More accurately you need to flash boot.img which is the kernel , in the case where root was being installed using systemless mode.
Otherwise, if you tried an old SuperSU version (where systemless didn't existed or the ones that failed to detect to install using systemless method on this phone) you'll need to reflash the whole system partition (using Firmware system chunks or custom ROM zip file).

Rooting the Moto G5 Plus and keep getting OTA updates

The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).

omino said:
The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).
Click to expand...
Click to collapse
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sure, to be on the safe side, either flash stock ROM then apply all OTA updates as you suggest. Otherwise, one can take a backup of the system partition too. I am not sure why OEM would be modified... but if that is the case, I guess it can be backed up as well.
As a side note, OTA updates from Motorola are downloaded to the following folder: /data/data/com.motorola.ccc.ota/app_download
It is always a good idea to back up the ROM to SD card before applying it, especially for full upgrades (which contain all partitions). That way, it is easy to flash the latest working ROM.
As for the Magisk modules, I had your same experience. It's just my preference to install them through TWRP.

Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Wolfcity is right. From my own experience ANY use of TWRP (i.e., booting or flashing) modifies the OEM partition and prevents OTA from succeeding.

Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.

ctwftp said:
Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.
Click to expand...
Click to collapse
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?

ctwftp said:
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?
Click to expand...
Click to collapse
No. You have to be on untouched stock firmware incl stock recovery to capture OTA.
Sent from my Moto G5 Plus using XDA Labs

Still need to load up both twrps?
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,

TimelesslyPrecise said:
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,
Click to expand...
Click to collapse
As the latest official TWRP has the decryption issue fixed it should work. Imo this guide won't work, a complete flash of stock is needed as I wrote before.
Sent from my Moto G5 Plus using XDA Labs

For some reason I could not get a backup of system and boot...
Ended up noticing a few issues with aosp, so flashed to lineage. Pretty smooth so far.
Been out of the game for awile, but it's coming back.

How G5 plus could be rooted.