Yeah, also patched switch consoles can enter RCM but you can’t inject a payload.Hey thanks for your concern, i've been told that all switches are able to enter RCM mode irrespective of it being patched or not. Only difference is that you might not be able to inject the payload. I've tried hitting up all my second hand stores and nothing proved fruitful
Reinstall them.
I personally recommend just switching to FAT32 because it won't corrupt your SD card and you don't have to worry about updating to the exFAT version of your firmware. There are ways around the 4 GB limitation on FAT32 which involve splitting your files and installing via USB/network. If you don't want to do those and don't mind the risk of corruption, you can install the exFAT version of your firmware either offline with tools like ChoiDujourNX or online via Nintendo.
Currently, you need an unpatched Switch. But later on there'll be software exploits released for 7.0.1=>, so if you're patient...
K, I was stuck wondering before I went to bed that I might be incorrect about the RCM Mode on Patched units myself. Didn't get to looking that up unfortunately. Thank you. And Best of luck.Hey thanks for your concern, i've been told that all switches are able to enter RCM mode irrespective of it being patched or not. Only difference is that you might not be able to inject the payload. I've tried hitting up all my second hand stores and nothing proved fruitful
What do you mean by "plug in a battery"? If it enters RCM on boot even without the pins being shorted or holding the buttons, it has AutoRCM.
Send a payload to the Switch, and once the OS boots, charge it with the AC adapter.
Unfortunately, Windows 10 is known to have a lot of problems when connecting to a Switch in recovery mode. Since you already know that many people have had this problem, you don't have much in the way of options. You can try a different PC or installing a different OS on yours, just in case you're paranoid about it being something wrong with the Switch itself, but outside of that I would just look into using your phone for RCM stuff.Hi guys,
I'm a bit new at this but after initially setting up my Switch with CFW (I believe it was ReiNX) last year I've finally found the time to start using it again. Unfortunately I am having trouble getting TegraRcmGUI and TegraRcmSmash to recognize the Switch once it is in RCM and connected to my Windows 10 PC. Oddly enough the Switch IS recognized by my PC, but only when the screen is on and only through Devices and Printers + USB View - NOT through Device Manager. Fortunately I can still access OFW so it hasn't been bricked or anything, but obviously if it is not recognized by my PC then I cannot send the payload to the device (as of the present time I only have USB C to USB C and USB A to USB C, nothing that would support my Android phone) and thus cannot get CFW to work. Additionally the Switch charges successfully from the USB C connection, so I do not believe it is the cables fault either (for what it's worth I'm using the Amazon Basics one which explicitly states it supports data transfer). As of the present time I have tried the following;
It does seem to be booting into RCM as it doesn't launch like normal and instead stays on the black screen, but despite all of my attempts I cannot get my PC to recognize the Switch in Device Manager (or at all when the screen isn't on). As such any suggestions would be appreciated, outside of getting a USB C to micro-USB USB cable to try it on my phone (which I will do quite soon if I continue to have no luck getting the device to work). Oh and I would take advantage of Zadig 2.4 but that requires the Switch to show up as SOMETHING in device manager, which it refuses to do
- Updating the TegraRcm version to the latest release
- Installing the applicable drivers (which always works successfully)
- Restarting the PC multiple times
- Removing my existing Jig and trying a new one (aluminium foil method both times)
- Updating the Payload to the latest version
- Unplugging and re-plugging the cable ad-finitium
- Updating the USB C 3.1 drivers on my PC
- Holding the volume-up + power button for varying lengths of time (12 seconds, 2.5 seconds, quick tap etc)
- Reading about a dozen forum threads wherein people describe the same issue
- Using both TegraRcmGUI and TegraRCMSmash
So it is ok to transfer the entire 64GB card over. This has no files I have added manually that are over 4GB
thanks
