Database Info

[Q] Ubuntu 11.04 in VirtualBox on Win7 host - can't access Infuse using adb

I am trying to set up an Ubuntu environment using VirtualBox on my Win7 host but I'm unable to pass my USB-connected Infuse through from the host to Ubuntu. Running adb devices from Ubuntu just outputs "List of devices attached" with no devices listed (my Infuse DOES show when running this out of my Win7 host).
I followed these directions here to set up my udev rules,
http://forum.xda-developers.com/showthread.php?t=570452g
using the below settings in my /etc/udev/rules.d/51-android.rules file but I'm not able to ever see my Infuse when executing the adb command:
1st failed try:
SUBSYSTEM=="usb", ATTR{idVendor}=="04E8", MODE="0666", GROUP="plugdev"
2nd failed try:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04E8", ATTRS{idProduct}=="681D", MODE="0666", OWNER="<your user name>" #Mass Storage Samsung Infuse 4G
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04E8", ATTRS{idProduct}=="681C", MODE="0666", OWNER="<your user name>" #Debug Samsung Infuse 4G
3rd failed try:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="80ee", ATTRS{idProduct}=="0021", MODE="0666", OWNER="<your user name>" #Debug Samsung Infuse 4G
I got these various Vendor and Product IDs by hovering over the "SAMSUNG_Android [0400]" USB Device Filter (after clicking the green '+' button in the USB section of the Settings menu in VirtualBox:
When connected in Debug mode:
Vendor ID: 04E8
Product ID: 681C
Revision: 0400
Serial No.: I997********
State: Busy
When connected in Mass Storage mode:
Vendor ID: 04E8
Product ID: 681D
Revision: 0400
Serial No.: I997********
State: Busy
VirtualBox hover over Unknown device 04E8:6877 [0400] when in Kies mode:
Vendor ID: 04E8
Product ID: 6877
Revision: 0400
State: Busy
I got the settings for the 3rd try after running lsusb and getting this output:
lsusb command when connected in Debug mode:
Bus 002 Device 002: ID 80ee:0021
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Any idea what I'm doing wrong?
Thanks

[Q][SOLVED] SGH-T959V - Issue in Linux

Okay... I did a little searching through the google and through these forums, but I didn't really find anything that applies..
Sys Info:
Ubuntu 12.04
I used the Heimdall One-Click method, which worked like magic. I've been running roms for the T959V ONLY, and only stick to those forums for ROMs.
About Phone: (As listed by the Android OS)
Model No. SGH-T959V
Baseband Version: T959VUVKJ6
Kernel Version [email protected] #1
What my computer sees:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 002 Device 003: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard Hub
Bus 002 Device 004: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard
Bus 002 Device 005: ID 18d1:4e22 Google Inc. Nexus S (debug)
This is causing the Heimdall One-Click to see my t959v as "Disconnected"...
Any ideas? By the way, I've tried a few different distros of linux. Before running the Heimdall, I have installed Android SDK and Eclipse w/ADT Plugin....

FetalVivisection said:
Okay... I did a little searching through the google and through these forums, but I didn't really find anything that applies..
Sys Info:
Ubuntu 12.04
I used the Heimdall One-Click method, which worked like magic. I've been running roms for the T959V ONLY, and only stick to those forums for ROMs.
About Phone: (As listed by the Android OS)
Model No. SGH-T959V
Baseband Version: T959VUVKJ6
Kernel Version [email protected] #1
What my computer sees:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 002 Device 003: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard Hub
Bus 002 Device 004: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard
Bus 002 Device 005: ID 18d1:4e22 Google Inc. Nexus S (debug)
This is causing the Heimdall One-Click to see my t959v as "Disconnected"...
Any ideas? By the way, I've tried a few different distros of linux. Before running the Heimdall, I have installed Android SDK and Eclipse w/ADT Plugin....
Click to expand...
Click to collapse
A lot of devices actually share the same device id (in this case the 4e22). I say just follow the directions and just use the vendor id to manage permissions (in this case 18d1 for samsung).
http://developer.android.com/tools/device.html
Download mode, charging mode, recovery, etc... can all have different usb Device IDs

bhundven said:
A lot of devices actually share the same device id (in this case the 4e22). I say just follow the directions and just use the vendor id to manage permissions (in this case 18d1 for samsung).
http://developer.android.com/tools/device.html
Download mode, charging mode, recovery, etc... can all have different usb Device IDs
Click to expand...
Click to collapse
Okay, since last we spoke, this is what I've done so far
I flashed back over to CM9...issue persists. {When I figure this out, I will post if for the XDA World to see..}
This is the only thing listed in etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<plugdev>"
(I'm somewhat familiar with that page, and I did try what you suggested, by using 18d1, but this is my 4th go around.) SOMETHING CHANGED.
The only ONE thing I can think of: I recently got a new computer that is AMD 64 and I'm running i386 OS. Potentially asinine, I know..
===============================================
$ lsusb -v
idVendor 0x18d1 Google Inc.
idProduct 0x4e22 Nexus S (debug)
bcdDevice 2.27
iManufacturer 1 Samsung
iProduct 2 Galaxy S 4G
iSerial 3 0123456789ABCDEF
===============================================
Heimdall STILL doesn't see it as connected when in Download Mode....

FetalVivisection said:
Okay, since last we spoke, this is what I've done so far
I flashed back over to CM9...issue persists. {When I figure this out, I will post if for the XDA World to see..}
This is the only thing listed in etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<plugdev>"
(I'm somewhat familiar with that page, and I did try what you suggested, by using 18d1, but this is my 4th go around.) SOMETHING CHANGED.
The only ONE thing I can think of: I recently got a new computer that is AMD 64 and I'm running i386 OS. Potentially asinine, I know..
===============================================
$ lsusb -v
idVendor 0x18d1 Google Inc.
idProduct 0x4e22 Nexus S (debug)
bcdDevice 2.27
iManufacturer 1 Samsung
iProduct 2 Galaxy S 4G
iSerial 3 0123456789ABCDEF
===============================================
Heimdall STILL doesn't see it as connected when in Download Mode....
Click to expand...
Click to collapse
That wouldn't work, because 04e8 is not samsung's vendor id. 18d1 is samsung's vendor id. Also, there is no group called "<plugdev>", but there is a group called "plugdev".
I'm saying: Change your udev entry to:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="plugdev", GROUP="plugdev"
Remove the usb device and run this:
Code:
sudo udevadm control --reload-rules
Then plug in your device again. This will have you covered for any samsung device.
If it still doesn't work, make sure you are in the plugdev group:
Code:
groups YOURUSERNAME
If you don't see plugdev in there, add yourself to plugdev.
Code:
sudo adduser YOURUSERNAME plugdev
Logout and login again.
You should be golden.

bhundven said:
That wouldn't work, because 04e8 is not samsung's vendor id. 18d1 is samsung's vendor id. Also, there is no group called "<plugdev>", but there is a group called "plugdev".
I'm saying: Change your udev entry to:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="plugdev", GROUP="plugdev"
Remove the usb device and run this:
Code:
sudo udevadm control --reload-rules
Then plug in your device again. This will have you covered for any samsung device.
If it still doesn't work, make sure you are in the plugdev group:
Code:
groups YOURUSERNAME
If you don't see plugdev in there, add yourself to plugdev.
Code:
sudo adduser YOURUSERNAME plugdev
Logout and login again.
You should be golden.
Click to expand...
Click to collapse
Thank you. I did exactly as per your instructions, step-by-step. No errors. Everything did as I'd expect. No change, however.
The problem is: If my computer is seeing my phone as a Nexus, I fear that the One-Click for the Galaxy S 4G will not work.
I've tried multiple ports, but always the same. (( With the phone in download mode, it's not listed in lsusb AT ALL; but if it is booted into Recovery or Android OS, it's at least detected as a Nexus.....))
What better ROM to be stuck with than a Cyanogenmod ROM?!

bhundven said:
That wouldn't work, because 04e8 is not samsung's vendor id. 18d1 is samsung's vendor id.
Click to expand...
Click to collapse
Well, I took another stab at this today. Actually 18d1 is the Google vendor ID according to that link (http://developer.android.com/tools/device.html) and the Samsung is 04e8.
This has to be, because I've done it several times with this phone and have added that sequence to udev on quite a few occassions.
Before all of this began lsusb would, in fact show the correct "ID 04e8 - Samsung Electronics, Inc."
I think I'll keep stabbing away at udev until something breaks or I find the solution.
Thank you.

FetalVivisection said:
Well, I took another stab at this today. Actually 18d1 is the Google vendor ID according to that link (http://developer.android.com/tools/device.html) and the Samsung is 04e8.
This has to be, because I've done it several times with this phone and have added that sequence to udev on quite a few occassions.
Before all of this began lsusb would, in fact show the correct "ID 04e8 - Samsung Electronics, Inc."
I think I'll keep stabbing away at udev until something breaks or I find the solution.
Thank you.
Click to expand...
Click to collapse
I stand corrected on the vendor ids. My bad!
FetalVivisection said:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 002 Device 003: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard Hub
Bus 002 Device 004: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard
Bus 002 Device 005: ID 18d1:4e22 Google Inc. Nexus S (debug)
Click to expand...
Click to collapse
When I'm in download mode, I see:
Code:
[email protected]:~$ lsusb -s 001:005
Bus 001 Device 005: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
I'm wondering if you either have Froyo bootloaders, or you flashed the UVKF1 bootloaders from AdamOutler's OneClick?
This is what is in my /etc/udev/rules.d/51-android.rules file:
Code:
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="bryan"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="bryan"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="bryan"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="bryan"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="bryan"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="bryan"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="bryan"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="bryan"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="bryan"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="bryan"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="bryan"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="bryan"
# adb protocol on grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="bryan"
# fastboot protocol on grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="bryan"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0600", OWNER="bryan"
I set the OWNER to my username, bryan.
As I'm the only one using this laptop.
Try just using what I have, granted using your username instead of mine, then do the reload rules with udevadm again.

bhundven said:
I'm wondering if you either have Froyo bootloaders, or you flashed the UVKF1 bootloaders from AdamOutler's OneClick?
Click to expand...
Click to collapse
Here are the only two files I ever really flash http://forum.xda-developers.com/showthread.php?t=1358498.
The only one I most recently flashed bootloaders for was the " AntonX-Basic_with_a_twist-v1.1.0-OC_UV.jar ".
I flash the stock rom first, boot into Android, reboot into DL Mode, then flash the AntonX kernel, let it boot into Android, then reboot back into download mode and flash Bootloaders.
.... which has worked plenty of times before. (I only wonder if I'm over-doing it..)
How would I go about finding what bootloader(s) are currently active or in use?
Wouldn't that be ./adb reboot bootloader?
(By the way, I did what you said, completely replacing mine with yours, appending octopus as the owner, save&exit, then sudo udevadm control --reload-rules ...no change.)

EDIT: I FIGURED IT OUT!!!!!!!!
I thought about it...what is it that interfaces with the computer? Mass Storage.
I went into Clockworkmod and formatted the sdcard. VICTORY!
"Bus 002 Device 021: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica/S"
HOWEVER.......... now the plot thickens.
I'm unable to get out of recovery. IN recovery, I can adb devices and my phone is listed. Rebooting to download mode... Devices is BLANK.
SO... now it won't boot into any OS. ALSO, booting into the one-click, my device consistently shows as disconnected.
I've tried different ports. When I put a ROM onto my sdcard and try to flash, I get the following error: E:Can't open /cache/recovery/last_log
-------------------------
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 002 Device 003: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard Hub
Bus 002 Device 004: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard
[email protected]:~/Android/sdk/platform-tools$ ./adb devices
List of devices attached
(From adb I put it into download mode, then lsusb again.... nothing. ./adb devices....blank.

FetalVivisection said:
EDIT: I FIGURED IT OUT!!!!!!!!
Click to expand...
Click to collapse
We can mark this one closed. I thought I checked the "Question" box...but I don't see a way to mark it resolved. (Bad cable and Bad SDCARD)

Yay!
Edit title of thread..
Cool, glad you figured it out.
Sent from my SGH-T959V

FetalVivisection said:
We can mark this one closed. I thought I checked the "Question" box...but I don't see a way to mark it resolved. (Bad cable and Bad SDCARD)
Click to expand...
Click to collapse
Edit your original post - go to advanced edit and add SOLVED to the thread title.

[Q] Fastboot, how to check if it works?

Hi all, my Infinity is running on CWM and the CROMI. Just to make sure I have a safety net, I am trying to get access with fastboot to the device. Originally I have installed the CWM by dd'ing the image on the device itself. All the PC systems I have access to are running Linux, so Windows is no option for me.
I have the fastboot binary for Linux and my other Android device -a HTC HD2- can be accessed via fastboot. This makes me believe the PC side of the story is ok. Now, when I start my Infinity with the Volume minus key pressed, then hit Volume minus two more times and then Volume plus, there is a message saying "Starting Fastboot USB download protocol". The device is not recognized from my PC though. I checked with
Code:
fastboot devices
.. and simply nothing happens. The command returns without any message or error. When I plug into USB, this are the log messages:
Code:
kernel: [11222.200068] usb 1-1.3: new high-speed USB device number 14 using ehci_hcd
kernel: [11222.286798] usb 1-1.3: New USB device found, idVendor=0b05, idProduct=4daf
kernel: [11222.286808] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [11222.286814] usb 1-1.3: Product: Fastboot
kernel: [11222.286818] usb 1-1.3: Manufacturer: ASUSTeK COMPUTER INC.
[11222.286823] usb 1-1.3: SerialNumber: xxxxxxxxxxxxx
mtp-probe: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
mtp-probe: bus: 1, device: 14 was not an MTP device
Here comes my question. What do I have to expect on the screen of the Infinity when fastboot is active? Is "Starting Fastboot USB download protocol" ok? Taken literally this does not imply it's ready to be used. Do the log messages look ok?
I additionally have tried to enhance my udev rules file. There are a lot of descriptions all over the place, unfortunately they are contradicting in places. Any help is highly appreciated. Thanks!

The message that the fastboot protocol had started was the only thing I ever saw happen on the screen. The rest is in the terminal/command line window.
-that recently remarked that the manufacturer's code was no longer necessary (from JB bootloaders and onwards). You might need to add it in your case. <?> (I always forget what it is, but you can most easily look it up in the recovery flashing threads (esp. the CWM ones). "-i ..."
)

MartyHulskemper said:
The message that the fastboot protocol had started was the only thing I ever saw happen on the screen. The rest is in the terminal/command line window.
-that recently remarked that the manufacturer's code was no longer necessary (from JB bootloaders and onwards). You might need to add it in your case. <?> (I always forget what it is, but you can most easily look it up in the recovery flashing threads (esp. the CWM ones). "-i ..."
)
Click to expand...
Click to collapse
Thanks for replying. Well, maybe I was overly sensitive here because it was not working. However, the message on the Infinity says it's "starting" and not that it "has started".
Encouraged by your reply I tried something different. Instead of trying to check with the "devices" command, I simply tried to re-flash the recovery. To my amazement and pleasure it simply worked Now I feel prepared for any flashing adventure the future may bring! On a lighter note, I find it strange that the devices command doesn't work. To me that seemed to be the most "harmless" command to check the fastboot setup. My HD2 also reacts different on the devices command.
Bottom line, the fastboot devices command seems not to be suitable to do the check I wanted. Thanks for your help!

FordPrefect said:
TBottom line, the fastboot devices command seems not to be suitable to do the check I wanted.
Click to expand...
Click to collapse
It works for me:
Code:
[email protected] ~ $ lsusb|grep ASUS
Bus 002 Device 066: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
[email protected] ~ $ fastboot devices
015e3aabe751ed14 fastboot
[email protected] ~ $ fastboot continue
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.001s
(then the tablet says "Cold Booting Linux" and does exactly that)
Here are my udev rules:
Code:
# Transformer TF700
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c90", GROUP="plugdev", MODE="0660" # normal
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c91", GROUP="plugdev", MODE="0660" # USB Debugging
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4daf", GROUP="plugdev", MODE="0660" # Fastboot
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7030", GROUP="plugdev", MODE="0660" # Tegra APX

_that said:
It works for me:
Code:
[email protected] ~ $ lsusb|grep ASUS
Bus 002 Device 066: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
[email protected] ~ $ fastboot devices
015e3aabe751ed14 fastboot
[email protected] ~ $ fastboot continue
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.001s
(then the tablet says "Cold Booting Linux" and does exactly that)
Here are my udev rules:
Code:
# Transformer TF700
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c90", GROUP="plugdev", MODE="0660" # normal
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c91", GROUP="plugdev", MODE="0660" # USB Debugging
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4daf", GROUP="plugdev", MODE="0660" # Fastboot
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7030", GROUP="plugdev", MODE="0660" # Tegra APX
Click to expand...
Click to collapse
Thanks for supplying your udev rules. I adjusted mine following your example. Still shows nothing with the devices command. Also for flashing I have to supply the manufacturer code, which I have read somewhere wouldn't be needed any more. Anyway, flashing recovery works for me now, and that's what I wanted to achieve.

Ubuntu 12.04 fastboot no devices ASUS MemoPad

After building a system image to root the ASUS MemoPad FHD 10, I am fed up with having to wait almost 15 minutes for Windoze to boot up and shut down so I can run fastboot to flash the image file. So, I've been on a quest to get adb and fastboot working with Ubuntu so I don't have to deal with stupid Windoze.
Using lnusb, tablet has different vendor:device ids when regular booted and usb debug on (adb mode) and when bootloader/recovery booted with fastboot waiting for command.
Tablet mounts using 'go-mtpfs' so I can work with internal/external SDcards.
Tablet displays with 'adb devices' (normal boot) as Medfield9A65CCEC (also shows this with Windoze fastboot devices)
Tablet doesn't display with 'fastboot devices' (bootloader/recovery boot)
51-android.rules file to recognize both vendor ids:
Code:
# ASUS MemoPad FHD 10 32Mb
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666", GROUP="plugdev", OWNER="Me" # MTP mode with USB debug on
SUBSYSTEM=="usb", ATTR(idVendor}=="8087", MODE="0666", GROUP="plugdev", OWNER="Me" # fastboot mode
Tried downloading a different fastboot binary, same results.
At this point I am stumped why adb works but fastboot does not. fastboot works fine in Windoze.

More Info
After some more research, I found this:
http://packages.ubuntu.com/raring/i386/android-tools-fastboot/filelist
which shows a rules file in /lib/udev/rules.d/70-android-tools-fastboot.rules
so I looked in /lib/udev/rules.d and found the rules file: 51-android-rules.rules with loads of entries
and not /etc/udev/rules.d/51-android-rules.rules as most discussions refer to
so I modified the ASUS section to this:
Code:
# Asus MemoPad FHD 10 (Intel)
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", ATTR{idProduct}=="521f", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="8087", ATTR{idProduct}=="09ef", SYMLINK+="android_fastboot"
#SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0660", GROUP="adbusers"
#SUBSYSTEM=="usb", ATTR{idVendor}=="8087", MODE="0660", GROUP="adbusers"
If I comment out the first two lines and use #3&4 syslog shows an error - udevd[3982]: specified group 'adbusers' unknown
If I use the first two lines and comment out #3&4 (as shown above) syslog shows:
Code:
Dec 20 14:45:48 kernel: [25297.608132] usb 2-1: new high-speed USB device number 11 using ehci-pci
Dec 20 14:45:48 kernel: [25297.745240] usb 2-1: New USB device found, idVendor=8087, idProduct=09ef
Dec 20 14:45:48 kernel: [25297.745252] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Dec 20 14:45:48 kernel: [25297.745260] usb 2-1: Product: Android-Phone
Dec 20 14:45:48 kernel: [25297.745268] usb 2-1: Manufacturer: Android
Dec 20 14:45:48 kernel: [25297.745275] usb 2-1: SerialNumber: Medfield9A65CCEC
Dec 20 14:45:48 mtp-probe: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Dec 20 14:45:48 mtp-probe: bus: 2, device: 11 was not an MTP device
There are no errors, so the rules file in /lib/udev/rules.d and not /etc/udev/rules.d is being used
Also interesting is that lsusb shows:
Bus 002 Device 011: ID 8087:09ef Intel Corp.
...which is a different Vendor ID
However, even with the correct rules file set and no syslog errors on USB connect, fastboot still refuses to recognize the device when connected in fastboot mode.
I have also tried fastboot i 0x8087 reboot and fastboot -sMedfield9A65CCEC reboot and it just waits for device.
It may be possible that fastboot doesn't like the Intel and is looking for ARM, not sure - although Windoze version of fastboot works fine.

On Archlinux I have the same problem
sudo adb devices works, fastboot fails with <Waiting for device>
but in fastboot mode nothing works at all

Same problem in Ubuntu 14.04 for Kindle Fire
I know this thread has been dormant for a while, but it's pretty much the only hit that comes up when searching on how to setup the /lib/udev/rules.d/70-android-tools-fastboot.rules to get device to mount in fastboot properly.
I had followed some other guides like the OP that said to put rules in the /etc/udev/rules.d/51-android-devices.rules which didn't work at all. I do not have a file /lib/udev/rules.d/51-android-devices..rules
I am having issues similar to the OP with a Kindle Fire Gen2. Device shows up when in Adb mode, but not in fastboot (using factory "fastboot" cable).
Was there ever a resolution to this issue?
Anybody have a source of documentation on how these config files need to be set up when in fastboot mode to gain access and/or get a trusted connection in MTP?

understanding if fastboot is enabled on mi a3 with broken screen

Hi *,
I hava a xiaomi mi a3 with broken screen, i already rooted and enable debugging previous of the broken.
Now i would use scrcpy but adb listing my device as unhautorized.
I see in other post that i need to copy the key on /android/data/..., but i unable because adb shell does not work, so i read that entering in fastboot mode i able to copy the files without key.
So i powered off the phone and restart with volume up+power and i see this on my syslog
Oct 22 15:32:22 debian-z230 kernel: [ 5541.994136] usb 2-7: new high-speed USB device number 19 using xhci_hcd
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144023] usb 2-7: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.14
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144038] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144044] usb 2-7: Product: Mi A3
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144048] usb 2-7: Manufacturer: Xiaomi
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144051] usb 2-7: SerialNumber: 7044fce4312c
Oct 22 15:32:23 debian-z230 gvfsd[14218]: LIBMTP PANIC: Unable to find interface & endpoints of device
Oct 22 15:32:23 debian-z230 gnome-shell[2659]: Unable to mount volume Mi A3: Gio.IOErrorEnum: Unable to open MTP device “002,019”
Oct 22 15:32:24 debian-z230 gvfsd[14218]: Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
I tryed to run adb but it seems always recognized it as unhautorized, fastboot devices command instead does not report any output:
[email protected]:~$ fastboot devices
[email protected]:~$ fastboot reboot
< waiting for any device >
[email protected]:~$ adb devices
List of devices attached
7044fce4312c unauthorized
if the phone starts in normal mode instead on the syslog i see this
Oct 22 15:44:24 debian-z230 kernel: [ 6263.802797] usb 2-7: new high-speed USB device number 24 using xhci_hcd
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953115] usb 2-7: New USB device found, idVendor=2717, idProduct=ff08, bcdDevice= 4.14
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953121] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953123] usb 2-7: Product: Mi A3
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953125] usb 2-7: Manufacturer: Xiaomi
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953126] usb 2-7: SerialNumber: 7044fce4312c
Oct 22 15:44:24 debian-z230 mtp-probe: checking bus 2, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Oct 22 15:44:24 debian-z230 mtp-probe: bus: 2, device: 24 was not an MTP device
Oct 22 15:44:25 debian-z230 mtp-probe: checking bus 2, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Oct 22 15:44:25 debian-z230 mtp-probe: bus: 2, device: 24 was not an MTP device
Oct 22 15:44:55 debian-z230 /usr/libexec/gdm-x-session[2473]: (EE) event2 - Primax HP USB Keyboard: client bug: event processing lagging behind by 13ms, your system is too slow
Oct 22 15:45:01 debian-z230 CRON[14796]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
so seems that product, vendor and device id is different.
Could someone confirm that the first id, of product vendor and device is fastboot device?
There is a method to solve this impasse?
Thanks a lot to all
so the vendor product and device is different

Fastboot gets enabled by default when an Android device boots up, unless manufacturer ( e.g. Samsung ) decided not to support Fastboot. But Xiamomi devices support Fastboot, AFAIK.
FYI: Fastboot isn't a device you can find in /dev/block, it's a software that allows to operate on Android device's bootloader.

jwoegerbauer said:
Fastboot gets enabled by default when an Android device boots up, unless manufacturer ( e.g. Samsung ) decided not to support Fastboot. But Xiamomi devices support Fastboot, AFAIK.
FYI: Fastboot isn't a device you can find in /dev/block, it's a software that allows to operate on Android device's bootloader.
Click to expand...
Click to collapse
Hi and thanks for the answers, but I think that Linux discover fastboot device with different product vendor and device id respect normal boot. I would know why fastboot command does not discover my device, I suspect, because my screen on device is broken, that device not start in fastboot mode and I ask to group what kind of product device and vendor I'd you seen for your xiaomi mi a3 device under syslog or lsusb in fastboot mode.

Yes
Code:
sudo ./fastboot devices
returns
Code:
<SERIAL_ID> fastboot
but that's NOT AN ANDROID DEVICE, IT'S THE DEVICE'S BOOTLOADER connected to, and nothing else.
If the output is shown as above listed, then Fastboot-mode is enabled/activated and working.