3.50 Retail Update for Brink Question

Well, more about the nature of the update, than the update itself. This has obviously been asked a thousand times, but nobody has answered it yet. If this was just providing a 3.50 EBOOT file that was stupidly slipped in, and that makes it work, I have a question. Would it be possible to unpack a Portal 2 update (if there's been one..?) and slip in a 3.50/3.55 EBOOT file and see if that works?

I know nothing of the keys and 3.60 protection/encryption and all that, so I probably seem like a helpless noob to those who have more knowledge than me, but hell, everyone learns somehow, eh? Anyways, just a thought that I've seen floating around.

Ok, clarified via PM.

You can create PKG files, including PKG updates, but it still won't do any good without the EBOOT in the first place. There's currently no update for Portal 2, so there's no way of knowing if the update will be 3.5x based or 3.6. Brink, MK9, Motorstorm Apocalypse ... all those have updates that lower the FW to 3.5x. You can't use one of those EBOOT.BIN files in any other game as they are, essentially, the same as PC game EXEs or Xbox's XBEs.

So, quick question, what does that update pkg contain? Essentially what I mean is HOW does it make the firmware requirement lower? Do we know, and can we recreate this?

(Ah, figured out what I was trying to say and the problem with it.) EDIT:
You can't make an apple tree out of an orange seed. The WHOLE GAME is running with the encryption of the EBOOT, so everything about it runs on 3.60. Though, my question on this post still stands, could we recreate it?

It's not the update "per se" it's the EBOOT within. The reason why some EBOOTs from updates have lower FW reqs is down to the developer in question; they may not have signed their updates with the 3.6x SDK. The thing is, you can't modify update EBOOTs as they are encrypted with NPDRM.

Question unrelated:
What's the difference between a retail update and a debug update?

Also, knowing Valve, and the fact that they KNOW how huge Portal 2 is, they're probably going to be smart enough to sign the update with the 3.60 SDK. Bethesda still isn't that huge, and Brink wasn't that hyped.

Retail updates are the standard ones, the ones everyone gets when you load the game. Debug updates are for developers only, for testing their release before it gets put out for the public. The best thing is that debug updates AREN'T signed with NPDRM, which means you can modify them and alter the FW reqs - usually. Sadly they're few and far between (Sony shutdown direct access to them after the PSN game debacle, where everyone was using debug updates to steal full PSN games)

Hopefully Portal 2 updates will be 3.55 or less... If it's 3.56 we can add 3.56 keys to 3.55.
If you look at the Portal 2 eboot, you'll notice it was built with the 3.50 sdk, really hoping the updates are signed with those keys...

Quote:

---

Originally Posted by cookie42

Hopefully Portal 2 updates will be 3.55 or less... If it's 3.56 we can add 3.56 keys to 3.55.
If you look at the Portal 2 eboot, you'll notice it was built with the 3.50 sdk, really hoping the updates are signed with those keys...

---

Aye, that's the killer.. you check it out and find the EBOOT itself was built with 3.50 -- but then signed AFTERWARDS with 3.60. Lame.

People were getting these by way of Rebug, I'm guessing?

Sounds to me like Sony really shot themselves in the foot when they started suing everyone and their mother. Everyone decided to start hacking, when they probably wouldn't have heard about it in the first place otherwise. Nice going, Sony? :crazy:

Nah, it was nothing to do with Rebug. Before the PSN-game stuff, you could directly search the debug servers for updates -- Sony then locked that out. This was WAY before Rebug.