OFW not working on OLED Switch (SX Lite)

[BullsOfLime]

Hello!

Things I have verified:
I received a OLED Switch with installed SX Lite Chip (Burnt Fuses (ODM 7/6): 15 - 0 (HOS: 12.0.2+))
I downloaded the latest HATS Pack, created emuNAND and booted into Atmosphere successfully.

Things that have been told to me (Not verified by me yet!):
SX Light got updated to Spacecraft-NX 0.2.
The OFW does work, if the 3V power cord to the SX Lite Chip gets cut.

Problem:
OFW doesn't start via Hekate -> Reboot -> OFW.
After the "OFW" reboot, the "Nintendo" logo lights up, goes away and nothing happens, until I reset it. (Long press "Power Off/On" button)

Question:
I can't find anything online, that the OFW on the OLED Switch is currently not supported, like I has been told.
CFW (emuNAND SD Partition) is working perfectly fine.

How can I start the OFW?
What could be the problem?
How can I solve it?

 

[thesjaakspoiler]

On Reddit someone mentioned that if AutoRCM is enabled, he can't boot OFW.

 

[Donnie-Burger]

On Reddit someone mentioned that if AutoRCM is enabled, he can't boot OFW.

You cant RCM Oleds.

 

[Donnie-Burger]

Hello!

Things I have verified:
I received a OLED Switch with installed SX Lite Chip (Burnt Fuses (ODM 7/6): 15 - 0 (HOS: 12.0.2+))
I downloaded the latest HATS Pack, created emuNAND and booted into Atmosphere successfully.

Things that have been told to me (Not verified by me yet!):
SX Light got updated to Spacecraft-NX 0.2.
The OFW does work, if the 3V power cord to the SX Lite Chip gets cut.

Problem:
OFW doesn't start via Hekate -> Reboot -> OFW.
After the "OFW" reboot, the "Nintendo" logo lights up, goes away and nothing happens, until I reset it. (Long press "Power Off/On" button)

Question:
I can't find anything online, that the OFW on the OLED Switch is currently not supported, like I has been told.
CFW (emuNAND SD Partition) is working perfectly fine.

How can I start the OFW?
What could be the problem?
How can I solve it?

AMS newest and Hekate newest?

 

[HellsBoyz]

Why do you need to re-flash the SX chip? My SX Lite chip still has original pre-installed software in it (ofc it won't boot to SX OS menu but it works with SX Gear). It works just fine on my Oled without re-flashed to Spacecraft.

 

[mvmiranda]

Hello!

Things I have verified:
I received a OLED Switch with installed SX Lite Chip (Burnt Fuses (ODM 7/6): 15 - 0 (HOS: 12.0.2+))
I downloaded the latest HATS Pack, created emuNAND and booted into Atmosphere successfully.

Things that have been told to me (Not verified by me yet!):
SX Light got updated to Spacecraft-NX 0.2.
The OFW does work, if the 3V power cord to the SX Lite Chip gets cut.

Problem:
OFW doesn't start via Hekate -> Reboot -> OFW.
After the "OFW" reboot, the "Nintendo" logo lights up, goes away and nothing happens, until I reset it. (Long press "Power Off/On" button)

Question:
I can't find anything online, that the OFW on the OLED Switch is currently not supported, like I has been told.
CFW (emuNAND SD Partition) is working perfectly fine.

How can I start the OFW?
What could be the problem?
How can I solve it?

I have a pretty similar issue on one OLED I have here!
I do suspect it's a corrupted NAND because the DAT0 was hard to get giving me red or white lights some times before I properly found it and got a green light. The SX Lite LED always blinked fine.

Finally, the LED turned green and the console booted into Hekate, but I immediately saw some weird stuff was going on.
The battery status displays a very wrong data (but I know the battery was about 70% at that time)


When I try to boot Atmosphere I got the screen below:


I removed the installation and the console is DEAD! Nothing happens when I press power without the 3V3 on the SX Lite.
If I solder the 3V3 again I get the same behavior above!

I dumped the NAND as it was and I've been trying to recreate the NAND with no luck so far. I suspect the current tools doesn't work for OLED NANDs yet.

I'm going to keep this OLED for testing purposes!

Cheers!

 

[Draxzelex]

Hello!

Things I have verified:
I received a OLED Switch with installed SX Lite Chip (Burnt Fuses (ODM 7/6): 15 - 0 (HOS: 12.0.2+))
I downloaded the latest HATS Pack, created emuNAND and booted into Atmosphere successfully.

Things that have been told to me (Not verified by me yet!):
SX Light got updated to Spacecraft-NX 0.2.
The OFW does work, if the 3V power cord to the SX Lite Chip gets cut.

Problem:
OFW doesn't start via Hekate -> Reboot -> OFW.
After the "OFW" reboot, the "Nintendo" logo lights up, goes away and nothing happens, until I reset it. (Long press "Power Off/On" button)

Question:
I can't find anything online, that the OFW on the OLED Switch is currently not supported, like I has been told.
CFW (emuNAND SD Partition) is working perfectly fine.

How can I start the OFW?
What could be the problem?
How can I solve it?

You cannot reboot with Hekate.

 

[Tmonk12]

Did you

Hello!

Things I have verified:
I received a OLED Switch with installed SX Lite Chip (Burnt Fuses (ODM 7/6): 15 - 0 (HOS: 12.0.2+))
I downloaded the latest HATS Pack, created emuNAND and booted into Atmosphere successfully.

Things that have been told to me (Not verified by me yet!):
SX Light got updated to Spacecraft-NX 0.2.
The OFW does work, if the 3V power cord to the SX Lite Chip gets cut.

Problem:
OFW doesn't start via Hekate -> Reboot -> OFW.
After the "OFW" reboot, the "Nintendo" logo lights up, goes away and nothing happens, until I reset it. (Long press "Power Off/On" button)

Question:
I can't find anything online, that the OFW on the OLED Switch is currently not supported, like I has been told.
CFW (emuNAND SD Partition) is working perfectly fine.

How can I start the OFW?
What could be the problem?
How can I solve it?

Did you fix this? I have exactly the same problem. My chip is an OLED specific chip.

CFW boots OK but CFW Sysnand does not boot and the reboot to OFW just seems to switch off the console, no errors or information.

Any ideas?

 

[FR0ZN]

You cant RCM Oleds.

You can set OLEDs in RCM but you can't exploit them this way.

 

[mvmiranda]

You cant RCM Oleds.

You can, in fact, RCM any Switch
But just as @FR0ZN said, you just cannot use it as exploit anymore

 

[Donnie-Burger]

You can, in fact, RCM any Switch
But just as @FR0ZN said, you just cannot use it as exploit anymore

If so be careful trying certain rcm apps. You have been warned.

 

[mvmiranda]

If so be careful trying certain rcm apps. You have been warned.

Yup!
There was an homebrew called ChoiDujourNX that we used back when there was only Erista and some ppl used it on Marikos and ended up with a V2 console in AutoRCM with no easy way of removing it.
Eventually it was sorted out and along acme Daybreak and now it's just sun and flowers
Now Hekate also doesn't allow you to set AutoRCM for patched consoles.

 

[Donnie-Burger]

Yup!
There was an homebrew called ChoiDujourNX that we used back when there was only Erista and some ppl used it on Marikos and ended up with a V2 console in AutoRCM with no easy way of removing it.
Eventually it was sorted out and along acme Daybreak and now it's just sun and flowers
Now Hekate also doesn't allow you to set AutoRCM for patched consoles.

Choi messed up boot. But yeah some apps brick mariko aulu in rcm attempts.

 

[mvmiranda]

Choi messed up boot. But yeah some apps brick mariko aulu in rcm attempts.

That also!
There was a tiny checkbox at the very end of Choi that was used to "install" AutoRCM and if it was left checked in a Mariko console, BAM, you'd be in a though situation

 

[Donnie-Burger]

That also!
There was a tiny checkbox at the very end of Choi that was used to "install" AutoRCM and if it was left checked in a Mariko console, BAM, you'd be in a though situation
View attachment 296352

Yeah. Still get these in for repair.

 

[Donnie-Burger]

That also!
There was a tiny checkbox at the very end of Choi that was used to "install" AutoRCM and if it was left checked in a Mariko console, BAM, you'd be in a though situation
View attachment 296352

So was it actually triggering RCM or messing up boot 0/1 or both?

 

[mvmiranda]

So was it actually triggering RCM or messing up boot 0/1 or both?

Kinda both... you see AutoRCM is made by "bricking" your console by carefully messing around with your BOOT0

 

[Draxzelex]

Did you

Did you fix this? I have exactly the same problem. My chip is an OLED specific chip.

CFW boots OK but CFW Sysnand does not boot and the reboot to OFW just seems to switch off the console, no errors or information.

Any ideas?

You just said CFW boots but CFW SysNAND doesn't. Which one is it?

 

[Kaniky]

Hello, has anyone managed to solve this problem on the oled?

I have one and am currently experiencing this issue.

 

[Bradle6]

Hello, has anyone managed to solve this problem on the oled?

I have one and am currently experiencing this issue.

My reboot and ofw works perfectly fine hwfly v4 latest 7.1 flashed