(adsbygoogle = window.adsbygoogle || []).push({}); Couldn't see this anywhere else, and i don't really think it is of much use.

Nevertheless all of those who have unpacked a pup file have seen the update_flags.txt file in there with '0000' in it. So i decided to try different numbers to see what it did so far then put it into the ps3, i tried:
0000 - Loaded
0001 - Loaded
0010 - Data Corrupted
0100 - Data Corrupted
1000 - Not Found

0011 - Data Corrupted
1100 - Not Found
0110 - Data Corrupted
1010 - Not Found
0101 - Data Corrupted

1110 - Not Found
0111 - Data Corrupted
1111 - Not Found

So i began to try:
0002 - Loaded
Going to try other digits, would like to be able to view inside the package files in update_files.tar but i cannot open them.

Just tried this:
00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000001

still copies to 79% then says data corrupted, i shall still play about but not until i can unpack those package file inside the update_files.tar.

UPDATE:
I never thought to try different update flags in the recovery mode, will try later to night.
I still don't understand why unpacking then instantly repacking the 3.56FW is recognized in a different way?

No difference, from what i have seen.

UPDATE 2:
It does treat it differently but its hard to tell on 3.56, i tried this on 3.55 and it seemed to accept anything but its my only system on 3.55 so i didn't risk losing it. Although i did notice on 3.56 recovery mode it would install the 3.56FW (unchanged) but said everything else was corrupted, even if you have two usb pens one with 3.55 the other with 3.56 it would choose the 3.56 over the 3.55. But if you packed the 3.56 yourself it would choose the pen with 3.55 then say data corrupted.

UPDATE 3 - this section was tested on a 3.55CFW -kmeaw and team blizzard with multiman.:
Right i unpackaged the 3.55OFW and copied all the files into dev/hdd1/ when i turned the ps3 off, it sat there for a long time flashing, which i think it just crashed it BUT there was alot of hard drive accessing going on. Eventually i had to turn it off manually. When i went back to dev/hdd1/ the data had gone. When i changed the boot flags to one of the corrupted flags found above, it kept the data inside it, every time i went back to dev/hdd1/ it was all still there.

Not very helpful i know, does anyone know the point in hdd1, i assumed it was a partition put there by Sony to ensure it always had space to store the update data when flashing it.

Tested on a PS3 - 60GB on 3.56FW, so when i says loaded i mean it got as far as the 79%/85%/99% copying or whatever then said data corrupted. And i am changing the 3.56 FW, but i am not confident it is using the correct key to sign and create it as it should technically say "latest software installed".

Again not totally sure if this is relevant or helpful but just though i would post it, if any information on this is available and i have overlooked it please send me it, i am very eager to understand these files.

yeh read it properly then:
Going to try other digits, would like to be able to view inside the package files in update_files.tar but i cannot open them.

not i cannot open the update_files.tar.

But thanks anyway.