Develop Bugs

Redmi Note 8 Pro Guide [Firmwares | ROOT CN/GLOBAL | TWRP Recovery]

Redmi Note 8 Pro
[Begonia]
[Global Version Only]​
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Firmwares
Global Stable
V10.4.1.0.PGGMIXM
V10.4.2.0 to V11.0.10
V11.0.1.0 PGGMIXM
V11.0.3.0 PGGMIXM
V11.0.4.0 PGGMIXM
V11.0.6.0
China Stable
V10.4.4.0.PGGCNXM
V10.4.6.0.PGGCNXM
V10.4.8.0.PGGCNXM
V10.4.9.0.PGGCNXM
V10.4.10.0.PGGCNXM
V10.4.11.0.PGGCNXM
V11.0.1.0QGGCNXM
China Beta
V9.9.25
V9.10.17
India Stable
V10.4.3.0.PGGINXM
V11.0.1.0 PGGINXM
Europe (EEA)
V10.4.5.0.PGGEUXM
Indonesia
V10.4.2.0.PGGIDXM
V11.0.1.0PGGIDXM
Russia
V10.4.2.0.PGGRUXM
USB Drivers
Download
Unlock Bootloader
Enable OEM Unlocking
Unlock Here
Installing TWRP Recovery and ROOT
Enable USB Debugging - Goto Settings / Additional settings / Developer options / USB Debugging & USB debugging (Security settings) - Enable (If you have not activated Developer options, then Goto Settings / About phone / tap MIUI version 7 times - now developer options enabled.
Global Version
GLOBAL firmware V10.4.5.0.PGGEUXM only
Drivers installed properly
Enabled USB Debugging (enabled developers menu)
1. Turn Off
2. Go to Fastboot mode (Volume - + Power)
3. Connect to the PC
4. Download and extract in C drive, "Run as administrator" and execute "ifelixit+FLASHER+TOOLKIT+Begonia.bat".
5. Choose 1 (TWRP recovery) and enter or Choose 2 (Root Only)
Immediately disconnect the phone from the PC, otherwise it will go to reboot on command and the stock recovery will be restored.
6. Put the Minimal ADB and Fastboot in C: of your PC.
Transfer the Recovery.img in Fastboot folder
Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
7. Type fastboot flash recovery recovery.img and enter (TWRP will be installed)
8. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Stock boot IMG for V10.4.5.0.PGGEUXM just in case bootloop
TWRP for Begonia
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Proof of Video that Redmi Note 8 Pro Rooted
https://www.youtube.com/watch?v=P4rBUT9qR-0&feature=youtu.be​
Contributors
Nikas
esleer
Xakep1993
SPIRITic
m3lbrunton
Lyelik74
@topjohnwu
TWRP Community
XDA Community
Xiaomi Community

How to Root Redmi Note 8 Pro Chinese Version
Redmi Note 8 Pro
[Begonia]
[Chinese Version Only]​
How to Root and installing Google Pay
Download
Magisk-release.zip
Magisk-uninstaller
Magisk app release apk
1. Download magisk-uninstaller.zip and magisk-release.zip and transfer in MicroSD
2. Reboot to TWRP Recovery
3. Install and look for the supersu folder>select the file SuperSu_instsller.zip and install.
4. Make Wipe, Advanced Wipe, Dalvik/Art Cache, Data and Cache and swipe
5. Make Wipe and Format Data
6. Mount the SD card, install magisk-uninstaller.zip to remove the old Magisk
7. Install magisk-release.zip Install the new Magisk v20.2
8. Advanced > File Manager >system_root / system > Delete the recovery_fromboot.p file
9. Advanced (put 2 checkmarks) Close AVB2.0
10. Advanced (put 2 ticks) RM Force encrypt
11. Reboot System
12. Pass authorization, install the Magisk app-release.apk
13. Click in the application: Check SafeNet status
Installing Google Pay
Download
Google Pay Module
1. Download in the Google Pay market
2. Download the Gpay.zip module for Magisk.
3. Open Magisk Manager>Modules and install Gpay.zip module and reboot
4. Open Magisk Hide
5. Look for Google Pay and Google Services Framework and check then close the application
6. Launch Google Pay and enter your data and card details.
7. The bank will check and wait for the confirmation code via SMS.
9. For GPay to work you must configure the lock with a password or pattern.

Gcam Stable for Redmi Note 8 Pro
GCam Stable for Redmin Note 8 Pro
Download:
GCam Stable
Changelog:
Stable release for Redmi Note 8 Pro!
-> Fixed excessive noise on aux cameras (thanks to Savitar).
-> Separate AWB settings for lenses.
-> Opening settings from aux cameras is not crashing anymore but lens will be reseted to main after exiting settings (need to use proper config wyroczen_rn8pro_3.xml)
Settings:
- Configs for this version
GCam for Redmi Note 8 Pro
There are two versions of Google camera available:
Google camera mode
Night Sight
PhotoSphere
Photobooth
Slow Motion
RAW support
HDR+
Motion
Panorama
Lens Blur
Google Lens
Portrait
What's not working
Google Camera 6.1.021
Portrait mode
Video mode
Slow Motion
Night Sight
Google Camera 5.1.018
All working
Download 6.1.021
Download 5.1.018
Contributors
Arnova8G2
BSG

GPay in Redmi Note 8 Pro
Instructions
1. Download GPay in Playstore (Don't open it)
2. Go to Magisk Manager > Magisk Hide > GPay
3. Install GPay Magisk Module and reboot
4. Open GPay and Bind a card.

Nice

Not working, bootloop. To fix bootloop, need to flash original boot.img - need to put original boot.img from ROM we have in adb folder and run command "fastboot flash boot boot.img".
Before posting such tutorials I suggest to check is it even working, because on chinese version of device this will NOT WORK.

chudy88 said:
Not working, bootloop. To fix bootloop, need to flash original boot.img - need to put original boot.img from ROM we have in adb folder and run command "fastboot flash boot boot.img".
Before posting such tutorials I suggest to check is it even working, because on chinese version of device this will NOT WORK.
Click to expand...
Click to collapse
And this is not a Chinese version tutorials.
Read above before doing some things.
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Did you read about it?

madsponge26 said:
And this is not a Chinese version tutorials.
Click to expand...
Click to collapse
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.

Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.

wuxeon said:
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
Click to expand...
Click to collapse
You have chinese device, or global or EU? Or other?

wuxeon said:
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
Click to expand...
Click to collapse
You should indicate Global or CN version? What boot.img?

chudy88 said:
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Click to expand...
Click to collapse
It clearly states: [Global Version Only]
Can someone confirm it's working on global though? Including rooting?

donkyshot said:
It clearly states: [Global Version Only]
Click to expand...
Click to collapse
Yeah yeah, OP added it after my post. And it's not true - should work also on EU version.
That's why amateurs shouldn't make such threads.

chudy88 said:
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Click to expand...
Click to collapse
And what's your contribution towards fixing the problem ? ?
Do some work instead of whining and waiting for others to give you the solution on a plate.

chudy88 said:
donkyshot said:
It clearly states: [Global Version Only]
yeah yeah, OP added it after my post
Click to expand...
Click to collapse
Okay sorry I didn't know.
This thread is obviously taken from here : http://c.mi.com/thread-2529429-1-0.html
I think it should be clearly stated in the thread as it is a more complete guide than this copy.
Click to expand...
Click to collapse

robbie_lpl said:
And what's your contribution towards fixing the problem ? ?
Do some work instead of whining and waiting for others to give you the solution on a plate.
Click to expand...
Click to collapse
Still better than breaking peoples phones. I'm warning potential users to not do this if they have chinese device, that's my contribution.

chudy88 said:
Still better than breaking peoples phones. I'm warning potential users to not do this if they have chinese device, that's my contribution.
Click to expand...
Click to collapse
When signing up for this website you sign a waiver that you are the sole person responsible for your device. Bootloops too.
Don't wanna have it bricked ? Don't mess with it.
Nobody's telling you to do that.
How about some gratitude and appreciation for those who take the time and trouble looking for a solution. Sponging off others work and whingening about it ?
Show some manners.

robbie_lpl said:
When signing up for this website you sign a waiver that you are the sole person responsible for your device. Bootloops too.
Don't wanna have it bricked ? Don't mess with it.
Nobody's telling you to do that.
How about some gratitude and appreciation for those who take the time and trouble looking for a solution. Sponging off others work and whingening about it ?
Show some manners.
Click to expand...
Click to collapse
What time, what solution?! Method posted by OP for this device is known for weeks already... And its just copied solution from other tutorials for older Xiaomi phones... I can bet that OP even didn't check it and I won't be surprised if he even don't have this phone... Besides, I still don't have solid proof that it works, even on global/EU version of device.

in the end this tutorial is working or not on global?

holymoz said:
in the end this tutorial is working or not on global?
Click to expand...
Click to collapse
Not working.

[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?

Anybody is pro/has much experience with Fastboot/Mi Flash Tool/Stock Recovery?

.

Sorry to bother everybody...
I just wanna know that can we flash non carrier firmware into a verizon moto z3 (xt 1929-17) as it can not be getting its boatloader unlocked?? Please help... M new here at xda ....

How is your phone now? Is it still stucked on lockscreen lockout? Is it still containing the exact version of miui? My guess is yes but I need a confirmation.
You can't access adb from lockscreen for an obvious purposes, not even MTP.
And what is the error says?

@Osmanism.91 please ask in that particular forum before you ask it elsewhere

.

You may try from recovery flash via mi flash pro. It will need a miui account and internet connection
Second approach is by erasing every lines up to something that says "fastboot erase boot". Keep those line downwards.

.

rodagola said:
you mean delete everything but "fastboot erase boot"? probably not going to do anything because that line also shown me an error before.
Click to expand...
Click to collapse
Not everything, just every checks. It will goes like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figure 1 : Lines to be removed​
If you specify every error messages you've encountered, it will help everyone.
rodagola said:
I loaded up mi flash pro before and hit the recovery button to go to that interface but the actual recovery interface within miflashpro didn't popup, do you recommend a specific miflashpro version and specific drivers? or is it because I haven't logged into a mi account yet? can it be a brand new mi account?
Also if I actually have the chance to download a recovery rom then go into this recovery miflashpro menu...I'm scared miflashpro might delete the personal data partition, at least on regular MiFlash there's a checkbox with "save user data"
Click to expand...
Click to collapse
You need to boot to recovery, of course. You're in vanilla, so I bet you still have the miui recovery. No need to be specific about miflash pro version, any version will do. It will work like an upgrade. It will require same level or more recent firmware. You can't revert your firmware this way: the server will refuse. I don't know about the account requirements, but it will be better to log in to your account there.
Figure 2 : MiFlashPro > Recovery Flash interface. My flash is rejected. IDK why. It's been rejected when I tried to upgrade from 12.0.6 to 12.5.1. Used first method to upgrade instead.​There is that "Wipe user data" button, pretty self-explanatory.

.

rodagola said:
oh alright, recovery method could work as long as I dont click wipe data, however, how do I get to that screen you screenshoted? Since a Mi Account is a must, if I make an account today, you think will that let me work with that?
Click to expand...
Click to collapse
Boot to recovery, select "Connect to PC Suite", the 3rd option, control selection with volume rocker and select with power button. Depending on how is your device is connected, it will automatically detects the corresponding flash method. In this case, there will be this "Flash in recovery" button in the main interface. Just click that and select your ROM directory.
I don't know about account details, since I always use my account that have permission to get a device unlocked

rodagola said:
Hi all, I've had this issue for a while.
I have a RN8P Chinese running MIUI11.0.3 stable over Android9, however, I wanted to start customizing my experience but didn't mean to go 'too far'.. the issue is:
> I've never unlocked the bootloader on it, therefore no custom recovery available on it. But didn't mean to change this and wanted to keep stock ROM
> However, within my stock ROM, I wanted to have it as clean as possible from bloatware, so I went ahead and plugged the phone to my PC, installed adb, and started running commands with adb shell pm uninstall... I managed to uninstall quite a few useless apps but also thought uninstalling a system app called something like "yman" and another like "xman" was a good idea, oh boy it wasn't a good idea...
> Now the phone has some sort of soft brick. When it reboots and goes to the lock screen (I had it with swipe), I try to swipe up but the phone doesn't respond, and I think the yman and xman apps were responsible for this function, but are now uninstalled)
> I need a way to get my phone working normally. When going back to adb to reinstall these via commands, I get "unauthorized" when checking the phone status with 'adb devices', so no commands are accepted. I also went into the stock recovery mode and tried to run commands but it now shows "sideload" and will give error for every command, so I discarded this option
> Maybe I can run these commands through the fastboot menu somehow? However I don't know how (if even possible)
> If there's absolute no way to get this RN8P to receive the command to reinstall the same package that caused the trouble, then I think I could try flashing...
> I went and downloaded MiFlash, downloaded the corresponding same exact stable ROM on same region for fastboot, plugged my phone and checked SAVE USER DATA on the botton, in order to have the data partition intact, but MiFlash throws some errors. I read somewhere just click on the desired batch file while the phone is still plugged in and it might bypass MiFlash errors, but it didn't, then I tried redownloading drivers and from 3 different PCs, looked up why MiFlash was failing and found out perhaps deleting a few lines from the batch would fix it, but I kept getting further errors related to the next line and the errors were endless.
> Still with the flashing idea on MiFlash, I downloaded the other further Chinese fastboot ROMs, as in upgraded versions to Android10 and MIUI12 (instead of the exact versions the phone still had). But now I get same thing as before, endless errors keep coming up and the flash process won't go through.
> I really want to retain my personal data, so I was suggested to try MiFlashTool v2, however, I've heard that one has no option to save the data partition, so I haven't bothered yet, and before I move on to try, could anybody with experience tell me their experience?
> In general, would there be a way still for me to fix the phone without losing user data? Maybe there's hopes the phone can receive adb commands somehow still? I'm confident I can revive the phone very quick through adb, if only it still wanted to be adb friendly...
Thanks to any pros that might be out there and would save a junior
Click to expand...
Click to collapse
You said you have a RN8Pro Chinese.
Can you give us the full MIUI ROM filename that you're attempting to flash? We have to be sure you're flashing the correct ROM.
Also check if the MIUI ROM you downloaded isn't corrupted.
Compass.

.

rodagola said:
I downloaded "begonia_images_V11.0.3.0.QGGCNXM_20200518.0000.00_10.0_cn" which is supposed to be rn8p chinese fastboot miui11.0.3 a10. And from 2 different sources to try to make sure it wasn't corrupted. I don't know any actual way to check if the ROM is corrupted or not...
Before the soft brick, the phone had this exact same version but for a9 instead of a10. So I guess this is some sort of upgrade.
I'm now going to try downloading same thing but for the recovery version within miflashpro, just like what kekesed97 said
This could have a different output, so I'll update here
If this doesn't go successful, then I guess next step is trying SP flash tool? though I have no clue how to use that one
Click to expand...
Click to collapse
You downloaded a very old MIUI but it should work. Check the link below for a newer release. The latest fastboot for MIUI 12.0.x China is V12.0.5.0.QGGCNXM (if I didn't skip a version; the list is quite big). There's also MIUI 12.5.x China if you want the latest stable (MIUI 12.5.x Global is buggy so I'd skip MIUI 12.5.x for now).
https://xiaomifirmwareupdater.com/archive/miui/begonia/
Here is a YouTube playlist that might help you: https://www.youtube.com/playlist?list=PLLy0_Q3fJ1DLjE5Cx7uCD3yTxeTaUbiIo
Be careful when you flash so that you keep your data. If I remember well that author usually wipes data in his videos.
I don't know which package manager people with Windows are using these days, but I guess WinRar is a popular choice. WinRar should have a "test file" so you could try that to check for a corrupted download.
I can't help you with the flashing process on Windows since I don't use it. kekesed97 instructions or the YouTube playlist should work (I think the YouTube author uses different software for flashing, just so you know).
Compass.

.

rodagola said:
Hi again, I'm in MiFlashPro recovery section, and have downloaded the corresponding recovery ROM, it downloaded as zip. Now should I just browse and select it as is, or do I need to uncompress and select something else? My guess is select as is but would like to confirm. Thanks a lot for your tips so far dude.
Click to expand...
Click to collapse
No unzipping. Use it as is as it will be sent over your phone and flashing is done recovery side (put it simply, it's an ADB sideload, with restrictions)
rodagola said:
Moreover, there's an option to download an incremental zip (just the ota extra files instead of full zip) would you recommend that over full zip? would that fix the brick? My guess is not because it doesn't have all the apks on it, whereas the full one has all the apks so it can reinstall the uninstalled app that caused my brick, and probably the OTA version can't, but I'm NOT sure...
Click to expand...
Click to collapse
It only accepts recovery ROMs (2 gb ones). You are only allowed to flash greater version of your current firmware from the same ROM distribution. It's works like updating your phone when incremental update fails after all.
rodagola said:
Also, to add more detail, I was looking arond and found that MiFlash Tool could not be so friendly with phones running on Mediatek so it's more for Qualcomms... instead, SP flash tool is more meant for MediaTeks (so that makes me believe that's why my RN8P was having all sorts of errors with that "MiFlashTool"). Anyway, I'll stay away from SP flash tool aswell because I read it always wipes everything. So my only real chance now seems to be the Recovery method on MiFlashPro, but I'd love if you confirmed my inquiry mentioned above
Click to expand...
Click to collapse
Not quite correct. There are 3 different flashing methods there. Recovery mode, fastboot mode, and deep flash mode.
In recovery mode, flash is using ADB sideload-like mechanics (or it is? I have no evidence, but it works similiarly that way), while in the Mi Flash program is using fastboot method. Both methods are platform-independent, which means it will work in both MTK or SD chipsets, as long as the phone permits. As for deep flash one, it will require lower level access to hardwares, and only manufacturers are having such access. Thus, flashing method diverges. MTK is using SP Flash tools, in which the mechanics behind that can be red in the CFW Megathread (CFW is quite irrelevant today, but the boot process explanation is something else that will never went irrelevant, unless another boot sequence is introduced), as for SD chipsets will use QPST over Sahara Protocol (more info on this: just dig how to ressurect xiaomi redmi note 5 pro edl 9008 that have their arb lock triggered).
It isn't that it will wipe your phone clean that to be your concern. That can be avoided by selecting "Download Only". But that there is this method requires a special account that only service centres have (but a bypass method is known recently, just dig deeper). Consider this as your last resort. Oh yes, it will need a fastboot rom, and the scatter file is available in the ROM directory.

.

rodagola said:
Hi again, I'm now in recovery mode in MiFlashPro and have attempted browsing the files I downloaded from https://xiaomifirmwareupdater.com
The files I choose were recovery roms with "stable branch" ( I don't know if weekly branch would work better?). Well, I loaded the stable ones into the menu and xiaomi servers authenticated and checked the rom... but then it throws "Sorry, flash to this stable version is not allowed" error.
What is this... I first tried with my downloaded zip package "miui_BEGONIA_V11.0.3.0.QGGCNXM_b656ebe642_10.0"
which is 1 step forward from the version I had (I had v11.0.3 with A9 but this package should update me to A10)
got the error... then tried with a little further update with another zip I downloaded "miui_BEGONIA_V12.0.2.0.QGGCNXM_972f66522c_10.0"
Same error again after xiaomi servers check it out.
There only seems to be a few more stable ROM versions for my chinese variant AFTER these. Those are: "V12.0.3.0.QGGCNXM", "V12.0.4.0.QGGCNXM", "V12.0.5.0.QGGCNXM" and "V12.5.1.0.RGGCNXM".
Before I try with these next 4 versions, from older to newer, I'd like to ask if should I rather try with BETA versions instead of stables... (since the error I was getting says: "Sorry, flash to this stable version is not allowed")
Anyways, I have read somewhere that with an authorized account it would let me install betas and stuff no problem, however those 2 that I tried to install weren't even betas. So I'm confused.
Thanks a lot again for your help dude
Click to expand...
Click to collapse
Don't do that.
Weekly is beta and doesn't mean it's better. It's supposed to be a test version and bug hunting release to device enthusiast so xiaomi can go fix it and accumulate the bug fixes to be included in the next stable version. Weekly is always newer so moving from beta to stable is considered downgrade, which require a data wipe. Btw, is your current firmware is from stable branch?
Or perhaps is it because your account doesn't hold a permission to flash since it's never been granted bootloader unlock permission? Idk about the account part.
Well, now try to use fastboot method if recovery update method fails. Mi Flash Pro have it so you don't have to download another tool. It allows broader range of firmware version, particularly for this phone.
Download a recovery rom and unzip it. Load it to mi flash, boot your phone to fastboot, and flash it there.
Figure 3: Mi Flash main interface. Choose this option to retain data​Or modify a flash batch file as I instructed in previous post and run it through command prompt.
I never flashed anything in a locked bootloader because I always unlock my phone the moment I grab it. But one thing for sure is you are bound to the same ROM region. Never flash any other ROM from another region distribution. You have been warned.

.

.

rodagola said:
Also, reading other threads, I should quote this guy called "zqm" on xda forums. From this post: https://forum.xda-developers.com/t/is-mi-unlock-really-needed-to-unlock-bootloader.4024519/
I quote his input: "This shouldn't be a concern for now. Xiaomi isn't planning to restrict unlocking the bootloader. Another thing you should consider is that Redmi note 8 pro gets easily bricked by flashing custom twrp, magisk, etc. but it's not easily recovered as it requires xiaomi authorised account."
So he's implying you need an auth account for recovery ROMs, (I think)......
I'm reposting this for you because you said you didn't know about the account requirements, maybe this brings forward a theory. However I insist I might need to borrow an authorized account now but don't know where or how
Click to expand...
Click to collapse
No, that one thing is different. What @zaqm talking about is the one to access the low level parts of hardware i.e. deep flash via SPFT, which only the manufacturers have, perhaps xiaomi engineering team and service center team to name a few. Adb sideload and fastboot is user accessible, so it doesn't need such permission, with limited access to emmc partitions (afaik no raw readback is one of its limitation). And fastboot doesn't enforce any account security measure, so does the adb sideload. That thing is implemented via mi recovery and mi flash pro. It will send an sha check to one of xiaomi server, returning if the phone is ok to be flashed. After the check returned true, it will begin to send the zip file to phone. This procedure is non-skippable. Therefore, you can only send firmwares this way. This is not happening in custom recovery, so you can send any command. But unfortunately you have vanilla.
After a quick inspection, that is indeed ADB sideload.
It refuse adb sideload command on redmi note 5 pro with vanilla recovery, unlocked bootloader (see attachment). After the command is issued, the phone immidiately restart and boot to system. It's likely won't hurt, so I think it worth the shot.
Try this :
1. Connect your phone to phone thru pc suite mode in recovery
2. Download minimal adb and fastboot or adb platform tools. Extract it.
3. Check your device by executing this in command prompt:
Code:
adb devices
4. If your device is connected, command prompt will return this:
Code:
D:\begonia\Minimal ADB and Fastboot>adb devices
List of devices attached
3d9ac49b sideload
5. Rename your firmware to something easy (something like update.zip but I don't care) and copy it to the same directory as the adb directory
6. Execute sideload command
Apache config:
adb sideload update.zip
7. See if wonder happens
8. ...
9. Profit?!
Anyway write back if this you succeed or not.

How To Guide How to flash a stock rom [alioth]

Hello everyone.
The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd.​Warnings!​Before starting I would like to make one point clear, every moding operation involves risks that could lead to bootloop, softbrick or hardbrick of your phone, they can be caused by countless circumstances or actions, so you need the utmost attention and scrupulousness in performing certain operations.​What I will describe I have tested it on my F3 and it works, in any case, ​neither I nor the xda forum are responsible for any breakdowns on the phone caused by the operations described below!​Having said that, let's start...
All you need is:​
Bootloader unlocked, using the official tool you find here
Latest version of miflash, which you can download from here;
SDK platform tools, which you can download from here;
Stock fastboot rom, which you can download from here, here or here.
Make a backup of your data because they will be deleted in the process!
Now that you have everything you need, follow the steps:​1) How to flash a stock rom using miflash.​
Unzip miflash to C:\ ; [Only for the first time]​
Unzip SDK platform tools to C:\ ; [Only for the first time]
Unzip the fastboot rom in the miflash folder;
Rename the fastboot rom folder with a shorter name and no spaces like "V12.5.6.0.RKHEUXM";
Disable driver signature enforcement in windows 10; [Only for the first time. It is a temporary option that is reactivated the next time the pc is restarted]
Spoiler: How to disable driver signature
1 - Open settings;
2 - Go to update and security;
3 - In the left column click on restore;
4 - Under advanced restart click on restart now;
The pc will restart in a blue screen, click in sequence:
1. Troubleshoot;
2. Advanced options;
3. Startup Settings;
4. Restart;
5. Press the 7 or F7 key to Disable driver signature.
Now the pc restarts by itself.
Go to the miflash folder in c:\, open it and search for XiaoMiFlash.exe, right click and start as administrator;
Click on the driver button at the top and then install (if a warning message comes out, install anyway); [Only for the first time]
Restart your pc; [Only for the first time]
Go to the miflash folder in c:\, open it and search for XiaoMiFlash.exe, right click and start as administrator;
Click on the select button at the top left and navigate to the fastboot rom folder in the window that opens, then press ok; (If you followed the guide it is located in C:\MiFlash20210226\namethatyougavetotherom);
Click on the clean all option at the bottom right;
Spoiler: Why clean all option
- The clean all option allows you to flash the rom avoiding blocking the bootloader (which I recommend);
- The save user data option allows you to flash the rom without deleting the data (not recommended if you come from custom rom or from stock rom of different regions and does not block the bootloader);
- The clean all and lock option instead at the end of the flash blocks the bootloader which in some cases especially if you flash a rom that is not the original and can lead to a brick of the phone (I do not recommend blocking the bootloader, but if you want to do it make sure you are on the stock rom of the same region your phone was born with).
Now in the phone enable debug USB in developer option;
Spoiler: Developer option
Enable developer option:
- Go to settings;
- Tap on my device;
- Tap on all specifications;
- 7 tap on miui version.
Debug USB:
- Go to settings;
- Other settings;
- Developer options;
- Debug USB.
Restart the phone in fastboot mode and connect it to a rear USB port or in any case to a USB 2.0;
Spoiler: Fastboot mode
Turn the phone off;
Long press of the power key + volume -.
If the phone is recognized by miflash its code appears in the first row of the table otherwise click the refresh button at the top right;
Make sure clean all is selected and click on flash;
The flash lasts several minutes wait without touching anything;
Surely miflash at the end of the flash will give an error because the clean all option is selected and not blocking the bootloader at the end of the process it recognizes it as an error. Do not worry!!! it's normal;
If all went well the phone should restart by itself, (attention! the first start of the phone lasts several minutes stuck on the miui logo, wait until the configuration screen appears.
2) How to flash a stock rom using cmd.​Small premise; You could easily use this method even just by starting the .bat file inside the fastboot rom, but if any problems should occur or at the end of the process the window would close immediately without giving you the time to understand what happened, while if you run the .bat file directly from the prompt (cmd) you have the possibility to check the whole flash process and see if any errors occur because the window will remain open anyway.​
Unzip miflash to C:\ ; [Only the first time to install drivers]​
Unzip SDK platform tools to C:\ ; [Only for the first time]
Unpack the fastboot rom and move all content to C:\platform-tools;
Disable driver signature enforcement in windows 10; [Only for the first time. It is a temporary option that is reactivated the next time the pc is restarted]
Spoiler: How to disable driver signature
1 - Open settings;
2 - Go to update and security;
3 - In the left column click on restore;
4 - Under advanced restart click on restart now;
The pc will restart in a blue screen, click in sequence:
1. Troubleshoot;
2. Advanced options;
3. Startup Settings;
4. Restart;
5. Press the 7 or F7 key to Disable driver signature.
Now the pc restarts by itself.
Go to the miflash folder in c:\, open it and search for XiaoMiFlash.exe, right click and start as administrator; [Only for the first time]
Click on the driver button at the top and then install (if a warning message comes out, install anyway); [Only for the first time]
Restart your pc; [Only for the first time]
Go to the start button with the mouse and click with the right button;
In the menu that will open click on command prompt (administrator) a cmd window will open;
Now in the phone enable debug USB in developer option;
Spoiler: Developer option
Enable developer option:
- Go to settings;
- Tap on my device;
- Tap on all specifications;
- 7 tap on miui version.
Debug USB:
- Go to settings;
- Other settings;
- Developer options;
- Debug USB.
Restart the phone in fastboot mode and connect it to a rear USB port or in any case to a USB 2.0;
Spoiler: Fastboot mode
Turn the phone off;
Long press of the power key + volume -.
Now in the cmd window you are in the path: C:\windows\system32. First we move to the platform tools folder and check if the pc recognizes the phone in fastboot (if you followed the guide it will be in C:\platform-tools) to move to the folder press this command and press enter:
Code:
cd c:\platform-tools
Now check if the pc recognizes the phone in fastboot with this command and press enter (The phone code should appear):
Code:
fastboot devices
If the code appears you can start the .bat file to start the flash, then type this command and press enter:
Code:
flash_all.bat
Spoiler: Why flash_all.bat
- The flash_all.bat allows you to flash the rom avoiding blocking the bootloader (which I recommend);
- The flash_all_except_storage.bat allows you to flash the rom without deleting the data (not recommended if you come from custom rom or from stock rom of different regions and does not block the bootloader);
- The flash_all_lock.bat instead at the end of the flash blocks the bootloader which in some cases especially if you flash a rom that is not the original and can lead to a brick of the phone (I do not recommend blocking the bootloader, but if you want to do it make sure you are on the stock rom of the same region your phone was born with).
The flash lasts several minutes wait without touching anything but you can follow the trend in case there are problems;
If all went well the phone should restart by itself, (attention! the first start of the phone lasts several minutes stuck on the miui logo, wait until the configuration screen appears.
I hope this guide can help you to get back or flash the stock rom.
Happy flash everyone!​

Thanks.
Can i do by twrp Install the rom

Nandowiko said:
Thanks.
Can i do by twrp Install the rom
Click to expand...
Click to collapse
It is not advisable to flash the stock rom with twrp for two simple reasons:
1) For the moment the only two twrp developed are in beta state and it is not certain that they perform this task correctly.
2) Twrp does not do the arb check (Anti RollBack) To find out more, read here:
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
So using miflash or the executable via cmd is the safest and most reliable way to flash the stock rom.

This is not working with locked bootloader.. any other method with locked bootloader to flash stock rom?

Mihiranpura said:
This is not working with locked bootloader.. any other method with locked bootloader to flash stock rom?
Click to expand...
Click to collapse
It is true! you need the unlocked bootloader, I read that with this tool you can do it. I have not tried it, I do not guarantee the success of the flash with a locked bootloader and in any case I strongly advise against flashing with a locked bootloader. If any errors occur it is risky and complicated to recover it, it is always better to unlock it.

RollDload said:
Hello everyone.
The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd.​Warnings!​Before starting I would like to make one point clear, every moding operation involves risks that could lead to bootloop, softbrick or hardbrick of your phone, they can be caused by countless circumstances or actions, so you need the utmost attention and scrupulousness in performing certain operations.​What I will describe I have tested it on my F3 and it works, in any case, ​neither I nor the xda forum are responsible for any breakdowns on the phone caused by the operations described below!​Having said that, let's start...
All you need is:​
Bootloader unlocked, using the official tool you find here
Latest version of miflash, which you can download from here;
SDK platform tools, which you can download from here;
Stock fastboot rom, which you can download from here, here or here.
Make a backup of your data because they will be deleted in the process!
Now that you have everything you need, follow the steps:​1) How to flash a stock rom using miflash.​
Unzip miflash to C:\ ; [Only for the first time]​
Unzip SDK platform tools to C:\ ; [Only for the first time]
Unzip the fastboot rom in the miflash folder;
Rename the fastboot rom folder with a shorter name and no spaces like "V12.5.6.0.RKHEUXM";
Disable driver signature enforcement in windows 10; [Only for the first time. It is a temporary option that is reactivated the next time the pc is restarted]
Spoiler: How to disable driver signature
1 - Open settings;
2 - Go to update and security;
3 - In the left column click on restore;
4 - Under advanced restart click on restart now;
The pc will restart in a blue screen, click in sequence:
1. Troubleshoot;
2. Advanced options;
3. Startup Settings;
4. Restart;
5. Press the 7 or F7 key to Disable driver signature.
Now the pc restarts by itself.
Go to the miflash folder in c:\, open it and search for XiaoMiFlash.exe, right click and start as administrator;
Click on the driver button at the top and then install (if a warning message comes out, install anyway); [Only for the first time]
Restart your pc; [Only for the first time]
Go to the miflash folder in c:\, open it and search for XiaoMiFlash.exe, right click and start as administrator;
Click on the select button at the top left and navigate to the fastboot rom folder in the window that opens, then press ok; (If you followed the guide it is located in C:\MiFlash20210226\namethatyougavetotherom);
Click on the clean all option at the bottom right;
Spoiler: Why clean all option
- The clean all option allows you to flash the rom avoiding blocking the bootloader (which I recommend);
- The save user data option allows you to flash the rom without deleting the data (not recommended if you come from custom rom or from stock rom of different regions and does not block the bootloader);
- The clean all and lock option instead at the end of the flash blocks the bootloader which in some cases especially if you flash a rom that is not the original and can lead to a brick of the phone (I do not recommend blocking the bootloader, but if you want to do it make sure you are on the stock rom of the same region your phone was born with).
Now in the phone enable debug USB in developer option;
Spoiler: Developer option
Enable developer option:
- Go to settings;
- Tap on my device;
- Tap on all specifications;
- 7 tap on miui version.
Debug USB:
- Go to settings;
- Other settings;
- Developer options;
- Debug USB.
Restart the phone in fastboot mode and connect it to a rear USB port or in any case to a USB 2.0;
Spoiler: Fastboot mode
Turn the phone off;
Long press of the power key + volume -.
If the phone is recognized by miflash its code appears in the first row of the table otherwise click the refresh button at the top right;
Make sure clean all is selected and click on flash;
The flash lasts several minutes wait without touching anything;
Surely miflash at the end of the flash will give an error because the clean all option is selected and not blocking the bootloader at the end of the process it recognizes it as an error. Do not worry!!! it's normal;
If all went well the phone should restart by itself, (attention! the first start of the phone lasts several minutes stuck on the miui logo, wait until the configuration screen appears.
2) How to flash a stock rom using cmd.​Small premise; You could easily use this method even just by starting the .bat file inside the fastboot rom, but if any problems should occur or at the end of the process the window would close immediately without giving you the time to understand what happened, while if you run the .bat file directly from the prompt (cmd) you have the possibility to check the whole flash process and see if any errors occur because the window will remain open anyway.​
Unzip miflash to C:\ ; [Only the first time to install drivers]​
Unzip SDK platform tools to C:\ ; [Only for the first time]
Unpack the fastboot rom and move all content to C:\platform-tools;
Disable driver signature enforcement in windows 10; [Only for the first time. It is a temporary option that is reactivated the next time the pc is restarted]
Spoiler: How to disable driver signature
1 - Open settings;
2 - Go to update and security;
3 - In the left column click on restore;
4 - Under advanced restart click on restart now;
The pc will restart in a blue screen, click in sequence:
1. Troubleshoot;
2. Advanced options;
3. Startup Settings;
4. Restart;
5. Press the 7 or F7 key to Disable driver signature.
Now the pc restarts by itself.
Go to the miflash folder in c:\, open it and search for XiaoMiFlash.exe, right click and start as administrator; [Only for the first time]
Click on the driver button at the top and then install (if a warning message comes out, install anyway); [Only for the first time]
Restart your pc; [Only for the first time]
Go to the start button with the mouse and click with the right button;
In the menu that will open click on command prompt (administrator) a cmd window will open;
Now in the phone enable debug USB in developer option;
Spoiler: Developer option
Enable developer option:
- Go to settings;
- Tap on my device;
- Tap on all specifications;
- 7 tap on miui version.
Debug USB:
- Go to settings;
- Other settings;
- Developer options;
- Debug USB.
Restart the phone in fastboot mode and connect it to a rear USB port or in any case to a USB 2.0;
Spoiler: Fastboot mode
Turn the phone off;
Long press of the power key + volume -.
Now in the cmd window you are in the path: C:\windows\system32. First we move to the platform tools folder and check if the pc recognizes the phone in fastboot (if you followed the guide it will be in C:\platform-tools) to move to the folder press this command and press enter:
Code:
cd c:\platform-tools
Now check if the pc recognizes the phone in fastboot with this command and press enter (The phone code should appear):
Code:
fastboot devices
If the code appears you can start the .bat file to start the flash, then type this command and press enter:
Code:
flash_all.bat
Spoiler: Why flash_all.bat
- The flash_all.bat allows you to flash the rom avoiding blocking the bootloader (which I recommend);
- The flash_all_except_storage.bat allows you to flash the rom without deleting the data (not recommended if you come from custom rom or from stock rom of different regions and does not block the bootloader);
- The flash_all_lock.bat instead at the end of the flash blocks the bootloader which in some cases especially if you flash a rom that is not the original and can lead to a brick of the phone (I do not recommend blocking the bootloader, but if you want to do it make sure you are on the stock rom of the same region your phone was born with).
The flash lasts several minutes wait without touching anything but you can follow the trend in case there are problems;
If all went well the phone should restart by itself, (attention! the first start of the phone lasts several minutes stuck on the miui logo, wait until the configuration screen appears.
I hope this guide can help you to get back or flash the stock rom.
Happy flash everyone!​
Click to expand...
Click to collapse
Thank You So Much - Get Back Device in normal Mode

Hello @RollDload
I have Flashed below Fastboot ROM in Mi11X India using the CMD method and working fine but I am surprised why I didn't get OTA for the next Version - Below Mentioned Update Tracker got from another post - My Bootloader is Unlocked - If I manually Update next version using recovery ROM then Can I flash without data lost? - If possible please let me know the solution
2021-04-20 | Stable Fastboot | V12.5.2.0.RKHCNXM (Currently Avalibale)
2021-05-25 | Stable Recovery | V12.5.3.0.RKHCNXM (Should Offer this via OTA as per my Assumption)

sunnymodh said:
Hello @RollDload
I have Flashed below Fastboot ROM in Mi11X India using the CMD method and working fine but I am surprised why I didn't get OTA for the next Version - Below Mentioned Update Tracker got from another post - My Bootloader is Unlocked - If I manually Update next version using recovery ROM then Can I flash without data lost? - If possible please let me know the solution
2021-04-20 | Stable Fastboot | V12.5.2.0.RKHCNXM (Currently Avalibale)
2021-05-25 | Stable Recovery | V12.5.3.0.RKHCNXM (Should Offer this via OTA as per my Assumption)
Click to expand...
Click to collapse
Hi, I'm glad it worked fine ...
First try to clear the update application data.
If you don't get the update try the recovery method, you shouldn't lose your data. Do a backup anyway to be sure ...

First of all thanks for the Response
I have already tried clear data of Update app, also login into Mi Account but non of the works
Now I will use the recovery method - will follow the below steps let me correct if I am going to do wrong steps
Download this ROM 2021-05-25 | Stable Recovery | V12.5.3.0.RKHCNXM
Put it into Device -> Choose update package - > will flash
Will take backup for Safety

Hi all!
Trying to flash stock ROM (On Linux, cmd command mode), i get following message: "Missmatching image and device" although my phone is a Poco F3 Alioth :/

sunnymodh said:
First of all thanks for the Response
I have already tried clear data of Update app, also login into Mi Account but non of the works
Now I will use the recovery method - will follow the below steps let me correct if I am going to do wrong steps
Download this ROM 2021-05-25 | Stable Recovery | V12.5.3.0.RKHCNXM
Put it into Device -> Choose update package - > will flash
Will take backup for Safety
Click to expand...
Click to collapse
Why not try the latest update directly? So there is no more need for the ota.
Remember that "CN" is the Chinese version.
"ID" the Indian version.
"MI" l "EEA" etc the global versions.
Use the one corresponding to the one you already have in use.
Otherwise flash what you would like with miflash but avoid blocking the bootloader.

nicfio said:
Hi all!
Trying to flash stock ROM (On Linux, cmd command mode), i get following message: "Missmatching image and device" although my phone is a Poco F3 Alioth :/
Click to expand...
Click to collapse
I don't know, I don't use linux, but try to check the drivers and make sure you use the right rom for your model, there are three versions, china india and global.

RollDload said:
Why not try the latest update directly? So there is no more need for the ota.
Remember that "CN" is the Chinese version.
"ID" the Indian version.
"MI" l "EEA" etc the global versions.
Use the one corresponding to the one you already have in use.
Otherwise flash what you would like with miflash but avoid blocking the bootloader.
Click to expand...
Click to collapse
Yes...Correct regarding latest flash
let me correct you regarding Version
ID - Indonesia ROM
IN - India ROM
I have changed ROM from India to another for Miui Dialer only but after installation, I found Xiaomi EU ROM much better than any other Region ROM
Chinese ROM - good but lots of bloatware, No Gapps
Xiaomi EU - Excellent Performance, MIUI Dialer with Gapps (you can download only from Xiaomi EU website (EU & EEA) both are different Version

Im stuck on
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what to do?
edit:
okay so I panicked. lol
I disconnected the phone from pc then I realized it was a dumb move
the phone is still on fastboot though.
So I reconnected the phone to pc and it wont detect. I am worried that if I turned off my phone it will die.
So what I did next was hold power button and volume down trying my luck to get into fastboot again.
And it did boot into fastboot again.
Then using miflash and everything worked now im on stock rom. Thanks!
PS: Im so happy that I am still within Gods grace.

LynnnXDA said:
Im stuck on
View attachment 5557529
what to do?
edit:
okay so I panicked. lol
I disconnected the phone from pc then I realized it was a dumb move
the phone is still on fastboot though.
So I reconnected the phone to pc and it wont detect. I am worried that if I turned off my phone it will die.
So what I did next was hold power button and volume down trying my luck to get into fastboot again.
And it did boot into fastboot again.
Then using miflash and everything worked now im on stock rom. Thanks!
PS: Im so happy that I am still within Gods grace.
Click to expand...
Click to collapse
yes, unplugging the phone in the middle of a flash is very dangerous, but luck was on your side. better this way

Guys just wanted to clear a doubt i had
So currently I have a mi11x Indian version running miui 13
So my first question is if I unlock via miunlock and then flash custom ROMs (pixelexperience)
Will I be able to go back to stock rom and relock bootloader if in the future I need to go back to stock or something
Or will it cause a brick.

Please, you don't need to know this but I am disabled, get really low on energy really quick. Trying to solve this is driving me mad!
Mi 11 bought with CN stock.
Unlocked the bootloader, loaded global rom for miui 12, all worked well.
OTA didn't work though.
Updated yesterday to latest global rom. All seems to work except, Google Wallet which used to work great gives me their CTS error.
Nothing actually changed on the phone, it's still just the unlocked phone, stock global rom.
I tried loading an older 12.5 rom and then, did an OTA update to MIUI 13
Still, Google Wallet doesn't want to know.
Was considering flashing again with the stock global rom (I don't want the CN on there) and locking the boot again but, would that even work or, does it have to be the CN stock rom?
All the bypass options for the security are just beyond my mind now sadly.

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.