Cechb01 on 2.35 unable to boot into safe mode

Not sure if it was you or someone else, but the other day someone was asking if there is some way to make a flash dump using the syscon UART commands
That question have a point, because the fact is that exists a data communication channel in between syscon and flash, is used at the first steps of the bootchain, is stuff related with security and the bootloader
The mistery is if there is some UART commands (from the internal or external ones) that could allow to read flash, something like that could be very handy because the solder job required for the UART syscon access is a loooot easyer than soldering in the NAND's flash chips

Anyway, brainstormings appart... the other way to get a flash dump is using a flasher (teensy recommended), but the soldering job is tricky
https://www.psdevwiki.com/ps3/Teensy_2.0++
 
I'll definitely look into that, I hate micro soldering but if I have to I have to lol

Luckily I have another cechb01 laying around with ylod but the reason for getting this one was it was "working fine other than not reading games anymore" guess I got stuck with but but now I'm determined to get it working again.

Sent from my SM-G965U using Tapatalk
 
I think that poor B got yloded, not bricked, so don't touch the nand just yet. I'd probably think in heating the NECs a bit just to see if the console shows image again, as its literally trying to do that. If you got errors messages while updating then there shouldn't be any brick, also is not surprise finding people that bought old fatties that went into ylod just in a few days or hours. You should have had tested the console with heavy games, at least the U2 demo, but updating was also a problem.. Though situation.
 
RCWD21 said:
I'll definitely look into that, I hate micro soldering but if I have to I have to lol

Luckily I have another cechb01 laying around with ylod but the reason for getting this one was it was "working fine other than not reading games anymore" guess I got stuck with but but now I'm determined to get it working again.

Sent from my SM-G965U using Tapatalk
Click to expand...
Oh get yourself a 360 clip.
The soldering is way to small If you have never soldered via a magnifying glass then your going to short or burn a pad off.
And validate the dump with all the validators.
Do not patch the dump without posting on here as any slim possibility its a bad dump will brick that console for good.
 
ElGris said:
I think that poor B got yloded, not bricked, so don't touch the nand just yet. I'd probably think in heating the NECs a bit just to see if the console shows image again, as its literally trying to do that. If you got errors messages while updating then there shouldn't be any brick, also is not surprise finding people that bought old fatties that went into ylod just in a few days or hours. You should have had tested the console with heavy games, at least the U2 demo, but updating was also a problem.. Though situation.
Click to expand...
Your giving bad advice.
Its not a ylod and this can happen from a console thats giving error messages
 
Oh just remembered
You won't get into recovery with your 2.35 console as its not part of the os until fw 2.50
You will need a fsm dongle and you should be able to reinstall your firmware that way instead of doing a dump and patch.

Your console is staying on long enough sk you can trigger the dongle
 
baileyscream said:
Your giving bad advice.
Its not a ylod and this can happen from a console thats giving error messages
Click to expand...
Yea I'd have to agree with you on this, I'm not as experienced as a lot of you on here but I know this isn't a ylod issue. It's something else.

I have 10 fat ps3s ranging from a b and e models to h k and l models that have all had various issues but this one by far is the most odd. Ive had consoles fail to update before but getting into safe mode always solved the issue for me.

I'm beginning to wonder if the person(s) before me maybe failed to properly downgrade the console so they could claim it was on 2.35. Its just speculation but at this point I think anything could go.

I have most of what I'd need to solder in a teensy but if there's a way to do it easier then by all means I'm going that route, no need to make it more complicated than it needs to be.

Sent from my SM-G965U using Tapatalk
 
baileyscream said:
Oh just remembered
You won't get into recovery with your 2.35 console as its not part of the os until fw 2.50
You will need a fsm dongle and you should be able to reinstall your firmware that way instead of doing a dump and patch.

Your console is staying on long enough sk you can trigger the dongle
Click to expand...
Well thats good news! I've read about the dongles in the past but never went past that. Can you give me some pointers on where to find them?

Sent from my SM-G965U using Tapatalk
 
RCWD21 said:
Well thats good news! I've read about the dongles in the past but never went past that. Can you give me some pointers on where to find them?

Sent from my SM-G965U using Tapatalk
Click to expand...
Try and get an e3 card reader i have all the files for that

There is a list of fsm dongles on the wiki

The teensy2.0++ is on the list but I never got that to work but you could try while you have one

https://psdevwiki.com/ps3/Downgrading_with_PSgrade_Dongle

You may want to do the remarry once it installs your firmware and brings the console back to life
But before that install mlt 3.55
Its a 3.55 cfw with bdvd emu patches so it should install
You may need to have a 2.35 nobd making so it will install in fsm too.
 
Last edited:
baileyscream said:
Try and get an e3 card reader i have all the files for that

There is a list of fsm dongles on the wiki

The teensy2.0++ is on the list but I never got that to work but you could try while you have one

https://psdevwiki.com/ps3/Downgrading_with_PSgrade_Dongle
Click to expand...
Do you happen to know where I could locate an e3 card reader? That seems to be the easiest solution and something that could easily be used console to console when needed.

Trouble is they seems to be like hens teeth nowadays [emoji53]

Sent from my SM-G965U using Tapatalk
 
baileyscream said:
Your giving bad advice.
Its not a ylod and this can happen from a console thats giving error messages
Click to expand...
I think messing with the nand it's even dangerous, mainly 'cause if you're not cautious enough, it could be damage, but that depends of the user. In this case a little bit of heat on the NECs won't do nothing bad, and it's definitely not a bad advice talking about an old lady like this. Now, the best choice would be to use the SYSCON trick, but that requires to get an adapter. If you wanna the securest option, I'd choose this one.

Talking about what the OP said, the console failed to update due an error related with the HDD (I think). And update that fails several times like this won't give you such a problem, even with different daughter boards. Long GLOD and then turn off. For me this isn't soft brick, or even a brick, it's hardware related, as I couldn't find a BC PS3 on youtube behaving like this with a knowleged soft/brick, all of them just instant YLOD.

Just my point of view, obviously, the OP can choose whatever he wants.
 
ElGris said:
I think messing with the nand it's even dangerous, mainly 'cause if you're not cautious enough, it could be damage, but that depends of the user. In this case a little bit of heat on the NECs won't do nothing bad, and it's definitely not a bad advice talking about an old lady like this. Now, the best choice would be to use the SYSCON trick, but that requires to get an adapter. If you wanna the securest option, I'd choose this one.

Talking about what the OP said, the console failed to update due an error related with the HDD (I think). And update that fails several times like this won't give you such a problem, even with different daughter boards. Long GLOD and then turn off. For me this isn't soft brick, or even a brick, it's hardware related, as I couldn't find a BC PS3 on youtube behaving like this with a knowleged soft/brick, all of them just instant YLOD.

Just my point of view, obviously, the OP can choose whatever he wants.
Click to expand...
Now that I have all my supplies my plan was to try and get the syscon route working but this console will only stay on for about 50 seconds, is that enough time to actually complete anything via syscon?

Sent from my SM-G965U using Tapatalk
 
RCWD21 said:
Now that I have all my supplies my plan was to try and get the syscon route working but this console will only stay on for about 50 seconds, is that enough time to actually complete anything via syscon?

Sent from my SM-G965U using Tapatalk
Click to expand...
Yes, If I'm not mistaken, you power the SYSCON up with an external PSU and then you get the codes. As all the guys that are working on this project have PS3s with instant YLOD. Maybe this route could let you know if you're having problems with the RSX or CELL powering, or it's something else.
 
ElGris said:
I think messing with the nand it's even dangerous, mainly 'cause if you're not cautious enough, it could be damage, but that depends of the user. In this case a little bit of heat on the NECs won't do nothing bad, and it's definitely not a bad advice talking about an old lady like this. Now, the best choice would be to use the SYSCON trick, but that requires to get an adapter. If you wanna the securest option, I'd choose this one.

Talking about what the OP said, the console failed to update due an error related with the HDD (I think). And update that fails several times like this won't give you such a problem, even with different daughter boards. Long GLOD and then turn off. For me this isn't soft brick, or even a brick, it's hardware related, as I couldn't find a BC PS3 on youtube behaving like this with a knowleged soft/brick, all of them just instant YLOD.

Just my point of view, obviously, the OP can choose whatever he wants.
Click to expand...

No your giving bad advice.
Ylod = yellow light of death
Its not giving a yellow light so the Syscon isn't in panic

Heating the chips up WILL create damage regardless of how long you do it.

Messing with the nands (there are two) is a risk but thats why we have validators and highly experienced people on here that DO know what there doing.

I fail to see how age can be an excuse for thinking bad advice is good advice

What Syscon trick? And what adaptor?

No its failed to update due to the drive board. Possibly a dead nor chip or bad files on that chip. But this does appear to be the issue with it not reading discs being the key point.

Yes it will give you this update problem thats why we make nobt + nobdvd firmware to get out of this loop

Ok this is not a glod
Its a known issue and the reason why Sony added the recovery menu into 2.50 firmware.
Its software thats caused this.

Your trying to give advice on something you have no idea about.

Trust me I'm good at what I do. But your wrong and giving wrong advice.
 
RCWD21 said:
I saw that, I'll do a bit of digging and see if they're legit or not.

Are there any others on the long list that you would recommend? Finding any of them seems to be a real challenge

Sent from my SM-G965U using Tapatalk
Click to expand...
Finding the files for them is just as hard too.
I thought you had a teensy++2.0
If you do then try that as a fsm tool
 
baileyscream said:
No your giving bad advice.
Ylod = yellow light of death
Its not giving a yellow light so the Syscon isn't in panic

Heating the chips up WILL create damage regardless of how long you do it.

Messing with the nands (there are two) is a risk but thats why we have validators and highly experienced people on here that DO know what there doing.

I fail to see how age can be an excuse for thinking bad advice is good advice

What Syscon trick? And what adaptor?

No its failed to update due to the drive board. Possibly a dead nor chip or bad files on that chip. But this does appear to be the issue with it not reading discs being the key point.

Yes it will give you this update problem thats why we make nobt + nobdvd firmware to get out of this loop

Ok this is not a glod
Its a known issue and the reason why Sony added the recovery menu into 2.50 firmware.
Its software thats caused this.

Your trying to give advice on something you have no idea about.

Trust me I'm good at what I do. But your wrong and giving wrong advice.
Click to expand...
Drive board? You mean the daughter board? The OP said he tested others and had the same issue, how messing with the NAND would be a solution in this case if we have a hardware issue on the mobo and not the daughter board?

BTW, the OP said the console turns off, nothing else. That's why I believe it's a YLOD, and what this console does it's pretty common when you have NECs issues. And I said "HEAT A BIT" those NECs, nothing else. I don't know what are you thinking, a common reflow on the processors???

And finally, the console will give another error code for the daughter board having issues or not being present at all..
 
baileyscream said:
Finding the files for them is just as hard too.
I thought you had a teensy++2.0
If you do then try that as a fsm tool
Click to expand...
I dont have one yet but I can get one easily enough. I'm just trying to figure out the easiest way to go about this.

But as of current ive found a possible supplier for some e3 dongles but I'll have to wait and see if they're truly available or not.

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

Similar threads

Back
Top