I'm pretty new at this and I'm having issues going into TWRP.
Whenever I try to install TWRP recovery using the KFU, It looks like it's going through the process, and I do end up seeing the teamwin logo popup and the device boots into the regular kindle interface (so it at least appears that TWRP was installed). The problem is whenever I try to go into recovery using the bootmode menu in KFU, the kindle will reboot, only it won't go into recovery and just goes back to the regular kindle interface. I'm not quite sure what I'm doing wrong. One thing I did notice from looking through tutorials, is that when you reboot the device it's suppose to go to a yellow triangle screen before going into TWRP. My kindle never does this. I don't ever see that yellow triangle screen and instead see the regular kindle fire logo before it loads the regular interface. One other thing is whenever i use the KFU, under "adb rooted:" it says no. I thought after I did the "Permanent Root with Superuser" that it was supposed to say yes. Anyways, any help would be much appreciated.
the yellow triangle is the bootloader (firefirefire) which you'r missing i think
i would take the newest KFU 0.9.2 (attention re-upped yesterday-redownload):
http://forum.xda-developers.com/showthread.php?t=1399889
reading the op (espacially the known tricks) is a good idea
i recommend to extract kfu to c:\ and rename "kindle fire utility" to "kfu" because it don't allways like the blanks in the path
if you are on windows7 you should run kfu and all other commands from an elevated command shell (as administator)
to install the correct drivers (espacially on win7/64bit) by running install_drivers.bat is also a good idea
now you are ready to use kfu and install twrp again
that's the easy way
if it don't work you can install fff (firefirefire - the yellow triangle) manually
ask again about this ...
Thanks for the reply - just got home and I'll try your suggestions.
I'm having the same problem as the OP here.
I originally rooted using BurritoRoot, which worked just fine.
When using KFU, option 5, it seems to run everything smoothly, the downloads are the correct size... But when it goes and starts rebooting at the "DON'T TOUCH ANYTHING! DON'T EVEN LOOK AT IT! OR ELSE!"* screen on KFU, my Kindle boots into the standard Kindle Boot Animation, then the TeamWin splash pops up for a moment.
It then reboots back to the regular Kindle Fire boot animation and KFU says "There we go. TWRP is installed. Ter-dah!"*
When I go to restart the Kindle, however, I never get the FireFireFire icon at all. Just straight into the normal KindleFire stuff.
I decided to take a look at my device manager while my Fire is plugged in. It's listed under "Android Phone > Android Composite ADB Interface"
Perhaps this is the drivers for my Android Phone interfering with the drivers for the Kindle? Iunno. I'm pretty lost on this one.
(* Paraphrased, in my own words, of course)
the driver is the you stated is the right one for kf in normal bootmode
would retry the installation with kfu and watch the output carefully
maybe copy and paste the output for later analysis
seems to be a common problem at the time:
http://forum.xda-developers.com/showpost.php?p=21316424&postcount=49
How about just download the older KU 0.9.1 that's known to work everytime. 0.9.2 had issues installing TWRP.
Once you installed it using KFU 0.9.1, you will have no proiblems getting to your TWRP recovery.
Using the 0.9.1 version did it for me. Thanks a bundle.
Now I'm drooling over ICS on the Kindle Fire. Can't wait for a stable build! +_+
Just follow this guide:
http://rootkindlefire.com/kindle-fire-root/kindle-fire-root-new6-2-1windowsmaclinux/
Sent from my Kindle Fire using xda premium
Related
Hello, brand new to the Kindle. I rooted my device just fine last night and decided to use Kindle Fire Utility to install TWRP. ADB was recognizing the device perfectly and the script seemed to be running fine until it rebooted the Kindle. At that point the script said "reboot: operation not permitted waiting for device" for an extended period of time. After waiting awhile, at this point I did something I probably shouldn't have, I unplugged the Kindle and rebooted it using the power button. It's been getting stuck at the "kindle fire" boot animation ever since. I haven't gotten a screen with a triangle and fire logo.
I tried following the instructions in the sticky but it seems adb no longer recognizes the device, so I can't push zergRush or anything past that.
Is it permanently bricked or is there a method to fix my problem yet?
Thanks for any help.
_______________________
Update: kindle was fixed by uninstalling drivers, reinstalling as android composite usb device, and switching it out of fastboot. not permanently bricked.
sounds like its in fast boot.
open the utility again, check if its in fast boot, if it is run the install command again. if u can't get it installed, use utility to change boot mode back to 4000.
I had the same problem this method worked for me http://forum.xda-developers.com/showpost.php?p=20509949&postcount=245 http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Thanks for the fast replies!
When I try to change the bootmode using the fastboot it just says waiting for device and never progresses. KindleFireUtility shows ADB Online, Boot status at 4002, and fastboot as offline. Device manager doesn't show a Kindle, just an android adb interface with a yellow ! triangle.
I did restart the PC once and the kindle a few times. No luck yet.
I installed the ADB Composite driver again for the device and got this error (attached)
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
uninstall the driverand use the driverin the utility thread? someone said leaving ur kindle connected to ur pc and rebooting ur pc will reboot the kindle? if it works su with terminal and change bootmode back to 4000
sent from my kindle fire
Alright everyone, I got it working after uninstalling the driver for the Android device, shutting down, starting up again, and plugging in and reinstalling the driver, then changing the bootmode using the instructions previously posted. Thank you all SO MUCH for helping as much as you could. Now to try this again!
terracode said:
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
Click to expand...
Click to collapse
Now I'm wondering what you mean by making sure the drivers are installed for TWRP to install correctly. Obviously I missed a step the first time, what do I do to make sure I don't miss it again? Right now when I try to install TWRP again it says "The system cannot find the filepath specified" several times.
would recomend to use following:
http://forum.xda-developers.com/showthread.php?t=1399889
download the utility and prepare according:
http://forum.xda-developers.com/showthread.php?p=20574755#post20574755
change bootmode, install twrp or whatever with the utility
Got twrp on it last night successfully and flashed CM7.
My question is somewhat related to this thread...
I'm on 6.2 (wifi turned off) and was already rooted and am trying to update to the 6.2.1 secured update with root installed update found on XDA. I'm using Kindle Fire Utility v.6, and to the best of my knowledge using the drivers included with the KF Utility program.
In the utility I show...
ADB Status: Online
Boot Status: 4000
Fastboot Status: Offline
Question is I'm not familiar with fastboot and unclear if I have everything configured in order to (safely) install TWRP. In a command prompt when I type 'fastboot devices' nothing is displayed ("adb devices" shows the device). Combined with the fact I've never seen anything but "Offline" for the Fastboot Status, I'm a little concerned I'm missing a piece of the puzzle and hesitant to install TWRP until I know better.
Any help/advice would be appreciated. Thanks!
look at my post on page 1 of this thread !
@Stevebro: I believe if you are using KF Utility v.6, then you should be good to go. As long as you installed and updated the usb Drivers and then ran zergRush, you should be at the point where you can install TWRP. Just make sure you are using the latest version of KF Utility and it should go pretty smoothly.
... After you install TWRP, I'd recommend going back to your KF OS and do a Titanium Backup of your apps and then doing a TWRP backup. When you flash to CM7 you can restore all your apps easily and painlessly using Titanium backup to restore with the Batch restore option.
Couple nervous moments, reboots and switching out of fastboot mode in the utility... but it all went well. Thanks for the help!!
glad to hear everything is fine ...
Glad to hear everything worked out. I myself sat staring at the "yellow triangle" for a couple of hours. lol, but I just kept working through it and tried not to panic and I got everything working again.
I think OP should edit the first post, or get a mod to edit the title. I keep reading random posts about "lot's of people permanently bricking their Kindle Fires" while I cannot recall a single instance of someone bricking and having to return one and it is getting tiresome.
Hi All, I bricked my Kindle Fire after installing Go Launcher so had to resort to rooting it. Fire was stuck at the Kindle Fire screen.
I basically followed this post:
So to fix I needed to root my Kindle with out a UI. Command Line only :-/
Download the Java Development Kit and install http://www.oracle.com/technetwork/ja...ads/index.html
Download the Android SDK and install http://developer.android.com/sdk/index.html
Run the SDK Manager.exe and make sure you install the 'extras' package. (It has the google drivers)
Update your Kindle Drivers http://www.jayceooi.com/2011/12/13/h...db-usb-driver/
Get the Kindle Fire Utility http://forum.xda-developers.com/show....php?t=1399889
(Thank you thank you thank you for writing this util, saved my butt!)
If all is working, you will be able to root your Kindle from the command line!
I am now at the stage where i can boot using option 3 in the KFU and enter TWRP, but when i select option 1 for normal boot i end up back at the kindle fire splash screen (After the yellow triangle shows). Same place i was at pre root!!
I've read a million posts but not sure where im at. Can anyone suggest anything, i'm stuck in a loop...
Any help/comments/suggestions welcome.
Gedi
from the first page of KFU:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
thanks b63, i can get it to recognise after it says <waiting for device>. This put it to the kindle fire screen though...
Also it always shows as Android Composite ADB device too!
I'm missing someting fundemental i think
do you have a yellow triangle in device manager ?
when does it say <waiting for device> ?
immediately after starting KFU or when you select change bootmode -> normal ?
Hi everyone.
I managed to brick my kindle fire within an hour of purchasing it, but using the suggestions on this forum, I was able to get it back up and running in a few hours.
The method that I had to use involved suggestions grabbed from several threads, so I wanted to provide instructions on exactly how I managed to fix mine in case someone ends up in the same situation as me.
For starters, I had just updated my Kindle Fire to 6.2.1 and I was messing around with trying to get the google app manager installed. I rooted the device, and I was changing permissions in the /system/app directory when the device crashed and became stuck on the boot animation. I did not have TWRP installed at the time.
So if you are like me, or in a similar situation, this may be applicable.
These instructions assume that you have adb on your computer.
First, ensure that you are able to communicate with your device using ADB. Verify this by using the command:
adb devices
Click to expand...
Click to collapse
or by using the kindle fire utility and ensuring that the status is online.
If you are not able to communicate with your device AND have the boot animation (right to left reflection across the "Kindle Fire" logo text), you likely have a driver issue.
Several possible ways to resolve this. First, I recommend going to device manager and unistalling the driver for the android phone adb interface. Unplug the kindle fire and plug it in again. The device should show up without a driver as "kindle". Manually apply the proper driver again and check the adb connection. If this does not work, uninstall the driver again and add 0x18d1 at the end of adb_usb.ini on a line underneath "0x1949" and reapply the driver. Toss in a few shutdowns in between some of these steps if you are still having trouble. Hopefully you now have a connection to your device.
If you are not able to communicate with your device AND do not have the boot animation (right to left reflection across the "Kindle Fire" logo text), your kindle fire is in the wrong bootmode (likely fastboot).
To fix this, download fastboot.exe (if you don't already have it) and run the following command, even if you don't have an adb connection)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
or if that doesn't work
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
Click to expand...
Click to collapse
Your kindle fire should restart and now be stuck at the logo with animation, and you should have the ability to communicate with your device through adb now.
Now, you should download the kindle fire firmware (6.2.1 as of the time of writing this) from http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620. Rename this to update.zip and drop it in the same directory as adb.exe on your pc. Execute the following command.
adb push update.zip /sdcard/
Click to expand...
Click to collapse
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/showthread.php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
Quick note: I wrote this from memory quickly to try to help anyone experiencing problems. I'm no android expert, so if there are ways to improve on this or corrections to be made, please let me know so that the community can benefit.
And I don't want to appear to take undue credit for any of these instructions. I did not come up with anything on this guide on my own, everything came from various threads on this forum. These are just the steps that I followed to successfully bring my kindle fire back from death.
Man, My Kindle Fire does not even get detected by my PC
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/show...php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-how...03#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
****When I run the fbmode I am getting stuck on the boot logo screen. Can someone please help me??
that is normal - you are in fastboot mode now - adb commands don't work in this mode - fastboot commands do - resume with the description ...
Thanks for your post.
I also "bricked" my kindle the day I got it but my issue was not having the correct drivers installed when I started the rooting process. My drivers would recognize the Kindle when it was booted normally but when it went into fastboot mode the Kindle would just show as "Unknown Device" in device manager. In windows you can't remove the drivers for unknown device so I had no way of backing out the old drivers.
What I ended up doing was grabbing my other laptop and making sure I had the correct drivers installed, then connected the kindle and was able to back it out of fastboot mode.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
umarsl said:
Man, My Kindle Fire does not even get detected by my PC
Click to expand...
Click to collapse
Does it show up as "unknown Device" in device manager?
you can uninstall the drivers
win 7:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
xp:
http://www.techrepublic.com/article/removing-unused-device-drivers-from-windows-xp-machines/6017628
Just wanted to say thanx for the post. I ran into the exact same condition that the op did where I inadvertently screwed up the permissions on the /system/app directory which caused the kf to wig out and brick. I wished I had seen your post earlier because I ended up going to many posts and piecing together the information which was a little confusing at times. The op is great and I just wanted to point out two observations that seemed to me the most confusing working through the issue and getting it unbricked and hopefully will bring some clarity for folks.
1. Understanding the different states of the "kindle fire" logo.
- Shimmering animation and appears to loop = normal boot mode and is the state that you should be able to communicate with adb. This is the state where you can push files to the kf like twrp and fbmode which is what is needed to get kf in fastboot mode when bricked like this.
- The logo is static and does not "wink" out or loop = fastboot mode. This is when you use fastboot commands on your PC to change boot modes and also execute files such as twrp to get it installed once you pushed it to the kf with adb.
2. USB Drivers.
- This can be a real killer. After playing with this for hours, the one thing that I found that helped the most was when the driver stopped working I would unplug the kf from the PC and then hard reboot the kf (hold on/off ~20 seconds) then just plug back in, don't use on/off. Keep the device manager open on the PC and watch. You will soon start to see a pattern when you have the right driver and do this a few times.
Once these things are ironed out all eventually works out. BTW, this occurred after my kf was upgraded to 6.2.2. So the instructions and tools and everything else you will find still works. Good luck to anyone working through this issue. Just remember, if you can communicate with it, it's almost certain there is a way to recover it.
So, as many new KF rooters have, I seem to have bricked my KF. I rooted it just fine, but when installed TWRP through KFU .93 the process seems to have stopped. After waiting over an hour and reading countless "I've been stuck installing TWRP through KFU .93" threads, and seeing many "I switched to .91 and it worked fine" responses, I decided to give that a shot. After unplugging and hard resetting my KF, it is still stuck on the KF logo screen. No yellow box, just the logo screen.
When I plug the KF into my computer, the device is recognized and the proper KF drivers are installed, but I can't get adb to work at all. Every attempt returns a "Device not found" or a "Server didn't ACK." The device does not show up on my list of attached devices, but in Device Manager it is loaded.
I'm unsure of what the next step should be, as I can't get the hardware to respond to anything but resets, and I can't get the software to communicate with the hardware from my PC. I really don't want to admit defeat and contact Amazon.
*edit* Through more research I've made some progress. Opening KFU and selecting the bootmode option, and then when it says "waiting for device" hard resetting the KF and letting KFU change the bootmode to Recovery has done some things. I got a message saying "Failed ..." but it flashed too fast for me to read. Then, upon several restarts, I received a message saying that the KF needed to factory reset, which it is doing now.
As of right now I have a Factory Resetted, working KF. My updated question is now "Where did I go wrong?"
I assume it had to do with TWRP, as it was working until then. Should I redo the whole process using KFU .91 instead of .93? The root went of without a hitch, but the TWRP was what killed me.
Also, do I do Root THEN TWRP, or TWRP THEN Root? I guess I might need Root access to install a Recovery console, but I'm unsure.
use KFU to root, then hit up my gscript install method in the development thread. easy peasy.
but for the record, you were in fastboot, so it won't see adb commands..
fastboot -i 0x1949 oem idme bootmode 4000 maybe woulda saved you. but avoid fast boot entirely, n use my gscript method.
heres how i did it
I was trying to unbridled my kindle fire all last night and about 5hours today.here is how I did it (don't get your hopes up too high,it might not work)
1.Download kindle fire utility
2.Unzip kindle fire utility
3.To install the driver,its easy,just plug in your kindle, when it pops up with the install wizard say pick from the location of: KindleFireUtility>drivers>kindle
4.run kindle fire utility,select 1 then select 1 again
That's it, hope it helps
Finally tiring of the stock Kindle Fire OS and wanted a more robust tablet experience I decided I wanted to root my Kindle Fire and install an ICS ROM. Here is how I messed up my Kindle Fire.
1. I downloaded "Kindle Fire Utility 0.9.6
2. I extracted the RAR
3. I ran "install_drivers" and they installed perfect
4. Hooked up my Kindle Fire, it popped up saying found and finalizing some drivers and then a window popped up showing me the contents of my Kindle Fire.
5. I ran "run" and it brought up a menu saying "ADB Status: Online" so I chose option 2 "Install permanent boot with superuser"
6. It said it didn't find "twrp" but it would download it
Here is where I ran into a problem, it must have started to do something to my Kindle before it got to this point. For some reason KFU was unable to download "twrp" as it keep erroring out and trying again. After 15 attempts I decided to close the DOS window down and unplug the Kindle Fire. Now my Kindle Fire will not boot, it hangs at the "kindle fire" logo. I can hold the power in for 30 seconds and shut it off but it will not load boot up, it just stays at the logo. I can plug the cable in with it either off or on the kindle fire logo but the PC never recognizes it. I even when in and the driver is still there and installed properly.
Why would it start altering my Kindle Fire if it can't get TWRP downloaded? What can I do?
GameGuru41 said:
Finally tiring of the stock Kindle Fire OS and wanted a more robust tablet experience I decided I wanted to root my Kindle Fire and install an ICS ROM. Here is how I messed up my Kindle Fire.
1. I downloaded "Kindle Fire Utility 0.9.6
2. I extracted the RAR
3. I ran "install_drivers" and they installed perfect
4. Hooked up my Kindle Fire, it popped up saying found and finalizing some drivers and then a window popped up showing me the contents of my Kindle Fire.
5. I ran "run" and it brought up a menu saying "ADB Status: Online" so I chose option 2 "Install permanent boot with superuser"
6. It said it didn't find "twrp" but it would download it
Here is where I ran into a problem, it must have started to do something to my Kindle before it got to this point. For some reason KFU was unable to download "twrp" as it keep erroring out and trying again. After 15 attempts I decided to close the DOS window down and unplug the Kindle Fire. Now my Kindle Fire will not boot, it hangs at the "kindle fire" logo. I can hold the power in for 30 seconds and shut it off but it will not load boot up, it just stays at the logo. I can plug the cable in with it either off or on the kindle fire logo but the PC never recognizes it. I even when in and the driver is still there and installed properly.
Why would it start altering my Kindle Fire if it can't get TWRP downloaded? What can I do?
Click to expand...
Click to collapse
Oh and I forgot to mention that "Kindle Fire Utility" shows it as "Offline" now and nothing I can do can get it to say online.
GameGuru41 said:
Oh and I forgot to mention that "Kindle Fire Utility" shows it as "Offline" now and nothing I can do can get it to say online.
Click to expand...
Click to collapse
Anyone please?
Ok I fixed in using a command line method from a user on this forum.