EZ FLASH OMEGA SAVE PROBLEM

[Mancore]

Is this issue only with the Zelda game? Are other games working fine?

Please check the ROM's hash results compare known online dat.

Or have you manually set the save type in the ROM's launching menu before?

This happens in all games. Tested goodboy galaxy, spyro, zelda. The roms themselves were clean. Once the problem went away, I was able to create a save in Zelda and the progress was saved in Spyro, but then everything disappeared again, and Zelda started showing an error.

I will add that I changed the type of memory for saving from Auto to SRAM. The problem still persists.

 

[EZ-Flash2]

This happens in all games. Tested goodboy galaxy, spyro, zelda. The roms themselves were clean. Once the problem went away, I was able to create a save in Zelda and the progress was saved in Spyro, but then everything disappeared again, and Zelda started showing an error.

I will add that I changed the type of memory for saving from Auto to SRAM. The problem still persists.

What kernel are you using?

I once saw an OMEGA user who had a similar situation as you, where none of the games could be saved. It was ultimately discovered that he had modified the filename of OMEGA DE kernel, forcing it to be flashed onto OMEGA, and the problem was resolved after he switched back to the original OMEGA kernel.

It's easy to distinguish between kernel versions: the OMEGA kernel has 4 TABs, while the OMEGA DE kernel has 5 TABs.

 

[Mancore]

What kernel are you using?

I once saw an OMEGA user who had a similar situation as you, where none of the games could be saved. It was ultimately discovered that he had modified the filename of OMEGA DE kernel, forcing it to be flashed onto OMEGA, and the problem was resolved after he switched back to the original OMEGA kernel.

It's easy to distinguish between kernel versions: the OMEGA kernel has 4 TABs, while the OMEGA DE kernel has 5 TABs.

After the purchase, the SimpleLight kernel with firmware 9 was installed, then it was downloaded from the official website and installed also with firmware 9. I understand that the files are different. The question is, why did the device allow everything to be written once, and then similar errors appeared? Could this be related to the hardware, not the software? And if it is the software, then how can the device be restored?

 

[EZ-Flash2]

After the purchase, the SimpleLight kernel with firmware 9 was installed, then it was downloaded from the official website and installed also with firmware 9. I understand that the files are different. The question is, why did the device allow everything to be written once, and then similar errors appeared? Could this be related to the hardware, not the software? And if it is the software, then how can the device be restored?

There is another possibility.

If you have ever manually changed the game's save method from AUTO to something else, it might result in the sav files created under the SAVER directory being too small. Even if you change the save mode back to AUTO afterwards, the saving may not work properly.

So, you can delete all files in the SAVER directory and let the game start with the AUTO save method.

 

[Mancore]

Есть и другая возможность.

Если вы когда-либо вручную меняли метод сохранения игры с AUTO на что-то другое, это могло привести к тому, что файлы sav, созданные в каталоге SAVER, были слишком маленькими. Даже если вы потом снова измените режим сохранения на AUTO, сохранение может работать некорректно.

Таким образом, вы можете удалить все файлы в каталоге SAVER и запустить игру с методом сохранения AUTO.

Проблема изначально возникла, когда тип сохранения был АВТО.
Затем было отправлено письмо продавцу о том, что появляются ошибки. В этот момент все заработало (это была уже официальная прошивка последней версии) и сохранения появились. Но через несколько часов проблема появилась снова. Продавец посоветовал сменить тип сохранения с AUTO на SRAM, но проблема не ушла.

 

[EZ-Flash2]

Проблема изначально возникла, когда тип сохранения был АВТО.
Затем было отправлено письмо продавцу о том, что появляются ошибки. В этот момент все заработало (это была уже официальная прошивка последней версии) и сохранения появились. Но через несколько часов проблема появилась снова. Продавец посоветовал сменить тип сохранения с AUTO на SRAM, но проблема не ушла.

If your ROM is a Clean ROM, you don't need to set the save type, as AUTO can match any ROM.

However, if you are using a modified localized ROM, it might have been patched for save functionality, in which case you will need to change the save mode to SRAM.

In such a scenario, if there is already a previously created file in your SAVER directory that has a different size from what SRAM creates, it could lead to save failure.

Let me give you a specific example. Say you're playing a game with an EEPROM of 128Kb. According to our kernel's identification, the first time you run the game, a 16KB .sav file is created in the SAVER directory. But if this game has been patched with an SRAM patch, where an SRAM save is 256Kb, i.e., 32KB, then the 16KB .sav file won't be able to contain 32KB of data, leading to a save failure.

Therefore, my recommendation is:

First, confirm whether your ROM is CLEAN or a modified localized version.

Then, delete all files in the SAVER directory and select either AUTO or SRAM according to your ROM's type before starting the game.

 

[Mancore]

If your ROM is a Clean ROM, you don't need to set the save type, as AUTO can match any ROM.

However, if you are using a modified localized ROM, it might have been patched for save functionality, in which case you will need to change the save mode to SRAM.

In such a scenario, if there is already a previously created file in your SAVER directory that has a different size from what SRAM creates, it could lead to save failure.

Let me give you a specific example. Say you're playing a game with an EEPROM of 128Kb. According to our kernel's identification, the first time you run the game, a 16KB .sav file is created in the SAVER directory. But if this game has been patched with an SRAM patch, where an SRAM save is 256Kb, i.e., 32KB, then the 16KB .sav file won't be able to contain 32KB of data, leading to a save failure.

Therefore, my recommendation is:

First, confirm whether your ROM is CLEAN or a modified localized version.

Then, delete all files in the SAVER directory and select either AUTO or SRAM according to your ROM's type before starting the game.

Thanks for the advice.
Today I will try to restore the cartridge according to the instructions and check everything on clean ROMs

Post automatically merged: Today at 5:53 PM

If your ROM is a Clean ROM, you don't need to set the save type, as AUTO can match any ROM.

However, if you are using a modified localized ROM, it might have been patched for save functionality, in which case you will need to change the save mode to SRAM.

In such a scenario, if there is already a previously created file in your SAVER directory that has a different size from what SRAM creates, it could lead to save failure.

Let me give you a specific example. Say you're playing a game with an EEPROM of 128Kb. According to our kernel's identification, the first time you run the game, a 16KB .sav file is created in the SAVER directory. But if this game has been patched with an SRAM patch, where an SRAM save is 256Kb, i.e., 32KB, then the 16KB .sav file won't be able to contain 32KB of data, leading to a save failure.

Therefore, my recommendation is:

First, confirm whether your ROM is CLEAN or a modified localized version.

Then, delete all files in the SAVER directory and select either AUTO or SRAM according to your ROM's type before starting the game.

I restored the bootloader according to the instructions https://www.ezflash.cn/zip/recovery-en.pdf but it did not give any result. The error still appears, the ROM that I launch works correctly on EZODE and is not modified.