Tutorial  Updated

How to skip the "Connect Joycons" system init screen

I've seen this asked a lot over the years and since someone asked it today and I recently mapped out all the Settings saves, I decided to test my theory that the answer was there. It was.

Use case: You are stuck at the system initialize screen with the 'connect joycons' animation but you don't have joycons or one or both rails is broken.

TL;DR for those who already know how to edit system saves: Dump the SystemSettings save 8000000000000050, change the byte at offset 0x29484 from 0 to 1, repack, sign and replace the save.

Tools required:
  • hactoolnet (fire up your command line skills)
  • Lockpick_RCM (if you have an existing dump from this console a fresh dump is not required)
  • TegraExplorer (if you're familiar with HacDiskMount you can use that instead)
  • HxD (or hex editor of choice, this one is just free, lightweight, capable, and ad-free)
Steps:
  1. Use Hekate/Nyx and make a full Raw EMMC backup if you never have! This is the first rule of any hacking endeavor.
  2. If you don't have a key file, use Lockpick_RCM to dump keys from either sysnand or emunand, it doesn't matter which for this purpose. This will dump the key file to SD in /switch/prod.keys.
  3. Reboot to RCM if needed and push the TegraExplorer payload.
  4. Use the Volume keys to navigate to and select either [SYSTEM:/] EMMC (for sysnand) or [SYSTEM:/] EMUMMC (for emunand).
  5. Acknowledge the warning regarding modifying your system NAND and breathe easy since you made a backup, right? RIGHT? Please go back and do that if you haven't. Press Power to continue.
  6. Select save (this might take a minute to load if using file-based emunand).
  7. Select 8000000000000050, then select Copy to clipboard.
  8. Navigate back to the main menu by selecting Folder -> previous folder twice.
  9. Select [SD:/] SD CARD.
  10. Select Clipboard -> Current folder and wait for the copy to complete.
  11. Navigate back to the main menu by selecting Folder -> previous folder.
  12. Select Exit then either reboot to RCM or power off.
  13. Mount the SD card on your computer either using a card reader or by pushing the Memloader payload (this is always recommended to reduce stress on the SD reader connector component).
  14. Open a command prompt (eg. press Win+R and type cmd then press Return).
  15. Navigate to where you unzipped hactoolnet or drag the executable onto the command prompt window (this is a handy trick that makes the next few steps easier; Windows automatically enters the whole path to whatever you drop on it).
  16. I don't know what drive letter you mounted your SD as, but you do! So I'm going to pretend it's Z: but if it's something else, use that instead.
  17. [Note: if the console is Mariko (red-box, new/chipped or Switch Lite) you may need to edit prod.keys by changing "save_mac_key" to "save_mac_key_00" if you get an error like "Unable to sign save file."] If you dragged hactoolnet into the window, you'll have c:\whatever\hactoolnet.exe already populated, so after that, type a space then -t save -k z:\switch\prod.keys z:\8000000000000050 --outdir z:\syssave so your whole command should look like:
    Code:
    c:\whatever\hactoolnet.exe -t save -k z:\switch\prod.keys z:\8000000000000050 --outdir z:\syssave
    Again, please edit this so it matches your own path to hactoolnet and SD mount point.
  18. Open z:\syssave\file in HxD.
  19. Press Ctrl+G to open the Go to Offset dialogue, and type in the number 29484 then select OK. The cursor should be hovering over a byte that reads 00.
  20. Type 01 then press Ctrl+S to Save.
  21. Go back to your command prompt and similarly enter c:\whatever\hactoolnet.exe -t save -k z:\switch\prod.keys z:\8000000000000050 --replacefile file z:\syssave\file. Verify that hactoolnet prints:
    Code:
    Replaced file /file
    Successfully signed save file with key <key>
  22. Eject the SD from the computer, reinsert into console, however you did it, get back to RCM with the SD inserted and inject TegraExplorer.
  23. Select [SD:/] SD CARD.
  24. Select 8000000000000050, then select Copy to clipboard.
  25. Navigate back to the main menu by selecting Folder -> previous folder.
  26. Use the Volume keys to navigate to and select either [SYSTEM:/] EMMC (for sysnand) or [SYSTEM:/] EMUMMC (for emunand), making the same choice as in Step 4.
  27. Acknowledge the warning, press Power to continue.
  28. Select save (as before, this might take a minute to load if using file-based emunand).
  29. Select 8000000000000050, then select Delete file.
  30. Acknowledge the warning, press Power to delete, wait for completion.
  31. Select Clipboard -> Current folder and wait for the copy to complete.
  32. Navigate back to the main menu by selecting Folder -> previous folder twice.
  33. Select Exit then do whatever you need to do to reboot, with or without CFW.
  34. You're done! Instead of the joycon connect animation you should get a screen asking you to accept the Eula then reboot, after which you should be in the OS!
 
Last edited by shchmue, , Reason: clarify step 4 & 26
Something that I would highly recommend after performing this procedure is to disconnect the joycon connectors from the Switch’s motherboard. That way you can actually use the switch in portable mode without having to deal with one of your joycons showing up as docked and the other one as wireless. Plus, the latency is so low that I can’t notice the difference.

If you decide to do this I’d also recommend you enable Auto-RCM (you won’t be able to boot into Atmosphere without this) and purchase a joycon charger (your joycons won’t charge while docked to the Switch).
 
Last edited by JLO64,
Panic Occurred while running Atmosphere

Title ID: 01000000000000002B
Error: std: :abort (0xFFE}

Press Power to continue.

Pressing power brings me to hekate bootlauncher for some reason, and I cant get passed there. Running fusee loops me back to where I am currently. Any help would be greatly appreciated!

EDIT: I obviously did a back up before proceeding, so Im not in panic mode personally (Pun not intended lol), but genuinely confused because I dont believe I've done anything incorrectly. I've been hacking systems for a couple decades now and am very confident in my ability to follow directions as well laid out as these were lol Is it possible that something has changed in the system files since this guide was put together? @shchmue
 
Last edited by ShawnMacTM,
Just made this account to let you know that after following every steps that it worked perfectly for my v16.0.0 system,

Thanks.
 
  • Like
Reactions: mathew77
2023 and still works , thanks alot !!!!!!!!!
Post automatically merged:

2023 and still works , Thanks alot !!!!!!!!!

FOLLOW THE STEP ONE BY ONE DONT SKIP IT !!!!!
 
I have the following problem, when I continue the screen freezes, hactoolnet -t save -k prod.keys 80000000000000000050 --replacefile file syssave\file the same error
 

Attachments

  • IMG_4049.jpeg
    IMG_4049.jpeg
    447.7 KB · Views: 119
replace the rails. you can also get into RCM by booting with the eMMC disconnected but that's quit tedious
My joycon connecter is broken. So, I have to disconnect the eMMC to get into rcm and then plug it in again before sending the payload?
 
Failed to match key device_key_4x
Failed to match key eticket_rsa_kek_personalized
Failed to match key eticket_rsa_kek_source
Failed to match key eticket_rsa_kekek_source
Failed to match key save_mac_key
Failed to match key ssl_rsa_kek_personalized
Failed to match key ssl_rsa_kek_source
Failed to match key ssl_rsa_kekek_source
Failed to match key ssl_rsa_key


im confused... this is a mariko model but it should just work, no?? i point it towards the keys i dumped from lockpick.
 
This worked perfectly!! Thank you so much, very well written and clear tutorial.

For any people doing it nowadays a previous user stated this but a reminider that TegraExplorer has a slightly different layout now. Instead of the path specified in the tutorial the file can be found here instead:

Browse EMMC > SYSTEM > save > 8000000000000050
 
  • Like
Reactions: SkullHex2

Site & Scene News

Popular threads in this forum