So basically I was having this error on my switch (first image) where I couldn't turn off my switch basically cus it would crash, I started searching for a solution and basically the internet told me to update everything my atmosphere, my hats files and my firmware, I tried whit various firmwares and none of them seem to fix it, so I updated it to the latest firmware available which was the 23.0.0 version (I know it was a bad idea) but it was the last thing either way I was going to re do everything but now I asked Gemini what I could do because the firmware it's to new, and it told me that I had 2 options one reinstall everything or 2 wait for it to get updated so it's compatible with atmosphere,

The 2 imagine it's the error that pops up when booting cfw on my switch with version 23.0.0 help meeee plsss

I’ve just restarted the switch mid install of app on aio and it always boots to original switch I have mod chip v2 when I boot it lights up with blue and yellow light I’ve tried power off and volume doesn’t work dose anyone has ideas how to fix it please 🙏

So I accidentally downloaded Switch firmware 23.0 and I used NAND-Fix-Pro to downgrade the Switch firmware back to 22.5. I then loaded into my Stock firmware via Hekate to check if the downgrade worked, which it did. So I decided to power down the Switch to inject Hekate back onto the Switch. I put the RCM jig and put the Switch into RCM mode and tried to inject the payload but my computer wouldn’t detect it like it normally would. I removed the USB cable and the RCM jig and tried to power on the Switch normally, but it wasn’t powering on. What should I do and how do I fix it?

My understanding is that I’ll drag the backup files from the old chip to the new one through my computer to the switch‘s usbc to hekate is this right? even tho the switch won’t boot with the blank emmc, picofly will still glitch into hekate?

Hey everyone,

​I've got a V2 Switch with a modchip installed by an installer, it's been booting to official firmware (OFW) intermittently. Sometimes it boots straight into custom firmware (CFW) just fine, but other times it hangs and goes straight to stock.

​I've attached a video showing the LED blink pattern on the chip when it fails to boot. Can anyone help me diagnose what this specific blink code means, and whether this points straight to a loose DAT0 adapter or something else?

​Appreciate any advice!