You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
Looks like the mount option 'fileencrypt' is considered to be parameterless, thus only this world itself is deleting from userdata entry. In the case it has some parameters that leads to the spare tail inside fstab line, which prevents userdata partition mounting. The result is continuous bootlooping. Here is the diff between ramdisks unpacked from both original and patched bootimages:
Suggestion:
Use regexp like ,f[a-z]*encrypt=*[^$,]* to delete from fstab while patching boot. It would remove both 'fileencrypt' and 'forceencrypt' options together with thier parameters and leading commas.
The text was updated successfully, but these errors were encountered:
Issue:
Looks like the mount option 'fileencrypt' is considered to be parameterless, thus only this world itself is deleting from userdata entry. In the case it has some parameters that leads to the spare tail inside fstab line, which prevents userdata partition mounting. The result is continuous bootlooping. Here is the diff between ramdisks unpacked from both original and patched bootimages:
--- ramdisk.orig/fstab.mt6771 2021-03-09 08:18:57.899091100 +0200 +++ ramdisk.patched/fstab.mt6771 2021-03-09 08:20:18.814931800 +0200 @@ -19,7 +19,7 @@ -/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,formattable,quota,resize,reservedsize=128m,checkpoint=block,fileencryption=aes-256-xts +/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,formattable,quota,resize,reservedsize=128m,checkpoint=block,=aes-256-xts
Suggestion:
Use regexp like
,f[a-z]*encrypt=*[^$,]*
to delete from fstab while patching boot. It would remove both 'fileencrypt' and 'forceencrypt' options together with thier parameters and leading commas.The text was updated successfully, but these errors were encountered: