I have LG G3
with android 5.0 lollipop
and I want to connect it to my laptop with windows 8.1
OS (For using unity remote).
When I connect my phone I can access to storage but I can't see my device in adb.exe
. I tried many solution like this and this but nothing work for me.
For now in developer mode I checked these:
- Stay awake
- USB debugging
- Allow mock locations
And I installed the driver from lg website. This is output for adb usb
command:
shell@g3:/ $ adb usb
adb usb
error: device not found
Actually I really confused because I think it recognize my device and show g3
name but I don't know why it can't show my device name in attached device!!!
This is windows command prompt screenshot:
Without lg driver installed, my device in device manager is like image below and when I try to update the driver using Android\android-sdk\extras\google\usb_driver
it say: Windows could not find driver software for your device
And when I install lg driver, my device is like image below and again i can't update driver and it say: Windows has determine the driver software for your device is up to date
C:\Users\hossein>
, while yours isshell@g3:/ $
. That's what a Unix prompt looks like, and that means you're in your device's shell interface. If I am correct about this, then the reason youradb devices
command doesn't work is because your phone is looking for other phones connected to it - of which it finds none. – dantis May 19 '15 at 12:02shell@g3
) looks like the shell of your phone. What commands did you enter until you got to that screen? – dantis May 21 '15 at 02:07shell@g3
shows you are executingadb devices
*on the G3, not on your Windows computer. What happens when you executeadb devices
from the Windows* prompt? – Izzy May 22 '15 at 15:49abd shell
. And that was the result foradb devices
command – Yandirr May 30 '15 at 11:35adb devices
*on the device itself*, which makes no sense – as (usually) there are no other Android devices connected to it. There are some lines missing at the top; I bet one of them readsadb shell
(which opened a shell to the device, so that's where you are). – Izzy May 30 '15 at 20:41