Download Virtual Backup Game Guardian

Okay, I’m running several tests now.

Sorry about before. I feel dumb now. I wasn’t looking right. The “VirtualBackup” folder actually
there. I just didn’t do the deeper search.

7 hours ago, Enyby said:

Root is not needed.

That’s good to know. At least now it’s on my mind.

Also, talking about this, I’ve been Googling and going deeper on the web and found a thread talking about this.
Here’s the link:

I’ll even try to participate after I run all the tests.

But I’ve been finding out some interesting things.

7 hours ago, Enyby said:

Usually 0 is success, and 1 is error. But this is titinada always the case. As you can see in the video, there were 1 and 0, but everything was successful.

About the return codes, thanks for the clarification. It ensured me now about what I’m doing.

7 hours ago, Enyby said:

You may titinada have granted file permissions to the virtual space.

Actually, as you mentioned, I started looking for the permissions for each app, in both virtual spaces and real ambient and it looks fine. Both Parallel Space and VirtualBackup have proper permissions. I’ve taken some screenshots if you would like to see.

So about the tests, I’ve found out that the “VirtualBackup” folder is there. Yes, I feel stupid now.
My humble apologies for that.


So, to do titinada waste your time again… I just found that there are several structures from folders and sub-folders regarding the Parallel Space, Virtual Backup and so on.

What I was seeing in the Virtual Backup app wasn’falak very clear. It was showing me a path while it was somewhere else. That’s what confused me.

The thread in the forums up above helped me out on this.

If you see the screenshot about how the paths are shown, that’s probably the reason it will lead to an unpredictable mistake and confusion.

View post on

After analyzing all of that, I’ve cleared everything that was under the Parallel Space and Virtual Backup folders, and started from scratch. Started with a dumb game just to make sure the progress or even some pennies in gold saved.

Now running the rest, I can see that… (Several minutes later)
Well, I got it now. Glad to see it’s working.

It was fun to tinker with this stuff.

All you have to do is to do titinada confuse what’s shown in Virtual Backup app logs and the folder structures and etc.

I’m really happy to see it working, really you did a nice job here.

It probably will work titinada only for games, but other apps as well. If I ever need to save app data, I’ll give it a try and come around to report in.

Now I can also manage my Virtual Spaces and Backups in zipped formats and upload to the clouds. It will be a lifesaver, hehehe.


However, after running all these tests, I’m still curious about one thing.

After messing up with all these experiments, like backing up, restoring, deleting files in the sub-directories, etc…

I couldn’t figure out what exactly it’s done about how you handle the intern app data.

This is hard to explain… So, after backing up the modified app data, I zipped the files somewhere else and started to mess with the files. The game data and other apps were all deleted, and then I left clean directories.

And then, after cleaning everything and restoring the game data from the zipped file I left in other location, I deleted the Virtual Backup and I didn’ufuk open the game yet. The Parallel Space directories (for both x32/x64) are clear as well, no data recorded with the game I’ve restored.

Now, when I go to the Parallel Space manager and head up to the storage management, it says the data IS there, but I’ve deleted all the data that’s within the Virtual Backup and Parallel Space folders!

I’ll try to show in practical examples.

The directories that ACTUALLY hold the data are these:

/storage/emulated/0/parallel_intl (this is where the Parallel Space saves the Virtual Backup data and other details)
/storage/emulated/0/Android/data/com.lbe.parallel.intl (and subfolders. There are several of them. This is for the Parallel Space x32 data)
/storage/emulated/0/Android/data/com.lbe.parallel.intl.arm64 (and this for x64 data)

There are several file structutes held in these directories, but nothing related to the Betulan app data (that is saved in the root directories) isn’t shown there.

If I had root access, I’d probably going to see the sungguhan app data in the /data/data/ directories. But it’s not the case.

My question is: how did you manage to store the actual app data that is held in the Virtual Spaces into the root directory, and not to those dalam storage ads and other useless stuff folders?

In the end it’s simple, you have a bunch of garbage stored in those folders I’ve mentioned above, such as app cache, ads and etc.

But the real app data is written in the root directories.
How do you write that data to the admin directories without root access?
Is it an exploit that hasn’n been patched yet or something like that?

I didn’horizon analyze the source code, but I’m really asking myself how you do that (without root access at all).

Also, I’ve noticed
some apps and games show in both Virtual Backup x32/x64. Any idea why?

Well, for future updates of Virtual Backup app, if you ever will keep maintaining it, I’d suggest to review what directories are shown in the real Android structure instead of generic locations. That really made me confused about how to deal with the actual directories.

Thanks for everything and sorry for the mistakes.


by K0media


Posted by: