Everything is covered here https://android.stackexchange.com/a/213374
Only addition is the "Restore process" chapter.
Google Support makes it sound like you can only restore the backup on setup.
At setup, to restore your data, follow the on-screen steps.
| #!/bin/bash | |
| #Source: https://www.krausmueller.de/en/2017/07/04/dynamic-dns-client-for-ipv6/ | |
| HOSTNAME="" | |
| PASSWORD="token" | |
| USER=HOSTNAME | |
| CACHE_FILE="/tmp/update_ipv6_cache" | |
| while getopts ":d" opt; do | |
| case $opt in |
| Address | Netmask | Gateway | Comment |
|---|---|---|---|
| 192.168.1.1 | 255.255.255.255 | 192.168.1.1 | Adds the router/gateway only |
| 192.168.1.0 | 255.255.255.0 | 192.168.1.1 | Adds the subnet |
| Desks are not being synced across Chromebooks | |
| Shelf (taskbar) can't be set/customized to only display open application icons from the same desk | |
| Fixed in ChromeOS 89: | |
| On Chrome session restore (e.g. after crash), restored windows are all being placed on the first desk (i.e. all other desks are empty) | |
| "When you reboot, your windows will restore to their previous desks so your workflow isn’t interrupted." - https://www.google.com/chromebook/whatsnew/ | |
| Maximum amount of desks you can have is 4 (limit is hindering for categorizing) | |
| Was increased to 8 (I still sometimes reach this limit) |
This is about a drive with MBR/DOS partition table and a NTFS partition on which I accidentally overwrote the partition table with fdisk /dev/sdb and then pressing g (new GPT partition table) and w (write changes to disk).
Luckily, I still had a terminal open, where I had the partition table (from fdisk -l) printed before I created a new one that overwrote it:
Disk /dev/sdb: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: 2115
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
| #!/bin/bash | |
| ccuip="192.168.178.XX" # private/LAN (this way, the action can't be executed outside the home network, except if you happen to be connected to it via a VPN) IP address of your HomeMatic CCU | |
| action="<prototypejs><![CDATA[<YOUR ACTION>]]></prototypejs>" # Copy the action request data from browser dev tools | |
| # Fetch session id | |
| sid=$(curl -sD - "http://${ccuip}/pages/index.htm&client=3" | sed -n "s/^.*\(sid.*\)$/\1/p"); # Only if automatic login is activated on your CCU, this request will receive a response with a session id (sid) which can be found by sed # If you run this script too often (multiple times within a short period), the CCU will not respond with new sids due to "too many connections" for a few minutes. | |
| sid="${sid//[$'\t\r\n ']}"; # sanitize: filter out \t,\r,\n,space chars | |
| # Request desired action, e.g. "open door" on a KeyMatic lock |
| #!/bin/bash | |
| _fileloc=$HOME/lqxcheck #Where to keep the pkgs | |
| _CHROOT=$HOME/chroot #Where do you want the chroot | |
| _nproc=$(nproc) #How many threads to compile on | |
| if [[ $EUID -ne 0 ]]; then | |
| echo "Give me the root password:" | |
| sudo echo "Thanks" | |
| fi |
If you activate WhatsApp (verifying your phone number) while having a /sdcard/WhatsApp/Databases/msgstore.db.crypt12 file present AND have a WhatsApp backup on Google Drive, WhatsApp will claim to restore your Google Drive backup (with your consent), but it only restores the media files from Google Drive but at no occassion the msgstore.db.crypt12. It won't merge your local backup and the cloud backup databases!
With local WhatsApp media files it will only offer to restore the local backup at activation but not the one from Google Drive, hence the need for an empty /sdcard/WhatsApp/Media/ folder. But with a local chat backup, the Google Drive backup restore process just imports media only anyways.
Ways to get to the key file to decrypt the *.crypt12 DBs:
/data/data/com.whatsapp/files/key with root permissionsadb backup com.whatsapp and extract the key from the .ab fileI have extracted the key and found out that it's the same for all my devices (*I always tested wi
kstart5 plasmashell works as intended. If this is not the case, the solution will very likely not help you!Open "System Settings -> Startup and Shutdown -> Autostart -> Add Program" and add plasmashell (manually write it into the text field in the dialog window). (File saved in ~/.config/autostart)
The old autostart file only had the content
dig sometimes uses double tabs which is only good for visually viewing lookups of short to medium-length hostnames, but it is bad for reusing the values as in parsing them like a CSV file into a table.
To prevent the double use of tabs, you can pipe as follows:
dig <host> | sed --quiet 's/[\t ]\+/\t/gp'
pipe/forward it to sed and let it replace one or more (greedy) tab or space with a single tab