Develop Bugs

Moto G7 Power/Supra [All Versions] [Pie] Magisk Root Guide [OTA/SafetyNet Working]

Disclaimer: This WILL void your warranty. I am not liable for breaking/bricking your phone, you losing your data, or any nuclear war/other catastrophe. This process WILL totally wipe all data on your phone. Make sure you have a backup! You will also forever see "bad key" displayed in the top left of your screen for a few seconds after a reboot after unlocking the bootloader. There is currently no way around this that I'm aware of (let me know if you have a way)
This guide was assembled from mingkee's G7 guide here: https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
You will need:
1. Your Moto G7 Power (Any hardware version, any carrier, but running Android 9 Pie)
2. A stock boot.img for your hardware version, here are the two that I have. You can just extract the boot.img from a stock ROM for a hardware version not listed, although I'm not sure it actually matters which one you use. Experiment at your own risk.
XT1955-5 US: https://mega.nz/#!L0sHzSKY!323GrDQ8BTsPmKvrSoU7DV-2kJuVris0cWN8Xt3u_6o
XT1955-2 LATAM: https://mega.nz/#!uk912I4B!12_EgPML2l5sIXDeDGVqiVDB2RwA6iF6-H-mivNecOo
(Full stock ROM's for both versions will be linked in the next post. )
3. A USB cable to connect your G7 to a computer
4. Motorola USB drivers: https://support.motorola.com/uk/en/...moto-g-family/moto-g7-power/documents/MS98028
4. Your bootloader unlock code from Motorola, more on that below
5. Android SDK
Step 1: Unlocking the bootloader
First we'll need to unlock the bootloader, to do this, you'll need your unlock code from Motorola:
https://support.motorola.com/us/en/bootloader
Note that this will require you to register your device with Motorola, and this WILL void your warranty.
Then, download and install the Motorola USB drivers (link above), you may need to reboot your computer after installation.
Next you'll need to download and extract/install the Android SDK
https://developer.android.com/studio/index.html#downloads
Note that you'll only need the "command line tools" for this guide, unless you really want the whole SDK (huge).
Extract the command line tools to anywhere really, C:\Android is fine for Windows. If you downloaded/installed the whole sdk, the tools you need will be in C:\Users\[your username]\AppData\Local\Android\Sdk\platform-tools
Once you have that, open up a powershell window in your tools folder by holding Shift and right-clicking in the folder.
Now, reboot your G7 to fastboot mode by powering off, then holding power+volume down until you're in the bootloader. Now, connect your G7 to your computer with your USB cable.
In powershell, verify your device is recognized by typing "./fastboot devices". Your G7 should show up by its serial number.
Now, type "./fastboot oem unlock [your motorola unlock code]". THIS WILL WIPE ALL DATA ON YOUR PHONE. After that, use the volume up and down buttons and then the power key to restart the bootloader. You should now see "flashing_unlocked" at the bottom of the bootloader screen. Now use the volume/power buttons to select "start" to boot the phone. You will see "bad key" displayed in the top left corner of the screen. This is normal. The phone should boot and bring you to the Android set up wizard. Go ahead and set up the phone as you normally would.
Note that at this time, if you go to "Update" in system settings, it may warn you that "system integrity is compromised" and that you will no longer receive OTA updates. This is also normal, we'll fix that in a bit.
Step 2: Rooting
Now that we have an unlocked bootloader, we can flash things to the phone through fastboot (at the time of this writing, TWRP or other custom recoveries are not available for the G7 Power. Once it is, you can use that to flash the Magisk .zip file instead of using powershell).
Copy the correct *_boot.img for your hardware version to a folder on your phone. I used the downloads folder. (not too sure if the version makes a difference; I was able to flash the entire US XT1955-5 firmware/rom to my Latin America XT1955-2 without a problem, but experiment at your own risk)
Download and install the Magisk Manager APK through Chrome or browser of your choice on your G7
https://github.com/topjohnwu/Magisk/releases
It will ask you if you want to allow [your browser] to install things from unknown sources. Say yes.
Then, open Magisk Manager and tap "Install". Then tap "patch boot image file". Select the *_boot.img you copied earlier and let it run. It will tell you when its done.
Once it completes, copy the patched *_boot.img back to your computer and place it in the same folder as your Android SDK tools (where fastboot.exe and adb.exe live)
Now power off the phone then boot to fastboot, again by holding power + volume down until the bootloader appears.
Now in powershell, type "./fastboot flash boot [the name of your patched boot.img].img" and hit enter. Alternatively, type "./fastboot flash boot" then hit space, then drag your patched *_boot.img into powershell and hit enter.
(Note, if you get an error saying "Invalid partition name boot__a" like I did, add a "_a" to "boot" ie "./fastboot flash boot_a [the name of your patched boot.img]" instead. )
Powershell should tell you "Image signed with key bad key". This is normal.
Now use the volume up/down buttons and power button to start the phone.
Once booted, load up Magisk Manager again. You should see all green checkmarks. Congrats, your G7 is now rooted! One last thing:
Tap where Magisk says "tap to start SafetyNet check". This tests to see if its able to fool Google's checks and let you install OTA updates or use Android Pay. If you did everything properly, this should all check out fine. Confirm by going into Updates in System Settings and verifying that you are up-to-date and it doesnt say anything about "device integrity compromised".
Thanks to everyone who's work I shamelessly paraphrased. I wanted to make a concise guide specifically for the G7 power as I didn't find much online regarding it. (And the stock US rom was ridiculously hard to find and acquire). I'll link stock US and Latin America G7 Power firmwares/roms in the post below in case anyone wants to go back to stock, once the upload finishes. Note: there is no known way at the time of this writing that you can ever get rid of "bad key" being displayed at boot once you unlock the bootloader (again, if anyone knows how, let me know! Thanks!)

gedster314 linked me to a site in another thread where stock ROMS for a lot of devices can be found, including the XT1955 (codename: Ocean).
https://mirrors.lolinet.com/firmware/moto/ocean/official/
"RETUS" on that page would signify "Retail, US"

until some good custom roms will pop out i don't have needs to unlick/root...

mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse
Baby steps my friend.

Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse

Got everything to work! Flashed Tethering Enabler too. Thank you!

nucher said:
Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
Click to expand...
Click to collapse
There's one more reason to root: CF Lumen
I want all devices have same exactly same white tone.

Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked

turboyo said:
Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked
Click to expand...
Click to collapse
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.

diversenerd said:
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.
Click to expand...
Click to collapse
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?

turboyo said:
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?
Click to expand...
Click to collapse
I was wrong in my first thread, my -2 does NOT have NFC. Heres the newly minted LTE Band unlocking guide: https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-enable-lte-t3925246

After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?

Darkstarsx said:
After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?
Click to expand...
Click to collapse
What kind of issues? I haven't noticed any ill effects of rooting with this method.

my touchscreen is not working at all after the rooting step. how do i fix this?

jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Try rolling back to stock with my other guide. Then try again.

Thanks for the guide, phone is now rooted. Is it safe to do a factory reset to be able to start the phone set up again to automatically download apps, settings, etc from Google? If not, is there another, better way to do that?

diversenerd said:
Try rolling back to stock with my other guide. Then try again.
Click to expand...
Click to collapse
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday

jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Chickenaa said:
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday
Click to expand...
Click to collapse
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that

Poto222 said:
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that
Click to expand...
Click to collapse
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop

Chickenaa said:
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop
Click to expand...
Click to collapse
Someone on the Telegram group has a working TWRP build, he said he'll be posting it soon.

LineageOS for Huawei Y9 2018 (FLA-LX2)

Looking for a way to install LineageOS for Huawei Y9 2018 (FLA-LX2)
I couldn't find my model under official site

harshan said:
Looking for a way to install LineageOS for Huawei Y9 2018 (FLA-LX2)
I couldn't find my model under official site
Click to expand...
Click to collapse
Hopeless
https://forum.xda-developers.com/android/help/y9-2018-update-t3859859

Y9 2018 running Android 9 Custom ROM
(Havoc OS+MicroG)
Hi, so I landed on this forum a year ago, thinking that it would be impossible for me to one day unlock and tweak my Huawei Y9 2018.
Today everything works fine for me as I managed to install a custom ROM after unlocking the bootloader. I'll detail you step by step what I did, I'm new here so this is obviously not the only way, I'm just telling you what I did to make it work, and of course I am not responsible if anything wrong happens to your device, many times during the process I did things wrong and I bricked the phone, but you should always be able to come back to step 1 and restart fresh.
STEP ONE: INSTALL STOCK ANDROID 8 FIRMWARE (before June 2018 security patch)
For this step all you need is an SD card (and a computer if the phone is bricked).
Go to here and type in your phone model, I have the FLA-LX3 so I took this file which is at the bottom of the result list.
Afterthat extract the zip and copy the filed called update.APP to a folder called dload in your SD card.
Turn off your phone with the SD card placed inside and boot it from the SD card. To do that, you have to press volume up and power button at the same time for 5 seconds.
The installation should start and you will soon boot back in Android 8.0.0. Quickly reach the settings to check if you have successfully downgraded before June 2018. Otherwise the rest won't work. Finally, rename dload folder in your SD card to something else so that next time your phone won't try to install a system from the SD card.
STEP TWO: FIND YOUR BOOTLOADER CODE
If you already know your bootloader code, directly go to step 3.
This is a tricky part, as you already know there is no official way to get your bootloader code. There are different approaches to get the code. Both need a computer.
A free one can be found here but I didn't use it personally. It's a simple brute force attack to find the code, it can be extremely long so most probably not the best one.
A second option, which is most used is the DC-unlocker tool for Windows that will find the bootloader code in couple of seconds. You have to use 4 credits (4$) to perform the action "Huawei Qualcomm Read Bootloader Code (up to Android 8)". The tutorial can be found here
Once you know your code, save it everywhere !!!
STEP THREE: UNLOCK BOOTLOADER
For this step you will need a computer with ADB and Fastboot commands. (download the command line tool for Windows/Mac/linux from here)
Go to phone settings, activate OEM unlock and USB debugging (you might need a WiFi connection to enable OEM unlock). If you type adb devices in your shell you should see you device in the list.
Type adb reboot bootloader to enter fastboot mode.
If you type in fastboot devices you should see again your device in the list.
Type in fastboot oem unlock *paste your code here*
On our device confirm unlock and the device will reboot after a factory reset.
STEP FOUR: FIND THE RIGHT GENERIC SYSTEM IMAGE
There is no official custom ROM for Huawei Y9 2018 but the phone is compatible with Generic system images, which are universal ROMs (all listed here). To be sure quickly reach the browser to download Treble Check app from here. This app will tell you wether or not you can install GSI images on your phone. If Projet Treble is ticked then you are good to go. If Seamless updates is ticked then you have an A/B system, if not then you have an AONLY system. Finally the CPU Architecture tab should tell you if you are on ARM64 or something else.
The GSI rom I chose is Havoc OS, it is the most compatible for Huawei phones. It is an Android 9 rom built on top of Lineage OS and adds up some functionalities, fixes for Huawei phones, and signature spoofing for MicroG to work. Go to this link and choose the right Havoc version based on the Treble Check app.
STEP FIVE: INSTALL HAVOC OS
Once you downloaded the connect img file connect your phone again and enable USB debugging, type in adb reboot bootloader to enter fastboot, and enter fastboot flash system *GSI rom path*
Once done, unplug device from computer and reboot to eRecovery by holding power and volume up for 5 seconds (just like in step 1 so make sure no SD card with dload folder is placed inside the phone). Once in eRecovery perform a factory reset and after that hit reboot system. Your device should now boot with Havoc OS !
STEP SIX: install F-Droid MicroG and Aurora Store (Alternatives to Google ecosystem)
Go to the browser and install F-droid from their official site. Next add the MicroG repo to F-droid to install and activate all the replacements to Google services. You can finally install Aurora Store from F-droid which replaces the official Play Store.
That's it folks!

fepoulpa said:
Y9 2018 running Android 9 Custom ROM
(Havoc OS+MicroG)
Hi, so I landed on this forum a year ago, thinking that it would be impossible for me to one day unlock and tweak my Huawei Y9 2018.
Today everything works fine for me as I managed to install a custom ROM after unlocking the bootloader. I'll detail you step by step what I did, I'm new here so this is obviously not the only way, I'm just telling you what I did to make it work, and of course I am not responsible if anything wrong happens to your device, many times during the process I did things wrong and I bricked the phone, but you should always be able to come back to step 1 and restart fresh.
STEP ONE: INSTALL STOCK ANDROID 8 FIRMWARE (before June 2018 security patch)
For this step all you need is an SD card (and a computer if the phone is bricked).
Go to here and type in your phone model, I have the FLA-LX3 so I took this file which is at the bottom of the result list.
Afterthat extract the zip and copy the filed called update.APP to a folder called dload in your SD card.
Turn off your phone with the SD card placed inside and boot it from the SD card. To do that, you have to press volume up and power button at the same time for 5 seconds.
The installation should start and you will soon boot back in Android 8.0.0. Quickly reach the settings to check if you have successfully downgraded before June 2018. Otherwise the rest won't work. Finally, rename dload folder in your SD card to something else so that next time your phone won't try to install a system from the SD card.
STEP TWO: FIND YOUR BOOTLOADER CODE
If you already know your bootloader code, directly go to step 3.
This is a tricky part, as you already know there is no official way to get your bootloader code. There are different approaches to get the code. Both need a computer.
A free one can be found here but I didn't use it personally. It's a simple brute force attack to find the code, it can be extremely long so most probably not the best one.
A second option, which is most used is the DC-unlocker tool for Windows that will find the bootloader code in couple of seconds. You have to use 4 credits (4$) to perform the action "Huawei Qualcomm Read Bootloader Code (up to Android 8)". The tutorial can be found here
Once you know your code, save it everywhere !!!
STEP THREE: UNLOCK BOOTLOADER
For this step you will need a computer with ADB and Fastboot commands. (download the command line tool for Windows/Mac/linux from here)
Go to phone settings, activate OEM unlock and USB debugging (you might need a WiFi connection to enable OEM unlock). If you type adb devices in your shell you should see you device in the list.
Type adb reboot bootloader to enter fastboot mode.
If you type in fastboot devices you should see again your device in the list.
Type in fastboot oem unlock *paste your code here*
On our device confirm unlock and the device will reboot after a factory reset.
STEP FOUR: FIND THE RIGHT GENERIC SYSTEM IMAGE
There is no official custom ROM for Huawei Y9 2018 but the phone is compatible with Generic system images, which are universal ROMs (all listed here). To be sure quickly reach the browser to download Treble Check app from here. This app will tell you wether or not you can install GSI images on your phone. If Projet Treble is ticked then you are good to go. If Seamless updates is ticked then you have an A/B system, if not then you have an AONLY system. Finally the CPU Architecture tab should tell you if you are on ARM64 or something else.
The GSI rom I chose is Havoc OS, it is the most compatible for Huawei phones. It is an Android 9 rom built on top of Lineage OS and adds up some functionalities, fixes for Huawei phones, and signature spoofing for MicroG to work. Go to this link and choose the right Havoc version based on the Treble Check app.
STEP FIVE: INSTALL HAVOC OS
Once you downloaded the connect img file connect your phone again and enable USB debugging, type in adb reboot bootloader to enter fastboot, and enter fastboot flash system *GSI rom path*
Once done, unplug device from computer and reboot to eRecovery by holding power and volume up for 5 seconds (just like in step 1 so make sure no SD card with dload folder is placed inside the phone). Once in eRecovery perform a factory reset and after that hit reboot system. Your device should now boot with Havoc OS !
STEP SIX: install F-Droid MicroG and Aurora Store (Alternatives to Google ecosystem)
Go to the browser and install F-droid from their official site. Next add the MicroG repo to F-droid to install and activate all the replacements to Google services. You can finally install Aurora Store from F-droid which replaces the official Play Store.
That's it folks!
Click to expand...
Click to collapse
Hi there these steps seems easy enough.
But I had to ask why you chose android 9 and will higher versions work correctly?

[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware

First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile Stock 10.0.8 to Rooted Global Firmware.
Please take the time to read every step carefully. It'll explain a little bit as to the why behind some of the steps. PM me if I've missed anything.
This has been revamped as some of the steps are no longer required. Devices coming from 10.0.6 and below might have to try a different set of steps. Click here for the post with the old instructions
Requirements:
ADB setup and working
Global Fastboot ZIP Grab the latest version (10.0.8 as of 3/20)
For Root:
Magisk Canery apk
Modded-Boot.img From here or make your own pulling your own boot.img and using magisk to create a modded boot.img file
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin (could also be labeled unlock_token.bin) file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5a. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Global Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img​8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.​
Code:
flash-all.bat
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 8 and try again.
10. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post).
You're done! Continue on if you want to root your device...
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
If you're interested in root:
11. Boot the device from the modded-boot.img file to give your self temp root. Once this is done, boot the device.
Code:
adb reboot bootloader
fastboot boot modded-boot.img
12. Install Magisk Manager Canary from here
13. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
14. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
15. Once that finishes it'll have you reboot the phone.
16. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post)
=-=-=-=-=-=-=-=-=-=-=-=
Shoutouts will go here soon.

nolimit78 said:
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. This will be a living first post as I'm currently not able to successfully get rooted. The idea of this thread is going from 100% T-Mobile Stock to Rooted Global Firmware. Once I can replicate and get root stable on my phone I will finalize this post. I will also add in shout outs to where I pulled this information from, both thread post and user, as it was through our group that I was able to piece this together. All this will be updated and make to look nice later.
The reason we flash to Indian and then Global is because if you don't, wifi/data and camera will be broken. I can't explain why it works, it just does.
Ok. Now to the good stuff. Please take the time to read every step carefully. It'll explain a little bit as to some of the why behind the steps. PM me if I've missed anything.
Requirements:
ADB setup and working
Global OTA ZIP (download from here)
Indian Fastboot ROM(download from here)
1. Unlock your bootloader. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!).
2. Move the Global Rom.zip file to the root of your OnePlus7T. It'll save you time later. Do this now or there's a later step where I give you the chance.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
4. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5. Reboot your phone into fastboot adb reboot bootloader
6. Extract the Indian Fastboot Rom folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img
7. Open CMD (with admin rights) and navigate to your ADB folder.
Mine would be-- cd c:\adb\
8. flash-all.bat
9. It will also ask you to wipe data. This is your call. If you followed Step 2, this will wipe out this file and you'll need to replace it once your phone has converted.
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says []. This is normal, just ignore it. Once everything settles, the device will reboot by itself. If it doesn't, start over and go back to Step 5 and try again.
10. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
11. You should have already moved the Global OTA to the root of the OnePlus 7t. If you haven't, do so now.
12. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
13. Select the Global OTA file and it'll start to flash from within the update app.
14. Once that finishes it'll have you reboot the phone.
15. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--==
This is where we should be able to root. Once I can verify getting this setup and replicate it I will continue with the tutorial. Hopefully, everyone who reads this will find it helpful.
Click to expand...
Click to collapse
I'm having a issue when inflash globel my phone stays on Indian firmware

Are we 100% sure that WiFi/Data/Camera will be broken if you just go straight to Global? Because just this morning I flashed from TMO 10.0.4 to Global 10.0.6 using the fastboot flashable ROM with perfect VoLTE/WiFi/Camera...
Also fully rooted!
Edit: Updated to 10.0.7, kept root via Magisk Manager install to inactive slot.

Reserved for old instructions. Going from 10.0.7 and up the instructions were changed and certain steps weren't needed, like flashing Indian before Global.
Keeping these here just in case someone purchases a phone with older firmware and doesn't want to wait updating to the latest version.
Requirements:
ADB setup and working
Global OTA ZIP (grab the 10.0.6 from here)
Updated 10.0.7 OTA Build from hereas well
Indian Fastboot ROM(grab the latest from here)
Pre-Rooted 10.0.6 boot.img file here
Magisk Canery apk
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Indian Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img​8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.​
Code:
flash-all.bat
10. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 5 and try again.
11. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
12. Be sure to copy the Global OTA to the root storage of your OnePlus 7T. If you haven't, do so now.
13. Reboot the phone and boot the Modded-boot.img file from the bootloader
Code:
adb reboot bootloader
fastboot boot modded-boot.img
14. Once the phone boots up, you should now have temp root. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
15. Select the Global OTA file and it'll start to flash from within the update app. Let this finish before proceeding.
16. Install Magisk Manager Canary from here
17. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
18. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
19. Once that finishes it'll have you reboot the phone.
20. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
If you'd like to update to 10.0.7:
1. Download and move the OTA file for 10.0.7 to the root of your OP7T
2. Go to Settings > System > System Updates and look for the gear in the top right.
3. Select Local upgrade and select the update file for 10.0.7.
4. Let it run through and finish, don't reboot.
5. Open Magisk Manager
6. Update and select direct install to inactive boot partition to update.
7. Once this finishes, reboot and you're now on 10.0.7 rooted.
=-=-=-=-=-=-=-=-=-=-=-=

nolimit78 said:
Yup, tried to be slick by going straight to Global and ran into this problem. Data worked for me but Camera was super unstable and Wifi was the only solid no that I got. Required more research to discover that this issue is avoided by flashing the indian rom first.
Tell me more about this. What steps did you take to do this? I'm thinking that once you flash the global ROM to reboot, and then use the a image-new.img that boots a temp-magisk to then use magisk canary to install magisk on the inactive slot (should be a right?)
Click to expand...
Click to collapse
Hmm I'll watch and see if my Camera is unstable but it seems fine so far.
To root I flashed (not booted) a 10.0.6 Magisk patched boot img (fastboot flash boot patched_boot.img) that someone posted in the "how to patch boot with Magisk" thread and installed Magisk Manager Canary.
I used Oxygen Updater to local update to 10.0.7 (it says 10.3.0 because of a typo from OnePlus, see another thread. It says 10.0.7 in settings) but make sure to download the full 2gb update not the 200 something mb incremental one because it will fail.
Then when the update is done, don't hit reboot, go to Magisk Manager, make sure you're set to the Canary channel (unless you patched the boot img yourself with something else) and install and choose inactive slot. Then you can hit reboot in Magisk.

Perfect, means I was thinking correctly with an extra unneeded reboot. Updated info in OP.

Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything

Once converted to Global oos, will it support Dual SIM?

ysfk7 said:
Once converted to Global oos, will it support Dual SIM?
Click to expand...
Click to collapse
Yes it will support dual SIM as long as you have the dual SIM tray.

rgreen83 said:
Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/one...cking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/one...us-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/and...ctory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything
Click to expand...
Click to collapse
FYI link to fastboot rom is broken.

Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
Sorry bout that, crosspost fail

Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
I clicked on it and it worked, but I didn't check through mobile. Can you show me what happens when you try?

There is no link to request unlock file from OnePlus. Also will regular global OTA updates work? Or will I have to manually update every time?

Will this work for McLaren 5g?

I just followed the instructions in post#7 and was able to do this successfully as well (direct Tmobile->Global, without the Indian version flash in between). Note that the phone will reboot sometime in the middle of the flash, do NOT manually go into the phone and reboot yet again, just wait for it to complete.

Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?

tkoreaper said:
Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?
Click to expand...
Click to collapse
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+

cm0002 said:
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+
Click to expand...
Click to collapse
i guess thats why i can unlock the bootloader and convert the Tmo 6T without asking the unlock_code.bin from oneplus. thank you kindly for the info

I got the unlock bin today I just flashed via fastboot received message the bootloader is unlocked, but the device status still states locked?

nolimit78 said:
...
4. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
...
Click to expand...
Click to collapse
So OEM Unlock button suppose to be OFF or ON?

[Guide] Root Galaxy A10 Magisk prenormal rmm/kg state (October Patch- later)

Hi All this is just a quick tutorial to help you all root your devices, on later firmwares
This 100% works ive done it over and over without any problems. I am currently on october patch latest firmware for my A105FN. As you may know Samsung have now added extra security meaning even if you have already unlocked your bootloader after you patch the firmware with magisk, flash patched firmware and reboot you will be greeted with that dreadfull message, Only official binaries allowed and your device will be locked and wont boot untill you reflash stock firmware again. The below will help get you out of the prenormal kg state, and save's you a 7 days waiting period as we dont have any TWRP available for our device at this time. Also note due to the extra security magisk cant be flashed with the whole firmware no more, as each time you flash the firmware your back at square 1.
Note: You will need 7-zip - google is your freind
1. Download odin: https://odindownloader.com/download/odin3-v3-13-3.
2. download the latest stock firmware for your device via SamMobile
3. Download latest Magisk Manager - https://www.google.co.uk/amp/s/forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/
4. Flash latest firmware via odin and let device boot up and finish setting up.
5. Grab Your Firmware AP_A105FXXXX.tar.md5 remove the md5 so its a tar file makes it easier to work with. Copy it to your device storage.
6. Install latest magisk manager, and open check advanced settings to make sure recovery is checked, select install image / patch image and select the AP file you put on your device, magisk will patch and save as magisk_patched on your internal storage. Copy this back to your pc and extract it.
7. Download this https://forum.xda-developers.com/attachment.php?attachmentid=4818715&d=1568308074 thanks to @droidzer1 and extract the vbmeta.img.
8. Make a new folder on you pc it's temporary so you know where your files are. From the Ap magisk_patch.tar you extracted, copy the boot.img, recovery.img, and the downloaded vbmeta.img from step 7. And place them in the new folder you created, using your mouse select all 3 and right click select 7-zip add to archive, select tar format and name it magisk.tar.
9. Now we have all the files ready back to your device, if your bootloader is already unlocked skip this step and move to the next. For those that havent unlocked there bootloader go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it, if the OEM switch is not there proceed to step 10. If it is and you enabled it it might ask you to factory reset if not it will be this way to complete the unlock bootloader.......
switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
10. Remove any account you have on your device go to settings, look for time and date automatic time zones, turn it off and set date back 8 days from now (example 30th today change date to 22nd) restart device. Now go straight back into automatic time zones settings and turn it back on. Again reboot device, when device reboots turn it off. You can now enter download mode and it should say checking instead of prenormal that means you good to go. Those of you that had no OEM switch in developer mode please now check.... if it's there enable it and go back to step 10 unlocking bootloader then proceed to step 11.
11. Open odin and select in the ap tab the magisk.tar you created earlier. Plug in your usb whilst holding vol-up and vol-down together to boot into download, press vol-up to proceed. Press start on odin and soon as it finishes and device reboots and you see the bootloader message hold power and vol-up until into stock recovery, select wipe factory reset then select reboot device, this the same as soon as you see bootloader unlocked message hold power and the vol-up together this time count to 7.... and release. Phone wont boot it will go blackscreen and reboot, dont worry this is normal, again do the exact same at bootloader unlocked msg screen hold power and vol-up count to 7... release, now phone will boot and you can set it up.
Note: you will need to reinstall magisk manager and on 1st open it will ask do to additional setup, let it do its thing, then device will reboot,
Remeber every time your device reboots you will have to do the power and vol-up to boot system with root.
I hope this guide help you and a big thank you to @afaneh92 for his original guide

thnaks man
how do i install twrp?
if it is possible, can i flash GSI?

tttt7hhhhjjjk said:
thnaks man
how do i install twrp?
if it is possible, can i flash GSI?
Click to expand...
Click to collapse
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.

mikeyb123 said:
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.
Click to expand...
Click to collapse
thanks for the fast reply man :good:

I gave up rooting this phone, ended up bootloop 3 times and always has to flash it to get the phone working again

timba123 said:
Any chimeratool tricks for no oem unlocking in developer options? On a102u1
Click to expand...
Click to collapse
no.. chimera tool cant unlock the bl on usa variants

hello Thanks for this method but not working after install again magisk manager , say app magisk is not installed and not root
When I was creating the magisk_patch file with magisk manager go to advanced settings and check recovery mode
is it correct?

How To Guide Asus ROG Phone 6 / 6 Pro [ROOT GUIDE/SUP]

Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.

Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?

leathan said:
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Click to expand...
Click to collapse
Sorry, I messed with the reply: it's my previous post.

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.

leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course)

leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
leathan said:
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
Click to expand...
Click to collapse
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?

fux1976 said:
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
Click to expand...
Click to collapse
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.

leathan said:
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
Click to expand...
Click to collapse
Phone looks certified, country WW, safetynet passed and upgraded to .160. Only 2 problema left: voice dictation of GBoaed and Android auto not working.
I tried several ways but they didn't solve. Voice dictation worked and then stopped: I guess something interferes... Android Auto app crashes although phone connects to car and is recognised.
Very strange behaviour...
Do you have any idea on how to reflash last .160 zip without twrp? Once installed it gets ignored by system when saved in home directory...
Everything else is working properly.

Isn't Android Auto no more (i.e discontinued).....?

elmor0 said:
Isn't Android Auto no more (i.e discontinued).....?
Click to expand...
Click to collapse
what?!? where did you hear that? It'just something causing problems (compatibility issues with app or setting: magisk, modules, adaway, skipad, disabled system apps and so on). If I could manage to reflash the stock rom it'll work again (I hope)

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly

finallau said:
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
Click to expand...
Click to collapse
I only have raw for .143 but I updated to .160*...can I use the previous version or do I get bricked? I don't trust anti roll back mechanism. I can live with this 2 "limitations" waiting for twrp and then be able to flash zip with no hassle.
*I downloaded source code from the Asus site but not sure how to use it (and unzipped is around 10 gb )

Thank you for this! I've been out of the root game for years but noticed with your post that I can hide root from Google Pay and my banking apps, so thinking of trying this. One question though - you mentioned that official updates need to be manually downloaded and the phone re-rooted. Would this wipe the phone each time?

fastboot driver doesnt support win64

Will the phone do a factory reset after unlocking the bootloader?

Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route

MrKioFLow said:
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
Click to expand...
Click to collapse
Yes, if you unlock the bootloader using the bootloader unlock app (which is a step that is missing in the original post), your phone will perform factory reset.

Troubleshooting​
Once you boot into the bootloader with the adb reboot bootloader command, stay on the screen with the green START. Do not navigate to the fastbootd.
Use the side USB port to connect to your computer - not the bottom one.
Run the adb and fastboot commands in Command Prompt as Administrator.
Before you reboot into bootloader, remove Lock screen in Settings.
If you execute fastboot flashing unlock and you got FAILED (remote: 'permission denied'), just ignore it.
It's always better to install the latest updates, then download the firmware to your PC from ASUS Webpage and extract the boot.img and patch it in Magisk in the phone using this tutorial.

Thanks for the guide! Should add that you have to use the side port for fastboot to see the device. Was stuck for a while trying to figure out why neither mac nor pc couldn't find it when it was in bootloader mode - it was because I was using the bottom port lol!
Also if you want to disable verity and verification for the verified boot images, you have to do for both vbmeta.img and vbmeta_system.img. Didn't boot for me until I did that, and had to do an additional factory reset from recovery because of this.