Related
So, I've been up all night after buying this Fire trying to fix it, and I've decided to go along with my original decision to just return it. I'll rewind a bit to give you guys a play by play to show how I got to what I've determined is a FUBAR situation, and hopefully you guys can help me at least remove TWRP so I can return it without much issue.
If it's tl;dr, I bolded the main errors I got from the console and TWRP
1. I purchased my Kindle Fire from Best Buy with a 1 Year Protection plan, so in all reality, I could just break it in half and get a replacement, but I don't necessarily want a replacement.
2. I initially purchased it for my mom, but when I found out that the stock Fire OS didn't have Korean input or the option to have a Korean interface, I did a bit of research and started reading up on how to root, how to install the market, things like that. My mom's not a native English speaker, so this was an important thing for her, etc etc.
3. I read multiple guides on this forum and others, and rooted using the guide found here , since a few of the threads I was reading through seemed to point in that direction, and I had a bad experience with SOCR on my Droid X.
4. The root was successful, so I moved on and used KFU .3 to do the rest of the important bits; android market, etc etc.
5. Everything was working fine, but, after looking through it, I realized that it wouldn't work for what I needed it to, and I would have to return it, so, I attempted to unroot the tablet using TWRP's interface.
6. I cleared the cache, the devlak cache, and system wiped, then restored using the system restore point in the TWRP folder, figuring after that, the Kindle would boot up with stock OS and then I would just system restore the default way. This method got me stuck in a recovery-loop, and no matter what I did, the Fire always booted to recovery mode.
7. I figured I had bricked it, so I followed the steps in this guide, but always seemed to have problems at the step where I have to chmod 755 of the zergRush. I get "Not a directory" error, which after doing some research, I believe is on account of me no longer having rw privilege?
8. I looked around some more, ignoring that guide, and found a method to force-push the amazon update, but TWRP would no longer run the update, saying it could not Mount the SD Card due to an Invalid Argument, and I have yet to determine what that means.
9. After manually changing it to fastboot in an attempt to at least get it out of recovery mode, I have the Fire recognizable as a device in my ADB, but it is now stuck in a fastboot loop, and when I attempt to re-root it in order to give myself rw privileges again, it stalls on "waiting for device" and never gets past that point.
Update
I tried to reroot while the Fire was stuck in the Kindle Fire splash screen using the KFU tool, and used zergRush, but the error message I got was - exec '/system/bin/sh' failed: No such file or directory (2) - 4 times over.
What I think the problem is, is that when I wiped the cache/devlak cache/ and system reformatted, it wiped my SU privileges, and as a result, no longer allowed me to write the backup to the Fire, therefore leaving me in a perpetual state of limbo?
What I'm asking for from you is;
What can I do to fix this?
Is there any more information you need/want from me?
And finally,
Is there an easy way for me to remove TWRP from the system?
Thank you.
Hi!
There are a lot of great tips regarding TWRP and fastboot over at RootzWiki.
Some users are reporting the same fastboot loop that you currently experience. I suggest you read the thread and follow the suggestions. One suggestion which you may want to try first is the one in this post.
Thank you for the reply. I did as you suggested and followed the links and the post on the guide, and although that did change the nature of my fastboot loop, I'm still stuck in a fastboot loop.
I was initially stuck in a fastboot loop on the Kindle Fire logo, which I determined by running fastboot devices, while it was stuck on that logo, and it showed the device as being fastboot. After following that guide, and using the hard reset, then using the "How to Unbrick" in order to change back to a normal boot, I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it. I'll continue looking through the guides to see if I can solve the problem, but thank you once again, and sorry for not clarifying which type of fastboot loop I was in.
Sorry it didn't work out! However...
isjonamon said:
I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it.
Click to expand...
Click to collapse
I really though the solution posted over at RootzWizi would solve this problem. Getting stuck at the yellow triangle is 'common'. I really though adding
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
Click to expand...
Click to collapse
to android_winusb.inf would solve it. But if you are able to recognize your Fire in fastboot mode via your PC, I guess that's not where your problem is.
Is this tip to any help?
And lastly... the great Kindle Fire Utility thread is worth checking out, in case you haven't already
I hope you'll find a solution to this problem!
I've tried the tip you linked me to, and sadly it didn't do anything for me.
Moving on, though, I'm reading through the KFU thread again to see if there was anything I missed, and decided I might as well try re-flashing to CM7 to see if I can at least get it working up to a rooted/rom standpoint. I figure from there, I can at least have a working platform to factory reset from. If I can't do that... well...
Does anyone know a way to just return everything to factory settings? To just wipe everything and make it so it turns on like it's out of the box? Either through adb commands, or TWRP or anything?
Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Fixed it!!
For anyone interested, this is what worked for me;
From where I ended up with the problem, I followed hachiueno's advice and read through the KFU's thread as well as the TWRP thread on Rootzwiki, that led me to adding those lines to the device firmware, which I think was the first step in the solution, so...
Step 1. Add
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
to android_winusb.inf , then restart your computer with your Fire unplugged.
After that, I was inspired, through reading the KFU thread, to attempt to manually install CM7 since I wasn't having much luck zergRushing on my own, so, I went to the CM7 thread and pushed the Update.zip there, and used my TWRP to install that, effectively rebuilding my filestructure, since it seems the Kindle Fire doesn't have so much as a SH folder in it.
Step 2. MANUALLY (maybe) install CM7 if you can.
Once I got CM7 up and working, using the USB mounting option, I replaced the update.zip in the sdcard folder with the Amazon 6.2 firmware downloaded from their website, renamed to update.zip, and then unmounted my fire from my laptop.
Step 3. Download the Amazon 6.2 Firmware from amazon's website (I can't post...), rename it to update.zip, and replace the CM7 mod update.zip in your /sdcard directory with it.
Then, I figured if I ran TWRP like it was supposed to run, and just ran the update.zip like any other ROM, it should fill in the blanks in the filesstructure, bypassing Amazon's own lack of certain folders, and various other things, filling in the gaps as they were. The next step might be entirely redundant, since I'm a bit clueless, and it might have been entirely luck on my part, but I initially forgot to wipe my cache, devlak cache, and system restore, so I did all that and did it again, and my wishful thinking leads me to believe that doing that saved my ass from having a crapton of errors....
Step 4. Using the install function on TWRP, install the renamed Amazon update.zip, reboot, clear your cache, devlak cache, system reformat, then reinstall the update.zip. Reboot one more time, and you should come up to the Kindle Fire splash screen. Leave it for a few minutes, and it'll be like it just came out of the box.
Thanks for all your help. I love you. Seriously. No homo. Maybe a little. I love you.
Good to hear that you managed to boot it again!
isjonamon said:
Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Click to expand...
Click to collapse
This guide seems to be an easy solution to this. However, no one has replied any success or failure, so not sure if it's 100% bulletproof for everyone... if I were you, I would follow JackpotClavin's guide here. He's a known developer here and knows what he's doing, and many successful replies from users having used this method... so yeah, just to be 'sure' (can you ever be...?) that you won't experience any further problems, I recommend the last one.
I actually used the first guide in order to get the Amazon update, but couldn't post a reply since I'm still a noob. I had to do a few things differently, and ultimately got a few different results, but posted up my own version of the steps.
Once again, thanks for all your help!
It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium
all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire
smirkis said:
all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire
Click to expand...
Click to collapse
I actually changed bootmodes quite frequently, following multiple threads and guides, changing from recovery, to normal, to fastboot, and back and forth when called for. Changing to fastboot stuck me in an eternal fastboot loop, changing to normal reverted me to a recovery loop, and recovery was the only bootmode I could access adb from.
Sheolrock said:
It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Driver issues seemed to be part of the problem for me, but just updating the drivers didn't fix the issue entirely. I'm jealous that you got it to work with just a driver update...
Hey i believe im in the same problem but i keep reading the posts and im still stuck and i have no idea what to do im worried that i cant fix it.... Some please help me ASAP
Thanks in advance
wrong boot mode ?
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
bad drivers ?
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
I have had the looping problem and none of these would fix it. I got it to work by adding those lines to android_winusb and running the run.bat, trying to make it switch to normal mode as the kindle was turning on. Somewhere along the yellow triangle when it was loading it accepted the command from KFU. Hope this helps, only thing that worked for me.
the drivers i included contain all the necessary entries in adb_usb.ini and android_winusb.inf
Please can someone help me!?
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?
awidawad said:
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?
Click to expand...
Click to collapse
you switched it to fastboot (4002) - adb commands are not working in fastboot mode !
little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
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
Not sure if this is totally helpful to anyone but originally I thought the thread was started with a posting of being stuck bootlooping into twrp in recovery mode with a complete loss of file structure. I had this same issue my Kindle would not start in anything but straight to twrp and if I tried to flash my CM9 ICS rom it was not there and only the twrp folder empty was. So I went to mount and mounted usb storage and moved the stock update zip file from amazon to the twrp folder and flashed that. Worked like a charm now I appear to be straight stock. I am no developer of this stuff I just am a bit of a tinkerer so don't understand all the code stuff but it starts like a normal kindle and appears totally stock. So hopefuly that helps you return your deice to stock for return or to continue wahtever modifications you intend.
2992
I tried to use the kindle fire utility in order to root my fire, but when I tried to use it, the first thing I did was install the drivers..... Then change it into fast boot mode, which I didn't realize would make it automatically reboot.... With out TWRP, or the fire fire fire boot loader. It is stuck at the "Kindle Fire" splash screen, and does not even connect to my computer. Is there a way to change it back to normal boot mode? Because when I tried to use the kindle de-bricking utility, it did not work, because it says waiting for device. If anyone could give me some advice, I would appreciate it.
May not help, but try the following: http://forum.xda-developers.com/showpost.php?p=21477909&postcount=13
have you tried to hold pwr button for ~20sec ?
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
b63 said:
have you tried to hold pwr button for ~20sec ?
Click to expand...
Click to collapse
I actually did, I had tried a hard reboot several times.
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I will try as soon as I get home. Thanks for the help so far!
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
it's not save without fff ! you need it to get to twrp and to have fastboot available for some seconds during startup
would recomend to try with kfu 0.9.3 and 0.9.1
some people have success with only one of the versions
Glad you got back to stock at least. The problem I had was that my internet connection timed out when KFU was downloading the files for the TWRP and FFF installation. There were incomplete files that KFU recognized as being there when i re-tried and it tried to install them again. You need to make sure you delete the files in the TWRP folder before you try again that way KFU won't find them and will download them again, hopefully successfully this time. You could also just delete the entire KFU you already have on your computer and download the whole thing again and re-try.
Hopefully this helps.
elporsche said:
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
Click to expand...
Click to collapse
That means it can't find the ADB.exe in tools for Kindke Fire Utility. The tools folder must be in the same folder as the batch file.
b63 said:
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
Click to expand...
Click to collapse
Worked! Thank you so much sir! Now that I followed a guide! (since I am no longer a derp about it) I am now rooted.
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Can you please tell me how you changed the boot mode because i also bricked my kindle by the kfu.
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
b63 said:
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
Click to expand...
Click to collapse
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
papugoz said:
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
Click to expand...
Click to collapse
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
So what your saying is i can't do anything.
kingrafa135 said:
So what your saying is i can't do anything.
Click to expand...
Click to collapse
it is nearly impossible to realy brick a kf - just do as i suggested
if it's not working tell us what exactly happens ...
some important hints from the op 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.
Click to expand...
Click to collapse
and from vashypooh - dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
b63 said:
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
Click to expand...
Click to collapse
From my exp with KFU, I had to use fastboot command directly, becouse KFU, couldn't hadle it.
So I was messing around with my rooted Kindle Fire trying to apply a new theme to my Ice Cream Sandwich Launcher with metamorph and totally screwed everything up. I rebooted my Kindle Fire and it was stuck on the kindle fire logo screen. This morning I tried to unbrick it with the Kindle Fire Unbrick utility but it screwed up everything even more. Now i'm stuck on the yellow triangle screen (firefirefire), I realized that I totally screwed up the framework apk in the system folder. My computer will recognize the Kindle Fire but it comes up as "kindle" in the Other Devices in the "Device Manager". I tried to update the driver but the wizard will say that it cannot find any driver. What should I do? I already read many other posts but throughout the steps I get stuck on one and cannot continue.
I suggest try the following:
Adb kill-server
Adb start-server
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Good luck
Sent from my Amazon Kindle Fire using Tapatalk
I know how to fix the yellow triangle, do this
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
fedorp said:
So I was messing around with my rooted Kindle Fire trying to apply a new theme to my Ice Cream Sandwich Launcher with metamorph and totally screwed everything up. I rebooted my Kindle Fire and it was stuck on the kindle fire logo screen. This morning I tried to unbrick it with the Kindle Fire Unbrick utility but it screwed up everything even more. Now i'm stuck on the yellow triangle screen (firefirefire), I realized that I totally screwed up the framework apk in the system folder. My computer will recognize the Kindle Fire but it comes up as "kindle" in the Other Devices in the "Device Manager". I tried to update the driver but the wizard will say that it cannot find any driver. What should I do? I already read many other posts but throughout the steps I get stuck on one and cannot continue.
Click to expand...
Click to collapse
First off, what rom are you running on you Kindle stock 6.2.2, CM7, CM9? Did you make a backup of the original framework-res.apk? If so follow these instructions (assuming you have adb working):
if original framework-res.apk is stored on you computer:
from command prompt (start -> in search box type cmd then enter) cd to where you have backed up the original file if it's on your computer
then type the following commands
adb devices
adb remount
adb push framework-res.apk /system/framework
adb shell chmod 644 /system/framework/framework-res.apk
adb reboot
if the original file is stored on your kindle:
adb devices
adb remount
adb mv /path-to-original/framework-res.apk /system/framework/framework-res.apk (fill in actual path in "path-to-original")
adb shell chmod 644 /system/framework-res.apk
adb reboot
Hint: If you didn't make copy of original framework-res.apk, you can always download and open up the install zip for your rom and extract the original file. Good Luck!
Kindle Fire Bricked PLEASE HELP!!!
So like every other noob with a new kindle fire 6.2.2 i tried to root it, after nearly 3 days of trying different ways i was able to root it i then proceeded to install go launcher ex once i selected go launcher it froze and i have not been able to boot sense.i was stuck on kindle fire logo and it would not do anything i tried to run the unbrick utility 1.1 and 1.0 i get device not found but it does say it was unbricked but it is not, now let me say how stupid i was to not create a backup i know i know ugh im kicking myself now... my computer sees it under device manager as android adb interface when pluged in and i see the usb connection in the task bar on WIN 7, but i cannot access it as a protable drive. when i turn it on it will only load twrp.im guessing im screwed and everything is gone... any help will be much much appreciated, im not sure what other info you may need at this point and i am sorry for my ignorance in advance. thank you for any help!
and yes i have tried several things to get it working again which has gotten me to this worse point...i was able to see it normaly as protable device but i dont know what i did to get this.
somebodyssomewhere:
- boot to twrp
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
now you can delete the faulty .apk of go launcher with adb commands or install a new rom:
- now you can download and copy your new rom to sdcard (ie prerooted stock)
- mount sdcard -> "mount /sdcard"
- exit adb shell -> "exit"
- tap install in twrp and install the new rom
- ignore errors about volume "misc" - the kf don't have a volume "misc"
- on the screen where you return after installation tap clear dalvik/cache
in eighter case set the bootmode back to normal:
- set boot mode to normal -> "adb shell idme bootmode 4000"
- reboot -> "adb reboot"
thank you for your replies i will try them all as well as let my friend know who is coming over to try to fix my stupid lol thank you all for your suggestions.
Update - Here is the Fix
With a bit of research and lots of help from b63 I got my Kindle Fire to work again:
1. Booted into TWRP (Recovery Mode).
2. Flashed new MD5 zip (Kindle Fire Stock 6.2.2).
3. Wiped all data off the sd card except the TWRP folder and the MD5.
4. Booted the Kindle Fire and it went straight to the lockscreen.
Thanks for all your help!
Fedor
Still am sorta stuck
Ok, so I tried to flash a MIUI ICS rom using TWRP and followed the (apparently crappy) instructions here. So, I'm stuck on the TWRP logo and have used the Kindle Fire Utility to try and reset the bootmode to no avail (it does set it and it reboots but still never progresses into the actual TWRP menu.
Any ideas?!
karlhafer said:
Ok, so I tried to flash a MIUI ICS rom using TWRP and followed the (apparently crappy) instructions here. So, I'm stuck on the TWRP logo and have used the Kindle Fire Utility to try and reset the bootmode to no avail (it does set it and it reboots but still never progresses into the actual TWRP menu.
Any ideas?!
Click to expand...
Click to collapse
would try to follow this:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
i did finally get my kindle working again after several reboots of the pc and kindle and re installing the drivers a couple times it is now recognized. after almost a week of messing with this i have found that rooting this is alot more simple then many people are giving directions for.
what i did:
download kindlefireutility1.1
download what apps you want BEFORE you root, i have found many apps work when installed before rooting some apps may still not work..
once kindle fire utility is downloaded extract it to your c: drive
go into the kindle fire utility folder in the c drive and install the usb drivers if you need them,if not click run this will open the utility make sure you have a fresh reboot of both the kindle and pc, plug the usb cable into the kindle and pc leave it on usb mass storage mode, move any apps or files you want and press 5 to install the latest twrp MAKE A BACKUP IN TWRP BACKUP ITS EASY, DO NOT PRESS CONTINUE UNTIL KINDLE IS BACK ON THE HOME SCREEN it will say press any key a few times when using this utility.
once done you will want to install the google frame work and Go Launcher.The kindle will reboot a couple times during all this and can take up to 5 min to load so be patient.
go back into the kindle utility and then press 7 and then press #2
once this is done you can then root so hit # 3 for perm install of burrito and super user
now once those are done and you are back into the kindle home screen click on the super user icon looks like an android dude and click ok. if you dont see ok then it didnt work and try again
then click on the burrito root guy he looks like an android cop open him and if you see exit then ur good if not try again.
now your kindle should be rooted. now if you want to install a custom ROM do the same exact steps but then when it is rooted power off the kindle and press the power button once and immediately again press and hold the power button for 7 seconds until it turns orange you will then see the yellow triangle for about 2 min then it will load twrp
once in twrp go tot he folder where you saved your ROM onto your kindle, i like to copy files to the download folder..
select your rom then click on flash, you may get a couple errors but ignore them. make sure to wipe the cashe and then hit reboot and you should be good...i hope this help someone and if you need help feel free to send me a msg. im no expert but ill try
Aim rrawrimakitty
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
good info thx for your post
does anyone have this issue?
Important
before do any fix brick or flash firmware. Please use the normal cable to charge your kindle fire at first. The 950ma charger is best. You charging time is 6-8H(battery empty). most confuse case can be solved!
xiaohewu said:
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
Click to expand...
Click to collapse
I was looking at this device driver distribution hoping to find something in here that would help people having fastboot problems. When compared to the set of files you'd get in KFU, this one is missing a couple of DLL files and some adb hardware IDs in the INF file.
I think most people would have already installed from KFU or used directions to install from SDK before looking at this set because in most cases, you'd need the adb drivers before the fastboot drivers. Maybe I'm just not understanding why you'd want to just install only the fastboot drivers and skip the adb ones?
kinfauns said:
I was looking at this device driver distribution hoping to find something in here that would help people having fastboot problems. When compared to the set of files you'd get in KFU, this one is missing a couple of DLL files and some adb hardware IDs in the INF file.
I think most people would have already installed from KFU or used directions to install from SDK before looking at this set because in most cases, you'd need the adb drivers before the fastboot drivers. Maybe I'm just not understanding why you'd want to just install only the fastboot drivers and skip the adb ones?
Click to expand...
Click to collapse
The method is not adb driver. it's only recovery mode fastboot driver. and donot need type -i 0x1949.
?
xiaohewu said:
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
Click to expand...
Click to collapse
how can i find the adb driver files?
visitor831 said:
how can i find the adb driver files?
Click to expand...
Click to collapse
in this mode, can not use adb. If the kf was booted, you can use the adb. below is the adb driver.
I was attempting to root my kindle using kfu and it attempted to download twrc.
Kindle fire utility had managed to reboot my kindle before this.
The download failed and the utility attempted to continue without it.
The utility claimed that "Your kindle is now rooted", but the kindle never got past the boot screen.
I am assuming that the kindle is stuck in boot mode, but, when I tried to use the bootmode: Normal (4000) option in kfu, it said: The system cannot find the drive specified
I have also tried using kindle unbrick utility with similar results.
This was installed on a win 7 32-bit system
Twrc and Firefirefire did not install, so don't suggest that.
Fireofgod8 said:
I was attempting to root my kindle using kfu and it attempted to download twrc.
Kindle fire utility had managed to reboot my kindle before this.
The download failed and the utility attempted to continue without it.
The utility claimed that "Your kindle is now rooted", but the kindle never got past the boot screen.
I am assuming that the kindle is stuck in boot mode, but, when I tried to use the bootmode: Normal (4000) option in kfu, it said: The system cannot find the drive specified
I have also tried using kindle unbrick utility with similar results.
This was installed on a win 7 32-bit system
Twrc and Firefirefire did not install, so don't suggest that.
Click to expand...
Click to collapse
Let's first determine whether your drivers are working properly or not.
Shift + Right-click on the KFU folder containing fastboot.exe and select "Open command window here". In that window, enter:
Code:
fastboot -i 0x1949 getvar product
If it hangs at "waiting for device", hold the power button until the device shuts down, then start it up again.
This appeared right after entered:
product: kindle
finished. total time: -0.000s
I assume that means they are installed correctly
Fireofgod8 said:
This appeared right after entered:
product: kindle
finished. total time: -0.000s
I assume that means they are installed correctly
Click to expand...
Click to collapse
Before you do anything...Do you know for sure whether you have a first generation or second generation device? If you have a second generation device, STOP. Continue no further.
If you know for sure you have a 1st generation device, enter the KFU option to install TWRP. If it hangs at "waiting for device", restart it same as before.
If the device doesn't automatically boot into TWRP:
Code:
fastboot -i 0x1949 oem idme bootmode 5001
fastboot reboot
Once you're in TWRP download FFF1.4A.zip, push it to your sdcard with adb and install it via recovery. Avoid installing FFF with KFU. It's risky and can really brick your device if something goes wrong. Get at least this far before trying anything else.
I am fairly certain I have the 1st gen.
Kfu did not display anything beyond 'Activating Fastboot (4002)
Fireofgod8 said:
I am fairly certain I have the 1st gen.
Kfu did not display anything beyond 'Activating Fastboot (4002)
Click to expand...
Click to collapse
If "fairly certain" is good enough for you, so be it.
When it says activating fastboot, restart the device as before. It's a "bug" in the bootloader that causes that.
I attempted using the same code you gave before but put 4000 instead of 5001 and it worked.
Thanks for the help,
sorry to waste your time
Btw, your post on 'this is what you all sound like' is hilarious, even if i am one of the noobs.
The problem now is your device is rooted (or seems to be) but you don't have recovery or a custom bootloader installed. If anything happens to your system files, it can brick your device with no way to recover it.
I highly suggest you read the Kindle Fire for Beginners guide stickied at the top of this forum and get recovery installed so you can install a new bootloader.
"That's a special kind of stupid. The kind that makes me laugh."