Dingoonity.org

Hi there,

First of all, I just want to say this is a great website. I've got a lot of help in setting up my Dingoo just by looking at these forums.

Now to my current problem - I have a Dingoo A330 with the standard system setup. All I've done is download some ROMS and emulators that work on the native system (eg, Master System, PC Engine, Game Gear etc)

Last night I was charging my Dingoo and thought I would just knock another level or two off Kirby's Nightmare in Dreamland  Anyway, I played it for about 15 minutes while the charger was plugged into the power socket and then put it down for a few minutes. I didn't seem to have any issues at the time, but now I am having a few problems:
- The main problem is that when I turn on the Dingoo, it gets stuck at the very first screen (the 'Dingoo Technologies' logo). I don't get any further than that.
- Second issue is that none of my PCs seem to recognise the Dingoo when I connect it via USB. When I go into devices, I can see it there, but it doesn't show up as a drive and there's no way to access the folders. Initially it said the device had malfunctioned, but I don't even get that message anymore.
- The third issue is that while it is on (stuck on the opening screen), I can't turn it off using the usual power button on the side. I can only turn it off by using the reset button, which actually resets it and I end up with the same problem.

Prior to this I haven't really had any problems. I've had a few issues here and there with ejecting from USB ports etc but nothing too bad.

In terms of solutions, I've tried downloading the driver to my computer so that the Dingoo is recognised but haven't been able to achieve that so far, through a combination of me being wary of shifty download websites and me being unable to use the drivers once downloaded.

I've also tried the 'hold B then reset followed by insert USB cable' strategy which I've read about in a few places. This usually results in my PC making a chime sound but nothing actually happening. The Dingoo screen turns black and it basically looks like it has turned off.

Any help would be appreciated.

Well, the A330 is really problematic for recovery. The black screen when you start up holding B is an indication that the device is waiting for a connection. On the A320 at this point you should use the unbricker tool - driver is included, but I'm not sure it works with newer versions of Windows, or 64-bit windows for that matter. Worst case scenario, you may have to install a compatible version of Windows in a VM to get it working. Once the flasher tool connects and start flashing the device, the screen should light up and show the flashing progress.

However, the biggest problem, and one that you may not be able to get around, is that there's no provided HXF file (which is the firmware image) for the A330 on the unbricker tool, there's one only for the A320. As far as I could tell, I don't think an HXF for the A330 was ever released or leaked...

So, at this point you might as well just try your luck with the A320 HXF file. The A330 is almost the same device as the A320, only with a slightly faster CPU and double the RAM. I'm a bit skeptical it'll work, but if it does you'll be left with a firmware that will not use the full hardware resources. One workaround to that is installing OpenDingux on it, that should make full use of the devices' resources.

Good luck!

EDIT: Ok, just found a link to an A330 HXF file on a youtube video, it links to dingoo.hk which I believe is down, but thanks to the gods of Web Archive, you can get it here: http://web.archive.org/web/20101119105622/http://www.dingoo.hk//bbs//UploadFile//2010-5//A330kongjian.zip

On further reading, however, it seems the A330 firmware is really just a slightly modified A320 that doesn't fully use the A330 hardware capabilities anyway. You might still have better chances with it as opposed to using a straight up A320 firmware, if only because the file was originally hosted by Dingoo Tech and has "A330" in the filename... 

FINAL EDIT: See:
http://boards.dingoonity.org/dingoo-hacks/a330-firmware/
http://boards.dingoonity.org/dingoo-general/latest-a330-firmware-from-dingoo-hk/
http://boards.dingoonity.org/dingoo-general/a330-firmware-works-on-a320/

I believe that, afterall, your biggest hurdle will actually getting the drivers and the unbrick tool working if you've got a newer version of windows. I'm pretty sure the unbricker driver will only work on no later version than Windows 7 32-bit.

Ok, what follows is a summary on the process, it's been a long time since I did it, so a few details may be different, but it's pretty straightforward, you should have no problems adapting if you find any differences.

I'm assuming here you have some basic knowledge on how to install drivers on Windows, via the Device Manager and such. Please note the instructions below assume Windows with english language. Since you've said the laptop you've got has another language of Windows, you'll have to work it out where to find the elements from Windows I'm referring here. And remember, the driver for the unbricker will not work on Windows 64-bit, only on 32-bit:

• Unpack the unbricker tool somewhere on your PC. Also unpack the zip with the HXF you'll flash;
• Run the unbricker tool, which is the executable "hacked-TestVersion.exe". Click the "Install Driver" button, and let it run its course - you'll know when it's done when a dialog saying "Installed!" shows up;
• Hold down B and reset the dingoo, then connect it to the PC. The Dingoo's screen will stay black / blank, that's normal;
• The PC should initially detect the device as "JZ4740 USB Boot device", or something like that. It will not show as a removable drive at this point, since it is in recovery mode;
• Windows will try to hook it up automatically using the drivers installed on step 2. If it can't, you'll have to try installing the drivers manually, so go into the Device Manager, find the broken device there, and try to install / update its driver pointing it to the folder "usb_drv" that's inside the folder where you've unpacked the unbricker tool on step 1;
• With the driver properly installed, go back to the unbricker tool. On the line saying "Firmware file", click the "Select..." button and select the HXF file you will flash;
• Click the "Burning System" button. If everything went correctly, the flashing should start and at this point the dingoo's screen should light up and show the flashing progress. Once it finishes, reset the dingoo (if doesn't on its own after flashing finishes) and hope for the best...

Unfortunately the Dingoo has a bad tendency to frequently corrupt its internal drive that is exposed to Windows, so you can expect the dialog asking to "Fix it" to show up often. That's one of the reasons I don't like using the native OS on the Dingoo, and almost always use OpenDingux instead.

Also - I'm pretty sure that some of the files on the internal memory (the part of it that's exposed to Windows as a removable drive) actually contains the emulators that the device runs, so if you can't see any files when you access it from Windows, then it's possible you won't be able run any games since the system will not be able to run its emulators. I may be wrong about that of course, since it's been a long time I've last reflashed my Dingoo or messed with the files on the internal memory (again, since I mostly use OpenDingux anyway). Just in case I'm right though, download this file and unpack it inside your Dingoo from Windows Explorer. These files are the ones on my own Dingoo, and some of the emulators in there actually are not the ones that are bundled with the device, but are instead third-party ones developed by the community, but trust me, they are miles better than the ones bundled with the Dingoo.

You can always try flashing other HXF files (e.g. from the A320). I'm actually a bit concerned about what you said of the flashing process getting stuck or something to that effect: did the flashing application on the PC seemed to hang as well with no indication of having finished or only the flashing progress on the dingoo display seemed stuck? If it was the latter, then I'd say that's ok, but if it was also the former, then as far as I remember, that shouldn't be normal (but again, bear in mind I haven't done that in a long time, so I may be wrong).

As for the emulators crashing, on the pack I've linked to there's an improved SMS emulator that may work better and it has save state and pause feature. Can't say about PCE, I don't play games from that one. In fact, you might want to just unpack everything on top of anything you have, because for those emulators that I didn't replace with third-party ones I've kept the original, built-in ones and they are also in the pack - including GBA, which is one of the few emulators that are built-in that actually work pretty well, and it is working here.

You can also always try alternate emulators linked from the wiki or from the openhandhelds archive.