Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,780,475
  • Replies Replies 9,374
  • Likes Likes 93
Can't you just downgrade your console? If you haven't burned your fusees there should be no problem

Inviato dal mio Nexus 5X utilizzando Tapatalk
Currently you can only downgrade your console if it's not ipatched.

Anyone with an ipatched switch will have the correct number of fuses burnt for their firmware, since you need to have coldboot execution to protect them.
 
  • Like
Reactions: Frank1905
Of course, I was talking about hackable switches
Currently you can only downgrade your console if it's not ipatched.

Anyone with an ipatched switch will have the correct number of fuses burnt for their firmware, since you need to have coldboot execution to protect them.

Inviato dal mio Nexus 5X utilizzando Tapatalk
 
Thanks for the progress on Atmosphere. I wanted to know if anyone has come across the issue where the switch crashes when launching the "album" icon through Atmosphere. It starts to load for a few seconds then goes to black. I think it somehow crashes and shuts down. Any advice would be great appreciated :)
 
Thanks for the progress on Atmosphere. I wanted to know if anyone has come across the issue where the switch crashes when launching the "album" icon through Atmosphere. It starts to load for a few seconds then goes to black. I think it somehow crashes and shuts down. Any advice would be great appreciated :)
Are you using version 0.8.2? Try 0.8.1 ;)
 
Has anyone done a cart update with atmosphere 0.8.1 or above, with AutoRCM installed? Having read through the 'AutoRCM protection' patch, I *think* it would protect AutoRCM during game cart updates, because it generally prohibits BCT writes from the NS service, rather than any specific firmware-upgrade function, but I thought I'd ask to be sure.

An update: I used Atmosphere 0.8.1 to update to 5.1 using my Super Mario Party cart, and it did, in fact, preserve my AutoRCM.
 
silly question. i just updated from 5.1 renix to 6.2 atmosphere. and when i boot there's no atmosphere bootscreen. i go right from hekate to the nintendo logo. is there a way to add a bootscreen so i know for sure im in CFW? thanks.
 
silly question. i just updated from 5.1 renix to 6.2 atmosphere. and when i boot there's no atmosphere bootscreen. i go right from hekate to the nintendo logo. is there a way to add a bootscreen so i know for sure im in CFW? thanks.
I think the boot logo only shows if autoboot=1 is set in hekate_ipl.ini
 
  • Like
Reactions: meohsix
silly question. i just updated from 5.1 renix to 6.2 atmosphere. and when i boot there's no atmosphere bootscreen. i go right from hekate to the nintendo logo. is there a way to add a bootscreen so i know for sure im in CFW? thanks.
You could alternatively use fusee-primary.bin as your payload instead of hekate, that way you get the atmosphere logo.
 
  • Like
Reactions: meohsix
You could alternatively use fusee-primary.bin as your payload instead of hekate, that way you get the atmosphere logo.
I remember getting the boot logo with one of the first releases of atmosphere/fusee, but it suddenly stopped showing it at some point. I can however get a custom logo to show using hekate with autoboot.
 
  • Like
Reactions: peteruk

Site & Scene News

Popular threads in this forum