Using Magisk Backup with Apatch as root method fails

[LordJuice1]

Prerequisites

• I have searched existing issues to make sure this feature has not been requested before
• I have searched the XDA Forums to make sure this feature has not been requested before
• I have read the README documentation to confirm this feature doesn't already exist

Problem Statement

My device is patched with Apatch, not Magisk. It would be nice to be able to backup using Magisk Backup. Right now it just gives an error which I'm not sure is intended or a bug.

Extracting SHA1 from dumped partition ...
Source SHA1 embedded in dumped partition is: None

❌ 2025-11-26 22:33:44 ERROR: The dumped partition does not contain source boot's SHA1
This is normal for older devices, but newer devices should have it.
Cannot create automatic backup file, you can still manually select and create one.

support_2025-11-26_22-35-08.zip

Proposed Solution

Add whatever needs to be added. Or better docs on it

Alternatives Considered

No response

Additional Context

No response

[badabing2005]

Sorry what you're asking does not make sense, the feature is Magisk Backup because it's Magisk specific.

For starters Apatch does not create a backup of the original stock when it creates a patch, which is unlike Magisk.

More importantly, Apatch does not have a functionality to restore to stock by looking for a stock boot backup and flashing that, instead, it performs what's called a self-uninstall, which means:

• It removes Apatch's modifications from within the patched boot image — essentially disabling root/magisk like functionality.
• It tries to revert the changes Apatch itself made to the image, but it does not replace it with your original stock boot image.
• The rest of the kernel or boot image code remains the same as the patched one, just without Apatch’s active binaries or hooks.
• The phone reboots with a cleaned boot image — one that is close to stock, but not guaranteed to be bit for bit identical to the original stock boot.img.

As for PixelFlasher creating a backup, it's practically useless to Apatch as it does not make use of it.
Furthermore the backup that PixelFlasher creates for Magisk is specifically tailored for Magisk, the file naming convention, the location of where it is stored the permissions ...
You can still create that with PixelFlasher by choosing Add Backup from Computer option, but like I said it's useless to Apatch.

Finally the reason why Auto Create Backup fails is because unlike Magisk again, which embeds into the patch the sha-1 of the original stock image, hence PixelFlasher can figure out the matching stock boot image instead of the user making that selection, Apatch does not.