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
Related
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.
[Q] Help: Failed Kindle Fire 6.3 rooting/ fastboot problems (Linux), and ROM choice
Hello, everyone!
I have a Kindle Fire running OS 6.3, and I've decided to root it so I can use custom ROMs, and have access to the Google Market from the Caribbean.
Despite lots of reading and several attempts, I haven't been successful in my attempts to root my Kindle Fire from my Linux laptop. (Ubuntu 12.04.)
I've set up and rechecked adb and fastboot as outlined on this page:
http://androidforums.com/i7500-all-things-root/32481-howto-linux-adb-fastboot-mass-storage.html
And I've been trying the rooting method outlined in this thread:
http://forum.xda-developers.com/showthread.php?t=1568340
ADB successfully sees my device, as confirmed when I type
./adb devices
into my terminal with the KF attached to my USB cable.
The first set of adb commands seems to work fine:
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
...but the first fastboot command doesn't seem to do anything- I get "waiting for device" and nothing more.
I should note that "fastboot devices" command doesn't result in any output from the terminal.
What should I do next?
Also, what recommendations for a custom ROM can you folks suggest?
I am an avid reader and a gamer. I may watch some YouTube videos or sitcom reruns, but hi-def video isn't important to me at all; neither the Fire's storage nor my bandwidth are well suited to HD.
I'm currently looking at MoDaCo and MIUI.
thanks in advance,
adrian.
Any ideas, anyone?
Try turning your device off then restarting after you see the <waiting for device>
If that doesn't work you can still use adb to root your device before installing TWRP and FireFireFire. (just skip the fastboot steps)
After you are rooted you can use "Gscripts" to install FireFireFire and custom recovery
Sent from my Amazon Kindle Fire using xda premium
Just curious, what are the exact fastboot commands you are using; exactly how you typed them.
Sent from my Amazon Kindle Fire using xda premium
If you followed that guide to set up your udev rules, it may be insufficient to get it working with adb. Try this Kindle Fire specific guide...
http://forum.xda-developers.com/showthread.php?t=1475740
As for fastboot, you'll probably need elevated privileges to get that working. Switch to root or use sudo when executing fastboot commands.
Thanks for the replies!
I'm trying the suggestions now, detailed responses to follow.
Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.
guttaperk said:
Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.
Click to expand...
Click to collapse
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).
kinfauns said:
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).
Click to expand...
Click to collapse
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?
guttaperk said:
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?
Click to expand...
Click to collapse
That mount command should work in TWRP 2.0.0. I'm guessing that you are trying this while booted into the system or another version of TWRP. This one should work better in a wider range of situations....
Code:
adb shell mount -o remount,rw /system
The same problem
Hi, I have the same problem.
I stuck in the command
fastboot -i 0x1949 flash bootloader fire.zip
ok
fastboot -i 0x1949 flash recovery twrp.img
ok
fastboot reboot
My kindle fire reboot but i don't see any thing, the screen has not thing, not yellow triangle.
I hold on the power button 20s to restart. Then the power botton did not come red. My kindle fire not power on.
The adb command did not work.
The fastboot say: wait for devices
Please help me!
trungblc said:
Hi, I have the same problem.
fastboot -i 0x1949 flash bootloader fire.zip
Click to expand...
Click to collapse
This is where you screwed up. You need to read about what you are installing BEFORE you install it. The above named file is in .zip format. The newest version of FireFireFire was put in a .zip format for flashing in recovery.
If you use the "fastboot flash bootloader" command, you can only flash files in a .bin format. You now have a broken bootloader resulting in one of the hardest of bricks.
Research Firekit LiveUSB because that's your only hope at this point.
And let this be a lesson to anyone who wants to make ANY modification to their bootloader...Pay attention!
Thanks you so much
Thanks you so much. I will try and post the result soon.
I've owned you a beer now
Sorry to hear about your trouble trungblc at least you have two of the very best here watching your thread kinfauns and soupmagnet if anyone can get you out of a brick like this it would be them for sure good luck
Update status
I had used Firekit LiveUSB, and short the CPU method.
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
...
OKAY [ 0.073s]
finished. total time: 0.073s
Installing x-loader...
sending 'xloader' (128 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 55.162s
Flash FFF...
sending 'bootloader' (211 KB)...
FAILED (status read failed (No such device))
finished. total time: 211.638s
Flash TWRP...
< waiting for device >
After that, kindle boot in TWRP, but when i reboot, it still not power on.
Have you tried holding the power button for 30 seconds and trying again?
Oh.
soupmagnet said:
Have you tried holding the power button for 30 seconds and trying again?
Click to expand...
Click to collapse
Oh holding for 30s? I had tried with 20s. But kindle fire still not power on.
I will try again now
Pls help me more.
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
...
OKAY [ 0.072s]
finished. total time: 0.072s
Installing x-loader...
sending 'xloader' (128 KB)...
OKAY [ 0.036s]
writing 'xloader'...
OKAY [ 0.279s]
finished. total time: 0.314s
Flash FFF...
sending 'bootloader' (211 KB)...
OKAY [ 0.057s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.099s
Flash TWRP...
sending 'recovery' (5260 KB)...
OKAY [ 1.319s]
writing 'recovery'...
OKAY [ 4.118s]
finished. total time: 5.437s
Resetting bootmode to standard boot...
...
OKAY [ 0.079s]
finished. total time: 0.079s
Loading TWRP...
downloading 'boot.img'...
OKAY [ 1.319s]
booting...
OKAY [ 0.004s]
finished. total time: 1.323s
In the TWRP, I mount the SDCARD and copy the amazon update.zip (rename from update-6.2.1.bin) to sdcard. The install - Flash - Reboot.
The Kindle Fire still not power on. I really don't know why.
It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again
Thepooch said:
It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again
Click to expand...
Click to collapse
I had been tried to do that before. I just pressed reboot button when it gets into TWRP many times but nothing happened. After that, I had tried to flash room again but still the same.
I don't know why.
Pardon me if this has been covered in the past, but I'm having a difficult time finding the info that I'm looking for.
I have a Kindle Fire that I had put CWM on. Yesterday, I installed TWRP and the Reloaded ICS rom.
Everything went fine and I'm very happy with the ICS installation.
However, if I boot back into recovery, then CWM loads up. I was expecting TWRP to overwrite CWM, but apparently that's not how it works.
I'm on a Mac and these are the steps I took to flash TWRP:
Connect your KF to you computer and open a terminal.
Navigate to your platform-tools folder
cd Path to platform-tools
Once here check to see your KF is recognized by ADB
sudo ADB devices
Click to expand...
Click to collapse
*Note you may have to use the command Sudo ./adb devices, it really depends on how you have your SDK setup.
If you see a series of numbers it verifies your KF is being seen by ADB. Next you'll type
sudo ADB shell or sudo ./adb shell
Click to expand...
Click to collapse
Then ask for root permission
SU
Click to expand...
Click to collapse
Next you'll need to set your bootmode to fastboot
idme bootmode 4002
Click to expand...
Click to collapse
It will tell you that <idme> write 4002 to offset 0x1000. Now you'll need to exit the shell
Exit
Click to expand...
Click to collapse
Exit
Click to expand...
Click to collapse
Once you're back in your platform-tools folder restart adb
Sudo adb reboot or sudo ./adb reboot
Click to expand...
Click to collapse
ADB will restart then you can issue the fastboot command
sudo fastboot -i 0x1949 boot twrp-blaze-2.0.RC0.img or sudo ./fastboot -i 0x1949 boot twrp-blaze-2.0.RC0.img
Click to expand...
Click to collapse
If memory serves me correctly, the device will reboot to TWRP and saying its installed. It will reboot itself. Once rebooted you'll be shown a yellow triangle with a fire on it. Don't panic as its a modified bootloader that allows you to access your recovery. It boots here because your device is still set to boot into the bootloader. To fix this type
sudo fastboot oem idme bootmode 4000 or sudo ./fastboot oem idme bootmode 4000
Click to expand...
Click to collapse
Then simply give fastboot the command to reboot
sudo fastboot reboot or sudo ./fastboot reboot
Click to expand...
Click to collapse
Your device will reboot to the bootloader again, except this time it only stays like that for a short period in order for you to access your recovery if need be. To access TWRP simply hold your power button down for around 2 seconds. Your power button will change to an orange color, release the button and TWRP will show up. If you do nothing at the bootloader your rom of choice will continue to boot.
Click to expand...
Click to collapse
Does anyone have any advice? Thoughts?
I'm very new to Android. . .
Best,
Chris
czucker said:
Pardon me if this has been covered in the past, but I'm having a difficult time finding the info that I'm looking for.
I have a Kindle Fire that I had put CWM on. Yesterday, I installed TWRP and the Reloaded ICS rom.
Everything went fine and I'm very happy with the ICS installation.
However, if I boot back into recovery, then CWM loads up. I was expecting TWRP to overwrite CWM, but apparently that's not how it works.
I'm on a Mac and these are the steps I took to flash TWRP:
Does anyone have any advice? Thoughts?
I'm very new to Android. . .
Best,
Chris
Click to expand...
Click to collapse
If you are trying to install TWRP version 2.1.x then those steps will not get TWRP installed onto your recovery partition. "fastboot boot" just loads the image into memory and boots from there. You'll need to "fastboot flash" the image to actually get it on to the recovery partition.
Just to clarify a possible source of confusion... version 2.0.0 was distributed as a boot image wrapped around the recovery image. So, the instructions were to "fastboot boot" the boot image and then it would run an internal script that would flash the recovery image contained within the boot image. Now, version 2.1.x is just a recovery image, so you'll need to flash it manually.
Code:
fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img
Thank you.
That worked perfectly.
My kindle fire is bricked. I'm not sure it can be undone, as fastboot can't seem to change the bootmode.
Where I'm at (short version):
Mac os x 10.6.8
Kindle stuck on the amazon stock "Kindle fire" logo.
Kindle connected with factory cable.
Log:
> fastboot -i 0x1949 getvar product
product: kindle
finished. total time: 0.000s
> fastboot -i 0x1949 oem idme bootmode 4000
...
^C
How I go here:
I tried the KFU on a Windows VM running on Mac osx 10.6.8. Yes, that was dumb.
I went for the quick and dirty solution, it did not end well.
I've read the kindle beginners guide. Excellant resource. Switched to the Mac terminal interface.
My Knowledge:
I'm a knowledgeable unix user, android newbie. Meaning I know just enough to get myself in trouble.
Any suggestions would be appreciated. About the only other thing I can think to try is a linux interface instead of MAC.
Thanks,
Ann
The command you posted was successful. Did you reboot the device?
soupmagnet said:
The command you posted was successful. Did you reboot the device?
Click to expand...
Click to collapse
Yes I tried issuing the reboot command to the same result. Neither command returns to the command prompt, a ^C is required.
(apologies if this post appears twice.)
adavis749 said:
Yes I tried issuing the reboot command to the same result. Neither command returns to the command prompt, a ^C is required.
(apologies if this post appears twice.)
Click to expand...
Click to collapse
i think u dont have a recovery software and a rom flashed on ur kindle fire..first flash twrp.img(u can have it downloaded for u by KFU) from terminal..dont forget to open terminal in the location of twrp.img..then
fastboot flash recovery twrp.img
fastboot oem idme bootmode 5001
fastboot reboot
this should install twrp on ur KF
then mount it as usb mass storage through twrp and format it on ur mac or pc or whatever..sdcard partition needs to be formatted
then u can transfer .zip(ROM) file to it and flash it from twrp
after all this again revert bootmode to 4000 and u shud have ur kf running ur rom..
feel free to thank helpers!!!
prahladvarda said:
i think u dont have a recovery software and a rom flashed on ur kindle fire..first flash twrp.img(u can have it downloaded for u by KFU) from terminal..dont forget to open terminal in the location of twrp.img..then
fastboot flash recovery twrp.img
fastboot oem idme bootmode 5001
fastboot reboot
this should install twrp on ur KF
then mount it as usb mass storage through twrp and format it on ur mac or pc or whatever..sdcard partition needs to be formatted
then u can transfer .zip(ROM) file to it and flash it from twrp
after all this again revert bootmode to 4000 and u shud have ur kf running ur rom..
feel free to thank helpers!!!
Click to expand...
Click to collapse
That shouldn't matter. Even without recovery or a ROM installed, the device will still boot to a blank screen.
Sometimes after changing bootmodes in fastboot, the reboot command doesn't work. Just hold the power button until it shuts off and start it again.
soupmagnet said:
That shouldn't matter. Even without recovery or a ROM installed, the device will still boot to a blank screen.
Sometimes after changing bootmodes in fastboot, the reboot command doesn't work. Just hold the power button until it shuts off and start it again.
Click to expand...
Click to collapse
I have tried that as well.
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.