Hardware EZ Flash Omega Berry Glitch fix

[DolphinCube]

I may be a moron for posting this while two million people posted the same thing. But how do you fix the berry glitch on the EZ-Flash Omega? Is there a cheat code I could use (like that one gameshark cheat). Any help would be appreciated

 

[Localhorst86]

I may be a moron for posting this while two million people posted the same thing. But how do you fix the berry glitch on the EZ-Flash Omega? Is there a cheat code I could use (like that one gameshark cheat). Any help would be appreciated

I assume you mean the berry glitch where berries would stop growing the entire second year of playing the game, right?
From what I can gather, the issue is related to the RTC of the game being reset to "day 0" when the first year passes, but it apparently misses to add the first year to the counter. After year two, the glitch will fix itself, because it will then add a year to the counter.
(basing my research off of this: https://bulbapedia.bulbagarden.net/wiki/Berry_glitch, https://web.archive.org/web/2018041...page=Pokemon_Ruby/Sapphire_New_Battery_Glitch)

Now, I am unsure of how running the game the EZ-Flash Omega is affected by this, how exactly the game interacts with the clock on the flashcard and how the year you set your omegas RTC clock to gets taken into consideration. My guess is, that if you encounter the glitch, setting the internal clock of the omega forward by one year should fix the issue. But the glitch might not even trigg

Alternatively, you could use the method described in the archive.org link i posted above to alter the "last saved" offset.

However, even simpler should be using a version of the ROM that has this conversion error fixed, I assume this would be fixed on rev2 of the english release of the game, possibly even rev1. Better go for revision 2 of the game to be sure. Here's information about the releases (checksums) that potentially have the issue fixed.
Ruby:
https://datomatic.no-intro.org/index.php?page=show_record&s=23&n=1223
https://datomatic.no-intro.org/index.php?page=show_record&s=23&n=1981

Sapphire:
https://datomatic.no-intro.org/index.php?page=show_record&s=23&n=1218
https://datomatic.no-intro.org/index.php?page=show_record&s=23&n=1986

If you're using a language specific variants of the game (french, german or spanish), there is no rev2, since the initial release of the titles was after the english release, I assume the initial release of those titles is equal to the english rev1 release, and their rev1 release contains fixes included in the english rev2.

 

[DolphinCube]

Will it keep my save file tho. That is the real question

EDIT. I meant by getting the revision 2. I found out that I have the revision 1

 

[Localhorst86]

Will it keep my save file tho. That is the real question

EDIT. I meant by getting the revision 2. I found out that I have the revision 1

you could try, creating backups first.

 

[DolphinCube]

Update: I started a game of pokemon emerald which I KNOW has no berry glitch. Started working for a while then decided to screw me up. So I think it is with the EZ Flash omega itself. BTW I replaced the battery and it still didnt work. D:<

 

[Ryccardo]

From what I can gather, the issue is related to the RTC of the game being reset to "day 0" when the first year passes, but it apparently misses to add the first year to the counter. After year two, the glitch will fix itself, because it will then add a year to the counter.

The hardware clock is a standard part for computers (year/month/day/hour/minutes/seconds, unlike the MBC3's number of days/hours/minutes/seconds), so there's logic in the game to convert a date from and to "total days since the start of 2000", but since these are provably incompetent programmers (who can't even do long addition, resulting in the so-called ZZAZZ glitch) they got the loops wrong: 2000 is year 0, 2001 is year 0, 2002 is year 1... etc

The official "fix" (included in FR/LG/E and many GC pokemon discs) simply advances the clock as needed to solve or prevent the problem... not to be confused with the problem caused by replacing the battery without starting a new game is in any version (unlike in G/S/C the clock can't easily be manually set, so if the game was last saved on day 231 you would need to wait 231 days for it to start working again without access to a save or rtc editor)

As for game versions, only English 1.2 has the proper fix - 1.1 is a lot of minor stuff - and yep, subtract 0,1 for the equivalent in other languages