Hi,
Update 21-Aug-20: There have been report of Incognito normal NRO (not RCM) bricking Lites (and probably Marikos). While I myself find no problem using Incognito, it is worth mentioning that there is a risk out there. If you are skeptical, just use stealth mode or do incognito in Emunand. Worst case is probably you will need to reflash for emunand.
Update 02-Jul-20: TX has noted the issue and pushed a fix to those that 'bricked' their device using Choir. Quoting from @Thejigmaster :
"to fix the brick you have to turn off switch, plug usb into the debug port from sxcore into your computer, your computer will recognize switch as a COM device and the SX core will turn green, you then use sx installer to flash firmware v1.3 to the sx core and put 3.03 boot.dat on sd card it’ll boot now again as normal."
If you have updated SX OS past 3.03, it will be safe to update using Choi now, at least from what TX mentioned.
With more and more people receiving the SX Core, I think we need to have a thread to warn SX Core users, especially on patched switches, which are the tools that should be avoided. I am surprised that this information is not easily available elsewhere, not even in TX forum or pinned in their chat. Anyway here goes:
DO NOT USE (POTENTIAL BRICK, need to reflash):
1. ChoidujourNX. Doesn't matter if you keep autorcm enabled or not. Flash=brick. Not tested in emummc, but please do not try. UPDATE: TX claims that updating past SX OS 3.03 makes it safe for you to update again without bricking.
2. Incognito/Wipe serial in Tinfoil. Tested in emummc, your switch will freeze when booting, forcing you to recreate your emummc. I assume using this in sysmmc will result in a brick, please do not try. UPDATE: This feature has been purposely removed from newer versions of Tinfoil for Mariko sets.
3. Lockpick RCM (not sure about the normal non RCM version).
NO EFFECT (No brick, but doesn't work):
1. Hekate
2. Biskeydump
3. Emuiibo
4. Edizon
Working (Works based on my own experience, YMMV):
1. JKSV (save backup/restore, others not tested)
2. Tinfoil (do not backup/wipe the serial)
3. Awoo Installer (fork with anti sx code removed)
4. Kefir (ONLY NNID LINKING, please do not perform any other actions)
5. Tesla Overlay (Just the main overlay tested)
6. Incognito (NRO, not the one bundled with Tinfoil, and not the RCM version) PLEASE READ THE AUGUST UPDATE ABOVE
Working (reported to work)
1. Retraoarch
2. Checkpoint
3. moonlight-nx
4. nx-shell
5. sys-con
If anyone is willing to contribute their experience with other tools I am willing to edit my list. Please let this serve as a warning as a lot of users have already got their Mariko set bricked, after installing SX Core.
Update 21-Aug-20: There have been report of Incognito normal NRO (not RCM) bricking Lites (and probably Marikos). While I myself find no problem using Incognito, it is worth mentioning that there is a risk out there. If you are skeptical, just use stealth mode or do incognito in Emunand. Worst case is probably you will need to reflash for emunand.
Update 02-Jul-20: TX has noted the issue and pushed a fix to those that 'bricked' their device using Choir. Quoting from @Thejigmaster :
"to fix the brick you have to turn off switch, plug usb into the debug port from sxcore into your computer, your computer will recognize switch as a COM device and the SX core will turn green, you then use sx installer to flash firmware v1.3 to the sx core and put 3.03 boot.dat on sd card it’ll boot now again as normal."
If you have updated SX OS past 3.03, it will be safe to update using Choi now, at least from what TX mentioned.
With more and more people receiving the SX Core, I think we need to have a thread to warn SX Core users, especially on patched switches, which are the tools that should be avoided. I am surprised that this information is not easily available elsewhere, not even in TX forum or pinned in their chat. Anyway here goes:
DO NOT USE (POTENTIAL BRICK, need to reflash):
1. ChoidujourNX. Doesn't matter if you keep autorcm enabled or not. Flash=brick. Not tested in emummc, but please do not try. UPDATE: TX claims that updating past SX OS 3.03 makes it safe for you to update again without bricking.
2. Incognito/Wipe serial in Tinfoil. Tested in emummc, your switch will freeze when booting, forcing you to recreate your emummc. I assume using this in sysmmc will result in a brick, please do not try. UPDATE: This feature has been purposely removed from newer versions of Tinfoil for Mariko sets.
3. Lockpick RCM (not sure about the normal non RCM version).
NO EFFECT (No brick, but doesn't work):
1. Hekate
2. Biskeydump
3. Emuiibo
4. Edizon
Working (Works based on my own experience, YMMV):
1. JKSV (save backup/restore, others not tested)
2. Tinfoil (do not backup/wipe the serial)
3. Awoo Installer (fork with anti sx code removed)
4. Kefir (ONLY NNID LINKING, please do not perform any other actions)
5. Tesla Overlay (Just the main overlay tested)
6. Incognito (NRO, not the one bundled with Tinfoil, and not the RCM version) PLEASE READ THE AUGUST UPDATE ABOVE
Working (reported to work)
1. Retraoarch
2. Checkpoint
3. moonlight-nx
4. nx-shell
5. sys-con
If anyone is willing to contribute their experience with other tools I am willing to edit my list. Please let this serve as a warning as a lot of users have already got their Mariko set bricked, after installing SX Core.
Last edited by satanicangel,