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.
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.
No comments:
Post a Comment