Hacking Discussion is deja vu dead (on new units)?

[zaku]

This was the exploit they believed could still work on Mariko right? lol guess that's over. Looks like we will be probabaly have a situation like ps3 again. Only old units can be hacked.

 

[link42586]

zaku all ps3 consoles can be hacked now. IIRC.

 

[uyjulian]

zaku all ps3 consoles can be hacked now. IIRC.

No.
CFW can only be installed on 25xx and lower consoles.
HEN can be installed on 30xx and higher consoles.
Both methods can be used on 4.82 or lower. 4.83 can not be used.

 

[MostGood]

How was this exploit supposed to work on Mariko consoles if it only supports 4.1.0? Those won't ship with that firmware.

 

[Deleted User]

How was this exploit supposed to work on Mariko consoles if it only supports 4.1.0? Those won't ship with that firmware.

I think Mariko were released with 4.1.0

 

[zdotx00]

I think Mariko were released with 4.1.0

Mariko hasn't been released yet, it's a future hardware revision. The rcm-patched consoles aren't Mariko.

 

[Priyam]

I think Mariko were released with 4.1.0

Mariko isn't released yet. It will definitely release with atleast 6.2

 

[MostGood]

Mariko isn't released yet. It will definitely release with atleast 6.2

If the software side of deja Vu was patched, how could these Mariko units even of been exploited since they'd probably come with at least 6.2.0

 

[linuxares]

Time for Déjà Rêvé!

 

[DogParty]

If the software side of deja Vu was patched, how could these Mariko units even of been exploited since they'd probably come with at least 6.2.0

Deja Vu isn't a singular exploit; it's a chain of exploits. Nintendo patched one exploit in 4.1 but the rest remained unpatched. Nintendo will now patch the other exploits and thus Deja Vu won't be useful at all for the new hardware revision.

 

[MostGood]

Deja Vu isn't a singular exploit; it's a chain of exploits. Nintendo patched one exploit in 4.1 but the rest remained unpatched. Nintendo will now patch the other exploits and thus Deja Vu won't be useful at all for the new hardware revision.

Understandable, does this mean a new hack for ipatched switches will be released soon since theres now no point in keeping it private

 

[DogParty]

Understandable, does this mean a new hack for ipatched switches will be released soon since theres now no point in keeping it private

No idea. I have no idea if only one exploit from Deja Vu was leaked, whether or not the exploit that was leaked is usable without other hacks to boot it, etc. The exploit was disclosed very recently so I'm sure we'll hear more over the next few days.

 

[_hexkyz_]

This is not the core vulnerability of the exploit chain we call déjà vu, this is a variation of warmboothax. Obviously, it was being used as the last step on the chain for granting bootrom code execution.
Note that there are multiple ways of exploiting this, but the underlying issue is always the same: bootrom trusts PMC contents too much.

So yes, the vulnerability presented in hekate is the same as what has been documented in the wiki.

 

[Deleted User]

I though he was talking about pre-mariko sorry, the patched ones, not Mariko.

 

[Agent Moose]

So the whole class losses its privileges for dejavu for the few whom wanted sleep mode on their downgraded consoles. Lovey.

 

[MostGood]

So the whole class losses its privileges for dejavu for the few whom wanted sleep mode on their downgraded consoles. Lovey.

Just don't update your console until a public hack is made from the exploit, not all is lost. Just rip Mariko bootrom exploit

--------------------- MERGED ---------------------------

From what I understand this exploit is still well and alive on all currently released switches. In the future switch owners will need to find another work around once ninty patches this exploit with a hardware revision like they did with first bootrom exploit.

 

[Agent Moose]

Just don't update your console until a public hack is made from the exploit, not all is lost. Just rip Mariko bootrom exploit

Oh I am aware. I just updated Via Choijur and still have my stock 3.0.0 NAND backup.

 

[comput3rus3r]

I heard somebody knowledgeable say "mariko is dead before it's even born" So i woudn't make too much of this. There's always bugs/exploits to be found.

 

[V-Temp]

I heard somebody knowledgeable say "mariko is dead before it's even born" So i woudn't make too much of this. There's always bugs/exploits to be found.

Almost no one knows anything about Nintendo's "fork" of the chip as it has been private for some time, so unless you have someone going through corporate espionage, then nothing is currently know.

What is know is that *this* bug is already patched. But it also draws attention to the warmboot flaws so there will likely be more inspection thrown their way.

Just don't update your console until a public hack is made from the exploit, not all is lost. Just rip Mariko bootrom exploit

--------------------- MERGED ---------------------------

From what I understand this exploit is still well and alive on all currently released switches. In the future switch owners will need to find another work around once ninty patches this exploit with a hardware revision like they did with first bootrom exploit.

The problem is finding the execution to achieve it, and Nintendo's been getting told/found/patched iterations of said, so it becomes harder and harder to leverage. Hence why it currently cuts off at =<4.1. The exploit could persist forever in the bootrom (though they'll likely move in a new ipatch for it if they have already found how to fix it in other models) but you need be able to get to it to execute it.