LG D820 (Nexus 5) Hard Brick - Need help, guys! - Android Q&A, Help & Troubleshooting

Hi!
I have nexus 5 (d820)
I've replaced battery and in a time EMMC. But the problem still remains.
The problem:
Before now the phone was continuously rebooting on an on. It does not depends what app I'm in or where I am in OS. But now it's comletely brick) And it doesn't want to boot.
So I have QHSUSB_BULK in device manager and have installed drivers. Now I have Qualcomm HS-USB QDLoader 9008 there. Then I used BoardDiag software and got broken sectors (when writing laf.mbn, boot.mbn, tz.mbn)
rgho.st / 8zDGFMtd4 (Admins, please allow me to post the link here)
The questions:
1. Can I get it working? However I really like nexus
2. Can I may be remap sectors?
3. Can I at least recover my files?
Thanks in advance, people)!

Related

Hardbricked G2 Mini (Qualcomm HS-USB QDLoader 9008)

Long story short. The phone had a problem with the download mode update. I tried flashing one KZ file (or what the extension is) and Download Mode completely locked up mid update. As in, animation died and the screen was frozen. Pulled out the battery... Download Mode stopped functioning entirely and now I was having this Secure Boot error that was popping up each time I would start the device. Tried a few guides to fix it myself... (long story short, the phone wouldn't boot up, it would just allow me to access all the partitions however, I would have a secure write thingy to pass, so I had 0 access to the phone) and had 0 success with the fixing process.
Today I got mad. Connected the phone again... tried something again, it didn't work. I launched diskpart on CMD. Selected the phone's volume. Typed "Clean" and... here we are. The phone doesn't even have a name anymore (before it had LG G2 Mini regardless of it's state), it just shows up as "Qualcomm HS-USB QDLoader 9008 (COM4)". And from my knowledge... that's a really hardbricked device. Now... I am asking everybody who has more advanced knowledge with this device. Please help me. I know there's programming to do now and several other things here but I beg you... Please guide me and/or help me.
Note: The device doesn't even turn on it's own display. It just connects with that name once it's plugged into the PC. I read a few articles about this... still very clueless as to what I'm supposed to do. @mobiusm Any advice?
Model variant: D620
Does diskpart see the memory chip?
If it does, then I can tell you how you might be able to fix it.
Vagelis1608 said:
Does diskpart see the memory chip?
If it does, then I can tell you how you might be able to fix it.
Click to expand...
Click to collapse
Nope. Sadly, it only gets detected on it's COM port. Diskpart comes back null as well as disk manager doesn't display a storage solution connected.
What OS is your PC on?
Linux might help.
On the l90 forum there is a guide on how to make the phone enter 9008 mode (requires disassembly ofthe phone). It might work for the g2m as well. Just need to check where the Qualcomm test point is.
Good luck!
Vagelis1608 said:
What OS is your PC on?
Linux might help.
Click to expand...
Click to collapse
Windows 8.1 but I also have Ubuntu installed on a VM.
mobiusm said:
On the l90 forum there is a guide on how to make the phone enter 9008 mode (requires disassembly ofthe phone). It might work for the g2m as well. Just need to check where the Qualcomm test point is.
Good luck!
Click to expand...
Click to collapse
The phone is already in 9008 mode tho.
fogoticus said:
Windows 8.1 but I also have Ubuntu installed on a VM.
The phone is already in 9008 mode tho.
Click to expand...
Click to collapse
Does diskpart see the memory chip?
Or it's Linux counterpart (fdisk, I think)?
Vagelis1608 said:
Does diskpart see the memory chip?
Or it's Linux counterpart (fdisk, I think)?
Click to expand...
Click to collapse
Nothing is detected. Other than the name... nothing appears anywhere be it Windows or Linux.
From what I read, it's not dead. It just needs low level code injected, to be partitioned and so forth....

Bricked Samsung S III SGH-I747 (AT&T

Hello all.
I found my old Samsung S III SGH-I747 (AT&T) that I had hard bricked many years ago. The phone won't turn on at all. Can't get into recovery mode or download mode. Just a black screen and the charging light will turn on. I plugged it into my PC to see if I could fix it and too my surprise it came up as Qualcomm device (Qualcomm HS-US QDLoader 9008) in device manager. I found a program called QFIL that also detects it as a Qualcomm device.
Does anyone have or know where to get the proper files to to fix this issue? This QFIL program needs a .mbn file and a .xml file.
If anyone has any other ways that could possibly fix this issue please let me know.
In all honesty I think its buggered and stuck in the state before the factory flashes the os. How you get out of it.. I dont know.
This may help: https://forum.xda-developers.com/showthread.php?t=2525902
AT&T s3 forum is here: http://forum.xda-developers.com/galaxy-s3-att

hard-weird-bricked phone

Hello guys,
I have an ASUS ZB501KL which is hard-bricked and, when I plug it on PC, it shows up ONLY as Qualcomm HS-USB QDLoader 9008, no eMMC storage or something like that, just the COM Port. Nothing weird (I guess), right? The weird fact is: EVERY-SINGLE-TIME the device is plugged in, my PC hangs and after minutes (generally 5-10) crashes.
I've tried to change USB Port: nothing
I've tried to disable the driver signed verification: nothing
I've tried to run in Safe Mode: NOTHING - device keeps disconnecting and reconnecting
I've tried to install drivers which have a digital signature: NoThInG
I've tried to use other PCs and other Operating Systems: the same problem
I don't know what else I could try to make my device recognized and possibly my PC hangs/crashes-immune, so if you guys have any suggestions I would really appreciate them.
P.S.: in Device Manager, when I click on driver properties, it shows the event "Device configured (null)"
First, It might be the PC itself that is causing the crash.
And you are lucky that got that COM port.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
Peak.Krittin said:
First, It might be the PC itself that is causing the crash.
And you are lucky that got that COM port.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
Click to expand...
Click to collapse
Thank you for your reply, I really appreciate it.
I've downloaded the BoardDiag tool and it says: "partition.txt does not exist. Please extract the file from the total binary image."
Apparently I need a .tot firmware, which is LG specific, and I don't know if there are ASUS ones. I have a QFIL compatible firmware and another one called singleimage.bin, but they don't contain the file partition.txt.
By the way, my chip is a Qualcomm MSM8x26 and, regarding my PC, it seems that there are problems with my Generic USB Hub because I have too many devices attached for only 500mA of power.
Now, I don't know how to remove them, because when I uninstall their respective drivers, once I restarted the machine, they magically reappear as USB Composite Device (500mA) and Generic Bluetooth Adapter (100mA).
Also, BSOD Crash Dumps have to do with the file ACPI.sys and the error is: DRIVER_POWER_STATE_FAILURE
Yeah, I know that this will probably become an Android ft. Windows troubleshooting topic, but we are here now.
Thanks for your patience.
For me, Xiaomi devices can flash by that com port (aka EDL mode).
If you are lucky enough you'll figure it out!
btw did you got device firmware?
Peak.Krittin said:
For me, Xiaomi devices can flash by that com port (aka EDL mode).
If you are lucky enough you'll figure it out!
btw did you got device firmware?
Click to expand...
Click to collapse
I think there is a misunderstanding, because you are talking about Xiaomi devices.
I have an ASUS ZB501KL and it is in a sort of "infinite EDL mode". Let me explain: my device goes automatically in EDL mode, even if I unplug and replug the battery, so I do not need any combination of buttons.
I'm starting to think that there may be some eMMC-related problems, because I've probably messed up the block 0 in some way.
Anyway... the biggest problem is still the BSODs I get when I connect my phone in the USB port, and if I boot my machine with the phone plugged it freezes and doesn't even load the BIOS.
nono, it's just an example
Oh, ok. So, is there any eMMC diagnostic tool which is compatible with MSM8x26 devices?
I'll take a look for ya.
Hi maybe you can try something similar to my post
https://forum.xda-developers.com/android/help/asus-fonpad-7-fe170cg-bricked-stuck-t3740819
Download Official firmware first but look for old version for your Region:
https://www.asus.com/Phone/ZenFone-Live-ZB501KL/HelpDesk_BIOS/
Look if there is archive ipsw or something like that inside stock firmware which you need for xFSTK Downloader or download latest one .
rest you have in my post use then Raw firmware with Asus Flash tool .
https://www.beritahuaja.com/2018/01/download-firmware-asus-zenfone-live-zb501kl.html
If that doesn't help you try to flash boot.img , recovery.img and system.img with ADB & Fastboot command line (those files you can find inside your stock firmware , also try on another PC. Good Luck : )
Teddy Lo said:
Hi maybe you can try something similar to my post
https://forum.xda-developers.com/android/help/asus-fonpad-7-fe170cg-bricked-stuck-t3740819
Download Official firmware first but look for old version for your Region:
https://www.asus.com/Phone/ZenFone-Live-ZB501KL/HelpDesk_BIOS/
Look if there is archive ipsw or something like that inside stock firmware which you need for xFSTK Downloader or download latest one .
rest you have in my post use then Raw firmware with Asus Flash tool .
https://www.beritahuaja.com/2018/01/download-firmware-asus-zenfone-live-zb501kl.html
If that doesn't help you try to flash boot.img , recovery.img and system.img with ADB & Fastboot command line (those files you can find inside your stock firmware , also try on another PC. Good Luck : )
Click to expand...
Click to collapse
Hi, thanks for your reply.
Unfortunately, all of your possible solutions do not work in my case because, apparently, I wiped out the entire eMMC and there are no more partitions. I also installed usbdeview to see what is going on with my usb drivers, and I noticed that the "Qualcomm HS-USB QDloader 9008" device doesn't turn on (in order to understand each other: it has the red light), even if I disable the driver signature verification.
Reading some other topic I saw that is possible to boot a Qualcomm device directly from SD Card, is that true? Because, if it is, I could try to flash, I don't know, the bootloader I guess?
Let me know if it is possible and, why not, share some other solution which can help me to revive my dead phone.
Thanks for your patience.
Hi , I know that is possible to create cdc boot files inside sd card to boot your device but I'm not professional for that .
What you can try is to reconect your battery but you need to dissasembly your device.
Instruction How to do that.
https://www.youtube.com/watch?v=avf25E4p0qU
If that doesn't work maybe your battery is dead or hardware issue like emmc chip .
Good luck
Well... I tried the "boot from SD Card" method and it didn't work.
I don't think that the battery is dead, because when it is about to discharge a red LED light blinks for five seconds. Anyway... I'm still getting BSODs when I plug my device in the PCs' usb port(S), except Ubuntu which recognizes it as Qualcomm, Inc. Gobi Wireless Modem (QDL mode) instead of Qualcomm HS-USB QDLoader 9008. I don't know if that is the right driver and, if it is, how to work with it on a Linux distribution because as far as I know there is not a QFIL version for this OS.
If that could be helpful to find a solution: I've erased the entire eMMC using fdisk -d /dev/block/mmcblk0 in TWRP, maybe that's why PCs aren't able to read any data from it... and there is no way to recreate a partition table, apparently.

Lg G5 H850 won't turn on

Hello,
I have huge problem with LG-H850.
I need recover data from this phone.
LGUP can't find it, in device manager is HS-USB QDLoader 9008.
I tried use z3x, axiom process, another programmer for qualcomm and reballing of UFS chip but still nothing.
https://forum.xda-developers.com/lg-g5/how-to/bring-lg-g5-to-life-download-mode-lgup-t3565508 <- it doesn't work
in hydra is like here: https://forum.xda-developers.com/android/help/lg-g5-h850-qualcomm-9008-hydra-error-t4043329
I need make memory dump for data recovery.
Please for help, Regards

HELP, LG G2 HARD BRICK

I wanted to install the lineage firmware on my lg g2 phone, the instructions said to downgrade the bootloader version after I encountered a problem that the phone does not turn on; boot certification verify. What to do as quickly as possible I want to solve the problem, in other guides on xda the pictures or links are not working, the specific id of my phone LG G2 D802, sorry for my bad English. and i have black screen boot. help plz. thank you
I want to add that when connected to a PC, it is defined as Qualcomm hs-usb Diagnostics 9006
and create more disk about 10-13 and 1 disk have files
adb dont work . fastboot too . help plz

Categories

Resources