this thread was asking if updating in sx os is an alternative to that
It's not, you can't update with dumps in sx os, tryed bayonetta 2 to update to 4.1 but nothing.
Hacking Question Will updating with a cart to 4.1.0 using SX OS 1.2 burn any fuses and are there any drawbacks?
- Thread starter Xenon Hacks
- Start date
- Views 11,297
- Replies 90
It's not, you can't update with dumps in sx os, tryed bayonetta 2 to update to 4.1 but nothing.
I think there's some problems with the official way of updating that SX OS doesn't let you do because SX OS doesn't let you access your NAND. Like some users who used the official way of updating after following that method were nagged with the system update is ready prompt and they had to delete something in order to remove it. Not sure if recovery menu fixes this problem as well.
D
Deleted User
Guest
Wow, lot's of confusion in this thread.
Since SX OS v1.2 the fuses will not be burnt and the fuse check is bypassed.
Since SX OS v1.2 the fuses will not be burnt and the fuse check is bypassed.
My sources say just update to 5.1.0. Won't matter in a few months anyways. I updated my current switch to 5.1.0 and my neon one will just be fake updated to 5.1.0 with exfat support installed. Original fw will stay 4.1.0 just in case the info is somehow false.
Yes you can update with a real cart to 4.X in SXOS without burning your fuses. If you boot without CFW (boot normally) your fuses will auto burn. If you downgrade back to below 4.X you can’t use real carts anymore due to a firmware mismatch with the cartridge chip firmware. No you can’t update using an XCI. If you want to keep your fuses safe you would want to use AutoRCM.
So if we are in SX OS and insert a game cart to update to a higher firmware it won't burn fuses?
Is this tested to be functioning?
I thought SX OS won't let you update at all, and just always disables the fuse check at boot after you updated with rajkosto's method.
source???
SX OS 1.1 prevents the fuses from being burnt but didn't bypass the fuse check. This was why users were told to avoid it with his method because if you updated without burning fuses, you cannot load SX OS anymore with their loader. 1.2 now implements the fuse check so they're identical when it comes to fuse burning and bypassing. Only issue is you risk burning fuses if you don't use their loader to boot the Switch since the Switch's built-in bootloader will burn the fuses. AutoRCM is intended to prevent that from ever happening.
Maybe they use rajkosto's code as their fuse check
I already know about the bypassing of the fuse check in v1.2, but can you update directly in SX OS without burning fuses? I didn't heard about anyone who've done that.
Theoretically, you should be able to since rajkosto could not recommend using the SX Loader since it did not prevent fuse burning and bypass the fuse check. If TX isn't lying in their changelog, yes you should be able to do it. If you're telling me you are waiting on someone else's opinion on whether it is safe or not, then you have to re-consider how much you trust TX.Maybe they use rajkosto's code as their fuse check
I already know about the bypassing of the fuse check in v1.2, but can you update directly in SX OS without burning fuses? I didn't heard about anyone who've done that.
I thought the update process should be like:
1. Update with rajkoto' method to new firmware without burning fuses (includes first time booting of new firmware)
2. Launch TX OS which should now be running on the new firmware and hope that it didn't burn fuses
Like I said, SX OS did not have the necessary features to be fully substituted with this guide but based on what TX is saying, it can be now. It should also be noted that if you were to do it without the official update, you have to use Hekate to dump the NAND since SX OS does not support that. So to be clear, you can use SX OS with rajkosto's tutorial but only if you are updating the official way. And you must still be careful not to boot the Switch without entering RCM first as you will burn the fuses otherwise.
Alright so then my only feasible option is to enable auto rcm and follow the update tutorial and go to 5.1.0 and hope it never boots normally, but what about the cartridge slot if I restore from a Nand backup does that mean it gets trashed if I downgrade? Also if I were to update to lets say 6.0 in the future officially would this fix the broken cartridge slot?
Your cartridge stops functioning only if you update over 4xx without bruning fuses and then restore your NAND to <4xx.
Only then you can't run carts while your <4xx. If you now again update over 4xx your cartridge is functioning again.
So has anyone tried updating from a physical cartridge from "within" SXOS yet? Did it burn the fuses?
This has been said in a few threads, but no one has said they've done it. Just that you can.
My understanding was that they fixed a flaw when you upgraded without burning fuses and booting into Sx os burnt them anyway. not that it lets you update without burning fuses.
--------------------- MERGED ---------------------------
From the updating guide:
SX OS 1.2 WILL WORK FOR 2nd BOOT AND AFTER, FIRST BOOT YOU MUST STILL FOLLOW GUIDE.
My question still stands. Nobody has confirmed it.
My point exactly, I want to stay in range for fusee Gelee but also avoid tampering with my switch in a semi complicated way.
fusee Gelee works on up to 5.1.0, I think what you meant was staying with 3 fuses or less in case coldboot comes our way?
I know, Ive asked every person in every thread that said it works... But the question remains unanswered. I don't think it works. Raj's guide still needs to be followed.
Similar threads
