Database Develop

Data partition F2FS on stock?

Hell, I've decided to restore stock on my Moto and sell it, as I'm pretty sure I'm going to settle with the OnePlus One I also got with their offers.
I think I recall while flashing ROMs for this device I had to reformat Data to EXT4, but now when I go to change the FS again I don't have option for F2FS.
Could one of you please load up recovery, go into Wipe > Advanced Wipe > check "Data" choose "Repair or Change File System" and verify what the line "current file system" says for you?
Would be much appreciated.

Shemploo said:
Hell, I've decided to restore stock on my Moto and sell it, as I'm pretty sure I'm going to settle with the OnePlus One I also got with their offers.
I think I recall while flashing ROMs for this device I had to reformat Data to EXT4, but now when I go to change the FS again I don't have option for F2FS.
Could one of you please load up recovery, go into Wipe > Advanced Wipe > check "Data" choose "Repair or Change File System" and verify what the line "current file system" says for you?
Would be much appreciated.
Click to expand...
Click to collapse
Mine says EXT4.

My data partition is on F2FS on stock lollipop.

sivarticus85 said:
Mine says EXT4.
Click to expand...
Click to collapse
Which partition did you check?

divergens said:
My data partition is on F2FS on stock lollipop.
Click to expand...
Click to collapse
I wonder why TWRP does not have option to change to F2FS, I'm using 2.8.4.1

Shemploo said:
I wonder why TWRP does not have option to change to F2FS, I'm using 2.8.4.1
Click to expand...
Click to collapse
I just tried booting TWRP 2.8.4.0 and I don't see an option for F2FS either. Was this available before in older versions of TWRP? I never bother to switch from the stock recovery to TWRP at any point.

Shemploo said:
Which partition did you check?
Click to expand...
Click to collapse
You asked for the Data partition.
I brought it up in the TWRP thread. Maybe someone there can answer this for us.

sivarticus85 said:
You asked for the Data partition.
I brought it up in the TWRP thread. Maybe someone there can answer this for us.
Click to expand...
Click to collapse
divergens said:
I just tried booting TWRP 2.8.4.0 and I don't see an option for F2FS either. Was this available before in older versions of TWRP? I never bother to switch from the stock recovery to TWRP at any point.
Click to expand...
Click to collapse
Yes, it was in a previous version, I remember changing partitions cause of ROM not working.
Its interesting that both of your partitions are different. Did neither of you change them?

Shemploo said:
Yes, it was in a previous version, I remember changing partitions cause of ROM not working.
Its interesting that both of your partitions are different. Did neither of you change them?
Click to expand...
Click to collapse
I never purposefully changed partitions via TWRP, in fact I never have used TWRP on my Moto X yet. All the flashing I have done was with fastboot.
Now that you mention it, I remember my data partition being EXT4 back in kitkat. I don't know if it changed because of lollipop. I did flash a lollipop image from motofirmware at one point. However, then I went back to kitkat using Motorola's official kitkat image and took the OTA to lollipop.

Yeah I never purposefully changed it either. Twrp just doesn't format it to f2fs like it should. I wonder if doing a factory reset from within the stock recovery will revert it back?
Edit: Yeah that did it. Stock recovery reverts it back to f2fs. Verified by checking it twrp again afterward. That's the only way to get back as of right now.

Ha! - I got the same thing, I booted the latest TWRP and checked the partition, it's listed as F2FS, it would seem that 4.4.x is EXT4 and the upgrade to Lollipop changes is to F2FS, very interesting.
UPDATE: It looks like the option to change FS to F2FS is there when you install a theme, I got it under TWRP Materiel theme, but it seems that this might just be a button designed in case the function is introduced as it actually does not convert the FS.
UPDATE2: After loading the Material theme to get the Change FS to F2FS, the log says "mkfs.f2fs binary not found, using rm -rf to wipe"
Seems something is missing from the latest TWRP release?

I think twrp don't have f2fs because its not really cross platform mountable. Ext4 can be mounted easily with windows, Linux or Mac so it makes things easier for "devs", " tweakers" to just have ext4 support.

CyanogenMod 13 disk encryption and TWRP

I'm running TWRP 3.0.2 with nightly CyanogenMod 13. I'd like to know what's the progress on fixing the bug where you can't mount the encrypted storage even if your typed PIN is correct.
I know there are a few workarounds as to updating CM (like copying the zip file to cache and flashing it), but I'd like to know if there's any progress to fix this bug.

Not for now. I tried with the last CM13 and TWRP 3.0.2-1 and the issue still there. I tried to change the password with Cryptfs too with no results. I'm afraid we only can wait and keep flashing stuff via cache folder for the moment.

Fixed!
The last TWRP version (3.0.2-2) fixes the issue.

[RECOVERY][EXPERIMENT/TEST] TWRP 3.2.1.x for TF701T

Hi, I don't post much on here but I wanted to share something with everyone since this is one of my fav tablets (before one of my drives crash and the data is lost, lol).
Disclaimer: I'm providing this AS-IS, I've been using this for about a few weeks now and while there may be bugs, it's been working for me and figure I'd share a newer version of TWRP for the TF701T. This will need some testing, I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base).
Hopefully this helps someone who loves this lil tegra transformer as much as I do!
I'll post links to source later on but to build this but if anyone wants to try;
-I used a slightly modded version of the zombi-x device tree
-tweaked the rm-wrapper (from the timduru katkiss device tree) so it references the correct includes (I was building under zombi-x 5.1 using omni twrp 8.x)
-Since the device tree was already using a prebuilt kerenel, I plugged the one from the TWRP 2.8.x kang/area51 by sdbags release
-The "rom base" folder I was building under was "zombi-x" 5.1/LP
-and the TWRP sources were from omnirom's oreo/8.x source
Here's a link to my dropbox tf701t folder, I keep a backup in the recovery folder.
I also built a 3.0.0.0 "area51" version, think I found that in the zombi-x repositories also. Both booted, roms I had installed, backups were made and restored under both however I've used the 3.2.1.x version more exetensively.
DROPBOX TF701T LINK!
Anyways, happy holidays everybody! I'll try and keep up with this post and update things when I get a chance, but for now rock on!
PS. Should be able to
Code:
fastboot boot <recoveryimagefile.img>
to test it before flashing permanently with
Code:
fastboot flash recovery <recoveryimagename.img>
PS2. Added images to post for 3.2.1.0 and the "Area51" 3.0.0.0 builds, Enjoy!
PS3. UPLOADED SOURCES! (finally, lol)
DEVICE TREE
-The device tree is still setup to use the prebuilt kernel (I compiled from source posted below this, with gcc 8.x toolchain). If using the kernel source below, use recovery_tf701t_defconfig - otherwise just make sure whatever config you run is setup to use LZMA for ramdisks here.
-Also this device tree is setup to use F2FS, I left the original ext4 fstab files included with a ext4_* prefix if anyone's curious. I'll fix that eventually and split them into 2 branches (ext4-only and f2fs).
KERNEL SOURCE
-This experimental kernel has some tweaks, F2FS support (no encryption), O/C @ ~2.5Ghz, bunch of extra governors (lionheart works nicely), but in it's base form works great for booting recovery.
Hopefully this stuff helps others bulding for this awesome lil tablet! Back to some more compilations while I got time.
UPDATE: F2FS Test (12/30/17)
-Added a recovery build that I have been running for a bit with F2FS support
-Use this with a ROM that supports F2FS, or repack a boot.img with a F2FS kernel and mod the ramdisk (edit fstab to mount /data /system and /cache with F2FS.).
-It supports the usual ext4 and other filesystems, but defaults to f2fs when using the format data and wipe commands (modded fstab on /system /cache /data).
-Also haven't had any issues formatting /cache, or touch not working with this kernel. I'll get around to a normal ext4 version and upload that as it seems to fix the /cache issues.

Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.

hitmancho said:
Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.
Click to expand...
Click to collapse
Glad it works for you too, I noticed the /cache issue also on the other TWRP 2.8.x version posted for this tablet too. One thing that I do (even on the other TWRP) is wipe the partition I want (or change its fs type) first, and if I need to touch another partition then I reboot the recovery and it works.
It's annoying, I'm currently testing building the kernel inline instead of using the 2.8.x kernel (from that other posted recovery) in the device tree. I'm using sources that I know boot, just playing with the configs to see how it plays with TWRP. I ported over the f2fs stuff from the katkiss kernel to mess around with, boots in the rom fine - so if I can get it to boot recovery then the f2fs formatting stuff should work and mount correctly.
Sidenote - one thing I notice with the 3.2.1-0 version is the screen seems to work better, I haven't had the touchscreen not responsive issue I had with the previous TWRP 2.8.x version.
Going for a coffee, I'll play around with it tonight (and remember to upload stuff to my github eventually to share). Long day of work, time to unwind

Small Update (Progress is good!)
So, took some time to dig around why it wasn't booting the recovery when I built from the same (working) kernel source I'm booting the normal android os with. Turns out, most likely due to space savings, the recovery is set to boot LZMA - turned that on in the config and that kernel now booted up recovery perfectly!
I'm rebuilding the kernel, since in my infinite wisdom, I compiled with my selinux disabled kernel - which also worked, but bombed out on any rom zips that ran anything to do with contexts/perms. Good news was F2FS worked mounting, formatting, etc.. Hopefully tomorrow I'll have a selinux friendly f2fs supporting kernel for recovery that'll work.
Random sidenote: I was eyeing the newer kernel drivers (from 4.x), If everything works as it's currently configured, I'll give try backporting the newer stuff and see how she runs. Just wanted to post a small update with some notes just in case anyone in wants to try building it themselves.

Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.

silverchairbg said:
Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.
Click to expand...
Click to collapse
I need to reformat /system and /cache only - most times. No need to reinstall apps.

You're lucky then, I always end up with errors on dirty flash and format /data also fails, so I resort to changing FS. Sometimes even this gives errors and I need to do it several times until errors are gone.

I just restart recovery and try formatting again.

AmauryRR great work! Please use the memory card of the docking station

Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).

I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base)
Click to expand...
Click to collapse
Can you, please, describe how it is working?
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Sasisco said:
Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).
Click to expand...
Click to collapse
Yes, please, more info on that!

Tf701t update
Hi AmauryRR,
Any chance you could break the process down step by step for none-IT people like me? i have tried everything but think i have to accept that this is above my pay grade .
i am especially having a difficult time with the boot loader. Indicates the following: "An unknown error occurs, which may be a network......try again later"
i can email you the screenshots as i can't seem to upload them here.
regards
rob

Can someone get me recovery work in android 4.2.2 ,
10.14.1.47 bootloader please?
"" I searched in google all recovery file can't be downloaded''

Any chance of a flashable version of this?

[HELP] [URGENT] ONLY OxygenOS not Booting up !!!!

Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file

PreciousPulkit said:
Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file
Click to expand...
Click to collapse
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Exactly How Much Time can the re-encryption process could take?? Cause I gave it good 1 hour
Also to make sure i am getting it right , you mean to say that i should use the TWRP file you mentioned below your statement
"-------update 2" or is it some (img file) that i need to flash through TWRP

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
To Avoid Any Further Confusion , Could You Give me step by step instructions for what to do , please?
Please also give me details to which TWRP to use and all the configurations ( like ext4 or f2fs on system or data , whether to use format button, or advanced wipe) all that! Thanks in advance

Issue solved !!
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:

PreciousPulkit said:
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:
Click to expand...
Click to collapse
Well done. And because you worked this out yourself, you've learnt a lot.
Sent from my OnePlus3T using XDA Labs

TWRP: persistent decryption of /data

Hello and thanx for your attention. Can't fix my problem. Or I read the wrong threads. Anyway, i would appreciate your help.
Installed twrp r20, rebooted in recovery, flashed magisk 19.1 or su 2.82. First everything's fine, twrp's backup shows some Mb in /data (caused by magisk or su). So decryption is working at that point. Then, after booting into system and doing some settings, root is still there (rootchecker), but back to twrp there will be /data again with 0MB.
As i understand booting re-encrypts /data from f2fs to emmc. Anyone a hint? Main purpose of twrp for me is taking backups (before trying custom roms)
Running stock oreo 8.1.0 Europe with 01.02.19 sec patches
Thanx in advance

Found solution. Maybe it's for interest of TWRP newbies like me...
TWRP decrypts just in time, if you use the PIN of your android's LOCK SCREEN (settings-safety) at start. You will see full /data and can run a nandroid backup. Rebooting to system then will encrypt /data again.
A had issues using a password for lock screen, so better use PIN.