Develop Bugs

[Q] Is my phone brick? stuck on google boot image

I am not a noob when it comes to android dev, but this has stomped me and I am asking for expert's help. I have a GSM version SGN that I flashed the official yakju ICL53F on it via fastboot. It has been working great for a month now. Suddenly today I felt it was vibrating in my pocket, took it out and discover it was stuck in boot loop--the google sign with the unlocked icon. I waited til I get home to put clockworkmod on it, but when I try to nandroid it first it gave me an error. Then I figure I would just fastboot the stock rom on it again, using fastboot mode like I did before. I even flashed the bootloader, radio, and system image. Still stuck on google icon with screen went blank, vibrate and repeat. Is there anything else I should try? odin mode is also available, but I am not seeing any instructions on it at the developer section so I am reluctuant to try it. I can still adb and fastboot to access my phone...help please?

well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.

lettcco said:
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
Click to expand...
Click to collapse
I think you are mixing some things up.
The "update" parameter of fastboot is used to flash a group of images inside a zip file to you device.
The "flash" parameter is used to flash a single image to your device.
The following two groups of commands do the same thing:
fastboot update -w image-yakju-icl513f.zip
or
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot erase cache

Attempting to root and install a custom ROM (DU), where am I going wrong?

Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!

I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.

HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.

thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.

If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app

HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone

Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.

thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play

berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:

Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.

Stuck in TWRP after attempting to root

I've been following this guide:
https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591
to try and root my Pixel C. I was initially following a different guide, but I believe I now have:
bootloader-dragon-google_smaug.7900.50.0.img and TWRP_dragon_3.1.0-2.img, loaded through fastboot
I was then able to push
Update.ZIP_PixelC_Ryu_system-vendor-boot_OPP1.zip and SuperSU-v2.79-201612051815.zip to /sdcard/ via adb in TWRP. I then tried to install both, as per the guide.
I was a bit confused when the "flashing system.img... this will take some time" part took no time at all, but it had taken a while to get to that point so I figured maybe the messages were in the wrong order or something. Both said they were successful.
Tried booting to system - just came back to TWRP.
So I thought I'd try to flash the system image back on. But I can't push any files now. Everytime I try, it creates the files then fails and I start getting read-only file system errors
If I try to install update.zip again (the one above), I now get "failed to mount '/data-full' (Device or resource busy)"
So I'm quite stuck at this point. Can't revert to stock image, can't install the new image... any help would be much appreciated!

I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.

peter73 said:
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
Click to expand...
Click to collapse
I second this ^ except for the fastboot boot twrp.img part. Why do you do that? The first line should be enough.

how to flash recovery img ?

Hello, on any custom roms we see recovery as img, so whats the ultimate good process to actually flash it?
img to tar bootloop
any other recovery bootloop
only one thats working is "twrp-z3s-3.5.0_10-A11_6+vbmeta_DUB5" BUT i have x1s, so pain to flash some rom.
Im currently on beyond rom 3.1, because i cant flash anything else.
Any help here?

Try flashing vbmeta.img after flashing recovery

like download mode -> recovery, then download mode again and only vbmeta?
didnt try that, ill try it right away
edit:
1) download mode -> AP EXYNOS-G98X-LINEAGE-RECOVERY-20200709
2) booted up rom
3) turned off -> download mode -> USERDATA vbmeta.tar from beyond rom
4) bootloop, up button and power same thing

i dont know if i should try stock and then go for root again or what exactly do.. i dont want to lose any data now. It got really complicated, since i go from root apk clockworkmod era.
maybe magisk is the issue? since i have it installed

Go to fastboot
Flash recovery
Flash vbmeta
Reboot
If fastboot doesn't like extensions of your images, change them to .img

how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work

b30wu1f said:
how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work
Click to expand...
Click to collapse
Move vbmeta.img to your phone and go to Install section. Install it and reboot.
Also, TWRP offers an option to reboot to bootloader. You can try it too

well, i flashed lineage recovery img and then vbmeta, phone booted up, but got probably original recovery. its really frustrating. Do you have any valid and working "tutorial" to get the recovery working ?

i just need recovery thats x1s, so it should be probably lineage recovery, but cant install it. Im starting to hate these new phones.

I'm sorry, I don't have any specific tutorial, but in general:
adb reboot-fastboot
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot-recovery
If this doesn't work, search for your specific device on XDA. You shouldn't hate new phones, you should hate people who sell them, because they make everything hard so you won't switch from their software, which spies on you.

tried TWRP that works, installed as img lineage-18.1-20210224-recovery-x1s.img and now it suddenly worked. Thank you for help, after 6 hours =)

Question Rooting - anyone successful?

I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com

Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?

dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks

I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.

sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .

dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.

dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance

Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.

I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)

chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).