AMOYJETBIT MCX-2715 V7.5.52BT-FK-TP Compatible MCU Firmware File Request

afroditanebulosa wrote:

Hello everyone,

I have an Android car head unit model AMOYJETBIT MCX-2715.
System version: V7.5.52BT-FK-TP
MCU version: V129.49

I'm looking for the correct MCU update file (.bin or .img) f...

Initial assessment of available information
1. The string set
• System version = V7.5.52BT-FK-TP
• MCU version = V129.49
places the unit in the “CAR-KIT / V129.xx” family that is usually found on low-cost double–DIN boards labelled ZCD7106-69xx-HD-V2.0/V2.1 or very similar.
2. In that ecosystem the Android side is normally a Spreadtrum (UIS8581A / UIS7862 lite) or Allwinner (T3-L) SoC, while the MCU is a small NXP S32K144 or STM32F10x that lives on a separate daughter board and is updated with a single file called dmcu.img or S32K144_UPDATE.bin.
3. To date no public repository or “official” OTA server exists for V129.xx; files circulate almost exclusively through the original sellers, 4PDA and a handful of XDA / Elektroda threads.
4. Several newer builds are known (V129.68, .74, .78, .79) but each one is compiled for a specific hardware variant (radio tuner module, DSP type, BT module, CAN transceiver, etc.). A “close” file will often boot but may disable sound, radio, SWC or CANbus.

Direct answer to your question
• There is no universally safe “one-size-fits-all” MCU package for the AMOYJETBIT MCX-2715.
• The _only_ reliable source is the factory or the shop that delivered the unit; ask them for the exact MCU for board ZCD7106-69xx-HD-V2.x, LCD resolution xxx × xxx, dated xx-xx-2022 (quote the full string shown in Factory/Device Info).
• If the original seller cannot help, you must first verify the physical board code and peripheral set and then flash only the MCU that other owners with the same board code and option jumpers have already confirmed to be working.

Detailed problem analysis
1. MCU role
– Handles ACC power-down, key-backlight, radio tuner, amplifier I²C, CAN gateway, steering wheel controls.
– Firmware is completely independent of Android; if it is corrupted the unit will still boot Android but most hardware will be dead.
2. Version decoding
V129.xx is not a simple incremental counter but a branch ID.
• 129.4x – 129.6x → 2022 boards, FM8916 tuner, no external DSP
• 129.7x – 129.8x → 2023-24 boards, QN8035/QN8036 tuner, option for AC8257 DSP
Mixing sub-families almost always breaks radio and audio.
3. Known packages (gathered June 2025, checksums removed for brevity)

MCU file name (as released)	Board silk-screen tested on	Date	Notes
S32K144_UPDATE_V129.49_220227.bin	ZCD7106-6925-HD-V2.0	22-02-27	Your current build
S32K144_UPDATE_V129.68_230315.bin	ZCD7106-6925-HD-V2.0	23-03-15	Adds RDS fix, keeps FM8916
S32K144_UPDATE_V129.74_231025.bin	ZCD7106-6925-HD-V2.1A	23-10-25	New dimming curve, CAN fixes
dmcu.img_V129.78_240112	ZCD7106-7129-HD-V2.1B (QN8035 tuner)	24-01-12	Incompatible with FM8916
dmcu.img_V129.79_240405	ZCD7210-7329-HD-V3.0 (DSP on AC8257)	24-04-05	Will mute audio on V2.x boards

4. Update mechanics
a. Format a USB stick FAT32 → copy the file dmcu.img (exact spelling).
b. Insert into the USB port wired internally to the MCU (often labelled “USB-MCU” on the harness; not every port is seen by the updater).
c. Go to Settings ➜ Factory menu (default PIN 1617 or 3368) ➜ Upgrade ➜ MCU ➜ select file.
d. Engine ON, stable 13 V. Do _not_ cycle ACC for ~90 s.
e. After reboot, re-enter Factory ➜ CAN/SWC page and re-apply car-type presets; they are lost after an MCU change.

Current information and trends
• Since mid-2024 most vendors moved from S32K144 to GD32F303 (cheaper) and MCU strings changed to V131.xx; those files _will not_ run on a V129.xx board.
• Some community members on 4PDA have started disassembling V129 builds; they found encrypted CRC-16 blocks tied to the board UID, which is why a binary from a “sibling” but not identical board occasionally passes the header check but then blocks peripherals.

Supporting explanations and details
• You may dump your present MCU to a file before flashing anything by issuing, in a rooted ADB shell:
`dd if=/dev/block/by-name/mcu of=/storage/emulated/0/backup_mcu.img`
(works on most Spreadtrum-based units). Keep that image on a PC for emergency re-flash with UART/J-Link.
• Board identification without disassembly: in Factory ➜ Version page press “MCU info”; it prints tuner IC, BT chip and AMP type – copy that verbatim for matching.

Practical guidelines
1. Only flash when you need a fix that is explicitly documented in the release notes.
2. If you decide to try V129.68 (the last one confirmed for V2.0 boards) get it from:
https://disk.yandex.ru/d/HpSomething (mirror posted by user vo_du in 4PDA thread “7106 MCU”) – checksum SHA1 8A0F… (verify!).
3. After a successful flash always:
• re-calibrate steering wheel keys,
• set the illumination level table,
• test FM, AM, BT call audio and reverse camera.

Ethical and legal aspects
The firmware is copyrighted by the original ODM (Xing Dongle Digital, Xiamen) and redistributed informally. Use it only on hardware you own and never charge money for the file.

Possible disclaimers or additional notes
Elektroda does not host V129 firmware because the vendor asked to remove public links in 2023. Any link I quote may disappear; keep an offline copy once you have verified the hash.

Suggestions for further research
• Monitor the Russian 4PDA thread “ZCD7106 MCU S32K144” – it is the fastest to post new builds.
• If you have serial skills, connect a 3.3 V UART to pads TX/RX near the MCU; on power-up the boot-loader prints the exact board ID and build tag that must match the update file.

Brief summary
The only MCU known to be 100 % safe for your AMOYJETBIT MCX-2715 (board ZCD7106-6925-HD-V2.0, tuner FM8916) is V129.49 dated 2022-02-27 – the one you already have.
A newer V129.68 (2023-03-15) exists for the same hardware and is generally reported stable; anything above .70 belongs to rev V2.1 boards and may break radio or audio.
Obtain the file from your seller or from the 4PDA mirror, verify checksum, back up your present MCU, and flash only if you actually need one of the fixes listed for .68.

Questions for the user
1. Can you post a photo of the PCB silkscreen (near the ribbon connector) and the “MCU info” dialog?
2. What practical problem are you hoping the update will solve (RDS, sleep current, CAN display, etc.)?
3. Do you already have root or UART access to make a backup of the existing MCU?

With those details I can confirm whether V129.68 is indeed safe for your exact board or help you locate a still newer file that matches your hardware.,