I would recommend to tar up user-data and system-data in recovery, then adb pull that stuff, drop it into the new device and unpack it there (after removing both folders that were there to avoid merges).
ADB is currently not supported on any of the new Halium devices, sorry for that...
Not an easy solution, ssh was thought to be a replacement, but of course it needs network...
BR
@circ @domubpkm Hey so I'm having the same error code with my Ubuntu Phone VPN connexion.
I changed username and password to avoid non alphanumeric characters.
Do the name and location of .ctr and .key files have any sort of importance?
ca.crt has the form:
-----BEGIN CERTIFICATE-----
...
...
-----END CERTIFICATE-----
and ta.key has the form
-----BEGIN OpenVPN Static key V1-----
...
...
-----END OpenVPN Static key V1-----
Both are extracted from the xxx.protonvpn.com.udp.ovpn file downloaded on my protonVPN account.
Could the gateway port number be an issue?
Do you have any idea why it still doesn't work?
Thanks a lot for any kind of help or suggestion!
Edit1: Note that the password is always missing when I open the VPN editor app, but that could also just be some kind of security. Is that the expected behavior?
a note that the topic in the OP has more details, but adb backup is completely broken for me on pureOS (debian).
https://forums.ubports.com/topic/1725
Thanks for the info on adb_keys location @Lakotaubp !
Ah, I don't think adb backup works with UT, because it's not an Android ROM, and that feature only works with Android.
You need to adb pull /data/*-data or something like that. I forget the exact command.