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?
@advocatux , I'm more than happy to file - ( I came back to devel yesterday after filing some Q/A on rc )
I just really prefer to have a working VPN while I'm doing that...I get it though - I guess publicizing what I'm asking potentially breeds a feedback-less loop that makes the devel stale
FWIW, it appears that the original problem was an IP change for my VPN server - changing local config fixed.
haha! thanks @hummlbach
dc-732 has my formerly solid VPN connection timing out.
How can I rollback to a previous dev channel version?
Also, where is the best place to file a bugreport for the vpn timeout? I set up via VPN editor and have been running great for weeks before 732.
As you can see from this thread, we really need help with this area! Maybe you could pick up the contacts sync bits and make them what you want to see.
It's really hard to find stuff - if you know where the code is, who to talk to, where to look, tell it everywhere!
If you want a full system back-up via ADB, you need to do it via recovery, not developer mode in the running OS.
thanks, yes - this is all happening in recovery mode :
> adb devices List of devices attached 0b3a1eb703301be3 recovery
a note that the topic in the OP has more details, but
adb backup is completely broken for me on pureOS (debian).
Thanks for the info on adb_keys location @Lakotaubp !
... and after a direct grab of the toolkit here : https://developer.android.com/studio/releases/platform-tools
> ~/Downloads/src/platform-tools/adb version #Android Debug Bridge version 1.0.40 #Version 4986621 > ~/Downloads/src/platform-tools/adb backup totalgarbageandN0nS3nse Now unlock your device and confirm the backup operation...
which is the same 'error'
..so, I'm guessing it's definitely a UBports / this particular phone/install related issue....
so, here's some fun ->
> adb version #Android Debug Bridge version 1.0.36 #Revision 1:7.0.0+r33-2 > adb backup -these are not any kind of acceptable params .... Now unlock your device and confirm the backup operation... >
adb backup cmd is verbatim...
Where do I go to get help with this? I'm on pureOS (debian)
I've removed /data/misc/adb/adb_keys from the device (
rm -rf /data/misc/adb/adb_keys).
adb backup -apk -obb -shared -all -f ./current.ab # Now unlock your device and confirm the backup operation...