Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[bth]

The part about it being about desynced battery metrics or a modchip was uncalled for, as if there hadn't been well-known battery-draining issues that have nothing to do with hardware.

And the part about it not being an atmosphere issue is debatable, it doesn't seem like adding those lines from Github cause any issues at all so they could actually be added by default, putting this issue to rest once and for all.

You are misinterpreting that, so no, it's not an atmosphere issue.
the "lines" you speak of are a concept of set-mitm, which overrides the values applicable from https://switchbrew.org/wiki/System_Settings

and no, the values you speak of should not ever be default, as atmosphere is designed to be used while connected to nintendo, while being able to access eshop, while being able to play online and while being able to pay for games. The usecase where that doesn't happen, and the user profile de-syncs, is in 90% a piracy related problem.

(enable_sync_elicense_request = 0x0 <----- anti-piracy check within NS (the module that does rights management on the switch, specific to digital temporary licenses, gained from nintendo switch online, ex: "free" animal crossing dlc, if one chooses to not buy the dlc, but gains it from NSO, moment NSO runs out, the elicense will revoke itself and the dlc will become deactivated))

 

[Blythe93]

ex: "free" animal crossing dlc, if one chooses to not buy the dlc, but gains it from NSO, moment NSO runs out, the elicense will revoke itself and the dlc will become deactivated)

Wow, didn't know it was "free". Every day's a school day, I guess. Thanks for the insight!

 

[Bigdrago]

If you're not aware of an issue, maybe don't comment on it?

There is a battery drain issue that can occur, not that the developpers of atmosphere could issue a fix for it, that's true. But no it's not due to anything you cite here.



Anyway, it's due to the Switch trying to get you to validate a popup that would show on the unmodded side but can't because of Atmosphere's security measures. The quick fix is here: https://github.com/Atmosphere-NX/Atmosphere/issues/2528#issuecomment-3054401265

The long fix is rebuilding your EmuNAND from scratch after making sure you have validated that popup on the stock side.

Thank you. To my understanding this will not interfere with stock os?
Maybe I'll rebuild emuMMC one day, but then I have to reinstall everything even if I copy the entire sdcard because copying back and forth wont work?

 

[alfonsovin]

Is there a way to boot directly in atmosphere through fused.bin payload? With last version of atmosphere, 22.5 compatible, I can’t do it

 

[hippy dave]

Is there a way to boot directly in atmosphere through fused.bin payload? With last version of atmosphere, 22.5 compatible, I can’t do it

Yes as long as you use the latest version of fusee.bin which comes with the latest Atmosphere version

 

[alfonsovin]

Yes as long as you use the latest version of fusee.bin which comes with the latest Atmosphere version

I got an error when using the last fusee.bin don’t know why

 

[XenoFredo]

Thank you. To my understanding this will not interfere with stock os?
Maybe I'll rebuild emuMMC one day, but then I have to reinstall everything even if I copy the entire sdcard because copying back and forth wont work?

Yes you'll have to reinstall everything, sadly.

To save some time, I suggest you activate USB3, and then deactivate it again once everything is installed.

 

[alfonsovin]

I got an error when using the last fusee.bin don’t know why

trying again. atmosphere 1.11.2
fusee.bin downloaded
crystalRCM in macos
payload fusee.bin

"Fatal error occurred when running atmosphere
0100000000.......00000005
abort () called (0xffe)
Report saved fatal_errors: .......198f620.bin

I don't found the log showed

 

[Hayato213]

trying again. atmosphere 1.11.2
fusee.bin downloaded
crystalRCM in macos
payload fusee.bin

"Fatal error occurred when running atmosphere
0100000000.......00000005
abort () called (0xffe)
Report saved fatal_errors: .......198f620.bin

I don't found the log showed

You can try hekate to inject fusee.bin if you want but you problem might be crystalRCM.

 

[alfonsovin]

You can try hekate to inject fusee.bin if you want but you problem might be crystalRCM.

I use hekate without problem
I have use fusee in the past to reboot from a error or to boot using hekate payload but now it’s broken in 1.11.2

I have to change revoot_payload to hekate and only can launch atmosphere from hekate but not with payload only from the menu

 

[Hayato213]

I use hekate without problem
I have use fusee in the past to reboot from a error or to boot using hekate payload but now it’s broken in 1.11.2

I have to change revoot_payload to hekate and only can launch atmosphere from hekate but not with payload only from the menu

Well reboot_payload.bin only work via reboot on unpatched version 1. I mean just inject hekate to load fusee.bin if directly fusee.bin doesn't for you. You could just use fss0 if you want.

 

[alfonsovin]

Well reboot_payload.bin only work via reboot on unpatched version 1. I mean just inject hekate to load fusee.bin if directly fusee.bin doesn't for you. You could just use fss0 if you want.

Till 1.11.2 I use hekate and fusee.bin directly without problem. Now only fss0 load from hekate. Not reboot to atmosphere with fusee not load from pc nor load from hekate

 

[Hayato213]

Till 1.11.2 I use hekate and fusee.bin directly without problem. Now only fss0 load from hekate. Not reboot to atmosphere with fusee not load from pc nor load from hekate

Might be the mac since you are using a mac to inject payload.bin, but more specifically might that that crystalRCM problem.

 

[alfonsovin]

Might be the mac since you are using a mac to inject payload.bin, but more specifically might that that crystalRCM problem.

It isn’t. No matter with crystalRCM. Fugee doesn’t work when try to load from hekate and neither when reboot and system seek for update_reboot

CrystalRCM isn’t the problem