TCP protocol set block not working

35 views
Skip to first unread message

P. Andreas Schmidt, IVE

unread,
Sep 29, 2025, 5:56:42 PMSep 29
to Automate for Android
Hello Henrik,

I'm trying to get automate to automatically set the ADB to port 5555 upon reboot. I've got the privileged service paired and working. I make sure that before the reboot the data background restrictions are turned off and the VPN app killed, upon reboot, the wireless adb setting is changed to 1, I get the ADB services, but when I run the TCP protocol set block it always gives the same SSL error. 

09-29 18:07:54.994 I 240111@1: Flow beginning
09-29 18:07:54.995 I 240111@3: Network service discover
09-29 18:07:58.005 I 240111@2: ADB protocol set
09-29 18:07:58.237 F 240111@2: javax.net.ssl.SSLProtocolException: Read error: ssl=0xb400007498f99098: Failure in SSL library, usually a protocol error
error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN (external/boringssl/src/ssl/tls_record.cc:484 0xb4000074d9036310:0x00000003)
09-29 18:07:58.242 I 240111@2: Stopped by failure

I've tried forgetting all keys, and I went and manually removed any keys that still remained (perhaps from an old installation ...?), and made a new one for the TCP protocol block. I've used the host found by discovery and 'localhost'. All to no avail, unfortunately. I saw someone else on automate's Reddit running into the same issue, but you said you'd never seen it before. I did a little googling and it appears mostly in old posts about older Android versions, but on the shizuku GitHub there also seem to be recent problems of this kind (https://github.com/RikkaApps/Shizuku/issues/638). From what I understood it could be that automate is trying to do Tls and somewhere the system (?) goes to SSL instead, which explains perhaps why there's a ssl3 certificate unknown looking for a TLS record? So perhaps it's again an Android bug and they need to fix it, and once a new version is out this will work again ... Or is it something else? Oh yeah, the Google AI suggested it could also be due to antivirus ... I have Bitdefender. And also Motorola's own security app, that has some network/phishing/... security options, but I just checked and they're turned off ... And switching Bitdefender's internet security off didn't change anything either. 
If I hit the "restart in 5555" option in settings, it works fine ...

I always make sure to have everything up to date.
Android version: 15
Model: Motorola Edge 50 pro 

Thank you very much in advance,

P. Andreas Schmidt, IVE

unread,
Sep 29, 2025, 6:02:56 PMSep 29
to Automate for Android
Or would it have to do with the network I'm connected to? The WiFi here uses WPA/WPA2, would that be too low?

Henrik "The Developer" Lindqvist

unread,
Sep 29, 2025, 9:25:32 PMSep 29
to Automate for Android
The privileged service and ADB blocks use the same way of connecting, i.e. ADB client code. The only difference is how the certificates/keys are stored, the former in the AndroidKeyStore, and the latter in the KeyChain, for the difference see here.
For what i remember, the last report of such an issue was resolved, but i can't remember how. Maybe it was an VPN interfering, system "data save" feature, or if they just regenerated the key.
Also, if the block has the TLS option enabled then the prior Networks Service Discover block should look for "ADB over TLS", i.e. "Wireless debugging". If the TLS option is disabled then it wont work with "Wireless debugging".

Henrik "The Developer" Lindqvist

unread,
Sep 29, 2025, 9:25:53 PMSep 29
to Automate for Android
That's irrelevant.

P. Andreas Schmidt, IVE

unread,
Sep 30, 2025, 1:43:24 PMSep 30
to Automate for Android
The solution was very simple, though it took me to resetting all certificates, de- and reactivating the developer options, in order to get the flow-key to be paired as well (not just the privileged service key), and then it worked. No surprise it said it couldn't find it... Sorry I hadn't been specific enough perhaps in my first message, and gave the impression that I had done this step already. Never mind.
Reply all
Reply to author
Forward
0 new messages