Artificial Intelligence Response
Direct answer to the question
HZ-B500-MB VER2.1 appears to be a mainboard hardware revision used in a generic 12 V automotive CarPlay/MP5 head unit, not a consumer-facing product name by itself. The closest authoritative public match I could verify is an FCC filing for a Carplay device family from Shenzhen Hong Xiang Rui Technology co., Ltd., model B5306 and related variants, using hardware version HZ-B500-MB VER2.0, with 12 V input, 2.4 GHz Wi‑Fi, and Bluetooth. That strongly suggests VER2.1 is a nearby board spin/revision of the same family, but it should not be treated as universally firmware-compatible just because the silk-screen is similar. (fcc.report)
Key points
- It is most likely a PCB/mainboard ID, not the retail model number. (fcc.report)
- The verified family is associated with CarPlay-class automotive devices. (fcc.report)
- The verified related board revision is HZ-B500-MB VER2.0; VER2.1 is therefore best treated as a hardware revision update, not automatically the same firmware target. (fcc.report)
- I did not find an authoritative public source proving that HZ-B500-MB VER2.1 is the same as older HZ-06925-MB / 7018B / F1C200s platforms, so I would not assume cross-compatibility. (fcc.report)
Detailed problem analysis
From an electronics and repair perspective, a label such as HZ-B500-MB VER2.1 usually identifies the bare motherboard revision. In low-cost automotive multimedia products, the same enclosure and front panel may be sold under many retail names, while the internal PCB revision changes quietly. The FCC material for the related HZ-B500-MB VER2.0 family shows exactly that pattern: one hardware platform is tied to many model numbers, including B5306, B5308, B5009, B5369, B5301, B5113, B5303, B5311, A501-A509, D3230, and D3231. (fcc.report)
Technically, the verified related platform is a 12 V automotive CarPlay unit with:
- 2.4 GHz Wi‑Fi operation in the 2412-2462 MHz range for 802.11b/g/n testing,
- Bluetooth operation in the 2402-2480 MHz range,
- a PCB antenna,
- and documented testing completed in August-September 2024, with FCC grant information posted on September 21, 2024. (fcc.report)
That matters because it tells us this board family is not just a simple old “MP5 player” board; at least the verified related revision belongs to a wireless CarPlay-capable platform. Therefore, using firmware from an unrelated 7018B-type unit would be high risk. (fcc.report)
In practice, board silk-screen alone is insufficient for firmware matching. For successful repair or reflashing, you normally need to identify at least:
- the main SoC marking,
- the flash device part number,
- the LCD panel or ribbon identifier,
- the touch controller,
- the radio / Wi‑Fi / Bluetooth section,
- and sometimes the audio amplifier IC.
This is because OEMs often keep the same PCB family name while changing peripheral devices. A firmware image may boot the CPU but still produce:
- white screen,
- inverted or dead touch,
- no radio,
- no audio,
- dead Bluetooth/Wi‑Fi,
- or boot loops.
Current information and trends
The most current hard evidence I found is the 2024 FCC documentation for the related HZ-B500-MB VER2.0 platform. It identifies the product class as Carplay, not merely a generic standalone MP5 decoder board. The software version in that filing is HZ WIFI20240810-1441, which further supports that this family includes Wi‑Fi functionality and is part of a more recent wireless infotainment design rather than a very old non-networked head-unit platform. (fcc.report)
An industry trend visible here is the use of one PCB family across many private-label models. That reduces OEM cost, but it complicates repair because:
- the market name on the bezel may be meaningless,
- firmware archives are fragmented,
- and “same-looking” units may still have incompatible internal hardware. (fcc.report)
Supporting explanations and details
A useful way to think about HZ-B500-MB VER2.1 is this:
- Retail model number = what the customer sees
- PCB code = what the factory/service engineer uses
- Firmware compatibility set = determined by the total BOM, not just the PCB code
So if you are trying to repair, identify pinout, or find firmware, the minimum useful data is:
| Item |
Why it matters |
| Board photo, both sides |
Confirms connectors, regulators, memory type |
| Main IC marking |
Tells firmware family / flashing method |
| Flash chip marking |
Tells whether direct dump/programming is possible |
| LCD ribbon code |
Critical for display driver match |
| Symptom |
Distinguishes power fault from firmware fault |
| Original unit brand/model |
Sometimes maps to community firmware dumps |
Typical symptom interpretation:
- Completely dead: first suspect power rails, protection, regulator failure
- Logo then freeze: often corrupted flash or incompatible firmware
- Backlight only / white screen: often LCD init mismatch
- Touch offset / inverted touch: touch-controller or calibration mismatch
- No CarPlay/Bluetooth/Wi‑Fi: wireless section or wrong firmware build
- No sound: amplifier IC, mute control, or power rail issue
Ethical and legal aspects
- Vehicle safety: A car head unit is part of the driver interface. Unverified firmware can affect reverse-camera behavior, audio muting, or distraction-related functions.
- Regulatory compliance: The verified related platform has FCC-tested Wi‑Fi/Bluetooth characteristics. Hardware or RF modifications can invalidate the original compliance basis. (fcc.report)
- Untrusted firmware: Community dumps can contain hidden defects, region locks, or simply the wrong driver set.
Practical guidelines
If your goal is firmware, repair, or pinout identification, proceed as follows:
- Do not flash anything yet.
- Send or record:
- clear photo of the board front and back,
- close-up photo of the main IC,
- flash memory marking,
- LCD ribbon marking,
- exact symptom.
- Check basic rails first:
- vehicle input / bench input,
- 5 V rail,
- 3.3 V rail,
- any CPU core rail if accessible.
- If the unit is already bricked and uses external flash:
- read the flash first,
- save a backup,
- only then compare candidate firmware.
- Never assume:
- VER2.0 = VER2.1 firmware compatible
- same screen size = same LCD driver
- same shell/front panel = same mainboard
Possible disclaimers or additional notes
- I could verify the HZ-B500-MB family, but I could not verify an authoritative public datasheet specifically for VER2.1.
- The sample answers that connect this board directly to HZ-06925-MB / 7018B / F1C200s may be possible in some forum discussions, but I could not confirm that from the authoritative sources I checked, so I would treat that as unproven for your exact board. (fcc.report)
Suggestions for further research
To identify your exact board safely, the next best steps are:
- photograph the board and all major ICs,
- identify the memory device type,
- inspect connector pin labels,
- compare against known B5306/B5308-style CarPlay boards,
- and, if needed, dump the original flash before any write attempt.
Brief summary
HZ-B500-MB VER2.1 is most likely a mainboard revision for a generic automotive CarPlay/MP5 unit. The best verified public evidence is a closely related HZ-B500-MB VER2.0 FCC-documented CarPlay platform from 2024, powered from 12 V and equipped with Wi‑Fi and Bluetooth. Because only the board family—not your exact BOM—is known, you should not flash firmware based on the board code alone. (fcc.report)
If you want, I can do one of these next:
- help identify the board from a photo,
- help find the likely flash chip and test points,
- help diagnose “dead / white screen / boot loop / no touch / no audio,”
- or help build a safe firmware-matching checklist for HZ-B500-MB VER2.1.
User question
Hello Forum, I have a cheapie mp5 CarPlay unit with the HZ-B500-MB board. In the setup of the unit it has the ability to select where the driver is seated allowing the built in microphone to pick up voice when answering the telephone. It’s a very poor pickup. I wish to install an external microphone near the driver. Is this possible to achieve? If so, where on the board do I attach the wires? Thanks. I hope this is the correct forum to ask this question. Gary Roser, Sydney, Australia
Artificial Intelligence Response
Direct answer to the question
Yes, very likely it is possible.
On this class of low-cost CarPlay/MP5 units, the usual method is to remove or bypass the onboard microphone and connect an external 2-wire electret microphone to the same two PCB pads. However, I cannot responsibly tell you the exact pads on your specific HZ-B500-MB VER2.1 board without a clear photo of the microphone area, because I did not find a public schematic or readable microphone pinout for that revision. A closely related HZ-B500-MB VER2.0 board does appear in FCC documentation for model B5306, but the public material is only high-level and does not expose a usable mic pinout. (fcc.report)
Most likely connection point:
Most likely microphone type:
Detailed problem analysis
Your symptom is typical of these units: the built-in mic is mounted deep inside the plastic enclosure, far from the driver, with poor acoustic exposure and poor noise isolation. Even if the DSP/software is acceptable, the mechanical/acoustic placement of the original mic is often the real limitation. Replacing it with an external mic near the visor or A-pillar usually gives a much larger improvement than changing settings. (fcc.report)
1. What you should look for on the board
Open the unit and find the onboard microphone first. On cheap car units it is usually one of these:
For your purpose, the good case is the first one: a simple 2-pad electret capsule. Typical electret microphone circuits use:
2. Where to attach the external microphone
If your board uses a normal electret mic, the correct attachment points are usually:
That means the practical mod is:
This is the cleanest and most reliable method. (mouser.com)
3. How to identify which pad is which
Use a multimeter before soldering the external mic:
That matches standard electret microphone biasing practice. For example, common electret microphone datasheets specify 2 V nominal operation, 2.2 kΩ output impedance, and only a small current draw. (mouser.com)
4. External mic type to use
Use a car external electret microphone, preferably:
Do not use:
The board is expecting an analog electret capsule, not a digital audio source. (mouser.com)
5. Should you leave the internal mic connected?
My recommendation: no.
Remove or disconnect the original onboard microphone and use only the external one.
Reason:
In some circuits, paralleling two electret capsules may still “work,” but it is not the preferred engineering solution. Using only the external mic is cleaner and more predictable. (mouser.com)
6. Wiring method I recommend
Preferred wiring:
Cable type:
This matters because the microphone node is high impedance and low level, so it is easy to contaminate with alternator noise, switching noise, or RF pickup. (mouser.com)
7. How to verify the board is not using a digital microphone
Stop and reassess if the onboard mic is:
If so, it may be MEMS/digital, and then a direct swap with a 2-wire electret mic will not work correctly. In that case I would need a close-up board photo before advising further. The public documentation I found for the related board family does not provide enough mic-circuit detail to distinguish this for your exact revision. (fcc.report)
Current information and trends
I was able to verify that a closely related product family exists in recent FCC documentation:
Industry-wise, the common field fix for poor call quality in budget head units remains:
Supporting explanations and details
Think of the onboard electret microphone as a tiny sensor that needs two things from the board:
That is why one pad is not simply “audio+” in the same way as a speaker output. It is usually bias + signal on the same conductor, with the audio extracted by the following circuitry. This is standard electret practice and is shown in typical electret measurement/application diagrams. (mouser.com)
A useful analogy: the microphone line is more like a sensor node than a robust audio output. That is why:
Ethical and legal aspects
Practical guidelines
Recommended procedure
Best practices
Likely challenges
Possible disclaimers or additional notes
Suggestions for further research
If you want to continue safely, the next best steps are:
With that, I can tell you much more confidently:
Brief summary