- 566
- Posts
- 5
- Years
- Seen Apr 29, 2025
Normally, I can continue progress. But this rom specifically erased my save when I updated a few months ago. Same rom name and all. I had a backup fortunately.
I appreciate all the help you've given me regardless.
I think this is an issue with your K101 doing some kind of hash check. I'll see if I can bypass it.
I'm using a few different tools:
- There's goombasav (I use GoombasavCore.WinForms.x64.exe).
- Also the Revo save converter.
- Goomba color.
- And finally the good ol' VBA emulator.
- As before, I use goombasav to extract a raw gbc sav from your k101 sav.
- I use goomba color to compile the updated gbc rom into a gba rom.
- I open VBA, check my save type settings (automatic & 64k flash), and load the goombafied rom. I start a new game and then save the game after it drops me into the player's room. This generates a dummy VBA sav.
- I use goombasav again to load the VBA dummy sav. This time I use the raw gbc sav from before to replace the saved data in the dummy sav.
- I take the modified dummy sav and use it to fire up VBA with the goombafied rom. The saved game is detected and loads with invisible walls. Softlock teleport clears the invisible walls. Game is saved again. So far so good.
- I go into the gooba options (L + R) and go into and out of the save manager. This is just so that goomba updates its own save structure. This results in a cleaned VBA sav for the goombafied rom.
- Finally I use the Revo save converter to convert the cleaned VBA sav into a K101 sav. See attached.
So the file I ended up with is the same size as the file you initially posted. That's a good sign. But what a task it is to cut through not one but two special save structures. 136KB K101 save --> 32KB raw gbc save --> 64KB goomba GBA save --> 136 KB K101 save.
EDIT: You might want to replicate this process using your own compiled rom update just to make sure everything is consistent between the rom and the sav.
Attachments
Last edited: