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...
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.
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.
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
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?
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,
CFW only remove the bootloader fuse checks, not the warmboot ones and no you cant patch them out of warmboot afaik
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,
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?
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,
- Joined
- Jun 24, 2007
- Messages
- 12,007
- Trophies
- 3
- Location
- In the Murderbox!
- Website
- www.twitch.tv
- XP
- 16,143
- Country
Similar threads
-
- Portal
- No one is chatting at the moment.
-
-
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
