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
Have been trying to re-install everything for about 3 hours.
I keep getting code 10.
any help?
if your in fastboot adb won't work.
you need to issue the fastboot commands.
cd into platform tools and issue the following commands pressing enter after each line.
fastboot devices
you should get your kindle number showup.
then
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
this should reboot into normal mode
Sent from my Amazon Kindle Fire using xda premium
in cmd c/:kindle
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.2.0.img
fastboot -i 0x1949 oem idme boot mode 4000
fastboot -i 0x1949 reboot
not worked, fastboot is wrong commander..help me! ㅜㅜ
also Fastboot oem unlock is not working to....
icolt said:
in cmd c/:kindle
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.2.0.img
fastboot -i 0x1949 oem idme boot mode 4000
fastboot -i 0x1949 reboot
not worked, fastboot is wrong commander..help me! ㅜㅜ
also Fastboot oem unlock is not working to....
Click to expand...
Click to collapse
You have to have tools (android tools) linked cmd (with "cd" command).
You need to do these steps:
1. Go here http://forum.xda-developers.com/showthread.php?t=1399889 and download Version 0.9.6 (http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.6.zip)
2. Extract it on desktop.
3. Run install_drivers.bat and install the drivers (KINDLE MUST BE NOT CONNECTED TO THE PC)
4. copy "tools" folder into your C:\ disk
5. Copy openrecovery-twrp-blaze-2.2.0.img into "tools" folder (In C: Drive)
6. open cmd as administrator
6. Run these commands: cd C:\tools
fastboot -i 0x1949 flash recovery C:\tools\openrecovery-twrp-blaze-2.2.0.img
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
7. Enjoy
Also: Do you have FireFireFire installed?
You need to do these steps:
1. Go here http://forum.xda-developers.com/showthread.php?t=1399889 and download Version 0.9.6 (http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.6.zip)
2. Extract it on desktop.
3. Run install_drivers.bat and install the drivers (KINDLE MUST BE NOT CONNECTED TO THE PC)
4. copy "tools" folder into your C:\ disk
5. Copy openrecovery-twrp-blaze-2.2.0.img into "tools" folder (In C: Drive)
6. open cmd as administrator
6. Run these commands: cd C:\tools
fastboot -i 0x1949 flash recovery C:\tools\openrecovery-twrp-blaze-2.2.0.img
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
7. Enjoy
Also: Do you have FireFireFire installed?[/QUOTE]
so wating for device in cmd stop.....fff is installed
icolt said:
You need to do these steps:
1. Go here http://forum.xda-developers.com/showthread.php?t=1399889 and download Version 0.9.6 (http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.6.zip)
2. Extract it on desktop.
3. Run install_drivers.bat and install the drivers (KINDLE MUST BE NOT CONNECTED TO THE PC)
4. copy "tools" folder into your C:\ disk
5. Copy openrecovery-twrp-blaze-2.2.0.img into "tools" folder (In C: Drive)
6. open cmd as administrator
6. Run these commands: cd C:\tools
fastboot -i 0x1949 flash recovery C:\tools\openrecovery-twrp-blaze-2.2.0.img
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
7. Enjoy
Also: Do you have FireFireFire installed?
Click to expand...
Click to collapse
so wating for device in cmd stop.....fff is installed[/QUOTE]
Before you run fastboot commands, power off kindle. After you run first command in cmd, it will show "waiting for device". After "waiting for device" will apear plug in with usb your already POWERED OFF kindle.
Josepho1997 said:
This should work:
If you have fff installed:
Copy the tools folder from KFU to your local disk.
Now power off your Kindle Fire all the way.
Then open command prompt and type:
cd c:\tools
fastboot
fastboot getvar store
(now you should see <waiting for device>)
Now power on your Kindle. Now in cmd it should say finished and the time it took. do mot anser..
Now copy TWRP to your local disk
Then type:
fastboot flash recovery c:\openrecovery-twrp-blaze-2.2.0.img
fastboot oem idme bootmode 4000
fastboot reboot
Now as it boots up use your power button to boot into recovery and it should boot into TWRP.
Click to expand...
Click to collapse
just wating for devices...........
This should work:
If you have fff installed:
Copy the tools folder from KFU to your local disk.
Now power off your Kindle Fire all the way.(all doing)
Then open command prompt and type:
cd c:\tools
fastboot
fastboot getvar store
(now you should see <waiting for device>)
Now power on your Kindle. Now in cmd it should say finished and the time it took.(wating for device..... naver finishe)
Now copy TWRP to your local disk
Then type:
fastboot flash recovery c:\openrecovery-twrp-blaze-2.2.0.img(openrecovery-twrp-blaze certainly in to tool,)
fastboot oem idme bootmode 4000
fastboot reboot
Now as it boots up use your power button to boot into recovery and it should boot into TWRP.
naver ending wating for device~~~~~~~~~~~
cd c:\tools(recovery certainly into c
fastboot
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
(driver re-installing many times ,certainly driver install,well showing driver numbers)
don`t end ,naver ending~~~~~~~~~~wating for device
i wanna be korean keyboard,not needs markeet
You just said something that might be your problem because of how different korean characters are in your alphabet maybe just simply changing your computers language to english to complete the process will help
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