Hacking Error in Atmosphere (Happens sometimes when putting to sleep or exiting a game)

[Windsall]

Hi. I'm new to modding and I just did everything today for homebrew (followed guide), got everything to work, booting into the cfw emunand fine.

The problem happens randomly when I put the console to sleep or when exiting a game. It goes to an error screen and I have to restart it.

"
Error Code: 2002-3502 (0x1b5c02)
Program: 01000000000000001000
Firmware: 12.1.0 (etc)

An error has occured.

Please press POWER Button to restart the console normally [...]

If the problem peresists, refer to the Nintendo Support Website.[+ site name]
"

And then it lists tons of stuff, 'General Purpose Registers', and tons of addresses.

It just did it after I deleted software too.
What should I do? Could this have to do with sigpatches? Should I try (re)placing those? I just don't know.

 

[Windsall]

I don't know if it helps to know what's wrong, but I also get this error (rarely) when hekate tries to boot:

"
Failed to mount SD
Missing LP0 (sleep mode) lib!
Missing or old minerva lib!

Update bootloader folder!
"

But the bootloader folder has the latest for hkate. I don't know what those other things are tho.

 

[Tomato123]

Hi. I'm new to modding and I just did everything today for homebrew (followed guide), got everything to work, booting into the cfw emunand fine.

The problem happens randomly when I put the console to sleep or when exiting a game. It goes to an error screen and I have to restart it.

"
Error Code: 2002-3502 (0x1b5c02)
Program: 01000000000000001000
Firmware: 12.1.0 (etc)

An error has occured.

Please press POWER Button to restart the console normally [...]

If the problem peresists, refer to the Nintendo Support Website.[+ site name]
"

And then it lists tons of stuff, 'General Purpose Registers', and tons of addresses.

It just did it after I deleted software too.
What should I do? Could this have to do with sigpatches? Should I try (re)placing those? I just don't know.

0100000000001000 is the ID used for themes. You can delete that inside of atmosphere/contents/ but you won't have a theme. Could also be something wrong with your SD card if it sometimes has weird errors like that. Would likely be best to re-install Atmosphere and Hekate from scratch to be sure there's nothing wrong with them, but that is a last resort if nothing else works.

 

[Windsall]

0100000000001000 is the ID used for themes. You can delete that inside of atmosphere/contents/ but you won't have a theme. Could also be something wrong with your SD card if it sometimes has weird errors like that. Would likely be best to re-install Atmosphere and Hekate from scratch to be sure there's nothing wrong with them, but that is a last resort if nothing else works.

I didn't install any themes. Should I still delete something around the themes to see?

Right now I'm not even able to boot hekate correctly, after putting in the sigpatches again. It's giving me the error from the second post I made, every time.

 

[Tomato123]

I didn't install any themes. Should I still delete something around the themes to see?

Right now I'm not even able to boot hekate, after putting in the sigpatches again. It's giving me the error from the second post I made every time.

Sigpatches don't really have anything to do with hekate. But it sounds like something is seriously wrong with your SD card or even just the files on it. Are you using exFat or Fat32? Fat32 is recommended because exFat is known for causing problems like corruption. But that's not to say that corruption can't happen on Fat32.

 

[Windsall]

Sigpatches don't really have anything to do with hekate. But it sounds like something is seriously wrong with your SD card or even just the files on it. Are you using exFat or Fat32? Fat32 is recommended because exFat is known for causing problems like corruption. But that's not to say that corruption can't happen on Fat32.

fat32. No problems with the sd card.
The sigpatches had a bootloader folder. Could it be something in there? I temporarily stored the bootloader folder just now and could try with just the hekate bootloader folder. Not sure if I need to add anything else.

 

[Tomato123]

I'm guessing you setup an Emunand if you're using those sigpatches. They shouldn't make a difference but I would recommend trying to boot with a fresh bootloader folder from the latest version of hekate.

 

[Windsall]

I'm guessing you setup an Emunand if you're using those sigpatches. They shouldn't make a difference but I would recommend trying to boot with a fresh bootloader folder from the latest version of hekate.

I just did this and it's not working. Still giving me the error from the second post.


Edit: I'm using TegraRcmGui to inject the payload. Could it be that not working well?

 

[Tomato123]

I just did this and it's not working. Still giving me the error from the second post.


Edit: I'm using TegraRcmGui to inject the payload. Could it be that not working well?

You might need to re-format the card then. If you have another card to test with, that would also be a good idea. The files for Hekate and Atmosphere should fit on just about any size card.

Edit: TegraRCMGui is perfectly fine to use, just need to make sure you're using the correct payloads which is just the hekate bin you get in the zip file when you download hekate.

 

[Windsall]

You might need to re-format the card then. If you have another card to test with, that would also be a good idea. The files for Hekate and Atmosphere should fit on just about any size card.

Edit: TegraRCMGui is perfectly fine to use, just need to make sure you're using the correct payloads which is just the hekate bin you get in the zip file when you download hekate.

Yeah I don't know if I wanna erase all the work yet. But I can think about reformatting if I can't get it to work.

I do have another sd card I could try too. (smaller size)

 

[Tomato123]

Yeah I don't know if I wanna erase all the work yet. But I can think about reformatting if I can't get it to work.

I do have another sd card I could try too. (smaller size)

If you do test the other card and it is also not working then there might not be anything else I could suggest. Maybe someone else might be able to suggest something if it comes to that.

 

[Windsall]

If you do test the other card and it is also not working then there might not be anything else I could suggest. Maybe someone else might be able to suggest something if it comes to that.

Ok thanks. At least the idea to try with the other card can be something.
And then I can try again with this one later.

 

[crazy_p]

Try this:

Format your spare SD Card to Fat32.

If your Card is Bigger than 64GB use Switch Army Knife to bypass the Windows Restrictions.

Download Atmosphere, Hekate & Sigpatches or use this Site to download a pre built Bundle.
(You need to Download the Sigpatches separately with the Bundle)

Extract all Contents to your SD Card.
Copy fusee-primary.bin to bootloader/payloads.

Download the following zip File or make your own hekate_ipl.ini File (Or use the one from the Bundle).

Spoiler: hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=1
updater2p=0

[Atmosphere EMU (Hekate)]
emummcforce=1
fss0=atmosphere/fusee-secondary.bin

[Atmosphere SYS (Hekate)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin

[Atmosphere SYS (Fusee)]
payload=bootloader/payloads/fusee-primary.bin

Copy the hekate_ipl.ini File to /bootloader/.

Inject the Hekate Payload.
Go to Launch or Payloads to launch any Payload you like.

If you want to Auto Boot Emunand, go to Options -> Auto Boot -> Atmosphere EMU (Hekate).
If you want to boot to Hekate again, hold the Vol- Button while the Console boots.

If you want to Update your Firmware always Check if Atmosphere & Hekate are compatible.
Update Atmosphere & Hekate to the latest Build then use Daybreak to Update your Firmware.

If you use any Custom Themes keep in Mind to delete the 0100000000001000 Folder in atmosphere/contents
before updating the Firmware.

Additional:
Download Lockpick_RCM.bin and copy it to bootloader/payloads.

In Hekate go to Payloads and launch Lockpick_RCM.bin to dump your Keys (Keep them Save!).
You can use these Keys with Switch Army Knife to convert or patch .nsp's or make NSP Forwarder.
(Copy prod.keys to SAK_64bit/bin or SAK_32bit/bin)

Custom Themes
Download NXThemesInstaller to install Themes on your Switch.
Here's a Site where you can download Themes.

Don't forget to make a Nand Backup in Hekate if you don't already have one.

Have Fun!

 

[Windsall]

Ok I really don't understand. I used my other micro-sd card, formatted it correctly (fat32), put the files from the bundle, and added the sigpatches too, but It's giving me the same error!

Why would it do this? The first time it managed to actually get into the actual hekate, now it boots the sideways one with that error message.

@Tomato123 @crazy_p
Have any idea??

 

[crazy_p]

Try to download them manually. Or use H2testw to check your SD Card.

 

[Windsall]

Try to download them manually. Or use H2testw to check your SD Card.

I tested my bigger card the other day and it verified fine.
I could test this one but it'll take a while too.

What if I try to reformat it to exfat to see if that works?

 

[Tomato123]

Ok I really don't understand. I used my other micro-sd card, formatted it correctly (fat32), put the files from the bundle, and added the sigpatches too, but It's giving me the same error!

Why would it do this? The first time it managed to actually get into the actual hekate, now it boots the sideways one with that error message.

@Tomato123 @crazy_p
Have any idea??

Either you're doing something wrong (Which I doubt but mistakes do happen) or there's something wrong with your Switch. If it's hardware or software I have no idea. I think there are ways to reflash the firmware without booting into Atmosphere but not sure. You also could try boot into Atmosphere using fusee-primary.bin from the Atmosphere github (Which I only recommend if you never want to play online as you will be using Sysnand instead of Emunand.)

Try to download them manually. Or use H2testw to check your SD Card.

I doubt it's an SD card issue at this point. 2 cards having the same issue would be a pretty big coincidence.

 

[crazy_p]

That Error makes no sense the 0100000000001000 Folder is not even present.

Or did Hekate tell something about 1-Bit Mode?
If that's the Case your Micro SD Card connector is either broken or disconnected.

 

[Windsall]

That Error makes no sense the 0100000000001000 Folder is not even present.

Right now the error I'm dealing with is this one:

"
Failed to mount SD
Missing LP0 (sleep mode) lib!
Missing or old minerva lib!

Update bootloader folder!
"

 

[Tomato123]

That Error makes no sense the 0100000000001000 Folder is not even present.

That could suggest firmware issues? Not too familiar on how the Switch firmware works exactly but wouldn't that show it's having trouble reading from the firmware itself and not the SD card?
Only issue with me thinking this is that it doesn't explain the other error as the Switch firmware isn't touched when booting Hekate.