PS3 Bringing a CECHB01 back to life hopefully!

RCWD21

RCWD21

Member
The problem all started after updating from 2.35ofw to 4.86ofw. It bricked and now the console only powers on for maybe a minute before shutting itself off, I only get a black screen but it consistently powers on every single time.

So a long while back now I discovered the syscon thread. After several attempts to get the scripts working I gave up and waited for the day a GUI was developed which thankfully happened sooner than later.

So I pulled everything out of its slumber and tried pulling codes. I kept getting "system error" no matter what I did so I soldered wires to different ps3 with ylod and same thing. So I suspect my ttl converter is faulty as it doesn't show up anymore even after reinstalling drivers. I ordered a different one and it should be here next week.

My question is how would I go about flashing the fw to it to either overwrite whats faulty or is there a way to use a different console (would be a cechb01 with ylod or one of my various a01 models) to get a good dump from? I've seen nand clips and teensys but wanted some more input on my options. This console was working perfectly fine except for a supposed bad blu-ray drive when I purchased it. Ive updates several consoles without the drive even hooked up without issue but I guess my luck ran out on this one. I have plenty of consoles to pick from and if I have to take dumps from a couple of them then thats fine. I'd just like to get this one back up and going again.
e8f9a579a0cf62a999e29b522b47cb78.jpg


Sent from my SM-G965U using Tapatalk
 
Also if this is in the wrong section please feel free to move it! I figured it belongs in hardware mods because of the possibility of having to really dig into the board itself.

Sent from my SM-G965U using Tapatalk
 
While I don't know anything about flashing, I did have a bad ttl converter as well.
I ended up buying this one from amazon and it works well
HiLetgo FT232RL FTDI Mini USB

I'd post the link, but psx place keeps telling me it looks like spam..
 
I have a new ttl converter coming as the company's auto detection software wouldn't recognize it anymore even though it said the drivers were installed and the chip was recognized in windows itself.

I'm also gathering more things for the Teensy flasher and will be attempting to pull dumps from both of my b01 consoles. So hopefully I'll have enough to try flashing back.

My only question is do I have to patch back to the 2.35 firmware or can I patch to the 4.86 that was trying to install when all this happened?

Sent from my SM-G965U using Tapatalk
 
Nothing from your other consoles can help you with your problem. They have have specific id's and would only make the situation worse. Have you dumped the nand on this b01 yet? I would start there and run it through a checker to see what errors it spits out. It sounds like you were just unlucky and it had a hardware fault right after the firmware install. Syscon will tell you what that is so you are in the right path. More than likely a reball candidate
 
Why would it need to be reballed when it was working fine after repairing the bluray drive?

And if I cant use another console to help repair a dump what's with the threads mentioning that as an option? Not trying to come off as rude just genuinely trying to learn this stuff here.

As for syscon stuff I'll have my new reader in on Monday hopefully. Both of my b01 consoles are wired just so I can have 2 samples when doing this.


Sent from my SM-G965U using Tapatalk
 
You must log in or register to reply here.

Similar threads

Back
Top