Hacking Updated switch via “Match Version.” Did I burn a fuse?

[MovingxTarget]

So I wanted to play smash with my friend locally, it said I had to match versions.

He was on the latest update, I was on 6.1.0 updated via Choi so no fuses burnt!

I figured it was patching my game not the whole system LOL.

Basically I think it updated my console by taking the update from his switch via Bluetooth.

He wasn’t connected to the internet, nor was I.

It restarted. I still have on Autorcm so it won’t boot.

Did I screw up regarded fuses? Wanted to keep 4.1.0 fuses. I’ll test to see how many fuses are burnt when I get home and have access to a computer, I’m just curious.

Thanks!

 

[SCOTT0852]

I thought if the switch updates it removes autorcm...
If you really kept AutoRCM, then it wouldn't have burnt any fuses because it was never able to actually run Ninty's bootloader.

 

[MovingxTarget]

I thought if the switch updates it removes autorcm...
If you really kept AutoRCM, then it wouldn't have burnt any fuses because it was never able to actually run Ninty's bootloader.

That’s good news. I’m trying to boot my switch now but it won’t turn on.

I guess it just updated the game?

 

[SCOTT0852]

I guess it just updated the game?

No, Match Versions always updates the system too.

 

[Masamune3210]

Might have to update cfw/payloads before 6.2 will boot, but as long as Nin stock bootloader doesn't run no fuses should be burnt

 

[ZachyCatGames]

I thought if the switch updates it removes autorcm...
If you really kept AutoRCM, then it wouldn't have burnt any fuses because it was never able to actually run Ninty's bootloader.

Atmosphere preserves autorcm after updating

 

[annson24]

Atmosphere preserves autorcm after updating

It's good that someone around here accidentally tested it working, heh. I wonder if it also works if we boot atmosphere via hekate and not via fusee-primary.

 

[ZachyCatGames]

It's good that someone around here accidentally tested it working, heh. I wonder if it also works if we boot atmosphere via hekate and not via fusee-primary.

fsmitm is what does it iirc, so it should work through hekate

 

[mrdude]

If your switch won't turn on - keep your finger on the power button for about 12 seconds, then let go. Then press power again and it should turn on.
Sometimes if you turn the switch off and then quickly try to turn it on before giving it time to turn off properly - the software crashes and Turns on (but shows a black screen - but doesn't look like it's on), so holding power for 12 seconds - turns it off again and lets you boot normally.
I've encountered this problem a few times myself.

 

[ZachyCatGames]

If your switch won't turn on - keep your finger on the power button for about 12 seconds, then let go. Then press power again and it should turn on.
Sometimes if you turn the switch off and then quickly try to turn it on before giving it time to turn off properly - the software crashes and Turns on (but shows a black screen - but doesn't look like it's on), so holding power for 12 seconds - turns it off again and lets you boot normally.
I've encountered this problem a few times myself.

It's not turning on because they have autoRCM

 

[mrdude]

It's not turning on because they have autoRCM

Yep mine is chipped - so as long as there's a microsd card in, it boots without needing to attach to a dongle or computer/phone to send the payload. I should have paid more attention to the OP post.

 

[MovingxTarget]

Update: So my switch was updated to 6.2.0 but the fuse count was still at 5. It would only boot when I would send a payload, but then never boot CFW.

It would boot OFW after failing to boot CFW.

I have no idea why it did not burn fuses.

AutoRCM was definitely on cause the switch was refusing to boot without Hekate. However, it would never boot the CFW. Yes, Atmosphere was updated to the latest version

Restored my 4.2.0 backup, still at 5 fuses burnt. Had to wipe my SD because no exFat support on that FW, but I am just happy all my fuses are intact!