Rutagengwa
Newbie
This tool is not working when i try to start i got this error msg (Device dload mode, device was not found in dload trying flash programmer)
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help HARD BRICK LG G2 qhsusb_bulk, but no partitions detected.
iowabowtech
root@android:/ #
^^Please see.
ohcafe02
Lurker
HELLO...iowabowtech
I'm in the same situation.
My PC detected Qloader 9008(via port 3 but I had chang to port41).
My model is LG G2 D802/32gb.
No drive found.No partition.No light on charging.Black Screen.
I tried so many methods but nothing work.
When use BoardDiag3.99c it shown <Device dload mode, device was not found in dload trying flash programmer>
I'm hopeless
.
Please guiding me what can I do to recover it.
(Apologize to my bad English)
I'm in the same situation.
My PC detected Qloader 9008(via port 3 but I had chang to port41).
My model is LG G2 D802/32gb.
No drive found.No partition.No light on charging.Black Screen.
I tried so many methods but nothing work.
When use BoardDiag3.99c it shown <Device dload mode, device was not found in dload trying flash programmer>
I'm hopeless
.Please guiding me what can I do to recover it.
(Apologize to my bad English)
Rutagengwa
Newbie
Hello, I think this tool is only working when device partition is shown on disk management for my lg g2 F320L no partition found iv even use a tool download here https://mega.co.nz/#!pZQyXbAD!960ZDw...2VPFMaAGkobtCc still nothing for my problem i need a special help thanks.
patilkalpesh
Newbie
have u solve ur problm bro.
patilkalpesh
Newbie
have u solve ur issue bro ...if not...reply me...
patilkalpesh
Newbie
have u solve ur issue...if not ,reply me i will solve through teamview
patilkalpesh
Newbie
bro if u want to solve ur issue reply me ....i will help u out...
Rutagengwa
Newbie
Now my lg g2 f320l is working again from Qualcomm HS-USB QDLoader 9008 I v just use a tool download here https://mega.co.nz/#!pZQyXbAD!960ZDwH36ZwqY2C7CoiDdfgxCRodU2VPFMaAGkobtCc follow instruction from here http://forum.xda-developers.com/showthread.php?t=2432476 for extract a KDZ file use WindowsLGFirmwareExtract and about how to create a partition.txt follow this link http://forum.xda-developers.com/lg-g2/general/how-to-create-partition-txt-file-kdz-t3109859.
Thanks to all who helped me and developers.
Thanks to all who helped me and developers.
Rutagengwa
Newbie
Solved
Rutagengwa
Newbie
Any difference between RELINK HS-USB QDLoader 9008 and QUALCOMM HS-USB QDLoader 9008 My phone lg g2 d801 is recognised in device manager as RELINK HS-USB QDLoader 9008 and is dead no recovery no download mode when i try to use board diag v2 no result SDRAM test fail (capture666) and device not boot
Attachments
iowabowtech
root@android:/ #
I can honestly say I've never seen one show up like that. What you can try though is to go to the restore device section of the tool, and in the restore boot img drop down, select every partition one by one and see if you can restore that way instead.
Rutagengwa
Newbie
Hallo
I have bricked my G2 (d802) by updating Cyanoigenmod. Window shows a lot of drives and the device description is qualcomm 9006.After I start the phone it shows the LG logo and then it remains black. Is there any chance to fix this problem without loosing my data?
Thanks in advance
I have bricked my G2 (d802) by updating Cyanoigenmod. Window shows a lot of drives and the device description is qualcomm 9006.After I start the phone it shows the LG logo and then it remains black. Is there any chance to fix this problem without loosing my data?
Thanks in advance
iowabowtech
root@android:/ #
It MAY be possible but I wouldn't plan on it. If you could use the dd utility in Linux to write a TWRP recovery.img which would work together with the current firmware you have on the device, then you could possibly save sdcard contents by using adb pull. If you are looking to save userdata from the already borked CM rom install, then no.
In some situations similar to your own, the sdcard may be unreadable or it shows up as void of all contents.
Thank you for your quick response
I tried to write a recovery.img using ADB and SRK tool 2.1 in Windows 7 but both tools didn't find my phone. Am I right in assuming that the data will be lost if I try to fix it using SRK "FIXED UTILITY"? I do not know anything about Linux. Is there a chance to write a recovery in Linux even if it didn't work in Windows 7?
I tried to write a recovery.img using ADB and SRK tool 2.1 in Windows 7 but both tools didn't find my phone. Am I right in assuming that the data will be lost if I try to fix it using SRK "FIXED UTILITY"? I do not know anything about Linux. Is there a chance to write a recovery in Linux even if it didn't work in Windows 7?
iowabowtech
root@android:/ #
Yes there's a chance and it may also be possible in a Linux virtual machine. People have had hit and miss success on that. The basic way to do it is seen here:
http://forum.xda-developers.com/showthread.php?t=2582142
You wouldn't necessarily flash all the partitions they list there. Since you evidently had a custom recovery recently, you may be able to get by with flashing the TWRP recovery img which is suited for your current firmware.
Rutagengwa
Newbie
Same issues with my Samsung SM-G360F including the following
- when i connect to cherger the screen displays the battery but won't charge
- When i try to turn the phone on it stuck on samsung logo
- When i boot to recovery it displays only the following errors : MMC:mmc_read fail Movinand checksum confirmation fail.
If any one have advise on how to fix this issue please assist thanks.
- when i connect to cherger the screen displays the battery but won't charge
- When i try to turn the phone on it stuck on samsung logo
- When i boot to recovery it displays only the following errors : MMC:mmc_read fail Movinand checksum confirmation fail.
If any one have advise on how to fix this issue please assist thanks.
You may want to poke around and ask over here for that device:
http://androidforums.com/forums/samsung-galaxy-core-prime.3203/
as it's a different animal and may require a different process to fix it
Alex050316
Lurker
I have an urgent recovery situation, so I hope that you receive this ASAP. I don't have long to resolve this issue.
Does this apply to an LG G4 that shows "qhsusb_bulk"? Are you able to help me?
iowabowtech
root@android:/ #
I thought they patched the bulk mode vulnerability on the G4 but if you do truly have 9006 bulk, where the partitions are showing up as drives in Windows, then yes it could apply. You may wish to install the Qualcomm driver. It will allow you to see if its 9006 or 9008.
Alex050316
Lurker
Thank you for the instant reply! I downloaded the zip folder from the dropbox link, but I don't even care if I sound uninformed... I'm not sure how to install the driver(s) in the zip folder.
iowabowtech
root@android:/ #
Unzip into a regular folder. With device plugged into pc, goto device manager and right click on device labled as bulk. Choose option to update driver, use option to manually install driver, point to the entire folder of driver files you just unzipped as the source. Windows will search out the files it needs. Afterward, the phone should change the way it shows up in device manager to include a more detailed description including 9006, 9008 etc.
Alex050316
Lurker
Thank you so much! It seems it is 9008. I'm wondering if the fix you are suggesting is for sure applicable to the LG G4.
Thank you again for your help!
iowabowtech
root@android:/ #
Last I knew, the mbn's were not available for the G4. In other words, the 9008 unbrick tool will not work for your phone. If somebody has acquired the necessary files to unbrick from that state, it would almost certainly be on xda developers site. Best of luck to you and sorry I can't assist further.