Related
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Thanks so much! Will try this out! Nice work!
Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Please report back your success and how it goes for you!
SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP
Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out
I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532
Tested and 100% working! Recommended
smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?
PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.
Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode
It's normal that the patched boot.img is smaller.
PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing
Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.
where can i find the pre patched boot img of 10.0.12.0?
Just use the one for 10.0.11.0.
nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA
I had trouble finding this information, and since we have no working TWRP yet, here is a way to get low-level access to al lot of files.
Full credits go to: @s3axel, Source
So you flashed a module that is now causing a bootloop?
Follow these steps:
0. check if you can boot using stock boot.img, if that does not work, then you have a bigger problem then I had and this guide may not work for you.
1. Get the stock recovery.img by extracting it from the same OTA file as your current build, using payload_dumper
2. Follow s3axel's guide to get adb to work in recovery mode (after you unlock the drive)
s3axel said:
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Click to expand...
Click to collapse
3. rename the image_new.img to unsecure_adb_recovery.img
4. flash usecure recovery
Code:
fastboot flash recovery unsecure_adb_recovery.img
5. get into the adb shell
Code:
adb shell
then find the magisk module folder
Code:
cd /data/adb/modules
6. remove the module
Code:
rm -rf name_of_module
7. exit shell
8. reboot back to fastboot (See notes below)
9. flash stock recovery
Code:
fastboot flash recovery recovery.img
10. boot patched boot image to try if magisk worked
Code:
fastboot boot patched_magisk.img
Hopefully, if it boots again with root and Magisk
This worked very well and was very easy to do.
11. Use Magisk apk to install magisk to boot img. Or flash your patched magisk.
Notes:
DO NOT try adb reboot fastboot, I was hoping this would work (I was tired, ok...)
I got stuck in a bootloop (it kept asking me to unlock my device)
to break out of this loop, I used the forced off method: hold power + volume up & down until screen blacks out
From power off to bootloader:
press & hold volume down and power
and hold down until you get back to recovery, reboot to fastboot then flash stock recovery back to secure your ADB and return to as much stock as possible :good:
Here is my patched prop.default
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
grandpajiver said:
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Click to expand...
Click to collapse
The Recovery.img is from stock, so not a per-device thing.
I was just too lazy to find a place to upload large files.
I am currently on 10.0.4 but with 10.0.5 showing up, it would need updating later on.
I am not sure if you can flashboot boot recovery, certainly worth a try? Not sure how all this works, so I just flashed recovery and then flashed stock after I was done.
I also tested the TWRP build by not flashing it but booting it directly, but that was not very productive given it's current state.
hafiz.hasan said:
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
Click to expand...
Click to collapse
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
If only I didn't have tons of crap at work. This may be the gateway to v4a.
I have the images but not the extractor. Hmmmmm.
FreezyExp said:
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
Click to expand...
Click to collapse
Nice.. So are you gonna help building core only boot img for our device.?
hafiz.hasan said:
Nice.. So are you gonna help building core only boot img for our device.?
Click to expand...
Click to collapse
Nope sorry, not at this time.
There is a pull request on the magisk github that allows us to build Core-Only, so I will be waiting for that.
This guide contains the information that solved my immediate issue with not being in possesion of core-only.
Without having to deal with a lot of unknowns, just download some tools, extract some files, edit a few lines then patch it back up.
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
grandpajiver said:
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
Click to expand...
Click to collapse
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
This isn't fun to work on through a locked down Windows 10 pc. gonna try again on my chromebook after I get the 1.0.0.6 build.
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
grandpajiver said:
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
Click to expand...
Click to collapse
I got updated to 1.0.0.6.. I went from the '0' version to 'I'. Shrug.
fastboot boot recovery.img nor fastboot boot recovery recovery.img works... sigh.
I do have the full OTA. OnePlus7TOxygen_14.I.08_OTA_008_all_1911061912_10a180d3.zip. Dunno if anyone needs it.
I am on Linux. I used mktool to unpack and repack. I set all the flags properly between entered fastboot and Flash the new image to recovery as specified. device immediately hangs. I hold the keys to enter fastboot mode again and of course I can't run shell as ADB is not available in fastboot.
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
morback said:
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
Click to expand...
Click to collapse
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
morback said:
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
Click to expand...
Click to collapse
I have not fiddled around with fastboot ROMs. But you should be able to download your OOS rom with Oxygen Updater.
If someone else haven't uploaded the stock recovery, you'll need to use a tool like this to extract the payload bin inside the zip. The recovery is named recovery.img
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.
This will delete all the data from the phone + bootloader needs to be unlocked?
Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!
Will this work for 10.0.13 tmobile ? Thanks
gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.
Hello fellow XDA'ers
I have waited and unlocked the phone, running the MIUI 12.5.1.0 (RKHEUXM) the EU Official Rom that came with the phone, and was following the guide on how to root from NaldoTech, but i'm stuck, magisk can't patch any Firmware file i throw at it...
Don't know what i am doing wrong, i opened the zip files manually looking for the boot.img file but i cant seem to find it in any of the Firmwares i download from XiaomiFirmwareUpdater.
Also tried downloading the rom file and extracting the contents using the xiaomi-flashable-firmware-creator, but no luck with that either, throws some permission error at extracting the payload.bin
what can i do from here??
thanks in advance
Easy peasy
Steps
Download Adb and fastboot tool.
Or just download TWRP image and start CMD from there "the folder containing the twrp img" (in destination bar type cmd and press Enter) /the drivers should be installed and working properly ofc.
1- set phone in fastboot mode then plug it in to PC
2- Type: fastboot boot twrp.img (twrp here is the img file)
Then the phone will boot into twrp.
The phone will be shown in PC. Paste Magisk in the phone. Then go back and flash it using TWRP. Then reboot to system. And you're all done.
laid1995 said:
.
Click to expand...
Click to collapse
doesnt boot to twrp just turns off :S
Fyat said:
doesnt boot to twrp just turns off :S
Click to expand...
Click to collapse
You're doing something wrong then.
Check all drivers are set up properly. Try flashing twrp then boot to it using Volume UP + Power button.
Make sure you download Nebrassy's twrp 3.5.10
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Fyat said:
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Click to expand...
Click to collapse
Whatever was your way, I'm glad you managed to do it
sir i need boot.img file for poco f3
ZAki6464 said:
sir i need boot.img file for poco f3
Click to expand...
Click to collapse
Good
Which version do you need?
Is this international version I should get to use in USA on T-Mobile to root the same way as you?
Amazon F3
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Fyat said:
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Click to expand...
Click to collapse
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Greenspoof said:
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Click to expand...
Click to collapse
I'm not sure where to find these options as i do not use the turbo mode, can you point to it?
Can anyone confirm if we would be able to easily root Xiaomi 13 pro?
I want to buy the phone only if it is possible to root this phone.
droidkoder said:
Can anyone confirm if we would be able to easily root Xiaomi 13 pro?
I want to buy the phone only if it is possible to root this phone.
Click to expand...
Click to collapse
Yep,possible but only with V14.0.4.0.TMBCNXM/V14.0.8.0.TMBCNXM ,for the moment
NOSS8 said:
Yep,possible but only with V14.0.4.0.TMBCNXM/V14.0.8.0.TMBCNXM ,for the moment
Click to expand...
Click to collapse
Hi, do you have a tutorial on how to root this device? I have tried using Magisk but it does not work at all. The patched boot.img flashes successfully but nothing happens after reboot. Nothing is installed at all and the system is exactly the same as before. My bootloader is unlocked. Booting directly using the patched boot.img does nothing as well. It is as if nothing has been flashed at all.
Edit: I found a solution. You have to use init_boot.img instead of boot.img.
VincentThacker said:
Hi, do you have a tutorial on how to root this device? I have tried using Magisk but it does not work at all. The patched boot.img flashes successfully but nothing happens after reboot. Nothing is installed at all and the system is exactly the same as before. My bootloader is unlocked. Booting directly using the patched boot.img does nothing as well. It is as if nothing has been flashed at all.
Edit: I found a solution. You have to use init_boot.img instead of boot.img.
Click to expand...
Click to collapse
And is Magisk usable, zygisk, modules etc...?
NOSS8 said:
And is Magisk usable, zygisk, modules etc...?
Click to expand...
Click to collapse
Yeah, I've managed to get it working on 14.0.10.0.TMBCNXM. The only module I've tested is Universal SafetyNet Fix which is working. Google Play showing certified. Updating can be done without a PC as well. I first installed on 14.0.8.0, then installed 14.0.10.0 from the device updater itself. Before rebooting, simply go to Magisk and select the option to install to inactive slot. Reboot and you have Magisk working on the new version.
VincentThacker said:
Yeah, I've managed to get it working on 14.0.10.0.TMBCNXM. The only module I've tested is Universal SafetyNet Fix which is working. Google Play showing certified. Updating can be done without a PC as well. I first installed on 14.0.8.0, then installed 14.0.10.0 from the device updater itself. Before rebooting, simply go to Magisk and select the option to install to inactive slot. Reboot and you have Magisk working on the new version.
Click to expand...
Click to collapse
Bro can write a guide how to root? I try follow this method, but failed. https://forum.xda-developers.com/t/...urself-and-optionnal-debloat-privacy.4337693/
Cuz i have a m3 pro. I thinking should be same. But seems like its not
darrenlimch said:
Bro can write a guide how to root? I try follow this method, but failed. https://forum.xda-developers.com/t/...urself-and-optionnal-debloat-privacy.4337693/
Cuz i have a m3 pro. I thinking should be same. But seems like its not
Click to expand...
Click to collapse
Nope,this not the same method.
https://forum.xda-developers.com/t/root-gained.4290689/
VincentThacker said:
Hi, do you have a tutorial on how to root this device? I have tried using Magisk but it does not work at all. The patched boot.img flashes successfully but nothing happens after reboot. Nothing is installed at all and the system is exactly the same as before. My bootloader is unlocked. Booting directly using the patched boot.img does nothing as well. It is as if nothing has been flashed at all.
Edit: I found a solution. You have to use init_boot.img instead of boot.img.
Click to expand...
Click to collapse
Cuz you mention here use init_boot.img, i try use magisk patch the init_boot.img and flash it via adb, but then bootloop into fastboot. Mind write a tutorial for us? As i believe you are the first to root succesfully. Thanks in advance bro.
NOSS8 said:
Nope,this not the same method.
https://forum.xda-developers.com/t/root-gained.4290689/
Click to expand...
Click to collapse
Misunderstood bro. I have a mi 13pro as well. China version. Need to root it. Im just saying that i have another poco m3 pro. I though they use same method
darrenlimch said:
Misunderstood bro. I have a mi 13pro as well. China version. Need to root it. Im just saying that i have another poco m3 pro. I though they use same method
Click to expand...
Click to collapse
Understood,You have to use init_boot.img instead of boot.img.
Common tutorial
1. Find or redownload the TGZ file for your current ROM or other rom.
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
NOSS8 said:
Understood,You have to use init_boot.img instead of boot.img.
Common tutorial
1. Find or redownload the TGZ file for your current ROM or other rom.
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Click to expand...
Click to collapse
Tried this method. But like VincentThacker mentioned at first. After flash that modded.img, nothing was change. So might need his help already. No idea which init_boot.img is mentioning.
darrenlimch said:
Tried this method. But like VincentThacker mentioned at first. After flash that modded.img, nothing was change. So might need his help already. No idea which init_boot.img is mentioning.
Click to expand...
Click to collapse
I guess it is in the Fastboot rom or a command and root for what no rom or twrp currently available.
If it is to delete apps there are many tools or with ADB commands.
NOSS8 said:
I guess it is in the Fastboot rom or a command and root for what no rom or twrp currently available.
If it is to delete apps there are many tools or with ADB commands.
Click to expand...
Click to collapse
I need android auto to work, this china version doesnt have android auto
So yea, need use magisk to install that android auto module.
darrenlimch said:
I need android auto to work, this china version doesnt have android auto
So yea, need use magisk to install that android auto module.
Click to expand...
Click to collapse
This is the guide. It's basically the standard method but you patch init_boot.img instead of boot.img. Both can be extracted from the fastboot firmware.
VincentThacker said:
This is the guide. It's basically the standard method but you patch init_boot.img instead of boot.img. Both can be extracted from the fastboot firmware.
Click to expand...
Click to collapse
So to summarize, extracting the boot.img from the Fastboot rom, V14.0.10.0.TMBCNXM/V14.0.22.12.26.DEV/V14.0.8.0.TMBCNXM/V14.0.4.0.TMBCNXM roms doesn't work?
NOSS8 said:
So to summarize, extracting the boot.img from the Fastboot rom, V14.0.10.0.TMBCNXM/V14.0.22.12.26.DEV/V14.0.8.0.TMBCNXM/V14.0.4.0.TMBCNXM roms doesn't work?
Click to expand...
Click to collapse
Yeah, as I mentioned above, boot.img does not work; you have to use init_boot.img which has a size of exactly 8 MiB. If it does not have this size, you've got the wrong file. It probably has to do with the boot method used by the device as described here. The flashing command must also use init_boot_ab instead of boot_ab.
Guys i was in the same boat.
I have successfully root Mi 13 Pro, but i have another issue if anyone can help. Mi Wallet keeps changing as default payment method even though i have GPay selected.
VincentThacker said:
Yeah, as I mentioned above, boot.img does not work; you have to use init_boot.img which has a size of exactly 8 MiB. If it does not have this size, you've got the wrong file. It probably has to do with the boot method used by the device as described here. The flashing command must also use init_boot_ab instead of boot_ab.
Click to expand...
Click to collapse
Is it a must to include the "_ab" part in the command?
Jaberbenet said:
Is it a must to include the "_ab" part in the command?
Click to expand...
Click to collapse
Can I use magisk hide and passing safetynet with this device? Gonna buy this phone in Europe.
Wanna be sure that the module magisk hide props and universal safetynet-fix passes safetynet.
Can anyone confirm it for me?
aygul12345 said:
Can I use magisk hide and passing safetynet with this device? Gonna buy this phone in Europe.
Wanna be sure that the module magisk hide props and universal safetynet-fix passes safetynet.
Can anyone confirm it for me?
Click to expand...
Click to collapse
Yeah everything works with EU beta + DFe neo + magisk 25.2.. my phone passes safetynet without safetyfix module and google certified