Enable ADB on an AI Box: USB, Wi-Fi and Ottocast Port 65535

What ADB mode does on an AI box

ADB (Android Debug Bridge) is Android’s command line for talking to a device from another computer. Most community fixes on this site, from removing the network exclamation mark to enabling multitouch, start with an ADB connection.

AI boxes hide ADB because their single USB-C port normally pretends to be a phone for the car. On a Carlinkit TBox, engineering code 142618 flips that port from car mode to ADB mode. While it is in ADB mode the car sees an unknown device and reports “device not supported”. That is the one thing to remember from this page: switch ADB mode off before you plug the box back into the car. If you forget, the “device not supported” fix walks you back.

The alternative is ADB over Wi-Fi. Android 11 and newer have Wireless debugging in Developer options; it leaves the USB port in car mode, so the box can stay connected to the head unit while you work from a laptop or phone. Ottocast boxes run an ADB service on their own hotspot instead.

Which method fits your box?

If you are not sure which Carlinkit you have, check which TBox do I have. The commands you will use most often afterwards are collected in the ADB cheat sheet.

Steps

adb version

adb devices

adb pair 192.168.1.50:37123
adb connect 192.168.1.50:41235
adb devices

adb disconnect
adb connect 192.168.43.1:41235

adb connect 192.168.43.1:65535
adb shell settings put global development_settings_enabled 1

adb connect 192.168.43.1:29528
scrcpy

Verify it worked

Run adb devices. A working connection looks like this:

adb devices
List of devices attached
192.168.43.1:65535	device

unauthorized means you still have to accept the prompt on the box; offline means the connection dropped, so disconnect and connect again. Then try one harmless command, for example adb shell getprop ro.build.version.release, which prints the Android version.

What can you do once ADB works?

These are the jobs owners most often opened ADB for. Each has its own guide with the exact commands and its own undo steps:

• Clear the network exclamation mark. Android’s connectivity check fails on some networks and marks the connection as limited. One settings command turns the check off; see the exclamation mark fix.
• Remove the floating button or navigation bar. Owners disabled the stock overlays from a graphical client; see remove the navigation bar and floating button.
• Enable multitouch in Android Auto. The no-root method edits one system file over ADB: enable multitouch.
• Mirror and control the screen at home with scrcpy, so you can sign in to apps and arrange the launcher at a desk.

Keep a note of every command you run. If you later install a firmware update and it refuses, the cause is almost always a system change made over ADB, and the note tells you what to reverse. The verity case in particular is covered in firmware update fails after disabling verity.

Undo / rollback

Switching ADB off is part of the job, not an extra:

1. Carlinkit, USB method: enter 142618 once more in Factory settings, or run adb shell setprop persist.sdcarplay.reverse.disable 0. Then plug into the car and confirm the head unit sees the box. If the car still says “device not supported”, follow the full fix.
2. Carlinkit, Wi-Fi method: switch Wireless debugging off. The USB port never left car mode.
3. Ottocast: disconnect and change the hotspot password. If you enabled USB ADB in the factory menu, see below.

Anything you changed through ADB (settings, disabled apps, edited files) stays changed. Each guide that uses ADB has its own undo steps; follow those first, then switch ADB off.

Troubleshooting this guide

adb devices is empty, or the client never connects. Owners fixed this three times by changing the physical link: an Ultra refused a USB 3.0 port and connected at once on USB 2.0, another Ultra stopped reconnecting in a loop with a USB 2.0 cable in a USB 2.0 port, and an Ambient on a Mac turned out to have a bad cable. Also confirm the “adb” banner appeared after 142618.

Ultra seems dead right after entering 142618. It is in ADB mode, so the car ignores it. Switch it back as in the undo section.

“Can’t verify your response because an app is obscuring the permission request”. The stock floating button covers Android’s consent dialog. Drag it to another edge or wait until it fades, then tap Allow; that fixed it for an Ultra owner.

A QR code or “device not activated” overlay covers the mirrored screen. On an Ambient this is expected while the box is out of car mode and does not appear in the car. Right-click in scrcpy (it sends Back) and carry on.

unauthorized that never clears. A TBox Plus owner whose box sat in ADB mode with CarPlay disabled could not accept the prompt; Carlinkit support sent him a factory-reset file for the microSD card, which restored the box. Ask support rather than trying random files.

Picasou 3 no longer connects to the car after you enabled USB ADB in the factory menu. A Volvo XC60 owner hit this. Connect over the hotspot instead and switch the ADB configuration back to Wi-Fi, then reboot; it worked for him from a computer:

adb connect 192.168.43.1:65535
adb shell setprop sys.ly.adb.config wifi
adb shell setprop persist.ly.adb.config wifi
adb shell reboot

“more than one device/emulator”. Several connections are open. Run adb disconnect, or address one device with adb -s 192.168.43.1:65535 shell.

Nothing works and you need the box set up today. Configure it on your desk with Android’s Desktop Head Unit instead, which needs no ADB at all.