PS3 need coreos ofw 4.90

good luck! make sure you solder southbridge uart to know what's wrong :)
hi,
I'm back, i've tried it again with no success, I know nothing about "southbridge uart", I did syscon led test and i've got 5FFF error.
Thank you very much for your help, i'm going to sell it
 
good luck! make sure you solder southbridge uart to know what's wrong :)

hi,
i was able to get the syscon errlog, what can i do

> AUTH
Auth successful
> errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 0B49DA7E
# A0805FFF 0B49DA4E
# A0805FFF 0B49DA10
# A0805FFF 0B49D9E2
# A0802022 1B8DC968
# A0802022 1B8DC968
# A0802022 1B8DC967
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

>
 
hi,
i was able to get the syscon errlog, what can i do

> AUTH
Auth successful
> errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 0B49DA7E
# A0805FFF 0B49DA4E
# A0805FFF 0B49DA10
# A0805FFF 0B49D9E2
# A0802022 1B8DC968
# A0802022 1B8DC968
# A0802022 1B8DC967
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

>

Thanks! gonna check the meaning of these errors and will let you know soon...
 
Jose Coixao, [18/05/2023 20:06]
A0805FFF

Jose Coixao, [18/05/2023 20:06]
any idea what the error code means

M4j0r, [18/05/2023 20:31]
That code is only possible on consoles with a sherwood syscon

M4j0r, [18/05/2023 20:32]
And I didn't reverse that, could be related to CELL/XDR
 
Please clear the error log once (errlog clear) and start the console, then read the error log again.
 
Please clear the error log once (errlog clear) and start the console, then read the error log again.

It's off-topic, but have you seen our experiments with higher clock speeds on the RSX and memory?

We've tested on several systems and found that 700MHz for the core works well for most systems (All systems that we tested so far) , while at 750MHz and above, some artifacts may appear in a few games. (AC Black Flag and Crysis 1)

It seems that memory can run up to 1000MHz, although we haven't tested higher than this yet.

Both of my systems are currently running at 800/800 without any issues (2100A and 25001B). I plan to push them even higher today.
 
Last edited:
It's off-topic, but have you seen our experiments with higher clock speeds on the RSX and memory?

We've tested on several systems and found that 700MHz for the core works well for most systems, while at 750MHz and above, some artifacts may appear in a few games.

It seems that memory can run up to 1000MHz, although we haven't tested higher than this yet.
Both of my systems are currently running at 800MHz without any issues (2100A and 25001B).
Yes, I saw that, but I my goal was to provide a safe value for all consoles. 650 MHz on the core will already mess a lot with 90nm and some 65nm RSX (even ones with from the best bin).
The memory controller was changed between each RSX process shrink so the biggest potential might be there (28nm uses GDDR5 but we can't change the clock :/).
Since there's no way to make sure somebody installs a PUP with a higher clock setting on an incompatible console and the binning at least for retail consoles is almost random, I don't want to be responsible for bricked consoles.
But it is sure interesting to see more results (even though they will lead to some bricks), maybe organized in a way that we can see the complete rsx version string and then do some correlation.
 
Yes, I saw that, but I my goal was to provide a safe value for all consoles. 650 MHz on the core will already mess a lot with 90nm and some 65nm RSX (even ones with from the best bin).
The memory controller was changed between each RSX process shrink so the biggest potential might be there (28nm uses GDDR5 but we can't change the clock :/).
Since there's no way to make sure somebody installs a PUP with a higher clock setting on an incompatible console and the binning at least for retail consoles is almost random, I don't want to be responsible for bricked consoles.
But it is sure interesting to see more results (even though they will lead to some bricks), maybe organized in a way that we can see the complete rsx version string and then do some correlation.

Do you think overclocking could brick the system if it doesn't handle it? A friend of mine tried pushing his phat model to 800MHz, but all he experienced was games crashing at the start of gameplay.

He just rolled out to 700Mhz and it's working good now.

I plan to keep pushing mine until I encounter crashes or artifacts. Do you think there's a point where it might prevent me from accessing the recovery menu? i don't have a flasher so if something goes wrong here, the recovery menu is the only thing to save my console if it happens.
 
Do you think overclocking could brick the system if it doesn't handle it? A friend of mine tried pushing his phat model to 800MHz, but all he experienced was games crashing at the start of gameplay.
Yes, absolutely, I've seen that. As soon as lv2 wants to complete the rsx init (even before the display gets a signal) the PS3 crashes.
 
Yes, absolutely, I've seen that. As soon as lv2 wants to complete the rsx init (even before the display gets a signal) the PS3 crashes.

See the thread. i gathered all the RSX models and revisons... seems like mine is the newest and the one that is handling more OC.
 
Yes, absolutely, I've seen that. As soon as lv2 wants to complete the rsx init (even before the display gets a signal) the PS3 crashes.


Lets see if we find any correlation between the rsx versions and the overclocks

RSXRevMax GPU Clock

(Stable)
Max Memory Clock

(Stable)
Full DetailsNotesPS3 ModelOwner
rsx40a01800 MHz1000 MHzvpe:ff shd:77 [AP0022017:0:1:3:e:18:2:0:1][2a:0:a:0:1:0:1][1:1:0]No artifacts (More OC will be made)CECH-2511AMe
rsx40a01700 MHz1000 MHzvpe:ff shd:3f [NN8941-24:0:4:18:12:18:6:0:2][25:0:a:0:1:0:1][1:1:0]Artifacts at 750Mhz Core in specific games.CECH-2504A@Thimblewad
rsx40a01700 MHz1000 MHzvpe:ff shd:3f [NN0078-06:0:4:6:18:4:6:0:2][25:0:2:0:1:0:1][1:1:0]Artifacts at 750Mhz Core in specific games.CECH-2104B@cha0shacker
rsx65a06700 MHz1000 MHzvpe:ff shd:6f [KBA857800:1:2:c:11:7:3:8:2][3d:0:2:0:1:2:0][2:1:0]Artifacts at 750Mhz Core in specific games.CECH-2004B@Mitsu™
Issues on their systems: (probably more games)

Game TitleIssue
Assassin's Creed Black FlagConstant artifacts
CrysisConstant artifacts
Bioshock InfiniteLess frequent artifacts


Do you know the maximum frequency for the memory? It appears that all systems can handle 1000MHz without any issues, with artifacts only occurring at a core speed of 750MHz.


By the way, what distinguishes my RSX from others is the 'shd:77' - any idea what that is it? it is handling much more OC.
 
Please clear the error log once (errlog clear) and start the console, then read the error log again.

Auth successful
> errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

>
 
we can take this to dm on discord or telegram

i'm zecoxao#0254 (discord) or @zecoxao1 (telegram)
Hello, would it be possible for you to help me as well? I need to somehow get the CoreOS (.BIN) from 4.92 to unbrick my console. I already have the e3 flasher and soldered tristate to ground. I'm struggling to get the .bin file because at https://www.psx-place.com/threads/g...r-an-unfortunate-ps3xploit-flash.21750/page-2 only has up to 4.91. I tried DMing you, but you have private Discord. It would be very helpful. Thank you.
 
Hello, would it be possible for you to help me as well? I need to somehow get the CoreOS (.BIN) from 4.92 to unbrick my console. I already have the e3 flasher and soldered tristate to ground. I'm struggling to get the .bin file because at https://www.psx-place.com/threads/g...r-an-unfortunate-ps3xploit-flash.21750/page-2 only has up to 4.91. I tried DMing you, but you have private Discord. It would be very helpful. Thank you.

You can extract CoreOS.BIN from OFW 4.92 PUP.

Follow this thread: https://www.psx-place.com/threads/how-to-extract-coreos-bin-from-a-pup-file.45238/
 

Similar threads

Back
Top