[v8s10]

Originally Posted by svenmullet But what I mean is after one modifies their console to be a DEX, it still allows the CEX firmware to boot? (I know it won't allow you to install other CEX firmwares at that point, but it still boots the CEX firmware that is already installed?) Because if I understand correctly how the PS3 works, DEX features are allowed by checking the target ID, etc, so you could theoretically stay on CEX FW, but have all the debug features? Or would this be a sort of hybrid where nothing really works?

After booting to gameOS from petitboot (just after writing the nor, which only a very small section is actually changed) it is still booting the cex firmware that is installed. It isn't on debug fw yet, so there are no debug options. All this does is allow you to install a debug firmware.

[evilsperm]

Originally Posted by v8s10 After booting to gameOS from petitboot (just after writing the nor, which only a very small section is actually changed) it is still booting the cex firmware that is installed. It isn't on debug fw yet, so there are no debug options. All this does is allow you to install a debug firmware.

Correct

[svenmullet]

Originally Posted by v8s10 After booting to gameOS from petitboot (just after writing the nor, which only a very small section is actually changed) it is still booting the cex firmware that is installed. It isn't on debug fw yet, so there are no debug options. All this does is allow you to install a debug firmware.

You don't understand what I mean. To clarify what I'm getting at:

You change the target ID to DEX, it's now a debug PS3, yet it still happily boots CEX FW, right? Can you power-cycle the machine and still boot CEX FW? Because if so, it makes me wonder if the opposite is true, ie. convert target ID back to CEX after installing debug FW and be able to boot DEX FW on a retail machine... this is why I asked if this would only result in a hybrid where nothing really works.
[edit] Or am I wandering into "sensitive" territory here? Perhaps a TB/Cobra dev could pop up and tell me I'm wasting my time/nothing to see here/etc
[edit2] As in, you mount the flash r/w very early in the boot process, read/decrypt the target id sections, convert/encrypt them on a microcontroller and flash them back, then boot a modified FW that appears to be retail but actually is a hybrid debug.
[edit3] That doesn't make sense after thinking about it for a bit. Never mind

[butnut]

Originally Posted by svenmullet You don't understand what I mean. To clarify what I'm getting at: You change the target ID to DEX, it's now a debug PS3, yet it still happily boots CEX FW, right? Can you power-cycle the machine and still boot CEX FW? Because if so, it makes me wonder if the opposite is true, ie. convert target ID back to CEX after installing debug FW and be able to boot DEX FW on a retail machine... this is why I asked if this would only result in a hybrid where nothing really works. [edit] Or am I wandering into "sensitive" territory here? Perhaps a TB/Cobra dev could pop up and tell me I'm wasting my time/nothing to see here/etc

Basically you would have a ps3 that could not run any homebrew or play any games.

[JonahUK]

@evilsperm

For this to be done on a NAND, would the following change be all that is needed:

NAND:
13. WRITE eEID: dd if=dex_eid.bin of=/dev/ps3nflasha bs=1 seek=$((0x80800)) count=$((0x10000))

[DJ-1]

Originally Posted by evilsperm Thats just for making a nor dump and yes you can extract your metldr from it, but you still no matter what need to exploit your own metldr on you're own console hence the need for petitboot and metldrpwn. Only then can you get your eid_root_key. All of this is easy once you get the hang of it but if you do not understand or follow instructions to the letter your gonna brick when flashing your system, and without a hardware flasher your 100% fuct.

Have I misread something here, or not understanding what I've read....but as afaik nobody has succeeded in getting the eid-root-key at all ??.

Sent from my Galaxy S II using tapatalk

[DJ-1]

Also, I've not touched my cfw PS3 for ages now, its still on 3.55 kmeaw cfw... what is the best hardware flasher? E3 ?,progskeet... ( I don't wanna solder anything though ) I've seen bad report on here about the e3.... ???

Sent from my Galaxy S II using tapatalk

[malex]

Originally Posted by DJ-1 Also, I've not touched my cfw PS3 for ages now, its still on 3.55 kmeaw cfw... what is the best hardware flasher? E3 ?,progskeet... ( I don't wanna solder anything though ) I've seen bad report on here about the e3.... ??? Sent from my Galaxy S II using tapatalk

If you have a nor ps3, then both offer solderless solutions (not 100% sure about E3), if like me you have a nand... then as of yet there's no solderless solution (reason I'm not dual-booting my ps3 yet).

[DJ-1]

I've got a 250GB, so that'll be Nor (16mb ? )

Sent from my Galaxy S II using tapatalk

[malex]

Originally Posted by DJ-1 I've got a 250GB, so that'll be Nor (16mb ? ) Sent from my Galaxy S II using tapatalk

If that's the stock HDD on it seems so, as I don't see any 250GB nand ps3's, but don't take my word for it. Rather than just trusting my half-baked memory, here's a nice little table with the different ps3 skus courtesy of ps3devwiki

Look for your model# and make sure of what equipment you've got. Hope that helps to clarify your situation.