Hacking OFW 11.0.0 SX OS 3.1.0 black screen

[Spkcalv]

I've just came back from a long hiatus and wanted to update to latest supported.

Found some 3.1.0 zip online and updated my boot.dat file on my SD.

Launched sx os completely fine, showing as 3.1.0 then used choidujoir to update to 11.0.0, no issues.

But now I try load up and I get black screens after the SX OS splash screen, I never get to the screen to select firmware and just stuck on black screen.

Sometimes I get sx os splash screen then nintendo logo and black screen.

Sometimes I get stuck on black screen for ages

Sometimes after really long I get back onto OFW.

Anyone got any idea or can help?

 

[AkGBA]

Did you install an unofficial theme ?

 

[Maupiti]

I've just came back from a long hiatus and wanted to update to latest supported.

Found some 3.1.0 zip online and updated my boot.dat file on my SD.

Launched sx os completely fine, showing as 3.1.0 then used choidujoir to update to 11.0.0, no issues.

But now I try load up and I get black screens after the SX OS splash screen, I never get to the screen to select firmware and just stuck on black screen.

Sometimes I get sx os splash screen then nintendo logo and black screen.

Sometimes I get stuck on black screen for ages

Sometimes after really long I get back onto OFW.

Anyone got any idea or can help?

How is your sd card formatted ?

 

[Spkcalv]

Did you install an unofficial theme ?

No nothing

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

How is your sd catd formatted ?

I tried reformatting the sd to exfat and putting back only boot.dat and my serial key file but that didn't work, is exfat not correct?

 

[Maupiti]

No nothing


I tried reformatting the sd to exfat and putting back only boot.dat and my serial key file but that didn't work, is exfat not correct?

Better to use fat32 and you should perform a test to see if there’s no corruption.
Do you have access to Hekate ? if so, you can also perform an “archive Bit set”

 

[Spkcalv]

Better to use fat32 and you should perform a test to see if there’s no corruption.
Do you have access to Hekate ? if so, you can also perform an “archive Bit set”

I formatted to fat32 and that worked!! Thank you so much. It's so strange that I was completely fine with exfat before.

Just 1 thing I noticed, when I hold + and power I no longer get the 3 button menu for "customer firmware, official firmware, options" anymore I can only power button straight into custom firmware, any idea about it?

 

[Maupiti]

I formatted to fat32 and that worked!! Thank you so much. It's so strange that I was completely fine with exfat before.

Just 1 thing I noticed, when I hold + and power I no longer get the 3 button menu for "customer firmware, official firmware, options" anymore I can only power button straight into custom firmware, any idea about it?

Glad you got it working.There’s a good reason why fat32 is recommended over Exfat, to prevent corruption.
As for the menu of Sxos, did you do a “fresh install” after formating to fat32 or just “copy/paste “..?
Are you using AutoRCM ? How do you inject Sxos payload ?
How is you EmuMMC setup? Partition based or sd files ?

 

[evilone]

For me something similar happens all over again, i have a First Day Switch and some times when i completley shut it down it boots to a black screen after splash.
This i can fix when i boot into the SX Bootlooder (+) and start it from there.

This issue appears after version 3 i guess, i readed already alot about and it seems to be an issue with SXOS and the Old switches before Mariko.

 

[Maupiti]

For me something similar happens all over again, i have a First Day Switch and some times when i completley shut it down it boots to a black screen after splash.
This i can fix when i boot into the SX Bootlooder (+) and start it from there.

This issue appears after version 3 i guess, i readed already alot about and it seems to be an issue with SXOS and the Old switches before Mariko.

I also have a day one switch, and the only time I could have this “problem “, is sd card related.., I mean some “corruption “...So a “new fresh install “ is highly recommended. After checking and repairing if necessary the sd card.

 

[evilone]

mmmh.. that sounds strange, because i have with 2 switches the same problem (one time the grey and one time the neon) on the Neon i have a 200GB Sandrisk and on the other 128gb Sandisk.. perhaps the brand?

 

[Maupiti]

mmmh.. that sounds strange, because i have with 2 switches the same problem (one time the grey and one time the neon) on the Neon i have a 200GB Sandrisk and on the other 128gb Sandisk.. perhaps the brand?

I have the neon.., by brand you mean the sd ? I also use sandisk sd cards (a 200 go and a 400 ), and had very fiew issues, except, when I suspected corruption. Did you ever performed a test to check if they are genuine of fake ?

 

[Spkcalv]

I also have a day one switch, and the only time I could have this “problem “, is sd card related.., I mean some “corruption “...So a “new fresh install “ is highly recommended. After checking and repairing if necessary the sd card.

Is all I need for a fresh install after formatting the boot.dat and my license key file?

I did export new boot.dat before I formatted but after I just copied over the same boot.dat

I'm using the xecuter dongle thing btw. AutoRCM has been turned off since before I update to 11.0.0 but since I haven't seen the bootloader since updating I'm not sure but I think no

 

[evilone]

I have the neon.., by brand you mean the sd ? I also use sandisk sd cards (a 200 go and a 400 ), and had very fiew issues, except, when I suspected corruption. Did you ever performed a test to check if they are genuine of fake ?

Yes, i mean with Brand the SD Card. But we have the same, no i never checked if its original or fake as i never had problems with stuff from Amazon it self, but yes it could be possible that true.

I believe that this is true because the issue never appears when i dual boot in atmosphere or the OFW, only in CFW and this since a few updates ago.

I re formated both systems a while ago when i switched from EX-FAT to FAT32.

 

[Maupiti]

Is all I need for a fresh install after formatting the boot.dat and my license key file?

I did export new boot.dat before I formatted but after I just copied over the same boot.dat

I'm using the xecuter dongle thing btw. AutoRCM has been turned off since before I update to 11.0.0 but since I haven't seen the bootloader since updating I'm not sure but I think no

Do a fresh install, Format32, check for corruption,(repair if necessary) install your boot.dat (downloaded and not overwriting on the “old one)” and license key obviously.

Yes, i mean with Brand the SD Card. But we have the same, no i never checked if its original or fake as i never had problems with stuff from Amazon it self, but yes it could be possible that true.

I believe that this is true because the issue never appears when i dual boot in atmosphere or the OFW, only in CFW and this since a few updates ago.

I re formated both systems a while ago when i switched from EX-FAT to FAT32.

I ‘ve read that “even Amazon “ could sell “fake sd cards “, so do a check if it’s genuine or not, Hekate can tell you that by checking in d vendor and model.
And switching from exfat to fat32, could have left some bad sectors.., so do a full test for corruption.

 

[evilone]

Do a fresh install, Format32, check for corruption,(repair if necessary) install your boot.dat (downloaded and not overwriting on the “old one)” and license key obviously.


I ‘ve read that “even Amazon “ could sell “fake sd cards “, so do a check if it’s genuine or not, Hekate can tell you that by checking in d vendor and model.

I will give it a try, thank you =)

 

[Maupiti]

I will give it a try, thank you =)

I edited my previous post, do perform a full check for corruption, as switching from exfat to fat32 could have left “bad sectors”.

 

[3DSBricker]

You probably just didn't select the exFat firmware when updating with ChoiDujourNX. Or it got corrupted.

 

[Maupiti]

You probably just didn't select the exFat firmware when updating with ChoiDujourNX. Or it got corrupted.

It’s enabled by default on choixdujour and, all the discussion is about corruption

 

[3DSBricker]

So that's why I said both. ChoiDujourNX doesn't automatically enable it. It gives you the option for firmware: 11.0.0 & 11.0.0 (exFat)
You need to choose the right one, actually always exFat as it works with FAT32 too. Just an extra driver. In this case, it's more likely corruption as from what I understand, it did boot after updating which also means it is an Erista Switch as Mariko's boot0/1 gets corrupted (fixed in latest SX OS version).

 

[Maupiti]

So that's why I said both. ChoiDujourNX doesn't automatically enable it. It gives you the option for firmware: 11.0.0 & 11.0.0 (exFat)
You need to choose the right one, actually always exFat as it works with FAT32 too. Just an extra driver. In this case, it's more likely corruption as from what I understand, it did boot after updating which also means it is an Erista Switch as Mariko's boot0/1 gets corrupted (fixed in latest SX OS version).

You’re right, sorry, didn’t understood what you meant