Hacking SX OS SD Emunand

  • Thread starter Thread starter Frank1905
  • Start date Start date
  • Views Views 17,436
  • Replies Replies 75
I used old boot files and recent ones, with no succeed for both. At the end I used all the emunand files created after migration.
 
Last edited by Frank1905,
1. Create emunand
2. Try to boot > this fails
3. Backup boot 0/1 with SXOS launcher (You can click options to only backup boot 0/1)
4. Replace emunand boot 0/1 with the backup.
5. Boot emunand :)

Can confirm this worked for me, on 5.1.0 sysnand, 5.1.0 fresh emunand
 
  • Like
Reactions: Voridten
Can confirm this worked for me, on 5.1.0 sysnand, 5.1.0 fresh emunand
Cool, I'm happy we're finding solutions for this problem. It looks so misterious... Everyone needs a different solution

Inviato dal mio Nexus 5X utilizzando Tapatalk
 
BTW Why did they not add an LED to the Switch.

The Vita has file-access and power LEDs. The Switch, well it is completely dark. I would like to see if it is charging, on/off/standby etc.
 
BTW Why did they not add an LED to the Switch.

The Vita has file-access and power LEDs. The Switch, well it is completely dark. I would like to see if it is charging, on/off/standby etc.
That would be cool!
By the way guys, I found another problem/bug/Idontknowhowtocallit
When I'm on SD emunand I can't go on sleep mode. If I do, my nintendo switch doesn't turn on anymore and I have to hold power for some seconds to force shut down and then turn it on again.
Did you encounter this problem too?
EDIT: It doesn't happen every time, but it's like 80-90% of the times.
 
Last edited by Frank1905,
That would be cool!
By the way guys, I found another problem/bug/Idontknowhowtocallit
When I'm on SD emunand I can't go on sleep mode. If I do, my nintendo switch doesn't turn on anymore and I have to hold power for some seconds to force shut down and then turn it on again.
Did you encounter this problem too?
EDIT: It doesn't happen every time, but it's like 80-90% of the times.
I have got this problem too, on 6.2 sysnand, 6.1 emunand. It used to be not happening, now it happens 100% of the time!
 
I have got this problem too, on 6.2 sysnand, 6.1 emunand. It used to be not happening, now it happens 100% of the time!
Probably it happens because the operating system is loaded from SD card, and when we put our Switch on sleep mode the SD "goes to sleep too" and everything crashes. I hope and think they will find a solution for this.

Inviato dal mio Nexus 5X utilizzando Tapatalk
 
I have got this problem too, on 6.2 sysnand, 6.1 emunand. It used to be not happening, now it happens 100% of the time!
That's because the console's warmboot (aka sleep mode) freaks out due to the fuse count being higher than EmuNAND's firmware. This same issue occurs when people downgrade their SysNAND to a firmware lower than their fuse count.
 
Damn, that sounds bad... I just updated sysnand to 6.2.0, I didn't think it could affect Emunand.
Why doesn't it happen every time though?
That's because the console's warmboot (aka sleep mode) freaks out due to the fuse count being higher than EmuNAND's firmware. This same issue occurs when people downgrade their SysNAND to a firmware lower than their fuse count.

Inviato dal mio Nexus 5X utilizzando Tapatalk
 
Damn, that sounds bad... I just updates sysnand to 6.2.0, I didn't think it could affect Emunand.
Why doesn't it happen every time though?

Inviato dal mio Nexus 5X utilizzando Tapatalk
EmuNAND only creates a copy of the NAND but the Switch is made up of much more than just the NAND. It has TSEC, the gamecart slot, fuses, etc.
 
EmuNAND only creates a copy of the NAND but the Switch is made up of much more than just the NAND. It has TSEC, the gamecart slot, fuses, etc.
So every person in my position has to wait for the new 6.2.0 fw to be hacked too. Anyways we can still play without sleep mode, so... not so bad.

Inviato dal mio Nexus 5X utilizzando Tapatalk
 
1. Create emunand
2. Try to boot > this fails
3. Backup boot 0/1 with SXOS launcher (You can click options to only backup boot 0/1)
4. Replace emunand boot 0/1 with the backup.
5. Boot emunand :)

I just tried exactly these steps -> still boots into black screen forever.

I checked with Windiff again: Comparing emunand boot0.bin to backup boot0.bin there were differences. No difference for boot1.bin.

I guess I will wait for a fix from TX. In the meantime, I am happy I have a full backup of my system NAND for now.

And I will keep using system NAND until there exists an official fix for this problem. After all, we shouldn't have to manually copy any .bin files.
 
Last edited by rsn8887,
Ive try emunand on a friend 6.0.0 that worked fine... Than Update to 6.1.0 via choidujour works fine too...
I try to downgrade mine later to 6.0.0 and Try the same process with Update again to 6.1.0 :D
 
Ive try emunand on a friend 6.0.0 that worked fine... Than Update to 6.1.0 via choidujour works fine too...
I try to downgrade mine later to 6.0.0 and Try the same process with Update again to 6.1.0 :D
Let us know ;D

Inviato dal mio Nexus 5X utilizzando Tapatalk
 
Not worked^^ ive checked the sd card on cmd with chkdsk on Windows and viola... Many files were "corrupted" on sd and the fresh Emunand Backup.... After format the Emunand works
How do you explain the corruption?

Inviato dal mio Nexus 5X utilizzando Tapatalk
 
How do you explain the corruption?

Inviato dal mio Nexus 5X utilizzando Tapatalk
No idea. Many files was marked as corrupted/faulty. Example : "SXOS/Emunand/ (6): a corrupted file was detected" Same with Some titles in /Nintendo/content folder but the titles all work fine
 
No idea. Many files was marked as corrupted/faulty. Example : "SXOS/Emunand/ (6): a corrupted file was detected" Same with Some titles in /Nintendo/content folder but the titles all work fine
Many people say that exfat formatted SD cards may bring to corrupted files, after some transfers.

Inviato dal mio Nexus 5X utilizzando Tapatalk
 

Site & Scene News

Popular threads in this forum