i already set up adb and the sdk
now i need help setting up udev.
can anyone please explain it to me in a way a noob can understand?
teh5abiking said:
i already set up adb and the sdk
now i need help setting up udev.
can anyone please explain it to me in a way a noob can understand?
Click to expand...
Click to collapse
Here you go.
Yeah, I tried that tutorial.
Didn't work for me.
Sent from my T-Mobile G2 using XDA App
I installed 11.04 recently and ADB seemed to work right out of the box.
Have you tried:
Code:
adb devices
I grepped the rules.d directory for 0bb4 and came up with this, in 40-usb-media-players.rules
Code:
ATTRS{idVendor}=="0bb4" , ATTRS{idProduct}=="0c94" , ENV{ID_MEDIA_PLAYER}="htc_vision"
"lsusb" returns (among other devices)
Code:
Bus 002 Device 007: ID 0bb4:0c91 High Tech Computer Corp.
Note that the product ID is different.
For 10.10, I think I had to update the udev files, but support for the vision might already be baked into 11.04. If "adb devices" returns a serial number, you're all set. If it doesn't let us know what pops up.
I found this:
http://eddieringle.com/udev-rules-for-adb-in-ubuntu-11-04-natty-narwhal/
I'm not sure what to say? I don't have the 99-android rules and adb works fine. Maybe you didn't have enough permissions to change the udev files when you installed ADB/SDK?
maybe reboot or restart udev or unplug/plug your device?
Code:
sudo service udev restart
I don't see how it didn't work. That tutorial worked for me just fine.
Sent from a Western Union telegram.
You need to reboot your computer for it to work.
Sent from my HTC Vision using XDA Premium App
Well, I did get adb to work just fine on my Acer Aspire One.
I had to mix the tutorial on the Cyanogenmod wiki with a tutorial that was for the G1/Magic/Droid/N1/i7500.
It's working great.
The one on the android dev page didn't work for me because of some deep internal stuff that was going on with my laptop. as explained by my good friend Chris who's actually a registered Android developer. I forgot exactly what it was, but it had to do with the security features of Ubuntu that collide with something that's in my laptop.
For others looking for info with adb on natty, the SYSFS is deprecated (if you are following the tutorial on the android site). You should be using ATTRS instead. Also, the rule can be 51 or 99.
Here is mine (i have an nvidia pad and an htc phone):
Code:
[email protected]:/etc/udev/rules.d$ cat 51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
And don't forget to restart udev. Unplug the device, do the command below and then plug back in. HTH.
Code:
sudo /etc/init.d/udev restart
Related
Yes, I have searched hi n' low... the forums, Google and tried everything i came across (some fixes very outlandish)
Debug on, debug off, reboot, create a adb.ini etc, etc. 3 days worth.
Now, funny thing, when I open CMD I can type "adb devices" and it (adb) seems to recognize my device, but when I adb shell list of devices is blank:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Ja>adb devices
List of devices attached
d509097c device
C:\Documents and Settings\Ja>adb shell
[email protected]:/ $ adb devices
adb devices
List of devices attached
[email protected]:/ $
Never had a problem with my previous device (an LG Optimus).
Anybody have an idea whats up here?
Thanks,
Ja
jhill110 said:
Yes, I have searched hi n' low... the forums, Google and tried everything i came across (some fixes very outlandish)
Debug on, debug off, reboot, create a adb.ini etc, etc. 3 days worth.
Now, funny thing, when I open CMD I can type "adb devices" and it (adb) seems to recognize my device, but when I adb shell list of devices is blank:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Ja>adb devices
List of devices attached
d509097c device
C:\Documents and Settings\Ja>adb shell
[email protected]:/ $ adb devices
adb devices
List of devices attached
[email protected]:/ $
Never had a problem with my previous device (an LG Optimus).
Anybody have an idea whats up here?
Thanks,
Ja
Click to expand...
Click to collapse
That's because you're expecting behavior that wouldn't make sense - adb shell opens a remote connection to your phone (try typing ls, which is the Linux equivalent of the dir command, to see the files in your current directory - you'll notice that the files listed are not files on your computer. And the fact that ls works should tell you that you're not in Winblows anymore...). The "[email protected]" part gives it away - you're looking at your phone's command line interface at that point instead of the computer's command prompt.
If you run adb devices from an app like android terminal emulator, you'll get the same output - and it will be correct, because your phone is not externally connected to itself
Sent from my SPH-L710 using xda app-developers app
Ok, thanks
Sent From The Galaxy Via Subspace
jhill110 said:
Ok, thanks
Sent From The Galaxy Via Subspace
Click to expand...
Click to collapse
I'm happy to help
Feel free to ask if anything else isn't making sense - I don't have all the answers, but I'm usually pretty good at finding them, lol
Sent from my SPH-L710 using xda app-developers app
Will do. Much appreciated Styles
Sent From The Galaxy Via Subspace
okey im needing little help now, i just installed 64bit ubuntu to start practicing how to compile roms etc.....but now when i have zip on my computer finally, my nexus dont want to show itself anywhere on my pc. i followed these guidelines without succes "# sudo gedit /etc/udev/rules.d/99-android.rules" and added "SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your-login" # MTP mode with USB debug on" but obviously changed login and ATTR. also with ADB devices command my nexus is there, but should there read nexus instead of random numbers and letters?
E: got it working by following this -> http://bernaerts.dyndns.org/linux/74-ubuntu/268-ubuntu-automount-any-mtp-device
Hi all,
My Swift arrived today. Trying to put Cyanogen MOD on it. Unfortunately my computer can't seem to see the Swift through ADB. Mounting the MTP works fine.
I have a 51-android.rules file in /etc/udev/rules.d which contains
#Wileyfox
SUBSYSTEM=="usb", ATTR{idVendor}=="2970", MODE="0664", GROUP="plugdev"
my user is in the plugdev group and even if running as root I can't see the phone.
lsusb shows Bus 001 Device 010: ID 2970:2282 so I'm not entirely sure what's happening and what's not working.
I've tried switching debugging off and on again in various orders, also rebooted my computer and phone multiple times.
Anyone got any ideas for me please?
Thanks
Not_Technically_Minded! said:
Hi all,
My Swift arrived today. Trying to put Cyanogen MOD on it. Unfortunately my computer can't seem to see the Swift through ADB. Mounting the MTP works fine.
I have a 51-android.rules file in /etc/udev/rules.d which contains
#Wileyfox
SUBSYSTEM=="usb", ATTR{idVendor}=="2970", MODE="0664", GROUP="plugdev"
my user is in the plugdev group and even if running as root I can't see the phone.
lsusb shows Bus 001 Device 010: ID 2970:2282 so I'm not entirely sure what's happening and what's not working.
I've tried switching debugging off and on again in various orders, also rebooted my computer and phone multiple times.
Anyone got any ideas for me please?
Thanks
Click to expand...
Click to collapse
Hey there. Open device manager and check. Maybe the driver isnt installed
Naw, using Linux but thanks anyway.
I found the answer. In ~/.android I had to create a file adb_usb.ini and add the text 0x2970 to it. I added a comment to it before just for my future self.
Thanks anyway, thread solved.
I'm trying to get my system back to where it was before I lost everything. My files, notes, tools, etc. were gone but I've managed to get about 80% of it up again. In order to get my computer to talk to my VK815, I'm pretty sure I need a good udev rule. I think there's also a modeswitch script that needs to run when it's plugged in but that info was lost in the disaster. I have the linux development setup back to where I can compile AOSP and I get the tools like adb and fastboot as compilation products, but can't get the VK815 and computer to talk to each other. Any and all help is most welcome.
Thanks,
Jim
I guess there's some good news here. I was able to reconstruct two udev rules; one to modeswitch (which may or may not be necessary) and the other to symlink to ttyUSB0. With the phone in the normal (not download) mode, dmesg shows it initially as idProduct 6292 (where it attempts to feed the Micro$oft drivers) and then it changes to 6293 and symlinks ttyUSB0. After this completes, 'adb devices' shows a blank list. I'm in the developer mode on the tablet with USB Debugging enabled and the Build Version is LRX22G.
Ideas anyone?
edit: Be sure to turn on USB tethering in Wireless Networks -> More
Turns out that the usb_modeswitch rule wasn't needed. Here's the rule I put into /lib/udev/rules.d/51-vk815.rules
# LG G-Pad 8.3
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
After adding this rule, restart udev the way your version of linux wants you to.
Plug in the USB cable and wait for the VK815 to finish loading the Windoze drivers and change idProduct to 6293.
Now, adb devices "should" show you the device ID. It did on mine.
This can easily be made harder than it should be.
Still can't get the VK815 to become a ttyUSB device when it's in the download mode. Tried adding SYMLINK+="ttyUSB%n" to the udev rule without success. Gotta have this to squirt and image.
When this is done and working, I plan on making a step-by-step for future reference.
Jim
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Triscuit said:
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Click to expand...
Click to collapse
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Tulsadiver said:
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Click to expand...
Click to collapse
The first two commands are to install adb and fastboot, which I've done. The third command is to add a new product id in adb_usb.ini which I got "permission denied" so I entered it manually for ****s and giggles but it didn't help. Thank you though!
I was finally able to get the device to authorize, I did a few things but I'm not sure which one corrected the problem, first. I deleted the adbkey file from /home/.android folder, I also changed permissions of the folder to rw-rw-rw and finally I hit "Revoke USB debugging authorizations" under development settings WHILE the phone was plugged into the computer. Every other time I had done it after unplugging the device. Not sure which one worked but it did, now I can get back to flashing again!
Sent from my Pixel 2 XL using XDA Labs
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
jbarcus81 said:
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
Click to expand...
Click to collapse
Yep I honestly think my problem was that I was unplugging my device before revoking authorizations..... Silly me haha
Sent from my Pixel 2 XL using XDA Labs