I could mount my Gnex under Archlinux using gvfs-gphoto2, but I tried it with the Acer 700 and still have no luck. Have somebody successfully mount the sdcard under Linux using any mtp-file transfer?
In Windows it was no problem, but normally I boot Windows only if I have to, so it would be nice, if someone has a workaround for me
Anyone? I`m now on gentoo and have the same problem. Gnex is mounting fine and Acer doesn`t.
I want to fix the problem now and will collect all the information I need to sort this one out!
Here`s the dmesg output:
[14170.686330] usb 1-1.1: New USB device found, idVendor=0502, idProduct=3376
[14170.686334] usb 1-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=x
[14170.686336] usb 1-1.1: Product: Acer Iconia Tab A700
[14170.686339] usb 1-1.1: Manufacturer: Acer
[14170.686341] usb 1-1.1: SerialNumber: xxxxxxxxxxxx
lsb output:
gentoo-htpc ~ # lsusb
Bus 001 Device 006: ID 0502:3376 Acer, Inc.
Maybe an udev rule will fix it.
I will search further. If anyone have an idea to fix it, then please post it here in this thread. Big thx
Edit: Ok I`ve made a progress.
I emerged mtpfs, created a udev rule, which looks like this:
/etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
and add the following line to the /etc/fstab:
mtpfs /media/a700 fuse user,noauto,allow_other 0 0
Now I could see the A700 in nautilus but the Internal storage is empty... Hmmmm
Any suggestions?
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.
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?
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
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 deviceAnd 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_HammerHeadIn 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 fastbootThe 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.