Develop Bugs

LG G3 Hard Break

Hi there,
I have a problem that my LG will not boot the device is stuck at the logo, I've also done a hardware reset but the process also depends on the logo proof and 10min not happened.
In the download mode, I'm not coming.
About the fastboot mode I try to start TWRP, but it appears the TWRP logo and nothing else happens.

How did you manage to get it to this point? What did you do before it didn't boot anymore?
Also, if you manage to get adb access somehow you can just reflash the recovery again

I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.

So you cant enter download mode or recovery? And you cant turn on phone?

No download mode is not only possible fastboot mode. If I we want to install Recovery in fastboot mode, shown below
Command: fastboot flash recovery recovery .img
Error on LG G3:
Error: Command never completed
Error: Auto CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror:Command completed with errors
Failed to send stop command
Failed Writing block @1

SourceCoder said:
No download mode is not only possible fastboot mode./QUOTE]
Could you please explain this.
Is comma missing somewhere?
Click to expand...
Click to collapse

The following screen appears:
lgg3root.com/wp-content/uploads/2014/08/howto-unroot-unbrick-lgg3-2-690x492.jpg
And then immediately this screen:
android-hilfe.de/attachments/root-custom-roms-modding-fuer-lg-g3/345262d1415303724-lg-g3-kein-download-modus-mehr-img_20141106_093950.jpg
This screen does not appear:
androidheadlines.com/wp-content/uploads/2014/07/LG-G3-Download-Mode-AH-1.jpg

SourceCoder said:
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
Click to expand...
Click to collapse
Something does not compute in this at all. SuperSU should not have caused your phone to brick like that.
Is there something else you are not telling us about how your phone was set up? Were you doing anything before you updated SuperSU? This looks like a case of where you flashed the wrong image on your phone, if you ask me.
SuperSU is not phone specific, so I'm having a hard time believing SuperSU did this.
Something else must have happened that you are not telling us. You need to lay out in order, everything you did to your phone up to the point of updating SuperSU.
Also, SuperSU asks how to update: normal or via recovery. Which way did you choose? Either one shouldn't matter, but it's a start.

I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1

SourceCoder said:
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
Click to expand...
Click to collapse
Did you flash the correct laf.img file for your model of phone? If not, that could be part of it. What model of the G3 are you using and where exactly did you obtain the laf.img file from?

SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257

SourceCoder said:
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
Click to expand...
Click to collapse
Well, there you go. I have NO idea for what version of the G3 that thread was for. The guy never states which version it is. You do not, repeat, do NOT flash anything to system, boot, etc for this phone unless you know for sure it's for YOUR model of the G3. There are various models of the G3. For example, mine is the Verizon model (VZ985). There is an AT&T model (DS855), and numerous others, especially for those overseas. I would not and should not flash the DS855 boot image to my VS985 boot image. It will brick the phone as you have found out the hard way from what I can tell.
You just flashed something you have NO idea which version it was for. You may have completely bricked your phone. I'm not entirely sure, but you need to find the correct stock images for your phone and flash them back.
You need to go here and figure out which model of G3 you have:
http://forum.xda-developers.com/showthread.php?t=2791269
After that, you need to go and find the correct stock image files and flash those back onto your phone. Since this are NOT img files, you cannot fastboot flash them. You muse use either KDZ or TOT files depending on which ones are available for your model of phone:
http://lg-firmware-rom.com/
or
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
Then, you have to use the correct tool to flash these files depending on if they are KDZ or TOT file:
http://forum.xda-developers.com/showthread.php?t=2785089
Hopefully, flashing back to the correct stock image will fix you up. However, you better make darned sure which model of phone you have BEFORE you even attempt it. Once you figure out which model of G3 you have, post here and ask. Otherwise, you could bork your phone up even worse to where it may not be recoverable. Hopefully, it's not at that state right now.

I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)

SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Again, did you verify with the link you posted for the image file that it was indeed for YOUR model of your phone? If not, you probably have bricked it.
You need to go and follow the links I posted which tell you how to flash back to stock.
There was no reason to go into fastboot mode for SuperSU. I don't know why you felt you had to do that.
Also, the second link you posted has the thread pretty much deleted. The OP said he was incorrect in what he posted (whatever it was I don't know since he deleted it), so it was removed due to it not working as stated.
Go back to the links I posted to flash back to stock on your model. If what you say you have is the European model, then this would be the KDZ file you want:
http://storagecow.eu/Xda/LG G3/Stock/Europe Common 16G D85510A_00.kdz
I would verify for sure that is what your phone is before continuing or else, you'll bork your phone up even worse than it is already.
The boot image you flashed is probably for the Korean version of the phone and that's why everything is messed up.
If you are not sure on how to do this, then you might want to find someone near you who does.
Just remember, just because a post says it's for the G3 doesn't mean it's specifically for YOUR model of the G3. You need to verify for sure that it is. Most have the model number in the thread's title.

LG G3 Fastboot
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen

[1700] fastboot mode started
razaaliarain said:
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
Click to expand...
Click to collapse
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.

_narisha_ said:
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
Click to expand...
Click to collapse
But now i am stuck again on fastboot mode and this time i was not rooted and did not had twrp installed so now when i try to use the "fastboot boot twrp.img " my device will reboot and then will be stuck on twrp logo on the screen

I have the same problem...
I ran stock OTA update 20f, since a couple of weeks ago. While I had my phone on the table and it was runing voice recorder soft it restarted once and then after a couple of minutes again. This time it never booted but stuck at the LG screen.
Never rooted, never installed anything other than the OTA 20e and 20f updates. I have not flashed anything to the phone other than the official OTA.
Doesn't boot to anything other than fastboot. Recovery starts but after confirming twice it reboots and stuck still.
If I boot to Download Mode it goes to fastboot, if I wait long enough on regular boot that only shows the LG logo it will eventually go to fastboot.
Running "fastboot.exe boot openrecovery-twrp-2.8.4.0-d855.img" gives me the same error messages, stuck at the TWRP logo screen. I found the ADB port is connected but when running "adb devices" it says "LGD855..... offline". I didn't enable ADB before the device crashed and I can't enable it in TWRP because it doesn't start properly.
I have the 32GB D855 European unlocked. I belive this is hardware problem and will send it for repairs.

SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.

gee2012 said:
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
Click to expand...
Click to collapse
That's right. I tested to boot Philz recovery and it freezes at the text.
Mine says actually:
Error: Command never completed
Error: Auto CMD12 error
Error: Command never completed
Error: Command timeout error
Failed to send stop command
Failed reading block @ 1
mmc read failure misc 2048
The CMD12 is according to emmc spec a "Stop command".
So this is a hardware fault and not a software one.

Stuck on splash screen "Your device has been unlocked and can't be trusted."

Stuck on splash screen "Your device has been unlocked and can't be trusted."
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.

gabrce said:
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
Click to expand...
Click to collapse
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.

mrmazak said:
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
Click to expand...
Click to collapse
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.

gabrce said:
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
Click to expand...
Click to collapse
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.

mrmazak said:
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
Click to expand...
Click to collapse
Thank you but "fastboot get prop" is not the right command. If anybody has a solution it will be awesome.

Download the latest full ota package for your device (around 2gb)
Extract the contents of the update. App using huawei firmware extractor and
Flash
kernel
Ramdisk
Recover ramdisk
System and cust images using fastboot
After that flash the correct version of twrp for your device and then install images of version and vendor(found in update. App file) partitions using twrp.
.
This method worked for me

It didn't worked for me... Do you know any other method?

I tried many TWRP versions but the phone doesn't boot into TWRP...

Please help... My unlocked bl whyred stuck at logo... Please help

Hi guys.. my whyred stucked at Mi Logo with Unlocked Text Signed below.
Sorry, i need to create a new thread because i can't find any solutions from related thread that can help me.
The Problem start when i was using my phone (with 10% free space storage i think) then it got hang (stop respond), then i push and hold the power button to restart my whyred and then my phone stuck at Mi Logo as i told above;
Condition now :
1. Type : Whyred; Global Stable Rom; ARB 4; No Recovery (such as TWRP etc)
2. It can still get into fastboot mode
3. Unlocked Bootloader
4. Unable to get into recovery mode.
5. Unable to get into EDL Mode
6. Status fastboot oem device-info :
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
I have done some trial, and it always ends with error, such as :
1. Get the phone into fastboot mode and flash the latest Rom (Global & China) using Mi Flash, the result is some kind "error : write protected"
2. Get the phone into fastboot mode and using adb fastboot do :
- flash any recovery (TWRP) using adb (fastboot flash recovery twrp.img), the result is "error : write protected"
- flash boot.img from Latest Firmware partition using adb (fastboot flash boot boot.img), the result is "error : write protected"
3. Get the phone into the EDL Mode using Test Point (with battery been connected), it has been detected as qloader 9008 and Mi Flash can detect it as a COM Port, but when i flashed it with the latest ROM (Global and China), it ends with error too.
4. Get the phone into recovery mode using "fastboot boot twrp.img" and the result is the twrp just appear as a start screen without any button, so i can't operate the twrp.
5. Get the phone into recovery mode using "fastboot boot recovery.img" (recovery.img from Stock Firmware) and the result is the the phone success got into recovery, i did wipe data, the indicator showed the progress but it stuck without success sign, so i restart the phone using power button and the problem still persist.
Please, any suggestion will help much, i just dont know what to do anymore, i don't plan to bring it to service center because it will make an expensive price.
i am so sorry i am unable post any picture because i dont have any other phone.
Please any help guys..

Try flash in EDL Mode with EDL Authentification & Fail
Aswery said:
thanks for the offer..
Click to expand...
Click to collapse
Here is my update..
I have try flash using EDl Mode with EDL Authentification. Here is the Flash Log, please what is that mean :
[01.27.22]:3 COM3 3.1394316s [01.27.21 COM3]:dump:<?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>
[01.27.27]:3 COM3 8.1708237s [01.27.26 COM3]:System.Exception: authentication failed The operation completed successfully
at XiaoMiFlash.code.bl.SerialPortDevice.dlAuth()
at XiaoMiFlash.code.bl.SerialPortDevice.ConfigureDDR(Int32 intSectorSize, Int32 buffer_sectors, String ddrType, Int32 m_iSkipStorageInit)
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() at XiaoMiFlash.code.bl.SerialPortDevice.dlAuth()
at XiaoMiFlash.code.bl.SerialPortDevice.ConfigureDDR(Int32 intSectorSize, Int32 buffer_sectors, String ddrType, Int32 m_iSkipStorageInit)
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
Any suggest please..

Tryon orangefox recovery

Did you use the dummy.img to bypass arb protection?
You can try orange fox recovery.
Download it, then flash dummy with command "fastboot flash antirbpass dummy.img" , after that try to boot orange fox recovery with "fastboot boot recovery.img"

Result is the same, flash antirbpass dummy.img done but flash recovery (even orangefox) got error : remote : error flashing partition : write protected.
When try boot with flash boot orangefox, the result is only the logo orangefox screen appear.

Prathamesh 27 said:
Tryon orangefox recovery
Click to expand...
Click to collapse
Thanks bro..
But it's not work on my device

I don't know why, but I have tried this 2 things :
"Fastboot flash userdata userdata.img"
It finished successfully
But when I tried
"Fastboot flash recovery xxx.img"
It failed because error write partition.
That's why I think that there must be a solution to pass the write protected error..

Aswery said:
I don't know why, but I have tried this 2 things :
"Fastboot flash userdata userdata.img"
It finished successfully
But when I tried
"Fastboot flash recovery xxx.img"
It failed because error write partition.
That's why I think that there must be a solution to pass the write protected error..
Click to expand...
Click to collapse
fastboot boot xxx.img
Copy recovery img in phone, then flash the recovery from recovery.
Try orangefox, pitchblack, twrp

Prathamesh 27 said:
fastboot boot xxx.img
Copy recovery img in phone, then flash the recovery from recovery.
Try orangefox, pitchblack, twrp
Click to expand...
Click to collapse
I have tried 2 trial "Fastboot boot xxx.img" and it gave me 2 results :
1. If xxx img is twrp, it can only show the begining screen (if twrp) without any button.
2. If xxx.img is stock recovery, it can only give wipe data that will stuck at 99.99%.
Both of it has not given access to copy from PC into phone.

Aswery said:
I have tried 2 trial "Fastboot boot xxx.img" and it gave me 2 results :
1. If xxx img is twrp, it can only show the begining screen (if twrp) without any button.
2. If xxx.img is stock recovery, it can only give wipe data that will stuck at 99.99%.
Both of it has not given access to copy from PC into phone.
Click to expand...
Click to collapse
Try clean flashing and locking bootloader in mi flash tool, then unlock bootloader and booting into recovery. I recommend getting latest version of MIUI in your device before booting into recovery. If you want, before this, try pitchblack recovery also. If it works, no need to install MIUI.

Prathamesh 27 said:
Try clean flashing and locking bootloader in mi flash tool, then unlock bootloader and booting into recovery. I recommend getting latest version of MIUI in your device before booting into recovery. If you want, before this, try pitchblack recovery also. If it works, no need to install MIUI.
Click to expand...
Click to collapse
Thanks man.. Soon I ll try it, and I will let you know the result

Aswery said:
Thanks man.. Soon I ll try it, and I will let you know the result
Click to expand...
Click to collapse
Yeah

Prathamesh 27 said:
Yeah
Click to expand...
Click to collapse
HIi guys, have you resolved?
I have the same problem with my phone
Please, can I have help?
thk

gotxges said:
HIi guys, have you resolved?
I have the same problem with my phone
Please, can I have help?
thk
Click to expand...
Click to collapse
Did you try to flash MIUI firmware using mi flash tool?

Mysteryagr said:
Did you try to flash MIUI firmware using mi flash tool?
Click to expand...
Click to collapse
Yes, I tried all standard procedure...TWRP RECOVERY, FLASH ROM etc...
The finally msg it's same "write protected".
Any IDEA ?
I think it's a "commercial lock" applied by XIAOMI. .... for change a phone.

gotxges said:
Yes, I tried all standard procedure...TWRP RECOVERY, FLASH ROM etc...
The finally msg it's same "write protected".
Any IDEA ?
I think it's a "commercial lock" applied by XIAOMI. .... for change a phone.
Click to expand...
Click to collapse
If you try to flash using MI flash tool, i.e, use clean all and flash option in mi flash tool. It will succeed. If it doesn't, you may have to use other method.
Here link contains all details.
https://c.mi.com/thread-2248078-1-0.html

Aswery said:
Hi guys.. my whyred stucked at Mi Logo with Unlocked Text Signed below.
Sorry, i need to create a new thread because i can't find any solutions from related thread that can help me.
The Problem start when i was using my phone (with 10% free space storage i think) then it got hang (stop respond), then i push and hold the power button to restart my whyred and then my phone stuck at Mi Logo as i told above;
Condition now :
1. Type : Whyred; Global Stable Rom; ARB 4; No Recovery (such as TWRP etc)
2. It can still get into fastboot mode
3. Unlocked Bootloader
4. Unable to get into recovery mode.
5. Unable to get into EDL Mode
6. Status fastboot oem device-info :
Please any help guys..
Click to expand...
Click to collapse
Me also faced this issue on my whyred last week. I read through the comments and find me faced exactly the same bricking. 'write protected' message on fastboot flasing, twrp and orangefox booting only to its logo, able to boot into stock recovery but wiping data stuck on 99.99 %. etc..
I also tried the recovery method by using miflas pro , Edl flash (not worked due to the authentication or device storage emmc corrupted) but no luck. Finally i give up on flashing and went to the service center. They tried to flash the software but no luck. They said the internal memory emmc got currupted , so need to replace it. Now i am waiting for the device for one week. I will let you know whether it will working or not.
I would like to know one thing..
Which Rom and Kernel are you using when the phone was bricked. My phone also bricked like the same way as you said in the OP.

https://files.orangefox.tech/OrangeFox-Stable/whyred/
Try Flashing zip recovery from recovery mode.

This happen to me 2 day ago.same like the user mention.screen freeze and then when restart it stuck forever on splash image.twrp also stuck on start image.read from 1 user from indonesia.he also have this symtom and the mi technician said ic cpu got damage.so guys.whether u have to change motherbod or buy new phone its up to you.but i suggesting buy a new phone.move on..changing mother price is u can get new phone with better chipset.hope this will known to other user that have this problem.i also don know what to call this phone symtom.. hardbricked faker?.fyi i already oder note 9s.but i really love reno5 huhu.so sad it cant be fix.

Same happened to me last week, tried all methods like OP but no luck so gave up and ordered redmi note 9 pro (64mp). But i miss my rn5 pro so much ?
Probably emmc or cpu got corrupted for no reason, shame on you xiaomi but i couldnt give you up ?

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

Fastbootd missing

Hello everyone! So I have a OP7T 1907 TMobile variant, and I've been following this guide to convert it. I have done it successfully a long time ago. I went to update to android 11 and after a while my flashing stopped working, I finally figured out the problem. I was getting the error. "fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
I was stuck here for a while so I deleted the adb folder and went to bed last night. I woke up and it suddenly was working again. I tried to update to Android 11 and it bootlooped my phone, I tried to reflash but I had already relocked the bootloader, and the command "fastboot flashing unlock_critical" would return the error I had to flip the enable oem unlock switch. So I plugged into the MSM tool and hit start. I am now stuck at the same fastboot error. Any ideas?

After trying a bunch of different stuff, flashing the international rom and it stopped. I guess that put back some files that I was missing. I was then stuck with the tmo splash screen that goes nowhere, I then restarted and I finally go to the fastbootd screen. I wiped all data. After that fastboot reboot fastboot worked, idk if I just once again got lucky or not. But It worked

having same problem, can anyone explain how to enable fastbootd for oneplus 7t indian variant?

You need stock recovery (not twrp, los recovery, etc) for fastboot reboot fastboot to enter fastbootD mode (looks like stock recovery mode with 2 lines of Chinese and 1 line of English)

HueyT said:
You need stock recovery (not twrp, los recovery, etc) for fastboot reboot fastboot to enter fastbootD mode (looks like stock recovery mode with 2 lines of Chinese and 1 line of English)
Click to expand...
Click to collapse
Not entirely true, though.
Both LOS recovery (like the one from StatixOS or Pixel Expierience) and TWRP (the unofficial 3.5.1_10) have working fastbootd.
I don't think the same can be said about the Chinese TWRP, or mauronofrio's version, however.

Good 2 know. Thanks

open platform tools zip (fastboot&adb) place everything you want to flash in same folder as open zip (it can be whole payload extracted) and that will fix fastboot error

ecompton59 said:
open platform tools zip (fastboot&adb) place everything you want to flash in same folder as open zip (it can be whole payload extracted) and that will fix fastboot error
Click to expand...
Click to collapse
I don't think this is true.