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?
Related
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)
Hello everyone ! I have a BIG problem with my lg... So I buy it refurbished, suddenly I decided to flash it with lgflashtool2014 Open EUROPE firmware.... So it flashes without issues, when it reached 100% TURNED OFF AND MY LG DIED COMPLETLY !!! NO DOWNLOAD, NO FASTBOOT, NO NOTHING I started searching for this kind of problem and I found that it is "super hard brick" mode. I got only qualcomm hs usb qdloader 9008 driver. So first I use the method with QPST Tool, flash some dump from h811 so then it entered in download mode and when I turn it on LED starts blinking with secure boot error 1006 :/ Then I use: LG UP STOPS at 9%, lgflashtool2014-same, the other flashtool with dll. file- same (tried more than 10x different KDZ firmwares for h815 even TOT. doesn`t work... I ****ed Up two sd cards and thats it. Iam done. But one little bird told me that I haven`t asked in the XDA forum, and here it is . Iam writting this with hope to fix my lg g4 and use it like before sry for my english...
@TheMadScientist @steadfasterX
IvchoLord said:
Hello everyone ! I have a BIG problem with my lg... So I buy it refurbished, suddenly I decided to flash it with lgflashtool2014 Open EUROPE firmware.... So it flashes without issues, when it reached 100% TURNED OFF AND MY LG DIED COMPLETLY !!! NO DOWNLOAD, NO FASTBOOT, NO NOTHING I started searching for this kind of problem and I found that it is "super hard brick" mode. I got only qualcomm hs usb qdloader 9008 driver. So first I use the method with QPST Tool, flash some dump from h811 so then it entered in download mode and when I turn it on LED starts blinking with secure boot error 1006 :/ Then I use: LG UP STOPS at 9%, lgflashtool2014-same, the other flashtool with dll. file- same (tried more than 10x different KDZ firmwares for h815 even TOT. doesn`t work... I ****ed Up two sd cards and thats it. Iam done. But one little bird told me that I haven`t asked in the XDA forum, and here it is . Iam writting this with hope to fix my lg g4 and use it like before sry for my english...
Click to expand...
Click to collapse
There is one step in your journey which is crucial important :
You flashed with QFIL something. Tell me EXACT what.
To do this share the link or upload the files you flashed. Then I can say more.
Sent from my LG-H815 using XDA Labs
I followed this guide
http://forum.gsmhosting.com/vbb/f779/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box-2211744/
flashed file which was for h811 but in the top says that it work for h815
this is what i flashed with QPST tool https://mega.nz/#!AK4DwRga!3L5jR5e8FGflLlN8tmxDSb5V3KcKprlxmgXK1wmdEE4
IvchoLord said:
http://forum.gsmhosting.com/vbb/f779/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box-2211744/
flashed file which was for h811 but in the top says that it work for h815
this is what i flashed with QPST tool https://mega.nz/#!AK4DwRga!3L5jR5e8FGflLlN8tmxDSb5V3KcKprlxmgXK1wmdEE4
Click to expand...
Click to collapse
As for the sd cards ypu might be able to use something like partition magic and a few other things to fix em. U can google say like what ever size it is. For example 32 gb sd card only showing as 8 gb or any random. I have saved a few.
Once im up outa bed I will look at what i got on my PC.
OK Thank you soo much
I have repaired SDs with mini tool partition wizard. After messing them up with debrick.imgs and win32diskimager.
You can delete all the diffrent partitions,Takes a while but can reallocate it as free space then format....
The sd cards are fixed... thank god. I manage to fix them with cmd. So I will hope that you will help me in this software thing, because Iam round zero :|
IvchoLord said:
Hello everyone ! I have a BIG problem with my lg... So I buy it refurbished, suddenly I decided to flash it with lgflashtool2014 Open EUROPE firmware.... So it flashes without issues, when it reached 100% TURNED OFF AND MY LG DIED COMPLETLY !!! NO DOWNLOAD, NO FASTBOOT, NO NOTHING I started searching for this kind of problem and I found that it is "super hard brick" mode. I got only qualcomm hs usb qdloader 9008 driver. So first I use the method with QPST Tool, flash some dump from h811 so then it entered in download mode and when I turn it on LED starts blinking with secure boot error 1006 :/ Then I use: LG UP STOPS at 9%, lgflashtool2014-same, the other flashtool with dll. file- same (tried more than 10x different KDZ firmwares for h815 even TOT. doesn`t work... I ****ed Up two sd cards and thats it. Iam done. But one little bird told me that I haven`t asked in the XDA forum, and here it is . Iam writting this with hope to fix my lg g4 and use it like before sry for my english...
Click to expand...
Click to collapse
i have exact same problem with h811 i tried sd card 64gb class 10 writing via win32 disk software but no luck.
i even tried qpst QFIL method but it shows device is not in "firehose mode" sometimes it shows "sahara fail" i have all drivers installed correctly and in pc device manager it detects as qdloader 9008 port4 i dont know what am i doing wrong. how did you able to flash the dump via QFIL and enter download mode please explain the steps i am desperate to fix this device from 4 weeks.
if you are in download mode you can search in youtube for "z3x box lg software cracked" or "octopus box lg cracked" this softwares is little hard to use unless you are technician or watch some video tutorials how to use this software but this will flash any kdz even older version of kdz on your device the LGUP will not work since you used h811 dump on h815 but this software will defiantly fix this issue
TIA
Installed everything and face this error
{
"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"
}
https://ibb.co/cm312b
IvchoLord said:
Installed everything and face this error
https://ibb.co/cm312b
Click to expand...
Click to collapse
you need to install z3x drivers properly i guess or try different version of z3x the latest there are many versions available on youtube .
most important disable any antivirus on your pc or windows defender because any cracked software will detect as virus and the software will not work properly.
how did you enter download in your device can you guide me the steps and files required please.
https://www.youtube.com/watch?v=QOB5XI3CFF8&t=2s
the guide which i followed, i enter in download mode while holding vol up and connecting to pc
can you tell me how to do it please and link to download...
IvchoLord said:
https://www.youtube.com/watch?v=QOB5XI3CFF8&t=2s
the guide which i followed, i enter in download mode while holding vol up and connecting to pc
Click to expand...
Click to collapse
that guide did not worked for me i tried dump and system image writing in microsd card but still no download mode
you mentioned earlier you able to boot into download mode by qpst how and which files you used ?
yes but the files were for h811...
http://forum.gsmhosting.com/vbb/f779/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box-2211744/
and i treid all the files which are for the qpst program and ONLY one worked: LG G4 H811 fix.zip. The others face error. I tried flashing firmware for h811 with lg up but no result.
The z3x program started working but, when i click FLASH it closes
hey guys found something new check out: https://ibb.co/jUrGkw
I need LS991 ZVA kdz firmware, someone ??
@TheMadScientist help me please
IvchoLord said:
@TheMadScientist help me please
Click to expand...
Click to collapse
I dont think there is a zva tot. Now if its a ls991 you can downgrade zva not zvb but zva back to zv6 and root as for that there are zv6 tot firmwares out. I just dont think there is a zva. Im mobile rite now and have crappy data covrage. I can look some more later but again dont think there is one....
Every time i connect my OnePlus 3 with my PC is says "USB Device Not Recognized"
{
"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 in Device Manager it shows "Unknown Devices" under Universal Serial Bus Controllers.
I tried to update driver by right click on "Unknown Devices" and update driver software. But it didn't work.
For this problem i cannot unlock my bootloader.
thinks i tried:
1. Install oneplus driver
2. Install ADB drive
3. Update driver from device manager
ariyan rana said:
Every time i connect my OnePlus 3 with my PC is says "USB Device Not Recognized"
and in Device Manager it shows "Unknown Devices" under Universal Serial Bus Controllers.
I tried to update driver by right click on "Unknown Devices" and update driver software. But it didn't work.
For this problem i cannot unlock my bootloader.
thinks i tried:
1. Install oneplus driver
2. Install ADB drive
3. Update driver from device manager
Click to expand...
Click to collapse
Change PC's usb port..will works.
simkhadalila said:
Change PC's usb port..will works.
Click to expand...
Click to collapse
tried, didn't work.
Instal ADB 1.43. It contains drivers for windows. When ask install them too.
I had similar issue about 2 years, when I had Oneplus One. Eventually it turned out it was coz windows 7s driver recognition went kaput, because some local usb device messed up windows 7s driver recognition
I am also having this same issue.., I am 100% sure it's not driver issue. I've tried in Linux PC., Even QCom Diag mode (to use unbrick tool) doesn't work... Only I'm able to charge phone at USB speed. Dash charge as will as OTG doesn't work. I even got a USB-C port replacement and still am having the issue. Last week gave my OP3 to OP service centre they also confirmed some issue in board and can't be fixed without replacing entire motherboard (Stupid folks!!).., I'm rooted and on Oreo.
Any leads/advice on this issue is much welcome...
---------- Post added at 14:00 ---------- Previous post was at 13:16 ----------
@
ariyan rana
Click to expand...
Click to collapse
I started to encounter this after flashing OB24 firmware (As far as I can remember) But now I have flashing both older FW as well as latest new one and nothing helps. I remember flashing that FW when phone was charging.. Do you remember from when you got this USB issue?
arvindgr said:
I am also having this same issue.., I am 100% sure it's not driver issue. I've tried in Linux PC., Even QCom Diag mode (to use unbrick tool) doesn't work... Only I'm able to charge phone at USB speed. Dash charge as will as OTG doesn't work. I even got a USB-C port replacement and still am having the issue. Last week gave my OP3 to OP service centre they also confirmed some issue in board and can't be fixed without replacing entire motherboard (Stupid folks!!).., I'm rooted and on Oreo.
Any leads/advice on this issue is much welcome...
---------- Post added at 14:00 ---------- Previous post was at 13:16 ----------
@
I started to encounter this after flashing OB24 firmware (As far as I can remember) But now I have flashing both older FW as well as latest new one and nothing helps. I remember flashing that FW when phone was charging.. Do you remember from when you got this USB issue?
Click to expand...
Click to collapse
for some reason my dash charge work but not OTG. after updating to latest OB this problem shows up. for this reason i cant unlock my BL or root
ariyan rana said:
for some reason my dash charge work but not OTG. after updating to latest OB this problem shows up. for this reason i cant unlock my BL or root
Click to expand...
Click to collapse
For me too, 1st week when it started occured Dash charging worked after then it also stopped. Only USB charging upto 1.8A in present.., OTG doesnt work but phone give power to external device!
Atleast I'm safe in that way with Unlocked BL and rooted... Today fully I've spent flashing old Nougat TWRP sys_image backups and no use...
So all combos tried and I'm in total vain.. Devs if able to help Pls let me know., I can share all possible logs.. I am curious to know what's the problem or how its caused, so that others can play safe...
ariyan rana said:
arvindgr said:
pl check my reply https://forum.xda-developers.com/showpost.php?p=74936334&postcount=6
Click to expand...
Click to collapse
i thinks its motherboard problem.
Click to expand...
Click to collapse
I've visually inspected MB and found no clues of burnt components.. Also OP3 is one of well-built phones hence I suspect H/w issue in the last place..
Just because of my wildest dreams I got into this prob after Oreo OB fw update, (I remember I was dash charging that time) Can firmware files interfere USB data port interface?? @jamal2367 Pls provide your guesses...
Hi Guys,
Update on this thread:
Since I got no response, I was somehow managing with my OP3 but now this issue has grown like blocker for me. Now despite connecting with PC, Charging line is also not working properly.
So, I connected to charger last night. It charged only till ~70% and phone was fully heated up. I tried reconnecting charger and phone doesn't show its charging. Then assumed some cable/charger issue and continued using. Evening when I connected back, it was charging but dead slowly. Like from 20% to 50% in 3-4hours! So, this deems phones as almost dead, forcing me not to use it any longer. Pls help with any suggestions to resolve this...
I am having the same issue if anyone found any fix please let me know
I'm having weird problems with the PC to USB connection on a oneplus 3. Im trying to get it to recognise so that I can flash it back to stock, but my PC always gives the "the last device malfunctioned" error and it always shows up as "unknown usb device (device descriptor request failed)"...
This happens in MSM bulk mode, fastboot mode and even in recovery mode. Tried it on a windows 7 and 10 pc, no dice, can't even install the driver. Tried a different cable too. It works completely fine on another op3...
Replacing the USB c port didn't work either. Has anyone had a similar issue? Charging works fine...
I'm hoping it's somehow a software issue because otherwise it's looking like a mainboard issue and these seem quite expensive to replace... so any tips or advice are very welcome
Thanks already
dafonehacker said:
I'm having weird problems with the PC to USB connection on a oneplus 3. Im trying to get it to recognise so that I can flash it back to stock, but my PC always gives the "the last device malfunctioned" error and it always shows up as "unknown usb device (device descriptor request failed)"...
This happens in MSM bulk mode, fastboot mode and even in recovery mode. Tried it on a windows 7 and 10 pc, no dice, can't even install the driver. Tried a different cable too. It works completely fine on another op3...
Replacing the USB c port didn't work either. Has anyone had a similar issue? Charging works fine...
I'm hoping it's somehow a software issue because otherwise it's looking like a mainboard issue and these seem quite expensive to replace... so any tips or advice are very welcome
Thanks already
Click to expand...
Click to collapse
Try a different usb cable. I was using an anker usb c which finally worked. Got an original dash charge and it craps out. The usb c port on our phones is just weak compared to modern phones. Mine is giving out slowly and gradually after more than 2.5 years and I have to angle the connector at times for the charging to start. Guess it's slowly dying
nagi_007pk said:
Try a different usb cable. I was using an anker usb c which finally worked. Got an original dash charge and it craps out. The usb c port on our phones is just weak compared to modern phones. Mine is giving out slowly and gradually after more than 2.5 years and I have to angle the connector at times for the charging to start. Guess it's slowly dying
Click to expand...
Click to collapse
It's not the cable. It works fine on another phone and I tried a samsung and anker cable....
My particular issue was similar to ROKLAF here in this thread
thread
my phone entered Qualcoomm crash dump mode after flashing pixel experience. When connected to USB it would show up as "USB Device Not Recognized".
MSM downaloder tool also does not recognize my phone
After updating
Qualcomm HS-USB QDLoader 9008 Drivers - FOR THE 64-BIT ARCHITECTURE : https://www.mediafire.com/file/5wc5nk5adevatrj/QDLoader_HS-USB_Driver_64bit_Setup.exe/file
Qualcomm HS-USB QDLoader 9008 Drivers - FOR THE 32-BIT ARCHITECTURE : https://www.mediafire.com/file/q1uynnim8arbim9/QDLoader_HS-USB_Driver_32bit_Setup.exe/file
OnePlus Drivers - https://oneplususbdrivers.com/#choose-device
I pressed the volume up and volume down and power button for about ten seconds, oneplus fastboot logo shows up, then it boots into Qualcomm crash dump again.
After this step, turn off the device using volume up and power button for ten seconds
and immediately pressing volume up and volume down button I was able to sucessfully register my device on MSMDownloader tool and unbrick my device via a fresh install.
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Wachecheiro said:
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Click to expand...
Click to collapse
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
sdembiske said:
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
Click to expand...
Click to collapse
I'll take a look at it, thanks
Seems like a similar problem as I had, that's not gonna work though. The only way to fix it is to use a firehose which you can use a one from a Cyanogen MSM8939 device.
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.