Today Spanish PS3 homebrew developer Estwald
has updated the COSPKG and COSUnPKG PlayStation 3 CORE OS PS3Tools originally released by Sven Peter
of Fail0verflow attempting to fix some of the prevailing bugs.
Download: PS3 Fail0verflow CORE OS PS3Tools COSPKG and COSUnPKG Updated
/ PS3 Fail0verflow CORE OS PS3Tools COSPKG and COSUnPKG Updated
(Mirror) / CYGDLLs
(Required cygwin1.dll, cygz.dll, and cyggcc_s-1.dll)
Below is a rough translation, as follows with a better one HERE
courtesy of daveribz
: Hello, when the team fail0verflow published his tools, it was clear that not all were functional, or lack of certain bugs. Waninkoko had the "honor" to check in their own flesh (unfortunately) when your CFW few bricks caused due to incorrect operation of certain tools.
Recently brought new CFW that apparently have the same problem when composing the CORE OS package (and at least I could check in on Rogero cospkg being used ...) and honestly, but I'm fine in 3.41 the time and I have no intention of returning to the scene of PS3, say you had some obligation "moral" and here is the reason for the thread and the application (well, I have no desire for it tomorrow if I install a CFW these new, I enladrille console for CORE OS raruno
) Extracting CORE OS
After unpacking the. Pup and extracted content. Unpkg tar utility to unpack the CORE OS can this:
unpkg 341firm/CORE_OS_PACKAGE.pkg 341firm/cos
This will generate 3 files in the folder "cos": info0, info1 and content
The content of "content" is extracted by the utility cosunpkg this:
cosunpkg 341firm/cos/content 341firm/cos/files
Now inside the folder "cos" have the folder "files" where we proceed by example, to patch lv1 or lv2.
However, once patched, we proceed to repackage the CORE OS and this is where the problems begin.
When introduced its CFW 3.55 flukes1 I noticed that in your python program was more or less what I have shown, but then proceeded to patch the "content" original with new content instead of using the utility "cospkg" . So I did the same with the CFW 341 and as we saw, there were bricks on consoles for that reason.
This technique has a drawback: the modified self, not to exceed in size to the original, because we fit them into the "hole" of the ancients. The advantage is that it respects the order of the files and the original lineup (why should the ordinary cospkg discard), but what happens if for some reason we get files with a size greater than the original?
Well, we have no choice but to fix utilities and cosunpkg cospkg to generate the "content" exactly as you would the original.
To do this I proceeded with several official firmwares to try and test the results, obviously, if I extract the content and recompose just like, I get the same data (both files are the same) and the number of firmwares used to view little peculiarities and exceptions that serve to determine how to proceed correctly (without failure a utility FIRMS with different nuances, indicates that we are on track)
The utility "cosunpkg" attached, works just like the original that generates a file called "list.txt" contains the number of entries and the list of files in the order of "content".
The utility "cospkg" generated "content" with the list and applies the corresponding alignment based on the observation of the following test firmwares I've used: 1.02, 3.15, 3.41, 3.50, 3.55 ancients and moderns 4.21, 4.25, 4.30 (A small detection based on the name of some important files)
To package would proceed as follows:
cospkg 341firm/cos/content 341firm/cos/files
If the original desempaquetaramos empaquetaramos in "Content2" without having changed anything, no difference should be compared in any of the cases and that is what I have seen with these firmwares and the methodology used.
That if, as I have no flasher, no interest in making a CFW, or consoles that risk, I can not guarantee that if you change the content otherwise may fail. In principle, it should not, but I would not put my hand in the fire and guess who is going to create a CFW has the means and knowledge to perform and can reverse the errors by flasher.
So Use it responsibly and understand that although the original files generated correctly, that the changes can not, if you change sizes, or has some other problem you have to fix utility (that may be a fault occur in addition, obviously, to generate either the pkg, tar or pup)
Deputy: the sources cosunpkg.cy cospkg.c ps3tools modified and executables compiled for Cygwin. I hope you find it useful and please refrain from using such applications unless you know what you're doing or do not have possibility to fix a potential problem.
Ah! and do not understand one iota of what I'm saying, you can save the questions do not apply equally
More PlayStation 3 News