Did I just brick my Switch

[E30Nova]

Hey y'all.

So I have an unpatched v1. Been working flawlessly for years.

I just installed a game yesterday (.NSP if it matters) by connecting the Switch with Tinfoil running to my PC and putting it into the install folder. Tinfoil gave me an error (I can't remember what it was), and when I went back to the home screen, the new game was just a gray square with a spinning wheel in it.

I thought maybe sigpatches needed to be updated since it's been a while. So I googled and installed the latest ones. No change.

But the Switch was saying an update was available, so I figured maybe I'll update it and then update Atmosphere.

I used Daybreak to install the update that was on the Switch, but now it won't turn on at all.

I have no idea what firmware I was on prior to this mess, so I don't know where to go from here.

I've tried holding volume up, volume down and power, and any other combination I can think of, but it won't do anything.

Is it dead?

 

[HawaiianInTown]

Your console probs get auto RCM, you need the updated (maybe modified) .bin file to inject payload.

 

[E30Nova]

I doubt it, because it automatically booted into the stock OS unless I put the jig in and injected the payload.

What updated/modified .bin file are you talking about? I tried searching for updated/modified payloads and couldn't find anything.

So far I've tried hard rebooting it with and without the SD card, connecting it to my PC with/without the jig, and even disassembling it and unplugging the battery for a few minutes.

I just can't get it to turn on.

I think it might be legit bricked.

 

[Jayinem]

I don't think it's bricked lot's of people have problems with updating. Try to delete the entire Atmosphere folder, copy the new Atmosphere to the sd card, then copy over with sigpatches and retry. I know you may think what you did was essentially the same thing but for some reason this fixes the problem a lot of times starting with a fresh Atmosphere folder.

Also by the way your post reads you added the sigpatches then updated, but did you put the new Atmosphere as well? You only mentioned sigpatches but sigpatches and Atmosphere are two separate things. You have to install Atmosphere then overwrite with the sigpatches. The sigpatches only work with the new Atmosphere not the Atmosphere you already had before updating.

I think you're going to be fine. You either missed this very important step of updated Atmosphere AND the sigpatches or you just need to delete the Atmosphere folder anyway and put a fresh one then apply sigpatches.

Here is the new Atmosphere https://github.com/Atmosphere-NX/Atmosphere/releases

Here are the sigpatches https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-177#post-10438165

Use this fusee.bin to send the payload via TegraRCM found in this post (also very important if you don't use Hekate, it won't work without THIS fusee.bin, you probably thought you could just use any fusee.bin) https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10437379

 

[impeeza]

Hey y'all.

So I have an unpatched v1. Been working flawlessly for years.

I just installed a game yesterday (.NSP if it matters) by connecting the Switch with Tinfoil running to my PC and putting it into the install folder. Tinfoil gave me an error (I can't remember what it was), and when I went back to the home screen, the new game was just a gray square with a spinning wheel in it.

I thought maybe sigpatches needed to be updated since it's been a while. So I googled and installed the latest ones. No change.

But the Switch was saying an update was available, so I figured maybe I'll update it and then update Atmosphere.

I used Daybreak to install the update that was on the Switch, but now it won't turn on at all.

I have no idea what firmware I was on prior to this mess, so I don't know where to go from here.

I've tried holding volume up, volume down and power, and any other combination I can think of, but it won't do anything.

Is it dead?

first at all press and let pressed the power button for 30 seconds not less.

which method do you use to inject the payload?


Did you updated Hekate and the payload.bin on your injection method?

 

[Jayinem]

There's several things he could have missed, it sounds like he just sends the fusee.bin payload instead of Hekate (but I could be wrong) then he needs the specific fusee.bin I linked to at the end of the last post. He also mentioned he updated sigpatches but didn't mention updating Atmosphere at all. Some people get confused and think you just need the sigpatches and can overwrite the Atmosphere on your sd card but you need to update both. Let's see if these things help. I'd be shocked if at least one of these don't solve his issue and it works.

If you get the Switch to boot after doing all this and you get a fatal crash error I know how to fix that too, reply here. I went through this just this morning.

I'm 99.999999999% sure he didn't brick the Switch. But you need to use Incognito I think that's still what is needed to block Nintendo servers from updating your Switch on you. You should be the only one updating your Switch on your own not Nintendo.

 

[M7L7NK7]

Search for topics about bricking your switch and every one of them gets fixed, unless it's a hardware issue you can fix it

 

[Nephiel]

But the Switch was saying an update was available, so I figured maybe I'll update it and then update Atmosphere.

Always update Hekate, payload, and Atmosphère first, and only then, the console firmware.

Also, it's best to check beforehand and make sure Hekate and Atmosphère support the latest firmware (18.1.0 is supported at this time).

 

[E30Nova]

I don't think it's bricked lot's of people have problems with updating. Try to delete the entire Atmosphere folder, copy the new Atmosphere to the sd card, then copy over with sigpatches and retry. I know you may think what you did was essentially the same thing but for some reason this fixes the problem a lot of times starting with a fresh Atmosphere folder.

Also by the way your post reads you added the sigpatches then updated, but did you put the new Atmosphere as well? You only mentioned sigpatches but sigpatches and Atmosphere are two separate things. You have to install Atmosphere then overwrite with the sigpatches. The sigpatches only work with the new Atmosphere not the Atmosphere you already had before updating.

I think you're going to be fine. You either missed this very important step of updated Atmosphere AND the sigpatches or you just need to delete the Atmosphere folder anyway and put a fresh one then apply sigpatches.

Here is the new Atmosphere https://github.com/Atmosphere-NX/Atmosphere/releases

Here are the sigpatches https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-177#post-10438165

Use this fusee.bin to send the payload via TegraRCM found in this post (also very important if you don't use Hekate, it won't work without THIS fusee.bin, you probably thought you could just use any fusee.bin) https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10437379

To answer your question, yes, I just copied over updated sigpatch files without updating atmosphere. That's what I've done in the past and have never had issues.

BUT...

I did what you said. Reassembled the Switch.

Deleted the Atmosphere folder. Copied the latest Atmosphere folder to the SD card.

Copied the latest Hekate folder (bootloader and a .bin file) to the SD card. (not sure why I did this, I think it's just because I already downloaded it and saw someone else mention Hekate, so I copied it over)

Copied the individual sigpatch files to their respective folders.

Put the SD card back into the switch, injected the latest fusee.bin file, and.....signs of life!!

My PC recognized I connected the switch to it and successfully injected the payload. But it booted to a black screen with the following:

A fatal error occurred when running FusEe.
Failed to open sdmc:/atmosphere/package3!

Press POWER to reboot.

I pressed the power button but now it's stuck at a black screen.

I'm guessing it has something to do with whatever firmware was on the Switch that I installed with Daybreak, but I have no idea what to do now to fix it.

Post automatically merged: Sep 21, 2024

Search for topics about bricking your switch and every one of them gets fixed, unless it's a hardware issue you can fix it

Yeah, sorry. I tried searching but I was probably panicking and also probably had a few too many beers, so I couldn't find relevant search results. I tried doing everything suggested in the posts I found but none of them worked. Sorry if this is another duplicate "omg I bricked my switch" post.

 

[linuxares]

Nay, package3 just need to be updated.

Do like this, completely clear your SD Card of all Atmosphere and Hekate folders.

https://switch.hacks.guide/extras/updating/#keeping-your-system-up-to-date - then just follow this

 

[E30Nova]

Nay, package3 just need to be updated.

Do like this, completely clear your SD Card of all Atmosphere and Hekate folders.

https://switch.hacks.guide/extras/updating/#keeping-your-system-up-to-date - then just follow this

Bro.

I don't know what the difference is with what I did today versus what I did the other day, but that did it.

I deleted the Atmosphere folder again, but I didn't have a Hekate folder, so I deleted the Hekate .bin file.

Extracted the latest Atmosphere folders to the SD card, extracted the latest Hekate bootloader folder to the SD card, injected the latest fusee.bin payload and it's alive again!!!

System settings shows current version is 11.0.1|AMS 1.7.1|S

The game I installed actually shows the game art and title, but has an exclamation point and says corrupted data.

Do I need to update sigpatches or do I need to delete it and reinstall it?

 

[linuxares]

Bro.

I don't know what the difference is with what I did today versus what I did the other day, but that did it.

I deleted the Atmosphere folder again, but I didn't have a Hekate folder, so I deleted the Hekate .bin file.

Extracted the latest Atmosphere folders to the SD card, extracted the latest Hekate bootloader folder to the SD card, injected the latest fusee.bin payload and it's alive again!!!

System settings shows current version is 11.0.1|AMS 1.7.1|S

The game I installed actually shows the game art and title, but has an exclamation point and says corrupted data.

Do I need to update sigpatches or do I need to delete it and reinstall it?

Well you have to update the signature patches now, since you delete the atmosphere folder, they are inside there.
Also you need to firmware update now I guess?

 

[E30Nova]

I'm scared to update the firmware now, lol.

My Switch has already been banned a long time ago, so what's the recommended way to update the firmware?

 

[linuxares]

I'm scared to update the firmware now, lol.

My Switch has already been banned a long time ago, so what's the recommended way to update the firmware?

https://rentry.org/UpdateCFWAndFW

Just google Switch firmware and Darth and you should find it

 

[E30Nova]

https://rentry.org/UpdateCFWAndFW

Just google Switch firmware and Darth and you should find it

YUP.

So I updated the firmware and updated the sigpatches, but the game was still showing the exclamation mark and saying corrupt data.

Uninstalled the game through Tinfoil and reinstalled it, and now the Switch is back to normal and the game is working.

So THANK YOU to everyone!

For anybody that stumbles across this thread with the same issue:

Delete your Atmosphere, bootloader and Hekate folders.

Install the latest Atmosphere, bootloader and Hekate folders.

Download the latest firmware, transfer it to your SD card and install it with Daybreak.

Install the latest sigpatches.

Enjoy your working Switch with the latest games.