Related
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 have a problem. I rooted my Kindle fire (6.2.2) with BurritoRoot 2 and then tried to use Kindle fire Utility 0.9.2 to install TWRP and FireFireFire on my device. Everything was going fine until it told my kindle to go into fastboot and now its stuck in there. ive tried adding new vendor IDs, fastboot bootmode 4000, draining out the battery, uninstalling the drivers, rebooting my computer, everything. Can someone please help before I decide to use up my warranty?
Using Windows XP 32-bit
Install the kfu driver go into tools folder in kfu hold shift right click run command... this should boot adb then type
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Sent from my Amazon Kindle Fire using Tapatalk
The exact same thing happened to me on the first try. Different drivers are needed when using KFU than when just using ADB. Run the install drivers batch file provided with KFU and run the commands listed above. That should get it out of bootloop.
Sent from my Kindle Fire using Tapatalk
interceptor_1972 said:
Run the install drivers batch file provided with KFU
Click to expand...
Click to collapse
I tried that, but it failed, saying the drivers were unsigned :/
alternativeaura said:
I tried that, but it failed, saying the drivers were unsigned :/
Click to expand...
Click to collapse
Follow these steps to set driver verification levels:
1.Press [Windows]Break to display the System Properties dialog box.
2.Select the Hardware tab and click the Driver Signing button in the Drivers panel.
3.Select the Block-Never Install Unsigned Driver Software button. (Verify that the Make This Action The System Default check box is selected.)
4.Click OK twice.
Still didnt work :\
"Errors were encountered while installing the software for your devices.. See the Status column for more details."
Driver name Google, Inc (WinUSB) AndroidUsbDeviceClass (12/06/2010 4.0.0000.00000)
Status
Install failed (unsigned)
did you do it with install_drivers.bat or did you update it manually ?
have you put kfu to c:\ and renamed to "kfu" that it is c:\kfu ? - it don't like spaces in pathname
are you on an english xp ? - since the xml of the driver installer has to be edited
b63 said:
did you do it with install_drivers.bat or did you update it manually ?
have you put kfu to c:\ and renamed to "kfu" that it is c:\kfu ? - it don't like spaces in pathname
are you on an english xp ? - since the xml of the driver installer has to be edited
Click to expand...
Click to collapse
1. I tried both
2. it's c:\KindleFireUtility
3. yes im on english, but how do i edit the xml?
alternativeaura said:
1. I tried both
2. it's c:\KindleFireUtility
3. yes im on english, but how do i edit the xml?
Click to expand...
Click to collapse
if your on english the installer should be ok
what does it tell you in device manager ?
in fastboot mode it should be "android adb interface" under "android phone"
b63 said:
in fastboot mode it should be "android adb interface" under "android phone"
Click to expand...
Click to collapse
Thats what i have, but adb does not recognize it
alternativeaura said:
Thats what i have, but adb does not recognize it
Click to expand...
Click to collapse
very fine - if the kf is in fastboot it don't recognize adb commands
an other little trick is to issue the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and when it says <waiting for device> power down the kf by holding the pwr button for ~20sec - then unplug and replug - don't turn it on - it should do it by itself - at some point the command is recognized and finished - then power off and on again
here a little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible the commands:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
or
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
b63 said:
very fine - if the kf is in fastboot it don't recognize adb commands
an other little trick is to issue the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and when it says <waiting for device> power down the kf by holding the pwr button for ~20sec - then unplug and replug - don't turn it on - it should do it by itself - at some point the command is recognized and finished - then power off and on again
here a little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible the commands:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
or
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!!!!!!!!
I have been searching for DAYS over the Internet, and lets just say when it comes to kindle fires, you are my SAVIOR. thank you
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
b63 said:
very fine - if the kf is in fastboot it don't recognize adb commands
an other little trick is to issue the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and when it says <waiting for device> power down the kf by holding the pwr button for ~20sec - then unplug and replug - don't turn it on - it should do it by itself - at some point the command is recognized and finished - then power off and on again
here a little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible the commands:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
or
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
i had the same problem, this worked !
but after i did everything and restart system, it went straight to the TWRP menu not the kindle fire system.
how can i fix this?
adb shell idme bootmode 4000
adb reboot
KFU v0.9.1 fixed this for me thankgod
Nice! And my KF's good to go again! Thanks b63! One air high-five for you bro!
This forum helps a lot of people! Hahaha! Thanks and more power!
HELP!
Hey guys! Back again. So noob me here has a new problem.
I CAN'T GET OUT OF NORMAL BOOT MODE! (Plain "Kindle Fire" logo but with dim backlight.)
These are what I did but to no avail:
- I tried switching it to fastboot mode, but everytime I do it, it becomes unrecognized by the device manager.
- And when I switch it back to normal boot mode, it just gets stuck there. (I HAVE NOT INSTALLED TWRP OR FFF OR ANYTHING ELSE FOR THAT MATTER BECAUSE THESE RECOVERY TOOLS NEED THE KF TO BE IN FASTBOOT MODE TO BE INSTALLED, BUT AS I SAID EARLIER, MY DEVICE GETS STUCK ON FASTBOOT MODE AND GOES UNRECOGNIZED, THAT'S WHY I DON'T HAVE TWRP AND FFF.)
Here is probably the most important info I can give.
I HAVE INSTALLED "GO LAUNCHER EX" ON MY KF AND AFTER THAT, I REBOOTED MY KF AND IT ASKED IF IT WANTED TO BE STARTED WITH THE KINDLE FIRE LAUNCHER OR GO LAUNCHER EX, I CHOSE GO LAUNCHER AND THEN IT GOT STUCK, I REBOOTED BY PRESSING THE POWER BUTTON FOR 10 SECS., TURNED IT ON AGAIN AND IT JUST GETS STUCK AT THE PLAIN KINDLE FIRE LOGO.
- I have watched some videos and read some articles saying that Go Launcher Ex can be installed for the KF without the device needing to be rooted, so when I tried it, everything mentioned above happened.
I hope somebody here can help me! This KF was a gift from my aunt and I don't want to be on the receiving end of a harsh scolding if she finds out I busted her gift. Thanks in advance and cheers!
brickboi said:
Hey guys! Back again. So noob me here has a new problem.
I CAN'T GET OUT OF NORMAL BOOT MODE! (Plain "Kindle Fire" logo but with dim backlight.)
These are what I did but to no avail:
- I tried switching it to fastboot mode, but everytime I do it, it becomes unrecognized by the device manager.
- And when I switch it back to normal boot mode, it just gets stuck there. (I HAVE NOT INSTALLED TWRP OR FFF OR ANYTHING ELSE FOR THAT MATTER BECAUSE THESE RECOVERY TOOLS NEED THE KF TO BE IN FASTBOOT MODE TO BE INSTALLED, BUT AS I SAID EARLIER, MY DEVICE GETS STUCK ON FASTBOOT MODE AND GOES UNRECOGNIZED, THAT'S WHY I DON'T HAVE TWRP AND FFF.)
Here is probably the most important info I can give.
I HAVE INSTALLED "GO LAUNCHER EX" ON MY KF AND AFTER THAT, I REBOOTED MY KF AND IT ASKED IF IT WANTED TO BE STARTED WITH THE KINDLE FIRE LAUNCHER OR GO LAUNCHER EX, I CHOSE GO LAUNCHER AND THEN IT GOT STUCK, I REBOOTED BY PRESSING THE POWER BUTTON FOR 10 SECS., TURNED IT ON AGAIN AND IT JUST GETS STUCK AT THE PLAIN KINDLE FIRE LOGO.
- I have watched some videos and read some articles saying that Go Launcher Ex can be installed for the KF without the device needing to be rooted, so when I tried it, everything mentioned above happened.
I hope somebody here can help me! This KF was a gift from my aunt and I don't want to be on the receiving end of a harsh scolding if she finds out I busted her gift. Thanks in advance and cheers!
Click to expand...
Click to collapse
Your only chance at fixing the device is with fastboot by installing TWRP and performing a factory reset. Work on getting your drivers working.
brickboi said:
Hey guys! Back again. So noob me here has a new problem.
I CAN'T GET OUT OF NORMAL BOOT MODE! (Plain "Kindle Fire" logo but with dim backlight.)
These are what I did but to no avail:
- I tried switching it to fastboot mode, but everytime I do it, it becomes unrecognized by the device manager.
- And when I switch it back to normal boot mode, it just gets stuck there. (I HAVE NOT INSTALLED TWRP OR FFF OR ANYTHING ELSE FOR THAT MATTER BECAUSE THESE RECOVERY TOOLS NEED THE KF TO BE IN FASTBOOT MODE TO BE INSTALLED, BUT AS I SAID EARLIER, MY DEVICE GETS STUCK ON FASTBOOT MODE AND GOES UNRECOGNIZED, THAT'S WHY I DON'T HAVE TWRP AND FFF.)
Here is probably the most important info I can give.
I HAVE INSTALLED "GO LAUNCHER EX" ON MY KF AND AFTER THAT, I REBOOTED MY KF AND IT ASKED IF IT WANTED TO BE STARTED WITH THE KINDLE FIRE LAUNCHER OR GO LAUNCHER EX, I CHOSE GO LAUNCHER AND THEN IT GOT STUCK, I REBOOTED BY PRESSING THE POWER BUTTON FOR 10 SECS., TURNED IT ON AGAIN AND IT JUST GETS STUCK AT THE PLAIN KINDLE FIRE LOGO.
- I have watched some videos and read some articles saying that Go Launcher Ex can be installed for the KF without the device needing to be rooted, so when I tried it, everything mentioned above happened.
I hope somebody here can help me! This KF was a gift from my aunt and I don't want to be on the receiving end of a harsh scolding if she finds out I busted her gift. Thanks in advance and cheers!
Click to expand...
Click to collapse
did yuo figure it out eventually?
i cant get my fire (stuck on logo, unknown device in windows) to connect to the utility tool or adb.
been trying different solutions for hours now.
thanks.
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
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.