Question Has anyone been able to restore nand backup since Android 13?

Search This thread

Aserar

Senior Member
Oct 10, 2014
187
28
I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?
 

Aserar

Senior Member
Oct 10, 2014
187
28
Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.

Requires Root, but you can always uninstall Magisk Root
Yeah I do a swift backup also messages call log all of it but setting up the rest of the phone, logging back into accounts, is a pain, plus I always find an app or something that I forgot to refresh its backup. Nothing is like nand backup if you're testing new rom and might just go back
 
Last edited:
  • Like
Reactions: duttyend

DarthJabba9

Recognized Developer
May 5, 2014
4,184
4,331
Greater London
Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.

And you might want to read this wiki very carefully.
 

Aserar

Senior Member
Oct 10, 2014
187
28
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.

And you might want to read this wiki very carefully.
Oh I've gone through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
 
Last edited:
  • Like
Reactions: DarthJabba9

DarthJabba9

Recognized Developer
May 5, 2014
4,184
4,331
Greater London
Oh I've went through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.

2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.

3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).

4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.
 
  • Like
Reactions: Aserar

Aserar

Senior Member
Oct 10, 2014
187
28
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.

2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.

3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).

4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.
 

DarthJabba9

Recognized Developer
May 5, 2014
4,184
4,331
Greater London
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).
 
  • Like
Reactions: Aserar

Aserar

Senior Member
Oct 10, 2014
187
28
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).
And I restored my AOSP backup with no errors! I wish I hadn't deleted my EU backup that I got the error with. The EU rom I had was the latest weekly release V14.0.23 bc the official release had issues but I doubt its that. I'm at a loss :/
 

johnr64

Senior Member
Mar 27, 2021
444
293
Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.

As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.
 
Last edited:

DarthJabba9

Recognized Developer
May 5, 2014
4,184
4,331
Greater London
Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.
Is this on the Play Store?

As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.
Having an alternative backup plan is good. But I have always found nandroid backups sufficient - as long as you know what you're doing.
 

DarthJabba9

Recognized Developer
May 5, 2014
4,184
4,331
Greater London
Honestly I can't be sure of the exact release since its weekly. I looked it up and I can narrow it down to like 3 or 4 releases but it could be this one
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.
 

Aserar

Senior Member
Oct 10, 2014
187
28
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.
Lol there was no need for investigating my friend! The point of the thread was to see if its generally working with others and so eliminate it as the reason for the fail.
 

lapirado

Senior Member
Aug 25, 2015
306
105
39
OnePlus 3
Xiaomi Poco F3
Same here. Since a12 that nandroid gives error on restoring. After that I don't count with that anymore. Ive been relying on Google to restore some apps, and on swift backup to restore the ones that are out of ps.
Before I was using migrate, but have put it aside, since the last time I've got error on zip file and so unable to restore my apps (a real pita). Swift have working flawlessly, and with the advantage of restore app settings too.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of
    Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.

    And you might want to read this wiki very carefully.
    1
    I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?
    Of course. Backup and restore work fine on OrangeFox.
    1
    Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.

    Requires Root, but you can always uninstall Magisk Root
    Yeah I do a swift backup also messages call log all of it but setting up the rest of the phone, logging back into accounts, is a pain, plus I always find an app or something that I forgot to refresh its backup. Nothing is like nand backup if you're testing new rom and might just go back
    1
    Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.

    And you might want to read this wiki very carefully.
    Oh I've gone through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
    1
    Oh I've went through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
    1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.

    2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.

    3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).

    4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.