Ez Flash Omega DE - some solution for some games not saving - EEPROM (0.5KB, 8KB)

[Semro695]

So...

These are the links I checked (the relevant):

Learn about save type: https://www.neogaf.com/threads/the-great-console-save-type-and-save-memory-size-list.336369/

• Resume for gba:
• On-Cart: SRAM (CR2016) (32KB), EEPROM (0.5KB, 8KB), Flash RAM (64KB, 128KB), FRAM (32KB) (Type depends on game)
• Go check in your SD, in /SAVER/ check the .sav of the game that is not saving correctly in the Ez flash, if that .sav is 0.5kb (might look like 1kb) or 8kb, keep reading

What's the deal with gba saves: https://zork.net/~st/jottings/GBA_saves.html

Now...

I realized that my games could load the save files I manually copied to the SAVER folder. But then, when saving the game while using the console, the previously saved game was replaced with a blank one (the progress was lost).

After a little over a day of investigating, I realized that the .sav files I couldn't save while using the console were those smaller than 32kb. Those are "save type: EEPROM". The trick here is to patch the ROM (the game, not the sav) so it saves in SRAM, not EEPROM.

I found a program called GBATA. This program first tells you what type of save the ROM uses... there you confirm it's EEPROM. It actually has many other uses... IPS patcher, clock fix, a lot. The important thing is to use the SRAM patch function, patch the ROM, and then put it on your SD card. I think you need to delete the previous .sav file; it must be without the game's .sav file. Now we start the game in the Ez flash ODE, making sure to set the save type to SRAM (you only need to do this once, it will stay that way for that game). Now I can smash the save option when asked for saving the .sav.

If this doesn't help then first check if the problema is your Ez Flash hardware. Using the safe mode of the Ez flash ODE lets you test. Then check the battery... well that info is everywhere.

 

[Wokann]

1. When manually loading a .sav file for game A from another source, do not select "OK" to save the game's save file during startup. This is because it will overwrite the save file of game A stored in the FRAM chip with the save file on the SD card.
Alternatively, before manually replacing the save file for game A by removing the SD card, run game B. This will overwrite the save file with game B's save file during startup, not the save file for game A.

2. In auto-save mode, EZODE uses the save file type of the official game stored in its lib. As long as you are playing with the official original ROM, there will be no problem.
Considering that your save file issue is related to EEPROM saves, another possibility is that the EEPROM game ROM size exceeds the capacity limit. This is common in various EEPROM game hacks or fans localizations, causing the ROM size to exceed 16MB. You can check if this applies to you.