Hacking Update 2.1.0 out.

  • Thread starter Thread starter zoogie
  • Start date Start date
  • Views Views 38,423
  • Replies Replies 152
  • Likes Likes 6
Can anyone confirm forced updates like the Wii U? I'm gonna block out the network for my Switch until the URLs are figured out.
 
To get rid of the update nag:
  • Set 205.166.76.187 as your primary DNS in the settings
  • Complete power off the console (hold power button > Power Options > Power Off)
  • Turn back on
Does anybody know who's DNS this is, I'm assuming that they have the url's needed to block updates which would probably be more beneficial than just a DNS?
 
Don't have much reason to care to stay on the old firmware or update either, just waiting for the upcoming month's retail games at most.
 
Just upgraded a new Switch from 1.0.0 to 2.1.0. Pegaswitch on console refreshing endlessly, debug log reads "Success percentage: 0.00 (100 samples). Exploit failed."

Could you tell us if you had to do 2 updates or if it was just one update from 1.0 to 2.1?

My switch will arrive tomorrow and I wonder if I can still update to 2.0 version.
 
I'm not familiar with it but this may be due the missing update or the DNS may block friends / eshop related things too.

Feel free to correct me if im wrong.
 
This update is great. It has enhanced my user's experience.
Your user's experience? Does someone pilot you around with an RC controller?

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

Just upgraded a new Switch from 1.0.0 to 2.1.0. Pegaswitch on console refreshing endlessly, debug log reads "Success percentage: 0.00 (100 samples). Exploit failed."

Not super surprising -- there were changes made to the open source release in 2.1.0 ( see https://www.nintendo.co.jp/support/oss/index.html ) that look plausibly related:
So...don't update? Or are these results any better on 2.0.0?
 
Could you tell us if you had to do 2 updates or if it was just one update from 1.0 to 2.1?

My switch will arrive tomorrow and I wonder if I can still update to 2.0 version.

One update, direct to 2.1. I didn't see any indication of the new version until the update completed.

EDIT: Xzi -- my understanding is PegaSwitch works on 2.0.0, so if you have 2.0.0 and want to use PegaSwitch, probably hold off on the update to 2.1.0 until somebody locates another exploit or repairs the current one.

I am curious whether a hardware downgrade is possible although I didn't have an appropriate tri-wing screwdriver handy when my console arrived so I don't have a backup of the 1.0.0 eMMC.
 
Last edited by adrake,

Site & Scene News

Popular threads in this forum