Sponsored Links

Sponsored Links

Video: PS3 Slim Retail Console Running 3.66 Custom Firmware


Sponsored Links
179w ago - As a follow-up to the previous JaicraB JFW DH PS3 Custom Firmware videos came a video (below) by pdnked of a PS3 Slim Retail console running Rebug 3.66 Custom Firmware (which is actually PS3 OFW 3.66 with a few Debug files added) from Dospiedras1973 via Spanish site [Register or Login to view links].

A rough translation from [Register or Login to view links] states the following:

Dospiedras1973, EOL and user who has already managed to do the downgrade recently consoles INFECTUS using FAT for that necessary, has released a firmware that allows PS3 to version 3.66 with options debug a machine operative. Some clarifications are annotated by the developer:

Download: [Register or Login to view links] / [Register or Login to view links] (Mirror) / [Register or Login to view links] (Mirror #2)

Dospiedra Modified Firmware details to note:

  • Only user-3.55 (no matter if CFW or OFW)
  • No turning back, pass over to 3.66 with all that that entails. Only you can downgrade to INFECTUS (dospiedras method).
  • No syscalls / payloads ... so that the burden of copies is disabled. For what is agreed is a firmware guy ... GeoHot.
  • The 3.55 homebrew installed no longer work.
  • There is no package installer (for now).
  • Full access to PSN.
  • Works on both Fat and Slim (as shown in the video), no tricks hardware and could suggest a user in the comments.

Of course, install under your own responsibility, nor do I Dospiedras not responsible for any errors or omissions performed by the user.

Shortly following, Rebug developer Cyberskunk stated via ps3crunch.net/forum/threads/206-?p=1380#post1380 the following warning: "DO NOT INSTALL THIS. After ripping this PUP apart it appears the rundown will be VERY VERY SHORT.

This is RETAIL OFW 3.66 with just a 'few' of the files from DEBUG firmware.

  • vsh.self
  • index.dat
  • version.txt

ALL OTHER FILES ARE RETAIL INCLUDING COREOS."

In conclusion, those without an Infectus Mod who do not wish to risk their JailBroken PS3 console and lose the ability to run PlayStation 3 back-ups and homebrew should avoid this PS3 CFW at the present time... whether further progress will change this or not only time will tell.








Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter, Facebook and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene and PlayStation 4 scene updates and fresh homebrew releases!

Comments 46 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles.
 
#31 - ph4rcyd3 - 179w ago
ph4rcyd3's Avatar
My slim is still at 3.61. Since I don't have anything to lose, I'll update with this cfw just to take a look at it. Downloading right now and I'll update as soon as it completes. I'll report back once the process is all done.

#30 - xpa12 - 179w ago
xpa12's Avatar
daveshooter you are correct in thinking that Multiman does not run on debug 3.66, you can install it fine it just comes up with an error message on startup and goes back to XMB.

The original BUM that was patched for debug units still works fine in terms of actually backing up a game, however does not run the game and in my experience the Debug version of Back up manager was not able to run backups from the start. Really wish there was a Master Disc patch application for ps3 games like there was for PS1/2 games Oh well at least i've still got a retail to play with too!

#29 - rikukh3 - 179w ago
rikukh3's Avatar
Correctly signed NPDRM homebrews will work just fine on 3.66 OFW, just like unsigned on debug. Geohot's signing tool use one STATIC npdrm key for all programs, and sony blacklisted that specific key in 3.56+ firmwares.

We need normal npdrm signing tool. And if you can launch your own apps in 3.66 OFW, I'm pretty sure you can write homebrew for installing PKG's or homebrew for decrypting 3.60+ non-npdrm SELFs (hello, psp prxdecrypter!), both doesn't requare low level access or custom syscalls.

#28 - daveshooter - 179w ago
daveshooter's Avatar
As it stands at the moment then, the only chance of playing backups on a stock ps3 3.66 is to find a way of turning your backups into DLC pkg's and then some how creating your own spoofed dlc server, and we know thats not really that hard.

Sign the home made pkg's with 3.55 keys, we already know, if you have a dlc game on from 3.55 or below it will run on a stock ps3 on 3.66 after upgrading the pkg that is.

If you had a true debug/test unit then you would be able to run an unsigned ftp server making backing up no problem, but I was on the understanding the new 3.66 debug units can not play backups that are dumped on the drive, only unsigned pkgs from the PSN or unsigned pkg's you create yourself ?

I also don't think dean's mm will run on a 3.66 debug unit as it will not have the access to the system like it dose on 3.55 and below, but I hope I'm wrong on that one.

#27 - rikukh3 - 179w ago
rikukh3's Avatar
No, multiman and other backup managers requires custom syscalls. But it's possible to launch backups on debug by editing decrypted eboot's.

 

Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links







Advertising - Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2015 PlayStation 3 News