I believe I read that’s only for the patched switch’s trying to use cfw on 8.0.what about the brick with AUTORCM? was rumor or fake?
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.
I believe I read that’s only for the patched switch’s trying to use cfw on 8.0.
Mariko? They still not released yet, however those are patched units, but not mariko.Ahh MARIKO consoles, ok got it, thanks
So this confirms TX was spouting BS?
Sources that confirm this? This is incredibly unrealistic...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...
Thanks!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
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.So this confirms TX was spouting BS?
Looking further into the tweet. It only bricks if you're playing with Deja Vu (a patched exploit on 8.0).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.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.
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).
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.
Turned out this is false. 8.0 has burned only one efuse.8.0 has 9 burnt fuses, the same as 7.x