yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Hashcode:
F2FS IS HERE!

WHAT IS F2FS?

http://en.wikipedia.org/wiki/F2FS

I just put up a whole new set of files for supporting F2FS and the larger system/cache partitions which should be more future-proof.

All of the information is in the OP, but here's the individual pieces:

STEP 1: BOOTLOADER v2.05 (flash .zip for re-applying in your current TWRP)

XDA Hosted

Mirror 1 (Crackflashers)

Apply file in your current TWRP

To make use of the newer system/cache sizes you will need toggle to Amazon partition layout and then back to OtterX partitions. WARNING: THIS WIPES OUT THE EXISTING SYSTEM/CACHE/USERDATA PARTITIONS.. AS ALWAYS BACKUP YOUR "SDCARD" BEFORE DOING THIS.

CHANGES:

[v2.05]Tweaked the USB plug detection on startup for entering fastboot mode

[v2.05]Adjusted system and cache partition sizes in otterx partition mode to be a bit more future-proof

STEP 2: TWRP with F2FS support

Download the recovery.img file below:

Mirror 1 (Crackflashers)

Then use fastboot to update your recovery:

fastboot flash recovery <recovery filename>
fastboot oem recovery

You will see the same sort of warning regarding userdata mount that you saw when originally converting to OtterX.

WARNING: THE BELOW INSTRUCTIONS WIPE OUT THE EXISTING USERDATA PARTITION.. AS ALWAYS BACKUP YOUR "SDCARD" BEFORE DOING THE RECOVERY UPDATE.

Use the "Wipe" -> "Format Data" option, type "yes" and hit the enter soft key.

Once that's done, reboot back into recovery

STEP 3: DOWNLOAD / PUSH CM11 ROM with F2FS support and GAPPS TO SDCARD VIA ADB

(F2FS version will have *-f2fs.zip at the end)

Mirror 1 (Crackflashers)

Download KK Gapps: http://wiki.cyanogenmod.org/w/Gapps

On your PC open up a command prompt and cd to the directory with these files:

adb push <rom.zip filename> /sdcard/
adb push gapps-kk-20140105-signed.zip /sdcard/gapps-kk-20140105-signed.zip

STEP 4: FLASH AND REBOOT

A COUPLE OF NOTES:

I pulled the f2fs sources from upstream through kernel 3.13. And then used some Motorola kernel 3.4 backport commits as well as a couple more to backport to the 3.0 kernel.

All said, I think there were over 450 commits pulled to support f2fs

There are another 70 or so commits I can pull in which will take us all the way up to the current 3.15-rc7 kernel's f2fs sources. But I'd like to test that out more, and it won't involve any wiping as I update further.

F2FS in general is a VERY new filesystem. I would consider it stable enough to try, but don't expect it to be flawless on the first try.

As always let me know what you think (hopefully in a constructive way)
[Kindle Fire Android Development] leswgnr:
MD5 on F2FS d/l

Getting consistently different MD5 from that posted on Crackflashers: 8f811d3b371b425f473bc0e6af55e45d

D/L: 889293c2e7eff5fa4ca8c7980c846dc4

* Update 1

Seems to have installed correctly - putting it thru it's paces now. Happy to see the new improved theme support. and that some of the prior UI issues seem to be fixed.

As always, much appreciated Hashcode.

* Update 2

Directory searches seem to be significantly faster.
[Kindle Fire Android Development] MrBrady:
[MENTION=4243514]Hashcode[/MENTION], thanks for f2fs! I just got it dialed on my Kindle fire. I noticed when I wipe data or manually format any of the other options (other than the "yes" option), it says it's formatting using something other than f2fs. Is that normal?
[Kindle Fire Android Development] kornklown69:
finally decided to try otterx but when trying to push cm device not found and when i adb devices its blank :/ i know this happened to me before but i cant remember what i did to fix it any ideas?
[Kindle Fire Android Development] sd_shadow:
hows it listed in device manager?
[Kindle Fire Android Development] Hashcode:
Make sure you're using the new TWRP-2.7.0.1-otterx-f2fs. And all of the other partitions will be ext4, only userdata will be formatted f2fs.
[Kindle Fire Android Development] vbdss:
the same happened to me, just go to twrp-f2fs and make a wipe on data, dont go to advanced wipe.

Hash on advanced wipe, one of those wipes will give I/O Error
[Kindle Fire Android Development] kornklown69:
Android composite ADB interface

this is what command promt tells me running windows 8.1
[Kindle Fire Android Development] Idontwantausername:
I just flashed the new recovery and [MENTION=4410674]lovejoy777[/MENTION]'s SlimKat while keeping the 2.04 partitioning scheme, and so far it looks to be working well, so thanks for your work.
[MENTION=4243514]Hashcode[/MENTION], I wonder if the cache partition would also benefit from an f2fs filesystem?
[Kindle Fire Android Development] kornklown69:
not sure if i have wrong drivers or what
[Kindle Fire Android Development] sd_shadow:
looks like drivers are correct, maybe rewipe cache, reboot, Format Data, wipe system, reboot, try file push again
[Kindle Fire Android Development] lovejoy777:
why keep 2.04? (what advantages?, i didn't know it was compatible) (just curious)
[Kindle Fire Android Development] Hashcode:
Technically the extension for the ROM file is ".zip" and you're missing that on the adb push command. That probably won't help with finding the device in adb but I wanted to point that out:

adb push cm-11-20140528-UNOFFICIAL-otterx-f2fs.zip /sdcard/
[Kindle Fire Android Development] Hashcode:
The v2.04 otterx partitions are smaller:

system = 512MB)

cache = 265MB

Vs the newer larger partitions in v2.05:

system = 768MB

cache = 512MB

The idea was to protect from future required wipes do to low system/cache space.

The bootloader doesn't need to support f2fs only recovery and the ROM/kernel.
[Kindle Fire Android Development] Idontwantausername:
I figure that I'll repartition when I need the extra system partition space, in the mean time I see no need for it.
[Kindle Fire Android Development] lovejoy777:
on the wipe topic, i tried to format data 1st and got an error so then i went /advanced/wipe cache, then back and formatted data (with the yes command) everything else i did as hashcodes instructions. I know nothing about windows apart from there drivers always gave me issue's, so i swapped to ubuntu 3 years ago and now adb always works. wish i could help:(
[Kindle Fire Android Development] sabres032:
Right after I unlocked my Kindle I was having a though time getting Windows to recognize the device in adb or fastboot mode. Once I had the device powered on in the operating system Windows recognized it no problem. I think it may have had something to do with the device ID being reset to all zeros because once I got the new bootloader and recovery installed, set the OtterX partitions, all of a sudden the device was recognized by adb and fastboot WITH the proper ID.
[Kindle Fire Android Development] MrBrady:
[MENTION=4243514]Hashcode[/MENTION] when running Viper4Android on any of the 4.4.x ROMs I've tried, the app doesn't see the headphones. If I enable headphones effects it has no affect on the sound. If I enable device speaker effects, it affects the headphones and device speaker.

Do you think this is this an issue with our custom firmware or the Viper app itself? I've only had this issue on the KF.

Thanks again for the amazing work!
[Kindle Fire Android Development] kornklown69:
im going to try a windows 7 computer tomorrow that has never had adb set up, ivr had it on mine for a while doing things with my nexus 5 sometimes i worry about different drivers being installed for all my Android devices causing some kind of issue but who knows... ill update tomorrow, i inherited this kindle from my wife she wanted to sell it but i wanted to keep it because i heard about hash keeping it alive so its like a toy for me lol
[Kindle Fire Android Development] sd_shadow:
Did you try any other adb commands? or reboot to bootloader and try

fastboot reboot

verify that twrp md5 checksum was correct? reinstall twrp? rewipe everything?
[Kindle Fire Android Development] kornklown69:
tried other adb commands and got the same no device found message fastboot works perfectly except for "fastboot devices" which is blank
[Kindle Fire Android Development] chykal:
This is working great. Thanks hash!
[Kindle Fire Android Development] kornklown69:
started new on a windows 7 computer worked like a charm

Finally otter x!!!!!
[Kindle Fire Android Development] Hashcode:
Awesome. :)

On a side note, Windows is a nightmare of support for device maintainers. And you can see why.
[Kindle Fire Android Development] lovejoy777:
can someone on this rom please check if it has wifi location services working. (after the google play services updates). cheers steve
[Kindle Fire Android Development] ammubarak:
Thanks Hashcode, excellent work,.
[Kindle Fire Android Development] Sambena:
otterx to amazon

so I wanted to switch back to an amazon partition and I wanted to know if I needed to reflash the original twrp designed for that partition style?
[Kindle Fire Android Development] Hashbang173:
Yes you should

Sent from my OtterX running SlimKat
[Kindle Fire Android Development] Lord Morpheus:
I going to try this on a Windows 7 PC, all instructions read and kinda understood... here goes...
[Kindle Fire Android Development] Lord Morpheus:
Took me just under an hour, because I was having a dumb moment and forgot to download the ROM and GAPPS!!!

Will test and give feedback, Thank You Hashcode, for your amazing work!!!!
[Kindle Fire Android Development] HoangTuBot:
ROM is laggy when I toggle in QuickSetting
[Kindle Fire Android Development] SenorSmartyPants:
I'm running a 1.5 year old ROM from the XDA forums and I'm looking to update to 4.4 but I've got a couple questions

If I update to the OtterX bootloader and OtterX-TWRP will I be able to only install OtterX specific ROMs? Or would I be able to still install the generic CM Otter ROMs?

How "beta" is this? Should I expect crashes or only in the most specific of circumstances will I have problems?

I'm currently running FFF 1.4a and TWRP 2.1.1.

Before I started reading the forums again I was planning on install cm11 M7 when it comes out this month.
[Kindle Fire Android Development] lovejoy777:
you can only run otterx roms on otterx partitions. its in beta but proving to be stable. no issues reported yet (once setup properly).
[Kindle Fire Android Development] abarax:
When I attempted to utilize the EMMC corruption fix, this screen popped up. However, my computer (Windows 7) doesn't even see the device under Device Manager, even once I reinstall the drivers. Is my device bricked?
[Kindle Fire Android Development] lovejoy777:
no not bricked. your in fastboot mode. type fastboot devices into your terminal

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

sorry like this.

$fastboot devices

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

what step are you at?
[Kindle Fire Android Development] uoY_redruM:
I haven't touched my Kindle Fire in literally a year or more. I actually bought a Galaxy Tab 3 recently. However, I've never stopped following your work over here. I have it tabbed as a favorite on my XDA app. Today, I finally decided to pull it out of the drawer and blow off the dust.

I didn't have Android SDK setup anymore, as I stopped building ROMs and I built a new rig last year. So, starting from absolutely zero necessary files I was able to download all necessary files, successfully get everything set up and get adb working, push all the files, flash and have the ROM running without one single hiccup in about an hour, maybe hour and a half. Just followed Hash's instructions very carefully, and also made sure drivers were correctly working before starting.

Thanks Hash and this is ABSOLUTELY bad to the bone!

Your work is much appreciated and I look forward to future updates.

:victory::highfive:

---------- Post added at 04:55 PM ---------- Previous post was at 04:42 PM ----------

OK, minor hiccup. Any trick to getting WiFi working? Every time I put my password in, when I click OK it says "failed to connect to network".
[Kindle Fire Android Development] sd_shadow:
It likely is just listed with a different name/device type, try the fastboot commands like fastboot reboot or like lovejoy777 wrote $fastboot devices

if they work should be good to flash.
[Kindle Fire Android Development] uoY_redruM:
[MENTION=4267571]sd_shadow[/MENTION] or anyone else that might know.

(sorry if this is a double post. I edited my last post but I don't think it was seen by anyone)

I cannot connect to WiFi. Every time I try it says "Failed To Connect To WiFi". I did a thread wide search but I don't see anything related to WiFi.

Is there a trick to get it to work? I tried rebooting. I tried wiping both caches. I tried turning WiFi off then on.

Want to make sure I'm not missing something.
[Kindle Fire Android Development] sd_shadow:
I have had issues connecting to non protected wifi, seems to not see the wifi router

still on EXT4 DATA PARTITION VERSION, and cm-11-20140508-UNOFFICIAL-otterx

rebooting otterx has been my fix. Don't know if it is rom, partition, or twrp related.

could also try unpluging router, wait 20 secs, plug it back in to power outlet.
[Kindle Fire Android Development] uoY_redruM:
I'll try rebooting the router. Amateur mistake, I should have also tried that really quick.

I flashed the most recent of everything. Bootloader, TWRP, F2FS ROM and the 4.4 GAPPS.

I'm on a protected network (my home network). If rebooting the router doesn't work, I'm not sure what else to try.
[Kindle Fire Android Development] Hashbang173:
Do you have it so your router only accepts certain MAC addresses?
[Kindle Fire Android Development] Hashcode:
Why did you try EMMC corruption fix? That wipes out every partition on the device and attempts to restore the barebones xloader, bootloader

You'll need to flash a recovery.img via fastboot to get back up and running.
[Kindle Fire Android Development] uoY_redruM:
No, but I figured it out. I never had to use the button before, but I had to press the WPA button on the router. When I did that, it connected :good:
[Kindle Fire Android Development] koop1955:
Had the same issues, solved it by reflashing ROM and GAPPs. Worked perfectly after that.
[Kindle Fire Android Development] MrBrady:
Is there a link to manually fix the partitions? Whenever I run the fix, it throws errors and doesn't do anything.

I'm guessing it's because I had manually rebuild the partition years ago after a corrupt install. My partitions are probably slightly different than stock. Unfortunately I can't find the link to how I did it previously.

VZW SGSIII
[Kindle Fire Android Development] lovejoy777:
if you could downgrade your bootloader to one that has oem format (not sure which has it 1.4?). then do fastboot oem format. then swap back to 2.05 and try the fix from there?
[Kindle Fire Android Development] bflobills:
Does fstrim still apply with this new F2FS partition, or not needed anymore?
[Kindle Fire Android Development] Hashcode:
On the f2fs partition, its set for normal discard. Fstrim will only be run on the ext4 partitions.
[Kindle Fire Android Development] muiriddin:
set the region then it should work fine...

---------- Post added at 06:00 PM ---------- Previous post was at 05:59 PM ----------
[Kindle Fire Android Development] kornklown69:
4.4.3 is out can't wait for merge
[Kindle Fire Android Development] Italico:
Hey guys! How're you doin'?

I received a Kindle Fire (otter) some weeks ago, and it is already on KitKat (CM11).

It is really slow, though... I know it is an 'old' device, but Chrome, i.e., is super slow: digited text come out with delay.

And I have delayed touch response, too: even with a casual app and the settings panel opened, I have to wait so much to switch from recents to home and vice versa that it seems I haven't pressed any of the on-screen buttons.

Just asking: do the OtterX method, and maybe F2FS, may help to relieve this laggy situation?

And a fresh question to Hashcode: is there any plan about 4.4.3 merging?

Thanks to everyone who can help!
[Kindle Fire Android Development] lovejoy777:
no super lag on my device (when i was on cm11). have you ran the fstrim commands?. The new otterx and f2fs is the way forward. as for 4.4.3, as i see it every dev and his dog is beavering away at it as we type?
[Kindle Fire Android Development] sabres032:
Not to mention completely wiping the device will get rid of all that accumulated junk that could be slowing down your device. Anecdotally speaking, once I switched to the OtterX partitions my device sped up considerably. Just today I converted it over the the F2FS partition and clean flashed [MENTION=4410674]lovejoy777[/MENTION] SlimRom. It's charging up now so I can't speak for any performance gains but I'm sure since it's "Clean" it will fly.

Edit: I'm still trying to convince my wife to allow me to convert her Kindle over to the new partitions because she is complaining of this exact same thing. But, trying to convince a woman that a man is right is a whole nother story. :D
[Kindle Fire Android Development] lovejoy777:
you need to make her think it's her idea. ?
[Kindle Fire Android Development] PantherVT:
inception
[Kindle Fire Android Development] abarax:
When I flashed the ROM, it was stuck in an endless bootloop. I tried everything, but no luck. I fired up the EMMC corruption fix, and then... chaos.

As it stands, my PC doesn't recognize the Kindle at all. It's not listed under ADB devices, so what recourse do I have? I can't execute any fastboot commands as it won't recognize my device.
[Kindle Fire Android Development] kornklown69:
back up everything with titanium backup then move the back up file to a computer do the changes, move back over that file, re-download titanium, restore boom no harm done
[Kindle Fire Android Development] lovejoy777:
ok 1st have you tried the long press power (30 secs)?

what pc os?

when you say chaos?? what happened.
[Kindle Fire Android Development] Italico:
Thank you guys for the TRIM tip. Unfortunately the commands ran fine, but without any effect, positive nor negative.

I used the KF utility to throw in the TWRP recovery, and from there I flashed ROMs and Gapps.Tried HellKat, CM11 official nightly and now I'm on SGS7 unofficial build. each time with a clean flash, of course.

When I will be less busy I would like to use the OtterX partition system, as Sabres declares it will speed up the device a bit. And it will remove the annoying 'press once power button, switch on immediatly' thing.

I am just in doubt about F2FS... Is it worth? Are there any risk or drawback?

I will really appreciate if someone would say its opinion about it, so I'll have elements to support my decision.

It's my mother tablet, she uses it to browse, play games, read some PDFs and DOCs, chat on WA with my sister who studies away. So i would like to make it functional but without any 'extreme' configuration.

Thanks!
[Kindle Fire Android Development] sonomazr2:
I have Infriction 2.27.2014 build running currently and it works great for that. The nice part about the build is you don't need to flash gapps.
[Kindle Fire Android Development] sabres032:
I mentioned it would get rid of the annoying FCs, lag and reboots. She still said no. But, your right a few more days she will hand it to me and say fix it. Then I get free reign. Muuuhahahaha...

Will old ext4 TiBu work with the new file partition?
[Kindle Fire Android Development] lovejoy777:
yes it worked for me.
[Kindle Fire Android Development] kvestas:
I am sure the Hash's note in this thread says quite enough about f2fs:

"F2FS in general is a VERY new filesystem. I would consider it stable enough to try, but don't expect it to be flawless on the first try."

In addition I could say that no one have submitted any issue related to this new file system in the community yet (as I know).

On the other hand I don't see any big advantage using it as well - it's just kind of a hope this will be a bright future soon.

I like to play with new things so I am using it. So far so good.

As I know Infriction ROMs don't use f2fs (neither OtterX partitions) so the answer might be not related to your question. But I have to admit they are really nice ROMs.
[Kindle Fire Android Development] sonomazr2:
He hasn't done otterx yet, I believe he is still on amazon partition. He listed a bunch of roms he tried, I didn't see Infriction.
[Kindle Fire Android Development] abarax:
Yes, I've tried the 30-second press, and no change.

I'm running Windows 7.

My PC just won't recognize the device. Not sure what to do.
[Kindle Fire Android Development] Ixthusdan:
I just went thru a similar problem, discovered that my cable was defective. The kindle charged ok ( outer wires) but would not talk ( inner wires), so one was broken. New cable was the fix.
[Kindle Fire Android Development] lovejoy777:
try a different cable like mentioned above, but i bet its a driver issue. sorry i cant help (i know nothing about windows).
[Kindle Fire Android Development] Lord Morpheus:
The only major problem I encounter is, the kindle goes into Deep Sleep and I have to reboot the device to turn it on.
[Kindle Fire Android Development] kornklown69:
how do u get google now launcher to work i keep getting the Google bow launcher requires new Google search version
[Kindle Fire Android Development] mlkjuggalo:
I use Banks gapps and it works with no issues
[Kindle Fire Android Development] kev716:
What is Banks gapps?
[Kindle Fire Android Development] Hashbang173:
Thinks its this: http://xdaforums.com/google-nexus-5/themes-apps/gapps-t2012857
[Kindle Fire Android Development] mlkjuggalo:
Here is link to gapps i use with no issue on the 2 OtterX roms i have used.

BanKs gapps http://xdaforums.com/google-nexus-5/themes-apps/gapps-t2012857
[Kindle Fire Android Development] Idontwantausername:
Are you having any location issues? Can you see your position on maps?
[Kindle Fire Android Development] mlkjuggalo:
No issues when I open maps it locks in to my home address
[Kindle Fire Android Development] lovejoy777:
what version of google play services are included? my guess is as soon as it updates it will break location services:(
[Kindle Fire Android Development] mlkjuggalo:
I have play services version 4.4.52. With play store version 4.8.20
[Kindle Fire Android Development] danij3l:
Error lashing zip '/sdcard/cm-11-20140528-UNOFFICIAL-otterx-f2fs.zip'
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount storage.

partition mode is OTTERX

bootloader ver. 2.05

recovery ver. 2.7.0.1

any suggestions?
[Kindle Fire Android Development] Ixthusdan:
Format data with f2fs. It is a special step in twrp 2.7.0.1
[Kindle Fire Android Development] lovejoy777:
uncheck everything in twrp/mount
[Kindle Fire Android Development] kev716:
What is Banks Gapps?

Yes, I did a Google search and found a lot of sites with download links, but nothing that explains what it actually does. What is different between Banks gapps and regular gapps?
[Kindle Fire Android Development] mlkjuggalo:
The gapps are the newest versions as I don't think the regular gapps are updated as often.
[Kindle Fire Android Development] chykal:
Banks specializes in minimal gapps package. They are for users that do not require our wasn't the full gapps package and for devices that have limited storage like the Kindle.
[Kindle Fire Android Development] Hashcode:
Today, I noticed we would end up boot looping (due to a PVR crash) if any sort of higher res bootanimation was selected (via theme manager). Bad bad bad. So to fix that I pushed up some changes in how the bootanimation was being buffered and set it to a slightly easier to handle resolution.

The idea being: I can't control what boot animations are tried out, so they all need to work. If perhaps they stutter slightly, it's better than boot looping.
[Kindle Fire Android Development] Hashcode:
Also, I started the process to get OtterX brought into CM as a supported device for nightly builds.

I think many users are watching how the OtterX project is going, but haven't made the switch because they like the nightly builds... so that will change hopefully soon.

To my guess, only about 500-600 users have tried out OtterX. :/ I hope as we go forward more users can make the jump and experience new life with their Kindles.