Develop Bugs

*Solved* LG G3 No longer connects to PC via MTP/PTP - Only Charge-only

Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Edit: *SOLVED*
Ok so turns out the issue is, and this is just my case, my motherboard has various utilities, one of which is a USB 3.0 boost option.
When I did an upgrade to Windows 10, it somehow screwed up various programs on my PC including registry etc.
I reinstalled the particular utility (I was actually trying to fix my graphics clock etc so happy coincidence) which also re-installs the USB 3.0 Boost software which in turn has fixed my USB Ports.
So if you have a custom built PC (my Motherboard being a Rampage 4 Formula). Check the Mobo Utilities/Drivers for any conflicts.

I have the exact same problem, and I can't seem to find a solution for months now. It's really annoying and depressing

nicholsonr said:
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Click to expand...
Click to collapse
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089

ludoke said:
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Using the drivers on that page you have advised gives the following.
Device Manager shows a Warning on it in USB controllers as "LGE Mobile USB Composite Device". It automatically "malfunctions" according to Windows 10 and I can't change the connection interface on the phone.
Going into the properties on that device in Device Manager lists the following;
This device cannot start. (Code 10)
A device which does not exist was specified.

http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button

TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
Click to expand...
Click to collapse
This didn't work. Already tried

Fixed my problem
I've had the same issue with my LG G3 in being unable to connect the device to my laptop. I'm not sure if the cause was a phone software update or the upgrade from Windows 8.1 to Windows 10. Either way, I searched and fixed it tonight by installing updated drivers. Hope this helps others as well.
Hmmm, I cannot post the link! technobuzz dot net lg g3 drivers
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!

Op3 usb storage not working

Hi
I am trying to connect my one plus 3 to laptop as a USB storage device and its not working. I tried to change settings in developers option but its still nor working. I can only change phone.
I would be thankful if anyone can help me.

Nomi404 said:
Hi
I am trying to connect my one plus 3 to laptop as a USB storage device and its not working. I tried to change settings in developers option but its still nor working. I can only change phone.
I would be thankful if anyone can help me.
Click to expand...
Click to collapse
Change the option to File Transfer from the popup/notification on your phone when you connect it to the PC. It works for me.
EDIT: If it still doesn't change, check the adb drivers.

tnsmani said:
Change the option to File Transfer from the popup/notification on your phone when you connect it to the PC. It works for me.
EDIT: If it still doesn't change, check the adb drivers.
Click to expand...
Click to collapse
i am not getting any popup.

Check the sliding switch on the right hand edge of the op3 is "down" to allow ALL notifications. There are plenty of "install OP3 drivers" videos on Youtube. Windows drivers are also on the phone.
This should still work - the drivers are also supplied on the phone. Doing nothing other than connecting a op3 to a windows pc should cause a cd drive to appear in Windows Device Manager and in File Explorer (look under "This PC") for "CD Drive (drive letter: OnePlus Drivers" . Double Click the icon and run "OnePlus_USB_Drivers_Setup.exe". If you are running a recent version (and clean installed in the last few months) of W10 Pro then you may hit driver signing issues

Broken Screen/Digitizer need backup

Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit

Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0

jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk

jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.

tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works

Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb

jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.

Issues recovering data [adb] & not showing in 'This PC'

Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou

FinnSanity7 said:
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
Click to expand...
Click to collapse
If you had used adb before and the phone was recognised earlier, then there shouldn't be an issue. If not, then when issuing adb commands, there will be a popup on the phone asking you to enable authorisation and to make it permanent. In your current scenario, you will not be able to grant authorisation. Your drivers might be installed properly but because of this "authorisation" issue, the phone might not be recognised properly.
Search for methods to pull data from the phone. I had read about a couple of methods where you can mirror your screen on the PC which will solve the problem for you. Unfortunately I am not able to recollect where I read that.
EDIT: Enter fastboot mode on your phone and connect it to the PC. Then using 'fastboot boot twrp.img' you can boot into TWRP on the phone and access the files and copy them using adb commands. This requires the TWRP in the same folder as your adb tools or vice versa and renaming the file as TWRP. I don't know whether this also requires 'authorisation' but try it any way.

ADB - Cannot get it to work AT ALL. Euro H815

Ok - I'm looking for a top to bottom guide on how to get this working with my phone.
I'm wanting to install a new ROM on it to hopefully breath a new lease of life into my phone.
As I understand it, to do this I need to unlock the bootloader - and so on - and to do this using the official method I need to use the Android Debug Bridge.
I've downloaded the Android SDK - and run ADB.exe - but when I do "adb devices" nothing is returned.
I've tried assorted cables - assorted USB drivers and so on - but nothing seems to work.
So - I want to start from scratch - what do I need to do, to get a blank slate, to try again to do this.
What drivers do I need to uninstall to start again - and what should the process be, top to bottom to do this?
I assume the SDK files I downloaded is fine and working. (I've tried doing this on two different PCs - both Windows 10 though) and had the same results so I'm assuming the SDK is ok.
I've got a european H815 - which was updated to the most recent update available for the phone.
I've got Dev mode initiated on the phone with USB Debugging ticked.
Is there a specific order to do things?
Is there a specific order to initiating debugging so that it "catches"?
Does it matter whether it's on MTP or PTP or USB Tethering?
Any help would be greatly appreciated.
I think once I get this ADB thing sorted out, I should be ok, as I managed, back in the day to install several different ROMs on my old HTC Desire - and I never had this issue with that phone.
Please help!!!
PS - my PC is totally up to date with Win 10 updates too (which may well be a problem in itself)

So - I have tried the following LG Driver packages and none seem to work.
LGMobileDriver_WHQL_Ver_4.0.4.exe
LGMobileDriver_WHQL_Ver_4.4.2.exe
LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1.zip
UniversalAdbDriverSetup.msi
When I "Inspect Devices" via Chrome - the phone shows up ok too.
The phone is recognised as being attached to the PC and can be seen on the PC in the various modes (MTP, PTP, Midi and when USB tethered I think).
When the phone is connected by USB and a disable and re-enable USB debugging, I am asked if the PC cccess my phone data and I click "Allow".
I'm stumped.

Had another go on a different machine - and again the same things were happening.
Ditched another driver - not even sure if I even installed a different driver - I wasn't taking notes thinking that nothing was going to work anyway.
It just would not catch on the ADB.
But then I tried switching between modes whilst connected and somehow it worked!!!!!
Bish bash bosh - now I've got an unlocked bootloader!!!
Now for the next steps to getting some custom ROMs installed.

Note: I think the biggest issue was the screen asking to always trust the computer - when I did the bootloader unlock - it wiped everything (which I'd forgotten about!!!).
Anyway - as it was like plugging a new phone when I just connected to my home PC - it wanted to install PC drivers, and when I activated debugging, it flashed up the screen with a certificate??? ie a load of letters and numbers - asking if I want to trust the computer. (I can't remember the proper name for the screen - but have seen some people refer to it on other posts on here).
I said yes - and bang - first try - ADB works.
My advice - for anyone trying to do something similar and having problems with ADB - get everything backed up to begin with - and then do a factory reset.
That'll most likely reset stuff on the phone, and make things smoother...