This is a replacement bootloader so you can get into recovery with just the one power button. It's very simple to use, just turn on the Fire, and when the logo pops up press the power button.
FIREFIREFIRE also makes fastboot easy. For a few seconds on every boot, fastboot is enabled; no idme bootmode or special cable needed. The USB ID is changed to one that's supported by even the oldest fastboots. Unlike the stock, you do not need to use the "-i 0x1949" on every run of fastboot.
Now FIREFIREFIRE can fix your partition tables. "fastboot oem format" will overwrite the partition table with the stock table. You can use this to revert to factory partitioning if you have been messing with parted or the like, or can be used with the USB boot kit (Rekindle) to manually rebuild a totally bricked Fire. Running this command on 1.0 or earlier will fail.
Release notes:
1.2 - MD5: a8c8d702606de8ab7e73b898de50b4b6 u-boot.bin
Merge in 6.2->6.2.1 changes: low battery charge safety shutdown, official offsets for NVRAM params
The power LED now tells you more stuff: dim slightly while in fastboot / ready to detect recovery button press, bright green again when the boot of standard OS starts, more orangey orange when recovery starts
Fix Amazon's broken LED code
1.1 - MD5: 7a4f1a2ff60b13a3534df318f99d813c u-boot.bin
Fixed the built-in partitioning to match the partition map on a stock KF
Removed USB PID version. Realized this would screw up Windows. VIDID will always be 18d1:0100 from now on
1.0
Fastboot USB VID switched to Google's VID. Once this is installed you don't need to use "-i 0x1949" on every fastboot command
USB PID reflects the version. 0x0100 is version 1.0, 0x0402 is 4.2, etc
0.9
New logo with "press power button for recovery" message at the bottom
Delays ~10 seconds if no button pressed, but pushing the button immediately goes into recovery
During the delay, you can connect with fastboot. Works under Linux, but the delay may be too short for Windows
Howto flash
The TWRP installer flashes FFF 1.0 when it's run. For most purposes this is ok, but because TWRP has been orphaned, I can't recommend it as a way to get the latest. By the time you read this, KFU should support flashing FFF, and for Windows users is by far the easiest way.
Howto flash by hand
Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. Currently KFU or fbmode is the easiest
flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
reboot: "fastboot -i 0x1949 reboot"
Howto backup EVERYTHING (on Linux):
(not relevant in this post anymore, but good reference)
This will back up all partitions and the hidden NVRAM data. If you ever have to restore from scratch, you can get fastboot to write a new partition table and then fastboot in these backups
Need >8GB local free, and adb installed and able to get a shell.
Make a new directory to store the dump files and cd into it.
Make sure that your KF is running adb as root. As of 6.2.1 this requires running BurritoRoot, then "adb root" on your PC after it completes.
Then run in a terminal:
Code:
for F in `seq 1 12`; do adb pull /dev/block/mmcblk0p$F; done
adb shell idme ? > nvram.txt
On a brand new KF, this backup will bzip2 down to ~300MB. Once you start writing to the flash, this will go up even if you delete files due to nonempty free blocks.
github is now up at https://github.com/pokey9000/kf_u-boot
So will this still work with 6.2? I'm confused. Anyway, this is awesome! Just what we needed
Sent from my ADR6400L using Tapatalk
Yeah, a boring video of the "factory cable" method since the nvram boot mode is broke would be useful But awesome that it works.
I can't remember what the device was doing before the update but now if I try adb commands for recovery, bootloader, and fastboot, it looks like there is some response. I don't actually get in to recovery but it looks like maybe the device is rebooting in to fastboot. I don't have a ton of experience with this but just figured it was worth mentioning.
SikYou said:
So will this still work with 6.2? I'm confused. Anyway, this is awesome! Just what we needed
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I just need to debug it. For some reason even the u-boot that comes with the 6.2 source drop doesn't respect the new NVRAM layout. This is just a proof of concept since TWRP is still AWOL, so don't worry. I plan to make the button handling a little more robust, including a way to select recovery or fastboot with just the button so you can ditch the Fire ROM altogether.
SikYou said:
I can't remember what the device was doing before the update but now if I try adb commands for recovery, bootloader, and fastboot, it looks like there is some response. I don't actually get in to recovery but it looks like maybe the device is rebooting in to fastboot. I don't have a ton of experience with this but just figured it was worth mentioning.
Click to expand...
Click to collapse
I noticed that too. I tried building the u-boot from the 6.2 source drop and it doesn't detect when I set the bootmode either, but the one in the update .bin does.
pokey9000 said:
I just need to debug it. For some reason even the u-boot that comes with the 6.2 source drop doesn't respect the new NVRAM layout. This is just a proof of concept since TWRP is still AWOL, so don't worry. I plan to make the button handling a little more robust, including a way to select recovery or fastboot with just the button so you can ditch the Fire ROM altogether.
Click to expand...
Click to collapse
Sounds great, looking forward to seeing the finished product.
Sent from my Kindle Fire using Tapatalk
Xeddicus said:
Yeah, a boring video of the "factory cable" method since the nvram boot mode is broke would be useful But awesome that it works.
Click to expand...
Click to collapse
There you go.
BTW, have you been in touch with agrabren from TWRP? He is the one kinda spearheading the KF TWRP project and I think one of the issues was not having a reliable method for booting to recovery; if that is the case you have obviously done a lot of work towards solving that problem.
Sent from my Kindle Fire using Tapatalk
This is awesome!
Not trying to nitpick, but is there a way to add on-screen options or no?
death2all110 said:
This is awesome!
Not trying to nitpick, but is there a way to add on-screen options or no?
Click to expand...
Click to collapse
Maybe at some point. I'm just trying to get something that works for now. With one button there isn't much benefit imho other than a message that says "press button now for recovery"
pokey9000 said:
Maybe at some point. I'm just trying to get something that works for now. With one button there isn't much benefit imho other than a message that says "press button now for recovery"
Click to expand...
Click to collapse
Well fine then! I see how it is. Just shoot everyone down... jk
Great work man!
But that is what I was thinking, It can either normal boot and get shown a brief message like "Press Power Button again to boot in.to recovery." And if you hit the button again it boots recovery.
death2all110 said:
Well fine then! I see how it is. Just shoot everyone down... jk
Great work man!
But that is what I was thinking, It can either normal boot and get shown a brief message like "Press Power Button again to boot in.to recovery." And if you hit the button again it boots recovery.
Click to expand...
Click to collapse
Thanks
Right now it goes into recovery if you just hold the power button down when turning it on instead of just hitting it quick. I could add a delay and just throw some text at the bottom of the boot logo. Hmm... now that I think about it, how about this:
-Boots up, shows a splash screen with the logo and some text like "hold down power for recovery"
-Listens for fastboot for up to 5 seconds, enough to run fastboot on the commandline real quick
-If it doesn't get a fastboot connection in 5 seconds, it checks the state of the power button
-If the power button is pressed, boot recovery, or else boot normal
Also if anyone has any better logos than what I've got now... Requirements are that most of the screen area must be a single color like the current logo, or the logo won't compress well enough, and must be 600x1024.
pokey9000 said:
Thanks
Right now it goes into recovery if you just hold the power button down when turning it on instead of just hitting it quick. I could add a delay and just throw some text at the bottom of the boot logo. Hmm... now that I think about it, how about this:
-Boots up, shows a splash screen with the logo and some text like "hold down power for recovery"
-Listens for fastboot for up to 5 seconds, enough to run fastboot on the commandline real quick
-If it doesn't get a fastboot connection in 5 seconds, it checks the state of the power button
-If the power button is pressed, boot recovery, or else boot normal
Also if anyone has any better logos than what I've got now... Requirements are that most of the screen area must be a single color like the current logo, or the logo won't compress well enough, and must be 600x1024.
Click to expand...
Click to collapse
I'd be willing to create a cool boot-logo, how would just a flame in the background and some text saying "FireFireFire Bootloader" on top of it?
I dunno if it's just me but once I read the title FIREFIREFIRE I pictured Beavis and Butthead. One day..
MrJandD said:
I'd be willing to create a cool boot-logo, how would just a flame in the background and some text saying "FireFireFire Bootloader" on top of it?
Click to expand...
Click to collapse
I was actually thinking of something getting away from the name of the bootloader since in the scheme of the user experience it's pretty insignificant. Andy with some flames in the background maybe, or a Nook Tablet on fire (yes, i'm that bitter and petty)
Thelgow said:
I dunno if it's just me but once I read the title FIREFIREFIRE I pictured Beavis and Butthead. One day..
Click to expand...
Click to collapse
That's exactly what was going on at 1am... I needed to make a splash screen (Amazon doesn't include the stock one in the source, trademark and all that) and I typed the first thing that popped into my head into the editor.
pokey9000 said:
I was actually thinking of something getting away from the name of the bootloader since in the scheme of the user experience it's pretty insignificant. Andy with some flames in the background maybe, or a Nook Tablet on fire (yes, i'm that bitter and petty)
Click to expand...
Click to collapse
Hard to make a nook tab one color
How about the text FireBoot?
Im open to idea's.
First Edition.
How about 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"
}
MrJandD said:
Hard to make a nook tab one color
How about the text FireBoot?
Im open to idea's.
Click to expand...
Click to collapse
It doesn't have to be one color. The image has to be mostly background and the background must be a solid color. It all has to do with RLE compression, like GIF or faxes where black text on a white page compresses down really small. There's only about 8-10k to spare for the boot splash, so we can't just put up a full screen photo of something or smooth gradients.
Related
{
"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.
My Mac is not seeing the Kindle device and it is stuck at the FFF yellow triangle.
(update)
Now I have recovery options seen below. What is the best and easiest way to go back stock from here? I have downloaded the kindle fire update from Amazon.
{
"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"
}
So I took the update from amazon, renamed the bin to zip, and put it on the SD card. In recovery I hit update from SD card. Now it is stuck on the OEM kindle fire logo. Is this where I HAVE to have a factory cable?
No, you need to use the mount function in recovery to mount your sdcard. When mounted it will show up as an external drive on your computer. Transfer a new rom and the latest version of firefirefire from your computer to your sdcard. FFF 1.4 now comes in a flashable "Flash.zip" that can be installed in recovery.
Read about the new FFF and how to use it here: http://forum.xda-developers.com/showthread.php?p=25598837
Make ABSOLUTELY SURE that you have done an md5check on FFF before installing in recovery.
Install a new rooted rom in recovery and if you need to, use the new FFF to change your bootmode to normal (fixes stuck at boot logo)
Then, read this guide in it's entirety: http://forum.xda-developers.com/showthread.php?p=23747567
soupmagnet said:
No, you need to use the mount function in recovery to mount your sdcard. When mounted it will show up as an external drive on your computer. Transfer a new rom and the latest version of firefirefire from your computer to your sdcard. FFF 1.4 now comes in a flashable "Flash.zip" that can be installed in recovery.
Read about the new FFF and how to use it here: http://forum.xda-developers.com/showthread.php?p=25598837
Make ABSOLUTELY SURE that you have done an md5check on FFF before installing in recovery.
Install a new rooted rom in recovery and if you need to, use the new FFF to change your bootmode to normal (fixes stuck at boot logo)
Then, read this guide in it's entirety: http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thank you , but how am I going to use recovery if I am stuck at the kindle fire OEM logo after hitting update in recovery as seen under the picture? The only way I can see the kindle is to mount breakdroid and do an ADB check, but it still doesn't mount the SD card.
I've been staring at this for 12 hours.
iphonedownload said:
Thank you , but how am I going to use recovery if I am stuck at the kindle fire OEM logo after hitting update in recovery as seen under the picture? The only way I can see the kindle is to mount breakdroid and do an ADB check, but it still doesn't mount the SD card.
Click to expand...
Click to collapse
Okay it seems as there is a breakdown in communication here, so let's try to figure this out.
The OEM Kindle Fire logo that you see is the bootloader. The bootloader has several bootmodes to boot from. You want it to boot into normal bootmode (4000) but instead you're booting into fastboot (4002). When the new update tried to install itself it saw that you were using a modified system and caused the error. Installing the new FFF will fix your bootmode problem, but you still need a working rom to boot into (preferably a custom rom). If you like the stock rom, MoDaCo is a good alternative until there is enough information about the 6.3.1 update.
If you can't mount your sdcard in recovery you should still be able to boot into recovery and "adb push" a rom.zip and the FFF Flash.zip to your sdcard for flashing in recovery.
soupmagnet said:
If you can't mount your sdcard in recovery you should still be able to boot into recovery and "adb push" a rom.zip and the FFF Flash.zip to your sdcard for flashing in recovery.
Click to expand...
Click to collapse
Thank you very much for the info. This is pretty much where I am stuck as I do not know how to do what you described. Even as long as I have been here I still haven't been bothered with terminal commands on my mac until recently. New world for me. Gotta learn sometime.
I have tried every way possible to "boot in recovery" and nothing is helping. If I can just get it back stock I'll start from scratch, but I'd need a few instructions if you would mind saving my butt here and telling me how to do as you describe. I'm hung at the logo and the mac doesn't see the Kindle SD card so can I get maybe an A, B, C recovery explanation from you this once? I'm sure I'll return the favor one day.
I can't mount the SD, but I do have some power over the Kindle.
With Mac it should be fairly easy (I'll try to make it as easy as possible).
First and foremost, turn off your device while I write up a tutorial so your battery doesn't die and leave you in a worse place than you are now.
soupmagnet said:
With Mac it should be fairly easy (I'll try to make it as easy as possible).
First and foremost, turn off your device while I write up a tutorial so your battery doesn't die and leave you in a worse place than you are now.
Click to expand...
Click to collapse
Thanks a bunch! it's plugged in and fully charged. It was at 75% when everything went bad and it had an orange light, now it has green so I believe it went ahead and charged to 100%.
At the moment this is all I seem to be able to do. Mostly limited to my lack of knowledge of command. (tried it other ways too, just not doing it right)
Find copies of the following files and place them on your desktop.
TWRP 2.1
FireFireFire 1.4 Flash.zip
fastboot
adb
Rename the openrecovery-twrp-blaze-2.1.1.img to twrp.img (just to make it easy) Make sure FireFireFire is named Flash.zip
Open a new terminal window and enter the following commands
Code:
cd desktop
...and because you are already in fastboot mode (4002)...
Code:
fastboot -i 0x1949 flash recovery twrp.img
When you get a prompt that says "waiting for device" turn your Kindle on. You should see that the image was installed.
Now you have to change your bootmode to recovery
Code:
fastboot -i 0x1949 oem idme bootmode 5003
Code:
fastboot reboot
If the device doesn't reboot automatically, hold the power button until it shuts off then restart. The device should boot into recovery.
While in recovery you can only enter adb commands.
Code:
adb push Flash.zip /sdcard
Then use the same command to push whatever custom rom you want installed (not pure stock for now)
...when finished select install, and on the right-hand side of the screen select and install Flash.zip If you dont see the files you pushed to your Kindle, reboot and they should show up. That will install FireFireFire1.4
Use the same steps to install custom rom. Before installing custom roms, make sure you perform a "factory reset" (wipe data), wipe system, wipe cache, and wipe Dalvik cache.
Then reboot
Your Kindle Fire splash screen should now be blue. As soon as you see it for the first time press and hold the power button until it turns orange. There will be options on the bottom. Hold the power button for a second to cycle through the options. You want to change your bootmode to "normal". It will select automatically after a few moments. If the "normal" selection doesn't work try "reset bootmode"
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
iphonedownload said:
Thanks a bunch! it's plugged in and fully charged. It was at 75% when everything went bad and it had an orange light, now it has green so I believe it went ahead and charged to 100%.
At the moment this is all I seem to be able to do. Mostly limited to my lack of knowledge of command. (tried it other ways too, just not doing it right)
Click to expand...
Click to collapse
OMG You're lucky you didn't hard-brick your device with that.
Thank you so much, it's not going past waiting for device.
Open a new terminal window and enter the following commands
Code:
cd desktop
...and because you are already in fastboot mode (4002)...
Code:
fastboot -i 0x1949 flash recovery twrp.img
When you get a prompt that says "waiting for device" turn your Kindle on. You should see that the image was installed
Click to expand...
Click to collapse
Path to desktop
Video:
(the kindle logo is not actually oscillating, just appears that way)
http://www.youtube.com/watch?v=xplRRqUgv78
Keep trying it, sometimes it doesn't work right away. You could try entering the command with the device turned on to see if that works. Keep at it. It will work.
If after a few tries, it still doesn't work, make sure you are actually in fastboot:
fastboot -i 0x1949 oem idme bootmode 4002
[Edit:] ignore
[Edit2:] It's hard to tell from the video but, is the Kindle Fire logo actually flashing? Nevermind, you already answered that.
Thank you, I am actually getting waiting for device on that as well
Okay hold on a second. How were you able to get adb to connect? What happens when you type:
Code:
adb devices
If it returns a string of numbers, then try:
Code:
adb shell idme bootmode 4002
adb reboot
...and that will put you in fastboot so you can enter fastboot commands
soupmagnet said:
Okay hold on a second. How were you able to get adb to connect? What happens when you type:
Code:
adb devices
Click to expand...
Click to collapse
Well I have been booting in Snow Leopard and when I do I get:
When I boot in Lion I get:
soupmagnet said:
If it returns a string of numbers, then try:
Code:
adb shell idme bootmode 4002
adb reboot
...and that will put you in fastboot so you can enter fastboot commands
Click to expand...
Click to collapse
When I do that in Snow Leopard (the only OS I have been using for this) I get the same error any shell command gives me.
That sucks...It looks like you messed up your shell somehow. If that's the case, you need a factory cable before you can go any further.
Well it's ok electronics is what I do. I can have one made up in less than ten minutes. What do I do once I make it?
(and THANK YOU!)
You need the command for installing FFF1.4 with adb. I know most of it but I forgot which partition the bootloader is on. I'll look around to see if I can find it.
[Edit:] Nevermind, you need a shell for that as well.
Thank you, I'll make the cable.
The factory cable will force you into fastboot mode. You need it to flash recovery and firefirefire.
OK so when I make this cable (I'm going to use a 1k resistor since that seems to be the recommendation) and plug it in, turn the kindle on, it will look the same, but be in fastboot mode, then from there I'll do whatever I need just let me know.
When you get it into fastboot mode start over from...
Code:
fastboot flash recovery twrp.img
[Edit:] let me know if you succeded in installing twrp
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.
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
NavyLCDR said:
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
Click to expand...
Click to collapse
Can it boot into TWRP?
If it can
Code:
adb reboot bootloader
This should get you into fastboot
EDIT:
I so misread the question...so you are stuck at the blue KindFire boot screen and not the TWRP boot screen right?
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
NavyLCDR said:
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
Click to expand...
Click to collapse
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
LinearEquation said:
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
Click to expand...
Click to collapse
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
NavyLCDR said:
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
Click to expand...
Click to collapse
No, they are not the same thing. One reboots into the bootloader and the other reboots into recovery. My comment had nothing to do with testing a reboot and everything to see if you can enter fastboot mode.
Since you have now stated you can enter TWRP, use this tutorial to push a ROM onto TWRP and then just flash it from there. http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation,
I know that adb reboot bootloader and adb reboot recovery are not the same commands and I know that they are not SUPPOSED to do the same thing. HOWEVER, on MY Kindle both commands ARE doing the same thing. And that is why I know something is wrong. Both commands on MY Kindle ARE having the same result: the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns off.
Why would I want to reinstall a ROM from TWRP when I have a ROM installed? Once I press the power button, if I let it go it boots into CM 10.2 just fine or I can boot into TWRP by pressing the power button at the right time. I cannot reboot in TWRP or fastboot using software commands, and I don't even know if it is supposed to be that way, or if it is a problem.
I did not (and still don't) know if it is normal for the only way to get into fastboot is with a cable after CM 10.2 is installed (and I don't know if I can get into fastboot that way for a few more days), or if I need to reflash a bootloader file or which bootloader file I need to reflash.
I hope that clarified what my problem is.
Good day, I gonna be quickly.
Device information:
Kindle fire 8.9
System Version: 8.4.6_user_4620220
I'd like to install CM10.2 on my table, so i follow the next tutorial to get root, recovery, 2nd-bootloader, etc: (I can't post links but it's from the webpage wwwDOTrootkindlefireDOTcom, the article is called "How to Root & Convert Kindle Fire HD 8.9 into Pure Android Tablet!"
I follow every step as was there with two exception,
I change:
1. kfhd8-freedom-boot-8.4.3.img for kfhd8-freedom-boot-8.4.6.img (from official post of Hashcode)
2. and kfhd8-twrp-2.6.0.0-recovery.img for kfhd8-twrp-2.6.3.1-recovery.img (from official post of Hashcode)
everything went right, not errors, no mistake, just fine.
when i try to go into recovery by pressing power bottom and then volumen up, it doesn't do anything, i have tried with few seconds, holding it together, nothing works.... the table is working normal, once it turn on show the yellow logo, then the blue logo, and then yellow logo again and star normally the amazon os...
So am i doing something wrong? what should i do?
one more thing, the blue logo doesn't show up quickly as the video i saw, after the yellow logo it fades, turn off, on before stay quiet normaly, and then the yellow one again. is that normal?
Thank you very much.
Its in this order like this: turn on, let go of power button, hold volume down button until you see blue logo, and either continue holding it or let go as you see fit until you see the twrp logo. You can also get into recovery from in the os by using a mobile terminal and running something like
Code:
su -c "reboot recovery"
hope this helps!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its in this order like this: turn on, let go of power button, hold volume down button until you see blue logo, and either continue holding it or let go as you see fit until you see the twrp logo. You can also get into recovery from in the os by using a mobile terminal and running something like
Code:
su -c "reboot recovery"
hope this helps!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Now after i enter the command my kindle won't turn on, it stuck on the yellow logo.
any other solution?... i gonna leave some doubts i have.
what would happen if i re flash everything after the root, i mean reflash the kfhd8-twrp-2.6.3.1-recovery.img, kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin? will i brick my kindle fire? what happen if i re flash a older version of recovery? and boot?
Any suggestion what should i do now?
Um that's kinda odd, maybe twrp didn't flash correctly, even then I wouldn't expect recovery to corrupt itself that badly. Try restoring with kindle fire first aid and give it another shot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um that's kinda odd, maybe twrp didn't flash correctly, even then I wouldn't expect recovery to corrupt itself that badly. Try restoring with kindle fire first aid and give it another shot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
i didn't make a back up of the system (i want it to do it thought twrp) and was the version 8.4.6, can i find any back up of that version here?
Edit: I kinda understand how that works now, i don't need the image of system, I'm downloading it to try to restore it, if not I'm going to use this method: http://forum.xda-developers.com/showthread.php?t=2011126. is that a good thing to do?
Thanks for everything, I'm sure my kindle will come back to life later.
That tool should work too, go for it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That tool should work too, go for it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good morning..
I tried eveything yesterday but it won't pass the waiting for devices, with both application, but yesterday night i was able to go to the fastboot, with the fastboot today i can't go to fastboot with fastboot -i 0x1949 getvar product it just turn on the kindle to stay stuck in kindle logo.. i might be wrong but i think this might be because i tried to many drivers... i don't know.
What can i do? i need to fix this :S, there's anyway to get into the fastboot? with other computer, if that so what should be the processes clean of installing everything, SDK, drivers, etc.
I knew what was the first problem, the twrp file i flashed was corrupted. i checked it with md5 :S.
help!
OK download the drivers in my signature and extract them somewhere. When you turn the kindle off, open the device manager on your PC, as soon as you plug the device back in and see a jem device with a yellow triangle right click it and hit update drivers and choose the location of my drivers you extracted. Its hard to get the timing right because it will only appear for a few seconds. If you can't get the timing right then try kindle fire first aims driver installer. I believe it has one that will automatically put the drivers in windiow's cache so it will install them automatically. If that still fails then go download a Ubuntu 13.10 live CD and either boot it from a flash drive or CD, and install the fastboot command package from the Ubuntu software center. From their you can type the command and it would automatically work because Linux is awesome like that and doesn't tend to have driver issues like windows. xD
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK download the drivers in my signature and extract them somewhere. When you turn the kindle off, open the device manager on your PC, as soon as you plug the device back in and see a jem device with a yellow triangle right click it and hit update drivers and choose the location of my drivers you extracted. Its hard to get the timing right because it will only appear for a few seconds. If you can't get the timing right then try kindle fire first aims driver installer. I believe it has one that will automatically put the drivers in windiow's cache so it will install them automatically. If that still fails then go download a Ubuntu 13.10 live CD and either boot it from a flash drive or CD, and install the fastboot command package from the Ubuntu software center. From their you can type the command and it would automatically work because Linux is awesome like that and doesn't tend to have driver issues like windows. xD
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks, I'm going to use Ubuntu, windows will not work.
Once i get into the fastboot throught ubuntu, Do I have to come back to windows and use KF First Aide to restore stock os right?
or can I use ubuntu to do this? if that so, how? KF First Aide works on ubuntu?
Can't I just simple flash the system.img that is in KFHD_SRT_v2.1 folder? (throught ubuntu)
thanks a lot for the patience
I gonna leave these question to try no bother anymore. I'm asking because my KF First Aide yesterday won't pass after this lines..
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
{
"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"
}
it get stuck there...
and the KFHD_SRT_v2.1 didn't recognize the device even when i was in the fastboot already and my kindle was on the device manager installed as Kindle ----> Android ABD device (what i see is kinda wierd is that the first time i get working in the fastboot if i ask for devices it would should me some kinda of ID XXXXXXXXXXX but yesterday (and I'm sure is because the drivers and maybe something is not right installed even i read could be a conflict with Android SDK,) just show me the device product: Jem-PVT-Prod-04 not the ID.
This all the information i can give.
My kindle software/hardware was or is:
Kindle fire 8.9
System Version: 8.4.6_user_4620220
My OS is windows 7 64bits
I did install everything JAVA develoment, I did have android SDK already (because I flash a xperia sucefully) and it's on my C:\Program Files\Android SDK but i didn't install it, i just unzip it. here's a capture:
I'm using the fastboot that i used to get the kindle into the fastboot from the folder i used to flash twrp and root.
thanks for everything, sorry bother.
any advice will be great, have a good day.
kffa won't work in ubuntu since its a batch file, for some reason it never got converted into a bash script. You can just manually flash those images from ubuntu and it should work just fine, though i'm thinking there might not even be a need to, i mean flash the recovery image and it should work again theoretically, seems to me the idme mode just got stuck to recovery and never got reset because recovery is broken, but thats just my take on it, if that was the case you could change the idme from fastboot but thats kinda complicated because the numbers for idme on the first gen's were in the 4000's and the newer gen ones are single digits and i dont rember which digit is what option so i'd say try to flash recovery from srt and see what happens.
stunts513 said:
kffa won't work in ubuntu since its a batch file, for some reason it never got converted into a bash script. You can just manually flash those images from ubuntu and it should work just fine, though i'm thinking there might not even be a need to, i mean flash the recovery image and it should work again theoretically, seems to me the idme mode just got stuck to recovery and never got reset because recovery is broken, but thats just my take on it, if that was the case you could change the idme from fastboot but thats kinda complicated because the numbers for idme on the first gen's were in the 4000's and the newer gen ones are single digits and i dont rember which digit is what option so i'd say try to flash recovery from srt and see what happens.
Click to expand...
Click to collapse
great i'll try that, while i'm waiting for the ubuntu to download i tried to install the drivers and i know now if the work, i guess not, i turn off the kidle run the command to go to fastboot and this is what i get.
that command was off, you left off a word, its supposed to be "fastboot -i 0x1949 getvar product", just thought you might need it for future reference in ubuntu.
stunts513 said:
that command was off, you left off a word, its supposed to be "fastboot -i 0x1949 getvar product", just thought you might need it for future reference in ubuntu.
Click to expand...
Click to collapse
THANKS!!! i did fix my kindle fire.
But i still have a very last question...
once i get back to kindle with KFFA the OS system 8.1.2, I tried again to install the Cyangenmod. and get the stuck in the blue logo.
this time i made sure everything was checked, and everything was fine with MD5, all the files are from Hashcode. here's my question:
The kindle fire is running 8.1.2 and this file is kfhd8-freedom-boot-8.4.6.img that means i need to find my version? or that will not matter at all?
I get back to stock amazon os, waiting to see if i try again.
THANKS A LOT ONCE AGAIN..
For future references, i did fix my kindle fire by uninstalling every driver once the kindle fire show up for 3 seconds, Use ccleaner, reboot the computer, and the in those 3 seconds i installed the stunts513 drivers, then i go back to stock with KFFA.
RE-EDIT: THANKS, i'm running now cm10.2. Thanks very much, this is solved, can be closet.