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
Hi,
I'm trying to upgrade my Nexus S I9020 to ICS -- well, actually,
now I'm just trying to get my phone back. I backed up my phone
before I started, but now I can't even mount my phone on my
computer (Linux) to do a restore.
On power-on my phone immediately goes to fastboot mode, saying
> fastboot mode - no boot or recovery image
I see four options: reboot bootloader, reboot, recovery, and
power off. I go to recovery and I get to a screen with
ClockworkMod Recovery v5.0.2.0 at the bottom and a set of
options. At this point, if I connect my phone to the computer
with a USB cord, I can see it with 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:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 002: ID 1ea7:0002
> Bus 004 Device 002: ID 056a:0011 Wacom Co., Ltd Graphire 2 4x5
> Bus 001 Device 003: ID 18d1:4e22 Google Inc. Nexus S (debug)
but fdisk -l doesn't see anything. Now I execute "mount USB
storage" on the phone and Nautilus (linux file manager) pops up
with a mount at /media/CB59-1402, but there's nothing in it. Now
fdisk -l shows
$ sudo fdisk -l
...
> Disk /dev/sdb: 14.3 GB, 14314094080 bytes
> 64 heads, 32 sectors/track, 13650 cylinders, total 27957215 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
So the computer found some mass storage there. Now I try to
create a file there,
$ sudo touch /media/CB59-1402/test.txt
> touch: cannot touch `/media/CB59-1402/test.txt': Input/output error
so the filesystem or partitioning or something seems to be
borked. The filesystem is vfat (right?) so I try to fix it with
$ sudo fsck -t vfat /dev/sdb
> fsck from util-linux 2.21
> dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
> open: No medium found
I have the Android SDK installed, so I look to see if adb can see
the phone,
$ adb devices
> List of devices attached
> 3430CA26FCB200EC recovery
OK. Try
$ adb shell
It returns immediately. Try fastboot,
$ fastboot devices
Nothing.
--
I'm really stumped. I got here because the web page for the ROM
said to reformat everything from CMR. I reformatted /sdcard,
/system, /cache, /data, and /boot.
Help!
Thanks,
-Rod
fastboot only works in the bootloader i believe, not recovery. adb may not be working because Android is no longer installed (/system partition). To save the trouble next time, when switching between very different ROMs, all that needs to be done is a data/factory reset, formatting /system and formatting /boot. SDCard is optional, i never do it (data/factory reset gets rid of the .android_secure folder already).
I've not had this problem in linux with being unable to get into the SDCard though, this is what you want to sort out so you can copy a ROM .zip and flash through CWM. Everything besides this is how it should be. Try unmounting it and mounting it manually, something along these lines should work fine:
# mkdir /media/nexus
# mount -t auto /dev/sdb /media/nexus
Now try and open up /media/nexus with nautilus. Good luck.
I have a problem with my g2x that can't be turned up, it stuck when I flash the NVflash "G2X_V21E_00_NVFlash". I did get through once then it's error again. Then I followed the same instruction but I have no idea why I can't pass through. I hope people can help me with this and tell me how or experience that they had it and solved it. Anyway, thank before the hand, I'm really appreciated your help.
Here the message I got when I tried to flash the NVFlash with G2X_V21E_00_NVFlash.
"C:\Users\Free\Desktop\Download\Software\Android\LG G2X\G2X_V21E_00_NVFlash>.\nvf
lash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --set
bct --odmdata 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --bl
fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20c143e0b5d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 888548/888548 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize"
Did you try doing it with the battery out and holding the volume buttons down until it gets past the bootloader?
Sent from my LG-P999
I did but it never go pass through it. It just stop at the " waiting for bootloader to initialize ". I tired dozen of time but it never works.
When I use nvflash for flashing clockworkmod, I know it's not identical to what you are doing but it should be close enough, I use these instructions and it has always worked:
===== STEP 1 - Flashing ClockworkMod Recovery 5.0.2.0:
download the 5.0.2.0 clockworkmod recovery image
place recovery-clockwork-5.0.2.0-p999.img in C:\G2x\NVFlash
Unplug everything
remove the battery
Hold Vol Up/Down (and keep them held)
Insert USB cable
open command prompt
execute the following commands:
Code:
navigate to folder with nvflash.exe in it at command prompt, for me cd g2x\nvflash
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-5.0.2.0-p999.img
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". You can let go of the volume buttons at this point. Once the files are sent and the program is finished running in the command window, you CAN just pull the USB cord or be safe and just wait a few extra minutes, however it will still say "upgrading.
Click to expand...
Click to collapse
Hope that helps somehow....
kuhla said:
When I use nvflash for flashing clockworkmod, I know it's not identical to what you are doing but it should be close enough, I use these instructions and it has always worked:
Hope that helps somehow....
Click to expand...
Click to collapse
I have no idea it's still not working any thank for your replying.
Maybe try re installing the LG and APX drivers?
Sent from my LG-P999
Hi Everyone,
At the moment, I cannot get my LG G2X to boot into Cyanogen Mod. I cannot get it to boot into recovery mode. I cannot get it to do anything but sit at the second LG logo. This is a problem.
If I allow it to boot with no special button-pressing, it will get to the second LG logo, and stall there until the battery runs out. If I hold the VOLUME DOWN and POWER buttons, it will get as far as the first (white) LG logo and stall there (holding VOLUME DOWN and POWER for a full 60 seconds).
History:
A few weeks ago, I had flashed my G2X and installed CyanogenMod 7 (specifically 7.2.0) from here: http://download.cyanogenmod.com/?type=stable&device=p999. I accomplished this through the excellent One-Click NvFlasher ClockWorkMod provided by TGA_Gunnman (found here: http://forum.xda-developers.com/showthread.php?t=1056847). Once in a while, I would have to clear the caches after a reboot, but that was my biggest problem, and one I was prepared to live with. Until now.
Things I've tried:
Most fixes start with reflashing CWM. I did that, using the aforementioned One-Click NvFlasher ClockWorkMod tool. It stalls as follows:
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20824360c4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
-------------------------------------------------------------------------------------
...and won't do anything else.
So, for whatever reasons, it will not send CWM-5020.img. To check, I tried nvflash.exe directly. Same general result. I tried with a different file (recovery-clockwork-5.0.2.0-p999.img), same result. I also tried the advice here: http://forum.xda-developers.com/showthread.php?t=1590523&highlight=bricked+help and tried to wipe out my partitions. While that tool runs successfully, it does not change the results with One-Click NvFlasher ClockWorkMod
Summary:
Can't boot. Can't boot into recovery. Can't flash the ROM.
Any ideas? Anyone?
Thanks!
I forgot to add: when I unplug from the one-click updater, I get the following error message:
Code:
sending file: CWM-5020.img
- 65536/3563520 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
===============================================================
===============================================================
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
For when my partitions are messed up
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
djvoleur said:
For when my partitions are messed up
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, djvoleur, but when I try that, I get this:
Code:
.\nvflash.exe
--bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --odm
data 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --bl fastboot.
bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20824360c4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 888548/888548 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: UDA
creating partition: EB4
creating partition: UDB
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x42008 (0x19042008) flags: 0
So it seems that this doesn't help. I scanned through the thread and didn't see anything that seemed like it might address this issue.
It may be driver related. Reinstall drivers then follow the instructions to resurrect your phone.
Core Memory said:
It may be driver related. Reinstall drivers then follow the instructions to resurrect your phone.
Click to expand...
Click to collapse
Would you recommend reinstalling both the LG USB drivers and the ATX drivers for nVidia? (I'm probably going to do both anyway.)
I've forced a reinstall of the NVIDIA USB Boot-recovery driver, using the same files included in the one-click recovery tool. After that, I attempted to run the tool and had the same failure listed above (command failure: partition download failed). For laughs, I tried djvoleur's solution as well, and got the same error again. So it doesn't seem to be a driver issue.
When you do the NVFlash recovery, did you take out the battery, hold the up and down volume buttons in, while holding the buttons in plug in the usb cable, while holding the buttons in run the recovery until it is completed.
Just for ****s, try flashing twrp. I also have another idea, but I can't get it set-up tonight.
Sent from my LG-P999 using xda premium
Core Memory said:
When you do the NVFlash recovery, did you take out the battery, hold the up and down volume buttons in, while holding the buttons in plug in the usb cable, while holding the buttons in run the recovery until it is completed.
Click to expand...
Click to collapse
Yes. The battery was out the whole time. Held the buttons down, plugged in the USB cable, ran recovery, recovery stalls at 65536 bytes. Held it for about five minutes, just to make sure.
Волк said:
Just for ****s, try flashing twrp. I also have another idea, but I can't get it set-up tonight.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Same result as each of the others: stalls at 65536 bytes sent. I don't think it's an issue with any of the actual recovery mods, at this point. I think it's something wrong with getting data onto my phone, perhaps?
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Core Memory said:
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Click to expand...
Click to collapse
Tried this. First tried the second link (the all in one with the offline web server). That didn't work because the zipfile with the webserver and other software had a virus which specifically infected the web server.
Followed the directions in the first post, then. These seem to presume that you can get to USB debugging mode (which I can't, because the phone won't boot). Got as far as Step 3 in that post. When I click on "Upgrade Start" I should get a pop-up for "Select Country & Language". I do not. Instead, it starts the LG Mobile Support Tool directly. (I should mention at this point that I'm on WIndows 7, if it matters). The updater checks the connection with the phone, and finds an acceptable connection. Since it was supposed to go into the Updater anyway, I hit "Start Updating". After a while, this fails with some sort of connection problem with the phone. I've tried re-running the LG Updater under several conditions (in Upgrade mode, not in Upgrade mode, etc.). No luck.
Doesn't seem like this is a solution I can get to work. Should I try something else?
The virus warning is false. Disconnect from the internet and/or turn off your wireless connection then run it. Also, if it stalls, let it wait.
If it doesn't continue within 10 minutes, try it again.
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
Also, I made sure that all of the applications in the substitute web-server update package were allowed to run as administrator before I ran the script. If that doesn't work, try running the apps individually without the script in the order they're required to be initiated which is in the instructions that come with that package.
Core Memory said:
The virus warning is false. Disconnect from the internet and/or turn off your wireless connection then run it. Also, if it stalls, let it wait.
If it doesn't continue within 10 minutes, try it again.
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
Also, I made sure that all of the applications in the substitute web-server update package were allowed to run as administrator before I ran the script. If that doesn't work, try running the apps individually without the script in the order they're required to be initiated which is in the instructions that come with that package.
Click to expand...
Click to collapse
I'm having exactly the same problem as that person right now. Using the offline update, I got up to "Normal MTK Upgrade start" but then the program crashed right afterwards. It also doesn't help that the phone keeps on rebooting. For the online update, I can get up to 32% before the phone reboots and I have to restart the update process.
mbamg said:
I'm having exactly the same problem as that person right now. Using the offline update, I got up to "Normal MTK Upgrade start" but then the program crashed right afterwards. It also doesn't help that the phone keeps on rebooting. For the online update, I can get up to 32% before the phone reboots and I have to restart the update process.
Click to expand...
Click to collapse
If it got to 32%, it has installed the baseband, that gets installed first then the Android. Try doing a restore/recovery of just Android that's compatible with the baseband.
Have you tried running the flash with the battery in? I know all the instructions say take the battery out, but im having similar issues with my phone, and once the phone is recognized in Device manager in APX mode, insert the battery, then run the flash. That seemed to work for me.
Core Memory said:
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Click to expand...
Click to collapse
Nothing will work in this Case i try all most everything. I thnk 99% Partition or Flash Chip is Damaged
See Reports:
While try with KDZ File
Trying to Flash Recovery
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
Recovery Stock
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
Phone Information
Code:
Nvflash started
rcm version 0X20001
System Information:
[COLOR="Red"] [B]chip name: unknown[/B][/COLOR]
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
Rad Flash
Code:
[R&D Test Tools Log File]
00:54:52 : Start fn_StartUpgrade
00:54:52 : Extract kdz file
00:55:01 : kdz decrypt Success
00:55:05 : Extract file Success.
00:55:05 : LGMobileDL Load.
00:55:05 : Port = -1
00:55:05 : Connection check start.
00:55:05 : Port(or Device) Not Found!
00:55:07 : Finish All test
So to Flash with KDZ ect u need phone on Recovery mode and phone will not steep into recovery mode with vol - + Power
All we have is boot Recovery mode and phone hang on SW Upgrade Please Wait
I Try to Format partition manually via NVFlash but same thing its hang
Best Regards from me i am giving up after 2 days working on it, For me its simply Hardware Problem
In my experience when that happened to me.... It was my firewall/virus scanner. Try disabling those before attempting another flash.
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