Everything seems to be working now in 2.6.1, except...

[Pacman`]

Hi, I installed emunand 7.0.1 with SXOS 2.6.1, and SX Installer 1.5 is working better now, thanx

The problem I have now (and with 2.6) is when I boot into SXOS.
If I do the jig thing while the USB cable is plugged into my Switch, TegraRcmGui v2.4 will inject the payload correctly, the SXOS logo will appear, BUT then I'll get a blackscreen.
If I leave the USB cable UNPLUGGED, do the jig thing, plug the USB cable and boot into SXOS, it will work!
Now, in previous SXOS versions, the USB cable being plugged or not never really mattered.
Hope I caught a nice juicy bug

EDIT:
For those wondering, I installed my emunand as FILES on the SD (best way, for many reasons).
Also, my Samsung 256GB EVO SD is formatted as FAT32 for the best possible stability.
Now, I decided to start fresh from my 5.1.0 sysnand and it took 2.5 hrs to create the emunand on my SD.
Next time I do this, I will just copy my 5.1.0 emunand from my PC, and update that, or just update my current emunand to the latest version with ChoiDujourNX. I started from scratch to see if SXOS 2.6 could handle everything (it did).

Originally, I used an Anker 6ft USB-C to USB 3.0 cable connected from my PC to my Switch. My PC's USB3 port also charges the Switch... But today, I realized I didn't test the booting process with my dongle (Trinket M0). So, here it is: Whether the dongle is plugged in or not before I do the jig thing, it will ALWAYS boot into the emunand perfectly.
THE PROBLEM (for me, at least) SEEMS TO BE THE USB CONNECTION as described above originally.

 

[metal921]

Same here have SX Emunand on 6.2 and Sys on 7.0.1 tried sx 2.6 beta and 2.6.1 beta and I get a black screen. Tried to boot the payload directly and same problem. Although after a few times it booted into sys 7.0.1 after injecting the payload. My solution is just stay on 6.2 or make a 6.2 emunand and use the previous version (2.5.3 stable) until they have fixed the bugs. If games require 7.0 the solution to that is to install using SX installer as that ignores firmware requirements

 

[josete2k]

Maybe you have autorcm enabled and you don't power off your console correctly.

 

[Pacman`]

I solved my USB Connection problem by simply using TegraRcmGUI_v2.5.952fb4e_portable (was using v2.4 previously).
Anyways, not sure if doing Install Driver also helped


I tried it TWICE in a row, with the USB cable connected between my PC and Switch
This is the output I got:

No RCM device detected
RCM Device detected
Invoking TegraRcmSmash.exe with args : "C:\Program Files (x86)\Switch Utilities\TegraRcmGUI\favorites\payload.bin"
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \\?\usb#vid_0955&pid_7321#5&2fa0c562&0&2#{aa0dbd45-3117-f331-5c49-76bf65225042}
RCM Device with id 0003070D0000000CC495416401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 27748, total size: 93964, total padded size: 94208)...
Smashing the stack!
Smashed the stack with a 0x7000 byte SETUP request!
Payload successfully injected
RCM device disconnected

RCM Device detected
Invoking TegraRcmSmash.exe with args : "C:\Program Files (x86)\Switch Utilities\TegraRcmGUI\favorites\payload.bin"
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \\?\usb#vid_0955&pid_7321#5&2fa0c562&0&2#{aa0dbd45-3117-f331-5c49-76bf65225042}
RCM Device with id 0003070D0000000CC495416401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 27748, total size: 93964, total padded size: 94208)...
Smashing the stack!
Smashed the stack with a 0x7000 byte SETUP request!
Payload successfully injected
RCM device disconnected

I also noticed that SX Installer has been updated to v1.51.
Hopefully this will help to not crash the Switch if it is left to Timeout.

So, for me, barring any SX Installer 1.51 problem, SX OS 2.6.1 has been a COMPLETE SUCCESS!

 

[cjrocks]

Also confirmed here, on a virgin switch (without any modification), I got a blank screen. Tested on Ubuntu 18.04.

And I confirm that I am in RCM mode while running the payload. (I got a message asking for boot when it is not in the root of the SD)