Develop Bugs

Kindle Fire Stuck Logo

Hello all, please forgive me as I know there are a ton of threads with a similar title but I'm completely new at this and I'm frankly at a loss.
My Kindle Fire is stuck on the Kindle Fire logo screen after trying to unroot it. I know I messed up by trying to wipe everything off of it and rebooting it. I'm hoping someone can walk me through a step by step guide on how to unbrick it (I am completely dumb with this and probably shouldn't have attempted to unroot it in the first place).
I recieve the following error when trying to do anything in the KFU or the Unbrick Utility:
exec '/system/bin/sh' failed: No such file or directory (2)
Unable to access the internal portion of the Kindle Fire, when I try to "Browse Files" it's grayed out with no option of looking into it. When looking at the device itself, it's on the dimmed light Kindle Fire logo with the power button showing green.

well unfortunately you will need twrp and fff back on your device to do it... if you cannot get it into fastboot very likely you will need a factory cable to do so found here http://forum.xda-developers.com/showthread.php?t=1392693 after you get twrp and fff back on simply wipe everything except your sdcard or external storage and flash this rom http://forum.xda-developers.com/showthread.php?t=1439916 then you will be all refreshed and can decide where to go from there...
Edit:looks like at this point he has 5 cables maybe less left best jump on that as soon as you can... in the meantime keep it on the stock wall charger as not to compound the situation with a depleted battery...

Thepooch said:
well unfortunately you will need twrp and fff back on your device to do it... if you cannot get it into fastboot very likely you will need a factory cable to do so found here http://forum.xda-developers.com/showthread.php?t=1392693 after you get twrp and fff back on simply wipe everything except your sdcard or external storage and flash this rom http://forum.xda-developers.com/showthread.php?t=1439916 then you will be all refreshed and can decide where to go from there...
Edit:looks like at this point he has 5 cables maybe less left best jump on that as soon as you can... in the meantime keep it on the stock wall charger as not to compound the situation with a depleted battery...
Click to expand...
Click to collapse
Thank you for the response.
How does the cable work though? Does it work just by plugging it into the device? By using it and the Kindle Fire Utility I would be able to install the TWRP at that point? Also how do I flash a rom onto it when it is in TWRP? Kinda confused what flash means sadly..

Dont feel bad.. this is what I had to do to get the cable to work for me when I tested it: shift + right click on the tools folder in kindle fire utility.. select open command window here...hold down the power button on the kindle for 30 seconds to power it off , dont plug it in yet type
Code:
fastboot -i 0x1949 getvar product
in the terminal hit enter.... then plug the kindle in ... it will then power on in fastboot and return product:kindle in the terminal... this is if all your drivers are installed correctly if this is the very first time you have tried anything with your kindle I suggest you get at least a 2 gig usb flash drive and go this route....
Originally Posted by Thepooch
its all set up
Here try this iso http://db.tt/KDNzyCTP
Instructions:
1. Download this http://www.pendrivelinux.com/ universal usb installer is the program
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565
just pm me when you get to this point and I will help you do the rest factory cable in hand and running live usb...this live usb will allow you to boot linux on your machine if your on windows all the up front configuring is all ready done.. in your spare time while you wait I suggest some learning first here http://forum.xda-developers.com/showthread.php?t=1552547 and here http://forum.xda-developers.com/showthread.php?t=1638452 there is alot of content here but these are the best guides on the net bar none...

foxdieabetes said:
Thank you for the response.
How does the cable work though? Does it work just by plugging it into the device? By using it and the Kindle Fire Utility I would be able to install the TWRP at that point? Also how do I flash a rom onto it when it is in TWRP? Kinda confused what flash means sadly..
Click to expand...
Click to collapse
to better answer this question the cable forces the devices into fastboot so that things like bootloaders and recoveries can be easily replaced when there doesnt appear to be another way to do it. As far as flashing goes it pertains to flashing a rom flashing a recovery ect. In most instances it just means replace without a better term for it...

[Q] Bricked ... tried most things ... need some guidance

Hi,
Some background - I've been tinkering with android roms on phones for a while, and thought i'd give it a go on my Kindle, which I hardly ever use with the stock rom. I have a very low level of understanding regarding rooting, etc., but generally I'm good at following instructions (until now!)
So everything was going along nicely. Because I hardly ever use the device, I decided to do a full wipe before installing the new rom. Then, when I went to flash it, it turns out that I had forgotten to copy the new rom onto the SD card. In a moment of temporary insanity, I turned the device off (don't ask me why, I can't explain it).
On restart, the device now gets stuck on the logo screen. KFU tells me that the device is online, but boot status is unkown, and it can't change the status (although it does reboot the device when I try to put it into fast boot mode- but it doesn't actually 'fastboot').
If I try to reinstall TWRP or anything else, I get the 'exec system\bin\sh failed' error. The Kindle unbrick utility is unable to help.
I did some research and it kept pointing me to a factory cable, which I duly bought off eBay. When I use the factory cable, the only difference is that the boot sequence is slightly different (different levels of backlight) and KFU can't recognise the device at all - it says its offline.
I have no idea if the factory cable I have bought is any good - it might be complete rubbish.
Can any tell me if there is a simple option I have missed? Is trying fixes through Linux the only option? Will I have to open my kindle to fix it? I've already spent a heap of time on it, and I'm just about ready to call it a paperweight. Any help would be greatly appreciated.

I`m a little confused so file me in. Do you have access to recovery? with your type of error "exec system\bin\sh failed" a factory cable is indeed needed to reinstall twrp and the bootloader, unless you can access TWRP and mount your sdcard and transfer a rom. If that is not possible then you have some kind of mounting issue. So I still wonder what happened to your recovery and your bootloader? For me yet not everything is meshing to well. No bootloader, no acces to recovery, kindle just boots to logo and no further. Does the logo flicker and brighten and dim at boot? Yes very likely you will need to run linux on a live usb then run soupkit on it. Still you may still need a real factory cable not one half **s one from ebay you can find that here http://forum.xda-developers.com/showthread.php?t=1392693 from user @SkOrPn no one can beat what he does I`m sorry. As for linux and soupkit the where and how is here http://forum.xda-developers.com/showthread.php?t=1850038 . Unless you get easily confused then try the iso I created with some fairly easy instructions soupkit is ran already simple create boot and use you can find that here http://forum.xda-developers.com/showthread.php?t=1413358 post # 7 make no mistake that this is only for the kindle like the last person I helped with this setup. This is your best route to get your kindle fixed sounds like it could still be a combined effort cable and soupkit .You will know when you hook your kindle up and run some of the features in soupkit if your device is truly online or if a cable is needed. If you run my iso teamviewer is also installed so it provides a nice edition for assistance if you want someone to see what you see. If you choose to run soupkit then the par for instructions differ from those of my iso.

Thepooch said:
I`m a little confused so file me in. Do you have access to recovery? with your type of error "exec system\bin\sh failed" a factory cable is indeed needed to reinstall twrp and the bootloader, unless you can access TWRP and mount your sdcard and transfer a rom. If that is not possible then you have some kind of mounting issue. So I still wonder what happened to your recovery and your bootloader? For me yet not everything is meshing to well. No bootloader, no acces to recovery, kindle just boots to logo and no further. Does the logo flicker and brighten and dim at boot? Yes very likely you will need to run linux on a live usb then run soupkit on it. Still you may still need a real factory cable not one half **s one from ebay you can find that here http://forum.xda-developers.com/showthread.php?t=1392693 from user @SkOrPn no one can beat what he does I`m sorry. As for linux and soupkit the where and how is here http://forum.xda-developers.com/showthread.php?t=1850038 . Unless you get easily confused then try the iso I created with some fairly easy instructions soupkit is ran already simple create boot and use you can find that here http://forum.xda-developers.com/showthread.php?t=1413358 post # 7 make no mistake that this is only for the kindle like the last person I helped with this setup. This is your best route to get your kindle fixed sounds like it could still be a combined effort cable and soupkit .You will know when you hook your kindle up and run some of the features in soupkit if your device is truly online or if a cable is needed. If you run my iso teamviewer is also installed so it provides a nice edition for assistance if you want someone to see what you see. If you choose to run soupkit then the par for instructions differ from those of my iso.
Click to expand...
Click to collapse
No, I can't access recovery at all. When I use the factory cable, there is no flicker, but all other ways (standard cable, no cable) there is a flicker and it brightens. Either way, it just hangs on the logo.
I suspect that the factory cable is not all it should be ... I will probably try the @SkOrPn option first, then work my way through the other options you mention. I had kind of figured from reading other posts that this would be the case ...
Thanks for taking the tiime to help.

There is no flicker because your likely in fastboot the lack of recognition is drivers which can easily be solved using linux and soupkit. Otherwise straighten out your drivers in windows by running the driver bat packaged with kfu. If your on XP it`s a fight to the death to try to sort out unsigned drivers on that os. Sometimes I can get it fast other times it`s pointlessbut a huge hassle nonetheless. Attempt to fix your drivers while using the factory cable you have maybe you will get lucky.

Fixed! Thanks so much!
I used your pre-installed ISO and it was a piece of cake. Initially, I had the device connected over the factory cable and it wasn't recognising it, but when I swapped to a standard cable, suddenly I was able to reboot into recovery straight away. Rom mounted and installed, and I have a new tablet!
Definitely appreciate all your hard work!

That`s great I`m happy you had good success!!

KF Stuck at Logo - Sorry

I know this has been covered thoroughly in this forum multiple times, and I have really tried to read as many threads as possible before asking.
I rooted my device months ago and finally got a Nexus 7 and want to give my KF to my kids but wanted it stock first. I must have done something in TWRP that removed my bootloader.
I have tried the unbrick tool, I ordered a factory cable from Skorpn (awesome work btw) and by using KFU, my PC can finally see my Kindle.
The problem I'm having is that none of the commands are working and it looks like the bootloader is either bad or completely gone.
It used to turn on and the logo stayed bright. After I used the factory cable it now turns on, blinks, and goes dim.
All the drivers loaded correctly and KFU see's it online.
When I try to reinstall TWRP through KFU it downloads, but is stuck at waiting for device.
***********************************************
* Activating Fastboot (4002) *
***********************************************
2433 KB/s (510876 bytes in 0.205s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
After reading further, I think I formatted too much and wiped the SD card partition. It doesn't seem like there is a bootloader at all.
Did I miss something in all the reading?
Thanks.

So after doing even further reading I found
http://forum.xda-developers.com/showthread.php?t=1638452
I connected the factory cable and the logo is now staying brightly lit, so I assume it's in FB Mode.
I downloaded TWRP based on the link and FFF, but now I don't know what to do with them.
I went to ADB's site and installed SDK, but I'm not sure how to get the cmd portion to sideload TWRP and then FFF.

I'm doing my best to following along in the instructions and went to the ADB site and installed SDK.
I saved it to my C drive but when I try to do the following, along with "adb devices,
c:\Android\android-sdk-windows>
I get:
'adb' is not recognized as an internal or external command,
operable program or batch file.
Update:
NVM, I had it in the wrong directory.
Once I got that figured out, I did an "adb devices" and no devices came back. Of course I have the factory cable connected and I'm not sure if that matters.
Update:
Ok, now I used a standard USB and it sees my device, but now the logo went back to going dim after reboot.

So it looks like my problem is fairly common, however forum searches don't seem to be helping.
It looks like I wiped too much in TWRP.
Now that I finally figured out ADB, I'm confused about the factory cable.
When it's connected ADB does not see my device but the logo is lit bright yellow. When I use a standard cable ADB sees the device but the turns on and goes dim but the logo is still there.
I've downloaded the ZIP files for TWP and FFF, but I can't seem to figure out how to side load them no matter what I do.

I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.

Copcheck said:
I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.
Click to expand...
Click to collapse
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.

leroy329 said:
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.
Click to expand...
Click to collapse
No luck with adding persistence.
I get everything to to boot in Linux, followed all the instructions, but Soupkit still does not see my Kindle.
I've tried my factory cable and a regular cable. No luck
Some has changed though because now my Kindle logo light is solid bright whereas before it would blink and dim.
Good luck to you!

Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.

Copcheck said:
Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.
Click to expand...
Click to collapse
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck

Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
When I unplugged the factory cable from the PC and the KF, I could have done 1 of 2 things. Powercycle the KF and hold the power button down to get into TWRP or use a regular USB to side load a ROM and then load it.
Good luck to you, I hope you get it figured out.

Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
If you're getting the Kindle Fire orange and white, you haven't installed the new bootloader. Rerun KFU with the Kindle in Fastboot (using Cable) and select install FireFireFire. This will give you the bootloader to reboot to recovery.
Edit: You might as well reinstall TWRP while you're at it, just to be safe.

[Q] Team Black Hat Adapter

My son is trying to get his kindle fire back up and running. With not much success. He was reinstalling the software and must have wiped the device clean as now he cannot get back into recovery mode. When installing FFFF it says that there is no exec directory. He ordered a factory cable adapter from black hat under the impression that this would force the device into fastboot thus recovery. When he attached the adapter all that happened was that it went back to the kindle fire logo and is now showing offline status unknown. Before at least it was showing online. Are we mistaken that it should go to recovery (blue and white) kindle logo. We are a little tired of messing with it and are thinking of calling it quits. Any suggestions would be much appreciated. We have turned off and on, installed drivers, and switched cables to no avail.

jwhite0514 said:
My son is trying to get his kindle fire back up and running. With not much success. He was reinstalling the software and must have wiped the device clean as now he cannot get back into recovery mode. When installing FFFF it says that there is no exec directory. He ordered a factory cable adapter from black hat under the impression that this would force the device into fastboot thus recovery. When he attached the adapter all that happened was that it went back to the kindle fire logo and is now showing offline status unknown. Before at least it was showing online. Are we mistaken that it should go to recovery (blue and white) kindle logo. We are a little tired of messing with it and are thinking of calling it quits. Any suggestions would be much appreciated. We have turned off and on, installed drivers, and switched cables to no avail.
Click to expand...
Click to collapse
You almost got it right. The error you received means the shell is no longer accessible and therefore unable to send necessary shell commands, like those used to change bootmodes. In order to fix the problem, a factory cable is needed to access fastboot, which gives you an alternative method of changing bootmodes (to access recovery) or flashing partition images (i.e. installing recovery) by use of fastboot commands. But the factory cable does not actually boot the device into recovery on it's own though.
Here's where it get's a little tricky though. Unless you know what to look for, it's difficult to know whether the device is actually in fastboot because the only thing that will be displayed on the screen is the Kindle Fire logo. You'll know if the device is in fastboot because the Kindle Fire logo will stay brightly lit, indefinitely. If the Kindle Fire logo flashes and/or gets slightly dimmed, then you'll know the factory cable you have is defective. With that being said, however, just because the device boots into fastboot mode, doesn't necessarily mean the computer will communicate with it. For that, you need working drivers.
Long story, short...you need to confirm whether the device is actually in fastboot before you can go any further.

Thanks for the reply. I looked at the logo this morning and it came up brightly lit with no change so I am assuming it is in fastboot mode. That being said the device, in device manager it comes up as unknown usb device. Before it would come up as kindle and I would install the drivers and it would come up as an android phone adb composite. I went into device manager and tried to update the driver manually and windows tells me that the correct driver is being used for this device. I did unplug the adapter and go back with a regular data cable and that made no difference. Do you need to force it to use a different driver. I am trying to use the drivers that came with the KFU I downloaded.
soupmagnet said:
You almost got it right. The error you received means the shell is no longer accessible and therefore unable to send necessary shell commands, like those used to change bootmodes. In order to fix the problem, a factory cable is needed to access fastboot, which gives you an alternative method of changing bootmodes (to access recovery) or flashing partition images (i.e. installing recovery) by use of fastboot commands. But the factory cable does not actually boot the device into recovery on it's own though.
Here's where it get's a little tricky though. Unless you know what to look for, it's difficult to know whether the device is actually in fastboot because the only thing that will be displayed on the screen is the Kindle Fire logo. You'll know if the device is in fastboot because the Kindle Fire logo will stay brightly lit, indefinitely. If the Kindle Fire logo flashes and/or gets slightly dimmed, then you'll know the factory cable you have is defective. With that being said, however, just because the device boots into fastboot mode, doesn't necessarily mean the computer will communicate with it. For that, you need working drivers.
Long story, short...you need to confirm whether the device is actually in fastboot before you can go any further.
Click to expand...
Click to collapse

Kindle drivers are notoriously touchy. Try uninstalling/reinstalling them a couple of times. I predict they will suddenly start working and you can proceed with installing custom recovery/rom.
Sent from my GT-p511x

Thanks for the respone, I have installed and uninstalled to where if I here the computer connect and disconnect one more time I might throw it against the wall. Are there specific steps that I need to take other than ordinary to unintall/install the drivers correctly or maybe drivers that are more sccuessful than others.

Ok, after sifting through a number of threads. I read where adb and fastboot are mutually exclusive and adb will not see a device that is in fastboot mode. Is that correct? And when you install the drivers with KFU does that contain the fastboot drivers? Or should you download SDK platforms tools which contains both? And then run fastboot commands to flash a recovery? If so, is there a good tutorial for someone that does not follow directions well?

jwhite0514 said:
Ok, after sifting through a number of threads. I read where adb and fastboot are mutually exclusive and adb will not see a device that is in fastboot mode. Is that correct? And when you install the drivers with KFU does that contain the fastboot drivers? Or should you download SDK platforms tools which contains both? And then run fastboot commands to flash a recovery? If so, is there a good tutorial for someone that does not follow directions well?
Click to expand...
Click to collapse
Yes, adb and fastboot are mutually exclusive but the same drivers should work for each. You can try the drivers located HERE, or read the topic on understanding driver installation located HERE.
Of you are still unsuccessful in communicating with the device in fastboot while using fastboot commands, you may have to restore it with Firekit using the "shorting trick".

OK, here is an update. I was able to get the device into recovery and TWRP. Not sure what I did differently other than maybe standing on one foot, facing south and staring at the stars, but it worked. When all of this started it was right after my son updated the software to 6.3.2 via wifi, maybe something went wrong. So last night I was able to flash 6.3.1 back to the device and was told that it was done succesfully. Using adb I can see the device in recovery and the shell lsiting is ~ # ←[6n which I guess is good as it said there was no shell before. So now my question is could it possibly be a corrupt bootloader on the device as well as it was hung at the fire logo. If so, do I need to reinstall the stock bootloader and if so where do you find it or does it come with the software flash?

I have succesfully got the update file on the kindle, did all the wipes selected install and now seems to be hung at veryfing filesystem and partitions sizes. Can someone tell me how long a flash should take or is something wrong? Since I have never done this before I have no idea.

[Q&A] Firekit LiveUSB repair kit 1.1- when you're about to kill Windows

Q&A for Firekit LiveUSB repair kit 1.1- when you're about to kill Windows
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Firekit LiveUSB repair kit 1.1- when you're about to kill Windows. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

just to confirm
pokey9000 said:
What it is
Firekit combines all the command line tools for Kindle Fire recovery with the Ubuntu LiveUSB. All you need is a USB stick and a PC that can boot off it. All files stay on the stick, so nothing on your PC is changed.
Firekit is run from the command line, but there are scripts to automate common tasks so the typical restoration involves running just two commands. A fastboot-bootable TWRP and FFF is included as well as the Rekindle USB boot tools so even the most fubared bricks can be restored.
This is only for the first gen Kindle Fire 7" from late 2011. It will not work on any other model.
What can it do
Fix power on problems: If the Fire's screen never seems to turn on, you may have wrecked the bootloaders or the partitioning. Fortunately most of the time this results in the CPU falling into the low level USB boot mode. Use the "usb_fix_parts_and_install_fff_twrp" to rebuild the flash enough to boot TWRP. You don't need to use the USB shorting trick for this one, just power up the Kindle after running the script.
Fix stuck-at-triangle-logo: This can be due to being stuck in fastboot or having a corrupt /system. First try getting into recovery. Press power for a few seconds just after turning on, LED should go orange and the TWRP should show up. If that works, reflash your ROM from TWRP. If not, try the "normal_boot" script to get out of being stuck in fastboot.
Fix stuck-at-Kindle Fire-logo: Similar to the above. First try the "normal_boot" script. If that doesn't work, you need to reflash the stock ROM from TWRP. But you don't have TWRP. So use the "install_fff_twrp_from_stock" script which will force the stock ROM into letting you install fastboot. Then flash a ROM.
-and more
Why
A lot of people seem to be having problems with Windows and ADB drivers needed for fastboot and adb. Linux doesn't seem to have this kind of trouble, so I threw this together. It's not pretty or menu driven, but I find that too much automation gets in the way when things are broken to begin with.
Downloading a ~600MB Ubuntu image is needed, and this has only been tested on one PC so far. Don't complain if you spend hours grabbing this only to not have it fix your problem. I thought about rolling my own USB image with debootstrap for a much smaller image but figured that a prefab Ubuntu Live image is probably best for compatibility.
Using Firekit
Making the LiveUSB
Get the latest 32-bit Ubuntu and follow the directions to make a USB stick. If you want to try this with another distro (not tested) it must be 32-bit or have full 32-bit compatibility libraries.
Then unpack the attached zip to the top of the stick. The easiest way is to open the .zip in Explorer, right-click on "fk" (the only file in the zip), and choose "Send to..."->your USB stick's drive letter. You may have to unplug and replug the stick for Windows to see the drive after Ubuntu's been installed. If you have anything else you want available on the stick (roms, other recovery/bootloader, etc) copy them here as well. When done, eject the drive.
Before Booting
Set your PC's BIOS to boot USB before your internal drive. Each PC is different, so it's up to you to figure out how to set your PC to boot from USB.
Running the tools
Always start with your Kindle turned off and unplugged from USB. These directions assume that your Fire is stuck in fastboot, has FFF installed, or you are using the USB boot shorting trick. The exception is if you're trying to install FFF/TWRP from stock Kindle OS, in which case leave it booted and plugged in.
Now boot the LiveUSB. Once the Ubuntu desktop shows up, click the Ubuntu logo in the top left (or press the Windows key) and type "term". Hit enter to run the terminal.
In the terminal window, type "sudo /cdrom/fk". This unpacks the tools and sets up your environment. You should now have a prompt that says "[email protected]:~/firekit#"
A list of the possible scripts should now be showing. Type the name of the script you want and hit enter. Protip: type a few letters and hit tab to autocomplete the rest of the word. If you're using any of the usb_ scripts, short the test point and plug in the Fire. As mentioned before, you should have the Fire already booted when using "install_fff_twrp_from_stock". For all the other commands, just plug the Fire in.
If this keeps you from returning or junking an otherwise good Fire, consider throwing a thanks or a beer my way.
Props to TeamWin & agraben for TWRP, everyone at Canonical
These are the commands as of 1.1:
install_fff_twrp_from_stock: Install FFF and TWRP while in stock Android. Uses fbmode to reboot. Use this to get FFF/TWRP installed on 6.2.1 stock OS.
install_fff_twrp: Install FFF and TWRP while in fastboot. Good if you're stuck in fastboot and you want FFF/TWRP.
fix_parts Restore partition table to stock while in fastboot. Do this if you're in fastboot and your partition table is screwed up.
normal_boot: Set the bootmode to boot android and reboot while in fastboot. Try this if you're stuck at the Kindle Fire logo.
usb_boot_twrp: USB boot TWRP without installing. Boot TWRP if your Kindle black screens when you try to power it on. Needs the USB boot mode trick.
usb_install_fff_twrp: USB boot FFF, install FFF and TWRP. Install / recover the bootloader and recovery if they are broken. Needs the USB boot mode trick.
usb_fix_parts_and_install_fff_twrp: USB boot FFF, restore partition table to stock, install FFF and TWRP. Fix everything if you screwed up the partition table and your Fire's screen no longer turns on. Needs the USB boot mode trick.
Changelog:
1.1:
-Add restore of mmcblk0p1 (x-loader) to the "usb_fix_parts_and_install_fff_twrp" script to recover from total brain damage. Thanks to TyHi for proving this works and may be necessary.
1.0:
-Initial release
(todo: make videos, integrate usb boot mode instructions)
Click to expand...
Click to collapse
Just to confirm: my kindle is stuck in fastboot and was running 6.3.3. Would this work?
Thanks!

KFHD 8.9
my KFHD 8.9 (KFJIW) is hard-bricked (doesn't turn on) after trying to flash the FFF 1.5 via TWRP that didn't go as expected for an unknown reason, and I didn't find any solution to unbrick it so far, so I would like to ask if anyone here if they have any hint how to solve this, I know the experts here have seen this issue before and I am pretty sure that they are enough skilled to find a solution, I would like to try to revive it with this solution but since it's for KFHD 7 only I don't know if it will work or what I have to take into account to make it work, I don't have the soldering hardware right now to fix it via eMMC reflashing (but maybe I can do buy it if it is the only option) I did enjoy modifying the tablet and playing with the settings and hacks to make it better so it's more about emotional attachment to this tablet and curiosity than anything else.
I thank all the xda experts for all the knowledge they share and the effort they put to make us exploit the full potential of the hardware's

I tried the firekit without the usb trick, it stops at the "Fix Partition...", and "wait for device". Usually how long it will take?
Does it mean I can't avoid shorting?
I am sure my kindle bricks because the partition table is messed up. Can't power on, without led light. Windows recognizes it as "OPAM4430" but lose immediately.

Now PC only recognizes it as "Basic Device"

how do i use firekit
from my perusal of the thread, the procedure is geared towards windows users desirous of using the linux interface to solve the problem. in my situation, i have am an ubuntu user (a new user at that) and i was wondering if i would have to go through the exact same steps outlined in order to restore my kindle.