Hacking Sleep mode doesn't work on SXOS 2.0 in emunand

[der:Tom]

Yesterday I wanted to test the new Nand feature of sxos 2.0, everything worked fine so far but now I got the problem that the Switch crashes when I send it to sleep mode while in emunand (fw 5.1 on emunand), the original Nand with horizon 6.0 works fine.
Anyone else got this problem?

 

[subcon959]

I'm still on 1.7 or something but it's possible all these crashes and bugs are caused by code that was deliberately left fubar to see if it would get taken by TX.

 

[thefunkygibbon]

I'm still on 1.7 or something but it's possible all these crashes and bugs are caused by code that was deliberately left fubar to see if it would get taken by TX.

what?

 

[fadx]

what?

I think he's saying that it's possible that since SX OS uses code from other people's projects that they could intentionally be putting in code that would cause problems when used as it's implemented in SX OS, pure speculation though so don't take it too seriously unless this is proven to be the case.

 

[subcon959]

what?

I think he's saying that it's possible that since SX OS uses code from other people's projects that they could intentionally be putting in code that would cause problems when used as it's implemented in SX OS, pure speculation though so don't take it too seriously unless this is proven to be the case.

>when you push broken patches so TX can steal them and then amend commit with working patches.
( ͡° ͜ʖ ͡°)

— Rei (@Reisyukaku) September 23, 2018

 

[marveldragon]

I was having the same issue but not anymore.

When I was having the issue:
NAND FRM = 5.1.0
EMU FRM = 6.0
EMU SIZE = 5GB
COPIED User partition
EMU Free Space = ~1GB.

STOPPED Happening:
NAND FRM = 5.1.0
EMU FRM = 5.1.0
EMU SIZE = 5GB
EMU Don't Copy User partition
EMU Free Space = ~4GB
NOTE: When I did this I did not get the freezing issue anymore but Octopath stopped working for me. When I mounted I could not start the game anymore. However other games I never played worked.

Works Fine:
NAND FRM = 5.1.0
EMU FRM = 5.1.0
EMU SIZE = 10GB
COPIED USER partition
EMU Free Space = ~6GB
NOTE: Octopath works and no crashes from playing games and sleeping. Might be either the firmware or the amount of free space you have left. I would update my emuNAND firmware to test but I rather count my blessings and not test my luck at this point.

 

[drfunkenstein2k]

I installed EMUnand with default settings.
I do not use autoRCM.
I updated Emunand to fw6.0 and i have not experienced any problems with sleep mode or crashes.

 

[thaikhoa]

I haven't experienced any issue.

Pure Sysnand unlinked from Emunand

Pure sysnand 6.0, emunand 6.0 5GB + Copied USER

 

[der:Tom]

Thx for your input guys, gonna test this later again.

--------------------- MERGED ---------------------------

Pure Sysnand unlinked from Emunand

What do you mean by "unlinked"?

 

[thaikhoa]

Thx for your input guys, gonna test this later again.

--------------------- MERGED ---------------------------



What do you mean by "unlinked"?

After creating emunand, factory restore sysnand (without memory card plugged in) will unlink the two nands. It means the two nands no longer share the same Nintendo folder (Content and save) on the memory card. So you can control the content for each nand by renaming Nintendo folder as I said above.

If you don't unlink the OS will delete all data which doesn't exist on the nand it's not installed.

 

[Reecey]

How are people updating EmuNAND to version 5.1 from fw6.0 nand op mentions? I didn’t know you could update a chosen firmware.

--------------------- MERGED ---------------------------

After creating emunand, factory restore sysnand (without memory card plugged in) will unlink the two nands. It means the two nands no longer share the same Nintendo folder (Content and save) on the memory card. So you can control the content for each nand by renaming Nintendo folder as I said above.

If you don't unlink the OS will delete all data which doesn't exist on the nand it's not installed.

Don’t tell him that it doesn’t write the EmuNAND to the sd card at all, it writes it to the actual nands memory, if you delete your system nand memory it will delete everything.

 

[stewacide]

I was having the same issue but not anymore...

So, as you made more free space in emunand, it became more stable?

Makes me think that some bug is progressively 'eating up' emunand, and the more you have the longer until it inevitably crashes.

 

[thaikhoa]

How are people updating EmuNAND to version 5.1 from fw6.0 nand op mentions? I didn’t know you could update a chosen firmware.

--------------------- MERGED ---------------------------

Don’t tell him that it doesn’t write the EmuNAND to the sd card at all, it writes it to the actual nands memory, if you delete your system nand memory it will delete everything.

No, factory restore or any functions that delete things on the OS wont delete the created emunand.

Unless you restore BOOT1/ USER partition or delete NAND00 / 01.bin in the partition it will delete the emunand.

 

[marveldragon]

So, as you made more free space in emunand, it became more stable?

Makes me think that some bug is progressively 'eating up' emunand, and the more you have the longer until it inevitably crashes.

I won’t say it inevitably crashes. Been running it for 10+ hours so far without it crashing and me playing different games. But freeing up the space seems to be the case for me that or I screwed up when I updated my firmware with Choi.

UPDATE:
I can now honestly say it is not freeing up space on the NAND. It is a problem with 6.0 for me. I updated my emuNand again to 6.0 and it crashes. I updated my sys to 6.0 and it crashes. I removed my emu and just ran with sys and it crashes. I reverted back to 1.9 and it runs fine. Seem to be an issue with 2.0 and 6.0. I had no issue with 5.1.0

 

[DocBo]

Is it possible to use ChoidujourNX on EmuNAND to Down/Upgrade the EmuNAND?!

 

[marveldragon]

Is it possible to use ChoidujourNX on EmuNAND to Down/Upgrade the EmuNAND?!

Yes.

 

[bundat]

(fw 5.1 on emunand), the original Nand with horizon 6.0 works fine.

You burned your fuses since you have an updated OFW/sysNAND.
Check using Hekate, you must have 7 burned fuses.

Sleep mode is broken when you have too many burned fuses, this is expected behavior, as explained here by CTCaer (dev of the current Hekate fork):
https://gbatemp.net/threads/switch-...tore-crashes-after-sleep.519091/#post-8301468

Not sure why you are trying to run a lower FW emuNAND while having a high FW sysNAND. Is it for better Homebrew support?

 

[DocBo]

Yes.

The main question was, when i use ChoidujourNX to downgrade the EmuNAND, will the "SysNAND untouched"?!

--------------------- MERGED ---------------------------

Not sure why you are trying to run a lower FW emuNAND while having a high FW sysNAND. Is it for better Homebrew support?

Yes for better Homebrew support.

 

[marveldragon]

The main question was, when i use ChoidujourNX to downgrade the EmuNAND, will the "SysNAND untouched"?!
.

SysNand will not be touched. Only emuNand will be. Having said that, the EmuNAND will not work properly with 5.1.0 if you have updated to 6.0 and burnt your fuses.

 

[DocBo]

SysNand will not be touched. Only emuNand will be. Having said that, the EmuNAND will not work properly with 5.1.0 if you have updated to 6.0 and burnt your fuses.

Yes, the EmuNAND is on 5.1 and the only thing that wont work is the sleep mode.