Yes, reboot doesn’t change anything.
It is more likely that those errors are because you booted to android and that encrypted /data
You might have to back up your mount fixes and reformat that partitiion and re-apply fixes…
So, I have backup-ed all mount fixes.
And I did format data, but here is some error: unable to decrypt FBE device
Should I ignore this error and continue with SF OS installation or I need extra step for this?
Try booting to recovery again to see if the error still shows up
Yes, the error still shows up when I format the /data
I really don’t know what that is. Maybe try to search on xda-forums too. Or maybe it is not important, dunno
Solved. I have booted to Android:
'# fastboot boot magisk_patched-27000_XxPuq.img
And after that to TWRP recovery, and no error after that
1 Like
I have successfully re-installed SailFish on the phone.
1 Like
If you want to boot safely into Android you need a modified vendor image with /vendor/etc/fstab.qcom edited by removing the fileencryption- or encryptable-option from userdata.
I am not sure if you can remount r/w on device, I think the image on your PC and editing + flashing vendor is needed. In your case you need to reboot in fastbootd mode for the super partition to allow updating vendor.
I don’t really need to boot into Android. If this change help to fix camera and sound on incoming call, then I ready try to modify vendor.img
Here is the file content of “/vendor/etc/fstab.qcom” - https://paste.fo/raw/faaa5c7d601d
cat /vendor/etc/fstab.qcom
'# cat /vendor/etc/fstab.qcom '# Copyright (c) 2018,2019 The Linux Foundation. All rights reserved. '# '# Redistribution and use in source and binary forms, with or without '# modification, are permitted provided that the following conditions are '# met: '# * Redistributions of source code must retain the above copyright '# notice, this list of conditions and the following disclaimer. '# * Redistributions in binary form must reproduce the above '# copyright notice, this list of conditions and the following '# disclaimer in the documentation and/or other materials provided '# with the distribution. '# * Neither the name of The Linux Foundation nor the names of its '# contributors may be used to endorse or promote products derived '# from this software without specific prior written permission. '# '# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED '# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF '# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT '# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS '# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR '# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF '# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR '# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, '# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE '# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN '# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.'# Android fstab file.
'# The filesystem that contains the filesystem checker binary (typically /system) cannot
'# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK'#TODO: Add ‘check’ as fs_mgr_flags with data partition.
'# Currently we dont have e2fsck compiled. So fs check would failed.'# <mnt_point> <mnt_flags and options> <fs_mgr_flags>
system /system ext4 ro,barrier=1,discard wait,avb=vbmeta_system,logical,first_stage_mount,avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey
product /product ext4 ro,barrier=1,discard wait,avb=vbmeta_system,logical,first_stage_mount
vendor /vendor ext4 ro,barrier=1,discard wait,avb,logical,first_stage_mount
odm /odm ext4 ro,barrier=1,discard wait,avb,logical,first_stage_mount
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,noatime,nodev,barrier=1 wait
/dev/block/by-name/metadata /metadata ext4 noatime,nosuid,nodev,discard wait,formattable,wrappedkey,first_stage_mount'# Add fs_mgr flag - sysfs_path=/sys/devices/platform/soc/xxxx.[ufshc|sdhci] to userdata entry, based on UFS|eMMC device.
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,nodiscard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait
/devices/platform/soc/a600000.ssusb/a600000.dwc3/xhci-hcd.0.auto* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
'# Need to have this entry in here even though the mount point itself is no longer needed.
'# The update_engine code looks for this entry in order to determine the boot device address
'# and fails if it does not find it.
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=1073741824
What type of change is needed for this?
This is for android booting only.
For the other priblems, run ngfd as previously but as user respectively grab camera logs as in my previous post
remove fileencryption=ice,
(p.s. it seems the details/summary combo + pre does not scroll horizontally, was a bit hard to find that)