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.img8. 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.img8. 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?
Related
Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
To flash only the US modem to restore band 12 on any ROM:
Download: https://www.androidfilehost.com/?fid=601300970940399635
Extract the zip file and place it in your adb & fastboot folder.
From your abd & fastboot files folder (with the modem image in there too) open a command prompt and run
fastboot flash modem modem-5.8.019s.img
Then reboot your phone.
Keep this file handy because you'll need it every time you flash a ROM that doesn't have a US modem.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, flash whatever ROMs you want, and restore US modem.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.
Thank you for the good guide.
well done. Please keep it updated...
suhridkhan said:
well done. Please keep it updated...
Click to expand...
Click to collapse
lilila said:
Thank you for the good guide.
Click to expand...
Click to collapse
Thank you and you're welcome. I'll try to keep this updated as new info or procedures come up :good:
hondajohn88 said:
Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, and flash whatever ROMs you want.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.
Click to expand...
Click to collapse
Nice one John
seffmono said:
Nice one John
Click to expand...
Click to collapse
Thank you kind sir
"...It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther..."
Did I miss the part on how to keep the Band 12 capabilities?
Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk
ceo.mtcl said:
Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Flashing the CN-US ROM will not relock the bootloader, so you're safe there.
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk
rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
If you install TWRP from fastboot (fastboot flash recovery twrp.img), it should replace the factory recovery.
rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Click to expand...
Click to collapse
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.
seffmono said:
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.
Click to expand...
Click to collapse
i will try that.
I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?
worries said:
I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?
Click to expand...
Click to collapse
I hate to speak for everyone here but it's highly unlikely someone will take the time to do that. I suggest you instead do as much research as you can, and make a video for the next person like yourself that prefers it. Speaking from experience most people on XDA will recommend spending as much time reading and learning as you can, and then taking the "leap" on your own. Rooting and unlocking is not for the faint of heart, and a bit of confidence in your own abilities can go a long way! I hope this doesn't sound condescending, but just my advice. Best of luck!
I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
---------- Post added at 05:55 AM ---------- Previous post was at 05:29 AM ----------
Nevermind. Booted into recovery and formatted the system then it ran fine.
huemedia said:
I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
Click to expand...
Click to collapse
It had this happen and If i remember correctly, their is a bug in the system and it wont let you past that screen regardless what. Just boot to twrp do a data backup. Format everything else except internal storage and reflash your rom
I followed this guide and flashed the US modem zip on top of stock 19s. However, my SIM is recognized and the "Mobile Networks" setting page is grayed out. However, my phone is still booting with Chinese text in the bootloader. How do I fix this?
Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3
toanau said:
Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3
Click to expand...
Click to collapse
I am trying the long way and it's failing (20s)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Im dumb, nevermind
EDIT 8/2/19: I do not own this device anymore. So i cannot and dont know if anything changed about the procedures unlocking rooting etc. BUT if you are getting any trouble i might can help you. Comment your thoughts below
Hey guy, i saw a lot of guys here wondering how to root and flash twrp recovery on thier devices . Today i am gonna show you how to do that.
First of all make sure 3 things :
1. backup your images, contacts, music tracks etc on a external SD CARD, or on your computer.
2. You MUST have the BOOTLOADER unlocked. To do that, read this guide http://en.miui.com/thread-202290-1-1.html
3.Charge your device to 80%+
HOW TO FLASH TWRP AND ROOT MI MAX
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img"
14. Your phone is now in TWRP recovery mode ( if it is not, the write on ADB: reboot recovery )
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
DOWNLOADS
1. ADB- (https://forum.xda-developers.com/showthread.php?t=2588979)
2. XIAOMI MI MAX HYDROGEN DRIVERS (http://xiaomiadvices.com/download-xiaomi-usb-drivers/)
3. TWRP RECOVERY IMAGE https://dl.twrp.me/hydrogen/ LATEST VERSION IS twrp-3.2.3-0
4. BetaSuperSu 2.74 http://www13.zippyshare.com/v/OFQGvIyA/file.html
RESERVED
The thread must be removed to XIAOMI MI MAX GUIDES, NEWS, & DISCUSSION
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
hello, please write again your problem. I can understand what do you mean.
StonebridgeGr said:
hello, please write again your problem. I can understand what do you mean.
Click to expand...
Click to collapse
Ok just two questions then, because I'm not sure what you can't understand. Please explain.
1) What Android, MIUI and kernel did you root?
2) Do you have SuperSu.zip in TWRP 3.0.3 by default? You didn't say anything in your guide about downloading it and from where + what version.
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
This twrp. Img it's for all the versions but only for mi max. Not the prime . This twrp doesn't contain superSU. If I remember correctly. But if on the TWRP contain the super su. Don't say yes. Just flash it like I saying on the guide. Maybe they upload a newest version. You can use the new. I think I put the official website . I will check it.
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
noob456 said:
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
Click to expand...
Click to collapse
LOL I forgot to add the superSU link...
That's what I told you. Then please do.
noob456 said:
That's what I told you. Then please do.
Click to expand...
Click to collapse
ok on the first post you can find all the links. if i miss something please tell me here !
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
It's compatible with mi max. You will not have any problem. Don't worry
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
Waiting to tell me if everything went fine with the installation and the flashing
Hey, tried following Your guide to install a new rom last night. Great guide for noobs like me, but it may be worth renaming the thread to something like "How to flash whatever makes You happy on to Your Mi Max". These instructions seem to work fine regardless of what's being flashed. Great job, mate!
So I finally tried it and it was successful for me as well! But I used the latest version of TWRP (3.1.0) and SuperSu (2.79-20161205). Please add a point in your tutorial to upload SuperSU.zip to the phone first, because out of emotion, I forgot... So I flashed TWRP, booted it and then... ups... no SuperSu So I wanted to reboot the phone to upload SuperSU but since only SuperSU patches dm-verity (the thing I was afraid of the most - I told you before), my phone got into boot-loop and didn't want to start. So I just uploaded SuperSU to a memory card, entered Fastboot Mode again with key-combination, plugged the cable, typed "fastboot reboot-bootloader" command and was again in TWRP to flash SuperSu from my memory card.... ufff.
So I would reedit it a bit:
0. Copy SuperSU.zip to the phone/memory card!
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img" - the phone will get disconnected from your PC automatically
14. Your phone is now in TWRP recovery mode (it takes about 30-60 seconds before FastBoot screen switches into TWRP - wait patiently)
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
Hey, I just got connected with WiFi and new MIUI 8.2.3.0 MBCMIDL wants to be installed, although the phone is rooted with bootloader unlocked. Is it safe to apply the update? Is it goona remove root so that I have to go over the process again?
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Is there anyway to root the phone without connecting it to pc?
noob456 said:
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Click to expand...
Click to collapse
Thanks for saving me the trouble.
Can someone help with a better method of applying updates?
Will downloading the zip (1.4GB approx) and flashing via TWRP help?
DISCLAIMERS (please read !)
This thread is made for the Redmi Note 9, also known as Redmi 10X 4G.
This device's codename is Merlin.
I will not be held responsible if you brick your device.
Follow the instructions shown in this thread at your own risks.
Follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded files.
Feel free to cite parts of this thread in your own, just make sure to give credit where it's due.
Prerequisites for most manipulations
Your phone, well charged if possible
The USB cable used to link your phone to your computer (the one on your charger works just fine)
A computer, with recent ADB & Fastboot (Platform Tools)
Some time, patience, and the ability to read and follow instructions!
Tutorials
Spoiler: Unlocking your bootloader (Required for all other tutorials below)
Step 1
Make sure you have a Mi Account ready.
You should've created one when first setting up your phone, with your phone number and a password.
- If you have it: Double-check you have access to it by attempting to connect on Xiaomi's official website (Login page).
- If you don't: Create one with the Create an account button below the password form (same link as above), then connect to it.
Step 2
On your PC, go to Xiaomi's unlock page and click the colored Download Mi Unlock button.
{
"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"
}
Step 3
A download should start. Wait for it to finish, move the archive to your desktop and extract its content.
Step 4
Inside the extracted folder, double click the file called miflash_unlock.exe to start Xiaomi's Unlocking program.
Step 5
Read Xiaomi's Disclaimer then agree to their terms, or stop here and leave this thread if you don't.
Step 6
Sign in to your Mi Account we talked about in Step 1.
Step 7
Let's get your phone ready for unlocking.
Go to your phone's Settings > Mi Account and make sure you're logged in.
Now Settings > About Phone and tap the "MIUI Version" box multiple times until it says You are now a developer!
And finally Settings > Additional Settings > Developer Options
Enable the following settings inside Developer Options, and click Accept when warnings pop-up:
OEM Unlocking
USB Debugging
Still in Developer Options, check your Mi Unlock status and click the Add account and device button at the bottom if present.
Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 8
Alright, all backed up? Confident? Let's get going with the final steps.
Turn off your phone.
Turn it back on into fastboot mode by holding down the Power button AND Volume Down together until it vibrates, you may then let go of the Power Button, but keep Volume Down held until you see the fastboot image on your phone.
Connect your phone to your computer with the USB Cable.
Xiaomi's Software should detect it. If not, click on the cog-wheel in the top right, click the Check button to install the driver and follow instructions, then keep going.
Click Unlock, and follow the instructions!
Now there are two possible scenarios
Either you've done all this before and can have your phone unlocked right away.
Or this is the first time and at the end of the progress it'll ask you to wait ~7days, and, well, there's no way around that, so come back in 7 days and start from Step 8 again.
And there you go! Your phone will reboot and you can set it all up again, with the ability to follow the rooting tutorial below, and you can also install custom ROMs/recovery!
Spoiler: Rooting (Magisk)
Step 1
Download the latest Magisk .apk on your phone.
Go to the link above, click the latest (topmost) Magisk-vXX.X.apk you see in the list to start the download, open the file and install it.
Step 2
Go to the download page for the MIUI Official Rom for your region, make sure to get the fastboot version.
OR (if you don't want/can't download 3gb of ROM)
Follow DavitidzeSh's instructions on how to gather the boot.img and vbmeta.img files and SKIP to Step 5.
OR (if you're on a custom rom)
Look into your custom rom's .zip, find the boot.img and vbmeta.img files and SKIP to Step 5.
Step 3
Take the file you downloaded above, it should be a .tgz archive.
Extract it, you'll get a .tar achive.
Extract that one again.
Step 4
You should now have a folder similar to the one below
Go inside the images folder
Step 5
Grab the the vbmeta.img file and copy it to your ADB & Fastboot (Platform Tools) folder.
Grab the boot.img file and copy it to your phone's internal storage.
(where the Android, DCIM, Download, and more are present, just drop it in there)
Here's how it should look inside your phone's storage in the end.
Step 6
On your phone, open up Magisk Manager.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
Step 7
Link your phone to your PC, grab the file made by Magisk Manager.
It's located in your phone's downloads folder, called magisk_patched.img.
Copy and paste it where your ADB & Fastboot (Platform Tools) are located.
You should now have a folder structure like this:
adb.exe
fastboot.exe
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 8
Alright, we're ready to root!
Turn off your phone, then get in fastboot mode.
(Power + Volume Down, like the unlocking tutorial)
Step 9
Link your phone to your PC with the USB cable if not done already.
Step 10
Shift + Right click in an empty space inside the folder we prepared in Step 7,
And click Open PowerShell window here.
Inside the PowerShell window, input the following commands line by line, in order.
.\fastboot.exe devices
Click to expand...
Click to collapse
Make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 8 and try again.
.\fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
.\fastboot.exe flash boot .\magisk_patched.img
.\fastboot.exe reboot
Click to expand...
Click to collapse
Note: Your PowerShell window will look different, I'm using a different program, don't worry
Your phone will reboot.
Open up Magisk Manager, and double check that it's installed.
You're done!
That said, you will have issues with certain apps leaving it like this.
You should to hide the fact that your phone is rooted.
Check out the Passing SafetyNet tutorial further down below!
Spoiler: Getting EdXposed
I very much discourage to EdXposed your phone unless you have a very good reason for it.
It's a pain to pass SafetyNet.
It doesn't get updated often.
It has very niche use cases for which it's actually worth it.
That said, I explain it here for people who know what they're getting into and want instructions on how to do it.
This procedure requires to be rooted with Magisk.
Step 1
Inside Magisk Manager, go to the Modules tab.
Click the search button (bottom right) and search Riru.
Install the Riru module by Rikka.
Activate it and Reboot.
Step 2
Download and install the latest EdXposed Manager, the same way you did with Magisk Manager when rooting.
Step 3
Open it up, go to the ALPHA tab and click install/update.
It'll start a file download.
Step 4
Go back to Magisk Manager, Modules tab, except this time click Install from Storage.
Point to the .zip file you just got, located in the Downloads folder of your phone.
At the end of the installation, click reboot.
Step 5
Let's double check your installation is operational.
Go to EdXposed Manager, first tab.
It should say EdXposed Framework is active.
You're done!
You should now be able to install EdXposed modules.
That said, you will have issues with certain apps leaving it like this.
You should to hide the fact that your phone is EdXposed.
Check out the Passing SafetyNet tutorial further down below!
Spoiler: Passing SafetyNet (Magisk/EdXposed)
For Magisk Rooted Phones
Enable Magisk Hide inside Magisk Manager's settings.
You may also need to use the Props module to spoof your phone as another, if you want a tutorial on that, let me know.
For EdXposed Phones
Again, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services Framework
Reboot and enjoy! You're all set and SafetyNet should pass.
Spoiler: Installing GSI's (Non-device specific ROMs)
Step 1
Pick your poison in the Treble Forums!
My recommendations are in the Extras section of this post.
Step 2
Download the chosen ROM's A/B Arm64 version
It should be an .img.xz file
Extract it and you'll get an .img file.
You're almost ready to flash.
Make sure to backup your phone's data.
Continuing this tutorial will wipe your phone!
Step 3
Put your phone into fastboot mode.
(Power + Volume Down)
Connect it to your PC.
Step 4
Move the .img file you downloaded to your ADB & Fastboot (Platform Tools) folder.
Rename it to system.img
Step 5
Shift + Right click in an empty space inside the folder,
And click Open PowerShell window here.
Inside the PowerShell window, input the following commands line by line, in order.
.\fastboot.exe reboot fastboot
.\fastboot.exe --disable-verification flash vbmeta .\vbmeta.img
.\fastboot.exe flash system .\system.img
.\fastboot.exe -w
.\fastboot.exe reboot
Click to expand...
Click to collapse
Your phone will now reboot on its own.
Set it all up and enjoy!
That said, depending on how old the GSI you picked is, you MAY have issues leaving it at that.
Therefore, I highly recommend checking out the next tutorial section about Fixing GSI Issues.
Spoiler: Fixing brightness/jack on older GSI's
I have worked together with a developer to bring fixes for our device to every custom GSI rom out there.
The most recent GSI's shouldn't need the fixes listed below.
Older GSI (treble) roms have two known bugs that we can fix:
The brightness slider being misscalibrated, and therefore auto-brightness broken too.
The headphone jack not working.
You need to be rooted to do so.
Step 1 - Get yourself a Terminal Emulator, I recommend Termux
Step 2 - Type the following commands inside of it, line by line, in order:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
setprop persist.sys.overlay.devinputjack true
Click to expand...
Click to collapse
You're done! Brightness should be fine, headphones get detected, enjoy!
Spoiler: Resetting your phone
Backup all the data you might have on your phone to restore it after the manipulation!
Step 1
Download the fastboot ROM corresponding to your region here.
(The same one used to grab the boot.img and vbmeta.img when rooting)
And extract it.
Step 2
Download the latest MiFlashTool.
And extract it.
Step 3
Put your device in fastboot mode.
(Power + Vol Down, refer to the rooting tutorial for a more info)
And connect it to your computer via USB.
Step 4
Open MiFlashTool (XiaoMiFlash.exe), your device should appear in the list.
Step 5
Click the Select button in the top left,
And point to your fastboot ROM's folder
(The one containing the "AP", "BP", "BP_IN", "images" folders and a bunch of files)
Step 6
At the bottom right of the software, choose if you either want to just:
clean all
(wipe and re-install)
OR
clean all and lock
(wipe, reinstall and re-lock your bootloader)
Note: If you re-lock your bootloader but wish to unlock it again later, you won't have to wait the 7 days again.
Step 7
Finally, in the top right, click the flash button.
Now just wait a while, your phone will reboot on the stock rom and you're good to go!
Extras
Spoiler: Frequently Asked Questions (FAQ)
Q: Will unlocking my bootloader void my warranty?
A: No, it will not, it's easily reversable too, check the "Resetting your phone" tutorial.
Q: I rooted/EdXposed my phone and now Netflix won't even open, or doesn't work properly, what's up with that?
A: There's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.
Q: I tried unlocking my bootloader but, Mi Flash Unlock doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
Try another USB port.
Try another USB cable.
Install the Mi USB Drivers manually, they're included in the MiFlashUnlock folder.
Run the driver_install_64.exe, OR go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install.
In the Device Manager, check that the driver provider is Xiaomi.
If not, uninstall it and restart your computer.
RESERVED
Akitake said:
RESERVED
Click to expand...
Click to collapse
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
HemanthJabalpuri said:
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
Click to expand...
Click to collapse
1.Flashing official firmware is universal method for all devices through fastboot, And for recovery, we can't flash it yet since TWRP doesn't support dynamic partition yet.
2.No, you don't need the same firmware.
3.If you interrupt the process in between, the device would remain in fastboot Mode, and you can still restart the process.
Yxnq_Param said:
1.Flashing official firmware is universal method for all devices through fastboot, And for recovery, we can't flash it yet since TWRP doesn't support dynamic partition yet.
2.No, you don't need the same firmware.
3.If you interrupt the process in between, the device would remain in fastboot Mode, and you can still restart the process.
Click to expand...
Click to collapse
I heard a term called "Anti Roll Back" from https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
Are all our merlin ROMs have same version of anti roll back. That is are we able to flash MIUI 11 on MIUI 12?
Thanks
HemanthJabalpuri said:
I heard a term called "Anti Roll Back" from https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
Are all our merlin ROMs have same version of anti roll back. That is are we able to flash MIUI 11 on MIUI 12?
Thanks
Click to expand...
Click to collapse
Anti-rollback is only an issue if you're trying to downgrade through the stock recovery (Vol + Up) or through MIUI's recovery (About Phone > MIUI Version > Three dots and there is an option there)
If you want to go back to MIUI 11 for some reason, you can, by flashing it through fastboot.
HemanthJabalpuri said:
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
Click to expand...
Click to collapse
1 - Google, this isn't Merlin specific.
2 - No, you can go back directly to the latest MIUI for your device.
3 - Just start over, your device will remain in fastboot, it's actually really safe.
4 - That's a niche demand, 99% of people use Windows and, if you use something else it's on you. If you're a Linux user, you're used googling information and it's not a problem. And for mac, well, worst case scenario use someone else's pc for 10 minutes.
5 - To prevent boot-loops. If you don't flash vbmeta, it won't boot.
6 - Read disclaimers, the tutorial literally tells you to take the vbmeta from the official rom. There's no such thing as a modified vbmeta, what matters is how we flash it with fastboot, disabling verifications.
Also this is my first post, and I'll add more as time goes on. But even as it is, I think it's miles better than what people care to create for most devices on XDA. It's also pretty detailed with images and such to reassure the user.
can someone help me?
So I wanted to unlock the bootloader
Did the
Turnn on OEM unlocking
Turn on USB debugging
Added my device on my account (the other thing to do in developer setting)
Boot into fastboot
The Mi unlock can't detect my device although the drivers are fine (I checked it in device manager) and I run it in administrator check the driver again in the software it says it is installed.
What can I do? Did I missed some steps?
markevan12 said:
can someone help me?
So I wanted to unlock the bootloader
Did the
Turnn on OEM unlocking
Turn on USB debugging
Added my device on my account (the other thing to do in developer setting)
Boot into fastboot
The Mi unlock can't detect my device although the drivers are fine (I checked it in device manager) and I run it in administrator check the driver again in the software it says it is installed.
What can I do? Did I missed some steps?
Click to expand...
Click to collapse
Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Mi USB Drivers manually (included in the MiFlashUnlock folder, run the driver_install_64.exe, or go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install)
- In the Device Manager, check that the driver provider is Xiaomi. If not, uninstall it and restart your computer.
hi sir , can you tell the gsi rom install tutorial if we installed it from twrp?
fachrizoyy said:
hi sir , can you tell the gsi rom install tutorial if we installed it from twrp?
Click to expand...
Click to collapse
I will not support custom recovery's. I highly dislike them, and they're unofficial for Merlin as well.
Thx for the answer
Akitake said:
Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Mi USB Drivers manually (included in the MiFlashUnlock folder, run the driver_install_64.exe, or go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install)
- In the Device Manager, check that the driver provider is Xiaomi. If not, uninstall it and restart your computer.
Click to expand...
Click to collapse
thanks but I solved it by moving the unlock folder to C:
Hey man. First of all I appreciate that you spent this much time for redmi note 9 users. I just want to know that how do I know that my device is merlin?
mirzanuman6612 said:
Hey man. First of all I appreciate that you spent this much time for redmi note 9 users. I just want to know that how do I know that my device is merlin?
Click to expand...
Click to collapse
Hey, no problem!
Well, Merlin is just the codename for Redmi Note 9. So if you have a Redmi Note 9, you have a merlin.
BUT, keep in mind the Redmi Note 9 Pro, Pro Max and S are different and have their own section in the forums.
Akitake said:
Hey, no problem!
Well, Merlin is just the codename for Redmi Note 9. So if you have a Redmi Note 9, you have a merlin.
BUT, keep in mind the Redmi Note 9 Pro, Pro Max and S are different and have their own section in the forums.
Click to expand...
Click to collapse
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
mirzanuman6612 said:
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
Click to expand...
Click to collapse
Yes I could, I will actually add a section to the FAQ soon for better driver installation, it's a driver issue.
Akitake said:
Yes I could, I will actually add a section to the FAQ soon for better driver installation, it's a driver issue.
Click to expand...
Click to collapse
Alrighty, thanks for your replies.
mirzanuman6612 said:
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
Click to expand...
Click to collapse
Had you tried moving the unlock folder to c:/ ?
markevan12 said:
Had you tried moving the unlock folder to c:/ ?
Click to expand...
Click to collapse
I appreciate you replying to me. But, I already fixed it by installing windows 7 I had windows 10 before and it didn't seem to work on it so I installed windows 7 and it worked flawlessly. Btw, are you a user that has installed a custom rom? And if yes, then which one and is the performance any better?
Thanks.
mirzanuman6612 said:
I appreciate you replying to me. But, I already fixed it by installing windows 7 I had windows 10 before and it didn't seem to work on it so I installed windows 7 and it worked flawlessly. Btw, are you a user that has installed a custom rom? And if yes, then which one and is the performance any better?
Thanks.
Click to expand...
Click to collapse
Nope I didn't YET, I'm still waiting for the unlock to complete. I did tried treble roms in my other device. It just is basically have the same performance (LOSQ) but I had heating problems in my Samsung device, I expect a normal experience with this ROMs.
Hi guys I know their are threads how to do this but they are all over the place, If you'd like a complete tutorial, that will get your 2020 MOTO G Stylus phone rooted without any errors let me know.
Edit: It looks like people are interested so here goes. The tutorial below is for the 2020 version I tested on Android 10 on two variants. This method once followed correctly will take no more than 30 min tops. Not sure if this will work on updated versions but you could try at your own risk. If this helped you leave a like, if you have any questions let me know.
prerequisites:
PC (duh lol)
Fully Charged Device
Motorola Account (for bootloader unlock purposes)
adb fastboot installed (take note of your folder location especially the platform-tools folder
motorola drivers (link in step 5 if drivers don't install correctly after connecting phone)
Tutorial:
Unlocking bootloader
1. first step is to unlock bootloader(all data will be erased) for this you will need your unlock key
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.
Rooting
1. with bootloader unlocked time to get root. download the latest magisk manager (23 I believe) let it install and power off your phone we will use it later. We will be getting the specific boot image for your device through temporary twrp.
2. go to https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-0.4155041/ and download TWRP credits to @vache. Place the file in your platform-tools folder.
3. enter fastboot mode (by now it should be second nature) and plug into pc, verify fastboot device connected, by opening command window again in platform-tools folder
4. once verified type the following command without the quotes "fastboot boot twrp-3.5.0-0-rav-sofia.img" be patient, when it boots into twrp, cancel any password creation.
5. go to backup and select storage, choose a sd card, do not decrypt or do anything besides what I'm saying here. it will take you back to the beginning after sd card selected as storage, click backup and select only boot at the very top and creat backup. once done go out to twrp main menu and hit reboot, select "reboot system"
6. now to patch boot, open magisk manager and go to install, it will then give you the option to locate and patch boot.img, however we will be going into twrp backup on your sd card and locate boot.emmc.win (not the other two) once selected hit lets go on Magisk and allow it to patch. your patched boot.img will be in a download folder on your internal memory. Copy that file to your computer and then again move it to platform-tools folder
7. power off device and enter fastboot mode for the final time connect to pc, open command window in platform-tools folder and type the following command without the quotes "fastboot flash boot nameofbootfile.img" hit enter and allow to flash, once completed type "fastboot reboot" your device should now reboot, don't worry if it takes slightly longer than usual.
8. finally go into the magisk manager and let it complete its setup, it should reboot one more time and boom, you have root, remember to use magisk hide, That's it all set. If followed correctly this should only take about 30 min to a hour.
Shucks! I thought this was a tutorial.
zapjb said:
Shucks! I thought this was a tutorial.
Click to expand...
Click to collapse
I got you, updated tutorial up. Let me know if it helps.
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm pretty sure a factory reset would restore to 11 not 10. As the 11 update replaced the 10 OS altogether.
Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.
kgalv419 said:
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.
Click to expand...
Click to collapse
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11
kgalv419 said:
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11
Click to expand...
Click to collapse
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.
For downgrading to android 10:
1. Grab the moto flash tool from here
2. Grab the a10 firmware from your device here
3. Unzip the moto flash tool and put the firmware zip in the folder called firmware
4. Plug your device in to your pc in bootloader mode
5. Start the moto flash tool and follow the instructions
(Unlocked bootloader required)
EpicSaga said:
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.
Click to expand...
Click to collapse
Pretty sure theres a setting in developer options to turn off automatic updates.
ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).
EpicSaga said:
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).
Click to expand...
Click to collapse
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.
ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
I already turned it off, but I still got the notification for the update.
ph4n70m-404 said:
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.
Click to expand...
Click to collapse
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
EpicSaga said:
I already turned it off, but I still got the notification for the update.
Click to expand...
Click to collapse
I got a notification again today saying that it will update today if It don't do it manually.
EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
Assuming you have a non Verizon or any other oem that blocks unlocking the bootloader follow the steps from the original post:
(step one makes no sense they wrote it kinda weird)
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.
EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
you can install magisk manager with bootloader locked but there is no sense in installing it on locked bootloader, because when you unlock your bootloader your devices will be factory reset, if you checked my instructions you will see that magisk manager is needed to patch boot.img that you will get from TWRP backup. You seem a bit green about the whole fastboot process, if that's the case I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.
kgalv419 said:
...I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.
Click to expand...
Click to collapse
Sometimes it's been a couple years between me rooting phones. When I come back to root another phone I read & read & read & read some more here. And I have in case the shtf a back up phone to be safe.
EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Re: bootlock unlock code email
I went on the Lenovo/Motorola website just yesterday and input the long 5-line code from my phone (required) from SDK platform. Once I did this, the website replied that I will receive email with a unique 20-character bootloader unlock code (this is the part you should check again). Instead of getting a code, the email asked that I first "verify my email", so I followed the directions, clicked the link, the link brought me to their website and I was able to verify my account. Once that happened, the page just kinda froze. So I repeated the process and when I clicked the "verify email" button, it brought me again to the website but thus time to my profile page. There was no Bootloader Unlock Code, nor was I emailed the code as assured as I was, as per their website suggests. I repeated the process a 3rd time but the same thing happened. And when I tried to went back #2 + #3 times, I input all the information again, clicked on the "send email" link (where they email you the 20-character code) I never received any additional emails. I only received 1 email (the first time I input this into their website). So, the site will only work 1 time per unique phone (serial). I called customer support and got nowhere! I have Metro by T-Mobile Motorola Moto G Stylus XT2043-4. I hope you see this and please let me know if you are able to unlock or get a email code as promised (or not). And if you have any information on how else to solve this issue, please let me know. I hope this helps & my apologies for being a bearer of bad news. If I solve this issue, I will respond back.
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.