Closed hazzzy closed 4 years ago
facing same problem here
I have the same problem as you. When I formatted the tf card, it was solved.
I’m having this same issue any way to solve it formatted sd card problem still occur
i solve the problems using this tutorial Cleanup the NAND first - https://www.youtube.com/watch?v=gVjF_MKjSv8 Setup EMUMMC - https://www.youtube.com/watch?v=YW5OxN4SzUQ use the files give in the description of video work perfectly now
I personally would recommend against using video guides, as they get outdated rather quickly.
Also, this doesn't fully sound like a clean atmosphere install
awoo installer, (...) goldleaf, (...) sigpatch-updater
(...) kosmos sigpatches (...)
Piracy is not supported.
Bug Report
Hi, I really have no idea where else I'd report this first so I'll try my luck here. This issue is sort of weird and it only occasionally happens (although almost guaranteed lately), most often after rebooting from CFW into hekate and then trying to boot into CFW again.
What's the issue you encountered?
Switch gets stuck while booting emuMMC after the "Nintendo Switch" logo fades out. The screen is blank and the backlight is turned ON. The Switch does not respond to any button presses or combinations and needs to be force-shutdown by holding the power button for ~10 seconds. If left untouched for some time while it is stuck, the backlight does turn OFF, but turns ON again immediately after pressing any button or touching the screen.
Additionally, I've sometimes had an issue where after force-shutdown and reboot, the switch gets back into RCM after the sept logo.
How can the issue be reproduced?
restart
option in power menu (holding power button for ~3 seconds) (I've noticed that this also happens if I shutdown and inject hekate again manually)Crash Report
crash_reports
andfatal_errors
folders are empty/don't existSystem Firmware Version
9.2.0
Environment?
Additional context?
Additional info about your environment:
This is a newly hacked switch and this has been happening for a while, although I can't really remember for how long, could be from the very start. The firmware that was installed before the hacking was 9.1.0. After setting up atmos (or kosmos), I've updated the firmware to 9.2.0 with ChoidujornX on both emuMMC and stock sys. I haven't had any issues with stock sys.
The sdcard used is Toshiba Exceria 128gb. I've tested it multiple times on both Windows(with h2w) and linux (with f3) and all the times there were 0 errors or issues. I've done the emuMMC setup in 3 different ways just to rule out that as well:
At first my setup was the latest Kosmos. After experiencing these issues I've tinkered with Kosmos and tried different things from using sigpatches and different booloader configs to removing modules and homebrew, but to no avail. After that I've done a manual atmos setup with hekate + kosmos sigpatches + some sys modules like sys_con. This also produced the same behaviour, so I removed the sys_modules. It seemed as it would work for a while with no issues (maybe for a week) before I randomly started experiencing issues again (I've not modified anything regarding atmos or hekate)
My latest setup which I'm basing this report on is the following:
atmosphere/reboot_payload.bin
with hekate's payloadhekate_ctcaer_5.1.3.bin
(renamed to reboot_payload.bin)switch
folder containing previously listed homebrewI've also tried using hekate's "unset archiving bit" option but it made no difference to the problem.
AutoRCM is turned ON
I guess this could also be a hekate issue, sorry if it's not related to atmos