Database Users

[Q] Super Ultra Brick (WITH VIDEO)

UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?

looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state

b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.

maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer

b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.

Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.

ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.

skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.

Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?

at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...

b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.

fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...

b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.

great idea with the video !!!

b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?

I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.

with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...

b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!

The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)

foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.

[SOLVED] Stuck in boot loop with 6.2.2 and HAVE adb shell access, but still stuck...

Firstly, I'm sorry for creating a new thread, but please know that I searched everywhere (here and around the Internet) first. I barely slept last night. I have read and read. I'm still stuck.
I was able to root following these instructions - http://forum.xda-developers.com/showthread.php?t=1410223 - and all was good for a little while, until I made a bone-headed mistake in the File Expert app while trying to install Google Market. I changed the permissions to /system/app and I'm sure that if I was able to change them back, I'd be fine. I just can't figure out how to do that.
What I can do is connect to the device via ADB, but if I go to adb shell, the prompt is a $. As I understand it, I need that to be a #. I can't get a # prompt, because when I run "su", I get an error that says "Segmentation fault su". (Sometimes I get a different error message, but I'm sorry, I forget what that is right now.)
Anyway, so because I'm not superuser, when I attempt to run "chmod 755 /system/app" (which is what I know I need to do), I get an error "Unable to chmod ... Read-only file system."
In order to get around that error, I know I need to mount as readwrite. However, when I try to run "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system", I get an error that says, "mount: Operation not permitted."
No doubt, I cannot chmod or mount because I'm not su. In an attempt to regain su, I tried to run BurritoRoot2.bin again (I don't know if that makes sense, but I decided to try it anyway, because BurritoRoot2 is what worked for me last night, and everything really was fine until I messed up those permissions). Anyway, that was last night. Today, BurritoRoot2 won't work anymore. Now I get an error says, "android.util.AndroidException: Can't connect to activity manager; is the system running?"
Well, no. The system is not running. That's sort of my problem.
I have no idea what to do now. I do not have TWRP installed. If I did have that installed, I might be able to flash a completely stock 6.2.1 or 6.2.2 ROM, thus restoring everything to "out-of-the-box" condition, which would be fantastic right about now. I don't know if I can install TWRP at this point, however, since my access to the device is so limited.
PLEASE help me... Where, exactly, should I go from here?
(Thank you for reading this. I'm sorry it's so long; I wanted to be thorough.)

you have to install fff and twrp therefore you have to get to fastboot:
http://forum.xda-developers.com/showthread.php?t=1414832
then install twrp:
download from http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
install with:
fastboot -i 0x1949 boot recovery\twrp-blaze-2.0.0RC0.img
and reboot:
fastboot reboot
now you can flash one of the prerroted stock roms or cm7 - whatever you like
would not use the stock rom from amazon cause you'll loose fff, twrp and root

Okay, so far so good! Thank you so much for that information.
It seems as if fastboot has been enabled without complication. I'm moving on now to the download and installation of TWRP and FFF. I'll let you know how it goes!

Well, crap. Now I'm stuck at the yellow triangle and "press power button for recovery", except pressing power does not start recovery.
AND, I can no longer access the device via ADB. The drivers appear to be invalid now. :`-(
I'll be working my way through this thread now - http://forum.xda-developers.com/showthread.php?t=1408056 - and again, will report back later.

CarpeNivem said:
Well, crap. Now I'm stuck at the yellow triangle and "press power button for recovery", except pressing power does not start recovery.
AND, I can no longer access the device via ADB. The drivers appear to be invalid now. :`-(
I'll be working my way through this thread now - http://forum.xda-developers.com/showthread.php?t=1408056 - and again, will report back later.
Click to expand...
Click to collapse
you'll have to update the driver - some did up to 4 times to get the right driver for each boot mode
in short:
normal boot -> android composite adb interface
fastboot -> android adb interface
adb is'nt working in fastboot mode and you'r still in fastboot mode
once you got twrp installed correctly, the drivers updated and correctly recognized you can force to recovery mode:
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
btw. to get to twrp you have to press the button repeatently (not holding,not once) till the button gets orange

After rebooting the Kindle several times, it is now appearing in Device Manager as "Android ADB Interface" (which, if I'm understanding your most recent post, is correct). However, it is not listed when I type "adb devices", so that's troubling. And, when I try to run the "fastboot oem idme bootmode 4000" command, I get an error that "AdbWinApi.dll is missing from your computer".
So far I've only searched the forums briefly, but that error seems to be related to improper drivers, which means I'm even MORE confused, since the drivers appear correct now. Well, they appear correct in terms of what I see in Device Manager. I'm still uncomfortable about "adb devices" not returning anything, though.

just updated my last post
got it - from where do you run the commands kfu tools folder or sdk ?
if you use kfu tools folder (would recommend cause there are all necessary files) then move kfu to something like c:\kfu - it don't like spaces in pathname

ah-HA!!
Thank you. I was running the fastboot from "C:\Kindle Fire Utility v6\", which was clearly wrong. First I renamed that folder to C:\kfu\ and then tried from there (but I was obviously still misunderstanding your post at that point). THEN, I read your post again, and realized I needed to be in the C:\kfu\tools\ folder. From there, I ran...
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
...and I am now inside TWRP! It is working.
To be abundantly clear (for any others who many be reading this in the future), after typing those commands, the Kindle rebooted itself. I then waited a little while, and the green light changed to orange (I had tried waiting before, but nothing happened previously). Shortly after the light turned orange, the Kindle rebooted itself again (on its own). It was on that reboot that TWRP started.
And that's where I stand now. I don't have time to actually use TWRP at the moment, though. I'm going to have to come back to this later.
But thank you again SO MUCH for getting me this far. I might just be able to take it from here.

to get to normal boot once your finished maybe you have to issue adb commands since adb is working in recovery
adb shell su -c "idme bootmode 4000"
adb reboot
and:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
good luck !

HOT DAMN, I have a Kindle again!!
Alright, so once I had TWRP installed, I noticed there was a menu choice labeled "Fix Permissions". Since all I really wanted to do was undo the mistake I made with /system/app, I wondered if clicking that would do it. So I tried it.
When that finished, I connected via adb shell and checked the permissions on /system/app. They were still wrong. But, I also had a # prompt now, not a $. So then I thought, well, I bet I can use chmod now.
And I could! "chmod 755 /system/app" worked! At this point, I thought that might be good enough. I may not need to flash a ROM after all. I mean, changing those permissions is all I really wanted to do last night. Well, that and sleep.
At this point, I tried leaving the shell and running "adb shell su -c "idme bootmode 4000"" from cmd, as instructed, but that didn't work. It said "su" was not found. Hmm. On a whim, I decided to go back into the adb shell, and just type "idme bootmode 4000" right from the # prompt. It seemed to accept that. Then I typed "reboot" from the next # prompt.
The Kindle rebooted. At first, it went to the yellow triangle with the "press power button to enter recovery" screen. I didn't press anything. I just stared at it and waited. Eventually, it rebooted itself. On this reboot, it went to the Kindle Fire logo!! I wondered if it was working again, or just stuck back where I had been this morning. So I waited, tensely. I have mixed emotions about that logo animation now, ya know.
AND THEN IT BOOTED TO THE NORMAL LOCK SCREEN!!!
AND THEN I SWIPED TO UNLOCK, AND EVERYTHING WAS JUST AS I LEFT IT!!!
See? I told you it was just those permissions. I knew it all along.
Anyway, b63 is the best ever! Thank you SOOO much. If you're even in Denver, let me know. I owe you at LEAST a beer! Or if you have PayPal, seriously, I'll hook you up that way too. I really, really appreciate it!
(And... Original title edited. "Solved"!)

I tried following the fix but I am lost at the part that says:
then install twrp:
download from techerrata.com/file/twrp2/twr...e-2.0.0RC0
install with:
fastboot -i 0x1949 boot recovery\twrp-blaze-2.0.0RC0.img
and reboot:
fastboot reboot
I do not understand what that means. Plus, I now have the yellow triangle and ADB does not recognize my kindle.

that is normal - your kf should be in fastboot mode now - adb is'nt working here
regarding the driver you have to reinstall the driver at this point - in fastboot mode it should be "android adb interface" in device manager - here is how to do:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
then resume with the downloads and the commands

I just tried, that, but it said that the driver was the same one installed. Is there a different driver that I am supposed to be using? I selected the one I used to root it in my .android file. Is that the right one?
---------- Post added at 05:50 PM ---------- Previous post was at 05:43 PM ----------
Well, I think I just FUBARed it. I uninstalled the driver, reconnected, and not it is not letting me re install the driver because windows says its broken.

Daniel_Fate said:
I just tried, that, but it said that the driver was the same one installed. Is there a different driver that I am supposed to be using? I selected the one I used to root it in my .android file. Is that the right one?
Click to expand...
Click to collapse
no it is'nt - let's start at the beginning and check the precautions:
1. it would be good to know on what computer you are (os/bit)
2. download last kfu from http://forum.xda-developers.com/showthread.php?t=1399889
3. extract it to c:\ and rename from "kindle fire utility" to "kfu" that it is c:\kfu
4. the driver is now at c:\kfu\drivers\kindle - the file is android_winusb.inf
now you have all what you need
tell me if you'hv got it - i'll guide you further

AHA! I got it back, ill follow what you asked. I am running Win 7 64 bit.
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Alright, I downloaded, unzipped, and renamed the KFU. I went into device manager and selected update driver software, went and browsed and selected the kindle folder for the drivers. It started to install, asked if I trusted this unknown source, then started installing. At the end of the install it said:
"Windows found the driver software for your device but encountered an error while attempting to install it.
Android ADB Interface
This device cannot start. (code 10)"
Now my kindle is tethered and on. The screen is just the static kindle fire logo. thoughts?

Daniel_Fate said:
AHA! I got it back, ill follow what you asked. I am running Win 7 64 bit.
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Alright, I downloaded, unzipped, and renamed the KFU. I went into device manager and selected update driver software, went and browsed and selected the kindle folder for the drivers. It started to install, asked if I trusted this unknown source, then started installing. At the end of the install it said:
"Windows found the driver software for your device but encountered an error while attempting to install it.
Android ADB Interface
This device cannot start. (code 10)"
Now my kindle is tethered and on. The screen is just the static kindle fire logo. thoughts?
Click to expand...
Click to collapse
still trouble with the drivers - try to run install_drivers.bat from c:\kfu\
the status of the kf is ok on the logo - it's fastboot

b63 said:
still trouble with the drivers - try to run install_drivers.bat from c:\kfu\
the status of the kf is ok on the logo - it's fastboot
Click to expand...
Click to collapse
Here's what I did:
Opened cmd
entered "cd c:\kfu\"
entered "install_drivers.bat"
A window popped up saying "Welcome to the Kindle Fire Driver Installer. This will
walk you through updating your Kindle Fire. Click Next."
Clicked next
Says "drivers were successfully installed on your computer: Androidusbdeviceclass"
Clicked finish
Went to device manager
Still have yellow triangle.
Am I missing something here out of stupidity/ignorance?

Daniel_Fate said:
Here's what I did:
Opened cmd
entered "cd c:\kfu\"
entered "install_drivers.bat"
A window popped up saying "Welcome to the Kindle Fire Driver Installer. This will
walk you through updating your Kindle Fire. Click Next."
Clicked next
Says "drivers were successfully installed on your computer: Androidusbdeviceclass"
Clicked finish
Went to device manager
Still have yellow triangle.
Am I missing something here out of stupidity/ignorance?
Click to expand...
Click to collapse
no - you don't miss something - it's allways a hassle with win7 espacialy 64 bit
try to unplug - replug

I unpluged, and replugged about 5 times, each time it came up as an unknown device. I then unplugged it, shut it off, plugged it back in, then turned it back on, and it became a yellow triangle ADB.

Daniel_Fate said:
I unpluged, and replugged about 5 times, each time it came up as an unknown device. I then unplugged it, shut it off, plugged it back in, then turned it back on, and it became a yellow triangle ADB.
Click to expand...
Click to collapse
sounds not bad - let's test it:
you still have the command prompt open in c:\kfu\tools
issue the following command:
"fastboot -i 0x1949 getvar product" - it should return "kindle"

[SOLVED] a bit of HELP please...

Hello everyone.
I need a bit of help repairing my partitions on my Kindle.
To try and sum it up quickly, I am rooted, have FFF and TWRP installed. I decided to repartition my Kindle (using FireParted) to allow for more apps space. I did and everything went smooth. After installing some apps, I got a message saying my storage space was getting low. When I looked at the settings, I noticed that I had partioned my Kindle the wrong way. (Had more space for videos, music, pictures).
Sooo I decided to again repartition my Kindle once again using FireParted. Created a backup and let it do its thing. After 10 minutes I noticed the program still wasn't done and then it just stopped. Of course when I restarted it said that the partition couldn't be found. I tried restoring back up but it didn't find any. (wtf)
I then decided to try out the Unbrick utility but when I clicked on OTHER to see what other options were available, it immediately rebooted my Kindle and then I was stuck on the yellow triangle. I lost TWRP because I couldn't even boot into that. So I proceeded to uninstall/reinstall the drivers again. I ran the Kindle Fire Utility, it shows that I'm still rooted. Installed TWRP again and now I'm able to mount/unmount etc. but because my partion is all messed up. I'm unable to install a new ROM.
This is where I need help. I read about going into FASTBOOT mode with the KFU and then typing "fastboot oem format" but when I boot in FASTBOOT, I lose the TWRP and my computer/kfu/adb no longer recognizes the device. I tried entering the command through adb but I get a "'fastboot' is not recognized as a internal or external command".
So at this point I have no clue what to do or where to go. Any help would be appreciated.
Btw, I did look at this thread but it didn't help:
http://forum.xda-developers.com/showthread.php?t=1388996

sounds like you dont have fastboot.exe - issue the commands from the tools folder of kfu - there is fastboot.exe and all other commands you'll ever need

When I click on fastboot.exe from the tools folder of kfu, all it does is open and close right away nothing else. If I use the KFU to boot into fastboot it just gets stuck at activating fastboot but nothing happens.

to click it will not help you !
open an (elevated) command prompt and cd to the tools folder of kfu (ie "cd c:\kfu\tools")
now you can issue the suggested commands - ie "fastboot oem format"
if your drivers are ok the command should succeeed

b63 said:
to click it will not help you !
open an (elevated) command prompt and cd to the tools folder of kfu (ie "cd c:\kfu\tools")
now you can issue the suggested commands - ie "fastboot oem format"
if your drivers are ok the command should succeeed
Click to expand...
Click to collapse
Thanks for the help b63, I appreciate it.
I did what you said, elevated command prompt etc. Fastboot.exe worked correctly now. When I put "fastboot oem format" it just hangs on "waiting for device" but nothing ever happens. How long does this process normally take? It's been like 10 minutes now and no change. I don't know if the kindle is supposed to reboot or what. Right now it's on TWRP recovery...

ANDROID 3G said:
Thanks for the help b63, I appreciate it.
I did what you said, elevated command prompt etc. Fastboot.exe worked correctly now. When I put "fastboot oem format" it just hangs on "waiting for device" but nothing ever happens. How long does this process normally take? It's been like 10 minutes now and no change. I don't know if the kindle is supposed to reboot or what. Right now it's on TWRP recovery...
Click to expand...
Click to collapse
check your device manger - it's a driver issue
update the driver - the right one is "android adb interface"
if your driver is right there is another trick to try:
issue the command and let it sit on <waiting for device>
power down the kf by holding pwr button ~20sec - prw on again
the command should be picked up and finished

I had this problem when using FireParted as well. It causes problems on a stock ROM erasing partition 10 and 11. I was able to recover using the post you sent and have also my own instruction as well. http://forum.xda-developers.com/showthread.php?t=1453816
Hope this helps.

[Solved] Kindle Fire Bricked!! - stuck on yellow triangle/screwed up framework folder

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

Kindle fire stuck in boot screen after failed kfu attempt

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."