Database Users

ADB not seeing TPT

I am hoping someone can help me before the ICS OTA hits in the US.
I am trying to root, but I can NOT get ADB to see the TPT.
I am using win 7 64 bit, and have downloaded the adb driver and modified the .inf. It shows up in dev man under android phone as thinkpad adb, but when I run adb devices...nothing.
I installed that latest Java dev and android stk but still nothing.
The TPT is on OTA 2.5.
I have searched everywhere but cannot fined any answer.
Any ideas?
Thanks!

Is USB debugging enabled on your tpt? Did you try a different USB cable/port? On your PC are you in the same directory as adb.exe?

Yes, Yes, and Yes.
ADB is running fine...it just cant see the TPT even tho windows can.

I'm sure you're a little frustrated. I had that happen, and it turned out there were two adb processes running. A reboot fixed that. I'm sorry I don't have the answer.

It IS frustrating, but I appreciate your suggestions!

try running the emulator and make sure you can connect to it via adb, as a check to make sure adb deamon is starting up correctly.

True. Worked for me.

For whatever reason, it was my system that I do all my adb work on....just refuses to see the TPT.
Used my notebook with nothing installed and it went just fine.

My Win7-64 PC could only see my TPT as a portable device, and was listed between drive letters. I wanted to see it under "Android Phones."
After about 6 hours of searching, having installed the Lenovo-provided drivers probably 40 times, I went out on a limb and opened the Device Mangler, individually uninstalled each of the portable devices, including the TPT. Rebooted my PC. Plugged in the TPT, and finally it appeared under Android Phones, and ADB recognized it (I typed "adb devices" in the command prompt and it was listed).
What it came down to is the driver that wanted to be the default was trumping the one I wanted. Beware the Diva. She's not all that.
I should add that I also unplugged a usb card reader (that was making all the drive letters) because I thought that might be the culprit, but it still showed up in the Device Mangler, so I don't think unplugging it made a difference.
I miss Win2K.

Getting ADB to work on Windows 8? (Manual upgrade to Android 4.2)

Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Installing Windows 7 Drivers Please wait
Operation Started
android_winusb.inf
The resource loader cache doesn't have loaded MUI entry.
1
0
An Error Occured. Returning to Main Menu.
---------------------------------------------------------------------------------
If you got the message [the resource loader cache doesn't have loaded mui entry]
during the installation procedure dont worry as the drivers have been installed.
Click to expand...
Click to collapse

PCServe said:
Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Click to expand...
Click to collapse
Do you have Android SDK installed?, if so try the following, you're using Windows 8, right?
On the 'old' Windows Desktop, right-click on the bottom left corner
> Select 'Command Prompt (Admin)'
> type ' devmgmt.msc '
> Right click on the driver with warning sign and select update driver > select BROWSE and go to the extras\google\usb_driver\ folder of your SDK and then update the driver. Did that resolve the issue?

It works for the Nexus 7 when it's running, not in fastboot though

PCServe said:
It works for the Nexus 7 when it's running, not in fastboot though
Click to expand...
Click to collapse
Have you rebooted the PC since installing the drivers?, if not give that a go and try again, they may need a reboot to complete the installation.

Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
Windows was unable to install your Nexus
Windows could not find driver software for your device.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software.
Click to expand...
Click to collapse
I also tried the drivers from ASUS with the same result.

PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
Did you try browsing to the driver location instead of letting Windows find the driver?
This driver has helped others
http://forum.xda-developers.com/showthread.php?t=1766220

PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
turn off driver signing and then do it.Mine works fine in Windows 8..check this for reference:-
http://forums.mydigitallife.info/th...ble-driver-signature-enforcement-in-Windows-8

Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!

PCServe said:
Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!
Click to expand...
Click to collapse
Glad to be of help

No ADB mode, driver issue?

I'm Italian, sorry for my English.
A few days ago I unlocked the bootloader via Toolkit, rooted and flashed the TWRP recovery _.
But I had hard difficulty:
After driver installed, I unlocked bootloader, enable debugging and then NOTHING!
In practice, the N7 was recognized by windows 7 64bit only in FastReboot mode ..
I tried in every way possible, deleted and reinstalled the driver 50 times, restored windows to a previous point, installed the drivers manually tried without toolkit, but how ADB just do not want to know.
For hours I was still with the bootloader unlocked but without root, until came to my rescue a friend with another notebook but same windows 7 64. Load the Toolkit, install the drivers and everything goes perfectly, I do everything in 5 minutes.
On my laptop there is always the issue driver ADB, in the future I still need my PC recognized the N7 in ADB, how can I do?

One thing that I think is not well understood is that there is no "Generic Class Driver" for ADB nor for fastboot...
... even though the very driver that works for one mode (or phone/tablet device) may be perfectly fine with a different device. The wire protocol for both fastboot and adb are extremely simplistic.
So, what that means is that if the Hardware ID used by the USB device endpoint registers on the bus with a different VendorID/ProductID, Windows will (correctly) not use a previously-installed ADB driver, or previously installed fastboot driver - even though they would probably work just fine.
Here is an example. The Nexus 7 registers the following Hardware ID when ADB debugging is turned on in the OS:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
On the other hand, if you are using TWRP, it's adbd daemon shows up on the PC as:
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
This means that you might need to install a different driver for using the ADB with the OS, and a different driver for ADB under TWRP - even though it is exactly the same hardware on the other end of the cable! In the absence of a generic class driver for a given USB endpoint, Windows tries to match drivers in it's local (& internet) database based on this VID/PID pair.
If you have a look at the [ADB/FB/APX Driver] Universal Naked Driver 0.72 thread - and download it and have a look at it's included "android_winusb.inf" file - you will see literally hundred of different VID/PID pairs in the driver's android_winusb.inf file in the installer package, corresponding to many hundreds of phones/tablets. Same driver with hundreds of devices listed as compatible.
In the past I recall taking the Google (SDK) USB driver, and manually editing into place matching VID/PID pairs for a HTC phone into the .inf file. It worked perfectly; I probably flashed that phone hundreds if not thousands of times using the Google Driver (My PC is a Windows 7 Pro x64 machine btw).
Anyhow, I have pulled this stunt twice now - once editing the .inf file for the Google Driver, and I did it once with the Universal Naked driver too. You can choose which driver you want to start with.
If you want to give it a roll, you can start with any of those three drivers:
- Google (SDK) USB driver
- XDA "Universal Naked" driver
- Asus Nexus 7 USB Driver (Look under Download)
Note that since you are using W7 x64, make sure that you add each new entries to the .inf file twice - once in the ".NTx86" section, and duplicated again in the ".NTamd64" section. When editing .INF files, make sure to use an editor which preserves simple text file formatting - use "notepad", not "wordpad"
If you want a reference for what values to use, see the bottom end of this post. You should see exactly these same values in your Device Manager, however.
Note that if you see the device show up in the Device Manager as being correctly identified and marked as "working normally" - but it doesn't work - you should probably remove that driver and re-install from a different driver package.
This would certainly be the case for any drivers you saw associating with VID/PID pairs that look like:
VID_18D1&PID_4E40 bootloader/fastboot
VID_18D1&PID_4E41 single adb
VID_18D1&PID_4E42*&MI_01 composite adb
VID_0955&PID_7330 avx mode
VID_18D1&PID_D001 adb in TWRP (maybe CWM too, I didn't check)
That's a lot to throw at you, especially with Italian <=> English in the mix.
Feel free to ask questions.
bftb0

Hello,
I tried to follow your advice but I have not solved.
I'll explain what I did, so you can correct me.
-Uninstalled previous drivers (from device manager, control panel)
-Restart the PC
-Modified the inf file. Package Asus Nexus 7 USB driver (ntx86 and NTamd64 sections) attach screenshots
-Linked N7 (usb debugging actived)
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
I tried to change also too XDA "Universal Naked" driver by following the same procedure.
I tried to create another account on my pc, but no ADB!
View attachment 1734997

Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD

stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Use "Google USB drivers" you get after you install from here http://developer.android.com/sdk/index.html
Its drivers work with 4.2.2
I got 4.2.2. rooted with ADB working now via only this and no other method

No problem with adb in 4.2.2... I tested yesterday (no need psw too...)
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse

Marco16V said:
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
Click to expand...
Click to collapse
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.

bftb0 said:
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
Click to expand...
Click to collapse
When the drivers are not installed and I connect to pc N7, is only recognized as a portable device, then later recognized as Google Nexus 7.
To install the drivers (modified as described) I click reinstall driver, then later recognized (if connected to pc in android mode, with usb debugging actived) as Android Device in another voice, ADB interface. But is not recognized by the toolkit under adb devices, and even when I try using cmd.
1-When I install the drivers. seem to be installed correctly.
2-Sorry, where can I find Hardware IDs in Device Manager? What is the difference between OS adb and TRWP adb?
3 - In other pc (with same N7, same cable, same driver, same toolkit) I had no problems. I tried to change only the USB port.
4-I uninstall the driver from device manager (uninstall voice) and ask to be also uninstalled software from the PC
In some Italian forum, I found people with the same problems.
Solved by formatting PC. I would not do that ...
Thanks for your help, sorry for my English and my limited skills

AW: No ADB mode, driver issue?
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sdk but I have not solved.
I use Android 4.2.1. I'm having problems with the update! I can not update OTA (N7 stuck under the impending reboot). I also tried to download the zip file to upgrade the memory and flash it from recovery but the installation is not completed (error 7 build.prop).
I also tried to flash the factory image 4.2.1 (keeping userdata) and start again. Nothing, same mistakes!
Too many problems!

Marco16V said:
2-Sorry, where can I find Hardware IDs in Device Manager?
Click to expand...
Click to collapse
(Note I attached some pictures below)
From the Device Manager:
- Select the Device in question by right-clicking. Choose "Properties"
- A window with three tabs will appear: General, Driver, and Details. Select Details
- The "Property" combo-box-selector has 20 or 30 items - the 2nd one in the list is Hardware Ids. I attached two pictures from Win7-Pro-x64 (below)
But note as I said before: You should NOT be seeing the ADB endpoint under "Portable Devices" - if ADB Debugging is turned on in the OS, you should see it under "Android Phone" or something similar. In any event, the hardware Ids will identify it exactly
Marco16V said:
What is the difference between OS adb and TRWP adb?
Click to expand...
Click to collapse
Well, as far as the behavior of the USB driver on the PC, almost nothing. Unfortunately - for better or for worse - both TeamWin (TWRP) and CWM authors put their ADB interface on the bus with the VID/PID pair of USB\VID_18D1&PID_D001, whereas the OS puts all its USB interfaces on 18D1/4Exx.
So, even if you get a driver installed for the OS "adb" mode (say by using the Google SDK USB driver or the Asus Nexus 7 driver), it won't work for the custom recovery... unless you fix up the driver installer package to have the matching VID/PID pairs (18D1/D001) in the .INF file for that driver.
I think folks find this confusing - they think, "wait, I have a ADB driver installed" - why does it not work?
OK, there are a couple more things to try (at least before I give up). Roughly they try to answer these questions:
Q1) Is this a toolkit issue, or a driver issue?
Q2) Is it a prior driver you installed that you are not observing that is causing the problem?
The first one (Q1) is easiest to diagnose: when your PC Device Manager indicates that a device is "working normally" - AND THE VID/PID ID MATCHES WHAT YOU SHOULD EXPECT FOR THE MODE THE TABLET IS IN (regular OS, recovery boot, fastboot mode), can you communicate with the device from the Windows command line? e.g.,
Code:
C:\foo> cd C:\blahblah\sdk-platform-tools-directory
C:\blahblah\sdk-platform-tools-directory> fastboot devices
or
C:\blahblah\sdk-platform-tools-directory> adb devices
If you can communicate with the tablet from the command line - your device ID will be printed by the above commands, then you don't have a driver problem at all - there is something screwy about the way your toolkit is installed.
OK, Q2 -
When Windows installs a driver, it caches it into a kind of database. I suppose it is possible that a prior driver installation might be causing trouble. You can observe - from the device manager - all the drivers that are installed - even for devices that are not currently connected to your computer.
This is done by setting the "devmgr_show_nonpresent_devices=1" environment variable. It can be done semi-permanently this way, or for a single invocation of the device manager this way..
See the third image attached (devmgr-all-devices.jpg ) - it is my computer in that "show all devices" mode. See all that rubbish in there? It's from other Android devices (HTC, Samsung, etc).
You can walk through each one of those - even the devices that are not currently attached - and inspect the VID/PID pair to see if they happen to match the values that you are expecting to see for the different operating modes on the Nexus 7. I'll leave it up to you whether you want to do this or not; it is a bit tedious. Just don't start deleting drivers willy-nilly if you don't know what they are associated with.
Marco16V said:
Thanks for your help, sorry for my English and my limited skills
Click to expand...
Click to collapse
I am understanding everything you are saying - and your english is far better than my italian
good luck!

[Q] Can't install apks despite my device is NOT adb offline.

Ok I've been following every step some posts follow in order to upgrade every Android SDK component to the last version (adb, sdk manager, avd manager, usb driver, web driver and ALMOST EVERYTHING fetched in the sdk manager). I have my Nexus 4 on stock 4.2.2 (JDQ39) working like a charm with its USB driver with my PC, the debugging is on, also the unknown sources option (if any), the phone is properly linked with the "adb fingerprint protection" thing (can't remember the correct name), and last I can see my Nexus 4 detected on adb devices command AND STILL I can't install a sole apk, in this case I'm using Android Commander 0.7.9.11 and nothing, I've tried with Droid Explorer or even Moborobo and nothing.
However in my cousin's laptop I can successfully install apps.
I thought it must be something wrong or corrupted with my OS, so I reinstalled Windows 8 (x64) and take care about all the drivers and everything mentioned above and still... I get the same, so I'm running desperate here.
Maybe it's something simple, I just need someone to help me.
Sorry if I writed so much... I only did it to avoid Android's ABC related questions.
Thanks in advance for your time.
Best regards.

Does "adb install path/to/app.apk" work?

chromium96 said:
Does "adb install path/to/app.apk" work?
Click to expand...
Click to collapse
When I do it I get this:
Code:
C:\sdk\platform-tools>adb install C:\mxvideoplayer.apk
2752 KB/s (6930955 bytes in 2.458s)
pkg: /data/local/tmp/mxvideoplayer.apk
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]

[Q] ADB will not connect to new nexus 7

I just got a brand new Nexus 7 and I went to root it with the nexus 7 toolkit. Long story short the Nexus's serial number would not show up under the attatched devices.
I have tried uninstalling the driver, reinstalling both the driver provided by the nexus 7 toolkit and asus. Neither work. Interestingly eclipse will not connect either.
Device manager shows the adb interference as working however adb will not return a connected device.
I also tried putting the nexus into ptp mode and using adb even though I did not do that with my previous nexus 7. When the Nexus is in PTP mode device manager will not allow me to install drivers for the adb interference. Which is odd since I thought if I installed adb drivers once I wouldn't have to again.
EDIT: I should also add that adb in fastboot and stock recovery works. I was able to try reflashing the device with a stock nexus 7 ROM but it didn't work. Still couldn't connect to abd while android was booted. Also I noticed that my old nexus has both mtp and adb available at the same time. However the new nexus only allows one or the other. E.g. I can't access the files system while adb is enabled and vice versa.
Do you guys have any idea why this is happening? My old nexus works fine.

theaftermath said:
I just got a brand new Nexus 7 and I went to root it with the nexus 7 toolkit. Long story short the Nexus's serial number would not show up under the attatched devices.
I have tried uninstalling the driver, reinstalling both the driver provided by the nexus 7 toolkit and asus. Neither work. Interestingly eclipse will not connect either.
Device manager shows the adb interference as working however adb will not return a connected device.
I also tried putting the nexus into ptp mode and using adb even though I did not do that with my previous nexus 7. When the Nexus is in PTP mode device manager will not allow me to install drivers for the adb interference. Which is odd since I thought if I installed adb drivers once I wouldn't have to again.
EDIT: I should also add that adb in fastboot and stock recovery works. I was able to try reflashing the device with a stock nexus 7 ROM but it didn't work. Still couldn't connect to abd while android was booted. Also I noticed that my old nexus has both mtp and adb available at the same time. However the new nexus only allows one or the other. E.g. I can't access the files system while adb is enabled and vice versa.
Do you guys have any idea why this is happening? My old nexus works fine.
Click to expand...
Click to collapse
I will be watching this thread as am having the same issue right down to working fine in ptp or camea mode, but am unable to click and drag files to the device. And similiarily to you, have no problems with the 16g nexus only the 32. I am using skippen's toolkit.

A possible solution.
aircooledbusses said:
I will be watching this thread as am having the same issue right down to working fine in ptp or camea mode, but am unable to click and drag files to the device. And similiarily to you, have no problems with the 16g nexus only the 32. I am using skippen's toolkit.
Click to expand...
Click to collapse
I forgot I made this thread. I have since since solved the issue and have both mtp and adb at the same time with this particular nexus 7.
First of all installing new drivers on my windows 7 installation was causing a problem. So I backed up and reinstalled. However, while that solved other problems it did not solve my issues with the Nexus.
After a lot of fiddling I finally got it to work by using the official google usb driver. http://developer.android.com/sdk/win-usb.html
Now here's the thing. I discovered that windows treated each combination of adb+mtp or adb+ptp, adb alone, mtp alone, and ptp as a seperate device. So while they all might use the same driver windows considered them different devices.
So basically what I did was install google's driver whenever a combination of usb modes did not work correctly. So in adb+mtp (which is what I really want to be able to use) I went to device manager found my nexus 7 under android devices or whatever it is called and installed the the official google driver. It proceeded to tell me there was an error but then it proceeded to work perfectly. The error may have been just my computer acting up because of all the drivers I'd been installing/uninstalling trying to get this to work.
Also, when you go into device manager and try to install the usb driver you typically right click on the device, select update driver and then click search computer, browse to the folder containing the driver and install. Sometimes that would fail for me, windows would say I already had an updated driver. Thankfully I did find a workaround that forces windows to install the driver you want to install no matter what.
When you get to the part where you browse your computer for the driver click let me pick from a list of device drivers on my computer. Then there should be a button that says I have the disk. Click on that browse to the folder with drivers, say yes to any warnings and continue.
If the I have a disk button does not appear and instead a list of possible manufacturers or devices shows up just click on one of the entries. Then the I have the disk button should appear.
The danger with forcing windows to install the driver you want is that you can install any driver for anything and possibly damage something.
Hope this helps!