Team-Xecuter Community
I have used choi NX to update FW twice without any problems. Most recently went from 7.0 to 8.1 a few months ago.
This time, following what appeared to be a successful FW update from 8.1.0 (SX OS 2.9.2) to 9.1.0 and SX 2.9.4 beta, I am getting the Nintendo and Switch splash screens followed by SX error screen 2168-0002.
I understand this is an issue with the SD card and choiNX may have created, deleted or modified something. The only thing I've tried is getting the newest hekate .bin and adding to the SD root, and then to the bootloader>payloads folder, both of which have not worked. If anyone can give some feedback on the SD below I would appreciate it.
Table shows:
-SD root folder structure
-bootloader folder structure (the ini, payloads, and sys folder are all empty)
-hekate_ipl on sd root
- hekate_ipl in bootloader folder
This time, following what appeared to be a successful FW update from 8.1.0 (SX OS 2.9.2) to 9.1.0 and SX 2.9.4 beta, I am getting the Nintendo and Switch splash screens followed by SX error screen 2168-0002.
I understand this is an issue with the SD card and choiNX may have created, deleted or modified something. The only thing I've tried is getting the newest hekate .bin and adding to the SD root, and then to the bootloader>payloads folder, both of which have not worked. If anyone can give some feedback on the SD below I would appreciate it.
Table shows:
-SD root folder structure
-bootloader folder structure (the ini, payloads, and sys folder are all empty)
-hekate_ipl on sd root
- hekate_ipl in bootloader folder
| SD root structure: backup bootloader config Firmware 9.1.0 goldleaf Nintendo switch sxos boot.dat Goldleaf.nro hekate_ctcaer_5.1.3.bin hekate_ipl icense.dat | bootloader folder structure: ini payloads sys hekate_ipl |
hekate_ipl configuration file in bootloader folder: [config] autoboot=0 autoboot_list=0 bootwait=3 verification=1 backlight=100 autohosoff=0 autonogc=1 updater2p=0 | hekate_ipl in SD root: [stock_DANGEROUS] [PreventGCUpdate] kip1patch=nogc |