Database Users

121212121212121212

121212121212121212

I was hoping some post this here.
I wanted to know have you checked on stock kernel does it supports touchscreen work.
if not can anyone test and suggest which all kernels are supporting it and not.

anantshri said:
I was hoping some post this here.
I wanted to know have you checked on stock kernel does it supports touchscreen work.
if not can anyone test and suggest which all kernels are supporting it and not.
Click to expand...
Click to collapse
I got Aroma installer in X10S v8.2 addon zip (for unlock bootlaoader) and had no problem on stock or custom kernel.
However I never tried on fxp kernel.
For info there's a menu in aroma installer to config the touchscreen, values must be written in the config file (aroma config).
The only restriction for now is that Aroma installer is using Edify script so may cause problem on locked bootloader ... doesn't copy files or else ...
@Feravolt
Thanks for this thread !!!
About the script for locked bootloader did you have time to look at it ?
It would be very nice to include it directly in kernel .. maybe it could solve the problem with lock bootloader ?

Hi OP
Below is the latest Aroma File Manager's newest features :
- Terminal Emulator.
- Set Permissions.
- Auto screen calib.
Bugs :
- File copy, paste and move function from Internal Memory into SD Card (and vice versa).
- Scrolling Touch for X10, have to use volume buttons.
Any chance for X10 to have this recovery tool to be integrated in Kernel (for GB, ICS and JB) ?
Just incase if no backup file, PC/Laptop arround to repaire bootloop or bricked phone, easily .
Thanks in advance
Regards

[RECOVERY] ClockworkMod 6.0.3.7 for Xiaomi Mi3 tegra4 (pisces)

This is a modified ClockworkMod recovery for the Xiaomi Mi3 tegra4 (pisces). It includes some changes from M1cha's CWM for Mi2 to support the dual-system design of the Mi2 (same thing on Mi3), while leaving out "true dualboot" feature for now. I think TDB is useless as long as there is only MIUI available for this device. See source for details.
Working so far:
adbd in recovery
nandroid backup/restore, including system1, boot1
running any update.zip (including AROMA)
choose system to install update to
set active system
Anything else untested.
Installing:
(1) Flash using fastboot:
adb reboot-bootloader
{wait for fastboot screen}
fastboot flash recovery cwm-*-pisces-*.img
(2) Boot new recovery:
Type fastboot reboot and press enter while holding Vol+ key should take you directly to CWM.
(3) Let CWM disable recovery flashing (offered automatically when selecting reboot)
I didn't test this method so far (feedback welcome) -- in case it doesn't work, try this instead:
Alternative installation method:
(1) Disable automatic recovery reflashing (while running MIUI, requires busybox installed and a root shell, eg "adb root; adb shell")
Code:
mount -o remount,rw /system
chmod 444 /system/etc/install-recovery.sh
mount -o remount,ro /system
(2) Flash using fastboot
Code:
adb reboot-recovery
{wait for fastboot}
fastboot flash recovery cwm-*-pisces-*.img
Use at your own risk, right now this is largely untested
Download: cwm-6.0.3.7-pisces-a20131110a.img
Older Releases: cwm-pisces
Source:
Device tree (stub)
Recovery
Note: As there's no kernel source available yet, the kernel is left out of device tree. For building yourself, extract stock kernel from your boot image and place it in the device tree (filename "kernel")
History:
a20131110a:
Integrated all fixes by M1cha that are not related to TDB -- backup/restore of boot1 now working
Set default storage to /sdcard/0, nandroid backups now accessible via MTP
a20131110:
Integrated boot-system selection and recovery-check for both systems
Used biggest font for readability on fullHD display
a20131109a: Integrated the first dualsystem support modification by M1cha
a20131109: Unmodified CyanogenMod source, no dualsystem support at all

This is my future phone.. So thanks

Thanks, but keep in mind this phone comes with 2 different SoCs, Tegra4 and Snapdragon800 -- this here is for Tegra4, which is found in TD-SCMA version... maybe I should update OP to explicitly state that.
Btw, it's not complete yet, it doesn't flash original ROM updates correctly, I think thats because named partition nodes are missing ... I'll add support for these soon
Gesendet von meinem MI 3 mit Tapatalk

No third-party ROM MI3 brothers now seems less useful but thank you
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://115.com/lb/5lbdstd81pd#
recovery-clockwork-cwm-6....3.7-pisces-a20131110a.zip
115 network disk packs code：5lbdstd81pd

yao85930101 said:
No third-party ROM MI3 brothers now seems less useful but thank you
Click to expand...
Click to collapse
Well, I need some time to improve it, because there's two possible uses with stock ROM:
- nandroid
- re-flashing mods after upgrade
I'm especially interested in the second, because I want some apps to reside in /system/app permanently. Unfortunately, it doesn't work yet, as it doesn't flash official upgrades (right now need updater app for this) -- as I said, probably the named device nodes for partitions, need time to work on this.
For 3rd-party ROM ... There COULD be. I assume stock kernel is somehow based on this:
http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=tree;hb=refs/heads/linux-tegra-nv-3.4
(seems to contain platform drivers for tegra pluto board, has android drivers and it's even exactly the same linux version)
So, it COULD be possible to build a working kernel from these sources. Well, I didn't even get anything to boot far enough for giving useful error info to me But if you want to "waste" hours and days, please try yourself A custom kernel would be an excellent start.
yao85930101 said:
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://pan.baidu.com/s/1Dwmj9
Click to expand...
Click to collapse
Nice! :good: Is this installable from stock recovery, too?
A little remark: I'd prefer not to modify /system automatically from the installer but better boot directly into CWM and then let the user decide. Of course thist would require rebooting to recovery from updater-script. I didn't do edify script for quite some time -- is this possible? If not, maybe we could throw together a little arm7 binary for the boot to CWM for some kind of "final" release. I'd consider thios CWM version "final" as soon as it can flash official updates (from xiaomi)

Oh look forward to updating you again Come on you are the best

However, a day to focus on the brothers really no way to track it?

Hello, I don't have time for this right now. I'll get back to the project probably after christmas.
But, as I said, it's probably the missing partition names -- so this SHOULD be fixable in the device tree, adding init scripts to the recovery (no need to modify CWM itself further). Feel free to clone the repo (AND you need an original kernel image extracted from the phone)

Any reason this wouldn't work on Tegra Note 7?

e8hffff said:
Any reason this wouldn't work on Tegra Note 7?
Click to expand...
Click to collapse
At least two.
1. The kernel. It's taken from an original Mi3 tegra phone, unfortunately, there are no sources yet from Xiaomi. Although it's the same platform, the chances this kernel would boot on any other device are low.
2. "Dual-system". I don't know much about the Tegra Note 7, but I doubt it has 2 system and boot partitions. Most android devices don't -- the Xiaomi phones are the only ones I'm aware of. CWM code in this zip is modified/extended to handle this (mostly taken from modifications done by M1cha for the Mi2). It won't work on a normal single-system device. In fact, there's no need to modify CWM source for a standard single-system device, a device-tree would be enough for building a working CWM recovery.

Zirias said:
At least two.
Click to expand...
Click to collapse
Ok thanks for the reply.

any progress on this work? is this CWM fully working now?

Don't Copy Others Work
If u Copy some ones Post Then Plzzz........... Mention
http://forum.xda-developers.com/showthread.php?t=2521125

new cwm but in chinese dor tegra 4
i have find these two but i think it is in chinese
http://4pda.ru/forum/index.php?showtopic=541742&st=5360#entry32916655
http://www.miui.com/thread-2069908-1-1.html
if any one could help and translate them to english we can have true dual boot and try the new custom roms for tegra 4 xiaomi
Android - 5.0 Lollipop for tegra 4 xiaomi but this must be in chinese too
http://www.miui.com/thread-2111749-1-1.html

Flashtools (MiFlash4Linux, Recovery from QDL/DLOAD, Partition resize)

Introduction
This is a collection of Tools and Resources for Flashing Mi2(s)(c).
MiFlash4Linux
https://github.com/M1cha/aries-image-builder
Core Recovery Package for MiFlash
This is a small package to Recovery MI2 from any bricked state. It has the following advantages over the official ones from Xiaomi:
They don't flash any ROM, just the core system(bootloaders, modem and recovery)
They are small which means both Download and Installation are faster
It directly installs custom Bootloader and TWRP. That means you easily get your device back to a modded status.
Please follow the official MiFlash guidelines for installation with the following differences:
the DLOAD config is called rawprogram_core.xml
the fastboot script is called flash_core.bat(or flash_core.sh for linux)
there's a script called flash_partition_table_and_core which is a alternative to flash_core.bat/sh.
It can be used to change the partition table.
USE THIS WITH THE CUSTOM BOOTLOADER INSTALLED BY ONE OF THE CORE PACKAGES ONLY. Xiaomi's bootloader will format your whole MMC device. THIS WOULD ERASE YOUR EFS AND YOU CAN'T MAKE CALLS ANYMORE
Changing the partition table
There are multiple packages available:
separated: Xiaomi's original layout with a virtual internal sdcard
separated_single: same as separated but without Dualsystem and bigger system partitions
unified: Xiaomi's new layout with /data/media support
unified_single: same as unified but without Dualsystem and bigger system partitions
unified_single_xiaomi: Xiaomi's version of unified_single
SkiFire13 said:
aries_core_unified_single.zip -> only MIUI > 5.4.x or M1cha's CM12.1 or latest AOSP5 works (only they can see Internal Storage, that now is a virtual sd-card in /data/media/0)
aries_separated_single.zip -> other roms
Click to expand...
Click to collapse
Installation:
Backup all your data(including internal sdcard, and EFS just to be safe)
if you don't use the custom Bootloader yet, flash this package using flash_core.bat/sh first. See the big red warning above for more information
flash the package using flash_partition_table_and_core.bat/sh
boot into recovery(which is TWRP now), recreate the filesystems for all partitions(system,data,cache,sdcard to ext4) in the wipe menu and reinstall your ROM.
Version Information
Bootloader: https://github.com/M1cha/mi2_lk/commits/LA.AF.1.1-02810-8064.0
TWRP: v2.8.7.0
core partitions: aries_images_5.7.16_20150626.0000.4_5.0_cn_a63cddccfa.tgz
Download links for Mobile users:
aries_core_unified_single_xiaomi.zip
aries_core_unified_single.zip
aries_core_unified.zip
aries_core_separated_single.zip
aries_core_separated.zip
XDA:DevDB Information
Flashtools, Tool/Utility for the Xiaomi Mi 2
Contributors
m11kkaa
Source Code: https://github.com/M1cha/aries-image-builder
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2015-07-27

First (as always)
Sent from my A0001

the singleboot packages causes the latest version of CM12 to fail booting because of SELinux enforcing. I'll upload a fixed package asap.

everything has been fixed and is up again.
Pls download everything again(especially MiFlash4Linux if u use that).

i think i will wait util the release of GRUB4Android....

acastrocab said:
i think i will wait util the release of GRUB4Android....
Click to expand...
Click to collapse
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).

m11kkaa said:
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
Click to expand...
Click to collapse
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help

MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
On the top of the page just followed by the title, there is a "Download" tab, you could find the miracle at there ;p

MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads

ancics said:
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
Click to expand...
Click to collapse
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png

Hey M1cha, thank you! Great job!
I have some issues about the procedure:
1. I am not sure if already had a custom bootloader, so first i'll flash the package flash_core.bat :
- turn on mi2s in fastboot mode
- plug usb, device should appear in miflash(the program should be configured as the photo?)
- and click flash
- reboot phone, enter in fastboot mode again and do the same procedure with flash_partition_table_and_core.bat
Is that right?
It's easy to recreate the ext4 filesystem in TWRP? always used CWM....

m11kkaa said:
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Click to expand...
Click to collapse
Oh that's why, I'll download it from a computer, thanks!
Sent from my MI 2S using XDA Free mobile app

@m11kkaa: thnx for the linux tools/scripts, it made my migration from CWM to single-system partition + new bootloader + TWRP easier.
BTW, I just wanted to migrate and keep my current CM11 for the time being. I had to fight a bit with restore from backup because I was not aware of the incompatibility between CWM and TWRP, luckily enough it eventually was sufficient to:
reformat system, data and cache in TWRP
flash the old CWM temporarily and restore boot, system and data
flash TWRP again and make new backups.
Proposal:
It would be good if you can change the heading style of "Installation" in the OP to be the same as e.g "Introduction", because now it looks like part of "Singleboot Partition Layout" section only. It is confusing IMHO.
In my case (i.e. flashing both flash_core.sh and then flash_partition_table_and_core.sh), I had to recreate ext4 FS not only on the system partition in TWRP, but also on the data partition (it could not be mounted and TWRP announced 0 MB size) and eventually also on the cache partition. This seems to contradict the info in OP, part "Singleboot Partition Layout", which mentions that data will be preserved.

@cogano thx for your feedback
it's weird that u had to recreate the filesystems because the positions of these partitions still are the same. I resized system1, modem1 and boot1 to 2KB and system, modem and boot to 2*oldsize-2KB. I checked the offsets and they still are the same.

I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster

cogano said:
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
Click to expand...
Click to collapse
thx "parted /dev/block/mmcblk0 p" will help to debug these things.
If you don't have a ROM/Recovery with parted you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.

i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!

m11kkaa said:
you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
Click to expand...
Click to collapse
What a great feature!

superiyezi said:
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
Click to expand...
Click to collapse
There's a Download "card" on top.

What are the partitions sizes after flashing the singleboot partition layout?

TWRP 3.2.3-0 and older versions for Redmi Note 2

TWRP3.2.30-Universal version uploaded
https://drive.google.com/open?id=16BueY8230PzL-5ngkMiNZGxpIYBoK4EL
TWRP3.2.20-Universal version uploaded
https://drive.google.com/open?id=1Qr35EfIy76c6lkQZaKBzRS_PuBhUfjMX
TWRP3.2.10-Universal version uploaded
Rebased on TWRP3.2.1-0
https://drive.google.com/open?id=1Tcc5pk-7MOz5IRwqgH-zfKj-t7pnSMi5
TWRP3.2.0-0-Universal version uploaded
Changelog:
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
Oreo ready..........
https://drive.google.com/open?id=1uJAc84Qgw4k1NW3W3BjcVtwc37y--xz8
TWRP3.1.1-0-Universal version uploaded
Changelog:
Uses 7.5.11 Android 5.02 kernel
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
https://drive.google.com/open?id=0BwdRTuyj12_yVWZqUnd6MEN0QVk
Note: This version saves to a folder named as the serial number of the device which is different to the previous version. Old backups will not work unless they are copied into the new folder.
TWRP3.0.2-2 has had a makeover also:
Rebased on 7.3.16 Kernel
Removed F2FS support to prevent "mishaps"
Added ability to backup & restore Preloader partition
https://drive.google.com/open?id=0BwdRTuyj12_yU19qQWNra1o3alk

Hi, great work. Can you make twrp 3.0 for our beloved xrmn2? It's has been released: http://www.xda-developers.com/twrp-3-0-0-has-arrived/

If you don't like the extensive partition listings in the original, I have altered the fstab files and repacked so you see only the necessary partitions for each function. Other than that, it is the same.
Now only one version with all the partitions you need and none that will get you into trouble

Thank you for sharing!

jajk said:
TWRP3.0 is here. All credit to Jeminni.
Unpacked, examined and tested to be fully functional and free from malware by me. This is totally unaltered - just mirrored here for convenience.
Click to expand...
Click to collapse
Hi, great work...thanks alot, just keep peaking !
Can we get informed by you what kind of malware plant in this, does it method by flashing any zip using it or by restore/backup process?
Anyway, u're whispering somethin' th
at we cant wait ur MM builds desperately...

@Adam Hui Maybe you misunderstood, I checked that there is no malware in the original by unpacking it and looking at the code. I also tested every function does not break the phone and works correctly. I am assuring other users that maybe cannot examine the contents that it is clean.
My modified version only rationalizes how partitions are presented in Recovery. Try the original and you will understand the need to alter the partitions displayed.
MIUI based on MM is in beta testing for ReNo2 already (I am not one of the beta testers)
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1

jajk said:
[MENTION=4666525]
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
Click to expand...
Click to collapse
Hey man, pls washout that greyed info.
Do u mean there'll be a locked bootloader in miui MM ?
U should inform us if u knew it at first time !

Hi, Is there a MultiROM / dualboot feature included in this release?
Thank you to jemimi for the dev work and thank you in advance for any reply.

@MiSteven No dualboot in this one and I haven't seen one for our phone (not that I have been looking)

New version 3.0.0-3

jajk said:
New version 3.0.0-3
Click to expand...
Click to collapse
Is this update of jemmini's TWRP_3_ReNo2.zip from 4pda.ru?

@sanceliken2000 No it is original.

jajk said:
@sanceliken2000 No it is original.
Click to expand...
Click to collapse
Thanks for the answer. Could you please tell me if i could flash it directly with twrp 3 jemminis' in order not to do the procedure with fastboot?

@sanceliken2000 Just flash it in your existing TWRP (it is a flashable zip)

Interface look good, old backups need to be re-backup! Thx~

addro said:
Interface look good, old backups need to be re-backup! Thx~
Click to expand...
Click to collapse
If you have backup made by jemmini's TWRP3 it is not necessary to re-back. The new one understands that backup.

@faorekh It surely is. I look for compatible donors since we have no official build for our device.
The only thing that changes from previous TWRP backups is the folder name where it is stored. If needed, rename the old folder to /TWRP/BACKUPS/Redmi_Note_2 and TWRP will see it or just move the old backups into the new folder when it is created on first new backup.

There is the signature "Lenovo/full_aio_otfp/aio_otfp" inside recovery. Is this recovery port from recovery-twrp-3.0.0-3-k3.img of Lenovo K3 Note?

This version works great for my rmn2 prime.
Sent from my 2014817 using Tapatalk

I flashed this recovery yesterday through my twrp 2.8.7.
After updating to TWRP 3.0.0-3 I got messages like this:
Code:
This package is for "hermes" devices; this is a "".
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/external_sd/!Flash/twrp287.zip'[/COLOR]
After that I used the fix in this thread to make my old recovery flashable again. Now everything works fine again, but you may want to look into that, so others won't have to get similar headaches as me.
Little note: I spent 3 hours trying to make this work under OSX El Capitan, but it seems like OSX can't create flashable zips. I used a windows partition to zip the files and everything worked fine.

[HOW-TO] Convert to F2FS on Nexus 6 (ALMOST - Any Rom)

BE WARNED - THIS WILL ERASE EVERYTHING ON YOUR PHONE. DO NOT ATTEMPT THIS IF YOU HAVE NOT MADE A BACKUP AND/OR ARE NOT READY TO REINSTALL EVERYTHING ON YOUR PHONE FROM SCRATCH.
Credit goes to bbedward for his initial thread regarding this concept.
STATUS:
2017/01/08 - Not liking the performance of my Galaxy S3, so I've ordered a new phone (Huawei P8 Lite) for $58 from eBay! Supposedly brand new. I figured I'd have to give it a try just to see. Once I set this phone up I'll start tinkering with my Nexus 6 again. Phone should arrive around 17 Jan!
FOCUS:
Getting F2FS on ANY ROM, but for my purposes, I'm focused on getting F2FS with Flash Kernel to work on Nitrogen OS (if this can be done, then it can be done with any ROM!)
BASICS:
- Need recovery & kernel that support f2fs (tools + kernel driver version must match or be compatible - not sure what the specifics are yet)
Latest New Info:
- The Flash has said that his kernel and crDroid work with F2FS (I haven't tested it myself yet - this version of crDroid actually specifies F2FS support)
2017/01/08
- Found this thread by NABENDU1. It's for Nexus 4, but it gives some good insight on how F2FS works.
- @vprasad1 found another working combination (post #15) - franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Explaining a few details:
The issue here is that the exact version of F2FS tools included in most modded recoveries isn't actually specified (that I have found) and the version of tools that end up in the ROM (/system/bin/), which come from the recovery unless built into the ROM, must be compatible. One of the following is true (not sure which one yet):
- the F2FS tools version must be the same or greater than the kernel driver support version
- the F2FS tools version must be the same or less than the kernel driver support version
- the F2FS tools version must match the kernel driver support version
Given that The Flash is consistently including the latest F2FS support in his kernel, and since I've had the most trouble getting F2FS support to work with his kernel and other ROMs that technically don't support F2FS (using bbedward's method mentioned above - link to thread included) I'm inclined to think that the F2FS tools must be the same or greater version compared to the kernel driver support, though I have no way of confirming this yet. Hopefully I'll have different luck with Flash Kernel v1.7!
========
I used:
- Nexus Root Toolkit v2.1.9
- Nitrogen OS 2016-11-19
- MagiKernel v1.1 Stable-1023
- TWRP 3.0.2-0 (modded by xanaxdroid - thread is here)
(TWRP v3.0.2-0 by xanaxdroid mirror) - the original link is down.
I'll take these down if xanaxdroid asks. I have yet to hear from him...
Steps for clean install (and initial install of F2FS recovery / conversion to F2FS):
1) revert to stock (Nexus Root Toolkit)
2) flash recovery with f2fs support (Nexus Root Toolkit)
3) boot into recovery on device
4) full wipe device (normal wipe)
5) convert /cache & /data to f2fs
6) copy over desired kernel and rom to /sdcard
7) install rom & then kernel
8) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
9) reboot
========
When changing ROMs/kernel (F2FS recovery already installed):
1) boot into recovery
2) do full wipe (f2fs should have stayed from the first time)
3) install rom & then kernel
4) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
5) reboot
========
More semi-lengthy explanation about fstab:
bbedward suggests a difference in the fstab as being the primary suspect causing the difference in compatibility. Here's the only difference I could find that seemed to be relevant:
- the fstab that worked (MagiKernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
/devices/*/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
- the fstab that didn't work (Flash Kernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
*block/sda* auto auto defaults voldmanaged=usbdisk:auto,noemulatedsd
Both fstab files did clearly have the lines needed to mount /data and /cache as f2fs, but they were identical.
NOTE: I also tried TWRP v3.0.0-0 (by xanaxdroid) with Flash Kernel and still no dice. I'm a fan of Flash Kernel since it's my first custom kernel I've played with. I hope to be able to use it some day with Nitrogen OS! Until then, thanks MagiKernel! (maybe I'll convert??? ) <- MagiKernel development has halted for now
========
What I've tried before:
All of the following implies that I've used the previously mentioned adb commands to copy over the f2fs tools and set the proper permissions.
In my experience, it seems that f2fs requires just the right combination of kernel + recovery. For example I used Nitrogen OS (2016-11-19) + Flash Kernel + mod TWRP 3.0.2-0 and it hasn't worked for me, but Nitrogen OS + MagiKernel + mod TWRP v3.0.2-0 did work. The failure for f2fs to work with Nitro OS + Flash Kernel is very reproducible, as is the success with Nitro OS + MagiKernel. (Again using TWRP v3.0.2-0 modded by xanaxdroid).
Keep in mind that the developer of Flash Kernel (developed by The Flash) has tested his kernel with crDroid (a CyanogenMod base ROM) and it worked for him, but I don't know what version of modded TWRP he was using and what version of f2fs tools were in that recovery. From what I've noticed, there seems to be a fundamental difference with CyanogenMod based ROMs when it comes to f2fs support, either that or there's just a version mismatch of f2fs tools between certain recovery + kernel combos. I don't know enough to understand the difference yet, but it is clear that just because a kernel claims to support f2fs doesn't mean that it will work with any ROM, even if you follow bbedward's tutorial mentioned at the top of this post.
The kernel and the recovery must work together (as in what version of mkfs.f2fs / fsck.f2fs supported by kernel & recovery must match (i think - thanks to bbedward again for this info)). The main issue here is that most modded recovery zips/imgs (that I have found) don't list the version of f2fs tools they have. On the other hand usually you can see this info on the main page of any given kernel developer.
I haven't found any specific rhyme or reason yet, but for those looking for Nitrogen OS (2016-11-19 - Android 7.1 - Nougat) + f2fs, this will help you.
NOTE: I'm a clean-freak, so I enjoy clean flashes, so my instructions are geared toward clean flashes, not dirty flashes. Having said that, doing this with a dirty flash is possible, but it will depend on the ROM/kernel you choose as to the details in how you upgrade/switch the ROM/kernel. Done properly, you should only have to switch file systems once and forego any future wiping of your /sdcard or internal storage.
========
NOTE : You'll know your recovery + kernel combo isn't working right when it takes longer than usual to get off the bootloader screen and start with your ROM's animation boot screen. If it's taking too long, you're probably having everything converted back to ext4.
*** WARNING *** WARNING *** WARNING *** WARNING ***
DO NOT INTERRUPT THIS PROCESS DURING BOOT. If you do then you'll render your /data partition inaccessible. It's still fixable with Nexus Root Toolkit > revert to stock, but that's a pain and it takes a while.
This OP will be updated as new info is uncovered!

Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Sent from my Nexus 6 using XDA-Developers mobile app

ozzmanj1 said:
Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Click to expand...
Click to collapse
Thanks for the feedback!
I'm still researching a way to get Flash Kernel with Nitro OS + f2fs. I have some ideas. I'll update the first post with any new findings.
Edit: unfortunately MagiKernel is dead. So ill be hot on another trail soon. Also MagiKernel isnt as good as Flash out-of-the-box in my experience so far.

ozzmanj1 said:
Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Click to expand...
Click to collapse
I actually just tested the link to MagiKernel on my PC and my phone (on XDA Labs) and it worked fine. Are you using another (older) version of XDA forum viewer?
EDIT: OP updated. The "issues" we all run into is a version mismatch between RECOVERY & KERNEL mostly. As long as RECOVERY & KERNEL f2fs tools match, then you can copy over (mkfs.f2fs & fsck.f2fs) from /sbin/ to /system/bin/ and get any ROM to be compatible with F2FS.
EDIT: modified links and removed "" in URL tags. The quotes were necessary for proper display in the XDA Labs app, but not compatible with XDA Legacy app. I've switched to use XDA legacy!

Will this fix low battery throttling and video recording

PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
LOL, no.
This won't "fix".... ANYTHING.
In fact, this will very likely BREAK things.

Lol how so

No not breaking things here ... Not any more than usual tinkering under the hood... I'm just trying to flush out bbedward's old thread with some more info...

PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
To give you an answer, no it won't. This info will only "possibly" help you get a ROM to run on f2fs that was not initially designed to do so.

@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...

TheArkive said:
@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...
Click to expand...
Click to collapse
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?

ozzmanj1 said:
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?
Click to expand...
Click to collapse
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd

TheArkive said:
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd
Click to expand...
Click to collapse
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app

ozzmanj1 said:
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the news! I'll be checking that out as well.

FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Code:
mount | grep f2fs
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.

Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.

zelendel said:
Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.
Click to expand...
Click to collapse
Was that in response to my post???
Sent from my SM-N910T using Tapatalk

vprasad1 said:
FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.
Click to expand...
Click to collapse
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!

TheArkive said:
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!
Click to expand...
Click to collapse
Just a quick link I came across. Not sure if it's useful but as it pertains to f2fs I thought I'd share.
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my Nexus 6 using XDA-Developers Legacy app

What is F2FS
Can Ya Here Me Now