PS3 4.88.2 Evilnat Cobra (8.3) Custom FirmWare (CFW-CEX) Released

Coldheart2236 · Apr 13, 2022

Odyssey346 said:
Hello, does this firmware work on the CECH-2504B slim model? I have the 320gb model, I am running 4.88 ps3xploit hen, and my minimum downgrade version is 3.40. I'd like to try a CFW because apparently I can play online with that and I'd like to play online with some friends, and because I hate the epilepsy screen. Thanks

Yes is the short answer

Your factory firmware is 3.40 and so is compatible with CFW. Interesting though, mine is a slim 2503A and is 3.50 factory firmware.

Odyssey346 · Apr 13, 2022

Coldheart2236 said:
Yes is the short answer
Your factory firmware is 3.40 and so is compatible with CFW. Interesting though, mine is a slim 2503A and is 3.50 factory firmware.

Thanks! I've installed it and it works just fine

Naxil · Apr 14, 2022

Coldheart2236 said:
Yes is the short answer
Your factory firmware is 3.40 and so is compatible with CFW. Interesting though, mine is a slim 2503A and is 3.50 factory firmware.

my slim is 2.70

Pooka · May 8, 2022

bguerville said:
0x80010514 errors are related to BD read issues.

Check the wiki error codes list.
https://www.psdevwiki.com/ps3/Error_Codes

I gave this thing a further whirl today, as apparently more and more discs that I buy keep throwing this exact error while others just work fine. Some of various qualities, some pristine. Yesterday I bought a batch of 12 games and 4 of them throw 80010514, so it was pretty ridiculous.

With the help of VGPC and a little bit more experience than I used to have, I figured that maybe the disc dumps correctly but my PS3 (CECHL04) is unable to decrypt it for whatever reason. So I took one of the four discs (Bakugan Battle Brawlers), and dumped an encrypted ISO with Managunz. Then I copied it to my PC, and compared the hashes of my dump with redump's, and what do you know?

My encrypted dump is Redump quality.

This means I could use a software on my PC to decrypt it, send it back to the PS3, and play. So far so good, but this is driving me insane. Why would the PS3 be able to play games off disc such as The Last of Us (as recently as a few days ago even), but it can't decrypt discs that are perfectly okay and dump without issues? It's a puzzle for me.

And yeah, I tried various troubleshooting methods like restarting, different backup managers, disabling Cobra altgother, the works.

Would it be possible to force the PS3 to use an online or offline database of key sets (such as those available on Redump) and use those to decrypt discs in case the PS3 can't do it on its own?

bguerville · May 8, 2022

Pooka said:
I gave this thing a further whirl today, as apparently more and more discs that I buy keep throwing this exact error while others just work fine. Some of various qualities, some pristine. Yesterday I bought a batch of 12 games and 4 of them throw 80010514, so it was pretty ridiculous.

With the help of VGPC and a little bit more experience than I used to have, I figured that maybe the disc dumps correctly but my PS3 (CECHL04) is unable to decrypt it for whatever reason. So I took one of the four discs (Bakugan Battle Brawlers), and dumped an encrypted ISO with Managunz. Then I copied it to my PC, and compared the hashes of my dump with redump's, and what do you know?

My encrypted dump is Redump quality.

This means I could use a software on my PC to decrypt it, send it back to the PS3, and play. So far so good, but this is driving me insane. Why would the PS3 be able to play games off disc such as The Last of Us (as recently as a few days ago even), but it can't decrypt discs that are perfectly okay and dump without issues? It's a puzzle for me.

And yeah, I tried various troubleshooting methods like restarting, different backup managers, disabling Cobra altgother, the works.

Would it be possible to force the PS3 to use an online or offline database of key sets (such as those available on Redump) and use those to decrypt discs in case the PS3 can't do it on its own?

Keysets are unlikely to help, at this stage, you don't even know whether your issues are caused by decryption processes, do you?
You say the discs play fine but if you never actually played the entire games from disc, how could you know whether 1 or more sectors might error out when read, unless you play the entire game and even then, depending on the game, that may not ensure that every single bit of disc data will have been accessed.
Making a dump implies accessing every single disc sector and checking them all, whereas launching a game from disc simply doesn't.

Assuming that your discs are all legit and healthy, it sounds like a hardware issue and if it is, that's what needs fixed.
You could try to get debug logs to help point out the issue, for that you can use a Cobra debug payload and socat on your PC to capture the UDP broadcast logs.

Pooka · May 8, 2022

bguerville said:
Keysets are unlikely to help, at this stage, you don't even know whether your issues are caused by decryption processes, do you?
You say the discs play fine but if you never actually played the entire games from disc, how could you know whether 1 or more sectors might error out when read, unless you play the entire game and even then, depending on the game, that may not ensure that every single bit of disc data will have been accessed.
Making a dump implies accessing every single disc sector and checking them all, whereas launching a game from disc simply doesn't..

I'm fairly certain it's something to do with the decryption. I've been able to play a few games with damaged sectors (Heavenly Sword and GTA IV comes to mind), as in 1. boot them up and 2. play them a bit. So far, so good. The discs with the error fail at step 1.

But for other games, like The Last of Us which I mentioned, I'm actually sure the disc is legit and healthy: I dumped it with Multiman and checked the IRD with Managunz, 100% valid. Same for a majority of my other discs.

Furthermore, when I dumped Bakugan (and now MotorStorm, one of my other affected discs), I was able to decrypt the ISO with the disc keys listed on Redump just fine, making them bootable.

bguerville said:
Assuming that your discs are all legit and healthy, it sounds like a hardware issue and if it is, that's what needs fixed.
You could try to get debug logs to help point out the issue, for that you can use a Cobra debug payload and socat on your PC to capture the UDP broadcast logs.

I was thinking if a software solution to a hardware problem would be possible, as other than the accursed 80010514s and damaged sector games, they are 100% healthy and play fine. Should also eliminate this problem for other drives or consoles with this weird oddity.

I'll look for how to get debug logs and get back to you.
I'll also IRD check the decrypted motorstorm dump.

EDIT:

For some reason I can't find Toggle Cobra Version under Cobra Tools. I have Allow Restore Syscalls, then Toggle "What's New" and finally Toggle Cobra at the end.

That said, when doing a decrypted dump, Managunz shows these messages on-screen before failing:

Code:

Error: get data failed
Error: failed to get d1 and d2
Error: failed to get_keys

But...if I dump MotorStorm as an encrypted backup, decrypt it, and then copy it back over?

Code:

Game Name : MotorStormâ"¢
Game ID : BCES00006
Update : 1.50
Game Version : 01.00
App Version : 

Files Number = 85 (backup) / 85 (ird)
VALID        : 85
NOT FOUND    : 0
MODIFIED     : 0
EXTRA        : 0

bguerville · May 8, 2022

Pooka said:
I'm fairly certain it's something to do with the decryption. I've been able to play a few games with damaged sectors (Heavenly Sword and GTA IV comes to mind), as in 1. boot them up and 2. play them a bit. So far, so good. The discs with the error fail at step 1.

But for other games, like The Last of Us which I mentioned, I'm actually sure the disc is legit and healthy: I dumped it with Multiman and checked the IRD with Managunz, 100% valid. Same for a majority of my other discs.

Furthermore, when I dumped Bakugan (and now MotorStorm, one of my other affected discs), I was able to decrypt the ISO with the disc keys listed on Redump just fine, making them bootable.

I was thinking if a software solution to a hardware problem would be possible, as other than the accursed 80010514s and damaged sector games, they are 100% healthy and play fine. Should also eliminate this problem for other drives or consoles with this weird oddity.

I'll look for how to get debug logs and get back to you.

Sure, take your time and post stuff as you go along, although you might wanna start your own thread for this.

To my knowledge, the problems you are reporting are not very common, I don't really recall any occurrences in this forum in years although there might have been.

You could potentially dismiss the possibility of a software related error by changing CFW temporarily, for instance using Irisman 4.8x to dump isos on Rebug REX 4.84.2.

If you know someone else with a PS3 near you whether on CFW or on HEN, you could try dumping a couple of discs that error out on that console in order to confirm that the issue lies with your own console.

The obvious suspects with dumping errors are the BD drive (faulty lens or whatever else) and/or the discs, but of course there could always be other hardware related issues in the way, it's impossible to say without investigating the errors.
Cobra Debug logs and syscon error logs (you can get those dumped to a file on USB with the PS3 Advanced Toolset, look at the releases section of this repo https://github.com/bucanero/psl1ghtv2_ports) are the only things you could use to try to get some answers or leads.
However if that turned out not to prove useful either, you might find yourself at a dead end because you will need reverse engineering and programming skills to dig deeper.

Pooka · May 8, 2022

bguerville said:
Sure, take your time and post stuff as you go along, although you might wanna start your own thread for this.

Yeah, good idea. I'll also get more eyes on the problem, I hope.

I got the syscon error logs at least and they're unhelpful. Covers a bunch of stuff from December of...1999, to February of...2006. The first PS3 was released at the tail-end of 2006, right? Weird.

If I replace the CFW with Rebug, and then go back to the latest Evilnat, will things like account ID RAP activation still work just fine? Or will I have a lot of work to do when going back to my current setup?

bguerville · May 8, 2022

Pooka said:
Yeah, good idea. I'll also get more eyes on the problem, I hope.

I got the syscon error logs at least and they're unhelpful. Covers a bunch of stuff from December of...1999, to February of...2006. The first PS3 was released at the tail-end of 2006, right? Weird.

If I replace the CFW with Rebug, and then go back to the latest Evilnat, will things like account ID RAP activation still work just fine? Or will I have a lot of work to do when going back to my current setup?

The rif licenses depend on act.dat and IDPS so as long as you don't spoof idps or change the activation status, nothing will mess with your licenses.

There should be nothing specific to do when going back and forth between rex 4.84.2 and 4.88.
The only things you may potentially lose when installing a CFW are XMB customisations you made by changing files in /dev_flash.

Pooka · May 8, 2022

bguerville said:
The rif licenses depend on act.dat and IDPS so as long as you don't spoof idps or change the activation status, nothing will mess with your licenses.

There should be nothing specific to do when going back and forth between rex 4.84.2 and 4.88.
The only things you may potentially lose when installing a CFW are XMB customisations you made by changing files in /dev_flash.

So, since I have practically no XMB mods, basically nothing much will be changed other than:

having to revert the coldboot back again
maybe reinstalling webman
maybe wallpapers

That's hopeful, I could do it when I have lots of time to kill. Alright, thanks! I'm writing the other thread right now.

Pooka · May 9, 2022

bguerville said:
You could potentially dismiss the possibility of a software related error by changing CFW temporarily, for instance using Irisman 4.8x to dump isos on Rebug REX 4.84.2.

Yeah, I downgraded to REX 4.84.2 temporarily before going back to Evilnat. The end result is the error still persists, so at least it isn't an Evilnat thing.

Also the only thing I had to change when going back to Evilnat is the coldboot. My theme settings, webMAN Mod, etc, were all left as is.

I have started a thread about the error here:
https://www.psx-place.com/threads/the-accursed-error-80010514.37181/

TurtleNeck · May 10, 2022

It seems Playstation has released 4.89 for the PS3

bguerville · May 10, 2022

TurtleNeck said:
It seems Playstation has released 4.89 for the PS3

Yes, it's just now live on the official PlayStation sites. According to the notes, there are changes made to the PSN account management features and login.
It looks like accounts can no longer be created on the PS3..

TurtleNeck · May 10, 2022

Yep, I wanted to sync some trophies I earned offline and was prompted with "A system software update is required. Do you want to update now?" It had me stressing, as when I checked the PlayStation website and it still had 4.88 as the latest software.

I had to check my non CFW PS3 to confirm 4.89 was released.

Will wait for Evilnat to update.

TiggleBitties · May 10, 2022

SONY HAS JUST CAME OUT TONIGHT AND ONCE AGAIN UPDATED PS3 OFW TO 4.89 WHICH RUINS MY GAME TIME AND FUN

SHOULD I CUT MY LOSSES AND JUST BUY THE PS4 OR PS5 ?? I LOVE YOUR GUYS WORK AND YOU MAKE EVERYTHING POSSIBLE TO JUST HAVE FUN AND HAVE CREATED AMAZING THINGS FOR THE FRIENDS THAT USE PS3 <3

bguerville · May 10, 2022

TurtleNeck said:
Yep, I wanted to sync some trophies I earned offline and was prompted with "A system software update is required. Do you want to update now?" It had me stressing, as when I checked the PlayStation website and it still had 4.88 as the latest software.

I had to check my non CFW PS3 to confirm 4.89 was released.

Will wait for Evilnat to update.

Nat has not been around for months, at this point, it's hard to tell whether or not he will update his CFW, he may reappear but if ever he doesn't, someone else will have to pick up the torch..

Regarding HEN, I sent a message 1h ago to @esc0rtd3w (who takes care of maintenance) to let him know about the update, he has not replied yet, I dunno how busy he is atm though.
I haven't unpacked the new pup yet, I would assume that as usual the kernel will be untouched.
The PSN changes will probably be limited mostly to sprx and xml files, maybe some changes in VSH.

As to the PS3 Toolset, there will be no update until a CFW is released and littlebalup makes a new nofsm patch with it.

TurtleNeck · May 10, 2022

bguerville said:
Nat has not been around for months, at this point, it's hard to tell whether or not he will update his CFW

Just checked his twitter "New PS3 update 4.89, I will try to do the latest CFW 4.89 ASAP"

bguerville · May 10, 2022

TurtleNeck said:
Just checked his twitter "New PS3 update 4.89, I will try to do the latest CFW 4.89 ASAP"

That's good news. Let's hope he pops in here before he does it as there have been a few requests for features (like OOS+ support) and possibly a couple of issues to look into.

Pooka · May 10, 2022

bguerville said:
there have been a few requests for features (like OOS+ support) and possibly a couple of issues to look into.

Yeah, now might be a good time to request decryption by keyfile, to potentially solve 80010514. Here's what I think could be implemented based on what I know of the issue.

1. Check if a key file is present in e.g. /dev_hdd0/keyfiles matching the internal ID or other unique descriptor of the game
2.1. if it exists, attempt to load the disc using that keyfile (converted to HEX to produce a 32-bit decryption key as shown on Redump
2.2. if it doesn't, continue as normal

Which would run discs that fail the managunz check due to failing to get keys and throwing 80010514 errors.

The thing is, it sounds simple in theory, but I'm not sure if it's actually feasible on the Cobra side of things. Do you think it's possible?

SpyroMancer · May 10, 2022

A standard cfw would also be an option, since mamba has version 4.89 ready. Except if some changes were made to the firmware

PS3 4.88.2 Evilnat Cobra (8.3) Custom FirmWare (CFW-CEX) Released

Coldheart2236

Odyssey346

Naxil

Pooka

bguerville

Pooka

bguerville

Pooka

bguerville

Pooka

Pooka

TurtleNeck

bguerville

TurtleNeck

TiggleBitties

bguerville

TurtleNeck

bguerville

Pooka

SpyroMancer

Similar threads

Featured content

Trending content

Latest posts