Hacking Question Switch Won't Boot

[bluedart]

So I just turned my switch off and added some dlc nsps to a subfolder, put the SD card back in the switch, plugged my usb-c cable into it from my pc running TegraRcmGUI, it said "Payload injected !" like normal, but nothing happened at all on the switch. I held the power button for a while so that I could retry, and the same thing happened many times. Of course, I re-seated the microSD card many times; same result. I checked on my pc, and the miroSD card is working properly, all data in tact. I'm using AutoRCM, so I have to boot this way. I'm running cfw 8.1.0 with AMS 0.9.2 (Kosmos 13.0.2 [latest release]). I'm booting with hekate_ctcaer_5.0.1.bin, which is the correct bin for this cfw. I've only burnt fuses from 5.1.0 and updated each time with ChoiDujourNX. I'm wondering why this is a problem, since the last time I changed anything I booted this way and it worked.

I tried using a different usb slot, different cable, restarting TegraRcmGUI, and even removing the files I just put on the card; all of these things have the same reaction. Uh oh. Any ideas?

PS. When I plugged the switch in for some reason it said "installing ACX driver" or something, if that matters, since I already did that a year or so ago.

 

[Hayato213]

Set fusee-primary as what to autoboot.

 

[PHiLiPZ]

Maybe your card is corrupt (you didn’t say what “in tact” means and whether you binary compared the contents. If your card (or the filesystem on it is corrupt copying files on the card might have partially overwritten something needed during the boot. So I’d suggest to try a different card or backup this one, format it and get fresh Atmosphere/Kosmos on it from the web as a test.

 

[bluedart]

Well, I got it to boot up after trying a few recommendations that didn't work. Turns out that my old laptop still had a working TegraRcmGUI I haven't messed with in a while, so I just copied over the new .bin file and tried it with my laptop and it booted up properly. Somehow the driver on my PC must be borked, even though one of the things I tried was reinstalling it from inside TegraRcmGUI. So, just out of curiosity, how would I go about "fixing" the driver on my PC?

 

[Hayato213]

Well, I got it to boot up after trying a few recommendations that didn't work. Turns out that my old laptop still had a working TegraRcmGUI I haven't messed with in a while, so I just copied over the new .bin file and tried it with my laptop and it booted up properly. Somehow the driver on my PC must be borked, even though one of the things I tried was reinstalling it from inside TegraRcmGUI. So, just out of curiosity, how would I go about "fixing" the driver on my PC?

You can use tegrasmash gui to install the driver for the Nintendo switch, should be libusbk, worse case you can use Zadig to troubleshoot.

 

[bluedart]

You can use tegrasmash gui to install the driver for the Nintendo switch, should be libusbk, worse case you can use Zadig to troubleshoot.

... Somehow the driver on my PC must be borked, even though one of the things I tried was reinstalling it from inside TegraRcmGUI. ...

Definitely already tried that, I guess I'll look up an old tutorial and try that from scratch with zadig then. Thanks.

 

[Hayato213]

Definitely already tried that, I guess I'll look up an old tutorial and try that from scratch with zadig then. Thanks.

It should pick it up if it was in RCM mode.

 

[bluedart]

I'm back, because this apparently still isn't fixed on my main computer. I reinstalled the APX driver with libusbK (v3.0.7.0) as directed by TegraRcmSmash's github tutorial, it said "successfully installed" and I get the same result. I tried reinstalling the driver with TegraRcm as well to no avail, even though it said "driver installed." Again, my computer is capable of seeing the device in rcm and it says that it's injecting the payload, but nothing happens. Weird. I also just redownloaded the payload "hekate_ctcaer_5.0.1.bin" just in case and that did not help. Please mind the things I have already tried.

I appreciate any thoughtful help.

Again: works perfectly on my old laptop.