Database Users

[Q] Hard Brick D800 - Please Help! At a loss

Any help is appreciated! First some background:
Flashed device to stock using KK 4.4 version d80020c following steps found here http://forum.xda-developers.com/showthread.php?t=2432476. Successfully rooted using directions (and ioroot25) found here https://www.youtube.com/watch?v=HKuedInhdjU&noredirect=1.
Here's where I got into trouble...Downloaded TWRP 2.7 recovery img and flashed via Flashify. Since this step, my D800 has the exact same symptoms found on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
- No download mode (tried many times)
- No recovery (tried many times also)
- Secure booting error
- LG detected as qhsusb_bulk in device manager
- Device is recognized as 15 different drives, one of which contains a folder named image with 79 different files being .B0X files and Microsoft Access Add-in Data files
- Upon restarting, LG logo with secure booting error, then the screen goes black while your phone is still on
I've followed the steps in the thread that matches my G2's symptoms, run ubuntu 13.1 in VM, apply usb filters for my device which is then recognized as either LG Electonics Inc. QHUSB_BULK or Unknown Device 05C6:9006 when running in VM.
Upon running command ls /dev/sd* in VM Ubuntu Terminal, all that is returned is /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 which are the partitions for Ubuntu, no LG.
I've tried to download and update the Qualcomm drivers, device manager tells me that the drivers were recognized, but cannot be installed and do not pass the hash check (Note: PC is running Windows 8.1).
I've spent over 12 hours on this trying to fix this problem, researched and searched everywhere. If I could get ubuntu to recognize the device, I would be able to continue on with the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
Links for windows 8 qualcomm drivers, suggestions on how to get the device recognized in ubuntu vm, experiences from others in similar situation, or any with experience working with LG to get a repair done if I'm SOL (as in eMMC is fried) would be so helpful right now.
Thank you all!

After flashing recovery did you flash a patched kernel to boot stock kk?
Sent from my LG-D800 using Tapatalk

I had the same, also with a lot of drives etc.
Screen is black but low backlighted?
Then try with pluged USB Cabel in Phone, hold Power button until screen is realy off, then hold the Power Up Button and plug Cabel into PC.
So I got download mode after I tryed many times

I had problems a few weeks ago getting mine to go into Download mode... turned out that the cable I was using was great for charging, but sucked for everything else. Once I switched to a different cable things worked fine and I was able to load D80010c on the device.
I was running D80020c this morning (with the D80010c boot.img to have a custom recovery) and decided to do an update. Since you can't load D80020k if you have the older bootloader I went all the way back to D80010c, updated to D80010o, D80010q, D80020c and finally D80020k. I was able to root that using IOroot and have restored everything back onto my phone.
-Daryel

Thanks so much for the responses! I've tried endlessly to get the device into download mode, and tried a new cable to no avail. Any other suggestions?

The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
d800 partitions are here

Still no luck
bender_007 said:
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
Click to expand...
Click to collapse
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.

Sneaky Elephant said:
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Click to expand...
Click to collapse
As soon as in the background of the white menu (factory reset) the secure boot appear plug it in. I'm not sure how much usb filter helps you(maybe it does) but try installing ubuntu over WUBI installer so your win remains. Or at least try ubuntu from usb stick. So you can know for sure if it's working.

Hi Sneaky E. I have the same issue you have. I'll be following your thread. If I figure anything out I'll let you know. I am also having an issue getting mine to charge now. Have you tried downgrading your TWRP?

VirtualBox Error
VirtualBox recognizes the device is plugged in, but won't allow me to push the device for use in linux. I keep getting this error message:
Failed to attach the USB device LG Electronics Inc. QHSUSB__BULK to the virtual machine Ubuntu.
USB device 'LG Electronics Inc. QHSUSB__BULK' with UUID {d8db3712-b86c-4257-a87b-275cef04e5a3} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Click to expand...
Click to collapse
I've tried all USB ports, 2.0 and 3.0. I feel like if I can get past this there should be no reason linux can't see the partitions in the phone. Please Help!!!

Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!

Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.

ambetdelarosa said:
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
Click to expand...
Click to collapse
What are the negatives to doing a JTAG fix?

Sneaky Elephant said:
What are the negatives to doing a JTAG fix?
Click to expand...
Click to collapse
Here is your fix.
follow exactly. LINK

ingoljosh said:
Here is your fix.
follow exactly. LINK
Click to expand...
Click to collapse
Followed steps already, still can't boot into recovery.

Sneaky Elephant said:
Followed steps already, still can't boot into recovery.
Click to expand...
Click to collapse
if your device is insured maybe report it lost and pay deductible and get a new one AND NEVER ROOT AGAIN

linux cant recognizy my lg g2 f320L
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......

dr jam said:
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
Click to expand...
Click to collapse
The same with me - UP

install ur Ubuntu sing VMware....then partitions will appear.........
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
install ur Ubuntu using VMware......then ur mobile will be recognised and partitions will appear.....

Deleted ROM

A friend of mine accidentally deleted his ROM on his LS980. I took his phone home today to try and fix it for him.
It still boots into TWRP (luckily). I tried ADB sideload, and I manage to install ROMs with no issue, but the device boots right back into TWRP on its own. I also have access to download mode and tried the LG FlashTool but it doesn't do anything. I've followed the instructions for it and I just get the COM41 port saying "READY!!" and stays there.
Any advice would be greatly appreciated, he's been out of a phone for two weeks now.
Edit: This is the error on TWRP. "E:Unknown File System: 'datamedia'"
Edit: Fixed. I didn't set the phone to COM41 in device manager. Oops.

Probable brickage of TN7

Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray

Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps

DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839

Un-debrickable state ?

Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.

growiel said:
Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
Click to expand...
Click to collapse
It does sound like a hard brick... you said fastboot is hosed, do you have access to adb in any way?
Sent from my moto g(6) play using Tapatalk

None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...

growiel said:
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
Click to expand...
Click to collapse
On my lg tribute HD (ls676) fastboot was removed by lg themselves on Android 6.0.1 quietly with a security update and download mode never worked right for me. Without access to fastboot, adb or even diag mode it really sounds like you have a hard brick. if i can find a solution of some kind, I'll definitely let you know.
Sent from my moto g(6) play using Tapatalk

What would "diag mode" be and how can I check if I can access it ?

Small update for people who stumble upon this thread, I managed to save my phone by using the Qualcomm Test Point, see here: https://forum.xda-developers.com/showpost.php?p=81697447&postcount=128

Hard Bricked OnePlus 6t Tmobile Version

I have a Tmobile OnePlus 6T, hard bricked.
Mine gives the usb device malfunctioned error. I have installed, uninstalled and reinstalled the qualcomm usb drivers. It recognizes the phone in the device manager as USB DEVICE DESCRIPTION FAILED. The MSM tool wont recognize it, and my phone wont boot in any other mode except EDL. It will not boot to bootloader or anything. Funny thing is, all I was trying to do was convert the T-Mobile version to international which I've done before. During that process, it hung at "recording downloading time". I let it go for 20 minutes, according to the guide it is supposed to take 5. I canceled the process, (I had done this one other time before, and it booted just fine) and now nothing works. I am not a noob at this. I can restore through fastboot if I could get it to boot into fastboot. I could restore through recovery via sideload if I could get it to boot into recovery. Please help.
*Moderators, I have searched high and low through the forums and I cannot find a thread with this problem that has any steps to solve it. I found one thread with a similar description but it is a year old, has no replies and the author managed to fix his phone on his own, with no description of how he did so.*

Txdude35 said:
I have a Tmobile OnePlus 6T, hard bricked.
Mine gives the usb device malfunctioned error. I have installed, uninstalled and reinstalled the qualcomm usb drivers. It recognizes the phone in the device manager as USB DEVICE DESCRIPTION FAILED. The MSM tool wont recognize it, and my phone wont boot in any other mode except EDL. It will not boot to bootloader or anything. Funny thing is, all I was trying to do was convert the T-Mobile version to international which I've done before. During that process, it hung at "recording downloading time". I let it go for 20 minutes, according to the guide it is supposed to take 5. I canceled the process, (I had done this one other time before, and it booted just fine) and now nothing works. I am not a noob at this. I can restore through fastboot if I could get it to boot into fastboot. I could restore through recovery via sideload if I could get it to boot into recovery. Please help.
*Moderators, I have searched high and low through the forums and I cannot find a thread with this problem that has any steps to solve it. I found one thread with a similar description but it is a year old, has no replies and the author managed to fix his phone on his own, with no description of how he did so.*
Click to expand...
Click to collapse
The other of the previous post probably figured out how to get the device recognized by the computer. I would say see if you can use another computer/cable and see if it still has the same issue, if it does i'd probably be concerned about the device health. If the issue is gone on the other PC though then you likely have something wrong with either drivers or usb hardware on your PC. I would assume you've already tried using a different USB cable and port with your current PC.