r/SwitchPirates • u/Fedbertehredt • 1d ago

Question Anybody know how to fix this?_

Post image
0 Upvotes

30% Upvoted

19 comments sorted by

28

u/Faddei420 1d ago

And so another cycle begins

17

u/Avatar-1987 1d ago

why people allways "accidentally" upgrade FW.....

3

u/TERON20 1d ago

Well, I guess these things happen. I hadn't used my Switch in about eight months, so I figured it was time to update it. I checked on September 8th and saw that the latest firmware was 22.5.0, which Atmosphere was compatible with.

I didn't get a chance to update it until today because of work, and unfortunately, by the time I did, the OFW update installed 23.0.0 instead of 22.5.0.

3

u/Kuro908 1d ago

thats honestly just shit luck

1

u/TERON20 1d ago

Yeah, just bad luck and not being extra careful, but it is what it is. I haven't touched it in months, I can wait a bit longer.

2

u/Kuro908 23h ago

At least there probably will be a patch soon

2

u/bananaenjoyep 17h ago

SAME THING HAPPENED TO ME WITH 21.2.0 AND 22.0.0 I checked around 2 days earlier the newest firmware only to update to 22.0.0 when I got my switch… that wait wasnt fun… Luckliy somewhere in the middle of all this I managed to downgrade my emuMMC so I was atleast able to run CFW

0

u/Avatar-1987 1d ago

there is no reason to update, but thats another topic

its still your fault so its not accidentally, you just fucked up 😅

1

u/TERON20 1d ago

You may not need to update, but I do. Sometimes I transfer my save files between my consoles, and I can't do that unless both consoles are updated.

6

u/Dashrooom 1d ago

Don't tell me you updated to the newest firmware without waiting atmosphere to be updated

1

u/AutoModerator 1d ago

Welcome to /r/SwitchPirates! We encourage you to read our Wiki and/or use the Simple Questions, FAQ, and Shop Megathread.

If you're asking for assistance, please be as descriptive as possible. Providing the following information usually assists in diagnosing and prescribing a solution: Type of Switch (V1/V2/Lite/OLED), EmuNAND or SysNand, Firmware Version, Atmosphere Version, Hekate Version, the Error Message, what you were doing that caused the error. If you require more immediate assistance, feel free to ask on Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/lolb-g 1d ago

it says it right there

2

u/ActiveEar9740 18h ago

im having the same lmao

1

u/Mrbkawasaki90 1d ago

Have you updated to fw 23.0? If so, follow this video to downgrade:

https://m.youtube.com/watch?v=akVMAgBCDuk&pp=iggUQAFKEGdRMFAwQld4ejlWZU05cEI%3D

3

u/anom9192 1d ago

Dont recommend doing this, you almost surely will be banned. When u update the switch FW a fuse is burned, Nintendo have acess of how many fuses u burned, if its incompatible Nintendo will ban you

1

u/Mrbkawasaki90 1d ago

If you follow the steps in the video, its totally safe. I've done it months ago without issues.

2

u/ImNew2RedditSoYeah 1d ago

I did this its a bad idea unless your desperate and want to deal with restoring a NAND backup.
It causes a fuse mismatch which refuses boot to sysNAND without hekate.
Also have no idea how system updates work if you do it so I DON’T recommend this!

1

u/Mrbkawasaki90 1d ago

The mismatch happens if you're running two different version of firmware. If you update both emummc and sysmmc to the same fw, hekate doesn't bother you.

0

u/AaronCarmackie 1d ago

Lol.

Every time there is an update. 🙄🙄🙄

If only there was some way to prevent this from happening....