GBA emulator problem

Nothing f***ing works, ever .gba file i put in there freezes my dingoo a320 at the loading screen…


6 comments on “GBA emulator problem
  1. says:

    my advice: install firmware 1.22, official. Delete gba.sim configuration data. If possible, use a backed up gba.sim config data file. That should do it. If you’d like i can email you my working config data. It’s solved other people’s gba emu prob in the past.

  2. says:

    There is no config data file… now what?

  3. says:

    same thing. use my gba config data.

  4. says:

    I registered just to comment on this. I bought a Dingoo for a friend a while back and had the same issue right out of the box. I copied the working .sim and .cfg files from my Dingoo, tried upgrading firmware, even tried the unbricker tool and it just absolutely would not play gba roms. It froze on the loading screen every time.

    Then I came across this:,0,0,0,5,253

    It seems there’s a slightly different version of the GBA.SIM file that doesn’t work on certain Dingoos. I downloaded the file from the link above and it worked!

    May be worth a shot.

  5. says:

    This worked for me Bobo, I tried finding a gba.cfg file like mentioned before, but never found one included with the GBA roms from the original firmware. I am running firmware v1.22

  6. says:

    It’s because the only way to get one, is to make one.

    There are two different versions of the GBA.sim, one that works for UNpawed (sometimes referred to as “HK’s”, essentially an UNpawed unit) and one that works for the Pawed units. By changing the options of either one, during use, makes your system create a .cfg. So, you can either scout around online for the GBA.sim that works for your unit, or find someone who has them both and will share it and/or the .cfg datas like i do…

    As a side note, the same thing goes for the Odyssey 2 emulator, “O2EM.sim”, two working versions for the two different units, so using the wrong one on the wrong unit will result in emu non-operability/system hang. Also, 1.22 Official FW is, by experience and opinion, the best FW for Native OS users. The other FW’s were too unstable, with random system crashes, an overabundance of rom incompatibilty issues, etc. Ever since i went strictly to using 1.22 Official, i’ve very, very rarely had any issues. Right now i am running 20 different emulators on my units, all off the main, nand memory. No memory card, system hang fixes or other such silliness. Everything’s running nice and smooth, just the way it should be…

    I discovered all this and a whole lot more shortly after becoming a reseller, i’m talking late nights of troubleshooting, for at least a week… Lots of fun… 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *