[Please help] (MT6835) - Download Agent (DA) request for Motorola Moto G 2025 "kansas" XT2513V
[Please help] (MT6835) - Download Agent (DA) request for Motorola Moto G 2025 "kansas" XT2513V
19-09-2026, 03:01 PM
Device: Motorola Moto G 2025, codename "kansas", model XT2513V (TracFone variant; siblings XT2513-1/-2/-3).
Chipset: MediaTek MT6835 (Dimensity 6300), hw_code 0x1209, DA v6 / XML download mode.
Security state, read directly off the device rather than assumed:
SBC=true, SLA=false, DAA=true, Root cert required=false, ME_ID and SOC_ID both read cleanly.
The phone is preloader-only after a bad LK flash. No fastboot, no adb. Nothing has been written to it since, and every attempt so far has been read-only printgpt. The preloader handshake itself is healthy: I get a full identity read every time, watchdog disabled, the lot. It stops at DA upload with DAA_SIG_VERIFY_FAILED (0x7024), which is the device refusing the download agent's signature.
Things I have already ruled out, posted so nobody spends time repeating them:
1. Retail "kansas" firmware zips on mirrors.lolinet.com contain no DA and no scatter file. I opened them and looked.
2. A generic MT6835 DA_BR.bin, header-verified as v6 carrying 0x1209, reached DA upload and was refused with 0x7024.
3. Lenovo's own official Tab K11 Gen 2 (TB336FU) rescue package carries a real MT6835 DA for the same hw_code. I pulled it from Lenovo's live release stream, header-checked it, and tested it today: same DAA_SIG_VERIFY_FAILED (0x7024), on four full handshakes out of four. So Lenovo's tablet signing key and Motorola's phone signing key do not appear to sit in the same tier, even though Lenovo owns Motorola. Posting that as a negative result in case it saves someone else the trip.
4. No public BROM auth bypass covers mt6835. The MTK Auth Bypass utility thread's own supported-SOC list does not include it.
5. LMSA is dead on this unit both ways. v6.2.2.4's backend host is NXDOMAIN, and v7.6.2.10 loops on login after a byte-clean reinstall, on both email and Google sign-in, with the elevated service running.
So the whole thing now comes down to one file: a DA signed with Motorola's own key for this platform.
If anyone has a Motorola-signed DA_BR.bin or MTK_AllInOne_DA pulled from LMSA for kansas, or from a sibling Motorola device on MT6835 (Moto G Power 2025 "vegas", XT2515, would be the obvious one to try), I would be grateful if you would post it. I will test it and report back either way, including a clean negative, since that at least maps out the key tiers for this chip generation.
Users browsing this thread:
2 Guest(s)
2 Guest(s)
Users browsing this thread:
2 Guest(s)
2 Guest(s)
