Open dezem opened 1 year ago
These problems are also often resolved by making a fresh mmc image, especially if sysmmc fail (which should never occur and isn't what anyone else in this issue reports). I would try taking a backup and then following an unbrick guide to flash a factory image.
Will do, thanks @SciresM!
I have also tried to recreate the error on my Aula Switch. Without success. However, it would be interesting to know if it is perhaps a faulty SD card port. This could be determined in Hekate via Console Info -> microSD. Look out for errors or poor read rates.
I wanted to share an update from my further troubleshooting in hopes that this may help someone else. As SciresM had mentioned, my problem is very likely unrelated to this issue. If there is a need, I'd be happy to open a new issue.
I started noticing that about 20 seconds after initiating a power off from HOS, that the chip was glitching and launching hekate. When attempting to launch atmosphere from hekate in this state, it always leads to a failed boot (splash, logo, black). In my case the black screen is an actual power off, which would explain my 50% success rate. Any boot after a true power off is 100% successful.
The band-aid solution was to set autohosoff=2 in hekate_ipl.
Have you tried setting autohosoff=0 instead? This way when you shut down from HOS, the system shuts down completely right away. I also have the problem when I restart from HOS menu, try it too
Original version of the switch not waking up/black screen "when put to sleep in dock" 100% of times
Only way to get out of black screen is by hard rebooting holding volume+power until wake and boots in system "not atmosphere"
I started noticing that about 20 seconds after initiating a power off from HOS, that the chip was glitching and launching hekate. When attempting to launch atmosphere from hekate in this state, it always leads to a failed boot (splash, logo, black). In my case the black screen is an actual power off, which would explain my 50% success rate. Any boot after a true power off is >100% successful.
This is normal behavior of the chip and fixes nothing.
Any progress on this issue of just getting stuck on a black screen after updating to 1.5.0/1.5.1? Having the same issues updating AMS to 1.5.0 and 1.5.1 with the same build using Hekate as a bootloader and then using fusee.
Had to downgrade to AMS 1.4.0. Currently running Hekate 6.02 with AMS 1.4.0 on system firmware 15.0.1
Would AMS 1.5.1 work if I update the system software to 16.0.1?
Any progress on this issue of just getting stuck on a black screen after updating to 1.5.0/1.5.1? Having the same issues updating AMS to 1.5.0 and 1.5.1 with the same build using Hekate as a bootloader and then using fusee.
Had to downgrade to AMS 1.4.0. Currently running Hekate 6.02 with AMS 1.4.0 on system firmware 15.0.1
Would AMS 1.5.1 work if I update the system software to 16.0.1?
Exact same issue here. Was going to try updating to 16.0.1 next after a backup, so I'll let you know.
What's the issue you encountered?
Use newest ams release 1.4.0 on my Switch Lite. Then updated from firmware 14.1.2 to 15.0.1. Boot with fusee.bin chainloaded with hekate. I often get blackscreen after the Nintendo Logo. At the moment where the lock screen should pop up. There is only blackscreen with turned on backlight. I musst hold power off for 10 seconds to hard reset the Switch and try it again.
Sometimes it works and boots normaly.
If i downgrade back to 14.1.2 the Switch boots normaly each time. No more blackscreens.
Crash Report
N/A
System Firmware Version
15.0.1
Environment?