Hacking RELEASE Kosmos patches (ES & FS)

[345742D]

Why do you even exist? There are billions of other Humans on this Planet!
Why not being Thankful, instead complaining about nothing!

I actually think he's confused, as am I. Do I just add this to my current Kosmos installation to make tinfoil and whatnot compatible or is this some sort of stand alone CFW?

 

[azn87]

I don't think you got my point. Kosmos includes patches. What is the point of this release, or is it that Kosmos wont include patches anymore?

Then i'm Sorry! These Patches exist cause Kosmos and This Thread don't include ACID & nocmac Patches. Also this Way he can discontinue his hekate mod J Fork. You can read it in the First Post!

Can it just be merged and "overwrite" whatever I have installed with kosmos 13.0.1?

Yeah you can merge them together.

 

[gamemasteru03]

I don't think you got my point. Kosmos includes patches. What is the point of this release, or is it that Kosmos wont include patches anymore?

Kosmos devs just removed patches so the next release after 13.01 wont have sig patches but the devs have said this is the official way to get patches for kosmos now. Plus this has more patches that make it so tinfoil dz works.

 

[huma_dawii]

Then i'm Sorry! These Patches exist cause Kosmos and This Thread don't include ACID & nocmac Patches. Also this Way he can discontinue his hekate mod J Fork. You can read it in the First Post!



Yeah you can merge them together.

Thanks, now I actually understand what's going on! lol

 

[noahc3]

This is great news, the scene just became less fragmented. This is great news for goldleaf and tinfoil users as it will reduce the number of "this software cannot be started" errors that newbs got.

Can we expect Tinfoil to remove the signature check? It's entirely unnecessary for J to be bundling an update.bin in his release.

 

[blawar]

Can we expect Tinfoil to remove the signature check? It's entirely unnecessary for J to be bundling an update.bin in his release.

After the adoption rate becomes high enough, yes.

 

[jakkal]

Can it just be merged and "overwrite" whatever I have installed with kosmos 13.0.1?

just overwrite

 

[Slim45]

just movee all the folders to root? should we be using the kehate 5.01 then?

 

[OrGoN3]

Curious. Your GitHub says you updated to Hekate 5.0.1, but there is no 5.0.1, only 5.0.0?

 

[noahc3]

Curious. Your GitHub says you updated to Hekate 5.0.1, but there is no 5.0.1, only 5.0.0?

There is a pre-release build on RetroNX which fixes booting on plenty of firmwares and a bunch of emummc fixes. The build J is packing is the r3 version of that build.

 

[OrGoN3]

There is a pre-release build on RetroNX which fixes booting on plenty of firmwares and a bunch of emummc fixes. The build J is packing is the r3 version of that build.

I thought those were all Atmosphere fixes?

Edit: Okay, I get the point. Although the ones you mentioned seemed to be the Atmosphere fixes (couldn't boot emummc on 4.1.0, and a bunch of emummc fixes), I guess Hekate was also updated. So the updates aren't in the dev branch, and aren't committed to the master branch. So how do we follow these updates? Is there another GitHub for them?

 

[noahc3]

I thought those were all Atmosphere fixes?

Edit: Okay, I get the point. Although the ones you mentioned seemed to be the Atmosphere fixes (couldn't boot emummc on 4.1.0, and a bunch of emummc fixes), I guess Hekate was also updated. So the updates aren't in the dev branch, and aren't committed to the master branch. So how do we follow these updates? Is there another GitHub for them?

Hekate itself had plenty of issues alongside Atmosphere (both each had their own issues booting certain firmwares).

They are currently being posted on the RetroNX discord. That's the only place to follow updates until a proper release is posted on GitHub.

 

[Slim45]

There is a pre-release build on RetroNX which fixes booting on plenty of firmwares and a bunch of emummc fixes. The build J is packing is the r3 version of that build.

r3 version ???

--------------------- MERGED ---------------------------

so from now on hould i get my hekate from here or are the patches enough. eg ctcaer releases hekate 5.1 should i use that and copy patches over or should i wait for a hekate 5.1j???

 

[nabelo]

Curious. Your GitHub says you updated to Hekate 5.0.1, but there is no 5.0.1, only 5.0.0?

Hmm...Am i blind? I cant see any changes on J00nies github regarding the prerelease hekate version.
Anyone can point me in the right direction?

 

[OrGoN3]

Hmm...Am i blind? I cant see any changes on J00nies github regarding the prerelease hekate version.
Anyone can point me in the right direction?

It was edited again and removed. It was just saying it's compatible with hekate 5.0.1 if you're using the retronx build.

 

[wurstpistole]

So, I am understanding that you're no longer going to maintain the J mod of hekate, right? So for any future hekate updates we will have to revert to the official branch, which dz/lithium will refuse to work with because we don't have the properly signed update.bin.sig, right?

Wrong. Modded Hekate is still a thing, it's just not maintained individually anymore. It's in the pack.

 

[Slim45]

new hekate out as of writing this, do these work on it?

 

[wurstpistole]

new hekate out as of writing this, do these work on it?

Just wait three seconds and allow him to update

 

[regnad]

Just wait three seconds and allow him to update

I think his question was if an update is even necessary considering the Hekate update is pretty minor. Maybe the latest patches work fine with it?

 

[Localhorst86]

I think his question was if an update is even necessary considering the Hekate update is pretty minor. Maybe the latest patches work fine with it?

The patches should work. DZ will not.

Gesendet von meinem Mi A1 mit Tapatalk