Develop Bugs

Kindle Fire. Device Manager Sees but Kindle Fire Utility Doesn't

My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?

Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.

Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!

i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks

Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?

Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?

Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.

The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.

Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?

What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt

Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.

Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?

GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!

[Q] Kindle fire stuck in re-boot mode

Not sure what's going on here.. I unrooted my kindlefire with update.zip but I forgot to wipe to factory reset before i flashed update.zip and when i rebooted my kindle i noticed that A ! symbol popped up with "Sorry" that says "The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again" That isn't the only problem, i click force close and another prompt comes up saying "The process android.process.acore has stopped unexpectedly. Please try again" It waits a few seconds, then proceeds to do a fast reboot? It comes up with the yellow kindle fire and immediately after it boots up it shows the errors.
Not sure what to do. Tried installing TWRP but the kindle doesn't stay on long enough so right now I'm pretty unconvinced of anything..
Any help would be greatly appreciated.

You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...

Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
I'm not sure how to get there.. I don't have any form of backup installed. It's on the complete default rom
Edit: Found out how to get to factory reset, only to discover that I need a 40% charge, when mine is less than 5% and won't charge any more because of my problem

Still haven't figured this out. Can't use my kindle at all until this is fixed :/

iKrotos said:
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
Click to expand...
Click to collapse
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.

kinfauns said:
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
Click to expand...
Click to collapse
Read the beginners guide for KF, Found about about ADB fastboot etc. Going to install ADB tomorrow and try to figure this all out. Thanks.

I can't do this. It's been over a month. My kindle is finished..

iKrotos said:
I can't do this. It's been over a month. My kindle is finished..
Click to expand...
Click to collapse
"I can't do this"
Well that explains everything, doesn't it? It's a good thing you explained your problem in such great detail or I might spend time trying to help you fix your Kindle thinking you "could" do it. Phew. Saved us all a lot of time, thank you.

I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?

LaszloToth said:
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
Click to expand...
Click to collapse
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.

Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2

soupmagnet said:
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Click to expand...
Click to collapse
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
Thanks again fro the help!
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
kishorev said:
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.

Had a similar problem of rebooting every 10 sec or so..I left it on charge overnight and it worked..it got charged decent enough for me to help recover it..
Just try charging it overnight it might just work..I always feel using factory cable shd be the last resort
Sent from my Kindle Fire using Tapatalk 2

LaszloToth said:
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Click to expand...
Click to collapse
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.

soupmagnet said:
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
Click to expand...
Click to collapse
So instead of using fastboot to wipe the user data, I should use it to install TWRP? Can you give me the fastboot command for that? Or can I do that with KFU once I plug in the factory cable?

http://forum.xda-developers.com/showpost.php?p=23747804

Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.

same problem with kindle fire.
LaszloToth said:
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
Click to expand...
Click to collapse
hi, i am new here and i got exact the same problem with you, i just ordered the factory cable, can you please give the step by step procedure on solving this problem with the factory cable. your help will be appreciated, thanks.

Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
:good::good::good::good::good::good: works for me thank you

ok, today i had the same problem because i didn't wipe the factory restore!
The solution WASN'T the Factory Cable (I was considering buying one)!
Very easy:
Linux and SOUPKIT! were the solution, when the tablet boots up immediately hit the install recovery, after installing recovery, just set to boot into recovery.
Now is very much you can do (ex. wipe everything and than install update.zip all over)
Very much thank you to the guy who made SOUPKIT! (u've saved my S many many times )

[Q] Demo Kindle Fire ADB Help

I know that this has been gone over multiple times, but I can't get any of the other threads to help so I figured I'd post my own.
Basically, I worked for Best Buy for awhile, rooted the demo Kindle Fire we got at work and that was that. So I figured I could get a demo Kindle Fire off Ebay and just get it rooted and Rom'ed. Well, I can't get the damn thing to be recognized by my computer in ADB.
I've literally tried everything, I've changed the android_usb.ini file to include the 0x1949 and the other file to have the kindle fire in it. Then I tried to point the Kindle to the new file that was changed. Everytime I update the driver it stays as the MTP Device and I can't get it to ADB Composite. I've tried the KFF and that doesn't work either. Uninstalled drivers and reinstalled with no success.
Also, it seems that every time I plug the Kindle into the computer it reinstalls the Drivers.
I do have a Factory Cable on the way so I'm hoping that that will work for me if nothing else does.
Thanks in advance all.

As long as the factory cable you speak of is the fastboot cable that is all you will need. Simply get it into fastboot, flash FFF and TWRP, transfer a Rom.zip and Gapps.zip to the sdcard, do a full wipe in recovery minus the sdcard/external storage. Flash Rom, flash Gapps and reboot. if you get it properly into fastboot your driver will read Android ADB interface. If your running windows 8 you need to disable driver signature verification in order to install the driver.

Thepooch said:
As long as the factory cable you speak of is the fastboot cable that is all you will need. Simply get it into fastboot, flash FFF and TWRP, transfer a Rom.zip and Gapps.zip to the sdcard, do a full wipe in recovery minus the sdcard/external storage. Flash Rom, flash Gapps and reboot. if you get it properly into fastboot your driver will read Android ADB interface. If your running windows 8 you need to disable driver signature verification in order to install the driver.
Click to expand...
Click to collapse
Thanks! It should be here today so I'm excited. I read all of what you've posted multiple times now in other threads, I just haven't been able to get it into fastboot so I'm really hoping that fastboot cable works for me.
Thanks for the quick reply Pooch.

Well. It's bricked. Couldn't get it to boot into twrp. After trying for awhile I decided to just flash fff as I knew the recovery was there. I get nothing now. Completely black screen and no led on power button. I've tried the whole firekit short usb with no luck. It gets past the first part but then just sits at waiting for device. So I'm lost. Is it fried?

[Q] Can't find Kindle Fire on PC when in Recovery

Hello everyone!
A few days ago, my Kindle Fire crashed during use and I could not get it to reboot. I reflashed the ROM I used that I kept in /sdcard (now I realize that I should have done a factory reset beforehand, but, alas, that's in the past) and could not get it to boot, so I connected the thing to my PC and tried to just get the stock ROM back on with KUU, but it failed to write it while in fastboot. In fact, fastboot seems to fail to write any update.zip, as doing it from terminal gives me the error "android-info.txt or android-product.txt not found in archive". Of course, now I decided to be an idiot and perform a wipe, including the ROM from my /sdcard folder in it. This wouldn't be as big a problem if I had access to ADB; however, I don't. When in TWRP 2.5 Recovery, the device doesn't show up at all under Device Manager, neither as "Kindle" or "Android ADB Composite Device". Therefore, I can't use adb push to have a ROM to flash. Seems peculiar to me, since I can access fastboot just fine, albeit under the name "Kindle Blue Fastboot Mode | Gen 1" instead of "Android ADB Interface" (I assume FFF 1.4a is installing some driver hidden in it's files?) I also attempted to use USB Mount to just drop the zip onto the Kindle, but it did not show up on my PC either.
This leaves me with three possibilities, unless you guys think of a fourth one.
1. Activate ADB for my Kindle in recovery, somehow (you'll need to direct me how to even touch this).
2. Use fastboot to put a ROM on (again, either someone needs to show me how to get fastboot flash update update.zip to work, or possibly there's a way to push files in here too?)
3. Use USB OTG in TWRP to install a ROM. I'm not even sure if this is a thing that's supported, but I'll try after I get a little more juice in the tablet (Edit: doesn't seem to work, sadly :crying
Thanks so much for viewing this thread, I hope one of you has some insight on how to fix my problem

Demostrs said:
Hello everyone!
A few days ago, my Kindle Fire crashed during use and I could not get it to reboot. I reflashed the ROM I used that I kept in /sdcard (now I realize that I should have done a factory reset beforehand, but, alas, that's in the past) and could not get it to boot, so I connected the thing to my PC and tried to just get the stock ROM back on with KUU, but it failed to write it while in fastboot. In fact, fastboot seems to fail to write any update.zip, as doing it from terminal gives me the error "android-info.txt or android-product.txt not found in archive". Of course, now I decided to be an idiot and perform a wipe, including the ROM from my /sdcard folder in it. This wouldn't be as big a problem if I had access to ADB; however, I don't. When in TWRP 2.5 Recovery, the device doesn't show up at all under Device Manager, neither as "Kindle" or "Android ADB Composite Device". Therefore, I can't use adb push to have a ROM to flash. Seems peculiar to me, since I can access fastboot just fine, albeit under the name "Kindle Blue Fastboot Mode | Gen 1" instead of "Android ADB Interface" (I assume FFF 1.4a is installing some driver hidden in it's files?)
This leaves me with three possibilities, unless you guys think of a fourth one.
1. Activate ADB for my Kindle in recovery, somehow (you'll need to direct me how to even touch this).
2. Use fastboot to put a ROM on (again, either someone needs to show me how to get fastboot flash update update.zip to work, or possibly there's a way to push files in here too?)
3. Use USB OTG in TWRP to install a ROM (I'm not even sure if this is a thing that's supported, but I'll try after I get a little more juice in the tablet)
Thanks so much for viewing this thread, I hope one of you has some insight on how to fix my problem
Click to expand...
Click to collapse
"fastboot flash update.zip" doesn't work on the KF btw.
I haven't had a chance to look at hardware IDs or see how KFU's drivers are configured these days, but it may serve you well to use fastboot and install an earlier version of TWRP. Maybe a 2.4.x version to start out with...

soupmagnet said:
"fastboot flash update.zip" doesn't work on the KF btw.
I haven't had a chance to look at hardware IDs or see how KFU's drivers are configured these days, but it may serve you well to use fastboot and install an earlier version of TWRP. Maybe a 2.4.x version to start out with...
Click to expand...
Click to collapse
Rolled back to 2.4.4.0 and 2.2.2.1, no dice
Edit: I did buy two new Micro-USB cables, should I wait until I get them to try and get my Kindle recognized by my computer? This person did the same (http://forum.xda-developers.com/showpost.php?p=25896517&postcount=12) and I feel like when I can get ADB to run, I can fix everything from there. It just seems odd to me that Fastboot would be recognized and the tablet can charge when in recovery on the same cable, it just can't access ADB.

Got the new cables today, still nada. Tried on my Win8 desktop, Win7 laptop, and Ubuntu Laptop, and none of them even showed that a device was plugged into it in recovery. Any other tips before I try to get Amazon to replace this thing?

Any further instruction I should try? I really want to get this thing in operation...

Attempted to root, maybe bricked, can I recover?

Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!

enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.

monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.

enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?

monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.

enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.

monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.

enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.

monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!

enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)

monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.

enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.

monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.

enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...

enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.

monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.

So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?

enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!

monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.

enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.