[hellsing9]

Hello pals.

When fail0verflow published his tools was evident that not all of were functional neither certain bugs free. Wanikoko had the *Honor* to check this on his own (sadly) when his CFW caused a few bricks because erratic functionality of certain tools.

Recently we saw many new CFW'S that at simple sight share the same problem while compiling CORE OS pkg (and at least i checked that in Rogero's one *cospkg* is being used) and honestly even if im ok in 3.41 for the time being and i have no intention at all to come back to the PS3 scene.
Let's say i had some *moral obligation* and here you have it's this thread and the app (besides, i don't want if tomorrow i install some CFW of this news lead me to a brick because a faulty CORE OS).

Extracting CORE OS:

Once decompressed the .pup and extracted the .tat content with : unpkg. We can dump CORE OS this way:

unpkg 341firm/CORE_OS_PACKAGE.pkg 341firm/cos

This will generate 3 files on "cos" folder: info0, info1 and content.

In order to extract *content* data you have to use = cosunkpg this way:

cosunpkg 341firm/cos/content 341firm/cos/files

Now we have inside *cos* folder another folder called *files* where we will can patch lv1 or lv2.

Well once patched we have to proceed to repack CORE OS and HERE is where problems start to kick in.

When flukes1 presented his CFW 3.55 something catched my attention that in his own python program performed more or less i showed you so far but later continued to patch the original *content* with the new content instead of use "coskpg" utility. So i've done the same with CFW 341 and as you can see = No Bricks because of that factual *human error*.

This technic has a FLAW: modified selfs don't have to have bigger (in size) than the original ones because we have to *fit* them in that *gap* where the old ones reside. The advance of this that respects the files order and the originals alignment. (One motive why we have to get rid from the *normal* cospkg) But..what happens if for some reason we have to insert files with a size bigger than the original?

Well the only *remedy* for this that fix the utilities cospkg and cosunpkg so they can generate "content" the same way as the original.

For that i tested with many official firmwares and check the results but obviously, if i extract the content and repack the same way i have to obtain the same results. (two files will be the same) and the firmware numbers used allow us to see some *oddities* and exceptions that is useful to us in order to find out how to proceed correctly. (An utility without fails on the firms it's a good sign that we are on the right path).

The utility "consunpkg" that i attached, works the same as the original only difference this one generates a files called "list.txt" that contains entry numbers and file list as well in "content" order.

The utility "cospkg" generates "content" with the list and applies the correspondent (or correct) alignment by seeing carefully the next firmwares that i tested with: 1.02, 3.15, 3.41, 3.50, 3.55 old and the newer ones 4.21, 4.25, 4.30 (performs a little detection check about the name of some important files).

In order to make the package we have to do this:

cospkg 341firm/cos/content 341firm/cos/files

If we unpkg the original and *package* in "content2" without done any modification, when we compare there will be NO DIFFERENCE on both cases and that's what i learned with those firmwares and the *technique* i used to perfom this. I don't have a *flasher* neither the interest to make a CFW or a PS3 to risk it, tough i cannot make sure that if the content is modified in other way, well can fail.
I should not saying or posting this but i will not risk my reputation for anyone (so pretty much you are on your own) and i can think that the one who gonna create a CFW has all the tools as well knowledge to make it happen, reverting possible errors with a hardware flasher.

So use it carefully and responsable and understand that even original files gets generated correctly, maybe the modifications NOT. If sizes are modified or some problem with utility that needs to be fixed. (because can happen that some problem on other place, obviously when generating the .pkg, tar or the .pup)


===============================

Translation made by me = Hellsing9

Download = Click (Mirrored the files just in case)

Source = EOL

[haxxxen]

nevermind. just wanted to say, you can easily and safely replace coreos files with ps3mfw builder. i have done this several times now and as long as selfs are legit, there will be no problems

[hellsing9]

Originally Posted by haxxxen nevermind. just wanted to say, you can easily and safely replace coreos files with ps3mfw builder. i have done this several times now and as long as selfs are legit, there will be no problems

It's Hermes talk about the subject, i only translated from spanish to english what he had to say about the matter.
Since many are talking now because of the tidal waves of new *CFW'S*.

I think is late talk, rather keep researching than doing this..but well was his call not mine.

[nicknewbie]

I just unpacked and used your new unpkg and it doesnt work. I unpacked 4.21 pup and I get this error.

Exception: STATUS_ACCESS_VIOLATION at eip=00402EC9
eax=00000000 ebx=00000000 ecx=00000000 edx=00000002 esi=00000000 edi=00000000
ebp=0028CBD8 esp=0028CB30 program=C:\Users\N00blet\Desktop\New folder (3)\unpkg.exe, pid 3420, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CBD8 00402EC9 (7EA20000, 00000000, 00000000, 00000010)
0028CCA8 00401428 (0028CD28, 000001FF, 00000000, 0028CCE0)
0028CCC8 004016DF (0028CD02, 61179FC3, 0028CD58, 61006CD3)
0028CD58 61006CD3 (00000000, 0028CD94, 61006570, 7EFDE000)
End of stack trace

[hellsing9]

Originally Posted by nicknewbie I just unpacked and used your new unpkg and it doesnt work. I unpacked 4.21 pup and I get this error. Exception: STATUS_ACCESS_VIOLATION at eip=00402EC9 eax=00000000 ebx=00000000 ecx=00000000 edx=00000002 esi=00000000 edi=00000000 ebp=0028CBD8 esp=0028CB30 program=C:\Users\N00blet\Desktop\New folder (3)\unpkg.exe, pid 3420, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args 0028CBD8 00402EC9 (7EA20000, 00000000, 00000000, 00000010) 0028CCA8 00401428 (0028CD28, 000001FF, 00000000, 0028CCE0) 0028CCC8 004016DF (0028CD02, 61179FC3, 0028CD58, 61006CD3) 0028CD58 61006CD3 (00000000, 0028CD94, 61006570, 7EFDE000) End of stack trace

http://gaoithe.blogspot.com.ar/2011/...-windows7.html

It's a problem with cygwin.

[baargle]

Interesting, but surely an md5 checksum of the repackaged original files (just extract then repackage) would tell straight away if the utility worked.

...Of course not for modified files. But that again wouldn't be too hard doing a hex compare at various points between where the different file is expected to be different and so on.

...Ahhh I'm probs talking crap but heyho.

[ortis123]

HELLSING9 you can remove hermes M.I.A tag from trusted dev's thread

good to hear hermes speaking again
appreciate everything he has done for ps3scene

[hellsing9]

Originally Posted by ortis123 HELLSING9 you can remove hermes M.I.A tag from trusted dev's thread good to hear hermes speaking again appreciate everything he has done for ps3scene

Still M.I.A he appeared only to say this.

[GregoryRasputin]

Wow at all the big guys coming back to speak of this new hack...

[hellsing9]

Originally Posted by GregoryRasputin Wow at all the big guys coming back to speak of this new hack...

Someone made some kind of sorcery to make all them speak their minds..