Hacking Fatal Error 0x4A2 (2162-0002) 0100000000001000

n3IVI0

Member
Newcomer
Joined
Apr 18, 2017
Messages
11
Trophies
0
Age
49
XP
75
Country
United States
I have a non-patched Switch. It was on Atmosphere 14.0 and 10.04 firmware. It started crashing when my daughter would try to play Animal Crossing. So I decided to update to 14.1 and 10.1.0.

I have been stuck in a bootloop where Atmosphere crashes with the above error every time I get to the Home Menu, usually within 5 seconds. I initially tried restoring my newest backup, which was 9.1.0. It crashed with the above error.

I am using DeepSea 1.5.1 and the fss0 method of booting fusee secondary. Partition EMUMMC. SD card is FAT32.

I HAVE NO CUSTOM THEMES OR THEME LOADERS INSTALLED.

I cannot boot any firmware higher than 8.1.0. As soon as I reach the Home Menu, qlaunch crashes with the above error.

Now I know that normally, this is due to a custom theme folder by that name that needs to be deleted - this is not the case with me. No such folder exists.

Here is what I have tried to resolve this:

- restored my oldest backup to 5.1.0. Updated this to 8.1.0. Initialized the console, created an unlinked user account, entered 90DNS for DNS settings. No games installed.
- created a Partition based EMUMMC based on this with which to test.

I can boot into 8.1.0 without any issues or crashes.

Then:

- I have tried multiple firmwares ranging from 9.0.0 to 10.1.0
- I have tried multiple versions of AMS, ranging from 12.0 to 14.1.
- I have tried minimal versions of AMS without sysmodules. Only the barest minimum needed to boot Atmosphere.
- I have tried clearing the archive bit, in Mac, using the command "find /Volumes/SWITCH/ ! -name 'Nintendo' -maxdepth 1 -type d -exec sudo chflags -R arch {} +"
- I have done a full overwrite format of the SD card.
- I have initialized the console under EMUMMC.
- I have tried booting with fusee-primary.
- I have tried using Airplane mode.

I cannot resolve this. I have tried every conceivable combination of firmware and Atmosphere, trying to drill down the cause of the crash. Nothing is working.

What changed from 8.1.0 to 9.0.0 that causes every version of Atmosphere I try to crash with the above error when I reach the Home Menu?

I sure hope someone can figure this out.

I have attached the crash log and dumps.

Thank you.
 

Attachments

  • crash.zip
    718 bytes · Views: 170

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
16,941
Trophies
1
XP
15,873
Country
United States
If you're using an emuMMC, do the following troubleshooting steps:
  1. Make sure the SD card is FAT32.
  2. DELETE all CFW files/folders from your SD card (that would be folders like /sept/ and /atmosphere/)
  3. Download the latest Atmosphere
  4. Download the latest fusee-primary (next to Atmosphere)
  5. Download these signature patches (for Atmosphere v0.14.1)
  6. Put Atmosphere and the signature patches onto your SD card
  7. Set "emummc!enabled = 1" in emummc/emummc.ini
  8. (If not on 10.1.0) Download the 10.1.0 update and put the 10.1.0 folder onto the root of your SD card
  9. Put the SD into your Switch
  10. Enter RCM
  11. Launch Atmosphere using fusee-primary
  12. Check that you've booted into your emuMMC
  13. (If not on 10.1.0) If you're in your emuMMC, open the Homebrew Launcher, preferably using title override (R on a game instead of using the photo album)
  14. (If not on 10.1.0) Boot Daybreak
  15. (If not on 10.1.0) Select the 10.1.0 update. Choose the 10.1.0 exFAT option, even though you're using FAT32.
Also, is there a particular reason you're using an emuMMC?
 

n3IVI0

Member
Newcomer
Joined
Apr 18, 2017
Messages
11
Trophies
0
Age
49
XP
75
Country
United States
Also, is there a particular reason you're using an emuMMC?

Yeah, I was trying to keep my SYSNAND out of harm's way so I could test and try to resolve my issue. I was using my SYSNAND exclusively, but when it started the bootloop, I had to restore a backup. That didn't work, so I restored my 5.1.0 backup. That DID work. So I updated to 8.1.0 once I figured out that firmware would let me in without crashing, and I kept using it as a base to test different firmwares with EMUMMC.
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
16,941
Trophies
1
XP
15,873
Country
United States
Yeah, I was trying to keep my SYSNAND out of harm's way so I could test and try to resolve my issue. I was using my SYSNAND exclusively, but when it started the bootloop, I had to restore a backup. That didn't work, so I restored my 5.1.0 backup. That DID work. So I updated to 8.1.0 once I figured out that firmware would let me in without crashing, and I kept using it as a base to test different firmwares with EMUMMC.
I don't recommend using an emuMMC unless you're wanting to play online or have an ipatched Switch, so follow these steps instead:
  1. Make sure the SD card is FAT32.
  2. DELETE all CFW files/folders from your SD card (that would be folders like /sept/ and /atmosphere/)
  3. Download the latest Atmosphere
  4. Download the latest fusee-primary (next to Atmosphere)
  5. Download these signature patches (for Atmosphere v0.14.1)
  6. Put Atmosphere and the signature patches onto your SD card
  7. (If not on 10.1.0) Download the 10.1.0 update and put the 10.1.0 folder onto the root of your SD card
  8. Put the SD into your Switch
  9. Enter RCM
  10. Launch Atmosphere using fusee-primary
  11. (If not on 10.1.0) Open the Homebrew Launcher, preferably using title override (R on a game instead of using the photo album)
  12. (If not on 10.1.0) Boot Daybreak
  13. (If not on 10.1.0) Select the 10.1.0 update. Choose the 10.1.0 exFAT option, even though you're using FAT32.
 
  • Like
Reactions: Ty_

n3IVI0

Member
Newcomer
Joined
Apr 18, 2017
Messages
11
Trophies
0
Age
49
XP
75
Country
United States
Followed the steps. Atmosphere only. fusee-primary.bin on my injector. Re-installed 10.1.0 using Daybreak, using the FAT32 + exFAT option (I had been doing that).

Same error.

I am, as far as I know, using pure Atmosphere loading environments. The only thing that seems to make a difference is the firmware. 8.1.0 - it works. 9.0.0 and above - it crashes. This was a recent development. I had been running Atmosphere, making regular updates when they became available, and had no problems, apart from the odd sigpatch conflict.

Is there a hardware issue that only affects firmwares above 8.1.0? Is there something particular to Atmosphere that is causing only those firmwares to crash and not 8.1.0 and below?

My daughter told me that before it started crashing, the screen pixellated oddly and then crashed. So I thought, maybe there is something with Animal Crossing that is conflicting with 10.0.4, so I updated. Now it bootloops only. If it is a hardware issue, wouldn't it crash in the same way for any firmware I chose? That's what makes me suspect a software issue.

I am not seeing any hardware issues. Screen works. Card reader works. Plugs in, gets power. Joycons work. Nothing is indicating a hardware failure.

I can boot stock, but stock is 6.01. I can't go higher without burning fuses.

I can get into maintenance mode in 9.0.0, but as soon as it is allowed to boot normally and I get into Home Menu - crash.
 
Last edited by n3IVI0,

n3IVI0

Member
Newcomer
Joined
Apr 18, 2017
Messages
11
Trophies
0
Age
49
XP
75
Country
United States
Whelp, I finally broke down and updated the OFW to 10.1.0. I am getting 2162-0002 errors at the same point when reaching the Home Menu. It appears to be a hardware issue, which sucks, because this is an OG switch with the hardware vulnerability.

Anybody have a bead on where I might lay my hands on a working HAC-001 Switch?
 

Site & Scene News

General chit-chat
Help Users
    T @ tungns: around 50$ per month