Related
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.
Howdy.
I recently updated my YP-G1 from CM10 to CM 11 [4.4.2]. I need to use my device for Android app development (and have used it before way back when it was on stock, but haven't used it in a very long time), but am unable to get ADB/Eclipse to detect that there is a device detected. Using the emulator is not an option at this point, as I need to do some work with a real camera.
I've got the Android USB debugging enabled on the device, and the little notification that debugging is enabled comes up when I plug it in.
Things I've tried:
1) Update Eclipse/ADT (complete uninstall + reinstall)
2) Update Google USB Driver (from SDK manager)
3) Update Samsung Kies
4) Google
The only related forum thread that I've located for this situation is: http://forum.xda-developers.com/showthread.php?t=1776828, which just implies that Windows should be auto-detecting the device. Windows is not doing that.
I have noticed that the YP-G1 drivers do not show up as installed under Device Manager. Perhaps that is the source of the problem? I have not been able to rectify that situation via Kies, so I am unsure. Kies doesn't even detect that the device is connected!
If it matters, I'm running on Windows 8.
Thanks much.
P.S. -- I'd post in the CM11 thread, but since I just registered, I am not allowed to do so, unfortunately.
Edit: I got mine to work finally. I solved my issue by allowing windows to automatically search windows updates for drivers. After I did that it found them and it worked, so try that.
I too am having this issue and it's really bugging me. I've tried everything I can possibly think of but I cannot get the drivers to install. I'm using windows 7 64 bit and it sees the YP-G1 but it doesn't have the drivers so things like kies and adb won't detect it. Any solution would be very helpful.
Strange...that's what the thread I linked to suggested. I've tried that multiple times to no avail. Perhaps Windows 8 doesn't find it, while 7 does for some reason? I've tried doing searches via both Device Manager and Windows Update.
Could you perhaps upload the driver files it found? You should be able to figure out what/where those are by using Device Manager, then right click the YP-G1 and go to Properties, then the driver tab, then driver details. Maybe they'll work on Windows 8 as well as 7. I might try plugging my device into someone else's computer to see if somehow mine is just acting stupid.
Thanks for your reply!
Edit: I've plugged my device into another computer. You're right -- on Windows 7, it can find the drivers just fine. On Windows 8, it can't. Go figure. Now to figure out where to get those files and/or how to get the device recognized..... (??)
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!
MTP suddenly stopped working on my desktop running Windows 10 Pro N and I can't transfer files between my devices through USB. I already install the Media Feature Pack for windows before, I reinstalled it but it didn't solve the problem.
In windows Explorer there is just a grayed out USB-Drive and I can't do anything with it.
In the device manager the MTP device is in the 'Other devices' category with a yellow exclamation mark. I tried deleting the driver and updating the driver by selecting 'MTP device' from the driver list but it didn't help.
I tried it with a Oneplus One and a Nexus 7 (2012) and neither of them worked. Adb works fine and MTP works on my laptop, which also runs Windows 10 Pro N with the Media Feature Pack update.
Any help would be appreciated.
bump
I do not think this is phone specific, but I am working with an older Pixel 3XL (running stock 11)
I upgraded my home Laptop, an HP Envy to the latest Windows 11 Beta. And after doing so, my phone is no longer recognized 'properly'.
When I plug it in, if I switch the USB settings to PTP, windows will recognize it and show the camera.
But if I switch it to File Transfer, Windows does see anything? I can hear the Windows beep/sound that it switched over, but nothing shows up.
I have attempted to update and reinstall the google usb drivers, but no change. And I also noted that the Windows 11 machine seems to show 'waiting for device' with fastboot commands as well.
Has anyone else has a similar experience?
ptmuldoon said:
I do not think this is phone specific, but I am working with an older Pixel 3XL (running stock 11)
I upgraded my home Laptop, an HP Envy to the latest Windows 11 Beta. And after doing so, my phone is no longer recognized 'properly'.
When I plug it in, if I switch the USB settings to PTP, windows will recognize it and show the camera.
But if I switch it to File Transfer, Windows does see anything? I can hear the Windows beep/sound that it switched over, but nothing shows up.
I have attempted to update and reinstall the google usb drivers, but no change. And I also noted that the Windows 11 machine seems to show 'waiting for device' with fastboot commands as well.
Has anyone else has a similar experience?
Click to expand...
Click to collapse
I've not had any issues like that with Windows 11.
I've connected several different android devices, not the Pixel 3 though.
Open device manager and see how it's listed.
ptmuldoon said:
I do not think this is phone specific, but I am working with an older Pixel 3XL (running stock 11)
I upgraded my home Laptop, an HP Envy to the latest Windows 11 Beta. And after doing so, my phone is no longer recognized 'properly'.
When I plug it in, if I switch the USB settings to PTP, windows will recognize it and show the camera.
But if I switch it to File Transfer, Windows does see anything? I can hear the Windows beep/sound that it switched over, but nothing shows up.
I have attempted to update and reinstall the google usb drivers, but no change. And I also noted that the Windows 11 machine seems to show 'waiting for device' with fastboot commands as well.
Has anyone else has a similar experience?
Click to expand...
Click to collapse
Have you tried installing Google's USB driver?
ptmuldoon said:
I do not think this is phone specific, but I am working with an older Pixel 3XL (running stock 11)
I upgraded my home Laptop, an HP Envy to the latest Windows 11 Beta. And after doing so, my phone is no longer recognized 'properly'.
When I plug it in, if I switch the USB settings to PTP, windows will recognize it and show the camera.
But if I switch it to File Transfer, Windows does see anything? I can hear the Windows beep/sound that it switched over, but nothing shows up.
I have attempted to update and reinstall the google usb drivers, but no change. And I also noted that the Windows 11 machine seems to show 'waiting for device' with fastboot commands as well.
Has anyone else has a similar experience?
Click to expand...
Click to collapse
speed up windows 11 here
As long as USB-Debug isn't activated on phone you can't see it within Windows.
Update the MTP driver
You should check if the phone is correctly identified by your computer. Go to the Control Panel and proceed to Devices and Printers. If you manage to locate the name of your Android device, the MTP connection is working properly. If your device is named MTP or Unspecified, you’ll need to update some drivers.
Right-click on the Start button then click on Device Manager.
Expand Portable devices and see if your device is located there. If it doesn’t contain your device’s real name or it has a yellow exclamation mark, right-click on it and tap on Update Driver.
The Update Driver window will now ask you to either search for the driver automatically or browse your computer manually for it. Choose the latter.
Click on “Let me pick from a list of device drivers on my computer”.
Click on MTP USB Device to highlight it and then click Next.
The old driver should be replaced with a new one. Wait until the process finishes. Your Android device should now be seen as a multimedia device in File Manager.
Check if the Android phone not showing up on the PC issue still occurs.
Hope This Works,
Peter