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....
Related
hi, i have a trouble wit a l9II d605 phone, it is dead, in hs-usb qdloader 9008.
i tried with BoardDiag3.99c, but this model not are supported by this software, the phone chipset is msm8230.
can somebody help me and add support for this model?.
i tried with l7II msm8225 model in the software but doesnt pass the ap check.
thanks and sorry for my english.
in this post fix a g2 phone with boarddiag: http://forum.xda-developers.com/showthread.php?t=2933830
zesped said:
hi, i have a trouble wit a l9II d605 phone, it is dead, in hs-usb qdloader 9008.
i tried with BoardDiag3.99c, but this model not are supported by this software, the phone chipset is msm8230.
can somebody help me and add support for this model?.
i tried with l7II msm8225 model in the software but doesnt pass the ap check.
thanks and sorry for my english.
in this post fix a g2 phone with boarddiag: http://forum.xda-developers.com/showthread.php?t=2933830
Click to expand...
Click to collapse
Well if you can't access download mode you are pretty much done. There are some files you can't make most likely to unbrick it.
neutrondev said:
Well if you can't access download mode you are pretty much done. There are some files you can't make most likely to unbrick it.
Click to expand...
Click to collapse
Still no solution to fix this?????
There will be no solution to fix until someone makes the files for it. I don't have this device so you are out of luck. I need this device in hands to make files for it. Sorry.
neutrondev said:
There will be no solution to fix until someone makes the files for it. I don't have this device so you are out of luck. I need this device in hands to make files for it. Sorry.
Click to expand...
Click to collapse
You mean hex and mnb file? If yes than is quite sad, i searched all over internet, there is no one who have them. Im trying to fix it in linux using this thread http://forum.xda-developers.com/showthread.php?t=2582142
But no luck yet, because cant get any sdb after i type ls /dev/sd*, dont know where is problem because ubuntu recognise qualcomm qhsusb., soo im stuck here for now....
st_87 said:
You mean hex and mnb file? If yes than is quite sad, i searched all over internet, there is no one who have them. Im trying to fix it in linux using this thread http://forum.xda-developers.com/showthread.php?t=2582142
But no luck yet, because cant get any sdb after i type ls /dev/sd*, dont know where is problem because ubuntu recognise qualcomm qhsusb., soo im stuck here for now....
Click to expand...
Click to collapse
Dude listen to me I told you it is useless to try ANY other method. That method you are saying with linux works in mode 9006 which is partition access. 9008 = hardbrick. You need way more than HEX programmer you need partition layout and also mbn. If you don't know how to make those there is NO WAY. Sorry.
EDIT: Also JTAG works. So go to someone that JTAG devices. A service or do it yourself if you have Medusa, RIFF Box and knowledge in soldering.
LG D605 HARD BRICK (How to build eMMC flash programmer MPRGXXXX.hex and msimage.mbn): http://forum.xda-developers.com/opt...lg-d605-hard-brick-how-to-build-emmc-t3318824
First of all, sorry for my bad english. My problem started when i deleted accidentally one partition of the tablet, trying to make an working twrp for it. Now I have no adb commands, no recovery, no fastboot,no logo,no display light. Nothing works. Just an expensive brick. PC only see something like "diagnosis 900E, instead of USB QDLoader 9008,so QFIL can do nothing to fix.I have changed driver,now can be seen QDLoader but QFIL gave me errors. I just bought another tablet, same model, for my son. I will try to pull out system, recovery, boot etc. But after that...? Any chance to make an bootable microSD card with those files? Any advice please?
Costi979 said:
First of all, sorry for my bad english. My problem started when i deleted accidentally one partition of the tablet, trying to make an working twrp for it. Now I have no adb commands, no recovery, no fastboot,no logo,no display light. Nothing works. Just an expensive brick. PC only see something like "diagnosis 900E, instead of USB QDLoader 9008,so QFIL can do nothing to fix.I have changed driver,now can be seen QDLoader but QFIL gave me errors. I just bought another tablet, same model, for my son. I will try to pull out system, recovery, boot etc. But after that...? Any chance to make an bootable microSD card with those files? Any advice please?
Click to expand...
Click to collapse
So use ZTE tool studio emmc tool to unbrick your android.
Follow guide of Androidbrick.com.
The tool posted on these site is actually a ZTE tool studio tool by name of Androidbrick tool.
Just Google and download it from torforum.org
Already tried,not working.I cannot swich phone in download mode
Costi979 said:
Already tried,not working.I cannot swich phone in download mode
Click to expand...
Click to collapse
These tool unbrick your android when no fastboot, no recovery, not booting by anyways. Just detects in 9008 port. I am sure it's better than Qfil.
That`s the problem with port detection
How does this happened ?
Hello Costi979,
Sorry for your tablet, I hope you will find a solution
I wanted to know if this happened when trying to install TWRP on this tab2 10-30 tablet, under Android 6.0.1, like explained in this thread : http://forum.xda-developers.com/android/development/recovery-lenovo-tab-a10-30f-l-twrp-3-0-t3442588 ? Can you confirm that it does work or not ?
Thanks for your explanations,
I hope you will success to recover your tablet,
Regards,
Sebastien
Barnabe02 said:
Hello Costi979,
Sorry for your tablet, I hope you will find a solution
I wanted to know if this happened when trying to install TWRP on this tab2 10-30 tablet, under Android 6.0.1, like explained in this thread : http://forum.xda-developers.com/android/development/recovery-lenovo-tab-a10-30f-l-twrp-3-0-t3442588 ? Can you confirm that it does work or not ?
Thanks for your explanations,
I hope you will success to recover your tablet,
Regards,
Sebastien
Click to expand...
Click to collapse
Sorry if u have issues to. My problem started when i erased via adb one partition . Twrp works fine
Hello everyone!
I'm not good at English, so I'm sorry if it is difficult for you to understand my English.
I downgraded from Andoroid 6 to Android 5.1 using LGUP.As a result, when turning on the power of v 10, the power will be turned off after the LG logo appears.I wasn't able to enter the download mode.
It is recognized as Qualcomm HS-USB QDLoader9008 now.
Please tell me how to fix it.
mr.bushido252 said:
Hello everyone!
I'm not good at English, so I'm sorry if it is difficult for you to understand my English.
I downgraded from Andoroid 6 to Android 5.1 using LGUP.As a result, when turning on the power of v 10, the power will be turned off after the LG logo appears.I wasn't able to enter the download mode.
It is recognized as Qualcomm HS-USB QDLoader9008 now.
Please tell me how to fix it.
Click to expand...
Click to collapse
Yes there is a chance to fix your probleme by Sdcard dump look in the section lg v10 you find article how to proceed.have a nice night
magma506 said:
Yes there is a chance to fix your probleme by Sdcard dump look in the section lg v10 you find article how to proceed.have a nice night
Click to expand...
Click to collapse
Thank you.
I probably saw the article.
↓
https://forum.xda-developers.com/tm...ent/debrick-phone-h901-qualcomm-9008-t3440359
But I do not have dump.img of H961n.
I could find dump.img of H901.
I want dump.img of H961N. . .
pls can tell me what you do ihave h916n brocked
please i want to know if there is any update happened with you because i have also h961n and i cant find the image file
i tried to extract the rom into many .bin files but which file i should take to burn on the SD card
please this is my email: [email protected]
and facebook : the.amr.world
let me know if you have any new and off course me too i will inform you
LG H961N - Qualcomm HS-USB QDLoader 9008 Mode
mr.bushido252 said:
Thank you.
I probably saw the article.
↓
https://forum.xda-developers.com/tm...ent/debrick-phone-h901-qualcomm-9008-t3440359
But I do not have dump.img of H961n.
I could find dump.img of H901.
I want dump.img of H961N. . .
Click to expand...
Click to collapse
I have LG H961N, I tried the link mentioned. I used Samsung 32GB SD card, flashed H901 disk image (this seems to be a DD image, checked using Rufus). With the battery plugged in, the phone would turn on after 10mins and all I see is just the LG logo screen and nothing happens after that. I couldn't get it in download mode as it takes 10mins to get to the LG logo screen. Once I get the LG logo screen, I see "LGE androidnet usb serial port (com no.)" in the device manager. I tried LGUP, where the device type couldn't be identified for further process. Same thing with LGNPST, QFIL doesn't help. I wonder if the SD card should be 64GB as the disk image shows 58.24GB size in Windows Disk Management utility.
EDIT: Fixed with unbricking service. No other way AFAIK. The error is caused by flashing to US998 20d from V300L 21k. Another user ran into the same error flashing from V300 21 to H930 20. So I guess the takeaway is to be careful when downgrading.
So I think I messed up and now my phone is stuck in UEFI crash (text screen with "LGE crash handler: UEFI crash"). It keeps bootlooping and I can't even turn it off.
QPST says it's in download mode when I plug it in.
Any chance I might be able to fix this?
Picture of the error screen attached
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
sandking707 said:
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
Click to expand...
Click to collapse
I've been messing with QPST but of course there isn't much I can do as-is.
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
sandking707 said:
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
Click to expand...
Click to collapse
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Read some other threads, there was a mention of a built in fastboot in the PBL but that seems to be untrue.
Maybe this isn't the PBL considering screen is working and there's LG branding.
I've also heard of a recent exploit for SD chipsets, something about the PBL's signature verification. If this works for the firehose, then maybe someone can modify an existing firehose to adapt for the V30, this way a leak won't be necessary. Though if anyone will bother is another matter.
seloka180 said:
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Click to expand...
Click to collapse
edit:
my device solved with jtag in repair shop.
Sent from my LGM-V300S using XDA Labs
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
test point lg v30
Duo8 said:
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
Click to expand...
Click to collapse
there are two golden points near the ribbion of battery but not the big ones under the ribbion wehen you connect both the phone will go 9008 mode
i am stuck in the very same situation as OP please if anyone has any way or idea on fixing this issues let us know and so others can benefit from it as well
thanks
Sahara mode LG v30, please help!
Hello there,
my lg v30 us998 was 10% battery. I was browsing the web and suddenly it freezed up. I cound´t do nothing until it shut down itself after a few minutes. I plugged in to the charger and the same message showed: UEFI crashed. Sahara mode... Any help please?
Not sure if it is actually possible for me. Still no solution. I was waiting for a more complete reply ...
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.