Team-Xecuter Presents SX OS v2.4 BETA

Bloodlust · Dec 14, 2018

SaggyBeans said:
You can always disable autorcm but you may burn your e-fuses if you don’t use a jig + payload when u boot up.

I don't get it. Since it's installed on emunand why would efuses still be burnt?

Sent from my MI MAX 3 using Tapatalk

fringle · Dec 14, 2018

moopas said:
Hey, just two quick questions. I just got SX 2.4 and already deleted my old emunand on the SD, which I barely used due to many comments about that method eventually or rather easily corrupting your SD card. My first question is whether or not the new partition method is more safe for the longevity of your SD card, aside from use wear and tear, or if the old rumor/statements of the old SD method actually being that destructive to an SD card.

As for my second question is regarding Choidujour. When updating the emunand, I know that there is an issue regarding sleep mode and waking up if fuses are burnt or whatever, but I plan on having an OFW fully up to date, and an Emunand fully up to date for purely offline nsp games and so on. But my question is as follows: For updating the emunand, must I use choidujour, or is that only recommended to not burn fuses? If I am updating both OFW and Emunand, is Choi still the best option, or do I just update as regular in both emu and sys?

You do not want to go online with emunand. Update your ofw officially if not banned and use choidujournx to update your emunand. The whole point of emunand is to keep it offline to avoid bans and to keep your sysnand free of hacks. I don't think the separate partition would change anything with the lifespan of the sdcard though. It's still being written to just as much, it's just a separate partition so this wouldn't affect how often it gets written to during operation. The issue with having emunand on the sdcard wasn't so much that it wasn't a separate partition but the fact that it is formatted as exfat which is unstable. I can only suspect the new partition that gets created will be fat32 with the rest of the card being exfat or fat32 but this may not be correct as I have not tried it. Sleep mode issue is only present when OFW is higher version then emunand due to fuse count. If ofw is a lower version or the same there is no issue with sleep mode.

WiiuGold · Dec 14, 2018

sx Installer gets the games from your Collection ,sd,hdd, server,Nut,ftp,http

SaggyBeans · Dec 14, 2018

Bloodlust said:
I don't get it. Since it's installed on emunand why would efuses still be burnt?

Sent from my MI MAX 3 using Tapatalk

Fuses get burned if you have autorcm disabled, turn on your switch without a jig and then load directly into the firmware without a payload. The switch does a check and will burn your fuses if they are lower than your firmware version. However if you are using a jig everytime with a payload such as sx or hetake then it bypasses the fuse check and you’re good. Autorcm will force you to load a payload thus blocking the possibility of burning the efuses which is why it is recommended.

Bloodlust · Dec 14, 2018

SaggyBeans said:
Fuses get burned if you have autorcm disabled, turn on your switch without a jig and then load directly into the firmware without a payload. The switch does a check and will burn your fuses if they are lower than your firmware version. However if you are using a jig everytime with a payload such as sx or hetake then it bypasses the fuse check and you’re good. Autorcm will force you to load a payload thus blocking the possibility of burning the efuses.

Yes, I am aware that if I update my sysnand manually using choidujournx the efuses will burn as I would be starting it up in horizon. But I am asking why it will still happen on emunand since in the first place I would need to launch it with sx os first and that means I am launching cfw.

Sent from my MI MAX 3 using Tapatalk

SaggyBeans · Dec 14, 2018

Bloodlust said:
Yes, I am aware that if I update my sysnand manually using choidujournx the efuses will burn as I would be starting it up in horizon. But I am asking why it will still happen on emunand since in the first place I would need to launch it with sx os first and that means I am launching cfw.

Sent from my MI MAX 3 using Tapatalk

You’re correct, if it’s only emunand you’re updating then you have nothing to worry about. For some reason I was assuming that you’d be running the same firmware on both sysnand and emunand.

comput3rus3r · Dec 14, 2018

Albytrozz said:
Well the Stardew Valley update failed... the NSP installed in Tinfoil with fw ignore fine but when I went to launch it the game wouldn't start. I use Tinfoil with fw ignore because everything I've ever tried to install with the SX installer in 2.3 beta won't run on 5.1.0 and all ask for an update.

I'm not sure if that's related to 2.4 Beta or if it was maybe just a bad update file. I deleted and reinstalled it and of course it's still asking for the update.
I might try installing it in 2.3 Beta to see if there's a difference.

you have to update your keys.txt to get tinfoil to work with new nsps. or use devmenu

Bloodlust · Dec 14, 2018

SaggyBeans said:
You’re correct, if it’s only emunand you’re updating then you have nothing to worry about. For some reason I was assuming that you’d be running the same firmware on both sysnand and emunand.

No, I would never manually update in sysnand as it needs autorcm. I simply dread the day I would forget to leave it charged and completely drain the battery to the point that I might need to open up the set.

Sent from my MI MAX 3 using Tapatalk

Bloodlust · Dec 14, 2018

comput3rus3r said:
you have to update your keys.txt to get tinfoil to work with new nsps. or use devmenu

If I extract keys from my own switch but it's still 5.1 will it work with 6.x nsp updates?

Sent from my MI MAX 3 using Tapatalk

roamin · Dec 14, 2018

SonyUSA said:
Watch the video...sx installer is the new freeshop

Funny I'm not normally that guy but you do know the sxos apps even look the same as the open source ones they were ripped from. Menus and all.

I dont care you can RIP others software all you like. I couldn't give a rat's. But dont ever claim you have stuff that the open source already has.

comput3rus3r · Dec 14, 2018

Bloodlust said:
I don't get it. Since it's installed on emunand why would efuses still be burnt?

Sent from my MI MAX 3 using Tapatalk

I don't think it matters weather or not you use autorcm on emunand since you always have to boot through rcm anyways to boot into emunand.

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

Bloodlust said:
If I extract keys from my own switch but it's still 5.1 will it work with 6.x nsp updates?

Sent from my MI MAX 3 using Tapatalk

no.

Bloodlust · Dec 14, 2018

comput3rus3r said:
I don't think it matters weather or not you use autorcm on emunand since you always have to boot through rcm anyways to boot into emunand.

Yes, precisely! That's the main point [emoji3]

Sent from my MI MAX 3 using Tapatalk

comput3rus3r · Dec 14, 2018

For people having issues with tinfoil and installing nsps you need to get the latest keys.txt Or you can use devmenu definitive edition.

bernieyee · Dec 14, 2018

Does anyone know if I can just create the new partition in the SXOS menu and then drag/drop my old SD emuNAND files in?

SaggyBeans · Dec 14, 2018

comput3rus3r said:
For people having issues with tinfoil and installing nsps you need to get the latest keys.txt Or you can use devmenu definitive edition.

Do you get the keys.txt via hetake? Where do you put the file for tinfoil or the native sx installer? I’m using devmenu definitive edition so I didn’t even realize the others weren’t working.

comput3rus3r · Dec 14, 2018

SaggyBeans said:
Do you get the keys.txt via hetake? Where do you put the file for tinfoil or the native sx installer? I’m using devmenu definitive edition so I didn’t even realize the others weren’t working.

if you're on 6.2 you can extract them from your console or a much easier way is to use google.

SaggyBeans · Dec 14, 2018

comput3rus3r said:
if you're on 6.2 you can extract them from your console or a much easier way is to use google.

Do you place them in the root directory? Or is there somewhere else we should be putting the keys.txt?

PoppaDre · Dec 14, 2018

I accidentally updated yesterday so this is good timing for me

smf · Dec 14, 2018

aos10 said:
I am still on 5.1 with ChoiDujourNX from 4.1, so no burned fuses now,

At best you have 5 fuses burned, as that is how many are burned on 4.1.

If you ever booted 5.1 without injecting a payload (or the payload did something wrong) then you would have 6 fuses burned.

bricmii payload will tell you how many fuses you've actually burnt.

aos10 said:
so if get back to 4.1 using my clean NAND, then installed emunand and update it to 6.2, it shouldn't burn any fuse, but will it cause problem in sleep?

AFAIK sleep only has a problem running old code where too many fuses are burnt, not running newer code where the fuses haven't been burnt. If it did then sleep mode wouldn't work for anyone using choidujournx.

geenlung · Dec 14, 2018

I can't seem to access the album anymore by holding L. What is the new hotkey?

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Similar threads

Popular threads in this forum