CFW 4.89.3 Evilnat Cobra (8.4) (CEX/DEX/PEX)

PS3 CFW 4.89.3 Evilnat Cobra (8.4) (CEX/DEX/PEX) -

Go to download
Overview Extra info Updates (2) Reviews (2) History Discussion
I've once attempted to "detach" my PSN account from my main local account because I don't want to have multiple accounts with horrible growing numbers (I have an OCD with this kind of stuff). I've achieved this by editing the xRegistry.sys file and doing a hard reboot (never tried using Evilnat's CFW Tools soft reboot option).

The following entries must be cleared out:
  • /setting/user/<userid>/npaccount/accountid PSN Account ID
  • /setting/user/<userid>/npaccount/loginid PSN Login/Email
  • /setting/user/<userid>/npaccount/password
I wanted to develop my first homebrew for the PS3, maybe this can be a good idea.
 
NiQ said:
Seriously? You know Evilnat's not getting paid for it, he works hard to give this to the community and this is how you treat him? If you think you can do a better job then create your own damn CFW and prove me wrong. Otherwise, seriously, just shut up and show some respect to those of volunteer.
Click to expand...
He works hard haha nice joke is shit not cfw only rebug team made good custom firmware
 
Hey guys I'm wondering about something if anyone can explain it to me and help me out:

I get this message when I turn on my newly jailbroken PS3 running the Evilnat 4.89 CFW: https://postimg.cc/dhyTyGjv

The jailbreak went fine I can play games off multi man with USB and everything, but however I was just wondering because I dug up my PS3 a couple days ago to do this and I'm pretty sure I wasn't signed into PSN at any point that I was doing the memory patching with the tools, but does this message mean I'm banned? Or is the result of some failsafe the CFW has that prevents you from accidentally logging into PSN? If I had accidentally been auto logged when I was doing the tools part (before installing the CFW and rebooting) like when it patched the system so that I could install a CFW from the stick would that be banworthy?

FWIW when I tried logging in to my one and only PSN account through a browser on my computer I was able to, is that a good sign because when they ban a console I read they permaban the account as well? Any help would be greatly appreciated, thanks.
 
aldostools said:
It's true that Rebug team did an awesome job. IMHO Evilnat did it too.

If you don't like Evilnat CFW just use rebug cfw and sit to wait for a new update from rebug team.
Click to expand...
lol. it's pretty much obvious at this point that Evilnat's only doing this favor to the community in the first place because Rebug team is more or less retired.
Though I would like to see Rebug Toolbox for 4.89, since it already has support for Evilnat's 4.88 it shouldn't be too difficult to port.

Ps3enthusiast said:
Hey guys I'm wondering about something if anyone can explain it to me and help me out:

I get this message when I turn on my newly jailbroken PS3 running the Evilnat 4.89 CFW: https://postimg.cc/dhyTyGjv

The jailbreak went fine I can play games off multi man with USB and everything, but however I was just wondering because I dug up my PS3 a couple days ago to do this and I'm pretty sure I wasn't signed into PSN at any point that I was doing the memory patching with the tools, but does this message mean I'm banned? Or is the result of some failsafe the CFW has that prevents you from accidentally logging into PSN? If I had accidentally been auto logged when I was doing the tools part (before installing the CFW and rebooting) like when it patched the system so that I could install a CFW from the stick would that be banworthy?

FWIW when I tried logging in to my one and only PSN account through a browser on my computer I was able to, is that a good sign because when they ban a console I read they permaban the account as well? Any help would be greatly appreciated, thanks.
Click to expand...
That has nothing to do with a ban. Since version 4.89 Sony has removed the ability to log-in to PSN using your regular user/password. Downgrading will not help you since this has been also disabled at the server side. To log-in to PSN at this point you need to log-in with your computer and generate a device password for your PS3, which is what you then use instead of your regular password.
Of course, it's never guaranteed you won't be banned in the future if you log-in to PSN with a hacked PS3 so better use a throwaway account.
 
Hey thanks! That really clears up what I had worried about, thanks for the explanation. And for the record, I don't plan on playing online multiplayer anyway as I only really play single-player games. I just didn't like the idea of NEVER having the option to log in, if that makes sense. But yeah, I'm aware that I shouldn't log in now that I have the CFW running.
 
NiQ said:
I would like to see Rebug Toolbox for 4.89, since it already has support for Evilnat's 4.88 it shouldn't be too difficult to port.
Click to expand...

Try the PKG in the zip attached. The updated source code is included too.


EDIT: I re-uploaded the pkg. It didn't include the self tool needed to get the EID Root Key.
 

Attachments

Last edited:
By the way @aldostools @M3X2 AFAIK there are no features in Rebug Lite that Evilnat's firmware doesn't have, and new REX firmware won't happen unless a new version of DEX OFW leaks online - but we're not even sure it exists even internally at Sony.
A lot of people have been complaining that OFW 4.89 is half-baked to begin with and any such issues may affect Evilnat 4.89 CFW as well - you really can't expect a community developer to start fixing Sony's own screwups. If it's buggy you can downgrade to 4.88.
Also, unless you play on PSN or use your PS3 as a Blu-Ray player you can also stay on Rebug 4.84. I don't think there's a single offline game that requires a newer version.
 
I recently jailbroke my PS3 (Evilnat 4.89, latest Multiman release)and it works the way it's supposed to, but something happened when I was installing the homebrew .pkg file, when I selected my USB stick in the PlayStation view it showed two of them (the Multiman pkg), exact same name and everything. I just picked the bottom one and it worked fine but I found it really odd. When I was done setting up everything on my system I put the USB back in my laptop to format and put games on and when I looked at it sure enough, only one .pkg file. Does anyone know what this was all about?
 
Ps3enthusiast said:
I recently jailbroke my PS3 (Evilnat 4.89, latest Multiman release)and it works the way it's supposed to, but something happened when I was installing the homebrew .pkg file, when I selected my USB stick in the PlayStation view it showed two of them (the Multiman pkg), exact same name and everything. I just picked the bottom one and it worked fine but I found it really odd. When I was done setting up everything on my system I put the USB back in my laptop to format and put games on and when I looked at it sure enough, only one .pkg file. Does anyone know what this was all about?
Click to expand...

The reason of the "duplicated" package files is simple:
- Package manager lists the files of /dev_bdvd, /app_home, /dev_usb000, /dev_usb001, etc.
- /dev_bdvd and /app_home normally are mounted pointing to the same directory, hence the files are shown duplicated
- In some cases the packages could be triplicated if /dev_usb000 is mounted as /dev_bdvd

The duplicated entries is just a visual annoyance. There isn't anything wrong about the files.

This is a very old issue that could be reduced not listing /dev_bdvd and /app_home together in the same query of the Package Manager.
 
Hello,

For experienced people,

I have a question:

How do I design PS3 game libraries? What methods are used to create my own library of games? How is that?
Is it a somewhat complicated method?

My greetings,,
 
Hello, everyone!
I'm not able to sign into PSN after upgrading from latest REBUG REX release to this one. On local account, that was previously used to sign into PSN, when I try to Sign In, I get "Mount game and disable Syscalls" dialog (even though they are disabled, and it doesn't actually matter if game is mounted or not - the dialog is shown every time I access Sign In dialog). I've created a new local account and that did allow me to access Sign In dialog properly. I believe, the cause of it is presence of npaccount values in xRegistry (verified - every local account that has been used to sign into PSN previously can't access Sign In dialog after switching to Evilnat's CFW). How should I clear them out properly? I tried to simply clear the fields using xRegistryEditor 0.7.5 (found in Brewology), but after a restart I got system error and reinitialization (after which saves and trophies became unusable). After restoring original xRegistry file I was able to use saves/trophies, but still can't connect to PSN.
Any advice?
 
aldostools said:
The reason of the "duplicated" package files is simple:
- Package manager lists the files of /dev_bdvd, /app_home, /dev_usb000, /dev_usb001, etc.
- /dev_bdvd and /app_home normally are mounted pointing to the same directory, hence the files are shown duplicated
- In some cases the packages could be triplicated if /dev_usb000 is mounted as /dev_bdvd

The duplicated entries is just a visual annoyance. There isn't anything wrong about the files.

This is a very old issue that could be reduced not listing /dev_bdvd and /app_home together in the same query of the Package Manager.
Click to expand...
Hey aldo. The issue I see is that dev_bdvd and app_home are 2 different places a lot of the time. So seems we will lose something if we remove one. Lets say I have disc full of pkgs in BD drive, but I have PS Home mounted to app_home. I might want to be able to access my pkgs. I know its an edge case but seems a shame to remove something all the same.

I also noticed something strange, fresh install of Evilnat after a format, Went to install wMM pkg from USB, getting 1 pkg file duplicated. I had nothing running at this stage, literally first boot. Does Cobra mount USB as app_home automatically or something?
 
meska said:
Hello, everyone!
I'm not able to sign into PSN after upgrading from latest REBUG REX release to this one. On local account, that was previously used to sign into PSN, when I try to Sign In, I get "Mount game and disable Syscalls" dialog (even though they are disabled, and it doesn't actually matter if game is mounted or not - the dialog is shown every time I access Sign In dialog). I've created a new local account and that did allow me to access Sign In dialog properly. I believe, the cause of it is presence of npaccount values in xRegistry (verified - every local account that has been used to sign into PSN previously can't access Sign In dialog after switching to Evilnat's CFW). How should I clear them out properly? I tried to simply clear the fields using xRegistryEditor 0.7.5 (found in Brewology), but after a restart I got system error and reinitialization (after which saves and trophies became unusable). After restoring original xRegistry file I was able to use saves/trophies, but still can't connect to PSN.
Any advice?
Click to expand...
Try disabling syscalls from the Custom Firmware Tools menu (first menu option in network tab). I think Evilnat's CFW has this safety mechanism that prevents signing in when syscalls are not disabled and it may not recognize some 3rd party apps.
 
NiQ said:
Try disabling syscalls from the Custom Firmware Tools menu (first menu option in network tab). I think Evilnat's CFW has this safety mechanism that prevents signing in when syscalls are not disabled and it may not recognize some 3rd party apps.
Click to expand...

I've tried disabling syscals via CFW Tools Menu, via psnpatch, via wMM (R2 + triangle). Every time result is the same (syscalls actually do get disabled - I did verify that too). I even tried to disable Cobra (as it was mentioned that this blocker dialog plugin requires Cobra) and access Sign In dialog afterwards - this simply caused system crash (console rebooted itself and performed data verification afterwards).

Also, I did try to reinstall CFW again, hoping some kind of randomness struck my console first time. Reinstall was successful, but the problem persisted.
 
You must log in or register to reply here.

Similar threads

Back
Top