(adsbygoogle = window.adsbygoogle || []).push({}); Hey guys, I need some help from a dev. I recently unpacked the 3.60 update with fail0verflow's tools and need help to further unpack it to be able to look at it. Here is what I know so far:

1. How to use pupunpack and fail0verflow's tools on Linux
2. I have extracted update_files.tar into a folder named Update Files
3. Sony has changed their encryption method on the private keys, so fail0verflow's formula no longer works.

What I would like to learn:

1. How to fully unpack, mod, then sign a CFW
2. Where the keys are located (all of them) so we can decrypt them


I am familiar with VB.NET, C++ and C# and am willing to learn about these updates. I would greatly appreciate it if someone were to PM me and help me out. Thanks so much guys.

********************
NO FLAMING PLEASE
********************

"unpkg {pkg file name} {output folder}" <--- That unpacks the update files like the ones named .aa.{some date}
"pkg {input folder} {output filename}" <--- That repacks the unpackaged files

Thanks soo much dude. You guys all rock +Repped you all. Btw, what is the difference between s debug pkg and retail pkg? I am assusming debug is not signed, retail is? Thanks soo much guys.

yes, debug is not signed but it is also not compressed...
retail is signed and compressed...

Thanks so much dude

your welcome

Got the dev_flash_000.tar.aa unpacked into a file called "unpkg.exe.stackdump" What do I do with that file? Any help will be greatly appreciated!

UPDATE

I think I worked out the error. When I try to use fail0verflow's tools to unpack a .pkg under the update files in the update, I get 2 errors:

no key found
perror: No such file or directory

So, I am assuming this means I need the ps3 keys before fully unpacking this update to mod it? :mad: