Hi, I am looking for usb driver for viewpad 7 for using adb. Can anybody provide and link or pointers from where can I get the same.
Thanks,
Dang
There's no "real" driver...
Just connect your Viewpad 7 to your PC.
A window pops up where you can select "setup.exe" - select it.
Then a few drivers get installed (perhaps a restart is necessary)
Seems like the Viewpad 7 has a virtual drive which gets mounted when connecting it to a PC - it's shown up as virtual CD-drive for me under Windows XP and Windows 7.
PS: The drivers are also located on the virtual CD-drive in a directory.
Make sure you run the file from the virtual optical drive if you have autorun disabled.
Sent from my HTC Sensation Z710e using XDA App
plug youre viewpad in now youre pc see een cdrom right click and open use that adb.exe that one works
How to remove the virtual drive
I have already installed the drivers from this drive, but whenever I connect the device, the virtual CD-ROM drive still appears. Anyone know how to get rid of it?
LEGEND383 said:
I have already installed the drivers from this drive, but whenever I connect the device, the virtual CD-ROM drive still appears. Anyone know how to get rid of it?
Click to expand...
Click to collapse
I always open the Sync tool then (do nothing, no sync or so).
That's the only way my Windows 7 PC recognizes the tablet via ADB.
I have been doing that as well, but it's just annoying to have this extra drive that is of no use and just sits there taking up a drive letter.
Stupid question, ive never used adb, but does this mean i dont have to download it because already cames on that virtual drive, and so i only need to install it ?
Now i manage to install the drivers.
I go to the command line in windows and write :
adb usb
adb devices, and get this:
List of devices attached
FM6120420141
Then i do,
adb shell, and nothing happens.
Ive tried several commands and nothing works, what m i doing wrong here ?
Hi guys, i tried another pc with windows xp and everything worked perfect at first try. Thans for the help VPAD7, nice chating.
Bye all the other losers.
Hi VPAD7
Can you share the solution for "adb devices" not working on windows7? I am facing he same problem with my Viewpad7.
Thanks for your contribution to the forum.
---------- Post added at 12:45 AM ---------- Previous post was at 12:39 AM ----------
VPAD7 said:
Now i manage to install the drivers.
Could you share how did you manage to get drivers installed on windows7? I am also seeing same issue with viewpad7. I am trying to root it.
Click to expand...
Click to collapse
Solved driver issue on windows7
Hi,
I was facing issue in connecting viewpad7 to windows7 machine. Even synchronization steps were failing. Manuall attempt to run "adb.exe devices" were unable to detect the device. Here is my steps that I did for rooting the device with SuperOnceClick(SOC)1.7-
1. Initially driver were not detected/installed on windows7. Only CDROM displaying setup was displayed and clicking "Setup.exe" is not installing drivers. Copy the All files on computer and say folder name is "v7Setup".
2. To Install drivers, Connect Tablet/Phone to windows7, select "USB Tethering in tablet" (This is needed to detect devices by Windows7), in windows7:check the "Device Manager", it can show "Others" two devices: HSUSB & RNDIS. Update the driver for both devices from "v7setup/RUT/*" folders.
3. Now start SOC1.7 and select "rageagainstthecage" and click root. It may wait at "Running rageagainstthecage..." message in SOC log window. Then disconnect the Tablet after waiting for 1-2 minute and connect again after beep sound from windows7. Here, again I needed to install the drivers as mentioned in step2. SOC1.7 will proceed and finally in poup message, it will ask to "push su" files. And Done.
Related
I am new to the Android platform so please excuse any silliness on my part…
Below are the steps I took to successfully allow my Vizio Tablet (VTAB108) to connect via USB using the generic Google ADB driver as Vizio does not include ADB access for the tablet.
History:
I am trying to Root my tablet and from what I read throughout the forum, the easiest steps to root a tablet is using the SuperOneClick method.
Since SuperOneClick requires ADB access and the Vizio does not include the ADB driver (and the generic Google) do not work out of the box I was at a loss to how I would run SuperOne Click.
This article are the steps I took to get ADB access working with Windows 7 x64 and the Vizio Tablet.
I am hoping my steps here can further lead to root access for this tablet.
As an FYI, I was still unsuccessful in getting SuperOneclick to completely run after following these steps, but maybe someone has an alternate method of rooting now that ADB access is available? /me crosses fingers
It would stop at Step #6 at which time I would disconnect and reconnect the tablet. It would contine to step #8 but then finally fail. If anyone has an alternative to SuperOneClick, I would gladly try it.
IMPORTANT:
The instructions below assume you have already put your Tablet into USB debugging mode.
The instructions below assume you are running Windows 7 x64. If you are running x32 versions of your OS, modify the below settings as apporopriate for your OS[/B].
1. Download and install the Google Android SDK.
(Being this is my first post, I cannot post a URL so google the following topic exactly and click the first link):
what-is-adb-and-how-to-install-it-android
2. When you get to the USB driver install you will have to manually modify your android_winusb.inf settings file to allow Windows to recognize your Vizio Tablet using the generic Google ADB-USB driver.
3. Find the "usb_driver" folder in your sdk directory. (Mine was: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver).
4. Right-click "android_winusb.inf" and open it with notepad or your favorite text editor.
Under the [Google.NTamd64] section, paste the following:
Code:
;Vizio Tablet
%SingleAdbInterface% = USB_Install, USB\VID_0489&PID_E040&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0489&PID_E040&REV_0227&MI_01
then, open a command prompt and type the following:
Code:
echo 0x489 >> "%USERPROFILE%\.android\adb_usb.ini"
5. Right-Click the unknown device in Windows Device Manager (Under Other devices) and manually install the driver for your Tablet.
NOTE: Originally my tablet connected to the computer and installed the regular Windows 7 Mass Storage driver. I had to remove this driver before I could see the device listed under "Other Devices". Follow these instructions if you need to remove your generic Mass Storage driver:
Code:
A. Unplug all removable devices (USB drives, Thumb Drives, SD Cards, Etc...) but leave the Android phone plugged in.
B. Open Windows Device Manager.
C. Select "Universal Serial Bus Controllers"
D. Select USB Mass Storage Device.
IMPORTANT: Click on the details tab and select "Compatible Ids" under the Property drop-down. You should see three items listed under Value. If not, you are looking at the wrong Mass Storage Controller.
E. Select Uninstall Driver
F. Close the window.
G. Right-Click your computer name at the top of device manager and select "Scan for Hardware Changes".
H. Your new "Android Phone USB device" with a Yellow Exlamation mark! will appear under Other Devices.
I. Click on the "Android Phone USB device"
J. Select "Update driver software"
J. Select "Browse my computer for driver doftware"
K. Browse for the location that you have unzipped the android_usb_windows ( Mine is: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver )
6. Now test to make sure you can access your device in USB Debug mode:
Type the following from a command prompt:
adb kill-server
adb devices
You should see your device serial number at the command prompt and in Windows Device Manager if everything worked.
drivers
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
USB Drivers Not Installing
[email protected] said:
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
Click to expand...
Click to collapse
I grabbed those drivers a couple of days ago and could not get Win7 or WinXP to install them with the vtab1008.
I can use adb to interface with the vtab008 (using Linux and Win7), but GingerBreak and SimpleOneClick (which uses GingerBreak) are unable to root the vtab1008.
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Agreed
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
This is my thinking EXACTLY!
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
Yes, I agree. If there's no root, the tablet is not worth it.
The drivers worked for me.
I downloaded the drivers from the Vizio site and when I plugged the VTAB into my computer I manually installed the driver. I just used adb to grab a bunch of screenshots.
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
You can get to recovery mode by holding down both volume buttons and the power button. Details
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Mark0266 said:
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Click to expand...
Click to collapse
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
marvin02 said:
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
Click to expand...
Click to collapse
Thats the problem the prompt never comes up. Running Windows 7
Well I got the driver for adb to install but it still will not show up when I do adb devices
Bootloader?
the.joeba said:
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
Click to expand...
Click to collapse
Did you actually get into the bootloader? adb reboot bootloader simply reboots the device for me.
So whats with gingerbreak? No love with it? I thought this thing was rooted already prior to shipping? Hmmm. My bro just ordered one for me and I am curious about getting it rooted. Lets get this thing rooted and overclocked and get it some love. Also, whats the word on honeycomb on this beast? anything?....
Mark0266 said:
Well I got the driver for adb to install but it still will not show up when I do adb devices
Click to expand...
Click to collapse
Same here.
Rooting help
I have some coding knowledge, but have never worked on rooting a device. I did not pay for mine, so if anyone has references to some info I can look at about obtaining root then I will work on mine without fear of bricking it.
I have been at this for weeks, to no avail.. tried changing params in Gingerbreak, tried running it under every condition possible, and the only thing I haven't tried is changing how GingerBreak is using the /sdcard/ mount point, as that's where the internal memory is mounted to.. It's a pretty odd move to make, and I don't like having my true sdcard in /sdcard/external. what a crock :/
This tablet has to have a way to be rooted, I tried an older version of gingerbreak 1.1 just kept running, never failed, but didn't root the tablet just kept running, like it was gonna root the tablet, kinda weird, I do know that the bootloader is not locked down, my wife works for vizio, the company gave there employees a tablet for free
Hey folks,
got a "little" problem with my device. I tried to copy some videos of it and it just won't work.
---
I connect my device to my PC and these things happen ...
Windows 7 x64:
Nothing.
Windows 7 x64 with Kies installed:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Windows 7 x64 with Kies installed and device in mass storage mode:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Ubuntu 11.10 x64:
Nothing.
Ubuntu 11.10 x64 and device in mass storage mode:
I see some files on my device, but when trying to open them, I only get some errors ... the real problem here, when I disconnect the USB cable (or unmount) then there are no files on my device left ... everything has been moved to "lost.dir" and I can´t open them from there, not even from my phone.
---
I tried to connect with USB debugging enabled, but it would work.
Any ideas?
/Edit 1:
The only way to copy stuff over to my computer is by using Kies Air ... and it takes ages for HD videos.
/Edit 2: THE SOLUTIONS LOL :-D
1. I had to connect my device via another USB slot
2. when USB debugging is enabled, it still wouldn't mount; then I installed this app https://market.android.com/details?id=com.jrtstudio.automount and now everything works just fine
freakin.ro said:
Hey folks,
got a "little" problem with my device. I tried to copy some videos of it and it just won't work.
---
I connect my device to my PC and these things happen ...
Windows 7 x64:
Nothing.
Windows 7 x64 with Kies installed:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Windows 7 x64 with Kies installed and device in mass storage mode:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Ubuntu 11.10 x64:
Nothing.
Ubuntu 11.10 x64 and device in mass storage mode:
I see some files on my device, but when trying to open them, I only get some errors ... the real problem here, when I disconnect the USB cable (or unmount) then there are no files on my device left ... everything has been moved to "lost.dir" and I can´t open them from there, not even from my phone.
---
I tried to connect with USB debugging enabled, but it would work.
Any ideas?
/Edit 1:
The only way to copy stuff over to my computer is by using Kies Air ... and it takes ages for HD videos.
Click to expand...
Click to collapse
1) Using a Rom? If yes check in thread if it, if this problem is already known.
2) Tried different USB-Slots?
3) Connect phone, search in device manager for the device and uninstall the drivers.
Then un- later replug the phone and wait if all drivers got installed again.
CHEERS ;-)
Sent from my Galaxy S2 - I9100 with SensatioN Rom!
Lost DIr is for error files that have been corrupted .
jje
... connected to another USB port and it really works :-D it´s on the same controller ... so now I´m really confused lol.
I´m running Samsung's stock 2.3.4. I´ll try to get ADB working later and if it works i´ll close this, thanks very much
freakin.ro said:
... connected to another USB port and it really works :-D it´s on the same controller ... so now I´m really confused lol.
I´m running Samsung's stock 2.3.4. I´ll try to get ADB working later and if it works i´ll close this, thanks very much
Click to expand...
Click to collapse
You're welcome, mate ;-)
Sent from my Galaxy S2 - I9100 with SensatioN Rom!
JJEgan said:
Lost DIr is for error files that have been corrupted .
jje
Click to expand...
Click to collapse
I know, is there a way to restore this files?
so, just tried another app:
https://market.android.com/details?id=com.jrtstudio.automount
it mounts my device correctly even when USB debugging is enabled :-D
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?
Anybody else got problems with connecting to the PC with the USB cable?
What "problems" are you having?
The Windows Explorer does not start, though there is the sound when connecting the USB. Tried uninstalling the driver and letting the system reinstall upon connecting, but still cannot see Nexus 9 in Windows explorer. In Linux get the the notification and clicking on the "open with File Manager" gives a quick error message - too quick to read. So I am wondering if anyone got this problem??
Sent from my Nexus 9 using Tapatalk
Same here
I updated my SDK files, but that didn't seem to work either. It does show up as a camera when I change from MTP, so I just started sideloading apps, files, and books to the picture folder, then using a file explorer to move them to the correct folder.
+chuckie59 So I am not alone with this problem! Have used AirDroid to copy things over.
Sent from my Nexus 9 using Tapatalk
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Same for me. Only ptp working. Google USB ADB drivers instaled
mkygod said:
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Click to expand...
Click to collapse
You'll never get it to show up as a driver letter. Android gave up on mass storage a couple of versions ago.
Sent from my Nexus 9 using XDA Free mobile app
If you are on W8.1 then you may have the "ACER Composite ADB Interface" - A Microsoft upgrade fault.
A search for "ACER Composite ADB Interface remove error delete" should give plenty of hits. Here's the first post from http://forums.androidcentral.com/google-nexus-7-tablet-2012/362325-nexus-7-not-recognized-computer-2.html :
Would you happen to know if any Acer drivers are installed on your computer? Here recently there was a Windows Update that installed the wrong driver and made it so that I had the exact same problems as you're having. Here's how I fixed it.
Go To> Control Panel>Hardware and Devices>Device Manager. In Device manager look for something along the lines of "ACER Composite ADB Interface", at least in my case I had the wrong ADB interface installed. You'll know if you have the wrong drivers if you go to Devices and Printers and right click your Nexus 7 and go to it's properties. It should be under the hardware tab where it lists it. If it doesn't just say Nexus 7 then follow these instructions. Once you find it in the Device Manager (once again in my case it was the ACER Composite ADB Interface causing the issue) right click and and uninstall it. There should be a dialogue box that pops up right after which will ask you if you want to delete the drivers. Check this box and proceed with the uninstall. After successfully uninstalling the drivers plug in or unlplug and plug back in your Nexus 7. It should show up now with the correct drivers installed.
Thanks, but I am on Windows 7. Driver is ClockworkMod Ver 7.0.0.1 dated 2012-08-27, which Windows reports as up to date (?). Works for PTP but not MTP.
I have had problems with other devices including the nexus 5 and nexus 10 to connect over mtp. Previously i used the nexus root toolkit which has some wizard to guide you to install proper drivers for mtp and adb. The toolkit is yet to support nexus 9 but you can still use the wizard to uninstall the old drivers and reinstall correct ones
Updating sdk. Uninstall and installing again driver did the trick for me
SORTED!! (sort of) Updated sdk and uninstalled and installed the driver again, but it did not do the trick for me. Gave up on Win7.
Instead had a go on XP. Initially everything the same. Noticed two choices of compatible hardware given: "Google Nexus ADB Interface" (the one I had installed already) and "USB Composite Device". Tried the latter one, and yes it did install. In the device manager it turns up as "Portable Device/Nexus 9" (and not as "Android Phone/Google Nexus ADB Interface" as before).
In Windows Explorer it is shown as "Nexus 9/Internal storage" with all the directories, and actually when inserting the USB I do get auto start. By the way, was having the USB debugging disabled. The driver is Microsoft dated 2006-02-22 version 5.2.5326.4762 - which is not what I would have expected. But it works!
Will try to get something similar to work on Windows 7
SORTED! Yes also Win 7 - and it was easy. Uninstalled the driver, plugged in the USB and it installed! Also got the auto start to choose action. It now turns up as "Portable Devices/Nexus 9" in the device manager and as "Nexus 9/Internal storage/etc" in Windows Explorer. The driver is now Microsoft ver 6.1.7600.16385 dated 2006-06-21. Strange. As long as it is working!
I was unable to find help elsewhere, so I was recommended to come here. No rooting, hacking, reprogramming, or anything else. Just a basic connection problem.
I recently bought a new Solid-State hard drive, and re-installed Windows 7 on it. Everything is great, and it's fully updated.
My problem is that while my LG Optimus G E980 phone will charge via the USB cable, I can't "open" it in My Computer, to transfer pictures, music, etc.
I have tried downloading the driver from LG's Website (LGMobileDriver_WHQL_Ver_4.1.1), but when I run it, I get the following message:
"The Microsoft MTP driver is not found on your system. Please install Windows Media Format Feature Pack using Download Link for your media device to work correctly."
It then provided me with a link to download this. However, when I do that and run the update, I get told the update is not applicable to my computer.
Whether I try to install this update or not, it doesn't matter, because the driver installation tells me it was installed successfully. However, judging by the icon in my Taskbar with the red/white "X" and the fact that my phone still won't connect, it hasn't.
Yes, my phone is set up to ask me what I want to do when connected to the PC, and Media sync (MTP) is selected. Here's the kicker... remember, I have two hard drives. When I boot using the other hard drive, the phone connects with no problem. Same USB cable and port. Therefore, this is DEFINITELY software-related.
Is there something preventing this driver from installing? Why is the phone not installing the driver itself? Thoughts would be appreciated! Thanks.
Have you Manually installing the driver from Devices manager?
In the Device Manager locate your Android device. Then right-click on it and select "Update Driver Software".
Select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer".
Select "Show All Devices".
Press the "Have Disk" button.
Enter the path to the Google USB driver. Normally it is located in the following directory: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Select "Android ADB Interface" from the list of device types.
langithitam said:
Have you Manually installing the driver from Devices manager?
Enter the path to the Google USB driver. Normally it is located in the following directory: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Select "Android ADB Interface" from the list of device types.
Click to expand...
Click to collapse
Thanks for the quick reply.
I searched, and do not have a folder called "Android".
I did, however, find a folder called "LG United Mobile Drivers", however there are about 30 different drivers in there. I picked a few, including "Lgandadb" and "Lgnetandadb", but I get told "Windows encountered a problem", and "This device cannot start (Code 10)"
Anyone?
Ok, I'll try to put it another way. When you first connect an Android phone to a PC, drivers are installed automatically. I'm willing to bet there was an error when I installed them on my new hard drive.
Are the drivers already a part of Windows? If so, perhaps I need to do a Repair of Windows?
Are they located in an Auto-Run file on the phone, and maybe I need to re-run that program?
Perhaps there's something I need to delete or flag so that my phone thinks it's the "first time" again?