Using any sort of CFW/homebrew puts you at risk of a ban. There is no "safe" CFW.Does this support playing 6.2 legit retail games but still being able to play backups without a ban?
Using any sort of CFW/homebrew puts you at risk of a ban. There is no "safe" CFW.Does this support playing 6.2 legit retail games but still being able to play backups without a ban?
Wait for atmosphere's emunand support then ask again.Does this support playing 6.2 legit retail games but still being able to play backups without a ban?
I feel as if you are hinting at something, unless I went back in time? Or something just went way over my head that is completely obvious.Happy June 15th!
considering you can upgrade your FW without burning fuses, dont expect anything any time soon. That's what I did but also using autorcm, never bought or needed a jig.Are there any news about 1.0.0 coldboot hack?
Not currently afaik, but it's open source, so go for it.Atmosphere seems to be working pretty well so far. I was wondering if theres a way to replace the Fusee boot sequence with a spalsh screen?
Not currently afaik, but it's open source, so go for it.
I'm not sure but the text might be due to debug mode.Atmosphere seems to be working pretty well so far. I was wondering if theres a way to replace the Fusee boot sequence with a spalsh screen?
you can choose to autoboot to a cfw and choose atmosphere, so that when you boot it up the splash screen appears and boots directly to the cfw without you selecting itSadly I'm not into coding nor do I know how to code. But on the brighter side I found out that Hekate supports custom boot splashes. Now the only thing missing is a touch UI for Hekate.
Atmosphere seems to be working pretty well so far. I was wondering if theres a way to replace the Fusee boot sequence with a spalsh screen?
[stage2]
custom_splash = [PATH TO YOUR SPLASH SCREEN FILE]
Does this replace the default atmosphere splash at the same point it displays anyway, or does it actually replace the status text? I think that's what they were asking about.It is possible yes, but the method is missing from documentation.
To use a custom splash screen you must add the following to the BCT.ini file:
Code:[stage2] custom_splash = [PATH TO YOUR SPLASH SCREEN FILE]
The splash screen file must be in BMP format just like hekate.
and https://github.com/Atmosphere-NX/Atmosphere/commits/masterAnyway, browserhax + nvhax for < 6.2.0 will be released later this week (along with the writeup) so people with ipatched units can play around a bit in userland. It's not much, but hopefully will lead to more people researching other attack vectors in the latest firmwares.
— Mike Heskin (@hexkyz) December 17, 2018
Can't you just downgrade your console? If you haven't burned your fusees there should be no problemWarmboot coming later this week/early next week
Sources: https://twitter.com/hexkyz/status/1074712590347993090 and https://github.com/Atmosphere-NX/Atmosphere/commits/master
Potentially you won't need the rcm jig once released
@rajkosto any idea how will that work for users who have higher firms with less burned fuses? I suppose warmboot is not for us