hey guys...
it sucks so hard.
My setup:
Ubuntu 14.04 x64
Windows 10 in Virtualbox
LG G3 (stock 5.0)
My goal:
Flash latest kdz (marshmallow) with a tool available for linux.
-or-
Update my phone to Marshmallow using LG Mobile Support Tool / LGUP / LG PC Suite in a Windows10-VM on Ubuntu host.
My status:
Linux: Did not find any flashing tool which works with Linux.
VM:
Windows 10 - check.
LG tools - up and running.
But... Neither Windows nor - of course - the different LG tools recognize my phone.
It seems that Ubuntu will correctly recognize the G3 when it's connected as PTP-device.
Same with "adb devices". The celly is only recognized when connected via ptp.
Strange: Though not listed with adb devices I can access my files over mtp...
Unmentionable that the whole bunch of the windows tools seem only to work when device is connected correctly via mtp.
Is really the only way to run this update finding a windows-buddy?
Solutions, anyone? #desperate
"Work-Around":
Today the ota-update was rolled out. Next problem was that my phone is encrypted and the update can only be installed when the phone isn't encrypted. So: Decryption in progress.
But: I'm still interested in a solution for the ones who a working with linux.
I've tried to upgrade an (old) LG D605 using the windows Flash Tool under a VirtualBox VM (running Windows 10) and using the drivers linked in that website (after setting UP VBox to use the phone USB device in the guest), worked as expected.
Try vmware or parallels
Related
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
Let me start off with the basics...
Nexus 7 (2013) - Stock Rooted 5.0.2
Variant: flo 16G
HW Version: rev_e
Bootloader Version: FLO-04.04
Tried MTP on/off - Doesn't work
Tried USB Dev on/off - Doesn't work
Tried on Windows 7/8.1 - Doesn't work
Tried on Ubuntu 14.04/14.10/Linux Mint 17/17.1 - Doesn't work
EVERYTHING WORKS on Mac OSX Maveric and Yosemite!!!
MTP and ADB and Fastboot do not work at all. In linux, lsusb shows nothing. In Windows, Device manager shows no changes (also, never plugged it in before this and followed Wug's toolkit howto exactly).
When I plug the device into my girlfriend's MacBook Pro (10.10 Yosemite as well as when she was on Maverics) everything works. On her Mac, ADB works, Fastboot works, and MTP (using the android transfer tool) works flawlessly. This is using the same exact USB cable that I used on all other systems. I tried this on my Linux laptop and a Windows desktop. Triend all USB ports. It seems my tablet will only work with a Mac.
Any ideas??
Does the laptop or desktop recognize the tablet? Is the Android SDK up to date?
I don't use the full SDK. I use android-tools-adb and android-tools-fastboot which is a cross platform toolset. This works for 2 of my phones, my ouya, and her phone so I know its just the tablet. The 3 phones and the ouya work on the windows desktop and laptop but not my tablet. As soon as I plug the tablet into her Mac, it is detected right away. I really wish I can solve this... I hate taking her MacBook from her every time I want to tinker with things.
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Let windows download the fastboot drivers from the network.
boot into fastboot, connect to pc
open up
win-r
devmgmt.msc
right click the 5x device and search network for drivers (or wherever that option is)
It'll come it with something like marshall london bootloader interface. That is fine, it works, it is for different phone that is also android based. The bootloader interface is the same.
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the very same problem when I first received my 5X. I tried every damn think on to get Windows 10 to see the device, including all listed here and manually installing the drivers downloaded from Google and various other sites. Installed various Windows 10 packages. Even LG driver packages. I believe the issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer. I'm willing to bet it would work just fine on 7 (did on every machine I tried). Eventually adb and fastboot magically started working but I still could not use MTP. The ONLY thing that got it working was, strangely enough, a reinstall of Windows 10 (chose to kept files/documents) and then updating with the Anniversary Update). I know that is like the LEAST desirable option.
Windows 10 is really just not great for this sort of thing.
stmims1124 said:
The issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer.
Click to expand...
Click to collapse
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.
sfhub said:
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.
Click to expand...
Click to collapse
Yeah, that's exactly how it's worked every other android device I've owned too-only had issues with this device and this particular Windows 10 machine. This machine is configured to get drivers automatically, but for whatever reason I just couldn't get this to work. Of course, this was just my experience but there have defintiely been other folks out there with similar (maybe not exactly the same) problems. It was infuriating!
I can't really comment intelligently regarding what Google may have done to fix this. I'm shaking my head to hear that their drivers for Nexus devices is missing the fastboot USB ID's for a Nexus phone lol
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....
---------- Post added at 10:45 PM ---------- Previous post was at 10:34 PM ----------
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....
Thanks to all, I've solved with Google -> Android Bootloader Interface and it seems it works.
I attempted a downgrade 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, 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, 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 driver, I installed Win 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. . Ihave 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
I got stuck in that same boot loop as you. There's a thread that claims that the D851 is unbrickable: https://forum.xda-developers.com/tmobile-lg-g3/help/lg-g3-d851-unbrick-qualcomm-9008-t3430221 But I was also unable to get it to work on my laptop. I think some computers may have a hard time using the drivers correctly and maybe trying another computer is your best bet.
But personally, I ended up sending mine to a J-Tag service on eBay and paying some $30 to get the thing completely reset.
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