Hacking save problem with Gateway 2.0b1

  • Thread starter Thread starter udo4ever
  • Start date Start date
  • Views Views 13,313
  • Replies Replies 72
  • Likes Likes 1
I had issues at start but not since, probably 25+ times fine in a row, using home close.. 4.4 PAL 3DSXL EmuNAND 6.3 and also via an SD with just launcher
 
Can anyone tell me what type memory is on the GW board?
Does it need keeping power on to maintain a save session?
 
it doesnt need power to maintain, I want to know if i only play 1 game, and dont home/close, power off instead, aslong as there isnt a save on sd for that game, (so it doesnt copy it back next load) your progress and save will be fine ??
 
So based on what I have read, it wont fix the random hangs if I update my emuNAND to the latest version, correct?
 
it doesnt need power to maintain, I want to know if i only play 1 game, and dont home/close, power off instead, aslong as there isnt a save on sd for that game, (so it doesnt copy it back next load) your progress and save will be fine ??

Thanks for your answer. So the original save isn't a file on the SD but in a stand-alone memory chip?
Your concern is also mine, if there is no sav file on the 3DS SD card, will the GW firm clear any save in the GW memory chip?

PS. If you press power then turn it off, it also create a sav file on your 3ds SD card, because power button terminate the game, terminating a game provoke the save-to-sd process.
 
So based on what I have read, it wont fix the random hangs if I update my emuNAND to the latest version, correct?

It still did for me, but not always.

Here is what to do, to make sure it will save:
- Start the game
- Once it's loaded in (like at the main menu), press home.
- Wait a few seconds (I always wait for the little feet icon in the top screen to turn to the different icon and then back to 2 feet).
- Close the game.

If this worked, restart the game and play... chances it doesn't work after working the first time are very slim (aka I have never had it happen yet).
If it didn't work, well.. you gotta hard reboot anyways... so do that and try again.
 
It still did for me, but not always.

Here is what to do, to make sure it will save:
- Start the game
- Once it's loaded in (like at the main menu), press home.
- Wait a few seconds (I always wait for the little feet icon in the top screen to turn to the different icon and then back to 2 feet).
- Close the game.

If this worked, restart the game and play... chances it doesn't work after working the first time are very slim (aka I have never had it happen yet).
If it didn't work, well.. you gotta hard reboot anyways... so do that and try again.


Ok, yeah that is what I have been doing, seems that if it works once than it will 99% work every time afterwards, it IS a hassle but worth not losing my save.
 
ive only had 1 problem with saving , what i have done now, is to save the game, press home and then load the activity log whilst still in the zelda game, this then tells you, that you will lose all unsaved data, if you go ahead, go ahead and do it, upto now its been 100% without fail.
 
I've been having the same issue with my games and I THINK I've come up with a weird solution. Whenever I try to quit a game I consistently get the freezing and the 10 second rule doesn't seem to work for me but; oddly, the following seems to work 100% reliably for me:

- Manually boot into GW mode (ie. hold down the L button while clicking on the 3DS profile and PICK GW mode yourself).

I've been testing it by repeatedly booting into a game and quitting immediately. After many resets I realized that by doing the above the game quits without a problem, without needing the 10 second wait. If I let GW automatically boot me into GW mode (without pressing L) then the 3DS would crash on me on game exit, even when waiting the 10 seconds, 100% of the time.

Note, however, that I can't confirm that this is a reliable solution since I only tested it by going in and out of a game (Shin Megami Tensei IV in my case) repeatedly. Altho, in my case, the results where 100% reliable. Too tell if this works during extended play will require further testing. Maybe it's "just" a bug present when GW boots up the Emunand automatically.
 

Site & Scene News

Popular threads in this forum