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/
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.
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)
Well for now I can't find any compatible TWRP version for Realme C20. Even developers aren't going for it. May be I had to buy Realme C11,12 or 15. My bad. No custom recovery - No custom ROM. most funny thing is I cant even minimize apps alive without killing all the process with app. Even C20 made with G35 Later version of G35 Series phones have custom roms , etc. If anyone knows any way to Flash TWRP into C20 please reply to this thread.
1. Unlock bootloader using adb fastboot
2. Download stock rom from realme website
3. Extract boot.img and vbmeta.img from ozip File, then patch boot.img
4. First run, fastboot disable verify command with vbmeta.img and then unlock command with boot.img
5. Your device is rooted, you can uninstall OEM apps, and boost performance using magisk modules.
zavon21 said:
1. Unlock bootloader using adb fastboot
2. Download stock rom from realme website
3. Extract boot.img and vbmeta.img from ozip File, then patch boot.img
4. First run, fastboot disable verify command with vbmeta.img and then unlock command with boot.img
5. Your device is rooted, you can uninstall OEM apps, and boost performance using magisk modules.
Click to expand...
Click to collapse
How to unlock bootloader of realme c20
Because i cant find indepth test apk.
bootloader unlocked steps help me
Thank you
How do I go about rooting android 13 stable (update 2) ?
IGKID said:
How do I go about rooting android 13 stable (update 2) ?
Click to expand...
Click to collapse
Follow my guide. Pretty straight forward
NE2213 android 13 magisk stock boot patched c20
I have android 13 NE2215
Everytime I try to boot patched boot.image it goes to Qualcomm crashdump mode...is there a working way to root oxygen os 13 c20 on NE2211?
wshyar said:
Everytime I try to boot patched boot.image it goes to Qualcomm crashdump mode...is there a working way to root oxygen os 13 c20 on NE2211?
Click to expand...
Click to collapse
Where did you obtain your patched boot image?
It's always best to get it yourself and patch it yourself.
dladz said:
Where did you obtain your patched boot image?
It's always best to get it yourself and patch it yourself.
Click to expand...
Click to collapse
From OOS 13 payload.bin using fastboot enhance tool or payload dumper tool, it doesn't work with either of them..
wshyar said:
From OOS 13 payload.bin using fastboot enhance tool or payload dumper tool, it doesn't work with either of them.
Click to expand...
Click to collapse
That is the correct way to do it.
Are you using the latest Magisk? Was the firmware you extracted it from the full firmware? Or a smaller incremental zip?
Full zip is around 4.2GB
IGKID said:
I have android 13 NE2215
Click to expand...
Click to collapse
follow my thread
dladz said:
That is the correct way to do it.
Are you using the latest Magisk? Was the firmware you extracted it from the full firmware? Or a smaller incremental zip?
Full zip is around 4.2GB
Click to expand...
Click to collapse
I Am using latest Magisk version and even tested lower versions.
The firmware is about 4.85gb at first it installs version NE2211_11_C.19
But i updated it to NE2211_11_C.20 and checked the incremental update in fastboot enhance tool while extracting boot.img..
wshyar said:
I Am using latest Magisk version and even tested lower versions.
The firmware is about 4.85gb at first it installs version NE2211_11_C.19
But i updated it to NE2211_11_C.20 and checked the incremental update in fastboot enhance tool while extracting boot.img..
Click to expand...
Click to collapse
? It installs C_19 then it's not the one you want, you need to regrab C_20, use oxygen updater if it's available.
If not then I'm not sure buddy
g96818 said:
follow my thread
Click to expand...
Click to collapse
Will try it ton and get back to you.
Update: I do not understand what is going on in your thread. It's all over the place. For example you say use stock and patch it yourself or download patched bootloader. Can you provide a more simple tutorial please.
Does anyone root Android 13 succefully yet?
Xainn said:
Does anyone root Android 13 succefully yet?
Click to expand...
Click to collapse
Yes, same as oos12
1. Download zip rom and extract payload.bin
2. Use Fastboot Enhance export boot.img from payload.bin
3. Install Magisk Manager on your phone
4. Copy boot.img to your phone storage
5. Patch boot.img by Magisk Manager
6. Copy Patched file (in Download folder) to your PC and reboot phone to Bootloader Mode
7. Open Windows Power Shell at folder has Patched file and run command
fastboot flash boot patched_file_name.img
fastboot reboot
tranthengoc said:
1. Download zip rom and extract payload.bin
2. Use Fastboot Enhance export boot.img from payload.bin
3. Install Magisk Manager on your phone
4. Copy boot.img to your phone storage
5. Patch boot.img by Magisk Manager
6. Copy Patched file (in Download folder) to your PC and reboot phone to Bootloader Mode
7. Open Windows Power Shell at folder has Patched file and run command
fastboot flash boot patched_file_name.img
fastboot reboot
Click to expand...
Click to collapse
You wouldn't need Fastboot reboot as you're telling the device to boot when typing Fastboot boot.
Spot on otherwise