All tested games were carts.Cartridge or downloaded copies of the game?
All tested games were carts.Cartridge or downloaded copies of the game?
The DNS stuff won't block updates that come locally, they'll only block stuff that comes from the official online update URLIf you did do this previously where youyr dns settings set to manual to block updates?
Did you manually make sure any traces of an update we're deleted in maintanince mode?
yeah it's a bad idea as games get more and more updates it will work on fewer and fewer games and that's only if nintendo doesn't stop it from working right away.Kirby update requires 5.0.0. When using this method if the receiving system is too low to use the update the sending console also sends a system update with its firmware. I found that out last week when I tested this method. Hence why I didn't create a thread for it because it's a bit dangerous.
I already did thoroughly test this a week ago, and there is a reason why I didn't make a thread about it. It's an easy way to accidentally update to a non exploitable fw and I would avoid at all costs. Most game updates aren't a necessity to play the game.This is a sure fire way to piss people off when they end up with 2 Switchs on non exploitable FW.
I'd stick well clear of this before it's been thoroughly tested tbh.
Especially with 5.x.x games that will be coming up with the FW updates on the carts. Asking for trouble.
No, it just pushes the firmware from the 5.x+ system over to the receiving system. It's why I advise against this and never made a thread about it after I throughly tested it last week and discovered thatwhat's gonna happen when share a update that requires a higher firmware version on a lower firmware?
probably pop out some sort of updating notification?
Its already happened with Kirby, and people in this thread have already accidentally updated to 5.0.0what's gonna happen when shared a update that requires a higher firmware version on a lower firmware?
probably pop out some sort of updating notification? and wont be able to launch the game?
Huh. Does migration's local update sharing not validate both consoles are on the same version? That's super dumb.
Probably legitimate, good for you OP.
Don't really think it's useful given the updated console requirement, but meh. Neat.
I think Nintendo designed it this way. It will send over a firmware update too if the software update requires a firmware newer than the receiving system. Kirby update using this method from a 5.0.0 switch will update a 4.1.0 switch to 5.0.0 (or whatever firmware the sending system is on)Huh. Does migration's local update sharing not validate both consoles are on the same version? That's super dumb.
Probably legitimate, good for you OP.
Don't really think it's useful given the updated console requirement, but meh. Neat.
Welp, if you live in the US. Just go to Gamestop, buy a used Switch, if you get a good firmware, swap the tablets. Return the Switch with your 5.0.0 tablet, and keep the good firmware tablet. You get your money back at the end, so it doesn't really cost anything, but your time.
Gamestop employees tend to not give a fuck, and will probably just try and turn it on, and see if it powers on. lolFrom where I live, the warranty records the serial number of the machine. And by doing so above, it's consider fraud and apparently traceable as they got your credit card and on the CCTV. I highly recommend against it.
It works the same for both carts and digital. Except for carts with updates built in (which I haven't encountered yet) the updates install to SD/nand depending on if you have an SD installed. Most carts dont seem to have game updates installed on them either.Doesn't work the same way on physical copies, does it?
I'm on 4.1 and got a Kirby cartridge. Have a friend on 5.0.1
The update stores somewhere on the system and not on the cartridge, am I correct?