Hacking Nintendo switch toggling between homebrew and online mode? Homebrew emulators..

[tom2199]

You don't have reinx files on your sd, that's why you can't launch it, just use atmosphere. I guess you're lacking sigpatches, just use both zips from here: https://gbatemp.net/threads/latest-fs-and-acid-patches-for-kosmos.562915/ and unzip them on your sd. It should work but if it not you can try awoo-installer as well, it works with ns_usbloader (set on tinfoil)

 

[jimlaman8]

You don't have reinx files on your sd, that's why you can't launch it, just use atmosphere. I guess you're lacking sigpatches, just use both zips from here: https://gbatemp.net/threads/latest-fs-and-acid-patches-for-kosmos.562915/ and unzip them on your sd. It should work but if it not you can try awoo-installer as well, it works with ns_usbloader (set on tinfoil)

Thanks for the tip, yeah i hadnt added sigpatches, wasnt aware of them, though this topic looks like a whole other area to understand. On that link there is the homebrew sd setup wizard, i assume that just generates a structure of files for various options, something separate, though looks useful.

I do have the Reinx files on the sd card, at this point i can get it to go to the splash screen, but the splash screen sticks. I thought maybe there was an advantage over atmosphere but ill stick with atmos.

For now i've been payloading atmos from the pc, i cant seem to get atmoshere to launch from the rcmloader device (i select the blue icon), each time it splashes with atmosphere briefly then boots up into ofw instead, perhaps a file/folder is wrong on the rcmloader in some way. EDIT: i did fix it, copied over the hekate_ctcaer_5.2.0.bin to the rcmloader and renamed payload.bin (the one there wasnt right i guess), though this takes it to the hekate menu, from which i can launch atmosphere (is there a more direct way to get to atmosphere, i assume a different bin in there would do it, ie: from the actual atmos dl the fusee-primary.bin, though that might have been the "bad" payload.bin i had put originally)

I have not upgraded the switch to firmware 10.0 yet, i assumed maybe i should wait till i have all this fully working and try to firmware update it.

 

[tom2199]

Thanks for the tip, yeah i hadnt added sigpatches, wasnt aware of them, though this topic looks like a whole other area to understand. On that link there is the homebrew sd setup wizard, i assume that just generates a structure of files for various options, something separate, though looks useful.

I do have the Reinx files on the sd card, at this point i can get it to go to the splash screen, but the splash screen sticks. I thought maybe there was an advantage over atmosphere but ill stick with atmos.

For now i've been payloading atmos from the pc, i cant seem to get atmoshere to launch from the rcmloader device (i select the blue icon), each time it splashes with atmosphere briefly then boots up into ofw instead, perhaps a file/folder is wrong on the rcmloader in some way. EDIT: i did fix it, copied over the hekate_ctcaer_5.2.0.bin to the rcmloader and renamed payload.bin (the one there wasnt right i guess), though this takes it to the hekate menu, from which i can launch atmosphere (is there a more direct way to get to atmosphere, i assume a different bin in there would do it, ie: from the actual atmos dl the fusee-primary.bin, though that might have been the "bad" payload.bin i had put originally)

I have not upgraded the switch to firmware 10.0 yet, i assumed maybe i should wait till i have all this fully working and try to firmware update it.

You can select autoboot in hekate, it's in the settings, so when it starts it automatically selects one of your options. If everything works, you can update with choidjournx https://switchtools.sshnuke.net you can find the firmware files on a website called Darthsternie's Firmware Archive (I'm not sure I'm allowed to link it here) just unzip the file to a folder on the sd card and select the update within choidjournx

 

[jimlaman8]

You can select autoboot in hekate, it's in the settings, so when it starts it automatically selects one of your options. If everything works, you can update with choidjournx https://switchtools.sshnuke.net you can find the firmware files on a website called Darthsternie's Firmware Archive (I'm not sure I'm allowed to link it here) just unzip the file to a folder on the sd card and select the update within choidjournx

Ah yes i think i saw that option in there. Thanks for the tips along the way

Are you saying i shouldnt just boot to ofw mode, update firmware there, and then resend the payload, but rather use the choid method? Guessing there is an "advantage" to that.

Ill check the other out. I did succeed so far after those patch files added (or maybe because i used goldleaf on the switch and browsed to do the install from there instead of selecting on pc, will retry via pc but i think its working). It would be nice to remotely control the switch from a pc for this process, betting there is a way. Also think i should have partitioned it to allow for an android setup, intrigued by that, maybe i can use a partition tool on the pc to resize things later if i decide to try that.

 

[tom2199]

Ah yes i think i saw that option in there. Thanks for the tips along the way

Are you saying i shouldnt just boot to ofw mode, update firmware there, and then resend the payload, but rather use the choid method?

Ill check the other out. I did succeed so far after those patch files added (or maybe because i used goldleaf on the switch and browsed to do the install from there instead of selecting on pc, will retry via pc but i think its working). It would be nice to remotely control the switch from a pc for this process, betting there is a way. Also think i should have partitioned it to allow for an android setup, intrigued by that, maybe i can use a partition tool on the pc to resize things later if i decide to try that.

No just update your EmuNAND (if you want, I think there's no game right now that requires 10.0.x) with Choi, ofw can be updated over the air as usual.
I think awoo-installer has the option to do batch installs, not exactly what you're looking for but it makes the process of installing many files easier.

 

[jimlaman8]

No just update your EmuNAND (if you want, I think there's no game right now that requires 10.0.x) with Choi, ofw can be updated over the air as usual.
I think awoo-installer has the option to do batch installs, not exactly what you're looking for but it makes the process of installing many files easier.

What did you mean by update the emuNand? You mean put the latest files on the sd card/loader mechanism from the pc side? I did put all the latest versions of everything so in that regard i think im good.

I guess i just boot to ofw and update it (i only thought i should because i thought it said they addressed some joy con hardware issues or similar, but aside from that no real reason too yet)

 

[tom2199]

What did you mean by update the emuNand? You mean put the latest files on the sd card/loader mechanism from the pc side? I did put all the latest versions of everything so in that regard i think im good.

I guess i just boot to ofw and update it (i only thought i should because i thought it said they addressed some joy con hardware issues or similar, but aside from that no real reason too yet)

If you followed the guide you created an Emunand (EmuMMC) for the cfw, so its an independent system thats stored on your sd card not on your switch. so if you update your ofw it doesn't update the emunand, you'll have to update the emunand manually with the hombrew choi because you dont want to connect your cfw with the internet, it will connect to nintendo servers and if you have nsps installed you will get banned so neither ofw nor cfw can play online anymore.

 

[jimlaman8]

If you followed the guide you created an Emunand (EmuMMC) for the cfw, so its an independent system thats stored on your sd card not on your switch. so if you update your ofw it doesn't update the emunand, you'll have to update the emunand manually with the hombrew choi because you dont want to connect your cfw with the internet, it will connect to nintendo servers and if you have nsps installed you will get banned so neither ofw nor cfw can play online anymore.

Yeah i had followed that guide, but it was my understanding that as long as i shutdown/reboot into ofw it was safe to buy the store bought titles online/do updates to those titles etc, but i think i see what your saying that if i did ofw update, then the emunand needs it as well, so i guess this isnt the case on being safe? In the guide it said the emuMMC method was safe for online use in ofw mode, as one of the pros, so a little confused now.

Or what is the way to get around that, ie: maybe a second sd card that is "clean" and fresh? I wonder because i see some talking of updating nsp's that are brew type but that doesnt seem safe at all obviously.

I also see talk of burnt 'fuses", but i'm not clear on what that means, i assume that is a software term.

 

[tom2199]

Yeah i had followed that guide, but it was my understanding that as long as i shutdown/reboot into ofw it was safe to buy the store bought titles online/do updates to those titles etc, but i think i see what your saying that if i did ofw update, then the emunand needs it as well, so i guess this isnt the case on being safe? Or what is the way to get around that, ie: maybe a second sd card that is "clean" and fresh? I wonder because i see some talking of updating nsp's that are brew type but that doesnt seem safe at all obviously.

it is safe as long as you use emunand, it's a copy of your internal 32gb switch memory on you sed card, so everything you do in cfw happens there. so the switch memory is not affected on ofw as that is running from internal memory. if you installed nsps already you can use your backup and restore it, if you didn't connect to the internet in the meantime

 

[jimlaman8]

it is safe as long as you use emunand, it's a copy of your internal 32gb switch memory on you sed card, so everything you do in cfw happens there. so the switch memory is not affected on ofw as that is running from internal memory. if you installed nsps already you can use your backup and restore it, if you didn't connect to the internet in the meantime

Ah so, if i hadnt tried installing an nsp i would have been fine to boot to ofw and be online, but because i tried that route and did an nsp now it has muddied the ofw waters so to speak? This stuff gets confusing too because there are what seem like 1000 ways of doing things and lots to digest. I also assume that any save data from an nsp is "dirty" at this point, so an original/store title shouldnt load those in online mode, ever.

 

[tom2199]

Ah so, if i hadnt tried installing an nsp i would have been fine to boot to ofw and be online, but because i tried that route and did an nsp now it has muddied the ofw waters so to speak? This stuff gets confusing too because there are what seem like 1000 ways of doing things and lots to digest. I also assume that any save data from an nsp is "dirty" at this point, so an original/store title shouldnt load those in online mode, ever.

It is confusing, that's why i'm recommend to read the guide several times to be sure. You are almost there! Just need to restore your backup and create an emunand. The idea is to play games you own legally on sysnand (ofw), you can go online with it as well since it is 100% original and not altered in any way (if youre not installing nsps on there) But for installing nsps there is emunand, the idea is to not let it connect to nintendo servers so you can do all the fun stuff there, but not online play etc. all that is done to prevent nintendo from finding out you're tampering with your switch and banning you from their services.

 

[jimlaman8]

It is confusing, that's why i'm recommend to read the guide several times to be sure. You are almost there! Just need to restore your backup and create an emunand. The idea is to play games you own legally on sysnand (ofw), you can go online with it as well since it is 100% original and not altered in any way (if youre not installing nsps on there) But for installing nsps there is emunand, the idea is to not let it connect to nintendo servers so you can do all the fun stuff there, but not online play etc. all that is done to prevent nintendo from finding out you're tampering with your switch and banning you from their services.

Haha getting there but now that confused me. I thought the guide I followed was creating the emunand (same as emuMmc)? or you are saying on another sd card to go online again with ofw, or, i should have done the emunand for installing those nsps? (i thought it was limited to only the 29gb or so out of the 400gb partition) I do need to reread

I also need to dig into how to turn wifi on with cfw and block nintendo, i guess through custom dns ip addreses of some kind? Or stealth mode (sx only?), unsure how the homebrew app store can work otherwise (to find the other emulators)

 

[tom2199]

Haha getting there but now that confused me. I thought the guide I followed was creating the emunand (same as emuMmc)? or you are saying on another sd card to go online again with ofw, or, i should have done the emunand for installing those nsps? (i thought it was limited to only the 29gb or so out of the 400gb partition) I do need to reread

I also need to dig into how to turn wifi on with cfw and block nintendo, i guess through custom dns ip addreses of some kind? Or stealth mode (sx only?), unsure how the homebrew app store can work otherwise (to find the other emulators)

Yes if you followed it you should have created an EmuNAND, you can check in system settings there should be an E together with atmosphere version in the system version dialogue. If you boot in sysnand and there are not any nsps you've installed you're fine. I recommend using another theme for both to see the difference. You can use 90dns and/or Incognito, I linked them both earlier in the thread. If you download retroarch there are almost all emulators bundled in there, so that's something for later down the line I would say

 

[jimlaman8]

Yes if you followed it you should have created an EmuNAND, you can check in system settings there should be an E together with atmosphere version in the system version dialogue. If you boot in sysnand and there are not any nsps you've installed you're fine. I recommend using another theme for both to see the difference. You can use 90dns and/or Incognito, I linked them both earlier in the thread. If you download retroarch there are almost all emulators bundled in there, so that's something for later down the line I would say

I just powered it off to go ofw, and in ofw mode the nsps do Not show up, so i guess, in theory, it might be ok to go online. If i ever update firmware i guess in ofw mode and do the other via cfw and that tool, for now ill leave it at 9.x i guess.

I cant launch my purchased titles in cfw mode, it throws an error, they do still work in ofw mode.

 

[jimlaman8]

It was mentioned that my hekate_ipl.ini should have a section like this:
[CFW EMUMMC]
emummcforce=1
payload=bootloader/payloads/fusee-primary.bin (because primary allows

Mine is slightly different, i have one cfw emummc and one cfw sysmmc along with stock sysmmc.

Mine has
[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bm

In payloads folder i have the lockpick file and fuse primary bin.

I tried putting the primary bin in the other folder and doing this, but it wouldnt load past the splash
fss0=bootloader/payloads/fusee-primary.bin

I'm also launching payload.bin from the dongle which is hekate_ctcaer_5.2.0.bin renamed payload.bin (i think this is correct).

When i view HW & cached fuses info (still unclear what the fuses are), i see burnt fuses (odm 7/6): 13 - 0
There is a note at the bottom that says "Your unit is exploitable to the rcm bug". Does this mean i've "burnt" 13 or none? Not sure what the bug is.

Im about to get 90dns configured and should finally be about wrapped, so long as all the above is normal/not to worry, and i can just reboot into official fw mode as needed and be online regular there (pretty sure deemed safe before).

 

[tom2199]

Mine has
[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bm

Just use that if it works for you, there is nothing wrong with using this method. If you want tucrun tinfoil (I guess that's why you're asking) then you need to use you first example with payload=...
fss0 just supports booting fusee-secondary, if you want to use primary you have to use payload or just put the payload (fusee-primary) on the rcmloader, that works too. Only disadvantage of that would be that you have to update the fusee-primary if you update Atmosphere, and I find it easier to update the payload on the sd card then on the rcmloader. But it's your choice, if fss0 is working for you I would use that, as I said there is nothing wrong with it whatsoever.

 

[jimlaman8]

Just use that if it works for you, there is nothing wrong with using this method. If you want tucrun tinfoil (I guess that's why you're asking) then you need to use you first example with payload=...
fss0 just supports booting fusee-secondary, if you want to use primary you have to use payload or just put the payload (fusee-primary) on the rcmloader, that works too. Only disadvantage of that would be that you have to update the fusee-primary if you update Atmosphere, and I find it easier to update the payload on the sd card then on the rcmloader. But it's your choice, if fss0 is working for you I would use that, as I said there is nothing wrong with it whatsoever.

Yeah it was mainly for tinfoil which i wanted to test out. I dont know why it wont work like that.
Whats confusing is there is the launch area, then payloads area. Payloads lists the lockpick and fuse primary, then under launch i have the 3 from the ini

Still confused on what cfw sysmmc is (custom firmware sysnand)? Or why i'd ever click that (maybe i should just remove from the ini).
I tried creating a 3rd ini entry for primary.. when launching from there it throws an error "error while loading fs0 wrong ini cfg or missing files.

I also thought i needed primary to do the R button hold to have title take over for things like retroarch (which seemed to crash for me once inside and clicking a menu choice via applet mode). Holding in R doesnt seem to do anything when launched as secondary

 

[tom2199]

The R thing should work regardless, and as I said, if you want to have payloads from the payload folder in your ini, you can do so, I will link a tutorial below. And yes you are right, CFW sysmmc is exactly what it says, you can remove it if you want some people use it so it's an option.

https://gbatemp.net/threads/how-to-hekate-chainload-vanilla-atmos.563255/ as you see you have to use payload= instead of fss0= if you want to use fusee-primary instead of fusee-secondary

 

[jimlaman8]

No just update your EmuNAND (if you want, I think there's no game right now that requires 10.0.x) with Choi, ofw can be updated over the air as usual.
I think awoo-installer has the option to do batch installs, not exactly what you're looking for but it makes the process of installing many files easier.

I gave awoo installer a shot, however, once it was done i found that it installed the titles in the eshop main SD Nintendo folder (i discovered because booting to ofw all the nsps were listed as if cfw).

I dont think thats standard, it should have put in the emuMMC / nintendo folder but didnt for some reason.
I guess the quick fix here is that i deleted the nintendo folder and brought back the initial nintendo folder before cfw (should be safe now), still unclear why it occurred.

edit:deleting the folder didnt help still shows in ofw as tiles at least

EDIT: rolled this into its own thread here but i suspect i accidentally booted the cfw - sysnand entry (i swear i had removed it from the ini), trying to figure out best course of action, sysnand was in offline mode, hoping i can just format (and not need restore nand)