Threaded Mode | Linear Mode

vinnydisilvio · 28/09/2009 02:59 PM

ok. it's been a long time since I've been on EP. I'm glad to see that it's still alive and well and that the most reliable people from back in the day are still here.

the reason i mention i haven't been here in a while is because i don't know if this post will be against the TOS, but i have to try.

hex editing in order to lower firmware version requirements of software used to be very easy. for example, let's just say that i would do it if i wanted to try a new demo without upgrading to the latest Sony FW ;-)

however, it's not as simple as it used to be. if someone out there knows how to do this and you don't want to expose yourself by posting publically, please PM me. however, if you want to reply to this thread please do that instead. I've tried looking for the version number in the item I'm editing and it's not there (at least not in an obvious way).

and if this post breaks the TOS, please don't ban me. a simple "that's against the EP rules" will do, and i will never ask again.

thanks!

.:ʕΘЯg@nʔ:.™ · 28/09/2009 03:02 PM

your looking for a KD hack , or even just edit the ISO it's self .

vinnydisilvio · 28/09/2009 03:04 PM

.:ʕΘЯg@nʔ:.? Wrote:your looking for a KD hack , or even just edit the ISO it's self .

hmmm. yeah...that's what I'm trying to do. it's frustrating though because i can no longer find what part of the ISO to edit. like where would i lower the version number? it used to be that simple...in the opening lines would be a version number and you could change it.

also, I've never heard of a KD hack. what is that?

InfinitiProject · 28/09/2009 03:32 PM

KD hack is tinkering around with the KD folder located in flash0 on the PSP I believe.

Sony smartened up, caught on to what users were doing, plugging up bypasses and holes in both firmwares and games.

SchmilK · 28/09/2009 04:59 PM

5.55 umd are different than ever before. In this and newer firmware required games, the eboot.bin is encrypted and the boot.bin is a dummy file.

The only way to decrypt the eboot.bin is using firmware of 5.55+ which has the proper decryption keys...now what my meager mind would think, if there is a way to decrypt eboot.bin, then use that file to replace the dummy boot.bin maybe then it would run? But how the hell that is done, I have no idea. :( Sony has become very much against custom firmware and the benefits of ripping games to memory stick :(

S7* · 28/09/2009 05:12 PM

SchmilK Wrote:The only way to decrypt the eboot.bin is using firmware of 5.55+ which has the proper decryption keys...now what my meager mind would think, if there is a way to decrypt eboot.bin, then use that file to replace the dummy boot.bin maybe then it would run? But how the hell that is done, I have no idea. :(

Finding it in a Memory Dump after soft decrytion would do it... I think.

Problem is trying to be able to get a dumper or something like that to run after its been decrypted.. and that's after wee find a way to run newer PRXes or DevHook-like system to fiddle with the OFW.

vinnydisilvio · 28/09/2009 05:34 PM

thanks for the replies folks. i don't know how to do most of what was suggested, but hopefully this stuff will inspire those who do :)

any other thoughts on this? is it easier than it seems? I'm on 5.00 M33-6. trying to avoid going to non-M33 FWs that may not even solve the problem as the software I'm trying to bend to my will came out after 6.00 so it may require higher than 5.5...

Joom · 28/09/2009 05:38 PM

My only input on this is to wait for a new CFW.... :-\

vinnydisilvio · 28/09/2009 06:45 PM

Joomla12 Wrote:My only input on this is to wait for a new CFW.... :-\

haha...you see, i already arrived at the possibility that your suggestion may be the only conclusion. this is just what I'm doing until it arrives. as far as I'm concerned: who knows, maybe some of the brilliant people at EP can help me solve this before the new CFW comes out.

wee all know that new CFWs can take a while sometimes...at least the good ones can :)

vinnydisilvio · 28/09/2009 08:30 PM

well, wee all knew they were doing something differently. i just confirmed that it's something different in addition to previous firmware checks...

downloaded the peace walker demo from IGN. tried running it without any editing. the gameboot didn't even load...instead i got the message that i needed at least Sony OFW 5.51 in order to run the demo.

so i went into the EBOOT and found the firmware check (!). in the opening lines of the file there is a very clear "551" string. changed it to 500. replaced the old eboot with my new one and...GAMEBOOT LOADS. then, heartbreak: still getting the error after the gameboot plays "The game could not be started". 2 firmware checks? guess it's easier to add a layer of security rather than to fix the old one :-P

Threaded Mode \| Linear Mode hex editing firmware requirements
Author	Message