yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] tomktsang:
I've run my battery flat, and now when I plug it in to charge, the battery light does not turn on and neither does the screen....
[Kindle Fire Android Development] thedarksavant:
How long did you wait? That's happened to me and I just wait a few hours and the light kicks on.
[Kindle Fire Android Development] gots54:
Just wanted to give a quick thanks for this thread. I got my wife the Kindle Fire when it came out which she used daily up until several months ago, when I gave her a Sero 7 Pro which offered more features and functionality (cameras, hdmi port, sd slot, bluetooth, etc). Since then, the KF sat unused as a paperweight.

I decided to finally give this a shot to bring new life to the device. I'm extremely pleased with the results. It's really brought a whole new life to the KF!!! Thank you!!!:good:

Quick question, when the KF is in recovery mode and connected to my PC, my PC (Win7 64bit) recognizes it as an Amazon OtterX with a yellow triangle; however, I can access the KF's Internal Storage filesystem in explorer just fine. It shows up as a portable device "Amazon OtterX Portable Media Player"

But if I reboot to system and CM is up and running, my PC recognizes it as a Kindle with a yellow triangle, but Windows can't access it's file system and doesn't detect it as a drive or portable media player like it does when it's in recovery mode. Is that expected? Or is there a workaround to this to be able to copy files to/from the KF without having it be in recovery mode?

EDIT: I found the fix here I totally forgot about that since I'm used to Samsung Rom's (S3, S5) which have Android debugging turned on by default
[Kindle Fire Android Development] lovejoy777:
plug it into your pc usb (not your charger) leave it for an hour then plug it into the mains (1.8A at least) charger.
[Kindle Fire Android Development] OnkelKaethe:
error: device unauthorized. Please check the confirmation dialog on your device

Hi,

i have a problem.... every step works fine until adb push after step 3.

when i try to push the zip files to my device i only get "error: device unauthorized. Please check the confirmation dialog on your device"

But after step 3 there is no OS anymore to boot in an confirm. :(

How to solve the problem?
[Kindle Fire Android Development] sd_shadow:
Started a Thread [How To] Fix Lollipop Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
[Kindle Fire Android Development] kvestas:
It is mentioned in the Shadow's thread (very helpful btw) but only to narrow your research: most likely you are using twrp 2.8.2. It requires adb authorisation. Go back to twrp 2.7.1 and adb commands should work fine.
[Kindle Fire Android Development] Delvien:
Trying to update my kindle fire to otterx...

Followed step 1, and step 2 to the T. Reboot to "Open the bootloader menu by pressing [POWER]" and nothing happens.

Bootloader just sits there.

Cannot fastboot flash another version/download of twrp as it says "waiting for device"

adb devices states: 0123456789ABCDEF unauthorized.

attempting to push to the device states: "error: device unauthorized. Please check the confirmation dialog on your device.

1) I cannot boot into recovery by any means

2) bootloader is stuck, even after rebooting multiple times

3) cannot adb or fastboot.

Halp.

EDIT: Actually just fixed it.. It appears when the kindle is low on battery (didnt notice before) the bootloader gets stuck. I let it charge for about half an hour on a normal AC cable, and I can continue.
[Kindle Fire Android Development] sd_shadow:
try power off kindle, run fastboot command, power on kindle

---------- Post added at 08:24 PM ---------- Previous post was at 08:22 PM ----------

fastboot commands only work with bootloader/fastboot mode

adb commands only work with recovery and rom

---------- Post added at 08:26 PM ---------- Previous post was at 08:24 PM ----------

you may be pressing power button too soon or too late.

Did you watch my video? Flashing TWRP in OtterX bootloader
[Kindle Fire Android Development] Delvien:
Actually just fixed it.. It appears when the kindle is low on battery (didnt notice before) the bootloader gets stuck. I let it charge for about half an hour on a normal AC cable, and I can continue.
[Kindle Fire Android Development] labyrinthian:
I have gotten through step 4, but cannot get to step 5 since I cannot get a driver to work for "Amazon OtterX". I've installed-uninstalled-rebooted with KFU 0.99 drivers; tried Android SDK Amazon drivers; and have tried on 2 separate Win7 machines and one WinXP machines.

Any new ideas to get the "Amazon OtterX" to be recognized.
[Kindle Fire Android Development] gots54:
I had the same problem as you and was also stuck on step 5. For me, when in recovery mode, Win7 recognized the KF as an Amazon OtterX with a yellow triangle in device manager. my PC and would classify it a s Mobile Device in Devices and printers and allowed me to transfer files to it through explorer. It didn't show up as a new drive letter, just a device, but by clicking on it, I was able to get to the KF's filesystem and copied the ROM to the Downloads folder through windows explorer. But I noticed if the device went to sleep/timeout in recovery mode, I could no longer write to the folders, they somehow became read only. I'd have to disconnect the USB cable, reboot back into recovery, then reconnect the USB cable.

Hope that works for you. If not, you could try installing the ROM using ADB sideload. Enable ADB sideload on TWRP, then from your PC, run adb sideload <path-to-rom>\<rom-name>. I had to do this when I tried a different ROM.

If that still doesn't work, you could manually change the device driver to Google ADB Device or something similar to that (I forgot exactly what it was). Had to do this as well because at some point, my PC would just recognize the device but wouldn't allow me to write to it with either explorer or ADB despite trying various drivers and the last ADB executables.
[Kindle Fire Android Development] labyrinthian:
Still no progress - still have the yellow triangle for "Amazon OtterX". A Drive "E" does pop up (which is linked to it), but I get "Please insert a disk into (E:) Removable Disk." I don't see anything under Devices and Printers that I can access. ADB doesn't seem to be working at present; but, I do get the Android ADB to show up when I sit in Boot Recovery (not in TWRP).

Other things I tried, I downgraded to TWRP 2.7.1.0 (from 2.8.2.0), still have bootloader 2.05, followed these instructions (to the best of my understanding):

If you have Twrp 2.7.1.0 and bootloader 2.05, and have wiped cache, rebooted, Formated Data, wiped partitions in wipe>advanced , rebooted to bootloader, select Amazon partitions, select recovery, wipe cache, reboot to bootloader select OtterX partitions, select recovery, wipe cache, reboot, format data. I stopped short of wipe all partitions since I wasn't sure what all of them were.

Things would be a lot simpler if I could get Windows to recognize the driver...
[Kindle Fire Android Development] sd_shadow:
[IMG="partitions"]http://i1248.photobucket.com/albums/hh500/sd_shadow/IMG_20141219_214522_854_zps43f26c17.jpg[/IMG]

---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------

Data, Cache, Dalvik, System...
[Kindle Fire Android Development] labyrinthian:
So, to be clear 'all' is really four of five, excluding internal storage..
[Kindle Fire Android Development] sd_shadow:
did you check the partition sizes? and file system?

---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------

no, that is marked for checking partition sizes and file systems,

for wiping check all
[Kindle Fire Android Development] labyrinthian:
Still yellow

Data Partition, Size: 5880MB; Used: 0MB; Free: 5497MB; Backup Size: 0MB; f2fs < doesn't match for Used

Cache Partition - matches

System Partition, Size: 751MB; Used: 12MB; Free: 739MB; Backup Size: 12MB; ext4 < doesn't match for Used

Still not accessible via Windows; I can get fastboot access, but still no ADB.

P.S. Anyone else notice runaway threads on XDA in Chrome? Memory ballooning on open tabs, probably flash.
[Kindle Fire Android Development] sd_shadow:
all should say Present: Yes

system: Current file System: Ext4 - Size: 751MB (768MB)

Cache: _Current File System: Ext4 - Size: 503MB (512MB)

Data:__Current File System: _ f2fs - Size: 5820MB (5880mb)

the rest of the info will vary

---------- Post added at 10:17 PM ---------- Previous post was at 10:12 PM ----------

I would change Data to Ext4

wipe Data, change Data to f2fs

wipe data

reboot

retry push

---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------

if you still can't push

I would in Bootloader select amazon partitions

reboot to twrp, wipe cache, reboot, format data, wipe system, wipe data

try push,

if yes then go back to OtterX partitions, wipe, format, wipe

if no, flash older twrp like

fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img

http://techerrata.com/browse/twrp2/blaze
[Kindle Fire Android Development] Hashcode:
I think I see what's causing the issues with MTP working. I'll try and get a new TWRP up in a bit for those having issues.
[Kindle Fire Android Development] lovejoy777:
nice mate you pushed upto cm yet i can add the commits and give it a test if you want.
[Kindle Fire Android Development] Ace42:
I think my Kindle just died...After trying to wipe data the screen flashed & turned black, but when I pressed the pwr button everything in twrp was fine. After rebooting the boot animation started and then it said "encryption of data unsuccessful blah blah", so I chose to reset the device, which initiated a reboot. After rebooting it returned to the same screen (using AICP 5.0). I ended up wiping every partition, then used fastboot flash recovery for the new twrp since adb push couldn't access /sdcard for some reason. Now it shows 0MB for internal storage while in twrp 2.8.2.0.
[Kindle Fire Android Development] sd_shadow:
Don't use TWRP 2.8.2.0, flash twrp 2.7.1.0

[Video] Flashing TWRP in OtterX bootloader

---------- Post added at 06:21 PM ---------- Previous post was at 06:10 PM ----------

then you should should switch back to amazon partitions>reboot>choose otterx Partitions> wipe cache>reboot>format data>format system> wipe>advanced>check all boxes>swipe to wipe.

then see if partitions match post 2 of http://xdaforums.com/kindle-fire/general/how-to-fix-lollipop-install-errors-t2974063
[Kindle Fire Android Development] Ace42:
Darn, I read your post too late. I reverted to 2.8.1.1 & flashed FFF 1.4A bootloader after restoring the amazon partition from Otterx. All partitions register as EXT4, but MTP & USB storage no longer show on my PC. Also I totally forgot that FFF can't access fastboot from the boot splash.
[Kindle Fire Android Development] sd_shadow:
Not sure what you are trying to do? but suggest you flash a 2.7.X.X Twrp Flashing TWRP in FFF bootloader For Kindle Fire 1
[Kindle Fire Android Development] redbean25:
I can't get ADB to work in any version of TWRP now. It shows as Amazon Otterx in device manager. But it works when in fastboot and when booted to the ROM. I tried 2.7.1.0 and 2.8.2.0. Could my drivers be borked? Even though it works just fine in the two other modes?
[Kindle Fire Android Development] sd_shadow:
may need to reinstall, but first

Did you try mounting in TWRP 2.7.2.0?

or

In Device manager>select unknown device>Update driver software>

browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>

show all(uncheck show only compatible)>look for ADB interface or android phone

select yes to Ignore warning

may need to reboot both.﻿
[Kindle Fire Android Development] redbean25:
I'll give it a shot when I get some time later. Thanks!

Wait... Where is 2.7.2.0?
[Kindle Fire Android Development] sd_shadow:
Typo
[Kindle Fire Android Development] redbean25:
Mounting in 2.7.1.0 does not work.

After uninstalling in device manager and scanning for hardware changes, it assigned the proper type to the Kindle in Recovery. So now ADB DEVICES states the proper ID and says online. However, when I say adb reboot, it hangs and nothing happens. Not sure why ADB in recovery has stopped working...even in old versions where it used to work. Oh well, it still works in fastboot and when the ROM is booted. I'll just continue to ignore it in recovery I suppose. It's just frustrating.

Thanks for the help.
[Kindle Fire Android Development] sd_shadow:
Which twrp.zip are you using?
[Kindle Fire Android Development] Ace42:
Nah, my PC (win8.1) literally doesn't see the device anymore. I'll try what you suggested after buying the fastboot-usb cable.

Sent From Capsule Corp.
[Kindle Fire Android Development] sd_shadow:
fastboot boot cable only forces Kindle Fire in to fastboot mode, if you have fff or OtterX bootloader

fastboot cable will not help.
[Kindle Fire Android Development] Ace42:
Well, I guess my hands are tied lol. These are relatively cheap to buy, so I could get another KF second-hand. Also thanks for all the help dude, Happy holidays! :beer:

Sent From Capsule Corp.
[Kindle Fire Android Development] sd_shadow:
does Kindle show bootloader screen, when booting up?
[Kindle Fire Android Development] redbean25:
I use the img file and flash in fastboot. Never flashed TWRP in recovery before. I use the img file linked in the OP btw (click on the 2.8.2.0 img link and you will see the 2.7.1.0 img file I use).
[Kindle Fire Android Development] sd_shadow:
you wrote that you flash/installed FFF bootloader so I guessed you also used a otter/blaze twrp.

No, mount options do not work with 2.7.1.0 OtterX TWRP.

---------- Post added at 02:03 PM ---------- Previous post was at 01:49 PM ----------

if you still have FFF, I would flash openrecovery-twrp-2.6.3.1-blaze.img

and see if mount options work

---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------

if you get a

Choose a quick format (if possible) and format it as "fat32", block size "4096".
[Kindle Fire Android Development] labyrinthian:
Sad to say, tried as directed, still not viewable by ADB :(

Fastboot always works, but running out of twrp ideas.
[Kindle Fire Android Development] :
Flammable Lol

Thats the Kindle Fire
[Kindle Fire Android Development] sabres032:
That was going to be my very next question, how to actually get the files to a PC. So if something does go wrong then I just push the files back using adb or is there other sorcery involved?
[Kindle Fire Android Development] lovejoy777:
I think to restore you can fastboot flash them back. Just wait for confirmation from one of the devs:)
[Kindle Fire Android Development] lovejoy777:
[MENTION=5417966]androvista[/MENTION] ^^^^^^^^? you know far more than I
[Kindle Fire Android Development] lovejoy777:
i knew i shouldnt have synced cm repo on april fools day. just took 4 hours for sync and build and all notification sounds are of sheep bleating:-s
[Kindle Fire Android Development] MrBrady:
So does this mean my bootloader didn't fully install if I can't get the partitions to fix?

Sent from my SCH-I535
[Kindle Fire Android Development] Roseysdaddy:
Is your partition set to OtterX or Amazon? I had the same issue on and when hashcode said otterx wa snt supported it fixed that.
[Kindle Fire Android Development] :
Sheep Bleeting? I synced the PAC repo yesterday and the Pac-Men ate all my cherry picks :\ Anyway lets continue this Off-Topic here:

http://xdaforums.com/showthread.php?t=1940308

Lets keep this thread to Hashcode and his gallery of inventions
[Kindle Fire Android Development] MrBrady:
It's set to whatever it installs with, which I believe is Amazon.

Are you saying you switched to Amazon and it worked?

Sent from my SCH-I535

---------- Post added at 05:13 PM ---------- Previous post was at 04:51 PM ----------

If you select the OtterX partition layout (which there isn't a recovery or rom available yet, right?) can you switch back to Amazon partition layout?
[Kindle Fire Android Development] lovejoy777:
not sure unless you moved the partitions that get backed up by the emmc fix (ie. xloader boot0, boot1 or bootloader and its flipping out because it can't back up those partitions????. not even sure if [MENTION=4243514]Hashcode[/MENTION]s code refers to them by name or location??. if you could boot into recovery before you repartitioned originally then maybe try an oem format of your partitions to return them back to stock and damaged, then install 2.03 and run fix again. or wait for Hash to comment

sent from my Hash powered Otter
[Kindle Fire Android Development] titusseid:
Need some help please. What is the official way to get into fastboot mode with this bootloader. I want to flash the image but no luck. Thanks in advance.
[Kindle Fire Android Development] koop1955:
I save the image to the same directory as the fastboot executable , which by default is C:\Users\UserNme\AppData\Local\Android\android-sdk\platform-tools

then run: fastboot flash splash initlogo.bmp
[Kindle Fire Android Development] Samuelgames:
I am having the same issue after doing an EMMC Fix and reflashing TWRP, here is my log

-removed-

Edit: Scrap that, I have fixed the problem, turns out I had to repartition it manually, see here: http://xdaforums.com/showthread.php?t=1949372
[Kindle Fire Android Development] :
[MENTION=4243514]Hashcode[/MENTION] I have a faulty boot menu. Whenever I try to start the menu there is nothing on the screen. Restored the boot from recovery but the bootloader remains. Had to flash fff v1.5, Thanks(no critisism, thanks for all your work(including fff 1.5)and god bless you sir)
[Kindle Fire Android Development] Hashcode:
I should have some instructions coming later tonight for how to install the 1st release of CM for OtterX..

Sorry for the delay. Trying to debug some new features as best I can before I put this out there.
[Kindle Fire Android Development] Hashcode:
Thread updated with instructions for installing the new OtterX changes (complete with a CM ROM to use).

Read the instructions THOROUGHLY.

If you have questions, use this thread in General.
[Kindle Fire Android Development] JaViJeC:
Error in tutorial

adb push <test file> /sdcard

is

adb push <test file> /sdcard/
[Kindle Fire Android Development] koop1955:
Error

Made it through the first three steps without an issue. Once I try to wipe, however, I receive an error "E:unable to mount '/data', E:Unable to mount storage.

Able to load both the ROM and GAPPS via ADB, but when I try to flash them, I receive the same errors.

Partition mode is correctly set to OtterX.

Any ideas?
[Kindle Fire Android Development] lovejoy777:
see other thread http://xdaforums.com/showthread.php?t=2623327

Project OtterX: New Direction
[Kindle Fire Android Development] koop1955:
Thanks, lovejoy777, found it.
[Kindle Fire Android Development] seishuku:
I get a similar issue... I can't get ADB to work at all, though MTP does half-way work, just enough to be able to copy the zip to flash.

It's very intermittent though, USB keeps crashing and I have to unplug and reboot the tablet.

I don't know if something got broken in the kernel, or if it's the USB support on the tablet that's flaking out.
[Kindle Fire Android Development] sd_shadow:
If you have issues with 2.8.X.X. Just use TWRP 2.7.10, no MTP, but push works and Lollypop roms install fine
[Kindle Fire Android Development] Sputnikk23:
I just successfully flashed the otterx bootloader followed by 2.8.2 twrp otterx and followed the wipe instructions. I have my zip'ed ROM ready to go but mount usb storage doesn't work and adb says "offline".

mount usb storage says "unable to find partition to mount to usb"

help please?
[Kindle Fire Android Development] :
You need TWRP 2.7.1.0 for ADB to Work(I think)
[Kindle Fire Android Development] bowen873:
I posted a few pages back about my issues with ADB and I see other people are also running into similiar problems. Just curious, but is there a reason why ADB is necessary for step 5 in the install instructions or after you've got everything setup? Since TWRP 2.8.2.0 allows MTP Mount I was able to just push the ROM and Google Apps I wanted to install through my Windows File Explorer (rather than ADB) and then flash them in TWRP. I know ADB has many other uses, but am I missing something else?
[Kindle Fire Android Development] labyrinthian:
I wasn't able to get a mtp mount on any of these versions...
[Kindle Fire Android Development] sd_shadow:
if mtp is working for you with 2.8.2.0 you don't need to use push

but 2.8.2.0 is not working for many.

---------- Post added at 10:09 PM ---------- Previous post was at 10:04 PM ----------

mtp is on by default with 2.8.2.0

mtp doesn't work with 2.7.x.x
[Kindle Fire Android Development] Kfire21:
Cant boot into twrp

Just installed latest twrp zip through recovery, now whenever i try to get into recovery it goes to teamwin logo and goes back to the kindle fire screen
[Kindle Fire Android Development] sd_shadow:
yes, 2.8.2.0 does that to me too

use 2.7.1.0 [Video] Flashing TWRP in OtterX bootloader
[Kindle Fire Android Development] G4 Man2:
Just tried installing on my Kindle, Installed 2.0.5 fine, installed twrp 2.8.1.0 through fasboot, everything looked fine, then after reboot I get a bootloop, even during fasboot it reboots before my computer can find it. I'm a bit new to kindle's so forgive me if I've made mistakes.
[Kindle Fire Android Development] sd_shadow:
Did you verify the md5s for files?
[Kindle Fire Android Development] G4 Man2:
Yes md5s were correct.
[Kindle Fire Android Development] sd_shadow:
did you try to power off?
[Kindle Fire Android Development] G4 Man2:
Powered it off and back on brought me to the same thing, no menu on the bootloader tho, factory cable just gave me a fastboot loop.
[Kindle Fire Android Development] sd_shadow:
which screen?
[Kindle Fire Android Development] G4 Man2:
not getting past the bootloader, just the grey kindle fire, no menu option, then it reboots.
[Kindle Fire Android Development] sd_shadow:
which bootloader?

---------- Post added at 09:22 PM ---------- Previous post was at 09:20 PM ----------

guessing that Kindle's battery is low

---------- Post added at 09:22 PM ---------- Previous post was at 09:22 PM ----------

power off connect to wall charger
[Kindle Fire Android Development] G4 Man2:
Plugging it into the wall charger after powering it down gave me the menu, apparently 44% is too low? :laugh: Sorry for bothering you with something so simple but thanks!
[Kindle Fire Android Development] sd_shadow:
Battery stats maybe off somewhere, should be fine after a full charge.
[Kindle Fire Android Development] :
Same thing happened to me when I installed the latest build of slimkat. Just boot to recovery and flash another ROM
[Kindle Fire Android Development] bloodstorm666:
I cannot ADB to the device. Device not found. In thge device manager, Amazon OtterX is listed, but has an exclamation next it. It needs drivers. Please help!!
[Kindle Fire Android Development] sd_shadow:
see Started a Thread [How To] Fix Lollipop Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...

try

In Device manager>select unknown device>Update driver software>

browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>

show all(uncheck show only compatible)>look for ADB interface or android phone

select yes to Ignore warning

may need to reboot both.﻿
[Kindle Fire Android Development] bloodstorm666:
Ok, thanks. Iv managed to get ADB to detect it, but now its saying unauthorized device! I cannot push anything to it.
[Kindle Fire Android Development] sd_shadow:
downgrade to twrp 2.7.1.0

[Video] Flashing TWRP in OtterX bootloader