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

[Onsight79]

Would it be okay to install the 4.91 2 OC version on fat ps3 check03 ?

 

[Charles_n_town]

Would it be okay to install the 4.91 2 OC version on fat ps3 check03 ?

@Mitsu™ or @Tanzu15 might be able to help there. they both have a lot of experience with how high an oc specific models can go to. I don't have the experience myself.

 

[Zwei]

@Evilnat
Would it be possible to make a port to 4.84.2 REBUG REX? COBRA 8.5 plus the current xai_plugin?

 

[Charles_n_town]

@Evilnat
Would it be possible to make a port to 4.84.2 REBUG REX? COBRA 8.5 plus the current xai_plugin?

I don't know about cobra, but I think @LuanTeles said the xai_plugin was firmware-agnostic, meaning it's not firmware-specific.

 

[Tanzu15]

Would it be okay to install the 4.91 2 OC version on fat ps3 check03 ?

You can but you are limited to only 650/850 overclock. That's the highest most stable OC that ps3 can do.

 

[Onsight79]

You can but you are limited to only 650/850 overclock. That's the highest most stable OC that ps3 can do.

Thanks for reply.

 

[Charles_n_town]

Thanks for reply.

if that's the case, check this: https://1fichier.com/?nlygg9bcshft4n0w5umg

it says cex, but it's pex. it only says cex due to tarbells.

 

[LuanTeles]

I don't know about cobra, but I think @LuanTeles said the xai_plugin was firmware-agnostic, meaning it's not firmware-specific.

Yeap, you just need to port cobra first

 

[Charles_n_town]

Yeap, you just need to port cobra first

what would happen if you just injected a newer cobra into rebug? iirc, disabling rebug added like .bk or something to the cobra filename to prevent it from being picked up.

 

[LuanTeles]

what would happen if you just injected a newer cobra into rebug? iirc, disabling rebug added like .bk or something to the cobra filename to prevent it from being picked up.

It will simply disable itself, nothing bad will happen. Before Cobra 8.3, it could cause a brick on NAND systems (On NOR you can format the hdd) , but since 8.3, NAT implemented a failsafe feature.

 

[Charles_n_town]

It will simply disable itself, nothing bad will happen. Before Cobra 8.3, it could cause a brick on NAND systems (On NOR you can format the hdd) , but since 8.3, NAT implemented a failsafe feature.

I'm not sure if @Evilnat is willing, but some people are wanting the newer cobra on 4.84 rebug rex, I believe.

 

[montcer]

"If we open DEX vsh.self (4.84) in a HEX Editor and we go to the offset 0x703A20, we can see info about the last CA available in CA_LIST.cer"

Lol. I can only see rare characters in hexadecimal. Amazing how some people can read and understand data in such format!

By the way, what use can we get from these tools?

 

[Charles_n_town]

"If we open DEX vsh.self (4.84) in a HEX Editor and we go to the offset 0x703A20, we can see info about the last CA available in CA_LIST.cer"

Lol. I can only see rare characters in hexadecimal. Amazing how some people can read and understand data in such format!

By the way, what use can we get from these tools?

you can make it readable with a disassembler like IDA or ghidra. that's how things are reverse engineered. it looks like a mass of confusion simply in a hex editor.

 

[esc0rtd3w]

"If we open DEX vsh.self (4.84) in a HEX Editor and we go to the offset 0x703A20, we can see info about the last CA available in CA_LIST.cer"

Lol. I can only see rare characters in hexadecimal. Amazing how some people can read and understand data in such format!

By the way, what use can we get from these tools?

.elf is needed, not .self

It needs decrypted.

 

[Charles_n_town]

Yeah, you can easily decrypt the self by installing PS3tools, opening the package content Id as administrator (adds several options to the context window), exiting package content ID, then right-clicking the self file and selecting decrypt to elf or whatever it says. I don't think it says decrypt but it mentions elf iirc. If you're on windows 11, it will be under more options, I believe.

 

[Kevstah2004]

I installed the latest D-PEX but the xmb is still showing it as 4.91 DEX Cobra 8.5
the installation went fine as it deleted the activation & accountid, was the xmb version string not updated from 4.91 to 4.91.2?
I also set the QAFlag Debug option but I can't update from the internet using the 4k ps3-updatelist.txt it has the option blanked out in System Update.

 

[Charles_n_town]

I installed the latest D-PEX but the xmb is still showing it as 4.91 DEX Cobra 8.5
the installation went fine as it deleted the activation & accountid, was the xmb version string not updated from 4.91 to 4.91.2?
I also set the QAFlag Debug option but I can't update from the internet using the 4k ps3-updatelist.txt it has the option blanked out in System Update.

The xmb won't differentiate different versions of the same software version, if that makes sense. Best way to know what you're installing is the version.txt, which is what tells you the firmware you're about to install right before installation. Ofw always just has the version (i.e. 4.91).

 

[Kevstah2004]

The xmb won't differentiate different versions of the same software version, if that makes sense. Best way to know what you're installing is the version.txt, which is what tells you the firmware you're about to install right before installation. Ofw always just has the version (i.e. 4.91).

Fine, how do I update Evilnat CFW without USB though directly to the HDD?
The default behaviour in this CFW is to block all future OFW releases rite? but can't the ps3-updatelist.txt still be used to test multiple alpha / beta releases of CFW?

 

[Charles_n_town]

Fine, how do I update Evilnat CFW without USB though directly to the HDD?
The default behaviour in this CFW is to block all future OFW releases rite? but can't the ps3-updatelist.txt still be used to test multiple alpha / beta releases of CFW?

I don't know about the update list, but you can update from the internal HDD with update debug, which is part of qa flagging.

 

[Kevstah2004]

I don't know about the update list, but you can update from the internal HDD with update debug, which is part of qa flagging.

Is that with DEX consoles only? mine is converted from CEX to DEX, I tried both options from custom firmware menu to unlock both the standard & advanced debug settings menu & the server list url is blank with a limited entry to add the url via the virtual keyboard do you have to do the button combo under network settings if the xmb says it was already enabled, sorry i'm kinda confused, I have little to no experience with actual ps3 homebrew, coming from previous ps2 & psp exploit research.