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,
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?
if you read the writeup is affecting only system saves, the game saves are always indexed ones.
Sorry guys,i still haven't fully understood whether you can update to 17.0.0 and also install Atmosphere without problems or not.
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.
@impeeza ,
thank you for the explanation,i will wait until everything is updated to avoid unpleasant surprises.
you can safely go to FW 16.1.0, and as so far NO GAME needs 17.0.0 so you really do not need to update.@impeeza ,
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.
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.
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?
I have the same situation. Are the sigpatches to enable exosphere and related?
Wondering if, at the current stage, is possible to enable the blank_prodinfo_emummc in exosphere.ini
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
Similar threads
-
- Portal
-
- Portal
-
- Portal
-
- Portal
