Related
So I am a bit done with just flashing other roms to my kaiser and also want to develop some apps and want to experiment with making my own roms, but initially just porting roms from other devices like the HTC wildfire. But I am not able to use debugging:
So this is what I have done I have installed the android sdk and also installed the ADT plugin for eclipse. Then I have compied the android-sdk file to the root of my c drive so it is easier to use the command line interface with this file. I then run the following commands in the cmd, as admin:
adb kill-server
adb start-server
adb devices
And here is where the **** just hits the fans I am unable to see my device in the list of devices. While my device is recognized by the computer as ADB Interface > HTC Dream Composite ADB Interface in the device manager section. (But I must note that when I click on the device it is noted: "Device cannot start. (code 10)" ) Also when I double click on the device in the regular computer windows (where all your hd's are showed) the file system of the device is empty!
So does anyone have any advice?
Have you test it from a live usb or CD GNU/Linux like Ubuntu?
Nope, I hoped that it would work in Windows, but I will try it in Linux if that would solve it.l But can you see anything that i am doing wrong or is it just Windows
I always have problems with USB management on Windows, all versions...with all my computers. Linux kernel seems to be better, imho, for USB.
The easiest way of getting ADB to work:
Turn your phone OFF (Yes, off)
Connect it to your pc and wait for windows to finish "installing the drivers"
Try ADBing by going to ure fastboot folder (assuming it has the ADB executable inside the folder as well).
You could check if your device was recognized by firing
Code:
adb devices
If it doesn't show anything then do the following:
Grab the appropriate pc drivers from here: http://www.android-advice.com/2012/how-to-root-the-htc-one-x-and-htc-one-s/
Extract the drivers
Now go to Start menu and right click on my computer and then click manage.
Now go to device manager and there you should see your connected One X listed as being without a driver.
Right click on that entry and select 'update driver'
Now tell it that you have the driver on local disk and then browse to the folder you extracted.
Update your driver.
Disconnect and reconnect the device and try ADBing again.
Should work.
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
EddyOS said:
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
Click to expand...
Click to collapse
That is the thing -- IT DOES SEE IT! Try it yourself.
I didn't think it would but Jotha told me that it would. I tried it and it worked. I was surprised.
Yes device is seen through adb when off.
This is because as soon as you plug the USB cable, offmode comes up with charging and ADB support
Offmode is embeded in the recovery partition
PS: This needs latest clockworkmod recovery to work...
Latest ADB?
Hi!
When i was restoring my Sensation to S-ON i noticed that ADB was complaining about version out of date something....
Where can i get the latest version of ADB for using with my One X when i've decided if i should wait or use hTC bootunlocker...
Is there a way for Linux?
D0GuKaN said:
Is there a way for Linux?
Click to expand...
Click to collapse
Android SDK straight from Google should take care of that.
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
DoeBoi said:
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
Click to expand...
Click to collapse
No. As long as the cable is properly USB 2.0 compliant, it WILL work, otherwise HTC CANNOT certify against USB 2.0. Tried with proper Nokia, Sony Ericsson, Samsung and Google cables.
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
tashunke said:
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
Click to expand...
Click to collapse
See here a few posts back:
You have to have the latest clockworkmod recovery.
Can you help/guide me on how to install it ?
Sorry for being a dummy.
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
RaVe-N said:
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
Click to expand...
Click to collapse
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
rilorolo said:
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
Click to expand...
Click to collapse
Never mind... I found the androidlib.DLL (I think that's wrong, but its a .net DLL available here on xda) and that manages to return fast boot so I can tell programatically what state it's in...
Thanks
Thats Work
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Thibor69 said:
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Click to expand...
Click to collapse
I can understand the difficulty. This problem is pretty common because there are no official drivers for Win10. These drivers work best on XP. I also could not get the adb to work on my Win10 so I installed Ubuntu and rooting/installing ROM's from ubuntu is a breeze.. srry for not hvng a solution for this.
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
http://www.mylgphones.com/tag/usb-drivers try these drivers
That's the ones that didn't work.
Same problem here... Any luck?
Change the USB mode to PTP and you should get the RSA prompt.
anod said:
Same problem here... Any luck?
Click to expand...
Click to collapse
Yes I have install Google universal usb drivers worked for me search on Google for them
PTP worked for me, no LG driver installed.
Just got my G3 on Verizon, cannot see the device over ADB either on Mac OSX
I tried MTP, PTP, and Charge only both with and without LG drivers installed. Since it's OSX, there are no Google Universal USB drivers.
Android File Transfer opens up fine, but ADB doesn't show the device. Quite fishy indeed.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
May I ask how you managed to connect your phone to your mac via MTP? I am unable to get any kind of connection to my mac.
On windows it works finde, I can open the internal and external sd card and copy files from and to the device, I would be more than happy to achive the same on my mac.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
Hi there, you will first need to enable USB Debugging. Head over to Settings > General > About Phone > Software Information. Tap Build Number 5 times, and you'll unlock the Developer options.
Go to Settings > Developer options, and check USB Debugging. From there, ADB should work. Good luck!
OK, so I installed the new drivers, rebooted, and got ADB to recognize my LG, and was able to debug successfully. Now Android File Transfer doesn't see it, nor does Finder show the device. What am I missing?
It's broken, I saw a tweet from jcase regarding the issue. I have the same problem. I just adb push/pull when necessary for now.
Sent from my LGLS990 using XDA Free mobile app
EDIT - It wasn't jcase, it was @utoprime
Mine works fine on my Mac
faded03cobra said:
Mine works fine on my Mac
Click to expand...
Click to collapse
You have adb and MTP works? What OSX version?
Sent from my LGLS990 using XDA Free mobile app
Solution
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
KAR0SH1 said:
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
Click to expand...
Click to collapse
Seriously old, and seriously unresolved (for me and a few people on reddit, at least). Still have not succeeded at getting ADB to detect G3 on USB, tried running the -usb flag on the cli and everything. Is there a working process yet? Verizon seems to be the outlier here as well...
Just worked for me on OSX Yosemite with a D855 on V10l:
- Update ADB (android platform tools)
- Install LG Driver (link is in this thread)
- Reboot
- run "rm ~/.android/adbkey" and "rm ~/.android/adbkey.pub"
- run "adb devices" (you should now see your G3)
- run "adb kill-server" (just to make sure there is no interference)
- quit all applications on your phone and go to home screen
- run "purpledrake_osx.command" which should now work
Inbetween (guess it was directly after running "purpledrake_osx.command") you should get a permission request on your phone which you should allow
Thanks
_ranch said:
Change the USB mode to PTP and you should get the RSA prompt.
Click to expand...
Click to collapse
Thanks, this works for me on El Captain
Also on El Capitan:
After enabling developer settings + USB debugging on phone (see earlier in thread),
Removing the adbkey + pub from the users .android folder (see earlier in thread),
and connecting with PTP,
It finally works
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
danhawker said:
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
Click to expand...
Click to collapse
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
melendi said:
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
Click to expand...
Click to collapse
Do you have a nvidia gamepad?
gengt said:
Do you have a nvidia gamepad?
Click to expand...
Click to collapse
Yes and I had already been in fastboot but on another android device with osm0sis ADB & Fastboot script there are no fastboot devices listed.
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Click to expand...
Click to collapse
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
So im kind of at a loss here of what to do.... any ideas?
UPDATE:
Thanks to these three posts I was able to get it working:
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
simplepinoi177 said:
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Try on Windows
ikram.senguen said:
Try on Windows
Click to expand...
Click to collapse
If I could avoid installing an entire operating system (VM or straight on hardware) that would be preferable.
limepot said:
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Click to expand...
Click to collapse
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
simplepinoi177 said:
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
Click to expand...
Click to collapse
thanks! ill give it a try.
limepot said:
thanks! ill give it a try.
Click to expand...
Click to collapse
doesnt seem to make a difference here unfortunately.
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
TheGhost1951 said:
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
....
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Too bad OP stated he's she's not on windows, but on Linux...
simplepinoi177 said:
Too bad OP stated he's not on windows, but on Linux...
Click to expand...
Click to collapse
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
limepot said:
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
Click to expand...
Click to collapse
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Masterchief87 said:
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Click to expand...
Click to collapse
i tried on various different ports, i tried on 2.1 and 3 so far no luck.
ive been spending way too much time trying to install windows and ended up being able to on an old laptop so im going to try the windows suggestions (this laptop has only 2.0 ports), that ive seen so far.
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
TheGreatBumBum said:
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
Click to expand...
Click to collapse
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
limepot said:
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
Click to expand...
Click to collapse
Oh yeah sorry bout that, just want to tell you windows is a bit buggy. I had to install the fastboot drivers every 5-10 minutes.Dunno why,Dunno how.
Back to basics, use only the motherboard/rear ports. Some phones are picky about the cable, you might need to use a factory cable. Does the computer see the phone at all? If not you don't have the right drivers.
Also 'adb reboot fastboot' "working" doesn't mean it worked.
In simple terms, the command will work but it must return a device ID below it and should trigger the phone to trust the PC.
Command order on Windows is:
adb devices
adb reboot fastboot
"whatever the Oneplus Unluck command is" some phones have different ones for different models.
TheGhost1951 said:
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Okay after taking a lot of time this was indeed the solution, thankyou!
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
der_akinator said:
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
Click to expand...
Click to collapse
This is incredibly helpful thankyou.