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

[alexj9626]

The full exploit only worked on 4.1.0, but it's primary vector is a hardware bug like Fusee Gelee.

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


Yes.

Ok thanks for clarifying that, but then is not """dead""" is just that it probably wont work on the new units. A little confusing tittle, but i get the point.

 

[TotalInsanity4]

So Deja Vu isn't "dead," it's just public

 

[YugamiSekai]

I've heard it only worked on 4.1.0, unsure if it works on 6.2.0

It's anything above 1.0.0 IIRC, anything above 4.1.0 requires extra permissions from the Switch

 

[MostGood]

It's anything above 1.0.0 IIRC, anything above 4.1.0 requires extra permissions from the Switch

So, can an exploit for patched switches above 4.1.0 in the future be cfw compatible because of this exploit or no? sorry for the noob questions im new to the switch hacking scene

 

[leo60228]

Ok thanks for clarifying that, but then is not """dead""" is just that it probably wont work on the new units. A little confusing tittle, but i get the point.

So Deja Vu isn't "dead," it's just public

Added more clarification. It's just as dead as Fusee was in July, it just hasn't actually been fixed yet.

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

So, can an exploit for patched switches above 4.1.0 in the future be cfw compatible because of this exploit or no? sorry for the noob questions im new to the switch hacking scene

Yes, but Deja Vu had two components. It had a software component (which was patched in 5.0.0) and a hardware component (which can only be patched in new switches). We need a replacement for the software component, and even then, the hardware component was the most important part.

 

[alexj9626]

Added more clarification. It's just as dead as Fusee was in July, it just hasn't actually been fixed yet.

Yeah i know what you are saying. I just think the term "dead" would refer to other stuff happening. Like, Fusee is not "dead", just public.

For me dead would be that is not longer usable. It would be dead for Mariko units, but again, this is just a discrepancy in use of the word dead.

Still, thanks for the info.

 

[TotalInsanity4]

Added more clarification. It's just as dead as Fusee was in July, it just hasn't actually been fixed yet.

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


Yes, but Deja Vu had two components. It had a software component (which was patched in 5.0.0) and a hardware component (which can only be patched in new switches). We need a replacement for the software component, and even then, the hardware component was the most important part.

Oh wait, Deja Vu had a hardware exploit? I thought it was purely software

 

[leo60228]

Oh wait, Deja Vu had a hardware exploit? I thought it was purely software

That was intentionally kept quiet to avoid it getting fixed/looked for by Nintendo.

 

[Treeko]

I don't know if I am out of the loop of things going on in the scene, but wasn't this exploit reported to nintendo for their hacker bounty program before this was made public?

 

[ZachyCatGames]

F

F

 

[leo60228]

I don't know if I am out of the loop of things going on in the scene, but wasn't this exploit reported to nintendo for their hacker bounty program before this was made public?

No, that was a completely different exploit.

 

[Treeko]

No, that was a completely different exploit.

Then this is a big oof from whoever made the commit to hekate.

 

[guicrith]

Then this is a big oof from whoever made the commit to hekate.

Nah, Im thankful, hopefully the old switchs will get untethered boot now instead of waiting indefinitely.

 

[leo60228]

Nah, Im thankful, hopefully the old switchs will get untethered boot now instead of waiting indefinitely.

It's untethered, but not cold boot. More like the good old MSET hacks from the 3DS days.

 

[guicrith]

It's untethered, but not cold boot. More like the good old MSET hacks from the 3DS days.

Thats fine, so it just has to boot twice, once to normal mode then to CFW.

 

[leo60228]

Thats fine, so it just has to boot twice, once to normal mode then to CFW.

Exactly.

 

[MostGood]

Thats fine, so it just has to boot twice, once to normal mode then to CFW.

But would we need to send it a payload everytime we power it on?

 

[guicrith]

But would we need to send it a payload everytime we power it on?

No, thats the point, its untethered.

 

[MostGood]

No

Then that would make this exploit better than the old RCM exploit.

 

[alexj9626]

No

Yes? Like, powering on (OFW) and then using the exploit (to go to CFW). No dongle/PC payload, but we do need to send it. I think?