Cobra USB Full Software BC Findings
 

I did some investigation about Cobra USB's full software emulator and I came to some conclusions that I need you help to continue.

Conclusion 1:
Extracting the contents of the CFW that Cobra has on their site reveals that there is NO ps2_emu folder of the dev_flash folder of the firmware, which means that everything remains unchanged/unmodified, Cobra team didn't mess anything with those files.

Conclusion 2:
Since on the guide of the dongle it says in a nutshell that the first time you launch a PS2 game it makes a change inside PS3's files, I really had to take a fast look at the contents of the backup loader also available on their site. There is nothing interesting inside apart from the layout PNGs and the EBOOT.BIN that -if what they say in the manual is correct- it must change a string on a file inside dev_flash to enable non backwards PS2s when an Original PS2 Disc gets inserted to recognise it instead of Unsupported Data as a PS2 Format Disc and being able to launch it from the XMB without the need of a backup launcher. An other possibility is that it changes a value on xregistry.sys that we are not aware yet of what it does.

So after that I come to a brick wall to continue without your help.

It would be very kind if somebody with the dongle and a Non BC PS3* could make a dump (and send me via pm) of his dev_flash BEFORE the launcher patches the dev_flash and a different dump after it applies the patch so i can see what the heck is messing with. Also if he could be kind to do the same thing with his xregitsy.sys I'd be very kind.(I know that it holds unencrypted personal data, don't worry the last thing I care is about your personal info, I once posted my xregistry publicaly here too, but if you still don't want me to know any of your personal info before you do anything put fake info on your account settings, either way I won't bother)

*=For those who want to know exactly what are the Non BC models are all slim models plus all Fat Models with the series of CECHG-CECHQ (Alphabetically all variables between G-Q)

Thank you!

I'm getting a dongle through in a week or so il do that for you il let you know when it comes


Thanks, superfurry :)

Thank you very much, remember, do the dumps before and after the proccess of the backup launcher.
Dunno if anybody else has any idea what should we dump more?
I think dev_flash and xregistry.sys are enough, what other could it modify?
It says that it needs to be done just once, so that means that it doesnt patch anything in the payload or the HV or whatever would get erased after a reboot so it must modify a file that stays permanent in the console, so the only possibilities are the HDD and the Flash ones.
NOTICE that it also says on the manual that it doesnt mess with any files that could brick the PS3 so some obviously not sensitive dev_flash files or the xregistry.sys are the main suspects.
I think (and hope) we are pretty close to find something.
Put your ideas...

i wonder if it would stay after installing ofw & reformatting the hdd??? i would imagine that would be the one way to completely get rid of it??

If it is infact on dev_flash I guess an upgrade/downgrade would fix it, I also think there is an option on the launcher to disable it again (Not 100% sure what it does exactly).
If it is xRegistry.sys pfff... just holding down the power button till it beeps twice would reset that. I'm still investigating what could it modify. I don't seem to find any files on the hdd that are involved to the function (I could be wrong but I doubt it). dev_flash2 and dev_flash3 also seem extremelly impossible. dev_flash and xregistry.sys remain the only suspects at the momment. When I get some results I'll compare one by one all the files of the dumps before and after the function in a HEX editor and see which one of them are not identical to it's prior.
I find it practically impossible to not be somekind of file/string on a file that it gets modified to enable the software emulator, the description that they give just leads that one file or a string/value of a file is responsible for how the PS3 reacts only when a PS2 disc gets inserted to the PS3 so it leaves the PS3 safe from bricking because is not such an important function for it to operate.

I don't know how you are extracting their CFW, but i can clearly the ps2emu folder and their files there after extracting with pupexplode script.

There are more files than usual:
ps2_emu.self
ps2_gxemu.self
ps2_softemu.self
pst_emu.self
pst_gxemu.self

There is no pst_softemu.self as one would expect.

What the hell?!
Can you put those on a rar and send them to me?
Thanx!

I don't seem being able to run the script, it keeps freezing, can anybody please run it for me and send me the ps2emu forlder?

Alert STEP FORWARD!

Here are the decrypted elfs from the Cobra USB CFW:
Contents:
http://www.mediafire.com/?nohar57nhn1inad
ps2_softemu.elf
ps2_emu.elf
ps2_gxemu.elf
pst_emu.elf
pst_gxemu.elf

I guess that from pst, T stands for Test console/firmware.
Anyone with the knowledge to take a look on these?

I like your tenacious attitude, VIRGIN KLM.

I can't help in anyway but I feel what you're on.