Database Users

[Q] Help in installing adb drivers

My vibrant is stuck on the vibrant logo after I tried to use the one click unroot program. The only solution I found after two days searching on the net, is to use odin. The first problem is that my phone is locked, so I can't use the vol up+down+power button combo to get into recovery or download mode.
Now comes the issue, I want to use adb to reboot the phone, but adb can't see my device. After installing the samsung USB Drivers, I see that the adb drivers are not installed (The drivers for this device are not installed. (Code 28)), and even when I try to manually install them from the SDK drivers (I checked the "include subfolders) it says that it can't find them.
I have windows 7 x64
Anyone have suggestions to how to install the adb drivers and make the adb see my device?

Can you get into download mode? Have you tried to Odin back to stock? If you want to set up ADB type ADB for dummies in search and you should find everything you need.

Here is the link from the sticky thread for help with drivers:
http://forum.xda-developers.com/showthread.php?t=728929

I just figured out a neat trick to get phone to work even if it's stuck on the vibrant screen.
Just connect it to the usb, wait until the grey battery picture appears.
After 5 seconds, take the battery out and put it right back, (leave usb in) and wait again. Do it once more, until you see that the battery picture turns green. After that take the battery out and unplug the usb, and turn the phone on.
It should work now.
The thing is that, next time you turn the phone off and on, it would be stuck again, so do something to fix it like odin.
That how it worked for me.
And about the adb driver problem, I just pointed manually the driver update to the "USB Drivers" that TGA_Gunnman posted here (I can't post link. just search usb drivers here in the forum) and after that adb worked like a charm, rebooted instantly to download mode - it's crucial for those like me that have hardware locked phones.
The thing is, that all the other posts say to point it to the sdk drivers, but that dosen't work.
Good luck to all others.

installing the samsung drivers and installing adb are two different things. the samsung drivers should install normal by double clicking the driver package (you may have to still tell windows where to look). installing adb is simply downloading the sdk, however, if you want adb to work everywhere (instead of just the sdk/tools folder) you need to put the sdk/tools folder in your path.
then 'adb devices' should show your device in win powershell, but will only work if you are in the sdk/tools folder or have added it to your environment variables.

[Fixed] Can't unroot nexus

I am trying to unroot my Nexus S and relock the boot loader. I've followed multiple guides and tried them on different computers (mac & windows). Every time I am supposed to type in "fastboot oem lock" and every time the command prompt just says waiting for device and nothing happens
I've installed the usb drivers from the android SDK so I'm lost as to why this is happening
I'm running the I9020T on Wind
Fix: Turns out it was just a driver issue, following these instructions got it working for me
Part 1 - Drivers
1 - Download Android SDK
2 - Unzip & launch "SDK Manager.exe"
3 - Cancel the first popup & go to "Available packages" > "Third party Add-ons" > "Google Inc."
4 - Select "Google USB Driver package" & click "Install Selected"
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
6 - (MOD EDIT: Ignore this step for i9020A models) Open "android_winusb.inf" and add the following lines to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
Click to expand...
Click to collapse
as described here [SOLVED] Google Android USB drivers - Nexus S SCLCD GT-i9023 not recognized
7 - Turn Off your SNS
8 - Make sure the SNS is connected to the PC via the USB cable
9 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
It reads LOCK STATE - LOCKED
Open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
10 - Do a right click and select Update Driver Software
11 - Select Brose my computer for driver software
12 - Point it to your Android SDK installation "extras\google\usb_driver" dir
13 - Make sure to CLICK "Let me pick from a list of device drivers on my computer"
14 - Then from the list 3 choices select Android Bootloader Interface
15 - If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Click to expand...
Click to collapse

Turn on usb debug inside the os.
Then do adb reboot bootloader
Once in bootloader do fastboot oem lock
Hope this helps
Sent from my Nexus S 4G using XDA

Unfortunately i've tried that, nothing happens after I enter fastboot lock

Once you unlocked your bootloader you can not lock it again.

Tom Foolery said:
Unfortunately i've tried that, nothing happens after I enter fastboot lock
Click to expand...
Click to collapse
Do you have a custom recovery installed? Did you try a different usb cable?

1. connect the USB cable directly to USB port on the laptop/desktop; dont connect via monitor USB or extension
2. Open device manager and check if the device is detected as ADB; you need to have the drivers installed
3. perform "fastboot oem lock"
or
Follow the step by step instructions here

zonesan said:
Once you unlocked your bootloader you can not lock it again.
Click to expand...
Click to collapse
Not true, i've done it...as have many others...

gullu101 said:
Not true, i've done it...as have many others...
Click to expand...
Click to collapse
Thanks very much, I always thought we can't lock back the bootloader.

gsrdemon said:
1. connect the USB cable directly to USB port on the laptop/desktop; dont connect via monitor USB or extension
2. Open device manager and check if the device is detected as ADB; you need to have the drivers installed
3. perform "fastboot oem lock"
Click to expand...
Click to collapse
I've tried these steps and I used the guide from nexusshacks but it didn't work.
Do you have a custom recovery installed? Did you try a different usb cable?
Click to expand...
Click to collapse
Although it probably didn't work because before I started the tutorial I installed a ROM which removed Clockwork recovery. I'm going to reroot my phone and try again from the beginning.
Edit: wait that's a lie, I did this a week ago so I'm not 100% sure what I did now, but I'm pretty sure I used the ROM from the guide

I've tried flashing a new recovery but I get the same "waiting for device" message
This makes me think it's a usb issue. I've been having usb issues for a while now, I've tried different cords and different computers. Is there any options I have left.
EDIT: Now I'm almost 100% sure the only thing standing in my way is the USB problems.

Try installing pdanet and using their drivers. Although i doubt this will work as im almost sure that the fastboot drivers arent the same as the adb drivers. Try disconnecting ng and reconnecting your phone on usb once you boot into bootloader.
Sent from my Nexus S 4G using XDA

A load of problems...

So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.

Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers

bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery

Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?

bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.

Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?

bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.

Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck

Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!

Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.

[Q] Having driver issues in Download mode VS980

I have a rooted Verizon LG G2 that I somehow screwed up when going to Lollipop from KitKat. I have lost my 3G and LTE capabilities, thus no data unless connected to WiFi. From what I have read, it sounds like I need to try to revert to stock and start over. This is where I am having my major issues. I have tried the .kdz and the .tot methods of returning my phone to stock firmware. Upon placing my phone into Download mode on both a PC and a laptop (Windows 7 on both) my phone is at best recognized as a USB Modem Phone ADB Port, not the Port (COM LPT) that is required for either method to work. What can I do to get my phone to register as the Serial Port so that the LG Flash Tools will recognize it? (I have installed the most recent LG VZW Drivers and have uninstalled other drivers without any changes). Thanks

!bump having the same issue myself

Beeve said:
I have a rooted Verizon LG G2 that I somehow screwed up when going to Lollipop from KitKat. I have lost my 3G and LTE capabilities, thus no data unless connected to WiFi. From what I have read, it sounds like I need to try to revert to stock and start over. This is where I am having my major issues. I have tried the .kdz and the .tot methods of returning my phone to stock firmware. Upon placing my phone into Download mode on both a PC and a laptop (Windows 7 on both) my phone is at best recognized as a USB Modem Phone ADB Port, not the Port (COM LPT) that is required for either method to work. What can I do to get my phone to register as the Serial Port so that the LG Flash Tools will recognize it? (I have installed the most recent LG VZW Drivers and have uninstalled other drivers without any changes). Thanks
Click to expand...
Click to collapse
Screenshots, exact details, please. Maybe it's a simple driver fix or maybe it's a scary Qcomm diag mode issue (hopefully the good one). You've installed the latest drivers from LG, yes (3.12 or 3.13)? You often (usually) have to manually update the driver in Device Manager. Nothing listed under COM ports at all while the phone is in download mode?
Standard what-have-you:
Install latest LG Drivers (can be downloaded from LG support website).
Open Windows Device Manager and look under COM Ports for the LG device. Right-click on device, choose properties, and change the COM port to Port 41. Even if it says that port is already in use, do it anyways. This the port that LG Flash Tools uses to flash their stock images.
NOTE: Some tutorials will tell you to set your computers date back to make LG Flash Tools work: that is incorrect with version 1.8x and unnecessary, ignore them.
After the port is set to 41, unplug the USB cable from the phone, then open up LGFlashTools.exe. Select the correct VS980 .dll file and select the TOT file to flash. Press OK. Then press the yellow arrow in the upper left of the main LG Flash Tools window. It will think for a minute, then say Ready! or some such crap in the upper left port 41 box. Then you plug the USB cable back into the phone and it will start flashing. You do not have to wait until it reaches 100%, only until the phone fully boots up and presents you with the LG Setup Wizard (1st thing it asks for is your language preference). After you get there just close the LG Flash Tools program.
If it does not successfully flash:
-- Make sure you connect the USB cable directly to a motherboard port, do *not* use a hub.
-- Do not connect or remove others devices to your system until the flashing is done, as I've had that bork my flash before.

info
culot said:
Screenshots, exact details, please. Maybe it's a simple driver fix or maybe it's a scary Qcomm diag mode issue (hopefully the good one). You've installed the latest drivers from LG, yes (3.12 or 3.13)? You often (usually) have to manually update the driver in Device Manager. Nothing listed under COM ports at all while the phone is in download mode?
Standard what-have-you:
Install latest LG Drivers (can be downloaded from LG support website).
Open Windows Device Manager and look under COM Ports for the LG device. Right-click on device, choose properties, and change the COM port to Port 41. Even if it says that port is already in use, do it anyways. This the port that LG Flash Tools uses to flash their stock images.
NOTE: Some tutorials will tell you to set your computers date back to make LG Flash Tools work: that is incorrect with version 1.8x and unnecessary, ignore them.
After the port is set to 41, unplug the USB cable from the phone, then open up LGFlashTools.exe. Select the correct VS980 .dll file and select the TOT file to flash. Press OK. Then press the yellow arrow in the upper left of the main LG Flash Tools window. It will think for a minute, then say Ready! or some such crap in the upper left port 41 box. Then you plug the USB cable back into the phone and it will start flashing. You do not have to wait until it reaches 100%, only until the phone fully boots up and presents you with the LG Setup Wizard (1st thing it asks for is your language preference). After you get there just close the LG Flash Tools program.
If it does not successfully flash:
-- Make sure you connect the USB cable directly to a motherboard port, do *not* use a hub.
-- Do not connect or remove others devices to your system until the flashing is done, as I've had that bork my flash before.
Click to expand...
Click to collapse
LG site has latest VS980 drivers as 2.18
When I plug in my phone and download mode starts, Device Manager will intially show it under 'Other Devices' as 'Android'. Then it will load a generic Android ADB driver. If I hijack the driver install I can manually install an LG Port (COM and LPT) driver, but it will error upon install. It will still show with a yellow exclamation point. I can still change the Port here, but its the error that I think is holding everything up.
I've tried both the kdz and tot method to no avail.
I've tried on a PC, both front and rear USB ports, and a laptop (both USB ports) and no luck.
Any other info I can provide to you? Thanks for helping

Beeve said:
LG site has latest VS980 drivers as 2.18
When I plug in my phone and download mode starts, Device Manager will intially show it under 'Other Devices' as 'Android'. Then it will load a generic Android ADB driver. If I hijack the driver install I can manually install an LG Port (COM and LPT) driver, but it will error upon install. It will still show with a yellow exclamation point. I can still change the Port here, but its the error that I think is holding everything up.
I've tried both the kdz and tot method to no avail.
I've tried on a PC, both front and rear USB ports, and a laptop (both USB ports) and no luck.
Any other info I can provide to you? Thanks for helping
Click to expand...
Click to collapse
Stick to the rear USB ports on the PC, definitely. I've sometimes had it work via a hub, sometimes not (more often not).
So you've chosen the LGE AndroidNet driver, yes? And at this point you don't have the LG Flash Tools open yet, yes? It's best to keep that closed until after you've set the COM port to 41 (probably safe either way, but it does flag a conflict in com ports sometimes, which IME, doesn't matter, but still). While leaving the phone plugged into the USB, is that exclamation point still there after reboot? Screenshots? What error message does it provide under the devices status when you choose Right-click->Propertires(/Alt+Enter)?

Info
I've attached screenshots of the driver error as I install it and its properties. I've also attached shots of using the kdz method showing that nothing is detected when I press the phone information button, and also a shot of the error saying phone is disconnected when starting the flash process.

Beeve said:
I've attached screenshots of the driver error as I install it and its properties. I've also attached shots of using the kdz method showing that nothing is detected when I press the phone information button, and also a shot of the error saying phone is disconnected when starting the flash process.
Click to expand...
Click to collapse
Oh gosh, I'm sorry, I didn't see this reply! XDA sometimes notifies me of replies, sometimes it doesn't. Often it doesn't, grrrr! Are you still stuck here? lol. crap, so sorry.
EDIT:
Oh, when I was mentioning port 41 I think was thinking LG Flash Tools for TOT files, no the 2014 version (which I haven't used in a while).
But that's moot, thanks to the 'device cannot start' error. This should put it into perspective:
- Uninstall all the drivers for that, all LG drivers, all Android drivers, kill 'em all -- this includes uninstalling all LG smartphone software, too. (Note: using something like UninstallTool is always best (IObit has a bloatware-laden tool like that that's free), but surely the Windows Installer should uninstall fine.)
- Reboot.
- Reinstall LG Drivers with their installer.
- Boot device into Android then plug in USB.
Windows should do the usual finding drivers rigamarole, and if it's taking a long time (more than 30 seconds or so), unplug device, the Windows add drivers dialogs should disappear, then plug it back in.
- Check Device Manager to make sure the drivers automatically loaded up, check the details on each of the drivers to make sure it's the LG driver (since you should have no other LG or Android drivers installed at this point it should be).
- If exclamation point next to device, the do the update driver thing and choose the correct LG driver.
- Reboot Windows.
- Unplug device.
- Put device in 'Download Mode' and connect USB (use motherboard ports if on desktop, not hub or case ports; never had port problem on laptop).
- Check Device Manager to see if drivers auto-found it (usually not, for me).
- Update them to LG drivers.
Is the driver still throwing up errors at this point?
Oh, when in Device Manager, select the device, then choose from the menubar View->Device by Connection. It will show the other drivers loaded for that device, and more importantly, it will show just where the device is connected to. A screenshot of that would be mucho helpful if your problem still persists.
Again, sorry I didn't get back to you. D:

Ha ha, I wasn't notified of this either. I never did get it to work. Because what I was really looking for was to get my radios working again, I had another member suggest going to a ;stock-ish' rom and flashing it (xdabbeb) along with the 12b bootstack. Lo and behold this worked for me. I was able to get my phone to show up via ADB so that I could push the files over. I never could get the .tot or .kdz to work, but I don't have the need to continue on at this point.
Thanks for your help though!

hello BEEVE i have screwed my lg g2 in the same way so can you please tell me how did you fix it or give me a link or something anything is fine
thanks in advance

I ended up flashing to a Rom that was based on stock LG. Been awhile so I don't remember. It seemed to help after a while. I also used the LTE Discovery app whenever I wasn't using my phone. The thought was that it would trick it into working. I think what actually ended up working was time. It just eventually started working better. Maybe a combination of everything, I don't know. I no longer use the phone so it's a little sketchy.

ADB Drivers not working Windows FIX

The drivers have been tricky with the Amazon Fire to say the least, and this seems to be because windows recognizes the driver as unsigned. To get around this issue, you will need to temporarily enable installation of drivers that are unsigned.
First go to Settings>Update and recovery.
from there click on advanced startup.
Your PC should say "please wait" then pull up a menu.
In this menu click on "troubleshoot" then click "start up settings"
Your PC will now restart
The PC will now boot into Startup Settings. Click 7 on your keyboard to disable driver enforcement then hit enter.
Your PC will restart once more.
Now your fire drivers should install as they are intended. Allowing installation of unsigned drivers can be a security risk, so once you have completed this process and installed the drivers reboot your PC and windows will automatically turn Driver Signature Verification on once again.

its smart to uninstall the fire drivers and reinstall them using the driver signature mode to make sure theyre installed correctly.
its also worth noting that in my case, the device needed a different driver from the downloaded for each mode (normal/on, fastboot, sideload), there is another thread on here for this but Ill add it here just in case someone else stumbles upon this first.
when installing the drivers in device signature mode, youll want to put the device in all 3 states while in signature mode to make sure you dont run into any problems trying to return the device to stock or moving on from fastboot etc. ( i did this, it was scary..)
1. when installing the drivers in signature mode youll come across 3 different drivers to choose from, the first driver "android ABD interface" is for when the device is in normal/on mode.
2. youll need to next boot the device into fastboot mode, i used the rootjunky amazon fire supertool and booted the device to fastboot, then disconnect and reconnected it to my pc and chose the second adb usb driver "android bootloader interface"
2. after installing that driver disconnect the device from the computer and power it down. power the device into the recovery mode by shutting it down then holding volume down and power (when holding the device in portrait orientation the volume down button is the one to the left) and navigate to the option that requires you to connect your device to a PC to load software (sorry i cant remember what option it is) it will say something like its waiting for a connection, connect the device to the PC and install the final driver "android composite ADB interface" now every facet of operation should have a driver, reboot your PC out of driver signature mode and if you were in the same boat as me, you should be able to sideload back to the android os, and flash roms or whatever else.