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 ...
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
Hi I messed up with my LG G5, help needed ?
I want to tell u what i did until now.
I want to root my phone:
1. Unlock Bootloader.
2. Install TWRP
3. Messing around in TWRP becaus i dont finde the SuperSU files cause of encryption usw.
4. Want to Swipe all data and start all over again
5. bootet my device normaly and ther is just the Message "Your device software cant be checked for corruption".
I cant do anything now. I tried to factory reset the phone didnt work. The phone doesnt react to any CMD commands.
I cant enter the TWRP.
I used LG UP to flash the device but LG UP doesnt recognizes my phone correctly, neither in USB Download Mode or in the so calles status, where i just got the blackscreen with the Message"Your device software cant be checked for corruption".
Maybe you guys have a solution.
PS. Sorry for bad english
as long you can start into download mode, your device is not bricked.
this thread should help installing and using LGUP correctly.
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
you have a KDZ for install?
zebulon98 said:
as long you can start into download mode, your device is not bricked.
this thread should help installing and using LGUP correctly.
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
you have a KDZ for install?
Click to expand...
Click to collapse
Thanks i did that and it worked. Thx to you mate problem solved
LG G5 Bricked
Hi guys...
I messed my LG G5 up trying to flash t-mobile nougat kdz via twrp on my rooted 7.0 vodafone branded phone (i wanted to use the WLAN calling feature).
Nothing works, no buttons pushing + power / up / down volume... The ONLY thing, that makes
a sign of life is the windows-sound when connecting the USB cable... there's a device shown
QUSB__BULK (not properly installed) and that's all..
I tried installing USB drivers for the LG G5 and also the Suite / LGUP / LG Mobile Support Tool / Bridge...
nothing works... is there any possible way to to fix it?
Thanks in advance for any kind of help...
mryo said:
Hi guys...
I messed my LG G5 up trying to flash t-mobile nougat kdz via twrp on my rooted 7.0 vodafone branded phone (i wanted to use the WLAN calling feature).
Nothing works, no buttons pushing + power / up / down volume... The ONLY thing, that makes
a sign of life is the windows-sound when connecting the USB cable... there's a device shown
QUSB__BULK (not properly installed) and that's all..
I tried installing USB drivers for the LG G5 and also the Suite / LGUP / LG Mobile Support Tool / Bridge...
nothing works... is there any possible way to to fix it?
Thanks in advance for any kind of help...
Click to expand...
Click to collapse
there is an answer by autoprime to your question
autoprime said:
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
Click to expand...
Click to collapse
with 9008 he means qhsusb_bulk. The drivers you will need are from Qualcomm, once BoardDiag files for G5 are public.
were the boarddiag files ever made public?
Facing the Same problem
I am now facing the above mentioned problem. My g5 h850 doesn't do anything and the only sign of life there is when i connect it to my PC and it picks up as Qualcom hs- usb Qdloader 9008 other than that no display no sound from the handset whatsoever tried getting it into download mode but it won't show anything. I installed all the drivers and tried connecting with lg up but it doesn't pick the phone on any com ports. Is my phone completely damaged or can I do something to bring it back to life. Please help someone
qfil with firehose or octoplus may solve your problem
Can't find the required files anywhere
sbacham said:
qfil with firehose or octoplus may solve your problem
Click to expand...
Click to collapse
QFIL needs PrimaryGPT_0.bin file through firmware extractor but no matter what stock firmware i extract I get multiple patch files like PrimaryGPT_0.bin, PrimaryGPT_1.bin, PrimaryGPT_2.bin, PrimaryGPT_3.bin .......PrimaryGPT_7.bin and when I try to get them through emmc it won't recognize any of the GPT files. That's the step where I am stuck plus I can't seem to find the mbn file for H850
I have lg v20, I too hardbricked my phone, when I extract any kdz I got 7 gpt files. primarygpt0 to primarygpt06 as you said.
are you sure we only need primargpt0 to flash via qfil? i think we need proper firehose/ programmer file and rawprogram file
Maybe I hard bricked mine:
Flashed with uppercut in download mode but with every KDZ file in UPGRADE mode I tried , after the second lg logo with sound of wellcome, it freeze and reboot over and over, it seems that crushes in infinite bootloop. Is this hard bricked?
no, this is not hardbricked. atleast you can enter into download mode.
trash195 said:
Hi I messed up with my LG G5, help needed ?
I want to tell u what i did until now.
I want to root my phone:
1. Unlock Bootloader.
2. Install TWRP
3. Messing around in TWRP becaus i dont finde the SuperSU files cause of encryption usw.
4. Want to Swipe all data and start all over again
5. bootet my device normaly and ther is just the Message "Your device software cant be checked for corruption".
I cant do anything now. I tried to factory reset the phone didnt work. The phone doesnt react to any CMD commands.
I cant enter the TWRP.
I used LG UP to flash the device but LG UP doesnt recognizes my phone correctly, neither in USB Download Mode or in the so calles status, where i just got the blackscreen with the Message"Your device software cant be checked for corruption".
Maybe you guys have a solution.
PS. Sorry for bad english
Click to expand...
Click to collapse
Hi . I I would like to know did you slove your problem ? If yes then what you did plz let me know I’m having same problem with my lgh850.
Hello,
A friend of friend of mine unlocked bootloader on his G5, then some magical stuff probably happened, because secure boot got stuck on boot verification failrue with probably most common issue, signature length mismatch. We're trying to get it to work now, but we can't seem to find a solution to it. Fastboot doesn't work, because secure boot gets tripped in every bootmode. Does anybody have an idea which pins to short out on motherboard for boarddiag operation or something? I'd really appreciate that.
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
[/COLOR]
autoprime said:
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
bumping old thread, i know. Did we ever establish either board diag files for g5 or any solution to No download mode issue with it reporting Different Hash when attempting to enter it? My phone boots fine but no DL mode......backstory: I have a RS988 that i attempted to repair for a friend after they locked it with frp, i removed the frp, via creating a apparently incorrectly modified firmware via my z3x's firmware maker feature(it copies the partitions available on the device into a new firmware file). it doesn't have rs988 listed as a model available to edit so(like normally works with devices, i used vs986(or whatever verizon's variation was, i know rookie mistake) but I believe i have screwed up because since writing the modified firmware i can get into the OS fine but can not enter DL mode again without the "Different Hash" issue. I believe shortwire plus board diag fix could be resolution but could use some feed back . @autoprime Anything i can do to rewrite those partitions manually with the RS988 variant's original kdz and any type of serial connection/jtag/virtual com ports/tty/AT+/linux computer, lol anything? I'm pretty much equipped for anything except jtag but even that can be arranged lol
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....
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.