This tutorial is for the Everdrive V3 Krikzz or Chinese clone BE CAREFUL, krikzz's OS V2 Firmware will brick ALL Chinese clones, even some Everdrive made in Krikzz
1 - Everdrive MD V3 bricked!
You tried to update your Everdrive MD V3 with OS V2 from krikzz and you had this red screen:
Here you are now with an Everdrive that no longer works! It is bricked! Despite a return to OS V1 & access to the everdrive menu, just after loading the ROM of a game it is a black screen. Your everdrive will be able to play master system games without any problem. But no more Megadrive / Genesis roms...
2 - Why my everdrive is bricked
Krikzz has put a security system on OS V2 for everdrive MD V3, which makes clones unusable! Yes, it is krikzz's desire to destroy the clones!
Even some official Krikzz everdrive were affected!
Here is a snippet of the OS V2 source code:
Don't panic, we've found out how to fix your Everdrive!
3 - How to unbrick the Everdrive V3?
The krikzz OS V2 modifies the code contained in the flash memory of your Everdrive. To be able to unbrick it, we will have to reflash the everdrive flash memory to restart the loading of the Megadrive ROMs.
4 - Reinstall OS V1 on your SD card
To re-install OS V1:
1 - Format your SD card in "FAT32" format 2 - Create a new folder named "EDMD" at the root of your SD card 3 - Copy the OS V1 "MSDOS.BIN" in the EDMD folder (available for download HERE)
5 - Reflash the flash memory of your everdrive
OS V1 is in your SD card, however your everdrive's flash memory is still bricked.
We will therefore have to reflash this flash memory. To do this, open your cartridge to gain access to the circuit board.
Locate the flash memory which is named "M29W640". Now you have to desolder it, we recommend that you use a hot air station to do this!
Once the operation is successful, we are going to need a programmer.
We recommend the "TL866 minipro" programmer, but any adapter taking into account the SST39VF040 chip will do.
Many GamePark 32 fail one after the other for no apparent reason. Here is a tutorial that will allow you to repair your GP32.
1 - Symptoms
The symptoms are always the same: Many people have noticed that their GP32 does not start after a longtime of inactivity (Blackscreen and red LED on).
First check to do: New battery and no oxidation in the battery compartment!
2 - The problem
After appraising and repairing several GP32s, we decided to publicly share our discovery. The problem with GP32 BLU, BLU + and FLU is the quality of flash memory.
Over time, flash memory will corrupt on its own until it has floating bits. This corruption appears when the organs power off. The flash memory responsible for this problem is named: AT49BV040
This GP32 onboard flash memory was manufactured by Atmel and has a size of 512KB. Its small specificity: it was developed to operate with a loss of voltage. We're on a portable console.
All the AT49BV040 flash memories that we have had in our hands have failed. But SST compagnie a make a compatible flash memory which allows us to replace it with a reliable and functional series. Manufactured by SST Electronic, it is called: SST39VF040 in TSOP32 format
3 - Repair the GP32
If you have made sure that the battery compartment is clean with no signs of oxidation and that your batteries are new, then you can begin to disassemble your GP32. Here are photos showing all the parts of the GP32 once dismantled:
By turning over the motherboard of your GP32, you will discover the AT49BV040 flash memory which is faulty.
You need to remove the flash memory from your motherboard. We strongly recommend that you use a hot air station to perform the operation.
Before marrying your new flash memory, we need to inject it with a bios. We recommend that you install the GPBios bios. Thanks to the latter, you will be able to change bios without reflashing your console.
For more information on GPBios: http://spadework.utopia.free.fr/gpbios/
This tutorial is for the Everdrive V2 Krikzz or Chinese clone.
Everdrive megadrive/genesis V2 make black screen, Why ?
An everdrive V2 is capable of starting on a Sega Megadrive without SD card inserted and without battery (for the Chinese version). If your console is working properly with standard games and your Everdrive connector is clean, your EVMD is likely to be broken. How can my Everdrive MD VC2 be bricked? : The Everdrive MD V2 version of (krikzz or Chinese) reads roms on SD to write them on its Eeprom. But here, nobody thought about it but there is a risk of brick with each writing of a games on the eeprom. The everdrive (OS) boot program is on this same eeprom. The OS of Everdrive and the game loaded in memory share the same EEPROM but are stored at different memory addresses If there is a problem during the flash of a game => Everdrive HS.
So there are two ways to debunk your Everdrive MD 2:
1 -Use the backup firmware (very rarely useful): Hold down the A + B + C buttons on controller # 1 and turn on the system. The reserve OS should start.
2 - Manually reflash the eeprom with a dump of a functional cartridge: We start by opening the cartridge to discover the PCB, here we end up with a Chinese clone PCB equipped with an Altera MAX2 and an EEPROM M29W640 (identical component to krikzz's v2):
We must remove the ST M29W640 eeprom, it is in this chip that the OS is stored as well as your games recently flashed. Let's start by protecting our pcb with high temperature tape Then proceed to remove the M29W640 eeprom.
Proceed with setting up your EEPROM in your programmer to read the M29W640 chip and save the corrupt binary file, this will eventually allow you to recover information on the brick.
Now proceed to write a non corrumpus binary file (dumper on a functional cartridge) available in the download section HERE
Reposition your eeprom using a powerful LED torch under the PCB:
This projet allow you to use playstation 1 controller (gamepad or joystick) on Neogeo AES or MVS This projet is under GNU GENERAL PUBLIC LICENSE You can build it by yourself for less than 15$ for MVS consolized
You can show the beta test and final result on our channel youtube :
Connect your PS1 to your PC with the "Serial to USB Net Yaroze" as follows:
3 - PC Configuration
Dans un premier temps nous allons connecter le « Serial To Usb Net YarozeAt first we will connect the "Serial to USB Net Yaroze" to the PC via a USB cable. Windows will detect it and install the drivers automatically.
Once completed, we must go to identify the number of the Com port assigned by Windows. For that we will go in:
>>Start > control panel > Device Manager
We go down the list and there should be the "Serial to Usb Net Yaroze" visible as a COM port with in parentheses the port number assigned.
Note it, it will be useful for the next step.
Now we'll unzip the "Net Yaroze Yaroze software development disc" archive on your hard disc at the following location :
We will now install "DosBox".
As a reminder this small utility allows us to launch Dos applications on our recent systems.
It has a very interesting function that allows us to return a real serial port in its emulated system. We install DoxBox.
To apply the DosBox patch, copy the "dosbox.exe" and "SDL.dll" files found in the "dosbox-0-74-5n1patch" archive into your DosBox installation folder, by default "C: / Program Files (X86) /DosBox-0.74/ ":
Then we will configure DosBox to map the "Serial to USB Net Yaroze" and give it its operating speed (9600 Bps at first).
We will go to the DosBox installation folder (default C: / Program Files (X86) /DosBox-0.74/) and we will run "DOSBOX 0.74 Options.bat:
Here we are in the presence of the DosBox configuration file opened with your favorite text editor.
Modify the "Serial" section as below and replace the "X" with the number of your previously recovered COM port:
Insert the "Net Yaroze Boot Disc" CD (cracker if you do not have the access card in slot 1 of your PS1 / Net Yaroze).
Turn on your PS1 / Net Yaroze. You must have the following image on your screen:
CIP Version 2.0 Startup
Access Card Checking...OK
Memory card Checking...Not found
Terminal Speed 9600 BPS
Access Card Checking...OK : Cracked CD, No need Access card.
Memory card Checking...Not found : the program of the "Net Yaroze CD boot disc" check if a memory card has been inserted in slot 2 and if a backup configuration is available inside them. Le cas échéant, même avec une carte mémoire insérée nous avons le message « Memory card Checking...Not found ».
Terminal Speed 9600 BPS: see "chapter 6 : Communication speed" to increase the transmission speed.
Your PS1 / Net Yaroze is now ready to receive code via its serial I / O.
5 - Hello World
We move on to serious things, we will now execute code. To do this we will use the program "SIOCONS" translate «Serial Input Output CoNnectionS ».
Start DosBox and type the following commands:
You should have the screen of your Net Yaroze / PS1 which will have evolved to confirm the good reception and storage of the program, followed by the execution of the code:
In folder C:\PSX\ on DosBox, you have several small test programs available, I let you discover them by navigating in your directories and executing the command "siocons auto"
6 - Communication speed
You are currently at a default speed of 9600bps, your Net Yaroze / PS1 has the capacity to mount at 115200bps and your "Serial to USB Net Yaroze" too!
We will increase the transmission speed to 115200bps.
Turn on your Net Yaroze / PS1 with the "Net Yaroze boot disc" CD and a memory card insert into slot 2.
It is normal for the message "Memory Card CHECKING...Not Found" appear.
Now run "DosBox" and type the following command:
Wait 2 sec and press the "Enter" key on your keyboard to regain control of the prompt "siocons".
Type the following command and validated by "Enter":
Your Net Yaroze or PlayStation is now at 115200 Bps, but your DosBox is still at 9600Bps.
Now press the "F10" and "F2" keys on your keyboard to recover the "DOS" prompt.
Now we will restart "Siocons" with an additional argument, for that type the following command:
After a few seconds, siocons asks you the following: "Save the new baud rate into the memory card ? ( y/n )"
Answer "y" with your keyboard.
"Siocons" will answer you "Completed".
"Siocons" has just confirmed the writing of the configutation speed to 115200 bps (Baud Rate) in the memory card slot 2 of your Net Yaroze or PlayStation.
Make a reset on your playstation. It now shows you the following screen:
CIP Version 2.0 Startup
Access Card Checking...OK
Memory card Checking...OK
Terminal Speed 115200 BPS
We still have to configure the transmission speed PC-side on DoxBox..
To do this, close dosbox and edit the file "DJSETUP.BAT" which must be here :
In line 4, you must have:
Replace 9600 by 115200, now you must have :
Save and relaunch DosBox.
Your PlayStation and DosBox are now set to the maximum transmission rate of 115200 bps.
7 - STU Configuration
You can reconfigure your STU Net to make it compatible with other applications or homebrew.
In first time, download FT_Prog
Proceed to FT_PRog installation and start it.
Connect your STU Net Yaroze.
In the top menu, do : "Devices" > "Scan and Parse" :
Your STU Net Yaroze will be recognized and will appear under "Device Tree" in the FT_Prog application: