I was asking about the risks of actual restoration process, since the github releases page says it's dangerous.
If I restore a clean NAND backup, is there any risk of bricking or is it safe? I will wait for 3.1 before doing it.
If I restore a clean NAND backup, is there any risk of bricking or is it safe? I will wait for 3.1 before doing it.
Nope it's OK.
I tried restoring my 4.1 backup with it and it worked wonders.
Another user also did that and successfully downgraded.
So it is the same for no downgrade and just restoring a clean filesystem.
It is still considered dangerous by me though. It writes to your eMMC.
So there might have been a swap out (for at least that run of Switches) for a obtainable replacement controller that happens to be incompatible with TX's driver... I know this is all speculation but seems a reasonable assumption.
*edit*
oh btw, if you see this i know it might not be helpful at this point but i put my fast sd card in a switch and I'm trying a full backup with the 3rd fix. It has started the verification.
Last edited by IS_Nitro,
If the problem is the same with another user's, it's possible.
The other user that had this problem, on initialization, the card was replying garbage stuff, which were out of sd association's spec.
It is possible that this could be because of the controller's init incompatibility instead of the card incompatibility.
EDIT:
Btw, don't think that TX's driver is very different than hekate's and fusee's.
Last edited by CTCaer,
I've gathered as much from reading from the sidelines the last couple of days lol
Anyway, I don't care about SX OS.
But for hekate, I still want to add support for sdmmc controllers or sd cards like these. But now I only know of one user having that.
SX OS is slick but... yeah...
I like "hacking" for game saves. I always want control of my saves. Having BOTW, among others, on my switch with my playtime and no way to back it up made me nervous. Yeah, Nindy added cloud saves but if you piss em' off or get unlucky your access to that backup is gone. Not ideal.
Backing up the whole system is even better. Just in case the messing about goes too far.
(as if im actually doing any "hacking"... thats all you guys. Thank you for making all this by the way.)
secondary reason, save game editing. Once im done with a game i go a bit nuts with messing about in game. Maxed out explosives because i can? yes please.
I like "hacking" for game saves. I always want control of my saves. Having BOTW, among others, on my switch with my playtime and no way to back it up made me nervous. Yeah, Nindy added cloud saves but if you piss em' off or get unlucky your access to that backup is gone. Not ideal.
Backing up the whole system is even better. Just in case the messing about goes too far
.(as if im actually doing any "hacking"... thats all you guys. Thank you for making all this by the way.)
secondary reason, save game editing. Once im done with a game i go a bit nuts with messing about in game. Maxed out explosives because i can? yes please.
Last edited by IS_Nitro,
I'm on 4.1. I made a full backup of the NAND as per the instructions on the first page. Then I followed this guide to update to EXFAT support for the SD.
https://gbatemp.net/threads/how-to-install-the-exfat-driver-without-updating-2-x.505176/
I used a downloaded game to get the EXFAT update per the instructions but otherwise I've just played my own ripped games. I'm not having any issues reading from the SD card using SX OS on 4.1.
I didn't realize SX OS had built in EXFAT support like hekate or I might have skipped the second part. Although it sounds like it may be having an issue. Not sure if doing the manual EXFAT support update might have helped or maybe it's just a couple (one?) devices having issues.
https://gbatemp.net/threads/how-to-install-the-exfat-driver-without-updating-2-x.505176/
I used a downloaded game to get the EXFAT update per the instructions but otherwise I've just played my own ripped games. I'm not having any issues reading from the SD card using SX OS on 4.1.
I didn't realize SX OS had built in EXFAT support like hekate or I might have skipped the second part. Although it sounds like it may be having an issue. Not sure if doing the manual EXFAT support update might have helped or maybe it's just a couple (one?) devices having issues.
No it was not so its best to make another dump to verify if your original was good enough by comparing the two (or using the built-in now working verification process)
It was not as said before.
Best case scenario for you is this:
Wait for v3.1. Make a new backup.
Restore your old BOOT0/1 and rawnand.bin and check if it has problems.
If it is, restore your new backup. If no problem, continue as is, but keep both backups available.
Semi-working verification (like always..).
No. Only these 3.
But wait for v3.1 to make a new backup of your current state, in case restore goes wrong.
(This way, if the old backup you made, does not work, you can go back to what you had).
Then it's either of the 2 following things:
- fusee patches for 3.x are not correct
- Exosphere is still incompatible with 3.x
The thing is that I only backed up my rawnand before using layeredfs and not boot0/1. So it is the only pre layeredfs backup that I have, and I want to clear its usage from my system.
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
If your not getting your pills from Psi's discount drugs who knows what your swallowing!+1 -
@
Psionic Roshambo:
Shawnita used to get her pills from some other street pharmacist and after switching to The Psi Discount plan she now only has to swallow two things a day!+1
-
-
-
-
-
-
-
-
-
-
-
