My bad, how about the other question?Can't asks that here, read the rules.
My bad, how about the other question?Can't asks that here, read the rules.
My bad, how about the other question?

Weird, so someone (or you) deliberately swapped the update.bin with the fusee.bin or something? Since it boots into sysNAND CFW? And not into Hekate?whenever I did the reboot to bootloader/update.bin it would lead me in to sys cfw
Yep, I definitely don't know what's going on your Switch.so what I did after clicking on it I pressed volume down & it led me back into hakate
I've already posted here, just make sure to adjust where necessary.so can you guide me on the format thing
Only if you've already made a at least one NAND backup.I tried haku33 but it didn't work, should I just go with the normal format
I would make a NAND backup right now and attempt the usual factory reset and, if it works, great. If not, restore the old backup and do not attempt to factory reset.I did remove all the apps that were installed on it deleted the old user & created a new one, should I just do the regular format that is in the settings?
I guess you need to update your Lockpick_RCM and dump the up-to-date ones?& Also what's with the keydump error thing when it load into tegraexplorer? Did I do something wrong with the console that it gives me that message or is it just a regular message that pops up on that menu?
Can't say for sure, it could be that you've swapped some of the payloads around. For example, I use the Reboot to Payload app on my Switch to reboot into hekate's payload instead of usual Atmosphere payload i.e. I just renamed hekate*.bin to reboot_payload.bin and removed the old one. Something similar must have been done to your Switch as well.& Why is it booting into that menu instead of directly booting into hekate? Is it because something got messed up on the sd card?
Thanks for the info.You can but mod doesn't really work for online play, just going to get you banned for using it online, you are fine to use it offline, as for your other question there is a paid shop for tinfoil, as for XCI/NSP google is your friend use that.

Can you post your hekate_ipl.ini? It could be outdated and still using fusee-secondary.bin or something which has been deprecated for a while.Still a yellow screen when loading the emu mmc.
If stock still boots, then you could try to recreate your emuMMC.@Blythe93
So it sounds like I updated the firmware in the emu mmc, and that’s why my system still shows 10.0.4, right?
I followed the guide you linked. Still a yellow screen when loading the emu mmc. Ofw and cfw on the sys will load up just fine. It’s only the emu nand that gives the yellow screen. The only thing I can think is maybe my card needs reformatted because something is corrupted and just start completely fresh. Would that be my next step? If it’s not that, I’m completely lost.
/Nintendo folder into /emuMMC/RAW1, so you have /emuMMC/RAW1/Nintendo.Is there any way to find if my Joy-Cons are genuine or fake without opening it ?
I already started the nuclear option a few days ago and am now just getting back to it and this post tonight. I reformatted and followed the NH guide, and I’m finally back into the emu mmc. I’ll remember this thread if I ever start having that issue again. I gave up all the saves I ever had, but eh, I’m not worried about them. I wasn’t in the middle of anything.
I’m back on 1.8.0. Will that be sufficient for Prime 4 after updating the fw to 19.0.1 and using the sdk downgrade or whatever needs done?
It comes with the 20.3.0 firmware in the cartridge. So if you are on that version or higher, you should be ok with the version requirements. Also here is the info from the nsc_builder about it:
Titleinfo:
- Name: Metroid Prime 4: Beyond
- Editor: Nintendo
- Display Version: 1.0.0
- Meta SDK version: 20.5.0.0
- Program SDK version: 19.3.13.0
- Supported Languages: US (eng), UK (eng), JP, FR, DE, LAT (spa), SPA, IT, DU,
CAD (fr), KOR, TW (ch), CH
- Content type: Base Game or Application
- Version: 0 -> Application (0)
Required Firmware:
- Included Firmware: 20.3.0-80
- RequiredSystemVersion: 1275068416 -> (19.0.0)
- Encryption (keygeneration): 20 -> UNKNOWN
- Patchable to: 1275068416 -> (19.0.0)