Thank but its not my chip model i have the one with the black stripe up to the 3.3v connector
I should have known! Appreciate the extra detail but to be honest I’m not sure of the exact model you’re looking at based on the info provided. You’re going to have to look at the videos and make the judgement call if it is significantly different than the simple videos I linked to.
FWIW, none of them required a reflow station.
Last edited by binkinator,
Posted this before just posting it fresh because I think I can explain it better now:
I hacked my switch with emuNAND a while back. I can't remember if I used to boot to Hekate or if it went straight to Atmosphere. I stopped playing for a year and came back. It wasn't working and I couldn't really remember what I did so I wanted to start over.
I followed the directions at https://switch.homebrew.guide/hacking/fuseegelee/sdsetup and downloaded the following:
.
├── payloads
│ ├── Lockpick_RCM.bin
│ └── hekate_ctcaer_5.7.0.bin
└── sd
├── atmosphere
│ ├── config
│ ├── config_templates
│ │ ├── exosphere.ini
│ │ ├── override_config.ini
│ │ ├── stratosphere.ini
│ │ └── system_settings.ini
│ ├── contents
│ │ ├── 00FF0000636C6BFF
│ │ │ ├── exefs.nsp
│ │ │ ├── flags
│ │ │ │ └── boot2.flag
│ │ │ └── toolbox.json
│ │ ├── 010000000000000D
│ │ │ └── flags
│ │ │ └── boot2.flag
│ │ ├── 0100000000001013
│ │ │ └── exefs.nsp1
│ │ ├── 054e4f4558454000
│ │ │ ├── exefs.nsp
│ │ │ └── toolbox.json
│ │ ├── 420000000000000E
│ │ │ ├── exefs.nsp
│ │ │ ├── flags
│ │ │ └── toolbox.json
│ │ └── 420000000007E51A
│ │ ├── exefs.nsp
│ │ ├── flags
│ │ │ └── boot2.flag
│ │ └── toolbox.json
│ ├── fatal_errors
│ ├── flags
│ ├── hbl.nsp
│ ├── hbl_html
│ │ └── accessible-urls
│ │ └── accessible-urls.txt
│ ├── kip_patches
│ ├── package3
│ ├── reboot_payload.bin
│ └── stratosphere.romfs
├── bootloader
│ ├── hekate_ipl.ini
│ ├── ini
│ ├── payloads
│ │ └── fusee.bin
│ ├── res
│ │ ├── icon_payload.bmp
│ │ └── icon_switch.bmp
│ ├── sys
│ │ ├── emummc.kipm
│ │ ├── libsys_lp0.bso
│ │ ├── libsys_minerva.bso
│ │ ├── nyx.bin
│ │ ├── res.pak
│ │ └── thk.bin
│ └── update.bin
├── config
│ ├── sys-clk
│ │ ├── config.ini.template
│ │ └── log.flag
│ └── sys-ftpd
│ └── config.ini
├── hbmenu.nro
└── switch
├── EdiZon
│ ├── EdiZon.nro
│ └── profile.zip
├── Goldleaf
│ └── Goldleaf.nro
├── appstore
│ └── appstore.nro
├── breeze
│ ├── Breeze.nro
│ ├── profile.zip
│ ├── profilehbm.zip
│ └── reeze
│ └── hbmenu.nro
├── daybreak.nro
├── nxdumptool
│ └── nxdumptool.nro
└── sys-clk-manager.nro
I deleted the contents of my SD card, then loaded the contents of the "sd" folder onto the root of my SD card. I figure I deleted my emuMMC so I guess I need to get into Hekate to recreate the emuMMC files per https://switch.homebrew.guide/emummc/emummc.html?
I have a fresh RCM Loader that I have never modified, and the folder structure looks like this:
.
├── ATMOSPHERE_HEKATE
│ └── payload.bin
├── FOUND.000
│ └── FILE0000.CHK
├── LAUNCH.TXT
├── REINX
│ └── payload.bin
├── SXOS
│ └── payload.bin
├── System Volume Information
│ ├── IndexerVolumeGuid
│ └── WPSettings.dat
├── USER1_XKOS
│ └── payload.bin
├── USER2
├── USER3
└── readme.txt
I'm not sure what to do with the "payloads" folder from the files I got from SDSetup, to get into Hekate, so I can build a new emuMMC. Or even if that's what I need to do.
Any help is appreciated.
I hacked my switch with emuNAND a while back. I can't remember if I used to boot to Hekate or if it went straight to Atmosphere. I stopped playing for a year and came back. It wasn't working and I couldn't really remember what I did so I wanted to start over.
I followed the directions at https://switch.homebrew.guide/hacking/fuseegelee/sdsetup and downloaded the following:
.
├── payloads
│ ├── Lockpick_RCM.bin
│ └── hekate_ctcaer_5.7.0.bin
└── sd
├── atmosphere
│ ├── config
│ ├── config_templates
│ │ ├── exosphere.ini
│ │ ├── override_config.ini
│ │ ├── stratosphere.ini
│ │ └── system_settings.ini
│ ├── contents
│ │ ├── 00FF0000636C6BFF
│ │ │ ├── exefs.nsp
│ │ │ ├── flags
│ │ │ │ └── boot2.flag
│ │ │ └── toolbox.json
│ │ ├── 010000000000000D
│ │ │ └── flags
│ │ │ └── boot2.flag
│ │ ├── 0100000000001013
│ │ │ └── exefs.nsp1
│ │ ├── 054e4f4558454000
│ │ │ ├── exefs.nsp
│ │ │ └── toolbox.json
│ │ ├── 420000000000000E
│ │ │ ├── exefs.nsp
│ │ │ ├── flags
│ │ │ └── toolbox.json
│ │ └── 420000000007E51A
│ │ ├── exefs.nsp
│ │ ├── flags
│ │ │ └── boot2.flag
│ │ └── toolbox.json
│ ├── fatal_errors
│ ├── flags
│ ├── hbl.nsp
│ ├── hbl_html
│ │ └── accessible-urls
│ │ └── accessible-urls.txt
│ ├── kip_patches
│ ├── package3
│ ├── reboot_payload.bin
│ └── stratosphere.romfs
├── bootloader
│ ├── hekate_ipl.ini
│ ├── ini
│ ├── payloads
│ │ └── fusee.bin
│ ├── res
│ │ ├── icon_payload.bmp
│ │ └── icon_switch.bmp
│ ├── sys
│ │ ├── emummc.kipm
│ │ ├── libsys_lp0.bso
│ │ ├── libsys_minerva.bso
│ │ ├── nyx.bin
│ │ ├── res.pak
│ │ └── thk.bin
│ └── update.bin
├── config
│ ├── sys-clk
│ │ ├── config.ini.template
│ │ └── log.flag
│ └── sys-ftpd
│ └── config.ini
├── hbmenu.nro
└── switch
├── EdiZon
│ ├── EdiZon.nro
│ └── profile.zip
├── Goldleaf
│ └── Goldleaf.nro
├── appstore
│ └── appstore.nro
├── breeze
│ ├── Breeze.nro
│ ├── profile.zip
│ ├── profilehbm.zip
│ └── reeze
│ └── hbmenu.nro
├── daybreak.nro
├── nxdumptool
│ └── nxdumptool.nro
└── sys-clk-manager.nro
I deleted the contents of my SD card, then loaded the contents of the "sd" folder onto the root of my SD card. I figure I deleted my emuMMC so I guess I need to get into Hekate to recreate the emuMMC files per https://switch.homebrew.guide/emummc/emummc.html?
I have a fresh RCM Loader that I have never modified, and the folder structure looks like this:
.
├── ATMOSPHERE_HEKATE
│ └── payload.bin
├── FOUND.000
│ └── FILE0000.CHK
├── LAUNCH.TXT
├── REINX
│ └── payload.bin
├── SXOS
│ └── payload.bin
├── System Volume Information
│ ├── IndexerVolumeGuid
│ └── WPSettings.dat
├── USER1_XKOS
│ └── payload.bin
├── USER2
├── USER3
└── readme.txt
I'm not sure what to do with the "payloads" folder from the files I got from SDSetup, to get into Hekate, so I can build a new emuMMC. Or even if that's what I need to do.
Any help is appreciated.
Like I said, posting that hekate_ipl.ini file will help more than you realize.
Oh sorry, wow, didn't realize I had that file. Was mostly trying not to waste more of your time here, was why I reposted:
Code:
[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=3
updater2p=0
[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp
[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp
[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1
[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin
Last edited by steamcheapcom,
does hekate creates different subfolders per backup on the same device or something like that?
like:
sdroot\backup\111111Backup1
sdroot\backup\222222Backup2
im asking because i wanted flash back a nandbackup but the subfolder in the backupfolder is named differently.
like:
sdroot\backup\111111Backup1
sdroot\backup\222222Backup2
im asking because i wanted flash back a nandbackup but the subfolder in the backupfolder is named differently.
Its fine, I don't think of it as a waste of time. Anyways, it seems that you mainly launch Hekate via package3 so you don't use fusee. When you plug in your RCM Loader, does it launch Hekate on your Switch? If so, what option do you use to launch CFW normally?
Interesting, I've never tried making more than one backup at a time although this would allow handling them appropriately. Also I don't know if you made up those number-folder names yourself or Hekate did since normally Hekate names them after your console's device ID. Either way, those backups should be fine and if you're confused on which is which, you can always look at the date they were created.
When I use the RCM Loader it shows the Atmosphere splash screen so I assume it's loading Atmosphere, but I never see Hekate.
I can't remember, in the past, whether I went through Hekate. I *think* I did, but I used to inject via a USB cable from my PC and I lost the original payload, and now I have also wiped out the SD card that had my emuMMC. So I'm just trying to start over.
Basically everything on the RCM Loader is the original files that were on there when I ordered it from eBay or something. And everything on the SD card is (only) what I got from SDSetup last night, in the "sd" folder of what they gave me, which I copied to the root of the SD card. So everything is untouched from either SDSetup or the factory RCM Loader.
Essentially I was trying to start fresh by following this guide https://switch.homebrew.guide/hacking/fuseegelee/sdsetup. At the bottom it says, "you are technically done... you can enter Hekate..." but I can't get into Hekate. The "payloads" folder of what I got from SDSetup contains hekate_ctcaer_5.7.0.bin and Lockpick_RCM.bin. I'm wondering if I'm supposed to do something with that hekate file, but really no idea.
I don't know anything about the backups tbh, that data actually came from SDSetup.
Last edited by steamcheapcom,
If that's the case, then I believe the payload that you're RCM Loader is launching is fusee instead of Hekate. You will have to flash Hekate onto your RCM Loader and replace the payload it is using to launch Atmosphere. I assume you know how to do that so here is a link to the latest release of Hekate.
seems youre bumping into a lot of file system related issues (Hopefully not corruption). Mind if I take a step back and ask why you’re attempting to restore? Trying to piece together the crime scene to make sure I’m not making things worse.
Unfortunately, I've never used an RCM Loader before. However, they have a website with instructions that you can follow. To summarize the steps listed on their page, it seems that you have to connect the RCM Loader to your computer then replace the corresponding payload. You're going to be replacing the one inside the Atmosphere folder. And make sure that the new payload is named payload.bin
I use one and you’re spot on @Draxzelex. All the payload.bin files are just renamed copies of a fusee.bin or a Hekate.bin, etc. Etc.
The only thing to be wary of is there are multiple payloads and they are color coded. You press the plus button to cycle through them. On mine the first one is Royal Blue. @steamcheapcom will need to confirm the color code or he’ll be replacing the wrong one (or heck…replace them all with the same thing and you can’t guess wrong)
correct. For the most part you will find yourself confirming what you’ve done before so “ignore” might be too harsh a word.
I recommend making an emunand (which would be a literal 30Gig copy of your sysnand.)
The reason for this is you can then use your “clean” sysnand to go online and do anything questionable in your offline emunand.
This keeps you from getting banned and also means that if you soft-brick your emunand you can easily recover.
running everything on Sysnand means you’re running dirty and can have traces of crashes, tickets, etc reported back to Ninty and anything that hooks up in your Sysnand will require a restore from backup to recover.
Hello. IPatched Switch owner here (13.1.0 AMS) . I normally get into Hekate by selecting Kosmos Toolbox from the Album app. I do this every time I need to get the SD Card out, for instance. The issue is that choosing Kosmos Toolbox from the menu now gives me a black screen each time I try it (which I can exit out of).
I appear to be unable to get into Hekate to take out the SD Card, which I do every once in a while to install new mods. Are there any safe fixes to the problem?
I appear to be unable to get into Hekate to take out the SD Card, which I do every once in a while to install new mods. Are there any safe fixes to the problem?
Did you recently upgrade and if so, did you update your Sigpatches?
https://github.com/ITotalJustice/patches
I'm on 13.1.0, which I think means I haven't updated for a while? Should I do that in AIO Switch Updater?
My games still work, or is this still a possible explanation for the issue?
