That's exactly the description I was confused about, but it seems to replace "reboot_payload.bin" so I think that answers my question, without that setting rebooting to payload doesn't get me back to Hekate from Atmos.
That's exactly the description I was confused about, but it seems to replace "reboot_payload.bin" so I think that answers my question, without that setting rebooting to payload doesn't get me back to Hekate from Atmos.
That just seems like you reboot_to_payload.bin file is not Hekate. Vanilla Atmosphere certainly doesn't give you that nor does certain packages that don't bundle Hekate (which is becoming more common due to DZ).
No I don't think it was, it was whatever comes with vanilla Atmosphere as it comes with reboot_to_payload.bin,
I'm guessing it requires a USB connection for the payload which I didn't have attached, hence the black screen.
Yes because as I just said, vanilla Atmosphere doesn't bundle Hekate so it would make sense that their reboot_to_payload.bin file won't be Hekate either. If you want it to be Hekate, just download the latest Hekate and rename it as such then place it in the appropriate folder.
Ok, and also if anyone sets that updater2p=1 then no files need replacing, it just does it automatically
That or you when you need to update Atmosphere, you download a package of Hekate and Atmosphere that already has the reboot_to_payload.bin file set as Hekate. I personally use SDSetup as it lets me avoid the bloatware that is associated with other bundles by letting me pick and choose exactly what software I want.Ok, and also if anyone sets that updater2p=1 then no files need replacing, it just does it automatically
Sounds good, I run pretty vanilla from github directly: atmosphere, hekate, patches, lockpick rcm, awoo installer, jksv, linkalho.
Thanks!
Does anyone know why games installed on SD Card need to be re-installed when Switch is re-initialized?
I'm guessing there's some temporary key created that now doesn't match with installed content?
I'm guessing there's some temporary key created that now doesn't match with installed content?
When a game is installed, a ticket is created and stored in the internal memory. Re-initializing the system wipes most of the internal data including these tickets.
Gotcha, and without re-installation I guess it's next to impossible to restore these tickets ...
Uh I think some title installers support dumping and installing just tickets but its considered more of a niche feature so I don't know how well it works.Gotcha, and without re-installation I guess it's next to impossible to restore these tickets ...
Silly question, but wondering if someone has ever run into a problem when installing multiple
games and updates at the same time. What I mean is does the installer know that a game should
be installed before an update is installed, or does that simply not matter anyways ?
games and updates at the same time. What I mean is does the installer know that a game should
be installed before an update is installed, or does that simply not matter anyways ?
So while that situation isn't likely in real life, its actually not that big of an issue to have updates installed before games. When you're installing them simultaneously for example, the end result will be the game with the update so the order doesn't matter. What can cause an issue is installing the update before the game then trying to launch the game because installing the update will create an icon for a game that you have not installed.
tl;dr If you install both the update and game then the order won't matter because the end product will be the same.
Ok thanks, I just wasn't sure if the update actually overwrites some game files, like on Windows systems for example,
or if they simply go into completely different folders.
Hey guys, just posting this to ask some help. Here's the situation that I'm in
- I own an unhacked Switch v2 and want to have a clean sysnand + piracy emunand setup
- I don't have an sx core as well as soldering skills but have experience in hacking one
- I paid a shop with an sx core to ONLY solder it for me WITHOUT hacking it
- Much to my dismay, the guy applies atmosphere on it anyway, I got even more annoyed that he didn't even bother setting up an emunand NOR did he make a backup so he ran atmosphere on sysnand.
- As to what he did, he just ticked the homebrew menu via gallery without doing anything else, probably for testing purposes
Is my sysnand considered dirty now for online use? Would defintely appreciate a fast response since I'm planning what to do from here on out depending on what you guys think.
- I own an unhacked Switch v2 and want to have a clean sysnand + piracy emunand setup
- I don't have an sx core as well as soldering skills but have experience in hacking one
- I paid a shop with an sx core to ONLY solder it for me WITHOUT hacking it
- Much to my dismay, the guy applies atmosphere on it anyway, I got even more annoyed that he didn't even bother setting up an emunand NOR did he make a backup so he ran atmosphere on sysnand.
- As to what he did, he just ticked the homebrew menu via gallery without doing anything else, probably for testing purposes
Is my sysnand considered dirty now for online use? Would defintely appreciate a fast response since I'm planning what to do from here on out depending on what you guys think.
Yes its considered dirty, and there is no saying if you will be banned or not, however, if it was only testing the HBmenu, you might be fine, I would still make a backup and create and emunand for your hacked side of it. and then just play syscfw as normal
dont forget to backup your boot files, additionally any firmware upgrades should only be done officially or via daybreak
Do not. If it went online and then you go online with cleared logs and stuff, then you will definitely get banned.
You are better off risking it
Just yeah make your backup of boot0/1 and rawnand, make your emunand and use emu for your hack stuff and hope you dont get banned
- No one is chatting at the moment.
