This tutorial uses TegraRCM command line to send payloads to RCM enabled Switch.
Command line is used since it offers a more detailed explanation on what is going on.
So it is a definitive way to confirm if your Switch is patched or not without further questions.
This tutorial does not make any modification to your Switch console.

Requirement:
No Micro SD Card is required.
1. Any way of entering Recovery Mode. Please read here, https://gbatemp.net/threads/the-ultimate-list-of-mods-to-enter-rcm.502145/
2. biskeydump.bin payload(please get the latest version, as of 30th July 2019, the latest version is V9), can be downloaded from https://switchtools.sshnuke.net/
3. TegraRcm GUI, can be downloaded from https://github.com/eliboa/TegraRcmGUI/releases
4. USB C to USB A cable
5. A PC with USB port (Sorry I don't have Mac so I could not cover this area)

Step-by-Step (in total 7 steps):
1. put in your RCM Jig on the right joy con rail. Press and hold Vol+ then press the power button.
You should see a black/blank screen after you press the power button.
If you see a Nintendo logo, you can power off your console and try to adjust your RCM Jig position.

2. To install APX driver
2.1 Launch TegraRcm GUI, go to Settings tab, click on "Install Driver" button.


Confirm the driver installation.


2.2 For those having problems installing APX driver :
Install and launch Zadig. Plug your Switch in RCM mode, then select Options > List All Devices.
Select the APX device and check which driver is installed for this specific device. If libusbK is not the current driver, install it.

(This step is copied from https://gbatemp.net/threads/tegrarcmgui-simple-gui-for-tegrarcmsmash.503510/)

3. Plug in USB cable from your PC to Switch(in RCM).
Open TegraRcm GUI and you should see this window with "RCM OK".


Alternatively, you can use Device Manager to confirm if the APX device is recognized.


Now you can close the TegraRcm GUI application.

4. Copy biskeydump.bin to the TegraRcm GUI folder.


5. Open a command line and go to the TegraRcm GUI folder.


6. Run this on the command line

TegraRcmSmash.exe -w biskeydump.bin BOOT:0x0

7. Check the result
7.1 Switch accepts and executes payload, which mean your Switch is not patched.
Please refer to 0X7000


You will also see QR code on your Switch screen.

7.2 Switch accepts but does not executes payload, which means your Switch is patched.
Please refer to 0X0000

 

[WC00]

Site is outdated. Biskeydump should work even on firmware 8.X since no new keys were added.

Thanks. Will try using the lastest version available on biskeydump site. Now i just hope to have luck and got an unpatched switch.

 

[Daenyse]

Hi, i know this one is pretty old but couldn't find a better place to ask.
So i have a new Pokemon edition Switch and I tried this, the GUI says 0x7000 setup. Does that mean it isn't patched or do i have to use command line? Because that doesn't work for me.

 

[redmagejosh]

Hi, i know this one is pretty old but couldn't find a better place to ask.
So i have a new Pokemon edition Switch and I tried this, the GUI says 0x7000 setup. Does that mean it isn't patched or do i have to use command line? Because that doesn't work for me.
View attachment 168402

Not sure if you noticed but the current payload you injected seems to be a .exe instead of a .bin file

 

[4thwioko]

guys I ran the test and it showed me this, I recon it's neither 0x7000 nor 0x0000,

so is it patched or not?

 

[Draxzelex]

guys I ran the test and it showed me this, I recon it's neither 0x7000 nor 0x0000,

so is it patched or not?

Your console is likely not to be patched but there is something with the port on your computer your using or the USB cable. Try different USB ports, cables, or computers.

 

[MagnesG]

I get the 0x7000. I'm giggling right now lol.

Edit: Nevermind I get it.

 

[[Alt][F4]]

What are the chances of 5.0.1 switch that I just bought xaw 10111 being patched, I don't have a usb c cable at home right now. I would imagine very high since it is so close to 1012

 

[Draxzelex]

What are the chances of 5.0.1 switch that I just bought xaw 10111 being patched, I don't have a usb c cable at home right now. I would imagine very high since it is so close to 1012

Ridiculously high considering that not only is the serial number really close to 1012 but because its firmware is 5.1 which is higher than the lowest firmware they ship with, 4.1.

 

[rorschach86]

Question. I checked my serial # (xaw1009.....) which tells me the console may or may not be patched. If I do this and it is patched, is there any risk of damaging console or getting banned just by checking?

 

[Draxzelex]

Question. I checked my serial # (xaw1009.....) which tells me the console may or may not be patched. If I do this and it is patched, is there any risk of damaging console or getting banned just by checking?

No and no.

 

[rorschach86]

Good answer. Thanks.

 

[cat2115]

Just got the Switch yesterday and based on the site, ismyswitchpatched, it's in the orange region (XAW10085xxx) Software version is 8.1.0.

If I want to be sure, the method on 1st page is still good using latest version (TegraRcmGUI v2.6, biskeydump v9)?

Thanks

 

[Draxzelex]

Just got the Switch yesterday and based on the site, ismyswitchpatched, it's in the orange region (XAW10085xxx) Software version is 8.1.0.

If I want to be sure, the method on 1st page is still good using latest version (TegraRcmGUI v2.6, biskeydump v9)?

Thanks

Any payload will do but OP recommends biskeydump as it is simple to use and will let you know if it was successful immediately.

 

[Wombleinc]

I am getting all the right messages back but nothing happens on my switch besides a black screen. I can boot up much switch just fine the normal way but there are no extras. I've tried different versions of atomosphere, different payloads, two different SD card(one a 128 GB card and a 32 GB Fat32 card). I've tried everything I could think how to get this shit to work but at this point I am getting frustrated.

I bought this switch literally 3 days after launch but for whatever reason my serial number is XAW70000363474, if anyone has any information to lead me in the right direction that would be great.

 

[awalsh053]

hey all got my switch in rcm mode...but when I inject biskeydump I just get a black screen does this mean switch is not hackable or am I doing something wrong thx..

 

[awalsh053]

If the driver is installed correctly, and the Switch is in RCM mode, the Switch will show up in Windows device manager as APX device under an entry called libusbK. If it does, then it is in RCM and you can launch the payload. This is like instant.

My switch is in RCM mode but only black screen after launching payload ...ses payload injected any ideas?

 

[gnilwob]

I am getting all the right messages back but nothing happens on my switch besides a black screen. I can boot up much switch just fine the normal way but there are no extras. I've tried different versions of atomosphere, different payloads, two different SD card(one a 128 GB card and a 32 GB Fat32 card). I've tried everything I could think how to get this shit to work but at this point I am getting frustrated.

I bought this switch literally 3 days after launch but for whatever reason my serial number is XAW70000363474, if anyone has any information to lead me in the right direction that would be great.

1. Use biskeydump payload to confirm if your switch is hackable.
Because this payload does not need any additional files on your microsd.
But your switch should be hackable because you bought it 3 days after launch, which is before Jul 2018.

2. Once you already confirm that it is hackable, they read other guide regarding how to use Atmosphere.
You may not have a correct file / folder structure on microsd so it does not work for your.

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

My switch is in RCM mode but only black screen after launching payload ...ses payload injected any ideas?

And what does it say on the console or TegraRCMGUI output console ?

 

[cat2115]

Any payload will do but OP recommends biskeydump as it is simple to use and will let you know if it was successful immediately.

My kids don't want NS to be hacked. Thank you

 

[RobinMeade]

The first post is not explained correctly or something.

I think I shorted the pin 1 & 10 (paper clip method) and Nin Switch powers on If I press power only.

If I hold volume up and power seem like nothing happens, which supposedly is the desired effect?

I then connect the USB cable and it immediately turns on the console! There is nothing in the first post whether that is expected behavior or not and is not addressed if it's not.

I tried again going into the RCM mode or whatever its called with cable already plugged in and tried to install the driver, but it just shows red as in no RCM devices is connected. Since it's not clear whether when console goes into RCM mode it supposed to shows any kind of sign of power on, I have no idea if I'm doing anything right and what is the remedy. It's really frustrating.

EDIT: Installation wizard for ADX Driver says that the device driver installation was successful "libusbK Nintendo Switch | Ready to use" But when I look for it in the Device Manager I don't see anything new. Is that standard "Installation successful" message regardless if NSwitch is in RCM mode or it can only install when NSwitch is in RCM mode?

EDIT2: It sucks that this forum detaches jpgs from the body of the thread. Is there any way to switch so the jpgs are zoomed in the body of the thread itself? Not only hard to juggle between text and jpgs, but then I was getting confused whether I'm looking at the window with the example or I was looking at the actual installation program because all dialog boxes were positioned about at the same height!

EDIT3: Never mind all the above. I switched from USB 3.0 to 2.0 and everything worked right away. Unfortunately my Nswitch with serial from the orange range is patched 0x00000. I still have a shot being on v4.1.0 or 4.0.1 whichever is compatible. Too bad though.

 

[oasch]

if my switch its on 9.0.0, does this method work?