Cechb01 on 2.35 unable to boot into safe mode

RCWD21

Member
I just picked up a cechb01 on 2.35 ofw with an apparent dead laser (disc spins up and stops several times and disc never shows on xmb with verified games)

I have a few other a and b consoles so I swapped daughter boards only to be met with the same issue. So even after swapping cables as I've had a couple go bad I tried booting into safemode to rebuild the file system.

Upon trying to boot into safe mode it repeats the first step everytime where you power it on and hold it until it powers off.

The console boots up to the xmb just fine it just won't let me into safe mode for anything.

Sent from my SM-G965U using Tapatalk
 
Your swapping the daughter board?
Do you mean your using the daughter board from the ps3 to try dona drives?

Did you break the seal to the ps3 or was it already open as it may not have its original drive and daughter in to start with.
I'm not sure what firmware revision recovery menu was added to the ps3 but you may have to get into fsm to remarry the drive. And again I'm not sure if there are files around for your revision firmware to get in remarry and exit
 
Yes I was the one that broke the seal on this console luckily (thats the main thing I look for when getting other consoles thought it isn't always 100%)

I'm keeping the original daughter board thats coded to each console and only swapping the main units.

I just tried to update to 4.86 to see if that fixes my issues but I get error code 8002f147 with the auto reboot. So we'll see how it goes second time around since it just rebooted.

Sent from my SM-G965U using Tapatalk
 
It just boot looped until it gave me the Sony trouble shooting suggestions so I'm currently trying that just for the hell of it.

Kind of annoyed as I paid a little over $120 for this console that was supposed to work otherwise [emoji849]

Sent from my SM-G965U using Tapatalk
 
Do you happen to know where I can find a clean copy of 2.35? I've found a few places but idk if I can trust them

Sent from my SM-G965U using Tapatalk
 
Found that. Got it on a flash drive ready to go but now when I power on the console it just sits there on a black screen and after about 30 seconds shuts off to the red light.

All I've done is run a surface scan on my laptop and now this.. it passed and the drive health is reported as 100%. I still can't access safe mode.

Is there a way to flash the update to the hdd via pc or am I now stuck with yet another unusable console?

Sent from my SM-G965U using Tapatalk
 
Btw, in https://www.psdevwiki.com/ps3/System_Firmware there is a table with all the known firmwares, and sometimes there is a download link for them (unless it expired)
But additionally you can see the hash of the PUP file... this hashes can be used as a verification incase you download the PUP from somewhere else
The OFW 2.35 CEX have a MD5:db48cbcde359982c065c2f5503204b67

Search for that MD5 in google, usually you are going to find several download links for it ;)
 
Btw, in https://www.psdevwiki.com/ps3/System_Firmware there is a table with all the known firmwares, and sometimes there is a download link for them (unless it expired)
But additionally you can see the hash of the PUP file... this hashes can be used as a verification incase you download the PUP from somewhere else
The OFW 2.35 CEX have a MD5:db48cbcde359982c065c2f5503204b67

Search for that MD5 in google, usually you are going to find several download links for it ;)
Thanks for that, I saw that page a while back but for some reason couldn't find it again. Its now bookmarked for later but now I'm having a completely different issue with it not doing anything now.

It powers on, sits on a black screen an after about 30 seconds (maybe less, haven't actually counted) it just shuts off back to the red light. No beeps no flashing lights no nothing.

Whats next? Syscon probing? E3 flasher?

Sent from my SM-G965U using Tapatalk
 
Found that. Got it on a flash drive ready to go but now when I power on the console it just sits there on a black screen and after about 30 seconds shuts off to the red light.

All I've done is run a surface scan on my laptop and now this.. it passed and the drive health is reported as 100%. I still can't access safe mode.

Is there a way to flash the update to the hdd via pc or am I now stuck with yet another unusable console?

Sent from my SM-G965U using Tapatalk
Have you tryed to turn it ON now without the hdd ?, it should display a warning text

The other problem about not being able to enter recovery menu maybe was because some problem in the button ?... that buttons of the fat are "touch sensitive" so are not so straightforward to use than PS3 slims or superslims (it could be a bit confusing because you are not completly sure if you are "activating" it)
 
Have you tryed to turn it ON now without the hdd ?, it should display a warning text

The other problem about not being able to enter recovery menu maybe was because some problem in the button ?... that buttons of the fat are "touch sensitive" so are not so straightforward to use than PS3 slims or superslims (it could be a bit confusing because you are not completly sure if you are "activating" it)
Without a hard drive in, it will power on then last 50 seconds according to the stopwatch on my phone before the light turning back to red. No warning message is ever displayed.

When the system is on I can press the eject button and I get the 3 warning beeps indicating no disc in the drive but thats it

Sent from my SM-G965U using Tapatalk
 
And the installation of OFW 2.35 CEX was completed successfully ?
Before that installation you was having problems with the BD daughterboard, im wondering if the installation was interrupted because a problem in the BD daughterboard and now you have a 2.35 partially installed
 
And the installation of OFW 2.35 CEX was completed successfully ?
Before that installation you was having problems with the BD daughterboard, im wondering if the installation was interrupted because a problem in the BD daughterboard and now you have a 2.35 partially installed
The original issue I was having was the console wasn't detecting discs so I swapped lasers (couldn't remember if it was bad or not but it was the same kem-400aaa laser carriage assembly) I reassembled everything only to have the same issue. So I swapped in a different drive all together keeping the daughter board with the appropriate console, but again same issue. I tried several times with different drives and even the main cables with no luck so I tried getting into safe mode but all it would do is beep twice and power off just like with the first half of getting to safe mode.

So after some digging around I read a few pages that mentioned that certain games required a newer firmware to work and figuring since I wanted to jailbreak this console anyways I went ahead and via the xmb options I went to update the firmware and at around the 58% mark it would give me the error code. After 3 times it game me the troubleshooting message and while I was doing that I did a surface scan on the disc to check the health of it. It passed. Upon clearing the test I reinstalled it with a copy of the 2.35 firmware on a flash drive ready to try and reinstall that hoping I could at least get back to where I was.

But as of right now when you power on the console with or without a harddrive installed it will only stay powered on a short while before shutting off and returning to standby mode. It doesn't beep or anything. With the hdd installed however the hdd activity light does flash.

But no matter what I do now it won't show anything on the TV.

Sent from my SM-G965U using Tapatalk
 
...while I was doing that I did a surface scan on the disc to check the health of it. It passed. Upon clearing the test I reinstalled it with a copy of the 2.35 firmware on a flash drive ready to try and reinstall that hoping I could at least get back to where I was.
But that installation was completed normally ?, and when it was completed the PS3 rebooted into XMB ?
Im asking because im wondering if thats the point where it had a software brick
 
When I originally selected the update via xmb it completely downloaded and then rebooted like normal asking me to accept the terms and conditions. I accepted them and upon its install it failed (I didn't see how far it got unfortunately) so it asked if I wanted to retry and after that it went into its self retry thing before instantly giving me the error code.

Ive tried swapping in a different hard drive but it still gives me the same issue

Sent from my SM-G965U using Tapatalk
 
Not sure, but i guess thats when it bricked, so it seems to be a software problem
Even the OFW installer have some checks to prevent the user to be trapped like this, incase something is wrong it takes you back without writing much critical data in flash
But with a problem in BD, or intermitent connections with it... it could happen that checks are bypassed, then it starts writing in flash but at some point the writing process is interrupted, and this could result in a firmware partially installed

The most interesting thing to check now would be a dump of flash, and scan the dump with the dump checker tools to see is there is some "breakpoint" in it
The important data from the dump (per-console or per-user) is not ovewritten by the firmware installers, so technically the flash dump can be rebuilt (i dont have any experience rebuilding flash dumps like that though)
 
Last edited:
Not sure, but i guess thats when it bricked, so it seems to be a software problem
Even the OFW installer have some checks to prevent the user to be trapped like this, incase something is wrong it takes you back without writing much critical data in flash
But with a problem in BD, or intermitent connections with it... it could happen that checks are bypassed, then it starts writing in flash but at some point the writing process is interrupted, and this could result in a firmware partially installed

The most interesting thing to check now would be a dump of flash, and scan the dump with the dump checker tools to see is there is some "breakpoint" in it
The important data from the dump (per-console or per-user) is not ovewritten by the firmware installers, so technically the flash dump can be rebuilt (i dont have any experience rebuilding flash dumps like that though)
I have a couple of confirmed flash dumps from a cecha01 and a ceche01 if it does have to be rebuilt.

Question is though, how do I get to that info? Is that something I can access via syscon?

Sent from my SM-G965U using Tapatalk
 
There are 2 ROS regions for the very purpose of protecting the Flash memory from bad firmware installations.
The ps3 system update installs the new firmware in the inactive ROS region & when the installation process is complete, it modifies the active ROS region value (0/1) stored in syscon ONLY IF the entire installation process was reported as successful.
It cannot be ruled out but it is extremely unlikely that a bad installation would actually succeed imho.
 
There are 2 ROS regions for the very purpose of protecting the Flash memory from bad firmware installations.
The ps3 system update installs the new firmware in the inactive ROS region & when the installation process is complete, it modifies the active ROS region value (0/1) stored in syscon ONLY IF the entire installation process was reported as successful.
It cannot be ruled out but it is extremely unlikely that a bad installation would actually succeed imho.
Whats odd is I've never had a bad bluray drive interfere with a firmware update, maybe I'm just lucky or something but I'd really like to get this console working again. Its in fantastic shape and doesn't have a bunch of run time on it.

Is there any way I can probe into this to find out what failed?

Sent from my SM-G965U using Tapatalk
 

Similar threads

Back
Top