Got the triangle screen and following instructions in guides are not fixing it. Heres my scenario. I got my kindle with 6.2 on it. Got it rooted, installed market and go launcher and was great. Then the update of course came thru and broke root. Still been able to download market apps and use go launcher. So I followed this guide
http://forum.xda-developers.com/showthread.php?t=1417284
to regain root and install twrp. It says root is successful, but superuser force closes everytime trying to open or use it. I can open my tibu and root explorer and everything still gave me root access. Went and changed the MarketIntentProxy.apk to MarketIntentProxy.apk.bak so market links go to market by default. That worked. Noticed that all amazon apps downloaded have a default amazon icon. Thought nothing of it. Went to install twrp anyway. Stuck at triangle now. Followed all instructions to fix and the KFU keeps flashing error device not found constantly and boot status unknown. Not showing up in my devices but I can eject via the safely remove hardware program. What happened? Did everything as guide states and watched the videos as I was doing each step.
you have to update the drivers by right click in device manager (some have to this up to 4 times)
to change the bootmode you can use kfu or do it manually:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
this is also sometimes helpful:
power down kf by longpress the powerbutton then replug it without powering on before - will do it by itself
then i would suggest to reroot with kfu but take care - if you allready have burritoroot on your device you have to delete it before retrying
b63 said:
you have to update the drivers by right click in device manager (some have to this up to 4 times)
to change the bootmode you can use kfu or do it manually:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
this is also sometimes helpful:
power down kf by longpress the powerbutton then replug it without powering on before - will do it by itself
then i would suggest to reroot with kfu but take care - if you allready have burritoroot on your device you have to delete it before retrying
Click to expand...
Click to collapse
I can't update driver any longer because it doesn't show in my devices. I will try the adb method since I can't install fastboot.
Sent from my MB860 using XDA App
pre4speed said:
I can't update driver any longer because it doesn't show in my devices. I will try the adb method since I can't install fastboot.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
maybe this helps:
power down kf (long press pwr) disconnect
http://support.microsoft.com/kb/315539/en-us
remove all regarding adb & kindle & restart comp
then reconnect without powering on - will do itself
b63 said:
maybe this helps:
power down kf (long press pwr) disconnect
http://support.microsoft.com/kb/315539/en-us
remove all regarding adb & kindle & restart comp
then reconnect without powering on - will do itself
Click to expand...
Click to collapse
No that did not work either. I have let my tech geek who has a linux based system try to unbrick it. Hopefully he can get his system to talk to the kindle since my windows cant. Thanks for trying to help.
Sent from my MB860 using XDA App
pre4speed said:
No that did not work either. I have let my tech geek who has a linux based system try to unbrick it. Hopefully he can get his system to talk to the kindle since my windows cant. Thanks for trying to help.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=1428428
Related
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!!!!!!!!!!
I successfully rooted my fire using Burritoroot 3. After it was rooted I clicked Flash FireFireFire, then hit deny....which Apparently I shouldn't have done. The Fire worked fine until it was turned off. Once it was rebooted, it just sticks at the "Kindle Fire" screen.
While I was stuck at the Kindle Fire screen, I deleted the Fire ADB Composite Drivers and tried to reinstall them. Now I cannot get them to install. When I plug the Fire into my computer, it shows up in the device manager as Android ADB Interface. I then uninstalled the drivers, to try to reload the drivers for the Composite Interface, which never worked. I can uninstall the Android ADB Interface, then the Kindle shows up under USB Controllers as an unknown device. it never gets listed as a kindle fire, always unknow devices. The only way I can get it to show up again is to open up the Kindle Fire Utility folder and open the Install Drivers.bat and run it. Then turn the Kindle off, then back on. Thats the only way I can get the Kindle to show up in the device manager under Android ADB Interface.
Also, I guess because I cannot get the Android ADB Composite Interface, I can't get it to show up as an attached device when using the "adb devices" command.
I assume it has to do with the boot (duh). Any ideas? I am a developer for Apple, and this is my first experience with rooting anything android, as you can probably tell. Any help is appreciated. TIA
Mike
Try to get KFU to recognize it.. then tell it to reboot in normal mode. It seems like you are stuck in fast boot to me.
if you have access to an Android phone, connect to your computer to retire the Android composite driver.
If not reinstall the sdk.
Sent from my Amazon Kindle Fire using Tapatalk
It looks like you want to root manually but KindleFireUtility will help you out of this conundrum. You can reinstall the drivers, root, and flash TWRP after you go back to normal bootmode
your kf is in fastboot mode - that means:
- it is using "android adb interface" -> not composite -> your driver is correct !
- it don't respond to adb commands -> only fastboot commands
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
Thanks a lot, using fast boot and changing the boot mode to 4000 fixed the problem.
MIke
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
my kindle fire is stuck on the Kindle Fire screen, with no animation.
i have looked through XDA but could not find anything with my problem.
i do not have TWRP or FFF.
I'm running the stock rom.
kindle is not recognized on ADB.
i uninstalled the driver, but now computer management doesn't have anything for the device listed.
i used the kindle fire utility to install the drivers, still not listed on computer management.
it is recognized in the bottom right as plugged in as a 'android adb interface'
i have tried using the kindle unbrick utility, but it says there is no device plugged in.
EDIT:
i restarted my computer. now the kindle is listed as unknown device in the bottom right and in computer management.
i am still unable to install new driver software on it, though.
EDIT:
I tried using the driver from the .android download, it says that it's not going to work.
if someone could help me, please, it would be great.
EDIT::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPDATE TO THE PROBLEM::::
the kindle is still in the kindle fire boot screen brick.
it went from being an 'unidentified device' to being 'android adb interface'
the error code has switched from code 43 to code 10.
it says Device Cannot start (code 10)
it is not recognized by ADB
unbrick utility still doesn't recognize.
neither does kindle fire utitlity.
look above
look above
look above
can someone please help me..
im having the same problem and cant find an answer anywhere we need help guys
maybe this helps:
for the kfu drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
Click to expand...
Click to collapse
that means:
your kf seems to be in fastboot mode -> adb commands not working
the question is what have you done to come to this situation ?
you can:
- try to switch to normal bootmode
- or try to install fff & twrp (this is done in fastboot mode)
switch to normal boot:
use kfu option 1 - bootmode normal or manually (see above)
when it says <waiting for device> power off the kf by holding the pwr button for ~20sec till it turns off - pwr on again - the command should be resumed and finished - another pwr off/on should bring you back
install fff & twrp:
refer to this post http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
if you can't get rid of the windows drivers:
http://forum.xda-developers.com/showthread.php?t=1430038
Thanks so much I was having this same problem and have been bashing my head against the wall all day. This kind of thing is a little above my paygrade but I'm learning quickly!
So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?
hillbillyhotrod said:
So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?
Click to expand...
Click to collapse
Sounds like you're still in Fastboot mode.
Try these ADB commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Thanks
Sorry it took me so long to respond but I had a login problem. From what I have read ADB doest go al that well using ubuntu, that and I'm not really all that good using command line and terminal. Any other ideas?
So my friend tried setting it up remotely last night but it didn't go well, anything I can't do from inside TWRP to make it work?
Sent from my SGH-T959V using XDA App
hey
hey man, in twrp, trying doing mount, then on your computer, put on a stock rom to the drive, then in twrp, run the stock rom
I'm pretty sure that is what I have been doing but I will try again
Ok, tried again and no luck, I have tried cm7 cm9 and a few others with the same result.
semms like the kf is in bootmode 5001 (recovery)
would try to use kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
but use the corrected run.sh from here:
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use option 1 - bootmode normal
an other option is firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
It's alive
Brought it to my friends house yesterday who has windows and that command worked perfectly. Now I have energy ICS installed and cant log in to gapps, lucky me.
Now should I be able to put on a different rom from Ubuntu computer without that happening again?
Sent from my SGH-T959V using XDA
to switch it accidentially to a wrong bootmode can allways happen, but it's no problem:
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
Way over my head, plus im not able to do the adb from my computer I have to have my friend do it from his windows machine.
just flashed a gapps for a different rom but still not letting me sign in to google. Driving me nuts.
everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal
b63 said:
everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal
Click to expand...
Click to collapse
I will have to check that out
Gapps
Any clue how to get my gapps working?
the energy rom should have it allready built in:
http://forum.xda-developers.com/showpost.php?p=23255224&postcount=75
It does but I couldn't sign it so I tried a different one, still cant get in.
sorry - don't know the energy rom - would try to ask NRGZ28 in his thread
Thanks for the help
It is stuck at the picture of yellow fire icon, with a phase press power button for recovery at the bottom...... but no matter how many times i press the power button, it does not respond..............helphelphelp.....
Try holding the power button for about 20 seconds, that should reset it. You can also try this: http://forum.xda-developers.com/showthread.php?t=1356257
Did you install a recovery yet? if so, try spam pressing the power button to get into it. From there you should be able to mount usb and install a rom
The kindle fire has several boot modes, one being a fastboot mode where it will stay at the bootloader until fastboot issues a command to change the boot mode. The command would be...
fastboot oem idme bootmode 4000 && fastboot reboot
not trying to be an ass but i wish people would learn some of the basics before jumping in head first into things they don't really understand then posting basic questions in the development section of forums
But my PC now cannot recognize my fire which is recognized as unknown device. Every time I tried to use adb shell, it said device is not found.....oh my god.....
And I have tried to hold the power button for more than 20s but it doesn't seem work.....
In fact I have installed TWRP once. However, when I am accidentally installing the TWRP twice, the fire is then stuck at the yellow triangle "FIRE" logo...and with a phase press power button for recovery at the bottom.
OH MY GOD....the Fire is my mum's ..... she is going to kill me
I didn't say anything about adb shell
foxdog66 said:
I didn't say anything about adb shell
Click to expand...
Click to collapse
not using adb shell??!! then how can I use the command????
You might also need to use the -i switch. So the command would look something like...
fastboot -I 0x1949 oem idme bootmode 4000
not to be "that guy" but this is in the wrong section. it should go in general.
--sent from my glacier.
I had the same problem ... my computer recognized my fire for 20 sec and BAM! everything just got frozen... just triangle for ever... then I connected to computer ... I had the TWPR installer already open... and before freezing I tried to re install the recovery mod and it worked!
some basics:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
b63 said:
some basics:
Click to expand...
Click to collapse
MY fire relights its fire!!!!! so many thanks!!!!!!!!!!!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
I solved it! it very easy:
1- plug your device to your PC while it is on fire icon
2- open "Kindle Fire Utility" and then press 5
3- done!
I was so scared that I had lost my kindle. I write this for others so hopefully will be helpful for them.