Hacking SWITCH NOOB PARADISE - Ask questions here

[britain4]

Hey all, getting an error when booting Atmosphere 1.3.0 on my Switch through Hekate 5.7.2 -

Title ID 010041544D530000
Error std : abort (0xFFE)

Rolling back to Atmosphere 1.2.6 it all works normally again. Both sys and emuMMC are on 13.2.1

Have tried removing all files from my SD card apart from totally fresh copies of Hekate, Atmosphere and my emuMMC and it's still got the issue. Same thing happens on both sysMMC and emuMMC, fusee and FSS0.

I'm on FAT32 and this is the first time it's given me an issue with any updates. I know 1.3.0 is a pre-release just now so anyone else having the same problem with it?

Looking into it more, it looks like it's the presence of my emuMMC on the card that's causing the issues, whether it's enabled in Hekate or not. It also causes the above error when booting CFW on sysMMC.

It does still however work absolutely fine in AMS 1.2.6, which suggests an AMS issue or an issue with my emuMMC - I cleared the serial in Incognito on there when I first set the emuMMC up ages ago under SXOS, it's file based and also resized to about 8gb ish so plenty of potential to go wrong but nothing to explain why it still works fine under 1.2.6

 

[binkinator]

@binkinator Thanks for you help. However, I think you misunderstood my first question. Can you tell me, if I can just use the V1 emunand for the OLED cfw? Or will I have to setup a completely new emunand for the OLED?

Reusing an emunand from another machine will not be good. Recommend you copy directly from the OLED SysNand to create a new EmuNand.

 

[binkinator]

Hey all, getting an error when booting Atmosphere 1.3.0 on my Switch through Hekate 5.7.2 -

Title ID 010041544D530000
Error std : abort (0xFFE)

Rolling back to Atmosphere 1.2.6 it all works normally again. Both sys and emuMMC are on 13.2.1

Have tried removing all files from my SD card apart from totally fresh copies of Hekate, Atmosphere and my emuMMC and it's still got the issue. Same thing happens on both sysMMC and emuMMC, fusee and FSS0.

I'm on FAT32 and this is the first time it's given me an issue with any updates. I know 1.3.0 is a pre-release just now so anyone else having the same problem with it?

Looking into it more, it looks like it's the presence of my emuMMC on the card that's causing the issues, whether it's enabled in Hekate or not. It also causes the above error when booting CFW on sysMMC.

It does still however work absolutely fine in AMS 1.2.6, which suggests an AMS issue or an issue with my emuMMC - I cleared the serial in Incognito on there when I first set the emuMMC up ages ago under SXOS, it's file based and also resized to about 8gb ish so plenty of potential to go wrong but nothing to explain why it still works fine under 1.2.6

https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/post-9786899

very similar issue (010041544D530000) one page back. Did yours dump a new error log?

 

[binkinator]

https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/post-9786899

very similar issue (010041544D530000) one page back. Did yours dump a new error log?

@britain4 @bupeapoop
Long shot, but can you guys do a Windows check disk on your sd card and the right click eject it carefully afterwords to ensure the file system sanity and try to reboot again?

Type in chkdsk /X /f [sd card letter]: or chkdsk [sd card letter]: /f.

For example, chkdsk /X /f h: or chkdsk h: /f, if your card is in drive letter H.

 

[britain4]

https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/post-9786899

very similar issue (010041544D530000) one page back. Did yours dump a new error log?

It did dump the new error log without issue, and still works fine through 1.2.6, so something has definitely changed in the new release stopping it from working, whether it's a problem with 1.3.0 or our emuMMCs (which something in the new release has revealed) I don't know though.

Will try your suggestion in the other post, thanks for taking a look at it!

 

[binkinator]

It did dump the new error log without issue, and still works fine through 1.2.6, so something has definitely changed in the new release stopping it from working, whether it's a problem with 1.3.0 or our emuMMCs (which something in the new release has revealed) I don't know though.

Will try your suggestion in the other post, thanks for taking a look at it!

Yeah man, we went through several things searching for clues about that same error number. Seems to be a bit generic. Mind posting your error log? Maybe a clue in there.

 

[britain4]

Yeah man, we went through several things searching for clues about that same error number. Seems to be a bit generic. Mind posting your error log? Maybe a clue in there.

No worries cheers, I've seen stuff about card corruption (in such a way it affects 1.3.0 but not 1.2.6?), setting archive bit (which I've done), chkdsk came back with no errors.

I've attached the error report here in case that tells you anything further, I've got no idea how to read it haha. Thanks for looking at it!

Edit: Had the wrong error attached! So just reuploaded the correct one

 

[britain4]

Ok so... I created a Github issue as I could switch between 1.2.6 and 1.3.0 and replicate the behaviour consistently each time.

You'll never guess what the issue was... my emummc path was set to emummc\Nintendo_emu. It should apparently be emummc/Nintendo_emu. Apparently 1.3.0 no longer likes this so one incorrect forward slash was causing it to fail to load!! Had this same config for nearly 2 years now and it's been fine haha

 

[binkinator]

Ok so... I created a Github issue as I could switch between 1.2.6 and 1.3.0 and replicate the behaviour consistently each time.

You'll never guess what the issue was... my emummc path was set to emummc\Nintendo_emu. It should apparently be emummc/Nintendo_emu. Apparently 1.3.0 no longer likes this so one incorrect forward slash was causing it to fail to load!! Had this same config for nearly 2 years now and it's been fine haha

No fricking way! You’re right…would have NEVER guessed that. That’s kinda wild.

I wonder if others like @bupeapoop have a similar directionally challenged slash…

here it is for anyone who is curious:

 

[Draxzelex]

Hi everybody !
I'm back with another weird issue. Pretty much, I was able to grab my hand on another CFW Switch. I did the emummc setup etc earlier, no issue. I've put the sigpatches from the GBA Temp thread, no issue.

So I wanted to put my dumped Sword / Shield stuff to be able to have them digital (as always). The mistake i've done (i mean the only thing I can see) has been to install the DLC before installing the game.

I've dumped my game, installed everything, but every time I try to run the game, it does the check and say something installed is not valid (the DLC). I've no issue running the game, but no way to get the DLC to work. I've tried to clean the tickets, re-installing everything but no way.

Edit : For more infos, i'm running on 14.0.0

Any help ? Thanks o/

Let's back up here because a lot of information isn't clear from your post. You say you dumped your game to have it digital; does that mean you dumped a physical cartridge then installed that? And when you say you installed the DLC, was the DLC pirated or legitimate? Finally, is any of this installed on sysMMC or did you only install this in emuMMC?

 

[Rick Astley]

Let's back up here because a lot of information isn't clear from your post. You say you dumped your game to have it digital; does that mean you dumped a physical cartridge then installed that? And when you say you installed the DLC, was the DLC pirated or legitimate? Finally, is any of this installed on sysMMC or did you only install this in emuMMC?

I don't go for the pirate games way, I just CFW for the tools and also being able to put my games without having to deal with my cartridges.
So everything is dumped from my other CFW Switch. The Sword is a cartridge and works fine on the 2nd CFW Switch.

The DLC are my DLC that i've bought day one, dumped, and works fine on Yuzu for example.
Everything on my emuMMC, i've put some sig patches because it's the easiest way for me to play my dumped stuff in the end haha.
So everything is clean, I can redump everything X times if necessary

 

[Draxzelex]

I don't go for the pirate games way, I just CFW for the tools and also being able to put my games without having to deal with my cartridges.
So everything is dumped from my other CFW Switch. The Sword is a cartridge and works fine on the 2nd CFW Switch.

The DLC are my DLC that i've bought day one, dumped, and works fine on Yuzu for example.
Everything on my emuMMC, i've put some sig patches because it's the easiest way for me to play my dumped stuff in the end haha.
So everything is clean, I can redump everything X times if necessary

Can you be a bit more specific on the message you get regarding something is not installed? Perhaps there is an error code attached to it?

 

[Constellation45]

What is the latest Switch firmware, where I can install Pokemon Sword and Shield 1.2.0 version? I have the most recent one, but It doesn't let me install anything, but the newest update.

 

[Rick Astley]

Can you be a bit more specific on the message you get regarding something is not installed? Perhaps there is an error code attached to it?

No error message, it's the verification process of something installed but non working. You have the option to run the game without caring (so you launch Sword, with the update but without the dlc) or it asks to go online to check what's going on (lol nope)
No corrupted file, nothing else, nothing more.
It seems to be related to sig patches not working with the DLC here, but I've tried the ones from here and from Github, still getting that error only for the DLC and not the game itself.

If the sig patches are clean, the only issue I see is the fact i've installed the two DLC BEFORE the game itself (because I had the DLC stored on my pc, not the game), but I'm not sure if it'd be a real issue ?

 

[Draxzelex]

No error message, it's the verification process of something installed but non working. You have the option to run the game without caring (so you launch Sword, with the update but without the dlc) or it asks to go online to check what's going on (lol nope)
No corrupted file, nothing else, nothing more.
It seems to be related to sig patches not working with the DLC here, but I've tried the ones from here and from Github, still getting that error only for the DLC and not the game itself.

If the sig patches are clean, the only issue I see is the fact i've installed the two DLC BEFORE the game itself (because I had the DLC stored on my pc, not the game), but I'm not sure if it'd be a real issue ?

Order doesn't matter when it comes to games, updates, & DLC since they all get combined at the end. I have to ask the million dollar question though: did you install the DLC for the game?

 

[Rick Astley]

Order doesn't matter when it comes to games, updates, & DLC since they all get combined at the end. I have to ask the million dollar question though: did you install the DLC for the game?

The DLC comes with one of the update (which makes the update so big)
My EmuMMC has the combo Game + Update + DLC on it yes :/ I can run the DLC without any issue with that setup on Yuzu for example

 

[PhyChris]

Any good open source Switch ports of 2D Games or 2D engines to 'Play with'

 

[Draxzelex]

The DLC comes with one of the update (which makes the update so big)
My EmuMMC has the combo Game + Update + DLC on it yes :/ I can run the DLC without any issue with that setup on Yuzu for example

As in the update is bundled with the DLC? I have the game, DLC, & update too but the update and DLC technically add different content to the game. The update contains all of the Pokemon while the DLC has the new areas. Normally just installing the update doesn't give you the content from the DLC.

 

[Rick Astley]

As in the update is bundled with the DLC? I have the game, DLC, & update too but the update and DLC technically add different content to the game. The update contains all of the Pokemon while the DLC has the new areas. Normally just installing the update doesn't give you the content from the DLC.

It 100% does, pretty much the DLC file itself is just a little check to unlock everything in game.
The DLC file is a ridiculous low size file, while the update with the DLC were 2GB+ (also as we work in the datamine on this stuff, no doubt on what you need in the end)

+ This setup allows me to use the DLC without any issue with Yuzu as said, so no double check to be double sure of that yeah.

Last point haha, if I run the game with the update (and no DLC check) the games read the maps of the both areas 100% fine. Just can't access to them

Edit : Could it be because I've installed these DLC nsp to the SD Card rather than the NAND (which i guess is the nand of the emummc) with Goldleaf ?

 

[Game_Fr3akz]

i used jksv to back up save from old switch then i restored save on new switch but i don't see my save being update? am i doing it all wrong?