I have modded one of my Sixaxis 3 controllers just fine using the blue usb-c board referenced by the OP and I have had no issues, charging works (from PS3 or PC USB-C to USB-C port, oddly it doesn't want to charge from USB-A to USB-C on PC even though data works).
Data works fine, I have tested...
The issue is might also be related to the RSX rather than the EE+GS, as some lines are connected to the RSX for post processing, which is used when smoothing/upscaling or Motion Adaptive deinterlace are enabled, otherwise the RSX is used as passthrough for video signals, this means that if some...
I would also be interested in this nand dump, incidentally. The eid_root_key would also be required to recover /dev_flash unless it can be dumped directly from the unit (after reflashing the nand data)
How recent? I tried playing a ps3 masterdisc on a retail 4.84 Rebug firmware (for the heck of it) and obviously it did not mount. (whereas it works fine on DEX even when running 4.84.2 D-REX)
No, it does not work this way 1. You can't just willy nilly burn retail iso dumps because they are encrypted and the bd drive cannot read the key to decrypt them from the ROM mark (they are meant to run on ODE or from HDD)
2. You can't just burn masterdiscs to play them on a retail bluray drive...
I am actually not 100% sure you can get code exec using this.
You would have to debug it
I am not sure if the offset is where it outputs the decrypted metadata header or where the decryption happens (probably the later)
if it's the later, it'd not work for code exec (unless you have extreme...
Metldr doesn't magically make the decrypted metadata available to you upon request, that would be quite the security oversight if this was done by design; you have to realize that this is exploiting a bug to make it happen.
If you need further details on how the bug actually works, please read...