PS4 Jailbreak USB Whistle & CFW Rumored by H3ck34 / Ha4cker4net

This is just a rumor making rounds on the net at this point, but h3ck34 has been tweeting recently that a PS4 jailbreak device called the USB Whistle will be coming on February 20th with a PS4 CFW arriving no later than a month later on March 20th.

Is it legitimate? According to Wololo: "There are growing rumors that a group affiliated with the Cobra team (a team popular for some of their PS3 hardware mods, and the same team that announced the – yet to be released – cobra blackfin for PS Vita) have been working on a PS4 Jailbreak usb dongle."

Download: BF_manual.rar / Blackfin-1.0.rar / ADI Blackfin GNU Toolchain / Blackfin Software / EVAL-ADICUP360
While it wouldn't surprise me if the Cobra PS3 scene profiteers started milking the PS4 scene dry instead of releasing open-source freeware, I'm not holding my breath on this rumor being true just yet.

Below are some related tweets, feel free to comment with your own thoughts on the USB Whistle rumor:

Spoiler

 

[pauline45]

I know they read our msgs im not stupid i watch things pretty close when im around and there famous teams ? realy dont you mean the same ones who released cobra?

Want others in here 2?

Now as you all think I'm nothing more then a hacker you are all dead wrong you don't know anything about me or how to obtain the rest that your missing incl daughter key lmao

Which I didn't reveal to Soren but I leave the rest in your hands as our team also watches and waits for your idiot moves to continue n then you will see a change

don't let it worry you about it all the stuff from the cobra side as we worked on things and exploits and theory on ps3 hax as you know mate they haven't got all the keys to it as you know theres 5 coded ones in cobra stuff just as rebug had in there cobra based cfw

 

[Chaos Kid]

don't let it worry you about it all the stuff from the cobra side as we worked on things and exploits and theory on ps3 hax as you know mate they haven't got all the keys to it as you know theres 5 coded ones in cobra stuff just as rebug had in there cobra based cfw

I needed to cool off had a good drink. They are also not aware of the other part of it which I know Soren does not have and the keys are also not hard to extract from cobra I dug that out with a simple exploite ages ago but I can verify this is legit this is actualy SorenAlke trying to use my work but he obviously is missing the huge amounts of my data which was never revealed it's far more superior then cobra

 

[Penne]

So let me get this straight.
This so-called cfw is just an open ssl exploit which enables one to load games from usb?

 

[Chaos Kid]

So let me get this straight.
This so-called cfw is just an open ssl exploit which enables one to load games from usb?

Anyway best of luck

 

[sEKTOR]

they key level 0 is another of what you say, I think they are improved for the keys here ''usb whistle''

$ freetype2-demos/bin/ftbench asan_heap-oob_783b6f_6837_eb01136f859a0091cb61f7beccd7059b

ftbench results for font `asan_heap-oob_783b6f_6837_eb01136f859a0091cb61f7beccd7059b'
-------------------------------------------------------------------------------------

family: (null)
style: (null)

number of seconds for each test: 2.000000

starting glyph index: 0
face size: 10ppem
font preloading into memory: no

load flags: 0x0
render mode: 0

CFF engine set to Adobe
TrueType engine set to version 35
maximum cache size: 1024KiByte

executing tests:
Load =================================================================
==22366==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000eb55 at pc 0x00000069e2fc bp 0x7fffc4670610 sp 0x7fffc4670608
READ of size 1 at 0x60200000eb55 thread T0
#0 0x69e2fb in tt_sbit_decoder_load_bit_aligned freetype2/src/sfnt/ttsbit.c:834:19
#1 0x69d214 in tt_sbit_decoder_load_bitmap freetype2/src/sfnt/ttsbit.c:1145:15
#2 0x69b1bf in tt_sbit_decoder_load_image freetype2/src/sfnt/ttsbit.c:1340:12
#3 0x69eee2 in tt_sbit_decoder_load_compound freetype2/src/sfnt/ttsbit.c:932:15
#4 0x69d214 in tt_sbit_decoder_load_bitmap freetype2/src/sfnt/ttsbit.c:1145:15
#5 0x69b1bf in tt_sbit_decoder_load_image freetype2/src/sfnt/ttsbit.c:1340:12
#6 0x6893d2 in tt_face_load_sbit_image freetype2/src/sfnt/ttsbit.c:1506:19
#7 0x55d265 in load_sbit_image freetype2/src/truetype/ttgload.c:2127:13
#8 0x55bedc in TT_Load_Glyph freetype2/src/truetype/ttgload.c:2487:15
#9 0x5301a2 in tt_glyph_load freetype2/src/truetype/ttdriver.c:396:13
#10 0x4f18ae in FT_Load_Glyph freetype2/src/base/ftobjs.c:742:15
#11 0x4e966e in test_load freetype2-demos/src/ftbench.c:250:13
#12 0x4e9c3f in benchmark freetype2-demos/src/ftbench.c:216:15
#13 0x4e80e9 in main freetype2-demos/src/ftbench.c:1058:9

0x60200000eb55 is located 0 bytes to the right of 5-byte region [0x60200000eb50,0x60200000eb55)
allocated by thread T0 here:
#0 0x4bc4a8 in malloc llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40
#1 0x756740 in ft_alloc freetype2/src/base/ftsystem.c:74:12
#2 0x51b4e7 in ft_mem_qalloc freetype2/src/base/ftutil.c:76:15
#3 0x51abb1 in FT_Stream_EnterFrame freetype2/src/base/ftstream.c:269:12
#4 0x51a800 in FT_Stream_ExtractFrame freetype2/src/base/ftstream.c:200:13
#5 0x69ccab in tt_sbit_decoder_load_bitmap freetype2/src/sfnt/ttsbit.c:1036:10
#6 0x69b1bf in tt_sbit_decoder_load_image freetype2/src/sfnt/ttsbit.c:1340:12
#7 0x69eee2 in tt_sbit_decoder_load_compound freetype2/src/sfnt/ttsbit.c:932:15
#8 0x69d214 in tt_sbit_decoder_load_bitmap freetype2/src/sfnt/ttsbit.c:1145:15
#9 0x69b1bf in tt_sbit_decoder_load_image freetype2/src/sfnt/ttsbit.c:1340:12
#10 0x6893d2 in tt_face_load_sbit_image freetype2/src/sfnt/ttsbit.c:1506:19
#11 0x55d265 in load_sbit_image freetype2/src/truetype/ttgload.c:2127:13
#12 0x55bedc in TT_Load_Glyph freetype2/src/truetype/ttgload.c:2487:15
#13 0x5301a2 in tt_glyph_load freetype2/src/truetype/ttdriver.c:396:13
#14 0x4f18ae in FT_Load_Glyph freetype2/src/base/ftobjs.c:742:15
#15 0x4e966e in test_load freetype2-demos/src/ftbench.c:250:13
#16 0x4e9c3f in benchmark freetype2-demos/src/ftbench.c:216:15
#17 0x4e80e9 in main freetype2-demos/src/ftbench.c:1058:9

SUMMARY: AddressSanitizer: heap-buffer-overflow freetype2/src/sfnt/ttsbit.c:834:19 in tt_sbit_decoder_load_bit_aligned
Shadow bytes around the buggy address:
0x0c047fff9d10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d50: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c047fff9d60: fa fa fa fa fa fa fa fa fa fa[05]fa fa fa fd fa
0x0c047fff9d70: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
0x0c047fff9d80: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
0x0c047fff9d90: fa fa fd fa fa fa 04 fa fa fa 00 fa fa fa fd fa
0x0c047fff9da0: fa fa fd fa fa fa fd fd fa fa fd fd fa fa fd fd
0x0c047fff9db0: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fd
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==22366==ABORTING
---

 

[B7U3 C50SS]

@Chaos Kid i believe you.. over these pricks. but i tell you what.. i'll follow them on twitter because I want to see what other nonsense they put out. Man they are stealing all your work! that's just life in the end, man that sucks

 

[pauline45]

yes they haven't got the exploite to do it half there files are missing aka 3 keys and master key that's not there to run anything but a emu which is no good as for drm dongle that's fake as a few devs can tell how files are compiled as chaos kid said and he knows more about the stuff and did it months ago and wont release stuff as the rest of his team but know who is behind this with the way they work and leave a signature on there exploite files

 

[sEKTOR]

I think it is Chinese but I will not assert without proof as what is fake, I think someone just hiding - it would be nice if they posted information about the key Level 0 I could start hacking. the way is now quite possible to make a working exploit usb whistle the Internet is full of codes and the information I am surprised that no one is taken.

 

[GritNGrind]

I think it is Chinese but I will not assert without proof as what is fake, I think someone just hiding - it would be nice if they posted information about the key Level 0 I could start hacking. the way is now quite possible to make a working exploit usb whistle the Internet is full of codes and the information I am surprised that no one is taken.

I'm looking everyday out there for sure, any help pointing in the right direction? Now, I did see this below link where n3twork released the 1.76 Kernel ELF. Where do you think that takes us?

 

[sEKTOR]

the fact that he is only 1.76 and make .elf is easy. where? naturally leaked (Lizard squad) code, I'm talking about the version 3.15 but for full happiness I need codes Level 0 and so far only you can do drm unit without access to the PSN but s launch of games.
He was talking about the chaos Kid usb-whistle. These codes give access which makes error sending ssl 0x14

SUMMARY: AddressSanitizer: heap-buffer-overflow freetype2/src/sfnt/ttsbit.c:834:19 in tt_sbit_decoder_load_bit_aligned
Shadow bytes around the buggy address:
0x0c047fff9d10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff9d50: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c047fff9d60: fa fa fa fa fa fa fa fa fa fa[05]fa fa fa fd fa
0x0c047fff9d70: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
0x0c047fff9d80: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
0x0c047fff9d90: fa fa fd fa fa fa 04 fa fa fa 00 fa fa fa fd fa
0x0c047fff9da0: fa fa fd fa fa fa fd fd fa fa fd fd fa fa fd fd
0x0c047fff9db0: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fd
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==22366==ABORTING
---