PS3 Woes after changing to new HDD (9.99, noBD and other things)

hughb

Forum Noob
Hi there,

First of all thanks for this forum it has helped me a lot over the past four days to work out how to fix my PS3.
Great community. Also I hope this post is not too long.

I had waited 15 years for my life and finances to be in a good place to finally get a ps3 and catch up on all the games I've missed out on over the years. So I am bit bummed about all of this.

I had got this fat PS3 already used and already modded with CFW4.8, the version I think was from 2017. It is CECHL00. It was a bit old, and also had some issues playing games - it'd just turn off. I figured as it wasn't too hot, it must be an issue with PSU or the hard disk.

Taking out the hard disk, it was actually a bit over 16 years old (!!!), so I had got a spare one laying around which would work much better.

Looking at all the guides, it all seems straight forward. Although the past four days I just can't get the latest CFW, it's a bit tricky. Here's some things I've encountered so far:

Trying to update the CFW would always return 'Corrupted data'. Safe mode or through xmb it doesn't make a difference.

When I had opened the case to see if it was clean or had dust, I had put it back incorrectly and tightened the screws... Before the BD was fine, however after that it just wasn't. The cable connection is fine. All the games/apps would just black screen. No problem as some noBD downgraders I had would load still load the apps at least. No games though after I formatted the new drive. Also the old drive wont load after the new reformat.

Still feel a bit stupid though! The BD not working has made it harder than it should be.

The version is stuck at 9.99 and I had limited success with some downgrade PUPs. HABIB_CRC[700C8D5A]_FW[v3.55_HABIB_-DOWNGRADER]_PS3UPDAT.PUP had worked, although I could install apps I could not load them. So I installed the toggle_qa.pkg.

Then to run the app I changed the firmware to 3.55_Rogero_Downgrader_RSOD_NoBD. Originally I could not find how to install apps with this one... so it was a long process of the habib to install an app, then reflashing with this to run the app.

Toggle QA seemed to run okay, it had beeped a few times and restarted... All good. So it should be as simple as flashing to a newer firmware right?

CFW 4.90 Evilnat Cobra 8.4 [CEX] [noBD] is what I am trying to use, although even with the toggle QA enabled - it will at least pass the 9.99 check but still.. data is corrupt. Tried from safe mode to install this, no luck.

It's not the USB stick and it's not the PUP files, md5 matches and the usb stick works fine elsewhere. No errors when analyzing it on my pc.

I am thinking whoever modded this console before broke something, so what is corrupted? It's not the USB or the PUP. Is it something to do with flash0?

I've tried for the past 4 days with searching and what not but still can't install a latest CFW noBD. It always comes back to data corrupted. Without any previous info about how this ps3 was modded it's a bit tough. Would trying DEX or other types be a good idea?

Tempted to just get another ps3 as they are cheap enough, although the ones I can find are already modded so I am worried that I'll have the same issues.

If anyone has any tips for how to update the firmware to noBD so I can get to MGS4 again that'd be great.
 
I had got back in contact with the original seller, and they had tried to tell me because it was connected to the internet it had caused these problems. An obvious lie, dodgy seller. I'll be more careful next time.

I had tried again with DEX today but still no luck. I'll just assume there is a problem with the consoles internals and leave it for another time.
 
Also the old drive wont load after the new reformat.
Read ERK and You will get access to old PS3 HDD on PC. You will be able then to retrieve any data from it.
https://www.psx-place.com/resources/ps3-hdd-decryption-helper.1293/

Toggle QA seemed to run okay, it had beeped a few times and restarted... All good. So it should be as simple as flashing to a newer firmware right?
Yes.

CFW 4.90 Evilnat Cobra 8.4 [CEX] [noBD] is what I am trying to use, although even with the toggle QA enabled - it will at least pass the 9.99 check but still.. data is corrupt. Tried from safe mode to install this, no luck.
Evilnat cannot be installed from 3.55 for unknown reason. Install Rebug Rex NoBD and after that Evilnat.

Would trying DEX or other types be a good idea?
No. You will only add another obstacles for Yourself.
 
Read ERK and You will get access to old PS3 HDD on PC. You will be able then to retrieve any data from it.
https://www.psx-place.com/resources/ps3-hdd-decryption-helper.1293/


Yes.


Evilnat cannot be installed from 3.55 for unknown reason. Install Rebug Rex NoBD and after that Evilnat.


No. You will only add another obstacles for Yourself.

Thanks for the reply. I have ordered some usb stuff to read the drives so I'll wait for those to arrive and try again.

Once I get this working I'll update this thread with the steps I had taken.
 
Read ERK and You will get access to old PS3 HDD on PC. You will be able then to retrieve any data from it.
https://www.psx-place.com/resources/ps3-hdd-decryption-helper.1293/


Yes.


Evilnat cannot be installed from 3.55 for unknown reason. Install Rebug Rex NoBD and after that Evilnat.


No. You will only add another obstacles for Yourself.


Had a new SSD arrive and a couple of external USB casings so I can read drives and swap data. Had taken a while to arrive.

Downgraded to 3.55 firmware again using ROGERO_CRC[BA3712AF]_FW[v3.55_Rogero_Downgrader]_PS3UPDAT.PUP

For the life of me I could not find the noBD of Rebug Rex.

I did find a normal one REBUG_4.84.2_REX_0835d81e3c581f3bdfdfbe86fca5e192_PS3UPDAT.PUP although it's the same with 'corrupted data' unfortuently.

Maybe this ps3 is just cursed and I really should get a new one, there are some cheap ones with no hdd or controllers. Either way learned a lot about ps3 stuff so it's been a good learning experience.
 
If BD or BT cannot be found, then You need CFW with patches for noBD and noBT. Normal OFW or CFW will be rejected.

But You couldn't install Rogero in the first place with one of those issues.

If You are on 3.55. Then go to FSM mode and reinstall normal CFW 3.55, i.e Rebug 3.55.4 (FSM on higher OFW or CFW without xai_plugin means You will stuck forever in FSM, updating fw on FSM above 3.55 means perm brick beyond repair).
 
If BD or BT cannot be found, then You need CFW with patches for noBD and noBT. Normal OFW or CFW will be rejected.

But You couldn't install Rogero in the first place with one of those issues.

If You are on 3.55. Then go to FSM mode and reinstall normal CFW 3.55, i.e Rebug 3.55.4 (FSM on higher OFW or CFW without xai_plugin means You will stuck forever in FSM, updating fw on FSM above 3.55 means perm brick beyond repair).
btw do we have any idea how Sony technicians leave FSM on higher firmware?
 
@NiQ We can leave FSM on higher fw but we needs CFW and xai_plugin with XML entry to tell him what to do to switch back to normal mode. Problem is on OFW because it needs valid method, which is: dongle + signed lv2diag. Dongle probably can be made the same way as back in 3.40 times but we have lv2diags signed only for 3.55 and below. And this is the only obstacle here I believe.
 
@NiQ We can leave FSM on higher fw but we needs CFW and xai_plugin with XML entry to tell him what to do to switch back to normal mode. Problem is on OFW because it needs valid method, which is: dongle + signed lv2diag. Dongle probably can be made the same way as back in 3.40 times but we have lv2diags signed only for 3.55 and below. And this is the only obstacle here I believe.
OK, but in that case how come installing CFW also bricks it? I mean, the new CFW also should have xai_plugin, and I guess you could also modify the CFW so it doesn't check the lv2diag signature, can't you?

BTW it's a bit surprising that the new signed lv2diag never leaked online since almost everyone working in an official repair shop should've had access to it.
 
Good questions, but I don't know answer to all of them. ^^

Maybe we never has public key for usb stuff for fsm mode so we cannot sign any apps to work there?
 
Good questions, but I don't know answer to all of them. ^^

Maybe we never has public key for usb stuff for fsm mode so we cannot sign any apps to work there?
Probably, but that still doesn't explain why CFW can't be modified to bypass the check in the first place.
 
Ended up getting a slim 2500a :) came already with CFW 4.89 and might enjoy playing it for a bit before messing with it haha.

Thanks for the help either way, when I am motivated again I can try get this fat going again.
 

Similar threads

Back
Top