Hardware 8.0 Confirmed Information

[GODDUKEMONEXA]

what about the brick with AUTORCM? was rumor or fake?

 

[fst312]

what about the brick with AUTORCM? was rumor or fake?

I believe I read that’s only for the patched switch’s trying to use cfw on 8.0.

 

[Rahkeesh]

Still wonder though if it’s wise for them to release deja vu before the new switch’s come out even though it got patched on the current switch. Obviously the new ones will be patched but it will be funny if they are already made with the 7.x firmware on them.

If they are already made with old firmware they won't be able to change that. Bring on deja vu.

 

[fst312]

Smash bros better not become one of those forced to update games like power rangers. If it’s not maybe this would be the perfect time test this out. Also Mortal Kombat too unless it’s 7.x than I’m good to go because I’m already on that.

https://gbatemp.net/threads/renxpack-repack-nintendo-switch-nsps-to-work-on-lower-firmwares.535614/

 

[GODDUKEMONEXA]

I believe I read that’s only for the patched switch’s trying to use cfw on 8.0.

Ahh MARIKO consoles, ok got it, thanks

 

[aos10]

Ahh MARIKO consoles, ok got it, thanks

Mariko? They still not released yet, however those are patched units, but not mariko.

 

[Essasetic]

So this confirms TX was spouting BS?

 

[gizmomelb]

So this confirms TX was spouting BS?

if you have a later patched console, then no.. you end up with a brick if you have autoRCM enabled.

 

[Essasetic]

if you have a later patched console, then no.. you end up with a brick if you have autoRCM enabled.

Sources that confirm this? This is incredibly unrealistic...

 

[gizmomelb]

Sources that confirm this? This is incredibly unrealistic...

usually when asked to provide sources for anything the anti SX OS crowd complain they are not google and won't bother providing searches, the person questioning can go search for themselves.

however most other CFW users are not that rude. here you are and you're welcome - https://twitter.com/SciresM/status/1117956835456061440

 

[Essasetic]

usually when asked to provide sources for anything the anti SX OS crowd complain they are not google and won't bother providing searches, the person questioning can go search for themselves.

however most other CFW users are not that rude. here you are and you're welcome - https://twitter.com/SciresM/status/1117956835456061440

Thanks!

 

[Legend Of Kay]

So this confirms TX was spouting BS?

Tx wasn’t spouting anything. A member on the tx forum that doesn’t have any insider information made a post and an admin suggested people don’t update to the higher firmware. That’s it.
Work on your reading comprehension before discussing things with adults.

 

[Essasetic]

Tx wasn’t spouting anything. A member on the tx forum that doesn’t have any insider information made a post and an admin suggested people don’t update to the higher firmware. That’s it.
Work on your reading comprehension before discussing things with adults.

Looking further into the tweet. It only bricks if you're playing with Deja Vu (a patched exploit on 8.0).

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

So only ipatched units will be bricked... So TX was technically right. But they have no ipatched users. So they took it out of context. Causing people to panic for no real reason.

 

[linuxares]

Tx wasn’t spouting anything. A member on the tx forum that doesn’t have any insider information made a post and an admin suggested people don’t update to the higher firmware. That’s it.
Work on your reading comprehension before discussing things with adults.

To be fair, any FW on a patched unit with autorcm will brick unless there is a way to boot an exploit from that mode. Since well... you bricked your Switch on purpose! It's mean to do this incase of an error on the boot so Nintendo can restore it/repair it.

 

[Idontknowwhattoputhere]

Wasn't nspwn patched in 5.0?

 

[Adran_Marit]

Wasn't nspwn patched in 5.0?

Just to provide a bit more context and hopefully clear some doubts:
- The déjà-vu exploit chain goes browserhax > nvhax > gmmuhax > nspwn > [undisclosed] > warmboothax;
- What is going to be released is a browser exploit for firmware versions 4.0.0 to 6.0.1 and the "nvhax" exploit which allows you to take over the nvservices' process and access the GPU MMU (which we used for gmmuhax).

I know it's not much yet, but this will grant those with ipatched units the ability to explore the system further and look for even more vulnerabilities on a higher privilege level.
For general users (with ipatched units), the benefits will depend on the firmware version you are on:
- 4.1.0: vulnerable to the entire déjà-vu chain so it can go up to nspwn right away (full userland takeover and therefore, homebrew);
- 5.0.0 to 5.1.0: nspwn was patched in this version, but workarounds are possible by abusing gmmuhax;
- 6.0.0 to 6.0.1: many changes made exploitation really hard to achieve, but there are still workarounds.

6.1.0 patched the browser exploit that will be released (others are already being worked on) and 6.2.0 patched "nvhax" (closing down the current exploit chain).

 

[Idontknowwhattoputhere]

So there not releasing the warmboothax exploit?
Just a simple userland exploit?
Bullshit
EDIT:I misred nvpwn as nspwn lol

 

[gizmomelb]

Looking further into the tweet. It only bricks if you're playing with Deja Vu (a patched exploit on 8.0).

So only ipatched units will be bricked... So TX was technically right. But they have no ipatched users. So they took it out of context. Causing people to panic for no real reason.

ahh it's the old **technically correct**, the best kind of correct

Better people don't upgrade before 8.0 compatibility is announced, than whine and complain in the meantime how it wasn't their fault and when is the next update coming?

 

[linuxares]

To clearify.

If you got an iPatched unit and run a software hack, that enables AutoRCM. You are bricked!
If you got an unPatched unit and run a software hack, that enables AutoRCM. You are fine!

@Adran_Marit mind quoting me on the OP? So people don't get scared?

 

[WiiUBricker]

8.0 has 9 burnt fuses, the same as 7.x

Turned out this is false. 8.0 has burned only one efuse.