Help with un-bricking Switch Lite

[ClementNerma]

Hi there!

I have a Switch Lite with an SX Lite chip that I messed up badly with. Basically, I tried I think the wrong options (I can't recall what they were as it was quite a bit of time ago).

Currently when I boot I get the SX OS logo and then a black screen.

If I hold Vol+ while booting I can fully access SX OS' options, and can even boot to Hekate. But that's when troubles start.

Basically my sysNAND is messed up and I have no backup at all. When I boot any payload, I get various errors, the main ones being about pkg1 and pkg2.

Once I had:

Pkg1 decryption failed!
BEK is missing!
Failed to launch HOS!

I tried countless tutorials and guides and never solved that one.

Currently when I try to boot Atmosphere with a custom pack I found online made to perform the switch from SX OS I get the following message:

Pkg2 decryption failed!
pkg1/pkg2 mismatch or old hekate

Failed to launch HOS!

So it seems like I don't have a pkg1/pkg2 anymore or that they're corrupted. As I said I don't have a single backup (I really messed up at the time).

What can I do about this? Ideally I'd like to run Atmosphere on it (no problem if I can't run commercial titles, if I can that's good but I'm mainly interested in running RetroArch), but I don't know how to solve this mess...

Thanks in advance for your help!

 

[binkinator]

Hi there!

I have a Switch Lite with an SX Lite chip that I messed up badly with. Basically, I tried I think the wrong options (I can't recall what they were as it was quite a bit of time ago).

Currently when I boot I get the SX OS logo and then a black screen.

If I hold Vol+ while booting I can fully access SX OS' options, and can even boot to Hekate. But that's when troubles start.

Basically my sysNAND is messed up and I have no backup at all. When I boot any payload, I get various errors, the main ones being about pkg1 and pkg2.

Once I had:

Pkg1 decryption failed!
BEK is missing!
Failed to launch HOS!

I tried countless tutorials and guides and never solved that one.

Currently when I try to boot Atmosphere with a custom pack I found online made to perform the switch from SX OS I get the following message:

Pkg2 decryption failed!
pkg1/pkg2 mismatch or old hekate

Failed to launch HOS!

So it seems like I don't have a pkg1/pkg2 anymore or that they're corrupted. As I said I don't have a single backup (I really messed up at the time).

What can I do about this? Ideally I'd like to run Atmosphere on it (no problem if I can't run commercial titles, if I can that's good but I'm mainly interested in running RetroArch), but I don't know how to solve this mess...

Thanks in advance for your help!

I’m no expert on this but these guys might be. Have you already checked out this thread?

https://gbatemp.net/threads/nand-rebuilding-for-no-backup-broken-emmc.593995/

 

[ClementNerma]

I’m no expert on this but these guys might be. Have you already checked out this thread?

https://gbatemp.net/threads/nand-rebuilding-for-no-backup-broken-emmc.593995/

This is for rebuilding a NAND, I'm not sure that's what I need? I don't need to boot the OFW after all.

 

[binkinator]

This is for rebuilding a NAND, I'm not sure that's what I need? I don't need to boot the OFW after all.

Not sure I follow what you meant by this statement then:

Basically my sysNAND is messed up and I have no backup at all

Sounds like your Nand is messed up.

Please clarify.

 

[ClementNerma]

Not sure I follow what you meant by this statement then:


Sounds like your Nand is messed up.

Please clarify.

Well if I understand correctly what I've read online the NAND contains the OFW (which I'm not interested in) and optionally a CFW (which requires to have an OFW working), which can ever be on the "sysNAND" or "emuNAND". Since I can't boot in OFW, I suppose my sysNAND is messed up? And that I don't have an emuNAND.

Or did I get something wrong?

 

[binkinator]

Well if I understand correctly what I've read online the NAND contains the OFW (which I'm not interested in) and optionally a CFW (which requires to have an OFW working), which can ever be on the "sysNAND" or "emuNAND". Since I can't boot in OFW, I suppose my sysNAND is messed up? And that I don't have an emuNAND.

Or did I get something wrong?

Sysnand and eMMC are synonymous.
Emunand and emummc are also synonymous (and are an exact copy of Sysnand at a point in time in the past.)

Since your Sysnand is messed up and you don’t have an Emunand and you don’t have a backup of either of them you are out of options.

You need to fix your Sysnand to proceed any further.

 

[Hayato213]

Well if I understand correctly what I've read online the NAND contains the OFW (which I'm not interested in) and optionally a CFW (which requires to have an OFW working), which can ever be on the "sysNAND" or "emuNAND". Since I can't boot in OFW, I suppose my sysNAND is messed up? And that I don't have an emuNAND.

Or did I get something wrong?

OFW and Sysnand CFW share the same NAND, so you should fix it if it broken and if it is fixable.

 

[ClementNerma]

Sysnand and eMMC are synonymous.
Emunand and emummc are also synonymous (and are an exact copy of Sysnand at a point in time in the past.)

Since your Sysnand is messed up and you don’t have an Emunand and you don’t have a backup of either of them you are out of options.

You need to fix your Sysnand to proceed any further.

I see. What does the sysNAND contains in that case? I thought it only contained the OS so it could be overriden any time without any problem, seems like it's not how it works?

Are pkg1/pkg2 part of the sysNAND?

And is emuNAND a separate part of the NAND which lives alongside the sysNAND?

Sorry for the questions but I struggle to fully understand how these work.

EDIT: Also this means that even if I want to install a brand new OS (e.g. Atmosphere) I still need to have a working sysNAND?

 

[linuxares]

Tried updating to latest Hekate and Atmosphere?
Also how is your Sysnand messed up?

 

[ClementNerma]

Tried updating to latest Hekate and Atmosphere?
Also how is your Sysnand messed up?

Yes, I tried.

I think they're messed up as I did many operations on it (I can't recall which ones as it was quite a bit of time ago) but since I only get a black screen when the console starts I guess that means the sysNAND is messed up?

 

[linuxares]

just a blackscreen after you picked Sysnand yeah. I would try to run Lockpick_RCM and try making a backup of your current NAND. Then open it on your PC with with nxnanadmanager and see what you can see.

 

[ClementNerma]

I'll try the guide that was linked earlier (https://gbatemp.net/threads/nand-rebuilding-for-no-backup-broken-emmc.593995/) when I get home and see if it works

 

[binkinator]

I'll try the guide that was linked earlier (https://gbatemp.net/threads/nand-rebuilding-for-no-backup-broken-emmc.593995/) when I get home and see if it works

Trying to make a backup as suggested by @linuxares is a good move. You never know when a fragment might come in handy and once you start down the path of overwriting things to recover them you are also destroying some of the fragments.

 

[ClementNerma]

Trying to make a backup as suggested by @linuxares is a good move. You never know when a fragment might come in handy and once you start down the path of overwriting things to recover them you are also destroying some of the fragments.

Absolutely, I did that on my 3DS and keep the backup preciously. But the Switch Lite was given to me already hacked so I didn't even think about it.

Post automatically merged: Jan 4, 2023

So I tried the tutorial linked, as well as the other one suggested in the related thread (https://gbatemp.net/threads/switch-unbricking-guide-prodinfo-fix-pikafix.578026/) but none work.

The first one requires to have a hacked donor Switch, which I don't have, so I go to the other one to get the first files and I'm required to run prodgen.bin.

But when I try to generate the PRODINFO from donor, I get the following error:

Dumping keys...
Unable to derive master keys for prod.
Master keys... done in 1869 us
Keygen part done in 2545 us

Couldn't set master_key_00

Done in 4136 us

I can't find any help on the "couldn't set master_key_00" message :/

 

[xcheaterx]

Hello my switch lite and hacker with picofly and my switch and black screen lock I can't do anything can you help me please

Post automatically merged: Feb 17, 2024

Hello my switch lite and hacker with picofly and my switch and black screen lock I can't do anything can you help me please

 

[ClementNerma]

If you have a black screen and nothing else (no error message) then you probably messed up somewhere in either the solder of the flashing process. You can open a new thread to get some help

 

[xcheaterx]

If you have a black screen and nothing else (no error message) then you probably messed up somewhere in either the solder of the flashing process. You can open a new thread to get some help

Hello yes I think the chip flashes 1 time blue then 2 times yellow I think rst or clk