Hacking Switch stuck with black screen after booting SX OS for the first time

[Axido]

Hey, guys. I might have a currently unusable Switch here right now. First of all, holding the POWER button for some time does not seem to turn off the console.

This is what happened:
-booted into RCM with CTCaer's Mod to toggle off my previous AutoRCM
-rebooted into RCM, this time using the SX OS payload
-toggled the SX OS AutoRCM on
-tapped the Custom OS option to get into SX OS
-got a request file
-ejected the microSD from my Switch and activated the OS on my PC
-reinserted the microSD and hit continue on the SX OS message
-got to the Nintendo Switch Logo screen
-screen stays black

As already mentioned above holding the POWER button for some time doesn't seem to turn off the console. I tried multiple times and even held it down for over two minutes the last time I tried. You couldn't really mess up RCM, so either the USB-C port of the Switch got busted somehow (I doubt that tbh) or the Switch is in some weird state that doesn't accept the force shutdown. Can anyone confirm that the latter is even physically possible?
I guess I screwed up by ejecting the microSD card without turning off the console before reinserting it. I noticed that the battery of my phone still drains a lot quicker when it is attached to the Switch than it would normally (13 per cent in 20 minutes with screen turned off and all apps closed, while the normal consumption in that timespan under those circumstances would not exceed 2 or 3 per cent). I know that my phone can charge my Switch from previous experience.

I don't know which state the console is in right now and I'm confident that opening it and unplugging the battery should fix the issue. Sadly I'm not in possession of a tri-wing screwdriver and the last time I messed with those screws on the Joy-Con rails I got a feeling that those wouldn't come off that easily anymore.

So, would it be a viable idea to just wait for the Switch to die of energy insufficiency? I do know that the infamous "AutoRCM battery issue" has already been confirmed as harmless to pretty much not existant, but I'd like to read some opinions on this.

 

[tecfreak]

I think you have to insert the sd card before you power your switch on.

 

[Risingdawn]

put in SD card, hold volume + and put in dongle, maybe you are stuck in auto rcm with no payload.

Alternatively hold volume + and connect to pc via USB and try smashing tegra again the old fashioned way.

Sounds to me like you are powered into rcm without a payload.

 

[Axido]

Wouldn't AutoRCM eliminate the need to hold Volume+?
That's what it was like with hekate.

Edit: OH... Holding Volume+ did actually work. My bad, I guess. Thanks for the answer.

Okay, SX OS works now. I'm stupid. Thanks for your attention.

 

[kevin corms]

same sort of thing happened to me except Im a sx os only user. Nothing is working for me. I tried holding volume up, holding power for 30 seconds to turn it off etc.. but nothing. Im also not using auto rcm or linux.

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

and now it works, had to use a different usb port on my pc for some reason

 

[plasticocelot]

I have the same problem, but I didn't boot into RCM, and I don't have a licenced copy. When I boot up Atmosphere, it says, "Unable to identify package1" How to fix?

Post automatically merged: Feb 24, 2023

The same problem happened to me! Except, it WILL accept a force shutdown, and TegraRCMGui finds it as an RCM device, but when trying to inject a payload, TegraRCMGui crashes. I am migrating from Atmosphere to SX OS.