SX OS and upgraded eMMC modules?

[Anondroid]

Hello TX team and users,

First of all, as a side note, thanks for your product and continued support. There is a lot of salt and hate, perhaps even jealousy out there.
Along with panicking users and users that don't know any better, but you guys and the moderators are still putting up with it.

Having said that, I have a somewhat odd question perhaps.
As we don't have the source code of SX OS's CFW implementation (which I understand, and am fine with obviously), it seems to be unknown whether a eMMC chip upgrade would be a problem in using SX OS.

Atmposphere recently had a update to account for larger than 32GB eMMC sizes.
I assume that this isn't a problem on Hekate/SX OS because of the differences in the term "CFW" between them so to say.

I'm planning on upgrading a eMMC module with 128GB eMMC memory, would this cause a problem?
I have no intentions of using it with emuNAND. In fact, the 128GB eMMC module will act as a "emuNAND", being a secondary eMMC module I will switch between from the original untouched (32GB) eMMC module.
This mainly because I would like to prevent the so called (by some in the community) wear and tear of the current emuNAND implementation to the micro SD card.

This post has gone on long enough, thanks in advance for your time!

Best regards.

 

[ybmug]

Would be pretty neat if you could setup that 2nd eMMC to read as a different system all together. One that isn't linked to your Nintendo account for a future ban, but not sure if that would be possible or not, since it's basically just extra internal memory.

 

[Anondroid]

Well, I mean, isn't that the idea of a physical dual (emu)NAND/eMMC?

You obviously do not connect to the internet with the secondary eMMC/emuNAND setup.
Just with the original eMMC containing the OFW, which should be touched with Homebrew of CFW software to avoid hopefully any form of detection by Nintendo. (In the Switch's case)

 

[ybmug]

Well, I mean, isn't that the idea of a physical dual (emu)NAND/eMMC?

You obviously do not connect to the internet with the secondary eMMC/emuNAND setup.
Just with the original eMMC containing the OFW, which should be touched with Homebrew of CFW software to avoid hopefully any form of detection by Nintendo. (In the Switch's case)

Sorry. What I meant was, it would be cool to setup a 2nd (larger) eMMC and program it with a new system/user ID. Different from the original eMMC and nand. So the 2nd eMMC could never ban the original eMMC if you tired to go online with it. Though, I'm sure that it would be a conflict with the rest of the hardware on the system to do this.

 

[Anondroid]

Sorry. What I meant was, it would be cool to setup a 2nd (larger) eMMC and program it with a new system/user ID. Different from the original eMMC and nand. So the 2nd eMMC could never ban the original eMMC if you tired to go online with it. Though, I'm sure that it would be a conflict with the rest of the hardware on the system to do this.

Ah, yes, that would be cool.
I read that there are some kind of certs stored somewhere, not sure if that's on the eMMC though. But that would be nice, except for all the online multiplayer cheating chaos that would ensue, though.

 

[evil nick]

are you basically saying youre going to pull out the stock eMMC and install a bigger one you would partition with a backup nand?

 

[Anondroid]

Very good question, not one I have the answer to, Let me ask questions.

Hey,

Did you have a chance to ask the team, or get a response yet?

Thanks,
Anondroid