Hacking 6.2.0 released

  • Thread starter Thread starter nachuz
  • Start date Start date
  • Views Views 57,672
  • Replies Replies 222
  • Likes Likes 1
Now that you mention it, if the switch rechecks the fuse count was indeed the case then shouldn't those who updated without burning fuses burn their fuse when their switch wakes up from sleep mode?
Yeah that would be very weird if Nintendo allowed the firmware to check the fuses after sleep but still didn't give it permission to burn new ones itself...
 
I'll be using SD emunand 6.1 using SX OS for brew stuff, while playing my official games online using sysnand on 6.2.
 
I'll be using SD emunand 6.1 using SX OS for brew stuff, while playing my official games online using sysnand on 6.2.
So have you applied that method now? Set up SD emunand for 6.1 and then updated sys to 6.2? Or are you holding back?
 
So have you applied that method now? Set up SD emunand for 6.1 and then updated sys to 6.2? Or are you holding back?
Tonight, when I get back from the movies. I said in another thread yesterday I'd be updating to SD emunand when SX OS 2.3 is out of beta, or when a new firmware hits the scene. Ironically the latter took less than 24 hours to happen. Time to put my money where my mouth is.
 
I had SXOS 2.0.1 with 6.1.0 for like 2 weeks. Only played xci and nsp backups, airplane mode all the time. Decided to go back to OFW 2 days ago. Restored a 6.1.0 NAND backup done through SXOS RCM Menu BEFORE installing any CFW (so it was definitely clean). Online worked fine for this 2 last days. This morning got a 6.2.0 update request and now I get "This nintendo account cannot be used at this time, this user can't use online features" when trying to acces e-shop or add new nintendo account. Later inspection on error history found code "2154-2005" that doesn't appear in nintendo's error logs. Technical support for nintendo on the phone said to try connecting and disconnecting wifi, deleting it and adding it again, try other internet connections etc. None worked. I'm now being told to send it in to check.

Any solutions, further info about this error and why it happened. I'm pretty shure I did all the possible to avoid any "known" ban (No internet on CFW, OFW Nand backup and restore)
Why are you spamming the site? Didn't you create a thread with this same copy pasta wall of text?
 
Yeah that would be very weird if Nintendo allowed the firmware to check the fuses after sleep but still didn't give it permission to burn new ones itself...

Well it is possible that burning fuses is something that can only be done at boot time by the bootloader. When installing a system update, the fuse is actually burned only when the system restarts. So I would think that it's possible the system has no way to burn a fuse when it wakes up from sleep mode.
 
  • Like
Reactions: PT333 and LeMageFro
Can you clear this one out, it still wakes up, it just take more time to do so? Or it doesn't wake up at all?
Since 5.x it takes a couple of seconds (2, max 3) to wake up. When i had 4.1 it woke up instantly. Idk maybe was that thing they implemented that creates that delay
 
  • Like
Reactions: ScottNBNP
Hey, quick newbie doubt, if I have SX Emunand on SD in 6.1, I still shouldn't update sysNand? it "breaks" the emunand or it'just breaks the non emunand cfw boot?
 
Emunand 6.0 still boots even on a 6.2 sysnand switch, so as long as emunand is not updated to 6.2, emunand will still work.
Are you sure you don’t mean the other way round, ofw/sysnand on 6.0 & emunand on 6.2? If it was the way you mention that’s impossible because you wouldn’t be able to boot sx on ofw 6.2 at first to access the emunand on 6.0 just checking. If your saying emunand works on firmware 6.2 that’s good news I was thinking about doing that myself did you just click on update in emunand like you would on ofw.
 
Last edited by Reecey,
Are you sure you don’t mean the other way round, ofw/sysnand on 6.0 & emunand on 6.2? If it was the way you mention that’s impossible because you wouldn’t be able to boot sx on ofw 6.2 at first to access the emunand on 6.0 just checking. If your saying emunand works on firmware 6.2 that’s good news I was thinking about doing that myself did you just click on update in emunand like you would on ofw.

Nope, dead serious. SXOS doesn't even touch sysnand at all while booting into SD emunand. My SD emunand is currently on 6.0, and my sysnand is on 6.2, and my emunand still boots just fine.
 
Nope, dead serious. SXOS doesn't even touch sysnand at all while booting into SD emunand. My SD emunand is currently on 6.0, and my sysnand is on 6.2, and my emunand still boots just fine.
That’s quite cool I didn’t know it did that so if you have an older firmware emunand saved on your sd card the sx dongle will still boot the emunand up as a priority boot but it won’t let you boot the sx menu part up because your sysnand is on 6.2. So it’s worth backing up a copy of an old emunand just in case.
 
Last edited by Reecey,
I have burned fuses and can use sleep mode fine

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


Gee give the team time to check out the update. I am sure they will release an update soon


What do you mean you burned efuses and sleep mode still works fine? I'm on 6.2 if I restore a 6.1 backup and then update emunand to 6.2 sleep mode will still work?? Or if I restore a 6.1 backup and keep emunand on 6.1 sleep mode will still work?
 
That’s quite cool I didn’t know it did that so if you have an older firmware emunand saved on your sd card the sx dongle will still boot the emunand up as a priority boot but it won’t let you boot the sx menu part up because your sysnand is on 6.2. So it’s worth backing up a copy of an old emunand just in case.

I'm on 6.2 OFW and I can still use the SX OS menu. The only problem is loading into CFW doesn't work at all.
 
  • Like
Reactions: Reecey
I'm on 6.2 OFW and I can still use the SX OS menu. The only problem is loading into CFW doesn't work at all.

Ok thanks I didn't know that I have not touched firmware 6.2 in anything as yet and the user did not explain that part to me, it makes sense now with emunand.
 
Last edited by Reecey,

Site & Scene News

Popular threads in this forum