ADB on Archos 101 - Gen8 Android Development

Has anyone connect their archos 101 to adb successfully?

As long as you have the SDK already installed, follow this (I originally posted this over at the Archosfans forum). I assume you're requesting this for Windows.
----------------
Go to the usb_driver folder (In your SDK root).
Next navigate to the android_winusb.inf file.
Open that file up, and immediately above the [Google.NTamd64] line, and the [USB_Install] line, add the following:
Code:
;Archos 101
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
Then plug your Archos in, and if it asks for drivers, point it to that file. If it doesn't ask for drivers, then navigate to your device manager and find the device with a yellow triangle with an exclamation point. Uninstall, and then when it finds it again, point it toward that file.
Done.
----------------
Hopefully that will do it for you.

Hi Harfainx,
I followed the steps you mentioned by some how it doesn't work. When calling "adb devices" nothing is showing up.
Deos it matter if my A101 is still in 2.1?

Doesn't matter, I've done that on both 2.1 and 2.2.
Are you ensuring that your system is actually updating the driver to the new file?
If so, do a system restart. That should fix your problem.

In device manager, I can see Android Phone -> Anchos G8 Composite ADB Interface. So I guess drivers should be properly updated right?
I have restarted both the PC and tablet both but still can't see the device in adb

Linux
Anybody know how to get adb working on a linux box?

Harfainx said:
As long as you have the SDK already installed, follow this (I originally posted this over at the Archosfans forum). I assume you're requesting this for Windows.
----------------
Go to the usb_driver folder (In your SDK root).
Next navigate to the android_winusb.inf file.
Open that file up, and immediately above the [Google.NTamd64] line, and the [USB_Install] line, add the following:
Code:
;Archos 101
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
Then plug your Archos in, and if it asks for drivers, point it to that file. If it doesn't ask for drivers, then navigate to your device manager and find the device with a yellow triangle with an exclamation point. Uninstall, and then when it finds it again, point it toward that file.
Done.
----------------
Hopefully that will do it for you.
Click to expand...
Click to collapse
Dont forget to modifiy the ".android/adb_usb.ini" (found in your user account folder) file in a terminal/command prompt
Code:
echo "0x0e79" >~/.android/adb_usb.ini
or on Windows:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"

supagforce said:
Dont forget to modifiy the ".android/adb_usb.ini" (found in your user account folder) file in a terminal/command prompt
Code:
echo "0x0e79" >~/.android/adb_usb.ini
or on Windows:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Click to expand...
Click to collapse
Well, my fix is for Windows, which you don't have to add anything to any other folders.
For Linux it's a bit more difficult. For Windows you only have to add those lines into the one folder (at least that worked for many users on the Archosfans forum since about two weeks ago).

(Rom)
anyone know if there has been a rom put out yet for this thing, and anyone give me some tweaks i could possibly do.
installed market and thats really it, read alot about the z4root and theres still some issues with it, so i dont really want to try it out yet

Harfainx said:
Well, my fix is for Windows, which you don't have to add anything to any other folders.
For Linux it's a bit more difficult. For Windows you only have to add those lines into the one folder (at least that worked for many users on the Archosfans forum since about two weeks ago).
Click to expand...
Click to collapse
mmm er ok
http://forum.archosfans.com/viewtopic.php?f=65&t=37386
see bottom post
http://forum.archosfans.com/viewtopic.php?f=63&t=41755&p=284338
From the archos website
First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:
* Go to the Android SDK page and download the latest SDK for your operating system. http://developer.android.com/sdk/index.html
* For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.http://developer.android.com/sdk/win-usb.html
* Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
o Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
o Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
o Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
* For Linux users only: You need to add a udev rule if ADB only works as root:
o Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
o Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)

Thanks! I will try this soon. Looks promising.

supagforce said:
mmm er
Click to expand...
Click to collapse
It seems like some people need to add the lines to the .android folder, and some people don't. Not really sure why it works for some people by just modifying the .inf in the SDK.
http://forum.archosfans.com/viewtopic.php?f=74&t=42495
With an A101, and an A70 at least that's all I needed on Windows 32-bit and 64-bit versions.
I never edited anything in any .android folder until I put ADB on Ubuntu.
I see that some people needed to add those lines it, but some people haven't had to do that. Obviously it's best to do it if you're having problems, I'm not arguing with you there.
I wonder why some people need that line and some people don't... Maybe it has to do with having the Gen7 (A5IT) ADB drivers installed from before.

Harfainx said:
I see that some people needed to add those lines it, but some people haven't had to do that. Obviously it's best to do it if you're having problems, I'm not arguing with you there.
I wonder why some people need that line and some people don't... Maybe it has to do with having the Gen7 (A5IT) ADB drivers installed from before.
Click to expand...
Click to collapse
Im not arguing either, i also noticed this too that it works for some. I wonder if it has anything to do with the OS version ie (Windows 7 / XP / linux) ??

Harfainx said:
As long as you have the SDK already installed, follow this (I originally posted this over at the Archosfans forum). I assume you're requesting this for Windows.
----------------
Go to the usb_driver folder (In your SDK root).
Next navigate to the android_winusb.inf file.
Open that file up, and immediately above the [Google.NTamd64] line, and the [USB_Install] line, add the following:
Code:
;Archos 101
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
Then plug your Archos in, and if it asks for drivers, point it to that file. If it doesn't ask for drivers, then navigate to your device manager and find the device with a yellow triangle with an exclamation point. Uninstall, and then when it finds it again, point it toward that file.
Done.
----------------
Hopefully that will do it for you.
Click to expand...
Click to collapse
I followed your instructions here and on archos fans, in cmd I enter adb devices, doesn't list it but says devices listed. Using esbdview it shows a driver and a serial number. Any other suggestions, and yes I rebooted. Didn't help.

Did you try editing the file in the .android folder as outlined by Supagforce further up in this thread? Some people are able to have it work without editing that file, but others have to.

Finally ADB is working.
I did it with a combination of instruction from Harfainx and some other from archosfans forum.
Here are the steps:
1. Go to the usb_driver folder (In your SDK root).
2. Next navigate to the android_winusb.inf file.
3. Open that file up, and immediately above the [Google.NTamd64] line, and the [USB_Install] line, add the following:
Code:
;Archos 101
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
4. Then plug your Archos in, and if it asks for drivers, point it to that file. If it doesn't ask for drivers, then navigate to your device manager and find the device with a yellow triangle with an exclamation point. Uninstall, and then when it finds it again, point it toward that file.
5. start run %userprofile%
find folder called .android
Create/Edit adb_usb.ini, add 0x0E79 inside. Save. Restart ADB service.
After the last step, the A101 shows up with the command "adb devices"

guoloong said:
Finally ADB is working.
I did it with a combination of instruction from Harfainx and some other from archosfans forum.
Here are the steps:
1. Go to the usb_driver folder (In your SDK root).
2. Next navigate to the android_winusb.inf file.
3. Open that file up, and immediately above the [Google.NTamd64] line, and the [USB_Install] line, add the following:
Code:
;Archos 101
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
4. Then plug your Archos in, and if it asks for drivers, point it to that file. If it doesn't ask for drivers, then navigate to your device manager and find the device with a yellow triangle with an exclamation point. Uninstall, and then when it finds it again, point it toward that file.
5. start run %userprofile%
find folder called .android
Create/Edit adb_usb.ini, add 0x0E79 inside. Save. Restart ADB service.
After the last step, the A101 shows up with the command "adb devices"
Click to expand...
Click to collapse
When I attempt to edit the adb_usb.ini all I get is "# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e79 ."

You should put "0x0e79"
in a new line

Anybody tried adb wireless app yet? Probably easier to go with that than medling with the usb drivers for windows.

adb wireless with temproot works like a charm

Related

windows 7 root NC

this from rad131304 not me, thank you
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (www dot cygwin dot com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
1. make sure your NC is disconnected from you computer
2. make sure your SD card is mounted on your computer (readable/browsable in explorer)
3. Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
4. download nooter at http //www dot mediafire dot com/?hugt8uxcfffpdvg
5. extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
6. Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
7. Select "Disk Management" under storage
8. note the drive letter of the SD card and the disk number
9. Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
10. At the prompt, type (WOQ): "mount //./<f>: /dev/sd<c>"
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
11. press enter - there should be no output
12. at the prompt, type (WOQ): "dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>"
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
13. remove the sd card from the computer and plug it into the NC
14. power down the NC (hold power button for 15 seconds)
15. connect the NC to the computer
16. Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
17. Wait for 15 seconds after the recognition
18. power down the NC
19. remove SD card ***
20. Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
21. Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
22. save the file and close
23. find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
24. add (WOQ) "0x2080" on its own line
25. power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
26. Go To: Start > Devices and Printers
27. Right-click on Nook and select properties
28. Select the hardware tab
29. If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 38
30. Click on "Nook"
31. Select Properties
32. Click Change Settings (may require UAC elevation)
33. Click update driver
34. Select "browse for driver software on your computer"
35. Browse to the android-sdk/usb_driver folder
36. click next
37. You should be done; skip to 47 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
38. If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
39. Select Properties
40. Click Change Settings (may require UAC elevation)
41. Select the Driver Tab
42. Click Uninstall
43. Click OK
44. Disconnect NC
45. Reconnect NC
46. You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
47. Go To: start > run > cmd
48. type (WOQ): "cd <path_to_android_sdk>\tools"
49. type (WOQ): "adb.exe kill-server"
You should get something like:
* server not running *
50. type (WOQ): "adb.exe remount"
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
51. You are done configuring to sideload
From here you should be able to sideload from ADB.
by rad131304
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
I believe it was mentioned in a previous post that if you did a factory reset (power off completely, then hold power, nook button and vol up) that it would reset the Nook back to non rooted factory defaults. Can anyone else confirm this?
HeroHTC said:
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
Click to expand...
Click to collapse
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
believe this was done on win 64, some buttons are located in or below menu bar, some will depend on launcher.
I also wanted to mention this
http://forum.xda-developers.com/showpost.php?p=9517050&postcount=863
NOTE: I have not even opened my nook box yet, its still sealed but I am getting ready. Just waiting on an email solution.
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
The back and menu buttons are soft-buttons. The nook for some reason hides them by default in a bunch of apps.
sudermatt said:
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
Click to expand...
Click to collapse
IIRC, somebody said that in the big thread, too.
oakleyrdc said:
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
It could be hidden (so you'll have to change the hidden files and folders setting), or installed in another user directory (like Admin).
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
I did mine on Win 64bit using winimage. Everything is working fine.
rad131304 said:
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
Click to expand...
Click to collapse
XP
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
plus 1 for XP
So once your rooted, do you need to do anything special to install apk files that you download from dropbox? Is superuser ready?
i cant find the android_winusb file in the windows XP version of the android SDK. is there a different one that does the same?
EDIT: it appears the sdk is not split between versions of windows
im going to reinstall the sdk and see maybe if i accidently deleted it at some point
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
Very little changes; the only thing I can tell you off the top of my head is that
C:\users\<username>\.android\
Becomes
C:\documents and settings\<username>\.android\
Also, I don't know where, besides device manager, that you could locate the nook like you do in devices and printers - it may show up in my computer, also in scanners and cameras in the control panel - you can always right click a drive, select properties, select the hardware tab, select the b&n storage device, click properties, select the driver tab and uninstall from there....
HTH
EDIT: To delete the NC through device manager:
start > run > compmgmt.msc
browse to Device Manager
Expand Universal Serial Bus Controllers
Select USB Mass Storage Device (there may be multiple)
Right-Click and select "properties"
select the details tab
in the dropdown, select "Hardware Ids" - if this says "USB\VID_2080&...." then this is the NC
click ok
right Click again and select uninstall
disconnect NC from computer
reconnect NC to computer
NC re-finds all drivers, including ADB
start > run > cmd
cd <android-sdk-dir>\tools
adb.exe remount
Fixed instructions!
that's what I get for writing this crap at 1 in the AM ... I left out two INSANELY important steps at step 11.
SORRY!!!!
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (http://www.cygwin.com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes or a code block, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
make sure your NC is disconnected from you computer
make sure your SD card is mounted on your computer (readable/browsable in explorer)
Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
download nooter at http://www.mediafire.com/?hugt8uxcfffpdvg
extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
Select "Disk Management" under storage
note the drive letter of the SD card and the disk number
Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
At the prompt, type:
Code:
mount //./<f>: /dev/sd<c>
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
press enter - there should be no output
REMOVE SD CARD FROM PC
INSERT SD CARD INTO PC
at the prompt, type:
Code:
dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
Click to expand...
Click to collapse
IF THIS COMPLETES ALMOST IMMEDIATELY, YOU PROBABLY HAVE AN ERROR
remove the sd card from the computer and plug it into the NC
power down the NC (hold power button for 15 seconds)
connect the NC to the computer
Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
Wait for 15 seconds after the recognition
power down the NC
remove SD card ***
Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
Code:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
save the file and close
find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
add (WOQ) "0x2080" on its own line
power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
Go To: Start > Devices and Printers
Right-click on Nook and select properties
Select the hardware tab
If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 40
Click on "Nook"
Select Properties
Click Change Settings (may require UAC elevation)
Click update driver
Select "browse for driver software on your computer"
Browse to the android-sdk/usb_driver folder
click next
You should be done; skip to 49 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
Select Properties
Click Change Settings (may require UAC elevation)
Select the Driver Tab
Click Uninstall
Click OK
Disconnect NC
Reconnect NC
You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
Go To: start > run > cmd
type:
Code:
cd <path_to_android_sdk>\tools
./adb.exe kill-server
You should get something like:
* server not running *
Click to expand...
Click to collapse
if adb.exe is not in tools (or tools does not exist), try:
Code:
cd <path_to_android_sdk>\platform-tools
./adb.exe kill-server
type:
Code:
./adb.exe remount
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
Click to expand...
Click to collapse
You are done configuring to sideload
From here you should be able to sideload from ADB.
To sideload an app, simply do the following:
Code:
./adb.exe install <app_name>
Thanks Rad!
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
When you updated the SDK, did you install the USB drivers also? If you did, that file should be in whatever directory you installed the SDK in under the usb_driver subdirectory.
cabbieBot said:
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
Click to expand...
Click to collapse
I'm an idiot, I was certain the USB Drivers were installed. Done and done now, sheesh what a waste of time!
now to hunt for adb_usb which is being a pain to find too. Has anyone found adb_usb on XP?
I can see the folder C:\documents and settings\<username>\.android\ but theres two folders in there for AVD and AndroidDesktopNotifier. Maybe if someone can upload the adb_usb file I can just throw it in the folder and cross my fingers?

[Q] ADB on Windows 7 64 bits

Hi
have you a solution to use ADB with Windows 7 64 bits
i use this tips
# For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.
# Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
* Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
but in the list of devices with adb devices : the list is empty !
Hi
have you added
;Archos 70
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
in the file android_winusb.inf of directory <android_sdk>/usb_driver?
It has to be added in the correct OS section [Google.NTamd64] or [Google.NTx86] - or to be sure to get it right, do it in in both sections.
Hi,
I've finally my Archos 70 working with ADB, but hard to work !
I first install the USB drivers from Archos, with no luck (installed fine, but adb devices give me no answer). Have then installed the USB drivers from Google. Have then a ! yellow on a USB disk.
I thenput more recent date and version in inf of Archos drivers, and make an update (if you don't change date and version, Windows don't want to change).
And after a reboot, it works !
I have also do the add to do in adb_usb.ini but not sure that is usefull or not...
Dunno if you have to do all of that, but work for me.
in the both section i have this
; Archos
%USERPROFILE%\usb_drivers\adb_usb.ini
%USB\VID_0E79&PID_1361.SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1361
%USB\VID_0E79&PID_1361.CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1361&MI_01
%USB\VID_0E79&PID_1400.SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1400
%USB\VID_0E79&PID_1400.CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1400&MI_01
%USB\VID_0E79&PID_1411.SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%USB\VID_0E79&PID_1411.CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
but for this line
%USERPROFILE%\usb_drivers\adb_usb.ini
what is the good position
This line
%USERPROFILE%\usb_drivers\adb_usb.ini
isn't in my android_winusb.inf at all.
I have also installed the Google USB Driver, not that from Archos.
Here is my android_winusb.inf file:
I've got the best solution at all:
Because I can't use the micro usb port while having the fullsize usb port in use (e.g. for dvb-t) I found the "ADB over Wifi" app in the market, that is great.
type # adb connect IPORT
and it connects to your android device
@findusBS : i use your file bit impossible to install
@chulri : good idea , i will be searching and testing
@chulri : oups only on root Archos
great on the archos rooted is good !!!
No adb_usb.ini file
cajl said:
Hi
have you a solution to use ADB with Windows 7 64 bits
i use this tips
# For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp support.archos tructions how to install the driver are available at USB Driver for Windows site on Android Developers.
# Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
* Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
but in the list of devices with adb devices : the list is empty !
Click to expand...
Click to collapse
Hi, I am trying to install ARCHOS usb driver for windows 7 x64. The problem is when i download the driver from the above website, it wont install. I cannot find the adb_usb.ini file. Although i have installed google driver as well as changed the android_winusb.ini. i think the problem is that the driver is only for 32 bit os and not for 64 bit system. Please help me out as i am stuck for my uni project.

[Q] Sony Tablet S ADB support

Has anybody got a Sony Tablet S being recognised by adb?
It seems to be blocked :-(
And yes, I have done all the usual enable USB debugging etc...
I can not use it for development :-(
---------- Post added at 12:56 PM ---------- Previous post was at 12:06 PM ----------
Managed to sort it myself
you need to cd to your .android folder (on a mac, this is ~/.android) and then type
echo 0x054c > adb_usb.ini
Where 0x054c is the vendor id for Sony (I got that by looking at the attached evices in the 'About this mac' preferences)
Now adb sees the device - woohoo
would this apply if i just wanted to use it to transfer music and such? I am not incredibly savy with coding but i tried to enable debugging and all that. I am justnot sure whats the problem.
No, the Android File Transfer program still works without this
Good to know it can be used to dev on. Anyone have any information on how to send data out using the IR blaster, I dont think there is support for it in the native android libraries from what I can see?
The following procedure has confirmed that ubuntu 11.04.
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Kaz Taguchi said:
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Click to expand...
Click to collapse
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Found a way on Windows!
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Bojanglez said:
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Click to expand...
Click to collapse
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file.
Works lime a charm now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
CaptainJack87 said:
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Click to expand...
Click to collapse
Done loading packages.
Preparing to install archives
Downloading Google USB Driver package, revision 4
File not found: C:\Program Files (x86)\Android\android-sdk\temp\usb_driver_r04-windows.zip (Access is denied)
Done. Nothing was installed.
I tried downloading and installing
(Can't post links)Download: Android USB Drivers - Original (Firmware 1.0)
But when I try to install the drivers for the tablet through device manager it says:
The folder you specified doesn't contain compatible software... ...Windows for x64-based systems.
Apparently this driver is only for x86. But after googling "download Google USB Driver Package" that's all I can find.
Got it...
At least I was able to "enable it" through the USB port,
thanks to this exercise in frustration.
Alas no root screen cap still didn't work.
It flashes wildly and does nothing.
Anyone happen to know the proper command line in system variables for win 7 for adb should be?
I haven't used adb in forever, and I think alot of peoples issues with adb is in the fact they cannot use it outside of the android/android-sdk/platform-tools directory. As in you can just type adb shell, adb start-server, adb kill-server from the root dir. I had it set up before, but with a new comp now, and I forgot what it was before.
whats going wrong
i cant seem to get the device driver on my adb at all. no matter what i do i cant get the usb driver sorted. this is where i get stuck"
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
home directory???? every time i try this from home directory i get nothing.
this is my problem.... i dont have this file or entry. what is the entry?????? o notpad doc??,
adb_usb.ini file was missing the 0x54c entry! <<< what is this. a screen shot goes a loooong way.
Adb was simple with my x10 and sgs2 but man this is giving me the ****s.
can someone please post a few simple screenshots of what directory is supposed to be where please?
---------- Post added at 08:39 AM ---------- Previous post was at 08:21 AM ----------
what does this mean?
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file
?????????
I've created an automated ADB driver installer for the Sony tablets.
No more messy, time-consuming SDK install.
http://forum.xda-developers.com/showthread.php?t=1488822
Official Sony instructions
Looks like Sony has posted official instructions for setting up ADB with the Tablet S:
esupport.sony.com/US/perl/support-info.pl?info_id=878
After following their instructions I still had to go to Device Manager, choose to Update the driver for my tablet, and point it to the SDK/usb_driver folder. After that it works great.
debug
Hey guys i have installed the android sdk and the sony s drivers from the official site as dreadengineer posted. but after run the adb devices command i was unable to saw my device.
After that i tried the automated installations that BluechipJ posted, but the result was the same i cannot see the devices neither on eclipse or adb devices command.
i want to debug my application on this device but i could not access it. Can someone help me.
I have a windows 7 x64 OS. i'm able to debug on htc phone and also on the super slower emulator

[Guide] Enabling ADB protocol through USB for Sony Tablet S [Win | OS X | Linux]

How do I connect Sony Tablet with adb protocol through USB?
Windows (Windows XP, Vista and 7)
Please install SDK and setup USB as described in Google Android SDK site
http://developer.android.com/sdk/installing.html
http://developer.android.com/sdk/win-usb.html
In order to connect Sony Tablet S and P, please follow below procedure.
Turn on "USB debugging" in Sony Tablet S and P
Put following device descriptions into each sections [Google.NTx86] and [Google.NTamd64] in extras\google\usb_driver\android_winusb.inf.
;SONY Sony Tablet P
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_04D2&MI_01
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
--------------------------------------------------------------------------
Linux (Ubuntu 11.04)
Please install SDK and setup USB as described in Google Android SDK site
http://developer.android.com/sdk/installing.html
http://developer.android.com/guide/d...tml#setting-up
In order to connect Sony Tablet S and P, please follow below procedure.
Turn on "USB debugging" in Sony Tablet S and P
Please utilize 0x54c as USB Vendor ID on creating new udev rule file(51-android.rules).
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from shell prompt.
echo "0x54c" >> $HOME/.android/adb_usb.ini
-------------------------------------------------------------------------------
Mac (Mac OS X 10.6.8)
Please install SDK and setup USB as described in Google Android SDK site
http://developer.android.com/sdk/installing.html
http://developer.android.com/guide/d...tml#setting-up
In order to connect Sony Tablet S and P, please follow below procedure.
Turn on "USB debugging" in Sony Tablet S and P
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from shell prompt.
echo "0x54c" >> $HOME/.android/adb_usb.ini
works!
but a info i had to add a >> ; before the SONY Sony Tablet
dont know if this usually known or not
XotusBlack said:
works!
but a info i had to add a >> ; before the SONY Sony Tablet
dont know if this usually known or not
Click to expand...
Click to collapse
Yes you are right. I corrected it. Thanx
so maybe fastboot in recovery could be achieved with that kind of method? i'm going to buy sony s, then i try to help btw someone said that the tablet is recognized with recovery but there were no drivers found? maybe the drivers for fastboot should be modified to install correctly?
--edit:
ordered. will get one tomorrow
I dont see the .android folder under
/data/data/berserker.android.apps.sshdroid/home
even I did ls -la
Waht is the path? Can someone give me the path? Thanks,
---------- Post added at 07:47 AM ---------- Previous post was at 07:36 AM ----------
ok since path did not exist, i created .android directory and corresponding file. and added 0x54c. However still it is not recognized by "adb devices" command. any hint? Thanks,
Any idea on this command line guys?
http://ng8.upanh.com/b1.s20.d3/2e58c2a9423d34b41b4f80e9defaa244_38687348.soc.jpg
http://ng8.upanh.com/b3.s20.d3/d50fb3dde4f9fde1302b4bea7452290d_38687348.soc.120x1.jpg
Well I have followed the Window steps here and have got the driver to load ok but adb refuses to list the device in when I run "adb devices"? Any one any clues? I've uninstalled the driver and tried different USB ports, restarted the adb server... but no joy :-(
---------- Post added at 08:02 PM ---------- Previous post was at 07:38 PM ----------
Working! I checked again and the adb_usb.ini file was missing the 0x54c entry!
Can't list the tab into "adb devices".
0x54c is in adb_usb.ini (In c:/Users/<name>/.android/
I'm not so sure if I did the android_winusb.inf thing right though, as Xotusblack mentioned something, and I can't really put my finger on where to place the >> ;.
I'd be glad to help for dev testing purposes though :]
---------- Post added at 12:21 AM ---------- Previous post was at 12:02 AM ----------
I followed this guide, which seemed to work: http://forum.xda-developers.com/showthread.php?p=17624941
Only difference is that instead of the Sony Tablet P and S directly, it's now supporting every device with a Tegra 2 CPU.
That, and I specifically pointed the failed driver to android_winusb.inf.
Other then that, awaiting a dev god
got it working! thanks,
http://www.kb.sony.com/selfservice/documentLink.do?externalId=C1024692
That's very nice, but what does it give us?
No root, no CWM, no S-Off.
Maine_Coon said:
That's very nice, but what does it give us?
No root, no CWM, no S-Off.
Click to expand...
Click to collapse
Is this true?
Sent from my PC36100
yeah but now those that don't know how to do this sort of thing can set them self up to help test possible roots etc
DreadPirateDan said:
yeah but now those that don't know how to do this sort of thing can set them self up to help test possible roots etc
Click to expand...
Click to collapse
Makes sense I guess, yes.
DooMloRD, all eyes are on you!
I can't install the driver on Windows 7 64-bit.
It wants 64-bit driver.
Maine_Coon said:
I can't install the driver on Windows 7 64-bit.
It wants 64-bit driver.
Click to expand...
Click to collapse
Windows7, Windows Vista and Windows XP -
Install the Google Android SDK and USB driver as described at the following Google Android SDK sites:
Installing the Google Android SDK - http://developer.android.com/sdk/installing.html
Google USB Driver - http://developer.android.com/sdk/win-usb.html
Once the Google Android SDK and Google USB Driver are installed, open the android_winsub.inf file and copy the the following descriptions into the [Google.NTx86] and [Google.NTamd64] sections of the extras\google\usb_driver\android_winusb.inf file:
;SONY Sony Tablet P
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_04D2&MI_01
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
Work fine on my windows seven x64..!.
graffy64 said:
Windows7, Windows Vista and Windows XP -
Install the Google Android SDK and USB driver as described at the following Google Android SDK sites:
Installing the Google Android SDK - http://developer.android.com/sdk/installing.html
Google USB Driver - http://developer.android.com/sdk/win-usb.html
Once the Google Android SDK and Google USB Driver are installed, open the android_winsub.inf file and copy the the following descriptions into the [Google.NTx86] and [Google.NTamd64] sections of the extras\google\usb_driver\android_winusb.inf file:
;SONY Sony Tablet P
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_04D2&MI_01
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
Work fine on my windows seven x64..!.
Click to expand...
Click to collapse
Works fine now too.
Don't know what my problem was.
Maine_Coon said:
Works fine now too.
Don't know what my problem was.
Click to expand...
Click to collapse
me either! but I'm happy for you that it works now !.
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
This one has me baffled.I'm a noob with this stuff.I did the rest without any problems (I think) ,just not sure which way to insert this into the cmd prompt.My file is in C:\Users\Vinny\android.
Cheers Vinny
Vinny1967 said:
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
This one has me baffled.I'm a noob with this stuff.I did the rest without any problems (I think) ,just not sure which way to insert this into the cmd prompt.My file is in C:\Users\Vinny\android.
Cheers Vinny
Click to expand...
Click to collapse
Yes in C:\Users\Vinny\.android folder should be a file:
adb_usb.ini
open this file or create if it not extsist as a text file and write
0x54c
ito the file. Save it
restart your pc and you should have adb.

How to install adb-driver for Archos 70b

If you want to develop apps with Eclipse on the Archos tablet you must have access to the device via adb.
There is a nice description how to install the adb-driver on an archos 101.
http://forum.xda-developers.com/showthread.php?t=866418
But the Archos 70b has a different PID.
I did it with the following settings
first step:
Copy the directory "google-usb_driver" from you android-sdk to a location on c:
Locate the file android_winusb.inf
Add as last line in [Google.NTx86]
; Arcos 70b Reader
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1409
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1409&MI_01
this lines must be located before the next block
[Google.NTamd64]
The Vendor ID and the PID are taken from properties in the device manager.
Connect the tablet with usb and the normal driver installation procedure will take place. Select the google-usb_driver directory and install from there.
The system should set a recovery-point and install the adb-driver
if it was successfull you shoud see a new symbol in the device manager.
second step:
search in the directory "Documents and settings" for a directory ".android".
modify or create the file adb_usb.ini.
It should contain the following information
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0X0E79
Restart the adb (or the computer) and you should see the device in Eclipse in the ddms perspective.

Categories

Resources