Atmosphere Error Code: 2162-0002 (0x4a2)

[Gandalf2000]

If you have pirated titles installed to the sysMMC or emuMMC that you are going to update in the system settings, then you will get banned if you connect to Nintendo's servers and update in the system settings.


If you don't have AutoRCM presently installed, then you probably already have a fuse count of 15, which isn't going to change if you update to 13.2.0.

When I boot normally (the only way I can boot right now), I don't have any games installed. Does that help?

 

[Lacius]

When I boot normally (the only way I can boot right now), I don't have any games installed. Does that help?

If you are using an emuMMC, then nothing you do when booting normally is going to help you. Updating your sysMMC is not going to update your emuMMC.

 

[Gandalf2000]

If you are using an emuMMC, then nothing you do when booting normally is going to help you. Updating your sysMMC is not going to update your emuMMC.

Yeah, that's what I thought. So what are my options? Can I revert to an emuMMC backup?

 

[Lacius]

Yeah, that's what I thought. So what are my options? Can I revert to an emuMMC backup?

Yes, that is an option. Now that I know you have an emuMMC and a functional sysMMC, it seems likely the emuMMC has to be repaired/restored. I was confused that you could boot without Atmosphere, but that makes sense if it's booting a clean sysMMC.

Out of curiosity, how are you launching fusee.bin?

 

[Gandalf2000]

Yes, that is an option. Now that I know you have an emuMMC and a functional sysMMC, it seems likely the emuMMC has to be repaired/restored. I was confused that you could boot without Atmosphere, but that makes sense if it's booting a clean sysMMC.

Out of curiosity, how are you launching fusee.bin?

I am putting it in RCM, injecting payload with TegraRcmGUI to hekate_ctcaer_5.6.5.bin then in Hekete, I ignore the "Launch" section and go to "Payloads" where I find fusee.bin

 

[Lacius]

I am putting it in RCM, injecting payload with TegraRcmGUI to hekate_ctcaer_5.6.5.bin then in Hekete, I ignore the "Launch" section and go to "Payloads" where I find fusee.bin

And you replaced fusee.bin with the new one, correct? If you are unsure if you did it properly, try booting using fusee.bin directly.

 

[Gandalf2000]

And you replaced fusee.bin with the new one, correct? If you are unsure if you did it properly, try booting using fusee.bin directly.

Yes. I put the new one in the Bootloader/payloads folder. but I'll try using it with tegra and see what happens

 

[Gandalf2000]

Yes. I put the new one in the Bootloader/payloads folder. but I'll try using it with tegra and see what happens

Same error message

 

[Gandalf2000]

Same error message

Do you have any advice about how to repaire/restore my emuMMC?

 

[soutin3]

I got the same problem.

I solved it deleting the whole EmuMMC folder and creating it again using Hekate.