search

ADeadTrousers / twrp_device_Unihertz_Atom_LXL

Common device tree for the Unihertz Atom L and XL
Apache License 2.0
7 stars 3 forks source link

fstab needs some missing flags (v2) #1

Closed ADeadTrousers closed 3 years ago

ADeadTrousers commented 3 years ago

According to various guides for implementing TWRP on unsupported devices there are several flags in the so called "fstab v2" to get the recovery to better recognize encrypted directories (see ADeadTrousers/twrp_device_Unihertz_Atom_XL_EEA#1) and removeable devices (sdcard, otg). Sadly I'm not that fit in all the possibilities to setup a working fstab to transform the current one to TWRP standards. I found a guide specifically for mediatek devices and it also offers a useable "template": https://gist.github.com/lopestom/a5e6b690028cedd47d7e648a1035b358 But the partitons don't add up. I'm sure I don't need every entry covered, especially the ones mentioning "cam", but others I think that are need are not covered at all. I belive it is because the guide doesn't use a super.img.

ADeadTrousers commented 3 years ago

I tried to use another tree as a template https://github.com/N00bTree/android_device_umidigi_fiona but it turns out TWRP is not quite ready for Android 10 and the changes made to it in form of super-partition. So no TWRP for now. At least the changed fstab offers a little bit of structuring. The problem with the encrypted filesystem persists though. I don't seem to get at least a "please enter the decryption key" dialog to work.

ADeadTrousers commented 3 years ago

Finally the update 3.5.0 for TWRP is out. But I still get various errors regarding the mounting of partitions: "unable to update logical partition: /system_image" "unable to update logical partition: /vendor_image" "Failed to mount /system_root (Permission denied)" "Failed to mount /vendor (Permission denied)" I think there is something "wrong" with the mountpoints in the fstab but for now I couldn't find any other TWRP-10 Repository that did it otherwise. Even if "/system_root" can be "/system" again (which was a workaround for TWRP-9) I'm certain that at least the vendor part should have worked.

ADeadTrousers commented 3 years ago

The original fstab seems to work now: ad7a28e522e237421472358da41247cec0487105 I still need to test it with the next LineageOS build though.

ADeadTrousers commented 3 years ago

Everything related to fstab seems to be working now: 3ab492c5830867d2d677c58b06a9080fbfe5b028