Develop Bugs

MTP device not showing

Hi, I just flashed the 4.4 official image from google. Still on stock recovery.
I do plan to install custom recovery to flash some custom rom now.
However, when I try to plug my tablet in laptop (windows 7 64bit), all i hear is that ding sound, hover over the usb devices i would see nexus 7, but it is not showing in the Windows Explorer.
PTP would show, but MTP wouldnt, with or without usb debugging enabled.
I tried to update my usb driver from google via SDK, i uninstalled first before upgrading so its a clean install, however i am still stuck here.
Any other solution?

hhwong said:
Hi, I just flashed the 4.4 official image from google. Still on stock recovery.
I do plan to install custom recovery to flash some custom rom now.
However, when I try to plug my tablet in laptop (windows 7 64bit), all i hear is that ding sound, hover over the usb devices i would see nexus 7, but it is not showing in the Windows Explorer.
PTP would show, but MTP wouldnt, with or without usb debugging enabled.
I tried to update my usb driver from google via SDK, i uninstalled first before upgrading so its a clean install, however i am still stuck here.
Any other solution?
Click to expand...
Click to collapse
If you have Wugfrest Root Kit, in there Click Full Driver Installation Guide - Automatic + Manual and follow his instruction.
Or you can uninstall the driver and update the driver yourself to a specific location on your computer. (this method i used) I run Win 7, and it would detect Nexus 7 but fail, when it told me to update driver i went to the folder where i put the drivers. Eventually you will find the right driver. Its a pain in butt to get the drivers to work sometimes.

Duffmantp said:
If you have Wugfrest Root Kit, in there Click Full Driver Installation Guide - Automatic + Manual and follow his instruction.
Or you can uninstall the driver and update the driver yourself to a specific location on your computer. (this method i used) I run Win 7, and it would detect Nexus 7 but fail, when it told me to update driver i went to the folder where i put the drivers. Eventually you will find the right driver. Its a pain in butt to get the drivers to work sometimes.
Click to expand...
Click to collapse
I manually updated the driver from the SDK and it worked, not too ure why exactly......but oh well.....its working as MTP with usb debugging enabled now

Download mode drivers won't install

Hey
I wanted to install Lollipop on my D855 using KDZ file so I proceed using instructions:
1. Install LG drivers
2. Enter download mode on the phone
At step 2 Windows detects new device and starts to install drivers.
For some reason it fails to install LG MTP driver. In the error I see "Device could not be started (Code 10)"
I tried this on:
my laptop (english Windows 7 x64)
desktop (polish Windows 7 x64)
virtualbox (windows 8.1 x64)
All with the same result. Could not install the driver
Is this normal and I should just proceed with LG Flash Tool 2014 or something is definitely wrong?
Bartek

Try to download the latest driver.
This one worked for me https://mega.co.nz/#!fR4QWApA!OMCuZzz9ZpBoHxOcxjDM49hL11iVHjYW-b2ttdH1c9w

i get the same stupid bull**** on XP and 7, can't win for losing seeing how i softbricked my lg g3.

Wow 3500 people have viewed ur thread yet only 3 replies how selfish this world is...
Simple solution go to device manager uninstall all the lg drivers reinstall all them again make sure ur screen is on when it ask to connect to pc select yes a drive will be shown on ur pc named g3

Impossible connection by MotorolaDeviceManager_2.5.4 in Windows 10

Hi, I have a problem with connecting to my AMD64bits PC with Windows 10.
I Install the MotorolaDeviceManager_2.5.4 tool in both normal and unsigned driver mode, starting Windows in a way that does not require the drivers to be signed, I also install it in compatibility mode and it effectively tells me that it is incompatible but Which is fixed.
The truth is that the PC recognizes Moto Z Play when in Bootloader mode but neither MotorolaDeviceManager_2.5.4 nor any other recognizes it.
My question is which driver can I use and where can I find it, I'm stressed.

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.

Boot loop after attempted downgrade of TWRP

Originally posted in LG G3 TMobile forum, but reposting here to reach a wider audience.
-----------
I attempted a downgrade of my TMobile G3 (D851) to an older version of twrp via twrp in recovery mode. Not sure what I did wrong. Now my LineageOS hangs at the LG logo at startup. When I try to access TWRP using recovery mode, the LG logo flashes on and off (loops). I cannot access the LineageOS to enable debugging, OEM unlock, MTP USB mode, place TWRP/ROM files on phone, etc...
From a Windows XP SP3 desktop:
I can manually put my D851 into Download mode and can get from Download mode to firmware update mode when connected to a Windows XP computer. The Windows XP computer sees the phone as new hardware ("LGE Android Net MTP") device when connected in Firmware Update mode. In Firmware Update mode, I cannot properly access the phone using the LG PC Suite, ADB/fastboot tools, MTP transfer, etc...
I have tried installing various versions of the LG United USB drivers. Originally, the driver installs failed citing "Windows MTP driver" not found and advising me to install Windows Media Format Update. After learning Windows Media player contained the Windows MTP USB driver, I installed Windows Media Player 11. Now the LG United driver install fails but without mentioning missing Windows MTP driver or Windows Media Format 11 runtime updates. I have tried installing the USB drivers using LG PC Suite but it too fails when reinstalling the driver. LG PC Suite cannot connect to my phone. I have tried to install the LGMobile Support Tool (ie. LGMobile Phone Software Update Tool), but the install seems to hang.
I feel that if I could just get a computer to communicate properly with the phone while in Firmware Update mode, I should be able to restore my phone. Does anyone have any ideas on other things I might try?
Thank you