Related
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
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.
I'm having the hardest problems with my sgt usb drivers being install . I have windows 7 and every time I install them and re-boot and than plug in my tab nothing happens it all ways gives an error( Unknown device) any help will be appreciated. YES I've look and search everywhere.
did installing/re-installing kies worked? Did you install android sdk? Running the sdk manager and install google usb driver package> samsung.
AND
try pasting the para into the inf file (under x86 for 32bit and x64 for 64bit system) in pathway:
C:\Program Files\Android\android-sdk\extras\google\usb_driver\android_winusb.inf
as
[Google.NTx86] // for 32 bit system or x64 for 64bit system
//start copying from here!
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
these three steps will install all possible drivers you will ever need!
If you mean to use with nvflash (APX) etc...
Grab the NVidia boot-recovery driver from here:
http://djmcnz.batteryboss.org/stuff/nvmobileboot.rar
Uninstall the driver from device manager, then update using this drivers.
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.
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.