Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,706,380
  • Replies Replies 9,235
  • Likes Likes 92
AmeliaFox said:
Well if you can boot into OFW your switch is working, can you see how much free memory the sd card has in OFW. If you can't boot into hekate did you check your sd card is not corrupted and not reading the contents of the bootloader folder, maybe you should redownload hekate and replace the bootloader folder, or try booting using fusee.bin payload instead.
Click to expand...

.Darky said:
I deleted both the atmosphere and bootloader folder I was using and did a fresh install (added back my contents folder I had backed up) and got the same black screen. I then deleted the contents folder entirely and still didn't work.
Click to expand...
Oh I solved it! Deleted the atmosphere and bootloader folders from the SD card completely. Extracted atmosphere, hekate, fusee, latest sys-patches, bootlogos, hekate_ipl.ini, and emummc.txt all to the SD. I was able to boot hekate, then to emuMMC. Thanks for the hints!
 
1775840632424.png

Glad you get it working, will try again after I'm done with work...

EDIT: Huh, deleted the same folders I tried before but this time I used the contents from the latest HATS pack and I can access emummc again with no problems. Weird. Somehow makes me think it was because I wasn't using sys-patches and instead kept using the sigpatches from the thread.
 
Last edited by .Darky,
Okay, this is genuinely driving me insane.

I was all happy to see that Atmosphere was getting a version 1.11 to keep up with Nintendo's system update boogaloo. Normally, I update Atmosphere and the like first before updating the emuMMC firmware. Well, that's turned into one big nightmare that's (IMO) soft-bricked my Switch.

(emuMMC) firmware is still on 21.0.0 btw.

What should happen? Still be able to load homebrew and installed games.

What happens? I can't launch ANY installed games at all! Can't do the "hold r" for the homebrew that needs it to run, either. All I get in either, is unable to launch software error from the system. And it's especially bad with the installed games because of course the Switch will try to insist the data is corrupt. It's already forced me to uninstall Legends Z-A, and because of the homebrew situation, I can't even launch Awoo or Tinwoo to reinstall it. Times like this, I miss DBI because at least its USB install actually worked; but that hasn't worked in some years now.

I don't even know what I can do anymore at this point. And I sure as hell can't afford to replace the SD card for the system especially now. :cry:
 
codezer0 said:
Okay, this is genuinely driving me insane.

I was all happy to see that Atmosphere was getting a version 1.11 to keep up with Nintendo's system update boogaloo. Normally, I update Atmosphere and the like first before updating the emuMMC firmware. Well, that's turned into one big nightmare that's (IMO) soft-bricked my Switch.

(emuMMC) firmware is still on 21.0.0 btw.

What should happen? Still be able to load homebrew and installed games.

What happens? I can't launch ANY installed games at all! Can't do the "hold r" for the homebrew that needs it to run, either. All I get in either, is unable to launch software error from the system. And it's especially bad with the installed games because of course the Switch will try to insist the data is corrupt. It's already forced me to uninstall Legends Z-A, and because of the homebrew situation, I can't even launch Awoo or Tinwoo to reinstall it. Times like this, I miss DBI because at least its USB install actually worked; but that hasn't worked in some years now.

I don't even know what I can do anymore at this point. And I sure as hell can't afford to replace the SD card for the system especially now. :cry:
Click to expand...
Check the hbl.nsp in your atmosphere folder

And install sys-patch
 
  • Like
Reactions: XenoFredo
codezer0 said:
Okay, this is genuinely driving me insane.

I was all happy to see that Atmosphere was getting a version 1.11 to keep up with Nintendo's system update boogaloo. Normally, I update Atmosphere and the like first before updating the emuMMC firmware. Well, that's turned into one big nightmare that's (IMO) soft-bricked my Switch.

(emuMMC) firmware is still on 21.0.0 btw.

What should happen? Still be able to load homebrew and installed games.

What happens? I can't launch ANY installed games at all! Can't do the "hold r" for the homebrew that needs it to run, either. All I get in either, is unable to launch software error from the system. And it's especially bad with the installed games because of course the Switch will try to insist the data is corrupt. It's already forced me to uninstall Legends Z-A, and because of the homebrew situation, I can't even launch Awoo or Tinwoo to reinstall it. Times like this, I miss DBI because at least its USB install actually worked; but that hasn't worked in some years now.

I don't even know what I can do anymore at this point. And I sure as hell can't afford to replace the SD card for the system especially now. :cry:
Click to expand...
Unable to launch software means your sys patches aren't installed properly. At least that fixed it for me
 
  • Like
Reactions: XenoFredo
josete2k said:
Check the hbl.nsp in your atmosphere folder

And install sys-patch
Click to expand...
Pardon, this is the first time im hearing of such a file existing. Where would it be? What am i looking for regarding it?

And how do i install or update sys-patch now? Used to be a file in these forums, then an app, but now cant find anything meant to do that, that works.
 
codezer0 said:
Pardon, this is the first time im hearing of such a file existing. Where would it be? What am i looking for regarding it?

And how do i install or update sys-patch now? Used to be a file in these forums, then an app, but now cant find anything meant to do that, that works.
Click to expand...
did you even look? /s

D

Homebrew Homebrew app  Thread 'sys-patch - sysmod that patches on boot'

sys-patch is a sysmodule that patches fs, ldr, es and nifm on boot. This has the same effect as sigpatches.

The benefit of sys-patch is that it only needs updating when something major breaks, the last time this happened was fw 15.0.0.

Another benefit is patching ldr will (likely) never need to be updated. In the past, if a silent atmosphere update happened, this would break sigpatches (unless you updated them again).

sys-patch also outputs a log where you can see which patches are applied, which one failed and some other useful data. You can manually read the log or use the overlay...
  • Like
  • Love
  • Wow
 
Last edited by sudeki300,
  • Like
Reactions: ldeveraux
sudeki300 said:
did you even look? /s

D

Homebrew Homebrew app  Thread 'sys-patch - sysmod that patches on boot'

sys-patch is a sysmodule that patches fs, ldr, es and nifm on boot. This has the same effect as sigpatches.

The benefit of sys-patch is that it only needs updating when something major breaks, the last time this happened was fw 15.0.0.

Another benefit is patching ldr will (likely) never need to be updated. In the past, if a silent atmosphere update happened, this would break sigpatches (unless you updated them again).

sys-patch also outputs a log where you can see which patches are applied, which one failed and some other useful data. You can manually read the log or use the overlay...
  • Like
  • Love
  • Wow
Click to expand...
The link provided just 404's, sir. :|
 
sudeki300 said:
i was pointing you to the thread, no need for a sir good buddy, we're all friends here. hopefully you got sorted
Click to expand...
Incidentally, downloading this one vanilla atmopack is what got everything working again. I do have some duplicate entries in the homebrew list, sure; but that's a minor nit to pick next to not being able to launch at all.
 
XenoFredo said:
I'm probably focussing too much on people who have issues with the latest firmware. Just to be sure, for most people, firmware 22.1.0 and the latest atmosphere are working fine, right?
Click to expand...
I wouldn't say 'fine' but eventually they get it working. Most people don't update their firmware unless they absolutely have to.
 
  • Like
Reactions: Blythe93 and XenoFredo
ldeveraux said:
I wouldn't say 'fine' but eventually they get it working. Most people don't update their firmware unless they absolutely have to.
Click to expand...
Maybe if people posted properly like this:

Emunand - fat or exfat firmware version installed.
Atmosphere - clean folder with no extra plugins/addons/patches etc.
hekate - clean install with virgin bootloader folder (no added extra files)

Then all you people having issues can see what the pattern is that's causing your issues.
 
  • Like
  • Love
Reactions: Blythe93, Bruce_Wayne and XenoFredo
ldeveraux said:
Oh I solved it! Deleted the atmosphere and bootloader folders from the SD card completely. Extracted atmosphere, hekate, fusee, latest sys-patches, bootlogos, hekate_ipl.ini, and emummc.txt all to the SD. I was able to boot hekate, then to emuMMC. Thanks for the hints!
Click to expand...
Perfect, so basically you follow the instructions of the upgrade guide!
 
  • Like
Reactions: NeoGranzon, Blythe93 and XenoFredo
ldeveraux said:
For years it was absolutely unnecessary to completely recreate those 2 folder. Copying over the top was quick and effective. Only recently did it become a larger problem. Sorry for taking up your time.
Click to expand...
I can't recall if I've ever removed those two folders since firmware 16.x.x (that's when I purchased my Switch). As long as you keep your CFW setup simple and tidy, it's just a matter of copying the new files over to the SD card, overwriting the existing files when prompted. Only a couple of times I had to remove sys-patch config file, just to start anew but that's pretty much it.

From what I've seen so far, people that had those issues usually used some premade packs or all-in-one updaters or didn't know what they were doing at all. Especially those that use bunch of apps and sys-modules. Outdated modules sometimes can prevent system from booting/working properly and, to me, it's not an easy task to troubleshoot other users' issues. Therefore, I generally suggest that they remove atmosphere and bootloader folders, maybe even switch folder and start from scratch with a fresh Atmosphere, hekate and sys-patch and see if it'll work. If not, God knows what else went wrong without fruther inspection.
Post automatically merged:

XenoFredo said:
I'm probably focussing too much on people who have issues with the latest firmware. Just to be sure, for most people, firmware 22.1.0 and the latest atmosphere are working fine, right?
Click to expand...
I have the latest firmware, Atmosphere, hekate, sys-patch and DBI running on my Switch and, so far, I haven't run into an issue. I only have a couple of sys-modules (sys-patch, emuiibo, MissionControl and TriPlayer) and most of the homebrew apps I use either have an official version updated to work on 21.x.x or higher or have an unofficial version in this thread. I only play Switch games on my Switch, can't say anything about Linux/Android stuff or the Retroarch or similar. Can't say much either for other sys-modules either.
 
Last edited by Blythe93,
  • Like
  • Love
Reactions: RnRpax, impeeza and XenoFredo
Blythe93 said:
If not, God knows what else went wrong without fruther inspection.
Click to expand...
If not, it means the emunand or sd card is corrupted or the sd card is failing. Because if you have a virgin Atmosphere and bootloader folder and updated hbmenu.nro (which comes with atmosphere). And you are using the correct fusee.bin or hekate.bin file which also comes the Atmosphere and hekate then there's no other reason it can fail.

Basically it's a user error using old files with new files by just copying new files into an existing folder that contains older files.
 
  • Like
Reactions: Blythe93
Blythe93 said:
I have the latest firmware, Atmosphere, hekate, sys-patch and DBI running on my Switch and, so far, I haven't run into an issue. I only have a couple of sys-modules (sys-patch, emuiibo, MissionControl and TriPlayer) and most of the homebrew apps I use either have an official version updated to work on 21.x.x or higher or have an unofficial version in this thread. I only play Switch games on my Switch, can't say anything about Linux/Android stuff or the Retroarch or similar. Can't say much either for other sys-modules either.
Click to expand...
Thanks for your reply, the latest updates were installed without any issues on my end too.
 
  • Love
Reactions: Blythe93
ldeveraux said:
For years it was absolutely unnecessary to completely recreate those 2 folder. Copying over the top was quick and effective. Only recently did it become a larger problem. Sorry for taking up your time.
Click to expand...
don't worry, we are here to help each others, unlike the mods are trying to do, this community is full of good people helping.
Post automatically merged:

Blythe93 said:
I can't recall if I've ever removed those two folders since firmware 16.x.x (that's when I purchased my Switch). As long as you keep your CFW setup simple and tidy,
Click to expand...
Yeah, that is because you didn't use a prepackaged package full of things you do not know they are there.

and when an upgrade comes you know you must to remove your theme (if you use any), and must upgrade the few Sys-Modules you have before the upgrade.
 
  • Like
  • Love
Reactions: Blythe93 and NeoGranzon

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Is it fixable

Hacking Emulation  Switch Prod Keys downloading from sites okay?