Validating dump files after E3 flasher
I have succesfully installed a e3 flasher onto my nor chip inside my ps3 slim, but i got a weird situation here.
I updated the e3 flasher with the update (ps3 dev wiki), I made a dump of my nor file. I extracted it with flowrebuilder. Still no problem here. But when I checked the bootldr file it seemed to be empty. I repeated the process 2 more times, and every time i got the same results. No data in the bootldr file. I decided to do another update on the e3 flasher now using the samung file. again I extracted the nor dump and this time I did get data in the bootldr file. But here comes the weird part.
I have the ps3 slim mode with datacode 0D on the back of my ps3. When I validate the dump files it seems that my nor chip is from the 0C datacode. Validating flash dumps on ps3 dev wiki
the most odd thing is that the bootldr size does not match. For a 0C datacode it should be 2F4F0, but my result says 2F4D0. The rest of the data is correct (metldr and bootldr offsets - except the bootldr size).
I am kinda afraid to contine with flashing the nor file. I was however not able to do a 2nd/3th process with the same updated (samsung) e3 flasher because it now gives a errorcode 10001100 Failed to initialize PS3 BIOS Check pads / clip at PS3 board check may not be properly seated. I have only reset the ps3 without slamming it onto the ground or something so i dont realy understand why he cant make a new dump. I will try this again tomorrow.
My dumpfiles are from datacode 0C, but my ps3 slim says its from 0D. The datacode on the back is a sticker though, is it possible that while production my ps3 got a diffrent sticker?
All the dumpfiles are correct metldr offset: E9 20 and 0E 8E, bootldr size: 2F4F0, offset 2F 4B and 2F 4B, except the size of the bootldr (which is 2F4D0 in my case)