i didnt know about the no sleep modeif you burned fuses, you can but you won't be able to go to sleep mode or booting up on OFW
i didnt know about the no sleep modeif you burned fuses, you can but you won't be able to go to sleep mode or booting up on OFW
Do I have to remove autorcm before I update? Haven't used my switch in a while . Surprisingly I'm still unbanned.
Unless people are unable to enter RCM that still holdsWeren't we told way back that the hardware exploit could "never ever" be patched out? Yet here we are?
Hardware exploit still works. CFW just needs to be patched to work on this firmware.Weren't we told way back that the hardware exploit could "never ever" be patched out? Yet here we are?
Weren't we told way back that the hardware exploit could "never ever" be patched out? Yet here we are?
Everything leading up a CFW doesn't have to be a single exploit. The hardware flaw will *always* be there, but there's more to it than that. You could nuke your NAND, and you'd still be able to run code through RCM.Weren't we told way back that the hardware exploit could "never ever" be patched out? Yet here we are?
Thought it would. Just make sure you make an emunand on your current firmwareEmunand 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.
smash wont be 6.2Damn. I'll guess I'll burn that fuse for smash
More like: all cfw users DO NOT UPDATEsx os users
DO NOT UPDATE
yes, they are waiting for SciresM to release an update for Atmosphere so they can steal the fixsx os users
DO NOT UPDATE
TX is working on a fix
maybe you can take scires out to dinner sometimeyes, they are waiting for SciresM to release an update for Atmosphere so they can steal the fix