Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
Probably the corruption could have happened because i originally took the backups on a PC with a Ryzen processor
How? It's extremely improbable that AMD's CPU would be the one to mess with your backups.
I've never done a "nandroid backup", but assuming it's a disk image that you got, you could try to do a mount -o loop,ro your_image_file /mnt/some_folder_where_you_want_it_mounted if you have access to a Linux distro.
just for academic purposes, in theory, it is possible to chroot into the mounted android image?
you could try that, for science of course :-)
If you search it online you can find that people have some issues with computer running amd ryzen processor and the adb and fastboot commands, i don't know if it's the case, but i couldn't find any other reasons on why a TWRP nandroid backup that was completely fine when i took it and didn't prompt any error couldn't be restored.
It's not a disk image, it is a particular type of compression that packs up different parts of the system (system, data, vendor etc..).
I also tried to enter the backup by using a tool that converts .ab backup in .tar, but i didn't manage to do it.
Anyway i don't really care if i lost that particular backup, i just want to avoid it to happen again