Database Users

LG G2 D802 Unidentified device Unknown device

I'm connecting the LG G2 D802 to the Windows 7 in download mode, with LGMobileDriver_WHQL_Ver_4.0.4.exe drivers installed, however the drivers fail to install.
{
"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"
}
Unknown device
Unidentified device

Install drivers manually and disable windows update to override whatever windows wants to install from there...

The issue was happened when trying to flash some LG G5 adapted rom on the LG G2, so the bootloader or the recovery got damaged. What I finally did was to force qhsusb_bulk short circuiting the capacitor and then using SRKtool_2.1_droidth.zip to use the unbrick method.
Then, you can reboot to download mode to use LG Flash Tool or reboot to recovery to flash the partition of your particular rom using dd (once you upload the partition images to the smartphone sdcard).
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Hey scandium, I know it's been years since you've posted this,
but I was wondering if your phone symptoms were unknown device on any pc+slow charging with any charger. I currently have a G2 in this situation. It works, but has no USB connectivity whatsoever, and takes ages to charge. Do you think that shorting the capacitor and flashing the phone from scratch would fix it? I'm afraid of trying it and when connecting to the PC still get the unknown device problem and end up with a brick. Thanks in advance.
scandiun said:
The issue was happened when trying to flash some LG G5 adapted rom on the LG G2, so the bootloader or the recovery got damaged. What I finally did was to force qhsusb_bulk short circuiting the capacitor and then using SRKtool_2.1_droidth.zip to use the unbrick method.
Then, you can reboot to download mode to use LG Flash Tool or reboot to recovery to flash the partition of your particular rom using dd (once you upload the partition images to the smartphone sdcard).
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse

Mrkblo said:
Hey scandium, I know it's been years since you've posted this,
but I was wondering if your phone symptoms were unknown device on any pc+slow charging with any charger. I currently have a G2 in this situation. It works, but has no USB connectivity whatsoever, and takes ages to charge. Do you think that shorting the capacitor and flashing the phone from scratch would fix it? I'm afraid of trying it and when connecting to the PC still get the unknown device problem and end up with a brick. Thanks in advance.
Click to expand...
Click to collapse
I did not have any problem with charging.

Bricked my A2017G

Hello guys,
I tried to update my phone to Nougat and I guess I totally failed.
First I just tried to flash this rom: https://forum.xda-developers.com/axon-7/development/rom-purefusionos-official-t3670580 and it did not work. So I thought I might have to update the firmware first and installed the A2017UV1.1.0B32 NOUGAT Update from this thread: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484. I found out I had to flash (with TWRP) the firmware's G version so I took the A2017G_N_Modem.zip from this https://androidfilehost.com/?w=files&flid=148464.
Now I only get the "your device software can't be checked for corruption. Please lock the bootloader".
Can somehow help me and tell me if and how I can get a rom working again?
Thanks in advance.

Check forum. There are topics to unbrick your device.

Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.

multimill said:
Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.
Click to expand...
Click to collapse
When led blinked you are on EDL mode. Screen is black on edl mode.

Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.

multimill said:
Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.
Click to expand...
Click to collapse
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.

WesTD said:
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.
Click to expand...
Click to collapse
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
{
"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"
}

multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
Good luck. Your device on DFU Mode. There another guide about it.

multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
4th category brick repair manual, google it

i probably hard bricked a1 open for any ideas ( only launch in edl mode)

Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"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"
}

onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver

hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.

onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?

OnePlus 6T Bricked

Hello,
This problem has come up a lot i'm sure, but having looked at what feel like everything in xda website nothing has worked for me.
How did this happen? Phone froze and i held power button to shut it off, and it never booted past oneplus logo(Somehow corrupted itself). I went into recovery and wiped the phone since i dont keep much data on it. Instead now my phone is stuck on wiping itself.
FYI, the phone had Android 10.0.1 installed on it if that makes a difference.
My OnePlus 6T is bricked and here is what i can and cannot do:
Can do:
Boot into fastboot mode
Have the phone detected in ADB tools
Have the phone detected as Qualcomm HS-USB QDLoader 9008
Can't do:
Unlock the bootloader(Bootloader has never been unlocked on this device so i cant flash anything)
Boot into recovery mode(Vol up + power boots the phone instead)
Device wont boot past "Wiping, please wait." (Yes, i have waited HOURS for this to fix itself, nothing happens)
Tools i have tried to no avail:
MsmDownloadTool (All versions, nothing works! I get "FireHosecheckrsp failed errno 258" error. I have tried all possible drivers and cables as per some tutorials and discussion but nothing
I have tried MsmDownload tool int Windows 10, 7, even Vista(FireHosecheckrsp failed errno 258 every time)
Tool All In One, I cant flash anything through here since my bootloader is locked and i cant unlock it.
Flashing TWRP or other recoveries doesnt work because of locked state.
Anyway, sorry to ramble here. If anyone has any ideas, i would be happy to hear.
Best Regards

You have several serial ports interfering with the tool, so click the COM port bar and select the one belonging to the Snapdragon modem in the OnePlus 6T phone, and run this tool again. Error 258 is serial port conflicts or USB connection issues.
If unsuccessful, you will need to install Qualcomm USB driver. I am not sure if you have installed it though.
Sent from my ONEPLUS A6013 using Tapatalk

Dr. Mario said:
You have several serial ports interfering with the tool, so click the COM port bar and select the one belonging to the Snapdragon modem in the OnePlus 6T phone, and run this tool again. Error 258 is serial port conflicts or USB connection issues.
If unsuccessful, you will need to install Qualcomm USB driver. I am not sure if you have installed it though.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
COM4 is currently the only one that shows in MsmDownlaodTool and Qualcomm drivers are installed.
{
"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"
}

That's odd. Did you either try new USB-C cable, or getting the lints out of the USB-C port on the phone?
Sent from my ONEPLUS A6013 using Tapatalk

Dr. Mario said:
That's odd. Did you either try new USB-C cable, or getting the lints out of the USB-C port on the phone?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I have tried the original cable along with 2 others, which are from OnePlus as well. There is no dust or lint or anything in the port, fairly clean. :good:

I need help trying to restore my Note 7

My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue

1Henryx said:
My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue
Click to expand...
Click to collapse
For fastboot you just need to update the drivers, run the same process you did sometime, when it, firstly, worked. Remember that a corrupted device must have the drivers updated, a kind of communication lost, nothing more.
I´ll upload some screenies from the process you need to do:
{
"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"
}
Once you get it, repeat the process, i.e. boot to recovery and flash the ROM.