Related
Ok so I am new hear and I was reading in THIS POST about installing TWRP using the Kindle Fire Utility. So I installed the drivers as directed and I see in my device manager "android ADB device" and in my taskbar I can eject the kindle. In File Manager I do not see the Kindle fire and the Kindle Fire Utility is not seeing my Kindle Fire. I am stuck and cannot post in the above forum because I have not made enough posts. Any help would be greatly appreciated. I would like to install Cynogen Mod to my Kindle fire to be able to access the full capabilities of this wonderful device.
Thank you
a good method to start is using kfu as you suggested but there are some tricks to get it running:
- place it to c:\ and rename it to "kfu" (it don't like spaces in pathname)
- try to install the correct drivers by running install_drivers.bat else install/update them manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
- pay attention on the driver verification level:
http://forum.xda-developers.com/showpost.php?p=22065426&postcount=846
- the drivers are in c:\kfu\drivers\kindle
- right drivers for each mode:
normal & recovery boot -> android composite adb interface
fastboot -> android adb interface
once you got rid of the drivers you have to update the run.bat of kfu to work with burritoroot3:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
now you should be good to go ...
Thank you BB3 I will give this a try later tonight. appreciate the help
man install buritoroot and TWRP(which installs and FireFireFire) by yourself when i tried with the kindle fire utility all got were errors, but when i installed it by myself everythink went smooth. Just find separate guide for every step
1.Root
2.TWRP and FireFireFire
3.CM7
I'm having the same problem as you and it sucks I just want to root it
Hate to necro post, but I'm having the same issue and none of the posted suggestions work. I have the ADB drivers installed (the Kindle is detected as "Android Composite ADB Interface"), but I did not install the drivers using the KFU batch file; I could never get it to stop producing the unsigned error, no matter what system settings I chose for unsigned drivers. I ended up doing a manual driver install and directing the installer at the driver files that came with KFU. Now KFU refuses to "see" the Kindle connected to my system and therefore I can't do a thing with it. I am able to browse the Kindle files in Windows Explorer (should I be able to? I've seen conflicting answers to this), but KFU always reports its ADB status as "Offline". Soft disconnecting the Kindle (hitting the "Disconnect" button on the Kindle) doesn't change anything, except removes my ability to browse the Knidle files (no surprise there).
This is a fully updated (6.3) Kindle and Windows XP. I did attempt to manually do what KFU does automagically prior to finding out about KFU, but that effort produced similar results; the Kindle was never detected by the SDK tools, despite the drivers loading properly. I have also tried multiple USB ports on my system, but they all produced the same results. About the only thing I haven't tried is a different USB cable, but if the Kindle is able to be "seen" by the OS correctly, I don't think the cable is a problem.
Have you tryed rebooting your computer? http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html or http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US nat3mil gives good instruction it helps to watch the video do the step while paused then move onto the next its how I did it the first time the second time I just used the utility was easy peasy cause drivers were already installed and functional
Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.
cogadh said:
Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.
Click to expand...
Click to collapse
If you followed the instructions to the t like not plugging in your device until you have the drivers installed .then you may have something on your computer preventing adb try the 6.2.2 method
http://m.youtube.com/#/watch?desktop_uri=/watch?v=AZ88CYWv0FU&v=AZ88CYWv0FU&gl=US or just keep looking for something that works cause people miss steps all the time sometimes its persistence or trial and error that gets results I'm very surprised your not seeing anything in device manager that applies to your kindle mine installed some drivers immediately when I connected it I had to change them to root it but it did show up in the list of devices as well as appearing next to my c drive as a kindle for SD card access but I'm on windows seven anything I connect does something.
No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.
cogadh said:
No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.
Click to expand...
Click to collapse
Could be your machine but don't use the utility and when you do put twrp on if ya get there use 2.0 the older version people are having trouble with the new one http://www.techtuple.com/477/how-to-root-kindle-fire-6-3-easily/ this is done through cmd without utility. Original thread here http://forum.xda-developers.com/showthread.php?t=1568340
About all the advice I can give you all else fails use another computer windows 7 machine things are more straight forward than xp
Edit: just a side note a lot of people are bricking their devices I keep remembering the Christmas story be careful you'll shoot your eye out also some people I believe are having success opening kfu attaching thier fire while off then powering up the kindle
I read somewhere that the utility doesn't work for xp wish I could find the post I think you need to push the files the old way using command prompt and you will get it sounds like your drivers are there but utility is useless
If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Thanx soup better said than what I was trying
if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.
First time i've ever rooted a kindle and i had the same problem.
To fix this just go to device manager and uninstall the driver and then unplug and replug in your kindle then run the utility.
oh no trouble at all rooting rooted rommed and rockin here took the 6.3 ota this morning with 5 mins I was rooted with fff twrp then went back to 1 of my restore points of cm7 after a backup of 6.3 thanx tho
soupmagnet said:
If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
If all newbs do no other work but learn to use fastboot and adb it would save save a lot of grief for them and the ones helping them. jes sayin..
Thepooch said:
if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.
Click to expand...
Click to collapse
This will only work if the device is booted to a point where it will receive adb commands. Otherwise, use "fastboot devices". Sometimes if you are stuck at the bootloader it helps to shut your device down completely and restart before issuing fastboot commands.
Beyond that, it's a driver issue.
Sent from my Amazon Kindle Fire using xda premium
I had that same problem., but then I uninstalled the current drivers for my kindle altogether, and disabled them, then I ran install_drivers .bat again, then it worked.
Kindle Fire running KANG CM9
New developer, working on my own custom rom
i bricked my kindle fire ... like flash update.zip and then my fatal mistake i reboot kindle then i was bricked so hard please help me
a bit few information !
what exactly have you done ?
what display on kf ?
fff & twrp installed ?
kfu available ? - and moved and renamed to c:\kfu ?
status in device manager ?
os/bit ?
i install update.zip from kindle fire utility
then i reboot. it sticks on second kindle fire logo whit lower light ,no TWRP,no fff
that means you tried to restore it to pure stock
do you want to return it ?
if not gimme a pm and we can try to get to fastboot mode - reinstall fff & twrp - then it's possible to reinstall a rom of your choice
if it's not possible to get to fastboot then you'r up to a factory cable - sorry
can u give me skype on pm i will show you
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
Follow the following after you KF to your PC:
Adb kill-server
Adb start-server
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Good luck
Sent from my Amazon Kindle Fire using Tapatalk
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
Try to use KFU to install Windows driver and changing the booting mode to normal
Sent from my Amazon Kindle Fire using Tapatalk
josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
furthermore check the adb_usb.ini in the .android folder in your personal folder
it should include 0x1949 (and i use to add 0x18d1 also)
would not use the sdk at all - you can save a lot of space and the drivers of the sdk don't have all the necessary entries
the sdk also messes around with the adb_usb.ini and deletes your allready made entries
would recommend to use kfu only (like in the linked in post) - you don't even have to run it but:
- the drivers are in c:\kfu\drivers\kindle and have all necessary entries
- the tools directory (c:\kfu\tools) has all commands you'll ever need (you can run all your adb and fastboot commands from here manually)
I'll try these suggestions out. I've done a wide array of changing in the .android fold and keying in the 01x.... but it hasnt been to any avail. I'll try it in the order that you've introduced.
I've tried the above mentioned and was looking in the actual driver android_winusb file and I can see that the hardware id listed on it and the actual hardware id that my kindle shows are different. It has the same VID but the PID ends in 005 instead of the 006 that is supposed to.
So I created a copy of this and altered the driver file to reflect the PID as 005, and was able to get the driver file to eventually show up as an ADB Device in the hardware description with the driver, but it still would not interact with ADB itself.
adb_usb.ini usually reflects the vid only and is necessary for adb to work
the only other vid's i'hv read that some had success are 0x006 and 0x0e79
you may add them also to adb_usb.ini - if it don't help it don't harm
furthermore would recommend to kill the adb server every time if you have changed something at the drivers with "adb kill-server"
So far, I've gotten Windows to recognize the kindle as and ADB device. Trying to get the .android file to reflect the change hasn't worked at all. The VID isn't really much of and an issue. It's the PID that seems to be different from any post that I have seen. I wish that I could force ADB to recognize the connection, but that's a bar above me. I'm an amateur at best compared to some of the people.
I'm really vying on the power of XDA here; because, this problem is so similar to the other issues that are similar with the driver issue, being stuck at the kindle fire homescreen. However when I tried the update in twerp of the update.zip file, it somehow screwed the pooch on my adb. I have a backup both on the kindle and my computer. I just can't do anything until I get ADB to recognize my KF.
maybe give firekit a try ? no windows - no drivers
http://forum.xda-developers.com/showthread.php?t=1430038
Try to use another computer. If this impossible, Install new Windows in VMWare and connect Kindle to virtual machine. Then use KFU.
Well, I've tried firekit, and ubuntu wouldn't even recognize my kindle fire... I'm half tempted to use the usb trick, but I really dont want to start taking the kindle fire apart if i dont have to.
Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.
josh24923 said:
Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.
Click to expand...
Click to collapse
What exactly do you see when you start up your KF? The stock "kindle fire" logo or the yellow triangle logo? Does the screen ever go black before getting "stuck" on the logo?
If all you ever see is one of these logos without it ever going black, it's in fastboot mode. You'll never get adb to recognize your KF in this state regardless of what drivers are on your machine. adb will only see your device when it's in recovery or booted into the OS. In fastboot mode, you can only issue fastboot commands to the KF.
You say in post #15 that you've gotten Windows to recognize it as an ADB device. What device is shown in the the device manager when you connect it? Please be specific.
This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse
Thread Moved
As the contains no development.
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
androitri said:
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
Click to expand...
Click to collapse
from the notification area click on more , security , ADB on
ADB doesn't see my Kindle HD 7
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:23 AM ---------- Previous post was at 08:55 AM ----------
tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
Well, I added the magic line you suggested, and this now works for me. I'm surprised that running "C:\android-sdk\tools\android.bat update adb" (the corrct directory for me) didn't fix this.
Ah well - so many things to learn. Thanks for your guidance.
Pat
tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
This didn't do anything for me. Any other ideas?
Driver install problem
dotvezz said:
This didn't do anything for me. Any other ideas?
Click to expand...
Click to collapse
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.
PMcHargue said:
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.
Click to expand...
Click to collapse
USB hubs cause problems, just sayin'.
I went round and round with this until I decided to plug directly into the PC and avoid the hub. Worked perfectly.
---------- Post added at 05:37 PM ---------- Previous post was at 05:33 PM ----------
If you have tried everything and still no workie, make sure you aren't using a USB hub. ADB wasn't listing it as a device but yet I was able to see it in Device Manager and even transfer files to/from it. Once I eliminated the USB hub, all was well. ADB now sees it.
dburckh said:
This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.
Click to expand...
Click to collapse
Thank you so much for this, I was fially able to get ADB to recognize my Fire and root it.
reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse
Mine was doing the same thing
Follow the link that the OP gives(i'll also post it)
Follow the instructions in BOTH the links below. The second link are instructions to get kindle fire add-ons(including usb drivers) for SDK.
https://developer.amazon.com/sdk/fire/connect-adb.html
https://developer.amazon.com/sdk/fire/setup.html#step6
I had the same problem, with adb, not finding my Kindle Fire. I downloaded the current Android SDK und used that ADB without changing anything. Works fine for me I also just copied the adb.exe in the same directory as rootqemu.bat and replaced the old one ( old ~159kb new ~796kb ).
Very helpful
Hello All,
I could use some assistance. I have ADB installed properly and the drivers for the Kindle Fire HD from this thread installed also. My issue is the Kindle Fire HD driver states:
Android Composite ADB Interface
The device cannot start (Code 10).
I am using the driver from 12/3/2012 version 1.2.0.0 and I get this error code if I have the Fire directly connected to the usb port on the pc or through the usb hub. Same issue over and over. Even if I attempt to use other Kindle Fire HD drivers.
Also, I have made the change in the adb_usb.ini file.
Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This ABSOLUTELY helped me! Was bangin' my head against the wall for a WHILE before I this little nugget got me going! THANK YOU!
My issue is fastboot takes commands but says flashing not allowed
Hi, I have no issue connecting to my Kindle Fire using ADB under Ubuntu using a USB cable, no drivers were needed.
However I'm trying to get ADB over WIFI to work, but I get "unable to connect to 192.168.1.234:5555"
Has anyone managed to do ADB over WIfi or is it not implemented on the Kindle Rom? Thanks
Hi, I'm currently struggling to get kfu to work on my KF2, i've got access to the root thanks to Qemu but kfu keeps saying <waiting for device>.
I've read and read and read post after post and I'm pretty sure I'm confusing myself now,
I have the Android SDK software installed including the Kindle Fire drivers, in Windows 7 Device Manager I have "Kindle Fire > Android Composite ADB Interface" (Amazon 1.2 driver) and Portable Devices > Kindle" ( Microsoft 6.7.7600) after modifying "android_winusb.inf" and "adb_usb.ini"
Nothing I do seems to put it into fastboot mode, is there something i'm missing, do I need to copy something to to the kindle??
Thanks for any help in advance
Factory USB Cable
crankyy said:
Hi, I'm currently struggling to get kfu to work on my KF2, i've got access to the root thanks to Qemu but kfu keeps saying <waiting for device>.
I've read and read and read post after post and I'm pretty sure I'm confusing myself now,
I have the Android SDK software installed including the Kindle Fire drivers, in Windows 7 Device Manager I have "Kindle Fire > Android Composite ADB Interface" (Amazon 1.2 driver) and Portable Devices > Kindle" ( Microsoft 6.7.7600) after modifying "android_winusb.inf" and "adb_usb.ini"
Nothing I do seems to put it into fastboot mode, is there something i'm missing, do I need to copy something to to the kindle??
Thanks for any help in advance
Click to expand...
Click to collapse
You need a Factory USB Cable: http://forum.xda-developers.com/showthread.php?t=1392693
There is a link to purchase one.
Is there no other way?
Sent from my GT-I9100 using xda app-developers app
Kindle Fire 2 Fastboot
crankyy said:
Is there no other way?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Maybe. If the Kindle Fire 2 has been rooted and you have the Android SDK Installed.
Try plugging the Kindle Fire 2 to USB:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
Respond with the results.
Well that got it into fastboot but in "Device Manager" it came up as "Otter2-Prod-04" with a yellow exclamation mark.
It couldn't find the correct drivers, what should it be displayed as in device manager?
Sent from my GT-I9100 using xda app-developers app
I've just reslised fbmode will not run ftom shell it comes up with an error
Sent from my GT-I9100 using xda app-developers app
Android Composite ADB Interface
crankyy said:
Well that got it into fastboot but in "Device Manager" it came up as "Otter2-Prod-04" with a yellow exclamation mark.
It couldn't find the correct drivers, what should it be displayed as in device manager?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If you have installed the correct driver, you will see Android Composite ADB Interface
In the Windows Device Manager. If you need a driver, here: https://dl.dropbox.com/u/54456659/usb_driver.zip is the latest ADB Composite Driver
Offered by Android SDK Community. This driver is Universal to over 1,000
Android Devices, including the Kindle Fire 2. If you do mind me asking
what are you trying to accomplish exactly?
---------- Post added at 03:39 PM ---------- Previous post was at 03:36 PM ----------
crankyy said:
I've just reslised fbmode will not run ftom shell it comes up with an error
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I see. This is due to two problems:
1) Your ADB Composite Driver is not installed: https://dl.dropbox.com/u/54456659/usb_driver.zip
2) You do not have Root Permissions Installed on the Kindle Fire 2 http://forum.xda-developers.com/showthread.php?t=2069117
I will try the drivers you suggested but my KF2 is definatly rooted
Sent from my GT-I9100 using xda app-developers app
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
crankyy said:
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
Click to expand...
Click to collapse
When you say "KFU“ I hope you do not mean kindle fire utility. That program/tool is for the original kindle fire, you are lucky you have not gotten it to work. It will definitely brick your device should you successfully run it.
Sent from my KFJWI using xda premium
Follow Up
crankyy said:
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
Click to expand...
Click to collapse
crankyy,
This is why I keep asking "what are you trying to accomplish exactly"?
If I know, then we can give you exact step-by-step, thus get you back in
business. Onemeila is correct "I hope you do not mean Kindle Fire Utility....".
This utility will Brick your Kindle Fire 2, it was designed for the Kindle Fire HD 7"
ONLY. Do not attempt to PUSH the system.img from KFU, it will permanently
Brick your Kindle. So, what are you trying to accomplish, exactly?
i'm a noob, please go easy on me. (this is my first post)
i rooted my kindle 2 days ago with qemu and bin4ry root, then installed twrp recovery. being an idiot, i wiped the system before i put the cm10 zip on the kindle, so i had no os. i tried sideloading the cm10 file onto the kindle, but my computer would not recognize the ADB, even though it had drivers installed and was working previously when the kindle was in the normal boot mode.
i read in this thread (http://forum.xda-developers.com/showthread.php?t=2117224) that you can put your kindle into fastboot mode from the twrp command prompt, so i did that, thinking that the adb drivers would work if it was in fastboot mode. they did not.
i have tried installing the adb drivers through the kfu, the android sdk, and every other way i have seen. when my kindle is plugged in, device manager calls it "otter2-prod-4" i have the fastboot with the blinking green light. i do not have a fastboot cable, though one is on its way. if i could get it to show up in adb, i could at least get it to boot into recovery and start again from there, but none of the methods i've seen are working for adb driver installation. can anyone help?
p.s. i am running windows 8 x64
Drivers ok, ADB doesn't show my KF2
Hi, my KF2 is bricked and i'm using a fastboot cable, i think the driver is ok but running the command adb devices i don't see any device connected.
{
"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"
}
ktron said:
Hi, my KF2 is bricked and i'm using a fastboot cable, i think the driver is ok but running the command adb devices i don't see any device connected.
Click to expand...
Click to collapse
You are using a "fastboot" cable, aren't you? You may want to use fastboot commands as well.
Right Driver / no devices attached
soupmagnet said:
You are using a "fastboot" cable, aren't you? You may want to use fastboot commands as well.
Click to expand...
Click to collapse
I have the right driver but i don't see any device, how can you help me?
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
prokennexusa said:
crankyy,
This is why I keep asking "what are you trying to accomplish exactly"?
If I know, then we can give you exact step-by-step, thus get you back in
business. Onemeila is correct "I hope you do not mean Kindle Fire Utility....".
This utility will Brick your Kindle Fire 2, it was designed for the Kindle Fire HD 7"
ONLY. Do not attempt to PUSH the system.img from KFU, it will permanently
Brick your Kindle. So, what are you trying to accomplish, exactly?
Click to expand...
Click to collapse
Hi, i have the Fastboot cable, right driver but when i run the command Adb Devices i don't see my KF2, how can you help me??
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
ktron said:
I have the right driver but i don't see any device, how can you help me?
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Hi, i have the Fastboot cable, right driver but when i run the command Adb Devices i don't see my KF2, how can you help me??
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
Click to expand...
Click to collapse
You quoted my post. Didn't you read it as well?
adb reboot bootloader
After I run adb shell su -c "reboot bootloader" it will put KF2 into fastboot mode and try to install usb drivers again and then fastboot can't find the device. The device is visible as a otter2-prod-04 in device manager. I've got windows 7 installed. Any idea appreciate it.
Thanks
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Click to expand...
Click to collapse
Thanks for that, I had to install drivers again when I was in fastboot mode and yours worked great. Appreciate your reply.
stunts513 said:
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi, this issue sounds just like the one I am having.
I have tried your drivers with no luck.
My KF2 shows up in device manager as OTTER2-PROD-04
And:
USB\VID_1949&PID_000A&REV_0100
USB\VID_1949&PID_000A
I took your drivers and copied them over the drivers in the programme files \ amazon \ drivers folder, rebooted and reconnected but still shows up as this OTTER2
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