(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.

Keep TRYING

well, i dont know if what i am trying is relevant at all. i was hoping some devs may have worked it out at some point.

EDIT: Not implying for devs to do it for me!

keep trying, and what i think the goal should be is to have the 3.55 pup and make the ps3 think is 3.56 so the ps3 can "update" to 3.55? that should be the goal. also are you useing fail0verflows tools for windows?

Im using fail-0verflow tools for linux with all the ps3 keys from the github repository.

I agree to use the 3.55.pup but because i'm already on 3.56 id have to figure a way of gettin rid that damn root kit first before going back, but i couldn't even start that until i can get in teh package files of the update_files.tar.

Also if any of you have 3.55CFW with multiMAN u can go to dev/flash(2? i think) and theres a registry file in there (vsh/etc il have to double check) and that ( I THINK ) tell sony what firmware your on so if you could get the 3.56 modify or just copy it straight over then it may think your on 3.56. but agian i cant see it being that easy.

EDIT : /dev/flash/vsh/etc.version.txt press R3 to view it and you will see what i mean but there are other xREgistryfiles in the other flashes to, some contain parental lock information and have not looked at the others. oh and you can copy the file to an external usb but cant copy it back, which i think would have to be changed when the ps3updat.pup does it flashing business.

My other issue is any decent info on this is dated before 3.41 and therefore sony has likely changed some things since then.

Oh and when i try and upkg the files i get this:
[root@localhost fail0verflow_ps3tools_linux]$ ./unpkg UPL.xml.pkg '/home/root/Documents/PS3/EXTRACTED/extracted_356_FW/update_files/update_files/'
open UPL.xml.pkg
perror: No such file or directory

Thanks for the help and interest!

ok thats what i have, it will let me decypt the pups but it wont let me encrypt them, any ideas?

well my setup on linux the keys are in /home/YOURNAME/.ps3
the folder will not appear to be there as any folder with '.' at the beginning makes it hidden, view them by selecting View>Show hidden files or CTRL+H

i open the terminal then go to where the fail0verflow tools are:
cd '/home/Johnathan/Documents/PS3/fail0verflow_ps3tools_linux'
or drag and drop the tool you want to use.

if you used the directory method load your files using ./ example:
./pupunpack FILE_DRIRECTORY/FILENAME.PUP OUTDIRECTORY

So you have unpacked them sucessfully to repack use
./puppack FILENAME.PUP FILE_CONTENTS_DIRECTORY

I assume you already knew this i just wanted to make sure we were on the same page.

When you unpack the pup file make sure you have something relative to this:
sections: 5
hdr size: 00000000_00000190
data size: 00000000_005193a8
header hmac: OK
unpacking version.txt (00000000_00000008 bytes; hmac: OK)...
unpacking license.txt (00000000_00040000 bytes; hmac: OK)...
unpacking ps3swu.self (00000000_0000f860 bytes; hmac: OK)...
unpacking vsh.tar (00000000_00005000 bytes; hmac: OK)...
unpacking update_files.tar (00000000_004c4b40 bytes; hmac: OK)...

make sure the header hmac is OK if its ????? then thats your problem.

I think to solve this download all the keys from the github repository, will post link shortly.
You must login or register to view this content.
select download in the top right and put the keys in .ps3

Noobs weren't meant to use these tools. Haha JK, and yes the flags are useless to us right now. It tells the PS3 what's going on.

Right thank you, i didnt think the devs would overlook it, i just could never find info on it.

oh and i agree noobs shouldn't have these tools lol ( i being one of em )

Have you tried to increment that value instead of changing the 0 and 1? Something like 0001 0002 0003 etc..

I don't know if it could lead to something but thank you for the effort.