Hacking Question I Need some serious assistance

[SuperSwifty]

So i was having trouble entering maintenence mode after downgrading from 7.0 to 6.2 my games everything worked fine but the problem arised after i used the hackshop hbg on wifi without any knowledge of a secure way to be avoiding nintendos update servers i tried booting into maintenence mode but auto rcm always rejects the stock boot so then i disabled auto rcm with hetake payload and tried but no luck accidently i tried changing auto boot to hetake but then after i can't use any other payload if i load fusee-primary.bin it works like a atmosphere payload comes on then afterwards a hetake screen shows up resulting in no custom firmware running on 7.0 anyway to change auto setting on my semihacked switch sd card?

 

[Hayato213]

What is your fuse count?

 

[petethepug]

If you see the hekate screen it should still work despite being on 1.0 fw. Even if you haven't upgraded the firmware yet. When I say 1.0 I mean whichever CFW or FW you are on.

 

[SuperSwifty]

What is your fuse count?

Where can i find the fuse count in the hetake menu or the sd card? I can get inside the menu now

 

[Hayato213]

Where can i find the fuse count in the hetake menu or the sd card? I can get inside the menu now

boot up hekate and check with that.

 

[SuperSwifty]

If you see the hekate screen it should still work despite being on 1.0 fw. Even if you haven't upgraded the firmware yet. When I say 1.0 I mean whichever CFW or FW you are on.

I believe i updated on accident it fixed my auto rcm problem but i cant use custom firmware and stuff anymore

 

[Hayato213]

I believe i updated on accident it fixed my auto rcm problem but i cant use custom firmware and stuff anymore

You should be able to get into RCM with a jig and a payload sender.

 

[SuperSwifty]

You should be able to get into RCM with a jig and a payload sender.

May i get a screenshot example of a fuse can't find it in console info.

 

[jorgesd]

May i get a screenshot example of a fuse can't find it in console info.

enter hekate -> console info -> fuse count

 

[petethepug]

You have a backup of your RCM (Or data.inf if I remember right.)

 

[Hayato213]

go into console info and then print fuse info, if your fuse count is 9, and you were on latest firmware and attempt to downgrade to 6.2.0, you can't boot into ofw without a custom bootloader, since mostly likely you updated via system update you burn your fuse.

 

[SuperSwifty]

Here is the fuses i got

--------------------- MERGED ---------------------------

So my fuse is 9 will i ever be able to get in a custom firmware?

 

[Hayato213]

Here is the fuses i got

Yep fuse burn, you need to load via a cfw and update your firmware I guess if you ever want to boot into ofw without a bootloader.

 

[SuperSwifty]

Yep fuse burn, you need to load via a cfw and update your firmware I guess if you ever want to boot into ofw without a bootloader.

Cfw without a bootloader okay sounds good how do i get started Any links or tutorials?

 

[petethepug]

This is the best way I can say this without getting off track or distorted; its likely that the fuses matter but they do not, they are the RAM or memory chips used in the Switch FW or the Hardware, all you can really do is downgrade but if you downgrade you will break the console, the only way to fix the console without updating or breaking the Switch is to completely re-update the software from the original FW you see.



If your confident fixing it you could likely fix your Switch without a hardmod, the only thing I can think of doing is changing the console software to something its not otherwise your doomed if you do not have a backup of your FW or payload (do not update or revert back to old fw.)

 

[Hayato213]

Cfw without a bootloader okay sounds good how do i get started Any links or tutorials?

https://github.com/AtlasNX/Kosmos/releases
https://github.com/Atmosphere-NX/Atmosphere

As for updating Im not sure if you can update via system update again, maybe you are ban from online service, as for updating you can use ChoidujourNX.

 

[petethepug]

As for updating Im not sure if you can update via system update again

You can't update if your stuck on the Hekate screen (i'm going to assume that the screen is a bootloader or a boot cfw screen like Luma CFW for the 3ds.) You will brick if you do because your console is on two instances of a CFW and a new system update. And its likely that an online service could break the switch but it can't necessarly destroy it, I think that's why some console units from manufactors bricked because updating the software did not prove anything (homebrew software with online accsess even "with wifi off")

 

[SuperSwifty]

I'm on 7.0.1 firmware atm update is the reason im in this predictiment i don't have my my old firmware only the one had last downloaded and used before updating which was 6.2 with choji software with atmos payload safe to revert?

 

[Hayato213]

I'm on 7.0.1 firmware atm update is the reason im in this predictiment i don't have my my old firmware only the one had last downloaded and used before updating which was 6.2 with choji software with atmos payload safe to revert?

Just stay on 7.0.1 if you can boot into atmosphere, since your burn your fuse.

 

[petethepug]

I'm on 7.0.1 firmware atm update is the reason im in this predictiment i don't have my my old firmware only the one had last downloaded and used before updating which was 6.2 with choji software with atmos payload safe to revert?

To confirm again (thank you for asking.) No its not safe.