PS4 Development Menu (Debug Mode) Enabled on Retail PlayStation 4

Just over a week ago we heard rumors of accessing the PS4 Debug Mode Settings on retail PlayStation 4 consoles, and today scene developer CTurt confirmed it's now possible to access the PS4 Dev Menu on 1.76 retail units thanks to Flat_z!

Download: Enable Dev Menu / PS4-dlclose.zip / PS4-debugmenu.bin (1.0 MB Compiled) via fx0day / PS4-debugmenu.bin (1.0 MB Compiled) via Di_Scala_ / Tutorial by Chaos Kid / PS4-dlclose GIT

From Stuart Fox via Facebook comes a video demo also.

Update: From lezek20 also comes code to enable the more advanced debug menu (dlclose.bin (1.00 MB) compiled by ultradogg), to quote:

*(char *)0xFFFFFFFF833242FD = 0x81;

Just add it into the kernel payload before this part:

writeCr0(cr0);

This could brick your console btw, so be careful!

Update #2: From @j0lama with help from @sealab (Demo video: jgoake.mp4 - 43 MB) via Twitter:
Download: Fully-Enable-Debug-Settings.bin (1 MB)

Fully enable Debug Settings:
*(uint32_t*) 0xFFFFFFFF8269C07Cull=0;
*(uint32_t*) 0xFFFFFFFF8269B56Full=0;

Thanks to B7U3 C50SS and GrimDoe in the Shoutbox for the heads-up!

 

[SorenAlke]

thats retarded who would port from debug to test .... its all messed up

 

[Chaos Kid]

2016
power8.

    * ppc-opc.c (BHRBE, ST, SIX, PS, SXL, VXPS_MASK, XX1RB_MASK,
    XLS_MASK, PPCVSX2): New defines.
    (powerpc_opcodes) <bcdadd., bcdsub., bctar, bctar, bctarl, clrbhrb,
    fmrgew, fmrgow, lqarx, lxsiwax, lxsiwzx, lxsspx, mfbhrbe,
    mffprd, mffprwz, mfvrd, mfvrwz, mfvsrd, mfvsrwz, msgclrp, msgsndp,
    mtfprd, mtfprwa, mtfprwz, mtsle, mtvrd, mtvrwa, mtvrwz, mtvsrd,
    mtvsrwa, mtvsrwz, pbt., rfebb, stqcx., stxsiwx, stxsspx,
    vaddcuq, vaddecuq, vaddeuqm, vaddudm, vadduqm, vbpermq, vcipher,
    vcipherlast, vclzb, vclzd, vclzh, vclzw, vcmpequd, vcmpequd.,
    vcmpgtsd, vcmpgtsd., vcmpgtud, vcmpgtud., veqv, vgbbd, vmaxsd,
    vmaxud, vminsd, vminud, vmrgew, vmrgow, vmulesw, vmuleuw, vmulosw,
    vmulouw, vmuluwm, vnand, vncipher, vncipherlast, vorc, vpermxor,
    vpksdss, vpksdus, vpkudum, vpkudus, vpmsumb, vpmsumd, vpmsumh,
    vpmsumw, vpopcntb, vpopcntd, vpopcnth, vpopcntw, vrld, vsbox,
    vshasigmad, vshasigmaw, vsld, vsrad, vsrd, vsubcuq, vsubecuq,
    vsubeuqm, vsubudm, vsubuqm, vupkhsw, vupklsw, waitasec, xsaddsp,
    xscvdpspn, xscvspdpn, xscvsxdsp, xscvuxdsp, xsdivsp, xsmaddasp,
    xsmaddmsp, xsmsubasp, xsmsubmsp, xsmulsp, xsnmaddasp, xsnmaddmsp,
    xsnmsubasp, xsnmsubmsp, xsresp, xsrsp, xsrsqrtesp, xssqrtsp,
    xssubsp, xxleqv, xxlnand, xxlorc>: New instructions.
    <lxvx, stxvx>: New extended mnemonics.

gas/
@toni1988 @CnCore

* mips.h (mips_operand_type): Add OP_IMM_INDEX and OP_REG_INDEX.
(mips_reg_operand_type): Add OP_REG_MSA and OP_REG_MSA_CTRL.
For MIPS, add comments for +d, +e, +h, +k, +l, +n, +o, +u, +v, +w,
+T, +U, +V, +W, +~, +!, +@, +#, +$, +%, +^, +&, +*, +|.
For MIPS, update extension character sequences after +.
(ASE_MSA): New define.
(ASE_MSA64): New define.
For microMIPS, add comments for +d, +e, +h, +k, +l, +n, +o, +u, +v, +w,
+x, +T, +U, +V, +W, +~, +!, +@, +#, +$, +%, +^, +&, +*, +|.

For microMIPS, update extension character sequences after +.

 

[SorenAlke]

ALL THE CRAP USED UP TO NOW IS USERLAND crap
why do you think @Chaos Kid is pointing out the obvious?
YOU CAN KISS MY ASS (oh they really dont know who )
and shove it.

 

[Chaos Kid]

I will also point out the obvious that these guys don't understand the art of bending or manipulation as there are specific rules to follow when doing all this stuff it's not rocket science it's understanding it which clearly these guys don't.
Only to be used to obtain the data output of something already compiled or you will compile whatever your building and destroy the headers and your alignment will be out of whack.
A master of manipulation knows the limits and where it can be used without damage or won't destroy headers. There's only one true way to use it without affecting files maybe it's time to learn what's going on rather then doing things without understanding the consequences

It's great to see so many developers involved but end game don't need to be a rush who has the first cfw this isn't the same days as back in the Ps3 scene

 

[proskopina]

the ps3 scene was a drama in many ways.....
first lets earn some cash with maximus avr teensy.etc.....
i hope ps4 scene dont start the same way

 

[Chaos Kid]

the ps3 scene was a drama in many ways.....
first lets earn some cash with maximus avr teensy.etc.....
i hope ps4 scene dont start the same way

Honestly it's already started the same way but in a different sence which is unfortunate. All the oh this is the first ps4 cfw and claims which were all false.
Very little is known all due to rush to me looks like the same b.s all over again

 

[SorenAlke]

#include <stdio.h>
#include <stdint.h>


#define BUF_SIZE 256


int main()
{
    char *args[3];
    char *fd[256];

    int  addr;

    addr = 0x1FFFFFFFF0;

    printf("Sploited");

    scanf_s("%d", &addr);

    if (addr < 100){

        printf("cant sploit cus of the length :/");

    }
    else if (addr == 256){

        printf("sploited like a dumb female dog");

    }

    return 0;

}

 

[GrimDoe]

Heres a link to (Silent Hill P.T.)
For both US and UK
https://m.reddit.com/r/silenthill/comments/3ohqaq/found_pkg_file_for_pt_on_sonys_servers/

 

[B7U3 C50SS]

Yeah you can install it but does it run?? @GrimDoe

 

[GrimDoe]

Don't know ?
But its no't that easy to find
PKG. Files for the PS4 like it is for
The PS3. And the Debug Menu was just release with more unlocks coming