+Audioboxer Subscriber² Posted October 18, 2010 Author Subscriber² Share Posted October 18, 2010 In fact it looks like the game update is indeed what buggered up MoH :laugh: It's simple, really. Retail disk contains an eboot which is encrypted with 3.42+ keys, obviously somewhere down the line they screwed up and released an online update that contains a new eboot.bin that is signed with the older, 3.41- keys. All the "bypass" is doing is allowing the update to be downloaded and installed, (the eboot.bin being from another game doesnt matter, because the game will launch using the patches eboot instead). Now this guide has been released you can bet your life that not only future patches for this game, but future patches for ALL games shipping wuith 3.42 or higher firmwares are going to start using newer keys. They probably can't or wont apply the same rules to patches for older games - only patches with keys up to the firmware versions included on the disks, but who knows. Fact of the matter is, if you can be online to get the game update, you can be online to get the firmware update too. Link to comment Share on other sites More sharing options...
+Audioboxer Subscriber² Posted October 18, 2010 Author Subscriber² Share Posted October 18, 2010 The MOH fix doesn't actually make use of whatever eboot.bin file you put in. The exploit is that the 1.01 update doesn't require 3.42. You can skip half the steps tneeded to get it working by just installing this update.Just: 1) Install MOH 1.01 update (you can download it straight from Sony's servers) 2) Install MOH to Internal drive. 3) Edit param.sfo to allow 3.41. 4) Boot with mempatch on and any disc inserted. How the **** did that update get through certification, PSN monkeys owned themselves there Link to comment Share on other sites More sharing options...
+Audioboxer Subscriber² Posted October 19, 2010 Author Subscriber² Share Posted October 19, 2010 Looks like SDK semantics Nope, they didn't **** up the update.You see MOH really was only complied with SDK v3.30 in the first place. It is same on the original disk, it is complied with SDK v3.30 also. The thing is, at the last minute, they added a check in the eboot.bin to verify the disc and firmware to make it install v3.42, the eboot.bin is linked to normally unused library call module, I might post the full details later, as I have alot of info on this! What we really need is new backup manager, or payload that patchs out that call that the eboot.bin makes on initial startup, it is very easy to do. All this talk about new encrypted keys is bull****, as currently MOH is not using the new SDK at all, even the other games like John Daly are also using an older SDK. The reason why replacing the eboot.bin with one from another game works, is that is does not make the call to check the disc and firmware, so it goes past that step, and then updates itself. But I sure later this week, Sony will re-complied all the online game updates to include this library call, like the original disc does. So we better get cracking and find the patch address to poke, to nop out this call when it happens so it returns the right value, once that is done, it's game over for Sony, until all games are in fact complied with the newer SDK. Link to comment Share on other sites More sharing options...
DrunknMunky Veteran Posted October 19, 2010 Veteran Share Posted October 19, 2010 I'm finally gonna try out a combo of RockBox & my old iPod tonight, see how everything goes. Saves me buying a dev board ;) Link to comment Share on other sites More sharing options...
Recommended Posts