Database Users

Do I Now Own A Brick?

So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?

Why don't you go read the many threads describing your exact same problem you can fix it.
No you can not return it your warranty is now void.

go into irc with vashypool and he might be able to fix it, donate if u can..

mguinta25 said:
So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?
Click to expand...
Click to collapse
It does seem that this is a very popular problem... I am not sure what amazon's requirements are exactly on returns once bricked especially if you rooted, but I will say with how popular this problem seems to be, I am sure many of the experienced devs on this site are working on a fix for this (hopefully)... If not I would suggest donating to one of your choice if possible for the work that they have already put into it, explain your problem to them and I am sure it would motivate them to come up with an easy fix for this. Whatever happens you should definitely post back with your findings so that you can help the comunity further with knowledge...

it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further

b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
Thank you just had to change the bootmode!

My KF is in a boot loop. Boots to the kindle fire logo, sometime does the animation (highlights letters from right to left), sometimes doesnt.
I've downloaded the KFU and installed the drivers. When I run the bootmode menu, it says ADB Status online, ADB rooted no (even though my kindle IS rooted).
When I try to change bootmode to normal, I get a number of errors:
Error: Could not access the Package Manger. Is the system running?
Error type 2
android.util.AndroidException: Can't connect to the activity manager; is the system running?
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
then it says root activated and that the kindle is running in root mode
<idme> Invalid permission
reboot: Operation not permitted
Then despite all the errors, says kindle has been told to reboot in normal mode.
Kindle still gets stuck in boot loop when I try to power on. I've tried powering off the kindle and then on and retrying, I've tried powering off and disconnecting the kindle and computer, still no luck.
Any advice?

if your kf is constantly rebooting (2-3 sec) read this thread:
http://forum.xda-developers.com/showthread.php?t=1424379
if not and you can connect via kfu set bootmode to normal or do it manually depending on the bootstate your in:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot

FWIW, Amazon are really liberal when it comes to returns on the entire Kindle family.
At a X-Mas Eve party, a friend dedcided it would be a good idea to stream some things with AirTwist and left his KF laying on a table, it recieved some pretty serious damage from being dropped, stepped on and having stuff spilled in it, we dont know how, but Amazon replaced it.
So I would say your best bet in case of brick is to at least simulate damage=\

b63 said:
1. run kfu - select change bootmode - select normal -> success ?
Click to expand...
Click to collapse
Thank you.
I just wanted to mention this "as it might help others": I was stuck in Kindle fire screen, can't boot, and can't see the ADB status.
In the device manager I was seeing the yellow mark.
I restarted the device, then the yellow mark went.
Selected change bootmoe -> normal from KFU (even though the status is offline), and worked!
Thank you again.

Having this issue
b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.

I just wanted to add, I just had a similar issue last night. I was loading up the MIUI ICS rom, wiped like normal and rebooted to the firefirefire triangle. ...Did not like... Anyhow, I was following the many unbrick guides and couldn't get anything to work. The KF would reboot, and my system (win 7 x64), would see the KF as an unknown device with, "error 43", device cannot start. Then the unit would disconnect(windows sound) from usb, and reconnect and disconnect and then go no where. Each time I rebooted the KF it would do the same thing, also would not go into recovery if I hit the power button during boot. I made a factory cable from an extra usb micro cable I had, to force it into fastboot, and it would come up in device manager as an android usb device. still could not see it via adb directly or in KFU. I found it was the android sdk drivers messing it up. I uninstalled the Android SDK and reinstalled the KF driver package that came with the KFU and viola! I was able to run the TWRP install, and successfully get into recovery. I tried the MIUI ICS Rom install again with a new download just in case, but with the same results. wash, rinse, repeat. I restored my previous ROM in recovery and it booted up like a champ. I'm assuming that since the SDK drivers were causing the issue, I could have probably got the fastboot in firefirefire(during boot) to work properly, and not needed the factory cable. Just wanted to share my late evening fun.
Cheers!
Rob

alfy984 said:
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.
Click to expand...
Click to collapse
maybe this helps to sort out the driver issue:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

How I was able to unbrick my Kindle Fire

Hi everyone.
I managed to brick my kindle fire within an hour of purchasing it, but using the suggestions on this forum, I was able to get it back up and running in a few hours.
The method that I had to use involved suggestions grabbed from several threads, so I wanted to provide instructions on exactly how I managed to fix mine in case someone ends up in the same situation as me.
For starters, I had just updated my Kindle Fire to 6.2.1 and I was messing around with trying to get the google app manager installed. I rooted the device, and I was changing permissions in the /system/app directory when the device crashed and became stuck on the boot animation. I did not have TWRP installed at the time.
So if you are like me, or in a similar situation, this may be applicable.
These instructions assume that you have adb on your computer.
First, ensure that you are able to communicate with your device using ADB. Verify this by using the command:
adb devices
Click to expand...
Click to collapse
or by using the kindle fire utility and ensuring that the status is online.
If you are not able to communicate with your device AND have the boot animation (right to left reflection across the "Kindle Fire" logo text), you likely have a driver issue.
Several possible ways to resolve this. First, I recommend going to device manager and unistalling the driver for the android phone adb interface. Unplug the kindle fire and plug it in again. The device should show up without a driver as "kindle". Manually apply the proper driver again and check the adb connection. If this does not work, uninstall the driver again and add 0x18d1 at the end of adb_usb.ini on a line underneath "0x1949" and reapply the driver. Toss in a few shutdowns in between some of these steps if you are still having trouble. Hopefully you now have a connection to your device.
If you are not able to communicate with your device AND do not have the boot animation (right to left reflection across the "Kindle Fire" logo text), your kindle fire is in the wrong bootmode (likely fastboot).
To fix this, download fastboot.exe (if you don't already have it) and run the following command, even if you don't have an adb connection)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
or if that doesn't work
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
Click to expand...
Click to collapse
Your kindle fire should restart and now be stuck at the logo with animation, and you should have the ability to communicate with your device through adb now.
Now, you should download the kindle fire firmware (6.2.1 as of the time of writing this) from http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620. Rename this to update.zip and drop it in the same directory as adb.exe on your pc. Execute the following command.
adb push update.zip /sdcard/
Click to expand...
Click to collapse
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/showthread.php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
Quick note: I wrote this from memory quickly to try to help anyone experiencing problems. I'm no android expert, so if there are ways to improve on this or corrections to be made, please let me know so that the community can benefit.
And I don't want to appear to take undue credit for any of these instructions. I did not come up with anything on this guide on my own, everything came from various threads on this forum. These are just the steps that I followed to successfully bring my kindle fire back from death.

Man, My Kindle Fire does not even get detected by my PC

Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/show...php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-how...03#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
****When I run the fbmode I am getting stuck on the boot logo screen. Can someone please help me??

that is normal - you are in fastboot mode now - adb commands don't work in this mode - fastboot commands do - resume with the description ...

Thanks for your post.
I also "bricked" my kindle the day I got it but my issue was not having the correct drivers installed when I started the rooting process. My drivers would recognize the Kindle when it was booted normally but when it went into fastboot mode the Kindle would just show as "Unknown Device" in device manager. In windows you can't remove the drivers for unknown device so I had no way of backing out the old drivers.
What I ended up doing was grabbing my other laptop and making sure I had the correct drivers installed, then connected the kindle and was able to back it out of fastboot mode.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
umarsl said:
Man, My Kindle Fire does not even get detected by my PC
Click to expand...
Click to collapse
Does it show up as "unknown Device" in device manager?

you can uninstall the drivers
win 7:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
xp:
http://www.techrepublic.com/article/removing-unused-device-drivers-from-windows-xp-machines/6017628

Just wanted to say thanx for the post. I ran into the exact same condition that the op did where I inadvertently screwed up the permissions on the /system/app directory which caused the kf to wig out and brick. I wished I had seen your post earlier because I ended up going to many posts and piecing together the information which was a little confusing at times. The op is great and I just wanted to point out two observations that seemed to me the most confusing working through the issue and getting it unbricked and hopefully will bring some clarity for folks.
1. Understanding the different states of the "kindle fire" logo.
- Shimmering animation and appears to loop = normal boot mode and is the state that you should be able to communicate with adb. This is the state where you can push files to the kf like twrp and fbmode which is what is needed to get kf in fastboot mode when bricked like this.
- The logo is static and does not "wink" out or loop = fastboot mode. This is when you use fastboot commands on your PC to change boot modes and also execute files such as twrp to get it installed once you pushed it to the kf with adb.
2. USB Drivers.
- This can be a real killer. After playing with this for hours, the one thing that I found that helped the most was when the driver stopped working I would unplug the kf from the PC and then hard reboot the kf (hold on/off ~20 seconds) then just plug back in, don't use on/off. Keep the device manager open on the PC and watch. You will soon start to see a pattern when you have the right driver and do this a few times.
Once these things are ironed out all eventually works out. BTW, this occurred after my kf was upgraded to 6.2.2. So the instructions and tools and everything else you will find still works. Good luck to anyone working through this issue. Just remember, if you can communicate with it, it's almost certain there is a way to recover it.

Can't go into recovery...

I'm pretty new at this and I'm having issues going into TWRP.
Whenever I try to install TWRP recovery using the KFU, It looks like it's going through the process, and I do end up seeing the teamwin logo popup and the device boots into the regular kindle interface (so it at least appears that TWRP was installed). The problem is whenever I try to go into recovery using the bootmode menu in KFU, the kindle will reboot, only it won't go into recovery and just goes back to the regular kindle interface. I'm not quite sure what I'm doing wrong. One thing I did notice from looking through tutorials, is that when you reboot the device it's suppose to go to a yellow triangle screen before going into TWRP. My kindle never does this. I don't ever see that yellow triangle screen and instead see the regular kindle fire logo before it loads the regular interface. One other thing is whenever i use the KFU, under "adb rooted:" it says no. I thought after I did the "Permanent Root with Superuser" that it was supposed to say yes. Anyways, any help would be much appreciated.

the yellow triangle is the bootloader (firefirefire) which you'r missing i think
i would take the newest KFU 0.9.2 (attention re-upped yesterday-redownload):
http://forum.xda-developers.com/showthread.php?t=1399889
reading the op (espacially the known tricks) is a good idea
i recommend to extract kfu to c:\ and rename "kindle fire utility" to "kfu" because it don't allways like the blanks in the path
if you are on windows7 you should run kfu and all other commands from an elevated command shell (as administator)
to install the correct drivers (espacially on win7/64bit) by running install_drivers.bat is also a good idea
now you are ready to use kfu and install twrp again
that's the easy way
if it don't work you can install fff (firefirefire - the yellow triangle) manually
ask again about this ...

Thanks for the reply - just got home and I'll try your suggestions.

I'm having the same problem as the OP here.
I originally rooted using BurritoRoot, which worked just fine.
When using KFU, option 5, it seems to run everything smoothly, the downloads are the correct size... But when it goes and starts rebooting at the "DON'T TOUCH ANYTHING! DON'T EVEN LOOK AT IT! OR ELSE!"* screen on KFU, my Kindle boots into the standard Kindle Boot Animation, then the TeamWin splash pops up for a moment.
It then reboots back to the regular Kindle Fire boot animation and KFU says "There we go. TWRP is installed. Ter-dah!"*
When I go to restart the Kindle, however, I never get the FireFireFire icon at all. Just straight into the normal KindleFire stuff.
I decided to take a look at my device manager while my Fire is plugged in. It's listed under "Android Phone > Android Composite ADB Interface"
Perhaps this is the drivers for my Android Phone interfering with the drivers for the Kindle? Iunno. I'm pretty lost on this one.
(* Paraphrased, in my own words, of course)

the driver is the you stated is the right one for kf in normal bootmode
would retry the installation with kfu and watch the output carefully
maybe copy and paste the output for later analysis
seems to be a common problem at the time:
http://forum.xda-developers.com/showpost.php?p=21316424&postcount=49

How about just download the older KU 0.9.1 that's known to work everytime. 0.9.2 had issues installing TWRP.
Once you installed it using KFU 0.9.1, you will have no proiblems getting to your TWRP recovery.

Using the 0.9.1 version did it for me. Thanks a bundle.
Now I'm drooling over ICS on the Kindle Fire. Can't wait for a stable build! +_+

Just follow this guide:
http://rootkindlefire.com/kindle-fire-root/kindle-fire-root-new6-2-1windowsmaclinux/
Sent from my Kindle Fire using xda premium

[Q] Stuck in a bootloop, again! I've tried everything, please help me...

I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over.
So I followed this guide: http://forum.xda-developers.com/showthread.php?t=1399072
Now I'm stuck at the "Kindle Fire" splash screen, been sitting here stuck for 10 minutes now and still going. Anyone to get out of this? Oh and while I'm sitting here stuck at the splash screen, my power button is still orange, if that means anything to anyone?
I also still see "android phone" in device manager and it says my drivers for it are installed correctly.
EDIT: I have KF connected to my PC, when I type in "adb shell" I get this now:
c:\>cd android
c:\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\Android>
Click to expand...
Click to collapse
I also tried following this:
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But when I type in "fastboot -i 0x1949 oem idme bootmode 4000" I just get this, doesn't do anything?
c:\Android>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
Click to expand...
Click to collapse
I also tried reinstalling my drivers. I removed them, restarted my PC and followed these directions again: http://forum.xda-developers.com/showthread.php?t=1431785&page=2
I tried typing in "fastboot -i 0x1949 oem idme bootmode 4000" but still just sits at "waiting for device".

to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19

bal1985 said:
I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over...
Click to expand...
Click to collapse
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.

Refot_Sirk said:
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.
Click to expand...
Click to collapse
so you tried everything that is listed above and nothing worked? by the way what is a factory cable, what does it do and how do you get one?
theres gotta be a way to get out of this bootloop...someone has to know.

b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
ive tried all of those.

for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode

b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
- the first one didn't work.
- the second, the unbrick utility didn't do anything. everything just sits at "waiting for device".
the third, [fastboot] stock 6.2.1 wont work for me. this is what i get when i try that option:
C:\Android>adb push fbmode /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2457 KB/s (510876 bytes in 0.203s)
C:\Android>adb shell chmod 755 /data/local/tmp/fbmode
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Android>
Click to expand...
Click to collapse

b63 said:
for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode
Click to expand...
Click to collapse
yeah im not soldering anything, ill just make things worse. if i could buy one that would be great. my only option is to get my kindle replaced again. no choice. hopefully someone here can help or knows something before i call amazon.

this is the other option - you have to open it:
http://forum.xda-developers.com/showthread.php?p=20565446
would buy a factory cable - there are at least 2 guys selling them here in the forum - one of them is SkOrPn
make a search for factory cable or SkOrPn
it's also good to have one for the future ...
EDIT:
here you can order one:
http://forum.xda-developers.com/showpost.php?p=21309629&postcount=123

u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium

smirkis said:
u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.

Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App

bal1985 said:
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.
Click to expand...
Click to collapse
i think i have read he charges ~ $15 with shipping

G1ForFun said:
Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
im not rooted so adb wont work properly...
i did what you said:
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>
Click to expand...
Click to collapse

b63 said:
to flash the stock stock rom was probably not the best idea....
Click to expand...
Click to collapse
So are threads like this:
http://forum.xda-developers.com/showthread.php?t=1399072
just bad advice? Or is there some inherent risk in flashing or removing any recovery?

bad advice ? don't know - it is written in the title what happens
i think this is for people who want to return the kf to amazon and mostly it works.
if i want to keep my kf and have a working recovery system i would NEVER EVER flash the original stock rom from amazon
there are prerooted stock images available as i mentioned earlier
also a pure update version to 6.2.1 is available (i used it from 6.2 to 6.2.1 - very fine)

There sending me a knew one, I learned my lesson. I'll get more info before flashing. Well at least people know not to use that thread above. He should put a little warning in his thread so no one else gets my promblem.
Sent from my HTC Rezound using XDA Premium

Hi all, I have the same problem, while I was using TWRP I don't know how but I have bricked my kindle, now it is in "kindle fire screen boot loop", when I attach the kindle at computer it is seen, kindle fire utility say:
ADB status: online
Boot status: unknown
I tried to change boot mode from kindle fire utility and it reboot my kindle but in the same situation, so I try to make a factory cable, I connect the red wire with the connector that have not any wire (on the rear), as I read in some threads, but when I reboot kindle pressing power button for 20 sec, with this modified usb insert, and power up kindle....never happens and it still say "kindle fire"
sorry for my english and please help me

[Q] Silly me, bricked my kindle fire after TWRP seemed to fail.

So, as many new KF rooters have, I seem to have bricked my KF. I rooted it just fine, but when installed TWRP through KFU .93 the process seems to have stopped. After waiting over an hour and reading countless "I've been stuck installing TWRP through KFU .93" threads, and seeing many "I switched to .91 and it worked fine" responses, I decided to give that a shot. After unplugging and hard resetting my KF, it is still stuck on the KF logo screen. No yellow box, just the logo screen.
When I plug the KF into my computer, the device is recognized and the proper KF drivers are installed, but I can't get adb to work at all. Every attempt returns a "Device not found" or a "Server didn't ACK." The device does not show up on my list of attached devices, but in Device Manager it is loaded.
I'm unsure of what the next step should be, as I can't get the hardware to respond to anything but resets, and I can't get the software to communicate with the hardware from my PC. I really don't want to admit defeat and contact Amazon.
*edit* Through more research I've made some progress. Opening KFU and selecting the bootmode option, and then when it says "waiting for device" hard resetting the KF and letting KFU change the bootmode to Recovery has done some things. I got a message saying "Failed ..." but it flashed too fast for me to read. Then, upon several restarts, I received a message saying that the KF needed to factory reset, which it is doing now.
As of right now I have a Factory Resetted, working KF. My updated question is now "Where did I go wrong?"
I assume it had to do with TWRP, as it was working until then. Should I redo the whole process using KFU .91 instead of .93? The root went of without a hitch, but the TWRP was what killed me.
Also, do I do Root THEN TWRP, or TWRP THEN Root? I guess I might need Root access to install a Recovery console, but I'm unsure.

use KFU to root, then hit up my gscript install method in the development thread. easy peasy.
but for the record, you were in fastboot, so it won't see adb commands..
fastboot -i 0x1949 oem idme bootmode 4000 maybe woulda saved you. but avoid fast boot entirely, n use my gscript method.

heres how i did it
I was trying to unbridled my kindle fire all last night and about 5hours today.here is how I did it (don't get your hopes up too high,it might not work)
1.Download kindle fire utility
2.Unzip kindle fire utility
3.To install the driver,its easy,just plug in your kindle, when it pops up with the install wizard say pick from the location of: KindleFireUtility>drivers>kindle
4.run kindle fire utility,select 1 then select 1 again
That's it, hope it helps