Hacking Switch Update 5.0.1 Released

[TheCyberQuake]

As opposed to illegitimate bug fixes



The majority seem to be just obliterating the USB-C port.

A boot loop doesn't shout "damaged usb c port" to me. And given the fact that some people have had charging issues without a third party dock in 5.0.0 points to these problems being at least enhanced by 5.0.0

 

[HexZyle]

There once was a USB-C
What an electric fellow was he
The Switch was so stable
'Til a third party cable
And a cheap dock that comes fuse-free

When your charger stops charging, just hate
On the most recent firmware update
To back up your save
Is a feature you'll crave
When your Switch is a nice paperweight

 

[TotalInsanity4]

There once was a USB-C
What an electric fellow was he
The Switch was so stable
'Til a third party cable
And a cheap dock that comes fuse-free

When your charger stops charging, just hate
On the most recent firmware update
To back up your save
Is a feature you'll crave
When your Switch is a nice paperweight

Limericks

Spoiler: I approve

 

[TheCyberQuake]

There once was a USB-C
What an electric fellow was he
The Switch was so stable
'Til a third party cable
And a cheap dock that comes fuse-free

When your charger stops charging, just hate
On the most recent firmware update
To back up your save
Is a feature you'll crave
When your Switch is a nice paperweight

The issue is a blown fuse doesn't cause a boot loop. I've seen them with blown fuses and still boot to home menu while it still has a charge. And a majority of the bricks include a boot loop.
Taking that into account, along with the fact that a huge amount of third party accessories stopped working and even started crashing the switch just by connecting, I don't understand how you can still not believe the 5.0.0 update didn't have some affect on the increased amount of problems revolving around 5.0.0. And given that complaints and bad reviews about bricking after 5.0.0 started vastly increasing, unless they all are time bombs going off at the same time, it's kinda hard to not believe 5.0.0 has had some kind of part in these issues.