Closed GiovanH closed 5 years ago
Update: This is not exactly true. If left alone for a long time (~10 minutes), the switch will occasionally show the Switch logo, boot for another few minutes, and then crash with 2162-0002.
Do you have an exfat card and if so did you install the exfat version of 6.2.0
This sounds to me like the SD card is failing to mount. Future versions of AMS will have bbed7814, which will make it take less time to get to the sad state you're in.
But, yeah, format your SD card as FAT32, or else manually install exFAT firm by fucking with NAND. I'd say use choidujournx, but in order for HBL to load the SD card needs to be readable, which isn't the case.
Exfat Is not recommended anyways due to its fragility
This sounds to me like the SD card is failing to mount. Future versions of AMS will have bbed781, which will make it take less time to get to the sad state you're in.
But, yeah, format your SD card as FAT32, or else manually install exFAT firm by fucking with NAND. I'd say use choidujournx, but in order for HBL to load the SD card needs to be readable, which isn't the case.
This was exactly the case. I was able to boot into full atmosphere by using a second SD card with a bare minimum homebrew setup, and from there installed 6.2.0 ExFat with ChoiDejourNX.
Hopefully others who have this problem will see this and be able fix it quickly. Also, apparently atmosphere loads between the Nintendo logo and the switch logo, so that'll be handy to know for future debugging.
Please mark as resolved.
Just update hekate to the latest version don't delete the bootloader folder rather replace it or you will lose your content in the menu page. if it still doesn't work add the latest patches this will fix it. I know this is a bit late however I had the same issue and haven't figure it out till recently.
Edit: The problem turned out to be mismatched ExFat firmware. Using a FAT32 card fixed the issue and allows you to install ExFat firmware properly. This is unrelated to firmware 6.2.0.
Bug Report
What's the issue you encountered?
Atmosphere can't boot on 6.2.0.
Sequence of events:
How can the issue be reproduced?
Issue occurs consistently on my console.
Crash report?
(If a crash report was created under /atmosphere/crash_reports/, please upload it to gist and paste the link here.)
Unfortunately, no crash reports were generated.
Environment?
The following environment produced the result:
Additional context?
Upgraded from 6.1.0 (with 6.2.0 fuses) to 6.2.0 using ChoiDejour. Stock firmware boots correctly.
Filesystem:
(There are some old ReiNX files, but they are not being used and should not be affecting anything, as far as I'm aware.)