Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,743,063
  • Replies Replies 9,309
  • Likes Likes 92
This is the commit d8a37b4b7 from the official repo build with latest libraries, I am attaching the Fusee.bin and sigpatches for this build.
installed it OK, then updated to 20.1.5 (daybreak) and upon reboot, got the following error on boot. Any idea what this might mean?
Unknown.jpg
 
  • Like
Reactions: ikynx and Blythe93
  • Like
Reactions: Blythe93
This is the commit d8a37b4b7 from the official repo build with latest libraries, I am attaching the Fusee.bin and sigpatches for this build.
Do I need to combine commit's atmosphere to the official repo atmosphere? Or delete the official repo atmosphere entirely and just use commit's version?
Can I just use sys-patches1.5.6 instead of sigpatches?
 
Or delete all users and create new ones. But you have to backup all your saves and restore them to the new users
I have tried this. Deleting linked users in emuNAND is not straightforward, because it needs to contact N servers. Some homebrew (e.g. DBI) can force delete these users without phoning home, but it doesn't seem to avoid the issue.

For reference: unpatched Erista, 19.0.1 emuNAND, single user, with legit NNID. Update to 20.1.5 resulted in 80% battery drain overnight, unless Airplane Mode is on.

So I created a new user without NNID in emuNAND, then used DBI to remove the old linked user. Now that emuNAND has a single, unlinked, user. It still drains 80% battery overnight.

I guess the only valid solution now is to boot sysNAND and either remove the linked user, or update and accept the new EULA. Then, create a new emuNAND.
 
New release soon! ™️
Post automatically merged:

And also building now

1752600313761.png

Post automatically merged:

Post automatically merged:

And also building now

1752600313761.png
Bild and is binary the same of muxi.
 
Last edited by impeeza,
Did anyone try downgrading firmware via Daybreak yet while on the latest firmware to e.g. 18.x.x or 19.x.x?
You can do it but after that you must to format the EmuNAND, because the User partition become invalid. Was a change on FW 20.x.x on the User Partition which is no retro compatible.
 
Well, he hasn't said that there is not any issue...
You can do it but after that you must to format the EmuNAND, because the User partition become invalid. Was a change on FW 20.x.x on the User Partition which is no retro compatible.
Thanks for the replies!
 

Site & Scene News

Popular threads in this forum