PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

December 2, 2010 // 7:10 am - A few weeks back we saw a video of PS Downgrade in action, and today ANTONIOPS at Spanish site (linked above) has posted up some videos showing PS3 Debug Firmware v2.15 being installed via PSDowngrade on a 40GB Retail version 3.41 console followed by running a PS Store demo.

Normally PlayStation 3 service boxes require a proper downgrade PUP file, however, comparing the SHA1 hash of the released PUP confirms it contains nothing special (just the old 3.41) so there appears to be something 'interesting' taking place when downgrading via PS Downgrade.

To quote, roughly translated: The noise you hear when you turn on the PS3 is the reader who is half repaired.

The Debug firmware I've installed the firmware downgrade PSDowngrade 3.41 to 2.15 Debug.

At the moment can only run signed code, such as a PS Store demo.

Those interested can check out the videos below!

Finally, in related news comes a brief guide from gliitch on installing PS3 Debug Firmware v1.0 on a Retail Console:

[ROoT] Level2Diag.self(1)/UPDAT.PUP(DEBUG1.0)

Put your PS3 into service mode, then once its powered down, plug in your usb stick with the files. it takes about 4 or so minutes to complete.

Wait for it to finish, and then turn the PS3 back on O_0 and vollia! 1.0 Debug on a retail PS3. Now, there isn't much point in doing this as it doesn't really have anything on it.

You can update straight back to FW 3.41 via usb by [RoOT] PS3/UPDAT.PUP/

Videos: Debug Firmware on Retail PS3 via PS Downgrade Demo

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew.

#81 - DeViL303 - December 21, 2010 // 7:38 pm
DeViL303's Avatar
1) yes, got RSOD plenty of times on my PS3 while messing around flashing different versions of files to dev_flash.Also sometimes it doesnt even show redscreen to just a blackscreen crash on bootup.

2&3) yes, using service mode payloads for worst cases, and recovery menu for semi bricks it fairly easy to recover and reinstall 3.41 retail, I can't gaurantees in all cases but for example I have tested deleteting over half of dev_flash folder (vsh 85MB) and recovery menu was still working fine , some red screens require service mode to fix, some don't.

#80 - flipperone - December 21, 2010 // 2:09 pm
flipperone's Avatar
1) can you got a RSOD?
2) can you RETURN to the normal ps3 3.41 fw instead?
3) if you obtain a RSOD on startup,you can get it back?

#79 - BwE - December 21, 2010 // 12:16 pm
BwE's Avatar
Quote Originally Posted by FMAranda View Post
If you guys want i can try on my 80GB NTSC (no BC). But if i brick it, how can i bring it back?

you can't brick with failed firmwares. the console doesnt turn on properly yes - but its not a brick

just re-enter service mode OR simply change the pup to 3.41 modified or lower and reboot.

#78 - FMAranda - December 21, 2010 // 11:32 am
FMAranda's Avatar
If you guys want i can try on my 80GB NTSC (no BC). But if i brick it, how can i bring it back?

#77 - BwE - December 21, 2010 // 9:01 am
BwE's Avatar
could depend on the nand - but i doubt it. it's a firmware like every other.

2.36 debug works fine - i've made a video of it, it's on page 7 i think.

#76 - DeViL303 - December 21, 2010 // 7:43 am
DeViL303's Avatar
I seen some people say they can get debug 3.41 firmware to install (and boot) on retail PS3's but Im not sure how many ,if any of the stories are true.Maybe its hardware dependant, seen some say 3.41 debug will install on launch models only.

I have 2 PAL 60GB launch models here(no hardware BC- EE) but no luck on them, when I try the normal downgrader method I get a failed update log and the green light never stops flashing, So maybe its only NTSC launch models or launch NTSC Kiosks, anyone got one and want to test ? (Must be a few slight differences in these models as they include full hardware PS2 emulation and may be other slight differeces to interact with that hardware etc)

I can only get upto 2.36 to install successfully (and boot) like most. I have found a way to get 3.41 debug to install fully on PAL retail (with a successful log and shutdown) but it wont boot after that, just makes the really fast beeping sound like a siren.

I think maybe now that I have 3.41 fully installed all I need is that payload math was describing on irc(quoted above) and it would boot and be fully functional, but im not sure if thats what he meant, maybe it needs to be booting already at this stage.Anyway for now it has retained some retail properties which wont even allow it to boot. Can of course revert it back anyway with service mode payload (this semibrick is beyond a recovery menu reinstall)

So I'm wondering has anyone got close or succeeded in installing and booting anything above 2.36 debug with the normal downgrade method? and if they did what hardware model/files/payload etc was used?

Also has anyone thought about creating a payload for 2.36 debug on retail now that anyone with a JB dongle can install it? be a nice cheap package for new devs combined with the 1.92 leaked sdk and it would be better than nothing until a 3.41 solution comes along.

#75 - evilsperm - December 20, 2010 // 11:08 pm
evilsperm's Avatar
Quote Originally Posted by gumbie View Post
EvilSperm you still chasing the 3.41 debug/hybrid psgroove?

I sent it to CW the other day but I am missing the last dump (my DB is mismatched)

We're working on something like that now but not a hybrid of 3.41. We are trying to actually get 3.41D to launch and making progress.

Can't really say more then that because it's slow going.

#74 - southpawryder - December 19, 2010 // 6:25 pm
southpawryder's Avatar
Quote Originally Posted by DeViL303 View Post
But he was in middle of psdowngrade, probably still in service mode, that's different. I'm talking about a full brick where there is no firmware on ps3, bricked before recovery menu was introduced on example, 1.80 firmware.

If it was a full brick that he recovered from then this is great news and I might even buy one!

i agree with that notation but also could had been how sony fix other issue then later on created the recovery menu for soother transition..

here a theory since debug run unsigned code why not write unsigned code to the nand chip permanatly in similar mode to acid custom but different also may i add how about writtng a whole new column in the xmb for apps.

#73 - BwE - December 19, 2010 // 11:30 am
BwE's Avatar
Quote Originally Posted by flipperone View Post
you can downgrade to debug without any problems?and if you want return to retail?and homebrew works with ps3key silabs?

1) you can downgrade with ALL debug firmware without normal downgrade?
2) you can use homebrew like a normal 3.41 jailbreaked?
3) the EU ps3 can use US ps3 update/downgrade?

no when debug firmwares are installed on retail ps3s they become hybrids with mixed features. its annoying and overall useless.

no because you need to have 3.41 debug and you then need to jailbreak it with the debug jailbreak - both of which you cant do as you cant install 3.41 debug on a retail and if you could it probably wouldnt work as it would be a hybrid

yes the firmware is universal.
Quote Originally Posted by markoskag25 View Post
pls help i tried to install this and how this is happings...

yeah some debug firmwares or firmwares that are too old for your ps3 will give you that error.

the solution is to just downgrade back to 3.41 modified or 3.15 or -- anything.

if it won't let you then just re-enter service mode very easy to fix so don't panic

#72 - arktos - December 19, 2010 // 10:31 am
arktos's Avatar
man you're screwed. now you can throw away your ps3 or you could sell it to me...