Develop Bugs

[Q] Kindle flashing and factory software

Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?

The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.

If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.

Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.

jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).

jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.

Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?

jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?

Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.

For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.

Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!

jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?

With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.

Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...

Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?

It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.

Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?

Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them

All I get is < waiting for device>. Looks like the drivers are not installed.

Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others

Kindle Fire. Device Manager Sees but Kindle Fire Utility Doesn't

My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?

Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.

Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!

i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks

Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?

Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?

Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.

The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.

Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?

What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt

Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.

Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?

GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!

[Solved]Lost TWRP/No way into recovery

After succesfully rooting my Kindle, I flashed a JB bulid. About a month later wanting to flash an update I noticed I have no recovery and no more FFF boot logo. I tried usiong KFU, but nothing worked. After searching through pages and pages, I decided to uninstall drivers as many have suggested, and delete, then reinstall kfu. I finally got it working again. I flash another rom, and two weeks later, no recovery or fff.
I repeated my steps to no avail. Trying KFU, or getting into fbmode, leave me nowhere, but with a cmd prompt screen with waiting for device.
On KFU my ADB status is online and Boot status 4000
When trying to install FFF I get: failed to copy 'files\fbmode' to data/local/fbmodeermission denied
Unable to chmod /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode:not found
Same when trying to install TWRP. When screen prompt initiates fbmode reboot, it boots into normal os.
adb devices gives me this reading 0123456789ABCDEF.
While trying Pokey 9000's fbmode, I was able to enter fbmode, but trying to install TWRP again left me with Waiting for device..
Any help/suggestions would be appreciated.

I'm not sure if /data/local/ is user writable. I've always used /data/local/tmp/ for this purpose. Here are some manual instructions to get TWRP and FFF installed manually...
http://forum.xda-developers.com/showthread.php?t=1638452
Fastboot mode uses a different interface than adb, so your Windows box may not have the drivers properly installed for it even if adb is working. You might also have to force the KF off by pressing/holding the power for 20 seconds or so and then restart it because both the host and the KF must see the other the moment the device goes into fastboot mode. Check the second post for help on getting the device drivers working properly...
http://forum.xda-developers.com/showthread.php?t=1552547

I tried pokey's fbmode which worked. Now I'm stuck in fbmode and can't get out.
When trying to flash TWRP it would not pass waiting for device
When I connect to my pc, a propmt states device is unrecognizable.
Device manager only shows USB Mass Storage with exclamation.
ADB does not recognize device

Here try this iso*http://db.tt/KDNzyCTP
*Instructions:*
1. Download this http://www.pendrivelinux.com/
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
All you need is a 2 gig usb flash drive to create this live linux adb and fastboot are preconfigured
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565

kinfauns said:
I'm not sure if /data/local/ is user writable. I've always used /data/local/tmp/ for this purpose. Here are some manual instructions to get TWRP and FFF installed manually...
http://forum.xda-developers.com/showthread.php?t=1638452
Fastboot mode uses a different interface than adb, so your Windows box may not have the drivers properly installed for it even if adb is working. You might also have to force the KF off by pressing/holding the power for 20 seconds or so and then restart it because both the host and the KF must see the other the moment the device goes into fastboot mode. Check the second post for help on getting the device drivers working properly...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Windows,Windows,Windows...Why must I reboot so much!
After installing/Unstalling drivers, many reboots, and unplugging/plugging in usb, I've finally got it fixed. Big thanks for those guides. Everything I needed was right there, except my pc was being a real d***head about these drivers.
I uninstalled faulty USB mass storage drivers then reinstalled, and it recognized my device immediately
Now that I have it fixed, any insight on why I lost TWRP and FFF. I would hate for this to be a recurring issue. Especially if I have to wait for my pc to play ball..

I really dont know what you did to wipe fff and twrp but I would say that your case is extremely rare in fact Im sure there is great debate about whether it is even truly possible... And if you were able to duplicate it would be quite impressive... It certainly wouldnt hurt to flash a little smirkit when you change roms if you do it frequently http://forum.xda-developers.com/showthread.php?t=1500935 as far as I know the only thing that will wipeout fff and twrp like that is update.zip your case I believe is only the 3rd that I have ever heard this happening to. I can almost say with at least 98 % certainty that one of those occasions was purely user error.......

Thepooch said:
I really dont know what you did to wipe fff and twrp but I would say that your case is extremely rare in fact Im sure there is great debate about whether it is even truly possible... And if you were able to duplicate it would be quite impressive... It certainly wouldnt hurt to flash a little smirkit when you change roms if you do it frequently http://forum.xda-developers.com/showthread.php?t=1500935 as far as I know the only thing that will wipeout fff and twrp like that is update.zip your case I believe is only the 3rd that I have ever heard this happening to. I can almost say with at least 98 % certainty that one of those occasions was purely user error.......
Click to expand...
Click to collapse
I'm not too sure if I lost TWRP, but I know I lost fff. Kfu and fastboot wasn't working. I know when things like this happen, usually a step was missed.
Sent from my HTC Sensation using xda premium

[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?

80% fixed but need an experienced opinion

Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe

joes6789 said:
Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe
Click to expand...
Click to collapse
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!

joes6789 said:
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!
Click to expand...
Click to collapse
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as in "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?

joes6789 said:
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?
Click to expand...
Click to collapse
I believe that the OS is properly patched in Hashcode's stock ROM, so you shouldn't need to worry about OTAs or a conflicting bootloader. Glad to see it works again!
Sent from my Amazon Jem using XDA Labs

How were you able to get into fastboot with kf first aide? Which drivers and which options?
Gesendet von meinem Nexus 6P mit Tapatalk