Hi, i flashed OwnROM yesterday and suddenly adb stopped detecting my device. I have the LG drivers installed and adb debug enabled, but
Code:
adb devices
still returns horrible blank space. Any ideas ?
EDIT: I deleted all drivers and installed koush's adb universal driver and solved my problem. I have no idea why official LG drivers weren't sufficient enough.
sackhorn said:
Hi, i flashed OwnROM yesterday and suddenly adb stopped detecting my device. I have the LG drivers installed and adb debug enabled, but
Code:
adb devices
still returns horrible blank space. Any ideas ?
EDIT: I deleted all drivers and installed koush's adb universal driver and solved my problem. I have no idea why official LG drivers weren't sufficient enough.
Click to expand...
Click to collapse
Simple. OwnRom is an AOSP based rom. The LG driver is made to work with LG stock rom.
Related
Recently switched to linux, installed android sdk, i can mount phone as an ext hard drive when it's on normally.
it's unlocked, i booted into fastboot, tried to use moto-fastboot and the device isn't found.
are there any additional usb drivers i need? i'm lost.
when the device is on normally and connected i get this:
$ adb devices
List of devices attached
???????????? no permissions
dont know if that would help but maybe usb deugging isn´t activated,
i havent unlocked my atrix but maybe there´s the problem.
just a thinking
thanks for the response. i checked at usb debugging is selected. it worked just fine on windows a few days ago but I don't have that installation anymore.
any motorola drivers i need installed? really stuck on this one.
Hi,
I need help to get ADB working on my PC with the Galaxy S2.
I have installed the drivers coming along Kies, I think under sub folder "25_escape".
The drivers appear correctly as "Samsung ADB interface" under the device manager.
When I run "adb devices" I get the following logs
>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
I'm wondering if it is a driver issue, or something else.
I have several other android phones that are working just fine (HTC, Motorola, Samsung Galaxy S1 even works) but that issue is happening on the Galaxy S2 (and Tab 10.1 as well).
Help is really appreciated!
Thanks!!
Hi.
Busy rooting my new S2.
Problems with SuperOneClick because of ADB drivers.
- download + install Kies from the Samsung site
- run Kies and select Tools / Install driver
This worked for me !
Good luck.
Are you using USB or ADB wireless?
Ian
I have installed the drivers, but it did not help. It seems that either ADB is crashing when I run any command, or its connection to the device fails in some ways.
I am using a regular USB connection.
Any idea?
thanks!
Ok.
Do you use ADB from the Android SDK platform-tools directory ?
Which ADB version are you using. i got 1.0.26
>adb version
Android Debug Bridge version 1.0.26
Older version ? upgrade the SDK.
Otherwise, give Wifi ADB a try.
Install it and connect with : adb connect <host>:<port>
good luck, Bromco
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
pda net
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
One thing that worked for me was to install pda nets drivers (google pdanet and it should be the first thing that comes up) it will ask you if you want to replace current android usb drivers and you tell it yes. Hope this helps!
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
Remove HTC sync, this should solve your problem. Also try a different port and reboot your computer.
If neither of these works then resinstall ADB you might have a dated version allthough that would NOT prevent it from functioning entirely
http://dl.google.com/android/installer_r21-windows.exe then choose download platform tools once the sdk opens.
I am on win7 x64 and have had 0 problems.
Good luck!
make sure the usb port you're using is 2.0 and not 3.0
it may be something as simple as that as well.
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
Thank you guys.
It was both using PdaNet to reset the drivers and also switching to USB2.0 ports that did the trick. Thank you for the help.
adb now sees my device Yay!
jayba420 said:
Thank you guys.
It was both using PdaNet to reset the drivers and also switching to USB2.0 ports that did the trick. Thank you for the help.
adb now sees my device Yay!
Click to expand...
Click to collapse
I am having the same issue. Which manufacturer did you select when you installed pdanet. I am stuck on the skip usb driver installation dialog. Have enabled usb debugging n all but it still can't detect my device.
I have a Win 8.1 machine with the HTC drives installed and when I run ADB with the phone booted to the ROM everything is fine. ADB returns the device ID and it is recognized. When I boot into the fastboot, I get fastboot usb but ADB does not recognize the device, I get List of devices attached and then nothing. I have rebooted both the phone and computer, uninstalled and reinstalled the drivers but no luck. Anyone ever seen this behavior?
Please close thread.
Hello fellow xda-members,
my ADB isn't working anymore. I own an LG G4 H815 Intl and a windows 10 computer. When I bought the G4 and rooted it ADB worked without a hassle.
Now, 6 months later, ADB is gone. I tried
Code:
adb kill-server
Code:
adb start-server
and replugged the cable
Installed latest LG Drivers
Reboot phone and PC
copied adb_key.pub to the phone (/data/misc/adb)
erased .android. folder on PC (/C://User/me/.android.)
None of that worked for me and I feel like the internet offers no more solutions for my problem. Been on, like, 20 pages.
So if anybody of you faces the same problems - please help :crying: