http://gbatemp.net/index.php?showtopic=75817

Download the file and then run SRAM patcher. It worked for me anyway.

Edit: See post later down for better explaination.

Don't get mad GPeter7, I'll post the real working patch in 24 hours from now. Got to go now...

Sorry guys for the delay... my ISP performing maintenance for this whole week and I'm a little bit busy (plus doing a final test with all of the patches before uploading it). Anyway, here's the SMA4 patches which correctly save the game to 128K flash save. Patch it with a clean rom and you have to delete your current save game unless it is 128K flash saved game from the VBA/No$gba emulator.

Guys, there's something you all need to know about the Dingoo's emulator save state, it will corrupt/delete your in-game save when you try to load it after loading a save state depending on the situation. It also happened to the other flash save type games!

It's got nothing to do with my patches. I believed you can play the patched rom perfectly fine on a decent flashcart (I don't have any flashcart to test with unfortunately).

There are at least two different method of the in-game save in Super Mario Advance 4:

In-game save (Type 1)
In-game message: "You can continue this saved data once."

Temporary saved game, which upon continue will erase the temporary saved game. The progressive saved game which permanently save your current gameplay will not be affected by this. You can access this type of save anytime by pressing the start button to bring up the menu and select the Save & Quit option.

In-game save (Type 2)
In-game message: "Save your progress up to this point?"

Progressive saved game, you'll get this type of save after you beat a boss in a castle or an airship. A message will popup at the World screen/etc. to tell you whether you want to do this kind of save or not. 

And here are some workarounds to save your game successfully with both save state & in-game save... 

1. Corrupted saved game
Problem:
... Do an In-game save (Type 2).
-> Do an In-game save (Type 1) [Optional].
-> Do a Save state.
-> Exit the emulator.
-> Load the In-game save.

Info:
USA released
- Saved game corrupted and trigger the shaking world screen.

Europe released
- Saved game corrupted including language changed (tested on English language).

Japan released
- Not tested thoroughly, should be the same as the USA released but working fine.

Note: When you load the SMA4 rom and if there's a message READING... on the screen in whatever language, it will possibly corrupted your in-game save. So refer the solution for the fix.

Solution:
a. Load SMA4 rom (till the Title Screen only).
-> Exit the emulator.
-> Load SMA4 rom again.
-> Load the In-game save.

b. Or, Do an In-game save (Type 2).
-> Do a Save state.
-> Do the In-game save (Type 1).
-> Exit the emulator.
-> Load the In-game save. 

2. Deleted saved game
Problem:
... Do an In-game save (Type 1).
-> Reset the game.
-> Do a Save state (at Title Screen).
-> Exit the emulator.
-> Load the In-game save/Save state.

Info:
All released
- The In-game save for both type will get erased.

Solution:
Never do a save state at the Intro screen, do a save state at your current gameplay or at the World screen only. 

3. Missing saved game
Problem:
The In-game save (Type 1 & 2) no longer available by any Save state.

Info:
All released
- Only happens when you deleted the .sav file on purpose and continue/loading with any save state.

Solution:
... Load a working save state.
-> Do an In-game save (Type 1).
-> Reset the game.
-> Load the In-game save (Type 1)

-> Do the In-game save (Type 1) again.
-> Exit the emulator.
-> Now load the fixed In-game save (Type 1).

(Yeah, save twice to make sure the .sav file is generated). 

4. Shaking World Map!
Problem:
The World Map is shaking after you load an In-game save.

Info:
USA released (other released too?)
- Only happens when you make a save state after an In-game save and then load the In-game save later. At first when you load the game, the READING... message in a different language will appear.

Solution:
... Load a working save state.
-> Do an In-game save (Type 1).
-> Exit the emulator.
-> Load the fixed In-game save (Type 1) again. 

5. Language Shifted
Problem:
Suddenly your language is changed into another one upon loading an In-game save.

Info:
Europe released
- Share the same info at #4.

Solution:
a. Load the game (till the Title Screen only).
-> Exit the emulator.
-> Load the game again.
-> Finally load the In-game save.

If it's still not fixed, try solution b.

b. Load a working save state.
-> Do an In-game save (Type 1).
-> Exit the emulator.
-> Load the fixed In-game save (Type 1) again.

If somehow you want to load a save state at the Intro Screen, load your save state after the GAMEBOY PLAYER screen or you'll get a graphic/sound glitches (maybe corrupting the save game too...).

If you want to tranfer your saved game to PC back and forth for whatever purpose (cheating, progressive play, e-card swapping, etc.), you better just stick with the In-game save only and never do a save state, and if you still want to do a save state... just do an In-game save after that and the next time, remember to load the game with the In-game save. As simple as that!

Tested all of them on the 1st save slot only, not sure what's the implication on the other slots.

It's all about dealing with the gameplay problems. Play at least Level 1 or till you can cleared the mini castle, keep experimenting with the in-game save (AKA saved game, internal save that produced the *.sav file) including saving with the save state (which produced the *.st* file) and see if you come across into one of the problems.

If you get one of those problems which I listed from 1 to 5, you can refer to the solution for the fix.

Problem: Info about how the problem occured/originated.

Info: Extra info regarding the problem and its outcome between releases.

Solution: A solution/fix, do it in sequence from "...", "a." or "b." till the last "->" to fix your problem.

If you just want to play SMA4 on the a320/x760+, beat the game and remember it no more... you don't have to concerned about the long post. It's for those who wants to play a smooth game and able to manipulate the working saved game file on the PC for whatever reasons.