Hacking New Theme for EZ-Flash Omega!

  • Thread starter Thread starter Sterophonick
  • Start date Start date
  • Views Views 627,817
  • Replies Replies 1,502
  • Likes Likes 52
are you restarting the system after exiting the game? are you just copying the new kernel to your sdcard, or flashing the new kernel by holding R during power on of the system to flash the new kernel as well?
Sorry for the delay. Yep, I restart it, it gives me the prompt to save the data to SD, and it normally always works. I was fortunate that I had a save state backup for this particular game (Harvest Moon: FoMT), although I still lost about 4 hours of progress, give or take. One thing I noticed was that it's not even letting me save in-game anymore, so I'm guessing I'll need to delete the save file to do that again. For now, I'm relying entirely on the save state function built into EZ. For future reference, is there a way to repair a corrupt save?

As for whether I flashed the new firmware, I'm pretty sure I followed all the instructions when I installed it but it's been quite awhile. I mean, it shows the "Simple" logo with the version number, and all the options are present. Would it do that if it weren't flashed? I guess I could try getting the very latest version and doing it again, assuming I don't lose any data from it.

Thanks, by the way!
 
  • Like
Reactions: f3bandit
@LukewarmTea Classic NES Series used multiple tricks to fool flashcarts and emulators, and one of these was setting the wrong save type in the header. Most games used SRAM, but these cartridges actually used EEPROM, and if the game was able to successfully perform an SRAM write, it would know it's pirated. Try setting the save type to EEPROM and see if that works.

Source:
https://github.com/mgba-emu/mgba/commit/c52edab71a0f3465c508b554130fdccb4108a654

No real clue why specifically Classic NES Series used various accuracy checks like this (trust me, some of them do crazy things), especially since the first known working Famicom emulator was released in 1990, and NESticle was already a popular project by this time. None of this would have helped fight NES piracy in any way.
 
Last edited by Sterophonick,
  • Like
Reactions: f3bandit
endrift, in her 2014 article, explains that Classic NES/Famicom Mini titles use six different tricks. Since she was working on mGBA, probably most of them aren't an issue for flashcarts on original hardware (AGB, AGS, OXY, NTR, USG and DOL-017).
https://mgba.io/2014/12/28/classic-nes/

The implementation of fixes shouldn't be difficult according to other devs I've discussed with.
 
Hello i buy a ez-flash Omega and i want to know what firmware is the best today
-stock
-simple 3.45
-simple 3.7

I dont want save destruction error in GB/GBA and ability to play pokémon saphyr if its possible
 
I see lot of persons have some problems with save on simple 3.7 (no 3.45 ?) and i need saves not disappear every day
Post automatically merged:


I buy a non de ez flash omego
Just use the latest SimpleLight version. And if you still feel uncertain, enable the backup function, and wait 5 to 10 seconds every time you save the game and you are about to turn off the console, or just every time you're about to turn off the console.
 
  • Like
Reactions: f3bandit
I see lot of persons have some problems with save on simple 3.7 (no 3.45 ?) and i need saves not disappear every day
Post automatically merged:


I buy a non de ez flash omego

This is a flaw with the hardware of the original Omega that cannot be fixed. The workaround is to wait for a few seconds after the save behavior of your game before turning off the system. The backup feature is a crutch in case things go wrong.
 
This is a flaw with the hardware of the original Omega that cannot be fixed. The workaround is to wait for a few seconds after the save behavior of your game before turning off the system. The backup feature is a crutch in case things go wrong.
So why save disparition bug is reported on lasts firm versions and no before or on stock ?
Its not just a material problem or ?
Post automatically merged:

This is a flaw with the hardware of the original Omega that cannot be fixed. The workaround is to wait for a few seconds after the save behavior of your game before turning off the system. The backup feature is a crutch in case things go wrong.
So i receive
-i update stock last firm
- i flash last simple firm
- when i play GB/gbc game i save , and After few second i cut off the console
Ive good ?
 
So why save disparition bug is reported on lasts firm versions and no before or on stock ?
Its not just a material problem or ?
Post automatically merged:


So i receive
-i update stock last firm
- i flash last simple firm
- when i play GB/gbc game i save , and After few second i cut off the console
Ive good ?
1. It does happen on stock. EZ-Flash knew about the issue and couldn't do anything until the Definitive Edition because it's a problem with the logic programmed into the FPGA.
2. Yes, if you wait a few seconds after saving, you should be fine.
 

Attachments

  • 20240508_191530.png
    20240508_191530.png
    314.9 KB · Views: 85
  • ezkernelnew.zip
    ezkernelnew.zip
    477.1 KB · Views: 74
  • 20240508_191657.png
    20240508_191657.png
    314.9 KB · Views: 85
  • 20240508_191652.png
    20240508_191652.png
    314.9 KB · Views: 88
  • 20240508_191648.png
    20240508_191648.png
    314.9 KB · Views: 79
  • 20240508_191621.png
    20240508_191621.png
    314.9 KB · Views: 83
  • 20240508_191549.png
    20240508_191549.png
    314.9 KB · Views: 76
  • 20240508_191543.png
    20240508_191543.png
    314.9 KB · Views: 72
  • 20240508_191530.png
    20240508_191530.png
    314.9 KB · Views: 91
  • 20240508_191506.png
    20240508_191506.png
    314.9 KB · Views: 80
  • 20240508_191434.png
    20240508_191434.png
    314.9 KB · Views: 64
  • 20240508_191427.png
    20240508_191427.png
    314.9 KB · Views: 78
  • 20240508_191424.png
    20240508_191424.png
    314.9 KB · Views: 95
gba nes classic roms work now with the patch from @TechieSaru
you have to set the save type to sram, and they work just fine.
NO. Do NOT do this. They are set to be detected as eeprom and then automatically re-adjusted to sram for the sake of outputting the correct file size. Just use the auto-detect for save type and they'll work fine.
 
  • Like
Reactions: hippy dave
NO. Do NOT do this. They are set to be detected as eeprom and then automatically re-adjusted to sram for the sake of outputting the correct file size. Just use the auto-detect for save type and they'll work fine.
ok nvm it works that way lol I was wrong
 
So I'm trying to make a custom theme for this but I keep hitting this error. I just installed DevkitPro and I don't know what would cause this to happen. Any ideas?

1715965226948.png
 

Site & Scene News

Popular threads in this forum