Hi, this is my first post, so im not sure how to do this
I have adquired a Vexia Navlet 2 White version, managed to root it everything worked fine but i was fooling around with it (of course ¬_¬) and now im stuck on a bootloop with no adb shell (due to permissions).
It tries too boot but crash, or something, and then it reboot and spit me into the default recovery (Android System Recovery <e3>), before this happened i made a backup with nandroid online backup but ended with a tar stuff
Code:
Files Backed-up:
"
----rwxr-x 1 7519232 May 20 23:01 .android_secure.vfat.tar
----rwxr-x 1 10485760 May 20 22:59 boot.img
----rwxr-x 1 2560 May 20 23:01 cache.yaffs2.tar
----rwxr-x 1 404272640 May 20 23:01 data.yaffs2.tar
----rwxr-x 1 352 May 20 23:06 nandroid.md5
----rwxr-x 1 10485760 May 20 22:59 recovery.img
----rwxr-x 1 667948032 May 20 23:04 sd-ext.vfat.tar
----rwxr-x 1 222075392 May 20 23:00 system.yaffs2.tar
"
Device data:
Code:
ro.build.id=MID
ro.build.display.id=full_m805_892x_evm-userdebug 4.0.3 MID eng.zxp.20121031.161114 test-keys
ro.build.version.incremental=eng.zxp.20121031.161114
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Wed Oct 31 16:13:19 HKT 2012
ro.build.date.utc=1351671199
ro.build.type=userdebug
ro.build.user=zxp
ro.build.host=kf-mid
ro.build.tags=test-keys
ro.product.model=Vexia Tablet 780 GPS
ro.product.brand=Android
ro.product.name=full_m805_892x_evm
ro.product.device=m805_892x
ro.product.board=m805_892x_evm
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=es
ro.product.locale.region=ES
ro.wifi.channels=
ro.board.platform=tcc892x
# ro.build.product is obsolete; use ro.product.device
ro.build.product=m805_892x
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_m805_892x_evm-userdebug 4.0.3 MID eng.zxp.20121031.161114 test-keys
ro.build.fingerprint=Android/full_m805_892x_evm/m805_892x:4.0.3/MID/eng.zxp.20121031.161114:userdebug/test-keys
ro.build.characteristics=tablet,sdcard
and i dont know if i can or how i can flash system and data back with fastboot, this device dont have clockworkmod.
I have tried different things but im totally stuck, as a note using the builder.clockworkmod.com and providing the older recovery and/or recovery.fstab gave my back a non-working CMW, in wich only the sd card can be mounted (even mount usb storage dont work), all the other stuff fail.
I suppose that if i can mange to fix the mountings points for the CWM i can restore system and data, but i dont know how to do it.
I have windows 7 and linux Mint 14, so it dosent matter where to go, i can enter botloader, fasboot mode and adb on recovery.
Pls, help
I attach all files i have available, except the backup (its big) ill add it, or other files, if neccesary.
Thx.
Good Luck
glorer said:
Hi, this is my first post, so im not sure how to do this
I have adquired a Vexia Navlet 2 White version, managed to root it everything worked fine but i was fooling around with it (of course ¬_¬) and now im stuck on a bootloop with no adb shell (due to permissions).
It tries too boot but crash, or something, and then it reboot and spit me into the default recovery (Android System Recovery <e3>), before this happened i made a backup with nandroid online backup but ended with a tar stuff
Code:
Files Backed-up:
"
----rwxr-x 1 7519232 May 20 23:01 .android_secure.vfat.tar
----rwxr-x 1 10485760 May 20 22:59 boot.img
----rwxr-x 1 2560 May 20 23:01 cache.yaffs2.tar
----rwxr-x 1 404272640 May 20 23:01 data.yaffs2.tar
----rwxr-x 1 352 May 20 23:06 nandroid.md5
----rwxr-x 1 10485760 May 20 22:59 recovery.img
----rwxr-x 1 667948032 May 20 23:04 sd-ext.vfat.tar
----rwxr-x 1 222075392 May 20 23:00 system.yaffs2.tar
"
and i dont know if i can or how i can flash system and data back with fastboot, this device dont have clockworkmod.
I have tried different things but im totally stuck, as a note using the builder.clockworkmod.com and providing the older recovery and/or recovery.fstab gave my back a non-working CMW, in wich only the sd card can be mounted (even mount usb storage dont work), all the other stuff fail.
I suppose that if i can mange to fix the mountings points for the CWM i can restore system and data, but i dont know how to do it.
I have windows 7 and linux Mint 14, so it dosent matter where to go, i can enter botloader, fasboot mode and adb on recovery.
Pls, help
I attach all files i have available, except the backup (its big) ill add it, or other files, if neccesary.
Thx.
Click to expand...
Click to collapse
A common problem when using adb to access your Android phone via USB is:
$ adb devices
List of devices attached
???????????? no permissions
According to official Android Developers website:
If you’re developing on Ubuntu Linux, you need to add a rules file that contains a USB configuration for each type of device you want to use for development. Each device manufacturer uses a different vendor ID. The example rules files below show how to add an entry for a single vendor ID (the HTC vendor ID). In order to support more devices, you will need additional lines of the same format that provide a different value for the SYSFS{idVendor} property.
Quick fix:
sudo -s
adb kill-server
adb start-server
adb devices
Permanent fix:
$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 093a:2510 Pixart Imaging, Inc. Hama Optical Mouse
Bus 004 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 002 Device 002: ID 18ea:0004 Matrox Graphics, Inc. TripleHead2Go [Digital Edition]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 010: ID 0bb4:0c87 High Tech Computer Corp. <<<<<<<< my HTC phone
Bus 001 Device 008: ID 046d:0817 Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Note 0bb4 is the vendor ID. Next, create /etc/udev/rules.d/51-android.rules with the following lines:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Final steps:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo udevadm control --reload-rules
Done.
A list of popular vendor IDs:
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
ref. Android Developers
ken.okech.94 said:
A common problem when using adb to access your Android phone via USB is:
$ adb devices
List of devices attached
???????????? no permissions
According to official Android Developers website:
If you’re developing on Ubuntu Linux, you need to add a rules file that contains a USB configuration for each type of device you want to use for development. Each device manufacturer uses a different vendor ID. The example rules files below show how to add an entry for a single vendor ID (the HTC vendor ID). In order to support more devices, you will need additional lines of the same format that provide a different value for the SYSFS{idVendor} property.
Quick fix:
sudo -s
adb kill-server
adb start-server
adb devices
Permanent fix:
$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 093a:2510 Pixart Imaging, Inc. Hama Optical Mouse
Bus 004 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 002 Device 002: ID 18ea:0004 Matrox Graphics, Inc. TripleHead2Go [Digital Edition]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 010: ID 0bb4:0c87 High Tech Computer Corp. <<<<<<<< my HTC phone
Bus 001 Device 008: ID 046d:0817 Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Note 0bb4 is the vendor ID. Next, create /etc/udev/rules.d/51-android.rules with the following lines:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Final steps:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo udevadm control --reload-rules
Done.
A list of popular vendor IDs:
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
ref. Android Developers
Click to expand...
Click to collapse
no no i have connectivity
adb during bootloop process
Code:
List of devices attached
20120122800F32 device
adb when tablet is on recovery mode
Code:
List of devices attached
20120122800F32 recovery
fasboot on bootloader mode
Code:
???????????? fastboot
i can flash stuff and all, but "adb shell" return this on device mode
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
and this on recovery mode
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and i dont know what to do ><
Is there no way to turn the system.yasff2.tar into system.img, so that i can try to do a flashboot system system.img ?¿
truth to be told i will rather make CWM work
PD
forgot mention i dont know that much about linux, thought im more that willing to learn ^^, i wouldn't been using mint if that wasn't the case
glorer said:
no no i have connectivity
adb during bootloop process
Code:
List of devices attached
20120122800F32 device
adb when tablet is on recovery mode
Code:
List of devices attached
20120122800F32 recovery
fasboot on bootloader mode
Code:
???????????? fastboot
i can flash stuff and all, but "adb shell" return this on device mode
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
and this on recovery mode
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and i dont know what to do ><
Is there no way to turn the system.yasff2.tar into system.img, so that i can try to do a flashboot system system.img ?¿
truth to be told i will rather make CWM work
PD
forgot mention i dont know that much about linux, thought im more that willing to learn ^^, i wouldn't been using mint if that wasn't the case
Click to expand...
Click to collapse
try to flash goclever gps firmware
Related
Not really a development question, but I still think this section of the forum suites best.
My device (Acer A500 tab) is not recognized by Eclipse when I plug it in via USB (USB debugging is set, ofc). It is, however, recognized by OS as a valid USB device - I can see it with lsusb.
Any suggestions?
Thanks in advance.
P.S. I never had such a problem on Windows. I can't beleive Linux cannot be use for development.
Sorry, my bad. The device couldn't connect via USB because it was already connected over Wi-Fi, and I forgot about it
Please close the topis.
Connecting via USB to Linux (Ubuntu)
I could not get my Ubuntu machines to recognize the tablet when I plugged in the USB cable. Bummer.
Digging around I found a similar issue experienced by Xoom owners. The original article describing the fix is here. The steps listed there are for the Xoom, not the Acer, although the fix is almost the same.
I am posting the slightly modified instructions again here for clarity and brevity.
I did this fix on both Ubuntu 10.10 (Maverick) and 11.04 (Natty). Your mileage may vary.
1. Get the mtpfs package installed on your machine.
Code:
sudo apt-get install mtpfs
2. In the tablet, go to Settings->Applications->Development and turn USB Debugging on (check the box). For me, this was required for file transfers to work.
3. Plug your USB cable into the tablet and your Ubuntu machine.
4. Open your Terminal app on the Ubuntu machine.
5. Use the lsusb command to get the vendor id. Type "lsusb" in Terminal.
6. The output should look something like this:
Code:
[email protected]:~$ lsusb
Bus 005 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 003 Device 006: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 003 Device 005: ID 05af:0802 Jing-Mold Enterprise Co., Ltd
Bus 003 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0502:3325 Acer, Inc.
Bus 001 Device 003: ID 04f2:b16b Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The line with "Acer, Inc." in it tells you the VendorID. In the example above, it's 0502.
** Disconnect the USB cable at this point **
7. Create a UDEV rule file. Use your editor of choice, mine is nano.
Code:
sudo nano /etc/udev/rules.d/51-android.rules
The file should contain this line when you are finished:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
8. Create a mount point and make yourself the owner.
Code:
sudo mkdir /media/a500
sudo chown user:user /media/a500
IMPORTANT: Replace user:user with your user name and default group on your Ubuntu machine. For most people it will be your login name. If your login is "bob", then replace user:user with bob:bob, capice?
9. Add the mount point to fstab.
Code:
sudo nano /etc/fstab
At the bottom of the file, type this stuff:
Code:
# mount point for Acer A500
mtpfs /media/a500 fuse user,noauto,allow_other 0 0
10. Modify fuse.conf. Uncomment user_allow_other.
Code:
sudo nano /etc/fuse.conf
Look for #user_allow_other and remove the #.
11. Add yourself to the fuse group.
Code:
sudo nano /etc/group
Look for the line starting with "fuse" and put your login at the end of that line (if it's not already there).
12. Reboot.
You should see your mount point in Nautilus when you open it. After plugging in the USB cable, you can click the a500 entry under Places to mount the tablet.
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
I have installed Arch Linux but cannot find suitable material on setting up drivers and utilities for flashing rom on Linux specifically arch linux.
I can setup arch even if instructions are available for other distro Linux Mint and Ubuntu so any link can come in handy.
I was using flashtool in windows but after shifting to Arch, I am not sure whats the right procedure to do it.
I have unlocked bootloader and rooted rom (FXP kernel + MIUI) installed as of now which I want to change asap.
Please help.
Regards
Hello,
You don't need any drivers,just install android-udev and android-sdk-platform-tools for adb and fastboot (both from aur).
Download latest flastool and run it from the terminal just like you do in windows (it requires jre and libusbx from official repos ).
Ok I have reinstalled fatsboot, android-sdk-platform-tools and openjre
Now I still cannot use fastboot devices , its list nothing.
Also since I should have adb available (from sdk-platform) when I run adb it says no command ?
Code:
[[email protected] fastboot]$ fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo adb
sudo: adb: command not found
[[email protected] fastboot]$ adb
bash: adb: command not found
I have also installed udev-android , previous I created 51-android.rules manually but still doesnt work.
fastboot won't list the devices nor it works.
Code:
[sha[email protected] fastboot]$ lsusb
Bus 002 Device 005: ID 413c:2107 Dell Computer Corp.
Bus 002 Device 003: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0fce:5146 Sony Ericsson Mobile Communications AB
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
First of all make sure you have enabled usb debugging on your phone.Adb and fastboot should be under /opt/android-sdk/platform-tools/ and also 51-android.rules file in /usr/lib/udev/rules.d/ (with -rw-r--r-- permissions).
With these things i have everything in my sytem to flash roms etc,maybe you're missing something with your installation.
Also for more information check wiki from archlinux wiki.archlinux.org/index.php/android
The issue is now solved.
I'm trying to set up adb in Ubuntu 14.04.3 64bit but its not showing up when I connect my device.
Here is what I did
I installed adb and fastboot using these commands
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
I got the adb driver files from my device and executed it
Code:
sh ~/Desktop/adb_config_Linux_OSX.sh
The command got executed and adb_usb.ini file got created successfully at ~/.android/ folder.
Now I connected my device with USB debugging ON
When I run the adb devices command this is what I get
Code:
List of devices attached
The list of devices is empty.
When I run my lsusb command
Code:
Bus 001 Device 005: ID 0cf3:0036 Atheros Communications, Inc.
Bus 001 Device 003: ID 0bda:5756 Realtek Semiconductor Corp.
Bus 001 Device 010: ID 2a70:904d
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The vendor is not showing up. It is left blank.
I tried the same method in both MTP as well as PTP mode. Still no luck.
Could someone help me out please because I operate only on Ubuntu and can't use Windows.
Have you enabled `android debug`?
YumeMichi said:
Have you enabled `android debug`?
Click to expand...
Click to collapse
You mean usb debugging?? Yes I have
Run the script as root and you should be fine, tested with Linux Mint 17.2.
Not sure if it makes a difference, I made it executable with chmod +x and run as root from my home directory instead of using sh.
Solved the issue...The RSA fingerprint had to be accepted on the device.
Also I had to run all commands as administrator using sudo
Sent from my ONE E1003 using Tapatalk
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.