What is sorely missing are the utilities (and perhaps kernel drivers) that can unbrick an Android phone after trying to install a custom ROM.
Note: I just got a new Oneplus 6 phone, tried to install TWRP (aiming at installing LineageOS), but TWRP totally bricked the phone, and I consummately followed the instructions. There’s nothing quite like that near-heart-attack moment, when your brand new phone gets ruthlessly bricked without even so much as an error message. Thankfully there was an unbricking tool, but it only worked in Windows.
I had no bare-metal Windows install, so I backed up my M2 drive (which had my MX Linux 19 install), then installed Windows 10 just to run that unbricking tool, which required a special Qualcomm driver for Windows.
Once unbricked, then I backed up the Windows install from the M2 drive (should I ever need that unbricking tool again, and I hope not). The Windows install on the 256GB M2 drive (in my case, “/dev/sda”, but be careful here, look before you leap!) compressed down to like 9GB, and it was fast, thanks to zstd!
zstd -v --threads=7 < /dev/sda > /media/youruser/big_disk/windows_bak.zst
Then I restored MX 19 back again:
zstdcat -v /media/youruser/big_disk/linux_bak.zst > /dev/sda
Whew!
This dumpster fire wasted about 20 hours!! It was a nightmare!! I’ve lost all trust in TWRP and trying to install custom ROMS, btw.
PS: I’m sure glad I used the MX Tools called “Snapshot”, and “Live USB Maker”, which allowed me to boot from a USB stick, then back up (compressed) and restore my M2 drive, quickly, using the awesome “zstd” compression utility on the fly. MX Linux and zstd were the beacons of sanity in this whole mess.