Nintendo Switch autorcm no picture at all

Have you tried maintenance mode? https://en-americas-support.nintend...to-update-nintendo-switch-in-maintenance-mode

 

Sounds like they used pegascape or the softmod and booted into autoRCM softbricking the unit. Take the EMMC out and place it in a RCM device and disable autoRCM

If that doesn't work, then it might be a screen issue

 

By RCM device I mean a first generation switch that will be able to boot a RCM payload. You can swap the emmc over for a minut, inject hekate and disable autorcm then swap it back

 

You need both SD and Hekate files on it. Grab yourself one and try again.

— Posts automatically merged - Please don't double post! —

That was mine trick, but it really works all the time.

— Posts automatically merged - Please don't double post! —

Next thing to remember - under any circumstances do not connect it to the internet or put cartridge inside! You might have got yourself a 4.1.0 FW switch which is vulnerable to Pegaswitch hack. Don't spoil it.

 

As Dark Ronin said, get a sd card, copy he bootloader folder over and try again

 

Boy oh boy...
Ok then.
First, google latest Hekate - you will find link to github. Take archive from there and unpack it to the root of your fat32 formated microSD. It doesn't matter though if you prefer to use exFA as it makes no difference for hekate.
Second, put that SD card into your unpatched switch with other's switch eMMC installed and launch Hekate.
Third, fix autorcm to normal state.
Forth, forge everything back and confirm that patched switch boots fine.
Fifth, check system firmware version in settings. If it stays at 4.1.0 or less - DO NOT CONNECT THIS SWITCH TO INTERNET as you'll catch supernag right away and won't be able to use caffeine.

 

Yep, that's plenty enough!

That's the idea! You want to take the eMMC module from the machine stuck in RCM and put it in the working unpatched switch.

Don't let either of the machines go online whilst you're repairing the eMMC just to be on the safe side.

Search for Hekate and Atmosphere. You'll find it. Afaik direct links to it aren't allowed for new members like myself.

Yeah. Just use rufus - google it. Select "Boot selection" as Non bootable and under Format Options > File system > FAT32 (Default). Just do that on your 8GB flash drive.

Then copy the files from the "sd" folder in the zip you downloaded from the link I provided to the root of your fat32 formatted sd card.

Put the eMMC that's stuck in RCM mode into the working unpatched switch, put the sd card into the unpatched switch and use your RCM jig to boot it into recovery mode. Plug the switch into your PC or phone, whatever device you use to inject the payload and inject the Hekate payload. Your unpatched switch should boot into Hekate. On the Hekate menus there should be an option to disable auto RCM. Find that option, disable it and shutdown the unpatched working switch.

Take the eMMC out of the unpatched switch and put it back into the none working one. See if it worked or not.

If it didn't it could be the M92T36 chip that's faulty. In some situations it will not short capacitors but can get a switch stuck into RCM mode from what I hear.

 

Good luck

 

Okay, yeah, okay that does seem like it's a bad emmc module from that information.... was the third emmc module loose of from a second console? If it's the latter, we may be able to get the console to boot, provided you have the biskeys for the unit that isn't working...

 

Boot into Hekate and turn off AutoRCM. Then boot into OFW. If it boots up (and shows the screen and all that) it's the CFW. after that just delete and reinstall the CFW you are using

 

You obviously didn't read it was a patched switch as they tried sending a payload and it failed, it was later found to be a faulty emmc module

 

oh I just read that there was an error and tried to help