Develop Bugs

Hard bricked...Need a solution :(

Hello,I recently flash a wrong file and now my device is straight up dead no logo nothing the led blinks for a mini second and turns off I tried using qfil and mi flash but it was getting detected as 900e port and wasn't even detected on mi flash I tried updating drivers and got it to 9008 but still it would get stuck forever when I hit download asap in qfil or would show some sahara port error and still no detection on mi flash even in 9008 mode I tried over 50+ times using the button combinations to get it to 9008 mode but every time it would be 900e any solution other than deep flash as I have just one type c cable and I may screw up

Press volume up key for 15 seconds, then press power button & insert usb (within a second) to pc..it will get it to edl mode..

probably your only way out is deep flashing, i've been through this

any solution for this ? i'm suffering the same

Any way to enter in EDL mode?

Hi im still can't unlock bootloader, anyway to enter in EDL mode?:crying:

2 Ways:
-Bricking your device on purpose (Not recomended, I discover this flashing a custom ROM on My Wife's phone without copying AB partitions.)
-Strpping a USB cable and joining D+ (Green Wire) and GND (Black Wire) for at lease 30 seconds until your phone forces EDL mode on itself and your PC detect the device as Qualcomm 9008
I hope this could be useful to you and to anyone.

Doesn't stays on edl mode

When pressed volume up and down key together and connected to pc it shows charging symbol then appears in my pc as qualcomm 9008 port then reboots .I'm trying to flash my device using qfil which needs phone to be in edl mode and my phone is not staying at edl mode so I can't flash it .Any advice will be really helpful.

Oneplus 7T bricked in EDL mode (Firehose GetUsInfo Failed)

I was using my oneplus 7T normally without root and with bootloader locked when it decided, out of nowhere, to fall into "Qualcomm Crashdump Mode". When I tried to reboot it, it just went into "Qualcomm Crashdump Mode" again. So I went into fastboot mode, unlocked it, and flashed an european ROM from here: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T/ . However when the device tried to boot up it just went to "Qualcomm Crashdump Mode" again, so I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) ( https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/ ) and it worked, but this time when the device attempted to boot up it went into EDL mode and the bootloader was locked and when I tried to unlock it, it gave me an error related to "OEM unlock" not being enabled in developer options. So I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) again, and somehow this time it actually booted up. Still, after 10 seconds it went into EDL mode AGAIN (note: at this point, I couldn´t get out of EDL mode, I could only boot into anything else after the battery died, in the first boot). So I downloaded another ROM for msm but this time it gave me the error: Firehose GetUsInfo Failed, and the phone seems to disconnect and reconnect. From here I tried multiple ROMs for msm and always received the same error, even using the one I used originally. (Note: I have been waiting for my battery to die for 5 days, and it still has power; also tried removing the battery )
Output when trying to use EDL-master:
edl.py printgpt
Qualcomm Sahara / Firehose Client (c) B.Kerler 2018-2019.
__main__ - Trying with no loader given ...
__main__ - Waiting for the device
__main__ - Device detected
__main__ - Mode detected: sahara
Device is in EDL mode .. continuing.
Library.sahara -
------------------------
HWID: 0x000a50e100514985 (MSM_ID:0x000a50e1,OEM_ID:0x0051,MODEL_ID:0x4985)
PK_HASH: 0x2acf3a85fde334e2e28d64cbc416b2474e0e95cad4698f143e27479d67e92d99
Serial: 0xb0180648
SBL Version: 0x00000000
Library.sahara - Couldn't find a loader for given hwid and pkhash
Commands I tried to unlock bootloader:
fastboot oem unlock; fastboot oem unlock-go; fastboot flashing unlock; fastboot flashing unlock_critical
Can someone help me with this issue?
Sorry if the description was too confusing, long, or had any mistakes in terms of English. I am just trying to be as complete as possible.

The same arround here.....
Any solution?

Sounds like hardware failure (memory ram chips). Buy a cracked 7T and swap motherboard

First of all thank you for replying! I really appreciate it. Second of all, I did some research considering your reply and I stumbled upon this post: https://forum.xda-developers.com/t/oneplus-6-possibly-soft-bricked.4297489/ . What I did after seeing it was, I vacuum sealed my phone in a bag (to minimize condensation) and place it in the freezer for about 20 minutes I tried booting up the phone but it just went into edl mode again. However this time when I used MSM download to it actually was able to complete the whole process. The phone still didn't boot, but now I can enter fastboot and recovery. All this leads me to conclude that you are right.

Moto G Fast (XT2045-3) no power (not even EDL) after blankflash

EDIT: My new problem is that the device no longer powers on after performing blankflash; see post 3+
Hello, I have a Moto G Fast (XT2045-3) that I tried to downgrade to Android 10 after it already had 11 (and didn't realize the bootloader had rollback prevention even after being unlocked) and got the dreaded "black-screen-of-death."
After cracking open the back cover and shorting the two pins to force EDL mode I am now at least successfully seeing the "Qualcomm HS-USB QDLoader 9008" in device manager which tells me I should be in EDL mode. (NOTE: I have done some some work on a different Qualcomm device months ago that was successful so I'm pretty confident that my EDL drivers are correct/working)
EDIT: I now know that Moto devices don't use QFIL and instead use blankflash with qboot -- leaving the rest below for reference
My problem now is that QFIL wants a "rawprogram*.xml" and "patch*.xml" that I can't seem to find. After some digging I was able to find a firehose MBN for the SM6125 on some other XDA thread for the Redmi Note 8 because I wasn't able to tell if the bkerler github actually had the firehose as it wasn't obvious to me based on filenames. Because of that I'm not fully 100% confident that I know I have the correct firehose, either.
I have yet to find the appropriate xml files that QFIL is asking for. Either that or I don't fully understand how to flash without those and just using, for example, the contents of the stock firmwares on the lolinet mirror. In QFIL if I try to do anything, all I get is "Sahara Fail" -- even when trying something as simple as "Tools" -> "Get Flash Information"
Can anyone let me know where I can get the QFIL special files (or a compatible firmware zip that contains them)? Alternatively, if there is some way to flash the lolinet stock ROMs in EDL mode that doesn't need those QFIL xml files please let me know. My digging hasn't given me any specifics if that's possible and I'm quite inexperienced with QFIL in general anyway.

Follow-up:
I've also tried blank-flash.bat as I've seen suggested elsewhere but it also fails at the beginning to even see the device:
.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.001] Opening device: \\.\COM6
[ 0.042] Detecting device
[ 34.713] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.713] Check qboot_log.txt for more details
[ 34.713] Total time: 34.714s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
Contents of qboot_log.txt:
**** Log buffer [000001] 2023-02-11_10:25:12 ****
[ 0.001] Opening device: \\.\COM6
[ 0.042] Detecting device
[ 34.713] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.713] Check qboot_log.txt for more details
[ 34.713] Total time: 34.714s
[ 34.714]
[ 34.714] qboot version 3.86
[ 34.714]
[ 34.714] DEVICE {
[ 34.714] name = "\\.\COM6",
[ 34.714] flags = "0x64",
[ 34.714] addr = "0x62FD54",
[ 34.714] api.bnr = "0xF336B0",
[ 34.714] }
[ 34.714]
[ 34.714]
[ 34.714] Backup & Restore {
[ 34.714] num_entries = 0,
[ 34.714] restoring = "false",
[ 34.714] backup_error = "not started",
[ 34.714] restore_error = "not started",
[ 34.714] }
[ 34.714]
Click to expand...
Click to collapse

So, yet another follow-up. I've since learned that the Moto 'blankflash' is supposed to be the entire process that QFIL would be doing for other phones and that I shouldn't need QFIL or it's xml files.
I was able to get the blankflash to work once by starting it seconds after the phone showed up in device manager as the EDL qualcomm driver. Maybe there was a timeout delay issue from me not trying it right away or maybe I got lucky after several attempts. The blankflash completed in what seemed to be a successful manner.
After the blankflash script ran, however, I can no longer get the device to respond in any way. If I didn't know better I'd say it's not powering-on at all. The vol up or down plus power don't produce any vibration or anything on the screen and `fastboot devices` and `adb devices` show no results. What's worse now, though is that the same two test points on the board behind the back cover that I was using to enter EDL mode now also don't seem to be working. before the blankflash I was able to enter EDL consistently every time but now I can't get it up at all. I try unplugging the battery to make sure it's off first; I've left it plugged in to a charger overnight; I've tried with the screen connected and disconnected... no combination of anything I've tried gets the device to do anything anymore. Not EDL, not Fastboot, nothing on the screen, etc.

Using this space to document what I've tried for my own records and also in case anyone is able to give advice (or if the device is DOA).
All operations were tried multiple times, with multiple different USB cables and different USB ports on the PC. All of those ports and cables were all tested working for other devices. Anything where I say I held it was tried with varying lengths of time, usually 20-30 seconds. For each of these tests I had device manager open and sections expanded to see if/when any new device is recognized and so far nothing has even shown up once in device manager nor on the device's screen. That is, not since after I flashed the blankflash -- it used to work and enter fastboot/EDL etc but ever since flashing blankflash it seems to not even be powering on.
"Off state" means I disconnected the battery ribbon cable for 10+ seconds before starting the next step.
"Jump EDL testpoints" means shorting the two pads on the mainboard that successfully worked for me on this device in the past to get it into EDL mode
Off state -- Hold VolUp+Power -- Plug in USB while still holding down
Off state -- Reconnect Battery -- Hold VolUp+Power -- Plug in USB while still holding down
Off state -- Hold VolUp+Power -- Plug in battery ribbon while still holding -- Plug in USB while still holding down
These were also repeated with VolDown+Power, Just VolUp, Just VolDown and Just Power
Off state -- Jump test-points -- Plug in USB while still holding test points
Off state -- Reconnect Battery -- Jump test-points -- Plug in USB while still holding test points
Off state -- Jump test-points -- Reconnect battery while still holding test-points -- Plug in USB while still holding test-points
These were also repeated with including the button combinations alongside the test-points each time as well
I tried letting the device sit with the battery unplugged overnight (12+ hours) and repeating the tests after that, and I've also tried letting the device stay attached to a charger for 24+ hours before repeating the tests as well. I've attempted all of these tests at least once with the screen's ribbon cable disconnected and at least once with it connected.
All-in-all I've probably made almost 100 attempts after the blankflash to get the phone to do anything at all without success.
I'm now wondering if there is a simple way to measure voltage on some points on the board to see if it's even powering up at a basic level or not.