BYD ADBUI version guide

Identify your BYD DiLink UI version

Look at the bottom dock, not the hardware name or build number. Then use the QR menu for the definitive ADB check.

Maintained byBAOLAB

Published

Last verified

EvidenceBAOLAB vehicles and field observations

Wide tile dock used by BYD DiLink 5.0 UI
5.0 UI on BAOLAB's Australian Denza B8

THE IMPORTANT DISTINCTION

UI generation is the number that matters.

A vehicle may ship with a UI generation matching its DiLink hardware, then receive a newer interface through a BYD OTA update.

BAOLAB's Denza B8 shows why the labels cannot be treated as one number: it has DiLink 6.0 hardware and currently runs 5.0 UI.

Based on BAOLAB's own vehicles, completed customer sessions and observed UI behaviour. OTA updates can change the interface, so the live QR test remains definitive.

DiLink hardware
The infotainment computer generation installed in the vehicle. It does not reveal the current screen design.
UI generation
The visible interface family. For this service, 5.0 UI or newer commonly exposes the required QR route and is often described online as DiLink 5+.
Build number
A software release identifier, often styled like a year and month. It does not confirm whether the QR menu appears.

Read the dock, not the wallpaper.

Apps and backgrounds change. The lower control structure is the fastest visual clue.

Classic cyan bottom dock shared by BYD DiLink 3.0 and 4.0 UI
3.0 and 4.0 UI

Classic dock

  • Cyan climate and vehicle controls
  • Separate Android back, home and recent keys
  • Legacy dark interface structure

If this visual match is correct, this UI family does not open the required QR menu. Run the dialler test to confirm the estimate.

Slim utility rail with compact centre shortcuts used by BYD DiLink 6.0 and 7.0 UI
6.0 and 7.0 UI

Compact app dock

  • Slim full-width utility rail
  • Four compact coloured shortcuts in the centre
  • Mirrored climate controls

6.0 and 7.0 share this dock family. As of 12 September 2026, ADB on 7.0 beta UI is beta-user reported rather than a public-release result.

These images estimate the UI family. They do not replace the QR test.

The definitive ADB compatibility check

The vehicle itself can answer the question in seconds.

Enter the dialler code*#91532547#*
Read the result

A QR page confirms the required route is present. If nothing happens, the current UI is not compatible.

If the QR page only shows WeCom

The vehicle has a Chinese configuration. A China-routed VPN must be active on the infotainment system during the QR process. Compare the WeCom, VDS and Chinese-configuration QR pages.

Now check the vehicle.

The interactive checker turns the QR result into the correct next step.