okay, this is to try to simplify the install for most windows users...
for starters get over to the teamwin website and download the official rc0 which comes with firefirefire bootloader so you can easily get into recovery with our 1 power button.
after youve downloaded the recovery file, put this file in the directory that your adb and fastboot is in, connect your device and open a cmd window
cd to the directory adb and fastboot is in, for me i typed
cd c:\sdk_tools (enter)
c:\sdk_tools becomes the directory, so now
adb shell (enter)
su (enter)
idme bootmode 4002 (enter)
so now your bootmode is set. now type in:
exit (enter)
exit (enter)
adb reboot (enter)
it should reboot to the splash screen of kindle fire in fastboot mode, now type in
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img (enter)
it should install, show team wins image, then reboot to the yellow triangle of firefirefire...
this is okay. from here, on windows, my computer did NOT read the device anymore and it was stuck in fastboot and wouldn't take commands. this issue is related to the drivers for some reason... what i did was reboot my pc, reconnected my device and it came up as a unknown device. this is okay!
go to devices and right click the one with an xclimation mark and click update drivers. choose manually and then choose out of available drivers. you need to select android phone or something android related depending on what drivers you had installed previously. i chose my asus android device since thats what i had when i first got adb working. after u choose android device choose adb generic and it should install fine.
after this get back in ur cmd prompt, cd to the proper directory and type this in
fastboot devices (enter)
u should get a listed device.
from here you can then change bootmode to properly reboot ur device
fastboot oem idme bootmode 4000 (enter)
fastboot reboot (enter)...
should be done! enjoy!
After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.
krelvinaz said:
After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.
Click to expand...
Click to collapse
when using apps to boot to recovery, can u get out of recovery without issue? someone said it gets stuck in the wrong bootmode?
Sent from my HTC Glacier using xda premium
I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).
krelvinaz said:
I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).
Click to expand...
Click to collapse
Yep, if you do everything right and have FFF and TWRP installed correctly, you should be able to flip between ROMS without too much trouble, and without have to use fastboot again.
Hmm...while attempting to reinstall the drivers for the Fire, I'm at a road block.
I see the kindle in device manager, and am informed that it's not installed correctly, but while manually choosing the drivers I'm greeted with the following (attached).
This is after choosing Android Phone from the available drivers.
Any ideas, guys?
reboot ur device and reconnect to ur PC.
Sent from my HTC Glacier using xda premium
Bricked?
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help
ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium
leglerreddin said:
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help
Click to expand...
Click to collapse
when the device is in fastboot it is unrecognizable with adb, just enter the fastboot commands and you'll be fine.
smirkis said:
ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I wish that was the case, i have tried a million different fastboot and adb commands, ive rebooted, used another os, the drivers are installed as an android composite adb interfaced, its still not registering as an adb or fastboot device.
EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers
CrackMonkey91 said:
EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers
Click to expand...
Click to collapse
I still had issues installing drivers after it booted to the yellow fire triangle (on Win7 x64 - even after adding the other device id to both x86 and x64 sections of the inf and ini of the drivers). Rebooting my computer with the Kindle plugged in caused the Kindle to reboot normally after which I used a terminal to set the boot mode to 4000:
Steps I took after doing step 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' (enter):
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
- Open the terminal app. (I used Terminal Emulator)
- Type 'su', press enter. (Superuser will pop-up - select allow)
- Type 'idme bootmode 4000', press enter.
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.
uunnzz said:
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.
Click to expand...
Click to collapse
this my friend, is interesting.
Related
I have just bought Kindle. So i try to root and install TWRP recovery for my Kindle. After installing TWRP, because don't look Super User icon in Kindle; I took hard-reset my device in Settings. And Now My Kindle boot Logo Kinder Fire stuck on here.
What problem ???? Please help me....... i don't know i had just done nothing. Thanks guys !
I try to text in command dos: "add shell" but it show may Laptop Screen:
- exec '/system/bin/sh' failed: No such file or directory (2) -
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
I'm having this same problem. It's apparently stuck in fastboot. I can't even figure out how to type in adb commands or fastboot commands (meaning I could before and now when I tried it says command not found, but I didn't change anything. It won't recognize my device and when I try installing the android-winusb.inf it says it won't let me. I don't know what else to do. Any help would be appreciated. My Kindle is listed as unspecified device.
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
g1no23 said:
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But Boot Status show: Unknow, so when i type this text comandos show: waiting device
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
lovejoy777 said:
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
thanks guy much. But i tried all, i used KFU to try installing Recovery ( CMW, or TWRP), try to plug in USB Kinlde, press power button, etc. But It'S seem not working, all show: " exec- system/bin/sh failed ; not such file orr folder "
i also use tool KF Unbrick on XDA, but it's too. Reply show: " -exec- "system/bin/sh"...
Can U know that what problem in "system/bin/sh" of Kindle Fire ???????
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
works perfectly for me too! awesome!
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
thanks but my kindle don't have TWPR recovery after i've just flashing office room 6.2.1 from Amazon. Now it stuck in my logo Kindle
tunglx1988 said:
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Serinety said:
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
thanks for repl. But My Kindle Logo is Stuck in here. open KFU then show : Boolloader: UnKnow. So i don't know it bootmod ??? ( recovery, Normal, or fastboot).
b63 said:
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
he is absolutely right, this happened to me and nothing would work until I got a factory cable
This is a typical problem with KFU.
You need to go to your device manager and uninstall both the adb and android drivers then reinstall them manually. Sometimes it helps to restart your computer and Kindle afterwards. Make sure your device manager says both "Android Phone" and "Android ADB Interface" NOT "Other Device" and "Kindle".
When you are stuck at the boot screen it means you are in fastboot mode. In fastboot mode your device will only recognize fastboot commands. If your device doesn't recognize fastboot commands (KFU uses fastboot commands to change boot modes), 99 times out of 100, it's a driver issue.
A factory programming cable, while nice to have, is not usually necessary. A factory programming cable does two things. It provides power directly to the device instead of the battery AND forces the device into fastboot mode (stuck at boot logo). Since most of you with this problem are ALREADY in fastboot mode, a factory cable would be pointless.
Make sure you are 100% certain that you have the correct drivers installed and configured properly and then use the command prompt to change your bootmode to 4000.
In command prompt, navigate to the folder that contains fastboot.exe and enter the following commands...
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Sent from my Amazon Kindle Fire using xda premium
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
soupmagnet said:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Click to expand...
Click to collapse
jingcleovil said:
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
Click to expand...
Click to collapse
i have the same problem as you it fills good to not be the only one
Hello. After a few attempts I was finally able to root my kindle fire using Breakdroid found here: http://forum.xda-developers.com/showthread.php?t=1511757 .(I only have access to an OSX, no windows). I have a dell latitude running snow leopard. (hackintosh)
I can get to the black and red screen.
I downloaded the energy ics apk and tried to install the zip through the CWM-base Recovery v5.0.2.7 FULL (by DooMLorD) and it just loops through the fire screen with the triangle logo. Occasionally you can see the ICS startup screen, but very briefly(like 1 sec) but it goes back to looping through the reset.
I am not new to rooting android devices as I have rooted my phones in the past with no problems.
1. What am I doing wrong?
2. I can try install TWRP but how?(step by step on overwriting the CWM-base Recovery in OSX please, i have adb and tried but it does not see twrp in my file location.
3. is there an updated script for osx that auto installs TWRP?
If someone has time, please post a video please as there are none on installing using OSX on a fire using 6.3 on youtube or anywhere else on the web.
I cant add a new post since im new so Im editing this one:
Thanks! After waiting 15 min for the opening ICS screen, I finally rebooted and had the same problem..
Now the big question... how do you install TWRP using OSX?
tell you the steps I have done with no success...
I went to http://www.teamw.in/project/twrp2 and chose kindle fire
downloaded the .img and placed it in my platforms-tools(and yes, I downloaded the ADB package and added platform-tools)
first did adb devices and got:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
436E000600000001 recovery
then followed the websites direction and started adb shell by typing adb shell and got:
:~ drive$ adb shell
~ #
then followed the websites direction and entered su and got:
~ # su
/sbin/sh: su: not found
~ #
why was su not found?
Think I might gotten closer to a solution to my own problem.. I re-rooted using Breakdroid(auto root method) and now I am getting the full ICS animation screen ... Im going to leave it alone for a bit and see if it actually loads ICS on my fire.. will let you know any findings...
matchnbpm said:
Think I might gotten closer to a solution to my own problem.. I re-rooted using Breakdroid(auto root method) and now I am getting the full ICS animation screen ... Im going to leave it alone for a bit and see if it actually loads ICS on my fire.. will let you know any findings...
Click to expand...
Click to collapse
TWRP is required to run the new ICS roms. CWM usually will not work.
ok.. got su to finally work after reloading kindle fire's image that I did a backup of and let it be on USB mode
got bootmode to go in from the site
tried to fastbook and i get:
# fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
fastboot: not found
.. Edit.. found out that fastboot requires that you exit out of ADB..
now fastboot stuck on 'waiting for device'
matchnbpm said:
ok.. got su to finally work
got bootmode to go in from the site
tried to fastbook and i get:
# fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
fastboot: not found
Click to expand...
Click to collapse
You don't need "su" to enter fastboot commands.
While in recovery, enter:
adb shell idme bootmode 4002
adb reboot
That will restart your kindle in fastboot mode. Then you can enter:
fastboot flash recovery /path/to/twrp.img
Then...
fastboot oem idme bootmode 4000
...and reboot
EDIT:
6.3.1
Wow.. what a pain! Finally got TWRP to load! Here are the instructions for OSX using http://forum.xda-developers.com/showthread.php?t=1511757 (since no one seems to have it)
download breakdroid
start breakdroid (not kindlewater)
press 5 for kindle
press ok
press 1 for autoroot
now this is where you either get it or not.. my first time I got hung at waiting for device, so i simply unplugged it and replugged it and continued the autoroot. The second time after i unrooted my kindle fire and rerooted I did an exit and re rooted and it went all the way through... so your choice...
after you should be able to load kindle fires normal os after you see a triangle with a fire in it
now download TWRP
head over to: http://www.teamw.in/project/twrp2 choose kindle fire from their
'please select device'
download their .img
follow the instruction here to add adb to your MAC: http://forum.xda-developers.com/showthread.php?p=9842005
with the instructions, make sure you do it step by step including the "Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it."
if you did the instructions correctly you made a quick way to start ADB.
you can check if it works by starting a terminal(under applications/utilities(i made a quickstart and pinned it to my bar) and type ADB devices(with caps)
you should see your device there, if not, retrace your steps
move the TWRP .img file to your platform-tools folder
now start your kindle fire to normal mode and plug in your usb.. leave it on USB mode, do not exit
start a terminal and type ADB devices, your kindle fire should NOT be in recovery, should show 'device'
follow the TeamWin directions and type adb shell
type su
type idme bootmode 4002
type exit
quit terminal
restart terminal
type fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
your kindle fire will look like it is locked up after a few min, simply power off your kindle fire after installation of TWRP by pressing the power button until it turns off..
power back on and press and hold until it turns orange, release..
Welcome to TWRP!
First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!
wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?
wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.
wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.
Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app
This is my gf's kindle fire and she wanted it rooted to have the google play store. This is completely untouched Kindle and on windows 7 pc. So I downloaded the KFU latest release 0.9.6 and proceeded w/ option 2 to install permanent root. Let it sit for about an hour with the please wait and waiting for device messages at the bottom of the screen. I wasnt sure how much longer this would be so i just let it sit. Couple minutes later my gf comes and let me know that she unplugged it accidentally while vacuuming. Im now stuck on the TWRP screen and will not reboot at all. If it try to reboot i get a message saying " E: System in not installed - preventing reboot! " which makes me think that the OS got wiped somehow. All I can do is let it run out of battery. Now in the KFU abd status: Offline and boot status: Unknown. Although that Windows will recognize the device as its showing up in device manager under Adroid Phone: Android ADB interface. What can I do?
not showing up.
Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.
soupmagnet said:
Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.
Click to expand...
Click to collapse
Mount function not working either. I hit the button and never shows up on my comp as a storage device.
Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).
soupmagnet said:
Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).
Click to expand...
Click to collapse
Could I just remove and reinstall the driver? Weird thing is that its still showing up on the device manager Adroid ADB interface.
In a perfect world, yes, that would work every single time.
soupmagnet said:
In a perfect world, yes, that would work every single time.
Click to expand...
Click to collapse
Well i managed to get the driver working and got to flash the latest update from amazon on and renamed it update.zip to get it to flash. Now it seems like its in a bootloop just showing kindle fire in the orange letters. Connecting it to KFU it shows ADB status: online , but still showing bootstatus as unknown.
You need to fix your drivers again.
Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.
neemo6 said:
Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668159
kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
Thanks kinfauns great info!
Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface
neemo6 said:
Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface
Click to expand...
Click to collapse
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.
soupmagnet said:
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.
Click to expand...
Click to collapse
Awesome thanks for the help Soupmangnet!! I got it in twrp recovery now. I would like to just have it back to stock at this point and have the latest update downloaded from amazon on the sd card. Im just worried that this will put me back into the same problem as before. Do need to download or fix something else?
Make sure you change the file's extension to .zip as before, and above all else, wipe System and "Factory Reset". Everything should go well for you.
You sir are awesome! Everything works great! Now to get play store.
You could have simply just flashed modaco instead of going through all he hassle of flashing update.zip and wiping out fff and twrp...
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt
I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!
Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.