Does anyone have the current Tits Pro host address? It looks like it got moved around again at some point recently and I'd like to get back in there
Does anyone have the current Tits Pro host address? It looks like it got moved around again at some point recently and I'd like to get back in there
Damn! That's a real shame. Guess I'll just have to live with waiting two weeks for releases, cuz lord knows i'm too lazy to find and transfer the roms from the internet lmaoI believe it got nuked.
Guys
My
Switch is still playing up. Is there a way I can refresh and restart
What should I format my sd card ? Fat 32 or exfat
I want to be able to transfer large files
I did when v1 switch first was available to be modded and running from sd card and a jig / rcm loader I have
Any other tips ?

Can you boot into OFW at least? Do you have an unpatched v1 Switch?Guys
My
Switch is still playing up. Is there a way I can refresh and restart
What should I format my sd card ? Fat 32 or exfat
I want to be able to transfer large files
I did when v1 switch first was available to be modded and running from sd card and a jig / rcm loader I have
Any other tips ?
Did you install your CFW to your sysNAND or emuNAND? Which firmware is your OFW on?hey guys, i bet this question has been asked a million times here but i hacked my Switch back in 2018 and just updated the CFW a few times after that. There has been a lot of new methods that came out over the years and i saw that its possible to have a clean stock FW to play online and a CFW launchable on the same switch and still be relatively safe. I still got my backup from 2018 before i hacked my switch and checked the burnt fuses that shows 8 burnt (6.2.0).
Does anyone know how to set this up in the safest way possible?
Thanks for the reply, im 100% sure that i didnt connect my Switch to the internet for the entire time after hacking it, it has been on airplane mode since then. I just used the Haku33 method and wiped everything, my Switch didnt launched after that though, i got an fusee-secondary.bin error and after a little bit of research ive found out that fusee-primary and secondary doesnt exist anymore so i restored my old 2018 backup. Everything seems to work fine atm. Eshop launched and Fortnite is working as well, so i guess im not banned, at least not yet. Ive read that it can take a while before they ban someone, so i guess time will tell. Im trying to set up an emuNAND rn. Thank you for ur advise, ill take a look into these guides.Can you boot into OFW at least? Do you have an unpatched v1 Switch?
exFAT is more prone to the data corruption, while FAT32 isn't as much. Why do you want to transfer large files? What kind of files?
If you're able to boot into OFW without issues and you haven't blanked your prodinfo in the past, you can probably start from scratch by following one of these guides: NH Switch guide and Rentry.org Switch guide.
Did you install your CFW to your sysNAND or emuNAND? Which firmware is your OFW on?
By no means I'm expert on resetting the console and starting from scratch, but as far as I know, restoring an older NAND backup should be safe only if you haven't connected to the Internet without blocking the Nintendo servers on the OFW after you've made your backup. If you did connect to the Internet and haven't blocked Nintendo servers, your sysNAND has made some permanent changes while connected to Nintendo's servers that are not present in your original NAND backup. In other words, Nintendo has something more in their logs about your Switch, while you do not, therefore causing a mismatch.
I'd advise you not to restore your NAND backup blindly unless you're 100% sure that you were offline and in airplane mode between the time you've hacked your console and now. If that's the case, restoring a NAND backup should be safe enoguh.
More often than not, you don't need to restore a backup if you've used emuNAND and effectively blocked Nintendo servers.
If you can boot into OFW, connect to the Internet and access eShop and other Nintendo services, your sysNAND should be fine and you can start from scratch on how to setup emuNAND by following one of the guides, NH Switch guide or Rentry.org Switch guide.
Once you set up your emuNAND, I'd advise that you set up 90DNS or DNS MITM at the very least. Prodinfo blanking on emuNAND probably won't do much since it's unknown whether that info is cached somewhere else on the system. DBI, for example, can guess your serial number through "creative coding" as they call it. You can see whether it's true or not by going into system info option once in DBI.

I usually install my games and their latest updates with DBI and so far I've never run into that issue. I'd suggest that you give it a try and reinstall the game with the latest updates with DBI and see if you run into the same error again. Here's a good video showing how it works (that's how I used it since the first day I've hacked my Switch).I have some games that requires me to download a game update (even if I "Start Software" it still downloads in the background). This happened because I didn't have MITM. Now I have MITM so when it tries to download an update it doesn't work. If I launch a game and then press home button, then try to go back to the game, I get an error. I tried using Goldleaf to reset the game versions (I did this on the Base game, not on any installed game updates) but this didn't work. How can I fix this?

question,
can Emunand firmware higher than sysnand?

what would cause emunand blue screen in that case?

solid blue, I doubt is just due to lower/unsupported hekate/AMS version.You mean Atmosphere crash screen? or solid blue screen?
solid blue, I doubt is just due to lower/unsupported hekate/AMS version.

yes, haven't got the device on hand yet, but the customer said he updated firmware to 18.0.1 and blue screen happenedDoes Sysnand ofw boot?
yes, haven't got the device on hand yet, but the customer said he updated firmware to 18.0.1 and blue screen happened
Can you boot into OFW at least? Do you have an unpatched v1 Switch?
exFAT is more prone to the data corruption, while FAT32 isn't as much. Why do you want to transfer large files? What kind of files?
If you're able to boot into OFW without issues and you haven't blanked your prodinfo in the past, you can probably start from scratch by following one of these guides: NH Switch guide and Rentry.org Switch guide.
Did you install your CFW to your sysNAND or emuNAND? Which firmware is your OFW on?
By no means I'm expert on resetting the console and starting from scratch, but as far as I know, restoring an older NAND backup should be safe only if you haven't connected to the Internet without blocking the Nintendo servers on the OFW after you've made your backup. If you did connect to the Internet and haven't blocked Nintendo servers, your sysNAND has made some permanent changes while connected to Nintendo's servers that are not present in your original NAND backup. In other words, Nintendo has something more in their logs about your Switch, while you do not, therefore causing a mismatch.
I'd advise you not to restore your NAND backup blindly unless you're 100% sure that you were offline and in airplane mode between the time you've hacked your console and now. If that's the case, restoring a NAND backup should be safe enoguh.
More often than not, you don't need to restore a backup if you've used emuNAND and effectively blocked Nintendo servers.
If you can boot into OFW, connect to the Internet and access eShop and other Nintendo services, your sysNAND should be fine and you can start from scratch on how to setup emuNAND by following one of the guides, NH Switch guide or Rentry.org Switch guide.
Once you set up your emuNAND, I'd advise that you set up 90DNS or DNS MITM at the very least. Prodinfo blanking on emuNAND probably won't do much since it's unknown whether that info is cached somewhere else on the system. DBI, for example, can guess your serial number through "creative coding" as they call it. You can see whether it's true or not by going into system info option once in DBI.