Database Info

ROOT MiA1 without TWRP

Hi guys, i was looking to make twrp for this device but couldn't do it because lack of knowledge. so i searched and found about CF-Auto-Root.
fortunately i was able to generate one for mia1. now we can root this device without any recovery.
Requirements -
1. unlocked boot loader. :cyclops:
2. this Zip
3.adb debugging should be enabled
How to -
1. put your phone in fastboot mode by volume down + power key.
2. connect to pc, ( make sure adb debugging is enabled)
2. extract above zip anywhere in your desktop and run root.bat file.
wait for some time, when it boots up you should have root access . although you won't see any su app. tried with solid explorer and was able to edit build.prop. without any issues. enjoy

so with this we get root access, a question about unlocked bootloader, does A1 already unlocked bootloader since begining or we have to request it from Xiaomi or Google to get that?
hope with this we can use substratum on stock Android

card-us said:
so with this we get root access, a question about unlocked bootloader, does A1 already unlocked bootloader since begining or we have to request it from Xiaomi or Google to get that?
hope with this we can use substratum on stock Android
Click to expand...
Click to collapse
No, it doesn't come unlocked, but you can unlock by either ---
1. requesting xiaomi for unlock code.
or
2. By using command " fastboot oem unlock" in fastboot mode.
i used 2nd method to unlock, it's just like unlocking a nexus phone.

Screenshot proof please Kratus
Can u upload or attach few screenshots of the root access working... Root checker or anything

Screenshots?

Well done!
Were you able to install any root apps SuperSU or Magisk? Post some screen shots if you can

See the proff guys...

Thanks
ravinder0003 said:
See the proff guys...
Click to expand...
Click to collapse
Were you able to install Magisk? BTW did you lose all data when you unlocked the bootloader?

Ex-Hunter said:
Were you able to install Magisk? BTW did you lose all data when you unlocked the bootloader?
Click to expand...
Click to collapse
Nothing to worry about... Xiaomi doesn't wipe data while unlocking...
Just extract the zip... Get the boot.img and flash it using fastboot...
If you are too lazy then run root.bat

Awesome News... Trying it.. i just want to enable nav bar

kraatus90 said:
Hi guys, i was looking to make twrp for this device but couldn't do it because lack of knowledge. so i searched and found about CF-Auto-Root.
fortunately i was able to generate one for mia1. now we can root this device without any recovery.
Requirements -
1. unlocked boot loader. :cyclops:
2. this Zip
3.adb debugging should be enabled
How to -
1. put your phone in fastboot mode by volume down + power key.
2. connect to pc, ( make sure adb debugging is enabled)
2. extract above zip anywhere in your desktop and run root.bat file.
wait for some time, when it boots up you should have root access . although you won't see any su app. tried with solid explorer and was able to edit build.prop. without any issues. enjoy
Click to expand...
Click to collapse
Oh my gosh! I can thank you forever!

any option to remove the unlocked bootloader screen/logo?

ravinder0003 said:
Nothing to worry about... Xiaomi doesn't wipe data while unlocking...
Just extract the zip... Get the boot.img and flash it using fastboot...
If you are too lazy then run root.bat
Click to expand...
Click to collapse
I should have read this sooner. I run root.bat twice.. it did not work.. my partner had to take the laptop to school since it's needed for teaching.. now i'm left with nothing.. unrooted, frustrated, aggreviated.. i should have flashed it manually.. i'm wanna cry. ????

@ravinder0003 Thanks. it working using root.bat. flashboot boot boot.img didn't seem to work for me. Any ideas? Did you get Magisk working?

Hey , can't we get separate device thread for MiA1 ?

THANK YOU Developers... U guys rock!!!!

melmarPH said:
I should have read this sooner. I run root.bat twice.. it did not work.. my partner had to take the laptop to school since it's needed for teaching.. now i'm left with nothing.. unrooted, frustrated, aggreviated.. i should have flashed it manually.. i'm wanna cry.
Click to expand...
Click to collapse
It should work. You must have missed something. Did you have the right driver installed?

fastboot flash boot failed and root.bat suceeded but my phone does not get rooted checked by root checker.

Hakim Farouk said:
It should work. You must have missed something. Did you have the right driver installed?
Click to expand...
Click to collapse
I know I have to right driver installed.. I have been flashing with fastboot since Redmi Note 3 Pro.. root.bat runs properly.. I did it twice but for some reason, I'm not getting root..
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
Desire 1007 said:
fastboot flash boot failed and root.bat suceeded but my phone does not get rooted checked by root checker.
Click to expand...
Click to collapse
Same here.. though I haven't tried manually flashing boot.img..

Didn't work for me!
Super SU failed!
Es explorer failed!

[ROOT][TRIAL][MAGISK] P20 Pro - Try out on Rooting Method

Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.

That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.

Fingers crossed twrp is possible soon

Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well

Would this method work on CLT-L09 model? Thanks

danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does

This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse

fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address

Great, thanks for that! I managed to find it on allrom.ir

Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post

danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?

otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks

danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?

otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?

danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well

otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!

danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command

otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.

[ROOT] [MAGISK] (Without Recovery) Root your device with MAGISK Without Recovery

Hello Everyone,
This is my first tutorial here.
So, any mistakes should be reminded in the thread.
==================================================
Guide for rooting with MAGISK​==================================================
This guide is for those devices for which currently there is no custom recovery available. So, don't be sad instead have MAGISK Root for your device and and sleep well.:angel:
Note - USE THIS GUIDE ON YOUR OWN. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICES.
BETTER KNOW WHAT YOU ARE DOING AND ITS CONSEQUENCES.
==================================================
REQUIREMENTS -
1 - An Android 5.0+ device
2 - PC with working ADB
3 - Stock boot image (boot.img) of your device
4 - Magisk Manager app
5 - A good file browser like Mixplorer, Solid explorer etc..
6 - Active Internet connection
7 - Active mind and patience.
==================================================
Step 1: Patching the stock boot.img
- Install MagiskManager apk on your android device
- Copy the stock boot.img of your device to your phone's internal storage or SD card
- Launch Magisk Manager app
- If prompted to install Magisk, select NO THANKS
- If you are using a samsung device and wish to flash using Odin, then select Options > Settings > Update Settings > Patched Boot Output Format > img.tar )
- Select Install > Install > Patch Boot Image File >
Navigate to the location of the stock boot.img you copied earlier on, then Select it
-Magisk Manager should begin downloading the magisk zip file used for patching
-Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img[.tar]
Step 2: Flashing the patched boot.img
You have a variety of options to flash the patched boot.img depending on your chipset (e.g Mediatek MTK, Spreadtrum SPD, Qualcomm QLM etc ), the resources you have and your skills. Note that some flashing methods might require you to rename the file to boot.img
- For those using MTK devices and have the specific scatter file for their device, you can flash the patched boot.img using SP flash tool or Miracle Box
-For those using SPD devices and have the PAC file for their device, you can flash the patched boot.img using Research download tool by replacing the stock boot.img with your patched boot.img
- For those using Samsung devices and then use ODIN to flash.
-You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
-Setup adb and fastboot on your PC.
-Unlock the phone's Bootloader (if its not unlocked)
-Re-enable USB debugging on the phone
-Connect the phone to the PC via USB cord
-Boot into fastboot mode.
-Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
-Verify root using Root Checker
Credits goes to topjohnwu of XDA for Magisk
Also to X3non of Hovatek for original guide.

Does this work with lenovo vibe k4 note?

I think this thing would be risky to do.
Or what do you think?

Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs

2FrEsH99 said:
Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs
Click to expand...
Click to collapse
if the bootloader checks boot.img, it will fail since Magisk patches the boot.img and it will have an invalid signature.
This process is only useful for locked bootloaders that do not check boot.img or people who want stock or are stuck with stock recovery.

2FrEsH99 said:
Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs
Click to expand...
Click to collapse
Hi, the best way is to flash a custom recovery beforehand. But if you can't find you can go for this method but bootloader must be UNLOCKED. And also if anything goes wrong even if the bootloader is UNLOCKED , the phone will only be soft brick not hard brick. But the best thing will be a custom recovery method.

Cjoman said:
Does this work with lenovo vibe k4 note?
Click to expand...
Click to collapse
If your device bootloader is UNLOCKED, then you are good to go. But you should look for a custom recovery for your device and flash magisk.zip . Try this method only if you can't find one. Although every method is risky, you should play safe.

DE SEXIEST said:
I think this thing would be risky to do.
Or what do you think?
Click to expand...
Click to collapse
Of course this method is risky yet safe.
If you have a less secure device with UNLOCKED bootloader, you should try this.
But the best thing will be to find a custom recovery or try to port one.
This method should work on most devices.

Aquib132 said:
If your device bootloader is UNLOCKED, then you are good to go. But you should look for a custom recovery for your device and flash magisk.zip . Try this method only if you can't find one. Although every method is risky, you should play safe.
Click to expand...
Click to collapse
Okay thanks!
---------- Post added at 02:33 AM ---------- Previous post was at 02:03 AM ----------
Will this factory reset my phone?

does it work / may work with S9 plus G965U Qualcomm chipset?
as i didn't find any Oem unlock option in the developer menu.

A7 2017 (Android 8)
So i have an a7 2017 with android oreo or know as 8.0.0. So i want to flash the patched boot image with odin. How do i do that? Like i understand you need oem unlocked but where do you flash it specifically in odin?

Use ADB and the push command.. Be careful what you type.. This thing is a ***** to get the first time.. I wish you good luck
---------- Post added at 07:16 AM ---------- Previous post was at 07:10 AM ----------
Remember one other thing.. Sammy can not use Fastboot.. It's not that it's bad.. But it just won't in most cases.. Try CROM first to unlock the bootloader

Thanks, very helpful!

Well i tried to root my phone before with cf auto root and with twrp and it said device verification has failed or something. Will it happen for this device?

How do i copy the stock boot image onto my internal storage?

I'm having a question: does the new patched_boot.img file also contain my personal data? If not, then what's the best way to make a backup so that when I restore it my phone to be just like I didn't do anything to it(it should have all my apps, files,contacts, accounts etc untouched), but to be rooted? I have a Elephone a4 and I can't set up a custom recovery, that's why I want to follow this tutorial...

Pcarioca said:
I'm having a question: does the new patched_boot.img file also contain my personal data? If not, then what's the best way to make a backup so that when I restore it my phone to be just like I didn't do anything to it(it should have all my apps, files,contacts, accounts etc untouched), but to be rooted? I have a Elephone a4 and I can't set up a custom recovery, that's why I want to follow this tutorial...
Click to expand...
Click to collapse
Go to smart switch and create a backup.

Easy peezy
Works as advertised. One thing i would add to the guide is copying the patch boot img to where the command prompt window is opened. If i was using my noodle, it would be an unspoken, but i forgot and had to reboot once more. This would've saved me about 30 seconds, but i won't complain. I am on the moto z2 force sprint may 1 update with an unlocked bootloader

I think this thing would be risky to do.

emod0705 said:
Try CROM first to unlock the bootloader
Click to expand...
Click to collapse
Sir what is CROM?

How To Root Oxygen 5.1.7

Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago

Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.

iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!

Edit: Screenshots

Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol

joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then

joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.

i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol

So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?

joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick

dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always

Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?

dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade

joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me

Yup that's it

joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?

BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes

joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?

Maybe someone will upload the full rom?

anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?

Question Has anyone successfully changed tmobile to internation yet?

using OnePlus 9 5g from tmobile and looking to convert to internation.anyone had any issues or tips to make sure I don't mess up?

So I come from the OnePlus 9 Pro forum, but the tips are identical because pretty much the same phone except for a few differences.
1. DO NOT FLASH BOOTLOADER
I can't stress this enough, flashing the bootloader will render the MSM tool that OnePlus provides for you USELESS! I figured this out the hard way!
2. Make a full device backup, if you're rooted already use Partitions backup and restore available on the Play Store
3. Keep OEM UNLOCKING ON THE WHOLE TIME! Don't turn it off until and unless you return to complete stock using a MSM tool! Also, keep your bootloader unlocked please.
4. Don't trust random "conversion" folders that flash everything at once without looking at the files, ESPECIALLY not without looking at the .bat file(s) such as a flashall.bat.

Sounds too risky. It's not so simple anymore .

Can I ask a clarifying question @razercortex ? You're saying to not flash the bootloader; does that mean I could simply take the boot.img, do the magisk thing to it, and at least have root? I don't wanna brick my T-Mobile variant here, but I really want to have root.

You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img

What if I don't want root, just international version

I am interested to switch from T-Mobile variant to international as well.

Josh McGrath said:
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
Click to expand...
Click to collapse
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.

inspron said:
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
Click to expand...
Click to collapse
Do you have magiskhide enabled?

inspron said:
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
Click to expand...
Click to collapse
Im showing to be passing. There was a magisk issue a week ago or so that cause it to fail but it was updated.
Playstore shows "Device is certified"

I really want international myself. This battery is complete garbage and tmo likes to drag their feet on an update the international got to fix the battery issue weeks ago

jfsat said:
Can I ask a clarifying question @razercortex ? You're saying to not flash the bootloader; does that mean I could simply take the boot.img, do the magisk thing to it, and at least have root? I don't wanna brick my T-Mobile variant here, but I really want to have root.
Click to expand...
Click to collapse
@jfsat If you just want root, patching the boot.img with magisk should be good enough. Just don't forget to keep OEM unlocking checked and keep the unlock code just in case. Also, don't relock until you have flashed stock boot.img.

Josh McGrath said:
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
Click to expand...
Click to collapse
It literally does not matter, but I would recommend flashing the boot.img instead because I don't know what the Direct Install method does to your phone's firmware. Flashing the boot.img works great, it only touches your boot partition and if you have the stock boot you can just flash it back and relock it, no problem. Direct Install could potentially change something else though it looks like it could be fine, but YMMV.

inspron said:
I am interested to switch from T-Mobile variant to international as well.
Click to expand...
Click to collapse
I know how to do it, you need to extract payload.bin from the EU OTA and flash all the partitions, find a tutorial online. Just make sure to make a full backup using Partitions backup and restore on the play store or manually dump partitions from your phone. You don't need userdata, it's too big and probably incompatible with the region change, just a side note that flashing partitions in the super partition (system, vendor, product, system_ext, odm, etc.) requires you to be in fastbootd, so use fastboot reboot fastboot to do so. Other than that, make sure there's an MSM tool available, you can check with OnePlus support.