My lg g3 has been hard bricked
not charging
no lg logo
it does get detect by computer under hs-usb qdloader 9008
help me
andoid789 said:
My lg g3 has been hard bricked
not charging
no lg logo
it does get detect by computer under hs-usb qdloader 9008
help me
Click to expand...
Click to collapse
I have a D852 as well. How did you hard brick it, if I can ask?
I did a quick search and it doesn't look too promising. Quite a few posts of people asking for help with a similar problem and no fixes.
There was one post I saw in the G2 section that I'll link for you and also the link to the Rogers img files. Not sure if you are with Rogers, but only found those image files.
I can't help you any further than that and not sure if it will work so don't blame me for anything you do to your phone. Best to send it back to LG for repair than attempt dive into uncharted waters. If you do find a fix though, post the results to share with others so we can all learn. Best of luck
Link to G2 section with question from G3 user
Rogers G3 stock partition files
Does anyone know if there is a way to fix using adb? I was told Jtag won't work. Or is there parts to replace that are cheaper than buying a new phone? I was rooted 11a and restored with the kdz then took the ota and rerooted. Some of my apps didn't work the same so I decided to go back and kdz back to 11a..... Now I have a brick. When I plug it in the charge light doesn't even go on and I can't get into download mode. Now I know I messed up by trying to downgrade back to 11a..... I get this when I run the ports bat
C:\Users\Bill Laptop\Desktop\G4 Root\LG Root zip>reg query HKLM\hardware\devicem
ap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\QCUSB_COM8_1 REG_SZ COM8
My phone is recognized by my win7 pc as qualcomm hs-usb qdloader 9008
This thread may help. http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Hope it helps.
Honestly, I wouldn't spend a whole lot of time trying to fix it. Trying to KDZ to 11a while already on 13b is a no-no and has been very well documented in 13b threads. Unfortunately, your phone is about as useful as a block of dried clay. Sorry!
The G4 can boot from micro SD?
Sounds like you need to replace the mainboard
Anyone know who to contact to do a motherboard replacement?
Screw it..... I bought a new one off swappa.....
vs986 unbrick
vs986 ve tüm lg verizon cihazlarınız unbrick. qualcomm hs-usb qdloader 9008 a düşen çihazlarınız %100 olarak emmc sökülmeden yapılmaktadır. cihaz ana kartınız deforme olmadan sorunsuz olarak düzeltirilir...
İletişim: 0543 644 66 31 Ankara türkiye
Nothing work at all now , so u need to replace mobo dude :\ , ive done it , and now my device works now
i need dump
http://4pda.ru/forum/index.php?showtopic=676146&st=5400#entry54915015
Sent from my LG-D838 using Tapatalk
Hello, Iam having a bricked Google Pixel XL 128GB with black screen, no fastboot, no recovery(phone only detected as HS-USB QDLoader 9008).
Is there anyway to unbrick the phone?
What was your setup before this happened? What were you trying to do before this happened?
chapelfreak said:
What was your setup before this happened? What were you trying to do before this happened?
Click to expand...
Click to collapse
Bad Flash on OTA update
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
5.1 said:
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
Click to expand...
Click to collapse
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
5.1 said:
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
Click to expand...
Click to collapse
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
droidan said:
Bad Flash on OTA update
Click to expand...
Click to collapse
What does that mean? Were you rooted, unlocked? If so return the device, no?
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Sent from my Pixel using XDA-Developers Legacy app
droidan said:
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
Click to expand...
Click to collapse
Yeah, unless someone leaks official programmer, you are SOL...
Good luck... :good:
Hi guys,
I've opened a similar thread on google forum - related to pixel 128gb being bricked and in chipset download mode.
If there are enough bricked pixels out there perhaps google will (hopefully) share those files?
Cheers,
Dan
The deluge of bricked Pixels resulting from the Oreo update continues...
I did, however, find these pages posted in the last couple weeks, and wondering if they're the answer to the Q's posted earlier ITT (sry I'm too new to post live links, so you'll have to paste these):
- androidauthority.com/download-android-8-0-oreo-794622/
- androidauthority.com/install-android-oreo-758342/
- developers.google.com/android/ota
Earlier ITT, posters were saying that they couldn't find the firmware or other files that would allow someone to recover from the hard-bricked state...but are those 'official' factory images and OTAs what they were saying they needed, but which they couldn't find at the time? In short, might we now actually have the files necessary to save our bricked Pixels without engaging in Macguyvering that would void the warranty?
Out of curiosity, was your bootloader locked prior to running into this issue?
Pain-N-Panic said:
Out of curiosity, was your bootloader locked prior to running into this issue?
Click to expand...
Click to collapse
I assume so...I bought the Pixel directly from Google, so assumed I was getting the purest Android installation possible / no provider bloatware etc...if i'm not mistaken, the bootloader would have been Locked when I initially received the phone, right?...if so, then yes it would still have been locked when it bricked, as I didn't take any actions to unlock it (nor would i know how)
hopefully files will be shared soon for sure it is exists
I have the same problem and all I can do is rma.
Is it possible to pull the files from a working pixel?
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
mattwheat said:
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
Click to expand...
Click to collapse
Maybe that's why they aren't giving the files
This happened to mine as well
Went from 8.0 to 8.1 - wiped data and re-locked bootloader. Ran fine for two days then powered down and now I'm in this qualcomm mode. Thankfully I purchased the 2-year through Google. Unfortunately their support is dogsh**.
Update: Ok Google's support rep was actually pretty solid but their system is awful. I'm already on a refurb and it doesn't have the IMEI printed on the sim tray. Either way they worked it out and I'm down $80 for the deductible.
I have the same problem
Howdy folks. I'm posting this on behalf of another user. I originally saw his post in an Android Q&A subforum and I suggested he post here. Instead he posted in the T-Mobile G3 Q&A section which probably has less eyes than this one. Due to D850 markings he sees there's also the possibility of a frankenphone. Tag him in your replies if you have any ideas. Thanks.
oxiiid said:
HELLO
I used to have LG D851 which was working fine on kitkat , I decided to upgrade to marshmallow using lg flash tool but the phone bricked during the operation and now I can't even turn the phone on , no charging or boot or anything.
the only thing I can do is plug it to my computer and the phone detect as Qualcomm HS-USB QDLoader 9008.
I tried to flash boot and stuff through Boarddiag but failed.. I think my phone is refurbished because it used to run on LG D851 10R but when I check the motherboard it appears D850 and I tried many flash apps but nothing work
PLEASE HELP ME TO FIX THIS PHONE I'am broke and I have no money to buy new phone
Click to expand...
Click to collapse
Moto G5S Plus XT1806, Validus 8.1.0, microG-NanoDroid, MultiROM, XDA Legacy
So i have recently bought a red magic 5g from Aliexpress. Thanks to xda i have rooted it successfully but by mistake, I have updated the phone and now the phone is bricked. I have used Jerry's tool to unbrick it but that didn't work, I have disassembled the phone for edl but still no hopes.
I think my phone is Chinese so I need Chinese unbrick tool. Can anyone help me with this?
arjun_m4 said:
So i have recently bought a red magic 5g from Aliexpress. Thanks to xda i have rooted it successfully but by mistake, I have updated the phone and now the phone is bricked. I have used Jerry's tool to unbrick it but that didn't work, I have disassembled the phone for edl but still no hopes.
I think my phone is Chinese so I need Chinese unbrick tool. Can anyone help me with this?
Click to expand...
Click to collapse
Chinese and global have same tool and same chip and people have succeeded to unbrick chinese ones with this tool. But generally the issue is the usb port/computer/usb cable. You dont have to open your phone.. Just continue to try other computers..but before everything i would suggest you to check if your phone is actually hard bricked or have you put it to edl mode etc.. But you can be sure ...there is johnny tool and jerry tool and they both work.there is nothing else
Sent from my LM-G850 using Tapatalk
Thanks but i have tried both the tools and that didn't help at all. The device doest boot and just connects to the pc using HS-USB QDLoader 9008 protocol.
arjun_m4 said:
Thanks but i have tried both the tools and that didn't help at all. The device doest boot and just connects to the pc using HS-USB QDLoader 9008 protocol.
Click to expand...
Click to collapse
Ok... Then try to continue to change pc , cable, usb port until it works.there is no other option. These tool are too much picky about these 3 things.
Sent from my LM-G850 using Tapatalk
i have tested it on 3 pc's. Jerry's tool seems stuck at Downloading Software image... and jhonny's tools gives me ack count error.
arjun_m4 said:
i have tested it on 3 pc's. Jerry's tool seems stuck at Downloading Software image... and jhonny's tools gives me ack count error.
Click to expand...
Click to collapse
Ok then contact the telegram people. Cant share link.sorry
Sent from my LM-G850 using Tapatalk
Thanks. Is it possible i can have your telegram id so I can contact you regarding this issue ?
arjun_m4 said:
Thanks. Is it possible i can have your telegram id so I can contact you regarding this issue ?
Click to expand...
Click to collapse
Sorry i changed device so i am not even active in that group or anything related to the phone..i saw you searching for chinese tool..so i answered. That group is available in a lot of place and they are very helpful..check with them..sorry couldn't help
Sent from my LM-G850 using Tapatalk