Flashed the new Firmware - Shows correct Version - SAVESTATE is still only usable with the "L+R + Start -> Menu opens" resulting in same issues as before. Therefore didnt even trying out Fire Emblem ;-)
--------------------- MERGED ---------------------------
--------------------- MERGED ---------------------------
1. GBA SP AGS-101
2. FW6 K1.04
3. Kernel version
4. SanDisk 16GB Class 10
5. Fat 32
6. 32kb
7. Classic NES titles released for GBA like Super Mario Bros. and The Legend of Zelda have their controls broken, the character stutters and button presses are not properly recognized.
8. Bug reproduce steps: Start up one of the games.
2. FW6 K1.04
3. Kernel version
4. SanDisk 16GB Class 10
5. Fat 32
6. 32kb
7. Classic NES titles released for GBA like Super Mario Bros. and The Legend of Zelda have their controls broken, the character stutters and button presses are not properly recognized.
8. Bug reproduce steps: Start up one of the games.
1. Original GBA/NDS Lite
2. 6.0
3. 1.04
4. Patriot 8GB
5. FAT32
6. 32kb
7. Pokemon games do not save when trying to save in game, from new game or imported save file
8. Start up game, start new game and save as soon as possible. Get window that says "Save failed checking backup memory"
2. 6.0
3. 1.04
4. Patriot 8GB
5. FAT32
6. 32kb
7. Pokemon games do not save when trying to save in game, from new game or imported save file
8. Start up game, start new game and save as soon as possible. Get window that says "Save failed checking backup memory"
A suggestion for the future? Require in bug reports that they include one of a md5/sha1/sha256/crc32 hash for any game mentioned. Not only will that help narrow down the version/region but also remove any concerns about patched roms.
Yeah I figured out my problem, all the tutorials I followed said I need to use the EZ4 Patcher to put the game files on the SD card. Just read one where it says I don't and that worked when I saved.
care to link said tutorial? I'd like to beat the creator of that tuorial with a baseball bat wrapped in barbed wire.
btw: if you used EZ4patcher with a ROM, you no longer have a checksum of E26EE0D44E809351C8CE2D73C7400CDD. Any modification to the file will also alter the checksum of it. That's why the real checksum of a file can help identify tampered ROMs.
Last edited by Localhorst86,
care to link said tutorial? I'd like to beat the creator of that tuorial with a baseball bat wrapped in barbed wire.
btw: if you used EZ4patcher with a ROM, you no longer have a checksum of E26EE0D44E809351C8CE2D73C7400CDD. Any modification to the file will also alter the checksum of it. That's why the real checksum of a file can help identify tampered ROMs.
Its also definitely on me as well, I didn't do as much research as needed. I get that I'm an idiot for using the wrong program but I learned my lesson.
You have to IPS patch those specific gba files to work on any flash card. It's not a problem with EZ FLASH Omega
THis is, simply, not true. The clean ROM from the No-Intro set runs fine on the EZFlash Omega. The cartridge applies AP patches on the fly.
Your right, just tried a few no-intro versions and they worked fine. I was trying what I thought were the clean versions, from the full ROM set downloaded from emuparadise.
It appears that all the no-intro NES Classic ROMS are all overdumps, and the [f1] ROMS have been fixed.
Last edited by GBAer,
Similar threads
