Separate names with a comma.
Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by cucholix, Apr 16, 2019.
The wording is a bit off. 8.0.0 burned 9 efuses.
Actually no, 8.0 burned only one efuse.
Fuse count was increased to 10. The master key, pk21 key, tsec root key, etc were unchanged
Changelog doesn't matter anyways. It's the same crap changelog as always
I’m not sure if anyone is aware yet but you can still use all your online features on 7.0.1 even on the 8.0 pending update no need to worry about updating for online use everything works.
I just played Splatoon 2 and realized this. Awesome.
I just found out as well using eshop, it still says pending in settings so it all works.
It probably wont last long though :/. If it’s the same as 6.2.0 —-> 7.0.0 was, then it’ll stop working in aboit 12 hours
I’ve never had this happen before when the pending update pops in when you connect to the internet soon as you try eshop it always says you need to update this is even when the update has gone live this is the first time I have ever noticed this happen.
You always get a grace period. Eventually the online access on lower firmware gets cutoff.
Does emunand work on the new firmware 8.0 I red they never changed the master key so does it work?
But ipatched consoles can't be modded
Your emunand must be 7.0.1 or lower at the moment. But if your OFW is 8.0.0 you can still boot your emunand.
Ok thanks for the reply.
They will be able to be modded publicly very Soon though
You dont have to disable autorcm to enter maintenance mode
So if it's a case. I think any game/update which will require 8.0 can be bypassed with Tinfoil installation on 7.0.1 cfw, because it will use the same master key. Am I right?
They use the same key, so yes. It will not require you to be on 8.0, just use the ignore firmware when you install them.
There’s a new sdk version for 8.x. any games that use that won’t work on 7.x
I saw that there are "fixes" out in the wild that you have to add to atmosphere to get a paticular title working. And it was SDK related.