As mentioned by RipFelix, the bring up command works better with the command line version of the tool For an up to date error code explainer check the DevWiki: www.psdevwiki.com/ps3/Syscon_Error_Codes GitHub for the Syscon Tool (incase updates or you need the CLI ver): github.com/db260179/ps3syscon
I just got a CECHK model recently that's YLOD'd so this tutorial was perfect timing for me, thank you for providing a clear and understanding tutorial for this 👍
Update: took me longer to get to it then expected, irl stuff and other projects aside. It actually works out well! I got the error codes off the PS3 and now sooner or later I can potentially start fixing it up
This video is incredibly professional!!! Now i am sure to buy some tantalums. Feel so proud to troubleshoot a problem with a clear step by step like that.
Good video with straightforward information to set up a PS3 Syscon device on an RPI Pico. Thank you, I was able to double-check my work with this and it was greatly appreciated.
Great tutorial, going to test on a 3 bips blinking red light CECHK01 here. Just one question: at 11:39, in the screen the command reads EEPSUM, but on the app screen you typed EEPCSUM. Is it a typo, or both commands work the same, or just the one you typed (EEPCSUM) is the right one? Thanks!
I get "scopen response invalid" and now my PS3 is stuck in this auto 3 beep mode. Update set it back as FF, disabled internal mode no more auto 3 beeps, since you don't really need to set it to that. My error code is 3003.
I followed all the steps for my VER.001 ps3 but when I connect the syscon to the pc and click "Auth" it shows the error that you mentioned in the video. I tried swapping the cables but nothing changes. I tried downgrading python to 3.10 (as this program seems to work on that version of Python), but it didn't help. I also tried using another pc with windows 10 this time (instead of 11), but I get the same error. I've been troubleshooting for an entire day at this point but I'm unable to find a fix.....do you have any idea what the problem could be?
Is the uart adapter showing in device manager correctly, sometimes windows installs the wrong driver. It may be showing as libusb or something, manually change the driver by going update (right click on the device > “let me choose” > then manually select a different driver from the list Also if you are using bread board jumpers, sometimes the wires aren’t crimped and have no connection inside (this happened to me yesterday) Also confirm ground is connected When installing python ensure add to path check box is selected
@@Slot1Gamer I manually checked continuity between the cables and the motherboard but the device was indeed being shown as an "unrecognized device", so it must have been the drivers not being installed correctly. I somehow still managed to make it work via the cmd version and I got 1002 and 2114 errors, so my NEC/TOKINs must be broken..... It's a shame because that was my uncle's PS3 and he gifted it to me in 2015....I have so many memories of me and him playing Gran Turismo and GTA IV but the fix is not worth it imo; I'll probably get a used PS3 slim but I'll lose all my data that was on the old hdd. Thanks for the help anyway, it could be helpful in a future troubleshoot 😁
the console can be turned on with the UART controller connected? my console is bricked in recovery mode, doesn t recognize usb either. That's happened after i tried to install cfw. 1. i cleaned up the console and drilled some holes in case for a better air flow (ps3 CECHG04) but i lifted up the disc drive destroying the flex cable grip from the MB. 2.Then i started to dump syscon with an web tool, all good until i had trying to install "EvilNat 4.90.1 CFW " . I didn't know that the console checks the disk drive while updating the firmware 3.Console entered into a boot loop which every time finished with an error, so i cut out the power supply. When the console turn on again in Recovery mode, all usb fat32 formated with ps3 update on it becomes unrecognizable. it can't rebuilt databases or format HDD.
@Slot1Gamer I discovered the problem! the minimum version of Python that the script required was 3.10. I was using Windows 7 where the last version released was 3.7, so it gave me an error.
@@Slot1Gamer yes She hás power, and did try a couple of Times Change the cable. I really cont get why i cant get the errors on the PS3 Slim. My PS3 60g works fine a d tell me everytime the errors.
Google " PS3 SYSCON Error Code 3004" Has lots of Info. Small sample: "This error is linked to inadequate filtering on the RSX_VDDC power line. A certain range of voltage ripple and noise can trigger this error before it becomes severe enough to cause an RSX_VDDC Power Failure (3004)."
@@giorgesuarez5807 Salm-O-Nella • 1y ago • I have the same problem on COK-002 Board, i've tried to replace Q6001 and Q6002 Mosfets, IC6002 and IC6003 Voltage Regulators, and IC6201 Cpu Power Processor without success. Obviously i replaced NEC-TOKIN with 470uF Tantalum Caps, 4 for each NEC-TOKIN, and done the bridge with 2.5mm^2. All voltages and enable signals are ok, resistance between caps and gnd is 3.5ohms, so that's also ok. Tomorrow i will try to replace IC6200..
@@giorgesuarez5807 olongrieving OP • 2y ago • omg never mind! i did some basic tracing from the fuse through the vias and found another shorted capacitor as shown in the first link (pic from the donor board). YLOD IS GONE. my first time. hurrah. newish to electronics repair so this is a pretty big ass dopamine hit. who knows if the console is stable but i'll take the win.
These boards take insane amounts of thermal energy to reflow the cpu Warming up the cpu may bring it back temporary and that would indicate a solder bump issue on the die but those are rare for ps3 Most issues lie in the gpu
11:39 is it "eepsum" or "eepcsum" 😶 your caption says something different to what you wrote on the machine and it kinda sounds like you said a mixture of the two 😅
If you dont get a red or yellow light, can you still use SYSCON to diagnose? I have a BC Fat that doesnt boot, but also doesnt red or yellow light either. Stays green, just never boots with screen artifacts and TV knows something is plugged in. Thank you!
Should be able to yes, the console has power and sounds like it’s hanging on GPU startup For this I suggest getting the log, then run bring up command (you may want to use the command line version of the tool for bring up )
Sometimes it installed as a different device. You need to find what it showing up as in device manager and manually choose the driver (update driver > choose driver from list) Then it will install as FTDI
I believe the GUI has a character limit and commands like bringup won't give you the full read-out. Given that this is one of the more useful commands it makes the current GUI not awesome in some regards.
It seems to bring up the error log fine which has a large character count You can scroll inside the response window Error log is probably the main reason people will use this anyway
Nice work. A few things. There is more information about the bringup string that doesnt show when the Power On Sequence reaches a certain point, namely the bittraining and bootloader string. Both of which require you the hit enter a second time to display the rest of the log. IIRC the GUI didn't display it. It adds a layer between you and the uart script that can also mess up commands, which is why I didn't include it in my tutorial. I also wouldn't have told them to enable internal access on mullion as a default. Changing a byte is a step people can and do mess up. And if they accidentally change the wrong address it can be hard to fix. So I would have liked to see you first tell them the external commands they can use before adding that they could proceed to internal if they are adventurous. The errorcode section probably should just link them to the dev wiki where explantions can benifit from improvments over time. I dont want to comment io the accuracy of the code explanations you offered, but they can be misinterpreted easily and the step numbers are missing. And extreemly important. This is a habbit I've been trying to get people to break. The last four digits are not the whole picture. We NEED the step # also. It can litterally be the difference between a fuse that blew or a dead GPU. When an error occurs is very importnant to know. Relatively minor things tho. All in all. I liked it!
Hello, I see very useful information thank you, I’ll add it into the description ❤️ Regarding the byte change, I feel (maybe I’m wrong) the risk is about the same or less than any kind of repair that will be attempted anyway A messed up syscon could possibly be fixed but a chipped die from a messed up de-lid not so much. 🙂 If I can add some text overlay to the existing video explaining external commands I will or a pinned comment. Yep still got to finish the description and all that , adding the syscon git and dev wiki today haha Thanks for watching and the tips :)
pls can u explain how to solder the wire to the ground pad on the superslim model? i can not get the pad tinned and without that wire i only get auth1 error :(
You can also try getting an alligator clip and connecting to the ground strip that runs around the outside of the board or on any part of the shielding.
Did you copy MY checksum entry or go off yours 3 beeps and red indicates the checksum is still invalid As in the video don’t write what I write, go off your own values
@@Slot1Gamer I FIXED IT YOU HAVE TO SOLVE ALL OF THE ERRORS FOR EXAMPLE Addr:0x000032fe should be 0x528c .WHAT YOU SHOULD WRITE : w 32fe 8c 52 AND YOU HAVE TO DO THAT TO ALL OF THE ERRORS UNTILL YOU NO LONGER SEE THE SUM WORD
@@Slot1Gamer A few. 2 slims, 3 fats. Mullion works fine it authenticates every time. Sherwood never worked on a all the ones I tried. Checked and rechecked everything and always get a Auth error.
@@ramiq7932 you can check the resistance to ground on the RX and TX lines on the sherwood machines and compare to a known good unit. Do all the SW you are trying attempt to power up? or atleast have 5V_SB present
i've soldered some stuff before but this is going to be my first real project. i have DIA-001 and plan on buying a broken one on ebay to practice but do i need to use flux before soldering the jumpers to the board?
It always says Auth1 response invalid.... :( No matter the orientation of the RX and TX cables. I use a TTL to USB C from the Arduino box. That should work too, wouldnt it?
The worst console ever made. Sony just needs to make this up to customers and make a complete backwards compatible console finally so we won't have to buy 10 PS3s just to have 1 fully functional one. This is a great video but it is way too much for a beginner. This repair requires an electrical engineer degree before attempting it.
@@Slot1Gamer exactly. I didn't abuse my console like most kids and hardcore gamers did. But mine still got that YLOD. And I cleaned it from dust and kept it cool. I even waited for a year to get one cause everyone knows when products first come out, there will usually be bugs in them and then later they make a new and improved one. And then they put out the 80gb fat PS3 with Metal Gear Solid 2 and backwards compatible. I was first in line for it and excited to have it. Today I regret getting it because I invested my time, love and money on it and had great times on it. Now it's all just a memory that will never be relived.
I was the same, my launch 60gb model was used sparingly but still died 🥲 Sadly it’s partly Nvidias fault The 90nm and some 65nm ps3 gpus will fail no matter what you do, they were a design flaw from the start. There is a fix however but it is complex requiring replacing the gpu
@@Slot1Gamer I noticed that also. You have to be a very good electrical engineer to actually fix it and even then it's a risk because if that don't get the GPU out right, that means your beautiful PS3 is gone forever. I don't know if I want to risk that. I'm hoping for a full proof solution.
@@Slot1Gamer the problem is I did tried the cmd one (the black one that pops along with the other GUI) but can't even type there no matter what there's not even a cursor on it to begin typing
The command line version is a different download github.com/db260179/ps3syscon Because you are inputting a lot of commands the gui has a character limit. I am working on a streamlined tutorial for editing fan tables This one requires Python to be installed
As mentioned by RipFelix, the bring up command works better with the command line version of the tool
For an up to date error code explainer check the DevWiki: www.psdevwiki.com/ps3/Syscon_Error_Codes
GitHub for the Syscon Tool (incase updates or you need the CLI ver): github.com/db260179/ps3syscon
Didn't know you had a channel
good
I just got a CECHK model recently that's YLOD'd so this tutorial was perfect timing for me, thank you for providing a clear and understanding tutorial for this 👍
No problem
Let me know how you go with it!
hey how's going
Update: took me longer to get to it then expected, irl stuff and other projects aside. It actually works out well! I got the error codes off the PS3 and now sooner or later I can potentially start fixing it up
THIS is what a tutorial should look like. Thank you.
Thank you, please share if you like ☺️
it took a while to make haha
This video is incredibly professional!!!
Now i am sure to buy some tantalums.
Feel so proud to troubleshoot a problem with a clear step by step like that.
You are super prepared! Congratulations. But all of this only to show a log is insane.
I have had my PS3 80GB CECHK 11 for 15 years and still works as the first day.
Nieither error or overheat. I hope it keeps going for some years left!
Lucky, looks like you have the 65nm version, probably the later revision that was fixed.
@@Slot1Gamer Exactly. I confirm that I have the 65nm version.
I was lucky with this console absolutely!
So lucky :)
Good video with straightforward information to set up a PS3 Syscon device on an RPI Pico. Thank you, I was able to double-check my work with this and it was greatly appreciated.
Great tutorial, going to test on a 3 bips blinking red light CECHK01 here. Just one question: at 11:39, in the screen the command reads EEPSUM, but on the app screen you typed EEPCSUM. Is it a typo, or both commands work the same, or just the one you typed (EEPCSUM) is the right one? Thanks!
sorry type EEPCSUM
Really good tutorial! =)
Thanks :)
I get "scopen response invalid" and now my PS3 is stuck in this auto 3 beep mode. Update set it back as FF, disabled internal mode no more auto 3 beeps, since you don't really need to set it to that. My error code is 3003.
didnt work with dyn 001 always auth error i tried swapping tx and rx and still nothing
Such a great video
Thank you ☺️
I've done everything but when I try to load cxrf option i get this error (scopen response invalid) can someone help me
Thank you for this! I just need to learn soldering and ill fix my 40gig non BC phat PS3!
I followed all the steps for my VER.001 ps3 but when I connect the syscon to the pc and click "Auth" it shows the error that you mentioned in the video. I tried swapping the cables but nothing changes. I tried downgrading python to 3.10 (as this program seems to work on that version of Python), but it didn't help. I also tried using another pc with windows 10 this time (instead of 11), but I get the same error.
I've been troubleshooting for an entire day at this point but I'm unable to find a fix.....do you have any idea what the problem could be?
Is the uart adapter showing in device manager correctly, sometimes windows installs the wrong driver.
It may be showing as libusb or something, manually change the driver by going update (right click on the device > “let me choose” > then manually select a different driver from the list
Also if you are using bread board jumpers, sometimes the wires aren’t crimped and have no connection inside (this happened to me yesterday)
Also confirm ground is connected
When installing python ensure add to path check box is selected
@@Slot1Gamer I manually checked continuity between the cables and the motherboard but the device was indeed being shown as an "unrecognized device", so it must have been the drivers not being installed correctly. I somehow still managed to make it work via the cmd version and I got 1002 and 2114 errors, so my NEC/TOKINs must be broken.....
It's a shame because that was my uncle's PS3 and he gifted it to me in 2015....I have so many memories of me and him playing Gran Turismo and GTA IV but the fix is not worth it imo; I'll probably get a used PS3 slim but I'll lose all my data that was on the old hdd.
Thanks for the help anyway, it could be helpful in a future troubleshoot 😁
Is it possible to change IDPS from SYSCON? without jailbreak, webman etc.
good work
the console can be turned on with the UART controller connected? my console is bricked in recovery mode, doesn t recognize usb either. That's happened after i tried to install cfw.
1. i cleaned up the console and drilled some holes in case for a better air flow (ps3 CECHG04) but i lifted up the disc drive destroying the flex cable grip from the MB.
2.Then i started to dump syscon with an web tool, all good until i had trying to install "EvilNat 4.90.1 CFW " . I didn't know that the console checks the disk drive while updating the firmware
3.Console entered into a boot loop which every time finished with an error, so i cut out the power supply. When the console turn on again in Recovery mode, all usb fat32 formated with ps3 update on it becomes unrecognizable. it can't rebuilt databases or format HDD.
Yes it can, but it sounds like you may need to use a hardware nand flasher to fix your system
Did you try the evilnat no BD update image if available
@@Slot1GamerShall E3 NOR FLASHER be of any help for this ?
In this case as it sounds like NAND/NOR corruption yes but it’ll require a bit of work.
Hi, I have a fat 80gb CECHL04 with ylod...which syscon program should I use?
go to the time 2:47 i was looking for the same thing
@ Thanks!
When I run the script it gives error python310.dll "LoadLibrary: Pylnstalier: FornatMessageW failed" 😢
Did you install python
In the installer also click add to path
@Slot1Gamer I discovered the problem! the minimum version of Python that the script required was 3.10. I was using Windows 7 where the last version released was 3.7, so it gave me an error.
Can you use this to get the ERK EID Key to put on a new motherboard?
My SW never auth. i dont get what i am doing wrong. Can you help pls?
Is your wiring ok
And what’s wrong with your console
@@Slot1Gamer yes. I have done everything like on the video. My old retro PS3 works fine,mi get all errors. But Im the Slim i cant get any.
Does the slim get any power?
And have you tried swapping the RX and TX wires
@@Slot1Gamer yes She hás power, and did try a couple of Times Change the cable. I really cont get why i cant get the errors on the PS3 Slim. My PS3 60g works fine a d tell me everytime the errors.
Did you manage to fix it, because i have the same issue
What about error A0093004 on a slim 20xx
Google " PS3 SYSCON Error Code 3004" Has lots of Info. Small sample:
"This error is linked to inadequate filtering on the RSX_VDDC power line. A certain range of voltage ripple and noise can trigger this error before it becomes severe enough to cause an RSX_VDDC Power Failure (3004)."
@@Islamisthecultofsin so this would most likely be a nec/tokin or power supply problem right?
@@giorgesuarez5807 Master Yuri95 gave this reply for the 3004 error: "theres a failed component along the power VRM".
@@giorgesuarez5807 Salm-O-Nella
•
1y ago
•
I have the same problem on COK-002 Board, i've tried to replace Q6001 and Q6002 Mosfets, IC6002 and IC6003 Voltage Regulators, and IC6201 Cpu Power Processor without success. Obviously i replaced NEC-TOKIN with 470uF Tantalum Caps, 4 for each NEC-TOKIN, and done the bridge with 2.5mm^2. All voltages and enable signals are ok, resistance between caps and gnd is 3.5ohms, so that's also ok.
Tomorrow i will try to replace IC6200..
@@giorgesuarez5807 olongrieving
OP
•
2y ago
•
omg never mind! i did some basic tracing from the fuse through the vias and found another shorted capacitor as shown in the first link (pic from the donor board).
YLOD IS GONE. my first time. hurrah. newish to electronics repair so this is a pretty big ass dopamine hit. who knows if the console is stable but i'll take the win.
I have 1200 error I changed the thermal paste but the same ylod... Is there any solution please?
Small change excessive noice from the NEC caps could cause it but it’s likely a physical issue with die or bga
Try replacing the paste under the cpu lid
@@TheGlitchyMario yes made assumption that's what they meant 😅
@@Slot1Gamer what if I apply some flux and heat the cpu?
These boards take insane amounts of thermal energy to reflow the cpu
Warming up the cpu may bring it back temporary and that would indicate a solder bump issue on the die but those are rare for ps3
Most issues lie in the gpu
11:39 is it "eepsum" or "eepcsum" 😶 your caption says something different to what you wrote on the machine and it kinda sounds like you said a mixture of the two 😅
Eepcsum
Sorry for confusion
@Slot1Gamer thank you, just wanted to make sure. Was pretty sure it much have been that since it worked on the pc 😆 great video !
@@Slot1Gamer haha i kept writing for 15 minutes EEPSUM , i was driving mad
If you dont get a red or yellow light, can you still use SYSCON to diagnose? I have a BC Fat that doesnt boot, but also doesnt red or yellow light either. Stays green, just never boots with screen artifacts and TV knows something is plugged in. Thank you!
Should be able to yes, the console has power and sounds like it’s hanging on GPU startup
For this I suggest getting the log, then run bring up command (you may want to use the command line version of the tool for bring up )
My PC doesn't recognize the usb uart, I installed the drivers and it still doesn't appear as a port, what could it be?
Sometimes it installed as a different device.
You need to find what it showing up as in device manager and manually choose the driver (update driver > choose driver from list)
Then it will install as FTDI
@@Slot1Gamer thanks, i will try
I do that, but now the program when i press auth gives the error permissionerror, what i do?
Try moving the program to a usb drive or to C drive, if you run from desktop as admin sometimes it can’t access the files in that location
I believe the GUI has a character limit and commands like bringup won't give you the full read-out. Given that this is one of the more useful commands it makes the current GUI not awesome in some regards.
It seems to bring up the error log fine which has a large character count
You can scroll inside the response window
Error log is probably the main reason people will use this anyway
Nice work.
A few things. There is more information about the bringup string that doesnt show when the Power On Sequence reaches a certain point, namely the bittraining and bootloader string. Both of which require you the hit enter a second time to display the rest of the log. IIRC the GUI didn't display it. It adds a layer between you and the uart script that can also mess up commands, which is why I didn't include it in my tutorial. I also wouldn't have told them to enable internal access on mullion as a default. Changing a byte is a step people can and do mess up. And if they accidentally change the wrong address it can be hard to fix. So I would have liked to see you first tell them the external commands they can use before adding that they could proceed to internal if they are adventurous.
The errorcode section probably should just link them to the dev wiki where explantions can benifit from improvments over time. I dont want to comment io the accuracy of the code explanations you offered, but they can be misinterpreted easily and the step numbers are missing. And extreemly important. This is a habbit I've been trying to get people to break. The last four digits are not the whole picture. We NEED the step # also. It can litterally be the difference between a fuse that blew or a dead GPU. When an error occurs is very importnant to know.
Relatively minor things tho. All in all. I liked it!
Hello,
I see very useful information thank you, I’ll add it into the description ❤️
Regarding the byte change, I feel (maybe I’m wrong) the risk is about the same or less than any kind of repair that will be attempted anyway
A messed up syscon could possibly be fixed but a chipped die from a messed up de-lid not so much. 🙂
If I can add some text overlay to the existing video explaining external commands I will or a pinned comment.
Yep still got to finish the description and all that , adding the syscon git and dev wiki today haha
Thanks for watching and the tips :)
pls can u explain how to solder the wire to the ground pad on the superslim model? i can not get the pad tinned and without that wire i only get auth1 error :(
You can also try getting an alligator clip and connecting to the ground strip that runs around the outside of the board or on any part of the shielding.
@@Slot1Gamer yes! i was able to do it that way. thank you! 🙏🏼
IT DOESNT WORK AFTER I FIXED THE CHECKSUM JUST LIKE YOU DID NOW WHEN I TURN ON MY CONSOLE IT JUST BEEPS 3 TIMES AND IT FLASHES RED
Did you copy MY checksum entry or go off yours
3 beeps and red indicates the checksum is still invalid
As in the video don’t write what I write, go off your own values
@@Slot1Gamer I FIXED IT YOU HAVE TO SOLVE ALL OF THE ERRORS FOR EXAMPLE Addr:0x000032fe should be 0x528c .WHAT YOU SHOULD WRITE : w 32fe 8c 52 AND YOU HAVE TO DO THAT TO ALL OF THE ERRORS UNTILL YOU NO LONGER SEE THE SUM WORD
Hi. I have problem with sur 001 motherboard. I soldered pins as showed but I only get AUTH error. Does it mean that Syscon is broken?
Have you tried reversing the RX and TX
@@Slot1Gamer yes I tried and unfortunately it didn’t work
Is console getting standby power
Any idea why I can't get any Sherwood models to work with this? Mullion works fine.
How many Sherwood have you tried?
Try swapping RX and TX and check the ground
@@Slot1Gamer A few. 2 slims, 3 fats. Mullion works fine it authenticates every time. Sherwood never worked on a all the ones I tried. Checked and rechecked everything and always get a Auth error.
@@ramiq7932 you can check the resistance to ground on the RX and TX lines on the sherwood machines and compare to a known good unit.
Do all the SW you are trying attempt to power up? or atleast have 5V_SB present
@@Slot1Gamer Will check. They all have YLOD issues but power up to standby just fine. It's really weird. Zero issues pulling Mullion codes.
Got the same problem, my SW never authenticates. I cant tell what is wrong.
bringup says unknown command mullion
What can I do if my PS3 gets no power at all?
power supply issue
i've soldered some stuff before but this is going to be my first real project. i have DIA-001 and plan on buying a broken one on ebay to practice but do i need to use flux before soldering the jumpers to the board?
Yes use no clean soldering flux
Does the checksum need to be put back after your done getting the codes?
No
It always says Auth1 response invalid.... :( No matter the orientation of the RX and TX cables. I use a TTL to USB C from the Arduino box. That should work too, wouldnt it?
i have the same problem :(
@@yuongluka I couldn't get it to work and eventually gave up
mine says F0000006..........
mine too how do i fix that
@@yaboii415 video says it all you must first diagnose it
Can i use teensy 2 for UART?
Maybe
forum.pjrc.com/index.php?threads/teensy-as-usb-to-uart-converter.27940/
The worst console ever made. Sony just needs to make this up to customers and make a complete backwards compatible console finally so we won't have to buy 10 PS3s just to have 1 fully functional one. This is a great video but it is way too much for a beginner. This repair requires an electrical engineer degree before attempting it.
Haha you can do it!
I’m surprised there wasn’t a big class action lawsuit over it.
@@Slot1Gamer exactly. I didn't abuse my console like most kids and hardcore gamers did. But mine still got that YLOD. And I cleaned it from dust and kept it cool. I even waited for a year to get one cause everyone knows when products first come out, there will usually be bugs in them and then later they make a new and improved one. And then they put out the 80gb fat PS3 with Metal Gear Solid 2 and backwards compatible. I was first in line for it and excited to have it. Today I regret getting it because I invested my time, love and money on it and had great times on it. Now it's all just a memory that will never be relived.
I was the same, my launch 60gb model was used sparingly but still died 🥲
Sadly it’s partly Nvidias fault
The 90nm and some 65nm ps3 gpus will fail no matter what you do, they were a design flaw from the start.
There is a fix however but it is complex requiring replacing the gpu
@@Slot1Gamer I noticed that also. You have to be a very good electrical engineer to actually fix it and even then it's a risk because if that don't get the GPU out right, that means your beautiful PS3 is gone forever. I don't know if I want to risk that. I'm hoping for a full proof solution.
I think eventually someone will start selling pre-modified boards like with the original Xbox and it’s CPU upgrade
I tried modifying the 34fe address line coz i change the fan controls for that, as you can see here even tho I've already written the new value for the 34fe line it still didn't changed in the eepcsum. in fact, why can't i change/ overwrite the 34fe line anymore? it still shows this weird should be value of 0x771c what did I do wrong?
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x771c
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
fantbl setini 1 p0 00.00 48.00 0x33
fantbl setini 1 p1 40.00 58.00 0x40
fantbl setini 1 p2 46.00 64.00 0x47
fantbl setini 1 p3 54.00 68.00 0x4d
fantbl setini 1 p4 56.00 72.00 0x54
fantbl setini 1 p5 60.00 74.00 0x5a
fantbl setini 1 p6 66.00 76.00 0x66
fantbl setini 1 p7 70.00 78.00 0x80
fantbl setini 1 p8 72.00 80.00 0x99
fantbl setini 1 p9 73.00 85.00 0xff
tshutdown setini 1 85
fantbl setini 0 p0 00.00 58.00 0x33
fantbl setini 0 p1 48.00 68.00 0x40
fantbl setini 0 p2 60.00 72.00 0x47
fantbl setini 0 p3 66.00 76.00 0x4d
fantbl setini 0 p4 67.00 77.00 0x54
fantbl setini 0 p5 68.00 78.00 0x5a
fantbl setini 0 p6 70.00 80.00 0x66
[mullion]$
w 34fe c7 f7
w complete!
[mullion]$
r 34fe 2
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
C7 F7
[mullion]$
r 3300 200
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
33 40 48 4D 5A 66 73 80 99 FF 00 4A 00 4B 00 4C
00 4D 00 4E 00 4F 00 50 00 51 00 52 00 55 00 00
00 3C 00 3D 00 43 00 44 00 47 80 47 00 48 80 48
00 49 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF
33 40 47 4D 54 5A 73 80 99 FF 00 30 00 3A 00 40
00 44 00 48 00 4A 00 59 00 4E 00 5B 00 5F 00 00
00 28 00 2E 00 36 00 38 00 3C 80 50 00 46 80 51
00 52 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF
33 40 48 4D 5A 66 73 80 99 FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 33 FF 01 00 00 FF FF FF FF FF FF FF FF FF
33 40 48 4D 5A 66 73 80 99 FF 00 3C 00 3D 00 3E
00 3F 00 40 00 41 00 42 00 43 00 44 00 47 00 00
00 27 00 30 00 36 00 37 80 3A 00 3B 00 3C 80 3C
00 3D 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF
33 40 48 4D 5A 66 73 80 99 FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 33 FF 01 00 00 FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 00 4D 14 FF FF FF FF FF FF FF 00 FF 00 FF
54 00 55 00 02 00 5E 00 5F 00 02 00 FF FF FF FF
02 00 46 00 47 00 02 00 FF FF FF FF 02 00 FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF C7 F7
w 34fe c7 f7
w complete!
[mullion]$
eepcsum
Addr:0x000032fe should be 0x52b7
sum:0x80ab
Addr:0x000034fe should be 0x771c
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
Try using the command line version of the syscon tool
You may be hitting a character limit on the GUI
@@Slot1Gamer the problem is I did tried the cmd one (the black one that pops along with the other GUI) but can't even type there no matter what there's not even a cursor on it to begin typing
The command line version is a different download
github.com/db260179/ps3syscon
Because you are inputting a lot of commands the gui has a character limit.
I am working on a streamlined tutorial for editing fan tables
This one requires Python to be installed