Well this took some time but we have it sorted out, CJPC posted a while back ago that an eboot.bin had been decypted from memory. The bad thing about this is that it is verry difficult to figure out how the file was before it was loaded and to put it back to an executalbe file. Well after HRS and sleepless nights this has been sorted and put in an easy to do map. The following is an example of the the file location offsets located in the elf header. Based on this the file can be rebuilt in a matter of mins.
Note: This is just an example of how it could be done the memory offset loactions can change a bit from file to file so one would have to double check there mem dump for sections if the offset table does not match up but this map was used on 3 differnt eboot.bin's so far hope this explains it a bit for ya.
This is not a attack but i mean you dont understand. Becouse every success on a dev ps3 will be also a seccuss for the retail ps3. So in case the retail con are good secured they have no chanche to study the ps3 and learn more about here internals.
So even if this is not the success that you and the whole community will wait for it will be a big step in hacking the ps3. And dont forget that the hardware of dev and retail cons are quit the same.