MTK F2FS Encryption issues

TrebleDroid / treble_experimentations

Scripts to automatically build/CI/Release TrebleDroid GSI

Other

203 stars 26 forks source link

MTK F2FS Encryption issues #34

Open Osanosa opened 1 year ago

Osanosa commented 1 year ago

My device is Blackview BV9200 with g96 CPU and A12 vendor. Currently GSI won't start "as is" until I disable encryption by modifying fstab. With encryption disabled system boots but a lot of things are broken: network, Bluetooth, sim cards, can't install screen lock, etc. I tried changing /data type to ext4 yet the system doesn't boot, I think that might be related to vendor/build.prop ro.vendor.mtk_f2fs_enable=1 line tho I haven't verified it yet.

What steps should I take (logs, patches, etc)?

Osanosa commented 1 year ago

Screenshot_20230526-012516

phhusson commented 1 year ago

Go back to everything STOCK UNMODIFIED OEM:

stock unmodified recovery
stock unmodified boot.img
stock unmodified vendor

Use Factory reset option from recovery.

Does the issue still happen then? If yes, then take Google's GSI:

Go to ci.android.com
Select aosp-android13-gsi branch
click on the highest row, aosp_arm64 column
in artifacts, download aosp_arm64-img-xxxx.zip
Extract its system.img and flash it

Does the issue still happen?

Osanosa commented 1 year ago

Thanks for the provided steps. As of now I can say that dsu caused dm-verity on stock with a locked bootloader.

Osanosa commented 11 months ago

Yes, it still does