Hardware Help with potentially bricked switch?

[dsrules]

G'mornin ~ yes my backup switch is recognized while my bricked one is not I'll try those steps. If it matters I let my switch charge all night (assuring the charger works on other devices first) but I'll try once again.

Also I know this may be an odd question considering it's a hacked switch but would sending it to Nintendo to get it "repaired" be of any use? I'm aware of the costs but would they be able to do anything not knowing it's homebrewed?

it could be either nintendo refuses to fix it if they found out that your Switch is using cfw or they will replace it with a patched Switch if they also couldn't make it to Power on

 

[Justerino]

it could be either nintendo refuses to fix it if they found out that your Switch is using cfw or they will replace it with a patched Switch if they also couldn't make it to Power on

Hmm well if all else fails i may just send it to em. Who knows but im going to try Lacius' last idea in a moment.

 

[Justerino]

HOLY HECK UPDATE! IT WORKS AGAIN! I got my RCM Jig today (even though I thought it was going to arrive yesterday/day before) and that seemed to help. Charging it ALL NIGHT, plugging it into my PC with the jig into RCM mode made it work again!

Only bad thing is it has 12 burnt fuses XD but thank you two SO MUCH!

 

[Lacius]

HOLY HECK UPDATE! IT WORKS AGAIN! I got my RCM Jig today (even though I thought it was going to arrive yesterday/day before) and that seemed to help. Charging it ALL NIGHT, plugging it into my PC with the jig into RCM mode made it work again!

Only bad thing is it has 12 burnt fuses XD but thank you two SO MUCH!

For my own curiosity, does Hekate report that AutoRCM is installed?

 

[Justerino]

For my own curiosity, does Hekate report that AutoRCM is installed?

Apparently it was not on. I have enabled it tho!

 

[Lacius]

Apparently it was not on. I have enabled it tho!

I guess it was bricked one way or another (perhaps it was just a fuse mismatch) and you just weren't entering RCM. If it boots the latest version of Atmosphere, it was probably a fuse mismatch, depending on the system version. If the latest Atmosphere doesn't boot, you should probably restore your NAND backup.

 

[Justerino]

I guess it was bricked one way or another (perhaps it was just a fuse mismatch) and you just weren't entering RCM. If it boots the latest version of Atmosphere, it was probably a fuse mismatch, depending on the system version. If the latest Atmosphere doesn't boot, you should probably restore your NAND backup.

It was 9.1 System, and 10.0 for atmo but i have just updated the sys to the current version using ChoiJour and updated atmosphere as well. Everything is working swimingly! Again, thank you so much <3

 

[Lacius]

It was 9.1 System, and 10.0 for atmo but i have just updated the sys to the current version using ChoiJour and updated atmosphere as well. Everything is working swimingly! Again, thank you so much <3

For future reference, Daybreak is the new recommended way of updating your system version. It's much safer than ChoiDujourNX. If you're already updated, there's no reason to redo it.

 

[Justerino]

For future reference, Daybreak is the new recommended way of updating your system version. It's much safer than ChoiDujourNX. If you're already updated, there's no reason to redo it.

Just got daybreak. Ill be using it from here on out Im not 100% certain that atmos was updated to current version. It looked like 0.13 actually for atmos. Thank you for the tip!