Develop Bugs

[Q] Kindle Fire shows up as a Disk Drive in devmgr, can't update driver

Windows 7 has my Kindle Fire listed as a Disk Drive, and when I try to update the driver so that ADB can read it Windows won't allow me to because android_winusb.inf is not a Disk driver.
Then I tried to uninstall the Kindle Fire driver and it simply immediately reinstalls itself the moment I restart the computer or plug the device back in, and it reinstalls as a disk drive...
Basically, I need help figuring out how reset the way Windows 7 recognizes my Kindle so that I can install the updated android_winusb.inf
How I got to this point
I installed the Kindle Fire on my Windows 7 computer through the device manager using the android_winusb.inf driver from the android-sdk/extras folder.
Couldn't connect to adb, but then I realized I needed to add the: [source]
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_0
to it in order for ADB to recognize it. So I modified android_winusb.inf and added the two lines. But, now I can't install the new modified driver because of what was stated above...​

Take it out of USB mode. Is it listed in Other Devices or Android Phone?

It is listed under Disk Drives (Device Manager) - which is also the reason why Windows 7 now won't allow me to update the drivers using android_winusb.inf - this is regardless of whether the sd card is mounted or not.
android_winusb.inf isn't a Disk driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Had this same problem, its because your computer was set up to run ADB before so it recognizes the kindle as Android and auto installs drivers that you have for it, unfortunately these drivers don't let you use ADB, go to android phone at the top and follow the steps to update the driver on the device under that instead.

Get this working
did the original poster get this working?? My machine will only recognize it as an MTP device now ... how do I stop it from applying those drivers??

[Q] How to work with windows adb to root phone?

Hello!
Well, I've followed your tutorials and installed android SDK which came in a .zip and I just extracted it to my C:\ directory.
But the phone just doesn't connect! See the image below please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have usb debbuging enabled in my nexus and I am freaking out with this eheh. Little help please xd

Did you boot into the bootloader?
Sent from my Galaxy Nexus using Tapatalk 2

Assuming you've already unlocked the bootloader.
Turn off your cell phone, press Vol+ & Vol- while holding both keys press and hold PowerButton you'll boot into bootloader, now connect your devices to PC and run the command "fastboot devices" if you have all drivers correctly installed you should see something like:
List of Devices
"Devices: xxxxxxxxxx"
Click to expand...
Click to collapse
if you don't see any devices that means either drivers are not installed or you're not booted into the bootloader, but if you see your devices connected use the "fastboot flash recovery recovery.img" once the installation is finished boot into recovery and flash the SuperSU(root).zip
Peace,
L4.1

Rayaxe said:
Hello!
Well, I've followed your tutorials and installed android SDK which came in a .zip and I just extracted it to my C:\ directory.
But the phone just doesn't connect! See the image below please.
I have usb debbuging enabled in my nexus and I am freaking out with this eheh. Little help please xd
Click to expand...
Click to collapse
Try using "fastboot devices" to see if it lists your phone. Fastboot only works when you're in bootloader mode. "adb devices" will list your phone when bored into the os.
Sent from my Galaxy Nexus

thanks guys, it worked ^^

[Q] Windows 7 doesn't recognize phone

I have a stock AT&T HTC One X, trying to root my phone.
I've downloaded everything I need, but I can't connect my phone via USB. I've downloaded various drivers from here and HTC Sync Manager, but that doesn't help.
All I'm getting is this whenever I connect via USB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, every time I install a driver, a command prompt window shows up with the words "Access Denied", spazzes out, and disappears. The installation never said it was finish, so I'm guessing it never worked.
Without it, I can't get to the command prompt of the ADB and Fastboot.
On my Windows 8 laptop, I'm capable of connecting with the right drivers, but Windows 8 isn't compatible with fastboot.

Vegeto30294 said:
I have a stock AT&T HTC One X, trying to root my phone.
I've downloaded everything I need, but I can't connect my phone via USB. I've downloaded various drivers from here and HTC Sync Manager, but that doesn't help.
All I'm getting is this whenever I connect via USB
Also, every time I install a driver, a command prompt window shows up with the words "Access Denied", spazzes out, and disappears. The installation never said it was finish, so I'm guessing it never worked.
Without it, I can't get to the command prompt of the ADB and Fastboot.
On my Windows 8 laptop, I'm capable of connecting with the right drivers, but Windows 8 isn't compatible with fastboot.
Click to expand...
Click to collapse
Wrong forum go to Evita go to ONE XL forum. This is for Endeavoru

Bricked, Crashed, Corrupted? Really lost

Hi everyone,
the reason I'm starting this thread is because after two days of trying to solve my issue by reading threads and trying various things, I'm still stuck. The scenario is this, my Kindle Fire HD is stuck at teamwin screen and I cannot access TWRP. I have no idea if this is soft-bricked or corrupted or whatever. What happens when I switch on the tablet is that I get the orange Kindle Fire logo, then the blue Kindle Fire logo and then teamwin screen which flashes every 5 seconds and is stuck there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
During this process, the Device Manager from Windows 8.1 successfully recognizes the tablet as 'Android Composite ADB Interface'
If I start CMD as Admin mode and key in 'adb kill-server' and then 'adb devices' I can see the device listed as '0123456789ABCDEF recovery'
Another issue is that when I go into 'adb shell', all the commands I type, I get '/sbin/sh: command not found'. I also tried 'KindleUnbrickV1.1.jar', but every option I select I get <waiting for device> and stays like that. I left it overnight.
I also tried Kindle Fire Utility, but was unsuccessful as well.
At this point I don't think there's anything else I could do and I guess it's time to say goodbye to my little fella. At least managed to finish univ with it.
If anyone has some opinions or suggestion, you're more than welcome to do so and they will be highly appreciated. By the way, I don't have any important data on the tablet so it's ok if I need to format it without taking backups.
Kind regards,
/pH-

7 in or 8.9 in?
Sent from my XT1028 using Tapatalk

7" Kindle Fire HD. Actually I think I posted in the wrong forum.

this thread can now be closed - managed somehow to fix the issue

Question Help

guys I can not reconnect the phone to the PC I get this error

If you're using type C - type C cable, try a type A - type C.

i am using the classic type c cable

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What does classic mean? Just make sure there's usb A on the computer side... Do you have USB debugging and OEM unlocking enabled in developer settings?

yes all active

You didn't install a fastboot driver..

I had the same problem i applied this:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com

Stef_ said:
I had the same problem i applied this:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
This resolved the same issue for me as well. Odd though, because it was working fine for me a couple of months ago.

This is a windows problem, and as others stated downloading the fastboot driver does work, I had to manually install it as an optional update through Windows Update last time it happened, but I prefer to use Linux, as this is one of those "just works" scenarios on there (albeit MSM tool requires Windows, and unaware of a workaround)