Hardware RCM Loader - not being detected on PC

The Real Jdbye · 2026-06-24T03:46:22+0100

VioletRose said:
Just using their phone is even easier and unless they have an iPhone, they don't have to purchase another device. Rekado even has the latest versions of hekate and fusee to auto-download right in the app. It can't get much more simple for the op.

I could never get Rekado to work personally, dongles have been way more reliable for me, but YMMV.

PKM190 said:
Going to try this in a bit.

I assume I just extract:
hekate_ctcaer_6.5.3_Nyx_1.9.3.zip

Onto my SD card. fusee.bin from the Atmosphere Github in the bootloader/payloads folder, and that should be it?

Don't want it to auto boot into Hekate or Atmosphere. Want it as stripped down as possible for online use. I only use it for backing up and editing game saves. I assume when I do that, it just launches into Hekate, and then I select the payload would should like into Atmosphere like usual?

Edit: On my SD card I have the following files under:

bootloader\payloads

fusee-primary.bin
Lockpick_RCM.bin

I am assuming neither of those are necessary anymore? Generally when I update the fusee.bin I just write it to the NS Atmosphere, so I am thinking those are old out of date files.

fusee-primary.bin is probably very old, you can just delete it. They don't even call it that anymore.
Lockpick_RCM probably has newer versions too.

When I say autoboot, I mean when you use the dongle. It will never autoboot without going to RCM mode and injecting a payload, so whenever you want to use OFW, you just boot normally without RCM. That doesn't change.

PKM190 · 2026-06-24T04:31:03+0100

The Real Jdbye said:
I could never get Rekado to work personally, dongles have been way more reliable for me, but YMMV.

fusee-primary.bin is probably very old, you can just delete it. They don't even call it that anymore.
Lockpick_RCM probably has newer versions too.

When I say autoboot, I mean when you use the dongle. It will never autoboot without going to RCM mode and injecting a payload, so whenever you want to use OFW, you just boot normally without RCM. That doesn't change.

Thanks, this was the correct method and finally got it to boot into Hekate. When I booted into Hekate it asked for date, which I set. Then I just clicked Payload and launched into Atmosphere. I assume it does nothing else. It did mention it saved something to the SD card (cannot recall what).

I assume as long as I don't load up the EmmuNand options and whatnot and just go straight to Payload, fusse.bin everything should be safe for online use?

My other question is, I assume this will continue to work even if it cannot be detected by my PC? Any files that would need updating would just be dropped onto the SD card, so it not being detected on my PC should not be an issue for future versions of Atmopshere I assume?

If Hekate needs to be updated, would that be a problem? Kind of wondering what the RCM loader does if all the files are on the SD card.

TLDR for those that may need help:

Removed old fusse-primary.

Dragged/dropped new Hekate files to SD card. Put the fusse.bin for Atmosphere on the SD card:
bootloader\payloads

The NS Atmosphere still works as well. But seeing how much the battery is swelling I have to assume it won't last much longer. Much better quality unit, I just wish the battery was not soldered on which makes replacing it hard.

The Real Jdbye · 2026-06-24T06:10:14+0100

PKM190 said:
Thanks, this was the correct method and finally got it to boot into Hekate. When I booted into Hekate it asked for date, which I set. Then I just clicked Payload and launched into Atmosphere. I assume it does nothing else. It did mention it saved something to the SD card (cannot recall what).

I assume as long as I don't load up the EmmuNand options and whatnot and just go straight to Payload, fusse.bin everything should be safe for online use?

My other question is, I assume this will continue to work even if it cannot be detected by my PC? Any files that would need updating would just be dropped onto the SD card, so it not being detected on my PC should not be an issue for future versions of Atmopshere I assume?

If Hekate needs to be updated, would that be a problem? Kind of wondering what the RCM loader does if all the files are on the SD card.

TLDR for those that may need help:

Removed old fusse-primary.

Dragged/dropped new Hekate files to SD card. Put the fusse.bin for Atmosphere on the SD card:
bootloader\payloads

The NS Atmosphere still works as well. But seeing how much the battery is swelling I have to assume it won't last much longer. Much better quality unit, I just wish the battery was not soldered on which makes replacing it hard.

More or less all options in Hekate are safe, except NAND restore since it can cause a mismatch that gets flagged by Nintendo.
If you aren't installing nsps and such then you're generally safe but save editing in online games can lead to a ban.

The Hekate payload is on the RCMloader but there is a second Hekate payload in the update.bin on the SD and Hekate will detect if this version is newer and boot into it. As long as nothing major changes with how that system works it should just keep working.

Hardware RCM Loader - not being detected on PC

Le derg

Well-Known Member

Le derg

Similar threads

Popular threads in this forum