The above video goes away if you are a member and logged in, so log in now!
IIRC The reason 3.60 games dont work is because the games eboot.bin requires the 3.60 firmware.
Originally Posted by Rautz
This updates has a new eboot.bin however it only requires 3.55
Looks like sony dun goofed.
Originally Posted by L0YD
Holy sh*t this could be a potentially big step if it isn't just something that the Brink developers messed up.
How is this possible?
Edit: Ahhh this is because a debug update with a eboot.bin 3.50. If the update isn't <3.55 it wont work.-
I do not have a copy of portal 2, but here is an idea. Download an update, extract the update. Try to change the info from 3.60 to 3.55 (If that is possible, I do not know ?), and repack it.
The retail update contains a 3.5 eboot thats all. No amount of analysis is going to help people run other 3.6 games! We have been here before.....
yep, just Brink was lucky...
Simple luck, that the update is out and it requires FW 3.50 to run.
Cant analize theese as its a RETAIL update, encrypted with NPDRM keys...
Now if this would be a DEBUG update, it could be "decrypted" (nothing to decrypt really) edited for ANY FW. So FW 3.41 JB users are out of luck. Still no reason for me to upgrade. My dongle is just so damn sexy.
Last edited by Hissatsu; 05-09-2011 at 11:36 PM.
Reason: Little bit of this, and that....
There's quite a bit that's not encrypted. I bet npdrm selfs still have the normal self header with an offset to the app_info which tells the loader that it's npdrm and what keys it's decrypted with. It should be an easy check to see if they just encrypted it with the wrong keys.
Sweet this is awesome! So now I can test it before my PC version unlocks tomorrow!