adb shell tail -f /var/log/syslog
@Krille has it pretty well covered, but I'll add I went through the entire teardown/clean/fiddle process (also static pics here : https://www.pntbrother.com/nexus-5-power-button-stuck-nexus-5-boot-loop-fix/ ), without success.
I'm wary of recommending it, but the thing that completely solved for me was HITTING THE POWER BUTTON WITH A HAMMER. Not super hard, but a nice solid hit right on the button. I arrived at this solution only after deciding the unit was otherwise bricked....
@libremax , this is great, thanks for sharing here!
I set subtitles to English and it was quite good. This is a great quick history and status overview of both Sailfish and UBPorts.
I'm on a Nexus 5, Development channel.
I'm not using a free Proton account, so I had to pull the CA certificate (.crt in blog post above) an the TLS auth key (.key in blog post above). I did this by opening an .ovpn file that otherwise works and extracting those parts of it to separate files. This gave me what is referred to in the post as the needed files.
Otherwise, I followed the setup instructions as they are written - I found the screenshots most helpful.
I should also note that I'm not connecting to a free ProtonVPN server, though I doubt that woulds make a difference. Do you have another way to check the configuration you are trying (like a laptop or other machine running OpenVPN) ?
One thing I did do first was to make sure I could use the config I had successfully outside of UT.
Adding this because it was frustrating for me and I could not remember this solution when setting up a new device.
Firing up a valid VPN connection from these instructions (mostly) gave me the message:
"VPN connection XXXX failed because there are no vpn secrets."
This setup uses a USERNAME / PASSWORD for authentication.
Changing username/pass to remove ALL non-alphanumeric characters from the BOTH the username and password fixed this.
This requires making changes with your provider credentials
ex: my_username => my123username
I'm pretty sure this is an encoding issue, but I'm not sure where to bug-post it.
this is great, thanks!
while we're at it, are there notes for what's in these pushes?