Database Develop

Is it possible for me to have this root combo?

Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?

Ulti2x said:
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Click to expand...
Click to collapse
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Sent from my ONEPLUS A3000 using Tapatalk

uudruid74 said:
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Click to expand...
Click to collapse
What's CE?

Ulti2x said:
What's CE?
Click to expand...
Click to collapse
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk

To simplify this question, could I disable dm-verify and unlock the bootloader on OOS 3.5.4 and boot back into a wiped phone without any problems? After unlocking the bootloader and disabling dm verify, will I able to just update to 4.0.3 using the OTAs in settings?
Or does booting into the phone with an unlocked bootloader and no dm verify cause me to get stuck at boot? Thanks in advance.

Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.

Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
Click to expand...
Click to collapse
Thanks so much. I don't need to wipe cache after I flash Magisk right? And what's the big deal if the play store detects my device as uncertified?

Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.

Just a small note but you should be able to root without modifying system. They modify boot image now and don't touch system.
Sent from my ONEPLUS A3000 using Tapatalk

Anova's Origin said:
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Click to expand...
Click to collapse
Can I use fastboot commands just by opening command prompt right?
EDIT: This link okay? https://forum.xda-developers.com/showthread.php?t=2588979

That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.

Anova's Origin said:
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Click to expand...
Click to collapse
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799

Ulti2x said:
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
Yep

uudruid74 said:
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
CE stands for community edition

Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Click to expand...
Click to collapse
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?

Ulti2x said:
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Click to expand...
Click to collapse
Go into settings, find Play Store and wipe cache. Then reboot.

Anova's Origin said:
Go into settings, find Play Store and wipe cache. Then reboot.
Click to expand...
Click to collapse
Still says it. Maybe I need to wait?

Forgot, I actually had to delete Play Store's app data last time before rebooting. Then it worked.

Thanks a lot everybody! I have never used fast boot before (have only flash w/ sammy phones) and now I know. Thanks again all for helping me.

OTA Updates after Unlocking bootloader

hey guys, i wanna know if i will still get ota updates if i unlocked the bootloader ??
i wanna unlock it and if i didn't flash TWRP after unlocking it i will be able to install the update ??

This thread is pretty old and it's referring to a Nexus 5, but I think the info holds true. Unlocking wont' stop ota updates, and if all it is is unlocked, then the ota update should install.
It's when you install twrp, or root, or a new system image, etc... that's when the ota update won't install.
https://forum.xda-developers.com/google-nexus-5/help/unlocking-bootloader-prevent-automatic-t3003581

When I unlocking the fastboot oem it will unlock but when I was goes enable to camera 2 I was applied patched boot img my mi a2 phone was stuck in between reboot only it'll showed Android one logo it not goes to restart after I waited 30 min I was flash my phone with new global ROM then it'll start. After that I check my if it's rooted or not .then found out my phone is not rooted properly
My question is can get OTA update ?

Ravirush said:
When I unlocking the fastboot oem it will unlock but when I was goes enable to camera 2 I was applied patched boot img my mi a2 phone was stuck in between reboot only it'll showed Android one logo it not goes to restart after I waited 30 min I was flash my phone with new global ROM then it'll start. After that I check my if it's rooted or not .then found out my phone is not rooted properly
My question is can get OTA update ?
Click to expand...
Click to collapse
In order to maintain the OTA compatibility there is one thing to bear in mind. The system must have the same parity as a standard image.
Changes to the build.prop (camera 2) or swapping out a boot image change this parity. Put the original boot and build.prop back and you should be OK.
Perhaps the best way to think about this is the red pill or the blue pill...
As for rooting - for our Xiaomi A2's the best way to root is to :
Unlock the bootloader (this will wipe your data - ensure you have backups)
Swap the boot.img for one that is Magisk compatible (from this point your OTA is broken)
Install magisk (for the SU)
At this point to get back OTA capability one has to uninstall Magisk and put back a standard boot.img - This hasn't worked for me since going Pie (I have thus swallowed the red pill)
If you touch your build.prop or other system files IMHO you can bury the OTA.
If I want a new version of android I'll manually flash the new image and go back through the rooting process and finish by modifying my build.prop.
There are Magisk modules that provide systemless changes but I've not tested these myself - I prefer to know exactly what I'm doing with my build.prop.
To get back to standard you can always flash a standard system image and if you really want to be clean you can relock the bootloader which will reset your phone as if it was out of the box.

Just to provide some more clarity, unlocking bootloader does not break OTA. OTA is broken only if you modify system partition. One important thing to note is that unlocking bootloader will break safety net. Meaning no Netflix and Pokemon go. But this can be easily fixed by just flashing Magisk.
Magisk and its modules don't modify system partitions. So you can go crazy with Magisk and still have OTA. Just be sure to restore the original magisk-less boot.img before upgrading via OTA as it will 100% cause boot loops..
Enabling camera2 api (via adb or terminal emulator) doesn't break OTA.
On my device, I have Magisk installed with viper4android, quickstep, and Camera2 api enabled and have OTAs intact. I just have to restore my original boot.img.
To be on the safe side, I would suggest you don't edit any files in system partition via file explorers and stay away from editing build.prop directly. You can edit build.prop via a Magisk module.
After the fiasco with the January update causing bootloops, I would suggest keeping bootloader unlocked so you can always downgrade or reflash your device if an OTA messes things up for you rather than having to give it for warranty.

Ashik_salim_ said:
Just to provide some more clarity, unlocking bootloader does not break OTA. OTA is broken only if you modify system partition. One important thing to note is that unlocking bootloader will break safety net. Meaning no Netflix and Pokemon go. But this can be easily fixed by just flashing Magisk.
Magisk and its modules don't modify system partitions. So you can go crazy with Magisk and still have OTA. Just be sure to restore the original magisk-less boot.img before upgrading via OTA as it will 100% cause boot loops..
Enabling camera2 api (via adb or terminal emulator) doesn't break OTA.
On my device, I have Magisk installed with viper4android, quickstep, and Camera2 api enabled and have OTAs intact. I just have to restore my original boot.img.
To be on the safe side, I would suggest you don't edit any files in system partition via file explorers and stay away from editing build.prop directly. You can edit build.prop via a Magisk module.
After the fiasco with the January update causing bootloops, I would suggest keeping bootloader unlocked so you can always downgrade or reflash your device if an OTA messes things up for you rather than having to give it for warranty.
Click to expand...
Click to collapse
hi my friend. i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals

Update to DP4 from Official 9.5.11 with root and without data loss

Tried and tested method to update to DP4 with twrp and root working.
If you update to DP4 directly before installing twrp you will be stuck without twrp.
You need USB pendrive and otg for it.
Steps
1. Update your phone to latest available official version.
2. Boot to fastboot and install TWRP (of course you need boot loader unlocked)
3. Flash DP4 from Thumbrive (keep it in external storage only)
4. Flash Recivery TWRP.zip from thumb drive
5. Reboot recovery
5. Flash DP4 again followed by Twrp.zip
6. Reboot recovery and flash magisk and any other mods you need.
7. Reboot
If you followed every steps correctly you will have working TWRP and root on DP4.
I am using it since DP2 and never had issues.
Note. Since Q diesnt allow twrp to read internal storage you will need usb drive for flashing mod also.
I have uploaded a video with DP4 Features if you want to know about its features.
New features
1. Volte working
2. Names of themes changed
3. System UI settings changed
4. Fingerprint faster
5. Overall phone is faster now.
Removed google assistant swipe shortcut.
Video link here

Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.

Bosstazem said:
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Click to expand...
Click to collapse
You need to use msm tool for reverting to stock
Or Stock reset rom for downgrade.
Then follow my steps

Is there any way to downgrade without MSM tool? I have a Mac. Local update doesn't work. Thanks for the reply.

Try MP version from DP Version package via local upgrade.
This will be available once the official thread is created by oneplus.
Or you may try DP to MP version for DP3

jhakjhuk1853 said:
Try MP version from DP Version package via local upgrade.
This will be available once the official thread is created by oneplus.
Or you may try DP to MP version for DP3
Click to expand...
Click to collapse
The old MP version works! :good:

jhakjhuk1853 said:
You need to use msm tool for reverting to stock
Or Stock reset rom for downgrade.
Then follow my steps
Click to expand...
Click to collapse
I just used the stock firmware .img file via fastboot. I restored 9.5.7 with no issues. Of course you'll lose all your data.

Bosstazem said:
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Click to expand...
Click to collapse
I was able to install twrp and magisk on dp3, i think you can do it with dp4 aswell.
I just fastboot flash boot twrp.img , it says slot a ok, slot b fail.
So i switched active slots and reboot, which boots to twrp installed on other slot. While in twrp (which cannot access data) i installed twrp through adb, switched active slot and installed twrp again. Same for magisk 19.4 installer.
After installing twrp and magisk to both slots i switched active to B and rebooted, which took me to rooted dp4.
Hope that made any sense
Oh and while in twrp, i used twrp installer (latest) to install twrp to both slots.

why do you possibly need to flash the rom and twrp TWICE? shouldn't the usual upgrade process for a rom if you are already rooted still work?
Flash the Q rom
flash twrp
reboot to recovery
flash magisk?
don't understand the reason to flash both twrp and the rom 2 times as posted in the instructions
regardless, i followed the exact steps and it didn't work for me. i boot to a plain black screen and can't get past it. any ideas?

knives of ice said:
why do you possibly need to flash the rom and twrp TWICE? shouldn't the usual upgrade process for a rom if you are already rooted still work?
Flash the Q rom
flash twrp
reboot to recovery
flash magisk?
don't understand the reason to flash both twrp and the rom 2 times as posted in the instructions
regardless, i followed the exact steps and it didn't work for me. i boot to a plain black screen and can't get past it. any ideas?
Click to expand...
Click to collapse
Repeating the steps twice installs the ROM to both system slots

jhakjhuk1853 said:
Tried and tested method to update to DP4 with twrp and root working.
If you update to DP4 directly before installing twrp you will be stuck without twrp.
You need USB pendrive and otg for it.
Steps
1. Update your phone to latest available official version.
2. Boot to fastboot and install TWRP (of course you need boot loader unlocked)
3. Flash DP4 from Thumbrive (keep it in external storage only)
4. Flash Recivery TWRP.zip from thumb drive
5. Reboot recovery
5. Flash DP4 again followed by Twrp.zip
6. Reboot recovery and flash magisk and any other mods you need.
7. Reboot
If you followed every steps correctly you will have working TWRP and root on DP4.
I am using it since DP2 and never had issues.
Note. Since Q diesnt allow twrp to read internal storage you will need usb drive for flashing mod also.
I have uploaded a video with DP4 Features if you want to know about its features.
New features
1. Volte working
2. Names of themes changed
3. System UI settings changed
4. Fingerprint faster
5. Overall phone is faster now.
Removed google assistant swipe shortcut.
Video link here
Click to expand...
Click to collapse
Can you elaborate on step 2? Do we flash twrp.zip the same as the other steps? or do we flash the twrp-installer?

1. Downloaded the 9.5.11 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Remove Magisk modules that may cause problems (Call Recording is one of them)
5. Launch Magisk, and click the first "install"
6. Choose the "Install to inactive slot (OTA)" option
7. Reboot once completed
8. Download TWRP (from another location) and then go into Magisk and install it, but ***DO NOT REBOOT!!***
9. Install Magisk again. Click Install, then select "Direct Install" option.
10. Reboot
Will this work for DP4 as well????

Bosstazem said:
Is there any way to downgrade without MSM tool? I have a Mac. Local update doesn't work. Thanks for the reply.
Click to expand...
Click to collapse
Downgrade using the rollback package, when I did it on Beta 3 it did not relock my bootloader.

kpmohamedhussain said:
1. Downloaded the 9.5.11 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Remove Magisk modules that may cause problems (Call Recording is one of them)
5. Launch Magisk, and click the first "install"
6. Choose the "Install to inactive slot (OTA)" option
7. Reboot once completed
8. Download TWRP (from another location) and then go into Magisk and install it, but ***DO NOT REBOOT!!***
9. Install Magisk again. Click Install, then select "Direct Install" option.
10. Reboot
Will this work for DP4 as well????
Click to expand...
Click to collapse
I don't think so - what I've read on Oneplus page, when you hit restart (after installing magisk) it will reboot and during that erase all data. then reboot again to system. So you cannot restart via system updater,, you need use TWRP to flash it, so i would stick to the 1st post instructions (including 2-times install t ocover both slots). But hey, ican be wrong, you can try and let us know, it would be easier for sure

Is this the only way to get root on DP4?

Simple way
Info for TMobile gm1915 on 9.5.11
You must have magisk installed.
Update through local upgrade method and don't reboot. Then go to magisk select modules hit + and find twrp installer install twrp and then choose install magisk choose install to inactive slot. Then reboot.
Data does not get wiped but fingerprints need to be added again.
Also twrp decryption does not work so best to keep otg USB with you with whatever you may want to flash.
You don't have to flash to both slots it's not necessary but do as you wish.

twinnfamous said:
Info for TMobile gm1915 on 9.5.11
You must have magisk installed.
Update through local upgrade method and don't reboot. Then go to magisk select modules hit + and find twrp installer install twrp and then choose install magisk choose install to inactive slot. Then reboot.
Data does not get wiped but fingerprints need to be added again.
Also twrp decryption does not work so best to keep otg USB with you with whatever you may want to flash.
You don't have to flash to both slots it's not necessary but do as you wish.
Click to expand...
Click to collapse
Is it to upgrade from 9.5.11 to dp4 without data loss???

kpmohamedhussain said:
Is it to upgrade from 9.5.11 to dp4 without data loss???
Click to expand...
Click to collapse
Yes

Hi, I followed all the steps in OP and didnt. using latest twrp and magisk 19.3 (stable)
Now my phone is still starting its first boot about 15 minutes.
Update:
Probably the problem: installed magisk modules.
Anyway after some research default twrp is'nt mounfing local storage. The latest custom TWRP is! So no issues with USB Anymore, just use local storage like u used to do! This is actualy the only way to use the Magisk uninstaller because you need to mount data for uninstalling magisk modules.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Anyway it took me a view hours of testing but now it works smooth! ?

[UPDATE/KEEP ROOT GUIDE] AUG 2020 (QQ3A.200805.001) "FLAME" Magisk/Stock Boot Images

[UPDATE/KEEP ROOT GUIDE] AUG 2020 (QQ3A.200805.001) "FLAME" Magisk/Stock Boot Images
Sorry I'm a little late this month. Didn't have time to update my wife's phone for a few days. I know the P4 forums aren't as "alive" as the P4XL forums, but I still wanted to continue sharing since I'm doing the work anyway. Hope you guys are still finding these guides and files useful.
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4-XL "CORAL"!!
Here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the August 2020 (QQ3A.200805.001) update.
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR AUGUST 2020 QQ3A.200805.001!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682911607
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682911606
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682911608
THESE FILES ARE FOR "10.0.0 (QQ3A.200805.001, Aug 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
Also, as most of us know by now, it looks like Google flipped HW attestation back on, and so SafetyNet will now fail (not just on August, but even previous builds). basicIntegrity test passes, but ctsProfile fails (due to hardware attestation method Google flipped back on), regardless of EdXposed / Magisk Hide status. Until people way smarter than us figure it out, if ever, I can't tell you how to fix it other than reverting back to full stock and locked bootloader. Oh well, carry on. Root is still more important to me anyway - for me the pros still far outweigh the cons.
[SAFETYNET UPDATE!!]: Another temporary SafetyNet fix available, thanks to @Displax. Just note some users have mentioned it could have some unforeseen side effects, as it changes your build prop's entry for your device model name to an unknown in order to force BASIC hardware attestation. Use at your own risk. Big thanks to Displax! Face unlock now working again on my TD Bank and Citi mobile apps. Also worked on my wife's P4 "flame". =)
Just flash Displax's zip file in Magisk Manager: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40656

EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200705.002, Jul 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-qq3a.200705.002-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682886735
flame-qq3a.200705.002-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682886734
August 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-qq3a.200805.001-dc4e0a1b.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot flame-qq3a.200705.002-factory-boot.img
3. fastboot flash dtbo flame-qq3a.200705.002-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-qq3a.200805.001-dc4e0a1b.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot flame-qq3a.200805.001-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
*Kirisakura 5.2.2 works beautifully.
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
SafetyNet not passing? READ OP AGAIN.

Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Coming from an earlier build than July 2020?
Download the July 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
SafetyNet not passing? READ OP AGAIN.

thank you for the thread!

OP has been updated with yet another SafetyNet workaround fix. I'm about 1.5 months late, so my bad!

Boss, are you doing one thread for Pixel 4 September too?

ahalol said:
Boss, are you doing one thread for Pixel 4 September too?
Click to expand...
Click to collapse
I did it the same way.
The only difference is that you have to patch your boot.img with Magisk Canary Build.

Is it possible to get canary the build with the custom URL option? I remember at some point was possible, however all my searches have come up empty. Or is it best to install the canary apk? Thanks in advance.

gmmurphy said:
Is it possible to get canary the build with the custom URL option? I remember at some point was possible, however all my searches have come up empty. Or is it best to install the canary apk? Thanks in advance.
Click to expand...
Click to collapse
I uninstalled the stable build and installed the Canary apk.

I rebooted my phone due to 0 signal and now it's just stuck on 'phone is starting' for hours. QQ. I think it was due to Magisk.
I dirty flashed September Unicorn ROM but still no luck. Ahh don't know what to do.

Sorry for going off the grid for a while everyone. I've been busy with life stuff, baby stuff, family travels, etc.
Also want to note that I don't actually officially own a Pixel 4, but rather is my wife's phone. And I've held off on updating our phones to Android 11 until GravityBox is updated for Android 11. But I did create a guide for my phone (Pixel 4 XL) for September, and now October. I still plan on continuing to make these guides for the P4, but even for the P4XL I had to be careful and have someone test last month since I wasn't updating myself. There are a few additional warnings in terms of making sure any modules are updated before upgrading or much higher risk of bootloop than previous updates.
When I get some time, hopefully sometime this weekend, I'll publish the guides for both months with the proper files for Pixel 4 (flame). Sorry for the wait, stay tuned...

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.

Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.

pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.

SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!