Problem (error 2105-0584) after update 15.0.0 on SysNand

[MobiusNero]

Hey everyone, sorry if this was already asked, but I didn't see it anywhere else.

I've updated my Switch from 13.0.0 straight to 15.0.0 (after updating atmosphere and via Daybreak, just like I've been doing it since 6.0. After the update, I got the error in the image.

I've found some fixes for it but they're all assuming that I've had this on an EmuNand, but my atmosphere always was on the SysNand, and, therefore, I assume that they don't work (I kinda don't want to try them and have an expensive brick).

So, please, can you guys help me?

 

[Hayato213]

https://github.com/Atmosphere-NX/Atmosphere/issues/1884

 

[MobiusNero]

So, I've seen this fix, but I'm afraid that creating an EmuNand with this "already-with-error" SysNand will only make things worse.
Are you sure this will help me?
Also, is the cfwaifu method to create an EmuNand reliable? Or can you link me a better one?
Thx in advance

 

[Hayato213]

So, I've seen this fix, but I'm afraid that creating an EmuNand with this "already-with-error" SysNand will only make things worse.
Are you sure this will help me?
Also, is the cfwaifu method to create an EmuNand reliable? Or can you link me a better one?
Thx in advance

You can give cfwaifu guide a try, was your nand a donor before?

 

[MobiusNero]

You can give cfwaifu guide a try, was your nand a donor before?

I kinda don't know what that means, but I assume it is not. I've already bought it with Atmos, so I don't exactly know.

 

[Hayato213]

I kinda don't know what that means, but I assume it is not. I've already bought it with Atmos, so I don't exactly know.

did you bricked your switch before, unbricked via using a donor nand?

 

[MobiusNero]

did you bricked your switch before, unbricked via using a donor nand?

Nope, never bricked it. That's why I'm worried. A lot, actually.
But since this is a soft-brick from what I've searched, I'm not THAT worried.

Post automatically merged: Nov 1, 2022

did you bricked your switch before, unbricked via using a donor nand?

Hey, since I've already bought it with Atmos, is there a way to know if my Nand is donor or not? Just curious.

 

[DiCarvalho]

Hey everyone, sorry if this was already asked, but I didn't see it anywhere else.

I've updated my Switch from 13.0.0 straight to 15.0.0 (after updating atmosphere and via Daybreak, just like I've been doing it since 6.0. After the update, I got the error in the image.

I've found some fixes for it but they're all assuming that I've had this on an EmuNand, but my atmosphere always was on the SysNand, and, therefore, I assume that they don't work (I kinda don't want to try them and have an expensive brick).

So, please, can you guys help me?

The exactly same thing happened to me and I didn't found any way to fix the sysNand.

I've bought the Switch with Atmos already in too, and don't know if it's using donor nand.

@Hayato213, there's a way to discover this?

 

[Hayato213]

Nope, never bricked it. That's why I'm worried. A lot, actually.
But since this is a soft-brick from what I've searched, I'm not THAT worried.

Post automatically merged: Nov 1, 2022

Hey, since I've already bought it with Atmos, is there a way to know if my Nand is donor or not? Just curious.

That is hard to tell, since you don't know what the previous owner did.

Post automatically merged: Nov 1, 2022

Sounds like you guys need newer prodinfo based on the github page I posted earlier, seem like whoever sold you guys those unit didn't use original NAND but rebuilded NAND.

 

[MobiusNero]

Okay, so, if I get a valid Prodinfo donor (from like, the PikaFix unbricking guide), I can attempt this?

 

[DiCarvalho]

Thanks for your answer, @Hayato213 .

The first step of the link that you sent is to creat an emuNand, but once my Switch is already with that error, it doesn't restrain me to use it to create an emunand?

 

[Hayato213]

https://github.com/CaramelDunes/prodinfo_gen

This is only for up to 14.0.0, so unless you guys can go back to lower firmware Im not sure for 15.0.0

 

[MobiusNero]

Thanks a lot, @Hayato213 ! I will look further into it, when I try this, I'll let you and @DiCarvalho know!