Develop Bugs

LG G3 not recognized under Device Manager Ports.

Hello, I was trying to go back to stock Kitkat by using the LG flash tool. I ran into a problem where my phone went into Factory Reset Status 2. I'm now trying to follow this guide to completing this. http://forum.xda-developers.com/lg-g3/general/problem-returning-to-stock-try-t2862463
The problem I face now it that my computer won't list the phone under ports. I have downloaded the drivers. (Even re installed a few times) The phone gets listed under "Portable Devices" as LGE Android MTP Device. I need to be able to connect it to COM41 to fix this issue but I'm not sure what to do here. Any help is appreciated.

dipalp95 said:
Hello, I was trying to go back to stock Kitkat by using the LG flash tool. I ran into a problem where my phone went into Factory Reset Status 2. I'm now trying to follow this guide to completing this. http://forum.xda-developers.com/lg-g3/general/problem-returning-to-stock-try-t2862463
The problem I face now it that my computer won't list the phone under ports. I have downloaded the drivers. (Even re installed a few times) The phone gets listed under "Portable Devices" as LGE Android MTP Device. I need to be able to connect it to COM41 to fix this issue but I'm not sure what to do here. Any help is appreciated.
Click to expand...
Click to collapse
Should be able to just omit that step. When I used the flash tool mine was not listed under under ports when I did.
Should be listed under that after you change the setting.

##diag# ##3424# enable diag port

Driver LGE Android MTP Device

This thread is about the defective installation of the LGE Android mtp device driver. Note that when the phone is on all the drivers seem to work correctly (LGE mobile ADB interface under "android device", G4 driver under "portable devices" and LGE mobile USB serial port).
The issue presents when i switch the phone to "download mode"; in this mode the "G4" driver (which is the LGE Android MTP device) appears not to be working.
The problem persists on three different PCs, either with windows 10 or windows 7 and either with a LG G4 or an LG G3.
I would like to root my G4 device following the firmware flash procedure 10E, but I am not sure that I can flash the device if there is this kind of issue with the drivers. Is it normal that the device appears not to be working?

I am having the same problem as you were. I am using Windows 7 and several versions of the LG drivers with the same result; Everything is fine when my device (a G4) is booted normally but in Download mode I get the same error as you (This device cannot start. (Code 10)).
I have tried everything I can think of, I have uninstalled all the old Android drivers with USBDeview, disconnected the internet to stop windows update installing its own drivers, different USB ports and cables.
Did you ever get your device rooted?

SO... in my case (YMMV - be careful) it turns out there is no need for the device manager to be error free when the phone is in download mode.
I just got root using this procedure from the "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread with no issue. I thought it would work because the LGMobileSupportTool was reporting as being connected to my phone despite the error (This device cannot start. (Code 10)) in device manager. Sure enough everything worked fine. I wish it hadn't taken me (literally) 20 hours of fecking around with drivers to get to this point though...
ETA I have a G4 H815 (EU)

i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?

012512 said:
i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?
Click to expand...
Click to collapse
Edit. Performed a factory reset and it worked as it is.

I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.

PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
But in my case only greenify is installed module,
Why you only post that After I factory reset my phone. Haha anyway thanks for the information.

PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
This helped me so much when I was trying to upgrade to Android M. After un-checking all my xposed modules, both my pc and laptop were finally able to read my LG G4 and install drivers, mtp, and others correctly without fail.

Same problem here with an AT&T G4. I've tried 2 different Win7 laptops (one of which has never had any Android drivers/tools installed previously), 3 cables, and even performed a factory reset. MTP Drivers work when booted normally, but fail ("Code 10") when in download mode. Any additional suggestions?
EDIT: As suggested by other posts/forums, this issue can be ignored, and isn't an actual problem. ADB works successfully, even if the MTP device isn't working in Windows' Device Manager. (This MTP device appears in Windows' Device Manager the same as it does when a USB Debugging connection hasn't (yet) been authorized on the Android side. My guess is that since Android isn't fully booted while in Download Mode, there's nothing to approve the connection. Either way, it doesn't affect the function of Download Mode, as long as the other Android-related devices in Device Manager have their drivers loaded successfully.)
TL;DR version: When in "Download Mode", as long as the other Android-related device(s) in Windows' Device Manager are working, ignore the "Code 10" error / "yellow triangle" on the MTP device. It's not needed for Download Mode to work.

soft bricked d855,goes into download mode but windows/adb/fastboot doesn't see device

Hi all, so this is my first post and a last resort attempt at recovering my phone, after hours of googling and downloading everything suggested by various forums, and still being stuck... Sorry for the long post, just trying to list all my attempts to fix it.
So, I've been on stock 5.0 Lollipop (v20n) for a long time, with the only issue being that android OS suddenly will decide for no good reason to make my phone super hot and drain my whole battery in 2 hours flat... Nothing that worked for other people worked for me, so yesterday I decided f*ck it, i'm gonna root and flash Fulmics 5.0, using this: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 (tried the classic method).
Everything went as per instructions, until I went "Send_Command.exe \\.\COM12 < reboot" and the phone got stuck in a bootloop...
So in other words, my phone is not rooted yet (thus nandroid/titanium backup was not made), TWRP was not installed (so i cant reflash stock kitkat). Latest LG drivers are installed (v4.1.1.0 from http://lgusbdriver.com/windows/lg-usb-driver-v4-1-1-0). Adb and fastboot are installed (http://forum.xda-developers.com/showthread.php?p=48915118#post48915118).
I can boot into download mode (Volume up + plugging in my usb cable), but i cant get adb or fastboot to see my device, when i try to flash twrp.img though command prompt! Downloaded the LG Flash tool 2014 to try and reflash stock kitkat 4.4.2 v10E, but it also can't see my device!! LG PC Suite can't see my phone when trying to connect...
I have removed the LG drivers from device manager and reinstalled the 4.1.1.0 drivers several times, but everytime i plug in my cable Windows (7 ultimate) tries (and fails) to install some drivers for it, even though i installed them already.
I tried to do a factory reset (holding volume - and power button, releasing and pressing them again when i see the LG logo), it gives me the option of doing a reset, but it goes back to the bootloop.
I have installed the Android SDK files (https://developer.android.com/studio/index.html), not the whole 1187mb SDK bundle, just the 144mb installer_r24.4.1-windows.exe. But i cant get my pc to see my device!
Went to a friends house and installed the LG drivers on his pc, installed adb and fastboot (as above), opened a command prompt in the folder where the adb and fastboot dll's are, and neither "adb devices" nor "fastboot devices" lists my phone.
What am i doing wrong???
TL;DR LG G3 d855 stuck in bootloop, but can boot into download mode, no root, twrp recovery not installed, LG drivers and adb fastboot installed on pc, adb refuses to see my device but windows tries (and fails) to install some drivers when i plug the cable in. Factory reset didn't work. Need help please!

Can't get sdk to detect my device when is fastboot/bootloader.

Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.

I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.

My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.

had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.

First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.

My tablet is stuck as an unrecognised USB device by Windows 10.

Hi there. Sorry if I sound dumb. I'm new to this whole thing and this was supposed to be my first experience with flashing custom ROMs and stuff like that. I was planning to get ready to install LineageOS on my Nexus 7 using a Windows 10 PC. Unfortunately, things quickly went south.
My first roadblock was the tablet not being recognised by fastboot. I checked online for a bit and from what I could gather, the solution was to install the Google USB drivers using device manager. I went into device manager, right clicked my Nexus 7 in "portable devices", selected "update driver" and chose the Google USB driver I downloaded from the official Android developers website. I'm not sure if this is relevant but the tablet was in fastboot mode when I did this. From that point on, my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode, and regardless of which USB mode I choose.
I tried uninstalling the driver, factory resetting, WugFresh NRT, and using different cables and USB ports. I checked for all sorts of solutions but they either didn't help or they require an unlocked bootloader (which was the very first thing I tried to do before finding out I needed to install the driver for fastboot to recognise the Nexus 7). Does anyone here know of a solution to get this working again? I'm completely stumped on what to do.
EDIT: I tested with a Chromebook and an old Windows 7 PC I had lying around. Neither could detect my Nexus 7 and the W7 PC even said it failed to install the driver as soon as I plugged it in. It seems that the driver update screwed up my tablet somehow and I have no idea how to fix it. I really don't understand how this could have happened considering I followed Google's own instructions for updating the driver.
Does anyone perhaps have a copy of the OEM driver for the 2013 N7 Wi-Fi (flo) model? ASUS don't distribute the driver on their website anymore and I'm out of ideas.

BenSkylake said:
my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode
Click to expand...
Click to collapse
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root

k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
Thanks for the response. I don't think I'll have enough time to try this today but I might as well ask. Do any of these fixes work without needing a USB connection to a PC, or if they do, do they require adb and fastboot to work? Because if so, I won't be able to use them since my USB data connectivity is completely busted no matter what I plug my Nexus into.

k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
I just ran the RESTOCK 1 script and it worked wonders! My tablet's USB connectivity has been fixed and as an added bonus, my bootloader is now unlocked. I'll be continuing the process in Linux on my Pixelbook since it doesn't require any driver installations as far as I know. Thank you so much! You're a life saver!