Develop Bugs

Help needed to Unbrick

Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.

mumith3 said:
Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.
Click to expand...
Click to collapse
Re failing at 5% suggests to me that one of the three file was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is you bootloader unlocked. Still?

mrmazak said:
Re failing at 5% suggests to me that one of the three files was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is your bootloader unlocked? Still?
Click to expand...
Click to collapse
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?

mumith3 said:
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?
Click to expand...
Click to collapse
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img

mrmazak said:
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img
Click to expand...
Click to collapse
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?

mumith3 said:
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?
Click to expand...
Click to collapse
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash

mrmazak said:
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash
Click to expand...
Click to collapse
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable

mumith3 said:
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable
Click to expand...
Click to collapse
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)

mrmazak said:
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)
Click to expand...
Click to collapse
Thanks for all the help Sir ?
P.S. Oreo stable is pretty damn good so far.

[BRICKED] Stuck in android 8.1 bootloop

I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks

Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.

BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked

Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem

droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.

BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...

after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool

LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....

try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash

Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.

Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?

I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.

I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?

droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?

Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]

How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?

had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again

Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.

Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse

Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !

How to do test point after show THE SYSTEM HAS BEEN DESTROYED

After upload 10.2.9.0 my phone was bricked with this message. The system has been destroyed:silly:
I have tried all the methods that exist for other Xiaomi phones because this is very new and I do not find tutorials for this mobile and whenever I do the test point and give it to flash it gives me the following error
dump error: <? xml version = "1.0" encoding = "UTF-8"?> <data> <log value = "ERROR: Only nop and sig tag can be recevied before authentication." /> </ data> <? xml version = "1.0" encoding = "UTF-8"?> <data> <response value = "NAK" /> </ data>
I have tried with China stable rom, China developer, global stable. I have tried with 3 cables. It always gives the same error
I resort to the test point because I can only enter Fastboot, I can not go into recovery. I do not have a Xiaomi account associated in my Device and neither do I have debug usb enabled. My last option was the test point.
It reached the step where the pc recognizes me as Qualcomm 9008 and when I flash the fastboot decompressed rom I get the error mentioned above.
Let's see if someone helps me tell me where I do it wrong.
Please help me

Husca said:
After upload 10.2.9.0 my phone was bricked with this message. The system has been destroyed:silly:
I have tried all the methods that exist for other Xiaomi phones because this is very new and I do not find tutorials for this mobile and whenever I do the test point and give it to flash it gives me the following error
dump error: <? xml version = "1.0" encoding = "UTF-8"?> <data> <log value = "ERROR: Only nop and sig tag can be recevied before authentication." /> </ data> <? xml version = "1.0" encoding = "UTF-8"?> <data> <response value = "NAK" /> </ data>
I have tried with China stable rom, China developer, global stable. I have tried with 3 cables. It always gives the same error
I resort to the test point because I can only enter Fastboot, I can not go into recovery. I do not have a Xiaomi account associated in my Device and neither do I have debug usb enabled. My last option was the test point.
It reached the step where the pc recognizes me as Qualcomm 9008 and when I flash the fastboot decompressed rom I get the error mentioned above.
Let's see if someone helps me tell me where I do it wrong.
Please help me
Click to expand...
Click to collapse
FIXED IT (at least temporarely)
- boot into fastboot mode. press volume down and power until you see the mi bunny.
- install and run minimal adb and fastboot on a pc
- plug phone to pc
- run "fastboot devices" you should see a line with device id & fastboot
- run "fastboot continue"
wait for it
tadam you will be back into the old miui 10.2.9.
first thing you should do is dev options, mi unlock and bind phone & account. (that way you can then unlock)
credits: laviniuc

Derfeeel said:
FIXED IT (at least temporarely)
- boot into fastboot mode. press volume down and power until you see the mi bunny.
- install and run minimal adb and fastboot on a pc
- plug phone to pc
- run "fastboot devices" you should see a line with device id & fastboot
- run "fastboot continue"
wait for it
tadam you will be back into the old miui 10.2.9.
first thing you should do is dev options, mi unlock and bind phone & account. (that way you can then unlock)
credits: laviniuc
Click to expand...
Click to collapse
Omg :good:
this method has worked
you're my idol
thanks for saving me
I tried power off and then on I have same problem but using your tip I can restart again. Now I need unlock bootloader, but then? Have I instalo TRWP and flash 10.2.3.0 version?

after you unlock you should have options that werent there on locked:
- twrp from fastboot, format and custom rom
- miflash the latest tgz
havent tried any myself, still on locked, waiting time 6 days
or you can just fastboot continue on each restart, xiaomi should fix the update eventually...

laviniu_c said:
after you unlock you should have options that werent there on locked:
- twrp from fastboot, format and custom rom
- miflash the latest tgz
havent tried any myself, still on locked, waiting time 6 days
or you can just fastboot continue on each restart, xiaomi should fix the update eventually...
Click to expand...
Click to collapse
Have you also tried to flash the official global rom using miflash but it has not left you flash because you had the bootloader locked? I tried a lot of times and always said ERROR
If I have unlocked bootloader will I can flash all roms using tgz in Miflash?

Husca said:
Have you also tried to flash the official global rom using miflash but it has not left you flash because you had the bootloader locked? I tried a lot of times and always said ERROR
If I have unlocked bootloader will I can flash all roms using tgz in Miflash?
Click to expand...
Click to collapse
after you unlock yes, the miflash SHOULD work.
i havent tried because my unlock is on the 7 days timer.
yes. when the phone was bricked i tried with miflash and kept getting error. sometime just error, others also 'cannot erase in locked mode'

Anyone can enter in recovery after unbrick by ADB?

parfetto said:
Anyone can enter in recovery after unbrick by ADB?
Click to expand...
Click to collapse
i cannot, maybe some of the users who managed to fully install 10.3.1 might be able to.

laviniu_c said:
i cannot, maybe some of the users who managed to fully install 10.3.1 might be able to.
Click to expand...
Click to collapse
you must flash complete Image with XiaoMIFlash! after this you can install TWRP too.

nill3bor said:
you must flash complete Image with XiaoMIFlash! after this you can install TWRP too.
Click to expand...
Click to collapse
nodoby (i think) has the 10.3.1 pfbeuxm tgz for eea because it wasnt ever released. so clearly some users do manage to flash the recovery package too. im hoping those are able to boot into recovery too...

I try to with recovery flash, 10.2 zip and 10.3 zip and have sussed installations but no recovery.
After boot it bricks again and don't have recovery
---------- Post added at 02:19 PM ---------- Previous post was at 02:16 PM ----------

parfetto said:
I try to with recovery flash, 10.2 zip and 10.3 zip and have sussed installations but no recovery.
After boot it bricks again and don't have recovery
---------- Post added at 02:19 PM ---------- Previous post was at 02:16 PM ----------
Click to expand...
Click to collapse
Hello, I think that's because you need to use the "fastboot" file and not the "recovery".
Try this one for instance:
https://bigota.d.miui.com/V10.2.3.0...BEUXM_20190403.0000.00_9.0_eea_60219f14d6.tgz

It's a Good help.
Now just need an authorised account to mi flash ?

quick update/question:
anyone with 201903 working ota? or 201904 failing? (the manufacturing date is printed on the phone box back, bottom right near the sn barcode)

parfetto said:
It's a Good help.
Now just need an authorised account to mi flash
Click to expand...
Click to collapse
load here last version: https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
or installer here: https://www.xiaomigeek.com/download-xiaomi-mi-flash-tool.html
work here without account or any login fine!
Use the right Image and unzip the file!
use downloadlink from kagazushi or use V10.2.3.0 or
V10.2.9.0.PFBEUXM

nill3bor said:
load here last version: https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
or installer here: https://www.xiaomigeek.com/download-xiaomi-mi-flash-tool.html
work here without account or any login fine!
Use the right Image and unzip the file!
use downloadlink from kagazushi or use V10.2.3.0 or
V10.2.9.0.PFBEUXM
Click to expand...
Click to collapse
Have you do test point? I have locked BL

parfetto said:
Have you do test point? I have locked BL
Click to expand...
Click to collapse
sorry my BL is unlocked!

@parfetto,
which version (MiFlash) did you try?
install version and 20180528 or older - you not need an account!
it's just a test...

Derfeeel said:
FIXED IT (at least temporarely)
- boot into fastboot mode. press volume down and power until you see the mi bunny.
- install and run minimal adb and fastboot on a pc
- plug phone to pc
- run "fastboot devices" you should see a line with device id & fastboot
- run "fastboot continue"
wait for it
tadam you will be back into the old miui 10.2.9.
first thing you should do is dev options, mi unlock and bind phone & account. (that way you can then unlock)
credits: laviniuc
Click to expand...
Click to collapse
laviniu_c said:
after you unlock you should have options that werent there on locked:
- twrp from fastboot, format and custom rom
- miflash the latest tgz
havent tried any myself, still on locked, waiting time 6 days
or you can just fastboot continue on each restart, xiaomi should fix the update eventually...
Click to expand...
Click to collapse
Hi.
Can you tell me when I try FLASHING which have I choose: "CLEAN ALL" or "CLEAN ALL AND LOCK"?

Husca said:
Hi.
Can you tell me when I try FLASHING which have I choose: "CLEAN ALL" or "CLEAN ALL AND LOCK"?
Click to expand...
Click to collapse
CLEAN ALL is ok, other will locked you bootloader!

"the current image(boot/recovery) have been destroyed and cannot boot"

I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead

Dude, you just should flashing original/stock boot.img and recovery.img. And your phone already fixed.

Jus flash vbmeta and than flash twrp again . It will work fine and you won't get erro

Flash vbmeta

where did you got the file?

I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that

orl4nd said:
where did you got the file?
Click to expand...
Click to collapse
I found one in the pixel rom thread, it worked fine for me when i had this issue flashing candy rom

Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
You have to flash the boot.img via adb to boot into Fastboot or Recovery.

Stuck at same problem.
I am also facing same problem. I can't open fastboot and the phone reboots to stock recovery after some time. Please help.

same problem for me
Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.

reza14 said:
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.
Click to expand...
Click to collapse
I will keep trying the different flashing tools. Also let me know if you are succesful.

RMX1901CH　unbirick
RMX1901CH
I was in the same state but unbirick.
When the power is off Press the volume minus and the power simultaneously.
If you are in fastboot mode
1.adb flashing command // fastboot flash recovery twrp-3.3.1-24- RMX1901-mauronofrio.img
2. after starting TWRP - connected with otg usb memory (StockROM.ozip)
3. USBOTG to mount
4.wipe dalvik / ARTCache & cache & system & data
* 5. INSTALL StockROM
* RMX1901_11_OTA_0190_all_fSt4F56aQlqf.ozip (China) A19
I haven't tried with older versions
The international version will show an inappropriate error, and it may be possible with the same language model
* 6. reboot
Japanese who cannot speak English
I did this way

Is this problem Solve? i face the same problem. what can i do?
Hatzey said:
I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead
Click to expand...
Click to collapse
Please help me.

same issue , can't do anything

the only way I found is , to know this user and pass in this tool so that I could test the firmware and post this here

Такая же проблема, помогите!!!

Long press volume down and power button , the phone will boot into fastboot mode. Flash vbmeta with disable verity command . It worked for me. No need do anything else.

volume down and power button for 10 sec
then flash stock recovery
then wipe data from stock rocovery
then back to bootloader and flash twrp recovery
then transfer stock rom zip on device
install it
done

Man i have the same problem, did you find any solution?
I already downloaded the qualcomm flash image loader, the pc detects the phone only when i press volume + and volume - and connect it, so i know i can do something, im gonna try with the EDL mode, any advance i'll let you know

how to do Flash vbmeta with disable verity command ???

Device unable to boot: Error - mdtp image is corrupted.

So basically, I've tried to flash a custom ROM on my Mi A2 Lite. After flashing the TWRP recovery on fastboot, it shows the message "Device unable to boot
Error - mdtp image is corrupted."
I need help. Please. If I can't fix this, I'm just going to give up. I've also flashed the stock ROM images, but it still doesn't boot into the system (It doesn't even work, actually). :crying: :crying: :crying:
I've also Googled a lot for a fix, but can't seem to find one that works. I did everything I could do on fastboot (fastboot tool was showing my phone was on fastboot in the cmd) but none worked. It showed this error: fastboot write command failed (no error). If there is a fix, please reply. I would be crying if it works.

Did you flash both _a and _b partitions?

Pixeloyco said:
So basically, I've tried to flash a custom ROM on my Mi A2 Lite. After flashing the TWRP recovery on fastboot, it shows the message "Device unable to boot
Error - mdtp image is corrupted."
I need help. Please. If I can't fix this, I'm just going to give up. I've also flashed the stock ROM images, but it still doesn't boot into the system (It doesn't even work, actually). :crying: :crying: :crying:
I've also Googled a lot for a fix, but can't seem to find one that works. I did everything I could do on fastboot (fastboot tool was showing my phone was on fastboot in the cmd) but none worked. It showed this error: fastboot write command failed (no error). If there is a fix, please reply. I would be crying if it works.
Click to expand...
Click to collapse
Just flash stock back via fastboot and MiFlash and flash custom ROM again with their instructions followed.
And BTW, use offain's TWRP for flashing custom ROMs (most).

Majaque said:
Did you flash both _a and _b partitions?
Click to expand...
Click to collapse
Yes I did, but it always shows the error "write command failed(no error)" during the flashing process.

RFD80M-75679 said:
Just flash stock back via fastboot and MiFlash and flash custom ROM again with their instructions followed.
And BTW, use offain's TWRP for flashing custom ROMs (most).
Click to expand...
Click to collapse
Ok, so I did that. But I accidentally selected flash_all_lock.bat instead of flash_all.bat.... Now it's stuck in a bootloop.

Pixeloyco said:
Ok, so I did that. But I accidentally selected flash_all_lock.bat instead of flash_all.bat.... Now it's stuck in a bootloop.
Click to expand...
Click to collapse
Try wipe data/cache from stock recovery. If no luck, then try the EDL short circuit test point method and reflash stock ROM again with MiFlash. If all fails, go to service center.
Test point EDL needs very short wire (or tweezers), your regular USB cable and Qualcomm Drivers. Disconnect battery before short circuit the test points.
Test Point video tutorial: https://www.youtube.com/watch?v=BrEyAEXid_o
Test Point Location Diagram: https://gsm5g917658702.files.wordpress.com/2019/02/edl-testpoint-xiaomi-mi-a2lite.png