Team-Xecuter Presents SX OS v2.3 BETA

thaikhoa · Nov 19, 2018

Localhorst86 said:
SD cards usually perform slower than the eMMC memory built into the switch. So you probably wont notice any change in loading times when launching games off of SD, but games installed to the Emunand will obviously not load at eMMC speeds, but SD card speed.

The installing speed from USB to SD when using emunand on SD is the same as on the nand, at a maximum speed of 28MB/s. USB HDD directly connected to usb c port (single cable) to the Switch.

jacopastorius · Nov 19, 2018

With the implementation of this sd emunand, do you see this protocol as safe?
I have no emunand at the moment and played nsp and xci so far. So i am gonna do this:

1- Backup game saves
2- Restore original, clean NAND
3- Create SD EmuNAND and restore save games into it

mrdude · Nov 19, 2018

aerios169 said:
just rename the folder of nintendo for Emutendo, and it should remove the black screen, i had the same problem and i did that and works fine for me even with the installed games

That didn't work. I ended up re-making an emunand, that still didn't work. To get emunand to work, I needed to just put my original nand dump in the emunand folder, then emunand worked.

TX - I figure there is a problem with this release with creating a good working nand dump to be used for emunand.
Reason - created emunand in the emunand folder fails, using a previous nand dump in emunand folder works.

On the bright side - it's a good way to test if a nand dump is working, before you restore a nand dump.

Localhorst86 · Nov 19, 2018

thaikhoa said:
The installing speed from USB to SD when using emunand on SD is the same as on the nand, at a maximum speed of 28MB/s. USB HDD directly connected to usb c port (single cable) to the Switch.

Sounds like the bottleneck here is USB, then.

raphzthename · Nov 19, 2018

I started off at 100% battery life and I'm about 63% of the way through creating the SD emunand. I'm worried my battery may day before it finishes since it has taken quite a while. Do we need to keep the dongle in while the full raw nand is being dumped?

thaikhoa · Nov 19, 2018

Localhorst86 said:
Sounds like the bottleneck here is USB, then.

I tried to install using Y-cable and on the dock usb3.0 port. The result is the same, max 28MB/s. Someone says they can get 40+MB/s but idk how to. I'm using Seagate Expansion 2.5" 1.5TB

Localhorst86 · Nov 19, 2018

thaikhoa said:
I tried to install using Y-cable and on the dock usb3.0 port. The result is the same, max 28MB/s. Someone says they can get 40+MB/s but idk how to. I'm using Seagate Expansion 2.5" 1.5TB

a Y-Cable will not increase transfer rates, on a Y cable only one plug provides data lines. The second plug only provides power to the connected device.

Either way, the eMMC performance (i.e. Sysnand) should generally be higher than 28MB/s so you're experiencing a bottleneck, either the USB connection or the device.

What's more interesting would be loading times. Try installing a NSP to Sysnand and SD-Emunand and you'll see a difference in loading speeds. Depending on the speed of your SD card, loading speeds can differ quite a lot.

Mateto · Nov 19, 2018

guitarheroknight said:
Still dont see the point in emuNAND other than staying on a lower firmware. Its all good and all, but its pointless if youre on the latest firmware.

Installing NSPs into emuNAND to keep sysNAND clean.

tinkle · Nov 19, 2018

Ev1l0rd said:
I'm holding out for those that can.

I'm not calling the sysNAND trick a hackjob, someone who can does. That someone being hexkyz back when the sysNAND hackjob came out.

They were proven wrong.

aos10 · Nov 19, 2018

i still don't get it, how this new emunand works?
is it really doesn't touch the real nand? so if i have 4.1, then installed this emunand then used ChoiDujourNX (which it shouldn't works on sxos?) to update to 6.1
after all that, if i boot without RCM to OFW i will get 4.1, and if i boot with RCM to emunand i will boot to SXOS 6.1, right?

then if i boot to reinx for example, i will boot to 4.1 also?

metal921 · Nov 19, 2018

Great release from TSX! My question is what are the benefits of having emunand on SD? Besides emunand being supposedly detectable by Nintendo what’s the point? Isn’t having more microSD space better? Would be great if they implemented the option to choose either. So far this has been best purchase for the switch I have ever made. Was thinking of selling it before homebrew but this made me keep it. I initially thought the switch sucked mainly got it for Smash but that’s for another topic haha thanks SX for your work! Also SX File Manager soon

?

Ev1l0rd · Nov 19, 2018

Shadowfied said:
Are you saying one partition has less chance of being corrupted because you are writing to another partition on the same storage device instead......?

Not exactly. Lemme explain for a mo'.

Filesystem corruption is, for the most part, an expected thing when using a digital appliance. Corruption happens whenever the appliance in question is interrupted when reading or writing to a file (power cycle, battery death, game crash, you get the idea, its stuff thats relatively common). Most modern OSes minimize the risk of corruption by checking the filesystem on boot (linux and macOS run fsck, windows uses chkdsk on all plugged in drives).

The problem is, because the Nintendo Switch still nowadays is still a... slightly underpowered device (as well as Nintendo being well, Nintendo but credit where credit is due, its better than the 3DS), Nintendo has not build in any filesystem checking into Horizon (Switch' OS), leaving filesystem checking up to the user whenever they plug it in their computer.

Now, we know that TX's emuNAND solution when it was on the sysNAND did nothing but create an image of the NANDs partitions on the USER partition, trim USERs image and mount it.

What has seemingly happened here is that they've done the same for the SD card. They mount the SD cards partition and mount the images on the SD card as the NAND.

The issue here is that because they're using the SD cards filesystem as well as the NAND images themselves for this, which again are stored on the SD card. This means that if the NAND image is ever interrupted from writing/reading, the SD cards filesystem is also corrupted as a result.

Combine that with the fact that they have to constantly read/write to these files, and an interruption is just waiting to happen.

If you were to use the legitimate emuNAND idea, you would mark some portions on the SD card as being reserved for the NAND (empty partitions or in the case of the 3DS, emuNAND was just marked as "free space" on the SD card. Then it's a matter of redirecting all read/writes to this reserved space. You wouldn't be be mounting a partition on the SD or anything.

The difference here is that if you should accidentally corrupt your SDs filesystem (and Nintendo has already such wonky exFAT support that pretty much doing anything w/ exFAT results in SD filesystem corruption), with TXs emuNAND, you basically put your emuNAND at risk every time this occurs. If they actually had made a proper emuNAND (aka what Atmosphere/SciresM is working on), they wouldve done what I just said in the last paragraph. If the SD filesystem corrupts in that case, your emuNAND would (generally*) remain untouched.

*Generally since filesystem corruption is kinda wonky and could occur in a lot of places. I once had my MBR corrupt somehow and had to restore that using testdisk, but these cases are much rarer than the risk that TX is putting things at.

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

tinkle said:
They were proven wrong.

And now for the controversial EmuNAND solution in 2.0:
- Everything is handled by the bootloader which starts by mounting 3 devices: "0:" (SDCard), "1:" (EmuNAND) and "3:" (original NAND);
- The original NAND partition is shrunk to about half of it's dimension;
— Mike Heskin (@hexkyz) September 23, 2018

I'm referring to these tweets.

Pretty sure there's nothing wrong in these tweets.

Aks · Nov 19, 2018

raphzthename said:
I started off at 100% battery life and I'm about 63% of the way through creating the SD emunand. I'm worried my battery may day before it finishes since it has taken quite a while. Do we need to keep the dongle in while the full raw nand is being dumped?

You can take the Dongle out and charge, the Dongle is only used to boot into the menu essentially.

The Real Jdbye · Nov 19, 2018

pka4916 said:
This sucks..
Lost all my games when I used Emunand.

You need to do as explained in the post to keep your data.

lufeig · Nov 19, 2018

shanefromoz said:
How would you then update to 6.1.0?

i didn't update yet, as i have no reason to do so by now. but without thinking, i would run choidujournx and update it, although i guess there would be no reason to have autorcm on emunand, since I would always have to launch sx os bootloader first, so autorcm would have to be present on real nand.

Hernie said:
So you copied the entire contents from the "Nintendo" folder to the "Emutendo" folder before you actually created the emuNand?

I was going to do it after, but if that worked for you, that's the way I'm going to do it.

I'm sure I would just boot into SD emuNand then use ChoidujourNX to update?? I'm still on 4.1.0

yes, that is exactly what i did.

and yes, i would use choidujournx if i had to update my emunand's firmware.

tinkle · Nov 19, 2018

Given how poorly the Switch handles ExFAT I dont know why yall arent using FAT32

Kubas_inko · Nov 19, 2018

tinkle said:
Given how poorly the Switch handles ExFAT I dont know why yall arent using FAT32

Cause I don't want to split games and exFAT works just fine. There is no real problem, unless you use stuff which causes them.

Ev1l0rd · Nov 19, 2018

Kubas_inko said:
Cause I don't want to split games and exFAT works just fine. There is no real problem, unless you use stuff which causes them.

So... using the Switch at all?

Nintendo's exFAT drivers are the epitome of "poorly made", corruption just happens on exFAT by default if you use it on your Switch.

Kubas_inko · Nov 19, 2018

Ev1l0rd said:
So... using the Switch at all?

Nintendo's exFAT drivers are the epitome of "poorly made", corruption just happens on exFAT by default if you use it on your Switch.

I never had problems with exfat. So if you can give me any sources on this.

Ev1l0rd · Nov 19, 2018

Kubas_inko said:
I never had problems with exfat. So if you can give me any sources on this.

Would personal experience count?

I've had my exFAT filesystem corrupt a bunch of times before I gave up and just moved back to FAT32.

Well-Known Member

Well-Known Member

Developer

Robert'); DROP TABLE members;--

Well-Known Member

Well-Known Member

Robert'); DROP TABLE members;--

Active Member

taciturn shill girl

Yuuki chan

Active Member

(⌐◥▶◀◤) girl - noirscape

Member

*is birb*

Well-Known Member

taciturn shill girl

"Something funny goes here."

(⌐◥▶◀◤) girl - noirscape

"Something funny goes here."

(⌐◥▶◀◤) girl - noirscape

Similar threads

Popular threads in this forum

is birb