[matttayyyy]

I saw some threads talking about changing from CEX to DEX. Some people are saying its only good for devs, others are saying you can run unsigned code on it. Can somebody please tell me what DEX is good for?

Sorry if this is already a thread :L

[JOshISPoser]

from what i understand, what you mentioned. it can install/run unsigned code.
i guess it's kinda like one less step for devs to run something

[matttayyyy]

Originally Posted by JOshISPoser from what i understand, what you mentioned. it can install/run unsigned code. i guess it's kinda like one less step for devs to run something

So homebrew? :P

[JOshISPoser]

i guess. don't exactly believe me 100%, i'm going with what i gathered

[Skarekrow_Juggalo]

I think DEX is like, Debug fw?
I gather that it has added permissions that CEX doesn't have. Either way I think it can run unsigned code, allowing for .pkg and unsigned eboots. But I don't know much about DEX except it's debug and CEX is retail.

[iwasaperson]

DEX will allow homebrew on any firmware, including 4.0. It will also allow access to the other PSN (soon to be SEN) networks, such as sp-int, on any firmware version. You will not be able to run backup managers unless you downgrade to 3.55 (no need for hardware, just a special PUP included in one of the SDKs) and patch lv2_kernel.self with Peek & Poke (same thing on a retail console).

You will have to use unsigned (3.41) homebrew so it will run. If it is signed (3.55 gh), then manually decrypt it and make fself with the SDK, then package it into an unsigned pkg.

If you don't understand any of this, then you shouldn't have a DEX console.

[matttayyyy]

Originally Posted by iwasaperson DEX will allow homebrew on any firmware, including 4.0. It will also allow access to the other PSN (soon to be SEN) networks, such as sp-int, on any firmware version. You will not be able to run backup managers unless you downgrade to 3.55 (no need for hardware, just a special PUP included in one of the SDKs) and patch lv2_kernel.self with Peek & Poke (same thing on a retail console). You will have to use unsigned (3.41) homebrew so it will run. If it is signed (3.55 gh), then manually decrypt it and make fself with the SDK, then package it into an unsigned pkg. If you don't understand any of this, then you shouldn't have a DEX console.

So it is pretty much like GeoHotz cfw? It can run unsigned code.. but not back up managers.

[iwasaperson]

Geohot's firmware can ONLY run signed code. This can run 3.56+ signed code (newer games only if on a newer firmware) or unsigned code. I don't know if the 3.55 keys are blacklisted on a DEX console, because I've never owned one. If you want to test it out, run Rebug 3.55.2 (with the newest update) and LV2_LOADER with QA-flag and a DEX lv2_kernel.self extracted from the core_os of a debug firmware. Note that this is equivelent to running 3.55 on a DEX console. There is an lv2_kernel.self with peek&poke enabled, but you will have to patch multiMAN for DEX. More info is available at the front page.

Sent from my Galaxy Nexus using Tapatalk

[matttayyyy]

Originally Posted by BrerichClice from what i understand, what you mentioned.

yeah from what i understand, what you mentioned.. sir

[carldenning]

Originally Posted by matttayyyy yeah from what i understand, what you mentioned.. sir

lmfao. @BrerichClice is a spambot and u like it lol . the spam bot just copied some off what @JOshISPoser said m8