Hacking Question I accidentally updated to 5.0 while playing mario

Didn't they say they have a hardware and software solution that nintendo won't be able to block ??? or did I get that wrong.
They said they have a bootrom exploit that can't be patched, but it may require other exploits that can be patched to install from software. With hardware its unpatchable. We just discussed this earlier in the thread
 
What will happen to vgc now only people who got the switch early in its life will be able to cheat.

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

At that point you will likely brick. Especially given the 5.0.0 update changes every title and re-encrypts with a new key. No matter what if you do that something will break.
it just restores the previous update if you do this like all modern consoles do.
 
If you buy a new Switch ASAP it might have the old bootrom and firmware 4.10. If you choose to stick with your 5.0 Switch you'll be waiting a lot longer for homebrew. In a moment of stupidity a month or two ago I also updated by accident.

From what I can gather Nintendo rushed the Switch's launch and the 1.0 firmware was a beta firmware which had some pretty big security flaws. But with each update Nintendo has been very diligently making the Switch their most stable system yet.
 
Last edited by ,
You can brick. That's why it says don't power off console. You can try it tho lol
Windows says that too.
I will doubt it until someone proves it :D (and I really don't want to leave 1.0.0 master race). Normal systems download the update and then apply it, but I have no idea how it is with Switch.
 
Last edited by Kubas_inko,
I'm fairly certain if you shutdown during a "firmware" update can brick. Regular software updates will usually do a roll-back to the previous version and start over or continue on the next reboot.. But firmware updates are typically different or progressive and can leave you in a state of unknown.. Similarly, you can't shutdown during a BIOS update or you have to re-flash the BIOS.. but you can shutdown during windows updates and driver updates (most of the time).

The difference? Firmware is usually very close to the hardware but regular software is virtualized. It really really becomes device specific at this point. Some devices have very little memory and get flashed immediately (some embedded devices) and shutting down will screw them..

Back in the PSP 1.5 to 3.71 M33 days, shutting down in the middle of the update would brick you and required a pandora's battery to re-flash the entire thing. It happened to me and I had to make a battery by cutting the side and soldering the silver piece and also purchasing a new battery for regular use.. :(


In any case, OP already screwed up so at this point it doesn't matter lol.
 
Last edited by JustBrandonT,
Windows says that too.
I will doubt it until someone proves it :D (and I really don't want to leave 1.0.0 master race). Normal systems download the update and then apply it, but I have no idea how it is with Switch.
The switch does firmware updates, windows does patches. You can brick your console for all I care
 
ut firmware updates are typically different or progressive and can leave you in a state of unknown.. Similarly, you can't shutdown during a BIOS update or you have to re-flash the BIOS.. but you can shutdown during windows updates and driver updates (most of the time).

While in general your mental model here is correct it is a bit outdated. "Firmware" is a generic term. While traditionally it implied to "hard override" data, that is no longer necessarily true. Just like vehicle is not the same thing as in 1776.

Even when a hard override is performed, this does not necessarily imply a brick or that it can not roll back depending on the block-level implementation. And even then, the PSP as you said is recoverable, fastboots typically too. Bricking by no means is the norm anymore.

For switch I don't think you have such a system in place. I am somewhat certain that the NAND is mounted and written to on the file level, likely in a commit-based manner. I may be wrong, but I don't expect to.
 
  • Like
Reactions: Kubas_inko
Hope for team X, its personally what I'm doing. I honestly don't mind spending a bit for homebrew, and it beats the shit out of waiting around constantly on a particular firmware. If your desperate to play homebrew on a console go buy a Wii, my girlfriend recently brought one from a retro store for $15, I would much rather enjoy play Dark Souls remastered, the Pokemon games, Smash Bros... and this years worth of amazing games that will require 5.0 than sit hoping for the future of softmod homebrew on the switch, but thats just me :P. Also if they deliver as they say they will, updating software will not matter. Its exactly the reason that nintendo are revising the current Tegra chip and will fairly soon re-release the consoles with more secure hardware.
 
Hope for team X, its personally what I'm doing. I honestly don't mind spending a bit for homebrew, and it beats the shit out of waiting around constantly on a particular firmware. If your desperate to play homebrew on a console go buy a Wii, my girlfriend recently brought one from a retro store for $15, I would much rather enjoy play Dark Souls remastered, the Pokemon games, Smash Bros... and this years worth of amazing games that will require 5.0 than sit hoping for the future of softmod homebrew on the switch, but thats just me :P. Also if they deliver as they say they will, updating software will not matter. Its exactly the reason that nintendo are revising the current Tegra chip and will fairly soon re-release the consoles with more secure hardware.
But nintendo is going for slight hw revision already (I think).
 
Still.. it can download the fw update first and then apply it.
When switch prompts you to update, the update is already downloaded (it downloads in the background beforehand) and when you click install it immediately begins applying the update. So no you are still wrong there.
 

Site & Scene News

Popular threads in this forum