Related
I'm new to the Kindle Fire flashing scene, and trying to get Jelly Bean on to my stock Kindle Fire. I've spent several hours on it so far, and haven't been able to get past the first step of getting KFU to see my Kindle Fire, so I can root it or do anything else. To be clear, this is a 1st gen Kindle Fire, running 6.3.1. I've never rooted or flashed it before, and it boots and works perfectly.
The main problem I seem to be having is that Device Manager (on my Win7 PC) shows the device as 'Android ADB Device.' It seems the expected description should be 'Android Composite ADB Device' but I can't get it there. Most of the posts and pages I've seen related to having trouble getting KFU to see a Kindle Fire focus on the drivers not being installed at all, which I don't think is my problem. And I've uninstalled/re-installed them at least 1/2 a dozen times with no effect.
The documentation would seem to suggest that seeing 'Android ADB Device' in the Device Manager implies my device is in Fastboot mode. However, when I uninstall the drivers I see 'Kindle' not 'kindle' in my device manager which suggests normal mode according to the 'Windows Device Drivers and the Device Manager' tutorial. This seems consistent with the fact that my device behaves perfectly normally, so I don't think it's actually in FB mode. Further, the FB tool can't see it.
I've tried connecting to the device from the command line using both the ADB (adb devices) and Fastboot (fastboot -i 0x1949 getvar product) tools. Neither one seems capable of connecting to the device. I also tried connecting the device on a second PC and there too I got 'Android ADB Device', suggesting the problem is device side. I don't have a factory cable to force FB mode that way.
I suspect I'm missing something obvious, but can't figure out what. Can anyone help me out?
It`s probably something strange I`m pretty good at working it out contact me tomorrow via Pm I would be happy to look at it for you. Check your user/.android folder for adb_usb.ini see if it has 0x1949 in it.
Thanks, the adb_usb.ini has the 0x1949 line in it, so that's not the issue. My %userprofile% directory name has a space in it, which initially caused the install_drivers.bat that comes with KFU to have some issues (because it assumes it doesn't.) But everything is where it should be now. Look for my PM.
Re: [Q] Can't get Stock Kindle Fire to show "Android Composite ADB Interface"
I had to used the drivers in superoneclick 2.3.3.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This problem is solved he was running kfu from a temp directory.
Actually, I don't think the problem was the location of KFU. Thepooch gave me a new android_winusb.inf to use along with the KF drivers. The new .inf file had additional Kindle Fire entries for USB\VID_1949&PID_0004 and USB\VID_1949&PID_0007 which the original version I got with KFU did not include. If I pull up the Hardware IDs from the details tab of the device in Device Manager, it showed the PID_0007 version. So I suspect the fact that was missing from the inf file was the cause of my issues (and it's inclusion the solution.) I've attached the updated inf file (with added .txt extension) to this reply.
Beyond that, Thepooch did an amazing job helping me through the whole process. Really went above and beyond. Thanks!
i have managed to sucessfully install a 2nd bootloader, TWRP Recovery, and CM10.1 onto my new KFHD with no apparent problems, following Hashcode's guide at http://forum.xda-developers.com/showthread.php?t=2128175.
I had already set up my system to support developing and debugging the KFHD, including the Amazon-specific Kindle Fire USB drivers; when plugged in, the device showed up in Device Manager as a "Kindle" with a "Composite ADB Interface", and `adb devices` detected the device.
After flashing the CM10.1 ROM I can no longer see my device as anything except an MPT USB Device, and `adb devices` says there are no devices attached.
I have tried both the Google USB drivers and the Kindle USB drivers and Windows claims that neither of them is correct for my hardware. When I check Device Manager, it says the attached device is VID_18D1, PID_6860, REV_0100, which doesn't match any of the device descriptors in either of the driver inf files.
Which driver am I supposed to be using now and how can I get it to install properly?
EDIT: I had forgotten to re-enable ADB Debugging on the tablet after flashing; now it is actually called an "Amazon Kindle Fire HD" and has a different device descriptor:
VID_18D1&PID_6861&REV_0261&MI_01
but still no love from ADB.
Thanks.
I'm having the same problem. No connection to ADB, and MTP only exists as a single file when activating the camera toggle. Frustrating to say the least, but not a deal-breaker.
Oh and a friend has the same problem. I know its not helpful, but atleast you're not the only one
That's really odd as adb works fine for me on Haschode's 10.1 Perhaps try reinstalling the drivers, The adb drivers are - click here
You may need to uninstall the old drivers before these work. Also, goes without saying that you need to enable USB debugging on the tablet!
No more Composite ADB driver after installing CM10.1
apd said:
That's really odd as adb works fine for me on Haschode's 10.1 Perhaps try reinstalling the drivers, The adb drivers are - click here
You may need to uninstall the old drivers before these work. Also, goes without saying that you need to enable USB debugging on the tablet!
Click to expand...
Click to collapse
I installed Hashcode CM10.1 for the first time tonight on an KFHD 8.9.
I have the same problem on both Windows and LINUX: loading CM10.1 on an HFHD8.9 tablet. (No ADB)
I use both every single day on both windows and LINUX so have lots and lots of experience.
In windows after installing 2nd boot /twrp and Hashcode zips (8.1.4.zip, or 8.4.1.zip) I have to use some old windows drivers for ADB and fastboot does not work at all. In LINUX, ABD and fastboot work for both Stock Kindle OS and all of Hashcodes Mod'd KindleOS.zips
If I load Hashcode's CM10.1, I have not ADB on Windows or LINUX ADB Devices shows 123456789ABCDE offline
Recovery shows devices = 123456789ABCDE Recovery
I can push files in Recovery but, not if the tablet boots into OS.
If I revert back to any one of the Hashcode KindleOS.zip images all is well at least in LINUX.
This issue is definately related to something driver wise in the CM10.1 OS.
Regards
I saw this same issue
I had this same issue after installing twrp and CM 10.1 as well. I was fortunate to have a second laptop that had not been used for this stuff before, and once i installed the adb drivers on that machine, had no issue connecting to the tablet from that machine. I still could not connect to it from the original machine. My guess would be to uninstall the ADB drivers from the machine you are using to connect, and reinstall. if that doesn't work, hopefully you have a spare machine, otherwise you might need to look at re-imaging you computer. I happen to keep a stock image file of my laptop in case of hard drive failure or other emergency, so it was about 20 minutes, and i was back up and running.
Please help. I've tried everything I can find on XDA and most of google with no luck. I'm not a NOOB, and have rooted and installed custom ROMS on lots of devices before without any problems, but this has me beat.
Now the basics....I'm running WIN8 64bit, but have a WIN7 32bit laptop.
I have installed the Kindle ADB drivers but whenever I connect the device in ADB mode, it only installs an MTP device. When I click on that and go to Properties-Hardware, it lists 3 Device functions;
Android Composite ADB Interface - Kindle Fire
Kindle - Portable device
USB Composite Device - USB controller.
It seems, no matter what I try, when I run adb devices in CMD (Admin Mode), it list DEVICES FOUND - BLANK.....
What am I doing wrong. All I want to do to start with is ROOT the thing, maybe add Google Apps and then consider a Custom ROM.
If anyone can help me, and please treat me as a complete NOOB, as it seems this is beyond me, I would appreciate it.
Thanks all in advance....
ViPaSoft said:
Please help. I've tried everything I can find on XDA and most of google with no luck. I'm not a NOOB, and have rooted and installed custom ROMS on lots of devices before without any problems, but this has me beat.
Now the basics....I'm running WIN8 64bit, but have a WIN7 32bit laptop.
I have installed the Kindle ADB drivers but whenever I connect the device in ADB mode, it only installs an MTP device. When I click on that and go to Properties-Hardware, it lists 3 Device functions;
Android Composite ADB Interface - Kindle Fire
Kindle - Portable device
USB Composite Device - USB controller.
It seems, no matter what I try, when I run adb devices in CMD (Admin Mode), it list DEVICES FOUND - BLANK.....
What am I doing wrong. All I want to do to start with is ROOT the thing, maybe add Google Apps and then consider a Custom ROM.
If anyone can help me, and please treat me as a complete NOOB, as it seems this is beyond me, I would appreciate it.
Thanks all in advance....
Click to expand...
Click to collapse
Well I too had this issue... Only thing that worked was installing Linux and running soupkit... Trust me this method works flawlessly!
Sent from my Sony Xperia P
ViPaSoft said:
Please help. I've tried everything I can find on XDA and most of google with no luck. I'm not a NOOB, and have rooted and installed custom ROMS on lots of devices before without any problems, but this has me beat.
Now the basics....I'm running WIN8 64bit, but have a WIN7 32bit laptop.
I have installed the Kindle ADB drivers but whenever I connect the device in ADB mode, it only installs an MTP device. When I click on that and go to Properties-Hardware, it lists 3 Device functions;
Android Composite ADB Interface - Kindle Fire
Kindle - Portable device
USB Composite Device - USB controller.
It seems, no matter what I try, when I run adb devices in CMD (Admin Mode), it list DEVICES FOUND - BLANK.....
What am I doing wrong. All I want to do to start with is ROOT the thing, maybe add Google Apps and then consider a Custom ROM.
If anyone can help me, and please treat me as a complete NOOB, as it seems this is beyond me, I would appreciate it.
Thanks all in advance....
Click to expand...
Click to collapse
Silly question but have you enabled adb on the tablet?
Sent from my HTC One using Tapatalk 2
I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten
Try putting it into fastboot again and use these drivers for the device that comes up and see if it will install them:
http://forum.xda-developers.com/showthread.php?p=44446906
Ha, for a minute I thought I saw my name at the end of this post... For the sake of privacy I don't really intend on giving my name out openly to explain why, but if you look at my skype profile it would make sense.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!
kasek said:
STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!
Click to expand...
Click to collapse
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yeah, you're right about Windows 8, it's really a pain in the a**.
I'm gonna switch to Ubuntu once they'll publish my beloved shooters (CoD, Battlefield, ...) on Linux. Fortunately, I'm using Linux since my college time ('94) so I guess the only one having problems will be my wife
stunts513 said:
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
confirm rooted in ver 8.4.6
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~
Zukii said:
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~
Click to expand...
Click to collapse
Shure.
This one worked perfectly for me:
http://forum.xda-developers.com/showthread.php?t=2337634
hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?
kasek said:
I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten
Click to expand...
Click to collapse
I'm like you (8.4.6) somehow I getinto fastboot quite succesfully, I dont know if this is your problem, you seems to try to "fastboot" before you poweroff your device.
don_ernesto said:
hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?
Click to expand...
Click to collapse
Maybe this link could be helpful:
http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
This was exactly what I did.
Good luck!
Hello all.
This is my first post and my first experience with android devices so please go gentle.
I recently purchased for £20 a kindle fire 2nd gen otter.
The reason it was so cheap was that it is stuck in a bootloop.
The friend I bought it from intended to bring it back to life and install CM to the device but never got round to it. So I took it on as my little project.
I have been scrolling through pages and pages of google and this site for research but have hit a brick wall.
I purchased a factory or fastboot cable knowing I may well need it. I also have the original cable.
When trying to boot the device I get the usual kindle and fire logo orange as of it's booting then every 10 seconds or so the screen will go black and back to the kindle fire bootloop.
I have tried to use the normal cable to link to my desktop on windows 7. When doing this the device will not show up in device manager at all.
When I plug it via a fastboot cable it boots into fastboot with a green flashing light on screen and is recognised as an otter prod 04 on device manager.
I have installed the latest sdk. Also fastboot.
I have changed the windows environment variables under path on the PC and can successfully run fastboot in a command window. I can also issue adb commands through also a dos command window so I know both are working correctly on my PC.
I have typed in fastboot devices
I have also typed in adb devices.
When I issue either or these commands my device will not be found through the command window. It just returns a blank.
I know this is due to drivers not working correctly so have opened device manager. Update driver , have tried the android sdk path for drivers have also tried my adb drivers. I have also downloaded the latest Google USB driver and none will install. I have a programme running that allows any unsigned driver to be installed on win 7 so I know it's not that.
All I have returned is cannot install drivers for otter prod. 04
The only thing it will accept is choosing from a list of devices, Then android. And installs as adb device or adb composite device, this is obviously useless as I can't boot device into normal mode to be able to use it as adb or issue commands to it.
I have tried everything. I know this kindle is save able I just don't know how. My end result is make it bootable, root device and install CM
I have trawled through loads of pages of info and tried tried and tried for answers but nothing works. Can anybody shed some light on the issue for me.
Many thanks in advance
Just thought id add, I have also tried all timed variations of holding down the power button
I have also let device run flat and recharge. Have also tried a different PC and USB port.
Hello Vincent,
ADB stands for Android Device Bridge (Just wanted to point that out since you are new to Android).
The ADB Composite Device driver lets your computer and your Kindle Fire device communicate with each other. This includes ADB as well as fastboot.
Install the ADB Composite Device driver in Device Manager and then go to the command line window and type fastboot -i 0x1949 devices and it should now show up in fastboot.
Now flash the stock bootloader, recovery, and system img files to your device. After that, you should see it boot successfully.
Hope this helped, and don't be afraid to ask me more questions about your device!
phiftyopz
Sent from my iPhone using Tapatalk