57w ago - Following up on the Rebug 3.55.3 / 4.21.1 PS3 CFW REX Editions, this weekend PlayStation 3 developer deank has updated multiMAN to v04.10.00 which includes PS3 Rebug (REX) support alongside the changes outlined below.
Added support for 4.21REX in DEX full mode (DEX flash + DEX lv2 kernel)
Added support for PS1 disc backups for 4.21REX CFW in DEX/DEX mode
Added support for direct-disc-access for 4.21REX CFW in DEX/DEX mode (data CD/DVD/BD discs)
Added support for flashing 256MB NAND *.EID0.NANDBIN backups
Users with broken BD drives can use 4.21REX in DEX mode with fake BDEMU stick/image for 100% game compatibility
IMPORTANT NOTE: If you're using DEX mode in 4.21REX, use this CEX version of mM (do not install the reguar DEX mM which is only for official dex firmwares).
This package also includes:
Rebug Toolbox 02.00.00
c2d + openssl
It is to help users with broken BD-ROM drives (which have a working logic board and married to the PS3). A lot of games have issues when started from /app_home or using "Direct Boot", that's why this is the BEST solution for such users. You will have to be on 4.21CFW REBUG (REX) with DEX Target ID flash and DEX LV2 Kernel (full DEX MODE).
From the ReadMe file: If you do not want to waste a whole USB HDD you can use a small 512MB USB STICK to emulate your broken BD-ROM.
PC and PS3
USB stick/drive (512MB minimum size)
Disc Image Generator Software (ps3gen)
PLAYSTATION3.iso Dummy BDEMU image
4.21CFW REBUG (REX) operating in DEX mode with DEX lv2_kernel (FULL DEX MODE)
Connect a USB HDD to be used for BDEMU
Start "Disc Image Generator for Playstation3" (ps3gen)
Click "Show" button in the top right-hand corner
Click "Select File..." button
Locate and select "PLAYSTATION3.iso" provided in this archive
Click "Save / Emu ..." button
Select "Write Image to BD Emulator HDD"
Select your BDEMU USB HDD
Pick a slot from the list and click "Write Image"
On your PS3 with 4.21REX CFW and multiMAN 04.10.00 installed:
Install "Rebug Toolbox 02.00.00" and launch it
In SELECTOR: REBUG MODE / DEBUG XMB / DEBUG MENU
In DEX/CEX: Flash your DEX EID0 NOR/NAND file (DEX-FLASH.EID0.NORBIN or DEX-FLASH.EID0.NANDBIN file on /dev_usb000 stick)
Quit Toolbox and reboot your PS3
In XMB "Settings" go to "Debug Settings" and set "Blu-ray Disc Access" option to "BD Emulator (USB)"
Turn off your PS3
Connect the BDEMU USB HDD drive/stick to the right-most port (/dev_usb000) - the port closest to the BD-ROM drive
Turn on your PS3
You should see "PLAYSTATION(R)3" Game Disc mounted in XMB Game column
Start multiMAN 04.10.00+, load a game from internal HDD or external USB HDD connected to another port. Do not unplug the BDEMU USB drive.
Start your game from the Disc Icon in XMB.
Done. In the pictures below you can see how it looks when you boot your PS3 with the dummy disc game, if you start it and if you mount a game with mM (Assassin's Creed III used as example) and check XMB
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!
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.