PS3 Syscon Replacement

I interrupted eEID, from the old dump, there is no result, does not read ps2 disks.Are there any other solutions to the problem?maybe the command is needed to see the syscon processor from ps2
 
M4j0r said:
That's fine, everything after 0x7400 isn't needed.

That's probably related to the wrong eEID information that's stored on the NAND flash.
You'll have switch your eEID to the one from the original NAND.
For this you need to decrypt the old eEID using the old eid_root_key and then encrypt it with the new eid_root_key, for example with this tool: https://github.com/zecoxao/ps3_decrypt_tools .
Please follow this thread by @zecoxao : https://www.psx-place.com/threads/v...ll-be-used-for-true-cex-dex-conversion.34135/ .
Click to expand...
Everything turned out to be much simpler, it turns out that the SSD in the ps3, if you put it, will not see the ps2 disk.I returned my native hard drive to 60 GB, the PS3 saw the ps2 disk format.But now the problem is different, when you start the black screen, it's probably because I flashed syscon.How to get the firmware back?does anyone have a file?
 
Oleg-ps3 said:
Everything turned out to be much simpler, it turns out that the SSD in the ps3, if you put it, will not see the ps2 disk.I returned my native hard drive to 60 GB, the PS3 saw the ps2 disk format.But now the problem is different, when you start the black screen, it's probably because I flashed syscon.How to get the firmware back?does anyone have a file?
Click to expand...
The problem isn't related to the Syscon EEPROM content, you can't change the firmware on retail Syscons.
 
For the experiment, I flashed another ps3 with a Syscon file.After your file, another ps3 stopped seeing the ps2 format.Is there another file to try?
 
M4j0r said:
The problem isn't related to the Syscon EEPROM content, you can't change the firmware on retail Syscons.
Click to expand...
For the experiment, I flashed another ps3 with a Syscon file.After your file, another ps3 stopped seeing the ps2 format.Is there another file to try?
 
Oleg-ps3 said:
For the experiment, I flashed another ps3 with a Syscon file.After your file, another ps3 stopped seeing the ps2 format.Is there another file to try?
Click to expand...
The file is only meant for a COK-001 board.
If the PS3 doesn't display the error "This model of the PS3™ system is not compatible with PlayStation®2 format software." it's not related to that.
You could also just use the eeprom content from the original syscon which was present on the COK-001 (excluding the area up to 0x2C00).
 
M4j0r said:
The file is only meant for a COK-001 board.
If the PS3 doesn't display the error "This model of the PS3™ system is not compatible with PlayStation®2 format software." it's not related to that.
You could also just use the eeprom content from the original syscon which was present on the COK-001 (excluding the area up to 0x2C00).
Click to expand...
Give me the file then for COK-002, I'll get everything back.
 
M4j0r said:
The file is only meant for a COK-001 board.
If the PS3 doesn't display the error "This model of the PS3™ system is not compatible with PlayStation®2 format software." it's not related to that.
You could also just use the eeprom content from the original syscon which was present on the COK-001 (excluding the area up to 0x2C00).
Click to expand...
I had a working ps3 , read the ps2 format .I took the COK-001 file that you sent for the experiment and flashed it.Now when I put the disk in the ps3, the ps2 disk is displayed, but when it tries to launch just a black screen.What could be the problem? I just flashed the COK-001 file.
 
Oleg-ps3 said:
I had a working ps3 , read the ps2 format .I took the COK-001 file that you sent for the experiment and flashed it.Now when I put the disk in the ps3, the ps2 disk is displayed, but when it tries to launch just a black screen.What could be the problem? I just flashed the COK-001 file.
Click to expand...
Both the COK-001 Syscon EEPROM file as well as the COK-002 Syscon EEPROM file are valid.
And if the console boots means that the EEPROM content has been written successfully, else the checksum checks would fail.
If you think it's invalid, you need to compare it to the donor Syscon EEPROM content.
 
M4j0r said:
Both the COK-001 Syscon EEPROM file as well as the COK-002 Syscon EEPROM file are valid.
And if the console boots means that the EEPROM content has been written successfully, else the checksum checks would fail.
If you think it's invalid, you need to compare it to the donor Syscon EEPROM content.
Click to expand...
I don't have a programmer to read, do you have another version of the COK-001 file?
 
If you rearrange SEM-001,SYSCON,CPU,NAND from the board to COK-001 Will it work?I want COK-001 to be at 65 nm.
 
Addr: 0x000032fe должно быть 0x1820
Addr: 0x000034fe должно быть 0x8785
Addr: 0x000039fe должно быть 0x0f38
Addr: 0x00003dfe должно быть 0x00ff
Addr: 0x00003ffe должно быть 0x00ff

Можете ли вы сказать мне, как изменить контрольную сумму?​
 
P0: TempD:255.75(0xffff) - TempU:79.0(0x4f00) duty:20%(0x33)
P1: TempD:255.75(0xffff) - TempU:80.0(0x5000) duty:25%(0x40)
P2: TempD:64.0(0x4033) - TempU:81.0(0x5100) duty:28%(0x48)
P3: TempD:77.25(0x4d48) - TempU:82.0(0x5200) duty:30%(0x4d)
P4: TempD:102.25(0x665a) - TempU:85.0(0x5500) duty:35%(0x5a)
P5: TempD:128.25(0x8073) - TempU:0.0(0x0000) duty:40%(0x66)
P6: TempD:255.50(0xff99) - TempU:60.0(0x3c00) duty:45%(0x73)
P7: TempD:83.0(0x5300) - TempU:61.0(0x3d00) duty:50%(0x80)
P8: TempD:84.0(0x5400) - TempU:67.0(0x4300) duty:60%(0x99)
P9: TempD:85.0(0x5500) - TempU:68.0(0x4400) duty:100%(0xff)
P10: TempD:86.0(0x5600) - TempU:71.0(0x4700) duty:0%(0x00)
P11: TempD:87.0(0x5700) - TempU:71.50(0x4780) duty:29%(0x4a)
P12: TempD:88.0(0x5800) - TempU:72.0(0x4800) duty:0%(0x00)
P13: TempD:89.0(0x5900) - TempU:72.50(0x4880) duty:29%(0x4b)
P14: TempD:90.0(0x5a00) - TempU:73.0(0x4900) duty:0%(0x00)
P15: TempD:91.0(0x5b00) - TempU:255.0(0xff33) duty:29%(0x4c)
P16: TempD:95.0(0x5f00) - TempU:0.0(0x0001) duty:0%(0x00)
P17: TempD:0.0(0x0000) - TempU:255.75(0xffff) duty:30%(0x4d)
P18: TempD:48.0(0x3000) - TempU:255.75(0xffff) duty:0%(0x00)
P19: TempD:71.0(0x4700) - TempU:255.75(0xffff) duty:30%(0x4e)
The fan setting is not correct, tell me how to fix it?
 
M4j0r said:
If you swap CELL, you need to also swap the NAND and Syscon or copy their contents. So your swap was done fine.
The error is caused by the wrong SB id stored in the Syscon EEPROM.
This can be fixed by connecting to the Syscon UART and running the command "w 3911 31" in the internal mode.
Click to expand...
Hello @M4j0r I'm swapping syscon cell and nands from Decha00 test cok001 board to a retail A00 cok001 board do you know if I'd need a syscon command for southbridge like the above? All the the best @ appreciate your work /help
 
M4j0r said:
Please see the attached files and run the following while Syscon is in internal mode:
Code: 
python3 write_eeprom_internal.py <your COM Port> COK-001-0x2F00-0x73FF.bin
Click to expand...

Would this also be possible to make a dump? example on a VER-001 syscon SW-301 board, or even to remarry a syscon exchanged with this method? because I have a console that is giving error 8002F225, it does not accept installing any CFW, I patched it normally, in safe mode it asks for 3.55, I tested with downgrade versions 9.99 and it was not, I tested with CEX and DEX, OFW 3.55 and without success I just get the same error, would it be possible to fix this problem through the Syscon UART? If there is any command I can do that forces the service mode or changes the requested firmware, I will attach the dump of the original NOR flash with RSOD, if necessary I will open a new topic.
 
You must log in or register to reply here.

Similar threads

Back
Top