Hi, I have a Tencent Edition phone with WW Firmware and Fingerprint and I was facing a lot of temperature related issues and sudden shutdown issues. After a lot of research I decided to switch to CN rom and believe me or all the heating and sudden shutdown issues are gone. I now wanted to change the fingerprint but without root I don't know how to do it. I can flash and run twrp without any issue but when flash the magisk my phone won't boot to system. It just stuck in boot loading screen. So I decide to manually patch the boot image with magisk manager to see what happens but I don't know how extract boot.img from a raw firmware. Can anyone please help me with this?
The rom version is: CN_ZS660KL_16.0631.1910.5
I followed this guide to convert from ww to cn: https://forum.xda-developers.com/t/...-cn-to-ww-or-ww-to-cn-rom-20-12-2019.3961042/
Thanks in advance
Use payload dumper .
Shoeb_Saad said:
Hi, I have a Tencent Edition phone with WW Firmware and Fingerprint and I was facing a lot of temperature related issues and sudden shutdown issues. After a lot of research I decided to switch to CN rom and believe me or all the heating and sudden shutdown issues are gone. I now wanted to change the fingerprint but without root I don't know how to do it. I can flash and run twrp without any issue but when flash the magisk my phone won't boot to system. It just stuck in boot loading screen. So I decide to manually patch the boot image with magisk manager to see what happens but I don't know how extract boot.img from a raw firmware. Can anyone please help me with this?
The rom version is: CN_ZS660KL_16.0631.1910.5
I followed this guide to convert from ww to cn: https://forum.xda-developers.com/t/...-cn-to-ww-or-ww-to-cn-rom-20-12-2019.3961042/
Thanks in advance
Click to expand...
Click to collapse
if payload dumper doesnt seem to be it for you then look online for a stock firmware which contains boot.img file
Related
So i already did some searching, but nothing yet, maybe i' m overlooking something
Soi did a full recovery with mi flash tool, no dice, then took the persist out of it and flashed it with twrp, no dice, so now i reverted back to Lineage since i can't stand MIUI, but yeah, now i still don't have sensors running
The fastboot image i used is 11.8, which is the euro image as far as i know (got my device here in europe), is there something i'm completely overlooking?
Had this issue with my Pixel Experience rom - do sensors work in Miui? If so, perhaps your method of flashing is dodgy/ the rom has issues.
Flash the permissive zip. It happens sometimes when it's set to enforcing. People were talking about it on Syberia 3.6 post, check it out, there's a link to download there.
I had this same issue as well. I solved it by reflashing back to stock with MiFlash tool and using V11.0.5.0 Stock MIUI ROM.
After that boot the phone and go through the initial phone setup process.
Then you can flash TWRP Recovery (twrp-3.3.1-0-cepheus.img).
In TWRP flash vbmeta.img. After that you can flash and boot your Custom ROM with sensors working.
Do not flash any other firmware file in TWRP. I have seen other ROM threads mentioning the need to flash a fw file but don't do that.
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 all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
ajadamjones87 said:
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
Click to expand...
Click to collapse
your devices is encrypted try flash other custom rom first then try revert to stock hope it help u out
Thanks very much for your response. Based on your advice i tried to flash the latest Kraken 11 Vanilla rom from this fourm, however after installing via TWRP now i can't even get into recovery anymore, just goes straight to fastboot.
Any other suggestions please?
I have now managed to get back in to TWRP and tried flashing lineage latest rom but still i am stuck in a boot loop taking me to fastboot this time.
Please can someone help suggest hwo i can get my phone working agian. At this point i dont care which rom i end up (custom or stock) with as long as i can get it to function again
If your device is rooted, you can NOT update the system using the OTA (over-the-air), or the device will be stucked in bootloop.
If your device is rooted, you need to update the system MANUALLY, using the fastboot or spflashtool.
I suggest to update the system using the fastboot.
Now, you need to flash the whole MIUI again, except userdata and you will have your device back.
For anyone with a asimilar problem i eventually managed to fix my issue by using miflash tool version 20180528 and flashing merlin_eea_global_images_V12.0.10.0.QJOEUXM_20210413.0000.00_10.0_eea_c4a9d5d7fc fastboot version which i downloaded from the xiami site.
I had to try this multiple times because the extraction of the file did not seem to be correct on the first attempts.
Having issues flashing a patched Magisk boot.img for 10.3.12 for op6t-fajita. I did update from Android 9 but messed up somewhere along the way and lost magisk root.
Side loaded twrp and installed it to recovery slot a/b.
I downloaded the full update from the Xda post. Took payload.bin and put it in the auto extracted input folder. Took the boot.img and patched it on my phone through magisk. Flashed it through adb, constantly led to a boot loop until I reflashed the same boot.img but unpatched. Flashing magisk as a zip also causes the boot loop.
Anyone with a clue of what's going on?
Weird0ne said:
Having issues flashing a patched Magisk boot.img for 10.3.12 for op6t-fajita. I did update from Android 9 but messed up somewhere along the way and lost magisk root.
Side loaded twrp and installed it to recovery slot a/b.
I downloaded the full update from the Xda post. Took payload.bin and put it in the auto extracted input folder. Took the boot.img and patched it on my phone through magisk. Flashed it through adb, constantly led to a boot loop until I reflashed the same boot.img but unpatched.
Anyone with a clue of what's going on?
Click to expand...
Click to collapse
This is stupid question.. Did you downloaded the right file for you device??
SOK seila said:
This is stupid question.. Did you downloaded the right file for you device??
Click to expand...
Click to collapse
Pretty sure I did since my phone works fine with the version I downloaded and flashed.
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
Bump? Anyone can help?
Have you tried looking through your device's forum here on XDA? That's usually a good resource for issues like this. If nothing else you can get help from users that know the device.
https://forum.xda-developers.com/c/xiaomi-mi-10t-10t-pro.11621/
Thanks, I'll check on there in case there's people there to help.
Thank you again!