Im new

Printable View

07-08-2010, 01:54 PM
Evolutionz

Im new

So go easy. I have some computer savvy but not a mad amount.

Here is my setup.

Cb 9.3 /CB 9.2 elfs tried them both seperately in the following fashion.
located on Memory Card 1. only this file(s) on there.

Memory card 2 has my FMB and Ulaunch and ESR etc.
CB_launch.elf is located on MC2 in the boot folder with the rest of the ELFS.

Im using UsB to transfer any data, I also want to note that I have the ability to use a fat or slim.

I have successful use of KH2 burned and patched for my ESR, but I want ONE code from CB.

My PS2 sticks once I press start game, both methods of starting with disc already in, the put in wait 5 seconds then hit X again.

Nothing, just black screen. it jumps but nothing happens. just black screen.
I want to go to my ESR to load KH2 with codes on. PLEASE HELP.

another thing. I cant rename my ESR? which is what one or two forums insist on. it says no and yells at me.

I can break down more if needed, but hopefully this is enough info.

Please, even if its a mod, someone help me asap. Thanks in advance!
Evo

EDIT: The first elf on my first MC IS in a boot folder btw
07-08-2010, 06:48 PM
Evolutionz

Someone?

Please you guys. even a link to what I need would suffice. I think its the placement of my files. help me!!!!!!

Thanks
07-08-2010, 08:44 PM
dlanor

Quote:

Originally Posted by Evolutionz

Here is my setup.

You left out one of the most important pieces of information, which is your console model, as identified by its product code, as found both on the cover of the console and in the "Version" menu of the console itself (in the Sony menu system).

The product ID format = SCPH-XXXyy where 'XXX' are three numeric digits specifying the hardware model, while 'yy' are two numeric digits specifying the console region.

Quote:

Cb 9.3 /CB 9.2 elfs tried them both seperately in the following fashion.
located on Memory Card 1. only this file(s) on there.

Memory card 2 has my FMB and Ulaunch and ESR etc.
CB_launch.elf is located on MC2 in the boot folder with the rest of the ELFS.

All of this sounds functional to me, on general principles. But CodeBreaker abilities are model dependent.

Quote:

Im using UsB to transfer any data, I also want to note that I have the ability to use a fat or slim.

'ability' you say. But what did you actually do ? What is it that fails for you ?
Did those failures happen on a fat console, a slim console, or both ?

Quote:

I have successful use of KH2 burned and patched for my ESR, but I want ONE code from CB.

My PS2 sticks once I press start game, both methods of starting with disc already in, the put in wait 5 seconds then hit X again.

This sounds typical for the CodeBreaker model dependency, making it allergic to all USB use on all slim PS2 models from v14.

Quote:

another thing. I cant rename my ESR? which is what one or two forums insist on. it says no and yells at me.

I am not aware of any 'yelling' interface in FMCB or the other softwares involved...
Please use clear and understandable descriptions of the program responses if you want us to understand what you mean.

If you are talking about attempts to rename stuff on MC, that ability only exists in some of the versions of uLaunchELF (aka: uLE), including the latest release v4.42. In v4.41 such attempts will always fail, and it varies for some preceding versions too, as we've had to switch the MC driver modules a few times.

Note also that if you rename the elf files on MC without also changing the FMCB configuration for those programs, then FMCB will no longer be able to launch them, as it will still be using the old filenames it was configured to use.

As for renaming files on USB, that is not permitted by existing USB drivers on the PS2, so for such renaming you have to move the USB drive to a PC and do the job there.

Quote:

I can break down more if needed, but hopefully this is enough info.

Not quite. As your PS2 model is of great importance in this.

Quote:

Please, even if its a mod, someone help me asap. Thanks in advance!

I do happen to be a mod, but I don't see why this should matter either way.

Quote:

EDIT: The first elf on my first MC IS in a boot folder btw

I'm not sure what you mean by 'first elf' here.
The boot procedure is not affected by storage order, but only by storage methods.
(Correct spelling of file/folder names etc, and of course a proper FMCB install.)

----- about your second post, nagging for attention -----

Patience is a virtue, especially when seeking help.
Starting to nag the people you want it from within only 5 hours from your first request is not a good idea... (Personally I happened to be sleeping during those hours.)

Quote:

Originally Posted by Evolutionz

Please you guys. even a link to what I need would suffice. I think its the placement of my files. help me!!!!!!

In fact I find it more likely to be a conflict between your console model, CodeBreaker, and how you are trying to use it.

It is a well known fact that all modern versions of CodeBreaker (v9 and higher) will freeze when launched on a slim PSTwo of console model v14 (SCPH-750xx) or higher and with any USB device connected. CodeBreaker can still be used on most of these models, provided only that no USB drives are connected while it is running.

And on the latest v18 model (SCPH-900xx) these CodeBreaker versions do not work at all.

If your console model is somewhere between v14-v17, then a simple fix for the problem is to just pull out all USB drives before or after starting the CodeBreaker program. Doing it before is 'cleaner', but doing it after allows you to use the USB drive for the launch. Once all USB devices are removed the program should 'unfreeze' and proceed normally, allowing you to choose game and cheats. And if it is a properly patched CodeBreaker elf you can then use the "Start Game" command to get back to FMCB or uLE or whatever you configured it to do when the elf was patched. And from there you can then start your game with cheats active.

On a console model older than v14, this problem should never happen, and on the latest v18 there is no way to use CodeBreaker for these purposes, because there it crashes regardless of any devices connected.

Best regards: dlanor
07-08-2010, 09:07 PM
Evolutionz

Ok.

Let me try and explain differently while giving you what you need.

System:SCPH75001 this is on the slim, Im not sure about the fat.

Im lost on where the CODEBREAKER ELF goes and where the CB_launch go respectively. I think I did them right, but then what, simply click on the CB elf and it starts up? Ive tried that and when I go to start the game on codebreaker, it seems like it is going to but remains black screen.

Ive done this two or three different ways a hundred times each.

I would simply like to boot the codebreaker from elf, then back to my ESR to play my game.

Im going to give you MAD amount of info so please bear with me, Im assuming this is a silly mistake somewhere.

MC1: Nothing but a boot file with the CB elf in it.
MC2: has FMCB and Ulaunch and ESR and everything else. inside the BOOT/ I have the CB_launch.elf it sits in betwee boot.elf and esr.elf

my USB was all done through the fat one btw, as to be able to have my USB read properly for transfer of install files from original install.

Now what? do I make a path? if so how?

from this point on when I simply run my codebreaker elf it works! but as I said earlier does not bring me back to my menu or anything, just black screen.

I apologize for my ADHD, Im very impatient, please excuse my earlier inconveniences

Make a note btw, that the CB_launcher I have had a few different versions. from torrents to megaupload and even from here. so if there is a basic one for what I need, please direct me to it.

EDIT: the codebreaker elf was renamed to BOOT.elf as told to do so in a tut

thanks!
07-08-2010, 09:32 PM
Evolutionz

I would like to verify that

my codebreaker has now loaded on the fat PS2.

Im getting somewhere.

It still doesnt load to my Dash though

Just wanted to update ;]

EDIT: another update. still black screen. and I just tried a different set of CB elf and CB launch. none are working. just black screen? do I need to configure it?
07-08-2010, 10:16 PM
Evolutionz

Fixed!!!!

dont really know how. but its working now
07-08-2010, 11:02 PM
dlanor

Quote:

Originally Posted by Evolutionz

Let me try and explain differently while giving you what you need.

System:SCPH75001 this is on the slim, Im not sure about the fat.

That slim console is a v14, so it suffers from the problem I mentioned before.
To use CodeBreaker with that console you must unplug all USB devices to unfreeze it.

Quote:

Im lost on where the CODEBREAKER ELF goes and where the CB_launch go respectively.

The CodeBreaker elf can be stored anywhere you like, as long as you can launch it either from FMCB or uLE (via uLE shortcut or FileBrowser).

Quote:

I think I did them right, but then what, simply click on the CB elf and it starts up?

Click ?

I assume you mean selecting that elf somehow to launch it, such as you can do with the uLE FileBrowser, which should work fine. But it is of course even more convenient to define a shortcut button for it in the uLE menu.

Quote:

Ive tried that and when I go to start the game on codebreaker, it seems like it is going to but remains black screen.

Yes, With a v14 console and a USB device connected the program always freezes. Until you unplug the USB device that is, at which point it will proceed normally.

Quote:

Ive done this two or three different ways a hundred times each.

Then you are a bit too stubborn for your own good. Somewhere in all of those tests you should have realized that you need to vary something else for success. And unplugging the USB ports should have done the trick...

Quote:

I would simply like to boot the codebreaker from elf, then back to my ESR to play my game.

That is possible, but it is really a better idea to patch the CB elf for exiting to uLE instead, so you can start any game launcher with cheats active, not just ESR. (Works fine also with HDLoader and "Open PS2 Loader" (the latter allows cheating on games run from HDD, USB, or a remote SMB fileshare on a PC or NAS unit).

Quote:

Im going to give you MAD amount of info so please bear with me, Im assuming this is a silly mistake somewhere.

One such mistake is that you didn't absorb the info in my previous post, about how CodeBreaker always freezes on a late-model console having some USB device connected.

Quote:

MC1: Nothing but a boot file with the CB elf in it.
MC2: has FMCB and Ulaunch and ESR and everything else. inside the BOOT/ I have the CB_launch.elf it sits in betwee boot.elf and esr.elf

Your information is incorrect, as you ignore character casing.
And correct character casing is crucial for correct use of PS2 homebrews.

Quote:

Now what? do I make a path? if so how?

You can no longer modify the behaviour of the CodeBreaker elf, as that should have been done properly in its patching. All you can do now is to attempt using it as intended, assuming there were some notes to that effect with the file when you got it.

Quote:

from this point on when I simply run my codebreaker elf it works! but as I said earlier does not bring me back to my menu or anything, just black screen.

This implies that it was patched to exit by launching an elf having either a different name than you've used, or stored in a different location.

But the normal correct location for "CB_launch.elf" is "mc0:/BOOT/", not "mc1:/BOOT/".

While it is possible to patch up to three alternate paths, the standard patching uses those for "hdd0:/__boot/CB_launch.elf", "mass:/BOOT/CB_launch.elf" and "mc0:/BOOT/CB_launch.elf". You could change that if patching your own, so as to make it look on both your memory cards. But to my knowledge it will not do so if only one MC path is defined in the patching, as is probably the case for the prepatched ones you've found.

Quote:

Make a note btw, that the CB_launcher I have had a few different versions. from torrents to megaupload and even from here. so if there is a basic one for what I need, please direct me to it.

The one I use for rebooting FMCB is only 13576 bytes in size, so if you have one of exactly that size it should be the same one. With this stored as "mc0:/BOOT/CB_launch.elf" it should work for you.

Quote:

EDIT: the codebreaker elf was renamed to BOOT.elf as told to do so in a tut

Completely idiotic advice that, in my opinion. First off because "BOOT.elf" is an incorrect name usage for PS2 homebrew, and secondly because the correct usage "BOOT.ELF" should be considered reserved for uLaunchELF.

The way I use CodeBreaker I simply use a name that is descriptive of what it is and how it was patched, such as "CBv10 BOOT_ELF doCdStop.ELF" or "CBv10 CB_launch doCdStop.ELF" etc. And I never store these elfs on MCs less than 32MB in size, so for cases where I need to use them with small MCs I launch the CodeBreaker elfs from USB instead (works fine even on v14-v17, provided you unplug the USB drive after launch freeze).

Quote:

Originally Posted by Evolutionz

my codebreaker has now loaded on the fat PS2.

Im getting somewhere.

It still doesnt load to my Dash though

Dash ? Please use correct language.
Since I am Swedish myself I am not accustomed to all US slang expressions.

To my knowledge of the English language the word "Dash" is a verb, though it can also be used as an adverbial noun, as in talking of someone making a quick run somewhere, and describing that as a 'dash'.

Possibly you used a kind of 'lazy-speak' expression for 'dashboard' in reference to the program you wanted to launch at exit from CodeBreaker, but then you need to express yourself more clearly. Simply using the abbreviation 'dash' does not tell me either which program you really mean, nor how you have it installed, nor how and why you expected CodeBreaker to launch it.

The only proper way of doing that is to patch your own CB elf, using ffgriever's patch program, as this allows you to specify what elf file to use at exit from the CodeBreaker GUI.

Quote:

EDIT: another update. still black screen. and I just tried a different set of CB elf and CB launch. none are working. just black screen? do I need to configure it?

Most likely your main problem is that your CB elf is patched to use mc0: for the elf launching though you store the CB_launch elf on mc1:.

Another potential problem that also causes black-screen crashes is if you attempt using cheat codes whose 'Master Code' begins with the digit "F" instead of the digit "9". The former type of master codes (the "Fxxxxxxx" kind) do not work properly with the patched CodeBreaker.

Best regards: dlanor