[Q] Kind Fire Bricked at Yellow Triangle....What Now??? - Kindle Fire Q&A, Help & Troubleshooting

So Ive read multiple threads from this forum and tried the suggested methods and nothing has worked at all. My Kindle Fire is stuck at the Yelllow triangle logo and I have no clue how to get it back working at this point. I originally rooted using BreakDroid using Clockwork recovery and was successful running the Energy ICS Rom.
I attempted to flash the Miui ICS Rom and thats where it went all bad and has been stuck at the Yellow Triangle ever since. I've tried to use the KFU 0.9.6 but my computer only recognizes the kindle as a "android phone" but doesn't see that's it plugged in. KFU states that it's waiting for device when trying to run any of the commands and I have reboot to get it to proceed but none of the commands work and only return me back to a frozen triangle screen everytime.
So I need some serious advise on how to start over and get my kindle fire back to stock and out of this dreadful yellow triangle screen thats haunting me! Please post any instructions based on your experiences or expertise.
Please Please Please Help!
Thanks in advance.....

Are you able to access recovery?

soupmagnet said:
Are you able to access recovery?
Click to expand...
Click to collapse
Nope not at all everytime I press the button and it turns orange nothing happens and it completely freezes and I have to reboot completely.

How comfortable are you with fastboot commands?

soupmagnet said:
How comfortable are you with fastboot commands?
Click to expand...
Click to collapse
Not the best but if you have some instructions I'm sure I can figure it out lol at this point I have no choice

You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.

soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I used the Kindle Fire Utility and did option #1 to boot normal mode but it didn't work but I'll these methods and post some feedback on it....thanks a lot

soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I understand all of that info but doesn't really lay out any steps to take to fix the issues I'm having. I'm not a newbie to rooting this is just the first time I've experienced this particular problem

Disregard

Thepooch said:
Disregard
Click to expand...
Click to collapse
Thanks for the positive advice

I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.

Thepooch said:
I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.
Click to expand...
Click to collapse
I actually got it fixed using breakdroid and thank god it worked but thanks for the advice I know exactly what not to do the next time

Had a similar problem brickoid sorted me
Sent from my i777 using xda
aokp on neak yo!

Related

[Q] Kindle with no OS

I have a kindle fire with no OS, it has TWRP recovery and I was trying to wipe android 4.0 from it and re install 6.2.2 but I accidentally deleted the OS and any hope of re installing it. I cannot communicate with the device whatsoever using kindle utility or Kindle fire unbricker. I played with the drivers for awhile in device manager to no avail. it currently sits in 'Disk Drives' as Amazon Kindle USB device but I cannot put anything on it because it it's showing up as a proper driver or w/e. when I turn it on I get what I believe is the firefirefire triangle and if I choose to I can access TWRP, but when I left it fully boot I get a black lighting. Any help is extremely appreciate. I did look around for a bit before posting my question and found nothing that fit my problem but if there is such a thread I'm sorry I posted an unnecessary one.
have you tried mounting your kindle in twrp if you can then just flash a new ROM and you should be good to go
Sent from my CM9 LG G2X using Tapatalk
I thought I already tried that but I went back and fiddle with a few settings and got access to my kindle, I went looking for the kindle 6.2.2 stock rom and couldn't find a download, I need to find a stock download because brother plans on selling this kindle, I'm only helping because I was the one who rooted and put android 4.0 on there.
TLR; Where can I get kindle fire stock rom at?
One does not simply delete an entire OS.... ;~;
http://forum.xda-developers.com/showthread.php?t=1399072
Bacondroid said:
One does not simply delete an entire OS.... ;~;
Click to expand...
Click to collapse
Lol one does simply delete an entire is. I made this same mistake and had to push a is to my kindle while in fastboot mode through adb. Took awhile for me to think of it but it finnally worked and I fixed it.
Sent from my Kindle Fire using Tapatalk
OK, My command prompt can't find my kindle fire as listed devices. I really need help! Plus, there is no exclamation point (!) all it lists is the Android ADB thing. How do I get it to find the device
threed42 said:
OK, My command prompt can't find my kindle fire as listed devices. I really need help! Plus, there is no exclamation point (!) all it lists is the Android ADB thing. How do I get it to find the device
Click to expand...
Click to collapse
This has literally nothing to do with the topic you posted in. Take a step back and do a little research before posting. You'll much likely be better off if you know what's going on.
I suggest you start here:
http://forum.xda-developers.com/showpost.php?p=25884555
soupmagnet said:
This has literally nothing to do with the topic you posted in. Take a step back and do a little research before posting. You'll much likely be better off if you know what's going on.
I suggest you start here:
http://forum.xda-developers.com/showpost.php?p=25884555
Click to expand...
Click to collapse
I mean, I got there, but there is no OS installed on my kindle fire
Okay, I realize I tend to come off a little "jerky" sometimes, but I really am trying to help. When you hijack a thread that's several months old and post a problem that seemingly has nothing to do with the OP, only to later reveal that there is much more to your problem (even after being suggested to do it differently), it makes other people that would normally be willing to help, think twice about getting involved. Nobody wants to have to ask 50 different questions to get to the root of the problem. You need to realize that the people who would help, probably don't want to do more work than absolutely necessary. And you should be respectful of that if you want some quality assistance from the people who might be able to solve your problem.
So once again, and respectfully, I suggest you click on the link I gave you, read it, do any suggested research and follow the directions given in the post.
Hey I'm having the same problem. I tried to root my kinble fire and accidentilly wiped the stockos off it but I have TWRP on the device, however I am not able to mount the device using twrp to put a ROM on the device to boot to. Any help getting the device to be recognized by the computer and mounting it would be a great help and any other info about installing a ROM to my kindle would also be a big help.
jgrun8732 said:
Hey I'm having the same problem. I tried to root my kinble fire and accidentilly wiped the stockos off it but I have TWRP on the device, however I am not able to mount the device using twrp to put a ROM on the device to boot to. Any help getting the device to be recognized by the computer and mounting it would be a great help and any other info about installing a ROM to my kindle would also be a big help.
Click to expand...
Click to collapse
[Edit:] Have you looked into SoupKit?
soupmagnet said:
[Edit:] Have you looked into SoupKit?
Click to expand...
Click to collapse
I actually figured everything out about 2 hours after my post. In order to get the Kindle recognized by my pc I had to change it over to USB composite device then I was able to load a ROM on it and I am now enjoying jelly bean 4.1 on the kindle now. I have not been able to restore the kindle os but I am assuming that if I look long enough for the kernal and firmware I will be able to restore it. Not that I have any plans to seeing as I have a dedicated android tablet now that does everything I want it and need to do anyways, I read on the kindle for like 3 months when it first came out, not worried about reading on it any more besides there's an app for it. Anyways thanks for the reply.
Hi, sorry if it is bad manners to post in threats months old but I am also having a similar problem with my kindle fire.
Today I spent hours rooting it and trying to get the google play store to work on it - all in a dangerously haphazard manner. It was really reckless of me.
Somewhere in the process I used KFU 0.9.9 after restoring to stock and re-rooting, then after a reboot the OS would't show up. it seemed like it loaded and everything but I couldn't see anything after it loaded past TWRP. I wiped system, and now am without an OS and only TWRP to use.
Some details:
Mounting works
Flashing stock is NOT WORKING. This is my main problem. I don't know any other method of restoring an OS; I do not know how sideloading with ADB works, or if that would help at all.
Much apologies in advanced for my juvenile-ty
thanks
DJLamontagneIII said:
have you tried mounting your kindle in twrp if you can then just flash a new ROM and you should be good to go
Sent from my CM9 LG G2X using Tapatalk
Click to expand...
Click to collapse
I count believe I was forgetting to mount Thanks
I know this thread is old and i apologize if this is the wrong place for me to post.
I'm in a similar situation, no os can access twrp and mount but my computer wants me to format. What can I do at this point?
thanks
iamchaos said:
I know this thread is old and i apologize if this is the wrong place for me to post.
I'm in a similar situation, no os can access twrp and mount but my computer wants me to format. What can I do at this point?
thanks
Click to expand...
Click to collapse
figured it out formatted and was able to load rom and flash.
Thanks
No idea What I need to do
I have a kindle fire with no OS, it has TWRP recovery and I was trying to wipe android 4.0 from it and re install 6.2.2 but I accidentally deleted the OS and any hope of re installing it. I cannot communicate with the device whatsoever using kindle utility or Kindle fire unbricker. I played with the drivers for awhile in device manager to no avail. it currently sits in 'Disk Drives' as Amazon Kindle USB device but I cannot put anything on it because it it's showing up as a proper driver or w/e. when I turn it on I get what I believe is the firefirefire triangle and if I choose to I can access TWRP, but when I left it fully boot I get a black lighting. Any help is extremely appreciate. I did look around for a bit before posting my question and found nothing that fit my problem but if there is such a thread I'm sorry I posted an unnecessary one.
Csnoopy35 said:
I have a kindle fire with no OS, it has TWRP recovery and I was trying to wipe android 4.0 from it and re install 6.2.2 but I accidentally deleted the OS and any hope of re installing it. I cannot communicate with the device whatsoever using kindle utility or Kindle fire unbricker. I played with the drivers for awhile in device manager to no avail. it currently sits in 'Disk Drives' as Amazon Kindle USB device but I cannot put anything on it because it it's showing up as a proper driver or w/e. when I turn it on I get what I believe is the firefirefire triangle and if I choose to I can access TWRP, but when I left it fully boot I get a black lighting. Any help is extremely appreciate. I did look around for a bit before posting my question and found nothing that fit my problem but if there is such a thread I'm sorry I posted an unnecessary one.
Click to expand...
Click to collapse
it's not broken, you have twrp,
don't use kfu or unbricker
what version of twrp?
Sent from my KFFOWI using XDA Labs
I have the newest version I think?
sd_shadow said:
it's not broken, you have twrp,
don't use kfu or unbricker
what version of twrp?
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse

Stuck in the orange boot loop and can't access ADB, TWRP or USB etc.

Now I'm in an even worse position to further prove my dopeyness. :crying: I installed CM10 and GAPPs in the root of my KF2. Went to do the wipes as instructed and then I couldn't get those files or access my KF2 via ADB or USB and I was stuck in TWRP with no OS. I couldn't do a sideload ADB through TWRP or Terminal Emulator since they couldn't find the device. FYI I successfully installed the drivers by restarting my Win8 computer and going through without signing drivers, but the device still wouldn't show up anywhere.
After that nightmare, I shut my KF2 down to do some work and then when I started it back up again, I was stuck in the dreaded orange Kindle Fire bootloop and I can't get into TWRP, ADB or anything else.
Any thoughts?
Re: I cannot get Boot Status 4000 in KFU and I can't install TWRP & I've tried EVERYT
KFU?
Do you have a Kindle Fire 2 (this is the kf2 forum)? KFU only works on the KF1.
Time to start reading. Too many people doing things like this lately..
Don't use ANYTHING made for the KF1 on the KF2!
--
Sent from my Kindle Fire 2, CM 10.1
mindmajick said:
KFU?
Do you have a Kindle Fire 2 (this is the kf2 forum)? KFU only works on the KF1.
Time to start reading. Too many people doing things like this lately..
Don't use ANYTHING made for the KF1 on the KF2!
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
Thanks!! I didn't realize. I also could swear that a KF2 thread lead me to KFU. Either way, what's the best method to get TWRP on my KF2. I love Jelly Beans. BTW I was able to install GAPPs with KFU without a problem. I just can't get a recovery on it.
I'm a dope. I installed the TweezerMod.apk and I have TWRP.
Thanks again for showing me the light. :good:
Re: I cannot get Boot Status 4000 in KFU and I can't install TWRP & I've tried EVERYT
jjdavola said:
I'm a dope. I installed the TweezerMod.apk and I have TWRP.
Thanks again for showing me the light. :good:
Click to expand...
Click to collapse
Lol. Glad to help. I was going to point you there next.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Now I'm in an even worse position to further prove my dopeyness. :crying: I installed CM10 and GAPPs in the root of my KF2. Went to do the wipes as instructed and then I couldn't get those files or access my KF2 via ADB or USB and I was stuck in TWRP with no OS. I couldn't do a sideload ADB through TWRP or Terminal Emulator since they couldn't find the device. FYI I successfully installed the drivers by restarting my Win8 computer and going through without signing drivers, but the device still wouldn't show up anywhere.
After that nightmare, I shut my KF2 down to do some work and then when I started it back up again, I was stuck in the dreaded orange Kindle Fire bootloop and I can't get into TWRP, ADB or anything else.
Any thoughts?
I change the OP accordingly.
Re: I cannot get Boot Status 4000 in KFU and I can't install TWRP & I've tried EVERYT
jjdavola said:
Now I'm in an even worse position to further prove my dopeyness. :crying: I installed CM10 and GAPPs in the root of my KF2. Went to do the wipes as instructed and then I couldn't get those files or access my KF2 via ADB or USB and I was stuck in TWRP with no OS. I couldn't do a sideload ADB through TWRP or Terminal Emulator since they couldn't find the device. FYI I successfully installed the drivers by restarting my Win8 computer and going through without signing drivers, but the device still wouldn't show up anywhere.
After that nightmare, I shut my KF2 down to do some work and then when I started it back up again, I was stuck in the dreaded orange Kindle Fire bootloop and I can't get into TWRP, ADB or anything else.
Any thoughts?
I change the OP accordingly.
Click to expand...
Click to collapse
Yes. If you don't have a fastboot cable.. Get one. You'll need it to restore back to stock.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Yes. If you don't have a fastboot cable.. Get one. You'll need it to restore back to stock.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I actually have two of the OEM cables. What do I need to do with them?
Thanks again!
jjdavola said:
I actually have two of the OEM cables. What do I need to do with them?
Thanks again!
Click to expand...
Click to collapse
Its a fast boot cable? Dude- you need to read like EVERYTHING in the dev section here. There is a thread on recovery.
http://forum.xda-developers.com/showthread.php?t=2035047
And here is a tool that can help:
http://forum.xda-developers.com/showthread.php?t=2096888
And PLEASE.. once you have recovered your device READ everything in the kf2 and kfhd forums. Use the xda app if that's easier, but read it all. I promise it'll help.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Its a fast boot cable? Dude- you need to read like EVERYTHING in the dev section here. There is a thread on recovery.
http://forum.xda-developers.com/showthread.php?t=2035047
And here is a tool that can help:
http://forum.xda-developers.com/showthread.php?t=2096888
And PLEASE.. once you have recovered your device READ everything in the kf2 and kfhd forums. Use the xda app if that's easier, but read it all. I promise it'll help.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
The original cables that came with the KF2 are not the same as fastboot cables? I thought I read that.
jjdavola said:
The original cables that came with the KF2 are not the same as fastboot cables? I thought I read that.
Click to expand...
Click to collapse
No. They are not.
Here is a legitimate source with fast shipping:
http://mobility.forumsee.com/a/m/s/p12-9168-063526--the-best-kindle-fire-factory-cable-period.html
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
No. They are not.
Here is a legitimate source with fast shipping:
http://mobility.forumsee.com/a/m/s/p12-9168-063526--the-best-kindle-fire-factory-cable-period.html
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I guess I'll order one.
Before I do that, is there anything else that can be done without getting the cable? Believe me, I searched and read everything I could find on the problem, but since I can't get into ADB or TWRP due to the lovely bootloop (and no OS), my options look very limited.
The super sad part is my KF2 was working great for around 1/2 hour, but I got greedy and wanted JB.
BTW if it might be my only hope, is there an easy way to disable Android SDK as pointed out in the First Aide thread since uninstalling seems like a pain?
Thanks again!
jjdavola said:
Thanks. I guess I'll order one.
Before I do that, is there anything else that can be done without getting the cable? Believe me, I searched and read everything I could find on the problem, but since I can't get into ADB or TWRP due to the lovely bootloop (and no OS), my options look very limited.
The super sad part is my KF2 was working great for around 1/2 hour, but I got greedy and wanted JB.
BTW if it might be my only hope, is there an easy way to disable Android SDK as pointed out in the First Aide thread since uninstalling seems like a pain?
Thanks again!
Click to expand...
Click to collapse
Your only choice left is to get the fastboot cable. No Adb, recovery OR ROM....
Not sure why you need to disable the SDK or what to do, since I've never used it on windows. I just use the files I need (adb and fastboot) and installed the drivers specific to this device. I've only used the SDK on Linux
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Your only choice left is to get the fastboot cable. No Adb, recovery OR ROM....
Not sure why you need to disable the SDK or what to do, since I've never used it on windows. I just use the files I need (adb and fastboot) and installed the drivers specific to this device. I've only used the SDK on Linux
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I figured, but I could dream. To quote the First Aide link you provided:
To keep your Kindle safe, we have integrated this feature into our software, You do not need any command line knowledge, just as simple as 1, 2, and 3.
Prerequisites for the Recover Options:
1. Install The Latest Version Of Java SE: Java SE Development Kit 7u13
2. Android SDK Must Be Disabled Or Removed
Click to expand...
Click to collapse
So are you saying I don't need to do that?
Thanks again for your help and patience. I really appreciate it.
jjdavola said:
Thanks. I figured, but I could dream. To quote the First Aide link you provided:
So are you saying I don't need to do that?
Thanks again for your help and patience. I really appreciate it.
Click to expand...
Click to collapse
I don't know. Ask in the thread. The OP likes to help and communicates way more clearly than me. I'm sure he can tell you how to disable or remove it.
--
Sent from my Kindle Fire 2, CM 10.1

[Q] Kindle fire wont work I cant install twrp no OS just Stuck at Kindle Fire Logo

The only thing I can do is get the device status to go online. It's recognizable on my computer devices. But I can't open it. Only right click. Iv tried fast boot. Iv tried installing twrp manually. But I always get stuck at waiting for device. When the Kindle reboots reconnects and disconnects and then reconnects. But all I see is the kindle fire logo. It can sit there for hours like that. Iv tried Soupkit. But that didn't work because it said the device was offline even it actually wasn't. Iv tried everything unless someone has an idea. It has no OS to boot to. So thats the reason. It must be. I void the warranty obviously by rooting. But I'm not here for admitting I did a stupid move of actually rooting when you dont know what your doing. If someone can leave a suggestion. I'd appreciate the suggestion. thanks
nobleman221 said:
The only thing I can do is get the device status to go online. It's recognizable on my computer devices. But I can't open it. Only right click. Iv tried fast boot. Iv tried installing twrp manually. But I always get stuck at waiting for device. When the Kindle reboots reconnects and disconnects and then reconnects. But all I see is the kindle fire logo. It can sit there for hours like that. Iv tried Soupkit. But that didn't work because it said the device was offline even it actually wasn't. Iv tried everything unless someone has an idea. It has no OS to boot to. So thats the reason. It must be. I void the warranty obviously by rooting. But I'm not here for admitting I did a stupid move of actually rooting when you dont know what your doing. If someone can leave a suggestion. I'd appreciate the suggestion. thanks
Click to expand...
Click to collapse
Does your Kindle Fire logo stay brightly lit or at any point does it flash and/or go dim?
soupmagnet said:
Does your Kindle Fire logo stay brightly lit or at any point does it flash and/or go dim?
Click to expand...
Click to collapse
brightly lit
nobleman221 said:
brightly lit
Click to expand...
Click to collapse
Okay, are you using a Linux VM, LiveUSB or full normal Linux install on your PC?
soupmagnet said:
Okay, are you using a Linux VM, LiveUSB or full normal Linux install on your PC?
Click to expand...
Click to collapse
full normal linux, Ubuntu 12.10`
nobleman221 said:
full normal linux, Ubuntu 12.10`
Click to expand...
Click to collapse
Are you using a USB 3.0 port?
soupmagnet said:
Are you using a USB 3.0 port?
Click to expand...
Click to collapse
Noob question how do you tell
nobleman221 said:
Noob question how do you tell
Click to expand...
Click to collapse
How old is your computer?
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
nobleman221 said:
Noob question how do you tell
Click to expand...
Click to collapse
If you have to ask then 99% likely you don't have one.
If you bought your computer in the last 6 months then maybe.
soupmagnet said:
How old is your computer?
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
Click to expand...
Click to collapse
Acer Aspire 5742. 3 years old.
nobleman221 said:
Acer Aspire 5742. 3 years old.
Click to expand...
Click to collapse
Nope. No way to possibly have a USB 3 port on that.
TheNetwork said:
Nope. No way to possibly have a USB 3 port on that.
Click to expand...
Click to collapse
So Is my kindle gone for good?
nobleman221 said:
So Is my kindle gone for good?
Click to expand...
Click to collapse
No. Did you follow the instructions I gave you previously?
soupmagnet said:
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
Click to expand...
Click to collapse
Ok, Im able to get the ADB device status to online in Soupkit. But where do I a start from exactly. do i got to bootmenu or what.
nobleman221 said:
Ok, Im able to get the ADB device status to online in Soupkit. But where do I a start from exactly. do i got to bootmenu or what.
Click to expand...
Click to collapse
Install menu > install TWRP...or COTR...your choice.
Sent from my Amazon Kindle Fire using Tapatalk 2
The kindle status is online. Should the kindle be off or not. Also when I run twrp install on the terminal. Its running nothing but words. How long does this take. Also do I need WiFi while doing this.
Sent from my EVO using xda app-developers app
nobleman221 said:
The kindle status is online. Should the kindle be off or not. Also when I run twrp install on the terminal. Its running nothing but words. How long does this take. Also do I need WiFi while doing this.
Click to expand...
Click to collapse
"It's running nothing but words." Hmm...interesting.
You have to understand that I cannot see your device and I definitely can't see these "words" you're talking about. I have no idea what you've done and you still haven't told me whether you understood the instructions I gave you to install FFF or whether or not you succeeded in doing so. So unless you are able to provide me some usable information, we're just going to go around in circles here.
Aside from that, ADB is not going to do you any good until you get TWRP installed. You won't get TWRP installed until you follow the instructions I gave you to get FireFireFire installed. In case you missed it...for the second time...I'll try to explain it a little better.
If you had read the SoupKit thread, you would find that the stock bootloader doesn't work like it should in regards to accepting fastboot commands. The command "fastboot devices" doesn't work, so the SoupKit, will always say "Device Offline". Other fastboot commands will work, but you have to enter the command, turn the device off (hold power button for 10 seconds), then turn it back on. I also explained in the SoupKit thread (and here...twice), that if you have the stock bootloader installed and you get "Device Offline", to choose an option anyway and follow the instructions it gives you (which will be to turn the device off, then back on, etc).
Now, considering you have not given me any information regarding the success or failure of those instructions, I'll have to assume you either didn't read or you didn't understand them. That being said, let's go back and try it again.
soupmagnet said:
"It's running nothing but words." Hmm...interesting.
You have to understand that I cannot see your device and I definitely can't see these "words" you're talking about. I have no idea what you've done and you still haven't told me whether you understood the instructions I gave you to install FFF or whether or not you succeeded in doing so. So unless you are able to provide me some usable information, we're just going to go around in circles here.
Aside from that, ADB is not going to do you any good until you get TWRP installed. You won't get TWRP installed until you follow the instructions I gave you to get FireFireFire installed. In case you missed it...for the second time...I'll try to explain it a little better.
If you had read the SoupKit thread, you would find that the stock bootloader doesn't work like it should in regards to accepting fastboot commands. The command "fastboot devices" doesn't work, so the SoupKit, will always say "Device Offline". Other fastboot commands will work, but you have to enter the command, turn the device off (hold power button for 10 seconds), then turn it back on. I also explained in the SoupKit thread (and here...twice), that if you have the stock bootloader installed and you get "Device Offline", to choose an option anyway and follow the instructions it gives you (which will be to turn the device off, then back on, etc).
Now, considering you have not given me any information regarding the success or failure of those instructions, I'll have to assume you either didn't read or you didn't understand them. That being said, let's go back and try it again.
Click to expand...
Click to collapse
i did read the instructions. But the terminal runs a bunch of commands rapidly so fast I cant read it. I have my WiFi turned on and when I enter the command to install TWRP the terminal window just runs and that's the end of it, it runs in an endless loop jumbled words. My Kindle fire connects making 3 connect/disconnect sounds when plugged in my computer. And Still is stuck at the boot logo with no signs of change.
nobleman221 said:
i did read the instructions. But the terminal runs a bunch of commands rapidly so fast I cant read it. I have my WiFi turned on and when I enter the command to install TWRP the terminal window just runs and that's the end of it, it runs in an endless loop jumbled words. My Kindle fire connects making 3 connect/disconnect sounds when plugged in my computer. And Still is stuck at the boot logo with no signs of change.
Click to expand...
Click to collapse
You can scroll up through the terminal to get the outputs of the previous commands. Regardless, if you ran the option to install FireFireFire, it would sit at "waiting for device" until you shut the device down and turn it back on.
soupmagnet said:
You can scroll up through the terminal to get the outputs of the previous commands. Regardless, if you ran the option to install FireFireFire, it would sit at "waiting for device" until you shut the device down and turn it back on.
Click to expand...
Click to collapse
"Your shell is either missing or corrupt shell making it impossible to change from the inside of the system your \nshell must be installed properly before you can proceed any further, the only way to do this is firefirefire." Is what was being spammed in the terminal. I couldent copy and paste the the thing because everytime I clicked inside the terminal the instructions dissappeared.

Kindle Fire 2nd gen - red triangle; cannot boot

Hello everyone...
I've been reading all the threads on this forum for a few months, but I couldn't find an concrete and final answer to this problem:
I have a Kindle Fire 7'' 2nd Generation, and after rooting and installing ICS ( with KF First Aide) i noticed that my wallpaper was flashing and the notification bar was disappearing. I tried to fix it but suddenly the RED TRIANGLE ( with exclamation point inside) appeared and looks like this:
( the triangle)
"Your Kindle device cannot boot.
You can reset your device to Factory defaults to fix this issue (all data will be deleted from the device).
<Menu options>
To reboot your device press and hold the power button for 4 seconds and release.
To reset to Factory Defaults, press the power button 5 times in succession"
None of those options work, and when I connect the USB cable to my PC nothing happens.
Is there someone who knows how can I fix it, but please... explain from the scratch because I am a total beginner. ( I rooted it only by following instructions for noobs, step by step)
I would be very thankful.
BTW I don't have a Factory Cable and if I have to buy one it would take about 40 days, and if it is possible to make one- I also don't know how.
You will need a fastboot/factory cable, here's a life o on how to make one, there's one on this forum as well but I knew where this was listed in the FAQs thread here so I used it. http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Why would buying a cable take 40 days? I bought one off ebay for £3 and had it within 2 days. It was easier than making my own, and i have a soldering iron.
Sent from my LG-D802 using Tapatalk
chronicfathead said:
Why would buying a cable take 40 days? I bought one off ebay for £3 and had it within 2 days. It was easier than making my own, and i have a soldering iron.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Only one sent from China could possibly take that long. Not sure what you're getting at...
LinearEquation said:
Only one sent from China could possibly take that long. Not sure what you're getting at...
Click to expand...
Click to collapse
Buying one should be quick and easy. You only have to look in the forum to see lots of posts of people struggling with the KF2, and how often a Factory Cable is required.
It should be a recommendation that you get the cable before doing anything.
Sent from my LG-D802 using Tapatalk
chronicfathead said:
Buying one should be quick and easy. You only have to look in the forum to see lots of posts of people struggling with the KF2, and how often a Factory Cable is required.
It should be a recommendation that you get the cable before doing anything.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Actually the tutorials for 2nd bootloader/TWRP for Kindle's of all kinds do suggest that you grt a fastboot cord. Show me one that does not. It falls on the person doing the modding to go ahead and read and maybe do a little bit of research first don't you think?
Edit: The problem is some tutorials failed to update when the firmware was patched creating many bootloops if the firmware was not downgraded to 7.2.3 or 7.3.0 first. Still warnings always exhisted to backup and get a fastboot cord.
How to root
LinearEquation said:
Actually the tutorials for 2nd bootloader/TWRP for Kindle's of all kinds do suggest that you grt a fastboot cord. Show me one that does not. It falls on the person doing the modding to go ahead and read and maybe do a little bit of research first don't you think?
Edit: The problem is some tutorials failed to update when the firmware was patched creating many bootloops if the firmware was not downgraded to 7.2.3 or 7.3.0 first. Still warnings always exhisted to backup and get a fastboot cord.
Click to expand...
Click to collapse
Hey, thanks for the advice
I recovered ( unbricked) my Kinde 2gen and it's working now.. but how can I root it now and instal ICS or JB on it?
I did it once on the same device using KF First Aide ( the one with 45 options) but now it cannot gain root access... why?
So:
1. How to gain root access?
2. How to instal android ICS or Jelly Bean on it, but with noobs description please
Thank you
idam_cuco said:
Hey, thanks for the advice
I recovered ( unbricked) my Kinde 2gen and it's working now.. but how can I root it now and instal ICS or JB on it?
I did it once on the same device using KF First Aide ( the one with 45 options) but now it cannot gain root access... why?
So:
1. How to gain root access?
2. How to instal android ICS or Jelly Bean on it, but with noobs description please
Thank you
Click to expand...
Click to collapse
Glad your tablet is working.
So first you want to go here http://forum.xda-developers.com/showthread.php?t=1886460 and download "Root_with_Restore_by_Bin4ry_v31: [Improved Root-Method by Ariel Berkman]" There is a of stuff in that post but v31 was an update to the OP so trust that it is correct. You will download and run the bat and root your KF2.
Now to get a custom ROM you first need to install a 2nd bootloader and TWRP (Team Win Recovery Project) The best thing you can do is read and ask if needed so you don't brick your Kindle.
Here is Hashcodes thread on how to install a 2nd bootloader and TWRP http://forum.xda-developers.com/showthread.php?t=2100963
Here is Hascodes thread on getting the custom ROM put on your KF2 using ADB commands http://forum.xda-developers.com/showthread.php?t=2100963
Here is a list of custom ROM's for KF2 http://forum.xda-developers.com/showthread.php?t=2462878
Make sure to not use anything not intended specifically for the Kindle Fire 2 (otter) or you may hard brick your Kindle.
idam_cuco said:
Hey, thanks for the advice
I recovered ( unbricked) my Kinde 2gen and it's working now.. but how can I root it now and instal ICS or JB on it?
I did it once on the same device using KF First Aide ( the one with 45 options) but now it cannot gain root access... why?
So:
1. How to gain root access?
2. How to instal android ICS or Jelly Bean on it, but with noobs description please
Thank you
Click to expand...
Click to collapse
Can you post on how you got it unbricked from the screen you were talking about. I have the same problem but can't seem to fix it. Thanks if you could do that.
crt2389 said:
Can you post on how you got it unbricked from the screen you were talking about. I have the same problem but can't seem to fix it. Thanks if you could do that.
Click to expand...
Click to collapse
Plug your fastboot cable in. Then run the KFFirstAide.
And to all you toilers, first you flash 10.2.4 bootloader, and then boot up and install the Alien Box (Tweezermod), and then you get second bootloader. Instructions to thank Hashcode or FMkilo (or whichever the guy is).
crt2389 said:
Can you post on how you got it unbricked from the screen you were talking about. I have the same problem but can't seem to fix it. Thanks if you could do that.
Click to expand...
Click to collapse
Hey, sorry for the late reply...
Well first install the KFFirstAide ( the program with 40+ options ). You can find it easy here.
Now, you need to have factory cable. Turn off your Kindle, plug the factory cable and turn the Kindle On. You should see your Kindle in Fastboot status now, showing green and red light circles.
Next, start the KFFirstAide and run option 1 or 2, and when you get to the question "would you like us to switch your Kindle into Fastboot status" you should answer NO, because you already are into fastboot.
Then, just let the program do it's magic and you'll have your Kindle in it's original version of Android ( the Amazon version).
I hope this helps, let me know what you did
Cheers!
Waiting for device
idam_cuco said:
Hey, sorry for the late reply...
Well first install the KFFirstAide ( the program with 40+ options ). You can find it easy here.
Now, you need to have factory cable. Turn off your Kindle, plug the factory cable and turn the Kindle On. You should see your Kindle in Fastboot status now, showing green and red light circles.
Next, start the KFFirstAide and run option 1 or 2, and when you get to the question "would you like us to switch your Kindle into Fastboot status" you should answer NO, because you already are into fastboot.
Then, just let the program do it's magic and you'll have your Kindle in it's original version of Android ( the Amazon version).
I hope this helps, let me know what you did
Cheers!
Click to expand...
Click to collapse
I did exactly what you said and was stuck at <waiting for device> ???????
rohanlad8 said:
I did exactly what you said and was stuck at <waiting for device> ???????
Click to expand...
Click to collapse
It's a pain in the ass sometimes...
When you connect it with the factory cable, does it show the Fastboot on the screen? If yes, make sure you answer the questions correctly from the KF First Aide program, for example if it asks you do you have the Kindle Fire 2 gen?
But if it cannot recognize the device at all and it shows "waiting for device" for the whole time, I really don't know what can you do, except disconnect and connect again...
Maybe you could send me photos of how it looks the screen after every step you make including the questions when you run the KF First Aide?
You can send it to my mail: [email protected] | no tricks, just wanna try to help |
I had that problem and I know how awful it is
Good luck!

Think I killed my fire TV

I followed the AFTV guide to a T. Flashed 51.1.4.0, had the boot menu, CWM and everything was golden. Pushed 51.1.5.3 to the SD, rebooted to CWM, flashed, now stuck in a loop. I cant even connect to it with the adb connect command. Am I screwed? Is this thing done? I dont understand. It doesnt even show the boot menu anymore. Just straight to the looping firetv logo. Was i supposed to reflash the boot menu after installing prerooted 51.1.4.0? This sucks if it's done for.....
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Calibaan said:
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks man. Hopefully one of those methods works. I've been at this for 4 hours carefully working my way through every single step. The highest high of the one last flash to go, turning into the gut wrenching sickness of a boot loop is too much for tonight and I'll try tomorrow.
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
supremekizzle said:
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
Click to expand...
Click to collapse
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
AFTVnews.com said:
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
Click to expand...
Click to collapse
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
supremekizzle said:
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
Click to expand...
Click to collapse
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
AFTVnews.com said:
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
Click to expand...
Click to collapse
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
supremekizzle said:
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
Click to expand...
Click to collapse
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
AFTVnews.com said:
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
Click to expand...
Click to collapse
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
supremekizzle said:
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
Click to expand...
Click to collapse
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
supremekizzle said:
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
Click to expand...
Click to collapse
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
AFTVnews.com said:
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
Click to expand...
Click to collapse
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
supremekizzle said:
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
Click to expand...
Click to collapse
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
Any suggestions?:
http://forum.xda-developers.com/fire-tv/help/fire-tv-boots-white-amazon-logo-screen-t3139511
supremekizzle,
Glad it worked out for you.:good:
supremekizzle said:
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
Click to expand...
Click to collapse
Glad it all worked out and glad I could help!
For future reference, when you edit a post, it doesn;t trigger XDA to send out a notification to the user you're quoting (me). That's why I didn't respond to your last message until now (when I manually checked it). Post a reply and use the '@' symbol (like this: @supremekizzle ) to ensure the user gets notified.

Categories

Resources