Amazon Kindle Fire HDX 7”
Deleted System by mistake because... well... I'm human (meaning, I make mistakes).
Spent the good portion of the last week reading forums/posts and have it recognized in Ubuntu Linux as a device in Nautilus. Unable to mount it.
I've attempted adb – no device.
I've attempted mtp – won't mount.
lsusb, mtp-detect, 50-android.rules, 51-android.rules, 99-android.rules, bash.sh, AARGH!
Sucks being me.
p.s. Thanks for letting me vent.
Is that a light at the end of the tunnel or just a train?
Have yet to give up. Still banging my head against it. Lot's of good info on here. None of it works for me... yet. Now if I could find my external DVD, I'm going to re-install Ubuntu on my Netbook, then JDK, then APK, then, then, then... configure... configure... recharge HDX... sob uncontrollably... drink... smile.
mtp vs adb
Nautilus recognizes Kindle as Android but will not mount. I assume this is via mtp.
adb does not recognize device regardless of what is in 51-android.rules.
Does not seem to matter if I use regular or "factory" cable.
I have to admit the grey Kindle Fire is memorizing.
Sigh...
I suppose the most frustrating thing is I have read many circumstances similar to mine, followed their steps, and still nothing. Maybe I'm just not holding my tongue the right way?
Gonna wait until external DVD arrives to rebuild system. Other than that, I'm at a dead end. Tired of attempting the same thing expecting different results. Been working on it now for 10 days, obsessively. Compulsively, even.
I'll post more once I have some different results.
What a let down...
Found my external DVD player. Installed Ubuntu 12.04 from DVD, replacing previous version. Installed updates.
Followed these instructions:
http://forum.xda-developers.com/showthread.php?t=2302780&page=2
Installing these packages:
https://developer.amazon.com/sdk/fire/setup.html
No luck. Still "no devices found".
Isn't even recognized by file manager.
I'm at a loss for next step. Ideas anyone?
---
lsusb:
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 001 Device 006: ID 18d1:0001 Google Inc.
Bus 001 Device 003: ID 0402:7670 ALi Corp.
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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
Bus 001 Device 005: ID 045e:0023 Microsoft Corp. Trackball Optical
Click to expand...
Click to collapse
usb-devices:
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=18d1 ProdID=0001 Rev=02.32
S: Manufacturer=Android
S: Product=Android
S: SerialNumber=0123456789ABCDEF
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=2mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=(none)
Click to expand...
Click to collapse
51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
Click to expand...
Click to collapse
Is more information needed?
Please let me know if I need to include more information in order to receive some assistance.
I don't care if I can ever root the thing again. I just want my Kindle HDX back.
Anyone?
Just wanted to let you know you're not alone buddy! I did something similar and have yet to be able to do anything with my hdx. Factory cable arrives tomorrow or Friday . Good luck to you!
Thanks. Speaking of Factory Cable...
Not to wish ill on anyone else, but it's nice to know I'm not alone.
That reminds me.
With factory cable:
lsusb:
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 001 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 001 Device 003: ID 0402:7670 ALi Corp.
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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
Bus 001 Device 005: ID 045e:0023 Microsoft Corp. Trackball Optical
Click to expand...
Click to collapse
usb-devices:
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 11 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=05c6 ProdID=9008 Rev=00.00
S: Manufacturer=Qualcomm CDMA Technologies MSM
S: Product=QHSUSB__BULK
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial
Click to expand...
Click to collapse
51-android.rules
same as before
adb devices results in nothing
I am in the same situation, device appears as a Qualcomm stuff if its turned off with lsusb
Anyone has any progress here?
Related
I've been googling for 2 days but no luck.
I've bought a new pad from some site from china. I don't know whether it is appropriate writing its link so I won't. It is a zt-180 10" pad with Android 2.2
Spec is:
Model:zt180
Android:android_2.2
Kernel:2.6.32.9
Build:zt180-eng AOSP OPENMASTER eng.root.20110808.120935 test-keys
I don't know what is build or required. Anyway, I'm using Ubuntu 11.10 32-bit on both desktop and laptop. My device is NOT rooted.
I've installed necessitas and android sdk. I enabled usb debugging on device. I'm using OTG input on the device.
Outputs:
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 005: ID 0cf3:3005 Atheros Communications, Inc.
Bus 001 Device 004: ID 13d3:5122 IMC Networks
Bus 002 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 003 Device 002: ID 18d1:0001 Google Inc.
[email protected]:~$ cd /opt/necessitas/android-sdk/platform-tools/
[email protected]:/opt/necessitas/android-sdk/platform-tools$ ./adb kill-server
[email protected]:/opt/necessitas/android-sdk/platform-tools$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:/opt/necessitas/android-sdk/platform-tools$
I've tried these rule configurations in /etc/udev/rules.d/51-android.rules seperately:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
or
SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666
or
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1"
TEST=="/var/run/ConsoleKit/database",
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
or
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”18d1″, ATTRS{idProduct}==”0001″, MODE=”0666″
and then called this after each one:
[email protected]:/opt/necessitas/android-sdk/platform-tools$ sudo service udev restart
udev start/running, process 15807
[email protected]:/opt/necessitas/android-sdk/platform-tools$
But no way, I couldn't make adb to see my device:
[email protected]:/opt/necessitas/android-sdk/platform-tools$ ./adb kill-server
[email protected]:/opt/necessitas/android-sdk/platform-tools$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:/opt/necessitas/android-sdk/platform-tools$
By the way, I tried HTC Tattoo and it works with the
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
configuration.
Please help me.
EDIT:
I've tried editing ~/.android/adb_usb.ini and adding 0x18d1 to this file. But again it didn't work.
Do you use appropriate drivers for your USB?
Accidentally sent from my Google Nexus S using XDA Premium
I thought drivers are only for Windows environments. Do i need drivers?
Hi guys,
I have used the following tutorials:
http://forum.xda-developers.com/showthread.php?t=735375
http://forum.xda-developers.com/showthread.php?t=921169&page=2
But still when I type "./adb devices" or "sudo ./adb devices" all I get is "List of aevices attached" followed by a blank. Do you know a way to fix this?
I'm using a Samsung Galaxy Tab.
Thanks in advance.
Could you paste your dmesg? What's your OS?
Could you paste your 51-android.rules and output of lsusb?
My OS is Ubuntu 11.10
The output of lsusb is:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:5c11 Hewlett-Packard PhotoSmart C4200 Printer series
Bus 003 Device 002: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000
Bus 006 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 006 Device 003: ID 045e:0730 Microsoft Corp.
Bus 002 Device 005: ID 04e8:6877 Samsung Electronics Co., Ltd
Click to expand...
Click to collapse
The 51-android-rules file contains
SUBSYSTEM==usb, SYSFS{idVendor}==0bb4, MODE=0666
Click to expand...
Click to collapse
Are you using the stock USB cable that came with your tablet? Is the cable in good shape?
I had a Samsung device that would not show up under my devices in Ubuntu. I later discovered it was because my cable was damaged internally. It charged, but had trouble connecting for data.
Is there any way this could be the issue?
adb driver
are you sure you have install the adb driver ?
The vendor id in your udev file is the HTC vendor id.. you should use the samsung one: 04e8
Besides, you can just try:
adb kill-server
and then:
sudo adb start-server
and see if you can get your device listed
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Hi,
Not sure where exactly to post this, so sorry if this isn't the right section. I've asked on the Linux Mint community forums (as they should have experience with the OS) but figured I'd also post here (as you guys should have experience with ADB and fastboot).
I recently switched over from Win 7 to Mint 15 and cannot get ADB and fastboot to work for the life of me! On Windows, I just downloaded and installed the Android SDK and had no trouble using ADB and fastboot to mod my phone. It is proving to be much more difficult on Linux.
I've searched Google, Linux Mint forums, and these forums; tried following numerous guides, and still my comp can't recognize my phone. Every time I type in "adb devices" I get "List of connected devices" followed by a blank line. No question marks and certainly no connected devices. "lsusb" shows my HTC One S as connected so I know it's not my USB port.
When I plug in my phone, I get an error message, "Unable to mount Android Phone Unable to open MTP device '[usb:002,005]'" and then a file explorer window opens displaying my phone contents anyways. Not sure if this could have anything to do with it but I thought I'd mention it.
In any case, I've tried so many things and am at a complete loss here. Any help would be great as nothing seems to be working and not being able to flash ROMs on my phone is killing me! :?
Thanks in advance.
No one? Craaaaaaap
DRUMROT said:
No one? Craaaaaaap
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
Check PM.
No luck. This is getting frustrating.
That did the trick for me:
Configuring USB Access
Under GNU/linux systems (and specifically under Ubuntu systems), regular users can't directly access USB devices by default. The system needs to be configured to allow such access.
The recommended approach is to create a file /etc/udev/rules.d/51-android.rules (as the root user) and to copy the following lines in it. <username> must be replaced by the actual username of the user who is authorized to access the phones over USB.
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="<username>"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="<username>"
Those new rules take effect the next time a device is plugged in. It might therefore be necessary to unplug the device and plug it back into the computer.
This is known to work on both Ubuntu Hardy Heron (8.04.x LTS) and Lucid Lynx (10.04.x LTS). Other versions of Ubuntu or other variants of GNU/linux might require different configurations.
Click to expand...
Click to collapse
from: http://source.android.com/source/initializing.html
Maybe you have to google a bit if your device is not included. If you just google 51-android-rules devicename you should find the corresponding entry.
Edit: Sorry, it was another file I used: http://code.google.com/p/51-android/source/browse/51-android.rules in this version, just the vendor is specified so you don't have to care about device id. And not just the owner (here: snowdream) is able to access the device but everyone in its group. But the one above should work as well.
The guides I followed had me create various rules.d files (99, 50, 70) and it still hasn't worked. They've never said to change the username but they must have followed the same rules as your updated link. Either way, I'll try what you've said and see what happens. I'll post back with results. Thanks for the help!
EDIT: Ok so I tried it...and it didn't work.
Not even sure what made me do it, but I decided to search for the tools for a 64-bit system (I'm using a 32-bit). I ended up getting different results and found this script https://code.google.com/p/adb-fastboot-install/ which finally made adb recognize my phone! Thank you for trying to help. Really appreciate it guys/gals.
Hello Everyone, my firts post asking for help, Installed ADB on Ubuntu 12.04 and succesfully rooted 1 Huawei and two Lgs but now im stucked woth MY own phone
Got a Chinese Double Sim Phone, actually not bad but after almost one week of trying and looking everywhere i cant get ADB to recognize my phone, When i Type lsusb on terminal, it appears:
Bus 001 Device 003: ID 1782:5d04 Spreadtrum Communications Inc.
my /etc/udev/rules.d/99-android.rules :
SUBSYSTEM=="usb", ATTR{idVendor}=="1782",ATTRS{idProduct}=="5d04" MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1782", ATTRS{idProduct}=="5d04"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{ACTION} --device=$env{DEVNAME}"
But when i put adb devices:
List of devices attached
(Empty)
Anyone, can please give me a hand here please? Thank You
Hello all, I have a little project I'd like some help on. I have recently bought an Alba 4 inch with android 7 (Nougat). I'd like to use this phone purely for SatNav work, but it appears that it doesn't like working the GPS without SIM or wireless. I have done some research and apparently, a few people have experienced a similar issue when updating from android 6 to 7. So I thought I'd root my 'Alba' and flash it back to 6 to see if that improves the GPS usage unless someone can tell me otherwise. It's quite maddening as I have an old Nokia Lumia 925 (Windows 8.1) which has no problem using the internal GPS device without wireless or SIM card - in fact, my old N8 and X6 have no problem at all and I still use those but software is now almost defunct. However, I'd like to pursue with the 'Alba' as I want to install OsmAnd or equivalent app and upload created gpx routes from my laptop, for me to use on my mountain bike or road bike. The reason I'm going for a fairly simple mobile, but should fit the bill, is that it can be charged while out in the wild with a basic solar power pack. My other phone the Honor 8 requires more than a simple solar pack....
Details of phone - Alba 4 3g (AC40AS3G / SKU133814622) with Archos android 7.
Steps taken...
'OneClickRoot' doesn't have a root app entry for my particular phone. Now I've done the build number trick, allowed usb debugging, got the PC authorised on the phone, installed android sdk on my Ubuntu 12.04 laptop and I can run adb and some commands:
'adb devices' creates:
[email protected]:~$ adb devices
List of devices attached
18643080980731 device
'adb shell' creates:
[email protected]:~$ adb shell
ac40as3g:/ $
'adb reboot bootloader' - gives a screen with 'fastboot mode' in the top left corner of the mobile.
'fastboot oem unlock' and 'fastboot flashing unlock- both give "< waiting for any device >" but no listing
'fastboot devices' - this then produces "no permissions (user in plugdev group; are your udev rules wrong?); see [developer website] "
My lsusb command produces this, with phone connected in normal mode:
userATlaptop:~$ lsusb
Bus 002 Device 004: ID 0e79:5604 Archos, Inc.
Bus 008 Device 002: ID 8086:0189 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
My 51-android.rules file contains :
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666", GROUP="plugdev"
I also have a custom rule called '70-abdroid-custom-device.rules' which I created from some 'googled' page...
# Archos 4
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", ATTRS{idProduct}=="5609", TAG+="uaccess"
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", ATTRS{idProduct}=="5604", TAG+="uaccess"
'fastboot flashing get_unlock_ability' - this produces "< waiting for any device >" but nothing.
So questions are:
Have I got my udev right?
What would be the next step after correcting the first question?
...any other suggestions? Apart from 'throw it in the bin...' thanks.