The above video goes away if you are a member and logged in, so log in now!
You don't need to run this, if you're happy with your current setup that's great. It's probably worth reading this thoough:
Originally Posted by MRDOCA
PS3: The payload mess… « KaKaRoTo's Blog
as you might find some benefits from moving to the PL3 payload.
Hope this helps.
Wow, that was fast, Kakaroto, thanks. And thanks for giving me the offset, you never know when it might come in useful. I have always liked the idea of what you're trying to do -- standardize things so everyone's not running around reinventing the wheel, though I'll admit I was frustrated initially when I couldn't figure out how to use it with my TI. I get the syscall_35 thing too. It's cleaner, more flexible, there's no more need to crack it, and it clears a major legal hurdle with the payload no longer being directly responsible for the enabling of backups (the one thing that is really going to land PSJailbreak in hot water, aside from failing to obfuscate the source of the BM). In short, that kills so many birds with one stone it's not funny. I like the way you think.
I'll test this in my TI, assuming all goes well, I'll put up some 8xv files for you TI users (assuming someone else doesn't beat me to it).
I'll tell you people who are confused on how to implement this what you need to know, though it's not as quick and dirty as the "port1_config_descriptor.bin" trick you're used to, so you may not like it. OK, first off, to use a PL3 payload with the TI or anything else that uses PSGroove, you need the PSGroove header, so just copy the first 32 bytes from any "port1_config_descriptor.bin" file you have laying around, or start at the "09 02" and select the next 32 bytes in any existing 8xv file you have, and copy those 32 bytes to a new file called header.bin. Next step, download and compile PL3 (I suggest using evilsperm's VM -- unrar the zip, copy to stick drive, mount stick drive in the VM via the USB icon at the bottom of the window, copy PL3 folder to desktop, navigate to folder in terminal, type "make all"). Now, PL3 supports multiple firmwares, so there's a payload for each, named default_payload_3_xx.bin, where xx is the corresponding minor firmware revision that matches what you're using (in my case, default_payload_3_15.bin). So, copy the one you need back over to the stick drive, then disconnect the stick drive from the VM (same USB icon, just click the device again) and copy your payload file from the stick over to the folder containing header.bin (note, you may have to remove and reinsert the stick drive to get the host OS to recognize it again). If you're using a TI, you should have to8xv in this folder as well. Now open a command prompt in that folder (or just use TC's command line) and type "cmd /c copy/b header.bin+default_payload_3_xx.bin 3xxPL3.bin" and you have your .bin file. Now, if it's not 3840 bytes, you'll need to pad it (if you're using a TI anyway, you need to). The easiest way to do this would be to download resize.com, and if you're using a 64-bit OS, you'll also need MS-DOS Player to run it (google them). Put both resize.com and msdos.exe in your C:\Windows\system32 folder so they're in your path, then type at your command prompt or TC "msdos resize 3840 3xxPL3.bin" and now it will be the correct size. Just follow that up with "to8xv 3xxPL3.bin 3xxPL3" to create your 8xv if you're using this with a TI (replace xx with whatever minor revision you're using of course).
Olimex Boards are 8Mhz, but all the compiled hexes are for 16Mhz?
Also, could someone point me to the source code of this latest payload?
Thanks for this KakaRoto, to clarify for the rest of the users, the BD emulation is disabled in the source, search for "/dev_xxxx" (and you'll see). This i believe is by far the best port around here, not the Hermes mess with the payload. If you can't get it working its your own fault.
Originally Posted by Kratos77
thanks for the mini guide, do you have the source for the v2 of PL3? I'd like to try a port to HTC Magic
Works well, so, as I said, here's a link to the TI-84 files and compiled binaries of the default payloads for those who need them. Also included are the compatibility files originally uploaded by ihaveit (nothing has changed there, as far as I know, they work anyway, that's what matters). And I also included the header.bin, msdos.exe, and resize.com, everything you might possibly need in order to help you out with how I put these together. So, get it here.
The latest source is here -- that's actually a link for his psgroove port, but you'll notice there's a symlink to PL3 under it, just click it and it will take you there. Then just hit the download button at the top right.
@ceckin: I noticed no such disabling of backups. Probably just a setting he forgot to remove from earlier versions, but there's no code for either enabling or disabling backups in the payload anymore. That's what this entire syscall_35 move was about, removing the need for the the payload to enable backups, the app can use whatever it wants now, without the payload having to define it first. I compiled it as is. Works fine with Gaia r7, updated 3D Dot Game Heroes and played it just fine. So, I wouldn't worry about changing it. Apparently it doesn't matter anymore. Have a look at the compiled payloads, there's no "PSFreedom" text for you to change to "dev_bdvd/" anymore. There's no paths defined at all, because with syscall_35 it's not needed. And while this is the only one I can try because Hermes only supports 3.41 and I use 3.15, so I can't objectively compare the two, I must admit that Kakaroto's work looks far more professional. I can say it's working well for me anyway.
Can you elaborate on this please? I Just pulled & compiled the latest hex... so it doesn't allow backups? (same as psgroove).... can you tell me what & where to patch?
Originally Posted by ceckin
Originally Posted by jtanner
I just flashed my blackcat with the latest hex from KaKaRoTo.
But you can't play games with it, the BM runs and it shows the games, but as soon as you hit the X to select the game, the BM/PS3 freezes and needs a hard reset.
I use the latest manager from Dean which is compatible with kakaroto's hex.
With the same setup and the fixed/patched/modified hex
on my Teensy 2.0 it works fine.
I don't think it's a relevant setting anymore, just one he forgot to remove. The point of this is to not need to enable anything in the payload, and give the apps the power to use whatever they want to. Seems to work, I didn't change anything and Gaia r7 is working, with updates, just fine. So, before you go looking for something that "needs" changing, just try it and see if it works first. It's probably fine.
Originally Posted by jtanner