71w ago - Today PlayStation 3 developers mysis and eussNL on the Wiki have posted a method to get the PlayStation 2 (PS2) Software Emulator working on 3.55 CFW without a DRM-infected Cobra USB dongle for all PS3 Fat and Slim consoles.
To quote: Getting PlayStation 2 Software Emulator working
Method (on Firmware 3.55, without! Cobra-USB Dongle or Downgrade) for all consoles (fat & slim).
1. Replace following files on your consoles /dev_flash/ with the ones included in this archive p3dwik-ps2compatfiles.rar
2. Get into Factory Service Mode (FSM Tool/Dongle)
3. Insert your Original PS2 Game Disc
4. It will run.
Note: Backups won't work. You're getting the compatibility of the 2.60 software emulator with all of its bugs.
A possible compatibility lists:
PS2 Compat. flag
All consoles have hardware information. In GameOS you can call Lv2 Syscall 393 (0x189) sys_sm_get_model to get your consoles information. In Lv1/Hypervisor its in the repository nodes sc 0x5B lv1_get_repository_node with Parameters "sys","hw","config" usually noded as "sys.hw.config#0" or something.
20 00 00 00 FF FF FE FF <--> a backwards compatible console
4E 00 FF FF 0A 03 BC 3C <--> on Hypervisor Page
4E 00 FF FF 01 07 BC BF <--> CECHJ04
Hi I just make a debug app that use some syscalls to do a reset into PS2 Lpar like boot_ps2 does, it should work on dex 4.11 or 4.20 but in these fw there is ps2 netemu instead of softemu so i need someone with an original disc of playstation 2 inserted on bd-drive and launch this test app and see what happens.
I am on 4.11 DEX but i don't have any original disc from PS2... This is basically the same thing that boot_ps2 does on 3.55 but there is a new emu file on dex 4.11 or 4.20 introduced on 3.70 with the use of PS2 Classics on PSN... This is not brick-risk, thanks to anyone who help me with this. Greetings...
1st - Download the file
2nd - Copy the file PS2 Evo v1.0.pkg to the root of a USB drive formated in FAT32
3rd - Install the .pkg from *Install Package Files*
4th - Insert a original PS2 disk on the BD
5th - Run the app and enjoy
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Every developer has the right to protect his/her work by using dongle protection (most of them pretty poor at best).
As seen many o' times over on the GSM scene, dongles are being cracked/hacked/exploited for their contents. It's only a matter of time. Look how quickly all the other dongles were phased out - in what, about 12 months (less I think) we were pretty much dongle free (except FSM)
I'm glad someone can see how much 'work' exists in zadow's releases.
From Wololo (via wololo.net/2012/06/16/ps3-zadows-release-a-useless-repost/): PS3 Zadow's release a useless repost?
Yesterday I posted what appeared to me as a massive breakthrough in the PS3 scene, a bunch of files decrypted from the Cobra dongle, one of the DRM encrypted piracy dongles for firmware 3.55. The files had been released by user zadow28, who seems to have a fairly good reputation on some of the scene’s websites.
I have been contacted since then by several veterans of the PS3 scene, who told me these files are, in essence, garbage.
They didn’t explicitly tell me the word “fake”, but rather, it seems the files posted by Zadow are basically useless information, which in addition has been publicly available for a while. None of them told me “where” that information actually can be found, which for now I interpret as “it is so useless that we will not even bother to tell people where they can find the information in the first place”.
I do not have the tools, the knowledge, or the time to confirm if Zadow28 is a fraud, but I can say I am seeing a pattern I’ve seen in the past on the psp and the vita scene: unknown guy gets semi famous by posting lots of garbage that looks like the real deal, famous devs call him out for a faker, random people start some conspiracy theories about old devs trying to get all the credits, other random people tell the old devs that they should collaborate with the new guy instead of bashing him, old devs have a hard time explaining that it is impossible to collaborate with a dude who has the IQ of a banana. (I’ve been through that so I know how people like kakaroto feel.
So, if I’m to choose a side, I’ll go and trust the old dudes. If they say it’s useless, I guess they’re right.
From defyboy: Thanks but these were mostly available already. With the exception of your IDA DB of course.
Why do I constantly find things newsed as a release when it's just copies of the stuff the developers made available on the wiki long ago. This isn't a gift for developers, it's another cry for attention. The developers either already have this stuff, or know exactly where to get it.
I made a mirror on the wiki for anyone who wants his files: ps3devwiki.com/files/zadow28/
From euss: At least I won't be needed to give zadow unself/ungpkg with sources and precompiles like his last readself2/3/4/5 fail (so much better to use scetool anyhow)... (which btw are all on wiki, /files and gitorious too)
I do not know who incepted this thread with nonbased remarks about Atmel AVR/Micochips PIC, but they should look closer to the content and what is needed for such target. There is nothing AVR/PIC related inside the filesets, just plain unself/ungpkg'ed files which where ran through IDA and exported i64/db files. It also does not make any sense to even /want/ it as a dongle, because if you have the PPU/SPU changes, it would make alot more sense to distribute it as patches (MFW Builder TCL) or live patcher: payload (payloader3) then a stupid dongle.
From CrashSerious: First, I've had some concerning health issues and haven't touched this for several months. Also, priorities were re-alligned in the process and haven't had a chance to pick it back up. So I have nothing to report... on to the main reason for posting.
I had a big long email started (about halfway done) detailing every file in there and just gave up due to the number of things that were junk.
Mostly, it looks like files we already have, unselfed eboot.bins (congratulations on using unself or scetool), a corrupt ida database, some meaningless/worthless logs and who knows what else.
I did look at the corrupt idb to make sure it actually "looked like"an idb. It actually did at a glaqnce--- so at least it's not like the last time and he was trying to pass off a linux binary as lv0 decrypted or some crap like that... oh wait... he did do that, didn't he defyboy .
Probably a better use of my time if I stopped dissecting the gift any ways. Zadow’s files are still available here if you want to give them a look, but it’s probably not the breakthrough I initially thought it was.
Finally, from flat_z: I am very sad looking at all news sites about ps3... when they keep posting any "shocking" news about such noobs as zadow28 and exposing him as the greatest hacker in the world
Hmm, cobra dongle payload hasn't been completely reversed by zadow, because he simply doesn't have the skills for doing that stuff, what he released is something anyone can do on their own, so it's of zero utility to get payload hacked.
yeah, with the improvements he done on MM I think he deserves to work on something that he can get something. He release stuff for free for over a year already, but I do hope that dean wont get mad on us who uses the dongle-less cobra.