Closed ghost closed 5 months ago
Ever messed with "Incognito", "Incognito_RCM", or have exosphere.ini with "blank_prodinfo_sysmmc/blank_prodinfo_emummc" set, or hekate with "cal0blank=1"?
if yes, restore original prodinfo or backup of nintendo switch, or disable those options listed.
if you cannot do either of those then: https://suchmememanyskill.github.io/guides/unbrick/#early-boot-errors https://suchmememanyskill.github.io/guides/unbrick/#mmc-rebuild
exosphere.ini those two parameters were set to 1, after setting them to 0, still same. I did try sometimes with the network cables detached, but they are attached now. Where do i find cal0blank?
mmc i had rebuild earlier.
my hekate_ipl.ini
[config] autoboot=0 autoboot_list=0 bootwait=0 verification=1 backlight=100 autohosoff=2 autonogc=0 updater2p=1
{--- Custom Firmware ---} [CFW (SYSMMC)] fss0=atmosphere/package3 kip1patch=nosigchk emummc_force_disable=1 icon=bootloader/res/sysnand.bmp {}
[CFW (EMUMMC)] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 icon=bootloader/res/emummc.bmp {}
exosphere.ini those two parameters were set to 1, after setting them to 0, still same. I did try sometimes with the network cables detached, but they are attached now. Where do i find cal0blank?
mmc i had rebuild earlier.
redo your mmc rebuild following the guide ( https://suchmememanyskill.github.io/guides/unbrick/#mmc-rebuild ) , but add --mariko to the command line when using emmchacgen
I did exactly that. but i cannot pass the logo screen. I used the gui version, and enable mariko but had 17.0.1 as firmware downloaded (didnt dump from the target switch)
i rebuilded my nand now once more following the lv2 guide from sthetix, and i can still not pass the logo screen.
i rebuilded my nand now once more following the lv2 guide from sthetix, and i can still not pass the logo screen.
Are the prod.keys you're using to "rebuild the nand" dumped from your console? Because them not being from your console probably might probably be the root cause of your problems.
I suppose you're going to have to find a version of lockpick_rcm that is capable of outputting 17.0.0+ keys, as some of the keys EmmcHaccGen uses are console unique.
(which is specifically stated in step 1 of https://suchmememanyskill.github.io/guides/unbrick/#step-1-getting-the-files if you for whatever reason ignored that part thinking it was a suggestion)
i rebuilded nand with my prod.keys. i dump them with lockpick.
This was a HW flaw, we got fixed, now i am able to boot into atmosphere on 17.0.1.
Bug Report
What's the issue you encountered?
From hekate 6.0.7 CFW or OFW Boot with fw 17.0.1 the switch logo gets stuck. In all boot modes same behaviour. Cannot enter Maintenance Mode too.
How can the issue be reproduced?
Install/Rebuild Nand with 17.0.1 on both sysmmc/emummc (e.g. via TegraExplorer). Then Boot via Atmosphere.
Crash Report
I didnt get any crash report from AMS.
System Firmware Version
17.0.1
Environment?
Hekate and also fuse payload. partition-based, emummc and sysnand
Additional context?