After downloading everything, how do i install it? What app works for that? Sorry for the noob question
You don't install homebrew, just place the nro on the switch folder of your sd card.
After downloading everything, how do i install it? What app works for that? Sorry for the noob question
eh, I'm not going to fight SciresM, he's kinda right about updating hygiene. Your solution could work though, I'd have to decide what I want to do.@Homlet as you can see here https://github.com/Atmosphere-NX/Atmosphere/commit/5b02c77400e8551199fefdbc36b1eb3ff86374dc
Upcoming atmosphere release will maintain an open reference to core atmosphere files so online updating in HOS wouldn't be possible anymore. You'll have to think about a new solution f.e. you could write a little rcm payload that will unpack or rename the files previously downloaded and then reboot to atmos/hekate/previously selected cfw payload. The update flow will be something like this: Download/unpack new files to a temp folder -> ask users to which payload reboot after the update -> reboot to your payload, rename/unpack the files and then chainload the previously selected payload to reboot cfw.
Sigh... yeah because everyone loves ejecting their SD Card to update...@Homlet as you can see here https://github.com/Atmosphere-NX/Atmosphere/commit/5b02c77400e8551199fefdbc36b1eb3ff86374dc
Upcoming atmosphere release will maintain an open reference to core atmosphere files so online updating in HOS wouldn't be possible anymore. You'll have to think about a new solution f.e. you could write a little rcm payload that will unpack or rename the files previously downloaded and then reboot to atmos/hekate/previously selected cfw payload. The update flow will be something like this: Download/unpack new files to a temp folder -> ask users to which payload reboot after the update -> reboot to your payload, rename/unpack the files and then chainload the previously selected payload to reboot cfw.
I love it! But I'd love AMS OTA updatesSigh... yeah because everyone loves ejecting their SD Card to update...
Doing USB file transfers with Hekate is probably gonna be the way to go.Sigh... yeah because everyone loves ejecting their SD Card to update...
Yeah... because getting a script to run in Sept to unzip like a update file sounds terrible I guess.Doing USB file transfers with Hekate is probably gonna be the way to go.
Why do you find it necessary to talk down to people like a dick?Yeah... because getting a script to run in Sept to unzip like a update file sounds terrible I guess.
Well I got my reasons I guess? But you are talking about the same people that add a timer for the splashscreen for no reason. The only problem I had with atmosphere have been when they add new mechanics where you more or less need to delete your atmosphere folder from the sd card anyway. So yet to see the big reason why a "auto-update" would be a issue honestly if you reboot right away.Why do you find it necessary to talk down to people like a dick?
The suggestions being made are for the homlet to decide if there a good idea or not.
Not for others to criticise.
If you're talking about the solution I suggested isn't so terrible and probably the only way from 0.15+. Also sept isn't needed at all because for extracting/moving files from SD sept's keys aren't necessary. A simple/stripped down automatic version of tegraexplorer rcm payload is more than enough. I had preferred that atmosphere's devs implemented a way to perform online in HOS updates safely instead of simply blocking them tho but this is what we got. Atmosphere is a great ever evolving cfw thanks to the same devs and we must only thanks them for all the efforts they put in a free project together with all the homebrews developers.Yeah... because getting a script to run in Sept to unzip like a update file sounds terrible I guess.
Yeah I had to change the way the app updated sometimes back. If you run v1.2.7 it will clean up everything, or you can just ease aio-switch-updater.nro@Homlet I just updated from 1.1.3 to 1.2.7 from within your app.
The update was placed in the correct folder
But its named aio-switch-updater-v1.2.7.nro
The 1.1.3 version is called
aio-switch-updater.nro
So the update didn't overwrite the original due to it containing the update revision in the file name.
Is this normal as in it won't overwrite with the nro being active anyway
Or is it a mistake and it should overwrite without needing to edit the file name on pc or a file browser
I sorted it i just wanted to check it was known.Yeah I had to change the way the app updated sometimes back. If you run v1.2.7 it will clean up everything, or you can just ease aio-switch-updater.nro
Sorry about that, I wish I had a cleaner way to do it (and truth be told since then I've thought of one) but if you do this thing now it shouldn't be an issue
Yeah, it's in Tools->reboot to payload, and then you either press X or Y (look at the hints at the bottom)I sorted it i just wanted to check it was known.
While your online
In v1.2.1 you added the option to set a payload to /bootloader/update.bin
Now I'm in 1.2.7 (I skipped from 1.1.3) and I have gone through the app and I can only see in tools
Download payloads to/bootloader/payloads and in there the 3 .bin files download as there called
not update.bin or give the option to put it in /bootloader
Where can I find the option
Ahh I see it cheers.Yeah, it's in Tools->reboot to payload, and then you either press X or Y (look at the hints at the bottom)
It does update. it has the function in builtCan an updater be added to this so that it can update the application itself to future versions?
Sent from my Samsung Galaxy Note10+ 5G SM-N976U using Tapatalk