PS3 I got an interesting PS3 there... (SYSCON ERROR)

Doomed_YLOD_47

Doomed_YLOD_47

Forum Noob
Hi everyone !

I decided to create this thread after buying a PS3 (CECHP04) sold as "working" a few months ago that... ended up not working ! Of course the culprit seems to be our best friend... the YLOD ! After this (small) disappointment I decided for the very first time to open a PS3 and tried to figure out what was going wrong.

My goal is to try fixing it and learn more about this beautiful machine on the way !

A few weeks ago I bought a UART and connected it to the test pads of my motherboard (VER-001), after installing Python and setting up everything I managed to access the SYSCON, but when I try to read the error log... even after several attempts, I get this :
Microsoft Windows [version 10.0.22631.3737]
(c) Microsoft Corporation. Tous droits réservés.

C:\Users\Utilisateur\Desktop\Logiciels\Syscon (PS3)\ps3syscon-master\Linux>python ps3_syscon_uart_script.py COM3 SW
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE CLOCK
# 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 FFFFFFFF

Please note that I have tried to clear the logs with "errlog clear", rebooted the console several times with "bringup" and "shutdown", checked my solder connection, and of course unplugged the console several times.

So after getting basically no errors, but still having a YLOD, I started documenting myself on what to do in this case, and surprisingly there is not that many people speaking about this issue. I found a few forums here and on Reddit speaking about what seems to be the very same problem, but nobody ever replied, so I am trying my luck here with you !

My question
Has anyone ever had this issue before ? Do you have any tips or tricks to try ? I am a newcomer in this PS3 fixing universe, but I am happy to chat with anyone about that !

Video on the YLOD process
As I am a new member, it seems that I unfortunately do not have the right to post any link in my posts (which is fine, I understand the risks of spam), so I had to get creative to give you chance to see the bootup process of my PS3 which I think could help). Below you will find a binary code that you can copy and paste on any online converter. It will generate you a Google Drive link towards my video. If any Admin see this and do not agree with my workaround, please tell me and I will remove this section ASAP. :
01101000 01110100 01110100 01110000 01110011 00111010 00101111 00101111 01100100 01110010 01101001 01110110 01100101 00101110 01100111 01101111 01101111 01100111 01101100 01100101 00101110 01100011 01101111 01101101 00101111 01100110 01101001 01101100 01100101 00101111 01100100 00101111 00110001 01000100 01110000 01100010 00110011 01000010 01101000 01100100 01011000 01010001 01001111 01000111 01110010 00110010 00110101 00110101 00110001 01101101 01110111 01011001 01110110 01010100 01100001 00110001 01110011 00110000 01100001 01110101 01111001 01001001 01001100 01100001 01010000 00101111 01110110 01101001 01100101 01110111 00111111 01110101 01110011 01110000 00111101 01100100 01110010 01101001 01110110 01100101 01110011 01100100 01101011

Summary of the Playstation informations
  • Model : CECHP04
  • Motherboard : VER-001
  • Motherboard version (Syscon reply after typing "version") : Sherwood Version = 0.17.0
  • Message on the CMD (Idk if it is useful) :
    # [SSM] Bringup Start.
    # [SSM] PS0 ok.
    # [SSM] PS1 ok.
    # [SSM] PS2 ok.
    # [SSM] PS3 ok.
    # [SSM] PS4 ok.
    # (PowerOn State)
    #!
    #!Boot Loader SE Version 2.4.5
    #!(Build ID: 3163,33519,
    #!Build Data: 2008-07-14_20:31:16)
    #!
    #!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
    #!
    #![INFO]: Connecting to Debug Device (SB UART)
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!
    #!Boot Loader SE Version 4.7.6 (Build ID: 5292,50550, Build Date: 2015-08-11_11:15:27)
    #!SDK Version: 476.000
    #!Copyright(C) 2015 Sony Computer Entertainment Inc.All Rights Reserved.
    #![INFO]: === eXtreme Data Rate Memory Subsystem ===
    #![INFO]: (Configured Memory
    #!S
    #!ize per single XIO channel: 128 MBytes.)
    #![INFO]: XIO channel[0] is available.
    #![INFO]: XIO channel[1] is available.
    #![INFO]: ---> Total 256 MBytes are now in use.
    #![INFO]: SPU enable [0, 2, 3, 4, 5, 7] 10111111
    #![INFO]: BE:11S DD1.0, SB:SX1.2
    #![ERROR]: 0xb0000
    #!0
    #!04 lv1ldr stop with stopcode 35
    #!load lv1 fail
    # [SSM] Cond/Fatal received, msg=2649.
    # [SSM] Fataldown Start.
    # [SSM] Fataldown ok.
    # (PowerOff State) (Fatal)
    # CODE CLOCK
    # 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 FFFFFFFF
 
Last edited:
GuilloteTesla said:
Just speaking out loud, but have you checked the internal battery?. Maybe it's all drained and can't hold the logs. Not really sure that would be the cause of blank logs, but could be possible.
Click to expand...

Hi Guillote ! Thank you for your reply !

You were indeed right, I disassembled the board and the Sony CR2032 was as dead as it could be... but after replacing it with a brand new one the issue seems to be the same, that is... really weird !

I attempted to clear the logs, boot the console, shut it down, unpluged it, but nothing !
 
Mmm, it's really weird. Try booting up your console normally, let the boot process fill in the SYSCON logs. Then, check if there are some data on the logs.
 
Really interesting defect. I've never seen anything like it either. Normally the Syscon is always able to save some kind of error code. As it looks with you, it does this too, but the error codes themselves are defective. Is it possible that the Syscon itself is faulty and therefore cannot store the correct error codes? Or that its power supply is interrupted before it can "remember" what has happened. Can you tell us what type of YLOD it is?
 
Hi guys ! Thank you for your messages !

GuilloteTesla said:
Mmm, it's really weird. Try booting up your console normally, let the boot process fill in the SYSCON logs. Then, check if there are some data on the logs.
Click to expand...

So, I just tried that and here is what happens on my device.

  • Step #1 : I connect the TTL to the PS3, turn on the power button (on the back), authenticate via the CMD, and finally I then turn on the console.
  • Step #2 : I press the front Start/Stop button, the console boot up for approx 4/5 seconds, and then goes red (flashing light) (you can check the video on my original post to see how it looks/sounds)
  • Step #3 : I wait for about a minute to see if I have any message on the CMD, but nothing, so I do a random command (in this case "bringup" just because the console is already blocked in it's red flashing light)
  • Step #4 : The CMD wakes up, show the bringup command process :
Press Ctrl+C to exit
>$ bringup
FFFFA605
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)

And then show this :

#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!Boot Loader SE Version 4.7.6 (Build ID: 5292,50550, Build Date: 2015-08-11_11:15:27)
#!SDK Version: 476.000
#!Copyright(C) 2015 Sony Computer Entertainment Inc.All Rights Reserved.
#![INFO]: === eXtreme Data Rate Memory Subsystem ===
#![INFO]: (Configured Memory
#!S
#!ize per single XIO channel: 128 MBytes.)
#![INFO]: XIO channel[0] is available.
#![INFO]: XIO channel[1] is available.
#![INFO]: ---> Total 256 MBytes are now in use.
#![INFO]: SPU enable [0, 2, 3, 4, 5, 7] 10111111
#![INFO]: BE:11S DD1.0, SB:SX1.2
#![ERROR]: 0xb0000
#!0
#!04 lv1ldr stop with stopcode 35
#!load lv1 fail
# [SSM] Cond/Fatal received, msg=2649.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)

Super weird !

I also double checked the voltage of my new CR2032 battery, and it is at 2,9V to 3,0V, well within operational range so it should be fine...

PS : By any chance, could this be linked to an incorrectly installed Python ? It looks unlikely but I am out of ideas haha

Joel_ said:
Really interesting defect. I've never seen anything like it either. Normally the Syscon is always able to save some kind of error code. As it looks with you, it does this too, but the error codes themselves are defective. Is it possible that the Syscon itself is faulty and therefore cannot store the correct error codes? Or that its power supply is interrupted before it can "remember" what has happened. Can you tell us what type of YLOD it is?
Click to expand...

Hi Joel ! You may be right, do you know if there is any way to reset/reinstall/update/check the Syscon state ?

If you want to see the exact type of YLOD my console is experiencing please check the video """link""" I put in my first post ! If you can not see it I can also try to send it to you by DM, just tell me :)
 
Last edited by a moderator:
No, I am not aware of any way to test the Syscon or to see if it works 100%. You could check in the assembled state whether it gives you an error code via LED. RIP Felix made a video on Youtube about this. Apparently, the Ps3 can also output a 4-digit error code like the Xbox 360, so you can rule out whether it is an error on your part when reading out and whether it really is the Syscon.
 
Doomed_YLOD_47 said:
So, I just tried that and here is what happens on my device.

  • Step #1 : I connect the TTL to the PS3, turn on the power button (on the back), authenticate via the CMD, and finally I then turn on the console.
  • Step #2 : I press the front Start/Stop button, the console boot up for approx 4/5 seconds, and then goes red (flashing light) (you can check the video on my original post to see how it looks/sounds)
  • Step #3 : I wait for about a minute to see if I have any message on the CMD, but nothing, so I do a random command (in this case "bringup" just because the console is already blocked in it's red flashing light)
  • Step #4 : The CMD wakes up, show the bringup command process :
Press Ctrl+C to exit
>$ bringup
FFFFA605
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
And then show this :

#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!Boot Loader SE Version 4.7.6 (Build ID: 5292,50550, Build Date: 2015-08-11_11:15:27)
#!SDK Version: 476.000
#!Copyright(C) 2015 Sony Computer Entertainment Inc.All Rights Reserved.
#![INFO]: === eXtreme Data Rate Memory Subsystem ===
#![INFO]: (Configured Memory
#!S
#!ize per single XIO channel: 128 MBytes.)
#![INFO]: XIO channel[0] is available.
#![INFO]: XIO channel[1] is available.
#![INFO]: ---> Total 256 MBytes are now in use.
#![INFO]: SPU enable [0, 2, 3, 4, 5, 7] 10111111
#![INFO]: BE:11S DD1.0, SB:SX1.2
#![ERROR]: 0xb0000
#!0
#!04 lv1ldr stop with stopcode 35
#!load lv1 fail
# [SSM] Cond/Fatal received, msg=2649.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
Super weird !

I also double checked the voltage of my new CR2032 battery, and it is at 2,9V to 3,0V, well within operational range so it should be fine...

PS : By any chance, could this be linked to an incorrectly installed Python ? It looks unlikely but I am out of ideas haha
Click to expand...

You can connect to the SYSCON, so no issues with Python or anything else.

Use the errlog command to see the latest errors during boot.
 
They are not displayed to him. There are only F's where the error code and the time should be. He could try to see if he can get them by asking for the error codes individually. For example, ERRLOG GET 00.
 
Joel_ said:
No, I am not aware of any way to test the Syscon or to see if it works 100%. You could check in the assembled state whether it gives you an error code via LED. RIP Felix made a video on Youtube about this. Apparently, the Ps3 can also output a 4-digit error code like the Xbox 360, so you can rule out whether it is an error on your part when reading out and whether it really is the Syscon.
Click to expand...

Hi Joel ! Are you speaking about the video Felix did 9 months ago ? If it is the case I think it is only related to the PS3 Slim unfortunately :/

GuilloteTesla said:
You can connect to the SYSCON, so no issues with Python or anything else.

Use the errlog command to see the latest errors during boot.
Click to expand...

Ooooh... Doing it during the booting process, really clever ! I will try this now !
 
Doomed_YLOD_47 said:
Ooooh... Doing it during the booting process, really clever ! I will try this now !
Click to expand...

I'm sorry, I didn't express myself well. What I've meant was to see the errors ocurred during boot. Using the errlog command during the boot process will have an impact only if you send the command after an error happened. If nothing occurred, no errors will be logged.
 
That's right. My mistake. I had read that it is compatible with models A to 2000. But it says it is not compatible with model A to 2000. The last option now would be to really only do what is necessary, i.e. ask for the error codes individually directly after the AUTH was successful. If that doesn't help either, I would say it's the power supply to the Syscon and that it can't remember the error codes because the power cuts out. You can communicate normally with the Syscon, so I would also rule out a connection error or incorrectly installed Python, then you would have no contact at all.
 
Alright, I just tried to spam it a few (10) times, but I (think) I still have no luck here :/

#!Boot Loader SE Version 4.7.6 (Build ID: 5292,50550, Build Date: 2015-08-11_11:15:27)
#!SDK Version: 476.000
#!Copyright(C) 2015 Sony Computer Entertainment Inc.All Rights Reserved.
#![INFO]: === eXtreme Data Rate Memory Subsystem ===
#![INFO]: (Configured Memory
# CODE CLOCK
#!S
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
#!ize per single XIO channel: 128 MBytes.)
#![INFO]: XIO channel[0] is available.
#![INFO]: XIO channel[1] is available.
#![INFO]: ---> Total 256 MBytes are now in use.
#![INFO]: SPU enable [0, 2, 3, 4, 5, 7] 10111111
#![INFO]: BE:11S DD1.0, SB:SX1.2
#![ERROR]: 0xb0000
# FFFFFFFF FFFFFFFF
#!0
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
#!04 lv1ldr stop with stopcode 35
#!load lv1 fail
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# [SSM] Cond/Fatal received, msg=2649.
OK 00000000
# [SSM] Fataldown Start.

Another attempt :

Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
# CODE CLOCK
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
#![INFO]: Connecting to Debug Device (SB UART)
# 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
OK 00000000
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!

GuilloteTesla said:
I'm sorry, I didn't express myself well. What I've meant was to see the errors ocurred during boot. Using the errlog command during the boot process will have an impact only if you send the command after an error happened. If nothing occurred, no errors will be logged.
Click to expand...

Oh my bad I saw your message a bit late here haha !

So you are suggesting to look at the errlog after the console is booted, and got into YLOD, right ? If I am not mistaken (and understood your message well) this is what I provided on my first message ?

Thank you for your (practically) real time advise here haha ! :)

Joel_ said:
They are not displayed to him. There are only F's where the error code and the time should be. He could try to see if he can get them by asking for the error codes individually. For example, ERRLOG GET 00.
Click to expand...

I missed you message sorry.

Alright, next thing to try then, I will try this tomorrow !
I was not aware of this command, thank you !

Thank you very much guys for your ideas and knowledge :encouragement:
 
Last edited:
Wait, after checking out the bringup logs, there is something else here.

Check these lines:

Code: 
#!04 lv1ldr stop with stopcode 35
#!load lv1 fail

I think the flash memory is corrupted or that some kind of FW modification went bad.

Did you try modifying lv1.self?.

Do you have any USB sticks on the USB ports?. If so, remove them and try to boot the console again.
 
Correct me if I'm wrong but isn't the Ps3 irreparable if it's not a USB stick or something but the FW itself? I mean the files were unique for each console so it wouldn't even help if he had the same model again.
 
Joel_ said:
They are not displayed to him. There are only F's where the error code and the time should be. He could try to see if he can get them by asking for the error codes individually. For example, ERRLOG GET 00.
Click to expand...

As promised I just tried the ERRLOG GET command, and unfortunately the Syscon gives back some F's

>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog get 00
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ errlog get 01
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ errlog get 02
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ errlog get 10
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ errlog get 15
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ errlog get 19
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$

GuilloteTesla said:
Wait, after checking out the bringup logs, there is something else here.

Check these lines:

Code: 
#!04 lv1ldr stop with stopcode 35
#!load lv1 fail

I think the flash memory is corrupted or that some kind of FW modification went bad.

Did you try modifying lv1.self?.

Do you have any USB sticks on the USB ports?. If so, remove them and try to boot the console again.
Click to expand...

Good spot ! I did not realise that was unusual !

I got this console second hand so I am not aware of its full story, although the seller told me that he never tried to jailbreak it. The machine also came with it's warranty seal intact, so nobody got in there before me as well. Otherwise I personally never managed to boot the console, so I never had a chance to jailbreak it myself.

Regarding the USB slots, I can confirm that I don't have anything plugged into it when I do my tests.

PS : Just to clarify, the lv1.self is usually altered when someone tries to jailbreak a console right ?

vyktormvmpay25 said:
This unit is bricked, he needs to dump and patch with hw flasher.
Special glod is going to a point where xmb is loaded but here is not the case. Lv2 not reachable. Lv1 is errors on load map from flash. Kernel if I'm not wrong.
Click to expand...

Hi vyktormvmpay ! Thank you for you message.

This seems to be a serious issue, but I am happy to give it a try ! Do you know by any chance a video or a forum link towards a tutorial that I could follow ? I have some knowledge in informatics so I may be able to try a few things if I have good indications :)

Do I need specific tools as well ?

Thank you !
 
Teensy 2++,tutorial support on psxplace and patient soldering wires. Most advanced people do desolder nor, read/write it outside board inside tsop 56 socket. Should be cheap nowadays. Nothing wrong to use bottom alt points with wires. One messy thing is to write something wrong. Make sure it is right dump before you go to write patched one
 
You must log in or register to reply here.

Similar threads

Back
Top