Back to blog
BYD, FIRMWARE, SOSJuly 24, 2026EVLANG

BYD Internet Not Working After Update: Maps, Music and App Dead — What to Do

An OTA update landed — and everything broke: maps won't load, the music is silent, the app can't see the car, and the interface is suddenly back in Chinese. Stay calm: in the vast majority of cases this is a software problem that can be recovered, not a hardware failure. DiLink is alive — the update simply overwrote your settings, and here's what to do about it.

First aid: try this right now

Before you drive anywhere or panic, a few safe steps that often bring the system back to its senses.

  • Force a restart. Press and hold the volume button (or the screen power button) for about 10–15 seconds until the tablet reboots. Many owners describe it exactly like this: "hold the volume button and the tablet reboots." This is a normal, safe method.
  • Give the system time. If after the OTA "the multimedia froze at a percentage and has been stuck for two hours," wait out one full cycle first, and only then force a restart. Sometimes the background finalisation really does take a long time.
  • Check the 12V battery. A voltage drop during or after the update is a common cause of a black screen and DiLink crashes. If the car sat unused for a few days, a weak 12V battery can stop the system from starting properly.
  • Check the connection. Make sure your SIM/eSIM or a phone hotspot is active — "without internet the maps, music and browser don't work" by definition.
  • Don't install random firmware. If the system offers to "update" again, or you see unfamiliar APKs, don't install anything blindly. This is the number one reason a bad situation turns into a worse one.

If after these steps the internet, maps and app come back to life — great. If not (and especially if your language pack has vanished) — read on, that's a different level.

Why this happens

Short and honest: your BYD (a Song Plus, for example) arrived with factory Chinese software — built for the Chinese region, services and language. When "an OTA landed and everything reset — Chinese again," the system simply reverted to what's baked in from the factory.

Localisation — the Ukrainian/Russian language, working maps, music services, the link between the app and the car — is a layer on top of the factory software. An update often overwrites exactly those regional settings and the language pack. As owners put it well: "the language pack drops on every update — it just isn't in the Chinese APK." In other words, the update didn't "break" the car — it returned it to its "straight from China" state, where your language and your services aren't present by default.

Hence the accompanying symptoms: "GoogleMarket launches and crashes," DiLink crashes to a black screen, maps can't see the roads without internet. Sometimes there's also the feeling that "the hardware is weak, everything lags" — after a failed update the system is also loaded with background processes. Mechanically, the car is perfectly fine.

What NOT to do

  • Don't reflash blindly. Searching "byd dilink crashes" turns up a pile of forum firmware and APKs. Installing a random package meant for another model or region is the fastest way to get a genuinely dead screen.
  • Don't disconnect the terminals "to reboot the brain." Resetting the 12V blindly won't cure a software glitch, but it can add errors in other modules.
  • Don't ship the car "back to China" or take it to a random shop willing to "just flash anything." Without a backup of the current state, that's a gamble.
  • Don't re-update "for luck," hoping the next OTA will fix it. More often it simply locks in the Chinese state.

How we recover it

The approach is calm and reversible — no experiments on your car.

  1. Assess the symptom. We look at what exactly dropped: the language, maps, music services, the app link — or whether it's already a black screen and a reboot loop.
  2. Back up the current state. Before changing anything, we capture what's there so there's always a way back.
  3. Safe rollback and re-localisation. We restore the software adaptation for our region and rebuild the link between maps, music, the app and the car.
  4. We don't touch critical modules. We work with the multimedia/DiLink and localisation, not with the car's control systems. The modules responsible for driving and safety stay untouched.

Usually this takes 1–2 hours in the workshop. We're in Kyiv, 21 Prykoliyna St — the car stays on site, there's nothing to "send off" anywhere.

How much it costs

Localisation and post-update recovery — from $300. We name the exact price after assessing the specific symptom: restoring the language and maps is one thing, bringing the system back after a black screen is another. No hidden charges: we quote the amount first, then we work.

If you also need a car concierge (support and small related tasks), that's separate — from $100.

FAQ

Can it be fixed remotely?

Some settings — occasionally, yes. But after an OTA failure with a black screen, physical access to the car is almost always required. The fastest and safest option is to drop by.

Will the car's warranty stay intact?

We don't touch critical control systems and we don't change the hardware — we work with the multimedia and software localisation. [ПОТРІБНО ПІДТВЕРДИТИ: exact wording on the impact on the dealer warranty].

What if the next OTA breaks everything again?

It happens — an update can overwrite the localisation again. In that case we re-apply the localisation; the terms and period of that guarantee are agreed with you in advance. [ПОТРІБНО ПІДТВЕРДИТИ: terms and period of free re-application of the localisation after an OTA].

Describe the symptom — we'll assess it

Don't torture the car with guesswork. Describe the symptom — "stuck at a percentage," "black screen," "language pack gone," "DiLink crashing" — on Telegram, WhatsApp or Viber, and add a photo of the screen if you can. We'll give a rough assessment and tell you what to do next.

For more on how we bring back the language, maps and app connection on these cars specifically — see the BYD localisation page.