Please tell me if there are drivers for our phone under Linux (Manjaro).
If there is, please provide a link.
neonzoff said:
Please tell me if there are drivers for our phone under Linux (Manjaro).
If there is, please provide a link.
Click to expand...
Click to collapse
It doesn't work like that on Linux, you don't need a driver. You need to add a udev rule: go to /etc/udev/rules.d, create if it doesn't exist a .rule file and add something like SUBSYSTEM=="usb", ATTR{idVendor}=="[05c6]", MODE="0666", GROUP="plugdev" to it making sure that you are part of plugdev group. Best, look online, I'm sure Manjaro must have precise instructions on this in some wiki. Vendor/device id can be found if you connect your device via usb and do in terminal lsusb, it will show you all usb devices connected, yours must be Qualcomm: Bus 003 Device 017: ID 05c6:9025 Qualcomm, Inc. Qualcomm HSUSB Device.
Related
I just got a refurbished Xoom wifi from woot.com. I am trying to access it via adb from my Ubuntu PC, but it doesn't seem to recognize it. I have followed the guides for the udev rules, and it works (to a degree). It seems that my PCIIDS may be different, and this may be the problem.
I previously owned a g-tablet and a Zenithink epad, and was able to access them through adb, after changing the udev rules.
I also want to root it, and I understand that it must be able to recognize it to do that. There seems to be three modes that you can start it up in, RSD, Fastboot and Android Recovery. I'm not sure if I should be in RSD or Fastboot for adb to work, but each mode gives a slightly different PCIID.
I do have a fastboot binary for Linux, but it too needs the PC to first "see" the Xoom.
For me, in opensuse
lsusb to see the constructor and id ( be careful the id change between normal mode, recovery and fastboot)
mine is :
In normal mode
Bus 002 Device 006: ID 22b8:70a8 Motorola PCS
with debug on
Bus 002 Device 006: ID 22b8:70a9 Motorola PCS
In Bootloader
Bus 002 Device 006: ID 18d1:708c Motorola PCS
In bootRSD
Bus 002 Device 006: ID 22b8:70a4 Motorola PCS
Edit or create your /etc/udev/rules.d/92-motorola-xoom.rules
to reflect the id's of your xoom
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a8", MODE="0666" SYMLINK+="xoom"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a9", MODE="0666" SYMLINK+="xoomdebug"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="708c", MODE="0666" SYMLINK+="xoombootloader"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a4", MODE="0666" SYMLINK+="xoombRSD"
Click to expand...
Click to collapse
restart udev or reboot
sudo /etc/init.d/boot.udev restart
And normally you should see your device with
adb devices
Thanks for the reply.
I have been trying something very similar. I don't believe that I can directly copy a SuSE version to use on Ubuntu, but it gives me some ideas.
Here is what worked for my g-tablet:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
I think that was for mounting it to transfer files. I tried something like that for the Xoom IDs, but it didn't give me adb access.
I'll keep plugging away!
I finally got it to find it in adb. I'm not sure what did it, but rebooting the PC may have helped.
I am still not getting it to be seen by fastboot. I am following a How-To for rooting that first requires unlocking the bootloader. That is why I am trying to get fastboot to work.
If you know of a better way to root it, please advise me.
Thanks.
Just plug it when in fastboot and note the ID and constructor (mine change from 22b8 to 18d1 depending of the state) in that state and add it to your rules
reboot and try again
I've done that, with and without USB debugging enabled.
I think that the Linux versions of fastboot that I am trying may not be working. I am currently trying to install everything needed on my Win 7 laptop. The windows SDK includes fastboot, where the Linux version doesn't.
Ran it in windows and it is now performing the unlocking. It's disappointing that it isn't working in Linux.
I found another copy of Linux flashboot, from somewhere on the web. That one seems to work if I run it with root permissions (sudo). Otherwise I get this:
Code:
$ fastboot devices
no permissions fastboot
I'm not sure if tweaking the udev rules will fix this, but running it with sudo is no big deal. I'm just glad I got it to work.
It's an ainol Novo7 Venus, 7" tablet.
According to Windoiws ADB, the vendor id is 10D6, and the product code is 0C02.
I've successfully flashed Android version 4.2.2 onto the device (from 4.1) using Windows.
My main develoment machine runs Ubuntu 12.10, but ADB on this machine won't recognise the Anal (ainol) tablet.
lsusb identifies the device as 10d6:0c02 from Action Industries Ltd, so it's almost a dead cert that the vendor id is correct.
I've set up udev rules to try and get it recognised, but it just won't have it.
Any ideas?
Thanks.
Geoff.
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
JAMCx said:
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
Click to expand...
Click to collapse
Did u allow your pc from the phone when connecting it to adb?
JAMCx said:
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
Click to expand...
Click to collapse
Just "sudo adb devices"
Happens to me on my ubuntu build VM too
bud77 said:
Just "sudo adb devices"
Happens to me on my ubuntu build VM too
Click to expand...
Click to collapse
Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.
JAMCx said:
Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.
Click to expand...
Click to collapse
Did yo follow these steps already ?
If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:
Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules.
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
(From here)
bud77 said:
Did yo follow these steps already ?
(From here)
Click to expand...
Click to collapse
Above my pay grade ... I'll just plug it in the Mac
Thanks though.
Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.
JAMCx said:
Above my pay grade ... I'll just plug it in the Mac
Thanks though.
Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.
Click to expand...
Click to collapse
Just had the same problem and solved it by creating the file above.
Create the file
sudo vim /etc/udev/rules.d/51-android.rules
add the line below:
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"
and reload the the new rules by using this command (or reboot ):
sudo udevadm control --reload
unplug the device and plug it back in and now "sudo adb devices" should show the correct name and status.
Do sudo bash, then password, the adb and fastboot work fine for me. If using windows cmd, run as admin.
Dear Folks,
I want to access the diagnosis port on my Nexus 5x on Linux machine to run a python script to extract the UE logs. This is my first post in XDA Forum.
Do I need to have a driver if I am working on Linux environment? My phone is rooted and I can view the device shown when I ran adb devices. Does this mean that I have the correct drivers installed? I tried the command setprop sys.usb.config diag,adb and it was accepted without any errors.
Where can I find the drivers to enter into diagnostic mode on Nexus 5x on my Linux machine? After this, how can I find the correct diagnostic port on my device?
ashishkurian said:
Dear Folks,
I want to access the diagnosis port on my Nexus 5x on Linux machine to run a python script to extract the UE logs. This is my first post in XDA Forum.
Do I need to have a driver if I am working on Linux environment? My phone is rooted and I can view the device shown when I ran adb devices. Does this mean that I have the correct drivers installed? I tried the command setprop sys.usb.config diag,adb and it was accepted without any errors.
Where can I find the drivers to enter into diagnostic mode on Nexus 5x on my Linux machine? After this, how can I find the correct diagnostic port on my device?
Click to expand...
Click to collapse
You shouldn't need any drivers.
Since you're working eith USB comnectivity, you might need to make sure that you have libUSB and Udev rules properly setup for your device, but if you have adb and commands are working then you might have it all correct already.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You shouldn't need any drivers.
Since you're working eith USB comnectivity, you might need to make sure that you have libUSB and Udev rules properly setup for your device, but if you have adb and commands are working then you might have it all correct already.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you Droidriven, Can you then help me how I can identify the diagnostic port coming up on my machine?
ashishkurian said:
Thank you Droidriven, Can you then help me how I can identify the diagnostic port coming up on my machine?
Click to expand...
Click to collapse
I don't know the answer to that part, I'll try to find what you need.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?
rogerpanza said:
Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?
Click to expand...
Click to collapse
Restart your device.
SubwayChamp said:
Restart your device.
Click to expand...
Click to collapse
I've done that tons of times
rogerpanza said:
I've done that tons of times
Click to expand...
Click to collapse
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.
SubwayChamp said:
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.
Click to expand...
Click to collapse
I only have my phone plugged into my laptop, tried moving /usr/bin/adb to another folder as you said but same thing. And yeah it's most probably a ROM problem :/