Goodmornig everyone..!
I just bought an Archos 80 G9 Turbo 16GB and I cannot connect it with my computer that runs Windows 7 64bit
When I plug it, it is detected as an Unknown Device (error code 43) and nothing is mounted.. (but tablet is in "slow charge")
In an old Win XP computer is working good, this made me think it's not completely tablet's fault..
here what I've tried, deeply searching on internet:
-Downloaded ADB android Drivers (in Archos site, on internet, various sources), forced installation of them, problem come out: Drivers are not for a 64 bit Os
-Uninstalled Kies, LG Pc suite and rebooted after every change..nothing changed
-Unactivate and reactivate after reboot Windows Media Player 12..no change
-Changed Usb Mode in tablet from MTP to PTP.. nothing changed
-Installed a lot of USB apps in Google Play and tried changing values..no change
-Upgraded tablet from GingerBread to ICS, deeply wiped and restored several times, and in every configuration, I allways had same results..
-Changed USB cable, several of them tested..and guess?? Nothing..eheh
-Tried shouting at it, tried kissing and asking for his forgiveness..but nothing
I'm stuck on Stock! i cannot upgrade it with XDA custom, I can only connect to pc via FTP server....!
Any Clues?!?!
Thank You to all!
1. To root and to enable SDE menu you need only adb driver
2. You can transfer archos.ext4.update files using FTP from pc to tablet
3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works"
You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download.
This worked for me on Windows 7 Ultimate.
Ooops overread something... forget it!!!
Have you checked for the correct MTP driver package...
Regards,
scholbert
gen_scheisskopf said:
1. To root and to enable SDE menu you need only adb driver
2. You can transfer archos.ext4.update files using FTP from pc to tablet
3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works"
Click to expand...
Click to collapse
Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS)
Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it..
xcen3x said:
You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download.
This worked for me on Windows 7 Ultimate.
Click to expand...
Click to collapse
Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing..
scholbert said:
Ooops overread something... forget it!!!
Have you checked for the correct MTP driver package...
Regards,
scholbert
Click to expand...
Click to collapse
Dowloaded and istalled a few from windows... the problem is, if it would be an MTP problem, I should not have it in PTP mode... I suppose...
EDIT: tried disabling Integrity Checks for non signed drivers with these string in cmd:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
nothing changed
indyjones83 said:
Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS)
Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it..
Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing..
Click to expand...
Click to collapse
For Gen9 you need Archos modified driver
gen_scheisskopf said:
For Gen9 you need Archos modified driver
Click to expand...
Click to collapse
These are the first one I tried.. From their site.. Not working.. Thankyou!
I wrote them in Contact and support in that site, copying and pasting the same I wrote here, they answered me, two days later.. Excited in what solution they could give me,from the heights of their knowledge, I suddenly opened and the answers was:
Please write the email in English.
Are they kidding me? This makes me suppose they have not even tried in reading it.. Well.. 1000 thanks for you and you support..!
Sent from my Optimus 2X using XDA
Second reply from Archos, this time they read it, but only first few lines..
their reply is:
"We invite you to connect the device to a 32 bits system and then to check if the Archos is seen by the pc."
Already done, and it's working with that (WIN XP)
Did you try to install manually the MTP driver from the device manager of the PC ?
YES.
any new clue from here?
Thankyou!
Try this
Sent from my ARCHOS 80G9 using XDA
1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port?
I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot.
pittnuma said:
1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port?
I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot.
Click to expand...
Click to collapse
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
indyjones83 said:
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
Click to expand...
Click to collapse
Did you try the link in my previous post? I'm running win7 64 bit and it worked for me!
Maybe just try adding the file in your USERPROFILE directory first!
Sent from my HTC Sensation using XDA
bobjbain said:
Did you try the link in my previous post? I'm running win7 64 bit and it worked for me!
Maybe just try adding the file in your USERPROFILE directory first!
Sent from my HTC Sensation using XDA
Click to expand...
Click to collapse
Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43).
I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean?
and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system...
It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG....
but it works with win xp...! I tried again..!
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
indyjones83 said:
Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43).
I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean?
and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system...
It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG....
but it works with win xp...! I tried again..!
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
Click to expand...
Click to collapse
OK try this :-
Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them).
Attache your G9 then go into device manager.
Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled.
Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point.
Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file.
If you get unsigned warnings click on the "trust me" or whatever it says.
Driver should now be installed.
The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist).
You can test adb connectivity by using "adb devices" from the command line.
Hope this helps
indyjones83 said:
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
Click to expand...
Click to collapse
I think this is probably because your USB cable only has 2 internal cables, not 4.
IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power.
If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless.
Are you using the cable you got with the G9??
bobjbain said:
I think this is probably because your USB cable only has 2 internal cables, not 4.
IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power.
If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless.
Are you using the cable you got with the G9??
Click to expand...
Click to collapse
Yes, I'm using the cable i got with the g9.. I could have a dual cable (the one they give to you with an external hdd), but it's mini usb, not micro...
bobjbain said:
OK try this :-
Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them).
Attache your G9 then go into device manager.
Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled.
Click to expand...
Click to collapse
And this is the problem.. I don't have any driver to uninstall, as if my device is an "Unknown Device" no service, no adb no mpt recognized.. only an "unknown device".. even with new drivers, the only driver it lets me install are Samsung drivers.. but obiously doesn't work!
I now tried in installing it as this samsung, just to have something to uninstall...
bobjbain said:
Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point.
Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file.
If you get unsigned warnings click on the "trust me" or whatever it says.
Driver should now be installed.
The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist).
You can test adb connectivity by using "adb devices" from the command line.
Hope this helps
Click to expand...
Click to collapse
You are really amazing, archos is not caring at all..
Before I tried your firs suggestion in USERDEVICE and for a minute it found my device as Error 10 and not Error 43 (unknown device)... and that's the only moment my pc saw the tablet...
Thankyou!!
indyjones83 said:
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
Click to expand...
Click to collapse
I too have run across this problem--AFTER woprking for 6 months with it under ADB just fine. Not just my work computer, home devices as well. Did you ever get this fixed?
Hi, I have a Scroll Excel tablet and was recently trying to flash CMW5 onto it using a recovery from the scroll forums, however in the command prompt whenever I type in the command ("adb push install-recovery.sh /data/" in case that helps) it says the daemon isn't running, then it starts the daemon, then it says "Error: device not found.
I've checked everything, I have correctly navigated to the folder which holds the recovery, I am entering the recovery name correctly, I do have the Google USB Drivers etc.. installed, the device is plugged in (and the computer knows it is, it detects it) but the prompt doesn't recognize the device.
There is one thing though, whenever I plug it in the computer tells me the device is not recognized, but it at least acknowledges that the device is there. Am I missing any drivers on my tablet's side or what? Thanks
Also, I attached a file of what the prompt tells me below v
I do not have this tablet so I cannot give you an exact answer. However, I would try uninstalling and reinstalling the drivers and restarting your pc. Also try a different usb port.
As stated in the post above, I would check my Drivers. I would also suggest checking your USB Cable. Make sure that it is good. Is your SDK Tools up to date ? BTW that seems like an odd path for your platform-tools folder.
prboy1969 said:
As stated in the post above, I would check my Drivers. I would also suggest checking your USB Cable. Make sure that it is good. Is your SDK Tools up to date ? BTW that seems like an odd path for your platform-tools folder.
Click to expand...
Click to collapse
It can't be the USB cable, I've tried 2 or 3. Also, yes. I updated the SDK tools yesterday. And I know it's an odd path, but I'm a bit OCD about keeping things in folders.
However, about the drivers, the computer says it doesn't recognize the device. And when it scans for the drivers it doesn't find anything to download. Regardless, Storage Options are willing to take a look at it for me (how nice, even with a technically void warranty.) Thanks for your help anyway.
I would definitely recommend re-installing the drivers. Then try again.
TEAM MiK
MikROMs Since 3/13/11
Im running on cm9.1. First time I plugged my phone in to my laptop, it said unable "android" driver unable to install. Im able to access the sd cards from windows though.
I opened device manager to try to update/install the driver. nothing has worked so far. I tried to install it from the android sdk and it didnt work. I installed the official samsung usb driver and kies and they didnt work.
what else can i try??
or should this really be a priblem??
Maybe you can flash another rom.
For example,you can try CM10.1 or samsung official rom.
I'm using cm10.1 and it doesn't have your problem.
Sent from my GT-I9100G using xda premium
well, I like to hold out on cm10.1 until the stable release which might not even happen at all for the s2.
any other solution you can think of??
how's the cm10.1 nightlies anyway?? good enough for everyday use?
Never mind I fixed it. I followed this instruction I found:
Connect phone
Run USBDeview as Administrator
Sort by Serial Number
Select all devices with Serial Number starting HT
Uninstall selected devices
Disconnect/reconnect phone
Windows will try, and fail, to install device, ignore that and...
Install driver via Device Manager:
Open Device Manager (Start->My Computer, right click->Manage->Device Manager)
Under Other, you should see a device with a yellow warning called ADB or Android Phone; right click -> Update driver software...
Click Browse my computer for driver software
Click Let me pick from a list of device drivers on my computer
Select Show all devices, click Next
Click Have disk...
Browse to android sdk install directory and find the usb_driver directory (mine is in extras\google)
Select android_winusb.inf and click OK
Select Android Composite ADB Interface and click Next
When the Update Driver Warning appears click Yes
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
Hello , well im sorry to bother you guys but i just cant seem to connect through ADB using any Cyanogenmod rom but adb seems to work on stock roms. Ive tried everything reinstalling drivers and using different cables but nothing seems to work , could anyone help me out?
Try this and see what the outcome is good luck
All credit goes to oc3rulz for finding this.
http://forum.xda-developers.com/show...&postcount=814
Originally Posted by oc3rulz
I have CM7 installed and I just got Windows to recognize the SDCARD via USB Mounting!!!!
Now again I am using Windows 7 so the steps are almost exactly the same. I literally just changed the device to a USB Mass Storage device and it worked!
Lol after trying so many drivers and it being the generic driver makes me angry. Here's what I did.
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your My HTC (should be the second one Android USB Device), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose USB Mass Storage Device
Then it takes some time to think and viola! All working! However we are not DONE!
EDIT: So the next step I did after experienced issues remounting after unplugging the phone. I have change the MTP to ADB Testing Interface and things seem to be mounting everytime. Rebooted phone and PC, both worked again so I think this may be a working solution.
Now go to MTP.
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your MTP (should be under Unknown Devices), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose Google Inc. and the Driver is ADB Testing Interface.
ENJOY!