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

[GUIDE] Fix Fastboot and USB

After writing my previous guide, i realized that a lot of people have had a fastboot problem when trying to flash cwm and adb problems while in cwm. After i flashed aosp, i realized that I lost recovery, and as i tried to reflash it, i had the problem as well.
Here's the fix.
1. Go to this github link and copy the text file.
2. Open up terminal and type in
sudo gedit /etc/udev/rules.d/51-android.rules​3. Replace what's in the folder with the the text in the file in github
4. Replace the text that says <username> with the username of your computer. (Don't erase the quotes!)
5. Find the line where it says "#adb protocol on the grouper (Nexus 7)"
6. Change the mode in the line under it to "0666"
It should look like this
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your user name here"​7. Save the file
8. Type in terminal
sudo service udev restart
sudo killall adb ​
Now fastboot and adb should be fixed!
Do a fastboot devices to check in bootloader and/or do a check for adb in cwm by adb devices.
If this helped at all, don't forget to click thanks and rate 5 stars!
Special thanks to ptspts on blogspot for the adb fix and johnmurrayvi on github for the rules file!

Is missing recovery-from-boot.p related to this problem?

another way
5implelove said:
Is missing recovery-from-boot.p related to this problem?
Click to expand...
Click to collapse
I had the same exact problem and I found this-
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Browse to your SDK directory and futher into <SDK>\extras\google\usb_driver
Open android_winusb.inf in your favorite text editor.
Find the appropriate section Google.NTx86 if your on 32bit or Google.NTamd64 if your on 64bit (doesnt matter that your using intel chip). Now find the ";Google Nexus 7" line inside that section and you'll see a series of settings below. Add the following lines at the end of that block.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
These are the identifiers for the Nexus 7 recovery and bootloader usb connections.
(Source- Napalm2) http://forum.xda-developers.com/showthread.php?t=1794203
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This may be easier for some and it worked for me.

5implelove said:
Is missing recovery-from-boot.p related to this problem?
Click to expand...
Click to collapse
This is something on the phone, not a driver problem. In the Nexus 7, some people had to do it, some didn't. When i first got mine at IO, i had to, but i recently did it, and i didn't have to. It's hit or miss

Thanks bro ...you know a way for win users?? My problem is that I do not know why, the recovery unmount when I test some my mod on rom AOSP
I've update usb_driver from SDK and add the string on android_winusb.inf but nothing to do...now I have anxiety every flash that the recovery can unmount
Inviato dal mio Nexus 7 con Tapatalk 2

"3. Replace what's in the folder with the the text in the file in github"
sorry, where is the folder?
terminal as in the nexus7 am i right?

I've followed these instructions yet I still get ???????????????????? after running adb devices
I'm on Ubuntu 12.04

Ir0nLy0n said:
I've followed these instructions yet I still get ???????????????????? after running adb devices
I'm on Ubuntu 12.04
Click to expand...
Click to collapse
i've tidied it and added all modes...
follow the instructions in the OP but instead make 99-android.rules: (it loads later after everything is initialized)
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your user name here" # 8GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="your user name here" # 16GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="your user name here" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="your user name here" # Recovery
You can do this with ANY usb hardware. Just use for example:
Code:
[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 005 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 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 005 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 08bb:2902 Texas Instruments Japan PCM2902 Audio Codec
Bus 003 Device 003: ID 04e8:329f Samsung Electronics Co., Ltd
Bus 001 Device 034: ID 18d1:d001 Google Inc.
Bus 002 Device 003: ID 1b1c:1b31 Corsair
Bus 002 Device 004: ID 08bb:2902 Texas Instruments Japan PCM2902 Audio Codec
[email protected] ~ $
My nexus 7 is attached and in recovery mode
Hope this helps. Please hit Thanks if it does
kodabmx

kodabmx said:
follow the instructions in the OP but instead make 99-android.rules: (it loads later after everything is initialized)
Click to expand...
Click to collapse
This worked for me. I also added the code for the Galaxy Nexus. After a quick reboot, I was able to execute both ADB and Fastboot commands without being in the same folder and no permission issues! Perfect

i am at a loss. I am on ubuntu 12.04 fully updated as of 8-22-2012. my 51 and 99 android.rules file looks like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="phillip" # 8GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="phillip" # 16GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="phillip" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="phillip" # Recovery
# fastboot protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="phillip"
I have tried it with and without the last subsystem. but no matter what i cant get my system to see my 7 in bootloader. in normal and recovery it works. any ideas?

ngc604 said:
i am at a loss. I am on ubuntu 12.04 fully updated as of 8-22-2012. my 51 and 99 android.rules file looks like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="phillip" # 8GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="phillip" # 16GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="phillip" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="phillip" # Recovery
# fastboot protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="phillip"
I have tried it with and without the last subsystem. but no matter what i cant get my system to see my 7 in bootloader. in normal and recovery it works. any ideas?
Click to expand...
Click to collapse
Try changing the mode for fastboot to 666. That might work.
Sent from my Nexus 7 using XDA Premium HD app

i figured it out. i was using the adb command and not the fastboot command. I forgot the 7 goes into fastboot right away.
just posting this in case someone else makes that same mistake.

Thanks for the follow-up on this. Here you say,
3. Replace what's in the folder with the the text in the file in github
Click to expand...
Click to collapse
Don't you mean "replace what is in this FILE?"
And that file was empty for me. Does that mean there is a problem? I still have insufficient permissions back on the original page:
adb devices
List of devices attached
???????????? no permissions
fastboot devices
gives no response, no error either.
fastboot
does give me the listing of fastboot usage and options.
UPDATE: (I also followed this guide: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/page__pid__981123__st__110#entry981123 , but had similar results as here)
Even though I could not complete this process, I do apparently have root! Google Play has SuperSU listed as an app "Up to date", ditto for Root Checker by joeykrim. And in Root Checker, when I click "Check root", "Verify Root Access", SuperSU does pop up and ask if it should be granted root, I say yes, and Root Checker says I have root.
I did manage to install the SuperSU app once or twice in my recent attempts. The first time I rebooted, I am sure I did not have root. Maybe the last two times I tried it, I did get root. About tablet says:
Code:
Android version
4.1.1
Kernel version
3.1.10-g52027f9
[email protected])
#1 SMP PREEMPT Thu Jun 28 16:19:26 PDT 2012
Build number
JRO03S
As far as root goes, am I all set? I don't care about using a different ROM or bootloader. I just want to have more control in customizing -- and using Titanium Backup -- and still get the updates when they roll out. Is it all good?

FadedLite said:
After writing my previous guide, i realized that a lot of people have had a fastboot problem when trying to flash cwm and adb problems while in cwm. After i flashed aosp, i realized that I lost recovery, and as i tried to reflash it, i had the problem as well.
Here's the fix.
1. Go to this github link and copy the text file.
2. Open up terminal and type in
sudo gedit /etc/udev/rules.d/51-android.rules​3. Replace what's in the folder with the the text in the file in github
4. Replace the text that says <username> with the username of your computer. (Don't erase the quotes!)
5. Find the line where it says "#adb protocol on the grouper (Nexus 7)"
6. Change the mode in the line under it to "0666"
It should look like this
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your user name here"​7. Save the file
8. Type in terminal
sudo service udev restart
sudo killall adb ​
Now fastboot and adb should be fixed!
Do a fastboot devices to check in bootloader and/or do a check for adb in cwm by adb devices.
If this helped at all, don't forget to click thanks and rate 5 stars!
Special thanks to ptspts on blogspot for the adb fix and johnmurrayvi on github for the rules file!
Click to expand...
Click to collapse
thanks for the tips,i already have this on my linux mahcine (like said the source.android.com under "configuring usb access")because it's requested if you want to build something,already did that some time ago for gnex.Anyway,also after did that times ago,i have little problems with fastboot and n7,adb works well instaed.i'll see what i can do.thanks!

This actually works on any device. All you have to do is replace the vendor and product id with that of the specific device.
I was having trouble seeing my HTC Evo 3D in fastboot (it was already set up with a device/product id for adb), so did a google search and landed on this page. All you have to do is type
Code:
lsusb
and see the vendor and product values (will be in the format 0abc:def1 - not the exact string but similar format). The first part is the vendor ID and the second part is the product ID. It will differ based on the mode your phone is in (bootloader, normal booted phone in dev debug mode, tethering etc). So you have to set up a line for each of these modes if you want to execute fastboot, adb etc type of commands on it.

chmod
might want to chmod the rules file after you save it and before restarting the udev service.. simple stuff can hang up the casual user.
Regards,
Rob
for me:
chmod a+rx /etc/udev/rules.d/70-persistant-android.rules
(still as root) [or add sudo in front]
a good page for reading up on udev stuff:
http://forums.team-nocturnal.com/sh...u-Linux-12-04-11-10-LTS-32bit-64-April-5-2012

Here is my 99-android.rules, pop this in, chmod a+rx it and restart udev and adb should give you a root shell no matter what mode your Nexus 7 is in. It also has defs for mtp. I used Linux Mint 14 with the android-tools-adb/android-tools-fastboot packages. It is important to have the mode 0600 entries, as they are vital for adb root access. Cheers!
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0600", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0600", OWNER="your username here"

HTC ONE XL an ADB problems under Ubuntu 12.04

Hi,
i've got a problem with my One XL during the correct installation of adb on my Unbuntu 12.04 system. When I start my phone in recovery mode adb detects my phone correct:
[email protected]:~$ adb devices
List of devices attached
HT29MW304980 recovery
Click to expand...
Click to collapse
But when I start my phone in the normal way adb doesn't detect it and the list of attached devices ist empty:
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ lsusb
Bus 001 Device 002: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
Bus 002 Device 042: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Bus 002 Device 003: ID 064e:a117 Suyin Corp.
Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
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
Click to expand...
Click to collapse
99-andrid.rules looks like this:
#Acer
SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0666"
#Dell
SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", SYSFS{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", SYSFS{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", SYSFS{idVendor}=="0482", MODE="0666"
#LG
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
#Pantech
SUBSYSTEM=="usb", SYSFS{idVendor}=="10A9", MODE="0666"
#Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", SYSFS{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666"
#ZTE
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"
Click to expand...
Click to collapse
Can anybody help me with this?

weltenspalter said:
Hi,
i've got a problem with my One XL during the correct installation of adb on my Unbuntu 12.04 system. When I start my phone in recovery mode adb detects my phone correct:
But when I start my phone in the normal way adb doesn't detect it and the list of attached devices ist empty:
99-andrid.rules looks like this:
Can anybody help me with this?
Click to expand...
Click to collapse
go into the settings -> developer options and ensure android debugging is turned on.

codeprimate said:
go into the settings -> developer options and ensure android debugging is turned on.
Click to expand...
Click to collapse
thx but android debugging is still turned on! so that cannot be the reason. Another suggestion?

weltenspalter said:
thx but android debugging is still turned on! so that cannot be the reason. Another suggestion?
Click to expand...
Click to collapse
sudo adb start-server

weltenspalter said:
Hi,
i've got a problem with my One XL during the correct installation of adb on my Unbuntu 12.04 system. When I start my phone in recovery mode adb detects my phone correct:
But when I start my phone in the normal way adb doesn't detect it and the list of attached devices ist empty:
99-andrid.rules looks like this:
Can anybody help me with this?
Click to expand...
Click to collapse
I had a similar problem after loading a rom that had usb debug checked by default. I unchecked it and rechecked it in the developer options and it fixed it for me. Not sure if its the same issue but worth a try.

Thats it. Now it works for me. THX
Sent from my MB632 using xda app-developers app

weltenspalter said:
Thats it. Now it works for me. THX
Click to expand...
Click to collapse
FWIW... this worked for me too... just had to uncheck then recheck "USB Debugging" in the "Developer Options" screen and it started working
Code:
$ adb devices
List of devices attached
HT2BDW300592 device
$ cat /etc/udev/rules.d/99-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Codename: precise
$ adb shell
[email protected]:/ # cat /system/build.prop | grep product | grep -i ev
ro.product.model=HTC EVARE_UL
ro.product.model=EvitareUL
ro.product.name=evitareul
ro.product.device=evitareul
# ro.build.product is obsolete; use ro.product.device
ro.build.product=evitareul

Hack: ACCENT A450 & Driver & ADB

Today I just bought a A450 Android Smartphone ACCENT because I want to work with on a project.
Why ACCENT A450:
ACCENT is a Moroccan brand
ACCENT is sponsoring the event SFD Casablanca
ACCENT A450: not a bad configuration
So the first thing I should do is to connect the smartphone and have access via ADB, but I have not found a driver for it either in the official website or in the web is why I created a Windows via Linux.
Download 51-android.rules Linux ACCENT A450
Download Windows driver for ACCENT A450
Steps with which I have created this driver:
I- Linux:
1- Before connecting our Smartphone:
Code:
@ ws ws-Pro: ~ $ lsusb
Bus 002 Device 003: ID 1bcf: 2805 Sunplus Innovation Technology Inc.
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 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
Bus 001 Device 003: ID 138a: 003C Validity Sensors, Inc. VFS471 Fingerprint Reader
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
2-I connected my Smartphone:
Code:
@ ws ws-Pro: ~ $ lsusb
Bus 002 Device 003: ID 1bcf: 2805 Sunplus Innovation Technology Inc.
Bus 002 Device 005: ID 24e3: 9025
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 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
Bus 001 Device 003: ID 138a: 003C Validity Sensors, Inc. VFS471 Fingerprint Reader
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
NB:
Bus 002 Device 005: ID 24e3: 9025
This is our "idVendor = 24e3" and "idProduct = 9025"
3- I created with a 51-right root file android.rules
Code:
@ ws ws-Pro: ~ $ sudo gedit -w /etc/udev/rules.d/51-android.rules
4- I added this line; that contains our idVendor:
Code:
SUBSYSTEM == "usb", ATTR {idVendor} == "24e3", MODE = "0666", GROUP = "plugdev"
5- I restarted the service:
Code:
sudo restart udev Service
6- I unplugged and then plugged in again (my Smartphone):
Code:
@ ws ws-Pro: ~ $ adb devices
* Daemon not running. starting it now on 5037 port *
* Daemon started successfully *
List of devices attached
8888888 offline
7- A message appears on our smartphone, we have to accept and voila:
Code:
@ ws ws-Pro: ~ $ adb devices
List of devices attached
8888888 device
II- Windows:
1- I downloaded USB_Driver Google:
See: http://developer.android.com/sdk/win-usb.html
2- Then I added our idVendor and idProduct:
Code:
;Accent A450
%SingleAdbInterface% = USB_Install, USB\VID_24e3&PID_9025
%CompositeAdbInterface% = USB_Install, USB\VID_24e3&PID_9025&MI_01
3- To install is easy:
Download the file and then manually install (video demonstration of a manual installation: https://www.youtube.com/watch?v=6IEdJZGQVI4 )
Enjoy

s2dar said:
...
Click to expand...
Click to collapse
Good tutorial but it doesn't work!
A friend of mine own an Accent A500 which lacks drivers.
He wants me to root it for him. We tried your method but Windows failed installing drivers.

Nonta72 said:
Good tutorial but it doesn't work!
A friend of mine own an Accent A500 which lacks drivers.
He wants me to root it for him. We tried your method but Windows failed installing drivers.
Click to expand...
Click to collapse
I think it should work if you make small changes because it is not the same device see Technical Specifications.
A question:
When you connect your A500 Focus on Ubuntu and you run the command "lsusb" What is new line as you see

s2dar said:
I think it should work if you make small changes because it is not the same device see Technical Specifications.
A question:
When you connect your A500 Focus on Ubuntu and you run the command "lsusb" What is new line as you see
Click to expand...
Click to collapse
I'm not on Ubuntu atm.
But lemme try it there.

Here's the screenshot.
Anyways, I got it rooted using Kingo Root App but I'd still love getting the drivers working.

Nonta72 said:
Here's the screenshot.
Anyways, I got it rooted using Kingo Root App but I'd still love getting the drivers working.
Click to expand...
Click to collapse
can you try that ?
Linux:
$ sudo gedit -w /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM == "usb", ATTR {idVendor} == "0a5c", MODE = "0666", GROUP = "plugdev"
$ sudo restart udev Service
$ adb devices
Windows :
Download Driver A500 Windows

s2dar said:
can you try that ?
Linux:
$ sudo gedit -w /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM == "usb", ATTR {idVendor} == "0a5c", MODE = "0666", GROUP = "plugdev"
$ sudo restart udev Service
$ adb devices
Windows :
Download Driver A500 Windows
Click to expand...
Click to collapse
Thanks,
But error is still persistant on Windows LOL

Strange behaviour of 51-android.rules file

I've been scratching head all evening trying to solve this, with no luck.
I've added the following lines to the /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="paul"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="paul"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0600", OWNER="paul"​When I run adb devices, it looks OK
List of devices attached
07c082820f1e64c0 device​And lsusb | grep Google finds the device (although it is identified as a Nexus 4 for some reason)
Bus 001 Device 105: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)​Finally, ls -Rl /dev/bus/usb/001/105 indicates
crw-rw----+ 1 paul audio 189, 104 Nov 11 00:13 /dev/bus/usb/001/105​
But, when I set the phone to bootloader mode by running adb reboot bootloader, and run fastboot devices, I get an empty line.
When I run fastboot flashall -w, I get
< waiting for device >​When I run lsusb, the Google line is no longer displayed.
Also, I see in the /var/log/syslog that the Google device is added when I boot the phone, and is removed when I change to fastboot mode.
On reboot:
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950990] usb 1-2: Product: AOSP on HammerHead
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950992] usb 1-2: Manufacturer: LGE
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950993] usb 1-2: SerialNumber: 07c082820f1e64c0
Nov 11 00:13:03 LENOVO-W541 colord: Device added: sysfs-LGE-AOSP_on_HammerHead​In fastboot:
Nov 11 00:21:08 LENOVO-W541 kernel: [ 3293.100855] usb 1-2: USB disconnect, device number 105
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-(null)
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-(null)
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-LGE-AOSP_on_HammerHead​
Can anyone help? I can't even do something as basic as flashing a new image to the phone.
Paul

Try
Code:
sudo fastboot devices

Found the problem (I think). Seems to be a stupid USB cable problem.
At work, with phone in fastboot/bootloader mode:
$ lsusb | grep Google
Bus 001 Device 098: ID 18d1:4ee0 Google Inc.​There seems to be a bug, because in normal mode, the same command gives:
Bus 001 Device 100: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)​At home, in fastboot mode this command gives nothing, just an empty line.
Similarly, at work, in fastboot mode:
$ fastboot devices
07c082820f1e64c0 fastboot​The same command at home gives:
<waiting for device>​
All with the same phone and laptop, just different cables.

After creating rules, did you reload them? either by rebooting or using udevadm?
What distro are you on?

beekay201 said:
After creating rules, did you reload them? either by rebooting or using udevadm?
What distro are you on?
Click to expand...
Click to collapse
beekay,
Yes, I had reloaded the rules, using sudo /etc/init.d/udev restart
Ubuntu 14.04. problem solved, as I indicated above.