C++ Asgards Wrath 2 VR v5186 (God Mode, No Cooldown, Increased Loot)

  • Hello everyone, the site is currently under construction. Please wait while we are re-indexing our mods on to the ByteUs forum. Thank you.
sk4040 said:
yes @Frencisis I also have the latest v 71 firmware. This modded apk does not say compiling shaders like the rookie one says
Click to expand...
Yes same identical problem of your..
I launch the rookie games and it start, after splash screen, to compiling shaders and after start game.
If i use the modded one i start with splash screen and after few seconds close automatically and return to the oculus home 🤷🤷🤷
 
  • Like
Reactions: sk4040
Frencisis said:
Yes same identical problem of your..
I launch the rookie games and it start, after splash screen, to compiling shaders and after start game.
If i use the modded one i start with splash screen and after few seconds close automatically and return to the oculus home 🤷🤷🤷
Click to expand...
I also went to the app info i.e. using the file manager proogram in the quest and force stopped the game, cleared cache and data but still same issue. Can you try that in yours and let me know. I also created a second account and tried to run from there as some people mentioned the reddit. But still same issue man :(
 
I've tried; yes the same also for me..forced stopped the game, cleared cache.
Maybe the problem could be the languages that it have to load.. for me the headset is in Italian, not English.. I need this update also to play it with my native language
 
for me it is default English. I am going to try one thing I will do the obb trick and rename the apk to: com.Sanzaru.Wrath2 and install and see. I think the apk name is different so it maybe looking into the wrong obb since the rookie apk is named as: com.Sanzaru.Wrath2.apk but the modded one is named as: Wrath2_ByteUs.apk
 
  • Like
Reactions: Frencisis
tried to mod the save using save editor but now the issue is the save is unable to be restored using adb restore. @ISOHaven did you have any luck on restoring the save? I saw your comments in one of the reddit posts
 
sk4040 said:
tried to mod the save using save editor but now the issue is the save is unable to be restored using adb restore. @ISOHaven did you have any luck on restoring the save? I saw your comments in one of the reddit posts
Click to expand...
the adb backup works fine but restore does nothing. I guess to restore you need root access lol :)
 
With backup and restore I noticed that a restore would not work if coming from retail and going to mod or come from mod and going to retail (which I needed to try to fix my broken save). Backup and restore worked fine from retail to retail and from mod to mod. So when I backed up from v8 mod I was able to restore to v10 mod. I had guessed at the time that backup and restore needed to be kept with the same signature APK but no one responded to that theory.

Out of curiosity what save editor are you referring to?

Oh wait....what backup and restore are you using? Rookie backup and restore it total crap. It only works when the save data is specifically stored in the data folder. AW2 is not stored there. Use this app instead:

ADB Backup

Find my comments on that thread for some helpful advice and warnings.
 
yes I used that ADB backup you linked above only. It prompts on the quest when trying to restore the edited save file .ab but does nothing. I check on the app info and no user data is present. I used this Save Editor
Basically I made a .tar file from the .ab file using the android backup processor and then extracted the .sav file and uploaded above. I saw the values that were in the game and increased them like health, xp, hacksilver etc. then I inserted them back and packed to .ab and then tried to restore nothing happened. Perhaps I need to run with adb logcat -v log.txt to see what the error is when I try again

What is the process you followed to restore the save using ADB backup tool? Do you mind explaining the steps. Not sure what you meant by: "I had guessed at the time that backup and restore needed to be kept with the same signature APK". I am also thinking the restore failed due to corrupt entries on the save editor or something changes like permission etc when you edit the save and put it back in the tar file and pack it back to .ab format like signature changes or permissions change etc
 
the error is related to invalid format within the .sav file. Apparently as per this thread: editing android backups like save files it is not straightforward and you should not use 7zip

Error message from adb loog
11-22 13:03:16.017 1282 7284 E BackupManagerService: Parse error in header: Illegal semantic path in
11-22 13:03:16.017 1282 7284 W BackupManagerService: io exception on restore socket read: Illegal semantic path in
Click to expand...
11-22 13:03:16.020 0 0 I binder : 7213:7213 ioctl 40046210 7fcd927584 returned -22
11-22 13:03:16.018 1282 7284 D BackupManagerService: Full restore pass complete.
 
With the backup tool you simply restore single app backup. Then it asks you which one. You pick the number you want to restore. Try restoring without altering the save.

APK signature. The modded APK, the Rookie APK and the retail APK will all have their own signature. I've never had any luck in backing up from one and restoring to another.

As I mentioned AW2 does not put save data in the data folder. It will always have nothing important in it.
 
yes @ISOHaven it worked without altering the save. I was hoping there was a way to alter the save like this one: edit sav. tried different tools like this one but it not working... since for me the mod apk does not work so was trying to alter the save and that is not working either. I guess I will have to pass on this one unless updates are made: thanks :)
 
just curios could you share your .ab save that you got from the ADB backup? I would like to see if other .ab files work without any modifications
 
You must log in or register to reply here.
Top Bottom