[JustThatDude]

As many of you know we can't use homebrew on 3.56+. Would it be practical to say that it isn't hard after all to get it working. Okay so lets get some things straight here Kaka said he can install .pkg's even hombrew but he can ONLY RUN RETAIL PACKAGES. So what's the problem well the problem is that we can't run homebrew. Maybe we could just create a "invisible wall". Now what this "invisible wall" would do is to well let us run homebrew. The idea is to have that wall distracting the ps3 so that we can get over that it. But how would we be able to this if we don't have any keys and can't sign any packages without keys. Well its simple really all we would need to do is take a retail pkg and have the PS3 focused on that so that it can't see the homebrew.

This is how i theorized it could be done

PS3 looks for a spoofed file(the retail package)
PS3 finds that file
PS3 sees that it is a legit package
PS3 runs that package that is retail
PS3 focuses on that package
PS3 then splits the package leaving only what we need to run homebrew
PS3 looks for rest of the file and finds it
But what it is actually searching for is a spoofed file(homebrew) to recognize it as if it were the other part that we split(retail pkg)


So what i'm saying is to split the retail package then have the PS3 find the other half which is the homebrew but the PS3 won't recognize this as a homebrew and think its the other part of the retail package allowing us to run homebrew


Again just giving some idea's. I just want to help out and share my theories. If you have any improvements to my idea go ahead and improve.

[DEFAULTDNB]

And how do you sign a package containing homebrew for 3.56+ ?

I mean a retail pkg would need to be opened up, homebrew added then resigned no?

Maybe I don't get your meaning of split?

Edit: sounds like a NOP slide?

[devstar]

from my limited understanding the ps3 now checks the hashes of retail packages so would splitting and adding to the file not change the hash making it non retail then it wouldnt install

[JustThatDude]

Originally Posted by DEFAULTDNB And how do you sign a package containing homebrew for 3.56+ ? I mean a retail pkg would need to be opened up, homebrew added then resigned no? Maybe I don't get your meaning of split? Edit: sounds like a NOP slide?

Okay so we take out what isn't needed while the Ps3 is running( the split) then we replace the files that we took out from the split with files from homebrew
And the hombrew the we are injecting is spoofed as the files we took out so that the keys get left there in the process which means that we wouldn't need keys for homebrew we would just need take out some files and keep the leys from the retail pkg there




Also what did you mean by NOP slide

[JustThatDude]

Originally Posted by devstar from my limited understanding the ps3 now checks the hashes of retail packages so would splitting and adding to the file not change the hash making it non retail then it wouldnt install

No cause the ps3 thinks the file we split is still there

[carldenning]

how would u put stuff into a retail eboot cos to close it u would need to sign it ?
how would the eboot from a retail game know how to boot another game when we cant dectpye eboots plus u need the source for the game i guess

[JustThatDude]

Originally Posted by carldenning how would u put stuff into a retail eboot cos to close it u would need to sign it ? how would the eboot from a retail game know how to boot another game when we cant dectpye eboots plus u need the source for the game i guess

Think of it as this. The retail pkg gets signed then we replace the stuff we don't want(someone would have to figure it out) with the ones we do want. This means there wouldn't be any need to having the keys on the hombrew because the keys would be on the console still.

[carldenning]

Originally Posted by JustThatDude Think of it as this. The retail pkg gets signed then we replace the stuff we don't want(someone would have to figure it out) with the ones we do want. This means there wouldn't be any need to having the keys on the hombrew because the keys would be on the console still.

but a eboot from one game wont boot another eboot .

but then again i think i get what u mean , eboot from retail game boots up game but then it boots up a file from the game which has been edited so it boots up the homebrew eboot

[JustThatDude]

Originally Posted by carldenning but a eboot from one game wont boot another eboot . but then again i think i get what u mean , eboot from retail game boots up game but then it boots up a file from the game which has been edited so it boots up the homebrew eboot

Okay what if we modified to where it could and maybe see from there never hurts to try something if it helps put us a step forward

[tjhooker73]

It wouldn't work The spoofed file would need the keys from 3.60+ too.