Hacking save problem with Gateway 2.0b1

  • Thread starter Thread starter udo4ever
  • Start date Start date
  • Views Views 13,309
  • Replies Replies 72
  • Likes Likes 1
It seems totally random, i can exit fine now everytime, and tested the 3 methods, via a EmuNAND (updated and still at base) and via an SD with just the launcher, the hang is when it saving back to the SD card on exiting, to be honest when i first was getting hangs i never actually went to the bird and saved, so i take it the hang was related to no save present, I never use GUI to enter GW Mode, only when i backed up and preped EmuNAND, the game itself is saving fine internally, if its the only game you are playing you should just be able to power down if you wish and the save will still be there, however if you have a save on the sd for the game that is older than your current internal save, may roll you back when you load... People where guessing the whole KeyY thing is the cause thats why it runs fine in EmuNAND etc etc, this isnt the case as whether SystemNAND or EmuNAND (updated or Not) GW mode does not use any of the flags in 6.x firmware, its all 4.x based, so it seems even though games have flags for new Crypto, it falls back to old KeyY method anyway, since it doesnt know about the new flags, basically we are tricking the system to think its running 6.3 in an updated EmuNAND although its really still running the original base FW wise, as we are always booting into original FW to begin with and still in that when redirected
 
Although I don't have a chance to test, I saw a solution on a Chinese forum:
After saving in the game, do NOT press home button, just press the power button once and wait a few seconds.
Lot of people in that forum approve this method.

The Copy-to-SD process happens on closing of a game, the power button did that too and with a much simpler circumstance, not like home button, it doesn't need to load some heavy stuff, just a simple message screen.

I think the simplicity increases the possibility of copy process. It makes sense.

FYI.
 
Although I don't have a chance to test, I saw a solution on a Chinese forum:
After saving in the game, do NOT press home button, just press the power button once and wait a few seconds.
Lot of people in that forum approve this method.

The Copy-to-SD process happens on closing of a game, the power button did that too and with a much simpler circumstance, not like home button, it doesn't need to load some heavy stuff, just a simple message screen.

I think the simplicity increases the possibility of copy process. It makes sense.

FYI.

Thanks for this great tips, it works for me..... I had problems before with saving in Zelda but not anymore.... :bow:
 
Although I don't have a chance to test, I saw a solution on a Chinese forum:
After saving in the game, do NOT press home button, just press the power button once and wait a few seconds.
Lot of people in that forum approve this method.

The Copy-to-SD process happens on closing of a game, the power button did that too and with a much simpler circumstance, not like home button, it doesn't need to load some heavy stuff, just a simple message screen.

I think the simplicity increases the possibility of copy process. It makes sense.

FYI.
Just tested this. It CAN crash
On the screen where it offers you to power off or home (after pressing the home button) sometime it WONT let you return to home and therefore it doesn't save. I checked the file afterwards and it DIDNT save
 
Just tested this. It CAN crash
On the screen where it offers you to power off or home (after pressing the home button) sometime it WONT let you return to home and therefore it doesn't save. I checked the file afterwards and it DIDNT save
So, what if you just power off?
Even then how about the frequency of crash?
 
So, what if you just power off?
Even then how about the frequency of crash?
Testing it right now. So far it has crashed 1/10 times. I might try a bunch of different methods

I thought of a possible theorem for the crashing:
If the emunand is booted 100% correctly it will always save correctly
If the emunand is not booted 100% correctly (for whatever reason) it will crash when returning to the home menu.

how to check if the emunand is loaded 100% correctly:
When loading the save you could collect 1 rupee (gem) then save close and relaunch the game (If it crashses emunand not booted correctly)
If it doesn't crash emunand booted correctly (so relaunch the game and continue playing :D )

Summary
All tests were done using the power off method
Methods:
Reboot emunand: Power off/on 3ds and start gateway normally
Checked emunand: Checked the emunand using the method above
Justins test 1: Save in game like normal then press the home button NOT EXITING OUT OF THE GAME wait 10 seconds then power off.
Justins test 2: Save in game like normal then press the home repetitively and then exit out of the game
Justins test 3: Press home and close as fast as possible

1. Rebooted emunand. Failed
2. Rebooted emunand succeed
3. Checked emunand succeed
4. Checked emunand succeed
5. Checked emunand succeed
6. Checked emunand succeed
7. Checked emunand succeed
8. Checked emunand succeed
9. Checked emunand succeed
10. Checked emunand succeed
11. ReBooted emunand succeed
12. ReBooted emunand succeed
13. ReBooted emunand succeed
14. ReBooted emunand succeed
15. ReBooted emunand succeed
16. Checked emunand succeed
17. Checked emunand succeed
18. Checked emunand succeed
19. Rebooted emunand succeed
20. Rebooted emunand holding "L" save succeed
21. Rebooted emunand save succeed
22. Justins test 1: save succeeded (Suprised me even)
23. Justins test 2: Failed
24. Justins test 2: succeed
25. Justins test 2: succeed
26. Justins test 2: succeed
27. Justins test 1: Failed (I know I waited long enough)
28. Justins test 1: succeed
29. Justins test 3: succeed
30. Rebooted emunand succeed
31. Checked emunand succeed
To Summarise:
Reboot emunand: Succeded 10/11 times
Checked emunand: Succeded 12/12 times
Justins test 1: Succeded 2/3 times (I think it would be 90%)
Justins test 2: Succeded 3/4 times
Justins test 3: Succeded 1/1 times


Edit 1: Started testing
Edit 2: Added a theorem
Edit 3: Posted results
Edit 4: Results are inconclusive
Edit 5: Added more results (still inconclusive) restructured post slightly
Edit 6: I read justins method I might have to try that tomorrow
Edit 7: 23. Might be an important discovery
Edit 8: Most likely a coincidence
Edit 9: Organized the summary because it was getting messy
Edit 10: Added a summary

More testing will need to be done
 
Testing it right now. So far it has crashed 1/10 times. I might try a bunch of different methods

Edit: I am updating this reasonably LIVE (This edit will change when I am done)

Edit 2: I thought of a possible theorem for the crashing (More testing will need to be done)
If the emunand is booted 100% correctly it will always save correctly
If the emunand is not booted 100% correctly (for whatever reason) it will crash when returning to the home menu. In this 1/10 times. I crashed on attempt 1 and have NOT crashed on attempts 2-10. If this theorem is correct when you load your save file. You should save to check that the emunand is booted 100% correctly and then you should (in theory) save correctly 100% of the time

Edit 3: To continue testing this theorem on attempts 11 - 15 I will restart my 3ds

Edit 3-2: Summary
All tests were done using the power off method
1. Booted emunand. save FAILED
2. Booted emunand save succeed
3. save succeed
4. save succeed
5. save succeed
6. save succeed
7. save succeed
8. save succeed
9. save succeed
10. save succeed
11. Booted emunand save succeed
12. Booted emunand save succeed
13. Booted emunand save succeed
14.
15.

More testing will need to be done

Thanks for your test.
Let's make it clear are you powerring off directly or returning to home on the power off screen?

Besides, how could you know if the emunand booted 100%?
 
Thanks for your test.
Let's make it clear are you powerring off directly or returning to home on the power off screen?

Besides, how could you know if the emunand booted 100%?

1. for tests 1-10 I was pressing the power button then pressing the home button
- for tests 11-15 I turned the 3ds off and on launched and launched gateway mode

2. When loading the save you could collect 1 rupee (gem) then save close and relaunch the game (If it crashses emunand not booted correctly)
If it doesn't crash emunand booted correctly (so relaunch the game and continue playing :D )
 
I'll repeat what I said earlier: after saving at a weather vane, press home, wait ten seconds for it to save to sdcard, you're done. Works every time, won't hang if you just wait a while. Not pressing the home button but just powering off is just waiting for trouble (especially when switching between games)
 
I'll repeat what I said earlier: after saving at a weather vane, press home, wait ten seconds for it to save to sdcard, you're done. Works every time, won't hang if you just wait a while. Not pressing the home button but just powering off is just waiting for trouble (especially when switching between games)
Thanks for the info, could you explain why there would be troubles?
 
Gateway 's red card temporarily stores the save info on the fpga in some way. They programmed a hook that transfers this info from the red card to your Nintendo 3ds's sdcard as a sav file. The hook is activated by suspension of the running app presumably, so when you press home. Now, it needs some time to do this writing, but if you interrupt this process by exiting the app (game) entirely, there is probably some kind of deadlock occurring due to concurrent data access.

Note that this is all conjecture, but I'd say they are fairly educated guesses.
 
Let me say again I'm not totally sure this is an accurate account of the issue, but since doing this I've not have any save issues. Please do try it, hopefully we can get confirmation or refutation on whether "always just waiting a few seconds after pressing home" indeed is the solution.
 
This whole topic is interesting. Im trying to get my saving to fail now to try reach a conclusion but its not failing at all. Before testing I had a reasonable fail rate. I will keep testing this.
 
In my 23rd test see a few posts above
Justins method test 2: Save in game like normal then press the home button repetitively then click home. SAVE FAILED


Edit: This is inconclusive tests 24 25 and 26 save succeeded
 
well if it takes some extra time to save on exit, why wouldn't take more time when you save in game to, maybe save and wait a min?
 

Site & Scene News

Popular threads in this forum