Before you install
Getting engineering access on a BYD
DriveLab reads the car and sends it commands through the car's own system service, and that needs ADB debugging to be switched on. On some head units you can do it yourself in a few minutes; on others it is locked and somebody else has to open it. Here is every step of both routes.
Nobody working on DriveLab has done any of this on a car. Everything on this page is either something the app measures on the head unit it runs on, something another owner wrote down once, or something nobody here knows — and every step says which of the three it is.
Once DriveLab is installed, Settings → This car → Connection tells you at any time whether the head unit's debug port answers and whether the car has let the app in.
How to read this page
- Measured The app read it from the head unit it is running on, or it is the app's own documented behaviour.
- Community-reported It comes from a guide another owner wrote. Nobody here has done it on a car. Treat it as a lead, not as instructions from the manufacturer.
- We do not know Nothing we have settles it — it changes with the firmware, the market and the importer — so we say so instead of guessing.
Nothing here is a manufacturer's procedure. Where a step genuinely differs between firmwares, markets or importers and nothing we have settles it, the step says so and stops there. Those are real gaps, not formalities: you have to find that answer somewhere else before you act on it.
Two different things are called “master”
Engineering access on the head unit — the hidden menu where ADB debugging is switched on. This is the one DriveLab needs, and it is what almost all of this page is about.
The car's BYD-cloud account, which on an imported car is often still bound to the exporter or to the first Chinese owner. That is why BYD's own phone app, over-the-air updates, remote control and sub-accounts do not work for the new owner. DriveLab does not need it, cannot see it and cannot change it: the app never reads your VIN.
Do the first one first. It is the one that makes the app work, it is the one with a real procedure, and on a DiLink 3 or 4 it costs nothing at all.
Before you start
Read this first
The DiLink 5 route ends with you sending money to a stranger in another country for a service nobody can guarantee. If it goes wrong there is no refund and nobody to complain to.
These steps change settings on the car you own. Work slowly, read every screen before you tap it, and do not tap anything this guide does not name.
Your dealer may treat engineering access as tampering. DriveLab does not flash or modify the car's firmware, but warranty terms depend on your dealer and your country. If that matters to you, ask them first.
DriveLab does not sell, broker or endorse any of this. We take no cut, we have no partner, and we cannot help you if a payment goes missing.
What you need on the day Community-reported
This is read off the steps of the two guides we cite at the end of the page. It is what those procedures need, not a checklist published by BYD.
DiLink 3 and 4
- A USB stick
- The installer has to get onto the head unit somehow; DiLink's file manager reads it from there.
- A computer or phone that can download a file
- To fetch the installer before you go out to the car.
- Permission to install from unknown sources on the head unit
- DiLink asks the first time. On some firmware it cannot be granted at all, and then this route is closed to you.
DiLink 5, 5.1 and 6
- A working internet connection in the car
- The car has to reach a server to produce the code. A hotspot that says “connected” but carries no data is the usual trap — prove it by loading something.
- A phone that can photograph the head unit's screen
- The code appears on the car's screen and has to be sent on as a picture. DriveLab cannot read it off the screen and cannot decode it.
- The messenger the person who will scan actually uses
- The guide we cite sends the photo over WeChat. The car's own dialog asks for WeCom, a different app from the same company. Settle which one with them, and do it before the day.
- A way to send money abroad
- The guides name Chinese payment services. Set the payment up and test it in advance — not with a five-minute timer running.
- A second person who has already agreed to scan
- Nothing in this route works without them. They have to be at their phone at the moment you generate the code.
- A DNS-changer app installed on the head unit
- One of the steps below needs it. Install it before you dial anything.
- A USB stick, and a computer or phone that can download a file
- The DNS-changer app is a file on a sharing page and the head unit may have no browser. It reaches the car the way route 1's installer does: downloaded elsewhere, carried on a stick, opened in DiLink's file manager.
- Permission to install from unknown sources on the head unit
- DiLink asks the first time. If it cannot be granted, the DNS app cannot be installed and this route is closed — find that out at home, not at the car with somebody waiting.
- Somewhere you can sit with the car for an hour
- You cannot rush this and you should not have to leave in the middle of it.
How long it takes We do not know
No source we have gives a duration, so what follows is our reading of the steps, not a measured figure.
- DiLink 3 or 4: minutes, once the installer is on a USB stick.
- DiLink 5 or newer: perhaps half an hour of your own work — getting the car online, installing the DNS app, setting it, agreeing everything with the other person — plus however long that person takes to answer, which nobody can promise. Agreeing a time with them in advance is the only thing that makes this predictable at all.
- The only part with a real clock on it is the code itself: about 300 seconds.
Do not start the remote route at the end of a day, at a charger you have to vacate, or anywhere you cannot stay with the car.
Which head unit do you have?
Once installed, DriveLab can tell whether anything answers on the head unit's debug port, and says so under Settings → This car → Connection. The build fingerprint is in its Diagnostics text, which it can send to support with no location and nothing that identifies you or the car.
What nobody here can read: the DiLink generation. Nothing on the head unit reports it reliably, so the Android version is the best hint.
- Android 10 or older — usually DiLink 3 or 4. Take route 1.
- Android 12 or newer — usually DiLink 5 or newer. Take route 2.
- Android 11 — we cannot tell. Pick a route yourself, or read both.
Those two hints are the only generation mapping anything we have supports. Your own answer always wins over the guess.
First, check whether you already have it Measured
- What to do
- Install DriveLab, open it and look at Settings → This car → Connection. The app checks the head unit's own debug port and answers within seconds.
- Why
- Some cars arrive with debugging already on, and some owners had it opened once and forgot. There is no reason to pay for something you already have.
- What you should see
- Either “Live” or “Waiting for you to allow debugging on the head unit screen” — debugging is already on, so skip straight to the steps after the unlock — or “No ADB: nothing is listening on the debug port”, which is the normal state on a car that was never unlocked.
- If it does not work
- “Not connected to the car” means the app has not reached the car yet. Wait a few seconds and tap “Reconnect”.
Route 1 — DiLink 3 and 4: you can do it yourself
Adapted from the README of BYDMate, a separate open-source project, section “Enable ADB”. It carries no date. This route costs nothing and involves nobody else.
Install BydDevelopmentTools on the head unit
Community-reportedBydDevelopmentTools, the link that README gives
https://disk.yandex.by/d/e3gEnY9P2Y9_fQ- What to do
- Download the BydDevelopmentTools installer on a computer or phone, copy it to a USB stick, plug the stick into the car and open the file in the DiLink file manager. Allow installing apps from this source if Android asks.
- Why
- Our source starts this route here — install this app, then open “Settings” → “Version Management”. It does not say what the app itself does.
- What you should see
- A new app called BydDevelopmentTools in the car's app list.
- If it does not work
- If DiLink refuses to install it, the firmware is blocking apps from unknown sources — look for that switch in the DiLink settings. If the file will not download at all, the link is a public file-sharing page and may simply be gone.
This is a third-party installer from a file-sharing link. Nobody at DriveLab has opened it, checked what is inside it or knows who publishes it. Installing it is your decision, and DriveLab will not download or install it for you.
Open Version Management
Community-reported- What to do
- Open “Settings”, then “Version Management”. Look in the car's own Settings app and inside BydDevelopmentTools: our source does not say which of the two it means, so check both.
- Why
- The hidden developer switches sit behind a tap counter on that page.
- What you should see
- A page listing versions, with a line reading “Reset to factory default”.
- If it does not work
- Check both places first — the car's own Settings and the BydDevelopmentTools app, including anything called “System” or “About”. Only if neither has a “Version Management” page is your firmware probably newer than that guide and locked like DiLink 5, and only then switch to route 2.
Which “Settings” this means is not settled by anything we have. The source says only “install BydDevelopmentTools, go to Settings → Version Management”; its Chinese version spells the path in the car's own settings terms, which reads like the DiLink Settings app rather than a screen of the tool. Nobody here has seen either screen, so look in both.
Tap “Reset to factory default” ten times
Community-reported- What to do
- Tap the text “Reset to factory default” itself — not a button beside it — ten times in a row, with an even rhythm.
- Why
- Ten taps is the counter that reveals the developer switches, the same trick as tapping a build number on a phone.
- What you should see
- New switches appear on the page, among them “Debug Mode when USB is Connected” and “Wireless adb debug switch”.
- If it does not work
- If nothing appears after ten taps, try again with an even rhythm. If a reset dialog keeps coming up instead, stop.
The line you are tapping is named after a factory reset. The guide says ten taps only reveal the switches, but nobody here has tested what a mis-tap does. If any dialog offers to erase the car, cancel it.
Turn on the two debugging switches
Community-reported- What to do
- Switch on “Debug Mode when USB is Connected” and “Wireless adb debug switch”. Leave everything else on that page alone.
- Why
- These two are what DriveLab needs: one opens debugging over the cable, the other over the network.
- What you should see
- Both switches sitting in the on position. Then go to the three steps after the unlock.
- If it does not work
- If a switch flips itself back off, the firmware is locked like DiLink 5 and this route ends here. Switch to route 2.
Whether an updated DiLink 3 or 4 firmware still allows any of this varies: the same source says updated 3/4 firmware can be locked like DiLink 5.
Route 2 — DiLink 5, 5.1 and 6: somebody else has to open it
From one owner's guide, created 26 February 2025. Firmware has changed since, and nothing here has been confirmed on 2026 firmware.
On these head units ADB is locked and there is no tap counter to find. The car can be made to print a one-time code; somebody with a tool nobody here has access to answers that code, and the engineering menu opens on the car's screen. That is the whole route — everything before the code is preparation, and everything after it is two switches.
The five minutes, and how to prepare for them
The code the car prints lives about five minutes — the guide's own photograph shows the counter reading “( 298 ) s left”, falling from there. That number on the car's screen is the authority; any timer on your phone is only a convenience. Five minutes is enough only if everything else is already done. Before you dial anything:
- 1The car is online and you have proved it by loading something.
- 2The other person has agreed, in writing, to a time, and is at their phone now.
- 3You have already agreed which messenger, and you have sent them a message today and had a reply, so you know the account still works.
- 4Payment is arranged the way you both agreed.
- 5The DNS-changer app is installed and its redirect is running.
- 6Your phone's camera is open, the car's screen brightness is up, and you know how to send a photo in that messenger without hunting for the button.
- 7You are sitting in the car, it is awake, and nothing about it is going to time out or go to sleep.
Then dial. If the code expires, nothing is broken: check the redirect is still on and dial again for a fresh one. If several codes expire in a row, stop and fix the timing with the other person before you burn another.
Get the car online
Community-reported- What to do
- Connect the head unit to the internet — the car's own connection, home Wi-Fi or a phone hotspot — then open something on the head unit that actually needs the internet and check that it loads.
- Why
- The car has to reach a server to produce the code. Without a working connection nothing later in this route works.
- What you should see
- A Wi-Fi or mobile icon in the car's status bar, and a page that loads.
- If it does not work
- A hotspot that says “connected” but carries no data is the usual trap. Prove the connection works before you go on.
Which network screen a given DiLink firmware has varies, and some have none that an app can open. Use the car's own menu if a shortcut lands somewhere else.
Arrange the scan before you touch anything else
Community-reportedThis step costs money and carries risk
- You would be paying a private person in another country, usually in advance, through a payment service with no buyer protection.
- We cannot verify who any of these people are. The contact our source names is copied from a guide written in February 2025. It may be stale, it may have changed hands, it may be someone else entirely by now.
- DriveLab does not sell this service, does not broker it and takes nothing from it. We cannot help you get your money back.
- What this does to your warranty depends on your dealer and your country. Ask them if that matters to you.
- What to do
- Find someone who can scan the car's code for you, and agree the price and the time first. The code the car gives you later lives for five minutes only, so the other person has to be at their phone the moment you generate it.
- Why
- Every later step is wasted if nobody is waiting to scan. This is also the step that costs money, so decide here, calmly, and not with a five-minute timer running.
- What you should see
- A person who has agreed, in writing, to scan a code for you at a time you both picked, in a messenger you have both used today.
- If it does not work
- If nobody answers, stop here. Do not run the rest of the steps “to see what happens” — you would only burn codes.
Our two sources disagree about who does this work and what it costs: different channels, different figures, and both are well over a year old. We do not publish a private person's contact details or a price we cannot stand behind on a public page. Agree the amount with them before you send anything.
The guide says to send the photo over WeChat; the car's own dialog asks for WeCom, a different app from the same company. Which one a given person wants varies — settle it with them.
Point the head unit at a different DNS server
Community-reportedDNS 1123.123.123.123Leave the second field, DNS 2, empty.
The DNS-changer app, the link that guide gives
https://drive.google.com/file/d/1hdoDwkVbdAYk2uz1z-JNHu9ocRrX-wB5/view?usp=drive_linkThat link opens a Google Drive viewer page, not the file itself — download the installer from that page, on a phone or a computer. A DiLink 5 head unit may have no browser at all.
- What to do
- First get the installer to the car, exactly as in route 1: download it on a computer or phone, copy it to a USB stick, plug the stick into the car and open the file in the DiLink file manager, allowing installation from this source if Android asks. Then open the app, choose the option to enter a server by hand, type the address below into the first field, leave the second empty, and press START. The first time you press START the car asks to allow a VPN connection — accept it, and tick “always allow” if it is offered.
- Why
- The guide says the car's verification only reaches the service that produces the code when its name lookups go through this server.
- What you should see
- The app's status changes from “not connected” to running.
- If it does not work
- If the app will not install at all, the firmware is blocking unknown sources — look for that switch in the DiLink settings. If the status stays on “not connected” after START, the car either refused the VPN connection or has no VPN: press START again and watch for the permission dialog, and if it never appears this route is closed on your firmware. If the next step shows a red banner “Network is not connected. Please check the network settings”, the redirect has dropped: open the app, press START again, and repeat the code step.
A DNS server decides where the car's network requests go. Sending a car's traffic through an unknown server run by an unknown party is a real risk, and the app the guide points at is an ad-supported third-party installer from a file-sharing link that nobody here has looked inside. Turn the redirect off again as soon as the unlock is done, and remove the app if you can. DriveLab will not download it or install it for you.
Why this server is needed at all, and who runs it, is something nobody here can explain — the guide simply states it. The VPN dialog and the key icon are our own reading of Android rather than the guide's words: it mentions neither, and a firmware that blocks VPN closes this route. It was reported working in February 2025; nothing we have confirms it still works on 2026 firmware.
Dial the secret code
Community-reported*#91532547#*- What to do
- Make sure the person who will scan is ready, then open the phone app on the head unit and enter the code below.
- Why
- The code makes the car show a one-time QR code that the other person's tool reads to open the engineering menu.
- What you should see
- A dialog headed “Perform secret code verification” with a QR code, the line “Please scan the QR code using WeCom”, and a countdown under it — in the guide's own photograph it reads “( 298 ) s left” and falls from there.
- If it does not work
- A red banner “Network is not connected. Please check the network settings” above the code means the DNS redirect is not active: go back a step, press START again, and dial again. If nothing happens at all when you dial, your firmware may use a different code — ask an owners' community for your model rather than trying other codes at random.
Whether the dialer accepts a code pasted into it, whether a SIM or a paired phone is needed, and where the phone app lives all vary by firmware. Our source only says “go into calls”.
Send the photo and wait for the scan
Community-reported- What to do
- Photograph the code with your phone and send it to the person who agreed to scan it. Stay by the car: the engineering menu opens on the car's screen within seconds of the scan.
- Why
- Only their tool can answer that code. DriveLab cannot scan it, cannot read it off the car's screen and can do nothing with it — the car makes it and someone else has to answer it.
- What you should see
- The engineering menu appears on the car's screen, with five entries reading LogControlSwitch, TestTools, “Adavanced Configuration” (misspelled by the firmware itself) and two Chinese ones.
- If it does not work
- If the countdown runs out, nothing is broken: check the redirect is still on and dial again for a fresh code. If several expire in a row, stop and sort out the timing with the other person first.
Turn on the two debugging switches
Community-reported- What to do
- In the engineering menu tap “TestTools”. On the page that opens, headed “OTATool”, switch on “Wireless adb debug switch” and “Debug mode when USB is connected”. Change nothing else there.
- Why
- These two switches are the whole point of the unlock. They are the same two the DiLink 3 and 4 route reaches by itself.
- What you should see
- Both switches on. Under the first one the page shows a line about this device and the host being on the same network, and an IP address.
- If it does not work
- If a switch will not stay on, leave the menu, dial the code again and ask for a second scan. If the engineering menu closed before you reached the page, it can only be reopened by another scan.
“Revoke USB debugging authorizations” sits directly under the two switches. Do not tap it — it throws away the very permission you are about to give DriveLab.
Whether these switches survive a restart or a firmware update varies; the source stops at “now ADB is on”. The next two sections are where that question gets answered for your car.
After the unlock: the two steps that finish the job
Both routes end here, and so does the money. Everything in this part is the app's own behaviour on the head unit it runs on.
Allow the debugging dialog on the car
Measured- What to do
- Open DriveLab. The first time it reaches the car's system, DiLink asks “Allow USB debugging?”. Tick “Always allow from this computer” and confirm.
- Why
- The switch opens the door; this dialog is the car agreeing to let this particular app through it.
- What you should see
- The dialog appears once, and live figures from the car start showing up on Home.
- If it does not work
- If you tapped it away, reopen the app and it comes back. If it comes back on every start, the “Always allow” box was not ticked.
Find out whether ADB survives a restart
Measured- What to do
- Restart the head unit once — press and hold the volume wheel until the screen restarts — then open DriveLab and look at Settings → This car → Connection.
- Why
- Some firmware closes the debug port at every restart. Which builds do is told by behaviour — restart and look — never by a version string.
- What you should see
- “Live” again: your firmware keeps debugging across restarts, and you are done.
- If it does not work
- “No ADB: nothing is listening on the debug port” or “This firmware needs wireless debugging, which this build cannot use yet”: the port closed with the restart. The next section says what that means.
When ADB closes at every restart
On some DiLink builds from around mid-2026 — owners recognise them by “2606” in the build string — the classic ADB port no longer stays open across a head-unit restart. The setting still reads as on, but nothing is listening, so live data and car control stop until ADB is switched on again by hand. Android's own wireless debugging still works on those builds and could be a way back in, but this version of DriveLab cannot use it yet. What it does do is say plainly what it sees, on the Connection card in Settings → This car:
- Live
The debug port answers and the car is sending data.
What to do — Nothing.
- Waiting for you to allow debugging on the head unit screen
ADB is on, and the car is asking whether to let this app in.
What to do — Allow it on the car's screen and tick “Always allow from this computer”.
- No ADB: nothing is listening on the debug port
ADB is off, or a restart closed it.
What to do — Switch ADB on again, the way you did the first time.
- This firmware needs wireless debugging, which this build cannot use yet
The debug port only accepts Android's wireless debugging, which this version of the app cannot use yet.
What to do — Switch the classic ADB debugging on again by hand. DriveLab cannot reopen it on its own yet.
- Not connected to the car
The app has not reached the car, and none of the reasons above applies.
What to do — Tap “Reconnect”. If it stays, send the diagnostics to support (see below).
If your car has such firmware, plan for it: after every restart, live data and car control stay off until ADB is on again. Trips from the car's own history keep coming in.
Checking that it worked
DriveLab shows what it gets from the car in three places, all read from the car itself. Nobody should have to take a stranger's word for it.
Settings → This car → Connection: “Live”
The debug port answers and the car has let this app in.
“Live” at the top of every screen
Readings are arriving from the car right now.
Diagnostics → “Test the helper”
A read-only self-test of the part of the app that talks to the car, one line per route. Nothing on the car is changed.
If one of them never comes good, open Settings → Sharing and support, tap “Send diagnostics to support” and write to us with the support code it shows.
Troubleshooting
Every entry says where it comes from, because this list mixes the app's own behaviour with things only another owner has reported.
BydDevelopmentTools will not install
Community-reportedThe firmware is blocking unknown sources — look for that switch in the DiLink settings. If the download itself fails, the file-sharing link may simply be gone.
No “Version Management” anywhere
Community-reportedLook in both the car's own Settings and BydDevelopmentTools — the source does not say which it means. Only when neither has it is your firmware probably newer than that guide and locked like DiLink 5; then use route 2.
Ten taps reveal nothing
Community-reportedTry again with an even rhythm. If a reset dialog comes up instead, stop — do not confirm it.
A debugging switch flips itself back off
Community-reportedThe firmware is locked like DiLink 5. Route 1 ends there; use route 2.
The DNS-changer app will not install
Community-reportedThe same as the row above: unknown sources are blocked, or the file-sharing page is gone. Without it, route 2 cannot go on.
The DNS app stays on “not connected” after START
We do not knowThe VPN connection was refused, or the firmware has none. Press START again and accept the dialog; if it never appears, route 2 is closed on this firmware.
Dialling the code does nothing at all
We do not knowYour firmware may use a different code. Nothing we have covers that — ask an owners' community for your model. Do not try other codes at random.
A red banner about the network sits over the code
Community-reportedThe DNS redirect is not active. Open the DNS app, press START, dial the code again.
The countdown ran out before the scan
Community-reportedNothing is broken. Check the redirect is still on and dial again. If several expire in a row, fix the timing with the other person first.
The engineering menu closed before you reached TestTools
Community-reportedIt can only be reopened by another scan.
Everything worked, but the app still sees nothing
MeasuredConfirm “Allow USB debugging?” on the car's screen, then tap “Reconnect” under Settings → This car → Connection.
“Allow USB debugging?” comes back on every app start
MeasuredThe “Always allow from this computer” box was not ticked. Tick it next time.
It worked, then a restart killed it
MeasuredYour firmware closes the port at every reboot. See the section above on restarts.
Still stuck
MeasuredIn DriveLab, open Settings → Sharing and support and tap “Send diagnostics to support”. Then write to us with the support code, your head unit's Android version and the step you stopped at. The diagnostics carry no location, no route and nothing that identifies you or the car.
The car's BYD account
The other thing people call “master” is the BYD account your car is bound to. On an imported car it is often still the exporter's or the first Chinese owner's, which is why BYD's own phone app, over-the-air updates, remote control and adding family members do not work for you. DriveLab does not need it, cannot see who your car is bound to and cannot change it.
We have no reliable source for the release procedure. What follows is the set of questions to ask and the papers to have ready, not a set of steps. Anyone who gives you an exact procedure for your country should be able to say where it comes from.
What the account actually controls
We do not knowAssume that pairing BYD's phone app, over-the-air updates, remote commands and sub-accounts all hang on it. This is the description owners give each other; we have no BYD document for it, and what is affected may differ by market.
Find out who holds it now
We do not knowAsk the seller or the exporter directly, in writing: which account is the car bound to, is it theirs, and will they release it. Ask before money changes hands if you are still buying. A seller who will not answer has answered. We cannot tell you how to look the binding up yourself — nothing we have describes a way to read it from the car or from this app.
Get your papers together
We do not knowThe purchase contract, the customs and import paperwork, the registration document in your name, the VIN exactly as written on the car, and the seller's written confirmation that they release the account. Scan all of it into one folder before you ask anybody for anything. This list is our suggestion, not a requirement published by BYD; your importer may ask for more, or for less.
Ask for the release
We do not knowIn this order: the seller or exporter, then a BYD dealer in your country, then BYD support for the market the car was built for. Keep every answer in writing. Which of the three can actually do it depends on where the car came from and how it was imported, and we cannot tell you which door will open. If all three say no, an owners' community for your model and your import route is the next place to ask.
Bind your own account
We do not knowOnce the car is released, create or use your own BYD account and bind the car to it, following whatever the party who released it tells you. Which BYD app applies to a grey-imported car, and whether it will accept an account registered in your country, depends on the market the car was built for. We have no source for this and will not guess.
What works in the meantime
MeasuredNothing here blocks DriveLab. Finish the engineering access and you get live data, trips, charging, the voice assistant, cluster projection and the head-up display — with no BYD account at all. What stays out of reach until the account is yours is BYD's own phone app, over-the-air updates and BYD's remote control.
Sources
Route 2 and every on-screen label quoted in it come from one guide, “Активация ADB на BYD Dilink 5 / 5.1 / 6”, written by just_firdavs. The file's own metadata gives a creation date of 26 February 2025.
Route 1, and the description of the firmware that closes the port at every restart, are adapted from the README of BYDMate, a separate open-source project. DriveLab is an independent app and is not built from it. The README carries no date, so we cannot tell you how old it is.
Neither source has been tested on a car by anybody working on DriveLab, and firmware has moved on since both were written. Check that a step still applies before you pay anyone.
We do not re-host either guide or its photographs. The author is cited and his channel is linked; only the firmware's own on-screen labels are reproduced here, because those are BYD's words, not his.
The author of the DiLink 5 guide publishes on this channel: https://t.me/just_byd
What DriveLab will not do
- Download or install any third-party installer for you. We show the links and say who wrote them; handing out a stranger's binary is exactly the brokering this guide refuses.
- Read the code off the car's screen or decode it. There is no camera that can see the head unit's own screen, and the code is only useful to the other person's tool anyway.
- Claim to know which DiLink generation your car has. Nothing on the head unit reports it.
- Change the car's DNS itself. That needs a system permission that only exists after debugging already works.
- Pretend to know how much time is left on a code. The car prints its own countdown, and that number is the only true one.
- Publish a private person's contact details or a price we cannot stand behind on this page.
- Sell, broker or endorse remote unlocking. No cut, no partner, no referral.
If you get stuck
Write to us with your head unit's Android version, the route you took and the step you stopped at. If DriveLab already reaches the car, also tap “Send diagnostics to support” (Settings → Sharing and support) and include the support code it shows.
contact@hakobi-tech.comWe cannot unlock a car remotely, we cannot recommend anyone to do it for you and we cannot get a payment back — but we can usually tell you which of the checks above is the one that is actually failing.