Sorry i was out for a while and i've made you a new exploit save with the numbers you proviced and a different BOOT.ELF, so maybe this one will work for you, just try those 3 games and hopefully one will boot uLaunchELF.![]()
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
Sorry i was out for a while and i've made you a new exploit save with the numbers you proviced and a different BOOT.ELF, so maybe this one will work for you, just try those 3 games and hopefully one will boot uLaunchELF.![]()

This means that the exploit triggered, but for some reason it either failed to launch the BOOT.ELF file, or did launch that file which then for some unknown reason crashed or froze.
There is no need to experiment further with finding a working PS1 disc or changing the game ID in TITLE.DB, since it did trigger this time.
But you may want to try some other "BOOT.ELF" in case the exploit code has some problem launching that particular elf file. (It happens sometimes...)
As I recall, ubergeek42 made an alternate exploit maker with slightly different launcher code than the traditional 'MrBrown' exploit. I've just tested that this newer exploit works fine with the latest uLE versions on my v7 console, so it should work for you as well. The zip I'm attaching contains only a single exe file used to create the TITLE.DB file you need. The rest of the work to create a proper system folder and converting that to a .max file etc is up to you. But for this version I can guarantee that the launcher in the TITLE.DB file is capable of handling even the latest uLE versions.
NB: This TITLE.DB launcher does not give a white flash, but instead shows a blue screen.
Best regards: dlanor
yes!!!! OMFG!!!! finally thank you sooo much!!
Errm when i select mass// in the browser thingy it freezes.... do I w8 for a while? or is there another problem....
Getting a little closer each time!!!
How come when ever I try and do something it fails -_-
THanks!
No problem....glad you got it to work.![]()

well i sorta have but now it freezes when i try to access my data on the flash drive in ps2..... do I w8 or is there another problem?
Its most likely incompatible with the version of BOOT.ELF i used...i used the default one from the PS2 Exploit Utility and its uLaunchELF v 3.61...rather old and not updated with the new USB drivers.
The one i gave the first time was the uLaunchELF v4.40, but didnt seem to work for you, so maybe replace the one in your exploit_save.max, by using PS2SaveBuilder and resave it with another verion of uLaunchELF.

Sorry.... what do I have to do? I used just the noobie package for all the files i needed so what geos where and how?
The Noobie Package files you need are the INSTALL folder and the FREE_MCBOOT.ELF on a USB stick...then launch it with uLaunchELF.
But if you cant access a USB device with the BOOT.ELF i gave, you will need to replace it in that Exploit_Save.max with the one from the Noobie Package (its in the INSTALL folder), using PS2SaveBuilder and re-install it with AR Max again.

We are assuming that you are capable of using the PS2SaveBuilder program to pack and unpack the contents of the ".max" save file. If not, then there is nothing you can do yourself, so we have to assume that you can do this.
There are then two things you can do.
Alternative 1:
Use the first ".max" file that JNABK posted, which gave you a white flash but did not boot. The reason for using this ".max" file instead of the second he posted is because this one contains the newer uLE version in its BOOT.ELF file, which is the best chance to get working access to your USB drive.
Use PS2SaveBuilder to open the content of that .max and replace the TITLE.DB file with one you create yourself using the tool I attached previously. The one by ubergeek42. And this creation is done as follows:
Launch that titledbmaker.exe file and observe the buttons and entry fields in the lower left part of the window. One of them has a drive letter in it, and if this is not already the correct letter for your PCs CDVD drive, change it to be so. Then insert your PS1 game in that drive and wait for the PC to access it properly (takes a few seconds normally). Then clickthe program button entitled "Read ID", which should put the correct game ID in the entry field in the bottom left corner of that Window. To the right of that field there is a button entitled "Add Entry" which you should click next, so as to copy the ID that was read into the main ID list above these buttons and fields. You can repeat this procedure for entering more IDs if you like (to allow several trigger discs), but when you have the IDs you want in the main list, click the button entitled "Save TITLE.DB" in the top right corner of that window. This will save the TITLE.DB file into the same folder as the program.
So now you just copy that file into the PS2SaveBuilder listing of the .max file, replacing its old TITLE.DB after which you resave the files to .max format again using PS2SaveBuilder, and making sure to use exactly the same format as before.
Alternative 2:
You can also use similar methods with PS2SaveBuilder to just replace the BOOT.ELF file with one that the old exploit will 'like', and which will have sufficiently new USB drivers to be compatible with your drive. But chances are that you may have to try many to find one that works both ways, and there is no guarantee of success.
Best regards: dlanor
| « Previous Thread | Next Thread » |
| Tags for this Thread |