Hi all,
A few weeks ago my LG G4 started bootlooping. (I've heard this is a common problem with serial numbers starting between 505 and 509 - mine is 505...) I heatgunned the chips under the shields on the back of the mainboard, but all that did was break it even further; now it won't even turn on! BUT, the computer recognizes it first as QHSUSB_BULK, then as Qualcomm HS-USB QDLoader 9008. I also tried the freezer method, but that did neither harm nor help. Is there any hope for this phone? Thanks in advance.
xaresys said:
Hi all,
A few weeks ago my LG G4 started bootlooping. (I've heard this is a common problem with serial numbers starting between 505 and 509 - mine is 505...) I heatgunned the chips under the shields on the back of the mainboard, but all that did was break it even further; now it won't even turn on! BUT, the computer recognizes it first as QHSUSB_BULK, then as Qualcomm HS-USB QDLoader 9008. I also tried the freezer method, but that did neither harm nor help. Is there any hope for this phone? Thanks in advance.
Click to expand...
Click to collapse
Check my signature for the bootloop fix list. Also read at the bottom what your current issue means..
Related
HTC Desire 510 D510n BRICKED(just like a brick) Solution?
Just received an Htc desire 510 D510n Completely dead.When Connected on pc, it s detected as HS-USB QDloader 9008 After drivers it shows as NOKIA EMERGENCY CONNECTIVITY.
NO vibration,no light no temperature phone clean.
I ve no history with the phone.
Any similar case here?
TX
You are bricked. No hope. Possible j tag but for the price just get a new phone. Sorry! That particular thing is a bad board or something of that nature. I would take out battery and put back in and try booting to recovery. Hold volume down and home for several seconds and see what happens. If you get somewhere from there you have a bad board most likely. Qdloader is not recoverable for cheaper than the phone is worth. Hope this helped and let me know if you have questions.
Edit. I'll go through my stuff later and see if I have anything that might help. This phone is so new it's not likely a lot to do.
Good advice.
Phone is new, i ve now bought it from the client,locked it in my safe for spares.
it need jtag fix.... 90% is hardware problem
Hellow fellows, so recently I've received HTC Desire 500 which I thought I could use as my secondary phone. However, the phone is bricked to the point where only LED flashes repeatedly when charging. But I found out that my computer can actually see the phone's chipset when plugged in through USB, which means there is a possibility to save it, right? So I started looking on the forums for the hex or xml file which contains the.. well.. "blueprint" to use in QPST to flash the software. Unfortunately my search results came out negative, so I thought if I could try to make my own blueprint and try to restore my phone to its functioning state, I don't mind if the phone is reset to the original state, that's actually what I want. All help is appreciated! If I can't do anything else, then I guess repair services is the alternate option.
Hello, my 2 month old S21 Ultra randomly decided to brick itself and won't turn on. When I plug it into my PC it's detected as Qualcomm HS-USB QDLoader 9008 (COM5). How do I fix this?
contact samsung or your carrier if you got it from them for warrenty repair
NotProton said:
Hello, my 2 month old S21 Ultra randomly decided to brick itself and won't turn on. When I plug it into my PC it's detected as Qualcomm HS-USB QDLoader 9008 (COM5). How do I fix this?
Click to expand...
Click to collapse
model and bootloader version?
This is extremely common - even without modifications - on the whole S21 series. There have been tons and tons of posts here about devices failing after no damage or anything... And, unfortunately, mine is starting to fall into the same boat right now as I generally have to restart it about 5-6 times PER DAY to have it keep working.
Mine has been kept up to date, hasn't been modified, and has been kept under great temperature control without any beefy/non-heat dissipating cases.
So all in all, do exactly what @jerrycoffman45 said and get a warranty repair ASAP! As supposedly (someone else said this in another post), Scamsung is starting to decline some of these device repairs which (I imagine) are primarily due to their own manufacturing mistakes. So get it fixed while you can and hopefully Samsung agrees to help you out. As after running through this issue, I'm never buying another crummy Samsung device ever again lol. I've made a huge mistake getting the S21U...
I think the tendency to install too many apps - most of which are useless data rapers you probably don't use and making too many tweaks will increase the likelihood of your phone going bonkers. Overcome the urge to do these things.
Hello all,
I've hard-bricked my OPO3T. Attached 2 files: the OPO3T motherboard and a screenshot of the PC Devices.
Basically, what I've done was formatting it from scratch using the MsmDownloadTool, as I've done many times before.
Don't know how, but after a "successful" flash, the phone gave no vital signs (no display, no leds, no vibration, no hope).
From that moment, the PC recognized the device as "Qualcomm HS-USB Diagnostics 900E" instead of "Qualcomm HS-USB QDLoader 9008".
I've tried many things, passed a good amount of time googling and searching and watching YT videos about it, but found no solution to the problem.
I've also used a borrowed Windows 7 PC as someone suggested on Oneplus Forums, but same result. The device is recognized as HS-USB Diagnostics 900E.
In my google research, I've found that, for Xiaomi devices, there is something called "test points" and a "DIY EDL cable" to overcome the Qualcomm 900E problem. But find nothing about the OPO3T.
I'm not an expert, but I assume that the OPO3T motherboard is not "broken", but entered in a state where it will not be willing to talk anymore via the "normal" protocol (pardon my pseudo-tech-ish assumptions), but expecting to talk to the PC in another way.
I've tried to open the OPO3T to find "spots" on the motherboard, without any other knowledge, to find hints of something similar, but (obviously) find none.
So, I'm asking to the community ... can I solve in any way this problem? Motherboard hack? DIY cable? Anything?
Thank you very much
you find a solution? My asus zenfone 8 flip entered ramdump mode basically hard-bricked randomly and now its recognised as 900E on device manager haveno idea what to do
900E mode isn't a full hard brick. It's a semi-brick
Master Santa said:
900E mode isn't a full hard brick. It's a semi-brick
Click to expand...
Click to collapse
Hello,
thank you for the good news.
Do you have any idea how to resolve this problem?
I'm not sure how useful this tool will be but I stumbled upon this https://github.com/bkerler/edl
You may be able to get your device recovered from it
Also to get into EDL mode try some of these combos:
Method 1:
Keep your device plugged in and press vol+ and vold- simultaneously as well as power... Once the device is off release power while still holding the volume buttons... Usually for most devices (like mine) this will throw it into EDL
Method 2:
Try the above, but with just one of the volume keys pressed and maybe you'll be able to get it into EDL
Method 3:
If you have a spare cable for your Android cross D+ with GND and make yourself a deep flashing cable to send the device into EDL or check for test points on your device
Hi all,
I've found a lot of information on this happening to Pixel 3's a while ago, but not as much out there for samsungs.
My S20 FE black screened yesterday and wouldn't reboot. When plugging into a computer it shows up as Qualcomm HS-USB Qloader (now that I have the drivers installed for it)
Is there anything I can reasonably due to unbrick this? EDL.PY does recognize my phone, but I also can't seem to find the firehose files that may or may not exist for the s20.
why F around, it could be a failing component or a bad connection on the board. get it looked at.