Has anyone gotten their computer find their G4 through cmd (adb devices). I cant get the adb message on my phone to allow access to my computer. I turned on and off usb debugging several times but i still don't see the message on my phone to allow access. I let me computer download the drivers when plugging up my G4 as well as allowing the install of PC drivers.
yes, working great for me. Do u have updated and right drivers? u find tread here with right drivers..
Sent from my unlocked and rooted LG-H815
I was having the same problem..
You need to install the LG Drivers and then your phone will connect via adb..you will be asked on your phone to allow the port connection after installing the proper LG drivers. Verify and you will be good to go..
I used these ones below in the attatchment or you can grab them from.....
http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode-77723/
I think I found the issue. I had Note 3, 4, Nexus 6, S6 edge, and G4 all still on my computer in the device manager. I uninstalled all of them plus I uninstalled the adb driver in device manager. Plugged my G4 back in and ran the PC driver update via G4 and it worked. I can now see my G4. Don't know if I had to do all that to get it working but hey it worked for me.
I was having issues with this myself and didn't find a solution. I found out that I was having better luck switching it to Camera PTP from the notification dropdown. Sometimes I have to toggle to MTP back to PTP, The dev notifcation should appear when it is actually connected.
1. PTP
(1a. switch to MTP back to PTP if it doesn't work)
2. 'adb kill-server'
3. 'adb devices'
-If you see your device, you can try to 'adb connect **IP**' but it will most likely say it was unable to connect
4. give it your adb commands you want
It's the only way I've been able to get adb, hope this helps!
I was having this issue also. After install win10 then adb connection to my LG G4 (h818) was not detected. Back to android.com, it said that if general USB driver doesn't work then we must find OEM driver to the producer web. LG ADB Driver was about 17MB. After installed the driver then it was immediately detected. Thank God, finally.
I have silly problem. I bought used G4 LG from someone found in online forum. Checked all series on phone (sticker), on software "about phone" all showing LG H815 software version H81510H, but by adb ( linux machine ) showed H812xxxxxx .... set on developer option debugging the command "adb reboot bootloader" just send device into android boot ( device boot ). I wish to unlock the bootloader and put CM. Hard button option > pushing vol up + power button simultaneously did nothing, vol up + power button then > connect to PC via usb, did nothing ( just send phone to device boot ) ..... I have no windows machine
Related
Hi All,
I flashed TWRP to my sm-t320 with Odin in Windows. `adb devices' (in both Windows & Linux) can recognize my device but it always show unauthorized. Does anybody know how to fix that? but it's ok when I'm in twrp (turn off the tablet, then power+volume up to go to twrp: I didn't know this before, so this is for people like me), adb devices works fine.
dxxvi said:
Hi All,
I flashed TWRP to my sm-t320 with Odin in Windows. `adb devices' (in both Windows & Linux) can recognize my device but it always show unauthorized. Does anybody know how to fix that? but it's ok when I'm in twrp (turn off the tablet, then power+volume up to go to twrp: I didn't know this before, so this is for people like me), adb devices works fine.
Click to expand...
Click to collapse
Make sure you have USB Debugging enabled on your phone if you do turn it off connect your phone to your PC turn USB Debugging on and see if you get a message to allow your PC to connect to your Tab if you do then allow it.
Also check you have the correct drivers installed when connected to your PC
If you are on windows 7 right click my computer then properties and click Device Manager, look for Samsung Android Phones in the list and expand it, this should then say Samsung Android ADB Interface.
If you don’t see Samsung Android Phones your have the incorrect drivers assigned to you TAB, the one windows installs by default is generally the wrong one.
If you see Samsung Android Phones but when expanded it doesn't say Samsung Android ADB Interface then again the wrong driver is installed.
To correct it right click and select properties, then update driver, then click browse computer, then click let me select from a list Select Samsung Android ADB Interface.
When its installed you may get messages about devices not working properly just click OK to it, unplug you Tab then plug it back in again and wait for it to connect.
Open a CMD and type ADB Devices hit return and you device should be recognised,
If you are using TWRP then when you connect to your device in Recovery mode to your PC you need different drivers for that to work properly again the ones installed by windows as default are not the proper ones, it will work with the default ones but not correctly you probably will not be able to Push or Pull files or apk's.
Hi all, posting here because my other thread hasn't been seen.
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Update: I have found that at the least I should be able to see my phone in the Other Devices list in the Device Manager but I've got nothing, just ADB Interface
Alright I see. I am assuming you are using stock COS. So when you enable developer options and enabled android debugging your computer did not want to pick it up. Unplug device and Try revoking USB Authoriztions in developer options. plug swift back in and look at the device. It should ask you for Authroization
Thanks Yasteellutch. Still not seen by adb devices. I think I'll just clear the phone back to factory and try again...
B
Hi everyone,
@finnfather I think I have solved the issue. Today, I decided to manualy install (cm-12.1-YOG7DAS2FI) the latest cyanogen update as my phone didn't recive it as an OTA. I downloaded the zip package here and installed it through the stock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,
Jev
I cound manage the get a workung adb connection, buy switching adb debugging off and on again on the device while the device was connected to the pc via USB. Then I opened the device manager in windows and klicked on update driver vor the unrecogniced device. After that the device prompted a dialog, I had to accept the connection. Now the device was visible in the adb device list. (@jevtheboss: So you do not have to reinstall the cm to make it work)
Just a quick question.
Im unable to access fastboot or bootloader mode through adb command line.
I turned on usb debugging, connected phone to usb cable with my pc, run command line in platform-tools - adb devices and nothing happens.
I think i know the answer, but i want to be sure. Is it because i dont have unlocked bootloaded (OEM Unlock, still 6 days to wait)
Do you have the proper drivers? Try downloading the universal ADB drivers.
Sent from my Lenovo P2a42 using Tapatalk
Switch USB mode to PTP instead of MTP. I don't know why, but it works like that after Android KitKat/Lollipop release. Used this trick on LG G2 mini and now on my P2
I dont know if i have correct drivers, but i think so
https://dl.google.com/android/installer_r24.4.1-windows.exe
http://download.oracle.com/otn-pub/...m=1498221676_80503fd7b283f64cfa8ae7825b0021e2
My Xiaomi Redmi phopne is detected correctly, but its rooted and OEM unlocked
edit:
It's fine now. Its unbelivable what a mess is with adb files/usb drivers and similar. There is so much that can go wrong.
I wiped everything and installed minimal adb and fastboot + lenovo usb/mtp drivers
Now pc detects my phone.
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Downloaded the latest driver zip from Google
Open Device Manager
Expand Portable Devices
Right-click on the Phone entry (notice, that's the entry, "Phone". Not Razer.)
Choose Update Drivers
Browse my way to the drivers folder and click Next.
Windows then returns immediately "The best drivers for your device are already installed", and shows that it's an MTP USB Device.
I noticed that under USB devices, there's an ADB Interface device listed, and I get the same results when I try to update that, too (excepting it says it's an "ADB Interface" device, of course). I have tried uninstalling both devices to get the drivers to install, but no such. I've rebooted both phone and computer as well.
On the phone, USB Debugging is turned on, and USB mode is set to MTP file transfer.
Please help!
Figured it out...
tkarakashian said:
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Click to expand...
Click to collapse
In case anyone else is seeing the same issues, I wanted to put my resolution up: I'd been trying to install the drivers with the Razer booted. On a whim, I rebooted it into Download Mode using "adb reboot bootloader". Once there, I had an Android Device listed in Device Manager. I ran the driver update wizard, and installed the "USB ADB Interface" option from the choices presented. I was then able to run the OEM unlock command and received the confirmation prompt on the Razer. Yay!
Now, since it's been so long, I've got to re-back-up everything so I can actually do this thing. LOL
Here's the PDF from Razer's how to install a factory image over PC guide. It explains how to do it all
s3.amazonaws(.)com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf (remove parantheses)
Hello my friends can someone help me with my problem? I have a LG G pad 10.1 v700 with broken/missing touch screen and LCD and I want it to connect to my monitor with vysor and/or [email protected] The problem is that I need to accept dialog windows when appears on my tablet when connecting to vysor, but i cant for obvious reason. I have installed ADB universal drivers, LG drivers, Android Studio and am trying with adb commands like "adb devices" to make some connection with my tablet but it says that my devices is unauthorized and don't accept adb commands at all. I read over the INTERNET that i need to boot in TWRP mode and than I can use adb commands there without authorization. I have previously installed TWRP recovery and also debugging mode is enabled, but when i am supposedly in TWRP mode (I don't hear LG boot sound sometimes after Power + Vol down button combination) my tablet doesn't recognize at all from Windows 10 and "adb devices" command show "error: no device". Can you help me?
My tablet is with android Kit Kat, rooted, Debugging mode is enabled, TWRP is installed
In Windows Device Manager I see in Android Devices - LG ADB interface, also in Portable Devices - V700
sinan.ismailov said:
Hello my friends can someone help me with my problem? I have a LG G pad 10.1 v700 with broken/missing touch screen and LCD and I want it to connect to my monitor with vysor and/or [email protected] The problem is that I need to accept dialog windows when appears on my tablet when connecting to vysor, but i cant for obvious reason. I have installed ADB universal drivers, LG drivers, Android Studio and am trying with adb commands like "adb devices" to make some connection with my tablet but it says that my devices is unauthorized and don't accept adb commands at all. I read over the INTERNET that i need to boot in TWRP mode and than I can use adb commands there without authorization. I have previously installed TWRP recovery and also debugging mode is enabled, but when i am supposedly in TWRP mode (I don't hear LG boot sound sometimes after Power + Vol down button combination) my tablet doesn't recognize at all from Windows 10 and "adb devices" command show "error: no device". Can you help me?
My tablet is with android Kit Kat, rooted, Debugging mode is enabled, TWRP is installed
In Windows Device Manager I see in Android Devices - LG ADB interface, also in Portable Devices - V700
Click to expand...
Click to collapse
Although I have personally not done so specifically for this purpose, you could try connecting a USB mouse via USB-OTG adapter and use the mouse pointer so select the check box and hit the correct button without using touchscreen... do provide feedback if you have success...