Nintendo Switch firmware 18.0.0 has been released

impeeza · Mar 28, 2024

MayorBryce said:
I’m an idiot. I got my Switch back from being modded and I was redownloading stuff because I had to reformat my SD card. I clicked on a demo and it said “Update” and I assumed it meant the game. But no it was the System. So that sucks.

at least was not your cat! for next time remember DNSiTM

MayorBryce · Mar 28, 2024

impeeza said:
at least was not your cat! for next time remember DNSiTM

I did it on SysNAND, so I can’t just block Nintendo’s servers. But thanks for the tip!

I made my EmuNAND first though so I should be good.

raylgo · Mar 28, 2024

M7L7NK7 said:
Who cares about themes, just play the games.. we've had them for years with CFW and it's a 2 second novelty

Themes usually break on an update and requires extra steps to fix. Easy enough to fix though.

impeeza · Mar 28, 2024

impeeza said:
With the attached post:
View attachment 427949

I got a question, How can you downgrade a EmuNAND or even a SysNAND from firmware 18.0.0 to 17.0.1 if nobody have the new set of keys? you need the keys to read the new (Emu)NAND.

Or Am I mixing two different concepts?

Viktorsilva said:
But you had a nand backup of an older version of firmware, right ?

Post automatically merged: Mar 27, 2024

with older nand backup ?

impeeza said:
Supposedly he "created" a 17 firmware using EmmcHaccGen and "restore" it using TegraExplorer scripts

dejavutr said:
No backup needed its patching 17 fw with your switch secret keys and restores that fw to device

Well I didn't ever made the «EmmcHaccGen» Process, just for the sake of learning I just made this process:

On my Console actually I have EmuNAND FW 17.0.1 and SysNAND 4.0.1

Using Daybreak I updated to FW 18.0.0 the EmuNAND, obviously I got this error:

So then I did use EmmcHaccGen and by using my Prod.keys and the FW 17.0.1 folder create a set of files:

Then downloaded SystemRestoreV3.te (from Original Scripts Repo., HATS package or NSW DEAD EMMC Repair pack ) and copied SystemRestoreV3.te, boot.bis files and SYSTEM folder to a folder on my console SD Card.

Then booted my Console to TegraExplorer, and using the option «Browse SD» selected the SystemRestoreV3.te and launch it, Selected the option to apply to my EmuMMC and confirmed

The process take 1 hour but when finished I was able to boot back on my EmuNAND and it was FW 17.0.1.

This process is supposed to be a «Last Resource» but for my experimentation worked just fine.

I really don't know the guts and how work the script but in a very light review the script Backup/Restore the files "BOOT0.bin", "BOOT1.bin", "BCPKG2-1-Normal-Main", "BCPKG2-2-Normal-Sub", "BCPKG2-3-SafeMode-Main", "BCPKG2-4-SafeMode-Sub", "PRODINFO" and on the SYSTEM partition makes a process similar to a firmware upgrade (downgrade) very neat.

The process is well documentated on the video:

by @sthetix A great Work :hrth:

switchvoid · Mar 28, 2024

relochile said:
everything still works in 18.0.0 atmosphere without problems

only that to enter the original system you must do it with the reboot option

Okay so, having read this, I used Daybreak to install 18.0.0 and now Atmosphere doesn't boot at all. I get:
"UNKNOWN PKG VERSION
HOS VERSION NOT SUPPORTED
OR emuMMC CORRUPT

Trying Backup Bootloader
foung pg1 <'20240207110330'>
Unknown pg1 version
HOS version not supported
or emuMMC corrupt

Failed to launch HOS!

Press any key."

Is my system bricked? It boots into stock fine. What should I do? inb4 "omg so stupid", I know.

Edit: Just saw the post appear above mine, will try that.

impeeza · Mar 28, 2024

relochile said:
everything still works in 18.0.0 atmosphere without problems

only that to enter the original system you must do it with the reboot option

WTF!!! which Atmosphère do you have?, SCIRESM in person told everyone what will not work until a pair of weeks.

Do you come from the future?

May be you are booting on OFW without Atmosphère?

Viktorsilva · Mar 28, 2024

impeeza said:
Reading the threads, you need picklock or lockpick but they can not yet extract the keys of FW 18...

If you use latest picklock on FW18 you will only get all keys until 17

Right! But in FW18 without any Emunand ou nand Backup can you rebuild a nand with lockpick ?

Larsenv · Mar 28, 2024

Viktorsilva said:
But you had a nand backup of an older version of firmware, right ?

Post automatically merged: Mar 27, 2024

with older nand backup ?

no

Luvigi · Mar 28, 2024

I received a switch with 18.0.0 so there is no point in installing pi2040, won't it work for me?

RedColoredStars · Mar 28, 2024

impeeza said:
SCIRESM in person told everyone what will not work until a pair of weeks.

Where? I don't see where he said this couple of weeks stuff that yourself and others have stated. The only thing I saw is that he'd get started in a couple of days, which was a few days ago so he's already working on it. There's no way it's going to be a couple of weeks.

impeeza · Mar 28, 2024

Viktorsilva said:
Right! But in FW18 without any Emunand ou nand Backup can you rebuild a nand with lockpick ?

Yes, something like:

impeeza said:
Well I didn't ever made the «EmmcHaccGen» Process, just for the sake of learning I just made this process:

On my Console actually I have EmuNAND FW 17.0.1 and SysNAND 4.0.1

Using Daybreak I updated to FW 18.0.0 the EmuNAND, obviously I got this error:
View attachment 428202

So then I did use EmmcHaccGen and by using my Prod.keys and the FW 17.0.1 folder create a set of files:

View attachment 428204

Then downloaded SystemRestoreV3.te (from HATS or NSW DEAD EMMC Repair pack ) and copied SystemRestoreV3.te, boot.bis files and SYSTEM folder to a folder on my console SD Card.

Then booted my Console to TegraExplorer, and using the option «Browse SD» selected the SystemRestoreV3.te and launch it, Selected the option to apply to my EmuMMC and confirmed

The process take 1 hour but when finished I was able to boot back on my EmuNAND and it was FW 17.0.1.

This process is supposed to be a «Last Resource» but for my experimentation worked just fine.

I really don't know the guts and how work the script but in a very light review the script Backup/Restore the files "BOOT0.bin", "BOOT1.bin", "BCPKG2-1-Normal-Main", "BCPKG2-2-Normal-Sub", "BCPKG2-3-SafeMode-Main", "BCPKG2-4-SafeMode-Sub", "PRODINFO" and on the SYSTEM partition makes a process similar to a firmware upgrade (downgrade) very neat.

The process is well documentated on the video:

by @sthetix A great Work

Post automatically merged: Mar 28, 2024

And lockpick got updated yesterday to extract Fw 18

https://gbatemp.net/threads/lockpick_rcm-payload-official-thread.532916/post-10388390

Post automatically merged: Mar 28, 2024

RedColoredStars said:
Where? I don't see where he said this couple of weeks stuff that yourself and others have stated. The only thing I saw is that he'd get started in a couple of days, which was a few days ago so he's already working on it. There's no way it's going to be a couple of weeks.

View attachment 428292

Hello there, how do you was able? I just updated my console to FW18 and tried to boot injecting fusee.bin and got this message:

HarveyHouston · Mar 28, 2024

PotatoStatic said:
Suyu just switched to a self hosted git instance and kept going.

True, but not without first getting DMCA'd on GitLab. I mean, come on, peeps! Nintendo is coming after most homebrew projects anymore, especially anything Switch homebrew. It's only a matter of time...

Statesman · Mar 28, 2024

Luvigi said:
I received a switch with 18.0.0 so there is no point in installing pi2040, won't it work for me?

Go ahead. By the time you get it installed, there will be no issues with 18.0.0

impeeza · Mar 28, 2024

Statesman said:
Go ahead. By the time you get it installed, there will be no issues with 18.0.0

You could install the PI, then make a backup of your NAND and create a EmuNAND then use EmmcHaccGen to get the EmuNAND back to 17.0.1 and use that EmuNAND offline while all the homebrew gets updated.

Viktorsilva · Mar 29, 2024

impeeza said:
You could install the PI, then make a backup of your NAND and create a EmuNAND then use EmmcHaccGen to get the EmuNAND back to 17.0.1 and use that EmuNAND offline while all the homebrew gets updated.

so, you are saying that it will work even if the emunand is on FW18 ?

Blythe93 · Mar 29, 2024

Viktorsilva said:
so, you are saying that it will work even if the emunand is on FW18 ?

I believe that in order to downgrade the emuNAND via EmmcHaccGen back to 17.0.1 you'll need the prod.keys which you can now get since Lockpick_RCM has been updated to support the latest 18.0.0 firmware. In the meantime, Atmosphere and Hekate will get updated eventually.

impeeza · Mar 29, 2024

Viktorsilva said:
so, you are saying that it will work even if the emunand is on FW18 ?

Something like.

Now your SysNAND is on FW 18. So:

Install the PicoFly and create a backup of your SysNAND.
Then create a EmuNAND using the backup.
Following the instructions of https://gbatemp.net/threads/nintendo-switch-firmware-18-0-0-has-been-released.652159/post-10388321 downgrade your EmuNAND to 17.01.
Theoretically the downgraded EmuNAND can be booted using PicoFly and Hekate
Now that EmuNAND is dirty Y SHOULD NEVER TO CONNECT TO NINTY servers, use Atmosphère's DNSMiTM and/or 90DNS to avoid that EmuNAND to connect to telemetry.
You can boot on the Dirty EmuNAND and use it offline and setup all Homebrew you like.

Post automatically merged: Mar 29, 2024

Blythe93 said:
I believe that in order to downgrade the emuNAND via EmmcHaccGen back to 17.0.1 you'll need the prod.keys

to create a set of files to downgrade to 17.0.1 you need 17.0.1 keys

Post automatically merged: Mar 29, 2024

impeeza said:
Something like.

Now your SysNAND is on FW 18. So:

Install the PicoFly and create a backup of your SysNAND.

Then create a EmuNAND using the backup.

Following the instructions of https://gbatemp.net/threads/nintendo-switch-firmware-18-0-0-has-been-released.652159/post-10388321 downgrade your EmuNAND to 17.01.

Theoretically the downgraded EmuNAND can be booted using PicoFly and Hekate

Now that EmuNAND is dirty Y SHOULD NEVER TO CONNECT TO NINTY servers, use Atmosphère's DNSMiTM and/or 90DNS to avoid that EmuNAND to connect to telemetry.

You can boot on the Dirty EmuNAND and use it offline and setup all Homebrew you like.

Post automatically merged: Mar 29, 2024

to create a set of files to downgrade to 17.0.1 you need 17.0.1 keys

also you can build the prerelease of atmosphère 1.7.0 which have FW 18.0.0 support.

snaker · Mar 29, 2024

For those who cant wait and for some reason they got a switch on 18.0.0 if you search good enough there is an atmosphere version that works on 18.0.0. Just use that version, launch daybreak and downgrade to 17.0.1. The fuse count is the same so there will be no issues. The other way is using emmchacgen, as stated by impeeza, after you have got your prod.keys generated from the newer lockpick for version 18.0.0. For those who find difficult to use the 2nd method the 1st one is a better choice.

Viktorsilva · Mar 29, 2024

snaker said:
For those who cant wait and for some reason they got a switch on 18.0.0 if you search good enough there is an atmosphere version that works on 18.0.0. Just use that version, launch daybreak and downgrade to 17.0.1. The fuse count is the same so there will be no issues. The other way is using emmchacgen, as stated by impeeza, after you have got your prod.keys generated from the newer lockpick for version 18.0.0. For those who find difficult to use the 2nd method the 1st one is a better choice.

i´ve searched all around and cant find any Athmosphere 17 (supporting FW18) . any tip where to find?

BigOnYa · Mar 29, 2024

Atmosphere and Hekate have both been updated for FW 18

https://github.com/Atmosphere-NX/Atmosphere/releases
https://github.com/CTCaer/hekate/releases

Ver. 18.0.0 (Released March 25, 2024)​

¡Kabito!

Well-Known Member

Well-Known Member

¡Kabito!

New Member

¡Kabito!

Well-Known Member

Dr. Wii, Ph.D

New Member

Well-Known Member

¡Kabito!

Christian Modder

Well-Known Member

¡Kabito!

Well-Known Member

The Treasure Tracker

¡Kabito!

Well-Known Member

Well-Known Member

Has A Very Big

Similar threads

Popular threads in this forum

Ver. 18.0.0 (Released March 25, 2024)