Hacking atmosphere Error Code: 2002-3005

[OggieBoogie]

I downgraded from 20.5.0 to 18.1.0 and now getting error 2002-3005 (program 0100000000000025) when trying to boot atmosphere.
I reinstalled fresh atmosphere 1.9.5, hekate, and sigpatches.
What should i do to fix it? Thanks!

 

[yankii]

You can't downgrade from 20.x.x. Restore a backup or make another emuMMC.

 

[OggieBoogie]

You can't downgrade from 20.x.x. Restore a backup or make another emuMMC.

i dont think i have a backup, can you elaborate on making another emuMMC? im quite clueless

 

[yankii]

i dont think i have a backup, can you elaborate on making another emuMMC? im quite clueless

If you downgraded your emuMMC, you'll have to make another one using Hekate. https://switch.hacks.guide goes into more detail.

If you downgraded your sysMMC and don't have a backup, you'll have to rebuild your NAND and restore it. Look into https://github.com/sthetix/NANDFIX if this is the case.

But you should have a backup if you followed https://switch.hacks.guide, so check first.

 

[OggieBoogie]

If you downgraded your emuMMC, you'll have to make another one using Hekate. https://switch.hacks.guide goes into more detail.

If you downgraded your sysMMC and don't have a backup, you'll have to rebuild your NAND and restore it. Look into https://github.com/sthetix/NANDFIX if this is the case.

But you should have a backup if you followed https://switch.hacks.guide, so check first.

sadly i dont have a backup and seems like i have sysMMC. can I create a emuMMC since its considered safer and less "brickable" (if i understand corrrectly) even that in the past i used sysMMC?
Thanks!

 

[yankii]

sadly i dont have a backup and seems like i have sysMMC. can I create a emuMMC since its considered safer and less "brickable" (if i understand corrrectly) even that in the past i used sysMMC?
Thanks!

Yes, you should use an emuMMC as long as you're not bothered by the slower system loading speeds. It's not less brickable, per se, just easier to recover from as long as your sysMMC is okay.

 

[OggieBoogie]

Yes, you should use an emuMMC as long as you're not bothered by the slower system loading speeds. It's not less brickable, per se, just easier to recover from as long as your sysMMC is okay.

Thank you very much! I will do so

Post automatically merged: Oct 12, 2025

Yes, you should use an emuMMC as long as you're not bothered by the slower system loading speeds. It's not less brickable, per se, just easier to recover from as long as your sysMMC is okay.

soooo it took a while, but i made a new emuMMC, yet when i launch Atmosphere (emuMMC) i still get the same error... it even says im using the same switch firmware (18.1.0). what wrong?

 

[petspeed]

Did you create a emummc from your faulty sysmmc? That won't work. You need to fix your sysmmc first

 

[yankii]

Thank you very much! I will do so

Post automatically merged: Oct 12, 2025

soooo it took a while, but i made a new emuMMC, yet when i launch Atmosphere (emuMMC) i still get the same error... it even says im using the same switch firmware (18.1.0). what wrong?

You need to fix your sysNAND first with NANDFIX, then make an emuMMC.

If you downgraded your sysMMC and don't have a backup, you'll have to rebuild your NAND and restore it. Look into https://github.com/sthetix/NANDFIX if this is the case.

 

[jelbo]

Wait, I made a similar mistake downgrading sysMMC from 20.0.5 to 19.0.1 and could fix it using this:

Post in thread 'Switch not booting into OFW, semi-stock, or SysMMC. error code 2002-3005'

Jun 17, 2025

Easy fix for this - Downgrade as normal and you will get the error code above. You need to then boot into hekate and boot full stock then at the same time hold vol+ and vol- to get to recovery menu. Select factory reset which applies to you and hey presto it will boot properly.

• ConsoleKid69

• 

Actually, I didn't do a factory reset but an update from recovery. That worked fine.