Headless Switch V1 (LCD motherboard connector broken)

nobitakun · 2026-08-18T11:33:26+0100

Hello, I have a Switch V1 which is unpatched but it has the LCD connector broken and it does not show image in the screen. The screen works perfectly, and the backlight too, including the touch controls.

I can turn the console on and once the OS has booted it shows image on TV if I connect it through the USB-C cable, so the USB-C port is also working correctly. I tested a 128GB microsd card and it is read correctly in the OS, showing 116GB free, formatted in FAT32.

The issue is, I am trying to boot into Atmosphere but it does not work. I prepare the microsd with the website switch.hacks.guide and use the sysMMC, as I can't create emuEMMC automatically through Hekate.

The hekate_ipl.ini file I have is as follows:

[config]
#Autoboots to any available boot option
autoboot=1
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1

[Atmosphere PKG3 sysMMC]
#pkg3=atmosphere/package3
fss0=atmosphere/package3
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp

[Stock sysMMC]
#pkg3=atmosphere/package3
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/stock_boot.bmp

I tested this very same microsd with another V1 unpatched working Switch and it works correctly, but it does not autoboot. It waits in Hekate screen, then I have to select the autoboot through the menu manually. After I have selected it, I turn off the good Switch and insert the microsd into the bad screen Switch to do the exactly same process, but the console stays with backlight on after the payload injection. I try to connect it to the TV, but no image.

Good Switch: firmware 7.0.1
Bad Switch: firmware 22.5.0
Hekate version: 6.5.3 (latest package)
Atmosphere: 1.11.2

I have both pkg3 and fss0 options in the file because I tested both of them with same results.

What could be the solution to this?

Thank you in advance.

thesjaakspoiler · 2026-08-18T12:25:15+0100

Emummc's are cryptomagically linked to each device so cloning an emummc from another Switch won't work afaik.

I presume you have an unpatched V1 Switch.

Hekate unfortunately does not support HDMI output so you need to do some of extra work with a PC to prepare the emummc :
1. Dump your NAND with NxNandManager with a PC.
2. Prepare the emummc on the SD card manually
If this is done you can boot into the emummc with Atmosphere instead of Hekate.

This is what my AI overlord had to say :

1 Dumping your NAND :
-------------------------------------
To dump your Nintendo Switch NAND without using Hekate, you can use NxNandManager (a computer-based tool) by connecting your Switch to your PC while it is in RCM (Recovery Mode). [1, 2]
This method requires Memloader, an ultra-lightweight payload that allows your PC to treat your Switch's internal NAND storage as a standard mass storage device or drive via USB. [1]

Step 1: Download the Necessary Payloads & Tools

Download the latest version of NxNandManager for your computer operating system.
Download the Memloader payload zip file (memloader.bin along with its accompanying bootloader or sample configuration folder).

Step 2: Set Up your SD Card
Memloader needs specific configuration files on the SD card to act as a bridge between the hardware and your PC.

Insert your Switch's microSD card into your PC.
Extract the Memloader files.
Move the configuration folder (usually named bootloader or containing files like ums_emmc.ini) directly onto the root of your microSD card.
Safely eject the microSD card and put it back into your Switch. [1, 2]

Step 3: Boot into Memloader via RCM

Put your Switch into RCM (using a jig or modchip).
Connect the Switch to your PC via your USB cable.
Open your payload injector (e.g., TegraRCMGUI) and select the memloader.bin payload.
Inject the payload.
Look at your Switch screen. You will see a text-based menu. Use the volume buttons to highlight ums_emmc.ini (or the entry for eMMC raw NAND) and press the Power button to select it. Your Switch screen will freeze or go dark, indicating it is now acting as a USB drive. [1, 2, 3]

Step 4: Run NxNandManager to Dump the NAND

Open NxNandManager on your PC with administrator privileges.
Click on File > Open Drive (or Open File/Drive depending on the layout).
Select your Switch's internal storage from the list of available physical drives. (It will typically show up as a ~29GB or ~58GB Linux/unformatted drive).
Once loaded, click on Options > Dump RAW NAND (or use the main "Dump" button).
Select a safe, easily accessible folder on your PC to save the dump, and click Save.

2. Preparing the emumms on your SD card

Step 1: Create the emuMMC Storage (File-Based Method)
The easiest way to skip Hekate is to create a File-Based emuMMC, which lives as regular files inside your SD card instead of an invisible hidden partition. [1, 2]

Insert your microSD card into your computer.
Navigate to the root of the card and create the following directory structure:
SD:/emuMMC/RAW1/
If your computer's operating system supports it (or using a command line), combine your raw NAND parts into a single file named rawnand.bin (total size must equal exactly 31,276,924,928 bytes).
Move your combined rawnand.bin, BOOT0, and BOOT1 files directly into the SD:/emuMMC/RAW1/ folder. [1, 2]

Step 2: Manually Create the emummc.ini Config File
Atmosphere relies on a small configuration file to know where the emuMMC is hosted without Hekate auto-generating it. [1, 2]

Go to the SD:/emuMMC/ folder on your computer.
Create a new text document and name it exactly emummc.ini (ensure the extension is .ini and not .ini.txt).
Open the file and copy-paste the following block: [1]

ini
[emummc]
enabled = 1
sector = 0x0
path = emuMMC/RAW1
id = 0x0000
nintendo_path = emuMMC/RAW1/Nintendo
Use code with caution.

Save and close the file.

Step 3: Configure Atmosphere to Force Boot emuMMC
Since you are bypassing Hekate's launch menus, you need to tell your primary custom firmware payload (like fusee.bin) to enforce your new emuMMC. [1]

Navigate to SD:/atmosphere/config/ (if the config folder or the file doesn't exist, look inside atmosphere/config_templates/ and copy it over).
Open stratosphere.ini in a text editor.
Find the line that mentions all_processes_on_emummc or similar configuration flags depending on your version of Atmosphere. Ensure emummc is globally active.
(Note: By default, if emuMMC/emummc.ini exists and is enabled, launching fusee.bin will automatically load into your file-based emuMMC).

Step 4: Boot Using Fusee
Eject the SD card, put it back into your Switch, and boot the console into RCM. Use your payload injector (like TegraRCMGUI or a web injector) to inject fusee.bin directly instead of Hekate. Atmosphere will detect the manually structured file-based system and boot straight into your emuMMC.

nobitakun · 2026-08-18T16:00:54+0100

In my comment I said I booted the Switch in sysMMC, because I just wanted to try the boot from Atmosphere is working, and it is. In my good Switch it boots no issues. Same card in my bad Switch it does not work. sysMMC is supposed to be booting in any Switch I put the microsd card on, because it simply takes the physical EMMC module the Switch is using and patches the OS on the fly.

I created rawnand.bin boot0.bin and boot1.bin with NXNandManager, using TegraRCMGUI to show each partition in PC.
I created the emuMMC as a partition with those 3 files, then added the usual hack files to the remaining FAT32 partition. Still not working.

Your procedure seems to change a few things from what I did, so I will test it. I just want to be sure Atmosphere does not complain when the LCD connector does not work, because if it does, it will never work, which I would find very surprising as it is a custom application that can almost do anything.

Thank you!

Headless Switch V1 (LCD motherboard connector broken)

Member

Well-Known Member

Member

Similar threads

Popular threads in this forum