Related
LegoKernel - With F2FS
NOTE This kernel version doesn't support "All-F2FS"
This is a Kernel for Android 4.4. I made this for SlimKat so i don't know if this will work with other roms.
Some users reported working also on:
Cyanogenmod (Reported by: buggatti)
Carbon (Reported by: Nosterius)
OmniROM (Reported by: SkOrPn)
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system 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.
The idea was of ss2man44. F2FS helps Nexus 7 2012 where he needs: IO Speed and slowdown after long period (months?) of use. This Filesystem is used in others phone too like Moto X where he shows good performance.
I tested this myself for some weeks without problems and i'm happy.
I started from the stock Slim kernel.
There are also others features by me:
Ported sl[aou]b from Linux 3.4
Ported timer and workqueue from Linux 3.4
Ported random from Linux 3.13-rc4
Ported rwsem from Linux 3.11
Kernel NEON Mode
Etc..Etc..
Added GPU OC (Franco way..)
Added Toggle for FSYNC
Revert CPU OC things (We don't need it and it was a bit dirty..)
Instructions:
I already said that i did this for SlimKat so my advice is to start this procedure with a working SlimKat rom or another rom that is reported to work good. (See the start of this post)
F2FS is a Filesystem so we have to Format our memory in this mode. How can we do this? We need a "special" TWRP and LegoKernel
Download LegoKernel LegoKernel-F2FS-140228
Download "special" TWRP recovery-F2FS-A.img
Copy LegoKernel on Tablet
Flash LegoKernel with your current Recovery
Flash "special" TWRP with Fastboot
I said "FORMAT" so it's obvious that you will lose all your data (even Movies..Music..all!). Backup them on PC to restore easily at the end.
Now..
Reboot in Recovery (To know that you are on "special" TWRP note that the BackKey is Red at the bottom-right)
Go to Wipe menu
Format Data (Not the simple Wipe!)
Reboot
Enjoy. (Now you may want to restore your backup)
Report back how do you feel your tablet now. I have a very positive opinion about this thing!!
Changelogs:
- 28/02/13: Add Kexec Support
Some thing you have to know:
After the switch to F2FS you can use only kernel with F2FS Support
Backup made with standard TWRP may not work with "special" TWRP and reverse.
How come back?
Flash a standard TWRP
Format Data
Flash your previous ROM/Kernel
Reboot
Github
It's great that someone else beside sgt.meow (Oxydo kernel) picked up ss2man44's idea. :good:
working great with cm 11
and Thank a lot for adding fsync off.. NOW THE NEXUS 7 FLIES
MultiROM v22a - With F2FS
I have adapted Tassadar MultiRom to work with F2FS. (All credits to him)
You need:
Its Multirom zip. Here
Kernel with F2FS Support and Kexec Support
(As now LegoKernel-F2FS-140228 is the only LegoKernel that work with MultiROM)
TWRP with F2FS Support and MultiROM. Here (For Grouper)
TWRP with F2FS Support and MultiROM. Here (For Tilapia)
If you already switched to F2FS:
Move Multirom zip and Kernel to your tablet
Flash TWRP with F2FS Support and MultiROM with Fastboot or Flashify
Reboot in Recovery
Flash Kernel
Flash MultiROM zip
Reboot
If you didn't switch to F2FS and want to do it now:
Copy Kernel to your tablet
Flash Kernel with your current Recovery
Flash TWRP with F2FS Support and MultiROM with Fastboot
Reboot in Recovery
Format Data in Wipe menu (you will lose all your files!!) Not the simple Wipe!
Reboot
Copy MultiROM zip to your tablet
Reboot in Recovery
Flash MultiROM zip
Reboot
Some things you have to know: (READ THEM)
All your ROMs must support F2FS so if you want to use "normal" ROMs you have to "share kernel"
I have tested this with SlimKat as Primary and CM11 as other ROM
I think i did some errors writing all the procedures. Hope they are right now.
Hi,
this mod works well for me on my Nexus 7 3G running CyanogenMod 11. I've been running this just for a few hours, but the filesystem performance seems much better, my N7 no longer lags when installing apps, which it did before.
The only problem, or rather inconvenience, I had is that the recovery is not made for the N7 3G, so it won't install ROMs and stuff made for tilapia, as it expects them made for grouper. It would be cool to have a tilapia version of the recovery, or some instructions in the OP on how to use it there.
If you want to use this mod on tilapia, you have to:
Install the special recovery by legolas93 from the first post.
Format /data from within the recovery (format, not just wipe).
Install back a recovery made for tilapia and DO NOT FORMAT /DATA!
Install your ROM/gapps/hippo/etc.
Flash the modified kernel from the firts post.
Anyway, big thanks to legolas93 for doing this. Have you also considered making /system and /cache as f2fs? Do you think it would have any significant benefits?
Hmm, well I decided to try this as well, however after flashing the kernel I sat it down for a few minutes so I could fire up my laptop (it has Fastboot on it) and when I came back to the tablet it was turned off. I turned it on and now out of the blue its asking for a password to decrypt the storage?
I have ran CM11 for the past year on it and purchased it brand new from Google last January. However, after trying my Google email password it is still asking for a password.
Anyway, I decided to do a full wipe, installed CM11 2/28, LegoKernel and Gapps. And upon rebooting its still taking me to a screen asking for a password. Anyone know why it would spontaneously ask for a password? is there a default password I am supposed to use with this kernel by chance? lol, I am at a loss and I usually have everything under control grr haha
EDIT:
CM11 2/28 is installed
Latest LegoKernel
Latest PA_Gapps
And I have not been able to flash the latest TWRP on it yet. But I do have the latest TWRP (MultiROM version) on it.
EDIT: #2, Ok I managed to use Fastboot on my laptop and I flashed the special TWRP. I went a head and re-wiped factory-reset and also re-flashed the CM11 rom and the latest LegoKernel, but after a reboot its still asking for some unknown password. Why would it need a password all of a sudden?
SkOrPn said:
Hmm, well I decided to try this as well, however after flashing the kernel I sat it down for a few minutes so I could fire up my laptop (it has Fastboot on it) and when I came back to the tablet it was turned off. I turned it on and now out of the blue its asking for a password to decrypt the storage?
I have ran CM11 for the past year on it and purchased it brand new from Google last January. However, after trying my Google email password it is still asking for a password.
Anyway, I decided to do a full wipe, installed CM11 2/28, LegoKernel and Gapps. And upon rebooting its still taking me to a screen asking for a password. Anyone know why it would spontaneously ask for a password? is there a default password I am supposed to use with this kernel by chance? lol, I am at a loss and I usually have everything under control grr haha
Click to expand...
Click to collapse
Did you format the /data partition with the modified recovery? This happens when Android can't access the /data partition, in this case very probably because there is a mismatch between the filesystem on /data (ext4) and the filesystem the kernel expects (f2fs). You have to first format the /data partition so it would have f2fs.
frantisek.nesveda said:
Did you format the /data partition with the modified recovery? This happens when Android can't access the /data partition, in this case very probably because there is a mismatch between the filesystem on /data (ext4) and the filesystem the kernel expects (f2fs). You have to first format the /data partition so it would have f2fs.
Click to expand...
Click to collapse
I cant remember now if I did or didn't format /data. I remember formatting everything except for OTG I think, lol.
Anyway, I used NRT and put the device back to stock, then I installed the modified F2FS TWRP recovery. Now I have the modified Recovery installed, and a fresh stock rom rooted with usb debug enabled. I just finished downloading the latest CM11 Rom and the LegoKernel and put it into my freshly formatted sdcard. I am sitting in TWRP at this moment but worried about flashing the kernel again. haha
Going to try again. Will report back. But first, let me make sure I have this right since I am trying to flash a ROM at the same time now.
1st. Flash the CM11 ROM
2nd. Flash the LegoKernel
3rd. Format /data???
4th. Flash Gapps?
I am almost certain I did this before, that's why I am asking.
SkOrPn said:
1st. Flash the CM11 ROM
2nd. Flash the LegoKernel
3rd. Format /data???
4th. Flash Gapps?
Click to expand...
Click to collapse
That should do it. Remember, you have to format /data, just wiping is not enough. And you'll have to flash gapps via sideload, because formatting /data also removes everything on /sdcard.
Personally, I'd format /data first, just to be sure you don't delete a part of the CM11 ROM after installing, but I think CM11 recovery zip doesn't flash anything into /data anyway, so it doesn't matter.
frantisek.nesveda said:
That should do it. Remember, you have to format /data, just wiping is not enough. And you'll have to flash gapps via sideload, because formatting /data also removes everything on /sdcard.
Personally, I'd format /data first, just to be sure you don't delete a part of the CM11 ROM after installing, but I think CM11 recovery zip doesn't flash anything into /data anyway, so it doesn't matter.
Click to expand...
Click to collapse
Ok, that must be what I am doing wrong then. I somehow was not aware that wiping /data was not going to do it. I did the above but I wiped /data and now I am back to the password screen yet again. Not sure if I have to go all the way back to stock again or not now.
SkOrPn said:
Ok, that must be what I am doing wrong then. I somehow was not aware that wiping /data was not going to do it. I did the above but I wiped /data and now I am back to the password screen yet again. Not sure if I have to go all the way back to stock again or not now.
Click to expand...
Click to collapse
It will be enough if you now just format /data and flash gapps again. You probably never had to go back to stock anyway, I didn't and everything went well.
frantisek.nesveda said:
It will be enough if you now just format /data and flash gapps again. You probably never had to go back to stock anyway, I didn't and everything went well.
Click to expand...
Click to collapse
Yeah everything seems OK now. Just waiting for Google to re-install all my apps. Wish I had realized there was a difference between wipe and format, and that the format data button is just staring you in the face too. lol
Thanks for your help bud. :good:
SkOrPn said:
Yeah everything seems OK now. Just waiting for Google to re-install all my apps. Wish I had realized there was a difference between wipe and format, and that the format data button is just staring you in the face too. lol
Thanks for your help bud. :good:
Click to expand...
Click to collapse
You're welcome. Glad I helped.
frantisek.nesveda said:
Hi,
this mod works well for me on my Nexus 7 3G running CyanogenMod 11. I've been running this just for a few hours, but the filesystem performance seems much better, my N7 no longer lags when installing apps, which it did before.
The only problem, or rather inconvenience, I had is that the recovery is not made for the N7 3G, so it won't install ROMs and stuff made for tilapia, as it expects them made for grouper. It would be cool to have a tilapia version of the recovery, or some instructions in the OP on how to use it there.
If you want to use this mod on tilapia, you have to:
Install the special recovery by legolas93 from the first post.
Format /data from within the recovery (format, not just wipe).
Install back a recovery made for tilapia and DO NOT FORMAT /DATA!
Install your ROM/gapps/hippo/etc.
Flash the modified kernel from the firts post.
Anyway, big thanks to legolas93 for doing this. Have you also considered making /system and /cache as f2fs? Do you think it would have any significant benefits?
Click to expand...
Click to collapse
Sorry. I dind't have time to do the tilapia recovery. But now i have just uploaded a TWRP Recovery with F2FS and MultiROM for Tilapia! Let me know if it is ok
I think that TWRP need some non-trivial edits from TWRP-guys to be able to use /system and /cache as f2fs. Anyway i don't think that we will gain some big benefits because..
- /cache is used very little..maybe only by recovery (i'm not 100% sure..)
- /system is used only by reading from it 99% of time so i dubt that we will gain some major benefits
Even Moto X use f2fs only for /data partition, maybe this is the best way to use it!
hows the battery life on this kernel, plus im running Kang-aroo kernel which mean ill lose all of the neat tweaks it supports, will you be adding tweaks and mods to this kernel or is this minimum version going to be how it stays moving forward.
Wtf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado desde mi Nexus 5 mediante Tapatalk
Why does it keep taking me back to the multirom menu when ever I boot it up ? You sure the kernel supports kexec-hardboot ?
Edit : Looks like flashing the kernel again after flashing the multirom fixed it.
Fransis88 said:
Wtf
Click to expand...
Click to collapse
Did you format /data with the modified TWRP? Remember, you have to FORMAT, not just wipe. And if you are really absolutely sure you did format, try flashing the kernel again.
Fransis88 said:
Wtf
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
You failed to use the format button. I did the exact same thing. All you have to do now is go back into the modified TWRP and use the "format data" button. It will work perfectly after that.
Sent from my Nexus 7 using Tapatalk
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.
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
Hi together,
i have an problem with the tablet encryption.
i wanna swap from xiaomi.eu to another more actual custom rom..
i tried PixelExperience , Havoc-OS, dotOS, ArrowOs .. and everytime i activate the encryption it's end in an bootloop regardless of pin,password,pattern ..
I'm using the latest TWRP Version
- Wipe Dalvik/ART Cache, Cache, System, Vendor, Data
- Flash from zip
- start os and enable encryption
-> bootloop
My experience with this device is limited, but I faced a similar problem switching from stock rom to an older ROM not using any encryption.
I think it was only succesful after removing encryption. Maybe it also helps in your case?!
There are many guides how to remove encryption, most of them suggest "Advanced Swipe" combined with changing the file system.
I used TWRP to swipe "data" to ext2, then again swipe "data" back to ext4 and afterwards it still needed a tap on "File System Repair" for the "system" partition. After that, the flash and boot worked for that older ROM.
Maybe that will leave you with a better starting point for activating encryption of your ROM.
(But as I wrote: Just a guess, not based on experience.)
aes32 said:
My experience with this device is limited, but I faced a similar problem switching from stock rom to an older ROM not using any encryption.
I think it was only succesful after removing encryption. Maybe it also helps in your case?!
There are many guides how to remove encryption, most of them suggest "Advanced Swipe" combined with changing the file system.
I used TWRP to swipe "data" to ext2, then again swipe "data" back to ext4 and afterwards it still needed a tap on "File System Repair" for the "system" partition. After that, the flash and boot worked for that older ROM.
Maybe that will leave you with a better starting point for activating encryption of your ROM.
(But as I wrote: Just a guess, not based on experience.)
Click to expand...
Click to collapse
Hi,
thanks for your answer. As i wrote i delete nearly everything
The OS booted, but at the point where i want to enable encryption most roms get stuck in a bootloop.
After endless roms i found carbonrom which works.. Additionally i found an post from TWRP about encryption.. i don't know if it's connected, but i guess it's an similar problem cause AOSP..
Why doesn't TWRP support encryption on my device?
Why doesn't TWRP support encryption on my device?TWRP encryption is supported in 2 phases. The first item is keeping up with the newest support from AOSP, wh...
twrp.me
So i found a working rom, but not the solution or true cause of the bootloop problem
Ok, I understand.
I guess I don't know the encryption feature well enough to help.
Found some interesting stuff to read about it, not sure if it applies to the Mi Pad 4 and its custom ROMs, though:
Any way to encrypt /data/data and /sdcard on Xiaomi EU ROM?
Hello, Xiaomi EU ROM is running decrypted, that's a security breach... Is there a way to use Xiaomi EU ROM, based on Miui 10, in a encrypted phone? Thanks
forum.xda-developers.com
So the bootloop seems to be expected and if I got it right then the fstab.qcom needs an edit at least.
Mhm it's confusing me.. cause i run nearly 5 years xiaomi.eu rom encrypted from scratch on. i think with FDE .. the rom says encrypted and twrp says encrypted and the sdcard folder is only crypted filenames.. also interesting the article.. but i'm sceptical that edit the fstab.qcom maybe work on more "normal" AOSP roms..
so i found a working rom i'm not motivated enough to try the edit xD
xXZaretXx said:
Mhm it's confusing me.. cause i run nearly 5 years xiaomi.eu rom encrypted from scratch on. i think with FDE .. the rom says encrypted and twrp says encrypted and the sdcard folder is only crypted filenames.. also interesting the article.. but i'm sceptical that edit the fstab.qcom maybe work on more "normal" AOSP roms..
so i found a working rom i'm not motivated enough to try the edit xD
Click to expand...
Click to collapse
Yes, sorry, I fully understand your point of view.
It is confusing me as well.
I'm currently experimenting with some ROM's, so yesterday I gave encryption on Havoc-OS a try - even by starting with encrypted stock rom, flashing Havoc-OS and modifying fstab.qcom - but without success. It rebooted immediately and then seemed to be hanging idle during boot for a long time.
I was not interested in encryption so far, but of course it would be great if it worked. And I should be interested for the sake of privacy.
Thanks for reporting that it works with the carbon ROM.
Edit: In Lineage OS it will probably work too, based on the description of the ROM.
I will probably try that one next, because it is also supposed to have the "split screen" feature which I am looking for.
Encryption in Lineage OS seems to work fine, as expected.
I tried to analyze Havoc OS encryption once more: It seems not to be supported at all.
It does "something" trying to encrypt... because TWRP asked for a password the next time I rebooted to recovery. Problem is, decryption in TWRP did not work with the previously given password and the data partition seemed to be messed up (file system type was "emmc", and the data partition was not responding to any of tune2fs, e2fsck or alike).
I looked at the dmesg log, it seems during the boot attempt, the system just cannot work with data any more (hence the idle hang, I assume).
There are many many log lines, showing attempts to work with data and that the system actually expects an ext4 file system for "userdata" (=mmcblk0p64):
Code:
[ 2.990548] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.990698] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.996651] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.996795] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
Is it Still Possible to use F2FS in Android 13 ?
I tried in LineageOS with No Gravity Kernel but i get a Bootloop.
Now i switched to PixelOS but it reformats the data partition to ext4 every time at reboot. Can someone tell me how to use f2fs or why it isnt possible anymore ?
F2fs only works on certain roms, crdroid 9 works with f2fs on data and cache. You can flash f2fstab to insert the f2fs format table in to the rom so you can use it, but not sure if this works with encryption.
noah001 said:
Is it Still Possible to use F2FS in Android 13 ?
I tried in LineageOS with No Gravity Kernel but i get a Bootloop.
Now i switched to PixelOS but it reformats the data partition to ext4 every time at reboot. Can someone tell me how to use f2fs or why it isnt possible anymore ?
Click to expand...
Click to collapse
first_damned said:
F2fs only works on certain roms, crdroid 9 works with f2fs on data and cache. You can flash f2fstab to insert the f2fs format table in to the rom so you can use it, but not sure if this works with encryption.
Click to expand...
Click to collapse
Thank you very much, f2fstab did it for me for LineageOS.
Do i need to reflash it after every update ?
noah001 said:
Thank you very much, f2fstab did it for me for LineageOS.
Do i need to reflash it after every update ?
Click to expand...
Click to collapse
I'm not sure sorry