Download Code Breaker V10 For Cheat Pcsx2 Bios

Feb 18, 2012  I tried using codebreaker v10 on pcsx2 for the first time trying to cheat on star ocean 3. Every time I load the game with or without cheats it crashes but it works with kingdom hearts 2.

Hi everybody, I have a PS2Slim(the last version of them). It have installed a Matrix Infinity v1.93 clone but works fine except saving the configurations. It does not support what they call Swap, if I open the lid the console won't read homebrew discs anymore. Im trying to run Codebreaker from somewhere different then disc so I dont need to open the lid. I copied uLE BOOT.ELF to my memory card and I can boot it normally. Once I booted uLE (the game disc is inside), I browse to my pendrive and launch Codebreaker executable. In this time I get a black screen with a lot of versions tested.

It works in one single situation, when I run uLE from disc then browse to mass:/ and then executing Codebreaker. When the pendrive led stop blinking I remove the device and finally the program starts, but I have to open lid to put game disc in drive and then process fail. Another weird thing is that I cant use uLE with my pendrive inserted, otherwise it wont detect my memory card. I need to boot then in the FileBrowser insert it and then it works well. How to make Codebreaker works when booting from memory card?

Thanks in advance, Felipe. I have a PS2Slim(the last version of them). If it really is the latest version, then your choices are limited by it, since there are no softmod methods that will work with it. You can double-check this by using uLE to launch its built-in subprogram 'MISC/Debug Info', which will display the bios version as part of a string read from the bios ROM in a file named 'rom0:ROMVER', which is displayed by that uLE command. The first four digits of that string show the bios version, and if that is '0230' then the softmods will not work, but if you are lucky and have '0220' then the FMCB and ESR softmods will work fine.

If you do have bios v2.20, you have much better choices available, but for now I have to assume that you have the latest v2.30. If I open the lid the console won't read homebrew discs anymore. That is the infamous 'sleep mode' of the MI chip, which makes it useless for all advanced uses, in my opinion. They implemented that just to cope with an extremely small minority of games that can detect an MI modchip and refuse to run. Instead of fixing the real problem, they just made the modchip turn itself off after the initial boot.

The opening of the lid is in fact not handled by the chip at all. It is Sony's mechacon (disc controller) that demands new validation of an original disc when you open the lid, just as if you had no modchip at all (which is exactly the case, after that initial boot when it turns off, except for the deadly 'Macrovision fix' of course, which remains always on.). But I have to open lid to put game disc in drive and then process fail. Since the sleep mode is active, you have no mod-chip at that time, so the mechacon demands original disc validation just as on an unmodded console. The obvious solution here would be to have the correct disc in the drive from the start, with modchip settings to ignore the disc and boot only from MC regardless of disc tray contents. But with your clone you can't modify settings that way.

But I think the MI still has pushbutton commands for boot time, so you can push and hold some specific button to force MI into using Dev1 boot even when there is a disc in tray. This should allow you to start CodeBreaker, and have it use the disc already in tray without opening the lid. But you need to modify one of the settings in CodeBreaker to make it work like that (it will then save that setting to MC too). If you find that this method does work for you, remember to NOT define any launch task for uLE using the same button that MI wants you to push for Dev1, so that uLE does not also respond to the same button in any way.

Another weird thing is that I cant use uLE with my pendrive inserted, otherwise it wont detect my memory card. I need to boot then in the FileBrowser insert it and then it works well.

That is very strange. You are the only person ever to report such a problem, so it definitely indicates something horribly wrong at your end. There is absolutely no real connection between the MC usage and the USB usage, and they should be completely independent of each other. Do you really mean that uLE is unable to browse your memory card when the USB drive is connected, or is it just that uLE won't boot for you when a USB drive is connected at reset or power-on. In the latter case this is clearly another problem with your modchip.