Answer: Just because the toolkit suggested a certain driver solution (most likely #1), does not mean that it is guaranteed work on your setup. NRT provides multiple driver solutions so that if you are unsuccessful with one method can try another. Remember when it comes to driver configuration device manager is your friend. You can launch device manager from within the driver guide itself, or from windows Start by typing ‘devmgmt.msc’ then enter. The goal is to configure your device so that adb can communicate with it when its on (with USB debugging enabled) and also so that fastboot can communicate with it when its in bootloader mode. Here are some tips that may help:
- If solution #1 doesn’t work for you, I highly recommend trying solution #4. Solution #4 is the manual method, so it allows you to directly point your computer to the correct driver files in device manager.
- If you are trying a new driver solution, make sure you start back at step 1; meaning you should use USBDeview again to uninstall any conflicting drivers first and fully reboot your computer.
- Enable USB debugging on your device and have NRT running before you plug it in. Doing it this way should initiate the RSA prompt (assuming you are running a 4.3* build). When you accept this prompt, make sure to check “Always allow from this computer”, otherwise NRT will not be able to communicate with your device without you explicitly re-accepting that prompt.
- When plugging your device in, always watch device manager. You should be able to easily identify which entry is your device, then you can Solution#4 to configure the drivers.
- This rule also applies to when you boot your device into bootloader mode. Watch device manager to make sure the entry is properly configured in this mode.
- Remember that a simple way to test the drivers is by using the ‘Quick Tools’ – ‘List devices’ feature. Check that it see’s an adb device when your device is connected and on with usb debugging enabled, and also that fastboot see’s your device when its in bootloader mode.
- If you are having limited success, try alternate USB ports. As mentioned in the guide, try to use USB 2.0 port if they are available rather than USB 3.0 ports.
- Try enabling or disabling MTP; also try this with PTP.
What NOT to do:
If you are having problems configuring your drivers… Please, please, please do NOT write me a message like this:
Wug, I installed the drivers, but it doesn’t work.
There is no way for me to respond to that. I did as much as I can to provide lots of information on Windows driver configuration and provide as many solutions as possible. Unfortunately, it is the one thing that is truly impossible to automate consistently on Windows; believe me, if I could – I would. The Universal ADB Driver Installer by Koush is the closet thing to an automated solution which is why I recommended it in the driver guide, however it may not work on your step up. So, please try other driver solutions like Solution#4, and take advantage of Device Manager before concluding that its not working for you.
With a little effort I hope that you will be successful setting up the drivers. Once you get that out of the way, the other toolkit procedures can be performed with minimal effort.