Make A TWRP Tree For Your Device & Build.md

How To Make A Working TWRP Device Tree For Your MediaTek Device & Start Building Them, Online

This Guide is tested on 64-bit mt6735/53 chipset device. It will also work on any 64-bit and 32-bit devices.

You will need something from your Stock ROM first. Get them all and Try to modify it using the procedure.

Table of contents

• Get Your Stock Recovery
• Extract The Recovery Into Ramdisk & Kernel
• Create A GitHub Repository
• Make Notes from build.prop
• Add Some Stock Files
• Create "Android.mk"
• Create "AndroidProducts.mk"
• Create "BoardConfig.mk"
• Create "omni_$$DEVICE$$.mk"
• Publish the GitHub Repository
• Create An Account in Travis CI
• Create .travis.yml in GitHub Repo
• Fire-Up The Build
• Flash The TWRP
• Troubleshooting

1. Get Your Official Stock Recovery and Stock ROM's build.prop

• You have to get your device's Stock "recovery.img" from the Official Firmware which you can (or maybe can't) get from the device manufacturer's website.
• You have to get the build.prop file (from ROM's /system/build.prop) because there are a few key things that we need.
  • Use ADB to Pull the file by the command adb pull /system/build.prop

2. Extract the ramdisk and kernel zImage

• Use Carliv Image Kitchen to extract the image from Windows or Linux.
• Need a Guide to Use it? Read This.

3. Create A GitHub Repository

• Go to https://github.com/ and SignUp there.
• You have to Create an online GitHub Repository with the name of the device.
  • For Example: something like android_device_Walton_PrimoRX5 or twrp_device_Walton_PrimoRX5 or whatever you want to call it.
• Go to https://github.com/settings/tokens/new/
  • It will take you to a page to create a New personal access token.
  • Name your Token as anything you like, for example: "GitHubToken" and save the Token Value in Notepad. We will need it later.

4. Make Note Of These Things From build.prop

• Write down the keys and their values in Notepad or something of the followings:
• For ease, I am showing from my device. As in "Keys" = "Values"

  ro.build.product=gionee6735_65u_m0                        # Company Given Codename for the Device.
  ro.product.board=Primo_RX5                                # The Board Name for Build.
  ro.product.brand=WALTON                                   # The Brand and The Manufacturer
  ro.product.manufacturer=WALTON                              # can be of the Same Name.
  ro.product.name=Primo_RX5                                 # The Device Name and/or The Codename
  ro.product.device=Primo_RX5                                 # we will be using.
  ro.product.model=Primo RX5                                # A Nickname, we will ignore it.
  ro.mediatek.platform=MT6735                               # The Chipset Platform of the Project.
  ro.mediatek.project.path=device/gionee/gionee6735_65u_m0  # The Original Build Location from Company.
  ro.product.cpu.abi=arm64-v8a                              # Shows if the device is 6-bit or 32-bit.
  

5. Put Some Stock Files In The Folder

• Create a Folder named prebuilt and put the unpacked recovery.img-kernel inside it. Rename that file to zImage
• Create another Folder named recovery. Go in there and create a folder named root
• In the root folder, Put your factory_init.*.rc files, meta_init.*.rc files, ueventd.mt****.rc, init.recovery.mt****.rc files
• Make a new folder named etc inside root. Make a file named recovery.fstab
  • Use THIS FILE as a reference point and edit it.
  • You Have to edit the Mount Addresses (Like /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system), Alternate Short Mount Addresses (Like /dev/block/mmcblk0p20).

    You can get Some of the Mount Addresses by ADB Commands from PC, using adb shell cat /proc/self/mountstats or adb shell cat /proc/self/mounts or adb shell cat /proc/self/mountinfo. Also check whether the Basic FSType (emmc or ext4) of the partitions match with your devices. If you fail to know the Alternate Short Mount Addresses, Just erase them.

• Make a new folder named sbin inside root. Make a file named permissive.sh with File Permission set to "644" by using chmod a+x permissive.sh shell command
  • The file must contain the below content:

    #!/sbin/sh
    
    setenforce 0
    
    # Get your device's block path where "system", "recovery", etc. lives.
    # That can be "/dev/block/bootdevice/by-name" or something like that.
    mkdir -p /dev/block/platform/mtk-msdc.0/by-name/
    busybox mount -o bind /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/ /dev/block/platform/mtk-msdc.0/by-name/

  The above script is for adding Old-Style Mount Points as-well-as New-Style Mount Points to avoid ROM Conflicts.

6. Create A New File Called "Android.mk"

• Make a new File, name it Android.mk, with the below content

  # Replace $$DEVICE$$ with your Device Name's Value. Mine is Primo_RX5.
  # Replace $$BRAND$$ with your Brand's / Manufacturer's Value, Mine is WALTON 
  
  ifneq ($(filter $$DEVICE$$,$(TARGET_DEVICE)),)
  
  LOCAL_PATH := device/$$BRAND$$/$$DEVICE$$
  
  include $(call all-makefiles-under,$(LOCAL_PATH))
  
  endif

7. Create A New File Called "AndroidProducts.mk"

• Make a new File, name it AndroidProducts.mk, with the below content

  # Replace $$DEVICE$$ with your Device Name's Value.
  # Replace $$BRAND$$ with your Brand's / Manufacturer's Value.
  # The part of last line in mine looks like "omni_Primo_RX5.mk"
  
  LOCAL_PATH := device/$$BRAND$$/$$DEVICE$$
  
  PRODUCT_MAKEFILES := $(LOCAL_PATH)/omni_$$DEVICE$$.mk

8. Create The Base File Called "BoardConfig.mk"

• Make a new File, name it BoardConfig.mk, with the below content

  LOCAL_PATH := device/$$BRAND$$/$$DEVICE$$
  
  TARGET_BOARD_PLATFORM := mt6735               # From ro.mediatek.platform, but lowercase value
  TARGET_NO_BOOTLOADER := true
  TARGET_BOOTLOADER_BOARD_NAME := Primo_RX5     # From ro.product.board
  
  # These two are for MTK Chipsets only
  BOARD_USES_MTK_HARDWARE := true
  BOARD_HAS_MTK_HARDWARE := true
  
  # Recovery
  TARGET_USERIMAGES_USE_EXT4 := true
  TARGET_USERIMAGES_USE_F2FS := true            # To add info about F2FS Filesystem Data Block
  # Put The Size of your Recovery Partition below, get it from your "MT****_Android_scatter.txt"
  BOARD_RECOVERYIMAGE_PARTITION_SIZE := 16777216
  # BOARD_USES_FULL_RECOVERY_IMAGE := true      # Uncomment this line if you want to remove size restriction
  BOARD_FLASH_BLOCK_SIZE := 0                   # Might be different for your chip
  BOARD_HAS_NO_REAL_SDCARD := true              # Depricated
  # BOARD_HAS_NO_SELECT_BUTTON := true          # Depricated
  BOARD_SUPPRESS_SECURE_ERASE := true
  BOARD_HAS_NO_MISC_PARTITION := true           # Delete if your partition table has /misc
  BOARD_RECOVERY_SWIPE := true
  BOARD_USES_MMCUTILS := true
  BOARD_SUPPRESS_EMMC_WIPE := true
  BOARD_CHARGER_SHOW_PERCENTAGE := true
  RECOVERY_SDCARD_ON_DATA := true               # Optional: If /sdcard partition is emulated on /data partition 
  
  # TWRP stuff
  TW_EXCLUDE_SUPERSU := true                    # true/false: Add SuperSU or not
  TW_INCLUDE_CRYPTO := true                     # true/false: Add Data Encryption Support or not
  TW_INPUT_BLACKLIST := "hbtp_vm"               # Optional: Disables virtual mouse
  TW_SCREEN_BLANK_ON_BOOT := true
  TW_THEME := portrait_hdpi                     # Set the exact theme you wanna use. If resulation doesn't match, define the height/width
  DEVICE_RESOLUTION := 720x1280                 # The Resolution of your Device
  TARGET_SCREEN_HEIGHT := 1280                    # The height
  TARGET_SCREEN_WIDTH := 720                      # The width
  TARGET_RECOVERY_PIXEL_FORMAT := "RGBA_8888"
  # Set the Brightness Control File Path below (as per your chip/device)
  TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
  TW_SECONDARY_BRIGHTNESS_PATH := /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness
  # Set the Path of Logical Units (LUNs) for Storage below (as per your chip/device)
  TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/devices/platform/mt_usb/musb-hdrc.0.auto/gadget/lun%d/file
  TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/class/android_usb/android0/f_mass_storage/lun/file
  TW_MAX_BRIGHTNESS := 255
  TW_DEFAULT_BRIGHTNESS := 80                   # Set custom brightness, low is better
  
  TW_INCLUDE_NTFS_3G := true                    # Include NTFS Filesystem Support
  TW_INCLUDE_FUSE_EXFAT := true                 # Include Fuse-ExFAT Filesystem Support
  TWRP_INCLUDE_LOGCAT := true                   # Include LogCat Binary
  TW_INCLUDE_FB2PNG := true                     # Include Screenshot Support
  TW_DEFAULT_LANGUAGE := en                     # Set Default Language 
  TW_EXTRA_LANGUAGES := false
  
  # Kernel
  TARGET_IS_64_BIT := true                      # true/false: Determine if the device is 64-bit or not
  TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/prebuilt/zImage
  TARGET_PREBUILT_RECOVERY_KERNEL := $(LOCAL_PATH)/prebuilt/zImage
  # Get the CMDLine, Base, Pagesize and offsets from Unpacked recovery image and put below
  BOARD_KERNEL_CMDLINE := bootopt=64S3,32N2,64N2 androidboot.selinux=permissive
  BOARD_KERNEL_BASE := 0x40078000
  BOARD_KERNEL_PAGESIZE := 2048
  BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x03f88000 --tags_offset 0x0df88000
  
  # Set FSTAB
  TARGET_RECOVERY_FSTAB := $(LOCAL_PATH)/recovery/root/etc/recovery.fstab
  
  TARGET_BOARD_SUFFIX := _64                    # Remove if the device is 32-bit
  TARGET_USES_64_BIT_BINDER := true             # Remove if the device is 32-bit
  
  # Architecture
  # According to the device's architecture (64-bit or 32-bit)
  ifeq ($(TARGET_IS_64_BIT),true)
  TARGET_ARCH := arm64
  TARGET_ARCH_VARIANT := armv8-a
  TARGET_CPU_ABI := arm64-v8a
  TARGET_CPU_ABI2 :=
  TARGET_CPU_VARIANT := cortex-a53
  TARGET_2ND_ARCH := arm
  TARGET_2ND_ARCH_VARIANT := armv7-a-neon
  TARGET_2ND_CPU_ABI := armeabi-v7a
  TARGET_2ND_CPU_ABI2 := armeabi
  TARGET_2ND_CPU_VARIANT := cortex-a53
  TARGET_CPU_ABI_LIST_64_BIT := $(TARGET_CPU_ABI)
  TARGET_CPU_ABI_LIST_32_BIT := $(TARGET_2ND_CPU_ABI),$(TARGET_2ND_CPU_ABI2)
  TARGET_CPU_ABI_LIST := $(TARGET_CPU_ABI_LIST_64_BIT),$(TARGET_CPU_ABI_LIST_32_BIT)
  else
  TARGET_ARCH := arm
  TARGET_ARCH_VARIANT := armv7-a-neon
  TARGET_CPU_ABI := armeabi-v7a
  TARGET_CPU_ABI2 := armeabi
  TARGET_CPU_VARIANT := cortex-a7
  TARGET_CPU_ABI_LIST := $(TARGET_CPU_ABI),$(TARGET_CPU_ABI2)
  endif
  

9. Create A New File Called "omni_$$DEVICE$$.mk" as in "omni_Primo_RX5.mk"

• Make a new File, name it omni_$$DEVICE$$.mk, with the below content

  $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk)
  
  # Add this line if your device is 64-bit
  $(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
  # Otherwise, If you have 32-bit device, add the below line instead of above line
  $(call inherit-product, $(SRC_TARGET_DIR)/product/core_minimal.mk
  
  # Another common config inclusion
  $(call inherit-product, $(SRC_TARGET_DIR)/product/embedded.mk)
  
  # If you are building from OmniROM's minimal source, Inherit some common Omni stuff.
  $(call inherit-product, vendor/omni/config/common.mk)
  
  # Replace $$DEVICE$$ with your Device Name's Value.
  # Replace $$BRAND$$ with your Brand's / Manufacturer's Value.
  PRODUCT_COPY_FILES += device/$$BRAND$$/$$DEVICE$$/prebuilt/zImage:kernel
  # Fles under $(LOCAL_PATH)/recovery/root/ gets automatically copied into recovery
  # PRODUCT_COPY_FILES += $(LOCAL_PATH)/recovery/root/*:root/*
  
  PRODUCT_DEVICE := $$DEVICE$$
  PRODUCT_NAME := omni_$$DEVICE$$
  PRODUCT_BRAND := $$BRAND$$
  PRODUCT_MODEL := $$DEVICE$$
  PRODUCT_MANUFACTURER := $$BRAND$$
  
  # Forcefully add mtp support (adb is already there)
  PRODUCT_DEFAULT_PROPERTY_OVERRIDES += \
      persist.sys.usb.config=mtp
  
  # Add fingerprint from Stock ROM build.prop
  PRODUCT_BUILD_PROP_OVERRIDES += \
      # These lines are from my device. You MUST Replace yours.
      BUILD_FINGERPRINT="WALTON/Primo_RX5/Primo_RX5:6.0/MRA58K/1465782828:user/release-keys" \
      PRIVATE_BUILD_DESC="full_gionee6735_65u_m0-user 6.0 MRA58K 1465782828 release-keys"

10. Publish the GitHub Repository

• If you have done the above process entirely online inside github.com, then it is okay.
• But, if you have done the above things Locally on your PC, Just upload the entire Folder or git push to server.

  No detail or tutorial will be provided here. This is A-B-C of Git, Man!

11. Create An Account in Travis CI for Building the Recovery

• Go to https://travis-ci.org/ and SignUp there using GitHub.
• Go to https://travis-ci.org/profile/ and Add the Repository there by tapping on the Radio Button switch at the right side of the Repository name.
• Now, On its further right corner, you will find an individual repository Settings button. Click it. You will be on the Repository's Settings Page Now.
  • Go below where "Environment Variables" is written.
  • Add "GitOAUTHToken" as New Environment Variables' Name and put your GitHub Token's value as it's Value here.

12. Create A File Named .travis.yml in GitHub Repo

• To Start the Build Process, go to your created TWRP Device Tree in GitHub.
• Make a file named .travis.yml with below content

  os: linux
  dist: bionic
  language: generic
  sudo: required
  git:
    depth: 1
  addons:
    apt:
      update:
        - true
  services:
    - docker
  before_install:
    - docker pull fr3akyphantom/droid-builder:latest
  before_script:
    - cd $HOME && mkdir twrp
    # download the TWRP Compressed Source Files from PhantomZone54's Release
    # Uncomment & Use below line If Building for Lollipop-based Devices
    # - TWRP_SOURCE="https://github.com/PhantomZone54/twrp_sources_norepo/releases/download/v3.3.1-20200222/MinimalOmniRecovery-twrp-5.1-norepo-20200222.tar.xz"
    # Use below line If Building for Marshmallow-based Devices
    - TWRP_SOURCE="https://github.com/PhantomZone54/twrp_sources_norepo/releases/download/v3.3.1-20200222/MinimalOmniRecovery-twrp-6.0-norepo-20200222.tar.xz"
    # Uncomment & Use below line If Building for Nougat-based Devices
    # - TWRP_SOURCE="https://github.com/PhantomZone54/twrp_sources_norepo/releases/download/v3.3.1-20200222/MinimalOmniRecovery-twrp-7.1-norepo-20200222.tar.xz"
    - wget -q ${TWRP_SOURCE} -O $HOME/twrp.tar.xz
    - tar -xJf twrp.tar.xz --directory $HOME/twrp/ && rm twrp.tar.xz
  script:
    # Replace your $$USERNAME$$, $$REPO_URL$$, $$BRAND$$, $$DEVICE$$
    - cd $HOME/twrp/ && git clone https://github.com/$$USERNAME$$/$$REPO_URL$$.git device/$$BRAND$$/$$DEVICE$$
    - rm -rf bootable/recovery && git clone https://github.com/omnirom/android_bootable_recovery -b android-9.0 --depth 1 bootable/recovery
    - |
      docker run --rm -i -e USER_ID=$(id -u) -e GROUP_ID=$(id -g) -v "$(pwd):/home/builder/twrp/:rw,z" -v "${HOME}/.ccache:/srv/ccache:rw,z" fr3akyphantom/droid-builder bash << EOF
      cd /home/builder/twrp/
      source build/envsetup.sh
      # Choose build flavor as "eng" or "userdebug"
      BUILD_FLAVOR="eng"
      lunch omni_$$DEVICE$$-${BUILD_FLAVOR}
      make -j$(nproc --all) recoveryimage
      exit
      EOF
  after_success:
    - export version=$(cat bootable/recovery/variables.h | grep "define TW_MAIN_VERSION_STR" | cut -d '"' -f2)
    - cp $HOME/twrp/out/target/product/$$DEVICE$$/recovery.img $HOME/twrp/TWRP-$version-$$DEVICE$$-$(date +"%Y%m%d")-Unofficial.img
    - cd $HOME/twrp/
    # Optional: You might need to switch from https://transfer.sh to https://file.io
    # - curl -s --upload-file TWRP-$version-$$DEVICE$$-$(date +"%Y%m%d")-Unofficial.img https://transfer.sh/ && echo ""
  deploy:
    skip_cleanup: true
    provider: releases
    # The secret api_key will be loaded from the environment variables
    api_key: $GitOAUTHToken
    file_glob: true
    file: $HOME/twrp/*.img
    on:
      tags: false
      repo: $$USERNAME$$/$$REPO_URL$$ # Optional: If you want to deploy on different repository
      branch: master # Optional: Needs to be exact as the config branch
  branches:
    only:
      - master # Set travis builder branch(es) names
    except:
      - /^(?i:untagged)-.*$/
      - /^v\d+\.\d+(\.\d+)?(-\S*)?$/

13. Fire-Up The Build

• When you save the .travis.yml file for the first time, the build will automatically start.
  • You can see the progress of the build on https://travis-ci.org/$$USERNAME$$/$$REPO_URL$$/
• After the first build, you can see the result on the GitHub Repository's Releases Page at https://github.com/$$USERNAME$$/$$REPO_URL$$/releases/
  • You can also download the file from viewing the Travis CI log, where the script uploaded it into https://transfer.sh/

14. Flash and Enjoy

• Flash the newly-build Recovery. It is better Not to Use with Stock ROM.

15. Troubleshooting Recovery Boot

• If The Recovery does not Boot,
  • Unpack the Stock Recovery Image again, and double-check properties used in TWRP Tree
  • Double-check files that are included in the Tree
• If the Recovery starts Upside-Down,
  • Edit BoardConfig.mk and insert the below line before the include part (last line)

    BOARD_HAS_FLIPPED_SCREEN := true

hello sir i want to ask you again today i tried to build my twrp using the DT and i successully build it my question is what image should i pick?

It's a very simple answer that comes from your action. When you had the img file built, what partition/option name were you given? mka recoveryimage ??

Obviously some parts confirm the choice: https://github.com/lopestom/twrp_device_oppo_CPH1717/blob/d7512fa874098cb146069c0151bcccae5c272122/recovery.fstab#L5 https://github.com/lopestom/twrp_device_oppo_CPH1717/blob/d7512fa874098cb146069c0151bcccae5c272122/BoardConfig.mk#L36 https://github.com/lopestom/twrp_device_oppo_CPH1717/blob/d7512fa874098cb146069c0151bcccae5c272122/recovery.fstab#L5

So obviously the file can only stand out: recovery.img

thank you sir

Here's the log file

Click to open

gitpod /workspace/empty/twrp (main) $ mka recoveryimage
build/make/core/soong_config.mk:196: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.
build/make/core/soong_config.mk:197: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=16.1.0
TARGET_PRODUCT=omni_CAP_sprout
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-6.1.54-060154-generic-x86_64-Ubuntu-22.04.3-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=SP2A.220405.004
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=device/hmd/CAP_sprout
============================================
[ 29% 27/93] including bootable/recovery/Android.mk ...
bootable/recovery/prebuilt/Android.mk:441: warning: vendor_hw: bootable/recovery/prebuilt/relink.sh out/target/product/CAP_sprout/recovery/root/vendor/bin/hw
[ 86% 80/93] including system/sepolicy/Android.mk ...
system/sepolicy/Android.mk:57: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.
system/sepolicy/Android.mk:62: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.

ninja: no work to do.

the source: https://github.com/kinguser981/Nokia-5.3-twrp/tree/android-12.0

what is the problem??? ninja: no work to do.

Here's the log file
PLATFORM_VERSION=16.1.0
TARGET_PRODUCT=omni_CAP_sprout

ninja: no work to do.
the source: https://github.com/kinguser981/Nokia-5.3-twrp/tree/android-12.0

what is the problem??? ninja: no work to do.

android-12.0 => update your knowledge
https://gist.github.com/lopestom/3c1f3eaa66248c56e61acf19ddd4b96c#build-levels

hlo sir i am building twrp for my device realme 9 pro plus ,i got twrp size error how to solve this here is my dt : https://github.com/DG-HEART/test_ossi_twrp can you help me out max size of recovery partition is 40mb

BOARD_BOOTIMAGE_PARTITION_SIZE := 41943040
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 41943040

That's a normal Max size of the partition? 40MB?
So, very attempts but not know if encrypt/decrypt works. Using some flags like TW_EXCLUDE_ can help or not.

TW_EXCLUDE_PYTHON := true
TW_EXCLUDE_NANO := true
TW_EXCLUDE_TWRPAPP := true
TW_EXCLUDE_MTP := true
TW_EXCLUDE_TZDATA := true
TW_EXCLUDE_BASH := true
TW_EXCLUDE_LPTOOLS := true
TW_EXCLUDE_LPDUMP := true`

But looking your DT so has only one file in the \recovery\root
https://github.com/DG-HEART/test_ossi_twrp/tree/main/recovery/root

In that condiction the size of img file compiled maybe have 33~36MB.
But if you putting more files in the \vendor\*.* to try encrypt/decrypt process so need minimal specific/special files.

You can try compiling with flags mentioned and put files - one by one - to know how size have in the final.
That's not easy and maybe have Large size file in the final. But that was the company's choice.

Bro go to this Telegram gc and ask ur questions plz 👍 .

If you not write here to help so
Can you send PM to him......

Build completed without size error but not 33~36 its 40mb what to do sir

Bro,
If you write:

BOARD_BOOTIMAGE_PARTITION_SIZE := 41943040
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 41943040

The img file compiled already have 40MB. This is the max size of partition and you can use img file for flash.
if put nothing or more like 67108864 so the compiled img file have 64MB. But you cannot flash that file in the device.

Lopestom sir i think you have released twrp for rmx3393 can you help out how to build without size error I am facing size error I am also building for the same device, is there any way to compress ramdisk into smaller size

I really not understand what you need:
1- Have a compiled file with 40MB --> Okay
2- TWRP compiled img file start in the device?
3- step -2 Okay. Want encrypt/decrypt mode?
3.1- step -2 not work?

What I undertand:

Click to open

You need functional TWRP with encrypt/decrypt mode.
But I wrote to three people about this issue that to have a fully functional TWRP on the RMX3393, the encryption/decryption files could not be placed in the device tree. This is all because the encryption/decryption files add up to a size much larger than 40MB. Even if you manage to have a TWRP with a size of 64MB, then unpack and repack it to know its real size.
Example: after the img file was repackaged, the actual size was 46MB. Well, so did you make the img file with all the TW_EXCLUDE_ flags?
Yes: So choose to have TWRP without encryption/decryption or you should study/learn how to increase the size of the boot.img partition;
No: Then try.

I can't help with this because I myself have a device with A12 and a maximum partition of 32MB. Whenever I compiled the img file with all the encryption/decryption files (with a minimum part of specific/correct files, so there are very few files in quantity and size), the final size of the img file is 33/35MB and I cannot flash it it on the device. I tried removing more files. But encryption/decryption always failed. There are encryption/decryption files that have a minimum size of 1~1.2MB and even if you try to remove this file, the final size of the img file will still not be the same as that of the device partition. So you try to remove more files and in the end you have a good sized img file. But it remains the same, encryption/decryption always failed.
I have the same direction/option that I wrote for you above.

Quick question: How do I compile this without Travis CI? I have admin access to a flavour of Arch Linux, if Arch would work.

Quick question: How do I compile this without Travis CI? I have admin access to a flavour of Arch Linux, if Arch would work.

What Android & Kernel version?

I have the tree built, I just need to make the boot image. (I have a A/B partitioned system, and I used twrpdtgen.)

I am using Android 12, with a MTK Helio G37. The phone's codename is (Motorola) Maui.

I have the tree built, I just need to make the boot image. (I have a A/B partitioned system, and I used twrpdtgen.)

I am using Android 12, with a MTK Helio G37. The phone's codename is (Motorola) Maui.

This gist How To Make A Working TWRP Device Tree For Your MediaTek Device is for <A9 and maybe you need read more.
Update mind and development: Device Tree for A10+

Quick question: How do I compile this without Travis CI? I have admin access to a flavour of Arch Linux, if Arch would work.

Read Tutorial Using online resource to build custom recovery

I have the tree built, I just need to make the boot image. (I have a A/B partitioned system, and I used twrpdtgen.)
I am using Android 12, with a MTK Helio G37. The phone's codename is (Motorola) Maui.

This gist How To Make A Working TWRP Device Tree For Your MediaTek Device is for <A9 and maybe you need read more. Update mind and development: Device Tree for A10+

Quick question: How do I compile this without Travis CI? I have admin access to a flavour of Arch Linux, if Arch would work.

Read Tutorial Using online resource to build custom recovery

Thank you for the info. I'm currently just a dumb teenager, so any help is greatly appreciated.

u r not dumb . text on gc . @build_twrp - view group telegram TWRP Building Support Group <https://telegram.im/build_twrp>

…

On Thu, Feb 22, 2024 at 5:05 AM Caedmon Craig ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ I have the tree built, I just need to make the boot image. (I have a A/B partitioned system, and I used twrpdtgen.) I am using Android 12, with a MTK Helio G37. The phone's codename is (Motorola) Maui. This gist How To Make A Working TWRP Device Tree For Your MediaTek Device is for <A9 and maybe you need read more. Update mind and development: Device Tree for A10+ <https://gist.github.com/lopestom/c4a2648958db5c3db03d32033a3583cd> Quick question: How do I compile this without Travis CI? I have admin access to a flavour of Arch Linux, if Arch would work. Read Tutorial Using online resource to build custom recovery <https://gist.github.com/lopestom/d85ce99bb244d308c5e681db31018626> Thank you for the info. I'm currently just a dumb teenager, so any help is greatly appreciated. — Reply to this email directly, view it on GitHub <https://gist.github.com/lopestom/a5e6b690028cedd47d7e648a1035b358#gistcomment-4925094> or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASVMBMA24Q2ZKZVNZBCJU5LYU2OGVBFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVEYTANBQGA3DQNBWU52HE2LHM5SXFJTDOJSWC5DF> . You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .