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!
Related
I'm currently trying to root my kindle with 6.2.2 with my windows XP Computer.
I've downloaded the most recent KFU and the 2 other files listed in the KFU post
KFU is currently located at c:\KFU
When I run the instal drivers.bat file It yells at me and tells me that the Google driver is unsigned. No problem, Plugged in the kindle and when the "install drivers" box came up I selected the C:\KFU\Drivers folder
Everything installed fine, When plugged in I get the USB Storage under USB devices and Anroid ADB Device under phones
when I run KFU it shows that ADB is offline
I've tried with the Mass storage stopped, still shows ADB offline.
Does anyone have experience getting KFU to work in XP?
Should I give up on the simple utility and do it from the CMD line with ADB? (I just feel safer having a script run becuase it gives less chance for error / skipped steps)
I've also tried on my mac, but sadly my older mac doesn't support KindleWater or ADB for that matter
PS as a background I have rooted 2 phones in the past and Custom ROM"d 1 of them.
Hi there, sorry for being another needy noob, but such is my reality. I've spent the last couple days reading and trying stuff out. A friend gave me it and I opened it up without signing into an amazon account. KFU shows offline and unknown boot status. I wasn't able to run the KFU install.bat because XP blocked it for being unsigned without any warning popup that allowed me to choose, which didn't respond to changes made in the drivers signing section. I was able to manually install by plugging it in, going into device manager, finding kindle, right click, blah blah blah. It shows that I'm in normal mode there with "Android Composite ADB Interface" but KFU still shows offline and unknown. KFU is in a c:\kfu folder as directed and I downloaded the fbmode file into a software folder within that. In the cmd prompt I copied and pasted "adb push C:\kfu\software\fbmode /data/local/tmp/" at C:\kfu\tools and get "*daemon not running. starting it now* daemon started successfully* error: device not found". Can I just drag and drop the fbmode file into a kindle folder through the windows "my computer" section where it shows as J:? Is that "/data/local/tmp/" part the file path for where I'd have dragged it in the kindle? I googled what that meant and didn't find anything I understood. Taking off that part brings up "Android Debug Bridge Version 1.0.25 and a list of commands for the program. I tried the next step in the guide without the "/data/local/tmp/fbmode" part and it made a recovery folder in my kfu folder with a fff.bin file in it. Figured I was causing a cascading **** storm and registered here to start this thread. I'm sure I'm missing something obvious but I thought the guide went from perfectly understandable to immensely complex from one step to the next. To be honest I just don't understand all the little shortenings everyone uses in posts and need specific step-by-step. Do I need to fully unlock this stock kindle with an Amazon account to put it in some sort of receptive mode? It shows a USB connected mode just fine since getting the ADB drivers installed, but now I'm stuck. Thank you so much for any help you send my way. Ben
No part of the /data partition will appear on your Windows system. You must use adb to push the fbmode file.
I think this is going to be another device driver problem. Right click on the Android Composite ADB Interface in the device manager, go to properties and take a look at the hardware IDs. You should be seeing this...
USB\VID_1949&PID_0006&REV_0216&MI_01
USB\VID_1949&PID_0006&MI_01
If those values don't match, uninstall those drivers using the directions here...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Try disconnecting and reconnecting the device and find the proper interface. The hardware IDs above must match on the interface where the device drivers get installed. That's the only way adb will be able to "talk" to the device. This might help you as well...
http://forum.xda-developers.com/showpost.php?p=26999297&postcount=37
give this a try it will rule out xp`s unsightly driver issues http://forum.xda-developers.com/showthread.php?t=1882565
I installed the driver provided with the KFU before I ever hooked it up to the PC. Started the utility but it says ADB status offline and boot status unknown. So I checked out some youtube videos and I noticed everybody's kindle in device manager shows up as ADB Composite Device or something similar. Mine just shows up as Kindle. I for the life of me can't get it to change after many tutorials on how to. No matter what, even after uninstalling, it automatically goes to Portable Device Kindle. Can somebody help me please? I know somebody will just point me to a different thread but if you could, just let me know what I'm doing wrong and how to fix it. Thanks.
Is it a first gen. Kindle? http://forum.xda-developers.com/showthread.php?t=1923010 and second post here goes into driver specifics http://forum.xda-developers.com/showthread.php?t=1552547 .
Yes it's a first gen Kindle that I just bought and I installed the exe that was included in the KFU.
Just followed that guide through and it did nothing. The one thing it says though is that if the driver doesn't install correctly, uninstall the driver and check the delete software option. I'm not getting that option at all. Still doesn't show up as android phone or adb composite device. One thing I did though, is run it as an administrator and that at least got ADB to say online. Boot status is still unknown though.
buffnutz1 said:
Yes it's a first gen Kindle that I just bought and I installed the exe that was included in the KFU.
Click to expand...
Click to collapse
Must be a sign You mean the drivers run.bat file? What os ?
Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.
ray8888888 said:
Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.
Click to expand...
Click to collapse
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.
stunts513 said:
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.
Click to expand...
Click to collapse
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?
ray8888888 said:
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?
Click to expand...
Click to collapse
it should be fine to use now, that's just stock rooted, you might wanna consider disabling ota's or flashing another rom onto it but its fine how it is.
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