Strange behavior from hardmodded Switch

[Deleted member 719522]

Sometimes the battery drains even when it's powered off and I have to wait a few minutes charging it before I can actually use it.

It's configured to boot to Hekate then I load Atmosphere from there but since updating to 18.1 there has been a time when it booted directly to OFW for no apparent reason and another time when Hekate loaded then it shut down.

It's still very much usable but the issues above are a bit inconvenient to deal with.

 

[SylverReZ]

Which chip are you using? Can you tell us the LED light sequence when the Switch is powered?

 

[Deleted member 719522]

Which chip are you using? Can you tell us the LED light sequence when the Switch is powered?

HWFLY 4.0 or 4.1. The LEDs go from purple to green when it's powered on.

 

[SylverReZ]

HWFLY 4.0 or 4.1. The LEDs go from purple to green when it's powered on.

So like purple fading in and out, and then a static green light?

 

[Deleted member 719522]

So like purple fading in and out, and then a static green light?

Yes

 

[SylverReZ]

Yes

That is expected to be normal on HWFLY-NX firmware. Anything other than what you mentioned, could indicate a bad installation (i.e., missing points).

 

[Deleted member 719522]

That is expected to be normal on HWFLY-NX firmware. Anything other than what you mentioned, could indicate a bad installation (i.e., missing points).

Why is this normal for HWFLY-NX firmware?

 

[thesjaakspoiler]

The HWFLY is always on. Even if you turn off the Switch, it drains some power from the Switch.
It's not much but is you leave it for several days you'll notice it.
The Picofly based modchips have the same issue.

It's configured to boot to Hekate then I load Atmosphere from there but since updating to 18.1 there has been a time when it booted directly to OFW for no apparent reason and another time when Hekate loaded then it shut down.

That might be unrelated to that update. The update won't change anything on how the hardware works.
Afaik, the hwfly boots to OFW if it fails to glitch.
It might be a connection going bad that causes this behavior sometimes.
Sometimes the dat0 connector starts giving problems after several years/months/weeks.
A good repair shop can replace the DAT0 adapter with a permanent DAT0 connection.

 

[SylverReZ]

Why is this normal for HWFLY-NX firmware?

Purple means that the payload is being injected, this will take sometime around 2-3 minutes before it finishes. Then afterwards, green will tell you that it was successful.

 

[Deleted member 719522]

That might be unrelated to that update. The update won't change anything on how the hardware works.
Afaik, the hwfly boots to OFW if it fails to glitch.
It might be a connection going bad that causes this behavior sometimes.
Sometimes the dat0 connector starts giving problems after several years/months/weeks.
A good repair shop can replace the DAT0 adapter with a permanent DAT0 connection.

It happened on the day I updated to 18.01 but not again. It if it only happens once a month or whatever then I'll just ignore it.

 

[randy_w]

I've modded many oled consoles and never had any issue with battery drain. I have a launch day oled switch modded with hwfly v4 which i keep as a backup unit, in case any of my modded oled dies i can simply exchange it. It's been sitting on my shelf for like 2 years, just tried to power it up and it's still has about 60% battery. The 3.3V point where the chip gets power from only outputs voltage when motherboard is powered on, so techically it can't drain battery once console is powered off.

One scenario that might cause battery drain is glitching failed for whatever reason and console enters rcm mode. Screen remains black and you think it's off, but motherboard is still powered on and it will drain battery till it's dead. Another scenario is that the system auto powers back on after you turn it off in HOS menu, and it sits at hekate screen and drains battery if auto HOS off is not enabled in hekate.

Updating sysnand will sometimes cause modchip fail to glitch the system, this usually happens at major update (like from 17.0 to 18.0) because iirc the payload modchip writes to emmc gets overwritten. If you are on latest hwfly-nx firmware or using instinct-nx, the chip will usually reinitialize the training session and retrain itself, nothing serious.