I saw on internet that I can do screen recording from phone, but i need to run a command via adb, and adb doesn't recognize my LG G2(D802)..i had installed the correct usb driver from lg site
When i open ADB and type: adb devices, it says "List of devices attached" and no name of device appears
PS: developer mode is enabled
EDIT: i managed with that..but now says that the device is offline what means that?
Related
I am trying to access my phone through ADB to register w/o data. My device center and device manager both see the phone ("Android Phone" in DC, and "ADB Interface > HTC Dream" in DM). However, when I run ADB from the command line it cannot find my device. I have tried reinstalling drivers, killing and starting the ADB server, and even re-flashing my phone.
Note: When booting the phone from a fresh flash I DON'T have to enter "<enter>setprop persist.service.adb.enable 1<enter>" to initialize ADB. It is automatically seen as an ADB device, and after entering the command it is only seen as a storage device.
Thanks in advance.
(unlocking a Dream on Windows 7 x64)
Solved it by installing the drivers from here: http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
Hi all,
I recently bought a OPT and wanted to root it, but I can't get the RSA Fingerprint dialog to appear.
What I've done:
Installed Android SDK and platform tools and all that stuff according to the guide in the general section
Installed Koush's universal drivers and also specifically installed the Oneplus drivers
Rebooted rebooted rebooted both my computer and phone multiple times
Revoked USB authorization multiple times (according to some this works, but not for me)
Tried both MTP and PTP
Switched off and on developer options and USB Debugging
Factory reset my phone
When I start a command prompt in the platform tools directory and execute "adb version", " Andoid Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android" pops up, so I think my ADB is working properly. But when I execute "ADB devices" the ADB server starts up and then nothing is listed under connected devices.
I'm using Windows 10. Any help would be greatly appreciated. Thanks!
This might work
This didn't work for me, but give it a try.
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332
I can't connect to ADB, at all... All i get is this message
List of devices attached
LGH918 ect. unauthorized
When i connect USB debugging, i never get the finger print prompt.... I have all the proper drivers installed, I installed ADB and Hotboot. I already cleared the contents in the .android folder.
Can someone please help. I don't know what else to do.
type
Code:
adb kill-server
adb start-server
then it should ask the RSA fingerprint again.
me2151 said:
type
Code:
adb kill-server
adb start-server
then it should ask the RSA fingerprint again.
Click to expand...
Click to collapse
Nothing unfortunately :/ the prompt never shows, no matter what i try.
Bump
Bump. Im in the same boat
Try
1) unplug v20
2) go into developer options then click Revoke USB debugging authorizations
3) plug v20 in, unlock v20 screen
4) type adb devices
5) authorize the popup you see on the phone
You should be good.
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Did you get permissions on your phone when popup appears?
No. The phone doesn't pop up the permission question. But I don't know why.
Don't know but as long as you don't give permission you can't sideload
Euclid's Brother said:
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Click to expand...
Click to collapse
Try the usb driver and SDK platform tools directly from Essential website:
https://www.essential.com/developer/current-builds
I am using the drivers from Essential website. However, I was using the lastest Unified Android Toolkit for the adb command. Looks like it may be outdated, as the adb.exe and it's dll's in the link from Essential website is newer. I will try the platform tools from there and see if there is a difference.
Thanks!
Is USB debugging enabled in Developer settings?
Are you in Fastboot? Did you try "fastboot devices"?
ADB devices returns your device is offline?
I went throug over 20 forums sites videos none of them helped me I forcfully manually installed abd drivers reconizes when the phone is on adb devices but when I do adb reboot bootloader and do adb devices nothing pops up in device manager I changed the driver around few times till shows norhing killed adb server truned it back on nothing rebooted my pc use diffrent usb port have nothing plugged into any other port Have owm unlocking bootloader is unlocked usb debugging is on I did put media transfer for files them ptp for pictures still no change I installed lg air drive thing still get same resutls. When I do fastboot devies it shows up there in bootloader or not.
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
I have to push those commands but I dont know how with fastboot command since there is no adb devices I tried also on 5 different os using android tool kit latest's android usb drivers some adb installer thing where you select Y for all options I tried on parrot os kali linux windows 10 pc and two windows 7 pc I have windows 7
I tried almost everything an the driver shows up in device manager please help
BTW It wasnt like that before it was before under android device tab as a good adb device lge adb device I tried them all
LG V20 android 7.0 T-Mobile I have 7.0 Build Number NRD90M Soft Version H91810q
st0rm1 said:
I went throug over 20 forums sites videos none of them helped me I forcfully manually installed abd drivers reconizes when the phone is on adb devices but when I do adb reboot bootloader and do adb devices nothing pops up in device manager I changed the driver around few times till shows norhing killed adb server truned it back on nothing rebooted my pc use diffrent usb port have nothing plugged into any other port Have owm unlocking bootloader is unlocked usb debugging is on I did put media transfer for files them ptp for pictures still no change I installed lg air drive thing still get same resutls. When I do fastboot devies it shows up there in bootloader or not.
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
I have to push those commands but I dont know how with fastboot command since there is no adb devices I tried also on 5 different os using android tool kit latest's android usb drivers some adb installer thing where you select Y for all options I tried on parrot os kali linux windows 10 pc and two windows 7 pc I have windows 7
I tried almost everything an the driver shows up in device manager please help
BTW It wasnt like that before it was before under android device tab as a good adb device lge adb device I tried them all
LG V20 android 7.0 T-Mobile I have 7.0 Build Number NRD90M Soft Version H91810q
Click to expand...
Click to collapse
adb and fastboot are totally different processes. Replace the 'adb' command with 'fastboot' and it should work.