Nintendo Switch 8.0.0 firmware update available

huma_dawii · Apr 16, 2019

If no fuses were burned, can we downgrade to 7.0.1 and have no need for RCM to boot into horizon?

(It is said that 8.0 has same 9 burnt fuses than 7.x).

Jayro · Apr 16, 2019

Seriel said:
There's no consistent standard for version naming. The most popularly used standard is probably semantic versioning (https://semver.org) but devs are free to do whatever they want Some increase the major version over set time periods (Firefox and Chrome) while some align them to the year and month (Ubuntu and Windows) while yet others stay in low versions forever, or follow a standard.
Nintendos versioning has always been odd, but in the end its up to them why they choose.

I align MediCat with Ubuntu's versioning system, because they release close together, and you can easily tell when the version was released.

Cyanopsis · Apr 16, 2019

xs4all said:
Yes, can also confirm, updated system NAND to 8.0, EmuNand on 7.0.1 still boots, now waiting to get my hands on the 8.0 offline update files so I can update EmuNAND, why? I like living on the edge.

Following...

Raymond7 · Apr 16, 2019

Oh god why. I am so into warframe currently, my ember prime was building as to speak ;_;. Now I have to update to play right ?

NoNAND · Apr 16, 2019

I SHALL RESIST until i will succumb yet another time to the overwhelming powers of system updates

Ev1l0rd · Apr 16, 2019

Wario said:
Can you elaborate? I thought the nVidia patched consoles didn't have any exploits for home brewing. No hardware fusee gelee exploit of course and I thought deja vu was a soft mod.

Theres a softmod exploit chain called Deja Vu that is capable of escalating all the way to TrustZone (TrustZone being the level of access we need for a CFW, anything below that is just userland).

Originally it was pushed back for release until Nintendo would bring out "Mariko units", but 8.0 fixes the last known bug in TrustZone that could permit it being exploited, meaning that Deja Vu is essentially patched (and with essentially, I mean SciresM said the last bug he found is patched and he's basically combed through the entirety of TrustZones source code so that means other bugs are extremely unlikely to pop up).

Aka, rip Deja Vu. If you have a patched console for fusee, don't upgrade to 8.x. You'll be able to access homebrew and CFW within a reasonable timeframe from now on.

pLaYeR^^ · Apr 16, 2019

SX OS EmuNAND doesnt work with 8.0.0 or?

goldensun87 · Apr 16, 2019

STABILITY INCOMING

Elliander · Apr 16, 2019

I'm curious about those save file transfers. Is it similar to this? Or does it work offline like in Matching Local Users? and if the same profile with the same NNID exists on both consoles, would it transfer? The old way wouldn't work if the profile already existed. You had to transfer literally everything in one go. If it allows offline transfer it will mean being able to transfer to and from emuNAND where it could then be backed up with homebrew, which means being able to clone saves for a true and effective backup solution unmodded Switch consoles.

I'm actually not interested in cheating. Rather, I want to be able to move my Minecraft save from my SXOS emuNAND to the online Switch so it can be used to create an online server in the future to then be downloaded and merged with my other worlds on a PC world and reuploaded back and transferred over to my offline Switch again so that I can effectively merge all of my worlds into one game.

It bites that they got rid of an exploit for the patched units, but I am sure something else will come along. For all we know, in the process of patching it out, they created a new vulnerability. In any case, I'm glad I went through the extra effort to get both of mine before the stores in my area ran out of old unpatched units. Funny thing is, at one store they had two left when I bought my first Switch, and when I came back a month later for a second the exact same serial number was still there because they put new shipments in the front, so unless someone is actively looking for an old one there still might be some on the shelf for all we know.

EDIT: As a side note: I imagine the wait for an SXOS update will be even more maddening for anyone who actually cares about online play, but personally I keep my unmodified Switch at the same version as my modded Switch so they can play together. I'll just update whenever it is safe to do so. I'm sure it will happen eventually.

thaikhoa · Apr 16, 2019

Elliander said:
I'm curious about those save file transfers. Is it similar to this? Or does it work offline like in Matching Local Users? and if the same profile with the same NNID exists on both consoles, would it transfer? The old way wouldn't work if the profile already existed. You had to transfer literally everything in one go. If it allows offline transfer it will mean being able to transfer to and from emuNAND where it could then be backed up with homebrew, which means being able to clone saves for a true and effective backup solution unmodded Switch consoles.

I'm actually not interested in cheating. Rather, I want to be able to move my Minecraft save from my SXOS emuNAND to the online Switch so it can be used to create an online server in the future to then be downloaded and merged with my other worlds on a PC world and reuploaded back and transferred over to my offline Switch again so that I can effectively merge all of my worlds into one game.

It bites that they got rid of an exploit for the patched units, but I am sure something else will come along. For all we know, in the process of patching it out, they created a new vulnerability. In any case, I'm glad I went through the extra effort to get both of mine before the stores in my area ran out of old unpatched units. Funny thing is, at one store they had two left when I bought my first Switch, and when I came back a month later for a second the exact same serial number was still there because they put new shipments in the front, so unless someone is actively looking for an old one there still might be some on the shelf for all we know.

It says
"Save data can only be transferred between users that are linked to the same Nintendo Account"
[Send Save Data to Another Console] [Receive Save Data]

The save data will be transferred via Nintendo Network.

Elliander · Apr 16, 2019

thaikhoa said:
The save data will be transferred via Nintendo Network.

Well there goes that idea >.< If you gotta go online to make the transfers... hmm. Well, there's another possibility: When creating an emuNAND, the save games clone to it, right? In that case, at the very least, saved games on a clean Switch can be transferred to a clean sysNAND on another Switch and then a new emuNAND created which would then be used to install Homebrew to backup that save which can then be used to inject back to the main emuNAND.

I wonder if there is a way to transfer saves from an emuNAND to the same Switch's sysNAND without use of Homebrew on the sysNAND to run that process in reverse, to get the save from the emuNAND to the sysNAND of another Switch.

thaikhoa · Apr 16, 2019

Elliander said:
Well there goes that idea >.< If you gotta go online to make the transfers... hmm. Well, there's another possibility: When creating an emuNAND, the save games clone to it, right? In that case, at the very least, saved games on a clean Switch can be transferred to a clean sysNAND on another Switch and then a new emuNAND created which would then be used to install Homebrew to backup that save which can then be used to inject back to the main emuNAND.

I wonder if there is a way to transfer saves from an emuNAND to the same Switch's sysNAND without use of Homebrew on the sysNAND to run that process in reverse, to get the save from the emuNAND to the sysNAND of another Switch.

Emunand is a clone of Sysnand, so yes, Save Data will be the same on the both nands. Save data can be extracted from USER partition (save folder), in that case, you can inject the raw save to another Switch.

Emunand and Sysnand save the same identification (unless unlinked), transfer data between the same partitions will also work (SYSTEM/save/ or USER/save/)

mironicurse · Apr 16, 2019

Is proper browser not going to happen on ofw?

Elliander · Apr 16, 2019

thaikhoa said:
Emunand and Sysnand save the same identification (unless unlinked), transfer data between the same partitions will also work (SYSTEM/save/ or USER/save/)

I see. So the :

SD > Nintendo > save

and

SD > Emutendo > save

Is identical, provided the folder was created prior to the creation of the emuNAND and then copied over and renamed from Nintendo to Emutendo?

That is very good to know. It means that I can transfer the save from the emuNAND that way and then transfer from system to system. Well, whenever SXOS is updated to support 8.0 that is. I mean, sure, I can update the sysNAND right away to do it with a lower version emuNAND, but then the sysNAND of one Switch won't be able to play with the emuNAND of the other. Still, this is something to look forward to.

thaikhoa · Apr 16, 2019

Elliander said:
I see. So the :

SD > Nintendo > save

and

SD > Emutendo > save

Is identical, provided the folder was created prior to the creation of the emuNAND and then copied over and renamed from Nintendo to Emutendo?

That is very good to know. It means that I can transfer the save from the emuNAND that way and then transfer from system to system. Well, whenever SXOS is updated to support 8.0 that is. I mean, sure, I can update the sysNAND right away to do it with a lower version emuNAND, but then the sysNAND of one Switch won't be able to play with the emuNAND of the other. Still, this is something to look forward to.

It will work just fine. Nintendo and Emuntendo (SX) folder will be identical. You're right Nand identification won't work on different Switches but Raw save data.

M7L7NK7 · Apr 16, 2019

leafeon34 said:
We might be able to edit saves on an unpatched Switch then transfer them to an unhacked Switch and play online without a ban. Note the emphasis on the word "might".

If a save game exploit is ever found that'll be useful

wurstpistole · Apr 16, 2019

I updated to 8.0 and now SX doesnt work help

thaikhoa · Apr 16, 2019

wurstpistole said:
I updated to 8.0 and now SX doesnt work help

1 Backup current sysnand
2 Restore your previous sysnand backup (<=7.0.1)
3 Create emunand
4 Restore (1) sysnand backup.

Bladexdsl · Apr 16, 2019

wurstpistole said:
I updated to 8.0 and now SX doesnt work help

noob mistake

Adran_Marit · Apr 16, 2019

huma_dawii said:
If no fuses were burned, can we downgrade to 7.0.1 and have no need for RCM to boot into horizon?

(It is said that 8.0 has same 9 burnt fuses than 7.x).

If you have a previous nand backup then yes you can downgrade to that, otherwise you need to manual downgrade to 6.1 then go back up to 6.2 or 7.x

Well-Known Member

MediCat USB Dev

Well-Known Member

Well-Known Member

Give me back my legions!

(⌐◥▶◀◤) girl - noirscape

Doctor Switch

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

GBAtemp MVP

Well-Known Member

fanboys triggered 9k+

Walküre's Hacker

Similar threads

Popular threads in this forum