Develop Bugs

[Q] Broken from update to Lollipop (stuck in fastboot)

I've seen some other people with this problem, but there have been no fixes.
The problem is that the phone was updated to Lollipop. It worked for a little bit, but after a couple of minutes lots of programs started force quitting, and it eventually turned off.
When it turns on, it takes about 20 minutes, and then goes into fastboot mode.
If I try to get into download mode, it stays on download mode for around 15 seconds, and then it continues into fastboot mode. Windows does not recognize the phone in download mode, so I can't restore anything from there.
What I have learned then is that I need to flash the laf.img file, which I got from download the official firmware from LG's website by inserting my IMEI, so it's the right version, and then trying both fastboot flash laf laf.img, as well as fastboot
boot laf.img. The problem is that they both fail writing, but it's not just that command. I can't do fastboot erase recovery, or fastboot erase anything, only thing that works is fastboot reboot.
Does this mean that the internal storage is broken? Is there anything else I can do? I can execute fastboot commands, but it seems like I cannot write anything. The drivers seem to be working, as it's recognized as a fastboot devices, but it only says
? fastboot devices
All commands result in a error(failure or something like that. I've removed the SD card as well, as I heard that might cause problems. As far as I know, I need to flash the laf.img to get into download mode, and from there on can flash via kdz.
Help please? This kind of sucks..

When you write a command, does it show on the phone?
You might need to change the driver in device manager. Look for "Android", update driver, browse my computer..., let me pick from a list, and here you'll see 3 different drivers, what you want is "Android bootloader interface"

hi
Hi dear frends.
Its sad to know that all you guys cant go to download mode or facing security error or stuck in lg logo or in fastboot mode
And some guys stuck qhsuab bulk 9008
So the solution is here.
If you are unable to get into download mode then you need to force your g3 into qhsusb bulk mode by shorting the test point.
I will help u all guys.....
I will help u to unbrick ur any lg model wothout download mode or stuck in 9008 or anytype of problem.
Please let me know your problem in pm.

[Q] LG D855 stuck in fastboot cannot flash

Hello,
I have my LG G3 D855 bricked. When i power it on, I get the LG logo for about 7 min, and then it enters to fastboot mode. Download mode doesn't work. As soon as I plug the USB I get the following message:
EP1/out FAIL nfo=40 pg0=f855200
usb_read() transaction failed
fastboot: oops!
fastboot: processing commands
Whenever I try to erase or write in the partition, I get the following message:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
Can someone help me??

Sorry to say but your G3 is fully bricked

solution for no download mode, fastboot mode, qhsusb bulk mode , security error.
Hi dear frends.
Its sad to know that all you guys cant go to download mode or facing security error or stuck in lg logo or in fastboot mode
And some guys stuck qhsuab bulk 9008
So the solution is here.
If you are unable to get into download mode then you need to force your g3 into qhsusb bulk mode by shorting the test point.
I will help u all guys.....
I will help u to unbrick ur any lg model wothout download mode or stuck in 9008 or anytype of problem.
Please let me know your problem in pm.

Bootloader/Recovery problems...

Hi!
I recently bought an LG G4 from an online seller. The cell phone itself is working fine, but it has some problems. It is a refurbished model.
I will very much appreciate any help.
The cell phone is actually a F500L model (I checked it by looking at the motherboard), but in the software information it shows to be a model H81510h.
The phone is not rooted. But I believe that someone did it, changed the device's descriptions and then uninstalled it.
It is an android 5.1, but I cannot update using the update center. There it shows that it is already in the latest version.
In the developer settings, I try to enable OEM unlock, it activates for 1 second and deactivates automatically.
I try to do the hard reset, but when restarting to start the process, it presents an error "Secure booting error 1002".
I can activate USB debugging, it is recognized in ADB tools and I can send commands to it. But it does not start the bootloader with the command "adb reboot bootloader", and it presents the same error "Secure booting error 1002" if I try to send the command "adb reboot recovery".
I can activate the Download mode (by pressing the VOL UP button and inserting the USB cable), but it is not recognized by LGup (UNKNOW / COM5 H81510h), LGup does not let me work with it.
In the LG Flash Tool, it does not start the flash process, when it reaches "BIN CRC Check" it presents the error "Failed PreviousLoad0". (I already changed the port to COM41)
In LG Bridge, it is recognized as F500L and shows that there is an update. But when trying to update, it does the first steps, but after the download, when installing it gives an error and asks to start over.
I have tried to use UPPERCUT_1.0.0.0, without success.
I do not know what else to do...
Any help will be appreciated.

Motorola g7 play xt1952-1 BLANKFLASH PROBLEM

Hi, I have a problem with my phone motorla g7 play (xt1952-1). The phone is hardbrick and I can't find the right blankflash for it. When I run blankflash from other topics sahara error pops up, if when I run blankflash I reset the phone (power + volume up) then very long time the message "Waiting for firehose to get ready" persists until finally error pops up and I can only shut down the program. I need the correct file most likely, qualcoom I have installed and it appears as com** in device manager. Sorry for my poor language.

Hi. Check my post on Blank Flash, i have a Firehose prepped. All you have to do is drag the firehose into your BlankFlash folder and watch it do magic.

Thanks a lot of for your answer. Main problem is, when i run cmd and put your command "fastboot oem blankflash" i've got information about "waiting for any device". Any ideas how to resolve it? Phone is full bricked, cant do nothing except turn off/on (sound at pc and appear in device manager as a qualcomm hs-usb qdloader).

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.