Hacking advice needed (which switch to keep legit)

Random Joe · Jul 28, 2018

I have a 4.1 nintendo switch with a bunch of retail carts that I have kept offline for awhile.

I decided I wanted to be able to play a few games online so I bought another switch to be legit and update.

The new switch is on 3.0.1.

Any thoughts how to proceed? Should I take the 4.1 switch and have that be my legit one? I'm assuming 3.0.1 will be better for hacks anyways right?

I am getting the SX Pro

gameus · Jul 28, 2018

There is never going to be CFW online with no ban capabilities. There will always be a chance. It doesn't really matter which one, but if you at one point want to be able to boot CFW without using a jig + RCM, then the 3.0.1 is your best bet to keep outdated. You can always use Checkpoint or a different save manager to backup all of your saves from your 4.1 device. But honestly with how easy it is to launch things through RCM nowadays, it doesn't matter, personal preference.

Oleboy555 · Jul 28, 2018

lower = better

Random Joe · Jul 28, 2018

gameus said:
You can always use Checkpoint or a different save manager to backup all of your saves from your 4.1 device.

Doesn't this require hacking though? Potential ban just to backup the saves?

gameus · Jul 28, 2018

Random Joe said:
Doesn't this require hacking though? Potential ban just to backup the saves?

There's always going to be a ban risk when using homebrew, but if you keep a switch offline and use it for homebrew purposes, nothing will happen to you. This is what I recommend. Update your 4.1 switch to the latest and use that as your legit switch. Keep your 3.0.1 where its at and use that for homebrew. You do not need an internet connection to take advantage of homebrew or CFW.

Random Joe · Jul 28, 2018

gameus said:
There's always going to be a ban risk when using homebrew, but if you keep a switch offline and use it for homebrew purposes, nothing will happen to you. This is what I recommend. Update your 4.1 switch to the latest and use that as your legit switch. Keep your 3.0.1 where its at and use that for homebrew. You do not need an internet connection to take advantage of homebrew or CFW.

Big thanks

QRC · Jul 28, 2018

Doesnt matter. Firmware 3 cant run newer games and latest firmware is fully supported.
Just backup your nand with hekate and keys with biskeydump. You can restore Fimrware 3 any time if you have that data.

I did: Backup stock firmware , update to 5.1 and insert SD card with exFat format then it will install new drivers, then backup that too.
After you finished, ZIP the folders it will shrink by 80%

Dvdxploitr · Jul 28, 2018

Despite the fact that I honestly don't think staying on lower firmwares is worth it, I would update the 4.x system to latest firmware....I think game compatibility with TX OS is 100% or very close to it. Keep the other one at 3.01. People keep saying that lower firmwares have higher chance of "Coldboot" but, I don't see the big deal about it really. I mean, once you get a selection of games on your system to keep you busy, how often are you going to shut the system down anyway? Also, if you go with TX OS Pro, you get a jig to make RCM mode and injecting a payload very easy.

Random Joe · Jul 28, 2018

QRC said:
Doesnt matter. Firmware 3 cant run newer games and latest firmware is fully supported.
Just backup your nand with hekate and keys with biskeydump. You can restore any time if you have that data.

I don't see how restoring your nand and keys will keep you from getting banned though. Isn't there log file at that point that you used homebrew?

--------------------- MERGED ---------------------------

Dvdxploitr said:
Despite the fact that I honestly don't think staying on lower firmwares is worth it, I would update the 4.x system to latest firmware....I think game compatibility with TX OS is 100% or very close to it. Keep the other one at 3.01. People keep saying that lower firmwares have higher chance of "Coldboot" but, I don't see the big deal about it really. I mean, once you get a selection of games on your system to keep you busy, how often are you going to shut the system down anyway? Also, if you go with TX OS Pro, you get a jig to make RCM mode and injecting a payload very easy.

i was planning on keeping one legit without any hacks. And one to use with SX PRO. But now I'm wondering if 3.0.1 with SX PRO is bad idea because I'll be limited to the 3.0.1 games.

QRC · Jul 28, 2018

There is no benefit staying on 3...doesnt matter if banned or not.

Random Joe · Jul 28, 2018

QRC said:
There is no benefit staying on 3...doesnt matter if banned or not.

So your move would be to update both. One plays legit game carts. The other SX PRO offline. Forget about cold boot in future? Cold boot is a big deal to me. But I don't care to wait years for it.

GBCTEMP · Jul 28, 2018

I would personally keep the 3.0.1 as is, and play games that are only available up to that firmware. I'd do that to see what the scene brings in the future, i.e untethered coldboot.

Random Joe · Jul 28, 2018

What about this......
Backup my 4.1 Nand
update my 4.1 switch without burning any efuse.
use legit game carts online and sx pro offline.
see if ban ever comes

Leave my 3.0.1 in closet collecting dust waiting for cold boot.

benson733 · Jul 28, 2018

Keep the lower firmware console for hax.

bundat · Jul 28, 2018

Hmm... If you update the 4.1 without burning fuses (either via rajkosto's HARD and LONG method, or via the simple method where you QUICKLY boot into RCM with a jig after an official update to prevent the fuses burning on reboot), you don't have to worry about not burning your "cartridge fuses".

So you'd be able to update from 4.1 to 5.1, then downgrade back to 4.1 and still have your cartridge slot working.

On the other hand, if you update the 3.0.1 to 5.1 without burning fuses, you have to ALWAYS run with nogc.kip1 on, so that your cartridge slot will still work when you downgrade back to 3.0.1. But nogc makes your switch SLOW (lags on wakeup), and it makes your cartridge slot unusable while you are at the higher 5.1 firmware.

Also, deja vu (the unreleased warmboot[?] exploit) supposedly works on 4.1.
So imo, using your 3.0.1 as the "hacked switch" seems like more of a hassle because of the nogc disadvantages.

Personally:

I'd NAND backup BOTH switches, then keep the 3.0.1 in that version (for possible future emuNAND use in whatever the latest firmware version would be then),
then update the 4.1 (without burning fuses, by doing an official update, then QUICKLY rebooting into RCM with a jig), so that this can be the "OFW" switch on latest firmware (albeit with unburned fuses, and autoRCM to protect my fuses)

...but then that counts as hacking them both.

Dvdxploitr · Jul 28, 2018

No one knows when a coldboot will come along...however with the rate of progression on the Switch hacking scene, it could be here the day after you update. Or you could be sitting on that 3.0.1 firmware and someone develops a coldboot method for the latest firmware that is out at the time and there was really no point in keeping a system on 3.0.1 after all...but who knows what the future holds for Switch hacking...Take the PS3 scene for example. It's kind of similar. On 3.15 firmware, you needed a dongle and to press eject then power to inject a code into the system. With the Switch, we have to get into RCM mode to inject a payload. Higher firmwares came out for the PS3 and next thing you know, we have coldboot CFW for higher firmwares (like 3.55) meaning that staying on 3.15 and injecting a payload was pointless. You had to have a dongle and press eject then power, and you were restricted from using newer games as well. Granted, I know that method is about 7 years old and security has significantly improved, however, it's still very similar to what we are doing with the Switch...

Ian095 · Jul 28, 2018

Update the 4.1.0 to 5.1.0 and use Sig Patches. Keep the 3.0.1 at that firmware for possible Atmosphère use in the future.

Hacking advice needed (which switch to keep legit)

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

¿

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum