Database Users

[Q] Managed to screw up my computer's drivers somehow, need help

I was trying to use the Kindle Fire Utility to push the market onto my Fire since I was having issues doing it otherwise. It actually ended up pushing all the gapps onto my phone, an Eris, and at some point I guess messed with the drivers, because after I (understandably freaked out and) unplugged my phone the utility couldn't find any devices at all. It was about then that I noticed that my computer has apparently ceased to recognize my Fire being plugged in or unplugged at all. It doesn't show up on the devices window or the device manager at all. It's like it never existed. I have no idea how to fix this with the drivers being completely missing from device manager and the computer not even giving any hint that it's noticed when the device is plugged in, and I'd really like some advice here.

http://forum.xda-developers.com/showpost.php?p=20729347&postcount=5
http://forum.xda-developers.com/showpost.php?p=20761609&postcount=12

My fire runs perfectly fine, and those posts are about bricked fires. My issue is that my computer isn't detecting my fire at all.

ketchupface said:
My fire runs perfectly fine, and those posts are about bricked fires. My issue is that my computer isn't detecting my fire at all.
Click to expand...
Click to collapse
It's gotta be in there somewhere, but it might not be named Kindle. Look in device manager under every option.

the posts are fine and meant to help you
if your kf is not recognised then you have a bad driver installation
the posts shoud help you to sort it out - follow the second post - it worked x times
if you have done and have any problems ask - i'm willing to help if i can

If the device is missing from device manager, and your computer is refusing to show the installed drivers for it, I would try this:
Open an elevated command prompt and type this:
set devmgr_show_nonpresent_devices=1
Then go to start and into the search bar type in devmgmt.msc
Then when device manager opens, click "view" at the top, and click "Show hidden devices"
Any non-present devices that have had drivers loaded for them in the past should show up here. You should be able to right click on the kindle and click uninstall and with any luck when you plug your kindle back in, it will pick it up again.
Best of luck

judasthehelpful said:
If the device is missing from device manager, and your computer is refusing to show the installed drivers for it, I would try this:
Open an elevated command prompt and type this:
set devmgr_show_nonpresent_devices=1
Then go to start and into the search bar type in devmgmt.msc
Then when device manager opens, click "view" at the top, and click "Show hidden devices"
Any non-present devices that have had drivers loaded for them in the past should show up here. You should be able to right click on the kindle and click uninstall and with any luck when you plug your kindle back in, it will pick it up again.
Best of luck
Click to expand...
Click to collapse
This worked! I deleted every instance of "Android ADB" entry, every "Kindle" entry and the entry with the kindle's name and when I plugged it back in it was detected. Thanks!

I'm glad I could help, you seemed very stressed out in your first post

[Q] Can't install win usb drivers on XP. Tried everything

I've used different guides, searched to death, but cannot seem to get the driver installed on this XP computer. Some of the guides seem to be for Vista or Windows 7. Is there a good video for XP, or one that relates to the driver issue?

xp is a good choice for this because you don't have to care about the uac (user access control)
maybe this one helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

I was in the same boat as you but luckly i had a netbook with windows 7 starter that worked for me. I couldn't find any help for XP either.
Sent from my Kindle Fire using xda premium

Unfortunately, that did not work for me. I'm fairly computer savvy, but this has stumped me. I will keep looking.

I was getting rather upset because I could get the USB drivers installed, but ADB still wouldn't recognize my Fire.
Is this the problem you guys are having? Or can you just not get the drivers to install at all?
It turned out that my problem was a complete, "I'm an Idiot!" deal. Especially because I'm a System Engineer and should know better than to overlook the steps I did. But, in very few of the instructions of how to load the drivers, does it tell you where the adb_usb.ini file needs to be located. I was thrown off because with the Kindle Fire Utility (ver. 0.9.3 at least), it comes located in the drivers folder. Plus, just about every time this file was mentioned, it always had a big thing about adding the 0x1949 device ID, which caused me to miss the couple times I ran across instructions that said where it needs to be located.
The adb_usb.ini needs to be, in XP, located in the ".android" folder that is located in your username's folder. For example, if I am logged into my computer as PBFred, the path would be the following...
C:\Documents and Settings\PBFred\.android
I also ran into one other problem. When you manually select the path for the driver, android_winusb.inf, (which you can place where ever you want) XP shows you a list of compatible device drivers. The correct device driver, "Android Composite ADB Interface", isn't listed unless you uncheck the box that says "show compatible devices only". If you don't uncheck that box, it just lists "Android ADB Interface", which is not the right one.
Once I did that, I was good to go. The only issue I have now with the driver is for no apparent reason, it asks for the driver to be reinstalled about half the time I plug my Fire in, even though I haven't plugged any other devices in inbetween. But since the path to the driver is still saved, it only takes 2 seconds.
I hope this helps you guys out.

I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.

DukeSilver79 said:
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
Click to expand...
Click to collapse
I don't quite follow where you are stuck.
Does running the command "adb devices" list your device? If so, your USB drivers are installed correctly. Which means that the version of Windows you are running pretty much doesn't matter any more.

I think I soft bricked the KFHD 7', help pls.

So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.

procter said:
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
Click to expand...
Click to collapse
No.. and really you shouldn't be doing these things without a fastboot cable.. What do you mean by the driver does not take effect? It sounds like you need to fix the bootloader. I would head over to the Kindle Fire First Aide thread and talk to Chris and see if he can help you out. Is adb working or have you checked? If adb is working then you will be able to enter fastboot without the cable..

I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2

procter said:
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?

lacoursiere18 said:
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
Click to expand...
Click to collapse
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.

procter said:
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
Click to expand...
Click to collapse
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well

lacoursiere18 said:
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
Click to expand...
Click to collapse
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.

procter said:
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
Click to expand...
Click to collapse
A lot of it is the same I am sure some aspects of the GUIDE do not work but as far as installing ADB drivers it is good. Did you uninstall it and also hit delete all software with driver?

did u recover
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:

KFHD 7 Stuck at splash screen
techdeisel said:
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
Click to expand...
Click to collapse
Hey. I am having a terrible time getting my KFHD 7 back to stock. I used KFFirstAide to root it and when I went to restore it back to factory settings it ended up with the holo launcher lock screen and the android start screen. Has no notifier bar at top or menu bar at bottom. Lock screen let's me go online, to the camera, or just unlock. Don't know what happened! It's not recognized in ADB but shows up on computer as Kindle. I just want it back to stock so I can use it again! PLEASE HELP!!

In my situation, when trying to update the "Kindle" driver from Windows device manager, use the option to let you choose install driver from a list of devices instead of pointing to the directory where you have the adb driver (it will always tell you can't install even if u point it to the right directory).
In my case, I had all the drivers installed already, so when I use the option to install from the list of known devices, I can choose so"Android adb" or sth similar in that list. And after that you will be able to restore the adb connection.
Sent from my SPH-L710 using Tapatalk 2

the the reason your kindle cannot communicate properly with your computer is because it is soft-bricked, only way to recover from a soft-brick is with the use of a fastboot cable, if you are partially soft bricked...ie boot is intact and functional but system filesystem is corrupt you may be able to access fastboot with the use of a fastboot command

Like I tell everyone, go here to solve your problem.
Sent from my KFHD using xda premium

[Q] Help with USB Drivers for Nook Simple Touch

The current project I am trying to work on is trying to get USB mode to work on a rooted NST with NookManager. I have found a guide somewhere else, but it requries pushing boot and uimage files from ADB. I have tried everything I could, even using Ubuntu in Vbox but I haven't been successsful yet. For whatever reason, the USB isn't being read in Vbox-Ubuntu correctly and can't be mounted.
I have done everything I could to install the USB drivers on Windows properly, but I haven't had any luck. I have scoured the forums, but I couldn't find anything. What I need help is how to uninstall what I have reinstall correctly. I have tried the uninstall fuction in device manager but if there is a better way of doing this I haven't found anything. Can anyone help? Point me in the right direction at least? I hope if i can at least get the drivers installed correctly and adb devices to read it properly, I can figure out how to do everything else. It's just that one hurdler I'm having issues with.
I am running win 8.1 pro but willing to use ubuntu if necessary.
I should also mention what I have done. I Have altered the android_winusb.inf and the adb_usb.ini files, which sort of worked, but I still have yellow exclamations ove the device names.

Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage "Android Devices" (or "Android Phones") with a device listed under it.
If you have yellow, what driver does it say it has loaded?
It should be using WinUSB.sys
What does it say when you try to reload drivers?
If it suggest "Composite USB Device" accept that.
If you are using the latest version of adb.exe (819,200 bytes) it will already have the vendor ID in it for Nook.
You will not have to modify adb_usb.ini (not that it will hurt anything).
The first step is to get the driver installed (obviously).
abd.exe should be able to connect.
If you have a problem you could try omaplink.exe as an independent check of ADB.

Renate NST said:
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage...
Click to expand...
Click to collapse
Well to say the least, it's mess
Anyhow, the category is "Other Devices - Nook SimpleTouch"
Driver Provider: Unkown
When I try reinstalling it says:
Windows found driver software for you device but encounterd an error while attempting to install it.
Android Composite ADB Interface​The system cannot find the file specified​I have done the Advance Restart for Win 8 that disables the driver signatures and I still get this message.

The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll

Renate NST said:
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Click to expand...
Click to collapse
It's in the adt-bundle folder under ~sdk/extras/google/usb_driver. Should it be in the i386 folder?

I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.

Renate, your questions helped me figure it out.
Yes all the files are where they are suppose to be in the same relative position that you outlined.
So i did this to get the "Have Disk Button"
I first did a right click "Update Driver software
1. Browse for driver on computer.
2. Clicked "let me pick from a list of device drivers"
3. A windows that says "Select your device type from the list below:"
4. List gives options includes Show all devices, ADB Interface, Android Device
5. I chose Android Device: It gave me a selection of devices and Nook Android Interface was there. I selected that and installed.
6. I then went to the command tutorial and typed in adb devices and I got the serial numbers.
I wrote this out for future refence for myself, and in the hopes it will help someone else.
thank you so much Renate! You were a huge help! I can't wait to start using your USB Host!
Renate NST said:
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Click to expand...
Click to collapse

I'm glad that worked.
I actually meant saying even more Nos until an actual "Have Disk" button appears.
Window caches the driver inf files and you could have had a bad one.

[Solved] Windows unable to install MTP driver

Hello guys!
I have already read some topics on this forum but it is my first message.
As indicated in the title, I cannot connect my Nexus 4 on my computer using MTP. This computer is running Windows 8.1 Update 1. So far I have tried every method I have seen on the web so I am a little bit desperate.
I have tried to plug my device on other computers and it was automatically detected on Windows 7, Windows 8.1 Update 1 and Ubuntu 14.04.
On my computer, as it does not auto-configure MTP I have tried to install ADB drivers, hoping it would help me. Universal ADB drivers, Naked Drivers and drivers from the SDK didn't changed anything. I also tried changing USB port.
It always recognised my phone as a "Nexus 4" in the "Other devices" section of the Device Manager (I do not have "Android Device" section), except in when MTP + debugging are activated. Then I have both "Nexus 4" and "MTP", in "Other devices" section.
It does not work in PTP mode either and I also tried uninstalling/reinstalling the Nexus Root Toolkit, even if I do not see how it can help...
One last point: I have the "connected as multimedia device" notification on my Nexus 4 when MTP is activated, even if it's not recognised by Windows.
Do you have any idea of what I can do?

Have you tried Nexus 4-specific drivers? Try following this guide.

Marvlesz said:
Have you tried Nexus 4-specific drivers? Try following this guide.
Click to expand...
Click to collapse
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes

Bartimoot said:
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes
Click to expand...
Click to collapse
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Here is another post from another forum that has something you could try:
still1 said:
ttwiitch said:
still1 said:
1. make sure Settings ->Storage -> Menu[3 dots on top right] -> USB Computer Connection is MTP
2. USB debugging is disabled (if you ever enabled it)
3. make sure the drivers installed is MTP drivers rather than adb device(you do this when you unlock/root nexus)
point 3 is important. thats the reason why its not getting detected
Click to expand...
Click to collapse
2. Where in setting do I check for USB debugging?
3. How do I check this? (I'm not rooted)
Click to expand...
Click to collapse
2. developer option.. if you have not enabled developer option then you wouldnt have enabled USB debugging. so skip this
3. Connect your nexus to PC-->Go to Control panel-->device manager
you will see something like Android adb in device manager
Right Click and click "Update device Software"
Click "Browse your Computer for driver Software"
Click "Let me Pick from a list of device drivers on my Computer"
Click Next, for the device list shown.
Click to expand...
Click to collapse
Tell us how it goes..

Thank you for spending some of your time to help me Marvlesz, I really appreciate.
Marvlesz said:
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Click to expand...
Click to collapse
Yes, I saw it worked for a lot of people, for what I have read, but it seems that I am not that lucky
When picking from the list, I tried from the Android Device section and it displays "Unable to find any drivers for this device". Same Results in “Mobile devices”.
When I try “Show all devices”, I have a lot of possibilities. I just tried “MTP Device” from both “Standard MTP-Compliant Device” and “Standard MTP-Compliant devices” sections, and it displayed “The install class is not present or is invalid”
Am I cursed?
I was wondering, is it possible that the problem is coming from my hardware? Or its drivers? (Those for the motherboard maybe?)
EDIT: I just found this thread : http://forum.xda-developers.com/showthread.php?t=2493734
I will try it and I will keep you updated when it is done.
EDIT 2:
So I tried the solution... and it worked! :good:
I had the N version of Windows 8.1, mainly to avoid useless software like Windows Media Player, and it was the exact problem.
Sorry for taking a little of your time, and thank you again!

No problems, I'm glad you had it fixed.