Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,696,714
  • Replies Replies 9,231
  • Likes Likes 92
The battery issue can be resolved by creating a new EmuMMC from a SysNAND with all connections established to Nintendo's servers.

That's what I did, and I no longer have any battery problems.
No need for this, just do this:

/atmosphere/config/system_settings.ini

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF
 
No need for this, just do this:

/atmosphere/config/system_settings.ini

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF

That's what I did initially, and it worked.

But to start fresh with a clean setup, I created a new EmuMMC, reinstalling all my games and their save files.

Yes, it was tedious.
 
No need for this, just do this:

/atmosphere/config/system_settings.ini

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF

My config folder is empty
 
Copy the system_settings.ini file from the config_templates folder and then add the lines AmeliaFox shared in the end of the file

Thanks but why is my folder empty? Was it something I forgot when I jailbreak it?

I created an empty file system_settings.ini and pasted amelia command lines into it.
 
Thanks but why is my folder empty? Was it something I forgot when I jailbreak it?

I created an empty file system_settings.ini and pasted amelia command lines into it.
It is empty by default. If you want to change any settings you need to copy the relevant config file from the config_templates folder. So it is normal that the config folder is empty until you actively put a file there.
 
  • Like
Reactions: forgotten-865
Thanks but why is my folder empty? Was it something I forgot when I jailbreak it?

I created an empty file system_settings.ini and pasted amelia command lines into it.
What petspeed said. It will always go by default settings, unless you tell it otherwise. If you had downloaded a "pack", such as HATS, the directory would not be empty. But I personally hate those packs, because you wouldn't learn what those config files are or what they do. Please take the time to read the docs for everything you use, ESPECIALLY hekate and Atmosphere. You'll be able to fix more issues on your own that way, and probably discover many options that you never knew were options.

Start with everything here (and know that when launching through hekate, it will render some of those options moot, as hekate has its own config): https://github.com/Atmosphere-NX/Atmosphere/tree/master/docs
 
  • Like
Reactions: forgotten-865
If I was a moron and updated my emuMMC to 22, then tried the experimental build of atmos, but upon booting get a yellow screen, is there a way to downgrade my fw manually? Or can I rebuild my emuMMC easily? Should I just wait for possible new release by the new team?
 
If I was a moron and updated my emuMMC to 22, then tried the experimental build of atmos, but upon booting get a yellow screen, is there a way to downgrade my fw manually? Or can I rebuild my emuMMC easily? Should I just wait for possible new release by the new team?
My friend, the best solution is always to wait for the firmware update to version 22; downgrading usually brings problems that ordinary users can't solve on their own.
 
Or can I rebuild my emuMMC easily?
Sure you can. You can ALWAYS build a new emummc through hekate. If you have enough space on your micro sd card, you can even have more than 1 emummc. But you really need to read the hekate docs to understand how to switch between them. Any newly created emummc will be a mirror image of your current sysmmc (so anything present on your current emummc, but not on sys, will have to be reinstalled).

You definitely would want to make a fresh backup of your current one to your PC first, so you can extract your saves later when the Atmosphere update is done...
 

Attachments

does it work? also how are you booting it up is there a fuse ?

not quite, it doesnt let u to go online it asks to do a system update even if ur on 22


this means nothing to me.
boot with https://github.com/CTCaer/hekate/releases/tag/v6.5.2 or provided fusee.bin in the archive, or the one from the github release

provide error reports if any, or image proof of error, and so on. Substantiate claims, kindly, cannot read your mind, can only do as much as value the information provided is, and in this context, no value.

ams.jpg
 
this means nothing to me.
boot with https://github.com/CTCaer/hekate/releases/tag/v6.5.2 or provided fusee.bin in the archive, or the one from the github release

provide error reports if any, or image proof of error, and so on. Substantiate claims, kindly, cannot read your mind, can only do as much as value the information provided is, and in this context, no value.

View attachment 565910
maybe i wasn't clear, it is working with the fuse yes but it doesn't let u connect online in games it ask u to perform a system update even if the firmware is 22
 

Attachments

  • n1.jpg
    n1.jpg
    237 KB · Views: 11
  • n2.jpg
    n2.jpg
    279.7 KB · Views: 14
maybe i wasn't clear, it is working with the fuse yes but it doesn't let u connect online in games it ask u to perform a system update even if the firmware is 22
Right so my work contains patches, you shouldn't be trying to go online (as in, play games online with nintendo online).

What you are seeing trying to play online in what i assume is mario kart 8?


is caused by this:
https://github.com/Atmosphere-NX/At...26d3a940655a6657fd5709e1f828aa8ce9feaR67-R345

this here is "stupid people" protection, preventing you from connecting to nintendo, to prevent you from being banned, as this version embeds patches.

you are not seeing an error, you are experiencing firsthand someone placing equivelant of child proofing onto product to prevent child from injuring itself.
 
Right so my work contains patches, you shouldn't be trying to go online (as in, play games online with nintendo online).

What you are seeing trying to play online in what i assume is mario kart 8?


is caused by this:
https://github.com/Atmosphere-NX/At...26d3a940655a6657fd5709e1f828aa8ce9feaR67-R345

this here is "stupid people" protection, preventing you from connecting to nintendo, to prevent you from being banned, as this version embeds patches.

you are not seeing an error, you are experiencing firsthand someone placing equivelant of child proofing onto product to prevent child from injuring itself.
its pokemon sword, and lmao your explanation is so good i appreciate it haha, and thank you for the build as well, i hope this child proof isn't there tho lol
 
its pokemon sword, and lmao your explanation is so good i appreciate it haha, and thank you for the build as well, i hope this child proof isn't there tho lol
I will never remove said "child proofing", from a build which embeds patches that cannot be toggled off, as that would be extremely bad user experience for users not understnading what they are doing.

I am forcing end users to have the necessary minimum protection to be able to use network enabled installers (network patches + reroute *nintendo* to 127.0.0).

if you want to "play online" with titles you have paid for, and to use NSO / paid subscribtion service to play online, this build is not for that purpose.
 
I will never remove said "child proofing", from a build which embeds patches that cannot be toggled off, as that would be extremely bad user experience for users not understnading what they are doing.

I am forcing end users to have the necessary minimum protection to be able to use network enabled installers (network patches + reroute *nintendo* to 127.0.0).

if you want to "play online" with titles you have paid for, and to use NSO / paid subscribtion service to play online, this build is not for that purpose.
totally understandable, thank you again
 

Site & Scene News

Popular threads in this forum