Prepare a central.
Depois, instale o DashArc.

Native USB — “Third Party Apps 61”

Use this when the original BYD aftermarket installer is still enabled.

This is the simplest method available. Australian head units use country code 61.

1. Format a USB drive as FAT32.
2. Create a folder in the root named Third Party Apps 61. Keep the spaces exactly as shown.
3. Copy the .apk files into that folder.
4. Connect the drive to the vehicle's data-capable USB port.
5. If the BYD password window appears, enter the password accepted by your firmware.
6. Select the APKs and install them.

Known BYD installer passwords

20211231
BYD6125F
GHY0613byd

Which password works depends on the firmware generation. If no password prompt appears at all, the USB installer is probably disabled on your build and another method is required.

Engineering menu + IMEI password

No downgrade required. Works on builds that still expose the older engineering menu.

1. Pair a phone with the BYD over Bluetooth so the vehicle dialer becomes available.
2. In the dialer, enter *#91532547#*.
3. If the screen shows an IMEI and asks for a code, generate it with the BYD Secret tool.
4. Enter the generated code.
5. Enable Wireless adb debug switch and Debug mode when USB is connected.
6. Connect with ADB and install APKs directly.

adb connect CAR_IP:5555
adb devices
adb install -r app.apk

BYD Secret online generator ↗
BYD Secret / Package Installer repository ↗

QR factory-menu activation

No downgrade required. For UI revisions that show a QR code instead of the IMEI page.

On newer UI revisions the same dialer code may show a short-lived QR code instead of the IMEI password page. Australian service BAOLAB documents a remote activation flow that completes BYD's existing QR factory-menu process without flashing firmware.

1. Open the Bluetooth phone dialer.
2. Enter *#91532547#*.
3. If a QR page appears, the vehicle may be compatible with the remote QR activation route.
4. Once the factory menu opens, enable the USB and/or wireless ADB switches.
5. Install apps using standard ADB.

BAOLAB procedure ↗
Australian ADB enablement service ↗

Downgrade to 13.1.33.2404, enable ADB, install Package Installer

The most widely documented route when newer firmware blocks both USB and the old engineering menu.

A 2026 guide specifically targeting the 13.1.33 family uses build 13.1.33.2404 as the downgrade and unlock version.

A. Prepare the downgrade USB

1. Remove any SD card from the vehicle.
2. Download the 2404 firmware from the download centre below.
3. Use an 8, 16 or 32 GB FAT32 USB drive where possible.
4. Create the folder structure BYDUpdatePackage\msm8953_64\.
5. Place the firmware package there as UpdateFull.zip.
6. Keep the traction battery adequately charged and the vehicle powered.

B. Start the downgrade

1. Insert the USB drive with the vehicle on.
2. Accept the update if the normal updater accepts the package.
3. If QR authorisation blocks the update, the documented recovery shortcut is to hold the steering-wheel left/back control together with the centre-console volume/power control for roughly 10 to 15 seconds, until the IVI restarts into the update flow.
4. Do not remove power or the USB drive while the firmware is being written.

C. Enable ADB

1. Pair a Bluetooth phone.
2. Dial *#91532547#*.
3. Use the displayed IMEI information with the BYD Secret generator.
4. Enable wireless ADB and USB debugging in Test Tools.

D. Install the unlocked package installer

adb install PackageInstallerUnlocked.apk

After this, APKs can normally be installed from a file manager, USB storage or an alternative app store, depending on the package-installer build you installed.

Download 13.1.33.2404 ↗
Download PackageInstallerUnlocked.apk ↗
Full 13.1.33 unlock guide ↗

Legacy 2307 downgrade route

The established pre-2310 path, documented by Defective Tech research.

The older Defective Tech research documents 13.1.33.2307 as the established pre-2310 firmware used to restore the original Third Party Apps and ADB-enablement path.

1. Download the Global Di3.0_13.1.33.2307210.1.18.3.2.2307190.2.zip.
2. Prepare it as BYDUpdatePackage\msm8953_64\UpdateFull.zip.
3. Downgrade using the normal updater, or the recovery-button sequence if it is blocked.
4. Use the old firmware to install an unlocked package installer, app manager and/or ADB switch tool.
5. Enable ADB and verify with adb devices.
6. Upgrade again afterwards, having preserved the installer and ADB setup.

Archive MD5 for the listed 2307 package: 4db4fec9e70f0426620b76853bf279ae.

Defective Tech — 13.1.33 firmware archive ↗
Defective Tech — UpdateFull / recovery procedure ↗

After unlocking

Installing apps day to day, and going back to newer firmware.

Install apps directly with ADB

Once ADB is enabled you no longer need to repeat a downgrade for every APK.

adb devices
adb install app.apk
adb install -r app.apk

# Wireless ADB
adb connect CAR_IP:5555
adb install -r app.apk

Australian Seal owners report keeping wireless ADB available after later manual and OTA IVI updates, and installing APKs directly from a phone. Persistence is firmware-dependent, so verify it after every update.

Install APKs from a file manager or an app store

Installing an unlocked package installer turns future app installation into a normal Android workflow: download or copy an APK and open it from a file manager. You can also install an alternative store such as Aurora Store or F-Droid. One well-documented procedure recommends backing up the original Android Package Installer before replacing it.

Upgrade again after unlocking

The usual workflow is downgrade, unlock ADB and the package installer, install apps, then return to a newer 13.1.33 build. Community reports from Australian Seal and Sealion 6 owners indicate that installed apps and ADB can survive later updates, although this is not guaranteed for every release.

Official Android SDK Platform-Tools (ADB) ↗
PackageInstaller.apk on GitHub ↗
Package Installer + file-manager procedure ↗
Aurora Store ↗
F-Droid ↗