If I connected my switch (OFW) to the Eshop with burnt fuses (started working but then it crashed and didnt let me in shortly after) am i banned?

[Pae]

I got my switch chipped yesterday and we found out it had burnt fuses, because OFW wasn't booting up (Or Nintendo logo showed up for a few seconds and then black screen or the switch logo would appear but stay there forever), so I am waiting for the technician to contact me and tell me we can finally solve the problem. Today, (early in the morning) somehow OFW started working, which is why i wanted to check if I could still access online functions, so I logged into the Eshop. Some secs later after doing that, the error code 2002-3540 appeared, locking me out of my console. I tried then restarting and going back in, but the same error code kept appearing until it finally only displayed the nintendo logo and then a black screen. I want to know if I'm banned because i am very scared of my old switch which i have many memories with getting banned. Am i banned? (sorry for bad english)

 

[linuxares]

A lot of answers of the error code in this thread - https://gbatemp.net/threads/error-code-2002-3540.635990/

I would suggest you try a fresh new SD Card that is of higher quality.

 

[Pae]

A lot of answers of the error code in this thread -

I would suggest you try a fresh new SD Card that is of higher quality.

The problem is happening with OFW, not CFW. CFW works perfectly.

 

[linuxares]

The problem is happening with OFW, not CFW. CFW works perfectly.

Someone claim it might be something with the modchip like badly connected.

 

[djcraze]

To directly answer your question, error code 2002-3540 is not related to being banned.

 

[Pae]

Someone claim it might be something with the modchip like badly connected.

Thanks, but, on the place where I modchipped my switch they said it was cause of burnt fuses, and checking on hekate (Console Info, HW & Fuses) it appears as:

Burnt Fuses (ODM 7/6) 19 | 0 - HOS: 17.0.0+

As. it says i have 19 burnt fuses (normal for 18.1.0) i am ocnfused, why did they say it is a fuse mismatch if it apparently has enough number of fuses blown?
P.S. They told me they will fix it next update, how?

 

[linuxares]

Thanks, but, on the place where I modchipped my switch they said it was cause of burnt fuses, and checking on hekate (Console Info, HW & Fuses) it appears as:

Burnt Fuses (ODM 7/6) 19 | 0 - HOS: 17.0.0+

As. it says i have 19 burnt fuses (normal for 18.1.0) i am ocnfused, why did they say it is a fuse mismatch if it apparently has enough number of fuses blown?
P.S. They told me they will fix it next update, how?

Fuses gets burnt when you boot OFW. Fuses haven't been a issue since forever.
So even if you go from 1.0.0 to 18.1.0 it will just burn the needed fuses during boot.

The freezing in staying forever could be issue with the Wifi circuit, but it often goes Yellow screen after a while. I'm sadly not sure what might be the issue.

Which chip do you run and is it the latest version on it?

 

[Pae]

Fuses gets burnt when you boot OFW. Fuses haven't been a issue since forever.
So even if you go from 1.0.0 to 18.1.0 it will just burn the needed fuses during boot.

The freezing in staying forever could be issue with the Wifi circuit, but it often goes Yellow screen after a while. I'm sadly not sure what might be the issue.

Which chip do you run and is it the latest version on it?

I believe it is a Picofly beacuse of the No SD card screen. Technicians told me it was the HWFly v7 (does not even exist yet). I am running Hekate 6.2.1. Is there a way to identify the chip I'm in further?

Post automatically merged: Aug 5, 2024

To directly answer your question, error code 2002-3540 is not related to being banned.

Thank you! I was deeply worried.

 

[linuxares]

I would honestly try to use the Picofly toolbox and update it to the latest fw and see if that helps.

https://github.com/rehius/usk/releases

 

[Pae]

I would honestly try to use the Picofly toolbox and update it to the latest fw and see if that helps.

Updated Picofly fw to latest, now OFW reads "Pkg2 read failed! Failed to launch HOS! Press any key..."

 

[linuxares]

hmm... boot0 or boot1 broken perhaps?
I would ask in the Picofly thread.

 

[Pae]

hmm... boot0 or boot1 broken perhaps?
I would ask in the Picofly thread.

Also tried booting from Lockpick, i got a purple screen.