Thanks, will try this! BTW, will there be an issue, if the device is MTK? Been reading there is a difference in approaches when dealing with MTK devices.I got stuck in a fastboot loop at one point but managed to restore MIUI with XiaomiADBFastbootTools.jar from https://szaki.github.io/XiaomiADBFastbootTools/ (if that isn't already how you were installing the new image), extracting the MIUI .tgz to a folder, and going through Flasher -> Image -> Select ROM Folder -> Clean Install -> Flash ROM
Thanks for the verification.
I see. I actually tried that, but no dice. What happens now is that my phone ends up stuck in the redmi boot logo and doesn't go anywhere (I think I ended up all night, and nothing happened). Wishing there was a way to check what the reall error is actually.I also had the dm-verity error at one point and IIRC I fixed it with the steps from "fastboot --disable-verity" onwards on the first post in https://forum.xda-developers.com/t/...s-on-redmi-note-10-5g-poco-m3-pro-5g.4346983/, using the vbmeta.img attached further down on the same page
Yes, I made sure I didn't use the China firmware. I already tried the Global, EEA, and Indonesia firmwares, but nothing worked. The bootloader is unlocked as well.are you shure you flash the eea firmware? dm verity error appen when you flash china firmware on global or eea firmware. global and eea firmwares all fully compatibles. i'm 100% because i switched between these more than one time. now i'm on 12.5.2 global, but my original stock was eea branded. have you unlocked the bootloader? you have to do
Sorry, it just saw FASTBOOT. I just saw this instruction now. It tried it, but it wouldn't go to fastbootd. It simply showed the list of commands for fastboot.
lock?!? what option have u selected? i hope flash all, not flash and lock. or u made a damage
I used the Clean All Settings. I got this image (camellian_id_global_images_V126.96.36.199.RKSIDXM_20210813.0000.00_11.0_global_e8b6b36cdd), and it now seems to work! The DM-Verity error can now be loaded with a blank one, and my phone now boots as normally.