Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[cicci084]

yeah, the bit fix is a problem with MAC users, that's why is on everyone of the guides.

I have never used the Mac to do these things, in fact I have never had similar problems.

I would like to specify that the Sthetix hats are all updated, including obscured DNS and visible serials, all the time wasted was due to the Mac of my "testicles"!

 

[impeeza]

Sorry I don't like the prebuilds packs, normally they don't work well for everyone. So I don't know so much about them. I do prefer to update each homebrew and knows what I am putting on my console.

 

[FanNintendo]

Good evening guys.
Yesterday I finally solved the problem.
I solved it and I want to write how I did it.
First of all, I thank all of you for the support you have provided me.

The cause of my problem was the MAC (computer) that I used to copy the files inside the microsd.

It was the master "Stethix" himself who gave me this answer. Considering that I had followed all the guides to the letter and despite this I had crash problems, I decided to ask him directly (via WhatsApp).
Surprisingly he responded to me instantly and instantly he gave me the solution.

As soon as I sent him the photo of the atmosf€r€ crash he immediately asked if I had used a Mac to perform the operations and, immediately after my confirmation he first gave me the solution which I will post below, then he explained to me why the mac doesn't get along with h@cking operations.

Below is everything you need, for those like me who might have difficulty if they use a Mac.

Obviously it's not my own making, so, in addition to you, I also thank Sir Sthetix in public.

--------------------------------------------

SOLUTION

You need to to the archive bit fix in hekate to fix that issue, mac is weird with hacking stuff.
(foto guide)

The macs computers adds a prefix in front of every files: “ ._ “ that prefix. Mac is designed to be like that, we cannot avoid it, as a matter of "backup" and "search" purpose.

glad you resolve the issues I see Mac is difficult to do with. Hey you told me about HATS is all in one update so i checked i see there fusee.bin was not there. so i don't like all in one updater. i do old fashion way just update one thing at a time. Congratulation you resolve it.

 

[Tails54321]

Question guys, i just wanted to check, has the "Crash" issue been resolved now?

I am using 16.1.0 and an older hekate version, I wish to update sysNAND (+ the others) to play legit games i own online
I used dns mitm method + exosphere, will I get the "crash" issue with 1.6.2 version of atmosphere or is everything resolved now?

Is there anything I need to change in the exosphere files for example or do I just update as normal now?

 

[impeeza]

Question guys, i just wanted to check, has the "Crash" issue been resolved now?

I am using 16.1.0 and an older hekate version, I wish to update sysNAND (+ the others) to play legit games i own online
I used dns mitm method + exosphere, will I get the "crash" issue with 1.6.2 version of atmosphere or is everything resolved now?

Is there anything I need to change in the exosphere files for example or do I just update as normal now?

there is no interest on "fix it" the official posture is "do not blank your prodinfo instead use DNS block"

 

[joeh1974]

Question if this crash affects me if I update from 16.0.3 to 17.0? I only use sysnand, and have never modified the stock downloaded version of Atmosphere. I have two switches, so never cared if my hacked one was ever banned. I update FW via booting back into stock FW and using the official updates. I've never tried to blank my prodinfo or use exosphere, DNS90, or MITM in the past.

Do I still need to configure DNS MITM if I upgrade FW and Atmosphere?

 

[Blythe93]

Question if this crash affects me if I update from 16.0.3 to 17.0? I only use sysnand, and have never modified the stock downloaded version of Atmosphere. I have two switches, so never cared if my hacked one was ever banned. I update FW via booting back into stock FW and using the official updates. I've never tried to blank my prodinfo or use exosphere, DNS90, or MITM in the past.

Do I still need to configure DNS MITM if I upgrade FW and Atmosphere?

It's really not hard to set it up, you can see how here. But seeing that you haven't cleared your prodinfo and don't care about getting your console banned, then you probably don't need to do anything other than update as you usually do (Hekate > Atmosphere > Sigpatches > Firmware).

Some games might stop working after the update, just reinstalling them afterwards should do the trick. Otherwise, check this thread.

 

[jmmc]

Question guys, i just wanted to check, has the "Crash" issue been resolved now?

I am using 16.1.0 and an older hekate version, I wish to update sysNAND (+ the others) to play legit games i own online
I used dns mitm method + exosphere, will I get the "crash" issue with 1.6.2 version of atmosphere or is everything resolved now?

Is there anything I need to change in the exosphere files for example or do I just update as normal now?

You have to use both of them to avoid the crash.

I’m using dns mitm and exosphere and it doesn’t crash.

If you disable dns mitm, it crashes.

I have exosphere enabled because if Nintendo introduces a new connection, I prefer the crash better than get banned.

 

[Nintendoswitchmodfan]

Has anyone gotten SaltyNX working? I can't get a single game to boot when I download it from the HBstore.

 

[ShadowOne333]

i don't think this has been answered, but it seems that in my particular case I ran Incognito_RCM at some point (I thought I did the prod blanking through Atmos, but disabling it still keeps it as all 00s in system settings), and I want to restore the prod info stuff for my Switch so I can sell it as a fully working homebrew console.
I think I still have the bin files with the proper serial stuff in it, since it has values other than all 00s, so I think those are the right files to restore, but how do I restore them?

 

[Dothackjhe]

"Failed to prepare the update. Result: 0x000106002"

Has anybody encountered this error when trying to make an update from FW 16.1.0 to FW 17.0.0 using Daybreak?

 

[Mikolaj]

"Failed to prepare the update. Result: 0x000106002"

Has anybody encountered this error when trying to make an update from FW 16.1.0 to FW 17.0.0 using Daybreak?

Make sure the latest hekate & atmosphere versions are already installed on your sd card.
Make sure your fw 17.0.0 hashes are ok and extract it in a folder placed at the root of your sd card, no other subfolders inside.
Return to the default console UI theme if you have a custom one installed.
Launch Daybreak with full ram and you should be ok.

There's also a small possibility that incognito (if you ever installed it) or custom modules/overlays (SaltyNX, InfoNX, Tesla, Edizon, ...) interfere with the process. You may temporarily uninstall/disable them.

 

[Dothackjhe]

Make sure the latest hekate & atmosphere versions are already installed on your sd card.
Make sure your fw 17.0.0 hashes are ok and extract it in a folder placed at the root of your sd card, no other subfolders inside.
Return to the default console UI theme if you have a custom one installed.
Launch Daybreak with full ram and you should be ok.

There's also a small possibility that incognito (if you ever installed it) or custom modules/overlays (SaltyNX, InfoNX, Tesla, Edizon, ...) interfere with the process. You may temporarily uninstall/disable them.

I was already using the latest version of Hekate and Atmosphere and the hashes of the FW 17.0.0 were okay.

But since you mentioned about an overlay, I recall installing Tesla as an attempt to use emuiibo before. I think that might be the culprit.

Update:

It's the Tesla overlay that was indeed causing it. I was able to update to FW 17.0.0 just fine without it.

 

[Morricorne]

Today I updated the old Nintendo Switch v1 to 17. Everything works like gold without any problems. No problems with games. Only one issue what i have is. I cant blank serial number. I did everything right. Same as Switch OLED. And here it doesn't work on v1

 

[Hayato213]

Today I updated the old Nintendo Switch v1 to 17. Everything works like gold without any problems. No problems with games. Only one issue what i have is. I cant blank serial number. I did everything right. Same as Switch OLED. And here it doesn't work on v1

Setup DNSMitm and Exosphere and then you be able to blank out the serial number.

 

[naddel81]

after update to latest version (deep sea NX) I only get the atmos boot logo for a second and then black screen. how can I fix this?

 

[impeeza]

after update to latest version (deep sea NX) I only get the atmos boot logo for a second and then black screen. how can I fix this?

Do not use premade packages. Update by yourself Atmosphère and hekate then reapply sigpatches

 

[Evamdro]

Can't disable usb3, using emummc

 

[impeeza]

Can't disable usb3, using emummc
View attachment 404038View attachment 404039

and I can not enable it!! my system_settings.ini have u8!0x1 but always shows Force enable USB 3.0 = no

;(

 

[Evamdro]

Funny thing, when I put u8!0x1 it shows that it's disabled, but checking on my computer with USB device tree, it's always connecting via usb 3 and this kills the reception of my joycons so I can't use them on a third party dock because it has usb 3 ports.