Hacking Switch V1 bricked after using Hekate USB Tool

[Cris1245M]

So I tried to use Hekate USB Tool but my pc didn't recognize the Switch so console freezed and I forced power off, now I can't make it turn on, TegraRCM says No RCM so my switched bricked HELP

 

[Plazorn]

This has happened to me many times, sometimes it fixes on its own. It shouldn't be bricked. maybe try this: https://rentry.org/ExosphereDNSMITM

 

[impeeza]

So I tried to use Hekate USB Tool but my pc didn't recognize the Switch so console freezed and I forced power off, now I can't make it turn on, TegraRCM says No RCM so my switched bricked HELP

Do the next steps and LET US TO KNOW:

• Press the power button FOR 30 SECONDS.
• Connect the console to the original charger directly, no to the dock, for about 1 hour.
• Disconnect the charger
• Press the power button FOR 30 SECONDS.
• press briefly the power button and try to inject the payload.

 

[Jayinem]

Guarantee it's not bricked.

 

[impeeza]

Guarantee it's not bricked.

yeah, using the UMS can discharge the battery so if the battery was low now is completely discharged because on RCM mode the charging is SLOW AS A HELL you need to charge the console long time before to be able to load the console via payload.

 

[Cris1245M]

Do the next steps and LET US TO KNOW:

• Press the power button FOR 30 SECONDS.
• Connect the console to the original charger directly, no to the dock, for about 1 hour.
• Disconnect the charger
• Press the power button FOR 30 SECONDS.
• press briefly the power button and try to inject the payload.

so my switch turned on 3 times since I posted, first time I let it charge all night and the next day I tried the 30s and worked, (before that didn't work) so I thought that my switch was fixed and I turned it off to move some SD files, then I plugged again to my pc to inyect payload and the same issue was happening, so I did the same, let it charge for some hours and then plugging in it, 30s power button and inyecting payload, this time I booted atmosphere but it freezed on black screen after atmosphere logo and after rebooting I had the same issue, so I did the same, now I booted hekate and turned off AutoRCM to see if that's the issue, so I tested the usb tools, freezed again so i forced power off and now can't even boot my switch normally even with autorcm off, so that wasn't the issue, now I'm charging it to test on another pc to see if it's some voltage issue

 

[impeeza]

so my switch turned on 3 times since I posted, first time I let it charge all night and the next day I tried the 30s and worked, (before that didn't work) so I thought that my switch was fixed and I turned it off to move some SD files, then I plugged again to my pc to inyect payload and the same issue was happening, so I did the same, let it charge for some hours and then plugging in it, 30s power button and inyecting payload, this time I booted atmosphere but it freezed on black screen after atmosphere logo and after rebooting I had the same issue, so I did the same, now I booted hekate and turned off AutoRCM to see if that's the issue, so I tested the usb tools, freezed again so i forced power off and now can't even boot my switch normally even with autorcm off, so that wasn't the issue, now I'm charging it to test on another pc to see if it's some voltage issue

I think you have a hardware problem.

 

[linuxares]

Check USB port for bent pins.

 

[ChengXiaoshi]

Guarantee it's not bricked.

Yeah iVe done everything said in this comment section and no sign of life at all. Did it short the cpu or smth?

 

[Jayinem]

Yeah iVe done everything said in this comment section and no sign of life at all. Did it short the cpu or smth?

No that isn't possible at least Hekate couldn't cause it it's just software and has been used for a good 7-8 years now totally safe. Did you fully charge the Switch first? If you use AutoRCM it drains the battery faster.

Also you didnt' describe anything I thought you were OP at first, do you have the drivers installed for your computer to recognize your Switch? Never be afraid to provide details.

 

[TheStonedModder]

Does your system have a modchip in it?

My v1 unit with a trinket m0 has this same quirk. Letting it “rest” for like 30ish min always fixes it for some reason

I always assumed its due to a bad install of a modchip.

 

[ChengXiaoshi]

No that isn't possible at least Hekate couldn't cause it it's just software and has been used for a good 7-8 years now totally safe. Did you fully charge the Switch first? If you use AutoRCM it drains the battery faster.

Also you didnt' describe anything I thought you were OP at first, do you have the drivers installed for your computer to recognize your Switch? Never be afraid to provide details.

I had the exact same issue as op. He actually found my post and then posted his own. Ive fully charged it over night twice with 2 different chargers. Nothing. I have drivers installed, but its not recognised by my pc (im assuming becasue its not booting at all). im on firmware 17.0.1 with latest version of atmostphere. RCM is on, now i couldnt find how to turn it off so i just replaced the hekate bootloader files. ive tried turning it on with vol- with the rcm jig. Without it. Holding it for 30s, holding for 10s. Then tapping it. Idk ever since that day it just hasnt turned on a single time.

Post automatically merged: Oct 31, 2024

Does your system have a modchip in it?

My v1 unit with a trinket m0 has this same quirk. Letting it “rest” for like 30ish min always fixes it for some reason

I always assumed its due to a bad install of a modchip.

nah regular v1. No modchip

 

[josete2k]

Do the next steps and LET US TO KNOW:

• Press the power button FOR 30 SECONDS.
• Connect the console to the original charger directly, no to the dock, for about 1 hour.
• Disconnect the charger
• Press the power button FOR 30 SECONDS.
• press briefly the power button and try to inject the payload.

1. Connect the console to the original charger directly, no to the dock.

2. Press the power button FOR 30 SECONDS.

3. Wait about 1 hour.

4. Disconnect the charger.

5. Press the power button FOR 30 SECONDS.
press briefly the vol+ and power (with your jig) button and try to inject the payload.



Fixed...

 

[Jayinem]

I had the exact same issue as op. He actually found my post and then posted his own. Ive fully charged it over night twice with 2 different chargers. Nothing. I have drivers installed, but its not recognised by my pc (im assuming becasue its not booting at all). im on firmware 17.0.1 with latest version of atmostphere. RCM is on, now i couldnt find how to turn it off so i just replaced the hekate bootloader files. ive tried turning it on with vol- with the rcm jig. Without it. Holding it for 30s, holding for 10s. Then tapping it. Idk ever since that day it just hasnt turned on a single time.

Post automatically merged: Oct 31, 2024

nah regular v1. No modchip

Wait you said 17.0.1 with latest version of Atmosphere, that is incorrect. You need the Atmosphere version specific to 17.0.1, the latest Atmosphere works with 19.0 only.

You need Atmosphere 1.6.2 https://github.com/atmosphere-nx/atmosphere/releases

The sigpatches however you can install the latest, but not Atmosphere.

Delete the entire Atmosphere folder you have on your sd card
Copy Atmosphere 1.6.2
Copy sigpatches into Atmosphere main folder
Retry

 

[ChengXiaoshi]

Wait you said 17.0.1 with latest version of Atmosphere, that is incorrect. You need the Atmosphere version specific to 17.0.1, the latest Atmosphere works with 19.0 only.

Can that brick a system uhhhh...

 

[impeeza]

Wait you said 17.0.1 with latest version of Atmosphere, that is incorrect. You need the Atmosphere version specific to 17.0.1, the latest Atmosphere works with 19.0 only.

Nop, The most recent version of Atmosphère support almost all late firmware versions. I think up to 10

 

[Jayinem]

Nop, The most recent version of Atmosphère support almost all late firmware versions. I think up to 10

Ah thought they were firmware specific, well nevermind then.

He still needs to try to completely delete Atmosphere folder, copy new Atmosphere latest or 1.6.2 and then copy sigpatches into main Atmosphere folder and retry.

 

[impeeza]

If not you will be never able to upgrade your firmware, you should go on this order:

On old firmware, upgrade Atmosphère, then reboot your console.
start the console with old firmware and new Atmosphère.
Upgrade to the new firmware version you like.
Restart the console now with the new firmware and latest Atmosphère.

 

[ChengXiaoshi]

Wait you said 17.0.1 with latest version of Atmosphere, that is incorrect. You need the Atmosphere version specific to 17.0.1, the latest Atmosphere works with 19.0 only.

You need Atmosphere 1.6.2 https://github.com/atmosphere-nx/atmosphere/releases

The sigpatches however you can install the latest, but not Atmosphere.

Delete the entire Atmosphere folder you have on your sd card
Copy Atmosphere 1.6.2
Copy sigpatches into Atmosphere main folder
Retry

1.6.2 is for 17.0.0 and 1.6.3 is for 18.0.0 Oh no, theres no inbetweener

 

[Jayinem]

If not you will be never able to upgrade your firmware, you should go on this order:

On old firmware, upgrade Atmosphère, then reboot your console.
start the console with old firmware and new Atmosphère.
Upgrade to the new firmware version you like.
Restart the console now with the new firmware and latest Atmosphère.

You didn't mention sigpatches, he needs those as well.

Post automatically merged: Oct 31, 2024

Can that brick a system uhhhh...

You need to get it out of your head that these perfectly safe software can brick your Switch, they cannot. No matter how many ways you screw up you just have to figure out how to fix it. This is not brickware.