Homebrew So many problems on my switch

  • Thread starter Thread starter UzealSmile
  • Start date Start date
  • Views Views 3,230
  • Replies Replies 34

UzealSmile

Member
Newcomer
Joined
Oct 2, 2021
Messages
21
Reaction score
3
Trophies
0
Age
20
XP
188
Country
United States
So i updated my atmosphere, my sig patches, hekate, and the firmware using the all in one switch updater. After I did that the sys-clk manager stopped working, tinfoil and legends arceus data got corrupted but it was saying "the microSD card is corrupted". My sd card is formatted to FAT32 so im not sure what that's all about. I tried to redownload the latest version of tinfoil by downloading the nsp on golden leaf but it's telling me it failed and that I should try updating sigpatches. All of these are making me so lost
 
So i updated my atmosphere, my sig patches, hekate, and the firmware using the all in one switch updater. After I did that the sys-clk manager stopped working, tinfoil and legends arceus data got corrupted but it was saying "the microSD card is corrupted". My sd card is formatted to FAT32 so im not sure what that's all about. I tried to redownload the latest version of tinfoil by downloading the nsp on golden leaf but it's telling me it failed and that I should try updating sigpatches. All of these are making me so lost
Don't use the AIO Updater; update your files manually.
 
So i updated my atmosphere, my sig patches, hekate, and the firmware using the all in one switch updater. After I did that the sys-clk manager stopped working, tinfoil and legends arceus data got corrupted but it was saying "the microSD card is corrupted". My sd card is formatted to FAT32 so im not sure what that's all about. I tried to redownload the latest version of tinfoil by downloading the nsp on golden leaf but it's telling me it failed and that I should try updating sigpatches. All of these are making me so lost
Try doing it manually

AIO updater sucks. 9/10 times it messes up something for me and I need to redo the process manually
 
Yep, no offence to the people who create or maintain these AIO updaters, but they create more problems than they solve. They should discontinue them and let the users update their Switch manually. If the users are not savvy enough to update manually, they probably shouldn't have hacked their console in the first place.
 
  • Love
Reactions: BaamAlex
Yep, no offence to the people who create or maintain these AIO updaters, but they create more problems than they solve. They should discontinue them and let the users update their Switch manually. If the users are not savvy enough to update manually, they probably shouldn't have hacked their console in the first place.
This exactly, I was testing the AIO updater for my Brother's Switch & the 3 times I've tried to use it either didn't work or completely messed something up. It's not hard to grab Atmosphere, Sigpatches, Hekate & Firmware to update with Daybreak.
 
  • Like
Reactions: Dust2dust
I dont understand why you would make aio updater a console app tbh. They should just make it a pc app. Plug sd card in (or mount from hekate), pc app would download the files and push them to sd card. There would be zero problems this way, but instead they insist on trying to update files while the cfw is running 🤷
 
  • Like
Reactions: platanos
I dont understand why you would make aio updater a console app tbh. They should just make it a pc app. Plug sd card in (or mount from hekate), pc app would download the files and push them to sd card. There would be zero problems this way, but instead they insist on trying to update files while the cfw is running 🤷
Because it's really not a good idea to keep taking your SD card in & out. I can't tell you how many damaged SD card readers I've seen on people's Switches.
After I put my 1TB in my OLED that is where it is staying forever.
 
Because it's really not a good idea to keep taking your SD card in & out. I can't tell you how many damaged SD card readers I've seen on people's Switches.
After I put my 1TB in my OLED that is where it is staying forever.

So true, I just got a scare when I reinsert my sdcard in my switch and get a boot.dat, luckily it gone away after I power off and reinsert the sdcard.
 
If anyone has issues with aio-switch-updater, it'd be nice if you could open an issue on github. Or at the very least, explain why "it doesn't work".
It simply extracts sigpatches, downloaded directly from the github repo everyone uses, to the root of your SD card. I agree that people should know how to update manually, which is why there is a disclaimer to learn how to do so when you first open the app, but it works at least as good as doing it manually. This is a tool to automate a repetitive process, and that allows you to update your system without a computer.
It seems to me that most of the criticism comes from people who don't understand how atmosphère operates (cf "insist on trying to update files while the cfw is running"), and others who just repeat what they heard. Again, if there is an actual issue I'd be more than happy to look into it and fix it.
 
  • Like
Reactions: bad361 and sley
Because it's really not a good idea to keep taking your SD card in & out. I can't tell you how many damaged SD card readers I've seen on people's Switches.
After I put my 1TB in my OLED that is where it is staying forever.
I have a day 1 switch and remove my SD card constantly and don’t have issues

How much force do you guys use to put these cards in lol
 
  • Like
Reactions: platanos
If anyone has issues with aio-switch-updater, it'd be nice if you could open an issue on github. Or at the very least, explain why "it doesn't work".
It simply extracts sigpatches, downloaded directly from the github repo everyone uses, to the root of your SD card. I agree that people should know how to update manually, which is why there is a disclaimer to learn how to do so when you first open the app, but it works at least as good as doing it manually. This is a tool to automate a repetitive process, and that allows you to update your system without a computer.
It seems to me that most of the criticism comes from people who don't understand how atmosphère operates (cf "insist on trying to update files while the cfw is running"), and others who just repeat what they heard. Again, if there is an actual issue I'd be more than happy to look into it and fix it.
I would always just get a generic atmosphere can’t find the package crash when using the updater

But doing a fresh CFW download of the latest version manually fixes the problem instantly allowing me to boot once more.
 
I would always just get a generic atmosphere can’t find the package crash when using the updater

But doing a fresh CFW download of the latest version manually fixes the problem instantly allowing me to boot once more.
Do you have a weird way of booting atmosphère, like chainloading fusée or something? Do you have hekate but don't use it to boot AMS? Do you have a patched switch?
 
Do you have a weird way of booting atmosphère, like chainloading fusée or something? Do you have hekate but don't use it to boot AMS? Do you have a patched switch?
My atmosphere auto boots from Hekate via a Trinket M0

This is a v1 switch
 
There you go, aio doesn't update your trinket payload because it has no idea where it is, or that you even have one. Now, aio *can* do it, and it's in the documentation, but the reason "9/10 time it doesn't work" is because you have a non standard setup and didn't configure aio for it.
That's exactly what I'm talking about, frankly it's frustrating that people who say that my app doesn't work just don't really understand their own system, and then others are parroting it. I know I sound upset, don't take it personally, but I think you can understand why it's annoying to read those posts
 
Last edited by Homlet,
  • Sad
Reactions: sley
There you go, aio doesn't update your trinket payload because it has no idea where it is, or that you even have one. Now, aio *can* do it, and it's the documentation, but the reason "9/10 time it doesn't work" is because you have a non standard setup and didn't configure aio for it.
That's exactly what I'm talking about, frankly it's frustrating that people who say that my app doesn't work just don't really understand their own system, and then others are parroting it. I know I sound upset, don't take it personally, but I think you can understand why it's annoying to read those posts
but your app is godtier
 
  • Like
Reactions: kidkat210
There you go, aio doesn't update your trinket payload because it has no idea where it is, or that you even have one. Now, aio *can* do it, and it's in the documentation, but the reason "9/10 time it doesn't work" is because you have a non standard setup and didn't configure aio for it.
That's exactly what I'm talking about, frankly it's frustrating that people who say that my app doesn't work just don't really understand their own system, and then others are parroting it. I know I sound upset, don't take it personally, but I think you can understand why it's annoying to read those posts
I don’t update the trinket payload either I just put the new firmware files on the SD card

The same thing the app attempts to do.
 
I don’t update the trinket payload either I just put the new firmware files on the SD card

The same thing the app attempts to do.
Then what, is your tinker payload a forwarder? Which payload is used to boot your switch into atmosphere?
Could also be (unlikely) that your trinket somehow interrupts aio's routine and inject its payload before aio can launch its own custom payload. Either way it is caused by your non-standard setup, and after 10 unsuccesful tries it would have been nicer to open an issue on github or post on gbatemp instead of saying "it sucks".
 
Then what, is your tinker payload a forwarder? Which payload is used to boot your switch into atmosphere?
Could also be (unlikely) that your trinket somehow interrupts aio's routine and inject its payload before aio can launch its own custom payload. Either way it is caused by your non-standard setup, and after 10 unsuccesful tries it would have been nicer to open an issue on github or post on gbatemp instead of saying "it sucks".

The payload on the trinket m0 is just an uf2 version of hekate, I don't see that is the problem, I must admit that your all in one software does really suck. Doesn't work for me either when I attempted to update atmosphere via your aio software.
 
The payload on the trinket m0 is just an uf2 version of hekate, I don't see that is the problem, I must admit that your all in one software does really suck. Doesn't work for me either when I attempted to update atmosphere via your aio software.
Alright, cool, but what payload does it chainload? Because from what I can read online, it chainloads a payload on your sd card (https://gbatemp.net/threads/interna...de-files-support.508068/page-178#post-9691512)
Trinket experts say:
>Really you have the options of either updating the uf2 format on the chip or the payload on the SD, as for the uf2 format to me it doesn't matter what version, as long there is one you can chainload another version of hekate.
Obviously my app doesn't do the former, and only does the latter if told to.
 

Site & Scene News

Popular threads in this forum