Hacking Possible brick? Swith only displays boot logo then turns of. Hekate loads fine

[grcd]

So, I bought this second hand Switch which the previous owner was very hush-hush about what he did to. All he said was that it had a "defect" and was sold "as-is" in broken condition. I was expecting a device with a hardware fault, but it functions perfectly fine.... except that the OS won't load at all. It cannot even get into recovery/maintenance mode. However, RCM works fine and I can send payloads and go into Hekate. I checked the burnt fuse count, and it seems to have been / or be on 10.0.x.

Is this a perma-brick? If so, how can I identify this? If it is a perma brick, is Lakka the only thing I can run on it?

 

[crazy_p]

I assume you have no Backups, if so follow this Guide.

 

[magico29]

So, I bought this second hand Switch which the previous owner was very hush-hush about what he did to. All he said was that it had a "defect" and was sold "as-is" in broken condition. I was expecting a device with a hardware fault, but it functions perfectly fine.... except that the OS won't load at all. It cannot even get into recovery/maintenance mode. However, RCM works fine and I can send payloads and go into Hekate. I checked the burnt fuse count, and it seems to have been / or be on 10.0.x.

Is this a perma-brick? If so, how can I identify this? If it is a perma brick, is Lakka the only thing I can run on it?[/QUOTE

So, I bought this second hand Switch which the previous owner was very hush-hush about what he did to. All he said was that it had a "defect" and was sold "as-is" in broken condition. I was expecting a device with a hardware fault, but it functions perfectly fine.... except that the OS won't load at all. It cannot even get into recovery/maintenance mode. However, RCM works fine and I can send payloads and go into Hekate. I checked the burnt fuse count, and it seems to have been / or be on 10.0.x.

Is this a perma-brick? If so, how can I identify this? If it is a perma brick, is Lakka the only thing I can run on it?

Make sure to learn what you gonna do, also if any step fails, do not move to next step.
Also do no forget to backup all files(Rawnand.bin,boot0,boot1,sysnand via hekate) just in case you don't have them before try anything.

 

[grcd]

I assume you have no Backups, if so follow this Guide.

Yes. No backups. That sounds hopeful. As magico29 said, I will take full back-ups first. So your recommendation is to install a firmware in accordance with the fuse count and hope for the best?

Make sure to learn what you gonna do, also if any step fails, do not move to next step.
Also do no forget to backup all files(Rawnand.bin,boot0,boot1,sysnand via hekate) just in case you don't have them before try anything.

Failing that, if it doesn't help, what are my other options?

 

[scandal_uk]

Failing that, if it doesn't help, what are my other options?

If you run into more problems, post back here and hopefully we can help diagnose any errors you run into.

 

[magico29]

Yes. No backups. That sounds hopeful. As magico29 said, I will take full back-ups first. So your recommendation is to install a firmware in accordance with the fuse count and hope for the best?



Failing that, if it doesn't help, what are my other options?

Get rawnand.bin and rest of files backups first, as we said. If not, i don't recommend you do any process.

 

[grcd]

Of course! I'll do that first thing. (I always do that first thing anyway!)

 

[magico29]

Of course! I'll do that first thing. (I always do that first thing anyway!)

As soon as finished come back and post.

 

[grcd]

Hi there,

I am reviving this thread as I am about to start trying to fix it (I was busy with other work until now).

I can also confirm that I get on Hekate this error (if it matters):

https://gbatemp.net/threads/pkg2-decryption-failed-after-update-to-9-1-0.555512/

Atmosphere boots with fusee-primary but then throws an error before completing boot process. I am now backing it up as we speak.

 

[grcd]

Hi everyone, I wanted to post an update on this. I tried to follow the process. The Switch booted, and at first I was elated. However, the moment it entered into sleep mode the Switch threw an error (Error code: 2001-0114). Now it is stuck on the logo once again.

EDIT: I have found a way to get the Switch to boot consistently. If I boot Hekate, chain the Lockpick_RCM.bin payload and then use the option from there to boot into the system then it will load fine. The moment it enter sleep mode, it will throw the same error and won't be able to boot normally.

The other interesting thing I found is that the console is unable to find any online networks whatsoever. Could it be that the WiFi module has a problem?

 

[Draxzelex]

Hi everyone, I wanted to post an update on this. I tried to follow the process. The Switch booted, and at first I was elated. However, the moment it entered into sleep mode the Switch threw an error (Error code: 2001-0114). Now it is stuck on the logo once again.

EDIT: I have found a way to get the Switch to boot consistently. If I boot Hekate, chain the Lockpick_RCM.bin payload and then use the option from there to boot into the system then it will load fine. The moment it enter sleep mode, it will throw the same error and won't be able to boot normally.

The other interesting thing I found is that the console is unable to find any online networks whatsoever. Could it be that the WiFi module has a problem?

Most likely it needs to be replaced.