Hacking How to access the PlayStation Store without updating! (Courtesy of Tech James)

[NANASHI89]

Sent from my SM-T280 using Tapatalk

 

[WiiUBricker]

For those who can’t or won’t watch the video, he is on 3.65 and all what he did is use this primary DNS: 212.47.229.76

He claims that works on all system versions from 3.60 to 3.65.

 

[SKGleba]

Well idk if using a """"" unknown""""" proxy is a good idea (you are providing own nfo after all!)

 

[Zukov]

Sent from my SM-T280 using Tapatalk

You should never insert a video and run away. There are people at work, with Youtube blocked and stuff.
So please write it down.

 

[Clector]

That"s just the Henkaku Update DNS.
By the way, this should only work for some time in theory (some weeks), so if anyone is in 3.65 and plan to stay in it, it will be better to purchase and download whatever that you want to play or have before it stops working.

 

[AndrewH]

doesn't work for me unfortunately. I am on 3.63 and manually changed the DNS server to above and nothing. Still being told I must update the system software.

Anyone else do this on 3.63?

 

[driverdis]

That"s just the Henkaku Update DNS.
By the way, this should only work for some time in theory (some weeks), so if anyone is in 3.65 and plan to stay in it, it will be better to purchase and download whatever that you want to play or have before it stops working.

This video is useless as anyone on 3.65 might as well update to 3.67 since the primary thing it did was to "probably" patch KRACK.
KRACK is not very useful from a hacking standpoint on Vita since all important communication is still encrypted so people might as well patch it now if they are above 3.60

 

[SKGleba]

This video is useless as anyone on 3.65 might as well update to 3.67 since the primary thing it did was to "probably" patch KRACK.
KRACK is not very useful from a hacking standpoint on Vita since all important communication is still encrypted so people might as well patch it now if they are above 3.60

Im pretty sure that enso was patched

 

[driverdis]

Im pretty sure that enso was patched

enso was patched with anything over 3.60 alongside henkaku

anyone over 3.60 should just move on to 3.67

 

[SKGleba]

enso was patched with anything over 3.60 alongside henkaku

anyone over 3.60 should just move on to 3.67

No, enso is working on 3.65, if you dont trust me - ask other devs

 

[RY0M43CH1Z3N]

No, enso is working on 3.65, if you dont trust me - ask other devs

We need proofs.

 

[SKGleba]

We need proofs.

Your thing if you trust me or not /shrug

 

[RY0M43CH1Z3N]

trust me or not

I trust in facts

 

[Tom Bombadildo]

enso was patched with anything over 3.60 alongside henkaku

anyone over 3.60 should just move on to 3.67

Enso is not the same as Henkaku, it used a separate exploit point that was still available on 3.65. The reason we don't have it on 3.65 now is because there wasn't any (public, anyways) entry point to load the exploit, and it's unlikely there will be one, IMO anyway.

 

[Clector]

doesn't work for me unfortunately. I am on 3.63 and manually changed the DNS server to above and nothing. Still being told I must update the system software.

Anyone else do this on 3.63?

This usally only works for the previous System Version of the lastest release and it usually only works for some time.
It worked for 3.63 for some weeks after 3.65 was released and then it stopped working in 3.63.

 

[Byokugen]

Yup, Enso was not patched in 3.67, but we still don't have the entry point. As we I mean public, regular people.

 

[SKGleba]

Yup, Enso was not patched in 3.67, but we still don't have the entry point. As we I mean public, regular people.

*was patched

 

[Byokugen]

Y

*was patched

You sure?

 

[SKGleba]

Y

You sure?

Personally didnt test , since some stuff is not working on 3.67, but yeah, im sure they patched it.
At least thats what i understood from yifans tweets /shrug

 

[AndrewH]

This usally only works for the previous System Version of the lastest release and it usually only works for some time.
It worked for 3.63 for some weeks after 3.65 was released and then it stopped working in 3.63.

Gotcha, so if I was on 3.65, this would have worked, but because I am too far behind at 3.63, it won't. I guess it is still looking for 3.65 and since it isn't present, no go. I figured this out, but thanks for clarifying. I really appreciate your time in replying.