this is what I had to do on Linux Mint 12 but should work with most ubuntu based distros
1: download twrp
2: if you dont already have it then you need to download the linux fastboot binary, extract the .zip and place the extracted file in your androidsdk/platform-tools directory
2: place the file you downloaded from TWRP into your androidsdk/platform-tools directory
3: connect your fire to your computer and disable mass storage mode
4: open a terminal and cd to your androidsdk/platform-tools directory and enter the following commands pressing enter after each line
Code:
./adb shell
su
idme bootmode 4002
then back out of the adb shell by
Code:
exit
exit
then
Code:
./adb reboot
after it reboots to the "Kindle Fire" boot screen its time to flash the recovery
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
once flashed and it installs and boots to the "firefirefire" screen (screen with the yellow sign and text that says "press power for recovery" you have to change the boot mode back out of fastboot
Code:
sudo ./fastboot oem idme bootmode 4000
sudo ./fastboot reboot
it should reboot to the "firefirefire" screen, to enter recovery press and hold the power button until it turns from green to orange then let go. You should boot into TWRP and be able to make your first backup.
from now on if you dont want to go into recovery then just let it sit and it will boot normally
Thanks to all the Teamwin members, agrabren for the port, pyrostic for testing, pokey9000 for the "FireFireFire" bootloader, and I am sure there are more but I dont know who you are so thank you.
if you can donate to these guys please do becuase without them we would just have an e-reader.
I am not responsable for any damage that YOU may cause buy following these directions.
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
issue the command with sudo
Nevermind, wasn't using ./ when I was issuing commands. As usual, need to pay better attention.
Thanks OP. Sweet.
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
abiezer said:
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
Click to expand...
Click to collapse
adb wont recogonize it after you change the boot mode thats where you issue the fastboot commands
smirkis said:
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
Click to expand...
Click to collapse
Download this file and place it in the folder your fastboot is located in: http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
do the following
open a command window where fastboot is located:
Step 1:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. if it still says "waiting for device" close the window and then then open a command window where fastboot is located and do step 2.
Step 2:
Code:
fastboot -i 0x18d1 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. If it is still not doing anything, this is where my knowledge is no good anymore, and you should consult someone else.
TWRP should be showing on your screen. Close your old fastboot window and open a new command window where ADB is located. Proceed to Step 3.
Step 3:
Code:
adb shell
idme bootmode 4000
reboot
your device should reboot, and if you had problems with Step 3 try the following from your ADB command window
Code:
su
adb kill-server
adb start-server
adb devices
your device should be listed. If so try Step 3 again.
hope this helps or at least puts you in the right direction.
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
craftyguy said:
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
sl0ttedpig said:
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
Click to expand...
Click to collapse
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
EDIT: Ok, had to pass "-i 0x1949" to fastboot. Got the device back, going to try it all over again
craftyguy said:
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
Click to expand...
Click to collapse
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
smirkis said:
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
try rebooting manually n see if u get fastbot.
Sent from my HTC Glacier using xda premium
craftyguy said:
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
Click to expand...
Click to collapse
woot for fedora! anyway, i set things up via /etc/udev/rules.d/51-android.rules and at first I had this...
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
and everything was cool. but after flashing twrp, i noticed there was firefirefire 1.0 out where previously i had flashed .9 so i thought id update I went to update and after putting the device in fastboot mode, it rebooted to the bootloader where fastboot wasnt recognizing the device started digging around and found windows users having driver issues and thought to myself... we dont have drivers BUT we do have rules!! added this line to the udev rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and everything working as it should again
I was on CM 11. I wanted to restart fresh to I flashed
to KF 8.4.6 which worked fine. I then (this starts the
trouble) tried to reset device (remove personal data) from within kindle screens
1) rebooted to red screen
2) finally got into fastboot
3) tried this:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
4) it reboots and stays at yellow kindle fire logo
5) then I tried just this but same result:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
Any Ideas?? Please? I am not upset that I cant use it...I'm upset that I cant fix it!
Fixed it
Used SRT tool and finally realised also had to flash boot.img and recovery.img
Sent from my HTC One X using xda app-developers app
So I've been working on trying to flash CM on my Fire 2 (I'm fairly experienced with flashing). I managed to get 10.5.1 rooted with SuperSU installed, and then I followed the directions here (https://wiki.cyanogenmod.org/w/Install_CM_for_otter2) to install CM. I made sure to verify the MD5 checksums on the files, and executed the fastboot commands successfully (I don't have a factory cable, I used the ADB commands after gaining root to get into fastboot).
When I executed "fastboot -i 0x1949 oem recovery", it gave me the blue Kindle Fire boot screen, and booted normally into the OS. I loaded the CM/Gapps zips into the storage partition, and then did "adb reboot recovery". It rebooted, showed the orange stock Kindle Fire screen, then this grey triangle screen and proceeds no further. I tried rebooting multiple times, nothing. Device doesn't show up in my device manager, nothing in fastboot or ADB.
View attachment 3621153
So what can I do? I read that as long as something shows up, it's not irreversibly bricked....Or do I need that dang factory cable....
Thanks!
Turn off the kindle completely (hold the power button for about 10 seconds). Open up a command prompt, type fastboot -i 0x1949 getvar product, and plug in the kindle when you see <waiting for device>. If your device boots into fastboot, and you get a string like "otter2-xxx-xx", then you should reflash the files like told to in the CM guide. However, before you type the "fastboot -i 0x1949 oem recovery" command, issue fastboot -i 0x1949 erase system, fastboot -i 0x1949 erase cache, and fastboot -i 0x1949 erase userdata. After that, I think you shouldn't have any issue flashing.
Hey guys,
My KFHD8.9 had stuck in fastboot (after a RED SCREEN showed up for a second) for quite a few days. And none version of KFHD_SRTv1.2.0-1.3.5 worked to make it back - 1.2.0 not even work to be exact.
I followed several xda posts like https://forum.xda-developers.com/showthread.php?t=2495741
to solve this, but seems not working.
I'll appreciate if anyone can help out.
Thanks
Assume that you have fastboot driver installed, KFHD_SRT_v2.1.zip, boot.img and recovery.img for 8.1.4.
You can follow these steps to downgrade to 8.1.4;
1. Power off your KFHD.
2. run [fastboot -i 0x1949 getvar product] and connect KFHD, this will put your KFHD in fastboot mode
3. run [SR Tool.bat] within KFHD_SRT_v2.1 folder. and choose option 2 or 3. (I prefer option 2)
4. After flashing 8.1.4 to your KFHD, don't reboot, you have to downgrade your bootloader and recovery as well.
5. Run [fastboot -i 0x1949 flash boot boot.img] to inject 8.1.4 bootloader
6. And run [fastboot -i 0x1949 flash recovery recovery.img] to inject recovery
7. Finally run fastboot -i 0x1949 reboot
Wait for a while and you will have KFHD 8.1.4 with root enabled, thanks to onemeila.
KFHD System.img Recovery Tool by onemeila
After this you can update to the latest 8.5.1 and gain root via iroot.
Now I'm happy with Nougat (unofficial CM14.1 by transi1)
P.S. Sorry, I can't remember where I fetched boot.img and recovery.img of 8.1.4, you have to find it yourself.
This works.
Thanks ong14. Your method saved my Kindle from its soft brick.
Haven't used my kindle for 6 months. Noticed today it just sits at the blue & white kindle fire logo.
If I hold the volume button down the Teamwin logo displays sitting there, nothing happens.
Hardware devices shows "Kindle" @ the Teamwin logo. I believe this is ADB.
If I just plug it in it shows Jem-PVT-Prod-04 with an exclamation.
edit: After about 5 hours I've determined the windows driver support is just ****. Using FWUL I can put the device into fastboot and send images. I sent a working copy of TWRP and now I cant enter TWRP at all, it just sits at the 2nd bootloader, ie. white and blue logo.
Code:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 reboot
even erased cache and userdata, nothing. sits at the blue white logo and cant get into TWRP when pressing the down button.
edit: about 10 hours I finally figured out how to get it stuck in fastboot mode using linux and forced it to install the driver in windows. Even tried SRT 2.1, it flashes everything but upon reboot it shows a red swipe and automatically stays in fastboot mode.
I suspect something may be wrong with the device because issuing a fastboot oem idme bootmode 5001 after flashing twrp and freedom just locks up the device and fastboot will hang only displaying "..." unless I pull out the cable.
I'm over it.
Have you tried "oem idme bootmode 1" instead of 5001 ?