Ok, but you can still downgrade as long as the major number hasn't changed.
https://switchbrew.org/wiki/Fuses#Anti-downgrade
Ok, but you can still downgrade as long as the major number hasn't changed.
There are many .XCI splitters if you search them either on Google or in this forum. I am also not sure that SX OS can install split .XCI files but I suppose it never hurt to try.I formatted my microsd card as fat32, how do I copy xci files onto it that are larger then 4GB. is there a "splitter"?
Would xci cutter? Then will SX join them again when installed?
Your NAND backup isn't entirely useless but if you do restore one that has a firmware less than your fuse count, you will only be able to boot after restoring that backup in RCM and bypassing the fuse check.dang i didnt know that I guess if i accidentally burn my fuses i should just make another nand backup
It did. Delete reinx.bin from your sd card. also make sure you are pushing the new payload
Do. Not. Update. 4.1 is the most vulnerable to the new version of pegaswitch meaning you will be able to do more with it, maybe even cfw.
The save file is technically on the micro SD card but its embedded within the file that SX OS created. I'm assuming Checkpoint can retrieve the save files since EmuNAND has been out for a while and nobody has complained about this yet.I'm using SX OS and Emunand (not hidden, on micro sd card) to play games and now I'm wondering where the save files of the games are located. Do I need to use Checkpoint to backup the save files or do I just need to copy some files from the micro sd card?
Sure. Although I myself am not personally advising this, I updated my firmware without burning fuses to 6.2 with Atmosphere. What I did was download the system update in stock/OFW, install the update in CFW (Atmosphere), then reboot back into stock/OFW with Hekate. Not saying this is safe but if you want to update without burning fuses to 6.2, this is the route I suggest. An alternative is to reboot back into RCM after the system update is finished installing.hi
i have a question about NES online
i don't have account linked to switch, so even if i pirated the nsp file it wont works, but if i decide to risk it and linked my account, then got banned, can i still launch NES online?
what i am thinking to prevent the ban, is to restore my old clean NAND 4.1, then update OFW to 6.2 then link my account, then make my system offline, can i still launch the games? or i must log to nintendo?
thanks, but you didn't answered my whole question, if i get banned, can i still use or launch the app?Sure. Although I myself am not personally advising this, I updated my firmware without burning fuses to 6.2 with Atmosphere. What I did was download the system update in stock/OFW, install the update in CFW (Atmosphere), then reboot back into stock/OFW with Hekate. Not saying this is safe but if you want to update without burning fuses to 6.2, this is the route I suggest. An alternative is to reboot back into RCM after the system update is finished installing.
If you don't care about fuses and subsequently downgrading, then just update normally. Also make a new NAND backup after you burnt your fuses since the old one can only be booted through RCM via bypassing the fuse check if you restore it.
Sorry. The game will work even if you're banned.thanks, but you didn't answered my whole question, if i get banned, can i still use or launch the app?
bypassing the sign in is the most important thing.
ok, that's good thing.Sorry. The game will work even if you're banned.
Same. I saw that as well and was going to just mention it in passing but I don't think OP had a lot of luck with it.ok, that's good thing.
i saw that method to inject another NAND (that contain another user linked) to my NAND, but it looks dangerous.
I'm assuming since you have a complete NAND backup, it won't hurt to try the patch suggested in the other thread so that if anything goes wrong, you can just restore your NAND which you do if you were going to update in the first place. Two birds, one stone.so now my options is:
1- update (by any method) and then link my account.
2- inject or make fake linked account by using app.
3- patch the system or the app so it wont asks for linked account (this is useful if you want to post to twitter directly without account and sign in to nintendo)
by injecting other NAND, does it matter what FW?I'm assuming since you have a complete NAND backup, it won't hurt to try the patch suggested in the other thread so that if anything goes wrong, you can just restore your NAND which you do if you were going to update in the first place. Two birds, one stone.
After rereading the thread, seems like OP got it to work but someone else was having trouble. Might be related to the CFW they were using. OP used ReiNX and it worked fine while the other user had SX OS. Both were using it on 6.X. I don't think the files in that thread are firmware-specific but it seems like all of the testing was done on 6.X based on that thread.by injecting other NAND, does it matter what FW?
i am on 6.2 CFW, still 5 fuses burnt, so i can go back to 4.1.
what FW does that NAND have? will it change anything or just inject the profile?