Develop Bugs

Kindle Fire stuck in TWRP boot loop, wont mount, not recognized.

I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.

Kamakookie said:
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Click to expand...
Click to collapse
Maybe go into twrp and do a factory reset. Can you get to that menu? Click wipe and then factory reset.

I've tried the factory reset but it seems to have no effect on it. How do I do the adb push? I've tried using the command prompt to run some of the commands on other threads but I'm not doing something right. I always get an 'adb' is not recognized as an internal or external command, operable program or batch file error.
I'll apologize now for my stupidity on this one- I have never worked with android software before this.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown
I can get it to boot in normal and recovery mode, but each time I try to boot in Fastboot I get an error message 'Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on.' The Kindle shows up in Device Manager under Android Phone as Android ADB Interface
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I'd appreciate any help I can get. I'm at a standstill on this one.

im in the same position you can open it as a USB by selecting mount in TWRP and selecting mount USB Storage

do you have drivers / ADB on your computer ?
I did manage to get my kindle go into a recovery boot loop by doing the root procedure for the original 6.3 original Amazon ROM while my kindle had the 6.2 ROM . After i realized that the root procedure (intended for ver 6.3) didn't work for me, I had to try the procedure for rooting ver. 6.2.
It worked but after a couple of resets, the tablet went into a recovery boot loop.
what i did was to use ADB comands:
enter windows - > start command prompt (start - > run -> cmd)
check if kindle is connected: adb devices
if the device is found then use:
adb shell
su
idme bootmode 4000
exit

Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!

lukebunny said:
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
Click to expand...
Click to collapse
At startup hold thepower button untill you see the bootmenu come up and select "normal boot"

On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.

lukebunny said:
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
Click to expand...
Click to collapse
What version of TWRP do you have?

2.2.0

From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2

jamminjon82 said:
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Tried it, no go.

This is what I get in the command line

The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.

Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810

Have you tried reboot to bootloader?
Sent from my Galaxy Nexus using Tapatalk 2

hey i got your answer I think? lol anyways...
soupmagnet said:
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Click to expand...
Click to collapse
i'm pretty sure it's bla bla bla \platform-tools in that picture anyways that my answer anyways, maybe not but goodluck anyways........... and this 5 mins between post for low posting users is for the birds

digital_cha0s said:
i'm pretty surs it's bla bla bla \platform-tools in that picture anyways that my answer anyways goodluck
Click to expand...
Click to collapse
As you can see, the "adb shell" command is successful because of the change in the prompt.
~ # <-indicates the shell is working and active, so the actual /path of adb is irrelavent.

soupmagnet said:
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Click to expand...
Click to collapse
That seems promising, but this is what I got when I tried it.

Also, thanks for your help everyone, I'm learning a lot as I go here!

Bricked and will not reboot!

This is my gf's kindle fire and she wanted it rooted to have the google play store. This is completely untouched Kindle and on windows 7 pc. So I downloaded the KFU latest release 0.9.6 and proceeded w/ option 2 to install permanent root. Let it sit for about an hour with the please wait and waiting for device messages at the bottom of the screen. I wasnt sure how much longer this would be so i just let it sit. Couple minutes later my gf comes and let me know that she unplugged it accidentally while vacuuming. Im now stuck on the TWRP screen and will not reboot at all. If it try to reboot i get a message saying " E: System in not installed - preventing reboot! " which makes me think that the OS got wiped somehow. All I can do is let it run out of battery. Now in the KFU abd status: Offline and boot status: Unknown. Although that Windows will recognize the device as its showing up in device manager under Adroid Phone: Android ADB interface. What can I do?

not showing up.

Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.

soupmagnet said:
Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.
Click to expand...
Click to collapse
Mount function not working either. I hit the button and never shows up on my comp as a storage device.

Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).

soupmagnet said:
Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).
Click to expand...
Click to collapse
Could I just remove and reinstall the driver? Weird thing is that its still showing up on the device manager Adroid ADB interface.

In a perfect world, yes, that would work every single time.

soupmagnet said:
In a perfect world, yes, that would work every single time.
Click to expand...
Click to collapse
Well i managed to get the driver working and got to flash the latest update from amazon on and renamed it update.zip to get it to flash. Now it seems like its in a bootloop just showing kindle fire in the orange letters. Connecting it to KFU it shows ADB status: online , but still showing bootstatus as unknown.

You need to fix your drivers again.

Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.

neemo6 said:
Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668159

kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
Thanks kinfauns great info!

Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface

neemo6 said:
Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface
Click to expand...
Click to collapse
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.

soupmagnet said:
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.
Click to expand...
Click to collapse
Awesome thanks for the help Soupmangnet!! I got it in twrp recovery now. I would like to just have it back to stock at this point and have the latest update downloaded from amazon on the sd card. Im just worried that this will put me back into the same problem as before. Do need to download or fix something else?

Make sure you change the file's extension to .zip as before, and above all else, wipe System and "Factory Reset". Everything should go well for you.

You sir are awesome! Everything works great! Now to get play store.

You could have simply just flashed modaco instead of going through all he hassle of flashing update.zip and wiping out fff and twrp...

[Q] Kindle Fire stuck on splash

Hey all!
I came across a Kindle Fire here at my work that someone left behind. It gets power and when turned on I get to the Kindle Fire splash screen and that is where it stays.
I read on Amazon's website that holding the power button for 30 seconds should hard reset the device, but that doesn't seem to be doing the trick. Is there any secrets out there to completely reset this thing?
I doubt it is rooted in any way or running anything custom.
Thanks for any help!

I just set up ADB on my Mac and I think I can see the device in it. I think that is a good sign.
Does "USB Debugging" have to be activated in the first place to even use ADB? Because I have no way of getting in the OS to activate it, but it's still showing up in the list of attached devices.
EDIT: Running the commands
$ ./adb reboot
$ ./adb reboot bootloader
$ ./adb reboot recovery
All of those send the tablet into a reboot but nothing more. Still hits the splash screen and never into the bootloader or recovery.

LearnIIBurn said:
I just set up ADB on my Mac and I think I can see the device in it. I think that is a good sign.
Does "USB Debugging" have to be activated in the first place to even use ADB? Because I have no way of getting in the OS to activate it, but it's still showing up in the list of attached devices.
EDIT: Running the commands
$ ./adb reboot
$ ./adb reboot bootloader
$ ./adb reboot recovery
All of those send the tablet into a reboot but nothing more. Still hits the splash screen and never into the bootloader or recovery.
Click to expand...
Click to collapse
Enter...
Code:
fastboot -i 0x1949 getvar product
Hold the power button to shut it off then start it up again (you do have fastboot, right?). Let's see where that gets you.

My brother recently did this to his KF and I downloaded a lot of stuff and troubleshot a lot of stuff I thought it could be. Turns out I just needed to changed the fastboot mode with the Kindle Fire Utility. Download that, run the .bat, and for me it used the first option to change the fastboot mode.
Sent from my at&t Optimus G

[Q] Fastboot after CM10.1 install

Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John

NavyLCDR said:
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
Click to expand...
Click to collapse
Can it boot into TWRP?
If it can
Code:
adb reboot bootloader
This should get you into fastboot
EDIT:
I so misread the question...so you are stuck at the blue KindFire boot screen and not the TWRP boot screen right?

Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.

NavyLCDR said:
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
Click to expand...
Click to collapse
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.

LinearEquation said:
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
Click to expand...
Click to collapse
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.

NavyLCDR said:
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
Click to expand...
Click to collapse
No, they are not the same thing. One reboots into the bootloader and the other reboots into recovery. My comment had nothing to do with testing a reboot and everything to see if you can enter fastboot mode.
Since you have now stated you can enter TWRP, use this tutorial to push a ROM onto TWRP and then just flash it from there. http://forum.xda-developers.com/showthread.php?t=2459498

LinearEquation,
I know that adb reboot bootloader and adb reboot recovery are not the same commands and I know that they are not SUPPOSED to do the same thing. HOWEVER, on MY Kindle both commands ARE doing the same thing. And that is why I know something is wrong. Both commands on MY Kindle ARE having the same result: the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns off.
Why would I want to reinstall a ROM from TWRP when I have a ROM installed? Once I press the power button, if I let it go it boots into CM 10.2 just fine or I can boot into TWRP by pressing the power button at the right time. I cannot reboot in TWRP or fastboot using software commands, and I don't even know if it is supposed to be that way, or if it is a problem.
I did not (and still don't) know if it is normal for the only way to get into fastboot is with a cable after CM 10.2 is installed (and I don't know if I can get into fastboot that way for a few more days), or if I need to reflash a bootloader file or which bootloader file I need to reflash.
I hope that clarified what my problem is.

Can I root from Recovery Mode?

Is it possible to root my Nexus 5x from Recovery Mode?
My phone is stuck in a boot loop, and I can't access my phone's settings. This means (as far as I know...) that I also cannot enable USB Debugging.
I also can't plug it into my computer to access the internal memory because it isn't recognized under normal circumstances, so that means I can't put any installation zips on my phone. However, it does show up in Device Manager as 'Android Bootloader Interface' if I hold down the Power Button + Volume Up keys. It also shows up as 'Android ADB Recovery Interface' if I use 'Apply ADB Update' while in Recovery Mode. Due to this, ADB commands return as 'device not found' or 'error: closed' if I attempt to use ADB commands to push or pull anything onto the internal memory.
As far as I know, the only way to save the contents of my phone is to recover it using ADB, but I can't use ADB unless my phone's rooted... so I've reached quite a conundrum here. Any ideas on what I can do?