CMOS kernel clock fix, Help

you may be able to fix it with todex, but the rtc payload only works on 5.05. it messes things up on later firmwares.
i am not sure yet, but i think that way will not mess anything since only sets time in certain FW versions. I think this is the way to bypass the problem when the cmos battery did end its life. Of course a modded console is required to bypass this.
Anyways it will be interesting to know what you have find on this...
 
i am not sure yet, but i think that way will not mess anything since only sets time in certain FW versions. I think this is the way to bypass the problem when the cmos battery did end its life. Of course a modded console is required to bypass this.
Anyways it will be interesting to know what you have find on this...
no longer needed, but you do need an exploited console. just change to sp-int for network environment, which will update the rtc from the dev network.
 
if someone here is having the cmos problem, we can perform a fast test to see if we can bypass it....
Post automatically merged:

no longer needed, but you do need an exploited console. just change to sp-int for network environment, which will update the rtc from the dev network.
that trick seems to be dependent on the sony's remote server... in that case that trick wont works in a future...
 
Last edited by xalfie,
if someone here is having the cmos problem, we can perform a fast test to see if we can bypass it....
Post automatically merged:


that trick seems to be dependent on the sony's remote server... in that case that trick wont works in a future...
Well, I don't know about that. The trick comes from @Leeful .
Post automatically merged:

Well, I don't know about that. The trick comes from @Leeful .
It's irrelevant though as hen bypasses it, and the latest firmware has been patched.
 
  • Like
Reactions: Leeful
On youtube, they say that this method was patched by sony
see comments
1693722169381.png

link:
 
conforming the info, out there, the trick is not longer working because sony did changes on Dev network. The big problem is again here because, consoles with 1.76 5.05 and 6.72 will reach that moment when the battery will reach the end of life...
I know that goldhen is bypassing the problem, but i wanted to know what happen with the original discs... i have read they wonk work at all... what a problem :(
 
So unfortunately there isn't a new method to fix this, opened my PS4 Slim on 6.72, replaced thermal pads with a brand new high end, new thermal paste, and insert a brand new CR2032 Battery, I knowed of this method of Debug settings, so I wasn´t worried about this clock bug, but I'm getting CE-33729-4, time resets to 1970.
 
So there is still no solution? I changed mine without keeping the board powered, cant log in anymore, or do anything else, time of course complete random, and ps4 support didnt do a s***, are we still stuck?
 
So there is still no solution? I changed mine without keeping the board powered, cant log in anymore, or do anything else, time of course complete random, and ps4 support didnt do a s***, are we still stuck?
Is it still the case I'm on 5.05 I updated from 2.03 so don't want to update further as I also have a 9.03 too which now GH supports, my problem is my clock on 5.05 is fast must have gained time over its almost 15 yrs, only about 20mins, but worry when cmos does go will date reset everytime, and is there a fix dor 5.05.
 
There is a payload that fixes this, don't worry about it. I too have a 5.05 pro but have not had any problems with the cmos yet. Modded warfare on youtube has a video on this.
 
So there is still no solution? I changed mine without keeping the board powered, cant log in anymore, or do anything else, time of course complete random, and ps4 support didnt do a s***, are we still stuck?
Goldhen 2.4.18b5 seems to fix it, not tried myself. Needs internet for NTP sync
 

Site & Scene News

Popular threads in this forum