PS3 I think I bombed the CBOMB fix. How do I undo my mistake?

Psx_Specter

Psx_Specter

Forum Noob
Hi everyone, thanks for taking the time to read my post. I recently dusted off my PS3 slim CECH2501a that had been sitting for many years and was amazed at the progress that has been made with CFW since I last played around with it. I was greeted with the need to set the time and date when I booted it up. I decided this would be the perfect time to test out Evilnat's latest CFW and try the fix. To make a long story short, I enabled the CBOMB fix while the date was set to a time in the future, and can't seem to revert it. I've tried downgrading to OFW 3.55, but as soon as I'm updated to any CFW (I've only tried two) and running Webman mod, the problem persists. I know very little about the inner workings of CFW, but I presume this clock value is being written to an area of flash that is untouched by firmware updates. Can someone with knowledge in this area help steer me in the right direction before I accidentally brick this poor PS3? I couldn't find any information on how to undo the CBOMB fix. Thanks so much.
 
Psx_Specter said:
Hi everyone, thanks for taking the time to read my post. I recently dusted off my PS3 slim CECH2501a that had been sitting for many years and was amazed at the progress that has been made with CFW since I last played around with it. I was greeted with the need to set the time and date when I booted it up. I decided this would be the perfect time to test out Evilnat's latest CFW and try the fix. To make a long story short, I enabled the CBOMB fix while the date was set to a time in the future, and can't seem to revert it. I've tried downgrading to OFW 3.55, but as soon as I'm updated to any CFW (I've only tried two) and running Webman mod, the problem persists. I know very little about the inner workings of CFW, but I presume this clock value is being written to an area of flash that is untouched by firmware updates. Can someone with knowledge in this area help steer me in the right direction before I accidentally brick this poor PS3? I couldn't find any information on how to undo the CBOMB fix. Thanks so much.
Click to expand...
Hi mate! You can re-use the CBOMB fix again, simply change your date to the real one and use the patch, it will use that date to add it in xRegistry

Also make sure that nothing else is patching it too
 
Evilnat said:
Hi mate! You can re-use the CBOMB fix again, simply change your date to the real one and use the patch, it will use that date to add it in xRegistry

Also make sure that nothing else is patching it too
Click to expand...

Patching after setting the correct time and date instantly reverts it to the wrong time and date. The setting is not enabled in webman. I don't have anything else installed.
 
Sorry to butt in, but when activating the CBomb fix, will the system ask for the date to always be on, or will this be fixed? Can I activate the Auto clock fix in webman together with CBomb?
 
Vinicius GP said:
Sorry to butt in, but when activating the CBomb fix, will the system ask for the date to always be on, or will this be fixed? Can I activate the Auto clock fix in webman together with CBomb?
Click to expand...
Hopefully Evilnat can answer that for you. The Webman clock fix is at least partially based on Evilnat's fix, so I'm not sure why you would want to use both.
 
Psx_Specter said:
If I press it once, i see "Date and time fixed" if I fumble around and accidentally press it twice (for debugging purposes, of course), it also says RTC fixed.
Click to expand...
If the option detects that your current time and RTC are not paired it will patch date and time and RTC, otherwise it will only patch RTC
Vinicius GP said:
Sorry to butt in, but when activating the CBomb fix, will the system ask for the date to always be on, or will this be fixed? Can I activate the Auto clock fix in webman together with CBomb?
Click to expand...
No, you need to set your current date first, and the use the patch. If you do not do that, xai will use a default "timestamp" to patch it but not the actual date

The option in xai is needed only once, you can use webMAN's too
 
Evilnat said:
If the option detects that your current time and RTC are not paired it will patch date and time and RTC, otherwise it will only patch RTC

No, you need to set your current date first, and the use the patch. If you do not do that, xai will use a default "timestamp" to patch it but not the actual date

The option in xai is needed only once, you can use webMAN's too
Click to expand...
I have exhausted every combination I can think of to get the clock to hold the current time after a reboot. If it helps any, this PS3 was running PS3ita 4.65 DEX prior to my disaster. Disabling plugins in cobra is the only thing that makes it behave "normally", as in it will hold the clock settings after reboot. If I apply the CBOMB fix with plugins disabled, the date and time are once again rendered incorrect. My CMOS battery has gained some strength at this point (how?) and holds the time fine (as long as plugins are toggled off in cobra).

Just a little update for anyone following along. I formatted a drive and did a system restore from the XMB , going back to PS3ita 4.65.I set the clock as usual during the setup process (correctly this time), and everything seems normal. Correct time after cold start/reboot. As an experiment (double checking my previous efforts), I then installed webman mod , and boom! the clock was screwed up again, in the future land of Y2.1K and the gargantuan thicket of madness. My advice to anyone reading this is to NEVER mess around and set your clock to a future year and then apply the CBOMB fix. Once I put in the wrong year, it would only let me change it to a year farther in the future... until the year 2100, which cannot be set by normal means in the time and date settings. Maybe @aldostools will see this and chime in, guiding me to the light. As it stands, my PS3 slim that can do 750mhz on the RSX is kind of stuck back in the stone age, while my CECHL is running Evilnat's overclocked firmware, webman mod, and the CBOMB fix applied without any issues. Oh, the irony. Be careful, folks. Don't be a dummy like PSX_Specter and spin the time and date around carelessly trying to test something out that you don't fully understand. I think if someone with the ability added a CBOMB fix undo button to a menu (any menu, pick one), to undo the CBOMB fix, thereby setting the default factory time or just blanking the values completely, it might not be a bad idea. My humble two cents. I'm only clever enough to be dangerous, obviously, so I'm resisting the urge to start hex editing or copying files in flash without knowing what I'm doing. I bought this particular console already jailbroken, and never got around to making a dump of the flash before my goof.
 
Last edited by a moderator:
Psx_Specter said:
I have exhausted every combination I can think of to get the clock to hold the current time after a reboot. If it helps any, this PS3 was running PS3ita 4.65 DEX prior to my disaster. Disabling plugins in cobra is the only thing that makes it behave "normally", as in it will hold the clock settings after reboot. If I apply the CBOMB fix with plugins disabled, the date and time are once again rendered incorrect. My CMOS battery has gained some strength at this point (how?) and holds the time fine (as long as plugins are toggled off in cobra).

Just a little update for anyone following along. I formatted a drive and did a system restore from the XMB , going back to PS3ita 4.65.I set the clock as usual during the setup process (correctly this time), and everything seems normal. Correct time after cold start/reboot. As an experiment (double checking my previous efforts), I then installed webman mod , and boom! the clock was screwed up again, in the future land of Y2.1K and the gargantuan thicket of madness. My advice to anyone reading this is to NEVER mess around and set your clock to a future year and then apply the CBOMB fix. Once I put in the wrong year, it would only let me change it to a year farther in the future... until the year 2100, which cannot be set by normal means in the time and date settings. Maybe @aldostools will see this and chime in, guiding me to the light. As it stands, my PS3 slim that can do 750mhz on the RSX is kind of stuck back in the stone age, while my CECHL is running Evilnat's overclocked firmware, webman mod, and the CBOMB fix applied without any issues. Oh, the irony. Be careful, folks. Don't be a dummy like PSX_Specter and spin the time and date around carelessly trying to test something out that you don't fully understand. I think if someone with the ability added a CBOMB fix undo button to a menu (any menu, pick one), to undo the CBOMB fix, thereby setting the default factory time or just blanking the values completely, it might not be a bad idea. My humble two cents. I'm only clever enough to be dangerous, obviously, so I'm resisting the urge to start hex editing or copying files in flash without knowing what I'm doing. I bought this particular console already jailbroken, and never got around to making a dump of the flash before my goof.
Click to expand...
Well this was very insightful, thanks for being our guinea pig man, the learning never stops.
 
Psx_Specter said:
I have exhausted every combination I can think of to get the clock to hold the current time after a reboot. If it helps any, this PS3 was running PS3ita 4.65 DEX prior to my disaster. Disabling plugins in cobra is the only thing that makes it behave "normally", as in it will hold the clock settings after reboot. If I apply the CBOMB fix with plugins disabled, the date and time are once again rendered incorrect. My CMOS battery has gained some strength at this point (how?) and holds the time fine (as long as plugins are toggled off in cobra).

Just a little update for anyone following along. I formatted a drive and did a system restore from the XMB , going back to PS3ita 4.65.I set the clock as usual during the setup process (correctly this time), and everything seems normal. Correct time after cold start/reboot. As an experiment (double checking my previous efforts), I then installed webman mod , and boom! the clock was screwed up again, in the future land of Y2.1K and the gargantuan thicket of madness. My advice to anyone reading this is to NEVER mess around and set your clock to a future year and then apply the CBOMB fix. Once I put in the wrong year, it would only let me change it to a year farther in the future... until the year 2100, which cannot be set by normal means in the time and date settings. Maybe @aldostools will see this and chime in, guiding me to the light. As it stands, my PS3 slim that can do 750mhz on the RSX is kind of stuck back in the stone age, while my CECHL is running Evilnat's overclocked firmware, webman mod, and the CBOMB fix applied without any issues. Oh, the irony. Be careful, folks. Don't be a dummy like PSX_Specter and spin the time and date around carelessly trying to test something out that you don't fully understand. I think if someone with the ability added a CBOMB fix undo button to a menu (any menu, pick one), to undo the CBOMB fix, thereby setting the default factory time or just blanking the values completely, it might not be a bad idea. My humble two cents. I'm only clever enough to be dangerous, obviously, so I'm resisting the urge to start hex editing or copying files in flash without knowing what I'm doing. I bought this particular console already jailbroken, and never got around to making a dump of the flash before my goof.
Click to expand...
If the PS3 battery is not good and needs to be replaced, simply turning off the console and unplugging it a few minutes will reset the date, also the value is stored in xRegistry, if you erase it and reboot the PS3 will reset it too

I have checked it on my PS3 and using only the option in xai and worked perfectly, I removed the CMOS battery to check it. I will add an option in xai to remove the current bad date to avoid this kind of issues

webMAN MOD is patching using a bad timedate? Do you have enabled the automatic fix of PS3 clock check?

@aldostools can take a look please?
 
Evilnat said:
If the PS3 battery is not good and needs to be replaced, simply turning off the console and unplugging it a few minutes will reset the date, also the value is stored in xRegistry, if you erase it and reboot the PS3 will reset it too

I have checked it on my PS3 and using only the option in xai and worked perfectly, I removed the CMOS battery to check it. I will add an option in xai to remove the current bad date to avoid this kind of issues

webMAN MOD is patching using a bad timedate? Do you have enabled the automatic fix of PS3 clock check?

@aldostools can take a look please?
Click to expand...
Regarding my battery, I left my console unplugged for 24 hours and it never asked me to set the time and date. I assume it has a marginal charge. It only asked for time and date on initial setup, and those values do not survive a reboot once webman mod is installed without ever using webMAN's automatic clock fix. I really don't want to disassemble and remove the battery because I just cleaned and repasted before my "time crime", but If you need me to remove the battery to help you figure this out, I will. At this point I have tried just about everything (end user level fixes). Your "fix for the fix" could maybe just be a package if you didn't want to bloat the xai menu any further or push another release? Thanks for your reply and for continuing to serve the community. :encouragement:
 
Evilnat said:
If the PS3 battery is not good and needs to be replaced, simply turning off the console and unplugging it a few minutes will reset the date, also the value is stored in xRegistry, if you erase it and reboot the PS3 will reset it too

I have checked it on my PS3 and using only the option in xai and worked perfectly, I removed the CMOS battery to check it. I will add an option in xai to remove the current bad date to avoid this kind of issues

webMAN MOD is patching using a bad timedate? Do you have enabled the automatic fix of PS3 clock check?

@aldostools can take a look please?
Click to expand...

webMAN MOD 1.47.48m is working as expected on my system.

If for any reason a future date was set, it can be fixed changing the date/time manually or via Internet in Settings > Date and Time Settings
https://manuals.playstation.net/document/en/ps3/current/settings/date.html

Also uncheck Auto Fix Clock is the feature is causing issues. This is performed only once when the system starts and the system date is before 2025-06-05.
 
aldostools said:
webMAN MOD 1.47.48m is working as expected on my system.

If for any reason a future date was set, it can be fixed changing the date/time manually or via Internet in Settings > Date and Time Settings
https://manuals.playstation.net/document/en/ps3/current/settings/date.html

Also uncheck Auto Fix Clock is the feature is causing issues. This is performed only once when the system starts and the system date is before 2025-06-05.
Click to expand...
Thank you for taking notice of my seemingly unique problem. I have tried more experiments and can confirm that uninstalling webMAN fixes my clock issue. The system will hold the correct time and date after a reboot. However, with webMAN uninstalled, if I apply Evilnat's CBOMB fix, the time and date will revert to the previous incorrect settings. At that point, if I again set the time and date correctly it will stay correct after a reboot. Reinstalling webMAN will revert the clock back to incorrect (future date) settings. The process is repeatable for me.
I hope this is of some help. The only thing I can think of that might be different about my system is that I have a 1.5TB spinning disk installed. I have noticed that the system will completely skip a disk check if the drive has more than ~500GB of data written to it. It's been recently formatted and will perform a disk check at the moment.
-update-
I am able to run Evilnat 4.92.2, updated xai plugin, multiman 4.91, and webMAN 1.41.16 MOD (PS3ita edition) without any clock problems aside from what i mentioned above. Of course this version of webMAN predates any clock fixes and doesn't work very well with the newer CFW.
 
Last edited:
Psx_Specter said:
Thank you for taking notice of my seemingly unique problem. I have tried more experiments and can confirm that uninstalling webMAN fixes my clock issue. The system will hold the correct time and date after a reboot. However, with webMAN uninstalled, if I apply Evilnat's CBOMB fix, the time and date will revert to the previous incorrect settings. At that point, if I again set the time and date correctly it will stay correct after a reboot. Reinstalling webMAN will revert the clock back to incorrect (future date) settings. The process is repeatable for me.
I hope this is of some help. The only thing I can think of that might be different about my system is that I have a 1.5TB spinning disk installed. I have noticed that the system will completely skip a disk check if the drive has more than ~500GB of data written to it. It's been recently formatted and will perform a disk check at the moment.
Click to expand...

Go to /setup.ps3 uncheck Auto Fix Clock and SAVE the settings.

Then go to XMB > Settings > Date and Time Settings. Set an old date manually. Then set the date/time via Internet. Reboot.

The issue happens when the system stores the RTC difference in the registry.
xSettingDateGetInterface()->SaveDiffTime(diff);

If Auto Fix Clock is unchecked, the clock should remain untouched.
 
aldostools said:
Go to /setup.ps3 uncheck Auto Fix Clock and SAVE the settings.

Then go to XMB > Settings > Date and Time Settings. Set an old date manually. Then set the date/time via Internet. Reboot.

The issue happens when the system stores the RTC difference in the registry.
xSettingDateGetInterface()->SaveDiffTime(diff);

If Auto Fix Clock is unchecked, the clock should remain untouched.
Click to expand...
This console is banned from PSN and unable to connect to the time server. Maybe I should have mentioned that :orange: When I get to "Then set the date/time via Internet" step, it returns "The current date and time could not be obtained. (80710016)"

-update-
I've switched to webMAN MOD version 1.47.46 (newest version I could find that didn't include the clock fix) and the clock holds time after reboot. For clarity to anyone following along that is not aware, this doesn't fix the erroneous RTC values, but it will fix the date and time displayed on your console if it's reverting to some strange time in the future when you start up or reboot.

-issue resolved-
After leaving my time-borked PS3 untouched for almost a year, I got it out today, Installed Evilnat's 4.93 D-PEX along with fixes, and webMAN MOD 1.47.48 package. The time reverted erroneously to the year 2100. Not great, but not unexpected. I then manually set the correct time and date, applied the cbomb fix, rebooted, and I'll be damned...the correct time and date settings held !!! A huge thanks to @Evilnat and @aldostools for whatever magic you performed to correct my foolishness. Hopefully it will help others as well.
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top