Develop Bugs

D851 Hard Brick

I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355

Nit3H8wk said:
I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355
Click to expand...
Click to collapse
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.

ThePagel said:
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.
Click to expand...
Click to collapse
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142

Nit3H8wk said:
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Yeah that's probably your best option I have a partitions dump from the tot if yours are not working for some reason. Instead of installing twrp If I was you I would boot into download mode after and flash the tot. I did do a debrick dump with the script that I can get to you tomorrow some time and if that doesn't work tell me and I can give you a link that has 250-500mb range for the dumps from when I was helping the other guy. They weren't made with a script but with terminal emulator but they should be the same thing just bigger because the smaller dumps weren't working for him. Any way here are the partitions just in case https://www.androidfilehost.com/?fid=23622183712472493
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
Oh and before I go to bed another thing you can try if you can send the images over but they don't seem to work. Hunt down the fastboot laf.img send that over then do the rest of the partitions via fastboot instead. Good luck!

Dead phone
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.

Nit3H8wk said:
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.
Click to expand...
Click to collapse
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.

ThePagel said:
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.
Click to expand...
Click to collapse
Yeah i will have to wait then can't afford the $175 deductible right now. Thanks for the help. I don't mind waiting just hope i can find a less costly solution know what i mean?

QPST
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.

Nit3H8wk said:
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.
Click to expand...
Click to collapse
Yeah I got ready to do it last night but got side tracked hopefully tonight

qpst
ThePagel said:
Yeah I got ready to do it last night but got side tracked hopefully tonight
Click to expand...
Click to collapse
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.

Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
Ill be able to tell you tomorrow afternoon if I can do it.

Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
I cant seem to get into diag mode or field test mode so I cannot create the files for you :crying: BUT before you completely give up on fixing it take a look at this http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/

Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.

cesarandres_8911 said:
Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.
Click to expand...
Click to collapse
I just did the same thing tonight, I'll let you know if I fix it.

mxpxboi said:
I just did the same thing tonight, I'll let you know if I fix it.
Click to expand...
Click to collapse
Hello,
What is your phone and variant model? Do you have D851 model?

Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"

mxpxboi said:
Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"
Click to expand...
Click to collapse
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.

cesarandres_8911 said:
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.
Click to expand...
Click to collapse
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.

cesarandres_8911 said:
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.
Click to expand...
Click to collapse
Thank you SOOO much for your help so far.
I installed Qualcomm Drivers and touched the points and it connected.
But it says that the Drivers are blocked due to not being digitally signed.
And it's showing up in Device Manager as "Qualcomm HS-USB QDLoader 9008" with an exclamation point.
I am posting screen shots.'
You didn't have this issue?
What steps do I do in the BoardDiag exactly? Just add the directory with the file and hit start?

@mxpxboi it seems you're using windows 8/above, you have to disable driver signature, here is how to do it https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Sent from my LG-D801 using Tapatalk

[Q] HTC M8 unbrick help

hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,

yes
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.

Hi Konsolen,
Thanks for the reply. I connected the phone, and qualcom hs usb showed up and i have added some screenshot , but i dont exactly understand your last comments qualcom bootloader driver and so on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
[/IMG]

i added some picture, but where do i find the bootloader driver?
konsolen said:
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.
Click to expand...
Click to collapse

It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.

Gkhnnn said:
hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,
Click to expand...
Click to collapse
Does the M8's screen come on? Any charge LED (and what color)?
Very key detail (among others): what did you do to get the phone into this condition?

m8
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
i installed cm12 but i couldnt use my navigation as the ohone couldnt find any sattelites.
so i tried several firmwares and after changing to supercid i managed to update firmware and hboot. after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp but it freezed and after a forced restart i saw red triangles on each corner and has never seen anytging on scrreen since. always black.

Gkhnnn said:
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
Click to expand...
Click to collapse
Red LED? I asked what color before.
Gkhnnn said:
after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp
Click to expand...
Click to collapse
That is remarkably vague. What commands exactly?

m8
​
sorry, the color is orange.
i'm on phone now and can send the commands i have tried
but the codes never worked but i believe i managed to delete a wrong partition .
when onnecting Phone to pc, 14 disk partition shows up, only 4-5 of them has files inside.

konsolen said:
It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.
Click to expand...
Click to collapse
Device is always in the device manager. If i remove the driver it shows up as qusb bulk with question-mark.
I tried to download several driver but i couldnt get the device in fastboot or download mode.
I look forward to your link
Thanks

m8
redpoint73 said:
Red LED? I asked what color before.
That is remarkably vague. What commands exactly?
Click to expand...
Click to collapse
TWRP after installing a rom giving me "unable to mount data" all the time.
I done a research and found out that i could type following commands and get it work.
cd /d c:\mini-sdk
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37
But i heard from somebody that these codes were for HTC M7 and not M8

What carrier or region (CID)?

m8
redpoint73 said:
What carrier or region (CID)?
Click to expand...
Click to collapse
Its a Verizon , i live in Europe, but i got the phone for free from company i worked in.
This is a pic i took for a weeks ago.
[/IMG]

Why not just try and flash the RUU?
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
That might at least get it working again, as you can do it via a microSD card

m8
i have now downloaded the standalone zip and copied that to sd card, renamed to 0P6BIMG.zip
as the screen doesnt show anything, i have powered on with vol down, i assume the hboot ask for vol up for continue to installing, now i wait but i dont thing anything happens
The exe RUU says "USB error, could not connect to the phone"

m8
When connecting the phone to pc, as said before 14 disk partition opens up, and here are the folder which contains the files showed
[/IMG]
[/IMG]
[/IMG]
[/IMG]

m8
When the phone connected to my pc , its shows in device-manager:
PORTS: Qualcomm HS-USB Diagnostics 9006 (COM12)

Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...

EddyOS said:
Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...
Click to expand...
Click to collapse
Screen not coming on, and device showing as Qualcomm on PC is a bad sign. Agree it might not be recoverable.
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
But extreme care needs to be taken before manually messing with partitions like the OP did. A single mis-typed character can be disastrous. And there are safer ways to have recovered from the fairly common internal storage issue (format with computer or in TWRP).

redpoint73 said:
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
Click to expand...
Click to collapse
That someone is the same one
And what I know ... that's a hard brick .. corrupted partition

[SOLVED] Can't Enter in Download mod / no boot / no Recovery

Hello,
So i am in BIG trouble right now.
i just flash my lg g3 D852 to stock firmware using LG Flash Tool. and after i setup my phone i reconnect my device to pc but i forgot to close that tool. and suddenly it start processing and then i remove my device.
so now basically my Os is gone, i can't go in download mode, i can't go in recoverymod either. and also phone is not connecting to pc .
any idea how can i fix that. PLEASE i need a solution ASAP.

You should wait the process to finish, unplugging usb cable is the cause. Now please tell me what you see in your device manager under ports tab, or as an unknown device when you connent your G3 to PC again ?
Use these drivers to identfy your new port then we will continue from there.
http://www.androidbrick.com/download/qdloader-hs-usb-driver/

os_man said:
You should wait the process to finish, unplugging usb cable is the cause. Now please tell me what you see in your device manager under ports tab, or as an unknown device when you connent your G3 to PC again ?
Use these drivers to identfy your new port then we will continue from there.
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Click to expand...
Click to collapse
Thankyou for your reply!.
okay so its stuck at boot looping. and even after installing those drivers you gave me. its not recognizing my device. and nothing shows up in device manager. not even a UNKNOWN DEVICE.

os_man said:
You should wait the process to finish, unplugging usb cable is the cause. Now please tell me what you see in your device manager under ports tab, or as an unknown device when you connent your G3 to PC again ?
Use these drivers to identfy your new port then we will continue from there.
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Click to expand...
Click to collapse
There is few things going on.
i already installed the drivers you gave me. after that.
1) when i connect g3(with battery) to pc with usb cable - it shows me nothing. and its keep restarting the phone.
2) when i connect g3 (without battery) to pc with usb cable - it shows me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and also last thing. i dont even need to press power button when i connect g3(with battery) to my pc. it just turns on automatically and start restarting again and again.

I asked wrong question in first place, i always assume "dead" brick phones when i hear "no download mode, no recovery", so your phone powers up but in a boot loop, all your boot partitions are lost, corrupt, including bootloader and laf parititons ( recovery and download mode ). There is a fix for that too, now second question, can you open your G3 ? I mean tear down to mainboard ? Becouse if you can do and shortpin two tiny spots, then we will have our necessary Qualcomm port to go on and start the rescue mission.
A little reading might help too, the schema of these two magic spots is in this article , please take a look.
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/

os_man said:
I asked wrong question in first place, i always assume "dead" brick phones when i hear "no download mode, no recovery", so your phone powers up but in a boot loop, all your boot partitions are lost, corrupt, including bootloader and laf parititons ( recovery and download mode ). There is a fix for that too, now second question, can you open your G3 ? I mean tear down to mainboard ? Becouse if you can do and shortpin two tiny spots, then we will have our necessary Qualcomm port to go on and start the rescue mission.
A little reading might help too, the schema of these two magic spots is in this article , please take a look.
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
Click to expand...
Click to collapse
yes i read that post. but i dont think i can do that. if there is no other way to do it then i might have to tear down main board.
do i have to separate screen and everything ?

setul34 said:
yes i read that post. but i dont think i can do that. if there is no other way to do it then i might have to tear down main board.
do i have to separate screen and everything ?
Click to expand...
Click to collapse
NO no ! Just a couple of screws, just hold up the back plastic part thats all, youll see the mainboard there. Sorry my mistake, not tear down completely.
After if you can manage to shortpin we will use LG's own BoardDiag to restore boot partitions, and your phone will be ok.

os_man said:
NO no ! Just a couple of screws, just hold up the back plastic part thats all, youll see the mainboard there. Sorry my mistake, not tear down completely.
After if you can manage to shortpin we will use LG's own BoardDiag to restore boot partitions, and your phone will be ok.
Click to expand...
Click to collapse
okay got it. i dont have to hold shortpin all the time right ?? just until i saw that port in device manager.

setul34 said:
okay got it. i dont have to hold shortpin all the time right ?? just until i saw that port in device manager.
Click to expand...
Click to collapse
Exactly, just shortpin a few seconds then plug usb cable (while shortpin), port will open.

os_man said:
Exactly, just shortpin a few seconds then plug usb cable (while shortpin), port will open.
Click to expand...
Click to collapse
okayy and then follow the procedure that is avaliable here --> http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/ ??
or with the boarddiag ?

yes first this link : http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091, its a very good way to test the emmc too. If everything goes well boot partitions will be fixed, if emmc passes the test but still no fix then we will try my fix, but boarddiag mostly handels these situations itself.

os_man said:
yes first this link : http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091, its a very good way to test the emmc too. If everything goes well boot partitions will be fixed, if emmc passes the test but still no fix then we will try my fix, but boarddiag mostly handels these situations itself.
Click to expand...
Click to collapse
Do i need to insert battery at any point ?

No you dont, you can do all procedure without the battery.

os_man said:
No you dont, you can do all procedure without the battery.
Click to expand...
Click to collapse
i got that port now

setul34 said:
i got that port now
Click to expand...
Click to collapse
Good work, did you downloaded your variant's tot ? All you need is your tot file and this :
https://drive.google.com/file/d/0B_Hol5T47S-bYjNETmVPZkdWUms/view
Rest is described at the pictures in willcracker's topic.

os_man said:
Good work, did you downloaded your variant's tot ? All you need is your tot file and this :
https://drive.google.com/file/d/0B_Hol5T47S-bYjNETmVPZkdWUms/view
Rest is described at the pictures in willcracker's topic.
Click to expand...
Click to collapse
Yes . And i just successfully start my device THANKYOU VERYMUCH For your help i really appreciate your help.

Glad to hear that
You have done all the work, i just guided

OS_MAN thank you so far
os_man said:
Exactly, just shortpin a few seconds then plug usb cable (while shortpin), port will open.
Click to expand...
Click to collapse
dude i know that you helped me a lot on g-mail
but had you tried yourself , it didn't work for me , and a capacitor i think flew away of the board but the phone works as it should when plugging it in the PC
what to do now
i wanna smash my phone that i enjoyed 4 days before everything went black thanks to my great mind of mine :crying:

Evilix said:
dude i know that you helped me a lot on g-mail
but had you tried yourself , it didn't work for me , and a capacitor i think flew away of the board but the phone works as it should when plugging it in the PC
what to do now
i wanna smash my phone that i enjoyed 4 days before everything went black thanks to my great mind of mine :crying:
Click to expand...
Click to collapse
Of course i did tried myself, still fixing many G3's this way. I never say or write things without experience (without trying it myself before). I know this is a dangerous method, but its an upsolute fix what can we do ? I wished that LG did chosen Qualcomm port for repairing, but no, to gain more money from their customers in its own service centers ( mostly charging for motherboard change ) LG choose to hide that port, so here we are, hacking it internaly..
Im sad to hear your accident, no mobile repair shops in your town ? Its not that hard to fix it indeed..

os_man said:
Of course i did tried myself, still fixing many G3's this way. I never say or write things without experience (without trying it myself before). I know this is a dangerous method, but its an upsolute fix what can we do ? I wished that LG did chosen Qualcomm port for repairing, but no, to gain more money from their customers in its own service centers ( mostly charging for motherboard change ) LG choose to hide that port, so here we are, hacking it internaly..
Im sad to hear your accident, no mobile repair shops in your town ? Its not that hard to fix it indeed..
Click to expand...
Click to collapse
thanks again very much for replying that fast , means to me a lot by the way as i feel i'm in a crisis
but everything works fine even after the dislocation of the capacitor , except the damn usb error that i get when i connect the phone without the battery , will try to short the pins for 3 mins cuz i only shorted them for 3 seconds (LOL)
i will try again and tell you if this capacitor ruined something or not
and yes i will try to go to an expert to put it back
thanks again hope i fix it so my mum can be proud (lol)

LG g3 bricked. Could not load Qualcomm 9008 driver.

Hello,
I have a LG G3 d855 which is bricked while updating ROM. It is hard bricked meaning I could not see anything on the display. I went to the LG service center. They had a suggestion to replace complete mother board. I went through few forums on XDA on how to unbrick the dead phone.
Here is the procedure which I have followed,
I was not able to see "LGE AndroidNet USB serial port" and "Qualcomm HS-USB QDLoader 9008" .. The suggestions were to short the pins.
After shorting pins and replacing the battery, I am able to "LGE AndroidNet USB serial port" only.
Here are couple of links I went through,
http://forum.gsmhosting.com/vbb/f49...ts-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
https://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
How do I get "Qualcomm HS-USB QDLoader 9008" in the driver list instead of "LGE AndroidNet USB serial port" ?

Just keep trying, with no battery. You should be doing it pretty fast, in less than 30 seconds, else, windows picks your phone as an unknown device.
Also try making the shorting of the 'pins' as strong as possible with something you know it's really conductive (for me, paper staples if can't get copper) and holding it still for 5 seconds.
I have to try for about 10 times to make it right, and sometimes BoardDiag still says it's not in QDLmode and have to redo the process.
When u manage to get HS-USB in Device Manager, try boardDiag3.99a and boardDiag2.99a as I've seen that on my laptop, 3.99 says that phone is not in QDLmode, yet 2.99 work perfectly

AKAndrew41 said:
Just keep trying, with no battery. You should be doing it pretty fast, in less than 30 seconds, else, windows picks your phone as an unknown device.
Also try making the shorting of the 'pins' as strong as possible with something you know it's really conductive (for me, paper staples if can't get copper) and holding it still for 5 seconds.
I have to try for about 10 times to make it right, and sometimes BoardDiag still says it's not in QDLmode and have to redo the process.
When u manage to get HS-USB in Device Manager, try boardDiag3.99a and boardDiag2.99a as I've seen that on my laptop, 3.99 says that phone is not in QDLmode, yet 2.99 work perfectly
Click to expand...
Click to collapse
hey, thanks a lot. It worked. I could get the phone flashed using the BoardDiag.
Now. Another issue which I am facing is, I am not able to flash the phone using the LG Flash Tool.
Here are the steps which I have followed,
1. Pressed Volume UP key .. while holding the same key I can attached USB to the phone.
2. Phone went into download mode.
3. PC has also recognized that the device. But it showing Qualcomm 9008 driver (which is not expected I suppose) . I should be able to see LGE driver in the port section.
4. I have installed all necessary LG drivers.
Still, I went ahead and tried the LG flash tool. But once it shows all ports are ready. I removed the cable to for 5 sec and reattached. Now, It's showing unknown driver in the USB controllers. It should be flashing the phone on this step.
Am I missing something ? Appreciate your help.

I assume that you are not getting the "Firmware upgrade" screen. The easiest way is, in BoardDiag, select AP, EMMC and SDRAM (and the path to the extracted .tot) and press start. It should get you to the screen.
From there you should follow the normal flashing procedure using one of the flashing tools.
If in your device manager under Ports you see a AndroidNet port, you must install LG usb Drivers.

AKAndrew41 said:
I assume that you are not getting the "Firmware upgrade" screen. The easiest way is, in BoardDiag, select AP, EMMC and SDRAM (and the path to the extracted .tot) and press start. It should get you to the screen.
From there you should follow the normal flashing procedure using one of the flashing tools.
If in your device manager under Ports you see a AndroidNet port, you must install LG usb Drivers.
Click to expand...
Click to collapse
Hey Andrew,
You mean If I see the firmware upgrade screen, I should be able to see LG usb driver loaded (instead of Qualcomm 9008). I did try the the AP, EMMC and SDRAM, but did not reach to the firmware upgrade (Still I will try once again). BTW, I tried multiple tools including LGUP, LG Flash tool (2014 Mod), LG Flash tool (kdz method). I am getting weird errors like model info check failed, KDZ method abruptly stops or LGUP shows null model after detection.
Is there any way we could chat somewhere. (may be on Gmail/WebEx, if don't mind). Really appreciate you help.

rushikesh005 said:
Hey Andrew,
You mean If I see the firmware upgrade screen, I should be able to see LG usb driver loaded (instead of Qualcomm 9008). I did try the the AP, EMMC and SDRAM, but did not reach to the firmware upgrade (Still I will try once again). BTW, I tried multiple tools including LGUP, LG Flash tool (2014 Mod), LG Flash tool (kdz method). I am getting weird errors like model info check failed, KDZ method abruptly stops or LGUP shows null model after detection.
Is there any way we could chat somewhere. (may be on Gmail/WebEx, if don't mind). Really appreciate you help.
Click to expand...
Click to collapse
[update]
Hi Andrew,
I followed the steps you have mentioned (Tried AP, EMMC and SDRAM). Then disconnected from the USB. Placed Battery. and while holding the up key reattached the USB.
I can see it went into download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But after that it shows blank screen( instead of firmware upgrade).
And Qualcomm driver is getting loaded. (which is not expected, I should be able to see
the firmware upgrade screen right ?).
Still I tried the LG flash tool. But it failed with model check error.
With above method I was getting Qualcomm driver loaded. (which was not expected).
I tried another way, where I booted the phone (it went into kernel panic) as written over there I pressed up key and reattached USB.
Now I can see the LGE Android drivers loaded. But still I am not seeing the firmware upgrade screen. And LG flash tools are also not working in this stage.
Am I missing something ?

Give it another try using LGUP8974.dll but you must have Firmware Upgrade screen. I don't think it will work through Qualcomm unless you flash each partition with BoardDiag but it is painfully slow.
I've read about this problem on the forum and this should have solved it. Worked for me too, most of the times.
Make sure you have a charged battery. Spend a whole day trying to get firmware upgrade screen just to found out wasn't getting it due to low battery...

AKAndrew41 said:
Give it another try using LGUP8974.dll but you must have Firmware Upgrade screen. I don't think it will work through Qualcomm unless you flash each partition with BoardDiag but it is painfully slow.
I've read about this problem on the forum and this should have solved it. Worked for me too, most of the times.
Make sure you have a charged battery. Spend a whole day trying to get firmware upgrade screen just to found out wasn't getting it due to low battery...
Click to expand...
Click to collapse
Thanks Andrew.
Not sure if this is low battery issue in my case. I am able to see LG logo without connecting it to USB. (was it the same case with you).
Still I will charge my phone again. Will do the SDRAM test again to see if phone shows firmware upgrade screen.
If this does not work, I will have to write all partitions using BoardDiag. Should I follow any sequence for the same ?
I have read on the other posts about the sequence. Would it matter ?
Let me know.

rushikesh005 said:
Thanks Andrew.
Not sure if this is low battery issue in my case. I am able to see LG logo without connecting it to USB. (was it the same case with you).
Still I will charge my phone again. Will do the SDRAM test again to see if phone shows firmware upgrade screen.
If this does not work, I will have to write all partitions using BoardDiag. Should I follow any sequence for the same ?
I have read on the other posts about the sequence. Would it matter ?
Let me know.
Click to expand...
Click to collapse
You can follow the partition order from this link(listed in steps 18 & 19)... https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
aboot, BackupGPT, boot, dbi, laf, PrimaryGPT, recovery, rpm, tz and finally sbl1 (MAKE SURE THIS IS THE LAST ONE FLASHED(it causes the phone to reboot)
*do not flash system or user data partitions with board diag - they take over an hour and they will be re-flashed once you get download mode working anyway
*if a partition fails to write you may need to erase it first
*another good guide for reference... https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Good luck!:good:

If you want to avoid using LG Flashtool I think(no sure) u can flash them through BoardDiag. The order is the one mentioned by startswithPendswithOOH but I thing u can add system partition and the others right befor sbl1.
I couldn't make my G3 stable even at the best GSM service in my city - due to notorious CPU/eMMC fails (overheating, protected storage etc.) and ther response was RIP. No chance to make it work again, will always crash whenever I will get the cpu reach 100%. I will never in my life buy LG phones again. Glad I won't lose more than 60$

Hello. I know that this thread is quite old but I am trying hard to revive my hard bricked LG G3 D855 these days. I have installed Qualcomm Drivers but I cannot get my device recognized on my PC. As soon as I plug in my phone I receive a "USB Device not recognized" error. I believe I am shorting the pins correctly and everything regarding drivers installation has been done as described. But I have tried too many times and I still receive that error. Please note that my phone is dead. It used to light up when I connected it on the PC but now its totally unresponsive. Could anyone please let me know what I could be doing wrong? Does the type of wire used to short the pins play significant role? Any images of a wire that I could use?

Question Bricked phone, looking for help!

I will literally pay someone to help me out here at this point.
I have been trying to unbrick my device for the past 2 days now, I have no access to Fastboot or the Recovery mode, just EDL mode. I have been trying to use MSM to unbrick the device. I have tried every version of MSM (EU, Global and India), my version of the phone is EU, I have tried multiple different variants of the Qualcomm driver, none have worked. I'm at the situation where its telling me "Param Preload, Device not match image". I have tried turning off Sha256 Check and turning on lite firehouse, none have worked. I have looked everywhere but can't seem to find any solution for me
I bricked it by flashing something onto the phone, where it required you to flash certain files, Wipe the phone and then flash more files, but I forgot to wipe the device before flashing the rest of the files, and it hasn't turned on since, I am starting to wonder if there is any way at all at fixing this or is it gone for good. i do not want to spend another $900 for this phone, and repair service is my last option, I am going to see if anyone can help me this on e last time before I file for repair service, as I do not want to pay the repair service
I would really appreciate if anyone could even give me a clue on what to do here as I am out of options, thank you very much for reading anyways even if you weren't able to help
I have also put this on XDA in hopes someone there could help me too!

HI, once the msm tool reads "Param Preload, Device not match image" which means your phone is connected. Please use the MSM EU varient, put your phone on EDL mode, turn on the Sha256 check but "don't use the lite firehouse". This will solve "Param Preload, Device not match image" problem, and the download should proceed normally. Give it a try, hope this will help !

epcwong said:
HI, once the msm tool reads "Param Preload, Device not match image" which means your phone is connected. Please use the MSM EU varient, put your phone on EDL mode, turn on the Sha256 check but "don't use the lite firehouse". This will solve "Param Preload, Device not match image" problem, and the download should proceed normally. Give it a try, hope this will help !
Click to expand...
Click to collapse
If I tick Sha256 then it gets stuck at some "Sahara communications" or something like that, I can't remember I'm not home rn. Any other options?

It seems that you've installed too much different drivers on your computer. Uninstall all android drivers and only install the OnePlus_USB_Drivers_Setup.exe and QDLoader HS-USB Driver_64bit_Setup.exe. Then give it another try !

Another option is that because the EDL mode only holds for may be 5 to 10 seconds, you have to get the msm tool ready with the Sha256 check turn on but "don't use the lite firehouse" also with "start" turn all standby. Once you've got all the above ready, then put your phone into EDL mode and plug into the computer immediately (in a very uick action), and try it again !

Try the option first before revised the drivers ! If I remember right the "Sahara communications" is caused due to the EDL mode is off when your plug into the computer too late. The timing is very important that's why it showed communication error. Try again !

Launch the MSM tool (use the Win7 one) Choose "Others"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ensure you select the EU from the top "Target" dropdown:
Don't change any of the other options, you shouldn't really need to. Just use the default options.
Then click "Start", once you see it's started and it's looking for the phone (ensure you've connected the phone directly to your computer, not via a USB hub, it's also usually better to use a USB2.0 port for some reason) reboot your phone holding down all 3 buttons (power AND vol down AND vol up).
If the program does not jump into life when it sees the phone then you have a driver issue, I've uploaded the correct Qualcomm driver here.
They're the ones I use and it works fine for me, always use it to go back after trying custom roms out.
I'd also recommend keeping your device manager open while you're doing this cos you'll see it change if the computer recognises the phone in EDL mode. It'll show it as a different device from normal.

djsubterrain said:
Launch the MSM tool (use the Win7 one) Choose "Others"
View attachment 5677693
Ensure you select the EU from the top "Target" dropdown:
View attachment 5677699
Don't change any of the other options, you shouldn't really need to. Just use the default options.
Then click "Start", once you see it's started and it's looking for the phone (ensure you've connected the phone directly to your computer, not via a USB hub, it's also usually better to use a USB2.0 port for some reason) reboot your phone holding down all 3 buttons (power AND vol down AND vol up).
If the program does not jump into life when it sees the phone then you have a driver issue, I've uploaded the correct Qualcomm driver here.
They're the ones I use and it works fine for me, always use it to go back after trying custom roms out.
I'd also recommend keeping your device manager open while you're doing this cos you'll see it change if the computer recognises the phone in EDL mode. It'll show it as a different device from normal.
Click to expand...
Click to collapse
I have tried these drivers with EDL mode, still no luck, just the same error, do you have any idea what it could be?

Aphriz said:
I have tried these drivers with EDL mode, still no luck, just the same error, do you have any idea what it could be?
Click to expand...
Click to collapse
"Param Preload, Device not match image" would suggest you're not using the correct MSM tool
Check your box and make sure you downloaded the correct one from here :
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Even if you're in the EU, depending on who you bought it from, it might be the global version, they all work the same though, obviously choose the region in the top dropdown that matches your device once you confirm it.
If you're not sure, tell us the model number here so we can advise further, although GSM Arena is always a good site to help with that

djsubterrain said:
"Param Preload, Device not match image" would suggest you're not using the correct MSM tool
Check your box and make sure you downloaded the correct one from here :
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Even if you're in the EU, depending on who you bought it from, it might be the global version, they all work the same though, obviously choose the region in the top dropdown that matches your device once you confirm it.
If you're not sure, tell us the model number here so we can advise further, although GSM Arena is always a good site to help with that
Click to expand...
Click to collapse
I have the EU version, I was talking to OnePlus support and they told me. I have tried the EU MSM and I'm still getting the same result, any help would be great

Aphriz said:
I have the EU version, I was talking to OnePlus support and they told me. I have tried the EU MSM and I'm still getting the same result, any help would be great
Click to expand...
Click to collapse
It sounds like you're doing something wrong when connecting device /entering EDL mode at the correct time. or you haven't got Proper drivers installed,. Keep trying different configurations bro you'll get it eventually. If you haven't restarted PC since installing drivers give that a go. That stopped errors for me.

Easy way to catch EDL mode on your phone is to have your phone completely shut off and not connected. Get MSM set up how it should be and go ahead and hit start. It will begin looking for your phone. Connect your phone to the USB that is connected to your computer while holding down both volume buttons.
No fuss or trying to time anything. It will start your phone and catch the EDL mode.
Won't solve your problem, but it's an easy way to catch EDL every time.

Deleted

After all the comments from the above members, your phone should work with the msm tool. If still not, which means you didn't catch the right timing when connect the phone to the computer. Last option, leave your phone for 3 to 4 days until the phone battery is completely drained off. Then try to re-connect your phone again with the msm tool. Once your phone is connected, it should start the firmware download automatically. Give it a go !

I would also check to see if the drivers work if you disabled driver signing in Windows, there were some issues previously with the certification:
After that, try installing the driver again, just in case that's what is stopping them working.
Check it with another cable also, I've honestly had a problem with one USB cable and not another, it's rather fickle but once you confirm what setup works, just use that in future.
Try on another computer/laptop also if you have one but install those drivers before you even start. You should do that with any USB device, install the drivers first THEN attach it.