I regurlary took nandroid backups on my pc with TWRP (adb backup --twrp) of my phone, one day i needed to restore one and i found out i wasn’t able to, the restore would stop midway and i needed to completely reset my phone…

Probably the corruption could have happened because i originally took the backups on a PC with a Ryzen processor, that’s what i managed to figure out.

Anyway now i wanna make sure to have safe and healthy nandroid backup, is there a way to check this without having to try to restore on an emulator every time?

  • AlmightySnoo 🐢🇮🇱🇺🇦@lemmy.worldEnglish
    7·
    9 months ago

    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.

    • Discover5164@lemm.eeEnglish
      4·
      9 months ago

      just for academic purposes, in theory, it is possible to chroot into the mounted android image?

    • dontblink@feddit.itOPEnglish
      2·
      9 months ago

      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