Hacking Discussion PSA: Do not update to a new firmware immediately (e.g. 6.0)

itzska · Sep 20, 2018

Welp I went to launch Odyssey and did my usual quick tapping of the A button to launch the game, my switch snuck in an update prompt and I ended up on 6.0 without being able to stop it.

For the post above mine, I was booted into SXOS as it updated and mine went through with it just fine.
(Can't confirm it will for others however as I don't want liability for damages)

On 6.0 as said in previous posts;

I can still boot into SXOS 1.9
I can still start already installed nsp games
~~LayeredFS is not working for me anymore~~ LayeredFS does work when booting into RaJnx cfw (can be found on google and is free)
Dev Menu does not work anymore (A compatible version of Dev Menu for 6.0 isn't available yet, if possible at all)
FTP, Checkpoint, Homebrew Appstore, Homebrew Menu, VBA Next (gba emulator) all work
Edizon crashes my console (could be my error from having a bad file)

~~I did not try to install any NSP files on the new update as I didn't have any laying around to test.~~
I did end up getting a NSP of the new NES Online app and it works flawlessly. I've heard you need an account linked to Nintendo, but you can be offline while using it.

hiroakihsu · Sep 20, 2018

Can anyone confirm if retronx still works or not? leosel's thread says it doesn't work but this thread says it works? Thx

thorasgar · Sep 20, 2018

itzska said:
Welp I went to launch Odyssey and did my usual quick tapping of the A button to launch the game, my switch snuck in an update prompt and I ended up on 6.0 without being able to stop it.

That is one of the habits one has to unlearn with a modded system. Easier said than done, but those few seconds a day saved can cause real headaches and heartbreaks.

FireCrow1013 · Sep 20, 2018

Draxzelex said:
The .nro works fine but the .nsp version won't launch unless you're using RajNX or SX OS. Waiting on confirmation if it works using tomGER's V9.0 SD files.

IFireflyl said:
Looks like Checkpoint works. I also downloaded the .nro BotW save editor (github[dotcom]/Jpe230/BOTW-Save-Editor-GUI/releases) and it is working as well.

This is fantastic news, thanks for the confirmation! I use the .nro version of the homebrew launcher, so that works for me.

aiat_gamer · Sep 20, 2018

Updated to 6.0. Osx is working fine. For some reason I could only see the first splash page of xecuter before going into normal boot mode. I put the jig again and redid the instal that RCM thing and things seems to be back in order.
I have tried many things, but my legit copies work, NPS works, homebrew works.

Albytrozz · Sep 20, 2018

itzska said:
Welp I went to launch Odyssey and did my usual quick tapping of the A button to launch the game, my switch snuck in an update prompt and I ended up on 6.0 without being able to stop it.

I came real close to doing that with Mario Kart after the recent CDN update... I started a thread to warn about the newest updates needing 6.0, forgot to mention how easy it is to accidentally upgrade to 6.0 with them if you're not careful.

That reminds me of when I was recently converting PS Demo Vitas into Retail units... on the Demo Units it will automatically and secretly download and upgrade to the latest firmware as soon as it detects any net connection at all. I had to stay on 3.60 and was trying so hard to do that but you have to go online to use the browser exploit... it caught me and it tried and successfully got half-way through installing the latest firmware before I desperately hard shut it down. It took a good 6 hours and 10,000 tries before I was able to fix it (I did trick it to install a fresh FW in the end).

I HATE when they are sneaky about the FW updates... you KNOW they made it that easy on purpose, why does every other action require so many more presses....

Draxzelex · Sep 20, 2018

Albytrozz said:
I came real close to doing that with Mario Kart after the recent CDN update... I started a thread to warn about the newest updates needing 6.0, forgot to mention how easy it is to accidentally upgrade to 6.0 with them if you're not careful.

While the XML files in those update .NSP files require firmware 6.0, the .NCA files in those .NSPs are still encrypted with a lower masterkey revision found on firmware 6.0. I believe Garou's image from that thread showed that they required masterkey 3 which is found on firmwares 4.X (although the last time I tried installing an update, I believe it said my firmware is too low).

KHEOPS · Sep 20, 2018

Hello
Stealth airplane mode sx os1.9, switch os 5.1.0
Mario odyssey?
How can it check new firmware?
Xml come with nsp update? After decompression?
So Xml requires the firmware ofw 6.0?

Draxzelex · Sep 20, 2018

KHEOPS said:
Hello
Stealth airplane mode sx os1.9, switch os 5.1.0
Mario odyssey?
How can it check new firmware?
Xml come with nsp update? After decompression?
So Xml requires the firmware ofw 6.0?

According to this thread (https://gbatemp.net/threads/theory-ban-risk-after-playing-upcoming-games.517590/), OP is insinuating that somewhere in the .NSP file, it installs something into the version list system save (8000000000000045).

KHEOPS · Sep 20, 2018

Wow!!! Thanks a lot, I can finally understand how my switch could have asked me for updates for some games,
in fact I think that monster hunter, which I played before the release, has updated a file?, which contains the list of new game updates available on eshop?, because my switch from hack sx os 1.4, has not reviewed the online, or ofw... And my games that didn't need to be updated, asked me on the popup after installing some nsp ( I think of monster hunter)
No matter what the nsp, because if I am asked to make updates, it is because a file has changed, and I have learned that I was no longer up to date on certain titles with popup
Thanks nintendo for keeping me up to date when you release updates, even more need to connect to the internet, I just install new nsp games.
Then if I see a popup, I switch to pc, and I download the update directly with a software that I don't mention here.

jslay · Sep 20, 2018

aiat_gamer said:
Sorry for the stupid question, but how did you do that update? I mean did you do anything specific since you have OSX or did you just boot up to either OFW or OSX (which one?) to update?

I booted into stock FW, performed the update, updated joycons, and went back to SXOS FW.
AFAIK, it is best advised to not launch/check anything with your installed NSPs/XCIs while in the stock firmware. But I had no issues updating and going back over to SXOS after the update.

KHEOPS · Sep 20, 2018

Without restoring the nand? Did you take the risk of ban for firmware 6.0?
Not a good idea, unless you know the risks

PsychOsmosis · Sep 20, 2018

Albytrozz said:
I came real close to doing that with Mario Kart after the recent CDN update... I started a thread to warn about the newest updates needing 6.0, forgot to mention how easy it is to accidentally upgrade to 6.0 with them if you're not careful.

That reminds me of when I was recently converting PS Demo Vitas into Retail units... on the Demo Units it will automatically and secretly download and upgrade to the latest firmware as soon as it detects any net connection at all. I had to stay on 3.60 and was trying so hard to do that but you have to go online to use the browser exploit... it caught me and it tried and successfully got half-way through installing the latest firmware before I desperately hard shut it down. It took a good 6 hours and 10,000 tries before I was able to fix it (I did trick it to install a fresh FW in the end).

I HATE when they are sneaky about the FW updates... you KNOW they made it that easy on purpose, why does every other action require so many more presses....

You could have used whitelist-based custom rules on your router to block all internet traffic from the PS Demo Vita but still allow the website with the exploit to work!

jslay · Sep 20, 2018

KHEOPS said:
Without restoring the nand? Did you take the risk of ban for firmware 6.0?
Not a good idea, unless you know the risks

I care 0 if my console gets banned. Not concerned about it at all. Still didn't get banned.

KHEOPS · Sep 20, 2018

Okay I think you are, or you will be at the next ban wave, not a big problem for you, so good game see you soon

PsychOsmosis · Sep 20, 2018

jslay said:
I care 0 if my console gets banned. Not concerned about it at all. Still didn't get banned.

KHEOPS said:
Okay I think you are, or you will be at the next ban wave, not a big problem for you, so good game see you soon

@jslay , there's absolutely no reason for you to have any more risk of a ban for doing the update in OFW.
It's not when you update that your console gets "verified" for modifications, and even if there's a simple check that's made at that point, since you're on OFW at that moment, you should pass said check. I would make sure AutoRCM is not enabled though, as it could be detected.
The "hardware/software modifications verification" happens when you send telemetry data or when you play a game online.

And telemetry data is sent when:
1) An error log is generated when an error occurs (ie. app has crashed, internet can't connect, etc.).
2) You connect to the internet and there were error logs "waiting to be sent away".
3) Periodically when you are connected to the internet.

So you are at no more risk while updating than normally when you're connected to the internet.
That's also why blocking access to the telemetry servers is the single most important thing you can do to prevent being banned (cf. link in my description).

But anyway, you said you don't care about being banned, so it doesn't matter!

hatchcanon · Sep 20, 2018

itzska said:
Welp I went to launch Odyssey and did my usual quick tapping of the A button to launch the game, my switch snuck in an update prompt and I ended up on 6.0 without being able to stop it.

I accidentally hit the same thing... kicking myself now because I can't launch LayeredFS anymore.

jslay · Sep 21, 2018

PsychOsmosis said:
@jslay , there's absolutely no reason for you to have any more risk of a ban for doing the update in OFW.
It's not when you update that your console gets "verified" for modifications, and even if there's a simple check that's made at that point, since you're on OFW at that moment, you should pass said check. I would make sure AutoRCM is not enabled though, as it could be detected.
The "hardware/software modifications verification" happens when you send telemetry data or when you play a game online.

And telemetry data is sent when:
1) An error log is generated when an error occurs (ie. app has crashed, internet can't connect, etc.).
2) You connect to the internet and there were error logs "waiting to be sent away".
3) Periodically when you are connected to the internet.

So you are at no more risk while updating than normally when you're connected to the internet.
That's also why blocking access to the telemetry servers is the single most important thing you can do to prevent being banned (cf. link in my description).

But anyway, you said you don't care about being banned, so it doesn't matter!

Yup, there should be no reason my console should get banned right now. I pcap'd all the data, nothing looked fishy. No AutoRCM (I think you are running a risk with AutoRCM anyway).

And yeah, I have had nintendo dot com and nintendo dot net blacklisted with the game update servers and ctest whitelisted on my pi-hole

pi-hole dot net

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

KHEOPS said:
Okay I think you are, or you will be at the next ban wave, not a big problem for you, so good game see you soon

uhhhh, not sure why you are upset... lol.

Draxzelex · Sep 21, 2018

After updating to firmware 6.0 and having a kind user test some things out for me, I can confirm 99% of hacks works on firmware 6.0; from sleep mode to custom homebrew .NSP files. For homebrew .NSP files, I would recommend deleting pm.kip under your modules/sysmodules folder to have them launch properly on firmware 6.0. I haven't had the time to extensively test all homebrew (there are a lot of these), but the general assumption is that most, if not all, work. SX OS is still the only CFW to not support LayeredFS on firmware 6.0 (I'm in tears) and we need a new DevMenu for firmware 6.0 but outside of that, I think its safe to update. I would highly recommend updating with ChoiDujourNX in case you encounter any problems on firmware 6.0 so you can just downgrade back down at any time.

tubebar · Sep 21, 2018

NSPs install w SX OS, not sure what custome/honebrew are as never seen or used them. Idk of any homebrew that need them.

The only issue w SX Pro is the LayeredFS just depends if you use it or not.

I updated first keeling 6 fuses but then joycon wouldn't work in wireless until you update,so I just went full 6 update.

Really no reason to go back and downgrade. IMO SX users are fine to update, it's all the other ones that may not want to.

Hacking Discussion PSA: Do not update to a new firmware immediately (e.g. 6.0)

Member

SUPREME LURKER OF THE WORLD

Checkout my evil Soon-in-ator™

Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum