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.
Currently I'm trying this guide:
Nook Tablet "One Click Root" + gapps ADB script
but I've been trying various guides all day. The drivers are there, debugging enabled, auto mount disabled, robot in the bottom corner but when I run ADB Devices, no dice. Anyone have any clues what the problem could be or atleast anyone else having this problem? At first I thought it might be because I was using a different USB cord but it still doesn't work even with the Nook cord
The problem you describe is almost guaranteed to be a problem on your computer and the driver installation.
For the folks here to help, they will need to know platform (PC or mac) and version of operating system.
If Windows, they will need to know how the device appears to Device manager. If it shows up as a disk drive - you will have to disconnect from the Nook side. ADB Composite should be good.
For either platform, confirm that adb_usb.ini is in the right place and modified correctly.
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
You need to have your nook tablet unplugged when you run that then you would see nook tablet in the device manager when you plug it back in.
Indirect said:
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
Click to expand...
Click to collapse
"Cannot find the path specified." But I can locate the file myself in that directory??
I'm running Windows 7 64-bit, device shows up as android phone>androud ADB interface.
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Check, still nothing in ADB, i did restart the server too. To be clear, the .ini file only has the "0x2080" line in it now, nothing else. I'm assuming that's ok because the other stuff was commented out anyway, am I right?
(thanks for your help! )
1) look in device manager now though, you need to install the drivers.
I still see it listed under android phone > android ADB interface and not mass storage or anything like that, you think that's still the problem though?
*Edit*
SUCCESS!! I uninstalled the "Android ADB Interface" and "Android Composite ADB Interface" appeared in its place!!(??) Whatever happened the device show up now. Thanks for the help and keep up the good work Indirect!
Indirect said:
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Click to expand...
Click to collapse
I was having problems seeing the Nook Tablet in adb devices, but this fixed it for me.
I was having the same issue for a bit, restarted my nook and it worked haha.
Sent from my BNTV250 using xda premium
This worked for me. Hopefully it helps.
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.
Now unplug and replug your NT, and you should now see an Android Composite device with the "!" next to it. You should now be able to install the custom drivers described in the other posts.
Essentially it seems windows is trying to "help" you by guessing at the drivers you want to use.
If this doesn't work, you can try to remove ALL android devices using the USBDeview Application that you can find http://www.androidsim.net/2009/08/how-to-1-how-to-install-usb-driver-on.html
I used USBDeview for the removal part just because I had a Kindle fire, HTC device, samsung device, all installed and I think they were fighting a little bit. I now have results from adb devices, and dare I say ROOT!?!?!
Hope this helps some of you!
Good post - Windows Vista especially, and Windows 7 somewhat, really think they know better than the user when it comes to drivers. Especially unsigned drivers in preference to signed ones...
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
tsubus said:
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
Click to expand...
Click to collapse
I just joined the forum to thank you! I spent hours looking for a solution and yours worked!
brices21 said:
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.!
Click to expand...
Click to collapse
Well I am stumped here, seriously. I can't get rid of the above mentioned 2 instances of "B&N NOOK Tablet USB Device" no matter what I do. Auto mount is off on the device and the device installation setting is already set to "No, let me choose what to do." Yet every time I plug the NT in- the computer kindly tells me it's "ready for use" and those two "B&N NOOK Tablet USB Device" listings are back. At this point I'm not sure I'm ever gonna be able to get the device to show up under ADB. The computer just won't seem to let it.
Any advice anyone might on this would be greatly, greatly appreciated.
maybe try what Indirect did here: http://forum.xda-developers.com/showthread.php?t=1363652
The website is below what I did to completely disable Windows from installing the Nook drivers every time it is plugged in. I also had the "Never install driver software from Windows Update" checked from Brices21's post but the drivers would still install everytime it is plugged in.
xxxx = http - still a noob, can't post links
yyy = www
xxxx://yyy.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
I never actually installed the USB drivers that indirect provided, but "adb devices" still detected the NT when plugged in.
This was my whole process to get "adb devices" to detect the NT:
With the NT plugged in and device manager detecting the 2 Nook devices as drives and 2 Nook devices in "other devices" and with automount disabled and USB debugging enabled
I also ran the runmefirst.bat at some point in time previously, so the necessary files were created already
***** Pulled this from the website above******
* Go to Start–>Search type in gpedit.msc
* Click the file to open the Local Group Policy Editor and show Windows who is in control!!
* You want to go here: Computer Configuration->Administrative Templates->System->Device Installation. Click on the subfolder Device Installation on the left and on the right side you will see the possible restrictions.
* Right Click on Prevent Installation of Devices not described by other policy settings and edit this option, set it on ENABLED.
*************************************
From here the website says to reboot and set the option back to default. I did not reboot or set the option back.
* Going back into device manager, I uninstalled the drivers for the 2 Nook drive devices.
* Unplugged the NT
* Plugged the NT back in
Then I got the B&N NOOK Tablet USB Device with the broken symbol under "Other devices" in Device Manager
* Open cmd and run "abd devices" from the ntroot directory
The service should start and list the NT device as a bunch of numbers.
* From here you can run NookandZergy.bat to root the NT.
After rooting you can set the options in the gpedit.msc back to defaults.
I also tried installing the Indirect provided drivers as the USB mass storage device. Windows then detected the device as an Android ADB Composite device but "adb devices" from cmd prompt would not detect the NT. I ended up removing all of the drivers and repeating my steps to get "adb devices" to detect it again.
Hope this helps! It may not be the best solution but it was a workaround for me to get the NT rooted.
****Update*****
Just got home and tried to install the drivers and it worked this time. I was able to see the NT with "adb devices"
With the gpedit.msc edit intact, I plugged in the NT and Windows detected 2 broken Nook devices under "other devices" and a mass storage device under USB controllers.
* I uninstalled the driver for the mass storage device
* set the gpedit.msc back to "not configured"
* unplugged NT
* made sure debug mode was set and automount disabled
* plugged NT back in
Device manager showed a Mass Storage device under "Other devices"
* Update drivers for that device with the Indirect usb driver
* ran "adb devices" in cmd prompt and NT is detected.
So if there's anything to take away from my post...hopefully you can use the gpedit.msc to completely disable the autoloading of drivers.
Drivers Fixed!
Rooted! Got past driver issues (Android Composite ADB Interface appeared in Device Manager, adb still couldn't detect Nook). Thanks to all who have worked so many hours on this.
Here's what worked for me (using Windows XP 32 bit):
1. make sure "adb_ini" file contains "0x2080" and is located at "%USERPROFILE%\.android"
2. I had to manually edit my "path=" environment variable to include the above location - both in Control Panel->System->Advanced->Environment Variables and in cmd window.
3. carefully followed instructions on proper installation of drivers for "Android Composite ADB Interface". At this point, cmd window use of adb was able to detect Nook (as well as runmefirst.bat).
4. Continued with root process (i.e. NookandZergy.bat)
Hope this helps anyone still having driver issues.
Never had this issue using the trick mac method.
I have installed SDK to my PC running Windows XP. I connect my Archos G80
G9 to . it shows found new hardware MTP and asks to install the driver.
I choose option
"install from a list of specific location" then
"search for the best driver in these locations"
"include this location in the search"
then browse to folder of the driver which I download from the Archos Website
(adb_winusb driver\usb_driver) then click "Next" to install the driver but the
PC shows "the hardware was not installed because the wizzard cannot find the necessary software".
I even tried the driver downloaded from the SDK tool but it's the same error.
So my PC does not shows the Archos.
In Device Manager it shows : Android phone
Android composite ADB interface
(this device is working OK)
but there is yellow question mark in MTP ( need install driver ).
It's very strange because if I goes to the command mode and type
"adb device " it shows my device ID.
So my question "How I install the driver so my PC will show my Archos?"
Thanks
Try searching in Windows Update (in New Hardware Wizard or in Update Driver wizard)
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
kam5iz said:
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
Click to expand...
Click to collapse
For me. Go into Device Manager and find the unconfigured device and manually assign the driver to it.
EDIT: Which you may need to get the android sdk and download the usb driver and manually assign it with those.
Excuse me if this has been posted before, but I've been having trouble with it (pretty new at this - the only other android I've had was a Galaxy S5 AT&T variant with a locked bootloader)
I'm on Windows 10 if it matters.
After installing the SDK and running the "adb devices" command, my results were:
List of devices attached
...and nothing more. "adb reboot bootloader" also did nothing. The phone never asked me to authorize the computer for debugging either.
The fix was to download the latest Google USB driver and install them manually.
https://developer.android.com/sdk/win-usb.html
(I can't post links yet)
Open device manager with your phone connect via USB. On mine there was an item called simply "ADB Interface" with a yellow symbol superimposed over the icon.
Extract the .zip containing the Google USB drivers (doesn't matter where). In Device manager right click "ADB Interface" and click "Update driver software..."
Click "Browse my computer for driver software"
Browse to the folder containing the drivers and click "ok"
Make sure the box marked "Include subfolders" is checked and click next.
Let the drivers instal. There should now be an entry under Android Device in Device Manager called Android Composite ADB Interface.
After doing this, check your phone and there should be a window asking you to authorize your computer for debugging. Authorize it and you're done.
Hope this helps someone do this a little faster than I did.
Man I gotta love you! thank you so much!!