Xiaomi Redmi note 10 Pro 5g (chopin) bootloop after patch boot.img from magisk v23
i have the fastboot ROM "chopin_images_V12.5.3.0.RKPCNXM_20210527.0000.00_11.0_cn_90be99bee5"
after flashing of boot.img via adb tools done sucessfully, after reboot bootloop starts
replace the boot.img with original boot.img file , problem disappeared and phone becomes Ok
ROM i am using is China Original ROM, didn't flash to global ROM
also tried to patch boot.img via magisk v22.0 same problem
heard from someone magisk 7.5.1 will solve this issue , but after installing magisk 7.5.1 there no file patch option
asadattari12 said:
Xiaomi Redmi note 10 Pro 5g (chopin) bootloop after patch boot.img from magisk v23
i have the fastboot ROM "chopin_images_V12.5.3.0.RKPCNXM_20210527.0000.00_11.0_cn_90be99bee5"
after flashing of boot.img via adb tools done sucessfully, after reboot bootloop starts
replace the boot.img with original boot.img file , problem disappeared and phone becomes Ok
ROM i am using is China Original ROM, didn't flash to global ROM
also tried to patch boot.img via magisk v22.0 same problem
heard from someone magisk 7.5.1 will solve this issue , but after installing magisk 7.5.1 there no file patch option
Click to expand...
Click to collapse
It sucks we still dont have proper twrp for chopin, we've been waiting for so long
Related
Hi,
I tried to flash Magisk on my Redmi 4X (using TWRP 3.0.3) no error during flashing, but then after booting completes, i don't see Magisk anywhere and phone doesn't get rooted.
ROM: MIUI GLOBAL 9.2 STABLE (9.2.5.0)
TWRP: TWRP Recovery (cofface) 3.0.3-0
Anyone has any idea?
Install magisk manager manually. Either search internet for magisk manager apk or extract the zip and install apk from there
mvrk69 said:
Hi,
I tried to flash Magisk on my Redmi 4X (using TWRP 3.0.3) no error during flashing, but then after booting completes, i don't see Magisk anywhere and phone doesn't get rooted.
ROM: MIUI GLOBAL 9.2 STABLE (9.2.5.0)
TWRP: TWRP Recovery (cofface) 3.0.3-0
Anyone has any idea?
Click to expand...
Click to collapse
Mount system in twrp then flash magisk zip
mvrk69 said:
Hi,
I tried to flash Magisk on my Redmi 4X (using TWRP 3.0.3) no error during flashing, but then after booting completes, i don't see Magisk anywhere and phone doesn't get rooted.
ROM: MIUI GLOBAL 9.2 STABLE (9.2.5.0)
TWRP: TWRP Recovery (cofface) 3.0.3-0
Anyone has any idea?
Click to expand...
Click to collapse
Get the boot.img file from the fastboot images of your miui version, install magisk manager, and install using patch boot image method, patch the boot.img file then flash this patched boot.img file to boot in twro recovery!
Hi.
Just after installing the .zip magisk file in twrp, my redmi k30 reboot as it should and after that it stays bricked in the bootloader. I've been able to reinstall the rom but I want to install magisk on the phone. I've tried it another time and the issue persists. Any idea of the origin of the problem? How can I install magisk?
I dont have k30, but you should flash lower version, say 19.3, it might help
lexobys01 said:
I dont have k30, but you should flash lower version, say 19.3, it might help
Click to expand...
Click to collapse
I've tried it but the issue persists
Give it another try by instaling magisk manager app first, then flash magisk from the manager. If it's still not working, remove with magisk uninstaller, rather than flashing the whole ROM, and try with 20.1
As for me I installed MIUI.eu using fastboot and then pull the boot.img from the ROM, patch it using magisk manager & fastboot flash the patched boot.img. From there you can get a proper magisk & passed all safety net check
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.
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.