Firekit LiveUSB repair kit 1.1- when you're about to kill Windows

Search This thread

three-p-o

Senior Member
Apr 20, 2012
100
29
My Kindle is bricked.

I ran the Kindle Fire Utility 0.95, followed steps in the first post, installed drivers fine, then rooted it. It turned off, and now will not turn on. I've tried charging it, pressing and holding the button 100 times for varying lengths.. nothing.

My question is, what are my options now? I was thinking of doing the Firekit LiveUSB repair kit short trick.. but that will for sure void the warranty. Is there any possibility of me returning the Kindle as is right now? It's only 2 days old.

Any advice would be most certainly appreciated, because I'm pretty f**ked right now.


I'm trying to run your utility, but am a little confused. At first it says:

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.

But then down below it says "Needs usb shorting trick".. which is it?
It doesn't need it.. I thought it did so I popped the back off mine before I found out I didn't need to.
 

freefaling

Senior Member
Dec 9, 2010
97
20
Lahore
@Adamp24

I was confused by that too. So I tried it without usb shorting (nothing happened) and then i tried it w/ usb shorting and my kindle came back to life.

Sent from my Amazon Kindle Fire using XDA
 

Adamp24

Senior Member
Apr 14, 2009
54
2
Raleigh
@Adamp24

I was confused by that too. So I tried it without usb shorting (nothing happened) and then i tried it w/ usb shorting and my kindle came back to life.

Sent from my Amazon Kindle Fire using XDA

Question for the 2 guys above me.. was your Kindle completely bricked (no lights, won't power on or anything) from trying to root?

And this fixed it?

Thanks in advance.
 

three-p-o

Senior Member
Apr 20, 2012
100
29
Mine would not power at all, No lights on screen or on power button.
My issue was that I wiped the internal storage completely, blowing away all partitioning information.
When I plugged it in however, it would show in windows' device manager as an omap4430. I just couldn't get anything to connect to it. The USB stick got me working.
 

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
Question for the 2 guys above me.. was your Kindle completely bricked (no lights, won't power on or anything) from trying to root?

And this fixed it?

Thanks in advance.

The problem you're experiencing is typical of a broken bootloader caused by improper installation, not enough battery power, or pulling the usb cable out during installation. So far the only way to fix it is the USBboot method.

Even with a broken bootloader, the device will still recognize low level USB commands like those from the "firekit", but the "shorting trick" must still be applied.
 

three-p-o

Senior Member
Apr 20, 2012
100
29
I'll agree with soup that 90% of the time, the USB trick is needed. However, if you are in a state like I was it may not be necessary.

I intentionally wiped the entire storage of the system, dd if=/dev/zero on the entire device. I had a full battery charge, well 80-90%, and after wiping the storage and I powered down, I would not get a visible power indication.
The trick was that when I had it "off" and I plugged it into a computer I would hear it detect the device and I saw the omap4430 item in device manager (windows 7) but oculd not interface with it.

What I ended up doing was powering it off by holding in the power for 20-30 seconds, I heard windows "disconnect" from the device. I then unplugged the kindle from the computer and booted using the liveUSB, ran the firekit and "usb_fix_parts_and_install_fff_twrp". After running that command I plugged the kindle in, and viola, it was fixed.

This however will only work if the device is seen as the omap4430 when you plug it into a computer. A few notes, if the kindle was "on" and I plugged it in, it would not be seen. If it was off though and I plugged it in, it would turn on and go into omap4430 state. This is the state needed for the "usb_fix_parts_and_install_fff_twrp" command.
If your kindle does not enter this state, you will need to open it up.
 

pokey9000

Senior Member
Apr 17, 2007
767
396
Austin
Mine would not power at all, No lights on screen or on power button.
My issue was that I wiped the internal storage completely, blowing away all partitioning information.
When I plugged it in however, it would show in windows' device manager as an omap4430. I just couldn't get anything to connect to it. The USB stick got me working.

For future reference: if you get the "OMAP4430" or "TI" device showing up when your KF is bricked too hard to turn on the screen, then you can skip straight to running one of the "usb_" commands.

The OMAP will try booting from USB if it can't find a valid bootloader, aka you trashed the first stage bootloader (x-loader). The shorting comes in when you screw up the 2nd stage bootloader (FFF), because the 1st stage bootloader doesn't check that there's a valid 2nd stage. If someone was REALLY dedicated, they could add a checksum to the 2nd stage, and have the 1st stage force the Fire into USB boot mode if it looks messed up.
 

freefaling

Senior Member
Dec 9, 2010
97
20
Lahore
Question for the 2 guys above me.. was your Kindle completely bricked (no lights, won't power on or anything) from trying to root?

And this fixed it?

Thanks in advance.

Exactly. No lights, no VISIBLE signs of powering on (although I knew it powered on b/c half of the kindle would get warm after a while; as opposed to staying cold when it was hard reset).

So try it w/o shorting and if that doesn't work (which is very likely), try it w/ shorting (like everyone here is suggesting). Be careful w/ opening ithe back cover, you don't want to scratch it up (use a plastic tool if available). Good luck.

Sent from my Amazon Kindle Fire using XDA
 
Last edited:

Adamp24

Senior Member
Apr 14, 2009
54
2
Raleigh
Hey all! Thanks for the help. After 2 hours of trying the shorting trick and getting into TWRP recovery.. I finally got a ROM installed. However, now.. when the Kindle is first powered on.. it shows the yellow triangle screen that says "press power button for recovery" for like.. 20 seconds.. then it finally boots into CM9. Is there any way I can either A) remove that triangle screen from showing, or B) return this thing to 100% completely stock so I can return it to Amazon?

I looked through the forums but all I can find are stock ROMs.. is there an RUU or something I can flash to reset recovery/bootloader/everything stock? Thanks in advance
 
Last edited:

freefaling

Senior Member
Dec 9, 2010
97
20
Lahore
Hey all! Thanks for the help. After 2 hours of trying the shorting trick and getting into TWRP recovery.. I finally got a ROM installed. However, now.. when the Kindle is first powered on.. it shows the yellow triangle screen that says "press power button for recovery" for like.. 20 seconds.. then it finally boots into CM9. Is there any way I can either A) remove that triangle screen from showing, or B) return this thing to 100% completely stock so I can return it to Amazon?

I looked through the forums but all I can find are stock ROMs.. is there an RUU or something I can flash to reset recovery/bootloader/everything stock? Thanks in advance

Flashing stock/Amazon ROM through TWRP (instructions can be found here on xda) will revert your kindle to stock, afaik.

Sent from my Amazon Kindle Fire using XDA
 

trungblc

Member
Aug 25, 2008
12
0
What I ended up doing was powering it off by holding in the power for 20-30 seconds, I heard windows "disconnect" from the device. I then unplugged the kindle from the computer and booted using the liveUSB, ran the firekit and "usb_fix_parts_and_install_fff_twrp". After running that command I plugged the kindle in, and viola, it was fixed.
.

I do every step as you said.
+ I run usb_fix_parts_and_install_fff_twrp then My Kindle boot on TWRP
+ I fash with update-kindle-6.3_D01E_4019920.zip
+ Reboot
But my Kinlde Fire still not power on. Is there something wrong?
 

three-p-o

Senior Member
Apr 20, 2012
100
29
I do every step as you said.
+ I run usb_fix_parts_and_install_fff_twrp then My Kindle boot on TWRP
+ I fash with update-kindle-6.3_D01E_4019920.zip
+ Reboot
But my Kinlde Fire still not power on. Is there something wrong?

Sounds like either your update-kindle flash failed, or you are out of power, because the first step worked.
At this point, plug it into your wall charger over night and check it in the morning. If it is still dead after that I would say try to return it and get a new one. And I'm actually against people doing that when they screw up.. so....
 

Deeva

Member
Aug 15, 2009
8
0
Ubuntu crashing when using FireKit

I screwed up my Kindle somehow while trying to root it with the KFU and I tried everything under the sun to fix it before I decided to post here... it took me two days to figure out how to boot Ubuntu off a USB stick in WinXP, but I finally got that going to the point of finally being able to run the fk in the Ubuntu terminal with no issue, until I plug the stupid Kindle in and try to use it.

My Kindle is stuck in the non-animated Kindle Fire logo. Unseen by USB or adb in Windows, last resort was to use the Ubuntu method. I tried all the scripts *except* the usb scripts, figuring it is stuck in fastboot mode - however no matter what I try to run, the Ubuntu goes into a kernel panic (bunch of text on black appears etc) and freezes every time. So nothing is getting through and connecting to the Kindle. I plugged it in and let it turn itself on, I powered it down and plugged it in then turned it on, etc. NADA. :mad: The only thing I haven't done is the shorting thing only because I really don't understand it...

I'm about to smash this POS into bits or use it for target practice, but before I give up I'd like some thoughts if anyone has any? Thanks :)
 

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
I screwed up my Kindle somehow while trying to root it with the KFU and I tried everything under the sun to fix it before I decided to post here... it took me two days to figure out how to boot Ubuntu off a USB stick in WinXP, but I finally got that going to the point of finally being able to run the fk in the Ubuntu terminal with no issue, until I plug the stupid Kindle in and try to use it.

My Kindle is stuck in the non-animated Kindle Fire logo. Unseen by USB or adb in Windows, last resort was to use the Ubuntu method. I tried all the scripts *except* the usb scripts, figuring it is stuck in fastboot mode - however no matter what I try to run, the Ubuntu goes into a kernel panic (bunch of text on black appears etc) and freezes every time. So nothing is getting through and connecting to the Kindle. I plugged it in and let it turn itself on, I powered it down and plugged it in then turned it on, etc. NADA. :mad: The only thing I haven't done is the shorting thing only because I really don't understand it...

I'm about to smash this POS into bits or use it for target practice, but before I give up I'd like some thoughts if anyone has any? Thanks :)

Your problem doesn't belong here. This tool is for SERIOUS bricks, yours is not that serious. Please repost this in the Q&A section so we can help you better.
 

Deeva

Member
Aug 15, 2009
8
0
Your problem doesn't belong here. This tool is for SERIOUS bricks, yours is not that serious. Please repost this in the Q&A section so we can help you better.

Ok sorry, I thought my post may have belonged here since I was using the Firekit tool and I think my Kindle IS a serious brick? Thanks for the reply I will find the proper place to hopefully get some input. I searched and searched and cannot find anything referencing Ubuntu crashing while using this tool.
 

pokey9000

Senior Member
Apr 17, 2007
767
396
Austin
Ok sorry, I thought my post may have belonged here since I was using the Firekit tool and I think my Kindle IS a serious brick? Thanks for the reply I will find the proper place to hopefully get some input. I searched and searched and cannot find anything referencing Ubuntu crashing while using this tool.

Kernel panics might be related to some other system instability you're having. Make sure you're using the "x86" version of the LiveCD, and try it on another PC. None of the code in Firekit should be able to cause a kp.
 

shantam

Senior Member
Apr 11, 2010
421
75
i am stucked at waiting for device

i bricked my kindle when i factory resetted with cwm recovery and it stucked at formatting/data

then i powered off the device by pressing down the power button for 20 seconds.then i pressed power button and it did''nt booted up..

now i have installed firekit live usb and issued the command for usb_fix_install_fff_twrp

and plugged the device.
device powered on and in terminal it was showing that
sending 2nd stage to target
waiting for 2nd stage response
sending image
fixing paritiions

and its showing waiting for device

and i stucked there for 30 minutes but nothing happened.then i unplugged the kindle and powered it off

i have issued every command listed on the terminal

one thing is that i have not transferred any fff bootloader,twrp or rom file to root of drive..

should i transfer the files it requires like twrp,fff,or roms
now what should i do for getting my kindle to life

i have tried this for about 4 to 5 times with no success..
 
Last edited:

alekslove

Member
Jul 10, 2008
10
3
what do you mean you had already set adb? how do I do that? Cause I get al the way thru till I plug in my usb while shorting and it gets stuck at "waiting for device".
 

Jdom58

Senior Member
Aug 30, 2009
1,531
275
South Florida
Guys, same here as shantan, had to use the usb trick of opening up the back of the kindle to short out the connection and after MULTIPLE tries got it just right but it went as far as

sending 2nd stage to target...
waiting for second stage response...
sending image to target...
fixing partitions...
<waiting for device>

then nothing happened for about 5-10 minutes so I tried again from the begining and got the same results, any ideas?

Thanks in advance
 

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    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 "root@ubuntu:~/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)
    2
    Hello,

    I have my unbuntu on a bootable usb and I have the extracted kf file on the root folder right where terminal opens up to... so in the terminal I do "sudo fk" and "sudo /fk" and it just gives me command not found, could somebody give me a little help? I'm not a linux noob but I am no pro either.

    sudo ./fk

    "sudo /fk" doesn't work because I'm guessing your file is located in /root/fk, and "sudo fk" doesn't work because executables without a path prefix are assumed to be in the $PATH, and most of the time /root and the current directory ("./") aren't in the $PATH.
    1
    Ah, I got it! the permissions needed to be changed, then I ran the sudo ./fk and it worked, thanks!



    That makes since to me, but my computer must hate me... here is from a brand new terminal window that I had opened.

    ubuntu@ubuntu:~$ dir
    Desktop Documents Downloads fk Music Pictures Public Templates Videos
    ubuntu@ubuntu:~$ "sudo ./fk"
    bash: sudo ./fk: No such file or directory

    Don't include the quotes...
    1
    When it says waiting then apply the short trick plug it in and keep it applied till the script runs also make sure whatever your using to short has good conductivity :)
    1
    BTW, no. This is not for the Kindle Fire 2...it will only make things worse for you.


    "That's a special kind of stupid. The kind that makes me laugh."

    anything similar to this that will fix a KF2? Not too sure what to do at this point. seems pretty bricked to me :p