I'm the one that originally posted that. Needs testing, just a theory since those are debug packages. But they are labelled on PS3News as requiring 3.50, so just because they are debugs means nothing.
|
|
|
|
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! | ||
|
|
I'm the one that originally posted that. Needs testing, just a theory since those are debug packages. But they are labelled on PS3News as requiring 3.50, so just because they are debugs means nothing.
Oh okay, I'll credit you then in the first post![]()
Did this really need its own thread considering we have at least 3 threads talking about using updates to bypass a 3.42/3.50 firmware check and 3 more threads talking specifically about Black Ops and how to get it to run?
Well I haven't been logged on long, and I'm not going to be either so I just posted this quickly..
I got the new Bond US region game working by using the euro eboot.bin and editing the ago. Maybe that will work as well. Not worried as I am jtaging this title.
The debug eboots do NOT work, i have the game and the disk
eboot is 57MB large, the t5_ps3mpf.self or whatever is 67MB
The updates are tiny executables theres no way they will work...
This must have something to do with the new "3.50" SDK...
Any ideas?
So there is nobody who got unlimited bandwidth? come on you guys!!! Test it for the scene!!!
//edit\\
the reply above mine was posted during typing... IGNORE MY POST![]()
This eboot won't even try to start, it gives you "wrong eboot" error.
Well since nobody has got COD:MW2 working so far (to my knowlege), is it surprising that this doesn't work?

| « Previous Thread | Next Thread » |