Hacking Discussion SX Core Mariko list of non-compatible tools

[3DSBricker]

Hello

IS choixdujour compatible to update emunand on a Switch lite with SX lite installed now ?

Yes. Sthetix posted a video a few days ago.

 

[Draxzelex]

Yes. Sthetix posted a video a few days ago.

That's ChoiDujourNX, not ChoiDujour.

 

[mattyxarope]

Hello

IS choixdujour compatible to update emunand on a Switch lite with SX lite installed now ?

Didn't you create a thread specifically for this question?

That's ChoiDujourNX, not ChoiDujour.

What's the difference?

 

[Draxzelex]

What's the difference?

ChoiDujourNX is a homebrew application as denoted by the -NX at the end that installs firmware files directly on the console. ChoiDujour is a python script wrapped up as a Windows .exe file which converts firmware files into flashable images to be used with tools such as hacdiskmount.

 

[mattyxarope]

ChoiDujourNX is a homebrew application as denoted by the -NX at the end that installs firmware files directly on the console. ChoiDujour is a python script wrapped up as a Windows .exe file which converts firmware files into flashable images to be used with tools such as hacdiskmount.

Ah ok. I've never seen anyone use the non NX version.

 

[3DSBricker]

No me too. Didn't know there was a non NX one.

 

[mattyxarope]

Yes. Sthetix posted a video a few days ago.

This guy posts generally useful information and videos but his comments on his videos about the recent Lite/Core chips are misleading. There's even a TX Admin (@Alchemy_Gaming) telling him off in the comments of some of them.

 

[MomZo]

Weird. The incognito.nro (Not RCM) is confirmed to work. The Tinfoil (HBG Shop) method is known to brick, however.

Incognito.nro v1.5 is working good on my Mariko with SX Core.
Serial number is hidden and a backup folder with prodinfo has been generated at first launch.

 

[Alchemy_Gaming]

This guy posts generally useful information and videos but his comments on his videos about the recent Lite/Core chips are misleading. There's even a TX Admin (@Alchemy_Gaming) telling him off in the comments of some of them.

Thanks for noticing lol
I saw his first vid posted in our chat server. I noticed there was no disclaimer about emuNAND so I made that clear in the comments. He agreed to add a disclaimer and even pinned a comment about it. Then he went and made a "debunking" video to prove it was totally safe to do it on sysNAND. Completely ignoring what I had told him, that any users following this video are still bricking their boot0 even though SX OS works. Because it's not a fix, it's a workaround. It's not like it was just some SX bug we needed to fix. It's because Raj left the scene and ChoiDujourNX is outdated. It does not recognize Mariko/Lite console as it should, and so you can no longer boot without the chip. You can always fix any soft brick like this with a NAND backup but it's best to just, you know, not brick it. EmuNAND use is totally safe because your actual NAND is not using that boot0.

Now, his Lite, and any other Mariko/Lite users that followed that guide, couldn't use the genuine boot feature if they wanted to. Don't get me wrong @sthetix is a pretty smart guy, he had a NAND backup and took this risk for the community, and I respect that. I just think the most important thing for a tutorial maker, is having 100% accurate information, and full disclosure on what is being done to the console. If anyone has any questions on this feel free to DM me in our chat server. I'd share the link but they hate us here and will remove it

 

[izy]

I'd share the link but they hate us here and will remove it

i dont blame them

 

[LapCheong]

I feel that tutorial without explanation is just plain lazy. Putting a disclaimer that updating your switch through choidujournx will turn on autorcm which in other words corrupt your your boot0. But no.... in the video he phrase it as a softbrick and by updating sx os firmware will solve the problem.

Well yes, you solved the problem because sx os is outdated and doesnt support the latest firmware. Hence it is not booting

Well no, because your boot0 is still corrupted and will not fix by updating sx os

Well.... and no one really cares what i just explained because your sx core hasn't fail. Good luck to those that didn't have a emunand.

 

[mattyxarope]

Now, his Lite, and any other Mariko/Lite users that followed that guide, couldn't use the genuine boot feature if they wanted to.

I'm not quite sure what this feature even does - could you explain it to me? Isn't its purpose basically the same thing as booting into sysnand?

 

[Alchemy_Gaming]

i dont blame them

Wat

I'm not quite sure what this feature even does - could you explain it to me? Isn't its purpose basically the same thing as booting into sysnand?

So basically genuine boot is pretty much what it sounds like. It clears out the modifications and deactivates the chip for a single boot to OFW. Keep in mind this will burn fuses (not that the average user should really care about fuses at the moment). After you shut down and attempt the next boot it will take longer since it needs to rewrite everything it cleared out previously. If you use this feature, or if you update sysNAND, don’t panic if you see the blue breathing light for a minute or so. Just needs to start from scratch.

 

[mattyxarope]

So basically genuine boot is pretty much what it sounds like. It clears out the modifications and deactivates the chip for a single boot to OFW. Keep in mind this will burn fuses (not that the average user should really care about fuses at the moment). After you shut down and attempt the next boot it will take longer since it needs to rewrite everything it cleared out previously. If you use this feature, or if you update sysNAND, don’t panic if you see the blue breathing light for a minute or so. Just needs to start from scratch.

A few questions:

1. What would be a scenario where using genuine boot would be useful? I don't see why you'd want to do that. Maybe I'm missing something. I always create an emunand immediately and only do bannable things on there, and leave the original firmware untouched.
   
2. You can update the SX chip firmware by putting a file on the sd card, right? It's not necessary to plug in the chip via the debug port every time you need to update?
   
3. Can you confirm that incognito.nro works on emunand?
4. As you said, booting into original firmware (sysnand) from the SX boot menu prevents fuse burning, right? Is there any point in worrying about fuses after you've installed a modchip? Doesn't seem like it to me...
5. Could you confirm that this is a correct summary of the emunand creation and general updating processes?:
   1. Update your original firmware online from Nintendo normally
   2. Create emunand
   3. (If you ever want to update your original firmware after the creation of emunand, just boot into original firmware (sysnand) from the SX boot menu and update normally online)
   4. Make sure that you're on the latest SX firmware (boot.dat) as well as the latest SX chip firmware and boot into emunand
   5. Use ChoidujourNX to update emunand firmware (with no RCM)
   6. Reboot into emunand where SX will fix the brick from ChoirdujourNX (that corrupts the the boot0 sector of emunand, not sysnand) and leave you with an up to date emunand firmware. There will be no problem booting original firmware after the update to emunand.

 

[LapCheong]

A few questions:

1. What would be a scenario where using genuine boot would be useful? I don't see why you'd want to do that. Maybe I'm missing something.
   
2. You can update the SX chip firmware by putting a file on the sd card, right? It's not necessary to plug in the chip via the debug port every time you need to update?
   
3. Can you confirm that incognito.nro works on emunand?
4. As you said, booting into original firmware (sysnand) from the SX boot menu prevents fuse burning, right? Is there any point in worrying about fuses after you've installed a modchip? Doesn't seem like it to me...
5. Could you confirm that this is a correct summary of the emunand creation and general updating processes?:
   1. Update sysnand online from Nintendo normally
   2. Create emunand from updated sysnand
   3. (If you ever want to update your sysnand firmware after the creation of emunand, just boot into original firmware (sysnand) from the SX boot menu and update normally online)
   4. Make sure that you're on the latest SX firmware (boot.dat) as well as the latest SX chip firmware and boot into emunand
   5. Use Choidujour to update emunand firmware (with no RCM)
   6. Reboot into emunand where it will fix the brick from Choirdujour and leave you with an up to date emunand firmware

1. I guess people wants to go online and play their games? But the ban risk is high and also to update their firmware officially. Basically genuine boot is booting ofw with fuse check, booting without fuse check will be by sx os main option. It is confusing but maybe someone can correct me with the right terminology?
2. I am not sure about this since i don't have a sx core
   
3. I am not sure about this since i don't have a sx core
4. Yes by booting with genuine boot option aka booting without hekate will burn fuses. Think of sx os menu like hekate.
5. Could you confirm that this is a correct summary of the emunand creation and general updating processes?:
   1. (If you ever want to update your sysnand firmware after the creation of emunand, just boot into original firmware (sysnand) from the SX boot menu and update normally online) Boot with genuine boot since you will be connecting to nintendo server to update, by using boot ofw in sx menu will result you in a ban since you are bypassing fuse check
   2. Make sure that you're on the latest SX firmware (boot.dat) as well as the latest SX chip firmware and boot into emunand
   3. Use ChoidujourNX to update emunand firmware (with no RCM) Not sure if you have a choice to disable this
   4. Reboot into emunand where it will fix the brick from ChoirdujourNX and leave you with an up to date emunand firmware Said this on my previous post, booting and updating sx os WILL NOT FIX the brick. Because this brick is caused by the corrupted boot0 partition and updating will not fix this. You are allowed to boot is because your sx os supports the firmware (10.1.0) not because it fixes the corrupted boot0 causes by choidujournx

 

[mattyxarope]

1. I guess people wants to go online and play their games? But the ban risk is high and also to update their firmware officially. Basically genuine boot is booting ofw with fuse check, booting without fuse check will be by sx os main option. It is confusing but maybe someone can correct me with the right terminology?
2. I am not sure about this since i don't have a sx core
   
3. I am not sure about this since i don't have a sx core
4. Yes by booting with genuine boot option aka booting without hekate will burn fuses. Think of sx os menu like hekate.
5. Could you confirm that this is a correct summary of the emunand creation and general updating processes?:
   1. (If you ever want to update your sysnand firmware after the creation of emunand, just boot into original firmware (sysnand) from the SX boot menu and update normally online) Boot with genuine boot since you will be connecting to nintendo server to update, by using boot ofw in sx menu will result you in a ban since you are bypassing fuse check
   2. Make sure that you're on the latest SX firmware (boot.dat) as well as the latest SX chip firmware and boot into emunand
   3. Use ChoidujourNX to update emunand firmware (with no RCM) Not sure if you have a choice to disable this
   4. Reboot into emunand where it will fix the brick from ChoirdujourNX and leave you with an up to date emunand firmware Said this on my previous post, booting and updating sx os WILL NOT FIX the brick. Because this brick is caused by the corrupted boot0 partition and updating will not fix this. You are allowed to boot is because your sx os supports the firmware (10.1.0) not because it fixes the corrupted boot0 causes by choidujournx

1. I don't think that there is a high ban risk of going online with sysnand if you keep it clean and don't do any hacking and don't play backups. At least with my V1 switch, I've always booted original firmware and updated that way. Let me be clear with this, I mean boot original firmware after having made a separate emunand, not boot sysnand with SX CFW enabled (which is a stupid idea lol)
2. -
3. -
4. -
5. -
   1. Like I said in 1 here, are you sure of that? I didn't think that booting into sysnand had a ban risk when going online if it's clean. As I said, I mean boot original firmware, not custom firmware on sysnand.
   2. -
   3. - Afaik, RCM isn't even selectable
   4. Isn't there a boot0 partition on emunand AND sysnand? It would only corrupt the boot0 of emunand, right? You might be right about it not fixing the corruption but just bypassing it. If that's true, how do we update emunand?

 

[LapCheong]

1. I don't think that there is a high ban risk of going online with sysnand if you keep it clean and don't do any hacking and don't play backups. At least with my V1 switch, I've always booted sysnand and updated that way. Let me be clear with this, I mean boot original firmware, not boot sysnand with SX CFW enabled.
2. -
3. -
4. -
5. -
   1. Like I said in 1 here, are you sure of that? I didn't think that booting into sysnand had a ban risk when going online if it's clean. As I said, I mean boot original firmware, not custom firmware on sysnand.
   2. -
   3. - Afaik, RCM isn't even selectable
   4. Isn't there a boot0 partition on emunand AND sysnand? It would only corrupt the boot0 of emunand, right? You might be right about it not fixing the corruption but just bypassing it. If that's true, how do we update emunand?

Ya of course as long it is not superban updating official will no problem. It is just a risk but if you start with emunand off the bat you should be good to go. It will be fine in emunand since you can just bypass and boot cfw. Just use choidujournx on emunand and make sure sx os supports that firmware you booting

 

[mattyxarope]

Ya of course as long it is not superban updating official will no problem. It is just a risk but if you start with emunand off the bat you should be good to go. It will be fine in emunand since you can just bypass and boot cfw. Just use choidujournx on emunand and make sure sx os supports that firmware you booting

Ok yeah, I think the confusion came from the fact that some people DON'T create an emunand and they use CFW on their sysnand that they use to go online with - which is CRAZY to me.

That's a ban waiting to happen.

That's what sthetix was saying in the comments of his videos - that not many people create emunand. That's really ballsy.

 

[LapCheong]

SX OS is really easy in create emunand but still people are not doing it. But to be honest getting ban should be the least of your worry, with the way of i how i treat my switches. I am scare that 1 day the solder point will come loose or it shorts something. The use of kapton tape in sthetix is really great and cutting of the heat shield to fit the sx core. I doubt most installer will go through the trouble doing this.


Few weeks later you will start seeing topics like "My friend break his switch"

 

[Alchemy_Gaming]

A few questions:

1. What would be a scenario where using genuine boot would be useful? I don't see why you'd want to do that. Maybe I'm missing something. I always create an emunand immediately and only do bannable things on there, and leave the original firmware untouched.
   
2. You can update the SX chip firmware by putting a file on the sd card, right? It's not necessary to plug in the chip via the debug port every time you need to update?
   
3. Can you confirm that incognito.nro works on emunand?
4. As you said, booting into original firmware (sysnand) from the SX boot menu prevents fuse burning, right? Is there any point in worrying about fuses after you've installed a modchip? Doesn't seem like it to me...
5. Could you confirm that this is a correct summary of the emunand creation and general updating processes?:
   1. Update your original firmware online from Nintendo normally
   2. Create emunand
   3. (If you ever want to update your original firmware after the creation of emunand, just boot into original firmware (sysnand) from the SX boot menu and update normally online)
   4. Make sure that you're on the latest SX firmware (boot.dat) as well as the latest SX chip firmware and boot into emunand
   5. Use ChoidujourNX to update emunand firmware (with no RCM)
   6. Reboot into emunand where SX will fix the brick from ChoirdujourNX (that corrupts the the boot0 sector of emunand, not sysnand) and leave you with an up to date emunand firmware. There will be no problem booting original firmware after the update to emunand.

Genuine boot is more or less for those too paranoid to connect to Nintendo’s servers with a modified boot0. I’m not an expert on what gets you banned and what doesn’t, but do people even get banned for autoRCM? I mean there’s always a risk but I prefer to go through the bootloader.

You can update the Core/Lite firmware with the latest boot.dat unless you did something wrong. Debug port is your saving grace for mistakes like we had with ChoiDujourNX.

I hear incognito.nro works fine but...if you’re using SX OS why would you even run it

Fuse count doesn’t make any difference to an average user since CFW bootloader don’t do what HOS bootloader does.

I think your process sounds fine but I’d like to add that you should only update before the mod if you’re 100% certain the firmware is compatible. Also that you should run lockpick.nro once you boot CFW to get your biskeys.

As for emuNAND/NAND dumping, we don’t have the luxury of a super fast dump with Hekate when it comes to Mariko/Lite units. My suggestion is to use a FAT32 card to make 1 NAND dump. Put the SD in your PC to COPY somewhere safe, and then rename `sxos/backup` to `sxos/emunand`
That should save a lot of time if you want to have a fresh NAND dump AND an emuNAND.

Is it just me or do my backticks do absolutely nothing here