[Solved] Stuck at Yellow Fire Triangle ***Ubuntu*** - Kindle Fire General

Hey guys I rooted my Kindle Fire with no problems.
Then I went on to what you guys know will follow after a root.
Flashing a custom recovery so that I can install a rom.
Well I followed this guide here:
http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
Yes I had the recovery in the same folder etc...
After I typed the following:
adb shell
idme bootmode 4002
exit
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
I got stuck at the Yellow Fire Triangle
I pulled open the case and unplugged the battery.
Even after that it boots right into the Fire Triangle.
I am using Ubuntu Linux.
Can anyone help me get out of this situation. Or does anyone know what I did wrong?
I herd about the kindle fire utility but im running Ubuntu not windows.
thanks guys

roketteere said:
Hey guys I rooted my Kindle Fire with no problems.
Then I went on to what you guys know will follow after a root.
Flashing a custom recovery so that I can install a rom.
Well I followed this guide here:
http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
Yes I had the recovery in the same folder etc...
After I typed the following:
adb shell
idme bootmode 4002
exit
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
I got stuck at the Yellow Fire Triangle
I pulled open the case and unplugged the battery.
Even after that it boots right into the Fire Triangle.
I am using Ubuntu Linux.
Can anyone help me get out of this situation. Or does anyone know what I did wrong?
I herd about the kindle fire utility but im running Ubuntu not windows.
thanks guys
Click to expand...
Click to collapse
Plug it in and type
Fastboot oem idme bootmode 4000
Sent from my HTC Sensation XE with Beats Audio using XDA

It says <waiting for device>
And nothing happens

I don't know if it helps but before it booted into that mode the vendor id on the usb was 1949.
Now the vedor id is 18D1
I'm not sure if that helps but that's what I have.
Thanks

Try running fastboot as root.

issue "fastboot oem idme bootmode 4000"
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal

I got it working last night. The problem was that it did flash a recovery it just wouldn't boot into recovery for some reason. I kept click and holding the power button until it finally rebooted into normal mode.
Then Instead of using twrp recovery I flashed cwm and installed ICS.
Thank you all for helping me.
Sent from my iPhone 4 on Straight Talk using Tapatalk

glad that you got it working ...
please mark the subject of the topic (edit first post) with [Solved]

There done.
Thank u again for the help peops
Sent from my iPhone 4 on Straight Talk using Tapatalk

Related

Unbricking Kindle stuck at Boot Logo/Recovery loop

Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
What is firefirefire? Have yet to see a formal definition of that
androidcues said:
What is firefirefire? Have yet to see a formal definition of that
Click to expand...
Click to collapse
Its a bootloader
Sent from my Kindle Fire using xda premium
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Tierehl said:
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Click to expand...
Click to collapse
Happy to help
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
Unfortunately this will only work if your windows based computer even recognizes the kindle, which mine doesn't. Thanks tho. I've given mine to my tech geek who has access to linux based system, so hopefully he will be able to recover my brick.
Sent from my MB860 using XDA App
Sorry about that. I wish I could help.
I am a newbie. I recover my kf using the recovery boot with kfu and it works fine now. how could
I know if it is in the recovery boot loop? Many thanks.
Sent from my GT-I9100 using XDA App
Zombiepiratez said:
Sorry about that. I wish I could help.
Click to expand...
Click to collapse
Its ok. I read everywhere its impossible to brick a kindle so im hoping that's true.
Sent from my MB860 using XDA App
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
*Snip*
Double post, fail.
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Tried that to no avail as well.
Sent from my MB860 using XDA App
Zombiepiratez said:
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
Click to expand...
Click to collapse
I guess I should make note that by this point I'd uninstalled the driver I used. It was recognized as "kindle" once after I plugged it in while off, so then I went ahead and manually reinstalled the driver (from Jayce Ooi's site), which allowed the fastboot commands to work. Otherwise, the command would hang at <waiting for device>.
Thanks! My kindle fire was stuck at the firefirefire logo. My computer couldn't even recognize my kindle but I uninstalled the Android ADB composite interface and plugged it back in, when the kindle was off. Then I used your commands to get fastboot. I installed TWRP, now I'm stuck in TWRP and can't mount my sd... to flash any rom.
Thanks
Thanks for the info. i thought i'd bricked it and the info worked a treat. that will teach me to keep my mouth shut "of course i can root your kindle"
try fixing permissions under advanced, and then make sure only the sdcard box is marked in mount option.
Sent from my Amazon Kindle Fire using xda premium
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
jamesphan said:
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
Click to expand...
Click to collapse
The Unbrick utility won't help in your case. When the device hangs at the boot animation or goes to a blank screen afterwards, the problem is usually one of three things.
* the rom installed is corrupted
* you didn't wipe the necessary data before installing
* you tried flashing a rom that's incompatible with the recovery you are using (I'm betting this is most likely the case)
Try installing a different rom (preferably non-ICS) to see if that fixes the problem. Of so, check to see if you're using the latest version of CWM by Hashcode or install TWRP to run ICS based roms.
Any further questions regarding this matter should be redirected to the Q&A section.
[Edit:] For some reason I thought this was the thread for the Unbrick Utility. Regardless, the solution is still the same.
You are a GENIOUS!!!
Thanks a LOT!!!!!!!!!!

[Q] Bootloop in TWRP + bricked device...

I just overall screwed up big time with this thing. I rooted 6.2.1, then uninstalled/froze a bunch of the stock apps (including the default Kindle launcher, as I had Go Launcher installed).
I then decided I wanted to restore to the factory default settings, as I wanted to use Amazon prime, among other things. I went into settings and hit the "restore to factory defaults button" (which was stupid, I know). Unsurprisingly, this resulted in Kindle Fire bootloops.
Trying to fix this, I used the KindleFireTool to install the most recent TWRP...which didn't work at all. It would just stay on the yellow triangle screen. Now, things have gotten even worse, though I don't know why. Whenever I plug the fire into the computer, it goes into TWRP bootloops!
For the brief few seconds that the Fire is on when plugged into my computer, the driver isn't recognized at all (shows up as "kindle" with a triangle next to it in device manager).
I know what I did was dumb, but even so, any help would be hugely appreciated.
YES YES YES!!!! OK HERES HOW I DID IT TO FIX THE BOOTLOOP OF TWRP
First you must download Kindle Fire Utility and extract it to your desktop
then go to command prompt or cmd then type in the location of the folder heres mine for example: C:\Users\Madaran\Desktop\Kindle Fire Utility\tools
then type in fastboot -i 0x1949 oem idme bootmode 4000
For me it said waiting for device all I did is rebooted the device and it worked
as the device reboot it will still go back to TWRP now type this in the command prompt
fastboot -i 0x1949 oem idme bootmode 4000
then it should reboot again and ITS FIXED
----------------------------------
I used this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=1428715
Thank you so much! I'll post results when I get the opportunity.
Well it didn't work...the thing isn't connecting to the computer properly. I think it's a goner.
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
skippwhy said:
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
Click to expand...
Click to collapse
It maybe your battery its low. Try to charge it and connect it again.
Definitely worth a shot
You were right! It was a battery issue
sirmavs said:
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
Click to expand...
Click to collapse
Hey guys... I kinda bricked my Kindle... I tried all the steps mentioned above. My Kindle boots but it freezes on the Kindle Fire Boot Screen. It does not load the home screen of Kindle with Shelf.
Please help
http://forum.xda-developers.com/showthread.php?t=1428428

TWRP and CM7 problem

I just did a restore setting in the CM7 option after that I cannot boot into the CM7 but only the TWRP...
Can anyone tell me how to reinstall the TWRP...
I tried to use the kindle fire utility to re-install it, however it doesn't connect...
always shows offline..
please help
thanks
Did you restore bootloader, recovery and system from your backup using TWRP? If so you should have TWRP installed.
Please provide detail info what you have done to give further help.
You may need to update your USB diver to get adb working and to be able to install recovery software.
Sent from my Amazon Kindle Fire using Tapatalk
i think you said boot to recovery in cm7 - now you'r in a recovery bootloop - means it boots allways to recovery by itself - right ?
if so (if it is booted to twrp) use kfu option1 - bootmode normal
or issue manually:
adb shell idme bootmode 4000
adb reboot
an other method is to use fastboot commands:
fastboot oem idme bootmode 4000
fastboot reboot
in the case it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if commands don't work check your drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Can anyone tell me what the befits are to running cm7 vs a lunched like adw ion the fire?

[Q] Got stucked on KF Start Screen. [solved]

Hi,
i am searching this forum for about 5-6 hours without finding a solution for my problem.
My KF is stucked on "kindle fire" start screen (it blinks) after i made a bad misstake by editing the account.db . I wanted to add a second google account to my new installed market.
But after that it is stucked.
I tried the kfu 0.9.3 but no matter what i do, i get an error with "operation not permitted" or "Could not access the Package Manager. Is the system runnung?"
[edit]Everytime i try to enter su at adb shell, i got this message "[1] + Stopped (signal) su"[/edit]
My driver seem to work.
And i dont know what i did, after some utility uses i got this yellow triangle and it stucked first. But now it continued again to the blinking kindle fire logo.
Can somebody please help me? I realy dont know what to do.
And i am sorry for my bad english :/ .
Thank you.
Have you tried going into recovery?
Sent from my Kindle Fire using xda premium
Issue the following commands to reboot to normal
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Sent from my Amazon Kindle Fire using Tapatalk
Hey, thanks for the answer.
I was able to get twrp running with this post:
b63 said:
hey cool - thought the shell is messed up - it's not - you can get to fastboot - great
would suggest to follow this thread starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
and your allready downloaded twrp is recovery.img not twrp-blaze-2.0.0RC0.img
simply adapt the corresponding command in the above thread
is you want stock rom i would suggest to use a prerooted stock rom (i prefer the unsecure version):
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
Click to expand...
Click to collapse
Now i tried to install a rom, but i am not sure it worked. Because the kf is starting for over 10 min now and just showing this "kindle fire" logo. Do you or anybody has got a link for the original 6.2.2 or maybe with google play? I have got the problem that the roms i downloaded dont have a md5 file and that discription i used said i have to activate md5 check.
Thank you.
P.S. How long do i have to wait until i can be sure it wont start? And do i realy have to command "adb shell idme bootmode 4000" and "adb reboot" after flashing? Or can i just click on reboot?
Check the check sum md5 before you install.
It looks like the KF is booting into fastboot mode. You need to issue the mentioned commands to boot normal either before or after you install a new ROM. First you to boot to normal and find the ROM you like to install. As you know, use TWRP to install a new ROM.
Sent from my Amazon Kindle Fire using Tapatalk
Guys, thank you. Its alive..again .
I just found a rom that worked .
Its is 5 am and i rly have to sleep now..what a night -.- .
Again, thanks for your help.
just for info:
had a case where a prerooted stock rom needed 20min for first boot
so be patient ...
please mark the subject of the topic (edit first post) with [Solved]

Kindle Fire automatically loads to CWM and won't load past it?

I finally managed to unbrick my KF and reroot it a few weeks ago only for amazon to come out with 6.2.3 or whatever the new version is and of course it unrooted it.
I have a MacBook Pro so I decided to use BreakDroid to reroot my KF.
Well in the process of doing so it installed CWM which has turned into a total monster.
Now my KF will only load to either the Yellow Triangle screen or the CWM-based Recovery menu screen. I keep trying to boot it out of that mode by using
cd /Users/macuser/android-sdk-macosx/tools
./fastboot-mac -i 0x1949 oem idme bootmode 5002
but that just seems to take me to the red CWM menu screen.
Does anybody know how I can get CWM off of my KF for GOOD?
I swear if I see that red menu or that yellow triangle again I'm going to throw it across the room.
Help a girl out?
To change to normal boot, use 4000 or use the following fast boot commands:
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk
Didn't Work
I tried that...it didn't work either. It just brought me back to that stupid yellow triangle.
Since you have cwm, restore your backup or flash your desirable ROM.
Sent from my Amazon Kindle Fire using Tapatalk
=D
You know I actually decided to do that on my own before I read your post and it totally worked! Thank you for giving me the advice though.
I am glad you got your KF working
Sent from my Amazon Kindle Fire using Tapatalk
I tried this but it didn't seem to work for me.
One problem is when I renamed the update to "update.zip" it doesnt show up as a file I can install in TWRP. However, when I actually .zip the update then it shows up.
I used install and it says "installing" with a progress bar, but when I reboot it goes right back into TWRP recovery mode.
My kindle is fully accessible through Kindle Fire Utility, but it will only stay in recovery mode, If I try to put it back into normal mode it gives a message "The system cannot find the drive specified".
I think at some point I deleted the system files using TWRP assuming I could just flash them back. I'm guessing I was wrong at this point.
Any help would be appreciated.
all u had to do, was tap reboot system on cwm. its not twrp, it ain't broken. no adb boot mode changes. just reboot lol
Sent from my HTC Glacier using xda premium

Categories

Resources