Hi! I've got lineage 14.1 and I want to format /data as ext4 to avoid flashing the f2fs module since I install a lot of modules and it exceeds the size of /cache resulting in a bootloop. I also installed Valyrian kernel and everything works almost flawlessly except the camera, it is not showing
in the app drawer and I cannot open it. It's installed but it doesn't open . And also the torch isn't working ( I think it's related to the camera app that doesn't work). The question is: can I format /data as ext4? Does the ROM start?
Sorry if it seems a noob question, but I don't want to brick it, it's my primary device. Thanks in advance.
Edit: delete post
Related
Hi people !
I've just one question, related to new TWRP (2.8.5.1) and CM12. I've seen some commits on CM12 changelog that makes me thing that, perhaps, CM12 now supports F2FS partitions.
While TWRP is now able to format in F2FS, is it possible to use F2FS with CM12 ? If yes, with which partitions ? /system, /cache, /data... ?
Also, is it possible to restore a Nandroid backup made in EXT4 in a F2FS partition ? (to "convert" it for /data without losing it).
Thanks for your help.
same question
Same question, but I want to use it with a i9192, sorry for comment in a LG thread!
Anyone here experienced with system partitions and dependancies?
Im trying to run my n7105 in f2fs system wide.
ive found a few small glitches that cause me greif.
1. if i format the cache to f2fs. twrp cant mount data afterwards.
installing roms works fine but you lose your modem/baseband. especially if its a pre 4.3 modem.
2. if i format my sdcards to f2fs, very difficult to mount them as MTP for pc file transfer.
is there something im doing wrong with cache file system?
maybe you just cant have it f2fs? ext4 works fine with the rest of the system being f2fs.
also. i just found out i can stock rom then restore backup and it formats partitions back to f2fs for me.
no more double flashing and formatting.. yay.
any other tips or tricks when dealing with system partitions would be great.
also. whats the deal with f2fs and encryption being a problem?
Hi!
I got twrp v2.8.6.0 on s4 mini gt-i9190, and wanna try f2fs on kitkat roms.
The problem is that i did format f2fs to system, cache, and data folders. But when i flash ANY rom (carbon, cm11 M12, slimkat, etc etc) the system folder gets reverted to EXT4.
Tried the "force f2fs format" option in settings (twrp 2.8.1.0) but its the same, after the rom flash, the partition gets reverted to EXT4.
No wondes whats happening, sure you guys can help.
Thanks in advance! And i apologize for my bad english...
Attached a screenshot where you can see
UP!
Any hint?
UP!
Hello.
I tried Syberia 3 but had some bugs like frozen interface etc and had to reboot when it happened
Then I wanted to go back to a stable ROM, LineageOS 16.
However, I am so brain dead when it comes to F2FS or Ext4 and device encryption.
Can anyone explain me:
When does the device become encrypted?
When talking about F2FS, is it for all cache data and system or only one/some specific?
When you have the famous "encryption unsuccessfull, what should you do? Set file system to ext4? If yes, which one? System, data, cache? All 3?
Thanks in advance, my phone is softbricked ATM. Even the stock firmware trick didn't worked this time ?
Kicroy said:
Hello.
I tried Syberia 3 but had some bugs like frozen interface etc and had to reboot when it happened
Then I wanted to go back to a stable ROM, LineageOS 16.
However, I am so brain dead when it comes to F2FS or Ext4 and device encryption.
Can anyone explain me:
When does the device become encrypted?
When talking about F2FS, is it for all cache data and system or only one/some specific?
When you have the famous "encryption unsuccessfull, what should you do? Set file system to ext4? If yes, which one? System, data, cache? All 3?
Thanks in advance, my phone is softbricked ATM. Even the stock firmware trick didn't worked this time ?
Click to expand...
Click to collapse
If u want f2fs, then all will be on f2fs..if u want ext4, then only data pertition will be on ext4 and rest will be on f2fs
Hello everyone, first post here.
[pre-submitting edit: I'm new so no external links, sorry if they are garbage]
tl;dr
Installed LOS 16 on crackling, the LOS Wiki should be updated, here the issues I had to solve:
When preparing the phone, TWRP complains about /system having squashfs filesystem; solved by formatting the /system with ext4 filesystem;
Sideloading LOS 16 on stock Android 7.1.2 gives an unbootable OS; solved by downgrading first to stock CynogenOS (Android 6);
Encrypting the phone does not work; solved by resizing /data via TWRP.
Long story
I installed LineageOS on a Wileyfox Swift running the stock Android 7.1.2, I followed the wiki wiki_dot_lineageos_dot_org/devices/crackling/install but I had to solve a couple of issues that were not documented there. Before proposing any changes to the wiki, I would like first to understand if the issues are well known and what causes them.
Issue 1: TWRP complains about /system partition being formatted with the squashfs filesystem
Following the wiki, at wiki_dot_lineageos_dot_org/devices/crackling/install#installing-lineageos-from-recovery, step 5 says:
...tap Advanced Wipe, then select the Cache and System partitions and then Swipe to Wipe.
Click to expand...
Click to collapse
here TWRP complains about the partition /system being formatted as squashfs. The problem does not permit a successful sideloading of LineageOS, and the solution seems to be formatting the partition with the filesystem ext4.
Questions:
Is it common to have the partition /system with squashfs filesystem? Or is it only the Swift having it like this?
TWRP complains about it just because it does not support squashfs? Or are there other reasons?
Do other recoveries support the squashfs filesystem?
Issue 2: LineageOS 16 is unbootable if sideloaded on stock Android 7.1.2
If sideloading LOS 16 on stock Android 7.1.2, the phone only reboots at fastboot. I found some possible solutions at www_dot_reddit_dot_com/r/LineageOS/comments/9pcgrh/cant_start_lineage_stuck_at_fastboot/: downgrading first at CyanogenOS, or installing crDroid, or using the FoxyKernel. As per the discussion, the problem looks like being the 'new bootloader'. I tried downgrading first to CyanogenOS, which should have installed the 'old bootloader', and it solved the problem.
Questions:
When was the 'new bootlaoder' introduced (Wileyfox Android 7?) and what is wrong with it?
Does the problem lies at kernel level? If so, only crDroid and FoxyKernel have the required changes?
Issue 3: Encrypting the phone fails because of something wrong with the /data partition
After a fresh installation and first configuration of LOS, encrypting the phone just fails: the phone shows a black screen, it flashes the main screen after every few seconds, then it reboots after an hour or so without being encrypted at all. The solution is suggested at gitlab_dot_com/LineageOS/issues/android/-/issues/700: to perform a filesystem resize of the /data partition via TWRP.
Questions:
What is wrong with the /data partition after following the LOS installation procedure?
What does the TWRP filesystem resizing actually do? I don't think it increased/decreased the /data partition at all!
And bonus question: Did someone else experienced the same issues? Are they known?
Had issue 2 once, found a workaround thanks to @beroid, https://forum.xda-developers.com/showpost.php?p=66158015&postcount=2 can't answer precisely your question unfortunately.
The official OS messed with the file systems when they went from the original CyanogenOS based Android 6 to whatever they used for 7 with the Russian launcher