yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] BitOBSessiOn:
Totally experimental.. ATM this is basically a "proof of concept" for proper F2FS support.

Please, don't take risks if you are not sure you're doing... This can totally erase your system, data, etc... (make a full backup before, etc...)

I've sucessfully tested formatting /cache and /data to F2FS. This should work on any Shield Tablet model (properly updated, at least MM).

Downloads:

Latest TWRP with F2FS support available here.

Kernel with proper F2FS support like BitO-K8 and BitO-K10 / KX10 for N

F2FS fstab injection tool (to replace fstab.tn8 in current ramdisk) for M (updated version for N here)

Instructions:

Flash TWRP (via fastboot, rashr, o r similar if rooted ) and boot into recovery

Advanced Wipe, select partition (data, cache), and select change FS to F2FS

Flash compatible Kernel zip from TWRP

Flash F2FS injection tool (this replaces fstab.tn8 in ramdisk with an updated version with F2FS support)

Reboot

WARNING NOTES:

If you format /system with F2FS, you'll need to reflash your ROM (ROM bust support install in F2FS /system WITHOUT re-format to EXT4...) (TESTED, not working ATM with standard restore from TWRP)

If you format /data you need to restore a backup (previous in TWRp...), or reconfigure your whole system (TESTED)

You can safely format /cache to F2FS following instructions (TESTED)
[Shield Tablet Android Development] skooter32:
Ok data and cache is f2fs for stock 1.3 system won't boot on f2fs
[Shield Tablet Android Development] BitOBSessiOn:
Do you mean you've tested successfully /cache and /data in F2FS but you got error with /system ? Thx
[Shield Tablet Android Development] skooter32:
Yes cache and data is at f2fs but when system is f2fs it don't go by Nvidia sign and switches off
[Shield Tablet Android Development] BitOBSessiOn:
Ok, that's right, tested... thx ! Only /cache and /data with F2FS atm...
[Shield Tablet Android Development] skooter32:
Great work tho Bit0 was gonna say tho about this Linux kernel flaw cow or whatever are u gonna be patching ur kernel with the coding?
[Shield Tablet Android Development] skooter32:
Twrp screenshots
[Shield Tablet Android Development] drewski_1:
Nice work Bit & co! :svetius:

From what I've seen, there's no benefit to f2fs on /system because in normal operation it is read-only and f2fs improves more the write performance.
[Shield Tablet Android Development] m0nt3s:
Awesome work Bit! I found a couple fix it's to make your TWRP work flawlessly. First your fstab file has an incomplete line, I've been testing with this attached fstab for the recovery successfully if you want to take a look. you can also copy it into the ect folder as recovery.fstab, your twrp.fstab is perfect. I also had to modify my boot.img with the same fstab.tn8. The only way I was able to get /system /data /cache to all format and boot was to re-install a rom with this edited into the updater script.

#--INFORMATION

ui_print(" "); ui_print("INSTALLING f2fs ROM STARTED");

#--PREPARE DEVICE PARTITIONS

ui_print("-- Preparing device partitions");

package_extract_dir("META-INF/SCRIPTS", "/tmp");

run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");

run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data");

run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/CAC", "/cache");

run_program("/sbin/fsck.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");

run_program("/sbin/fsck.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data");

run_program("/sbin/fsck.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/CAC", "/cache");

run_program("/sbin/mount", "-t", "f2fs", "/system");

run_program("/sbin/mount", "-t", "f2fs", "/data");

run_program("/sbin/mount", "-t", "f2fs", "/cache");

delete_recursive("/system");

ui_print("-- Wiping all user data files");

set_metadata("/tmp/wipe.sh", "uid", 0, "gid", 0, "mode", 0777);

run_program("/tmp/wipe.sh");

#--INSTALLATION

ui_print("-- Extracting system & data");

your kernel and fsf2 utils are perfect, with out your tremendous effort f2fs would still only be an far off idea, congrats and we did it!
[Shield Tablet Android Development] m0nt3s:
[MENTION=6411851]BitOBSessiOn[/MENTION] since you're the man, I was wondering if you could replicate some of the features of http://xdaforums.com/oneplus-one/development/lightning-kernel-omni-rom-v01-t3245895

into your kernel for us. with minimal changes from https://github.com/nikhil18/lightning-kernel-bacon do you think you could add some of the features? with minimal changes I think you could add the governors to your kernel and the optimizations
[Shield Tablet Android Development] GuyInDogSuit:
Does this work on stock? I'm gonna try it out anyway, but yeah...

Yup, it works on stock.
[Shield Tablet Android Development] BitOBSessiOn:
Latest kernel with full F2FS support (BitO-K8) and tool for fstab.tn8 updating:

http://xdaforums.com/showthread.php?p=69718234
[Shield Tablet Android Development] BitOBSessiOn:
TWRP MultiROM+F2FS v3.0.2 (008)

Available here.
[Shield Tablet Android Development] k3wlar:
BitOBSessiOn : I take it with a version of the K8 (kx8) can use on / cache / data and / system as well?
[Shield Tablet Android Development] sarmentoedu:
this work on shield tablet k1?
[Shield Tablet Android Development] BitOBSessiOn:
/system depends on specific ROM (it doesn't work on stock), but usually you only get a performance boost with /data and maybe /cache.
[Shield Tablet Android Development] BitOBSessiOn:
Yes, it should.
[Shield Tablet Android Development] BitOBSessiOn:
Twrp 3.0.3 (20121220)

TWRP 3.0.3 (MROM modded) available here.
[Shield Tablet Android Development] Son-j:
For those who are using F2FS, do you still experience the occasional and annoying lagging with your shield tablet? Thanks in advance :)
[Shield Tablet Android Development] BitOBSessiOn:
TWRP 3.0.3-1 (20170118) (F2FS support updated)

Latest TWRP 3.0.3-1 with F2FS (updated) support available here.

It's recommended to use one kernel with also updated F2FS support, like BitO-KE8-003.

EDIT: F2FS format option fixed. Link updated
[Shield Tablet Android Development] liam_davenport:
Flashed latest TWRP but don't have F2FS under advanced wipe :crying:
[Shield Tablet Android Development] BitOBSessiOn:
Ummhh... Bug. I will revise. Thx!
[Shield Tablet Android Development] BitOBSessiOn:
This new version should fix.

EDIT: Link in original post updated.
[Shield Tablet Android Development] liam_davenport:
Thanks bro :good:
[Shield Tablet Android Development] hello2ew:
Is there any way to have root alongside F2FS? I understand that some patch must be included in the kernel according to arter97's post... but in the meantime do the latest SuperSu systemless betas work with F2FS? Or must I install the system mode version?
[Shield Tablet Android Development] BitOBSessiOn:
You shouldn't have any issue, just flash latest SuperSU or Magisk and profit.
[Shield Tablet Android Development] hello2ew:
Heres what I did (while on stock 1.5):

1) Flash latest F2FS recovery

2) Change data and cache partition to F2FS

3) Flash Kernel

4) Flash injection tool

5) After rebooting and setting up, I rebooted back to TWRP

6) Flash SuperSu v2.79 SR3

From that point, the tablet just doesnt boot at all. I read that SuperSu and F2FS dont go well together, and a kernel fix has to be implemented as recommended by arter97 in this post. So how do you get the latest SuperSu to work with F2FS?
[Shield Tablet Android Development] BitOBSessiOn:
Change point 6) by flashing Magisk 10.2 (and install phh supersu manager from play store).
[Shield Tablet Android Development] lupick:
Restoring system partition on ext4 file system I had the following error

Extractarfork ended with error 255.

BTW the restore was successful and I was able to boot.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Shield Tablet Android Development] BitOBSessiOn:
F2FS support updated for N

TESTING NEEDED !!!!

F2FS injection tool updated for N.

Newer BitO-K9/KX9 for N also available.

Download links updated in OP.
[Shield Tablet Android Development] primaleph:
I followed this procedure with the new injector, but can't get it to boot. Even Without Magisk and superuser.
[Shield Tablet Android Development] BitOBSessiOn:
Which partition for...? Have you tried only cahe and / or data?
[Shield Tablet Android Development] primaleph:
Cache and data only.

Also data by itself.
[Shield Tablet Android Development] tikizondo94:
Same here. Tried both data and cache and also only data. No magisk or SuperSU installed. Just f2fs injector and latest K9 kernel. Just bootloops.
[Shield Tablet Android Development] BitOBSessiOn:
F2FS kernel support must be revised... Thx
[Shield Tablet Android Development] BitOBSessiOn:
F2FS support revised in BitO-K10 / KX10

More info here (BitO-K10 / KX10-001) .
[Shield Tablet Android Development] dape16:
Thanks for your work with F2FS and your kernel.

I have a strange problem. I followed your instructions for formatting data and cache partitions and after flashing the injection tool I got stuck at the Nvidia boot screen. I can boot to bootloader and run fastboot commands without problem. But I can't boot to recovery, stock or twrp.

I have flashed the latest recovery image which always has solved soft bricks like this before but I still can't get it to boot to anything except bootloader. What have I forgot? :)
[Shield Tablet Android Development] BitOBSessiOn:
Ummmhh... Have you used referred twrp in OP and latest BitO-K10 and injection zip for N?

Anyway, I must rebuild newest twrp-mrom v3.1 with latest BitO-K10 ...
[Shield Tablet Android Development] beitme:
So it's not ready to work yet with k10 kernel?
[Shield Tablet Android Development] BitOBSessiOn:
Sorry, indeed you shouldn't have any problem with latest TWRP-MROM.
[Shield Tablet Android Development] Son-j:
I've got all the necessary files and I've read the instructions and warnings. I'd like to clarify a few things:

1. I reverted back to stock kernel but rooted with latest supersu, do I need to unroot before doing this?

2. I plan to reformat cache and data. I take it that it's safe to restore data from in TWRP before rebooting? If I didn't restore, data is literally reformatted and so it's like I'm starting from scratch? (If I'm saying the same things in the warning in the OP, let me know ^_^)
[Shield Tablet Android Development] drewski_1:
1. You will unroot with stock boot and format of /data

2. Yes and yes
[Shield Tablet Android Development] Son-j:
Thanks!!! Ok, time to test this :)
[Shield Tablet Android Development] Son-j:
Original System: stock 5.1, SuperSu rooted

Backed-up boot/system/data

AnTuTu score: 92k+

My observations so far:

1. Formatted cache/data to f2fs (then flashed kx10-02, N-injector), then restored my data via TWRP, then wipe cache/dalvik

a. My game data was gone, the contents of SD card 0 was literally wiped out and only basic folders were restored. I noticed that when I factory reset then do a restore, this doesn't happen.

b. I didn't lose root

c. rebooting to recovery caused a bootloop

2. Went to recovery, restored /system /boot /data caused bootloop

3. Went to recovery, formatted /data to ext4 and reboot, still bootloop

4. Went to recovery, verified that /cache is f2fs and /data is ext4 then flashed kx10-2, then injection - finally boot - I figure that f2fs only works with kernels with f2fs support and that the stock kernel of 5.1 doesn't have f2fs support. But my game data and other app data are still gone

a. AnTuTu scores vary from 72k-87k

Next Step: will attempt to go back to original setting.

The device feels snappy, but I'm bothered by the decrease in performance. Did anyone observe and measure performance boost? Maybe I did something wrong. I'm welcoming comments and suggestions :) in any case, thanks for working on f2fs support! ;)

---------- Post added at 07:47 PM ---------- Previous post was at 07:37 PM ----------

I take it back! My game data weren't lost - I just needed to restore some obb files of my games and voila, my progresses were all there! :)

I feel like even with just my /cache formatted to f2fs, opening and shifting apps seemed much quicker/snappier. Now I'm thinking of reformatting my /data back to f2fs again. :P

But the decrease in AnTuTu makes me quite paranoid. I'll try playing with just /cache in f2fs for the moment. :)
[Shield Tablet Android Development] gokhujee:
So i got this to work,

Basically i formatted all to f2fs

Then i installed magisk where it installed root to

Then i installed the kernel and them injected

Then rebooted and now it working perfectly no complaints
[Shield Tablet Android Development] beitme:
Couldn't get it to work

Rom: lineageos 13.0

Kernel: k10

* directions don't state when rom should be installed.

A) if I installed rom before kernel and injector, after reboot TWRP would warn no OS is present. Indeed it seemed to have been wiped.

B) if I installed rom after kernel and injector, the boot logo would appear but never load the OS.

Also, I couldn't install gapps (pico opengapps) along with the rom. TWRP would respond with error message that there wasn't enough disk space on the partition.
[Shield Tablet Android Development] BitOBSessiOn:
Latest TWRP-MROM (v3.1.0-2) with F2FS available

Available here.

*With latest F2FS support (BitO-K10 based)
[Shield Tablet Android Development] Drims75:
You have made a lot of work. Everything works remarkably, a post-pitchfork your kernel with KX10-001, an insertion stock the android 7. In an antutu of 98300 balls.

You can make that the sections mmcblk0boot0 and mmcblk0boot1 were displayed?
[Shield Tablet Android Development] BitOBSessiOn:
What do you need this for ... ? Thx
[Shield Tablet Android Development] BitOBSessiOn:
TWRP-MROM v3.1.1 / MultiROM v33 (2017.06.21) - UNOFFICIAL

Available for testing here:

TWRP_3.1.1-2_multirom_shieldtablet_20170621-01.img

multirom-20170621-v33-UNOFFICIAL-shieldtablet.zip

*Remember to flash zip for proper touch support after multirom.zip if you need it.
[Shield Tablet Android Development] daeymon:
Minor issue with TWRP. When booting into recovery, sometimes does not initialise beyond the Nvidia logo and the device reboots instead. Using MM stock (4.4), with K8 Kernel.
[Shield Tablet Android Development] primaleph:
I just had an issue with restoring a backup in this version of TWRP.

My /data partition was formatted F2FS. I backed it up to my MicroSD card. When I went to restore it, it got as far as 128 MB and then returned the error "extractTarFork() process ended with ERROR:255".

I would really like to restore this backup. What could I try?
[Shield Tablet Android Development] Spexxos:
How do I get it to not re-format the partition?
[Shield Tablet Android Development] filjusz:
This error code mean Your backup is bricked, tried almost everything to restore data with no succes.
[Shield Tablet Android Development] primaleph:
When I install a new LineageOS update, do I need to reflash the F2FS injector in addition to the kernel??
[Shield Tablet Android Development] BitOBSessiOn:
Most probably is yes, because system (and boot) files become overwritten and I'm afraid that this includes fstab...
[Nexus 6 Q&A, Help & Troubleshooting] belek1979:
Is it OK to switch between Android 6 and Android 7 in TWRP 3.0.2.0 backups?

I would like to use both Androids on my phone until Xposed will be ready for Nougat, but I'm afraid of file structure, partitions and so on.

Both Androids are rooted and no encryption.

Restore backup of Android M won't mess with Nougat will it?
[Nexus 6 Q&A, Help & Troubleshooting] HueyT:
No problem provided u have N bootloader to use N ROMs. N bootloader is backward compatible. Nutty Nexus thread has link to latest N bootloader and radio combined in one zip to be flashed in TWRP 3.0.2.0 before flashing N roms
[Nexus 6 Q&A, Help & Troubleshooting] belek1979:
Thank you for your answer.

I'm going to update from ADB (factory image):

1 fastboot flash bootloader

2 fastboot flash radio

3 fastboot restart-bootloader

4 fastboot flash boot

5 fastboot flash system

6 entering twrp recovery from bootloader

7 flash SuperSU (root and no encryption)

TWRP doesn't backup BL or radio?
[Nexus 6 Q&A, Help & Troubleshooting] Dopamin3:
Why not use MultiROM so you can actually switch between them and not wipe/restore all your partitions each time you want to switch back and forth? I think it should work between MM and N so long as the kernels in each ROM are kexec patched.
[Nexus 6 Q&A, Help & Troubleshooting] HueyT:
TWRP only backs up \system, \data, \boot, \recovery, \EFS (\cache also but who cares)

You could flash like that but you could also just flash debloated N rom from tupac4u or DanvH straight from TWRP (after flashing N bootloader and radio zip).

Multi-rom can be tricky for Noobs

EDIT: Here are the useful links: N radio and bootloader in 1 flashable zip in TWRP by RatchetPanda: https://www.androidfilehost.com/?fid=312978532265362066

Here is tupac4u latest debloated N rom:

https://mega.nz/#!e9JDyRRY!mJl2CJeWTmlhELPbHdHdzT1GHE15awdlqd3Q4sIED70

(needs MEGA app to download or use "desktop" emulator on mobile browser to download)
[E 2015 Q&A, Help & Troubleshooting] aamszia:
XT1526 Surnia Sprint 6.0 Firmware for RSD ????

anyone have link to download ???
[E 2015 Q&A, Help & Troubleshooting] IIDarkII:
I have a xt1526 but i don't know how to backup it. If you tell me. I'd can help u
[E 2015 Q&A, Help & Troubleshooting] lumentiz:
hi, I'm new for here and can't post links, just copy and paste

this is the latest official rom for xt1526 sprint/boost

www.filefactory.com/file/4kz8usm92l7p/XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.12_cid9_subsidy-DEFAULT_CFC.xml.zip
[E 2015 Q&A, Help & Troubleshooting] IIDarkII:
Ahhhh, s*** , my xt1526 is Marshmallow. haha. Guy, you have to tell what API have your phone guy.

---------- Post added at 12:33 AM ---------- Previous post was at 12:33 AM ----------

That's for Lollipop. Not for Marshmallow
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] sylvantrails:
I've got a Samsung Galaxy Note 10.1 (2014 edition) SM-P607T tablet. It has not been activated on the T-Mobile network, just used as a WiFi device. Stock Android version 5.1.1. Never been rooted

About a month ago, it stopped charging. It's a couple years old now, and I purchased it factory refurbished (a couple years ago), so I assumed it was the battery. Took it in and they replaced the battery (which was a fiasco in it's own right, but I won't go into that here). But, that did not fix the issue. If I've got the tablet on, it will show that it is charging for about 30 seconds, then the battery shows not charging (either no indicator on the battery or a red "x"). If the tablet is OFF, it seems to be charging just fine.

What I've done:

--Replaced the charging port ribbon--the USB connector was actually broke in one corner, so I thought that was the issue.

--Reset the battery-- a couple of times

--Factory Reset the tablet--a couple of times

--Called Samsung Technical Support. They think it's a software issue, and had me call T-Mobile (since it's a T-Mobile tablet)

--Called T-Mobile. The guy walked me through the power/volume down reboot thing. I get the "Custom ROM install" thing. (Sorry, don't have the exact wording in front of me...) The "this may have been rooted" thing. Which *I* have not done. T-Mobile can't help me anymore.

--Did some more searching and got information to download KEIS. Downloaded it to my Windows 10 laptop, followed the instructions, plug tablet into the USB port and....

-- Get the "the USB device malfunctioned, Windows doesn't recognize" blather. Researched THAT, updated USB drivers on my computer and STILL get the same notice. Powered the computer down, unplugged it, took the battery out, put battery in, plugged it back in, powered up and, still...no go. Still doesn't recognize it.

So, now what? Is there a way "unroot" a tablet without hooking the tablet up to a computer, ie, via MicroSD? I suspect that if I could get it back to an "unrooted" state, I might be able to get T-Mobile's help proper. Any other suggestions as to what to do to get this silly thing running properly again?

I've got someone on another forum saying my battery connector is broke and needs soldering, but it charges fine powered off...

I miss my tablet. I've been using my son's old one and it's screen is too small and it doesn't use the S-Pen and...
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Toneman07:
Have you gone into the device manager on your computer and told it where to manually locate the drivers?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] sylvantrails:
I think so.

Anyway, I had ordered a replacement tablet and it came yesterday and it has the option to be activated on Verizon, should I so choose, so I am going to get rid of this tablet and not worry anymore about it.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Frankenbiker:
Mine does the exact same thing.

I think the actual problem is that the tablet and charger need to be able to "talk" to each other, and if the USB port is fubar'ed, they can't talk.

This tablet has some VERY strict charging requirements; every thread I've been able to dig up all but DEMANDS you use the charger that came with the tablet. The battery is SO F-ING HUGE that most chargers just can't keep up. (Look around at the battery mAH ratings on any other tablet; they're usually in the 5000-6000 range; the P607T is nearly 9000.)

(you mention that you bought another tablet; I'm posting this so that others might keep up...)

-blaine
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] sylvantrails:
I had this problem even after changing out the USB port, unfortunately. (Actually, it wouldn't charge at all with the broken USB port, but would with the new one...just only when off.)

I had it work just fine for nearly 2 years using a Samsung charging cord and appropriate plugs...they have to be 5 Volt plugs, not 2.x Volt plugs. Not-Samsung charging cords were a hit or miss...with all of our devices...so it was just easier to buy Samsung cords. ;)

Oh, and I replaced it with another 2014 Note, just a Verizon one instead of a T-Mobile. (Not that THAT matters too much as I don't currently have it activated...and will probably activate it on ...gasp... Tracfone! :D
[Tilt, TyTN II, MDA Vario III General] kpaznb0i:
Main point of all this is: What theme are you cube users using and where can I get it?

Story:

So I have a tilt and was really excited to get the cube working on it. I got all the necessary cabs and what not from duttythroy ( http://xdaforums.com/showthread.php?t=336482 ). The home plug in was working everything was there and I was so happy. The only thing missing (since I am using the stock att rom) was the htc grey/black theme to match the cube. So I found this one on google ( http://www.freewarepocketpc.net/ppc-download-black-wm6-theme.html ). Looks good right? Well after installing, that is where everything went wrong...

Now my tilt keeps freaking out by constantly flashing boxes. It looks like they are minimizing boxes starting from the entire screen and then into the middle. It also seems like its randomly clicking things when it sometimes does this too. I thought maybe it was the touchflo cube stuff so I deleted that all. Still does. Deleted the theme. Still did not fix the problem. It does the box/freaking out thing even more when i play with the wheel on the side.

I want to say it was the theme but I have no idea. I am going to hard reset the device anyway to get all the bloatware off so if the solution isnt found its not a big deal. I am just wondering what all you cube users are using for your theme and if you could point me in the right direction to it.
[Tilt, TyTN II, MDA Vario III General] stizzswizz:
I have Dutty's ROM and when I enabled "animate windows" it did the exact thing that your talking about. It was in "advanced settings" I believe, but that might only apply to the ROM I have, it's probably a registry setting.
[Tilt, TyTN II, MDA Vario III General] kpaznb0i:
GENIUS

You are a GENIUS my friend. After disabling window animation in kaiser tweak and after a soft reset the weird box thing problem goes away! Thank you so much. You just made my day... I would have never figured it out :D