Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[zerox521]

Hi, a few days ago I updated my sysnand to 17.0.0, and I can't boot back into it, I have my emunand on 16.0.0 and updated both Atmosphere and Hekate, my question is, will I get banned by nintendo if I boot atmosphere into sysnand to apply the fix? My console has been wipped before.

 

[Draxzelex]

Hi, a few days ago I updated my sysnand to 17.0.0, and I can't boot back into it, I have my emunand on 16.0.0 and updated both Atmosphere and Hekate, my question is, will I get banned by nintendo if I boot atmosphere into sysnand to apply the fix? My console has been wipped before.

Any usage of CFW/homebrew can you get you banned. Run Atmosphere on your sysMMC at your own risk.

 

[petspeed]

Hi, a few days ago I updated my sysnand to 17.0.0, and I can't boot back into it, I have my emunand on 16.0.0 and updated both Atmosphere and Hekate, my question is, will I get banned by nintendo if I boot atmosphere into sysnand to apply the fix? My console has been wipped before.

You really have no other choice if you want sysmmc to boot again. Just booting a clean Atmosphere in sysmmc should not get you banned. Just don't apply any sysmodules, themes or other extra things.

 

[helvetinperkeles]

Hi! I got this odd issue now when i updated my switch to latest atmos and fm that everytime i install charging cable to my switch and put it to sleep mode soon i get this error and switch reboots itself. I don't even have this labeled folder on my atmosphere content and this has never happened before. Any idea?

 

[linuxares]

Hi! I got this odd issue now when i updated my switch to latest atmos and fm that everytime i install charging cable to my switch and put it to sleep mode soon i get this error and switch reboots itself. I don't even have this labeled folder on my atmosphere content and this has never happened before. Any idea?

Can you take out your SDCard and do a chkdsk X: /f /r /x on it? So it ain't corruption causing it.

 

[helvetinperkeles]

Can you take out your SDCard and do a chkdsk X: /f /r /x on it? So it ain't corruption causing it.

Sorry but i have no idea what this method is . But when i connect my switch to pc it's not saying anything obaut corruption

 

[linuxares]

Sorry but i have no idea what this method is

Google how to do it

 

[helvetinperkeles]

Google how to do it

Could it be that this new atmos version has a bug that it don't like sleepmode when charging the device?

 

[linuxares]

Could it be that this new atmos version has a bug that it don't like sleepmode when charging the device?

Nope, it's an old error. Just search for the error code and people suspect it might be a broken sysmodule or corruption.

 

[helvetinperkeles]

Nope, it's an old error. Just search for the error code and people suspect it might be a broken sysmodule or corruption.

Hmmm.. i have updated all my files. Well but good to know i have hint now where to look if this gets worse.
Oh but if the case would be broken sysmodule should i then have that installed? I mean that i dont have that numbered folder in my content and i just noticed that it makes same crashes when i try to boot some games. Ok this needs to be fixed.

Post automatically merged: Nov 20, 2023

Can you take out your SDCard and do a chkdsk X: /f /r /x on it? So it ain't corruption causing it.

I did the chkdsk F snd there was no issues there. Any idea what sysmodule could cause this then and what should i delete?

 

[linuxares]

Generally check your loaded sysmodules with for example with https://github.com/Team-Neptune/DeepSea-Toolbox and check if all of them are up to date.

 

[helvetinperkeles]

Generally check your loaded sysmodules with for example with https://github.com/Team-Neptune/DeepSea-Toolbox and check if all of them are up to date.

Hmm.. never used this. I will check. Thanks!

Post automatically merged: Nov 21, 2023

Generally check your loaded sysmodules with for example with https://github.com/Team-Neptune/DeepSea-Toolbox and check if all of them are up to date.

Ok i disabled all sysmodules but tesla and sysclock and now there has not been crashes. So the case must be broken or outdated module.

 

[laz305]

Ok so I used for the first time the AIO to update atmosphere. I said no when it wanted to overwrite ini files, which I know now was wrong to do. I’m still on 16.1 so what’s best way to fix this and get Hekate to load up again?

UPDATE: ok so I was able to update ams via sd card and now it boots up Hekate and CFW. Always a mission.

 

[linuxares]

Hmm.. never used this. I will check. Thanks!

Post automatically merged: Nov 21, 2023

Ok i disabled all sysmodules but tesla and sysclock and now there has not been crashes. So the case must be broken or outdated module.

Nice! Then it's just to update all in the list

 

[helvetinperkeles]

Ok now my i got new issue after i updated atmos and fw to the latest versions. Everytime i put my switch now to sleepmode and open it next day my battery has fully drained. This has never happened before so what could do this? I use auto rmc and i do have sysmodules installed but why would they cause this now? I already set my switch to airplane mode but that did not help at all.

 

[burhansalih]

Ok now my i got new issue after i updated atmos and fw to the latest versions. Everytime i put my switch now to sleepmode and open it next day my battery has fully drained. This has never happened before so what could do this? I use auto rmc and i do have sysmodules installed but why would they cause this now? I already set my switch to airplane mode but that did not help at all.

Disable the modules and see if the same thing happens....

 

[helvetinperkeles]

Disable the modules and see if the same thing happens....

ok now i'm trouple again. I deleted all my sysmodules and i left only fizeau, edizon, sysmodules and sys-clk and i reinstalled them all with latest version. At first i got crash after i boot up the switch and i needed to delete these two folders from content folder. Now my switch boots up and i can open tesla menu BUT Fizeau wont open at all and when i try to open sys-clk i get fatal error sys-clk is not running error and if i try open edizon i get system crash. No idea what i have done wrong here

 

[Hayato213]

ok now i'm trouple again. I deleted all my sysmodules and i left only fizeau, edizon, sysmodules and sys-clk and i reinstalled them all with latest version. At first i got crash after i boot up the switch and i needed to delete these two folders from content folder. Now my switch boots up and i can open tesla menu BUT Fizeau wont open at all and when i try to open sys-clk i get fatal error sys-clk is not running error and if i try open edizon i get system crash. No idea what i have done wrong here

That point to Fizeau.

 

[helvetinperkeles]

Now i lost all my custom covers. What the hell is happening?

 

[Hayato213]

Now i lost all my custom covers. What the hell is happening?

You probably delete those custom covers, as for the error 0100000000000F12 it points to Fireau.