Need a little help - Kindle Fire Q&A, Help & Troubleshooting

I have managed to install gederom, however, i can't get back in to TWRP and it still shows the kindle fire boot screen, any clue how to fix this. I have tried connecting using adb however it doesn't find it from within windows.

It simply reboots back to the os

How are you trying to get into TWRP? Do you have FFF installed? What version for each?
May want to try "adb reboot recovery" and/or "adb shell idme bootmode 5001", from within the ROM.
EDIT: Just noticed the part about ADB not working. Since you installed gederom, it's most likely a driver issue. Take a look around the device manager for a possibly changed hardware ID.
However, if you have FFF 1.4a installed, you should be able to either "reboot into recovery" from the ROM or to press Power a few times as FFF's splash comes up to boot into recovery.

You can try using Smirkit to update/install FFF and TWRP
Sent from a thingymajig that sends things.

Smirk it worked thanks so much!!!
Sent from my Galaxy Nexus using xda app-developers app

Related

[Q] FireFireFire not showing up on boot after installing TWRP

I used KFU to root and install FireFireFire (first) then TWRP, after installing the latter, I noticed that the Android above the "Kindle Fire" logo was gone, is this normal. I apologize in advance if this is a repost.
Are you able to use the power button to enter recovery? If not, use fastboot to install FIREFIREFIRE.
fastboot -i 0x1949 flash bootloader u-boot.bin
"u-boot.bin" being the name of the version of FIREFIREFIRE you want installed. You must be in fastboot mode with both "fastboot" and "u-boot.bin" in your present working directory (dir).
Sent from my Amazon Kindle Fire using xda premium
consider the thread as stated making sure no steps were missed and if Rom boot fine into android OS no issues.
http://forum.xda-developers.com/showthread.php?p=24129239
mughalgxt said:
consider the thread as stated making sure no steps were missed and if Rom boot fine into android OS no issues.
http://forum.xda-developers.com/showthread.php?p=24129239
Click to expand...
Click to collapse
I used the Kindle Fire Utility to install both TWRP and FireFireFire, I decided to install the "ReloadedRom", it went well until I took the device out of the charger after leaving it overnight. I noticed that half of the screen had pinstripes and the other half was fine. Another question, is how do I get into fastboot? I am familiar with installing roms and such, so I do have a decent background. Thanks in advance!
showmeaction said:
I used the Kindle Fire Utility to install both TWRP and FireFireFire, I decided to install the "ReloadedRom", it went well until I took the device out of the charger after leaving it overnight. I noticed that half of the screen had pinstripes and the other half was fine. Another question, is how do I get into fastboot? I am familiar with installing roms and such, so I do have a decent background. Thanks in advance!
Click to expand...
Click to collapse
With FIREFIREFIRE installed you can enter the fastboot command (in your command prompt) with the device powered down. When it says <waiting for device> turn the device on and the command should run when FIREFIREFIRE goes into temporary fastboot mode.
Otherwise:
adb shell idme bootmode 4002
adb reboot
To change it back:
fastboot idme bootmode 4000
Be sure to <shift + right-click> on your KFU/tools folder and select run from command prompt to use fastboot
Sent from my Amazon Kindle Fire using xda premium
I was able to get into fastboot, but what next? Also, what is wrong with the screen?
I tried the Reloaded rom today and it seems like the rom itself is the culprit. I was having the same kind of screen problems before I switched back to Hashcode's rom. There have been others here with the same exact problem and they all were using Reloaded.
Sent from my Kindle Fire using xda premium
showmeaction said:
Also, what is wrong with the screen?
Click to expand...
Click to collapse
Update to hashcode's #7 kernel
Sent from my MB865 using XDA

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!

[Q] Bricked KF2 - no OS, fastboot & TWRP available

I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Background/How I 'Bricked' It: I have a Kindle Fire 2 and was able to successfully unroot/flash Cyanogenmod 10 onto it. Worked perfectly for about 6 months, when I decided that it would be a good idea to flash back to stock so that I could give it to a relative. I have TWRP 2.3.3.0, so I used a guide on xda to do the following:
I used a guide from xda and followed these instructions
-Download latest KF2 stock software from amazon. Re-name the file to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
Unfortunately, wiping the system seems to have wiped the CM10 OS (ROM) that I had installed, and there was a failure in installing the amazon stock:
Installing '/sdcard/download/update.zip...
assert failed: is_substring ("Otter2 , file_getstring("/proc/product_name"))
E: Error in /sdcard/download/update.zip
(Status 7)
Error flashing zip '/sdcard/download/update.zip'
Updating partition details...
Trying to reboot the system from TWRP results in a message that states: "No OS installed! Are you sure you wish to reboot?"
Investigating using ADB: So it looks like I have no OS on the Kindle Fire 2. This seems to be a problem because without an OS, I am unable to use adb (from what I've read, no OS = no way to accept/authenticate the computer RSA fingerprint to whitelist the kindle and allow adb to function). Trying to use KFU, KFFirstAide, or the Kindle UnBrick Utility results in Error: Device offline or Error: Device not found types of messages (I am assuming due to the fact that I can't "turn" adb on by accepting the RSA fingerprint prompt)
What does Device Manager tell me? My computer can 'see' the Kindle Fire in device manager [as I stated earlier: My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles] but going to My Computer and looking under mass storage devices, the computer doesn't seem to recognize the device as a USB storage device, which is a problem because I can't drag/drop or push/pull files to the SD card so I can't try to flash anything *other* than the original file that failed.
Fastboot Mode...? From what I can tell (http://forum.xda-developers.com/showthread.php?t=1668159), my device is in fastboot mode. My Kindle screen hangs on the blue/white Kindle Fire logo screen, which from what I understand is hashcode's bootloader/fastboot screen. However, when I look at the Hardware IDs in the device manager, it tells me that my hardware IDs are:
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
So...my kindle seems to be stuck on the blue/white fastboot screen, but register on my computer as the stock kindle fastboot? I'm not really sure what's going on there, and couldn't find too many people with the same discrepancy that I have...
I tried plugging in my cord (making sure to use a USB 2.0 port), going into Command Prompt and using some fastboot commands. (ie: fastboot flash bootloader \path\update.zip) but all I get is a <waiting for device> for a LONG time. As in, a few hours. Some basic googling/investigation seems to indicate that I don't have fastboot drivers installed, OR that I wasn't running fastboot in an 'elevated mode' but I haven't been able to find too many details about how to fix those, IF that is the problem.
TWRP 2.3.3.0: I can get into TWRP recovery just fine, although I can't seem to figure out how to get files onto my device. So I've tried re-installing the original update.zip file that failed the first time several times, with no success. trying to 'Mount' the device doesn't seem to do anything (at least, my computer doesn't see the device as USB storage regardless of whether it's mounted or not) I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the adb sideload <filename> command just gets me an Error: Device not Found message. I thought maybe I could try Advanced --> Terminal Command, but have no idea how to do that or what it does, and most sites are very vague about the step-by-step details, so I didn't really touch it.
Not sure if this is relevant or not, but when my KF2 is plugged into (attached) to my computer with the cord and is in TWRP, device manager shows the device under 'Other Devices' --> Amazon Kindle Fire2, and there is a yellow triangle on it. Not sure why...going back to 'fastboot' mode gets rid of yellow triangles and is recognized as a Kindle Fire again.
At this point - I'm pretty much stumped and have (hopefully) demonstrated that I've done my best to do my own research/read through threads/done due diligence. Is there anyone out there that might have any suggestions? Or do I now have a very large paperweight?
ANY input/suggestions/encouragement is welcome! I absolutely and sincerely appreciate your time in reading through this thread and trying to help noobs like me!
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
...tried those, but maybe am doing them incorrectly?
mindmajick said:
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Trying to use the ADB sideload feature to push CM or another ROM over doesn't seem to be working for me (unless I'm doing it wrong?)
I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the "adb sideload C:\users\Name\update.zip command just gets me an Error: Device not Found message". Could I be using the command incorrectly?
Trying to use any fastboot command in Windows Command Prompt results in <waiting for device> to hang for hours, with no changes to command prompt and no changes to the kindle (still sits at the blue/white boot logo).
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fastboot Drivers
mindmajick said:
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Are there difference drivers for fastboot and adb? I don't get a 'yellow triangle' and my device manager identifies the device as a Kindle Fire [Android ADB Interface], so I thought I was okay.
Should I be looking for fastboot drivers?
And btw, thanks so much for your willingness to help and input!
ME TOO
Just purchased a KF from someone...thay had rooted it...I tried to unroot...got stuck...now mine is doing the same as yours. I hope someone has a fix for you as I too have a large paperweight.
Follow Up
tessa33 said:
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Click to expand...
Click to collapse
tessa33,
I just sent you a response. Call me at 707-774-5923 when you have a moment.
Solution?
I figured I could post in this thread before staring my own because I am having a very similar issue trying to revert my Kindle Fire 2 back to stock from cyanogen so I can sell it. I downloaded the official software from Amazon but every time I try to flash it through TWRP I get the exact same error you were getting. Did anyone ever figure out how to resolve the issue for you?
Had the same problem, so I chatted with an Amazon associate, told him I turned it on one day and it showed the grey triangle and he sent me a new Kindle Fire 2nd Gen for free. Try that...
Sent from my iPhone using Tapatalk
Hello
I have rooted KF2 and I did factory reset I lost TWRP&Os I can see the device as ADB device, Howeverm when the device in fastboot the pc not recognize it.
issuing fastboot devices command return nothing.
I used ubuntu and windows still the same issue. any idea?

[Q] Stuck in recovery

Hi All
I was in the process of rooting, installing TWRP, and eventually attempting to get to CM10.1. I was able to get the TWRP but now stuck and cannot proceed further. When my Kindle boots it comes up with the orange and then switches to the blue logo and does not proceed. I can only get it to jump into TWRP mode and will then pull up the cmd prompt from there to try and troubleshoot.
When I run adb devices it will state that daemon is not running and then start it on port 5037. It will also note the serial number as well as state 'recovery' rather than 'device'. I have attempted to return it to the factory boot but it will only say that it is waiting on the device without any change. I can get it into fastboot mode by starting the server.
How do I get out of recovery mode? I have tried many different ways without any luck. Please help.
Thanks
Matt
When I get into fastboot mode I attempt to enter fastboot oem idme bootmode 4000. However it will then state waiting on device. I am stuck.
Fastboot commands need to have "-i 0x1949", also you should be able to push a new ROM onto the kindle in twrp to flash using "adb push filename.zip /sdcard/filename.zip" and install from there, you either don't have an is right now or the kindle os isn't booting because its a newer version that detects twrp and doesn't let it boot up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for responding.
I am now attempting to use adb sideload to push the ROM but it isn't working. I start the sideload feature within TWRP and then code in cmd prompt. I am getting 'error: closed'. Maybe I have a driver error? I have Android Phone>Android ADB Device.
Don't bother with side load if it errors, just let twrp load and run the adb push command I mentioned above, it should put the zip onto your sdcard so u can flash it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
So I think I am on the right track for the sideload. Yet still stuck. I have adb sideload running in TWRP and when I put in adb devices in cmd prompt it now gives me the serial number and notes sideload. Trying to push the zip folder, cm-10.1-20130812-UNOFFICIAL-jem, to the device. I have tried to use the full path, C:/users/name/file/etc. followed by /sdcard/filename but still coming up short.
got it!!
Thank you!

(STUCK) Kindle goes into "fastboot mode" screen even when entering recovery

Yesterday was my first time rooting a Kindle Fire, and the root process went very smoothly when I followed this guide which uses saferoot: http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
While I made use of this guide for flashing FFF and TWRP: http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
After successfully rooting it, I wanted to try the OtterX ROM/TWRP/Bootloader, since I read the comments and saw it would be good to try it out. After flashing the bootloader (otterx-u-boot_v2.05), the kindle kept rebooting showing the logo and the option to 'press power to enter boot menu'. I thought this was normal so I didn't mind it. (During this time, I could still enter recovery.) I proceeded to Step 2 which was flashing TWRP for OtterX (I downloaded zip-otterx-twrp-2.8.2.0-recovery.zip and installed it using the previous TWRP I flashed: openrecovery-twrp-2.2.2.1-blaze.img).
I wasn't able to remember what I did next, but I know I was already having issues. I was getting anxious and sleepy at the same time, I remember exploring the boot menu and foolishly/stupidly tried the EMMC Corruption Fix, without even trying to research about it beforehand, so now I'm stuck at the "fastboot mode" screen (I've attached a photo of the screen). Whenever I turn on the device, it shows the kindle fire logo and the option to enter boot menu. If I let it be for a while, it goes into the "fastboot mode" screen, the same thing happens when I try to choose "continue boot" or "recovery boot". Windows doesn't recognize it anymore whenever I try to connect it too (I'm using Windows 8.1 by the way.)
Please help, I've tried reading about how I could restore the kindle to the state it used to be after I rooted it, but no luck, I couldn't find anyone encountering the same problem as me since I think I'm the only one stupid enough to apply that EMMC corruption fix without knowing or reading what it actually does. Thanks in advance to anyone who could help.
Try
Download adb/fastboot files, if you have not yet.
Power off Kindle
In command prompt
Run command to flash recovery
Power on kindle
See [Video] Flashing TWRP in OtterX bootloader
THANK YOU SO MUCH for your reply. I tried it as soon as I woke up. I found out that the problem was the driver, I reinstalled it and flashed the recovery using the fastboot command.
Sent from my C5502 using XDA Free mobile app

Categories

Resources