Closed xmun2k closed 4 years ago
xmun2k
commented
4 years ago Adding a video link to show you what's going on. Off-screen, the switch is in RCM mode connected to my PC and I push fusee-primary (latest) video TegraRCM.
After the video ends, the screen remains blank.
hrvylein
commented
4 years ago Have you updated all sysmodules? Release notes say every sysmodule has to be compiled against 0.13.
masagrator
commented
4 years ago Have you updated all sysmodules? Release notes say every sysmodule has to be compiled against 0.13.
Not every. Every using atmosphere-libs as core part.
KiraPT
commented
4 years ago Having the exact same issue with my switch, but if I go back to 0.12.0, it solves the issue.
xmun2k
commented
4 years ago Have you updated all sysmodules? Release notes say every sysmodule has to be compiled against 0.13.
I am using a completely vanilla installation. No sysmodules beyond what would be included with the release.
xmun2k
commented
4 years ago Having the exact same issue with my switch, but if I go back to 0.12.0, it solves the issue.
Did you watch the youtube video I linked? Is it exactly the same ?
KiraPT
commented
4 years ago Having the exact same issue with my switch, but if I go back to 0.12.0, it solves the issue.
Did you watch the youtube video I linked? Is it exactly the same ?
Yes. It happens exactly the same.
haganebr
commented
4 years ago Same thing happened to me. Going back to 0.12 fixed it.
xmun2k
commented
4 years ago Same thing happened to me. Going back to 0.12 fixed it.
Could I ask you what FW version your SYSNAND is on?
xmun2k
commented
4 years ago Having the exact same issue with my switch, but if I go back to 0.12.0, it solves the issue.
Did you watch the youtube video I linked? Is it exactly the same ?
Yes. It happens exactly the same.
Could I ask you what FW version your SYSNAND is on?
haganebr
commented
4 years ago Same thing happened to me. Going back to 0.12 fixed it.
Could I ask you what FW version your SYSNAND is on?
SysNAND 8.1.0 EmuNAND 10.0.4
xmun2k
commented
4 years ago Same thing happened to me. Going back to 0.12 fixed it.
Could I ask you what FW version your SYSNAND is on?
SysNAND 8.1.0 EmuNAND 10.0.4
Same as me so. Might be an issue with SysNAND 8.1.0
KiraPT
commented
4 years ago Same thing happened to me. Going back to 0.12 fixed it.
Could I ask you what FW version your SYSNAND is on?
SysNAND 8.1.0 EmuNAND 10.0.4
Same as me so. Might be an issue with SysNAND 8.1.0
My SysNAND is 10.0.4 and my emuNAND is 10.0.4 and the issue is the same. But if I go back to 0.12.0 the issue is fixed. As I've read, it appears the issue is with Hekate. I will test the fix that was released and see if the issue is solved Just for information, my SD is in Exfat and never had an issue with atmosphere or any other CFW, don't think that the issue is caused by the format of the SD, as the previous version works great.
Update: Used the fix from Hekate and was able to boot the Emunand and use it with no issues, but I'm unable to boot Sysnand or stock (no patches applied), gives a blank screen. Doesn't even shows the sept screen...
Update 2: After some reading and some work I was able to fix the issue by using the fix from Hekate and rebuilding the hekate_ipl.ini file. Now it boots SysNand, EmuNand and Stock with no issues.
If it is any help, here's my hekate_ipl.ini file:
[config] autoboot=2 autoboot_list=0 bootwait=2 backlight=100 autohosoff=0 autonogc=1 updater2p=0
[Atmosphere (SYSNAND)] fss0=atmosphere/fusee-secondary.bin kip1patch=nosigchk emummc_force_disable=1 logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_payload.bmp {}
[Atmosphere (EMUMMC)] payload=atmosphere/fusee-primary.bin kip1patch=nosigchk emummcforce=1 logopath=bootloader/bootlogo_emunand.bmp icon=bootloader/res/icon_payload.bmp {}
[Stock] fss0=atmosphere/fusee-secondary.bin stock=1 emummc_force_disable=1 {}
SciresM
commented
4 years ago Turns out fusee/exo2 don't work on units which use new device key generation. Fixed locally, testing with xmun before merge.
What's the issue you encountered?
After Sept splash screen, Switch display goes blank and remains that way. Pressing the power button causes the process to loop.
How can the issue be reproduced?
1) Download Atmosphere 2) Copy contents to SD card 3) Boot to RCM 4) Send fusee-primary payload
Crash Report
No crash reports were created.
System Firmware Version
8.1.0 (tried a fresh SD setup on this) 10.0.3 (originally tried on this version)
Environment?
Additional context?
Tried completely clean installation with no modules or patches completely vanilla.
Tried starting from fresh eMMC
Restoring to Atmosphère 0.12.0 solves the issue.