Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,808,089
  • Replies Replies 9,401
  • Likes Likes 93
SciresM said:
Happy (pre-) June 15th!
Post automatically merged:

People may also be interested in the write-up I just posted
Click to expand...




Thanks a lot for your effort and hard work.

Additional question: have using Daybreak with the option «Reset to factory settings» caused this problem too?
 
Last edited by impeeza,
  • Like
Reactions: ShadowOne333
Can this be a problem with savegames/tickets (e.g. Mario Kart - season pass - static/temporary ) in future?
 
Sorry guys,i still haven't fully understood whether you can update to 17.0.0 and also install Atmosphere without problems or not.
 
NeoGranzon said:
Sorry guys,i still haven't fully understood whether you can update to 17.0.0 and also install Atmosphere without problems or not.
Click to expand...
As today at this time, you can update to FW 17.0.0 BUT THE FIRST TIME YOU BOOT SysNAND or EmuNAND YOU MUST BOOT VIA Atmosphère 1.06.1 to avoid bricks.

also you must use the latest Hekate.

Now, some Sysmodules, sigpatches and Homebrew still needed to be updated to support FW 17.0 so is up to you to update.
 
  • Like
Reactions: Tyvar1, hausa51, BigOnYa and 2 others
impeeza said:
As today at this time, you can update to FW 17.0.0 BUT THE FIRST TIME YOU BOOT SysNAND or EmuNAND YOU MUST BOOT VIA Atmosphère 1.06.1 to avoid bricks.

also you must use the latest Hekate.

Now, some Sysmodules, sigpatches and Homebrew still needed to be updated to support FW 17.0 so is up to you to update.
Click to expand...
@impeeza ,👌 thank you for the explanation,i will wait until everything is updated to avoid unpleasant surprises.
 
  • Like
Reactions: Tyvar1, BigOnYa and impeeza
impeeza said:
Thanks a lot for your effort and hard work.

Additional question: have using Daybreak with the option «Reset to factory settings» caused this problem too?
Click to expand...
Doesn't that setting do the whole initialize console thing? Like the one in system settings? Did that with ChourDujourNX and 17.0 OFW worked for me.
 
PADBXS said:
Doesn't that setting do the whole initialize console thing? Like the one in system settings? Did that with ChourDujourNX and 17.0 OFW worked for me.
Click to expand...
yeah, but my questions if the way Daybreak doit is the same of ChourDujorNX and TegraExplorer, so you will end on the same issue. or Daybreak do it on a more "official" way.
 
impeeza said:
yeah, but my questions if the way Daybreak doit is the same of ChourDujorNX and TegraExplorer, so you will end on the same issue. or Daybreak do it on a more "official" way.
Click to expand...
1697559532248.png



Sounds like it uses/emulates how Nintendo does it.
 
  • Love
  • Like
Reactions: Blythe93 and impeeza
impeeza said:
As today at this time, you can update to FW 17.0.0 BUT THE FIRST TIME YOU BOOT SysNAND or EmuNAND YOU MUST BOOT VIA Atmosphère 1.06.1 to avoid bricks.

also you must use the latest Hekate.

Now, some Sysmodules, sigpatches and Homebrew still needed to be updated to support FW 17.0 so is up to you to update.
Click to expand...
What about a new clean stock ofw Switch? Can't I just boot hekate, make a backup of my nand, create a cfw and boot into 1.7.0.0 CFW?
 
Pox said:
Is there any chance for Mario RPG to remain on the 16.1 requirement?
Click to expand...
It's a real coin toss with that one. Since it's fully possible it haven't gone gold until like this week or last week. (I have no idea basically). But chances are sadly quite high it's 17.0.0
 
  • Like
  • Sad
Reactions: mathew77, Blythe93, Tyvar1 and 3 others

Site & Scene News

Go to forum More news

Popular threads in this forum