Bro's teaching hard, pro af

Transsion Vendor Boot Recovery Tree Generator V2

What the Script Does – A Complete Overview
The Transsion Vendor Boot Recovery Tree Generator is a Python tool that automates the creation of device trees for custom recoveries (TWRP, PitchBlack, OrangeFox) from a vendor_boot image (or an unpacked directory). It intelligently scans and extracts necessary components from the provided partitions, handles multiple sources, and generates a ready‑to‑build device tree.

Core Features
Multi‑Recovery Support – Generate trees for TWRP, PBRP (PitchBlack), or OFRP (OrangeFox) with correct product prefixes (twrp_, pb_, fox_).

Extended Partition Input – Accept paths to vendor, vendor_dlkm, odm, product, system_ext. The noscript copies:

All .rc files → directly to recovery/root

All fstab.* files → to first_stage_ramdisk/

Referenced binaries and their library dependencies (policy‑controlled)

Firmware required by kernel modules

Auto‑Detection – Scans init noscripts to find referenced binaries and kernel modules. Uses readelf to resolve library dependencies.

Module Filtering – Keep only essential kernel modules based on built‑in patterns or a custom whitelist/blacklist.

Vendor Blob Policy – Control how much is copied from vendor partitions (minimal / normal / full).

Fstab Conflict Handling – When multiple fstab sources exist (ramdisk, vendor, etc.), choose the primary via policy (ramdisk / vendor / prompt); alternatives are saved as backups.

Batch Processing – Process multiple devices using a CSV file (--list); --continue-on-error keeps going if one fails.

Git Integration – --git initialises a git repository and commits the generated tree.

Ownership Fix – If run with sudo, automatically chowns the output tree back to the original user (no root‑owned files).

Dry‑Run & Interactive Modes – --dry-run previews actions; --interactive lets you confirm/correct detected values.

Logging – --log-file saves logs (auto‑creates directories, timestamped files).

🚀 Complete List of Flags & Options

Flag Denoscription Options / Values

--vendor-boot PATH Required. Path to vendor_boot.img or a directory containing unpacked contents (ramdisk, dtb, header). A valid file or directory path.

-o, --output DIR Output directory (default: ./output). A directory path.

-v, --verbose Enable verbose logging. (flag)

--keep-temp Keep temporary working directory after completion. (flag)

--device-codename NAME Manually specify device codename (e.g., Infinix-X6711). String.

--market-name NAME Manually specify market name (e.g., "Infinix GT 30 PRO"). String (use quotes if contains spaces).
--vendor-dlkm PATH Path to extracted vendor_dlkm partition (kernel modules). A directory path.

--vendor PATH Path to extracted vendor partition (binaries, libraries, .rc, fstab). A directory path.

--dtbo PATH Path to dtbo.img (if not already in input). A file path.

--recovery TYPE Target recovery. twrp (default), pbrp, ofrp

--maintainer NAME Maintainer name (default: アンドレイ). String.

--no-common Disable automatic cloning of common device trees. (flag)

--no-patch Skip patching adaptive-ts.ko. (flag)

--log-file PATH Save logs to file or directory. If a directory, creates a timestamped log inside. A file or directory path.

--dry-run Simulate actions without writing any files. (flag)

--interactive Interactively confirm/correct detected values. (flag)

--module-policy POLICY Policy for including kernel modules. all (keep all), essential (keep modules matching built‑in patterns), minimal (keep only explicitly whitelisted). Default: essential.


--vendor-policy POLICY Policy for copying vendor blobs. minimal (only referenced binaries), normal (referenced binaries + dependencies), full (all vendor binaries). Default: normal.

--fstab-policy POLICY Policy for choosing primary fstab when multiple sources exist. ramdisk (prefer from vendor_boot), vendor (prefer from vendor), prompt (ask user). Default: prompt.

--git After generation, initialise a git repository and commit the tree. (flag)

--continue-on-error continue even if error

Smash?

Is completed? or do we need to add some features? suggest features if ever LOL

next project maybe = another refined sepolicy patcher

Me at prom XD

What could it be?