Develop Bugs

[BOOT] FIREFIREFIRE 1.3 - Replacement bootloader w/ recovery selection

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIREFIREFIRE​
FIREFIREFIRE is a replacement bootloader originally created by pokey9000 for the Kindle Fire. While the stock bootloader simply boots into the system, FIREFIREFIRE provides an option to boot into recovery and also enables fastboot for a short period of time. Everyone from developers to users of alternative ROMs will certainly benefit from having FIREFIREFIRE on their device.
FEATURES
Recovery Selection - As the Kindle Fire boots up, the power button LED will change from bright green to a dim green. Once it changes to a dim green, press the power button again and release (repeat a few times to be sure). The LED will then change to an orange color indicating recovery selection and boot into recovery.
Enable Fastboot - As described above, when the power button LED changes to a dim green, the Kindle Fire will enter fastboot mode for approximately 4-5 seconds. During this time, fastboot commands can be issued and the device will remain in fastboot until it is rebooted.
Write Partition Tables - During fastboot, issuing a 'fastboot oem format' command will overwrite the existing partition table with the stock table values.
HOW TO INSTALL
From stock bootloader fastboot
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
From FIREFIREFIRE fastboot
Code:
fastboot flash bootloader u-boot.bin
From gscript - Details in the gscript thread
For a step-by-step guide on how to update FIREFIREFIRE from a previous version using fastboot, see this post by smirkis
RELEASE NOTES
1.3 - MD5: 928ae401d91963e1cb8f4dae6ca9519b
March 11, 2012
Replaced the original FIREFIREFIRE boot logo with a "kindle fire android" logo
Shortened the fastboot delay from ~10 seconds to ~5 seconds
0.9 - 1.2
Original FIREFIREFIRE thread
ADDITIONAL NOTES
I originally just wanted to rebuild the FIREFIREFIRE bootloader to bake in a custom boot logo for my own use. That opened the door enough for me to become interested in making some minor improvements in how it handles recovery selection. When I contacted pokey9000, he encouraged me to work on it and gave me enough confidence to begin studying the code. Although I couldn't begin to estimate a timeframe, I hope to continue working on it and build in some enhancements that would be worthy of eventually calling it version 2.0.
The bootloader is possibly the most underappreciated piece of software on the Kindle Fire. It's not overreaching to say that everything else is built on top of this foundation. Without the work of pokey9000, the XDA Kindle Fire community would not have gotten the other great developments as quickly as it did. When the next great device comes along, we will certainly need the work of talented people like pokey9000 again. If you enjoy using your Kindle Fire as an Android tablet, please consider making a donation to pokey9000.
A special thanks to smirkis for having the guts to be the first in line to flash my build on his device.

props to this gentleman for expanding on pokey9ks work, I love the logo and shortened delay. I love being a test dummy, thanks for the opportunity
ill update my gscript method when I get home!
Sent from my HTC Glacier using xda premium

Very nice; I like the logo and it works exactly as it should (guess this means I can stop trying to understand the uboot source myself for the time being lol)

Is this flashable in TWRP?

AustinFire said:
Is this flashable in TWRP?
Click to expand...
Click to collapse
As noted in this thread, fastboot flash shall be used.
Sent from my Amazon Kindle Fire using Tapatalk

I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?

ch0mch0m said:
I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?
Click to expand...
Click to collapse
You may use KF utility to boot into fastboot, then use fastboot flash mentioned in the header of this thread, then reboot to normal using KF.
Sent from my Amazon Kindle Fire using Tapatalk

ch0mch0m said:
I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?
Click to expand...
Click to collapse
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.

kinfauns said:
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.
Click to expand...
Click to collapse
I saved this from somewhere on XDA, not sure who or what thread:
Code:
Howto flash by hand
1 Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. "adb shell idme bootmode 4002"
2 flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
2b at <waiting for device> press power 30 seconds to power down, then power up
3 disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
4 reboot: "fastboot -i 0x1949 reboot"

it's not realy a tutorial but it should clear things up regarding the bootmodes and how drivers and commands are related

kinfauns said:
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.
Click to expand...
Click to collapse
I just did install FFF 1.3 using KFU.
Used KFU to set bootmode to fastboot (Bootmode menu -> Fastboot).
However, windows (Windows 7 x64 EE) then complained about the driver and fastboot (and adb) didn't recognize my KF and I was stuck in fastboot mode.
I needed to uninstall the driver, reboot windows, reconnect the KF in order to get windows to reinstall the Android ADB Interface driver.
Then all was fine. Used KFU's fastboot to flash FFF 1.3 and set the boot mode back to normal.

Pkt_Lnt said:
I saved this from somewhere on XDA, not sure who or what thread:
Click to expand...
Click to collapse
b63 said:
it's not realy a tutorial but it should clear things up regarding the bootmodes and how drivers and commands are related
Click to expand...
Click to collapse
Thanks for those crib sheets. I was hoping there was something out there that starts off answering the question, "What is fastboot?" and working up from there. While KFU and other press-this-button utilities do a good job of getting the beginner started, it's like teaching someone how to run without walking first. Then when the user gets into a bind because something went wrong, they have no idea what to do next. The General section seems to be filled with these kinds of problems. A while back, I started writing a general knowledge, FAQ style post, but it seemed too rudimentary once I got into it. When I glance at the General section from time to time, I have second thoughts about having shelved it. Maybe I'll dust it off again.

twa_priv said:
I just did install FFF 1.3 using KFU.
Used KFU to set bootmode to fastboot (Bootmode menu -> Fastboot).
However, windows (Windows 7 x64 EE) then complained about the driver and fastboot (and adb) didn't recognize my KF and I was stuck in fastboot mode.
I needed to uninstall the driver, reboot windows, reconnect the KF in order to get windows to reinstall the Android ADB Interface driver.
Then all was fine. Used KFU's fastboot to flash FFF 1.3 and set the boot mode back to normal.
Click to expand...
Click to collapse
Well, not to pick at semantics, but I think you used the tools from the KFU distribution and not necessarily KFU's menu interface. Regardless, it sounded like the original poster of the question didn't even want to bother with KFU, so actually typing some commands isn't going to be much of an option either.

kinfauns said:
Well, not to pick at semantics, but I think you used the tools from the KFU distribution and not necessarily KFU's menu interface. Regardless, it sounded like the original poster of the question didn't even want to bother with KFU, so actually typing some commands isn't going to be much of an option either.
Click to expand...
Click to collapse
No, I used the KFU batch file to change the boot mode. But I wasn't saying this is an issue with KFU, it's much rather an issue with freaking windows.

twa_priv said:
No, I used the KFU batch file to change the boot mode. But I wasn't saying this is an issue with KFU, it's much rather an issue with freaking windows.
Click to expand...
Click to collapse
I understood the part about you using KFU to change the bootmode and the part about you reinstalling drivers. My comment wasn't about either of those things. My point was that there's not a way to reinstall a new FFF from within the KFU menus. You used KFU to change bootmodes, quit out of KFU, then used the fastboot executable to do the actual installation... just as my installation instructions described. Although the fastboot executable is packaged in the tools directory of KFU, it is entirely separate from it. My intent was to clarify this point so that some other reader of this thread in the future doesn't get confused and say, "But he said I could use KFU to install it!"

I just used cmd and fastboot from the adb-sdk (winXP) to install this. Very nice! Great work.

Pkt_Lnt said:
I just used cmd and adb (winXP) to install this. Very nice! Great work.
Click to expand...
Click to collapse
Thanks for the feedback, I'm glad you like it. Did you use dd to write directly to the bootloader partition?
Edit: Nevermind, I see that you changed your post to say fastboot.

if you already have fff1.0, fff1.1, or fff1.2, all you need to do to install this:
first, connect your device to your computer and make sure USB is not mounted
make sure you already downloaded the new fff1.3 and copy it to your sdk folder where fastboot is located
open a cmd prompt if you on windows and cd to the sdk directory where fastboot is located, for me i typed
cd c:/sdk_tools
than go ahead and pre-initiate the fastboot command to install the new fff1.3
fastboot flash bootloader u-boot.bin
you should see a message saying, <waiting for devices>, now go ahead and reboot your kindle.
at startup fastboot is automatically detected and your cmd prompt should say something like
c:\SDK_tools>fastboot flash bootloader kinfauns_u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)... OKAY [ 0.057s]
writing 'bootloader'... OKAY [ 0.188s]
finished. total time: 0.246s
at this point, its still in fastboot. so issue
fastboot reboot
and u should see something like this
c:\SDK_tools>fastboot reboot
rebooting...
finished. total time: 0.002s
no need to change bootmodes, no need to use KFU, nothin.
if your pc has driver issues, avoid fastboot entirely and use my gscript method posted in the OP

smirkis said:
if you already have fff1.0, fff1.1, or fff1.2, all you need to do to install this:
Click to expand...
Click to collapse
Thanks to smirkis for the mini-guide on how to update FFF from a previous version. I've edited the OP to point to his post so others can find it easily.

That is good. Just for info, I used the commands in my post 9 above (note the "take out "-i 0x1949" if FFF is already installed" in step 2) and it works fine.
I used that to install FFF 1.0 and update 1.1, 1.2, and now 1.3 clean and quick.
The really short version is saved now for the next version.

Kindle Fire Bricked - Need Assistance

I rooted my Kindle Fire and have TWRP recovery installed. I flashed a CM9 Rom followed the directions step by step including wiping cache / dalvik etc... from recovery before rebooting. When my kindle fire boots now I first see the Kindle Fire logo screen and then it switches to the CM9 bootup logo (looks like a bunch of multicolored squares that appear and disappear). When I get to this point my computer makes the noise like it detects something plugged into the USB port and the device listed says Amazon under unspecified in my device list. When I right click on it i have the option to eject amazon.
Running the kindle fire unbrick utility wont work on any option I click. Each option says waiting for device or device not found.
Running kindle fire utility reports ADB status offline boot status unknown. My computer sees the kindle but I guess it's not mounting. The farthest I can get on this thing is the spinning bootup logo and I cannot get it to go back to TWRP recovery no matter what I try.
I'm guessing this thing is permanently screwed but if anyone has any suggestions i'd really appreciate it.

Okay, first I have to ask...because this mistake has been made by others, making this a much more difficult process than needed...what color is your "TWRP" screen?

soupmagnet said:
Okay, first I have to ask...because this mistake has been made by others, making this a much more difficult process than needed...What color is your TWRP screen?
Click to expand...
Click to collapse
I cant pull it back up so i'm only going by memory... I'm fairly certain it was a dark background with orange buttons.

urge311 said:
I cant pull it back up so i'm only going by memory... I'm fairly certain it was a dark background with orange buttons.
Click to expand...
Click to collapse
Did it look like this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...or this?....
The first one (CWMR), cannot install ICS or JB based ROMS. For that, you need to install the second one (TWRP).

It definitely looked like the second one with the big buttons.

I guess my question is, why are you leaving it plugged into your computer when flashing a new ROM? Just curious.

My next question is...what does your boot logo look like? (in detail)

I was plugging it into the computer in an effort to fix the problem using the kindle fire unbrick utility... My problem is when I turn the kindle fire on since installing my rom it gets stuck on a boot loop with the CM9 boot screen and never fully loads the rom. I have no way of fixing it by getting into recovery because it wont open no matter what I try.
My bootup screen first shows the kindle fire logo then goes to the cm9 wallpaper where it's like a bunch of colored squares the appear and disappear and it never gets any farther than that.
Connecting the kindle to my computer was only so I could try to reflash recovery which is not working because none of the downloadable utilities i've tried recognize the kindle is plugged in but my computer seems to know it's there because it recognizes a device but it doesn't mount to it at all allowing me to transfer data to it.

::facepalm::
No. I know what your problem is. I need to know what your boot logo looks like, in detail...Which is why I asked, "What does your boot logo look like? (in detail)"...as in, identifying characteristics...of the boot logo. (This is very important)

soupmagnet said:
::facepalm::
No. I know what your problem is. I need to know what your boot logo looks like, in detail...Which is why I asked, "What does your boot logo look like? (in detail)"...as in, identifying characteristics...of the boot logo. (This is very important)
Click to expand...
Click to collapse
Here's a link to a youtube video I made today showing exactly what happens when I turn the kindle fire on.
http://www.youtube.com/watch?v=Dl-VAunzSqc

urge311 said:
Here's a link to a youtube video I made today showing exactly what happens when I turn the kindle fire on.
http://www.youtube.com/watch?v=Dl-VAunzSqc
Click to expand...
Click to collapse
I would have taken "Kindle Fire in orange and white"...but that works just as well.
You never installed a custom bootloader. The Kindle Fire logo you see indicates that it's the stock bootloader that comes with the device. The custom bootloader we all use is FireFireFire (FFF). What makes FFF different from the stock version, is that it allows you to use the power button at startup to access custom recovery, and the most recent version has the ability to reset your bootmode (very handy). Your problem is that you have a bad ROM flash, possibly from a bad download or using the wrong recovery (yes I know, we went over that) or perhaps you didn't wipe properly (I know, we went over that as well). The typical fix for this is to access recovery and flash a new or different ROM (w/wipes) in TWRP, not CWM. Here's where the problem lies, without a custom bootloader like FFF, you have to rely on your computer's ability to connect with your device to send adb commands. The key to that is having working drivers, and I can tell by your previous description that you don't. So, install or reinstall, fix or whatever you have to do to your drivers to get connected with the adb, then send the command to change the bootmode to recovery.
And...before you ask any more questions (I can feel them coming), you need to read...
http://forum.xda-developers.com/showthread.php?t=1552547
first three posts
http://forum.xda-developers.com/showthread.php?t=1638452
install a ROM section
http://forum.xda-developers.com/showthread.php?t=1668159
all of it...just in case

soupmagnet said:
I would have taken "Kindle Fire in orange and white"...but that works just as well.
You never installed a custom bootloader. The Kindle Fire logo you see indicates that it's the stock bootloader that comes with the device. The custom bootloader we all use is FireFireFire (FFF). What makes FFF different from the stock version, is that it allows you to use the power button at startup to access custom recovery, and the most recent version has the ability to reset your bootmode (very handy). Your problem is that you have a bad ROM flash, possibly from a bad download or using the wrong recovery (yes I know, we went over that) or perhaps you didn't wipe properly (I know, we went over that as well). The typical fix for this is to access recovery and flash a new or different ROM (w/wipes) in TWRP, not CWM. Here's where the problem lies, without a custom bootloader like FFF, you have to rely on your computer's ability to connect with your device to send adb commands. The key to that is having working drivers, and I can tell by your previous description that you don't. So, install or reinstall, fix or whatever you have to do to your drivers to get connected with the adb, then send the command to change the bootmode to recovery.
And...before you ask any more questions (I can feel them coming), you need to read...
http://forum.xda-developers.com/showthread.php?t=1552547
first three posts
http://forum.xda-developers.com/showthread.php?t=1638452
install a ROM section
http://forum.xda-developers.com/showthread.php?t=1668159
all of it...just in case
Click to expand...
Click to collapse
Thank you for your help. I really do appreciate it.

Have you tried restoring it with data unchecked on the restore option of twrp?
Sent from my Kindle Fire using xda app-developers app

pandapounds said:
Have you tried restoring it with data unchecked on the restore option of twrp?
Click to expand...
Click to collapse
I'm guessing that's probably not an option...
urge311 said:
I have no way of fixing it by getting into recovery because it wont open no matter what I try.
Click to expand...
Click to collapse
I could be wrong though.

soupmagnet said:
I'm guessing that's probably not an option...
I could be wrong though.
Click to expand...
Click to collapse
Well after a lot of trial and error with installing and uninstalling drivers I finally got the kindle to boot into TWRP but i'm unable to get it back to stock. TWRP loads after white and orange kindle fire logo. I can access any of the menus on that but cant really do much else. I've tried flashing FFF but I can no longer get the device into fastboot mode. I've tried various ADB commands to do this manually but i'm getting some odd readings through ADB:
C:\Kindle Fire Utility\tools>adb devices
List of devices attached
313A02600000001 recovery
C:\Kindle Fire Utility\tools> adb shell
~ # ←[6n
C:\Kindle Fire Utility\tools>
Basically i'm stuck in a recovery boot loop now and the kindle fire unbrick utility with the recovery loop option just gets stuck at waiting for device. Kindle Fire Utility when launched shows ADB status: Online and Boot Status: Unknown.
Anyone know of a way around this? I'm guessing i'll have to run some commands but dont really know where to go from here.

urge311 said:
Well after a lot of trial and error with installing and uninstalling drivers I finally got the kindle to boot into TWRP but i'm unable to get it back to stock. TWRP loads after white and orange kindle fire logo. I can access any of the menus on that but cant really do much else. I've tried flashing FFF but I can no longer get the device into fastboot mode. I've tried various ADB commands to do this manually but i'm getting some odd readings through ADB:
C:\Kindle Fire Utility\tools>adb devices
List of devices attached
313A02600000001 recovery
C:\Kindle Fire Utility\tools> adb shell
~ # ←[6n
C:\Kindle Fire Utility\tools>
Basically i'm stuck in a recovery boot loop now and the kindle fire unbrick utility with the recovery loop option just gets stuck at waiting for device. Kindle Fire Utility when launched shows ADB status: Online and Boot Status: Unknown.
Anyone know of a way around this? I'm guessing i'll have to run some commands but dont really know where to go from here.
Click to expand...
Click to collapse
You can use recovery to install FFF1.4. See if you can use the mount function to mount your sdcard to the computer.

soupmagnet said:
You can use recovery to install FFF1.4. See if you can use the mount function to mount your sdcard to the computer.
Click to expand...
Click to collapse
The mount option does indeed mount the kindles SD card to my computer. Do I need to hunt for a FFF1.4 in a .zip file to flash through recovery?

Yes, indeed.
http://forum.xda-developers.com/showpost.php?p=25598837

soupmagnet said:
Yes, indeed.
http://forum.xda-developers.com/showpost.php?p=25598837
Click to expand...
Click to collapse
Just wanted to say thanks again. Everything is working now. I was able to flash FFF with a zip I found on another post on here which still kept me in a TWRP recovery bootloop but I was able to fix that with the kindle fire unbrick utility with the recovery boot loop option. Everything is working great now. You definitely got me pointed in the right direction and I really appreciate it.

urge311 said:
I was able to flash FFF with a zip I found on another post on here which still kept me in a TWRP recovery bootloop but I was able to fix that with the kindle fire unbrick utility with the recovery boot loop option.
Click to expand...
Click to collapse
FFF1.4 was designed to (among other things) address that problem. By holding the power button to bring up the boot menu and selecting "reset boot mode", it will reset the idme bootmode to 4000 and it will stay that way.

[Q] Used a not great tutorial now kindle fire hd won't restart. Help?

Okay starting off with this is the tutorial I was using: rootkindlefire . com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet and I like a lot of people in the linked youtube comments (which I stupidly didn't read before trying, yes I am aware that was stupid) am stalled after step 20. But my kindle fire HD doesn't seem to have TWRP because it turned on and the kindle fire logo is still orange. It didn't go to blue like most of the other peoples did.
Can someone please help me to either undo my mess or help me get past this block? I wasn't able to find any help in the comments or a related thread on here.
I think it's stuck in fastboot but I can't get it to go into recovery so I'm not sure.

It's not in fastboot, its just hung on the boot loader. If you have never installed the fastboot driver before I reccomend fixing this partially from Linux, your device will be detected briefly when its first turned on as a fastboot device, but it's a pain to try to install the drivers in that brief moment on windows. It is way easier to get it into fastboot from and Ubuntu live CD by installing fastboot from the software center on a Ubuntu 13.10 live CD, and then running this with the kindle unplugged and off:
Code:
fastboot -i 0x1949 getvar product
Then after it says waiting for device, plug the kindle on and wait for the device to say fastboot, from there you can boot back into windows and use kindle fire first aid to restore.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
It's not in fastboot, its just hung on the boot loader. If you have never installed the fastboot driver before I reccomend fixing this partially from Linux, your device will be detected briefly when its first turned on as a fastboot device, but it's a pain to try to install the drivers in that brief moment on windows. It is way easier to get it into fastboot from and Ubuntu live CD by installing fastboot from the software center on a Ubuntu 13.10 live CD, and then running this with the kindle unplugged and off:
Code:
fastboot -i 0x1949 getvar product
Then after it says waiting for device, plug the kindle on and wait for the device to say fastboot, from there you can boot back into windows and use kindle fire first aid to restore.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I'm glad to know I didn't break it haha. Thanks for the advice.

stunts513 said:
It's not in fastboot, its just hung on the boot loader. If you have never installed the fastboot driver before I reccomend fixing this partially from Linux, your device will be detected briefly when its first turned on as a fastboot device, but it's a pain to try to install the drivers in that brief moment on windows. It is way easier to get it into fastboot from and Ubuntu live CD by installing fastboot from the software center on a Ubuntu 13.10 live CD, and then running this with the kindle unplugged and off:
Code:
fastboot -i 0x1949 getvar product
Then after it says waiting for device, plug the kindle on and wait for the device to say fastboot, from there you can boot back into windows and use kindle fire first aid to restore.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hello,
I have found myself stuck in the same situation. I have the fastboot drivers installed and I can get into fastboot using your command. My question is about the version I have and the available restore versions.
I have the 8.4.6 software version. and I see in first aide that the newest for the HD 8.9 is 8.2.4.
I got stuck after a root attempt, the exploit worked but the files didn't install properly it seems. when I rebooted I just get stuck at the Kindle Fire screen no animation?
Any idea if it is safe to restore 8.2.4 on a 8.4.6 device? In uncertain if downgraded are safe.

Downgrades are perfectly safe, go for it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Cool thanks man, just wanted to know if there were any big don'ts before I try the downgrade.
I'll give it a go tonight after dinner.
Stupid me used the old KFFA from the rooting thread to try and root (may or may not have been the issue). I have the latest now all ready to go for the restore attempt.
Sent from my HTCONE using Tapatalk

[Q&A] [How To][Root] Kindle Fire 1 update 6.3.3/6.3.4 and Flashing FFF/TWRP [2015]

[Q&A] [How To][Root] Kindle Fire 1 update 6.3.3/6.3.4 and Flashing FFF/TWRP [2015]
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Rooting Kindle Fire Update 6.3.3 and Flashing FireFireFire and TWRP (2014)
Click link here>> (http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955) <<Click link here
Please feel free to share issues, questions and offer help
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on the topic described in the OP
[SIZE=+1]FAQs: For System Version 6.3.3 and 6.3.4[/SIZE]
[SIZE=+1]Q1: Can the Kindle Fire Utility root a Kindle Fire 1 with system version 6.3.3?[/SIZE]No, It can not​[SIZE=+1]Q2: Can the Kindle Fire Utility install a custom bootloader/recovery on a Kindle Fire 1 with system version 6.3.3?[/SIZE]No, It can not​[SIZE=+1]Q3: What can the Kindle Fire Utility with a Kindle Fire 1 with system version 6.3.3?[/SIZE]The included install.drivers.bat can install drivers on a PC
Once the Kindle is rooted, The Kindle Fire Utility can install Google Apps​[SIZE=+1]Q4: What can root a Kindle Fire 1 with system version 6.3.3?[/SIZE]SafeRoot Can [Windows/Linux/Mac]​[SIZE=+1]Q5: Can be used on Linux and Mac?[/SIZE] Yes see
The Easiest Way to Install Android's ADB and Fastboot Tools on Any OS
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) by AshtonTS
[Guide] How To Setup And Use Fastboot by demkantor

problem with step 6 " Flashing FFF and TWRP without Fastboot Cable"
HI, in the stepvto putting on the last command (fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
), stays loading and does not advance, what i can do in this case? even is loading, says: waiting for the device. and nothing happen, now the kindle not start and stays on the logo.. and does not recognize my laptop or pc in Usb.

skins20 said:
HI, in the stepvto putting on the last command (fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
), stays loading and does not advance, what i can do in this case? even is loading, says: waiting for the device. and nothing happen, now the kindle not start and stays on the logo.. and does not recognize my laptop or pc in Usb.
Click to expand...
Click to collapse
How is kindle listed in device manager?
Sent from my XT894 using Tapatalk

sd_shadow said:
How is kindle listed in device manager?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
just say "kindle" in device manager.

skins20 said:
just say "kindle" in device manager.
Click to expand...
Click to collapse
Did you get drivers installed?

x2110311x said:
Well, I tried that, and I ended up bricking my kindle (most likely because I tried the experimental version of his binaries) and neither of my computers (one runs linux, one Windows) are able to see the device correctly. Windows shows it as an unknown device, but I have the fastboot drivers installed. That's why I said I need a factory cable, hoping that I'd be able to get it into fastboot to repair it
Click to expand...
Click to collapse
I have little experience with Linux, but windows will not work till drivers are correct.
Did you in device manager uninstall unknown device, remove driver if asked, install drivers with Kindle Fire Utility's install.drivers.bat, reboot pc and kindle
may take a few reboots to get it.
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
x2110311x said:
Well, I tried that, and I ended up bricking my kindle (most likely because I tried the experimental version of his binaries)
Click to expand...
Click to collapse
what binaries? su? you didn't install TWRP/FFF?
What is it doing now?

sd_shadow said:
I have little experience with Linux, but windows will not work till drivers are correct.
Did you in device manager uninstall unknown device, remove driver if asked, install drivers with Kindle Fire Utility's install.drivers.bat, reboot pc and kindle
may take a few reboots to get it.
Click to expand...
Click to collapse
I've done work with fastboot on my kindle fire with this computer before, probably only like a month ago, so I don't think that was the issu
sd_shadow said:
what binaries? su? you didn't install TWRP/FFF?
What is it doing now?
Click to expand...
Click to collapse
Sorry, I didn't mean to say binaries, I wrote that response in a rush.
I used Pokey9000's experimental version of fbmode.
Right now, whenever I try turning it on, the green LED stays on, and it just stays at the "Kindle Fire " screen. Neither fastboot nor adb are recognizing it at this point.

x2110311x said:
I've done work with fastboot on my kindle fire with this computer before, probably only like a month ago, so I don't think that was the issu
Sorry, I didn't mean to say binaries, I wrote that response in a rush.
I used Pokey9000's experimental version of fbmode.
Right now, whenever I try turning it on, the green LED stays on, and it just stays at the "Kindle Fire " screen. Neither fastboot nor adb are recognizing it at this point.
Click to expand...
Click to collapse
If all you used is the alt fbmode file, it is likely in fastboot mode, which just shows Kindle fire screen with no animation.
If there is animation on the kindle fire screen, it's bootlooping...

It turns out that it was just stuck in fastboot, and windows was having some issues. I did nothing to the drivers, and it worked fine after trying again

Stuck on Kindle Fire(Doesn't Change) screen
Hello,
Sorry if this is addressed somewhere else, as I have been unable to find it.
I successfully rooted my kindle fire, then made it all the way to the "fastboot" part of step 6 of the fff and twrp post. The command prompt stuck at waiting for device. The kindle fire is now stuck on the unchanging kindle fire logo. I have tried the unbricking utility, holding the power button down for 20 sec. removing the device and drivers under device manager(I saw this somewhere else).
Any help would be greatly appreciated!

dharangamer said:
Hello,
Sorry if this is addressed somewhere else, as I have been unable to find it.
I successfully rooted my kindle fire, then made it all the way to the "fastboot" part of step 6 of the fff and twrp post. The command prompt stuck at waiting for device. The kindle fire is now stuck on the unchanging kindle fire logo. I have tried the unbricking utility, holding the power button down for 20 sec. removing the device and drivers under device manager(I saw this somewhere else).
Any help would be greatly appreciated!
Click to expand...
Click to collapse
99% of the time drivers are the issue
How is it listed inn device manager?
---------- Post added at 05:05 PM ---------- Previous post was at 05:04 PM ----------
Which windows version? 7, 8?

It is listed as 'other devices' and then kindle in the drop down from that. I am running windows 8.1 at the moment.
Btw, thank you so much for the help you've already provided, the youtube video and your posts really helped me figure out how to troubleshoot and eventually root it successfully.

dharangamer said:
It is listed as 'other devices' and then kindle in the drop down from that. I am running windows 8.1 at the moment.
Btw, thank you so much for the help you've already provided, the youtube video and your posts really helped me figure out how to troubleshoot and eventually root it successfully.
Click to expand...
Click to collapse
With windows 8, You need to disable driver signature enforcement, before installing drivers, and use the Instal.drivers.bat from Kindle Fire Utility

That took care of it. Thank you so much!

help on kindle 7.5.1
How can I root my KINDLE fire hd whose firm got upgraded to 7.5.1 thanx a lot

nilnyl said:
How can I root my KINDLE fire hd whose firm got upgraded to 7.5.1 thanx a lot
Click to expand...
Click to collapse
see http://forum.xda-developers.com/fire-hd/help/how-to-root-kindle-fire-hd-7-firmware-7-t2931436

Can't root KindleFire
hi I am trying to root my kindle but it does work I use the Saferoot way and it does work

Corrupted settings.db- stuck in boot loop
Help, I toasted my Kindle Fire!
Ok, now that I got that out of the way, here's the details. I followed the steps from SDShadow's first post on how to root my Kindle Fire (6.3.3) and it worked great. Many thanks SDShadow! What followed was how I went off the reservation.
My purpose in rooting was to change 'mock_locations' to 1 so that I can receive GPS position over wifi and use my Kindle screen for navigation. Being focused on my end goal, I did not take the time to install Google Apps or FFF or TWRP. My mistake. Another thread (http://forum.xda-developers.com/showpost.php?p=19688907&postcount=1) gave directions to do update 'mock_locations', but as with others on that thread, I ran into permission errors. Unable to figure out SQLite3, but able to find the 'settings.db' using ESFileExplorer, I managed to corrupt the file.
Not knowing how to test the updated 'settings.db' in any way, I copied the corrupted version to my Kindle and rebooted. The Kindle never finished booting, and that's when I realized that I must have corrupted the file. But now I can't copy my backup file where it needs to go because my Kindle never finishes booting to give me access to ESFileExplorer on the Kindle. I still have adb access to the Kindle from my computer, but still get permission errors when I try to push a file.
Is there a workaround to upload my backup settings.db file through adb, or do I need a factory cable? Does the workaround involve installing FFF and TWRP through adb while the Kindle is in its reboot loop? Either way, can someone provide detailed instructions for that?
BTW, I figured out how to modify my settings.db using SQLite3 Browser on my PC. So I can actually upload my desired file, if I can figure out how. But if I could perform a check in some way, that would be good...

cwaskey said:
Help, I toasted my Kindle Fire!
Ok, now that I got that out of the way, here's the details. I followed the steps from SDShadow's first post on how to root my Kindle Fire (6.3.3) and it worked great. Many thanks SDShadow! What followed was how I went off the reservation.
My purpose in rooting was to change 'mock_locations' to 1 so that I can receive GPS position over wifi and use my Kindle screen for navigation. Being focused on my end goal, I did not take the time to install Google Apps or FFF or TWRP. My mistake. Another thread (http://forum.xda-developers.com/showpost.php?p=19688907&postcount=1) gave directions to do update 'mock_locations', but as with others on that thread, I ran into permission errors. Unable to figure out SQLite3, but able to find the 'settings.db' using ESFileExplorer, I managed to corrupt the file.
Not knowing how to test the updated 'settings.db' in any way, I copied the corrupted version to my Kindle and rebooted. The Kindle never finished booting, and that's when I realized that I must have corrupted the file. But now I can't copy my backup file where it needs to go because my Kindle never finishes booting to give me access to ESFileExplorer on the Kindle. I still have adb access to the Kindle from my computer, but still get permission errors when I try to push a file.
Is there a workaround to upload my backup settings.db file through adb, or do I need a factory cable? Does the workaround involve installing FFF and TWRP through adb while the Kindle is in its reboot loop? Either way, can someone provide detailed instructions for that?
BTW, I figured out how to modify my settings.db using SQLite3 Browser on my PC. So I can actually upload my desired file, if I can figure out how. But if I could perform a check in some way, that would be good...
Click to expand...
Click to collapse
best option is fastboot cable, but you can try some adb commands like
Code:
adb devices
you will need adb files
power off kindle, run command, turn on kindle, also can try
Code:
fastboot devices
if you get one of them to work we have some options

sd_shadow said:
best option is fastboot cable, but you can try some adb commands like
Code:
adb devices
you will need adb files
power off kindle, run command, turn on kindle, also can try
Code:
fastboot devices
if you get one of them to work we have some options
Click to expand...
Click to collapse
Code:
adb devices
does show my Kindle serial number. As I said, adb seems to be working, despite the fact that the Kindle doesn't complete the boot process.
I have not installed or tried fastboot on my PC, so I can't answer whether that works.
Edit: I should mention that when the Kindle was still running, I allowed just about every permission in the on-Kindle superuser app.

Bricked 1st Gen KF.

Howdy all, I have an old KF here that I have bricked. I'm stuck at the logo. I'm trying to issue shell commands and I get the "- exec '/system/bin/sh' failed: No such file or directory (2)" error. So far I've found that this means I screwed up my /system when I tried getting this thing back to stock. I cannot remember what I was running on it earlier today.
I do know that I downloaded a factory update.zip and installed that from TWRP. I wiped everything before hand. I'm afraid wiping the SD card after installing the update.zip may have caused me to be stuck at the logo without being able to issue shell commands? I've tried the KindleFireUtility and KindleUnbrickUtility and a few things with soupkit. Nothing is working.
I seem to have found a few hints that there are indeed workarounds to this problem without having to make or buy a factory cable. I'm terrible at soldering.. much better at typing in terminals.
If there is any help out there, I would massively appreciate it.
All I want to do is read a d*** book.
-Ellison
UPDATE:
I bought a fastboot cable.
It appears that I can boot in to fastboot mode (Kindle Fire logo, green light, and screen never dims) but I think at some point, the device gets lost. I installed the android bootloader ADB drivers for the fastboot mode. If I start the kindle without the factory cable and it boots normally and sits at the logo screen forever, it gets listed as an ADB device. While the kindle is still attached, I can reboot it in to what I am assuming is fastboot mode. My Windows10 rig sees it as a composite ADB bootloader interface. But I can't get unBrickUtility to do anything... the only thing I saw it do to the kindle was wipe the userdata. Other than that, UnBrickUtility cannot see my kindle in fastboot mode.
Unplugging my factory cable and plugging it back in causes the kindle to be completely unrecognized ( unknown usb device set address failed) on Windows 10.
I have soupkit running on a netbook... it tells me that my shell is damaged, which I know is the problem. But now I'm not sure what to do next as I can't get linux (mint) to recognize my kindle in fastboot mode either.
I really hope someone out there has been here before and can help. I'd love to see this thing running back to normal again.
related image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE: I FIXED IT.
What ultimately saved this device was being able to get in to fastboot mode. I bough the cable, flashed FFF and TWRP from fastboot mode. I then found I could not run shell commands. I fixed this by running
Code:
fastboot oem format
from fastboot mode. Then going back in to TWRP, I was able to mount /System and was then able to use Soupkit's kindle fire utility to fix the /sdcard. The version of TWPR I was using would not flash the stock update, so I downloaded and flashed that. Afet that installed, I was able to flash the stock update and now I'm up and running again! WOO! Thank you so much for the developers here!!!
Admin: can I get the thread title so reflect the fact that I have fixed this for future users? Thank you!

most likely need a fastboot cable
did you try command
adb devices
Sent from my KFFOWI using Tapatalk

bump for update!

Help
I have a question, I acquired from a guy from another repair shop a couple first gen kindle fire's and one has the red screen upon boot. I have tried to attach it to my pc and I get a USB driver error. Says can't install driver even though I have the driver installed. Also when it pops up in device manager it shows up as Otter 2 prod 4. Only thing I can think of is the person before me flashed the kindle fire hd bootloader to the device. Any ideas on a fix? I have a fastboot cable if that helps. Also when I attach the device to my computer it shows me fast boot with a flashing green light and a solid red one.

arsonone said:
I have a question, I acquired from a guy from another repair shop a couple first gen kindle fire's and one has the red screen upon boot. I have tried to attach it to my pc and I get a USB driver error. Says can't install driver even though I have the driver installed. Also when it pops up in device manager it shows up as Otter 2 prod 4. Only thing I can think of is the person before me flashed the kindle fire hd bootloader to the device. Any ideas on a fix? I have a fastboot cable if that helps. Also when I attach the device to my computer it shows me fast boot with a flashing green light and a solid red one.
Click to expand...
Click to collapse
otter 2 is kindle Fire 2 (2nd generation /2012)
Sent from my KFFOWI using XDA Labs

umm...
sd_shadow said:
otter 2 is kindle Fire 2 (2nd generation /2012)
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yeah I know, that's what I was saying. Whoever had this thing before me flashed it with the kindle fire 2 rom or whatever not entirely sure. The model number is D10400 which is the first gen. Any clue if it can be saved? Right now I can't get it to connect to my PC or I'd just flash it

arsonone said:
Yeah I know, that's what I was saying. Whoever had this thing before me flashed it with the kindle fire 2 rom or whatever not entirely sure. The model number is D10400 which is the first gen. Any clue if it can be saved? Right now I can't get it to connect to my PC or I'd just flash it
Click to expand...
Click to collapse
i think Amazon used D10400 for both 1st and 2nd generation fires
at least there have been several people ask about a D10400 with a 2nd generation bootloader, trying to flash 1st generation bootloader has always ended up with a bricked device
but if it doesn't connect to pc now, cannot do anything anyways
Sent from my KFFOWI using XDA Labs

sd_shadow said:
i think Amazon used D10400 for both 1st and 2nd generation fires
at least there have been several people ask about a D10400 with a 2nd generation bootloader, trying to flash 1st generation bootloader has always ended up with a bricked device
but if it doesn't connect to pc now, cannot do anything anyways
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
It's a paperweight now lol. I got it to connect and flashed FFF to it as well at the rest of the software needed and when I typed in reboot into the fastboot cli it went dark and wont power back on now...oops lol

arsonone said:
It's a paperweight now lol. I got it to connect and flashed FFF to it as well at the rest of the software needed and when I typed in reboot into the fastboot cli it went dark and wont power back on now...oops lol
Click to expand...
Click to collapse
yep
Sent from my XT1060 using XDA Labs

... still need help. Can't seem to find any straight-forward threads on fixing partitions and/or /shell.

lsngregg said:
... still need help. Can't seem to find any straight-forward threads on fixing partitions and/or /shell.
Click to expand...
Click to collapse
don't use Unbrick utility, it doesn't work with newest versions 6.3.3 or 6.3.4
How to flash twrp and firefirefire with a Fastboot cable
Sent from my KFFOWI using XDA Labs

sd_shadow said:
don't use Unbrick utility, it doesn't work with newest versions 6.3.3 or 6.3.4
How to flash twrp and firefirefire with a Fastboot cable
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Currently, I'm able to attempt to flash the stock ROM.
I was able to fix the /sdcard by first running the "fastboot oem format" command in fasboot mode and then mouting /System in TWRP enabled being able to run shell commands. So I fired up my "bug" (a netbook running Mint) and had Soupkit fix sd card problems. That worked.
Now I'm stuck at not being able to flash the stock ROM because of a
Code:
E: unknown command [err_string]
getProp("ro.build.product") == blaze
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle..... .zip'

lsngregg said:
Currently, I'm able to attempt to flash the stock ROM.
I was able to fix the /sdcard by first running the "fastboot oem format" command in fasboot mode and then mouting /System in TWRP enabled being able to run shell commands. So I fired up my "bug" (a netbook running Mint) and had Soupkit fix sd card problems. That worked.
Now I'm stuck at not being able to flash the stock ROM because of a
Click to expand...
Click to collapse
which twrp version?
Sent from my DROID Turbo using XDA Labs