Related
Hi all,
this rom is built from cm sources with stock kernel. It has some extra cherry picks installed to enable either f2fs or ext4 to work. All else is stock (currently).
To flash it choose either all ext4 or data and cache partitions as f2fs.
Full format is recommended with first install. Any 5.1 gapps is fine.
Credit goes to cm, and to DCD for the following cherry picks
93001
92999
92997
92998
and to Percy Gahlot for 94118 for the patch to implement kexec hardboot to support multirom.
more detail of these here.
Download here
More updates soon.
Enjoy.
v2.0 is based on 05052015 CM 12.1 source and updated UBERTC (5.1 and 4.9)
F2fs is the beast!!
Hello
Meaning that if it is twrp ext4 recognisable, then i still can flash this normally as ext4? or meaning that i have to let my device in f2fs first and then flash this?
Salam Husin said:
Hello
Meaning that if it is twrp ext4 recognisable, then i still can flash this normally as ext4? or meaning that i have to let my device in f2fs first and then flash this?
Click to expand...
Click to collapse
Hi,
if your device is ext4 formatted this rom will install. You can also install this if it has data and cache formatted as f2fs.
zaphodbeeb said:
Hi,
if your device is ext4 formatted this rom will install. You can also install this if it has data and cache formatted as f2fs.
Click to expand...
Click to collapse
Hello...
Already installed. Successful!
But still wondering, is it possible to have viper4android and maxxaudio at the same time? I guess there are few modded versions of viper as well as maxxaudio but no idea which one would work. I tried maxxaudio with some other custom roms on 5.1.1 but unfortunately did not work as I expected. Out of sudden did not work after few songs on spotify.
If let say i do flash either viper or maxxaudio, would that replaces the current audiofx file or i have to disable first audiofx and then clear it from its root system and then flashing those two? I did experience repeated sudden audiofx has stopped pop up again and again / force close till i have to restore my rom...
Any advice?
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Thanks, as always, zaphodbeeb
Will you plan to release a F2FS version of CM12S, or we stay with CM12.1 nightlies ?
I used F2FS file system on data and cache partition and now its like i have a nexus 6p there is little to no UI lag or even any delay in opening apps.
Used to use F2FS on my previous devices(lg g2, Galaxy S2 and Xperia Z ultra) and man the effect was noticeable from day1, so tried it on this device and guess what it works flawlessly.
Here is a thread for comparition between F2FS vs EXT4(the default one).
So here is guide for you guys its Highly dangerous setup so please follow this if you know how to restore a SoftBrick status.
Caution:--
ONLY FOR CM13 and N based roms which support F2FS, If used on OOS3 or H2OS(mm) it will result in not converting the data/cache partition properly and will end up 0mb partition because of modified twrp used for these roms and you wont be able to be mount your internal memory too.
Backup backup backup. Make sure you take a backup and save it on your pc before performing the steps.
Things you can do to make your life easier:--
Clean flashing of rom is highly recommended but you can try dirty too as it does not touch the system partition but still clean is preferred.
Use ZipMe app to make a zip file for your apps so that installing all those apps becomes easier if coming from clean flash.
Full backup of your internal memory files as this setup formats even your internal memory even if you select only the data partion.
Best stay on stock kernel as there is no mention of any cm13 custom kernel to have f2fs support. They may have but in any thread of these i couldnt find f2fs word anywhere. So stay stock.
Rom compatibility/tried on:--
Exodus.
All cm13 based roms work flawlessly.
LineageOS14
Kernel compatibility:--
Darkbeast
Stock kernel or the one provided by default by the rom.
Yarpin's kernel.
Benschold kernel.
Note:- Please this method has worked on F2FS supported roms only before following any of it make sure your rom developer has incorporated f2fs support in his/her rom.
Steps:--
Use revert2lollipop to revert back to lollipop firmware if you are on OOS3/H2OS and wanna try f2fs.
Download and upgrade your twrp version to latest.
Copy the .img file to your root folder and reboot to twrp select--->Install-->Install images button-->select the new .img file you copied and reboot to recovery.
Format everything including your internal memory.
Go to advance wipe and select cache partition and select repair and change file system, once there select change file system and change it to f2fs and swipe. Images.
Repeat the above step for data partition.
Go to twrp settings and tick rm -rf, this will make your device retain your f2fs system after clean flash of some roms.
Reboot your recovery once and copy back all your data back to your internal memory.
Flash the required modem for your rom and clean flash your rom for the best bug free experience.
Benefit!
PS:- Please if someone daring does use this on another rom and if everything works flawlessly then please post about it, i will add it compatible roms/kernels.
Press thanks if it worked for you and do post about any improvements you saw.
Credits:-
@Androguide.fr
@ opt devs for awesome roms.
@ jrummy Apps for zipme app.
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
jbarcus81 said:
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
Click to expand...
Click to collapse
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
So we need stock kernel
isoladisegnata said:
So we need stock kernel
Click to expand...
Click to collapse
Yeah for now, since for f2fs roms to work properly the kernel also needs to support the file system and no custom kernel has f2fs as a feature mentioned in their list. I couldnt find anything related to f2fs even with the search function, will update the thread if f2fs support is confirmed by the devs of the respective kernels.
chintu1234 said:
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
Click to expand...
Click to collapse
Yeah.. Not using any kernel other than what's built into AICP from the OP.. :highfive:
Added yarpin's kernel to the compatible kernels.
Using AOKP with stock kernel perfectly! Thanks for this OP and also for sharing the ZipMe app! Which is amazing, Didnt work for me on CM13 though but love the idea! JRummy devs make the best apps
Can i use titanium backup to app+data?
isoladisegnata said:
Can i use titanium backup to app+data?
Click to expand...
Click to collapse
Yes you can.
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
isoladisegnata said:
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
Click to expand...
Click to collapse
Yeah if you connect to PC after conversion you will be able to access your memory as you used to with default system.
Just make sure to wipe system,data,cache,dalvic,internal before going any further for good measure.
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Tatsuya_ said:
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Honestly I wouldn't notice a difference unless you put 2 phones running ext4 and f2fs side by side for comparison. But if I were to really force an answer out from myself I would say that app opening and switching times are greatly reduced.
you really deserved more thanks for this guide.. keep it up and great work!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
Nice! thanks for reporting, will add to OP.
Works great with Exodus ROM !!!
very good. Thank you very much. wonder why only cache and data? What about the system partition?
rakieta said:
very good. Thank you very much. wonder why only cache and data? What about the system partition?
Click to expand...
Click to collapse
It really isnt needed because in system partition most of the time only read function is done while data and cache constantly need read/write functions to be performed so you wont notice anything different if you format system to f2fs.
Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.
When I try to format my Data partition to F2FS it shows:
mkfs.f2fs -t 0 -r 16384 /dev/block/sda9 process ended with ERROR: 1
Unable to wipe Data.
Error changing file system.
And also when I format System to F2FS it succeeds but when I install a ROM (AOSiP) it won't install unless I reformat it back to ext4.
Hope anyone can help..
Thank you!
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
ThE_MarD said:
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
Click to expand...
Click to collapse
Hi! I know it's been so long since I posted this but when I flashed AOSPExtended it shows an "Encryption unsuccessful " screen for me whenever I format Data partition as F2FS :/
Update: Dirty Flashed latest AOSPExtended and made a backup of it, did what you instructed and when I boot the phone it goes to fastboot mode.
ThE_MarD said:
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
Click to expand...
Click to collapse
Hi friend, does Lineage run well with the system partition in f2fs?
I use only the data, do you think it's worth the test?
Rom is great at it, congratulations! :good::good:
Jabbzz said:
Hi! I know it's been so long since I posted this but when I flashed AOSPExtended it shows an "Encryption unsuccessful " screen for me whenever I format Data partition as F2FS :/
Update: Dirty Flashed latest AOSPExtended and made a backup of it, did what you instructed and when I boot the phone it goes to fastboot mode.
Click to expand...
Click to collapse
Heyyo, hmm if that is the case I think AOSPExtended doesn't support quota for storage.. the only way to resolve this is to backup your data, copy it to USB OTG or to a PC and then going to wipe > format data > yes. After that you can copy back your data and restore the data backup.
drml said:
Hi friend, does Lineage run well with the system partition in f2fs?
I use only the data, do you think it's worth the test?
Rom is great at it, congratulations! :good::good:
Click to expand...
Click to collapse
Heyyo! To be honest I have not tested it much with f2fs. It feels smooth enough but then again ext4 still runs pretty darn good so any performance improvement is minor.
I only ever recommend converting the cache partition to f2fs as it constantly changes data and f2fs still doesn't handle file system fragmentation as well as others such as ext4 so f2fs on system and data still isn't as ideal as ext4 for long term performance retention.
ThE_MarD said:
Heyyo! To be honest I have not tested it much with f2fs. It feels smooth enough but then again ext4 still runs pretty darn good so any performance improvement is minor.
I only ever recommend converting the cache partition to f2fs as it constantly changes data and f2fs still doesn't handle file system fragmentation as well as others such as ext4 so f2fs on system and data still isn't as ideal as ext4 for long term performance retention.
Click to expand...
Click to collapse
f2fs ist superior to ext4 especially in write operations. That's way if you use f2fs you don't be affected to the slowness who comes with the time with the ext4. Otherwise ext4 exist longer and is more, lot of people assume this, stable. I use f2fs long enough to say that my last freezes with the f2fs filesystem are way back to 2014. Even then I would say that the troubles come with the custom roms than with the f2fs.
I use in my x2 the Lineage unofficial with f2fs without a single performance degradation and before that used Infrag nougat aicp with f2fs. F2fs is better but lot of people have trouble or they don't know how to convert the /data partition and before that that they must Backup the /internal Sdcard as the convert process wipe the whole /data + /internalsd
Here more Infos why f2fs is the better filesystem
https://www.google.com.cy/amp/s/www...ms-matter-interview-stan-dmitriev-tuxera/amp/
https://www.linux.org/threads/flash-friendly-file-system-f2fs.8931/
I try official releases of lineage 15.1, Omnirom and when I run encryption from option (with password), android reboot without encryption of /data partition.
I have seen that unoffical release of lineage 16, Aosp 9 has issues in hardware encryption. No problem with official MIUI Rom also.
Are there any custom rom for mido that allow encryption ?
(My configuration, special MIDO TWRP treble support)
Thanks for your experience return.
I think it depend of the data partition if its F2FS or EXT4 , but i dont encrypt anymore , the one who would crack my phone would be left with unsatisfaction, at the end it would just prove that humans are never satisfied.
i am using lineage os 15.1 with encryption.
I didnt manually encrypted my phone but it got encrypted during installation of los 15.1
BK said:
I think it depend of the data partition if its F2FS or EXT4 , but i dont encrypt anymore , the one who would crack my phone would be left with unsatisfaction, at the end it would just prove that humans are never satisfied.
Click to expand...
Click to collapse
I use ext4 on another encryptedr mido with miui official.
Rohit338 said:
i am using lineage os 15.1 with encryption.
I didnt manually encrypted my phone but it got encrypted during installation of los 15.1
Click to expand...
Click to collapse
Are you sure ? because the assistant does not prompt for encryption but only for lock password.
I have tryed to reset with flashboot flash_all.sh but no difference after Los 15.1 install
What recovery do you use ? TWRP or REDWOLF ?
BK said:
I think it depend of the data partition if its F2FS or EXT4 , but i dont encrypt anymore , the one who would crack my phone would be left with unsatisfaction, at the end it would just prove that humans are never satisfied.
Click to expand...
Click to collapse
I can now answer, F2FS make no difference, same problem no encryption with custum rom
neo_mat said:
Are you sure ? because the assistant does not prompt for encryption but only for lock password.
I have tryed to reset with flashboot flash_all.sh but no difference after Los 15.1 install
What recovery do you use ? TWRP or REDWOLF ?
Click to expand...
Click to collapse
For installation i used twrp posted on 1st page.
but now i am using red wolf recovery.
yes it doesn't prompt for encryption but i think setting the lock pattern encrypted the phone as i have to draw the same pattern to access internal storage using red wolf and during booting.
Rohit338 said:
For installation i used twrp posted on 1st page.
but now i am using red wolf recovery.
yes it doesn't prompt for encryption but i think setting the lock pattern encrypted the phone as i have to draw the same pattern to access internal storage using red wolf and during booting.
Click to expand...
Click to collapse
Curious because, android need the password in order to decrypt…
Did your recovery prompt for password ? (recovery is OS independant) if not, your device is not encrypted.
neo_mat said:
Curious because, android need the password in order to decrypt…
Did your recovery prompt for password ? (recovery is OS independant) if not, your device is not encrypted.
Click to expand...
Click to collapse
yes recovery asks for password to decrypt internal storage by the way have you checked the screenshot i have attached.
thanks, yes i have seen sreenshot.
I really don't understand because it s do basic.
I use the same twrp,
I wipe all partitions
after that, the redmi note 4 is empty (no system, no data...)
I install los 15.1
run encryption with assistant
the redmi immediatly reboot without pass throught mi boot logo screen
and no encryption
I can loop that everytimes.
It's curious because the redmi immediatly reboot like a bad reboot. (like an error)
I don"t know if there is any log of that
steps that i followed
flashed twrp
wipe all
advance data format (entered YES to format)
and finally flashed los.
I found it !!!
This can save people.
I have to leave 4K block into userdata partition.
In fact, fastboot, and TWRP can break filesystem and resize filesystem to all partition size.
Encryption need 4K block in order to write encryption data about userdata patition.
I have resized my ext4 filesystem with resize2fs.
Now all is OK !!!!
After that, I also format from ext4 to f2fs.
Thanks
neo_mat said:
I found it !!!
This can save people.
I have to leave 4K block into userdata partition.
In fact, fastboot, and TWRP can break filesystem and resize filesystem to all partition size.
Encryption need 4K block in order to write encryption data about userdata patition.
I have resized my ext4 filesystem with resize2fs.
Now all is OK !!!!
After that, I also format from ext4 to f2fs.
Thanks
Click to expand...
Click to collapse
Great news! Does it mean you could encrypt your device on a Pie ROM?
Of course !
I can now encrypt my device.
neo_mat said:
Of course !
I can now encrypt my device.
Click to expand...
Click to collapse
That's great news. I am pretty used to flashing my beloved mido but I never used the tool you mentioned (resize2fs). Would be great if you could provide some kind of documentation how to do this?
neo_mat said:
I found it !!!
This can save people.
I have to leave 4K block into userdata partition.
In fact, fastboot, and TWRP can break filesystem and resize filesystem to all partition size.
Encryption need 4K block in order to write encryption data about userdata patition.
I have resized my ext4 filesystem with resize2fs.
Now all is OK !!!!
After that, I also format from ext4 to f2fs.
Thanks
Click to expand...
Click to collapse
how to do it, can you explain it please?
I'm trying to disable encryption because with pretty much every ROM I tried the phone ends up encrypted. Which is very annoying as it prevents dirty flashes (+ updates) and flashing things like Magisk after first boot