@Homlet Everytime I update hekate manually, I also put the payload into the atmosphere folder overwriting reboot_payload.bin so Atmosphère's reboot feature reboots to hekate.
Is this possible somehow with your (apart from that, amazing) tool?
Also why isn't this in the appstore? Bugs be everytime I set up a Switch for a friend that I have to get this manually.
You used to be able to replace the reboot_payload.bin but seems like the feature is gone now
Cool, will try it for the first time ever then, to not manually update everything but to use your tool for that.If you go in Tools->inject payload, you can set any payload to reboot_payload.bin by pressing X. As for the appstore, I just haven't gotten around to do it, I should though
Edit : nvm, forgot my switchbru account details and they removed my sigpatches updater anyways, so it's not going on there
I've done it a few times, it should work! And no hard feeling regarding the hbstore, sigpatches are somewhat of a touchy subject
Pretty much yesWill this truly awesome AIO-tool be able to update FW from 9.1.0 to the most updated version, in one go?
Many thanks for putting this together!
Pretty much yes
Download the latest Atmosphere first (Hekate too if you use it), then download the latest firmware and use Daybreak to upgrade
You can download fusee-primary directly to /bootloader/ payloads and copy any payload to reboot_payload.bin and update.bin. For the rest, I suggest you use a file explorer like nx-shell. It'll be easier to use and that way you don't need a computer for thatI haven't taken a good look at this app yet, but it sounds like really great work and very useful. Happy to see the latest update lets you preserve specific files when updating. The one other thing I can think of that would help automate my own steps when updating atmosphere would be to be able to copy fusee-primary.bin to a few specified file paths (I have one copy in hekate's bootloader/payloads directory, plus one in argon-nx's directory for autoboot and one in its payloads subdirectory).
I understand this is pretty specific to me, but I saw someone ask a vaguely similar thing earlier in the thread re: modchips, so maybe you could make the app read a text config file of files to be copied from (source path) to (destination path)? It might provide a way for your app to be configurable to every user's weird specific needs, without making more and more weird specific changes. If you don't want to tho, no worries, doing those steps manually wouldn't be the worst thing.
Very nice!Added the ability to preserve specific files when updating.
In fact that's a use case for me as well. Or at least something close to that.I haven't taken a good look at this app yet, but it sounds like really great work and very useful. Happy to see the latest update lets you preserve specific files when updating. The one other thing I can think of that would help automate my own steps when updating atmosphere would be to be able to copy fusee-primary.bin to a few specified file paths (I have one copy in hekate's bootloader/payloads directory, plus one in argon-nx's directory for autoboot and one in its payloads subdirectory).
I understand this is pretty specific to me, but I saw someone ask a vaguely similar thing earlier in the thread re: modchips, so maybe you could make the app read a text config file of files to be copied from (source path) to (destination path)? It might provide a way for your app to be configurable to every user's weird specific needs, without making more and more weird specific changes. If you don't want to tho, no worries, doing those steps manually wouldn't be the worst thing.
To make this whole process a little more complete managable by only your app (+Daylight) you could also implement a feature toPretty much yes
Download the latest Atmosphere first (Hekate too if you use it), then download the latest firmware and use Daybreak to upgrade
No, it shouldn't be happening, probably a problem with your internet tbh. Did you manage to fix it?My atmosphere download is stuck at 3% for quite some time now, is that normal?
I also tried downloading the experimental version but that one stops downloading as well.
I'll think about. A bit out of scope though, especially since the app doesn't actually update the FW.To make this whole process a little more complete managable by only your app (+Daylight) you could also implement a feature to
This can be done from within the nxthemes app technically but yeah, since you already implemented many cool features from other apps this might be of interest for you as well since updating the FW without removing the current theme makes the CFW unbootable unless the folders are being manually removed from the SD card.
- backup and remove current homescreen theme
and- restore it after the firmware update
At least you should be fine if you put Atmosphère and hekate on your SD manually?Used AiO updater for the first time today... my CFW won't boot anymore
I had emuMMC 10.0.2 with AMS 14.4 and hekate 5.5.1 working fine. I downloaded firmware 11.0.1 first (without updating yet) then I updated sigpatch then atmosphere to 16.2 and finally Hekate to 5.5.1 (because I think Hekate must be updated after atmosphere) I always answered no to overwrite .ini's files. Then I was prompted to reboot to a specific payload which I did...and then the Hekate's splashscreen showed up and I can't get anything else now.
I tried deleting Atmosphere, bootloader, config and firmware and making fresh copy of atmosphere and hekate from windows but I still get stuck at Hekate's splash screen and can't access Nyx.
Also I noticed an update.bin file is created on my microSD when I try booting the switch.
Any help ?