They're presumably trying to figure out how to remove the Atmosphere splashscreen from sept.
Good luck with that
They're presumably trying to figure out how to remove the Atmosphere splashscreen from sept.
They did, with update 6.2 and 7.0 just fixed a security bug they used before.No they haven't...
Sent from my COR-L29 using Tapatalk
Because while the source code is freely available, it is a encrypted payload as the TSEC expects an encrypted payload. It requires the 7.x keys which are only available through a private exploit. That is the whole purpose of sept - to enable 7.x compatiblity without the exploit becoming public.Why do you say that? It's open source![]()
Why wait? You can run 7.0 right now and enjoy all the things (if not banned), and still use a 6.2 emunand with sx. I don't really have a need for CFW at the moment at all, but I tested it on my system today, just because. Everything works fine.Waiting for it patiently, just enjoy everything on Switch 6.2, just hope it can be asap.
Because while the source code is freely available, it is a encrypted payload as the TSEC expects an encrypted payload. It requires the 7.x keys which are only available through a private exploit. That is the whole purpose of sept - to enable 7.x compatiblity without the exploit becoming public.
You can get the sept-secondary.enc from the 0.8.4 release and then set the path when building like this.Why wait? You can run 7.0 right now and enjoy all the things (if not banned), and still use a 6.2 emunand with sx. I don't really have a need for CFW at the moment at all, but I tested it on my system today, just because. Everything works fine.
Ahh!!! That explains why I can't figure out how to complete the build myself. I was going crazy trying to figure out which keys to use to compile it.
That's very likely.They're presumably trying to figure out how to remove the Atmosphere splashscreen from sept.
Holy, smokes! Thanks! Worked like a charmYou can get the sept-secondary.enc from the 0.8.4 release and then set the path when building like this.
make SEPT_ENC_PATH=C:/set/the/pathto/sept-secondary.enc
Nice, glad it worked! I needed help compiling myself haha.Holy, smokes! Thanks! Worked like a charm![]()
Is it actually true that they have trouble removing splash screen o.O
Thought so haha, but its weird enough to be true xDIt's a joke related to past findings. No one can really tell if they really are.
Thought so haha, but its weird enough to be true xD
No, they can not. That's the whole issue everyone is talking about. The payload containing the logo is encrypted and signed, unless they figure out the keys to decrypt it themselves, they won't be able to change the logo.Also they could simply change the logo to SX OS![]()