I have a switch that doesn't appear to boot or charge or anything. The device doesn't show any sign of life on its screen and wont show up when plugged into a dock or charging. The only indication of life i've gotten is by plugging it into a pc. It registers in device manager as 'Nintendo Switch APX mode'. I took this to mean that it was stuck in RCM mode (maybe autoRCM or something) and tried to use tegraRCMgui (it did show up) to boot the test payload. It showed nothing on the screen still so i checked the serial and sure enough its a patched switch. So without being able to boot into any CFW, how can this switch be stuck in RCM mode. Its entirely possible i'm misunderstanding this somehow but I thought you guys would probably know more than I do about it. Thanks in advance for any help.
I am having this same problem and I am having a hard time finding help, please if anyone can figure this out.
It just shows up as APX in windows but thats the only indication I can get that its not completely bricked.
ALSO if i use the power button while its plugged in to the PC, the APX in windows will go away and come back like its powering on and off.... yet I am getting no backlight, no indication whatsoever from the switch that it has power.
The only other response I can get is when I plug it into the dock, the dock light flashes green for an instant.
It just shows up as APX in windows but thats the only indication I can get that its not completely bricked.
ALSO if i use the power button while its plugged in to the PC, the APX in windows will go away and come back like its powering on and off.... yet I am getting no backlight, no indication whatsoever from the switch that it has power.
The only other response I can get is when I plug it into the dock, the dock light flashes green for an instant.
https://gbatemp.net/threads/my-pc-doesnt-detect-my-nintendo-switch-in-rcm-mode-as-apx-device.512066/
Did you install Zadig properly.
Did you install Zadig properly.
Fixed!
well... evidently I did install Zadig correctly, but in the past i was using tegraRCMgui instead of tegraRCMsmash, so i just now tried using the payload in tegraRCMsmash, and the screen came to life! So try that, OP!
whats weird is i was using SX Tools on my phone as well as tegraRCMgui before this, and they both were working fine, so i am not sure why they BOTH did not work... but this is what fixed my issue.
well... evidently I did install Zadig correctly, but in the past i was using tegraRCMgui instead of tegraRCMsmash, so i just now tried using the payload in tegraRCMsmash, and the screen came to life! So try that, OP!
whats weird is i was using SX Tools on my phone as well as tegraRCMgui before this, and they both were working fine, so i am not sure why they BOTH did not work... but this is what fixed my issue.
Morning,
So the Tegra has a bootstrap processor which establishes the power management subsystem and does a bunch of other checks to ensure the integrity of things before transferring execution of the boot process to the bootstrap code on the onboard eMMC. If there is a problem during this stage, then the USB interface is opened up in recovery mode to allow some chances of recovery/debug of the problem. This is what your are seeing on your PC. If you take a working switch and pull the eMMC daughterboard, then this will force RCM mode as the bootstrap panics. Of course you can force this in software (AutoRCM) and also using a jig.
In your case, it's a patched switch, then AutoRCM is unlikely to have been set. This feels more likely to be an issue with the boot checks performed, so a corrupted or unseated eMMC, or something not right with the power subsystem. I would start with running some checks around the M92T PD controller. There are some great posts on this forum with guidance on what to measure, although don't be fooled into thinking that shorted capacitors is the only indicator of a problem. It's one failure indication. I've got Switches that have failed to boot, don't suffer shorts, but the problem has been the M92T anyway.....
Sheriff.
Similar threads
