Hacking Can't use EZ Flash IV saves on VBA

[CraddaPoosta]

For some reason, I can't get the .sav files that get created on my microSD card using my EZ Flash IV cart to import properly to VBA.

I'm running into this issue with every game whose .sav file size is 8kb.

If I use EZ4Client 1.03 and force the save type to EEPROM 512kb, I get 32kb .sav files that sometimes properly get imported, depending on the ROM. But, I am certain that I can't just go through and repatch some 160+ ROMs to the exact same save type and have them to work properly.

Is there a universal method of getting .sav files created by the EZ Flash IV cart to work for VBA? Any assistance would be greatly appreciated.

 

[how_do_i_do_that]

If your using the sav file from a game on the EZ-IV, it is best to used the ROM off the EZ-IV as well in VBA. Then make sure your VBA save type on automatic.


Otherwise you can use the EEPROM converter from the gba backup tool here: http://filetrip.net/nds-downloads/applications/download-gba-backup-tool-0-21-f3228.html
You will need a 32bit version of windows XP to run the vb script.

 

[FAST6191]

How are you attempting to import them? Just renaming and putting them with the VBA saves or file -> import -> battery save.

What games have you tried? There are some games that get annoying, typically pokemon but there are others.

 

[CraddaPoosta]

Tons. The weird thing is, it worked before.

I am using EZ4Client 1.03 and the same 2GB microSD card as always.

MegaMan Battle Network 2, Final Fight One, Super Street Fighter II Turbo Revival; it's completely random. None of them are working properly. I had MegaMan Battle Network working correctly, and was able to import the .sav just fine.

Been using VBA for some 12 years now and never had a problem like this before. Got the Emulator settings under Save Type set to Automatic, but it won't import no matter what I do. It only imports 32kb .sav files. I don't want to have to repatch my entire collection if I can avoid it.

Seems like the simplest solution would be a converter, but none of the ones I have tried so far are working, including the one posted above.

 

[how_do_i_do_that]

That depends on how old your EZ-IV is, if you had it 4+ years the battery probably dead by now. That would be the only thing different if you had no problems before.

 

[CraddaPoosta]

Brand new. Just got it a week ago.

The EEPROM converter says it succeeded in converting the .sav, but it's still 8kb (MMBN2), and it does nothing when I try to import it. I've tried making sure the names were exactly the same. Same ROM. Same folder. Tried every single possible configuration and it refuses to import it properly.

 

[how_do_i_do_that]

It flips the bits so you can use it in VBA or real cart where the rom is unaltered and the save type is EEPROM.

I just checked the rom information in offline list and on advanscence and they both come back as the rom save type is SRAM v112. That would mean you have been patching the rom for nothing.

Info on ROM and save type:
http://www.advanscene.com/html/Releases/dbreleases.php?id=0458

 

[CraddaPoosta]

I DID patch MMBN2 with GBAATM. Would that make its saves incompatible with VBA?

The same issue happens with other ROMs, too. I am going to test a bunch of them in a row and report back if any of them at all actually work.

 

[how_do_i_do_that]

gbaatm patches the rom. It doesn't affect the save as far as I know, but messed up cheats can prevent you from saving can be possible.