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!!!!!!!!!!
Related
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
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
I know how to get out of it by tying fastboot -i 0x1949 oem idme bootmode 4000
but when i open kindle fire utility 0.9.5 i try to install firefirefire or twrp but it just reboots and gets stuck on the kindlefire logo. what do i do. i believe i installed all the drivers just like it said
i get a online and 4000 status on the utility.
it says the img has been found in the utility
also i havent even seen a yellow triangle yet
I assume you rooted first...?
jluke86 said:
I assume you rooted first...?
Click to expand...
Click to collapse
yes.
i install the google apps with the utlity and it worked fine
im not sure why i cant get into recoverymode
KFU 0.9.5 does not seem to produce the yellow triangle upon startup. The only way I could enter TWRP was to run the utility again and install TWRP from scratch. 0.9.1 does not have this problem though.
Uninstall your drivers. Reinstall them manually.
Use command prompt to enter fastboot command.
Sent from my Amazon Kindle Fire using xda premium
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
Hey guys,
I'm sorry I couldn't figure out what to do next simply by searching your forum, so I will try to be both as brief and as descriptive as possible.
I started here (http://forum.xda-developers.com/showthread.php?t=1568340) trying to root my fiancee's KF 6.3. I didn't feel comfortable using KFU or similar because those programs are built for Windows and I am using Linux. The Kindle Fire seems to be stuck in a recovery loop. When plugged into USB (using the cable that's actually for my LG Optimus phone), it boots to FireFireFire (yellow triangle) then reboots constantly. At no point is it accessible via adb devices or fastboot, and it doesn't show up under lsusb, which would be the equivalent to not showing up in Device Manager in Windows. (The driver should be fine because all of this was working fine originally when I started the process.)
So I guess my question is what now? I've read a few things about needing a "factory cable" which may set it back into fastboot mode, and I'm pretty sure I could get going again from there. Is that what I need to do? TIA for any help.
PS - I've successfully rooted my LG Optimus S and flashed custom ROMs, so I'm not totally inexperienced. I use Arch Linux and I'm comfortable on the command line. If you have a solution for Windows, I *might* be able to translate it into Linux speak, so don't hold back. Same goes for Ubuntu/Debian - those are totally different than Arch Linux, but I might "get it" enough to translate it.
PPS - I have intentionally omitted information relating to what I was doing when I caused this for brevity, but I would be happy to discuss what steps I took in following the above linked thread if some guru believes it's relevant or someone wants to know.
A factory cable is a last resort kind of thing so I wouldn't jump the gun quite yet, although it doesn't hurt to have one in the first place.
It would be helpful to know which step in the rooting process things went awry. The constant rebooting/restarting isn't typical. Did you make sure you had enough battery before trying to root?
FIREFIREFIRE loads in a temporary fastboot and with the version you are using it lasts for about ten seconds (before the green light goes dim). You can issue fastboot commands during this time without the need of a factory cable.
See if you can get...
fastboot devices
...to be recognized during this time.
Sent from my Amazon Kindle Fire using xda premium
If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk
It would be helpful to know which step in the rooting process things went awry.
Click to expand...
Click to collapse
OK, let's start with that.
From the thread I linked in the first post:
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
Click to expand...
Click to collapse
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
Howto flash by hand
Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. Currently KFU or fbmode is the easiest
flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
reboot: "fastboot -i 0x1949 reboot"
Click to expand...
Click to collapse
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
pbailey212 said:
If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I think the problem here is the he can't get past the bootloader and stuck in an ACTUAL bootloop. In which case, adb commands are useless.
One thing that could be causing problems is the USB cable being used. If the device only experiences these symptoms when plugged in then I would say that's most likely the case.
Sent from my Amazon Kindle Fire using xda premium
I suggest you build a firekit USB for Linux. Search for firekit for Linux thread in the development section.
Sent from my Amazon Kindle Fire using Tapatalk 2
palintropos said:
OK, let's start with that.
From the thread I linked in the first post:
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/showthread.php?t=1475740
Installing TWRP 2.0.0 is different than installing TWRP 2.1.0. I think the instructions on the TWRP site is for the old version, but they link the new one.
http://forum.xda-developers.com/showpost.php?p=24732291&postcount=1298
Your OP sounds suspiciously like a dead battery, but you say you've corrected that. You might want to connect to your OEM charger for a while anyway and see if that helps
Also, in my experience, fastboot on linux required elevated privileges. Try running it as root.
Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/show....php?t=1475740
Click to expand...
Click to collapse
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.
palintropos said:
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
palintropos said:
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.
Click to expand...
Click to collapse
Have you tried setting the bootmode to normal and rebooting?
fastboot oem idme bootmode 4000
fastboot reboot
Like I said before, it would probably be best for you to try this as root.
EDIT: It's also possible your system is broken and the KF can't complete its boot process. When you start up the device, the boot logo will first come up. Does the display go black after that and come back with a dimmer yellow triangle logo? Because if it's doing that, it's not in fastboot any more.
kinfauns said:
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
Click to expand...
Click to collapse
Ditto. If you can get the device to be recognized even for a second, it's still enough time to issue...
fastboot -i 0x1949 oem idme bootmode 4000
Just keep trying
[Edit:] or what he said
Sent from my Amazon Kindle Fire using xda premium
Yay! I played around and got my udev rules working, and I got a reading on (sudo) fastboot devices, so I was finally able to set the bootmode to 4000 and reboot. Everything seems to be back to normal now. The Kindle appears to be working fine though not rooted.
Please let me know:
if there is anything else I should know to make sure the KF is normal
if there is any additional info I should post to benefit other users who might have this same problem
or if I should mark this thread SOLVED/RESOLVED or equivalent and how to do so.
if your fastboot ever stucks in waiting for device mode and you are on linux
try once with either root user or using sudo command.
thats one of the thing people forget most of the time and get stuck there.
http://forum.xda-developers.com/showthread.php?t=1576675
Try the above with the kindle switched off you should see waiting for devic, then press power once ( fast boot should kick in when you power on)
Sent from my Amazon Kindle Fire using xda premium