[RECOVERY] TWRP 3.5.2 | Unihertz Jelly 2

[karoooo]

Hi, Jelly2_JP has been updated to android 11.
So I tried to build TWRP for android 11.
However, my PC was too poor and the PC went down during the build.
(This is the PC which I built TWRP for android 10.)
Is the option -j used incorrectly?

My build operation
$ cd ~/twrp11
$ repo init -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-11
fatal: couldn't find remote ref refs/heads/twrp-11

$ repo init -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git -b twrp-11
$ repo sync --force-sync
$ cp -r ~/twrp10/device/Unihertz ~/twrp11/device
$ vi device/Unihertz/Jelly2_JP/omni_Jelly2_JP.mk
$(call inherit-product, vendor/twrp/config/common.mk)
#$(call inherit-product, vendor/omni/config/common.mk)
#$(call inherit-product, vendor/omni/config/gsm.mk)

$ export ALLOW_MISSING_DEPENDENCIES=true
$ . build/envsetup.sh
$ lunch omni_Jelly2_JP-eng
$ mka -j 1 recoveryimage
************************************************************
You are building on a machine with 7.38GB of RAM

The minimum required amount of free memory is around 16GB,
and even with that, some configurations may not work.

If you run into segfaults or other errors, try reducing your
-j value.
************************************************************

 

[karoooo]

I found "How to build AOSP with 8GB of RAM".
I tried the build again and it was completed successfully!

$ sudo apt install zram-config
$ export _JAVA_OPTIONS="-Xmx4g"
$ mka -j1 recoveryimage
#### build completed successfully ####

I wrote recovery.img to my Jelly2_JP and tried to boot it.

$ fastboot flash --disable-verification --disable-verity vbmeta vbmeta.img
$ fastboot flash --disable-verification --disable-verity vbmeta_system vbmeta.img
$ fastboot flash --disable-verification --disable-verity vbmeta_vendor vbmeta.img
$ fastboot flash recovery recovery.img
$ fastboot reboot recovery

However, the orange state screen was displayed twice and was booted by the system instead of the recovery.
I tried to boot recovery again.

$ adb reboot recovery

It was booted by the official recovery.
I think that the recovery partition has been overwritten during the boot process.