Hacking 6.0.1 released

  • Thread starter Thread starter Naked_Snake
  • Start date Start date
  • Views Views 40,055
  • Replies Replies 137
  • Likes Likes 4
Is it safe? YES!!!!
Should you update?:Depends on if u wanna idk maybe have an older firmware (use tx's emunand to update)
bye

Supposedly it bricks the Emunand.

"Is it safe" becomes "it depends". If you use themes or "Emunand" - then no. If you use neither - should be safe as it's a minor version bump (same fuse burn count as 6.0).
 
Last edited by Flying Scotsman,
F-That I just updated to v6.0 about a week ago. Plus! I already burned enough fuses on my Switch.

I'll just stay parked at v6.0 or I'll just go into RCM Mode and use ChoiDujour when v6.0.1 becomes available for download...

PS
My Switch seems to be running smooth on v6.0 and even if no fuses were not to burn while updating to v6.0.1 I still don't trust this update.
Unless it's 120% confirmed that is save to upgrade to v6.0.1....
 
Last edited by SoCALCat,
I stayed at 5.1.0

F-That I just updated to v6.0 about a week ago. Plus! I already burned enough fuses on my Switch.

I'll just stay parked at v6.0 or I'll just go into RCM Mode and use ChoiDujour when v6.0.1 becomes available for download...

PS
My Switch seems to be running smooth on v6.0 and even if no fuses were not to burn while updating to v6.0.1 I still don't trust this update.
Unless it's 120% confirmed that is save to upgrade to v6.0.1....
 
  • Like
Reactions: KK31184
TX just posted a bug fixed SXOS 2.01 a few hrs ago and Nintendo countered with 6.01. :D
This is why I rather stick with 6.0...:switch:

Who knows! Other than taking the chance on getting banned. Maybe Nintendon't has something up there sleeves by trying to get into a back door so they could brick or screw things up for anyone that has there Consoles Modded... :ninja:

It just seems very strange on how all of the sudden Nintendon't dropped a new OFW so soon...:gun:
 
Last edited by SoCALCat,
Apple also just released iOS 12.01 update a few hrs ago. This is a very strange day.
This is why I rather stick with 6.0...:switch:

Who knows! Other than taking the chance on getting banned. Maybe Nintendon't has something up there sleeves by trying to get into a back door so they could brick or screw things up for anyone that has there Consoles Modded... :ninja:

It just seems very strange on how all of the sudden Nintendon't dropped a new OFW so soon...:gun:
 
i read on this thread again that normal updating burns fuses, but what does that mean ?

i was on 5.x some weeks ago and updated with that homebrew app called choujoerux? i updated to 6.x with that app, that did not burn fuses, but whats the benefit of not burning the fuses guys?
 
i read on this thread again that normal updating burns fuses, but what does that mean ?

i was on 5.x some weeks ago and updated with that homebrew app called choujoerux? i updated to 6.x with that app, that did not burn fuses, but whats the benefit of not burning the fuses guys?

When you install a Update, it checks for your fuses. For example you can not downgrade to 4.0 if you already burned 6 fuses. Everytime you update fuses getting burned. It's Ns way to prevent users from downgrading. But when you didn't burn your fuses you can downgrade. For example : you are on 6.0 with 3 fuses burned. You can go all the way down to 3.0. But be carefull! Starting your switch not in rcm mode will automatically burn your fuses no matter how long your updating process lays in the past
 
  • Like
Reactions: leonmagnus99
What does that mean exactly? The link is not very clear. Does it mean that updating to 6.0.1 on sysnand trashes the emunand partition? Or is it only when updating on emunand?

For those wondering, thaikhoa's post below explains quite well what the issue is and how to fix it. He also confirmed that BOOT1 is identical between 6.0.0 and 6.0.1 so this method is safe.

Sysnand 6.0.1
Emunand 6.0.0
WORKS Perfectly.

The problem is when updating Sysnand, the firmware will patch BOOT0/1. Emunand signature is on BOOT1, after updating, SX OS won't recognize Emunand anymore.

Solution: Backup BOOT1 (unchanged after updating) when having Emunand setup.

Use Hekate to restore BOOT1 back after updating System to 6.0.1
 
TX just posted a bug fixed SXOS 2.01 a few hrs ago and Nintendo countered with 6.01. :D
It took Nintendo nearly half a year to release an update that stopped the pin bending joy con exploit and most people just used a jig instead so they aren't timely
 
  • Like
Reactions: peteruk
I red in my fb group that 6.0.1 broke sx os and it now black screens on them when payload is injected. Anybody here on 6.0.1 and sx os?
 
I've updated to 6.0.1, last update I've updated by choiduijornx, the fuse is 6, today I press error and update to system. Now rajnx, hekate when I choose cfw it black screen, and fuses burnt are 7, how can I boot cfw ?

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

I red in my fb group that 6.0.1 broke sx os and it now black screens on them when payload is injected. Anybody here on 6.0.1 and sx os?
the same, I press retroNX in dashboard and It say update, I dont read clearly and press error, fw now is 6.0.1 and cant boot to cfw (black screen)
 

Site & Scene News

Popular threads in this forum