black screen Mariko with SX Core, possible hardware issue

[singlet]

Hi,

I had my Mariko version of the switch with SX Core V2 modchip for more than 2 years. Half a year ago, I switched from SX OS to the atmosphere. Everything ran fine till weeks ago; my switch would not turn on anymore, with a few blue blinks then staying white.
At first, I suspected it was a soldering issue, so I resoldered the modchip. The problem still exists. I removed the modchip, and the switch would not boot as well.
So I decided to update the modchip firmware to hwfly 0.7.1. Supposedly it should support the SX Core chip. However, I get like 1 min green blink, then 3 green blinks with 1 red blink.
I managed to use the debug mode of the hwfly firmware, with the diagnostic mode, I found the error code is "BAD00110". I checked their source code, and it means 'ERR_MMC_SEND_OP_COND_FAILED'.
I also tried to use a clean SD card with FAT32 system with Hekate payload, still had a black screen.
I have no clue what to do next, maybe it is a hardware issue beyond the modchip? Or is the NAND damaged?
I would appreciate it If anyone could give me any advice.

 

[impeeza]

Seems communication error with the eMMC, if all connections and measurements (on diode mode) get clear, yes, could be a damaged eMMC chip.

 

[randy_w]

I removed the modchip, and the switch would not boot as well.

Clearly the problem is with your switch console, not the mod chip

 

[singlet]

Clearly the problem is with your switch console, not the mod chip

Seems communication error with the eMMC, if all connections and measurements (on diode mode) get clear, yes, could be a damaged eMMC chip.

Many thanks!

Now I will see if can I get a moded switch fixed by a repair shop.

 

[singlet]

Clearly the problem is with your switch console, not the mod chip

would the upgraded emuNAND prevent the original firmware on eMMC from booting? since it increases the fuse count when I upgrade the firmware?

 

[impeeza]

the mariko have a removable eMMC chip, you can try removing and putting the chip again.

 

[randy_w]

would the upgraded emuNAND prevent the original firmware on eMMC from booting? since it increases the fuse count when I upgrade the firmware?

No, upgrading emunand won't burn fuse because hekate bypasses it.

You will only have problem if your console has more burnt fuses than the firmware on your sysnand requires. However this is unlikely to happen, unless you upgraded your sysnand, booted without hekate and later restored an old nand backup.