Hacking Is updating the sysNAND safe if I've accidentaly booted into it using SXOS?

Calzy_G · Dec 10, 2019

Hi, my system is still on 4.1.0 (and no internet connection has been on since). I created the emuNAND (hidden partition) using that and have only ever updated the emuNAND (which is currently on 8.1.0). I've accidentaly booted into Horizon a couple of times using SXOS but have never installed anything. Always powered down straight away and booted into the emuNAND. My question is, would this leave any kind of data that would be sent if I connected to the internet and updated the sysNAND?

Wouldn't mind playing a legit game online but not if it'll get me banned in this situation. The first thing I done was a full backup in Hekate which I have and the fuse count is still what it was on 4.1.0.

Is it neccessary to restore this to be safe?

Thanks for any advice.

The Real Jdbye · Dec 10, 2019

Calzy_G said:
Hi, my system is still on 4.1.0 (and no internet connection has been on since). I created the emuNAND (hidden partition) using that and have only ever updated the emuNAND (which is currently on 8.1.0). I've accidentaly booted into Horizon a couple of times using SXOS but have never installed anything. Always powered down straight away and booted into the emuNAND. My question is, would this leave any kind of data that would be sent if I connected to the internet and updated the sysNAND?

Wouldn't mind playing a legit game online but not if it'll get me banned in this situation. The first thing I done was a full backup in Hekate which I have and the fuse count is still what it was on 4.1.0.

Is it neccessary to restore this to be safe?

Thanks for any advice.

How do you accidentally boot into sysNAND with SX OS? You would have to actually enter the SX menu and disable emuNAND...

Anyway, the latest SX OS has creport included so logs are redirected to SD, so in theory it should not leave any traces just from running it if you didn't do anything else. But that was only added in the very latest version, any older version is unsafe for online.

Calzy_G · Dec 10, 2019

The Real Jdbye said:
How do you accidentally boot into sysNAND with SX OS? You would have to actually enter the SX menu and disable emuNAND...

Anyway, the latest SX OS has creport included so logs are redirected to SD, so in theory it should not leave any traces just from running it if you didn't do anything else. But that was only added in the very latest version, any older version is unsafe for online.

I could be mistaken. Is it not possible to boot into Horizon using SXOS features with emuNAND enabled? Maybe I've selected boot original firmware or whatever it's called and just assumed that SXOS was enabled. Thanks for the reply

The Real Jdbye · Dec 10, 2019

Calzy_G said:
I could be mistaken. Is it not possible to boot into Horizon using SXOS features with emuNAND enabled? Maybe I've selected boot original firmware or whatever it's called and just assumed that SXOS was enabled. Thanks for the reply

emuNAND is Horizon, so your question doesn't really make sense, but I'll assume you meant sysNAND.
If you "boot original firmware" only some patches are enabled like disabling fuse checks, it should not be detected, but you never know for sure, as it's not true OFW.

Calzy_G · Dec 10, 2019

The Real Jdbye said:
emuNAND is Horizon, so your question doesn't really make sense, but I'll assume you meant sysNAND.
If you "boot original firmware" only some patches are enabled like disabling fuse checks, it should not be detected, but you never know for sure, as it's not true OFW.

Yes I meant sysNAND (been drinking a lot of beer). That makes sense, thank you. Given the fact the sysNAND is clean other than that, I'm tempted to just update it instead of worrying about restoring the backup. I'm guessing my emuNAND 8.1.0 won't boot if I update the sysNAND. The newest SXOS would be my first go to but I'm not sure if that would work. Thanks for the help so far.

The Real Jdbye · Dec 10, 2019

Calzy_G said:
Yes I meant sysNAND (been drinking a lot of beer). That makes sense, thank you. Given the fact the sysNAND is clean other than that, I'm tempted to just update it instead of worrying about restoring the backup. I'm guessing my emuNAND 8.1.0 won't boot if I update the sysNAND. The newest SXOS would be my first go to but I'm not sure if that would work. Thanks for the help so far.

I would restore it just to be safe, but it doesn't really matter if you're not planning on going online. You can always do it later if/when you decide you want to go online on sysNAND.

Nezztor · Dec 11, 2019

Calzy_G said:
Hi, my system is still on 4.1.0 (and no internet connection has been on since). I created the emuNAND (hidden partition) using that and have only ever updated the emuNAND (which is currently on 8.1.0). I've accidentaly booted into Horizon a couple of times using SXOS but have never installed anything. Always powered down straight away and booted into the emuNAND. My question is, would this leave any kind of data that would be sent if I connected to the internet and updated the sysNAND?

Wouldn't mind playing a legit game online but not if it'll get me banned in this situation. The first thing I done was a full backup in Hekate which I have and the fuse count is still what it was on 4.1.0.

Is it neccessary to restore this to be safe?

Thanks for any advice.

Dont update if you wish to use a software exploit some people that have that fw have 2 emunands , one for online another for offline and sysnand for the software hax

Calzy_G · Dec 11, 2019

The Real Jdbye said:
I would restore it just to be safe, but it doesn't really matter if you're not planning on going online. You can always do it later if/when you decide you want to go online on sysNAND.

I was planning on going online. If I restore the backup and then update, would emuNAND still boot at 8.0.1? Thanks.

The Real Jdbye · Dec 12, 2019

Calzy_G said:
I was planning on going online. If I restore the backup and then update, would emuNAND still boot at 8.0.1? Thanks.

emuNAND won't be affected, just make sure you are on the latest Hekate and Atmosphere versions to avoid the crash that happens when you boot older FW with updated game cart firmware with a cart inserted.

Calzy_G · Jan 7, 2020

I restored boot 0/1 and the rawnand and all went perfectly. I then updated officially online and again, all went well. Not banned so far and hopefully won't be. Next step is to do a nand backup of 9.1.0 and then update emuNAND. Thanks for all of the replies.

Hacking Is updating the sysNAND safe if I've accidentaly booted into it using SXOS?

Well-Known Member

*is birb*

Well-Known Member

*is birb*

Well-Known Member

*is birb*

Well-Known Member

Well-Known Member

*is birb*

Well-Known Member

Similar threads

Popular threads in this forum

is birb

is birb

is birb

is birb