Thanks. ^^ I guess I've updated my stuff a bit too soon.
Hehehehe
Same problemThanks. ^^ I guess I've updated my stuff a bit too soon.
Post automatically merged:
Now I get a solid blue screen after trying to load Atmosphere's package3 via Hekate's FSS0.
My emuNAND CFW still works just fine if I boot into Atmosphere via latest fusee.bin.
same problem hereThanks. ^^ I guess I've updated my stuff a bit too soon.
Post automatically merged:
Now I get a solid blue screen after trying to load Atmosphere's package3 via Hekate's FSS0.
My emuNAND CFW still works just fine if I boot into Atmosphere via latest fusee.bin.
New atmosphere is out, is it possible for you or someone to compile again the new Fusee payload with IPS sigpatches support?
Haven't tested but it's likely that each new atmos requires new Fusee or refuses to boot, but no idea... I can try later...
If I remember correctly, you need to update both your Atmosphere build and payload for both to work properly, otherwise it won't boot into CFW (probably just a black screen).I would guess it should work, but please let us know
Doesn't work sadly, says incorrect fusee version or somethingI would guess it should work, but please let us know
NICE, thank you!!!
Mine is fully working with the old Fusee sigpatches and if you are using FSS0 to boot you need hekate sigpatches or sys-patch for any case that you don't want to even use sigpatches...
Probably.I noticed Rekado already has the new fusee and hekate.
I usually update my payloads manually. I was mainly referring to those fake RCM loaders that come with hekate's payload pre-installed.
] No I'm nott 
[stink 
]