Database Users

F2fs Formating guide

Hello everyone heres a guide on how i formated my le pro 3 720 64gb from ext4. please know that this will delete all of your data will be delete i strongly recommand doing a twrp or tatanium backup before hand! allso if this somehow ****s up i will not be hold responsible. i am simply showing you all how i did this to get my result. now with all the formalitys in place lets talk about what exactly the steps are after you backed up everything you want to keep download your feverite rom. the one i am ussing is turbos aokp destroyer ver2, download it unto your pc, allso make sure you have twro custom recovery that support the f2fs.
here is the one i ussed. https://drive.google.com/file/d/0B9ZMWt4u_wSDVkp3UlMxS1liMUE/view
after you have made sure your twrp support it and you backed up everything you need. boot into twrp, wipe/advanced wipe/check data/repair or change file system/chenge file system/ f2fs do the same for data and for cache. then connect you phone via the usb cable to a pc with minimal adb put the rom you decided to install on your le pro 3 into the minimal adb folder and call it something easy like Kitty. i do this all the time xD
then open a cammend windows as admin and type the fallowing code.
adb push push kitty.zip /sdcard
this will start your rom being moved from the pc unto your sdcard on your phone. and i allso belive its the safest way to do it dont qote me on that tho.
then you just install your kitty rom and you should be good to go. NOTE in my case with the destroyer 2 aokp from my good freind turbo i dont think the /system supports f2fs as it reformats it into the ext4 on installation, but data and cache will reamain f2fs at all times. and it does seem quite abit faster regardless. thanks everyone for reading and im sorry if this is done in a extreme noob fashion i hope you all will be able to understand whats going on and all. peace out and be sure to let me know how it turns out for you

Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?

venezolano69 said:
Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?
Click to expand...
Click to collapse
It might work. I've never used a otg in TWRP before but if it works I can't see why not.

DrTorretz1 said:
It might work. I've never used a otg in TWRP before but if it works I can't see why not.
Click to expand...
Click to collapse
OK thanx for the guide

venezolano69 said:
OK thanx for the guide
Click to expand...
Click to collapse
Your welcome hope it helps!

Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!

FYI, at the very least you can format your cache partition to F2FS without losing any data.

slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6

villarleg said:
Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!
Click to expand...
Click to collapse
Wow thanks village! I'm happy you enjoyed the guide also thanks for letting me know about the system I will put it up there!

venezolano69 said:
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6
Click to expand...
Click to collapse
Does it come up with a error or something? I'm not sure mine did it fine

slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
Yeah I suppose so. It works really well regardless

DrTorretz1 said:
Does it come up with a error or something? I'm not sure mine did it fine
Click to expand...
Click to collapse
Something like "not possible to mount"

venezolano69 said:
Something like "not possible to mount"
Click to expand...
Click to collapse
That sounds really strange. I'm sorry I can't assist further. Data should be the most important one annyways

Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices

Enamak said:
Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices
Click to expand...
Click to collapse
Do you have an otg?

venezolano69 said:
Do you have an otg?
Click to expand...
Click to collapse
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway

Enamak said:
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway
Click to expand...
Click to collapse
Otg is very good stuff, when you wipe everything you put Rom insidie the otg and you can flash everything you want

I have another problem.. I formated /cache /data (no problems, errors). After that I flashed "TURBO2012's China / US EUI 23s V8" (no problems, errors).
But DiskInfo from the playstore is showing me ext4 in /cache and /data ?

Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.

cherryduck said:
Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.
Click to expand...
Click to collapse
Same here. I tried it a few days ago with the latest Lineage nightly and started formatting all partitions with F2FS with the same outcome: stuck on bootscreen.
Gradually I returned my partitions to ext4 and only after I returned everything to 'normal' I got past the boot screen. Not even "cache" worked with F2FS.

How to enable encryption?

Hello everyone!
I am wondering how to enable encryption of my P9 Lite running Nougat B370. My phone is rooted, bootloader unlocked and TWRP installed, if that is relevant.
In the menus I don't find any option to encrypt my phone. So, anyone knows if it is possible?

If you mean data encryption, it is already encrypted.

Potato997 said:
If you mean data encryption, it is already encrypted.
Click to expand...
Click to collapse
You sure about that? Because TWRP can access my data partition without pin...
Is there any way to check whether disk encryption is truly enabled?

android_xpert said:
You sure about that? Because TWRP can access my data partition without pin...
Is there any way to check whether disk encryption is truly enabled?
Click to expand...
Click to collapse
It's encrypted unless you unencrypted it with twrp but the latest update of twrp (nouget) lets you backup data unlike twrp on MM.

bghyt said:
It's encrypted unless you unencrypted it with twrp but the latest update of twrp (nouget) lets you backup data unlike twrp on MM.
Click to expand...
Click to collapse
It's strange though, I've never unencrypted my phone with twrp. But when I boot into twrp my whole data partition is open for access without any sort of password/pin. Seems to me there is no encryption active.

TWRP can mount data partition, but it does not mean that it is able to decrypt it.
It can backup/restore or format it which is what usually what a TWRP do, if you install a custom ROM like LOS you will need to format it because the system can't decrypt it while stock ROM can do it.

Potato997 said:
TWRP can mount data partition, but it does not mean that it is able to decrypt it.
It can backup/restore or format it which is what usually what a TWRP do, if you install a custom ROM like LOS you will need to format it because the system can't decrypt it while stock ROM can do it.
Click to expand...
Click to collapse
What I meant by my post is not only that twrp can mount the data partition. I can also access all my files within said data partition.

Stuck on 'To start android, enter your password'

I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch

Gaby_64 said:
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Click to expand...
Click to collapse
Does TWRP print anything about "successfully decrypting /data with default password" in the console when it starts?
Go WIPE > ADVANCED WIPE > check the box next to "Data" > REPAIR OR CHANGE FILE SYSTEM. What does it say the file system of /data is?
Edit: Did you format /data before or after the issue happened? Never mind, you have to have formated /data afterwords if you were trying different ROMs.

ext4
i dont see the console

Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason

troy5890 said:
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
Click to expand...
Click to collapse
i tried as both f2fs(performance is worth it) and ext4

Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.

Doc Ames said:
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Click to expand...
Click to collapse
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?

troy5890 said:
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
Click to expand...
Click to collapse
May I ask, why are you using that version of TWRP?

Choose an username... said:
May I ask, why are you using that version of TWRP?
Click to expand...
Click to collapse
It's the only version that will boot up successfully when flashed through fastboot.
Sent from my ZTE A2017U using XDA-Developers Legacy app

troy5890 said:
It's the only version that will boot up successfully when flashed through fastboot.
Click to expand...
Click to collapse
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?

Choose an username... said:
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Click to expand...
Click to collapse
I tried but it ended up not flashing successfully
Sent from my ZTE A2017U using XDA-Developers Legacy app

troy5890 said:
I tried but it ended up not flashing successfully
Click to expand...
Click to collapse
all hail axon7tool then :v

Choose an username... said:
all hail axon7tool then :v
Click to expand...
Click to collapse
Looks like I'll give that a try, thank you
Sent from my ZTE A2017U using XDA-Developers Legacy app

SM-T580 Android 7 : /data encrypted, can't flash no-dm-verity

So I just bought this Tablet and I wanted to Root it, but I immediately noticed that in trying to flash anything, this verification thing gotme stuck in a bootloop. I looked further into it, and I need to patch dm-verity out, however, the latest .zip I tried is for Android 6 it seems, as when I tried to flash it and then let TWRP make modifications, it still got stuck in the Verification Error bootloop.
Now I flashed the original system to it again through Download Mode, and that fixed the bootloop. However, I then went into Odin, flashed TWRP, went into TWRP, tried to do as it said in the guide where it says I need to "Wipe Data", but when I try to do that it says "Failed to mount '/data' (Invalid Argument)". So what now? And does anyone here have a dm-verity patch for this tablet that supports Android 7? Thanks

yanniclord said:
However, I then went into Odin, flashed TWRP, went into TWRP, tried to do as it said in the guide where it says I need to "Wipe Data", but when I try to do that it says "Failed to mount '/data' (Invalid Argument)". So what now? And does anyone here have a dm-verity patch for this tablet that supports Android 7? Thanks
Click to expand...
Click to collapse
Which guide?

ashyx said:
Which guide?
Click to expand...
Click to collapse
This one
https://forum.xda-developers.com/ga...ab-tablets-t3552509/post70924135#post70924135
Oh, I recognize your name, didn't you also make the no-dm-verity script?

yanniclord said:
This one
https://forum.xda-developers.com/ga...ab-tablets-t3552509/post70924135#post70924135
Oh, I recognize your name, didn't you also make the no-dm-verity script?
Click to expand...
Click to collapse
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
ashyx said:
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
Click to expand...
Click to collapse
These instructions are a tad simpler.
To disable forced encryption, disable dmverity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using the FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx

ashyx said:
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
These instructions are a tad simpler.
]To disable forced encryption, disable dmverity and mount internal storage:[/B]
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
Click to expand...
Click to collapse
Hmm alright, I actually tried that before but it worked this time after I reinstalled the Stock Firmware multiple times and did multiple resets as well, thanks
So do you have a no-dm-verity.zip for Android 7 for me? Or does the one from the thread work?
Oh and, I want to flash Magisk, so shall I flash Magisk first and then no-dm-verity? I am pretty sure that is correct assumed of me.

EDIT: Thanks for the no-dm-verity zip, will try it and I will also try Magisk Thanks for all the help, has been a while with Samseong devices for me :/
EDIT 2: As far as I remember, doesn't Magisk disable dm-verity to begin with when it flashes itself?

yanniclord said:
EDIT: Thanks for the no-dm-verity zip, will try it and I will also try Magisk Thanks for all the help, has been a while with Samseong devices for me :/
Click to expand...
Click to collapse
Will work on Android 7 too.
If you flash Magisk you shouldn't need the patch.

[FIX][8.1][Treble]Decryption Unsuccessful and TWRP Internal Storage 0MB

As the tittle says, this is my current workaround for issues that happened after most people update their AOSP based ROMs after 3rd July 2018.
Decryption Unsuccessful
Q: Why does this happens ?
A: There's some weird issues with the latest AOSP based ROM that makes encrypted ext4 based data partition unable to be decrypted in both system and older version of TWRP if you're encrypted before (intentionally or unintentionally). This however doesn't apply to F2FS and unencrypted ext4 data partition.
Q: How do I solve this ?
A: There's 2 ways you can do to solve this issue.
The best way and the most recommended way is to repartition your data into F2FS. However it does require you to do a backup beforehand since this will wipe everything in your internal storage.
1. Backup your internal storage from TWRP (either to a SD card or PC via ABD)
2. Format it by going into TWRP and select Format and choose "wipe data"
3. Type "yes" and let the process end.
4. Flash your ROM and GApps.
5. Finish the setup without setting any screen lock so that it doesn't encrypt your data partition.
-Or-
The other way does is to install a custom kernel is made after 20 July 2018
List of kernel that can boot successfully without the need to wipe /data :
-Xenial b25x or newer
-Revolt EAS-R13
(Got kernel that works and doesn't show up here? TELL ME, I'll add it to my list for everyone's reference)
Link for the working TWRP that can detect Internal Storage :
Jairus' modded TWRP
https://androidfilehost.com/?fid=5862345805528049168
Or you can look up Orange Fox recovery
(link will be added soon)

Good Stuff Also This Happened to me while i was using the Android P DP3 i tried twrp and redwolf and was the same i flashed the Orange Fox and it worked

Does this twrp can flash both treble and non treble ROM?

eko_epe said:
Does this twrp can flash both treble and non treble ROM?
Click to expand...
Click to collapse
Yes, it does

AkmalWarrior said:
Yes, it does
Click to expand...
Click to collapse
Ok i'll try. Thanks

As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.

DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
TWRP and redwolf too (find on telegram)
Envoyé de mon Redmi Note 4 en utilisant Tapatalk

DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
*Only in recovery, not in boot. The only way to fix decryption unsuccessful on boot is to either repartition data to F2FS or flash a custom kernel that's made after 20 July. List on working kernels is on main thread.

First I tried orange fox beta and it showed my internal storage
Then I flashed the RR endless
But the encryption was still there
Then I tried the twrp from this thread and flashed rom with latest xenial
And it worked no problem
Thank you

How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1

DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk

antony felix said:
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk
Click to expand...
Click to collapse
Thanks,So i must format internal too,. It's ok but how if i want to comeback use nougat..? I hear who's downgrade after using oreo will get "encryption was interrupted" on any nougat los/aosp base rom,should be format internal for working back the devices..
I think by this thread shared we get solution for who's want to downgrade from oreo without facing encryption issue enytime for oreo back to nougat or vice

DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.

What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?

AkmalWarrior said:
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.
Click to expand...
Click to collapse
Finally i can confirm for fixed "encryption was interrupted" by changing data partition into F2FS, yes i think it's only way to get free from that, i'v been test it back to back from oreo down to nougat or vice, no worry anymore
Below screenshot for oreo left side and nougat in right

ngydna said:
What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?
Click to expand...
Click to collapse
Read the OP, the recovery only help you boot into recovery and format your data partition or flash a custom kernel to allow you to boot into system as this issue does affect some older version of TWRP recovery. The recovery alone can't help you boot into system.

I took out my sdcard and did format data on the internal storage and now i can't mount my sdcard. Didn't think about the fact that removing the encryption on the internal storage would make it unable to recognize the encryption on the sdcard afterwards. Is there any way to fix this? Or did I just screw myself?
---------- Post added at 01:53 PM ---------- Previous post was at 01:00 PM ----------
When I reinstalled the rom and tried to boot it still asks me for my password which still works even though I can't boot because it says that the data is corrupted. But the encryption key should still be stored somewhere apparently. There must be a way to use it to decrypt the sdcard.