Homebrew Question Unable to update firmware via AIO Updater

[OptimisticPessim]

Hi, I'm trying to update the firmware for my Switch SX OS Lite and the error that pops up says "Because of the size of the FW archive, downloading firmwares in Applet Mode is not supported. Please launch the app with full RAM access"

How do I do this?

 

[M7L7NK7]

Hold R when opening a game

 

[OptimisticPessim]

Thank you. I sincerely apologise for being such a noob. But I have new issues.

I downloaded the firmware and now Daybreak keeps saying I need Atmosphere 0.14 and above.

Even though I've already downloaded and overwritten my Atmosphere files with the latest update which is Atmosphère 0.19.5... Trying to install Atmosphere update via AIO Updater 2.11.3 tells me that I have rename a payload.bin?

Please help... I've even downloaded all the sigpatches (fusee and hekate) and what-not separately and replaced all of them in their separate folders.

Can I install the firmware using ChoiDujourNX? Is it safe to install firmware 12.1.0 on my hard mod SX OS?

Do I have to boot into OFW to manually update to 12.1.0 before I can update the CFW?

Sorry I have so many questions...

 

[Hayato213]

Don't use ChoidujourNX if you are on SX Core, it will brick your boot0 if you have patched unit or Mariko, and your system won't boot if you use it on Sysnand, use Daybreak instead.

 

[OptimisticPessim]

Don't use ChoidujourNX if you are on SX Core, it will brick your boot0 if you have patched unit or Mariko, and your system won't boot if you use it on Sysnand, use Daybreak instead.

Daybreak keeps telling me I need Atmosphere 0.14 and above though. I've downloaded the latest files and dragged them to the root folder. But for some reason, it's not registering the update.

 

[Hayato213]

Daybreak keeps telling me I need Atmosphere 0.14 and above though. I've downloaded the latest files and dragged them to the root folder. But for some reason, it's not registering the update.

Update your Atmosphere file manually if AIO doesn't work for you.

 

[OptimisticPessim]

I've already extracted the files and placed them into the root folder. Is there something else I need to do?

I attached the 4 images via imgur below..

 

[Hayato213]

Perhaps someone with a SX Lite can help, I don't own a SX lite, only V1 Unpatched. Also it looks like your Atmosphere files aren't up to date.

 

[OptimisticPessim]

Perhaps someone with a SX Lite can help, I don't own a SX lite, only V1 Unpatched. Also it looks like your Atmosphere files aren't up to date.

That's really odd... Cause I updated the Atmosphere with the download from https://github.com/Atmosphere-NX/Atmosphere/releases

 

[Hayato213]

That's really odd... Cause I updated the Atmosphere with the download from https://github.com/Atmosphere-NX/Atmosphere/releases

Yea, that is what is recommended, Also AIO cause problem in general, so don't recommend that.

 

[OptimisticPessim]

I checked my Tinfoil and it has the option to boot into Atmosphere (sysnand). Can I update the CFW there and will it carry over to SX OS Lite?

 

[Homlet]

I've already extracted the files and placed them into the root folder. Is there something else I need to do?

I attached the 4 images via imgur below..

You're booting SXOS, you can't update Atmopshere with daybreak while using SXOS. You need to boot through Atmopshère. Same goes with updating Atmosphere with aio-switch-updater, it only works if you have a working Atmosphere setup

Yea, that is what is recommended, Also AIO cause problem in general, so don't recommend that.

I know I've asked before and I know your stance on my app, but can you please not tell people such broad statements such as "AIO causes problems"? The problem here isn't with the app, it's with the user playing sorcerer's apprentice, trying to upgrade firmware and launch Atmosphere from the SXCore without having researched anything prior to that.

 

[Hayato213]

You're booting SXOS, you can't update Atmopshere with daybreak while using SXOS. You need to boot through Atmopshère. Same goes with updating Atmosphere with aio-switch-updater, it only works if you have a working Atmosphere setup


I know I've asked before and I know your stance on my app, but can you please not tell people such broad statements such as "AIO causes problems"? The problem here isn't with the app, it's with the user playing sorcerer's apprentice, trying to upgrade firmware and launch Atmosphere from the SXCore without having researched anything prior to that.

I am correct about that updating via AIO cause problems especially with Atmosphere, I mean I ain't the only one who couldn't get Atmosphere to update properly with your app. I know it isn't fault, but if I was going to recommend way people to update I would just suggest doing manually via Hekate USB mounting option.

 

[Homlet]

I am correct about that updating via AIO cause problems especially with Atmosphere, I mean I ain't the only one who couldn't get Atmosphere to update properly with your app. I know it isn't fault, but if I was going to recommend way people to update I would just suggest doing manually via Hekate USB mounting option.

If it does, then I would appreciate any issue on the github page or even my thread, but for that particular case, it's obviously not my updater's fault so I don't see why it's relevant to mention it.

 

[Hayato213]

If it does, then I would appreciate any issue on the github page or even my thread, but for that particular case, it's obviously not my updater's fault so I don't see why it's relevant to mention it.

Im not saying it is a problem with your program just the way atmosphere update file via the AIO updater, until you can get it to work 100% Im sticking with my stance on it, I tried TotalJustice's Atmosphere updater in the past and it work 100% of the time, but due to SciresM request that why it was pulled, perhaps you should really figure out what up with your AIO updater, I mean look at your AIO updater thread, there is more than one person who couldn't get their switch to boot after updating via your AIO updater.

 

[Homlet]

Im not saying it is a problem with your program just the way atmosphere update file via the AIO updater, until you can get it to work 100% Im sticking with my stance on it, I tried TotalJustice's Atmosphere updater in the past and it work 100% of the time, but due to SciresM request that why it was pulled, perhaps you should really figure out what up with your AIO updater, I mean look at your AIO updater thread, there is more than one person who couldn't get their switch to boot after updating via your AIO updater.

True, there were issues, a lot of them are user errors too. One error I fixed somewhat recently that would botch updates for users updating from a low cfw. Now I do believe it's working 100%, but if it's not I'd like for people to tell me the error they encounter instead of people telling others who don't even have a problem with it in the first place that my app doesn't work.
Again, he posted screenshots of the SXOS homebrew menu and daybreak saying you need atmosphere to run it. How can it be related to my app? Not only you're blaming my app for no reason, you're steering him in the wrong direction. He can update Atmosphere manually as much as he wants, as long as he's not actually booting Atmosphere he won't be able to use Daybreak.

 

[OptimisticPessim]

Thank you everyone for helping me out. I managed to find someone to help me with the migration~ Really appreciate the time you guys have all taken to help a noob out~