yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] kornklown69:
well could always make it mandatory for future builds and retire the original otter builds.
[Kindle Fire Android Development] Lord Morpheus:
Technophobes won't make the jump!
[Kindle Fire Android Development] Idontwantausername:
Fresh install of slimkat with banks gapps still exhibits this issue. The map centres around the home location but location service appears disabled in location settings.
[Kindle Fire Android Development] kev716:
Sounds good. I'm guessing I have to wipe before flashing this?
[Kindle Fire Android Development] Koopa777:
If they're technophobes, I doubt they would have initially flashed a custom boot loader to get here in the first place haha.
[Kindle Fire Android Development] sd_shadow:
could include the otterX bootloader and Twrp with KFU, still would need to change partitions...
[Kindle Fire Android Development] chykal:
Sorry but I don't know if there is a definitive answer for you. I have changed gapps before without wiping but that does not mean it will work in your situation.
[Kindle Fire Android Development] SwoRNLeaDejZ:
So if I flash the TWRP with F2FS and then format data as F2FS, and then flash an F2FS rom, is that going to wipe my internal storage? Or does that just delete all my apps? Don't want to lose my son's minecraft worlds :P
[Kindle Fire Android Development] Hashbang173:
Just back them up in Titanium backup
[Kindle Fire Android Development] sd_shadow:
Yes, everything is wiped. If you have backup data checked in settings, when you sign back in to your google account, apps and app data should be restored. Good idea to back up with titanium backup pro also.

---------- Post added at 11:38 AM ---------- Previous post was at 10:57 AM ----------

Settings/backup & reset, check 'backup my data'
[Kindle Fire Android Development] micl9:
Installed with no issues, Works great Hashcode!

As has been discussed long vs short press can be tricky, but once you get the hang of the timing its not too bad.

One Question:

Is it ON or OFF by default? In the advanced menu it shows:

PARTITION MODE: OTTERX

Oh and thanks for adding the S/N! I bought 2 kindles in perfect condition (ie no scratches etc to tell them apart) so this is a nice feature to keep them straight since CM does not show the S/N.
[Kindle Fire Android Development] lovejoy777:
mine shows otterx on by default. but it can't be as im still able to boot into my old rom and recovery. im not going to toggle it just in case :)
[Kindle Fire Android Development] Hashcode:
I'll double check to make sure the setting actually matches whats on the device because the area that the setting is being saved to could have random data. It should be "Amazon" but this setting is only used when "fastboot oem format" is run.
[Kindle Fire Android Development] Hashcode:
Almost ready for beta v2.03. emmc fix will be included.
[Kindle Fire Android Development] lovejoy777:
im ready when you are. :)
[Kindle Fire Android Development] Hashcode:
Ugh. So I worked on the emmc restore process for about 4 hours tonight. I'm not sure what the difference is between how the bootloader sends the mmc commands and how the kernel does it. But anyway I could never get the boot size to reset back after setting it to 0. I had to fastboot boot recovery.img and adb push mmc_utils into sbin and run the corruption fix from there. :/
[Kindle Fire Android Development] Hashcode:
I may "bench" the emmc corruption fix feature in the bootloader for now to get it out in a more final form.
[Kindle Fire Android Development] Hashcode:
NEW RELEASE: v2.03

What a pain in the ass! EMMC corruption menu option is now WORKING (for those that need it). That and quite a few other new additions should get this version VERY close to a stable release. I'll be looking for feedback.

IMPROVEMENTS:

[v2.03]Splashscreen can be loaded as RGB565 BMP file from "splash" partition (can be applied by: fastboot flash splash initlogo.bmp)

[v2.03]Built-in menu option for fixing EMMC corrupted devices

[v2.03]Better long press button handling (won't get another button press till it's released and pressed again)

[v2.03]NEW Advanced menu item to force reboot and use a bootloader via usbboot (without shorting PIN) -- useful for testing new bootloaders (a hard power off will reset this function -- otherwise each soft reboot will wait for usbboot to load a bootloader)

[v2.03]Fixed partition mode to detect what's actually on the device vs. some random setting

[v2.03]Fixed fastboot erase command

[v2.03]Fixed fastboot flash bootpart command

Download the recovery-flashable .zip file here:

Latest File: otterx-u-boot_v2.03.zip

XDA Downloads

Mirror 1 (Crackflashers)

Mirror 2 (Goo.im)

md5sum: 9bfee6cad5b7f392079e2b3ad6ea7485

INSTALLATION:

1. (Can skip if you already have) Make sure you have a backup of your vital partitions. From recovery via adb:

adb shell "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin"
adb shell "dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.bin"
adb shell "dd if=/dev/block/mmcblk0p1 of=/sdcard/xloader.bin"
adb shell "dd if=/dev/block/mmcblk0p2 of=/sdcard/bootloader.bin"
adb pull /sdcard/boot0.bin
adb pull /sdcard/boot1.bin
adb pull /sdcard/xloader.bin
adb pull /sdcard/bootloader.bin

2. Download the flash .zip from the above link(s).

3. Apply the .zip file in recovery just like any other ROM or kernel .zip file. This is by far the safest way to upgrade your bootloader. It does a sha1sum check on the file before applying.

4. Reboot and Enjoy

For those that want to flash an OTTERX bootlogo:

XDA Link

Once downloaded you can flash it to the "splash" partition via fastboot:

fastboot flash splash initlogo.bmp
[Kindle Fire Android Development] micl9:
Thanks Hashcode!

Installed with no issues.

But I cant DL the OTTERX bootlogo
[Kindle Fire Android Development] Hashcode:
I'll add it to the XDA links in a moment

EDIT: XDA Link
[Kindle Fire Android Development] lovejoy777:
anything for me to do i can't flash through recovery, twrp just hangs on twrp boot logo and no adb shell:(
[Kindle Fire Android Development] seishuku:
Just FYI, you can turn the uboot.bin image into an android boot.img and use "fastboot boot" command to test bootloaders too, that's how I do all my testing (uboot is essentially a kernel).
[Kindle Fire Android Development] Hashcode:
you can extract the cache/otterx*.bin file and use that with the usbboot setup or try to use it w/ fastboot flash bootloader

or try to package it up as a boot.img like was mentioned
[Kindle Fire Android Development] lovejoy777:
i use pokeys firekit what file do i swap. u-boot.bin?? for the short trick. i will try when im back
[Kindle Fire Android Development] HoangTuBot:
I have KF with stock ROM on it. What should I do to install this bootloader. And how is it compare to FFF
[Kindle Fire Android Development] lovejoy777:
i don't get it. i renamed and swapped the otterx-u-boot.bin file with pokeys firekit u-boot.bin. whilst doing the short trick it says "pasted bellow" but when it boots up it just goes into fff "yellow triangle. i replaced the file in root/firekit and changed the permissions. what am i doing wrong??

---------- Post added at 12:30 PM ---------- Previous post was at 12:28 PM ----------

?

waiting for OMAP44xx device...

sending 2ndstage to target...

waiting for 2ndstage response...

sending image to target...

Fixing partitions...

< waiting for device >

...

OKAY [ 0.259s]

finished. total time: 0.259s

Installing x-loader...

target reported max download size of 402653184 bytes

sending 'xloader' (128 KB)...

OKAY [ 0.048s]

writing 'xloader'...

OKAY [ 0.053s]

finished. total time: 0.101s

Flash FFF...

target reported max download size of 402653184 bytes

sending 'bootloader' (233 KB)...

OKAY [ 0.075s]

writing 'bootloader'...

OKAY [ 0.067s]

finished. total time: 0.142s

Flash TWRP...

target reported max download size of 402653184 bytes

sending 'recovery' (5260 KB)...

OKAY [ 1.396s]

writing 'recovery'...

OKAY [ 4.702s]

finished. total time: 6.098s

Resetting bootmode to standard boot...

...

OKAY [ 0.073s]

finished. total time: 0.073s

Loading TWRP...

downloading 'boot.img'...

OKAY [ 1.401s]

booting...

OKAY [ 0.003s]

finished. total time: 1.405s

root@alien:~/firekit#

---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------

whats this line mean? did it not flash properly? "target reported max download size of 402653184 bytes"
[Kindle Fire Android Development] ammubarak:
Hashcode

Excellent work. When booting into fastboot mode, the boot menu message is not shown initially till the first short press to the power button. Displaying a message at the bottom of the screen will be very helpful.
[Kindle Fire Android Development] MrBrady:
I'm interested in trying this, but from what i read, a lot of the features rely on a ROM or recovery that support it, which there aren't any. Is that correct?

Looking forward to the stable release and future development. Thanks for all your hard work!

Sent from my SCH-I535
[Kindle Fire Android Development] ammubarak:
You can still flash this bootloader and maintain whatever ROM and recovery installed in your KF. The option of the new otterx partitions eventually will be activated once applications are available.
[Kindle Fire Android Development] Hashcode:
Yep. I decided later to keep the bootloader compatible with current and future builds.
[Kindle Fire Android Development] lllukas:
Hi guys :)

Im a new passanger of ship called otterx f2fs.

Now, galaxy its open and time to move on up;)

Everything works great.

Regards !
[Kindle Fire Android Development] Hashcode:
UPDATE:

Today I pushed a new version of TWRP: v2.7.1.0

There are some pretty exciting changes (pulled from here):

http://www.teamw.in/project/twrp2

Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.

Various bugfixes to backup and restore

Improvements to USB storage handling (doesn't apply to otterx)

Added a class to search for files to make finding the correct brightness file automatic in most cases

Various other bugfixes and tweaks

If you're happy with TWRP and want to donate to them, head over here:

http://www.teamw.in/project/twrp2

(and use the "donate" button)

TLDR: you can now re-format the data partition as ext4 or f2fs depending on your preference.

NOTE: This also requires a rom change to follow to support ext4.

INSTALLATION OPTION A (ASSUMES COMING FROM A PREVIOUS TWRP INSTALL):

Download the new TWRP flash.zip:

Mirror 1 (Goo.im)

Mirror 2 (Crackflashers)

Place this downloaded file on your Kindle's "sdcard" area

(If following STEPS 1-4 you should already be in recovery at this point -- if not get into recovery by using the power button press during the initial boot and then continue to press power till "RECOVERY" is highlighted)

Use "Install" and find the TWRP flash.zip that you placed on the device. Select it and then Swipe to install.

INSTALLATION OPTION B (USES FASTBOOT):

Download the new TWRP IMAGE FILE: otterx-twrp-2.7.1.0-recovery.img

Mirror 1 (Goo.im)

Mirror 2 (Crackflashers)

Open a command prompt on your computer and "cd" to the directory where it's saved

Enter this command and press enter. It should say "< waiting for device >"

fastboot flash recovery <recovery filename>

Now with the device plugged into USB. Reboot.

You should see the fastboot command execute
[Kindle Fire Android Development] Hashcode:
I'm currently pushing up an updated CM11 build (4.4.3) which also includes a review commit here:

http://review.cyanogenmod.org/#/c/65480/

This allows the ROM to be used with an F2FS or EXT4 userdata partition.

You as the user can select whatever you want using the new TWRP 2.7.1.0 recovery and it should work. (only supported on userdata at this time)

** IT DOES WIPE THE PARTITION WHEN SWAPPING FROM ONE FS TYPE TO THE OTHER **

NOTE: This also includes a device repo change in fstab.otterx:

diff --git a/fstab.otterx b/fstab.otterx
index 029a4bd..4814e40 100644
--- a/fstab.otterx
+++ b/fstab.otterx
@@ -3,6 +3,7 @@
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4 rw,nodev,noatime,errors=continue wait
+/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue wait,check,encryptable=footer,length=-16384
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait,nonremovable,check,encrypta
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue wait,check
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot /boot emmc defaults defaults
[Kindle Fire Android Development] koop1955:
TWRP and CM11 Build Names

Neither the recovery nor the ROM have F2FS in their build names. I assume that they are safe to use post conversion to F2FS?
[Kindle Fire Android Development] Hashcode:
Yes as of the oitterx 06/08 builds they should support either ext4 or f2fs for userdata.
[Kindle Fire Android Development] Hashcode:
New build is up for OtterX CM11 (4.4.3) which supports both EXT4 and F2FS on the userdata partition.
[Kindle Fire Android Development] Koopa777:
I won't have time to flash tonight, but TWRP 2.7.1.0 mounts /data and /cache properly in f2fs, correct? As in, once you format, it doesn't say "cannot mount?" On manta, TWRP fails to read an f2fs partition, and I feel like it's not TWRP, but rather the fstab for the manta in particular.
[Kindle Fire Android Development] Hashcode:
New version of TWRP will read ext4 or f2fs.

(I tested the filesystem reformat and everything worked for me).
[Kindle Fire Android Development] Koopa777:
Yup, that's what I thought. Thanks!
[Kindle Fire Android Development] lovejoy777:
[MENTION=4243514]Hashcode[/MENTION] when i add the commits you posted in skimkat thread, do i just make the changes in patchset 1 or all the patch sets?
[Kindle Fire Android Development] damystica:
Keep improving OtterX, discard Otter please!

I am a recent converter so that's 600 + 1 = 601. :)

Since the data/storage merge, the performance has really improved with extra RAMs. I usually have about ~146mb available with multitasking.

I am on the latest OtterX TWRP and CM11-6.8.14 and I would say it has progressed nicely. Everyone should switch to OtterX Partition!!!

Here are some bugs I am experiencing:

1. ***Battery drains quick during sleep mode (WiFi off), losing 10-16% in ~6 hours.***

2. Couple times (5th time) during sleep mode, my Kindle froze and required hard reset (this morning as well!)

3. Power button is a hit-and-miss, requires pressing several times to register when turning screen on/off.

4. Visual Sores - screen would lose notification and navigation bars, crash to lock screen, etc...

That's all for now and even though with these problems, it's a worthy upgrade!

I won't have to deal with low storage space headache on Otter again.
[Kindle Fire Android Development] BrooklynNY:
Been on the otterx boat from almost the beginning, and I'm lovin it. Currently using 2.05 bl, 2.7.1 twrp, twa_priv's latest ROM & yourzgapps minimal 4.4.3 gapps. Everything is beautiful & fast. What I am really waiting for is USB OTG support...

---------- Post added at 03:24 PM ---------- Previous post was at 03:10 PM ----------

Edit: Well actually, images on google play are a mess... see hiden. I'd say don't use this beta 4.4.3 gapps yet..
[Kindle Fire Android Development] Thepooch:
Those images are as bad on 4.4.2 so I guess I`m not the only one with that oddity lol.
[Kindle Fire Android Development] mlkjuggalo:
Try the 4.4.3 gapps by BanKs I've had no issues .
[Kindle Fire Android Development] BrooklynNY:
BanKs gapps are about 23MB vs yourzgapps's minimal about 17MB package....
[Kindle Fire Android Development] sabres032:
Just flashed TWRP 2.7.1.0. In Wipe>>Advanced Wipe>> I select the partitions listed below and how it's set by default.

Data: Current File System: f2fs

Cache: Current File System: ext4

System: Current File System: ext4

Dalvik Cache and Internal Storage come up with Invalid Partition Selection

Is this the correct set up for all partitions?
[Kindle Fire Android Development] kornklown69:
does it matter if system or cache is changed then formated to f2fs?
[Kindle Fire Android Development] Idontwantausername:
At the very least, you'd have to modify fstab to support it (see hashcode's patch earlier in this thread). I'd say there's a good chance the device won't boot with the system partition formatted to F2FS. I assume it would require making changes to the bootloader.

If you decide to give this a go, please let us know your findings.
[Kindle Fire Android Development] Cykyter:
For some reason I'm getting the same error as someone earlier and signature verification for otterx-u-boot_v2.05 is failing in twrp. I've tried both twrp 2.6.3 and 2.7.1 and checked md5:s multiple times.

Any idea how to fix this?

Edit: Fixed it by flashing the otterx recovery in fastboot and after that using the otterx recovery to flash otterx bootloader. Now everything works.
[Kindle Fire Android Development] koop1955:
Formatting Question

Let me join in on this and ask if there is something special that I should be doing in terms of formatting, any recommended settings?

Running the latest bootloader, the latest TWRP, new Slimrom build. I have been doing dirty flashes (format System, flash ROM and GAPPs, format the caches) using defaults, but I wonder if I am missing something?
[Kindle Fire Android Development] Roseysdaddy:
So, I forgot I had reformatted my pc since I first changed to otterx and now I cant get Kindle Otterx to be recognized in adb, because the drivers arent being found. Can anyone point me in a painless direction to fix this? Google is making me pull my hair out. Thanks.
[Kindle Fire Android Development] koop1955:
I don't know if you will consider it painless, but https://developer.amazon.com/post/T...p-the-ADB-driver-for-Kindle-Fire-Devices.html
[Kindle Fire Android Development] Roseysdaddy:
Thank you, that worked. My last question is if im going to use the f2fs do I need to manually format certain directories with that file system or will twrp 2.7.1.0 do that automatically?
[Kindle Fire Android Development] lovejoy777:
no when you do the switch it wipes out your data/internal storage dependent which way around you are switching to and from. i still did a manual wipe of each individual partition just to make sure they were formatted to the correct type (it can't hurt to wipe everything again).
[Kindle Fire Android Development] uoY_redruM:
Doesn't seem to charge. I'm on the 5/28 F2FS build. The battery died while my 5 year old was using it. Charged it, went to turn it on and nothing. I had to unplug and plug and trick it to get it to boot. Got it booted up but has been stuck at 2% for hours.

Any idea?
[Kindle Fire Android Development] koop1955:
There are two common causes for this issue (neither one ROM/Bootloader/Related unfortunately):

1) Check your cable/charger. If using USB, try wall or vice versa. Use the Kindle wall charger or a good cable.That is the easier solution. If you get it charging, leave it for a while. Like a long while.

2) If that doesn't help you, then the issue may well be with the USB charging port itself, Something may have become loose (5-year olds drop things.) That can be fixable but the answer begins with "Open you Kindle up..." So let's rule out the cable/charger issues first.
[Kindle Fire Android Development] lovejoy777:
The kindle comes with a 1.8A charger, most phone chargers are a lot lower than this and USB ports are lower still. As koop says above 1st try the oem charger/cable
[Kindle Fire Android Development] sd_shadow:
also could be a bad battery, though less likely than charger or charge port issues.

---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------

The kindle charge ports are weak, many have failed.
[Kindle Fire Android Development] uoY_redruM:
Weird. Tried five different cords before it worked. The one that wasn't working was the one I usually used for it, which is why I assumed something was wonky with the ROM.

Thanks for the tips guys. Now I'll let it charge and update to the newest release later.
[Kindle Fire Android Development] Hashcode:
Fyi: https://github.com/CyanogenMod/android_device_amazon_otterx

We were merged as an officially supported device. :)

I need to setup nightlies and choose the userdata format for now since the review commit to suppirt fallback mounting is still being discussed.

Edit: probably going with f2fs.
[Kindle Fire Android Development] lovejoy777:
well done hash:) awesome. I agree with f2fs. its funny when i was asking for help to buid slimkat in the slimroms thread, they wished me luck (with sarcasm) on getting it working on a "3 year old kindle 1st gen" obviously they didn't take into account your wizardry on keeping the kindle upto date:D thanks again Steve
[Kindle Fire Android Development] kornklown69:
caz i haz it yet hahahaha
[Kindle Fire Android Development] kornklown69:
time for that 4.4.4
[Kindle Fire Android Development] rhs013232:
Please help.

I successfully completed the first 4 steps but I cannot push the rom into my kindle thought adb, adb cannot locate my device. I tried to use adb when my kindle is in recovery mode. And my computer able to find a external driver when connected with my kindle. What should I do? Thanks a lot!
[Kindle Fire Android Development] sabres032:
Google is releasing nightlies... :D
[Kindle Fire Android Development] kvestas:
I am assuming you are using Windows. If yes, you may try to restart the computer while Kindle is still connected and try again. If you still can't access the device with adb, install a different adb driver appropriate for Kindle. As I remember the driver inside the newest KFU works fine.
[Kindle Fire Android Development] mystic74:
Really appreciate

Hashcode, I really appreciate your efforts

I was trying to find how to change partition sizes for KitKat for my Kindle Fire and finally found this thread here.

It was very clear to follow.

Thanks a lot
[Kindle Fire Android Development] rexxxxx:
hello,

I am not sure what I am doing wrong but after flashing the bootloader and the TWRP - the Bootloader is working but when I try to enter the TWRP recovery it only shows the logo screen of the TWRP and stays there infinitely.

how can I flash the TWRP again - without recovery ?
[Kindle Fire Android Development] sd_shadow:
flash twrp recovery in bootloader/fastboot with fastboot.exe.

If you have Kindle Fire Utility, copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe) and download otterx-twrp-2.7.1.0-recovery.img

Important verify md5 checksum before flashing

and see my Flashing TWRP with Fastboot.exe in Windows Command Prompt
[Kindle Fire Android Development] rotarydial:
Looking for assistance

I'm getting "No such file/dir" when attempting to backup partitions. Here's my /dev/block ls:

C:\adb>adb shell

~ # ←[6ncd /dev/block

cd /dev/block

/dev/block # ←[6nls

ls

loop0 loop6 mmcblk0p12 mmcblk0p7 ram10 ram2 ram8

loop1 loop7 mmcblk0p2 mmcblk0p8 ram11 ram3 ram9

loop2 mmcblk0 mmcblk0p3 mmcblk0p9 ram12 ram4

loop3 mmcblk0p1 mmcblk0p4 platform ram13 ram5

loop4 mmcblk0p10 mmcblk0p5 ram0 ram14 ram6

loop5 mmcblk0p11 mmcblk0p6 ram1 ram15 ram7

/dev/block # ←[6n

Also, my serial number in adb doesn't match my device s/n.

I haven't done anything with this device in about 20mo. Thx for any help.

Currently running MoDaCo GR9, TWRP 2.2.2.1
[Kindle Fire Android Development] rhs013232:
Yes, I am using Windows.

Thanks a lot, problem solved.

I reinstalled the driver and it works fine right now.