Hacking SX OS 3.0.5 boot hangs?

[britain4]

Hey guys, modding this Switch has been a rollercoaster so far to say the least but I've learned a lot doing it and seem to be in a decent place with it now. SX Core installed on a patched V1 and glitching working well (although my boot times seem a little longer than some).

I recently updated my sysNAND from 10.1.0 to 10.2.0 for online play (and emuNAND just because) and SX OS to 3.0.5 for compatibility. When 3.0.5 was on there the Switch has failed to boot roughly 50% of the time, seemed to be mainly an emuNAND issue but also happened once with sysNAND, hanging on a black screen either before the Switch logo or the Nintendo logo and requiring a hard reset.

I downgraded my emuNAND to 10.1.0 today and went back to 3.0.4 and it now seems to be booting perfectly again just like it did before I updated it.

Anyone else having the same issues with 3.0.5 (or SX OS updates in general) and any ideas on how to fix this?

 

[Xandroz]

Happened with me the first glitch took alot, and got a few black screens, was working well before

 

[britain4]

Happened with me the first glitch took alot, and got a few black screens, was working well before

Glad it's not just me, not sure if I'm imagining it or if the glitch is actually slightly quicker for me but just the issue of the black screens. Is this still ongoing for you or did it sort itself out?

 

[Basketto]

Is this causing many original fw boot issues? Still undecided on updating.
I use autorcm constantly and am questioning updating stock/sysnand.

 

[Reecey]

Sounds like bad news to me Nintendo must of tried to patch the reset glitch in the latest firmware v.10.2.0 that sx core/lite exploit rely on or certainly made it difficult somehow, this is probably why your getting inconsistent boots.

Edit: my opinion is don’t update to v.10.2.0 until you have further news.

 

[britain4]

Sounds like bad news to me Nintendo must of tried to patch the reset glitch in the latest firmware that sx core/lite exploit rely on or certainly made it difficult somehow, this is probably why your getting inconsistent boots.

Edit: my opinion is don’t update to v.10.2.0 until you have further news.

I’m not sure if it is this, the system glitches fine still (Maybe faster) and boots to the TX bootloader every time.

In addition, it still boots fine if I use 3.0.4 (even on 10.2.0 sysnand which I can’t get my head around)

 

[britain4]

Been testing this evening and it seems to do one boot on, one boot off. Switch it off, it will fail once, hard reset and it works 2nd time every time (so far)

Likewise if you pick restart instead of a cold boot - it seems to boot fine every time

Not sure if that provides any clues

 

[linuxares]

Been testing this evening and it seems to do one boot on, one boot off. Switch it off, it will fail once, hard reset and it works 2nd time every time (so far)

Likewise if you pick restart instead of a cold boot - it seems to boot fine every time

Not sure if that provides any clues

What Firmware does your chip run?
1.3 seem to be the latest one.

Maybe people that have issues got a lower version?

 

[sashka69]

It's not your modchip. It seems to be a problem in boot.dat in general.

I have an unpatched erista (v1) switch running a sx pro dongle and since I updated from 9.2 to 10.2 I have the same problem as you, folks.

On 9.2 i never had any problems booting into my emunand. Now on 10.2 and latest sx OS beta 3.05 I have the black screen very often and have to hard reset. the previous versions of sx os were okay when I was on 9.2.

Just my 2 cents.

 

[britain4]

What Firmware does your chip run?
1.3 seem to be the latest one.

Maybe people that have issues got a lower version?

Mines on 1.3, came with the 3.0.4 boot.dat which was the first one I ever used with it. Apart from the cold boot issue it works absolutely great and the glitching seems to have got quicker as well, it’s quicker than my 360.

It's not your modchip. It seems to be a problem in boot.dat in general.

I have an unpatched erista (v1) switch running a sx pro dongle and since I updated from 9.2 to 10.2 I have the same problem as you, folks.

On 9.2 i never had any problems booting into my emunand. Now on 10.2 and latest sx OS beta 3.05 I have the black screen very often and have to hard reset. the previous versions of sx os were okay when I was on 9.2.

Just my 2 cents.

This does sound like a similar issue - does yours follow any kind of pattern like mine seems to be doing? Restart instead of cold boot working ok for you?

 

[sashka69]

I tried to find a pattern but it's absolute random.

Sometimes it happens after cold boot, sometimes after jumping from sxos boot menu to hekate and vice versa, sometimes after reboot from horizon via power button.
I also saw a weird pixelated hekate screen once after I have chosen hekate 5.33 via sxos payload menu and then the switch froze.

Then it booted all these scenarios perfectly fine as I wanted to confirm the issues.

Absolute random!

--------------------- MERGED ---------------------------

Maybe it's tx's key obfuscation which is kinda broken in this version?!

 

[3DSDSXL]

Hi so is it safe to update the stock os to 10.2.0 if I have sx os 3.05 I want to sign out and delete my accou t on stock but its asking me to update to latest os on stock so my question is if I do that will it break anything ?
Also to the above problem I am on v1.0.10 stock os with sx os 3.05 boots fine no issues switch lite so it its probably stock os 1.0.20 that is the issue? So this means I can't delete my accou t because I don't want to update lol nintendo got us by the b.....

 

[Deleted member 534671]

Hi so is it safe to update the stock os to 10.2.0 if I have sx os 3.05 I want to sign out and delete my accou t on stock but its asking me to update to latest os on stock so my question is if I do that will it break anything ?
Also to the above problem I am on v1.0.10 stock os with sx os 3.05 boots fine no issues switch lite so it its probably stock os 1.0.20 that is the issue? So this means I can't delete my accou t because I don't want to update lol nintendo got us by the b.....

I hope we get an answer soon.

 

[Deleted member 534671]

Here

 

[popy]

I tried to find a pattern but it's absolute random.

Sometimes it happens after cold boot, sometimes after jumping from sxos boot menu to hekate and vice versa, sometimes after reboot from horizon via power button.
I also saw a weird pixelated hekate screen once after I have chosen hekate 5.33 via sxos payload menu and then the switch froze.

Then it booted all these scenarios perfectly fine as I wanted to confirm the issues.

Absolute random!

--------------------- MERGED ---------------------------

Maybe it's tx's key obfuscation which is kinda broken in this version?!

Can you please post your issue with pixalated hekate here: https://github.com/CTCaer/hekate/issues/485
Have the same issue and now also Nyx is not found, maybe we have the same issue!?
PS.: also using SX OS but very first switch model which is RCM exploitable. Seems SX OS 3.0.5 is f...... something up... just my two cents

 

[britain4]

Hi so is it safe to update the stock os to 10.2.0 if I have sx os 3.05 I want to sign out and delete my accou t on stock but its asking me to update to latest os on stock so my question is if I do that will it break anything ?
Also to the above problem I am on v1.0.10 stock os with sx os 3.05 boots fine no issues switch lite so it its probably stock os 1.0.20 that is the issue? So this means I can't delete my accou t because I don't want to update lol nintendo got us by the b.....

I get the boot problem with mine whether I'm using 10.1.0 or 10.2.0 on both sys and emunand so I really think it's more related to SX OS 3.0.5 than the system firmware but I cannot confirm that, that's just my own anecdotal experience and it may behave differently for you.

The update procedure from the TX forums above worked fine for me but again if you update you are stuck using 3.0.5.

I've installed Hekate on mine recently just to try it out - it has the same black screen every other boot issue as the Switch firmware! No idea if any of this is linked.

 

[popy]

When i'll read througth the sx community forums, i think this black screen issue is an issue of sx os 3.0.5.

 

[pausuri]

When i'll read througth the sx community forums, i think this black screen issue is an issue of sx os 3.0.5.

It's looks like is not an consistent issue across most of the SXOS users and it's just affecting a small percentage??

 

[popy]

Downgraded my emunand (which was on 10.2.0 back to 10.1.0) and downgraded SX OS to 3.0.4 beta.
Now the black screen issue is much much less often and also the "pixelated" hekate (after using SX OS) is solved.

So there there is devintily an issue with SX OS 3.0.5 (maybe in regression with hekate).

Hope xecutor is aware of this and will bring a fix soon.

 

[pausuri]

Downgraded my emunand (which was on 10.2.0 back to 10.1.0) and downgraded SX OS to 3.0.4 beta.
Now the black screen issue is much much less often and also the "pixelated" hekate (after using SX OS) is solved.

So there there is devintily an issue with SX OS 3.0.5 (maybe in regression with hekate).

Hope xecutor is aware of this and will bring a fix soon.

Yeah, sure thing I'm pretty sure that they are aware and (eventually) in a short time future they will release another version that fix these current issues, after all, those SXOS versions are still in BETA