I can't confirm it because i'm not SX user but I doubt it, they need to change the keys on their code to make it working again.
Took the risk and it's indeed working!
Sysnand 8.1.0
Emunand 8.0.1
Sysnand only boots without autorcm.
Last edited by JJTapia19,
Took the risk and it's indeed working!
Sysnand 8.1.0
Emunand 8.0.1
I didn't read fine, I think that you wanna update your emunand, don't do this of you can't run SX OS before the next version.
Took the risk and it's indeed working!
Sysnand 8.1.0
Emunand 8.0.1
Uh, no? Just did it with SX OS and stock 8.1.0 firmware no longer boots. Let me guess, no autorcm
Last edited by Shadow LAG,
That's a big leap from working, to won't work my dude. You might want to lead with that / clarify in your original post. Yes you can boot it, but it definitely breaks AutoRCM.
Last edited by Shadow LAG,
My original post was this
And I was referring to exactly that when I say it works. I was not talking about autorcm/booting sysnand using sx bootloader.
Not trying to put you down man, I'm just stating AutoRCM is a big part of dual booting firmware. Some of us boot with our phones in quick succession. You might just want to include that disclaimer because not everyone likes to carry a Jig around with them everytime they wish to dual boot, you know what I mean? It's partially working, meaning emunand / sysnand switching now requires a jig if you wish to dual boot.
Last edited by Shadow LAG,
I get what you mean but I was talking about if emunand was working after updating sysnand to 8.1. And it is. I did not state everything else was working. I'll still put the disclaimer. Don't want anyone misunderstanding what I was talking about.
Sounds good, I prob should have expected it on my end knowing they were messing with TSEC
GUYS I NEED HELP I'M A NOOB AND DESPERATE SWITCH USER,
My stupid 7 y/o accidentally updated the firmware to 8.1.0 and now it can't boot
and I'm freaked out because you guys said that it's broken forever
is there anything I can do? also please use language that I can understand ^^
My stupid 7 y/o accidentally updated the firmware to 8.1.0 and now it can't boot
and I'm freaked out because you guys said that it's broken forever
is there anything I can do? also please use language that I can understand ^^
Can someone explain what people mean with them "burning fuses" ? Do they literally brick their system every time they update stuff more and more ?
I dont have a hacked switch obviously i sadly never was able to to begin with but im following stuff
Thanks
I dont have a hacked switch obviously i sadly never was able to to begin with but im following stuff
Thanks
The Tegra X1 has many tiny “fuses” which can be programmed and used for a variety of things. The Switch uses them for storing hardware information, ipatches, and anti downgrade, and some other stuff.Can someone explain what people mean with them "burning fuses" ? Do they literally brick their system every time they update stuff more and more ?
I dont have a hacked switch obviously i sadly never was able to to begin with but im following stuff
Thanks
The anti downgrade (which people usually are referring to when they say “burning fuses)works by when booting the system, pk1ldr (initial bootloader) checks the ODM7 fuses to make sure the correct amount are burnt, if too few are burnt it’ll burn some, if too many are burnt it’ll immediately panic and go to a black screen
Last edited by ZachyCatGames,
I have a sincere question (Please go easy on me as I am very new to Switch modding)
I bought a Switch yesterday evening. I have a modded NN3DS with CFW/NTR, so I have at least basic understanding of setting up some of the software.
My ORIGINAL plan was to look through some of the beginner/support stuff to find out where to start.
My son was attempting to format the SD card and said that the system required an update before using the card so he updated to 8.1. (It's actually my fault for not specifying NOT to update)
I'm not even sure what firmware it was on because I only had a chance to setup the initial connections.
From what I am reading, I seem to be screwed until 8.1 is patched for CFW.
But in the meantime, can any of you direct me to some decent links here so I can look into efficient steps and programs starting off for CFW/Homebrew?
That way I'll at least have what I need and know what steps to take once 8.1 is cracked.
Thanks in advance for any help.
I bought a Switch yesterday evening. I have a modded NN3DS with CFW/NTR, so I have at least basic understanding of setting up some of the software.
My ORIGINAL plan was to look through some of the beginner/support stuff to find out where to start.
My son was attempting to format the SD card and said that the system required an update before using the card so he updated to 8.1. (It's actually my fault for not specifying NOT to update)
I'm not even sure what firmware it was on because I only had a chance to setup the initial connections.
From what I am reading, I seem to be screwed until 8.1 is patched for CFW.
But in the meantime, can any of you direct me to some decent links here so I can look into efficient steps and programs starting off for CFW/Homebrew?
That way I'll at least have what I need and know what steps to take once 8.1 is cracked.
Thanks in advance for any help.
1. Not nice to call your 7 year old stupid
2. Boot into your payload / bootloader and uninstall autoRCM
3. Wait for updated patches. Your switch isn't broke, just not able to use modified functions until new firmware patches are released, or you downgrade using Choidujour / use EmuNAND.
EDIT: Now that I think of it the update should have automatically disabled autoRCM unless you re-installed it. Should just boot normal without Jig. O.o
If all else fails,
Last edited by Shadow LAG,
Similar threads
