[APP][8.0+] [OPEN SOURCE] [ROOT] OAndBackupX - Apps and data backup tool for Android.

[Walden0]

Hello.

So, my new device is ARM64; old device is not. I installed an old version (0.3.5) on the old device; new device has version 4.0.

I haven't tried to restore anything yet, but, is this going to be a problem? Should I installed an older version on the new device and try? Any other work around that might help?

Thanks!

Yea, from version 3.0.0 onwards you cant restore backups made with older versions. So its better you use the older builds. Or can use original oandbackup app

 

[wilspeak]

I tried to install the apk on my Rooted S7 Edge and I received a "There is a problem parsing the package" error message. How can I correct that error? Also can this application freeze applications like Titanium Pro?

 

[heinhuiz]

I tried to install the apk on my Rooted S7 Edge and I received a "There is a problem parsing the package" error message. How can I correct that error? Also can this application freeze applications like Titanium Pro?

Probably something went wrong while downloading, just fetch it again.
Freeze is called 'Disable' in the app, so yes, you can.

 

[wilspeak]

Probably something went while while downloading, just fetch it again.
Freeze is called 'Disable' in the app, so yes, you can.

My Titanium Pro stopped working. This time I am going to load the apk through my PC. I may be getting a new phone .. I am thinking about getting the
Samsung Galaxy S20 5G and rooting it. Thank You

 

[mtshure]

Today I tried this app for the first time. I backed up from an old phone, copied the files to a new phone, then when I try to restore it says "RestoreFailedException: base.apk is missing in backup". I see base.apk files from explorer app and I granted root, storage permission.

I installed the app on both phones from F-Droid, version 4.0.0.

Why do I get this error?

 

[Walden0]

Today I tried this app for the first time. I backed up from an old phone, copied the files to a new phone, then when I try to restore it says "RestoreFailedException: base.apk is missing in backup". I see base.apk files from explorer app and I granted root, storage permission.

I installed the app on both phones from F-Droid, version 4.0.0.

Why do I get this error?

It is a known issue as of now.
According to the developer these are the workarounds to solve it :

Just make sure it's the same directory as when you've done it. The directory in a Uri form can be found in any of the .properties files that you made by then.

Or

Create a new backup with the same mode, then replace its files with the ones from the older one

 

[mtshure]

It is a known issue as of now.
According to the developer these are the workarounds to solve it :

Just make sure it's the same directory as when you've done it. The directory in a Uri form can be found in any of the .properties files that you made by then.

Or

Create a new backup with the same mode, then replace its files with the ones from the older one

After multiple failed attempts, I used Swift Backup to move apps from old phone to new. It was not perfect but it worked.

Reading your suggestions, I backed up the same app (with different app data) on both phones, replaced backup files from new phone with old phone, then tried to restore. It gave me "Errors occured, RestoreFailedException: Could not read the input file or write an output file due to IOException: java.io.IOException: Unable to create folder ..."

I am not sure what went wrong this time. It looks like this app is not mature yet. I will come back later to see if the app becomes stable then.

 

[goodflood]

On my manta tablet running LOS 16, I installed OABX 4.0. I took a backup. Then, I upgraded the ROM To LOS 17.1. Now, when I try to go to restore, nothing shows. Even though I have linked to the backup/restore folder several times. The issues to provide a location keeps coming up. I can't backup or restore. I have installed the app from f-droid and also, the one in the backup/restore folder. Funny thing is, even though ALL settings are enabled, and nothing shows up, I see my apps flash for a second and then disappear. I was afraid I did not do the backup properly, but I know there are there. What is going on? Worse case, I flash back LOS 16 and try a restore.

EDIT1: This might have to do with permissions to read / write. I haven't done anything wierd; its a clean install and I have magisk latest. What more do I need?

EDIT2: The path in .properties was screwed up. I used notepad++ to change it in bulk: http://cybernetnews.com/find-replace-multiple-files/. It worked!

Use notepad++, to search and replace the following. In my case:

From: content://com.android.providers.downloads.documents/tree/downloads/document/raw%3A%2Fstorage%2Femulated%2F0%2FDownload%2FOABackupX%2F
To: content://com.android.externalstorage.documents/tree/home%3A/document/home%3AOABackupX%2F
Example: http://cybernetnews.com/find-replace-multiple-files/

Oh, before that, use Unix Line Ending so you don't experience problems, if in Windows.

For those trying, no support is provided; do it at your own risk. Or, wait for an official release.

 

[Mumxek]

Like all backup apps, for example titanium, i never found the possibilty to split archives to max size. Fat32 has a 4gb file size limit!!!

 

[goodflood]

So, backup and restore using version 4.0 worked, after fixing the restore location. But, I have one app that shows a yellow shield, Device Protected Data, and, it is not restoring. What do I do?

Will chmod 777 on all the files work?

EDIT: Did not work... not sure what would help. Loss data... started over. App itself had a backup/restore option.

 

[Mumxek]

The app restores backups under its own uid/group, not apps...

 

[Machiav3lli]

So, backup and restore using version 4.0 worked, after fixing the restore location. But, I have one app that shows a yellow shield, Device Protected Data, and, it is not restoring. What do I do?

Will chmod 777 on all the files work?

EDIT: Did not work... not sure what would help. Loss data... started over. App itself had a backup/restore option.

The app restores backups under its own uid/group, not apps...

In the latest 5.0.1 SELinux issues are fixed. The update is already on Github, IzzyOnDroid and will neeed as usual couple of days to be on F-Droid.

 

[heinhuiz]

- deleted -

 

[Valiante]

Release 5.0.2 crashing constantly, can't get passed the setup screen. Anytime "backup folder" is pressed, it crashes.

EDIT: Same with Release 5.0.1

 

[Strephon Alkhalikoi]

Release 5.0.2 crashing constantly, can't get passed the setup screen. Anytime "backup folder" is pressed, it crashes.

EDIT: Same with Release 5.0.1

Logs? The developer can't solve your problem without them. Also, at least here both versions are working fine here (Pixel 2 XL, Android 11).

 

[Valiante]

Logs? The developer can't solve your problem without them. Also, at least here both versions are working fine here (Pixel 2 XL, Android 11).

I saw no instructions on where the logs for this app are located in the OP, where are the logs located?

 

[Strephon Alkhalikoi]

I saw no instructions on where the logs for this app are located in the OP, where are the logs located?

The app doesn't generate its own logs. You need an app like Logcat Extreme or else connect your device to your PC and use ADB to capture a log as the app attempts to run.

 

[SaidJan]

Same here, when I tap on "Backup folder" the app crashed. I'm using the latest version on Android 11. I allowed Storage permission from setting, and gave root access, but still crashes.

 

[birleytweet]

Honestly I've really wanted to switch to Titatium backup to OandbackupX, but always have issues. I was able to restore apps this time, but got the input file error. It restored apps ok, but missing data.
Ended up switching back to Titatium backup again as it just seems to be more reliable, but do hope OandbackupX keeps improving.

 

[Machiav3lli]

Same here, when I tap on "Backup folder" the app crashed. I'm using the latest version on Android 11. I allowed Storage permission from setting, and gave root access, but still crashes.

This usually points out that you've removed Files (system's file manager). This app is the only one able to manage SAF and looking at the direction the Android developers are going, it won't be going away soon but will be more established in the next months and years, as apps are forced to use SAF starting with A11. In the latest test builds this is communicated better now. I think the same applies to your error @Valiante

Honestly I've really wanted to switch to Titatium backup to OandbackupX, but always have issues. I was able to restore apps this time, but got the input file error. It restored apps ok, but missing data.
Ended up switching back to Titatium backup again as it just seems to be more reliable, but do hope OandbackupX keeps improving.

There's always this question, what type of "data" are we talking about here? In the settings(service preferences) you can choose the data that should be backed up. Otherwise, apps saving their data in the external storage against Android standards e.g. Whatsapp can't be backed up "fully", as there's no API to get the addresses of this on-external-storage data.