EPOS EXPAND Control DSWBT2 – Android Recovery accessible, need ADB/unlock path

[piotrbratkowski1222]

ha-paneld version

Not installed yet – unable to install because the EPOS Teams kiosk blocks APK/ADB access

Panel hardware

Other (state in description)

What happened?

I am trying to repurpose an EPOS EXPAND Control DSWBT2 as a Home Assistant wall panel. The device boots into Microsoft Teams kiosk mode. Developer Options, ADB, Android launcher, browser and file manager are not accessible. USB-C OTG works and a FAT32 USB drive is detected, but APK files cannot be opened from the kiosk. TCP port 5555 is closed. Using the physical reset procedure during boot, the panel reaches the standard Android "No command" recovery screen. I am looking for a way to expose the full recovery menu, enable ADB, enter Rockchip Loader/MaskROM mode, or otherwise escape the Teams kiosk so ha-paneld can be installed

Steps to reproduce

1. Boot EPOS EXPAND Control DSWBT2 normally.
   Device starts in Microsoft Teams controller mode.
   Developer Options / ADB / file manager are not available.
   Insert FAT32 USB drive through USB-C OTG; Android folders are created automatically.
   APK placed in /Download cannot be opened because the kiosk blocks file access.
   Power off by disconnecting PoE.
   Hold the physical reset button while reconnecting PoE.
   Device reaches Android recovery screen showing "No command".`
   Zrzut diagnostyczny (/diag): Not available – ha-paneld is not installed yet, so port 8888 and /api/v1/diag do not exist on this device.
   Wersja Home Assistant: wpisz swoją wersję HA, a jeśli nie wiesz teraz: Not relevant yet – ha-paneld is not installed.
   Odpowiednie dzienniki: No ha-paneld logs available because ha-paneld is not installed. Network testing confirmed TCP 5555 is closed

Diagnostic dump (/diag)

Not available. ha-paneld is not installed on this EPOS EXPAND Control DSWBT2 yet, so port 8888 and /api/v1/diag are not available. The issue is specifically about gaining ADB/Android access in order to install ha-paneld.

Home Assistant version

Not installed yet

Relevant logs

[davidcoulson]

If it's rockchip, use the rkdeveltools software. Connect it via usb and power it up holding down the button. It should show up in the rk tools in either maskrom or loader mode.

From there you can access the partition table and download file system images. No idea what you do after that though.

I got a new android rk device last week and just let Claude code go at it and it was able to root it all on its own with a usb connection (and my help booting it in loader more). Might be a good place to start even if you are going to drive the process manually.

[maxlyth]

Thanks for the detailed write-up.

Getting past a vendor kiosk lock like this one is outside what ha-paneld can help with. ha-paneld installer needs a working adb connection at the bare minimum and I have no route past a locked Teams image. Communities around Rockchip devices are the best place to ask about recovery, loader or MaskROM access on this model.

If you do get ADB working, let me know here and we can see how far it gets. I should say that in general EPOS panels are in general a bad choice for HA panels. Because they are designed for financial transactions, if they were any good, then they should be impossible to circumvent their security and if you can it then it clearly shows that the panels firmware is poorly conceived.