Yeah I just can’t find much information for solving the following error:
ninja: error: 'obj/STATIC_LIBRARIES/bootctrl._intermediates/export_includes', needed
by 'obj/EXECUTABLES/update_engine_sideload_intermediates/import_includes', missing
and no known rule to make it
I see you added some lines to the mk file for boot.ctl, the error message is directly related to this mk file change. Try to build first with out these lines and see what you end with.
Not sure that the files needed to make this are in the Omni twrp source
Is the default recovery.img provided with the SP-Flash tools?
In case flashing a compiled twrp.img fails I can flash the default recovery.img?
Yes - it is there in SP Flash image
Flashing my compiled TWRP image allows me to enter TWRP. Current errors when I tried to make a backup:
Unable to mount storage
Unable to find partition for path '/system'
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder
Unable to find partition for path '/system_root'
E:Bind failed
Failed to mount '/data' (invalid argument)
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (invalid argument)
Unable to find partition for path '/system_root'
Failed to mount '/data' (invalid argument)
Boots into android fine.
Hitting a dead-end trying to get encryption to work on TWRP:
If I can find the kernel source of the Teracube and compile a kernel with dm-verity disabled in the fstab then maybe TWRP will be able to decrypt the partition without having to flash a newly patched boot.img or otherwise wipe user data.
Now that the kernel’s available, will this help bringing TWRP to the teracube?
Makes it much more likely. As always, we’ll need a maintainer.
This project seems incredibly handy for this process as well:
@Sharad, maybe something for the team to take a look at as well (providing an official TeraCube TWRP release).
I was having trouble getting a bootable and decryption working build out of that even with my device connected to my PC via adb
Currently this build works for the Teracube but encryption/decryption does not work so you would need to reset your phone and set it to not use encryption.
Here’s the github issue where I’ve been tracking my progress if you want to take a look.
Russian thread found by googling the camera sensor part number:
New issue found:
Got a successful TWRP image built using kernel sources. I want to thank Kshitij Gupta for helping me resolve some issues with the build process. Going to test it and see if decryption works!
Okay, testing mrmazakblu’s configs with kernel source for a build.
Can someone with a rooted device find the fstab for the phone? My device became unrooted when doing OTA updates.
Any ideas as to where the fstab file might be hiding? I have root via Magisk, though fstab doesn’t seem to be in /etc/, as it would be on Linux.
Also, I found this thread on Stackoverflow.
Let me know what I should be looking for and where! More than happy to help.
It should be in /vendor/etc
Perfect, thanks. I found several files that may be related to fstab.
Here’s the contents of fstab.enableswap.
/dev/block/zram0 none swap defaults zramsize=1073741824
Here’s the contents of fstab.mt6771.
# 1 "vendor/mediatek/proprietary/hardware/fstab/mt6771/fstab.in"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 1 "<command-line>" 2
# 1 "vendor/mediatek/proprietary/hardware/fstab/mt6771/fstab.in"
# 98 "vendor/mediatek/proprietary/hardware/fstab/mt6771/fstab.in"
/dev/block/platform/bootdevice/by-name/system / ext4 ro wait,verify,recoveryonly
/dev/block/platform/bootdevice/by-name/vendor /vendor ext4 ro wait,verify,recoveryonly
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,formattable,quota,resize,reservedsize=128m,forcefdeorfbe=/dev/block/platform/bootdevice/by-name/metadata
/dev/block/platform/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable
/dev/block/platform/bootdevice/by-name/protect1 /mnt/vendor/protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/bootdevice/by-name/protect2 /mnt/vendor/protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/bootdevice/by-name/nvdata /mnt/vendor/nvdata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable
/dev/block/platform/bootdevice/by-name/nvcfg /mnt/vendor/nvcfg ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/devices/platform/externdevice* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/platform/11200000.usb3_xhci* auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/bootdevice/by-name/frp /persistent emmc defaults defaults
/dev/block/platform/bootdevice/by-name/nvram /nvram emmc defaults defaults
/dev/block/platform/bootdevice/by-name/proinfo /proinfo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/lk /bootloader emmc defaults defaults
/dev/block/platform/bootdevice/by-name/lk2 /bootloader2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/para /misc emmc defaults defaults
/dev/block/platform/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/platform/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/bootdevice/by-name/logo /logo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/expdb /expdb emmc defaults defaults
/dev/block/platform/bootdevice/by-name/seccfg /seccfg emmc defaults defaults
/dev/block/platform/bootdevice/by-name/tee1 /tee1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/tee2 /tee2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/scp1 /scp1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/scp2 /scp2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/sspm_1 /sspm_1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/sspm_2 /sspm_2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md1img /md1img emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md1dsp /md1dsp emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md1arm7 /md1arm7 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md3img /md3img emmc defaults defaults
/dev/block/platform/bootdevice/by-name/cam_vpu1 /cam_vpu1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/cam_vpu2 /cam_vpu2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/cam_vpu3 /cam_vpu3 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/gz1 /gz1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/gz2 /gz2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/spmfw /spmfw emmc defaults defaults
/dev/block/platform/bootdevice/by-name/boot_para /boot_para emmc defaults defaults
/dev/block/platform/bootdevice/by-name/odmdtbo /odmdtbo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/dtbo /dtbo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/otp /otp emmc defaults defaults
Let me know if you need any other files!
I am not anticipating needing any others but I will let you know!
Thanks for contributing! Every bit helps 
Hello Teracubers!
Any progress on this?
Update:
Sorry I’ve gotten really busy with the process of job applications and working on an article to get published. After I get another round of revisions done for publication I’ll probably have more time to tinker. I think I’ll end up abandoning getting device encryption to work and disabling AVB like another user did for the 2e
