Hi, i'm trying to root my CN version 13.0.5 without the twrp, I'm using the magisk to patch the boot file, but after patch and use the command "fastboot flash boot boot.img, the mi 11 ultra just stuck in the mi logo. I'm not been able to root my phone, right now, how to root the CN version 13.0.5?
i did the same root with the android 11 and worked, something change?
hi, did you install magisk canary and not magisk stable?
I have just Root Xiaomi.eu A12 Miui13 with the same method and it work.
Hi. FIrst - better to use Magisk 23.0 - as you will still have Magisk hide. But more important - just the "fastboot boot boot.img" command instead. Once you have booted without issues you can go into Magisk and patch the real boot image file from there and restart. This is how it always worked for me. Not really sure what is the big difference there but as I said - that worked for me.
When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot flash boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot
Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!
marcel112 said:
When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot
Click to expand...
Click to collapse
Does that Format my Data? And how do i remove the Patch(remove magisk)?
Afg Playa said:
Does that Format my Data? And how do i remove the Patch(remove magisk)?
Click to expand...
Click to collapse
It does not format. That's just for root. You can flash the rom in fastboot again or flash the boot.img again from the folder images
thiagoserrao said:
Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!
Click to expand...
Click to collapse
Did IT Work?
Afg Playa said:
Did IT Work?
Click to expand...
Click to collapse
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem
thiagoserrao said:
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem
Click to expand...
Click to collapse
Great, It also worked for me Xiaomi.eu 13.0.9.0.
I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.
User1977 said:
I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.
Click to expand...
Click to collapse
i just lost my root without reason, i just restarted my phone, than no root anymore and not being able to installing again ;D. what a hell
Start from the beginning by flashing unpatched boot.img and use Magisk v23. V24 has nothing but problems. I was frustrated for a few hours with it and going back to v23 solved everything.
Related
Hi,
I'm on MIUI Global 12.0.4.0 (QCREUXM) rom, and my bootloader is unlocked with official Xiaomi tool.
I tried to root my Redmi 9c by modifying the boot.img file with magisk, and flashing it via adb.
It resulted in bootloop. So I reset back to the original boot.img, and I'm still rootless...
Does anyone know how to root this phone ?
There is no TWRP for it right now.
Thanks for any help.
BTW, is it normal that modified boot.img is much lighter than original file ? (11Mo vs 65Mo)
batteurfou said:
Hi,
I'm on MIUI Global 12.0.4.0 (QCREUXM) rom, and my bootloader is unlocked with official Xiaomi tool.
I tried to root my Redmi 9c by modifying the boot.img file with magisk, and flashing it via adb.
It resulted in bootloop. So I reset back to the original boot.img, and I'm still rootless...
Does anyone know how to root this phone ?
There is no TWRP for it right now.
Thanks for any help.
BTW, is it normal that modified boot.img is much lighter than original file ? (11Mo vs 65Mo)
Click to expand...
Click to collapse
I am facing the same result, probably the reason is that the device is SAR - System-As-Root, therefore patching boot.img aint giving root previliges and flashing causing bootloops.
Moreover modiying the system.img and flashing it wont give you root ethier.
You can try modfying and flashing the recovery.img while wiping your data as dsecribed in magisk site but every time you reboot, you need to apply the same combo buttons to enable the magisk root.
All we can do for now is to wait for a custom recovery that will probaly never be arrived or im wrong.
BTW: the patched img is supposed to be small as what ive researched, magisk repacker is repacking and compiling it to a smaller img.
Flash pachedboot.img then vbmeta 256 bites file
Redmi 9c not rooting via magsik patched boot img
Same issue
same here ,
my xiaomi 9c BL are unlock with xiaomi unlock tools
after i patch my boot.img with magisk the patchboot.img become smaller like 10kb only
after i fastboot and flash it bootloop every time
im sure my patchboot.img have some problem
but no idea how to fix it
is there anyone get this kind of problem , and how you fix it
please share your Thought thank you
powershell wont run the .\fastboot flash boot magisk_patched.img command. it gets stuck in waiting for devices even when the device is plugged and already on fastboot mode. any ideas how to fix this?
rtanjunyu said:
same here ,
my xiaomi 9c BL are unlock with xiaomi unlock tools
after i patch my boot.img with magisk the patchboot.img become smaller like 10kb only
after i fastboot and flash it bootloop every time
im sure my patchboot.img have some problem
but no idea how to fix it
is there anyone get this kind of problem , and how you fix it
please share your Thought thank you[/QUOTE
Hi, how were u able to unlock the 9c? I tried to unlock using the mi unlock tool but the message appears Couldn't Unlock then some Chinese words beneath it (can shu gong chang). How to solve this? Thank you
Click to expand...
Click to collapse
Guys check out my thread on how to root it!!! Credits to Surendra R sonawane for it:
How to ROOT Xiaomi Redmi 9C [FUNCTIONAL]
Ok so i found out that you cant root this phone without flashing vbmeta.img So its pretty simple to root your phone, here are the steps: 1. Patch your boot.img with magisk 2. download vbmeta.img and put it into your adb folder (do the same with...
forum.xda-developers.com
batteurfou said:
Hi,
I'm on MIUI Global 12.0.4.0 (QCREUXM) rom, and my bootloader is unlocked with official Xiaomi tool.
I tried to root my Redmi 9c by modifying the boot.img file with magisk, and flashing it via adb.
It resulted in bootloop. So I reset back to the original boot.img, and I'm still rootless...
Does anyone know how to root this phone ?
There is no TWRP for it right now.
Thanks for any help.
BTW, is it normal that modified boot.img is much lighter than original file ? (11Mo vs 65Mo)
Click to expand...
Click to collapse
After flashing boot.img file flash vbmeta.img file it will prevent it from bootloop just Google vbmeta.img download it and flash it through adb tools after flashing magisk modified boot.img file
To flash it in adb type flash vbmeta vbmeta.img
I have successfully rooted my redmi 9C with this method and no bootloop issue
batteurfou said:
Hi,
I'm on MIUI Global 12.0.4.0 (QCREUXM) rom, and my bootloader is unlocked with official Xiaomi tool.
I tried to root my Redmi 9c by modifying the boot.img file with magisk, and flashing it via adb.
It resulted in bootloop. So I reset back to the original boot.img, and I'm still rootless...
Does anyone know how to root this phone ?
There is no TWRP for it right now.
Thanks for any help.
BTW, is it normal that modified boot.img is much lighter than original file ? (11Mo vs 65Mo)
Click to expand...
Click to collapse
First download official stock rom from here:
Xiaomi MiUI Fastboot ROM download link for all Mi phones
Here you can find download link to MiUI stable fastboot ROM for Indian, global & other Mi variants. Mi fastboot firmware download India
miservicecentre.com
Then install latest version of magisk manager patch boot.img
Then flash it with adb.
Most important!
After flashing patched_boot.img flash vbmeta by typing "fastboot flash vbmeta vbmeta.img
Download it from from here:
vbmeta
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Then reboot and enjoy root!
See this post: https://forum.xda-developers.com/t/guide-how-to-root-redmi-9c-tested.4251085/
OnePlus 7T Pro HD01AA Global 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719979
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719978
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719976
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719977
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322189
OnePlus 7T Pro HD01AA India 11 Open Beta 1
Magisk Patched Boot Image v21.4 Patched Manager v8.0.7
https://www.androidfilehost.com/?fid=17248734326145719991
May need to install Magisk Manager manually
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719989
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719993
Stock Recovery Image
https://androidfilehost.com/?fid=17248734326145719992
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322190
OnePlus 7T Pro HD01AA Global 10.0.13
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675591747
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01AA 10.0.13
https://www.androidfilehost.com/?fid=10763459528675591755
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675591746
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591748
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591745
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320328
OnePlus 7T Pro HD01AA India 10.3.7
Magisk Patched Boot Image
https://www.androidfilehost.com/?fid=10763459528675592073
Full ZIP OxygenOS HD01AA 10.3.7
https://www.androidfilehost.com/?fid=10763459528675592086
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675592074
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592075
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675592076
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320346
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboot
Wifi issue?
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
Make sure you flash the right boot for your model number.
Settings>About phone>Build number should end HD01BA or HD01AA so make sure it's the right one.
If you want to test that your Wi-Fi works with one of the boot images.
Instead of 'fastboot flash boot patched_file_name.img' do 'fastboot boot patched_file_name.img'
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
isellmidgets said:
Thanks for this! Forgive me if this is a stupid question, but last time I tried to root my OP7T, months ago, my wifi broke and I had to hard reboot. Is that still a possibility with this?
Click to expand...
Click to collapse
I unlocked my OP 7t pro's bootloader, and every time there is an update I download the stuff mirrored by digidude512 ... I grab the magisk patched boot and the updated system pack.
I go to updates, update manually with having the update pack in the root of the storage.
When the update is done, I do not restart using the update reboot button - I use the boot to bootloader option at the power button menu (which can be enabled at the dev settings).
Then going to fastboot directly I flash the patched boot image using fastboot on windows cmd: fastboot flash boot boot_blabla.img --slot all
Reboot, go to magisk manager, update magisk using recommended direct install. Update magisk manager. Done.
Never had any problem (no wifi f*ery, nothing) and there is no need for TWRP at all. Open bootloader, magisk root and modules, adaway, stock ROM. Decent and clean.
Thanks a lot @digidude512 once again for this. Pretty convenient for others this way.
[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
If you're rooting for the first time, use fastboot boot patched_boot.img and perform a direct install from within Magisk Manager to avoid potential headaches.
If you are doing an OTA update and want to retain root, you should not be fastboot flashing anything (you're not following the right guide).
[zozi] said:
I have the same problem with wifi and network issue, only have data network 4g.
I'm flashing the right boot for my model, also i dump the OTA zip, dumpped the boot.img tried patching on magisk and flash and i got the same wifi and mobile network issue.
Mu Model is HD01BA.
Any one have the same issue?
Thanks
=== EDIT ===
After this i tried flash the original boot.img and the problem doesn't have solved, i need reflash all the system again
Click to expand...
Click to collapse
Sorry for the late reply, I couldn't sign in while XDA was changing format.
For HD01BA you want this thread.
[OOS] [11] Open_Beta_2_HD01BA [EU] [Stock/Patched boot.img] [Stock/ADB Recovery] [Full ZIP] [OOS 10.0.13]
@digidude512 Every Update needs a new Thread... interesting. Stop this sh!t.
forum.xda-developers.com
can someone please provide me with batched boot image for OnePlus 7T (India), i extracted the boot.img by using payload dumper then i batched it using magisk 8.0.5 but unfortunately when i flash it using fastboot it loops at the OnePlus animation logo
Thread updated with files for OxygenOS 11 Open Beta 1 including both Global and India Variants.
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed
Do you unlock bootloader?
zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...
leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).
Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.
Hi Guys, so we got a pilot release for MIUI 13. Here is the guide to flash/update using Xiaomi.eu ROM:
Update to MIUI13 (Android 12) from MIUI EU V12.5
A TWRP backup of current rom is recommended before following the next steps
You can follow my guide to know how you do it here: https://forum.xda-developers.com/t/...-flash-twrp-root-device-flash-eu-rom.4402203/
Download Fastboot EU rom from here: https://sourceforge.net/projects/xi...13.0.1.0.SKDMIXM_v13-12-fastboot.zip/download
Extract all the contents in zip file to any normal folder
We will be using Bootloader/Fastboot mode. Boot into Bootloader: Power off your mobile then hold Volume Down + Power Button till Fastboot bunny pops up
Connect your device to PC
To update use the updater executable for respective OS platform windows_fastboot_update_rom.bat (for windows)
For clean flash you can use windows_fastboot_first_install_with_data_format.bat (for windows)
Follow the procedures as per above choice
Wait patiently while the PC does its Job.
You may see a long pause post “writing Cust” command depending on PC configuration. try hitting any letter key on your keyboard, the process continues this way.
You may hit letter key whenever you see unusual pauses during pushing of super partition file sparse sending 1 of 9 to 9 of 9
Wait till process finishes and reboots
Flash Magisk and Root
Copy boot.img from the extracted ROM images folder to your mobile
Global Boot.img (use this if you wanna root Globoal Miui13.
Install latest Magisk app from here: https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk
Install the app and select install in Magisk and choose patch source file and select the boot.img you copied.
Wait for the process, copy the new patched image form mobile to your PC
Now lets flash the new pathced boot image using below, replace with path to boot image in place of “< --- >”
fastboot flash boot_a “<magisk_patched.img>”
fastboot flash boot_b “<magisk_patched.img>”
Reboot and check the magisk app
Follow my guide here to pass safteyNet: https://forum.xda-developers.com/t/...-flash-twrp-root-device-flash-eu-rom.4402203/
Update to miui 13 can't flash via twrp?
Yuditkiichi said:
Update to miui 13 can't flash via twrp?
Click to expand...
Click to collapse
Only the stock global rom is for recovery, xiaomi.eu rom is for fastboot.
I can boot the twrp.img, but I can't navigate in the main menu. It won't do anything
dandris86 said:
I can boot the twrp.img, but I can't navigate in the main menu. It won't do anything
Click to expand...
Click to collapse
Probably twrp is not yet compatible with the new android 12 firmware, some users also reported the same problem.
sushuguru said:
Probably twrp is not yet compatible with the new android 12 firmware, some users also reported the same problem.
Click to expand...
Click to collapse
Thanks for the quick reply
I'm updated whiteout format data. Everything looks ok.
Alright, so I was previously rooted on 12.5 (global), non twrp. its not necessary for rooting.
I did the ota update to v13 miui (global). but as its a switch between v11 and v12 of android its not possible to install magisk into an empty a/b slot.
I tried to fastboot flash your global miui boot.img after patching it with magisk and it did not work.
I suspect the boot.img to not be compatible with the global rom.
So I opted to flash the Eu fastboot version of miui 13, I set up the phone.
Then patched the stock boot.img with magisk and fastboot that. Done phone is now rooted on v13 miui. and passing safety net check.
phone data was lost as i had to switch from global to eu.
Can anyone confirm that we get widgets and other features that are not found in the miui 13 global I want to make the switch but I want to know what would still be missing
The global fastboot rom is now released. follow same steps above to have rooted global non twrp.
V13.0.1.0.SKDMIXM (https://xiaomifirmwareupdater.com/miui/vili/stable/V13.0.1.0.SKDMIXM/)
-Edit-
Ive also updated to the latest via ota V13.0.2.0.SKDMIXM (Stable beta). but as it detected the boot.img was modified it downloaded the entire recovery rom. Installed. Lost root access.
I then fastboot re flashed the patched boot.img from the V13.0.1.0.SKDMIXM and it works.
so im rooted/ safetynet check passed on V13.0.2.0.SKDMIXM (Global)
roms can be found here https://xiaomifirmwareupdater.com/miui/vili/
Downloaded the latest EEU vili_eea_global_images_V13.0.8.0.SKDEUXM_20220224.0000.00_12.0_eea_38cc4dcea7.tgz
but the only .bat files I see are
flash_all.bat, flash_all_except_storage.bat and flash_all_lock.bat
BettlePimp said:
Downloaded the latest EEU vili_eea_global_images_V13.0.8.0.SKDEUXM_20220224.0000.00_12.0_eea_38cc4dcea7.tgz
but the only .bat files I see are
flash_all.bat, flash_all_except_storage.bat and flash_all_lock.bat
Click to expand...
Click to collapse
It's a fastboot stock rom which this flash with miflash or with bat files
This thread is about XIAOMI EU custom rom
This phone is so ****ty, I'm trying to do OTA update via 100mbit/'s network in netherlands from about two f***NG weeks and it can not be finished. I can't belive that I have paid 800€ for so big ****!
Hello
For the ROOT it works perfectly (without TWRP, just with magisk)
You unlock the bootloader and wait 1 week, you extract the boot.img, you modify the file with magisk and do the command wtih adb with the modified boot
Very simple
(If you want to extract the rom file by yourself you can just extract with a little tool after your download the rom
, you can extract the fil with the payloaf file, for that, just have a look in the method 3 in this link)
Hello!
After OTA MIUI update from stock MIUI 13 to stock MIUI 14 on my Mi 11 I have lost Magisk and root (as normally happens to me after OTA).
So I obtain boot.img from stock fastboot ROM, uploaded it to the phone, patch it via Magisk 25.2, download generated file to PC, reboot phone to fastboot, flash generated file to boot_a and boot_b but... Nothing happens! After successful reboot, Magisk app can't feel Magisk as installed.
Tried this process once again with no success.
Could you please help me?
artyums said:
Hello!
After OTA MIUI update from stock MIUI 13 to stock MIUI 14 on my Mi 11 I have lost Magisk and root (as normally happens to me after OTA).
So I obtain boot.img from stock fastboot ROM, uploaded it to the phone, patch it via Magisk 25.2, download generated file to PC, reboot phone to fastboot, flash generated file to boot_a and boot_b but... Nothing happens! After successful reboot, Magisk app can't feel Magisk as installed.
Tried this process once again with no success.
Could you please help me?
Click to expand...
Click to collapse
Did you try Magisk Canary? Try Magisk Canary 25208.
surajpai524 said:
Did you try Magisk Canary? Try Magisk Canary 25208.
Click to expand...
Click to collapse
Tried Magisk 25210 today - with no effect at all...
Any other suggestions?
artyums said:
Tried Magisk 25210 today - with no effect at all...
Any other suggestions?
Click to expand...
Click to collapse
Post a log or a bug report on GitHub Magisk Repo. The developers can help you.
artyums said:
So I obtain boot.img from stock fastboot ROM, uploaded it to the phone, patch it via Magisk 25.2, […] After successful reboot, Magisk app can't feel Magisk as installed.
Click to expand...
Click to collapse
Same here on Mi 11T, both using Magisk 26.1 and canary 47d2d4e3 (26102).
Maybe you can try to rename the Magisk.apk to Magisk.zip and sideload it with adb. That was my workaround but it is normally not recommended.
I have different issues after patching boot image phone has rooted ,but after eatch restart magisk root lost.
mi 11x.