4.93 EVILNAT (Cobra 8.5)

PS3 4.93 Evilnat w/ Cobra v8.5 - (CEX/PEX/D-PEX) 4.93

Go to download
Overview Extra info Updates (8) Reviews (4) History Discussion
XDeltaOne said:
I have another question, is it possible to support a 2TB hard drive? I once saw that went somehow with the 4.46?
https://www.psx-place.com/threads/ps3-1-75-tb-internal-hdd-upgrade-formatting-utility.11989/
Click to expand...

It won't work. The maximum limit is 1.75TB, and even that isn't stable. You'll have all the known issues: file system corruption, performance degradation, format prompt, etc.

Have a look at this: https://www.psdevwiki.com/ps3/Harddrive#Internal_Harddrive_maximum_capacity
 
I tried it once, more interesting white I could format up to 1.86 TB and the hard drive goes, but as they have said no filesystem check is possible anymore.
 
Hi everyone, I seem to have found an issue with the previous CFW and I am unware if it happens with the new one. Everytime I turn on the console, which is using CFW 4.89.3 Evilnat Cobra 8.4 [CEX] the controller (genuine and in perfect working order) do not sync to the console, and keeps 4 blinking lights, even after presing the PS button, if I turn the console off, the control shuts off too. Then, if I turn the console on from the power button on the console itself and I wait till it loads the system and turn the controller on, it syncs without issue. I've tested this controllers in an unmodified console and they do not present this behaviour. Could this be related to a bug in the CFW?
 
sigmarumberogen said:
Hi everyone, I seem to have found an issue with the previous CFW and I am unware if it happens with the new one. Everytime I turn on the console, which is using CFW 4.89.3 Evilnat Cobra 8.4 [CEX] the controller (genuine and in perfect working order) do not sync to the console, and keeps 4 blinking lights, even after presing the PS button, if I turn the console off, the control shuts off too. Then, if I turn the console on from the power button on the console itself and I wait till it loads the system and turn the controller on, it syncs without issue. I've tested this controllers in an unmodified console and they do not present this behaviour. Could this be related to a bug in the CFW?
Click to expand...
Never heard of something like that... I do have a few things I'd like you to check though -
1. You said the controller doesn't have that issue when using an unmodded console. What about other controllers on the modded one?
2. Please update your console to the latest Evilnat CFW (4.91.2b9 as of the time of writing this). You're not gaining anything by staying on an older version and you can always downgrade if there's an issue.
3. If you want to see whether it's a CFW issue, you can try the DB (Dual Boot) firmware, which is just OFW with a single modification that allows you to reinstall CFW without jailbreaking again (basically a way to temporarily revert to OFW without losing the jailbreak).
4. If the issue persists and you're willing to bother with it - you might want to factory reset / format the HDD while on DB (/OFW), to get your system as close as possible to factory conditions as possible. If the issue still persists then it has to be a hardware issue. You can use the dd command on Linux to take a raw backup image of the HDD so you can "un-factory-reset" the console after you're done testing.
 
NiQ said:
Never heard of something like that... I do have a few things I'd like you to check though -
1. You said the controller doesn't have that issue when using an unmodded console. What about other controllers on the modded one?
2. Please update your console to the latest Evilnat CFW (4.91.2b9 as of the time of writing this). You're not gaining anything by staying on an older version and you can always downgrade if there's an issue.
3. If you want to see whether it's a CFW issue, you can try the DB (Dual Boot) firmware, which is just OFW with a single modification that allows you to reinstall CFW without jailbreaking again (basically a way to temporarily revert to OFW without losing the jailbreak).
4. If the issue persists and you're willing to bother with it - you might want to factory reset / format the HDD while on DB (/OFW), to get your system as close as possible to factory conditions as possible. If the issue still persists then it has to be a hardware issue. You can use the dd command on Linux to take a raw backup image of the HDD so you can "un-factory-reset" the console after you're done testing.
Click to expand...
thanks for the response! I've been digging a bit and it seems this is a known issue with all consoles, and in some places its said that this started on 3.XX firmware. I would try what you suggest, but it appears as seen in this reddit post, that the issue also happens with normal stock firmware, but its a random issue that might happen to anyone, here is the post for reference. This is the exact same thing that's happening to me. And most disscussions claim it to be something firmware related.

I forgot, this does not happen with the BD remote control, only the gamepads. But some people have this issue with the BD remote too.
 
Last edited by a moderator:
GuilloteTesla said:
By any chance, do you have an SSD in your console?.
Click to expand...
No, original 160gb hdd that came with the console. And as regards the hardware issue, I don't think it might be that, as after the controller is synced to the console, it never disconnects or anything else, works like a charm, it's only when used to boot up the console. If I turn it on by the power button, and then press the PS button on the controller, everything works as normal.
 
sigmarumberogen said:
No, original 160gb hdd that came with the console. And as regards the hardware issue, I don't think it might be that, as after the controller is synced to the console, it never disconnects or anything else, works like a charm, it's only when used to boot up the console. If I turn it on by the power button, and then press the PS button on the controller, everything works as normal.
Click to expand...

I've asked because there've been reports of SSDs breaking Bluetooth controller sync.

I'm running out of ideas here, but try to downgrade to CFW 4.88 or 4.84 and check if the issue persist. Just to discard if it is a FW issue or not.
 
GuilloteTesla said:
I've asked because there've been reports of SSDs breaking Bluetooth controller sync.

I'm running out of ideas here, but try to downgrade to CFW 4.88 or 4.84 and check if the issue persist. Just to discard if it is a FW issue or not.
Click to expand...
que excelente ver alguien de argentina aca jajajaja, me tendria que fijar como hacer el downgrade, pero empezo a pasar ahora, realmente no me acuerdo si antes sucedia. Pero por todo lo que lei, podria ser ya algo metido por sony con sus updates. Ayer luego de que updatie al 4.88.3 creo, el ultimo cobra que habia antes del beta actual, funciono bien a la primera, el tema de la sincronizacion con el inicio, luego, apague, y volvio a esto.

Google translation: Next time post in English, please!
How excellent to see someone from Argentina here hahahaha, I would have to figure out how to do the downgrade, but it started happening now, I really don't remember if it happened before. But from everything I read, it could already be something that Sony has introduced with their updates. Yesterday after I updated to 4.88.3 I think, the last cobra that was before the current beta, it worked well the first time, the issue of synchronization with the startup, then, I turned it off, and it came back to this.
 
Last edited by a moderator:
sigmarumberogen said:
How excellent to see someone from Argentina here hahahaha, I would have to figure out how to do the downgrade, but it started happening now, I really don't remember if it happened before. But from everything I read, it could already be something that Sony has introduced with their updates. Yesterday after I updated to 4.88.3 I think, the last cobra that was before the current beta, it worked well the first time, the issue of synchronization with the startup, then, I turned it off, and it came back to this.
Click to expand...

OFW 4.89 and up are known to break some features, but Evilnat is fixing them with every beta. That's why I suggested to downgrade to a more stable FW, like REBUG 4.84 just to see if it is indeed a FW issue or no.
 
Hello! Im fairly new in the scene, I have a 4.84 2001A Slim without a BD Drive and want to get to use the CEX noBD CFW, is it still a work in progress for the 4.91 firmware so I can keep waiting? Or can I use the noBD CEX BETA 6 for now? I just want to utilize some backups and play online. Please let me know I appreciate everyone's work!!
 
Last edited:
Deb04 said:
Hello! Im fairly new in the scene, I have a 4.84 2001A Slim without a BD Drive and want to get to use the CEX noBD CFW, is it still a work in progress for the 4.91 firmware so I can keep waiting? Or can I use the noBD CEX BETA 6 for now? I just want to utilize some backups and play online. Please let me know I appreciate everyone's work!!
Click to expand...

Latest 4.91.2 beta 9 is so far the most stable version. But the noBD edition is not available yet for that version.

The closest version that have a noBD edition is 4.91.2 beta 8.
https://mega.nz/folder/UJ1WkCCa#ZboE1vQjyJUPvud-3EfQjg

The beta 6 is ok but still has issues that were solved in later releases.
 
GuilloteTesla said:
It won't work. The maximum limit is 1.75TB, and even that isn't stable. You'll have all the known issues: file system corruption, performance degradation, format prompt, etc.

Have a look at this: https://www.psdevwiki.com/ps3/Harddrive#Internal_Harddrive_maximum_capacity
Click to expand...

Well, I don't know how, but a friend of mine has been using a 2TB hard disk drive for months without any issues. He even recorded a video installing it as proof, as many people, including me, said that it was BS.
 
@Evilnat, is there any way to patch the fw to allow downgrading to lower versions? For example, I can't go back directly to 3.55, I need to go to 4.21 first and then to 3.55.

I just needed to downgrade all the way to 2.80, so I had to flash 4.21, then 3.55, and finally 2.80.
 
LuanTeles said:
Well, I don't know how, but a friend of mine has been using a 2TB hard disk drive for months without any issues. He even recorded a video installing it as proof, as many people, including me, said that it was BS.
Click to expand...

Maybe your friend made another partition in order to leave free space on the max size limit.

It would be good to know if your friend has run the file system check, that's the thing that breaks everything for big drives.
 
GuilloteTesla said:
Maybe your friend made another partition in order to leave free space on the max size limit.

It would be good to know if your friend has run the file system check, that's the thing that breaks everything for big drives.
Click to expand...

I doubt it passes the file system check, but i will ask it again

I just found a video on youtube , but no filesystem check too

 
excited for future updates. amazing stuff yall have accomplished. ive just gotten into this stuff and from reading it overclocking the ps3 doesnt change the voltage so as long as you keep the temperature down (and dont brick it) ocing should not change the lifespan of the silicon. I have a 2501B so i should beable to get a decent oc. ill do it when the latest version gets an OC profile. If i was wrong on any of my statements please correct me. Thanks!
 
You must log in or register to reply here.

Similar threads

Back
Top