The above video goes away if you are a member and logged in, so log in now!
|
| |
Would you like to get all the new info from PSX-Scene in your email each day?
| |
|
-
10-07-2010,02:37 AM
Wow, talk about a quick fix. I'm not surprised the backups on that first payload didn't work by default. Had a look at the 8xv file in hex and noticed he was using a different "magic number"
I was about to copy the payload to a new file, change the magic number, and run to8xv on it, but I checked back and you guys had beat me to it. Thanks Brandon and oldcripple.
And no, Ex-Cyber, that does not look like gibberish to me, I'm genuinely computer literate (I understand your reason for saying that though, there aren't many of us left). I've been a "power user" since BEFORE Windows 95 came out (and nearly destroyed the PC game market with it's lock-ups and BSODs -- even the "hard-core" PC gamers bought a PSX). I'm not exactly a Linux guru (I've mainly just used user-friendly Debian-based distros like Kubuntu, nothing like Slackware), but I've been a DOS god for over a decade. Anyway, thanks for the instructions, I'll try them out next payload. I'm sure I've got those installed somewhere (they have to be in the SDK VM if nothing else).
-
10-07-2010,03:06 AM
thanks for the clarificatin on device 6 Mr. Ombra & Mr. Wilson...
oddly enough, the original payload was fine except for the whole 'PSFreedom' instead of '/dev_bdvd' thing...thats all we changed
-
10-07-2010,10:38 AM
Hey oldcripple, I know a BM enabled v0.5 was posted alongside all the hermes payloads earlier but has the standalone default payload (PSGroove 1.1 w/BM Enabled for 3.41) been posted at all (For completionist's sake that is)?
Having to edit and recompile a new version of the TI-84 app just for Groove 1.1 w/backup manager support once it is released (like v0.6 for example) can become a pain when I can just have the AppVar payload.
-
10-07-2010,11:10 AM

Originally Posted by
oldcripple
Alright people,
Thanks to Ombra for his indispensable help and PSP0327 for his
willingness to be a PS3 lab rat...we finally got a Backup Manager version of the
3.15 payload provided by Mr.Wilson (to whom many first born are owed

).
Get it while its hot!
edit:for some reason i will figure out soon(i hope) you need to disable device 6 to not get nag screens about unknown USB devices
Thank you so much for this. Been looking all over for a working 3.15 payload. Which features are in it? Is it based on one of the Hermes releases or is it more vanilla psgroove?
-
10-07-2010,11:15 AM

Originally Posted by
jungelpunk
Hmm. I'm having some serious problems trying to get my Ti84 to play nice with my PS3 on fw 3.15.
I'm assuming that the file you've attached is supposed to work as a fw compatibility file on the Ti app. But what do you use as a payload? If I use the default payload or the defualt HERMES v1 or 3 payload that is floating around both my calculator and my PS3 crashes when the app reaches "P5WaitDisconn".
I have set payload to defualt. I have set S1FW315.8xv as the fw compatibility file. I have no stage 2 payload. I have tried with Device 6 both enabled and disabled.
What more can I do?
I am able to perfectly fine JB another PS3 running fw 3.41. It is just I can't seem to get this to work on my fw 3.15 PS3.
that file is the same file that was supplied by Mr. Wilson only its patched for BM support....nothing else...thats all...no more
you have to select that payload as stage 1...its working on at least 2 other peoples 3.15 ps3...pm me if youre getting frustrated and ill walk you through it
-
10-07-2010,11:21 AM

Originally Posted by
ILLPLEASA
Hey oldcripple, I know a BM enabled v0.5 was posted alongside all the hermes payloads earlier but has the standalone default payload (PSGroove 1.1 w/BM Enabled for 3.41) been posted at all (For completionist's sake that is)?
Having to edit and recompile a new version of the TI-84 app just for Groove 1.1 w/backup manager support once it is released (like v0.6 for example) can become a pain when I can just have the AppVar payload.

It never even occurred to me to do that
...good idea...ill start it up...
give me a little bit as i just woke up (i know i know, at 11 am, what a bum)
-
10-07-2010,12:48 PM

Originally Posted by
oldcripple
that file is the same file that was supplied by Mr. Wilson only its patched for BM support....nothing else...thats all...no more
you have to select that payload as stage 1...its working on at least 2 other peoples 3.15 ps3...pm me if youre getting frustrated and ill walk you through it
I eventually tried what you're suggesting on my own and was quite pleased that it did work on my 3.15 ps3. thx for the file
But, are you saying that the compatibility file and the payload is basically the same file. So if you wanted to run this on 3.15 without BM support then you'd basically just use the FWC315.8xv file as both payload and compatibility file? Just curious.
Anyway, any chance we could get some of the Hermes patches ported to 3.15? Would be kinda sweet and the new V3 is supposed to be mandatory for the new OM's that are released.
-
10-07-2010,01:18 PM

Originally Posted by
jungelpunk
I eventually tried what you're suggesting on my own and was quite pleased that it did work on my 3.15 ps3. thx for the file
But, are you saying that the compatibility file and the payload is basically the same file. So if you wanted to run this on 3.15 without BM support then you'd basically just use the FWC315.8xv file as both payload and compatibility file? Just curious.
Anyway, any chance we could get some of the Hermes patches ported to 3.15? Would be kinda sweet and the new V3 is supposed to be mandatory for the new OM's that are released.
The compat file wholly different from the payload...the compat file is overwriting Dev4Desc3 and jigResponse...thats all
if you dont want Backup support youd use the original payload that Mr. Wilson posted instead of the one i posted...
ombra and I are looking in to porting HERMES...but....
i HATE payloads soooo bad...if Jesus came down and asked if id rather be punched in the dick for all eternity or mess around with trying to port payloads for a week...id pick the first option
just one mans opinion...in a sea of opinions...
-
10-07-2010,01:20 PM
The payload and compatibility AppVars are very different.
The "stage 1" payload is the device 1 configuration descriptor. Contained within it is the PowerPC code that the exploit actually sends and executes. This contains the code that enables backup support, adds "Install Package Files", and all the other good stuff.
The "stage 2" payload is for AsbestOS' use only, its stage 1 payload requests stage 2 in pieces and then executes it.
The "firmware compatibility" AppVar is a group of overrides for other pieces of the jailbreak, namely other device descriptors (and the jig response) that change slightly when you jailbreak against another firmware version. It's necessary to specify those changes somewhere, so that's what this is.
So most people just need a "stage 1" payload, and if they're working against something other than firmware 3.41, then they also need a "firmware compatibility" AppVar.
-
10-07-2010,06:08 PM
Hey guys...another update,
Ombra and I have pieced together a port of a Hermes based payload for 3.15...
it will let you run Backups with no disc in the drive... that's what is important about it
Get it while its hot!
http://rapidshare.com/files/423600757/KOKO315.8xv
works on the .006 release of Mr. Wilsons program...its a stage 1 payload, BTW 
i will be posting the default payload as an appvar as well so people dont have to recompile Mr Wilsons source to enable BDVD support on 3.41 FWs
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|