[Q] Nook Tablet USB Debugging via Win7 - General Questions and Answers

Trying to use Indirect's rooting system for the Nook Tablet, but getting stuck on the install of USB Debugging.
I've "unrooted" from 1.4.1 back to 1.4.0.
The instructions suggest, "6a. When the batch file opens the device manager, If you don't see a broken device icon next to "NOOK Tablet" then you may have some other generic drivers taking over. Not sure how to remove them so you will have to move to another PC that has never had a tablet hooked up and start over."
However the Driver that is working for the Tablet is the standard Winidows Portable Device Filesystem (Win 7, 64 bit). I can uninstall it, but it comes right back as soon as I reconnect the Nook. Tried also to use the "Have Disk" approach, but it complains "Folder doesn't contain compatible Driver. Make sure it is designed to work with Win7 x64."
I'm thinking this has got to be a common problem for Win7 users.
Any solution?

Related

[Q] Device debugging with Eclipse

I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?
Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim
Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?
More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!
Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.
Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.
I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.
One thing I forgot. Do not unplug your device between uninstall and hardware scanning.
AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim

[Q] No Harmony Drivers

I have a Malata Z-pad bought in China.
Now running TnT Lite 4.2.0 which is far superior to the Chinese stock it was supplied with.
When I first connected it to a Windows 7 laptop it loaded some harmony drivers and the 'Safe to remove usb device' icon would appear on the pc.
I have subsequently connected it to Vista computers and I get an error saying the Harmony drivers cannot be found.
The Z-pad is rooted and I can see all the files and folders (with the exception of SDcard and SD card2). I can transfer files ok - I just do not have the disconnect usb device icon.
Do I need these Harmony drivers - and if so, where do I find them?
Many thanks
Paul
matchworker said:
I have a Malata Z-pad bought in China.
Now running TnT Lite 4.2.0 which is far superior to the Chinese stock it was supplied with.
When I first connected it to a Windows 7 laptop it loaded some harmony drivers and the 'Safe to remove usb device' icon would appear on the pc.
I have subsequently connected it to Vista computers and I get an error saying the Harmony drivers cannot be found.
The Z-pad is rooted and I can see all the files and folders (with the exception of SDcard and SD card2). I can transfer files ok - I just do not have the disconnect usb device icon.
Do I need these Harmony drivers - and if so, where do I find them?
Many thanks
Paul
Click to expand...
Click to collapse
i think the drivers are for ADB....its for development and the sdk so if you can transfer file fine you dont need to worry...if its really bothering you you can get pdanet or droid explorer cause they both have the adb drivers...hope it helped
Hi,
Actually, I think that the "Harmony" driver is for the normal non-ADB USB, i.e., for transferring files to the Gtab.
It may be that Vista doesn't have the Harmony USB driver, whereas Windows 7 does. I'm not sure (no Vista machine).
Jim

[Q] Win7x64 USB - Device Not Recognized

I tried connecting my Transformer to my PC this morning to make copying files to internal memory a bit quicker than using wifi. Assuming it would be like pretty much every other Android device, i just plugged the Transformer in using the supplied USB cable and assumed Windows would recognise the Transformer and download the appropriate device driver.
Unfortunately, it did not recognise the device and came up with that message. So i uninstalled the generic drivers for the unknown device and then installed the Asus PC suite thinking that this would work. Rebooted computer, plugged in Transformer and again same message, device not recognised.
Why isn't this simple? I'm yet to try on another PC. Can anyone suggest any tricks to get this working?
Just download the actual USB drivers from ASUS, plug in the TF, right click My Computer then click Manage, select Device Manager from the pane on the left and find the transformer in one of the dropdowns on the main pane. Right click the transformer in the dropdown and update driver, choose to find driver yourself, navigate to the ASUS usb driver folder you downloaded and continue. Drivers should then be installed.
Sent from my creaky Thunderbolt
Thanks for the suggestion. I've tried to manually install the drivers this way and pointing to the inf files to install but windows says they are not a valid driver installation file. I noticed someone else was having this problem in another thread and it was unresolved.
Weird. I have win 7 x64 on my desktop and laptop and never had problems installing drivers or recognition problems. Should try connecting to another machine with x64, might be a hardware problem with your machine.
Sent from my creaky Thunderbolt
If you run the asus sync or pcsuite application, either one will install automatically the usb drivers.
Remove all the drivers you have installed and then reinstall from ASUS. They may be conflicting

[Q] Problem with USB mass storage

Solved: Hopefully this helps someone else. I uninstalled all LG drivers from my PC. Then I connected my phone in via usb and checked my device drivers and updated them. However, rather than letting Windows find the best MTP drivers I chose to browse my computer and picked from a list on my PC. I selected the Linux drivers and everything works perfectly now,
I have a P509 running WC’s AOKP Milestone #6 but I did something stupid…while cleaning up files and programs I uninstalled my LG usb driver for my P509 and now I can’t get the PC to recognize the phone. I run W7 64 bit and it just won’t connect - not even from recovery. On another XP PC it connects no problem (it has LG driver 4.9.4 installed although I don’t recall installing it) and my laptop running W7 64 bit connects no problem either (it has LG driver 3.6 installed, but again I don’t recall installing it on the laptop either). Installing 4.9.4 or 3.6 on my problem PC doesn’t help. I keep getting an error that “MTP… whatever” failed. It’s driving me nuts. I can use the other computers if I need to but the problem PC is my main unit and more convenient to use for all my needs. Also, the phone is recognized by my work PC which has no LG drivers installed at all, nor could I if I wanted to as I don't have admin rights.
Any suggestions for my W7 PC?
Thanks,

A700 USB problem

Hello.
I've got A700 and I'm trying to root it but I've got a problem. I tried it with every key combination (power, volume up & down) I found on the internet but they don't work.
I also tried it when using the USB port but my PC and my laptop won't recognise the tablet. I've downloaded the drivers from Acer but when I install them my PC asks to install NET frameworks 2.0.5727. This version is no longer available but Frameworks 3 also worked according to Microsoft. After this installation the drivers from Acer still don't want to install. Then I tried it with Android USB driver but the same problem keeps coming back.
When I plug the tablet on my PC and look in the windows device manager there is a yellow triangle on the USB port with an error code 43. I've got the same problem and errors on my laptop. They both work on Windows 8.1. The tablet doesn't appear in the device list on my pc .
Could it be that the problem is on my tablet's USB? There is no problem when charging.
Does anyone have a similar problem or maybe a solution?
scan-x said:
Hello.
I've got A700 and I'm trying to root it but I've got a problem. I tried it with every key combination (power, volume up & down) I found on the internet but they don't work.
I also tried it when using the USB port but my PC and my laptop won't recognise the tablet. I've downloaded the drivers from Acer but when I install them my PC asks to install NET frameworks 2.0.5727. This version is no longer available but Frameworks 3 also worked according to Microsoft. After this installation the drivers from Acer still don't want to install. Then I tried it with Android USB driver but the same problem keeps coming back.
When I plug the tablet on my PC and look in the windows device manager there is a yellow triangle on the USB port with an error code 43. I've got the same problem and errors on my laptop. They both work on Windows 8.1. The tablet doesn't appear in the device list on my pc .
Could it be that the problem is on my tablet's USB? There is no problem when charging.
Does anyone have a similar problem or maybe a solution?
Click to expand...
Click to collapse
Well, Win8 can sometimes give issues. I might suggest 2 things,
1) Try a different USB port. Typically devices come with USB 3 and USB 2 ports. If you have a standalone PC (desktop) don't use the USB port in the front. Try it from the back port.
2) Try manually installing the drivers. In device manager, select "install from disk" and manually select the driver (even if windows won't guarantee compatibility)
As with .net, just install the newest.
If the above don't work, well, try somebody's Win7 pc.
One more thing, when you install the drivers, make sure you "right mouse click" and install as administrator.

Categories

Resources