PS3 error 80028f14

iEddyghost

iEddyghost

Member
Hello inmates I am facing dis error 80028f14.
Someone knows what it is? Cant install multiman or any other homebrew app...
 
I think that's a BD error... But assuming your on CFW and using ISO, then it's probably something to do with BD emulation
 
Fin9ersMcGee said:
I think that's a BD error... But assuming your on CFW and using ISO, then it's probably something to do with BD emulation
Click to expand...
Mean how I can fix it....
I just activated toggle as in rebug... but now I am getting another error...


The restore system file system is corrupted. Or something alike
 
I've not personally experienced this error... I am just searching online for the code and connecting dots.

You say you have disabled BD emu under rebug? Or you toggled on and off?
Might be worth reinstalling cfw if your getting corruption messages...
 
Fin9ersMcGee said:
I've not personally experienced this error... I am just searching online for the code and connecting dots.

You say you have disabled BD emu under rebug? Or you toggled on and off?
Might be worth reinstalling cfw if your getting corruption messages...
Click to expand...

I'll try to reinstall.
But I am afraid to get trapped in a infinite loop
 
What option did you choose?
I said it might be worth reinstalling custom firmware. This involves downloading your CFW version, copying to a usb drive and selecting to update, either from xmb or through safe mode.
 
Fin9ersMcGee said:
What option did you choose?
I said it might be worth reinstalling custom firmware. This involves downloading your CFW version, copying to a usb drive and selecting to update, either from xmb or through safe mode.
Click to expand...
I will reinstall it....

Anything new I'll write here
 
I'm on evilnat 4.88, I tried to log in my psn account and was told to deactivate schyllas or whatever it is. I deactivated it, logged into my psn, tried to enter my multiman the I saw this error.
 
Angel Umoru-Godwin said:
I'm on evilnat 4.88, I tried to log in my psn account and was told to deactivate schyllas or whatever it is. I deactivated it, logged into my psn, tried to enter my multiman the I saw this error.
Click to expand...
It's perfectly normal, you must learn how to use a ps3 on CFW or HEN in conjunction with PSN.

The ps3 system is a BSD system, it is organised in a similar way to Linux, with a kernel or system core separated from userland where the games & apps "live".
Syscalls are "system calls", in short & I will try to keep things as simple as possible, for security reasons a game or an app cannot communicate as it wishes with the core of the system, it must use system calls for that purpose. In other words, any communication between a game/app & the system core has to go through the system call interface.

For instance, when a userland app reads a file from the hdd or a USB storage device, the app cannot access the storage device to read it directly, it must use the "read file" dedicated system call, the kernel does the job & returns the result to the app
And similarly, if the app wants to have raw access to the storage device sectors, it must use the "storage read" dedicated system call.
And so on & so forth, there is a few hundred system calls available, related to storage access, bluetooth, gamepad input, network, memory allocation etc..
Each ps3 system call has a dedicated number (comprised between 0 & 1024).

In a customised firmware (permanent customisations in CFW or temporary in HEN), custom system calls are added by devs to the core of the system so that userland apps can get access to extended capabilities.
However those additional (custom) syscalls are easily detected, either by PSN related code or by games played online.
To minimise that risk of detection & consequent console idps + PSN account bans, it is recommended, among other things, to disable any custom syscall before using PSN or gaming online.

But of course, once custom syscalls are disabled, you should no longer use homebrews like multiman.
To game online (not recommended on CFW or HEN), you should mount your game with your backup manager (multiman or any other), disable custom syscalls & delete history, connect to PSN & launch the game.
When you are done with playing that game online, you should either reboot or disconnect from PSN & re-enable custom syscalls using the XMB system update trick (note that you must first enable the feature in the firmware settings menu of the network XMB column.
Only after reboot or after re-enabling the custom syscalls will you be able to launch a homebrew like multiman again & mount another game or whatever.
 
Last edited:
I understand all that you said, Thank You very much.
The solutions are working as you said they would.
But I wasn't having this problem since my 2yrs of using cobra cfw.
The problem started when i noticed the cobra toolbox for also the first time in 2yrs.
 
Angel Umoru-Godwin said:
I understand all that you said, Thank You very much.
The solutions are working as you said they would.
But I wasn't having this problem since my 2yrs of using cobra cfw.
The problem started when i noticed the cobra toolbox for also the first time in 2yrs.
Click to expand...
That would be because Evilnat introduced a number of new features in Cobra 8.3 & xai_plugin (CFW Tools) included in this CFW.
Before these new Cobra features, similar restrictions for ban protection could be put in place with an additional plugin like psnpatch, sen enabler or even wMM.
That's what you were supposed to use with earlier CFWs & maybe you didn't, it would explain why you are discovering all this stuff only now.
 
You must log in or register to reply here.

Similar threads

Back
Top