Unbricker for Gemei A330

As you know, our freshly purchased gemei do not have a radio module on board. Maybe because of this, and maybe for other reasons, when flashing the device, there may be trouble that can turn the device into a brick. In my case, after flashing the device hung when trying to write to it any files directly. The copying process just hung, and then completely crashed with an error. So it turned out that I did not have the opportunity to flash to another version of the firmware.

But thanks to the hope of the whole dingoo \ gemei-community - the creator of the alternative Dingux firmware - BooBoo , there was an output in the form of unbrick (by the way, there is no way to do a hard reset without dancing with a tambourine). How to return the rattling handheld to life can be found under the cut.

The first and, perhaps, the most disgusting feature of the anbriker is that it will work only from Windows XP x32, since no one bothered to write drivers for Chinachip USB Loader for other OSes. In general, we rejoice in what we have.

For successful anbrika we need a memory card compatible with our device. And card reader.
Since I didn’t have a reader at hand, I used a camera. It’s possible to make the memory card bootable using the console’s memory card slot, but I haven’t tried it.
As well as an archive with anbriker and drivers.

Disclaimer

Of course, I am not responsible for the restoration of your broken equipment, as well as for the failure of the whole. Do everything at your own peril, blah blah blah. Also I apologize in advance for the poor quality photos.
')

Anbrik preparation

1. Back up the console’s internal memory files, if possible.
2. Format the memory card in FAT with a standard cluster size.
3. Run run.bat from the SDBurn_BootLoader folder, having previously edited it in such a way as chinachipsdburntools.exe drive_name: rom.bin
   
   ... and here attention! If it doesn’t work right away, try chinachipsdburntools.exe in the batch chinachipsdburntools.exe rom.bin drive_name: that is, on the contrary, change the position of the flash drive and rom.bin. No matter how paradoxically it works somehow through time, without a system ...
   
   , so that instead of “drive_name:” you had the letter of your flash drive (just console flash drives, not the drive letter of the internal memory).
   The following command should help linuxoids:
   'dd if=rom.bin of=/dev/sdi bs=512 seek=2? (sd# – # ).
   It turns out something like this:
   
4. Remove the flash drive from the card reader and insert it into the off gemei.
5. Now connect the USB cable from the console to the port on the PC, hold down the button on the a330 and connect the cable. The device will switch to USB Loader mode. But since we don’t have any drivers in the system for this mode, we’ll proceed directly to installing them.
   
6. Run Burning_tool (CC1800 V1.14) _W35.exe
7. Click on the top big button (1).
   
8. It is the only active by default. There should be installed drivers for USB Loader mode A330.
9. Personally, I did not succeed, despite the cheerful pop-up with “OK” and gibberish instead of symbols.
   
10. If you are as lucky as me, then install the drivers manually. They are located in the drvrs folder in the root of the downloaded archive.
11. Now Burning_tool (CC1800 V1.14) _W35.exe, press alternately the three top small buttons (a, b, c), and select IPL_V1_04.bin for the first button, CN2009P_CFG_A330_LCM_TB_TD030WHEA1_320_240.DL for the second and A330.HXXTD030WHEA1_320_240.
    
12. We poke into the second large button on the left (2). In the Burning_tool window (CC1800 V1.14) _W35.exe, Burning will crawl on the bottom, and information about the Chinese process will be displayed line by line in the main window. On the A330 itself, the inscription Loading ... will appear.
    
13. We smoke 3-4 minutes. During this time, your XP will mount the device once (determined by sound) and unmount it once. After that, gemei A330 will boot up with its own bootstrap and immediately pick up in the form of flash drives. The Burning_tool window can be closed without paying attention to the Burning caption below.
    

Afterword

Actually, everything. Enjoy
If you backed up, just copy all the files back to the internal memory of the console, if there was none, you can download it here .

UPD. After anbrik, you will have firmware version 1.1 dated Feb 13 2011.

(screenshot taken from the firmware with modified graphics, but with the same version)
UPD2. I reloaded the archive with anbrik. I updated it with the most up-to-date firmware and added screenshots.
UPD3. The annoying mistake in point 3 crept into the guide. I apologize to those who because of this experienced inconvenience. Thanks to neelts for revealing it.
UPD4. I reloaded the archive with stock software. Now, when restoring from this archive, you will have the latest versions of emulators. Please note that their work requires firmware version 1.1. The archive includes itself SNES 1.0, MVS 1.1, NES 1.1

Thanks to Aldekein for the opportunity to post a topic.
And a big FAQ bonus.