Hacking EMUMMC CFW and problems launching on a 1.0.0 system

snoofly

Well-Known Member
Member
Joined
Aug 18, 2015
Messages
1,013
Trophies
0
Age
53
XP
2,122
Country
United Kingdom
Well if you have successfully setup emummc then you should have the configuration files for emummc present already. Now by default, pegascape will boot reboot_payload.bin from the atmosphere folder, just make sure that you used fusee-primary as your reboot_payload file.

Sent from my SM-N975F using Tapatalk
I just tried this (1.0.0 emummc created from hekate 5.2.0) and renamed fusee-primary to reload_payload.bin
Yes, nereba then boots up Atmosphere but after around 30s comes back with a fatal.
Title ID 01000000000001
std:abort (0xffe)
Power to reboot.

With SXOS emunand, after renaming the SX payload to reboot_payload I get the SX splash followed by the Nintendo Switch logo then a black screen.

Anyone else know what to do to boot 1.0.0 emunands so that I can then run ChoiNX to update them?
I really want to avoid updating sys via choi to a later version and then downgrading it after.
 

annson24

The Patient One
Member
Joined
May 5, 2016
Messages
1,190
Trophies
0
Age
31
XP
1,792
Country
Philippines
I just tried this (1.0.0 emummc created from hekate 5.2.0) and renamed fusee-primary to reload_payload.bin
Yes, nereba then boots up Atmosphere but after around 30s comes back with a fatal.
Title ID 01000000000001
std:abort (0xffe)
Power to reboot.

With SXOS emunand, after renaming the SX payload to reboot_payload I get the SX splash followed by the Nintendo Switch logo then a black screen.

Anyone else know what to do to boot 1.0.0 emunands so that I can then run ChoiNX to update them?
I really want to avoid updating sys via choi to a later version and then downgrading it after.
Do you have any sysmodules? Custom theme? Try running atmosphere again with a clean, vanilla, atmosphere and sept folders.

Sent from my SM-N975F using Tapatalk
 

snoofly

Well-Known Member
Member
Joined
Aug 18, 2015
Messages
1,013
Trophies
0
Age
53
XP
2,122
Country
United Kingdom
You're right.
Actually even before reading this I recalled to ensure I had a clean Atmosphere - I deleted contents folders and recopied Atmosphere from fresh and yes, it now boots!
Cheers & thanks for the quick reply in any case.
Did the same for one titles directory in SXOS so will see if that works.
Current system version: 1.0.0|AMS 0.12.0|E
Nice :)
 
  • Like
Reactions: annson24

annson24

The Patient One
Member
Joined
May 5, 2016
Messages
1,190
Trophies
0
Age
31
XP
1,792
Country
Philippines
You're right.
Actually even before reading this I recalled to ensure I had a clean Atmosphere - I deleted contents folders and recopied Atmosphere from fresh and yes, it now boots!
Cheers & thanks for the quick reply in any case.
Did the same for one titles directory in SXOS so will see if that works.
Current system version: 1.0.0|AMS 0.12.0|E
Nice :)
Cheers! About SXOS, I think it doesn't support v1.0.0 at all. Tried it before and it also didn't boot even with a fresh and clean sxos.

Sent from my SM-N975F using Tapatalk
 

snoofly

Well-Known Member
Member
Joined
Aug 18, 2015
Messages
1,013
Trophies
0
Age
53
XP
2,122
Country
United Kingdom
That's disappointing if so, still yet to try as updating the firmware on Atmos atm.
I wonder if it's possible to update the SX emunand via ChoiDuJour on the PC?
 

annson24

The Patient One
Member
Joined
May 5, 2016
Messages
1,190
Trophies
0
Age
31
XP
1,792
Country
Philippines
That's disappointing if so, still yet to try as updating the firmware on Atmos atm.
I wonder if it's possible to update the SX emunand via ChoiDuJour on the PC?
Check out NxNandManager, you can use it to make an SXOS emunand from your updated atmosphere emummc.

Sent from my SM-N975F using Tapatalk
 

snoofly

Well-Known Member
Member
Joined
Aug 18, 2015
Messages
1,013
Trophies
0
Age
53
XP
2,122
Country
United Kingdom
Thanks again for the help guys.
I'll take a look at NxNandManager

Update - had to rebuild from scratch my Atmosphere emummc as partition instead of file based as it was so slow. I thought that had been fixed but seems not.

Anyway, that's all good now. Running Neutos with the exosphere blanking emummc option.

So now I'm creating an SX OS emunand based off the 10.0.2 emummc with NXNANDManager as try as I might, SX OS 1.0.0 emunand boots up but within seconds of the homescreen appearing none of the inputs work so I can't update it with homebrew.

Will update in an hr or so once complete as to result.

Update 2:
OK after much faffing around with NXNandManager I gave up cos it only supports dumping SX OS emu as a 29Gb file and my SD is on fat32 and I couldn't be bothered splitting and getting the alignments perfect etc.
A much easier way is simply grab the 2.4.1 SXOS boot.dat and boot the 1.0.0 SX OS emunand with that, then use Choi to update to 10.0.2 and then put 2.9.5 back on. Simple.
 
Last edited by snoofly,
General chit-chat
Help Users
  • No one is chatting at the moment.
    K3N1 @ K3N1: https://youtube.com/shorts/PArWUK0WyDQ?feature=share