Initial assessment of the available information From the two photographs you attached we can read the following firmware data:
• Main SW version : V7.52 BT-FK-TP • Build string : ZCD-7089-6905C-IC-… • MCU version : V04.31 –- 2019-11-27 13:46:57 • BT name / PIN : CAR-KIT / 0000 • Device class : “MP5” (non-Android multimedia head-unit)
Nothing in the screen indicates Android (there is no “About tablet”, “Android xx” or Kernel build). This places the unit in the large family of low-cost 1 DIN / 2 DIN “MP5 Players” that are built around a Sunplus SPC56xx / SPC82xx or, on newer boards, a MediaTek MTK8257 single-chip multimedia processor. For this platform the whole operating system, UI graphics and MCU code are bundled in a single binary that is flashed from a FAT32 SD card or USB stick during power-up.
Direct answer to your question 1. There is no universal or official “latest” firmware for these devices. Every screen size, touch-panel type, button matrix, radio tuner and CAN/steering-wheel interface combination has its _own_ build. 2. The newest publicly leaked Sunplus firmware line for the “V7.xx” branch is V7.86 – V7.92 (2022Q3). Whether you can use it depends entirely on the PCB part number printed on your board, not on the front-panel model name. 3. If the device is working correctly, updating only for “something newer” is _not_ recommended: a wrong file will brick the unit and recovery almost always requires serial-flash desoldering.
Detailed problem analysis 1. Hardware identification • Remove the four screws, slide the front half out and photograph the main PCB. • Look for a silkscreen like “6905C-IC-V1.5”, “7089F-JZ”, “YXD_V2.7” etc. • Note the LCD FPC label (e.g. “TP-FT5336 800×480”), the radio chip (RDA 7705, QN8035 …) and the power amplifier (TDA7388, AC7389 …). Those strings are the _only reliable keys_ when you search for a compatible image.
2. Firmware structure The update package for Sunplus units is a single file (sometimes wrapped in a ZIP) commonly named: • “update.bin”, “JUI_FW.bin”, “SPHOST.BIN” or “7089.fw” (exact name is board-dependent). A txt control file (“UPGRADE.TXT”) may be needed to instruct the bootloader which areas to flash.
3. Update procedure (generic) a) Format a ≤32 GB SD card to FAT32, copy the exact file names required by your board. b) Power-off the radio, insert the card, keep VOL+ or the small reset hole pressed (again – depends on board). c) Apply ACC +12 V. The screen will stay black for 15-25 s, then display a progress bar. d) When 100 % is reached the unit reboots and silently erases the card. If the screen never lights up you probably flashed an incompatible image – the device is now “hard-bricked”.
4. What changed from V7.52 → V7.8x • Newer boot logo format (static 24-bit BMP, 800×480) • UI font supports Arabic, Farsi, Hebrew (right-to-left rendering) • Bluetooth stack updated – fixes iPhone 13/14 address-book sync • Optional Car-Park assist overlay (requires extra MCU pin) None of these changes improve audio quality or radio sensitivity; they mainly add language packs and minor BT bug-fixes.
Current information and trends (2024-2025) • Sellers have largely moved from Sunplus to entry-level Android 10/11 “8227L-Nand” and Android 12 “TS10/TS18” units. For them, system upgrades are delivered as ZIPs flashed via recovery and are _not_ compatible with Sunplus hardware. • Some Chinese vendors on AliExpress still ship Sunplus boards because they are cheap (<25 USD FOB); their last factory bundles are dated 2023-04 but rarely leak to the public. • A small community on 4PDA (Russian) and on the Brazilian forum “GPSPoint” maintain *modded* V7.8x builds. They localize the UI and pre-install IR remote codes, but they do not retarget screen or key matrix parameters.
Practical guidelines 1. Verify the PCB ID before doing anything – post a clear photo on the thread, or write the alphanumeric code here so we can cross-check. 2. Backup the current firmware if possible. Some boards let you read back SPI-NOR with `spflashtool.exe` over UART (115 200 Bd, 3.3 V). If that sounds unfamiliar, do not proceed. 3. Decide what you really need. – If Bluetooth drops SIM contacts with new phones → update _may_ help. – If you only want a fresher look, install a different _skin_ (BMP resources). No flashing required – skins are on the SD card `/RES/` directory. 4. Ask the seller. Occasionally they will send you a link to “2019-11-27” → “2021-08-30” incremental package that matches your exact batch.
Ethical, legal and safety aspects • Flashing firmware you found on public forums voids CE/FCC conformity of the product. • Operating a distracted or black screen while driving is a road-safety hazard. Make sure the car is stationary and the unit is on a lab supply when you experiment.
Suggestions for further research • 4pda.ru → Forum → “Магнитолы на Sunplus” → search for your PCB code. • github.com/daburubar/SpmpTool – open-source parser to inspect `SPHOST.BIN`. • If you plan to migrate to Android, consider replacing the entire unit with an AC8227L-based head-unit; it has real Play-Store support and OTA packages.
Brief summary There is no single “latest” firmware that fits all V7.xx head-units. The only safe way to update is: 1. Open the radio, write down the PCB identifier. 2. Find a proven V7.8x image for _that exact board_. 3. Flash via SD only if you absolutely need one of the bug-fixes and you accept the risk of a brick.
Questions for you 1. Can you provide a clear photo of the main PCB (both sides)? 2. What concrete problem do you hope the update will solve? 3. Do you have access to a bench 12 V power supply and a USB-TTL adapter in case recovery is required?
With that information I can look up the proper package – or confirm that staying on V7.52 is the safest choice.
You can call me in any topic by writing @ElektrodaBot. Disclaimer: Some answers provided by the ElektrodaBot may be inaccurate. Elektroda not responsible for accuracy, reliability or completeness of the information presented. All ElektrodaBot responses should be verified by the user. OpenAI can monitor and save information entered after calling ElektrodaBot.
@ElektrodaBot
@ElektrodaBot
