Help Backup game data when cloud save unavailable.

[PhiNu]

Hello! So, I have a game installed from Google Play, Phigros, on my Sumsung Galaxy J6 phone, that doesn't support cloud save 'yet'. The problem is that now I have a new phone coming up tomorrow and it's planned that I'll exchange my old phone immediately to get the new one. Hence, I'm finding ways to somehow backup all my game data (on my PC) since the data isn't readily accessible from the file system either.
I've tried ADB but I ran into a weird problem with it. I could make the backup for the game data, (of 5.21MB size), but when I restore it in another device with the same game installed (from GPlay), it auto deletes the .obb file and changes storage permissions of the game to "Deny", thus rendering the game unplayable, it freezes at loading screen. If I somehow reinsert the .obb file then, it starts a new game and doesn't show any of my saved scores, hence I'm assuming it just removes the restored data.
I don't know what else to do. If there's any way to backup this game, it'd be really helpful...

 

[Hadron]

I assume that the game doesn't provide an option to export/back up your game data.

You could see whether the Helium backup app can manage this. Most backup apps can't actually back up app data unless the device is rooted, but Helium (which uses the ADB backup mechanism) worked well for me a few years ago for transferring data when Google's own phone setup app failed totally on my new (at the time) Pixel. However you should know that it doesn't work for all apps (I believe that there is something the developer has to allow, which most do), so I can't guarantee success.

It's not certain that your saved games are stored in the .obb file. It's quite possible that that is game data (graphics, levels, whatever) and that your play record is in the app's "private" data. But that's what the above app (and the ADB backup) will attempt to back up, so it's worth a shot.

This is one area where Android has always lagged a bit, I'm afraid.

 

[PhiNu]

I assume that the game doesn't provide an option to export/back up your game data.

You could see whether the Helium backup app can manage this. Most backup apps can't actually back up app data unless the device is rooted, but Helium (which uses the ADB backup mechanism) worked well for me a few years ago for transferring data when Google's own phone setup app failed totally on my new (at the time) Pixel. However you should know that it doesn't work for all apps (I believe that there is something the developer has to allow, which most do), so I can't guarantee success.

It's not certain that your saved games are stored in the .obb file. It's quite possible that that is game data (graphics, levels, whatever) and that your play record is in the app's "private" data. But that's what the above app (and the ADB backup) will attempt to back up, so it's worth a shot.

This is one area where Android has always lagged a bit, I'm afraid.

Hello!
Thank you for replying!
I actually did get the Helium app prior and noticed some negative ratings on the app too, basically summarizing that a lot of it's features don't work like they used. And as such, when I was backing up my Phigros game data, it showed me the typical error.

An error occurred while performing your app backup. A log of the error has been sent to ClockworkMod. Click Backup to attempt to backup the remaining apps.

(image file): https://w6iqqw.dm.files.1drv.com/y4.../Screenshot_20210213-201743_Helium.jpg?psid=1

I even viewed the vid "Beginner's Guide - How to fix Helium backup" to update the Helium PC app's ADB server, but that didn't help either. I noticed though that the system apps (messaging storage and dictionary) could actually be backed up and out of the rest of the apps, literally only one could be backed up... which is a Simulation app at that.

So then I noticed one of the reviews suggest a further fix on how to get the app to work (image file):

https://xkijqw.dm.files.1drv.com/y4pZiw6XX-_U-tfEA_L3N7UjgTGcMwvbi1v_qj4F1xZt5Q3Jc4YGWwm1n0UqWG-oeUHuqQCJ6jvjLFEAM59-bEFSVVwjoRf1EN3b7PD_yIQT7Fkh-hcM8azdK6U6UEv36gz1rVjFaJHL9fbbA7rq8BdLa3SL7ndGek_lOAF8gnWCY-tSiVun7NZsIqWwmw7Nt_tDidXYHex0KiH6Yc3Iywc8rFLsbl9WUkRBLj_b60gE3k/Screenshot_20210213-202513_Google+Play+Store.jpg?psid=1

The thing they mentioned was to copy the "carbon" folder from phone to sdcard and then insert the sdcard in the new phone and continue restoration from there. The Google Drive and Dropbox options are ofc not working...
The "carbon" folder is in my phone's internal storage atm, obviously empty.. also i don't think i have an external sdcard right now...

What should I do?

 

[mikedt]

Hello!
Thank you for replying!
I actually did get the Helium app prior and noticed some negative ratings on the app too, basically summarizing that a lot of it's features don't work like they used. And as such, when I was backing up my Phigros game data, it showed me the typical error.



(image file): https://w6iqqw.dm.files.1drv.com/y4.../Screenshot_20210213-201743_Helium.jpg?psid=1

I even viewed the vid "Beginner's Guide - How to fix Helium backup" to update the Helium PC app's ADB server, but that didn't help either. I noticed though that the system apps (messaging storage and dictionary) could actually be backed up and out of the rest of the apps, literally only one could be backed up... which is a Simulation app at that.

So then I noticed one of the reviews suggest a further fix on how to get the app to work (image file):

https://xkijqw.dm.files.1drv.com/y4pZiw6XX-_U-tfEA_L3N7UjgTGcMwvbi1v_qj4F1xZt5Q3Jc4YGWwm1n0UqWG-oeUHuqQCJ6jvjLFEAM59-bEFSVVwjoRf1EN3b7PD_yIQT7Fkh-hcM8azdK6U6UEv36gz1rVjFaJHL9fbbA7rq8BdLa3SL7ndGek_lOAF8gnWCY-tSiVun7NZsIqWwmw7Nt_tDidXYHex0KiH6Yc3Iywc8rFLsbl9WUkRBLj_b60gE3k/Screenshot_20210213-202513_Google+Play+Store.jpg?psid=1

The thing they mentioned was to copy the "carbon" folder from phone to sdcard and then insert the sdcard in the new phone and continue restoration from there. The "carbon" folder is in my phone's internal storage atm, obviously empty.. also i don't think i have an external sdcard right now...

What should I do?

I would email the developers of the game. See what they can suggest.

 

[PhiNu]

I would email the developers of the game. See what they can suggest.

ATM they are actually implementing the cloud save feature for the next update, but it wouldn't be here until early March, I think they can only suggest to wait... I did ask some people who manage the game's community, and they helped, but without much success. (as mentioned originally, I could only create a backup, not properly restore it)
And anyway, my phone will be exchanged tomorrow, hence I am inquiring for quick backup solutions...

 

[mikedt]

ATM they are actually implementing the cloud save feature for the next update, but it wouldn't be here until early March, I think they can only suggest to wait... I did ask some people who manage the game's community, and they helped, but without much success. (as mentioned originally, I could only create a backup, not properly restore it)
And anyway, my phone will be exchanged tomorrow, hence I am inquiring for quick backup solutions...

OK, I've never done phone exchanges myself, and have still had the previous device around, and so had plenty of time to transfer my stuff to my new phone.

 

[PhiNu]

I assume that the game doesn't provide an option to export/back up your game data.

You could see whether the Helium backup app can manage this. Most backup apps can't actually back up app data unless the device is rooted, but Helium (which uses the ADB backup mechanism) worked well for me a few years ago for transferring data when Google's own phone setup app failed totally on my new (at the time) Pixel. However you should know that it doesn't work for all apps (I believe that there is something the developer has to allow, which most do), so I can't guarantee success.

It's not certain that your saved games are stored in the .obb file. It's quite possible that that is game data (graphics, levels, whatever) and that your play record is in the app's "private" data. But that's what the above app (and the ADB backup) will attempt to back up, so it's worth a shot.

This is one area where Android has always lagged a bit, I'm afraid.

Ok... so I managed to get an SDCard from my parents, it's a bit old but still recognizable by my device. After copying the "carbon" folder in it, the Helium app could recognize it too, but trying to backup gives the same error as before...

 

[Hadron]

Yeah, unfortunately I didn't think that a removable SD card would help (couldn't really see why it would - I suspect it was just that the person who wrote that used one). I last used Helium in 2017 (and neither device had a removable card), and it sounds like it may not have been maintained/updated sufficiently in the interim (checks: there have been 2 android releases since last update, which isn't a recipe for success with something like this).

(I've not looked at the images because it asks for a OneDrive login, and I'm not a Microsoft user. But I have a suspicion it wouldn't be something we could do much about).

 

[mikedt]

Hello!
Thank you for replying!
I actually did get the Helium app prior and noticed some negative ratings on the app too, basically summarizing that a lot of it's features don't work like they used. And as such, when I was backing up my Phigros game data, it showed me the typical error.



(image file): https://w6iqqw.dm.files.1drv.com/y4.../Screenshot_20210213-201743_Helium.jpg?psid=1

FYI that site requires a Microsoft login. Which I don't have.

If you got images you want to show, the best way is to attach them to your post.

 

[PhiNu]

Yeah, unfortunately I didn't think that a removable SD card would help (couldn't really see why it would - I suspect it was just that the person who wrote that used one). I last used Helium in 2017 (and neither device had a removable card), and it sounds like it may not have been maintained/updated sufficiently in the interim (checks: there have been 2 android releases since last update, which isn't a recipe for success with something like this).

(I've not looked at the images because it asks for a OneDrive login, and I'm not a Microsoft user. But I have a suspicion it wouldn't be something we could do much about).

oh well, at this point I'm just trying any method that has worked for others... do you have some other suggestion..?

 

[PhiNu]

FYI that site requires a Microsoft login. Which I don't have.

If you got images you want to show, the best way is to attach them to your post.

Noted.
Here are the images, just in case.
(I actually just figured out how to put images in the post itself )

 

[Hadron]

oh well, at this point I'm just trying any method that has worked for others... do you have some other suggestion..?

Sadly, not. If you were rooted, yes, but I don't know whether you can root that device, even less whether you can root without resetting it in the process (which would defeat the purpose of doing it), and if you are exchanging the device it would not be fair to root it in the meanwhile (certainly not without the informed consent of the other party).

 

[PhiNu]

Sadly, not. If you were rooted, yes, but I don't know whether you can root that device, even less whether you can root without resetting it in the process (which would defeat the purpose of doing it), and if you are exchanging the device it would not be fair to root it in the meanwhile (certainly not without the informed consent of the other party).

Rooting was the last thing I was going for too. I heard it gives full control to your device and full access to private data but is quite risky, you'll likely lose the warranty of your phone and one misstep can lead the phone turning into a "brick".
Oh well... um...

 

[Hadron]

Rooting was the last thing I was going for too. I heard it gives full control to your device and full access to private data but is quite risky, you'll likely lose the warranty of your phone and one misstep can lead the phone turning into a "brick".
Oh well... um...

It's also not something to do without making sure you understand the process - which is always to some extent specific to the model of phone.
And because it usually affects warranty status (and on some phones, particularly Samsung, there may be no way of undoing it that removes evidence that it had been done, which may itself be enough to refuse warranty support), and also because some apps won't work on rooted phones (many media apps, almost all banking or mobile payment apps), it's really not fair to do it to a phone that you are about to pass on (in some cases there are workarounds for this, but that's more stuff to learn in very little time).

Basically I would not recommend this at this point unless you already know what you are doing and how to undo it (which for root itself means "reflash the phone with a new set of official firmware") and unless the recipient is happy with you doing that (because you probably can't do anything about the warranty status - even reflashing to stock won't fix that). And, as noted, for many devices the process of rooting will involve a factory reset of the phone, which will destroy the data you are trying to save (and no, you won't be able to recover them, for several reasons), and for some devices, especially many US Samsung models, there just isn't a way of doing it. So overall I don't think that root is a reasonable solution at this point, I only mentioned it because it would be the only remaining way I know.