Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,706,238
  • Replies Replies 9,235
  • Likes Likes 92
Anyone else getting an error code 2137-7404 when updating the FW after Atmosphere?
I'm sure it's not a DNS thing because I've used my Switch on CFW-Sys for YEARS updating there and this is the first time something like this happens out of nowhere.
 
NinStar said:
I have two questions about this statement.

1. How exactly can he make sure no AI touches atmosphere when it is open source and under GPLv2?
2. Is he still reviewing code even after retirement?
Click to expand...

Even if hexkyz is the official maintainer, I assume things would still be reported to SciresM so he can ask the former to take them down.

He did say "high certainty of being llm-slop", so I guess if someone gets it through, he might not notice. He is definitely anti-AI.

GenoCL said:
Anyone else getting an error code 2137-7404 when updating the FW after Atmosphere?
Click to expand...

Nope. Able to use it on my sysMMC with no issue.
 
  • Like
Reactions: ELY_M
GenoCL said:
Anyone else getting an error code 2137-7404 when updating the FW after Atmosphere?
I'm sure it's not a DNS thing because I've used my Switch on CFW-Sys for YEARS updating there and this is the first time something like this happens out of nowhere.
Click to expand...
It could be your hosts file or a few other reasons, it's something blocking nintendo servers though. Just download the update from elsewhere and install with daybreak. (it's not hard to find with google).
 
AmeliaFox said:
It could be your hosts file or a few other reasons, it's something blocking nintendo servers though. Just download the update from elsewhere and install with daybreak. (it's not hard to find with google).
Click to expand...
Eh I guess I'll just update on Stock. Luckily I have a Hori Split Pad that surprisingly also works as a jig.
But I'm really puzzled as to why this is happening NOW after years of updating on CFW-Sys just fine.

Edit: Alright, I updated on Stock and now went back to CFW-Sys. Everything is fine aside from the "failed to apply nosigchk" so now we wait for SigPatches.
I'm browsing the eShop just fine so now I'm even more puzzled about the previous error. Somehow my Switch just decided not to download the latest firmware patch, I was wondering why I wasn't getting the nag message all this time.

Is it safe to play legit games on CFW-Sys with non-updated sigpatches?
 
Last edited by GenoCL,
pofehof said:
Even if hexkyz is the official maintainer, I assume things would still be reported to SciresM so he can ask the former to take them down.

He did say "high certainty of being llm-slop", so I guess if someone gets it through, he might not notice. He is definitely anti-AI.



Nope. Able to use it on my sysMMC with no issue.
Click to expand...

I fucking hate AI!!!!!! I agree with @SciresM about AI stuff.
 
  • Like
Reactions: ldeveraux
I'm using firmware 20.0 and it's a great satisfaction to know that the project is back and, apparently, stronger than ever.
 
  • Like
Reactions: Blythe93
Back to business, thanks a lot: Hexkyz / Alula / CTCaer, and all Others, I now have access to the eMuMMC again. I'll be more careful next time I update; I'll read more and investigate more. It happened because I was playing Fortnite; it asked me to update the system, and I thought it was just the game. But it's very satisfying to know that there are people like you, a true hero, that we're not helpless. Thank you so much.
 
  • Like
Reactions: D4M28 and Blythe93
recently updated to latest Hekate, AMS 1.10.2, HOS 20.5.0. I can't seem to launch anything with romfs enabled. Even a simple test file that does nothing generates a std::abort (0xFFE) error and forces a reboot. What am I missing here? Already ran the archive bit clear from Hekate.


Update: Should anyone else find this it appears to have been connected to a sysmodule but I can't say which one. I started over with clean Atmosphere which worked so I began adding them in one by one and everything kept working normally.
 
Last edited by l7777,
Good afternoon everyone, DBI in MTP mode is not establishing a connection after the Atmosphere update.
Post automatically merged:

MTP - USB
Post automatically merged:

I have a connection to the PC on Hekate, but there is no connection when dbi is active.
@duckbill007
 

Attachments

  • IMG_5791.jpeg
    IMG_5791.jpeg
    2.5 MB · Views: 14
  • IMG_5792.jpeg
    IMG_5792.jpeg
    2.4 MB · Views: 14
Last edited by Jhen97,
  • Sad
Reactions: XenoFredo

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?