Brax3_IodeOs/brax3_spflash_vendor
4
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
1 commit 1 branch 0 tags 1.3 MiB
  • Shell 100%
Find a file
Exact
akadmin bfd454ba50 Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 
Adds the 9 always-same vendor entries (preloader variants, MT6835
scatter, MTK Download Agent, carrier modem image, flash.sh wrapper)
used to assemble iode-<ver>-brax3-spflash.zip alongside per-release
AOSP build outputs. See README.md for context and consumer pipeline.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: Ia30cc4315908e32956eebb11627fd3a618965e72
2026-05-22 09:55:42 +03:00
download_agent Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
flash.sh Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
mcf_ota_TK_MD_NLWCG_6835__R16MP3.img Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
MT6835_Android_scatter.xml Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
preloader.img Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
preloader_emmc.img Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
preloader_k6835v1_64.bin Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
preloader_raw.img Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
preloader_ufs.img Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00
README.md Initial import: MTK vendor blobs for brax3 SP Flash Tool bundle 2026-05-22 09:55:42 +03:00

README.md

brax3_spflash_vendor

MediaTek SoC-side prebuilt blobs and SP Flash Tool helpers for the brax3 device (MT6835 SoC). These files are not produced by the Android (AOSP) build — they are vendor-supplied and change only when MediaTek or the carrier publishes a new SoC/modem release.

Why this repo exists

The final user-facing SP Flash Tool bundle for brax3 is assembled from two inputs:

  1. AOSP build outputs (boot.img, super.img, vbmeta.img, …) — rebuilt every release, change constantly.
  2. Vendor blobs (this repo) — preloader, scatter, DA, modem variant — change rarely.

Keeping the vendor blobs in their own versioned repo means:

  • The Jenkins job that produces iode-<ver>-brax3-spflash.zip has a clean, auditable source for the static half of the bundle.
  • Updating MTK prebuilts is a normal commit + review on this repo, decoupled from any AOSP build.
  • Build reproducibility: a given AOSP build + a given commit in this repo = a deterministic spflash bundle.

Contents (9 entries)

File Purpose
preloader.img, preloader_emmc.img, preloader_ufs.img, preloader_raw.img, preloader_k6835v1_64.bin MTK preloader (first-stage bootloader) in the storage and packaging variants SP Flash Tool needs (eMMC vs UFS, with header vs raw, plus the DA-protocol binary form).
MT6835_Android_scatter.xml Partition map for the MT6835 SoC — tells SP Flash Tool which image flashes to which partition and offset.
download_agent/ MTK Download Agent (DA) — proprietary binaries that run on the device in BROM mode and perform the actual flashing.
mcf_ota_TK_MD_NLWCG_6835__R16MP3.img Carrier modem variant for the device. The suffix encodes the carrier/region MD build.
flash.sh Wrapper that invokes SP Flash Tool's CLI with the scatter file and DA from this repo.

How it is consumed

The Jenkins pipeline that builds the spflash bundle:

  1. Checks out this repo at the desired tag/branch.
  2. Packs the 9 entries into brax3-device-preloaded.zip.
  3. Combines that zip with the 23 AOSP build outputs to produce the final iode-<ver>-brax3-spflash/ bundle, then signs and publishes it.

See SPFLASH_BUILD_GUIDE.md in the flash-tools workspace for the full assembly recipe.

Branching

Branches track the iode release line they are intended for (e.g. v7.5). When MTK ships new SoC prebuilts, land them on the appropriate release branch.