[MT6835 / Vivo V2346T] No matching Download Agent for HW code 0x1209 — bootloader unlock investigation

Open
  • Is something wrong?
#435 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
cli, security

Research direction

Start by reading mtkclient/config/brom_config.py and the DA parsing and selection path around DAconfig.dasetup; the report says the installed DA files contain no entry for hardware code 0x1209. First establish whether the device has an authorized compatible agent or requires authentication, using only non-destructive diagnostics. Done means documenting a reproducible support limitation or confirmed DA-selection issue and safe next steps; the issue does not identify a specific code change or test.

Written by the indexing model from the issue text.

Description

Device Information

  • Manufacturer: Vivo
  • Model: V2346T (V2346)
  • Chipset: MediaTek MT6835V/ZA (Dimensity 6100+)
  • Hardware code: 0x1209
  • Android: 16
  • Kernel: 5.15.197
  • Firmware build: compiler260914115452
  • Bootloader: locked (unlocked: no), Verified Boot: green
  • OEM unlocking: enabled in Developer Options

Environment

  • Ubuntu Live USB
  • MTKClient 2.1.4, commit 118a000 (2026-10-26)
  • Python 3.14.4 (virtual environment)

Problem

MTKClient identifies the MT6835 chipset, but cannot select a compatible Download Agent:

No da_loader config set up
No valid da loader found... aborting.

Investigation

  • mtkclient/config/brom_config.py includes 0x1209 with XML DA mode and dacode=0x1209.
  • Bundled MTK_DA_V5.bin: 50 entries; MTK_DA_V6.bin: 9 entries.
  • Parsing all installed DA files using DAconfig.dasetup: 87 distinct hardware codes, 0 matches for 0x1209.
  • Local main is synchronized with origin/main at commit 118a000.
  • mtk.py printgpt --skipwdt reports no valid DA loader.
  • ADB and Fastboot work; standard fastboot flashing unlock and fastboot oem unlock return unknown command.
  • Tested bbk unlock_vivo using a raw Fastboot script: FAILunknown command.

Questions

  1. Is MT6835 (HW code 0x1209) supported for DA-based operations on this device?
  2. Is there an appropriate, authorized Download Agent for Vivo V2346T?
  3. Does this device require additional SLA/DAA authentication?
  4. Are there known limitations for bootloader unlock on this Vivo firmware?
  5. What further non-destructive diagnostics would be useful?

I have excluded device-specific identifiers (serial, IMEI, ME_ID, SOC_ID). Thank you.

Dominant language
Python
Stars
1.5k
Forks
309
Avg merge
1d 7h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bkerler/mtkclient

All issues in bkerler/mtkclient

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.