Hacking Question Switch Lite Atmosphere CFW on sysNAND

[SephirothPlayer]

I have Switch Lite with SX Lite chip using SX OS and I want to run Atmosphere CFW on sysNAND (not on emuNAND). What should I do?

 

[GCS]

I have Switch Lite with SX Lite chip using SX OS and I want to run Atmosphere CFW on sysNAND (not on emuNAND). What should I do?

The best option is just creating an emuNAND for now. Afaik there aren't any other methods, even if there are other methods it is best to go with the safer emuNAND method.

 

[SephirothPlayer]

I need CFW on sysNAND

 

[Lacius]

I need CFW on sysNAND

Atmosphere runs on the sysMMC by default.

 

[SephirothPlayer]

Atmosphere runs on the sysMMC by default.

That is good. So a guide how to start it on a Lite unit with SX Lite (SX OS)?

 

[BaamAlex]

Why not emuNAND? It is easier to "recreate" a new one instead of messing up the SysNAND.

 

[Lacius]

Why not emuNAND? It is easier to "recreate" a new one instead of messing up the SysNAND.

There is no reason to use an emuMMC unless the goal is to play online with a clean sysMMC. The only other reason to use an emuMMC would be if you have an ipatched Switch on 4.1.0, but that doesn't apply here.

That is good. So a guide how to start it on a Lite unit with SX Lite (SX OS)?

SX OS boot menu -> Options -> Payloads, select fusee-primary.

 

[SephirothPlayer]

Tried that but I get:

Fatal error: [NXBOOT] Couldn't parse boot0: No such file or directory!
Press POWER to reboot.

While pressing POWER bunch of other stuff appears like "Exception type: data abort" or something like that.

 

[SephirothPlayer]

I don't have boot0. Should I have it? And why? And where?

 

[kerelenko]

If you have updated your emunand using choidujournx before then that is the reason why your boot0 gone. You'll need to restore boot0 back into your emunand.

A real issue I have encountered on my Switch lite with atmosphere 0.17 and file base emummc is that when I connect to wifi, the whole switch crashes.

--------------------- MERGED ---------------------------

Tried that but I get:

Fatal error: [NXBOOT] Couldn't parse boot0: No such file or directory!
Press POWER to reboot.

While pressing POWER bunch of other stuff appears like "Exception type: data abort" or something like that.

if you are on SXLite and you just want to use atmosphere on sysnand
- you need SX gear boot.dat
- atmosphere 0.17
- boot.ini in root of sd card
- license.dat in root of sd card
- fusee-primary.bin in root of sd card

On turning on the switch it should boot atmosphere directly.
Here's a video

 

[GCS]

You also may need exosphere.ini . You can follow this. (You should blank the SysNAND prodinfo instead of EmuNAND prodinfo in exosphere). But just to make sure get a prodinfo backup.

EDIT: Also you will need fusee-primary instead of secondary. Do not use the hekate ipl and you should skip the emuNAND migration steps

 

[MaxiBus]

There is no reason to use an emuMMC unless the goal is to play online with a clean sysMMC

Sure there is. I killed my emunand twice with incognito. If I used sysnand, I would have a nice brick. There is no reason to NOT use EmuMMC in my opinion.

 

[kerelenko]

^^^
This. This is the best reason on why to use emunand.

 

[Lacius]

Sure there is. I killed my emunand twice with incognito. If I used sysnand, I would have a nice brick. There is no reason to NOT use EmuMMC in my opinion.

Reasons not to use an emuMMC:

1. Slower response times in Horizon (read/write speeds are slower on the SD card than the eMMC)
2. Sacrificing 32GB of storage space on the SD card
3. Cumbersome setup process
4. Decreasing the lifespan of the SD card (using an emuMMC dramatically increases the reads/writes to the SD card)
5. If the SD card dies, which is more likely when using an emuMMC, you lose all saves, etc. associated with the emuMMC

Incognito should not cause a brick, so I'm not sure what you did wrong to brick "twice" with Incognito, but having a prodinfo backup or a sysMMC backup mitigates any brick risks. Any "bricks" that happened on your emuMMC might have also happened because of the fact that you were installing Incognito to an emuMMC; I would have to know more. There also isn't much of a reason to use Incognito on a sysMMC when Atmosphere has the Incognito function built in if enabled.

So, as I said earlier, there are only two recommended reasons to use an emuMMC:

1. Wanting to play online with a clean sysMMC
2. Having an ipatched Switch that's exploitable on 4.1.0.

 

[nero99]

I have Switch Lite with SX Lite chip using SX OS and I want to run Atmosphere CFW on sysNAND (not on emuNAND). What should I do?

Using cfw on sysnand will get you banned from online services. That means no game updates or Eshop for you. Also if you install or delete the wrong thing, you’ll have yourself a nice expensive brick.

 

[MaxiBus]

Reasons not to use an emuMMC:

1. Slower response times in Horizon (read/write speeds are slower on the SD card than the eMMC)
2. Sacrificing 32GB of storage space on the SD card
3. Cumbersome setup process
4. Decreasing the lifespan of the SD card (using an emuMMC dramatically increases the reads/writes to the SD card)
5. If the SD card dies, which is more likely when using an emuMMC, you lose all saves, etc. associated with the emuMMC

Incognito should not cause a brick, so I'm not sure what you did wrong to brick "twice" with Incognito, but having a prodinfo backup or a sysMMC backup mitigates any brick risks. Any "bricks" that happened on your emuMMC might have also happened because of the fact that you were installing Incognito to an emuMMC; I would have to know more. There also isn't much of a reason to use Incognito on a sysMMC when Atmosphere has the Incognito function built in if enabled.

So, as I said earlier, there are only two recommended reasons to use an emuMMC:

1. Wanting to play online with a clean sysMMC
2. Having an ipatched Switch that's exploitable on 4.1.0.

1. You should try it with a neat U3 Sandisk, not your wish huawei fake toys. You wont notice any difference between speeds.
2. 512GB SD and 32GB are no longer relevant
3. come on...
4. Thats maybe true, I have no experience values for this
5. True too, make backups on FTP or something

I bricked Emunand on a lite with SX OS. Have fun restoring your product info on a bricked sysnand with ease. If you try different 0 day homebrews, you are safe with emunand.

Maybe its suitable for you to use cfw on sysnand, but I will never recommend it to anyone.

 

[Lacius]

1. You should try it with a neat U3 Sandisk, not your wish huawei fake toys. You wont notice any difference between speeds.
2. 512GB SD and 32GB are no longer relevant
3. come on...
4. Thats maybe true, I have no experience values for this
5. True too, make backups on FTP or something

I bricked Emunand on a lite with SX OS. Have fun restoring your product info on a bricked sysnand with ease. If you try different 0 day homebrews, you are safe with emunand.

Maybe its suitable for you to use cfw on sysnand, but I will never recommend it to anyone.

You seem to be suggesting it's somehow difficult to restore one's prodinfo from a backup.

 

[MaxiBus]

You seem to be suggesting it's somehow difficult to restore one's prodinfo from a backup.

I never had to because of emuMMC so i do not know, how to do that.

 

[Lacius]

I never had to because of emuMMC so i do not know, how to do that.

It's extremely simple to restore one's prodinfo. There is no reason to use an emuMMC, other than wanting to use online play on a clean sysMMC or having a patched Switch on 4.1.0.

 

[MaxiBus]

It's extremely simple to restore one's prodinfo. There is no reason to use an emuMMC, other than wanting to use online play on a clean sysMMC or having a patched Switch on 4.1.0.

omg...
i am going to pet my cat now, makes more sense