Hacking Do any Hekate payloads work for 3.0.0?

[CTCaer]

Thanks for info. I'll try to compile it.
PS: you release already
https://github.com/CTCaer/hekate/releases

Yes, but I haven't updated the thread in GBATemp.
I'm building a guide also, so it will take some time.

 

[Deleted member 389726]

Is the reason nobody will make the patch for 3.0.x because of one person stating they will make something better, or is it because its easier to just wait for official atmosphere to be out? Because by then its basically pointless because we will have it then. Wasnt the whole point of this thread to be able to have a version for 3.0.x Firmwares in the first place? I also heard that its not too crazy difficult to make, just that it requires a few hours from multiple sources.

 

[Stoned]

I Have Jan4V Contacted via Discord.

He Work on a 3.0.x Version

 

[Deleted member 389726]

Official Hekate works for 3.0.x it just boots ofw or cfw to kernel panic atm sadly. But the commits were added for 3.0.x crypto. Itd be nice if someone could figure out how to make it boot proper. (Even compiled ipl.bin with it so people can see it does function.)

 

[reminon]

Consider yourselves lucky that you can't run Hekate. It's not meant for regular users to load and mess around with. Its got a lot of issues such as not working in sleep mode. IMO, you're not missing out on much. And last but not least, summer is almost here

Well IMO I dont feel like the few that stayed on 3.0.0 and lower are all complete noobs. I feel like making firmware patching available to 3.0.1 and higher, opens the floodgates to the vast majority of people, who will run any code blindly without caring where it came from. On the other hand that's a neccessary evil I guess. I do feel like firmware patching on 3.0.0 would be highly beneficial to those willing to dance the rcm dance.

 

[Draxzelex]

Well IMO I dont feel like the few that stayed on 3.0.0 and lower are all complete noobs. I feel like making firmware patching available to 3.0.1 and higher, opens the floodgates to the vast majority of people, who will run any code blindly without caring where it came from. On the other hand that's a neccessary evil I guess. I do feel like firmware patching on 3.0.0 would be highly beneficial to those willing to dance the rcm dance.

Oh no, I wasn't implying that either. But to me, it just seems like an arbitrary exclusion. Support for 4.x and 5.x were added in a snap, but the implementation for 3.x involved playing the waiting game, either for Atmosphere to come out or for someone to formally add the support. I feel bad for those who are on 3.x, except 3.0, because they don't have access to as much as the rest of us. Its just like finding out your PS3 is on 3.56 the day after the 3.55 exploit came out. You were so close, yet so far.

 

[reminon]

Oh no, I wasn't implying that either. But to me, it just seems like an arbitrary exclusion. Support for 4.x and 5.x were added in a snap, but the implementation for 3.x involved playing the waiting game, either for Atmosphere to come out or for someone to formally add the support. I feel bad for those who are on 3.x, except 3.0, because they don't have access to as much as the rest of us. Its just like finding out your PS3 is on 3.56 the day after the 3.55 exploit came out. You were so close, yet so far.

Yeah, but the ps3 had the luxury of hardware flashers.

 

[Draxzelex]

Yeah, but the ps3 had the luxury of hardware flashers.

Touche

 

[Azel]

anything new on the 3.0.1 and 3.0.2 front ? ^^

 

[CTCaer]

Well, I managed to do some researching, even though I had crashes in IDA, but the results were strange.
The problem is that it seems that 3.0.1 and 3.0.2 use the same offsets.
That means that the Secure monitor patches for 3.0.0 should work on 3.0.1/.2 but they don't.

Well I'm back from the weekend, so I can try things now.

 

[Deleted member 389726]

Well, I managed to do some researching, even though I had crashes in IDA, but the results were strange.
The problem is that it seems that 3.0.1 and 3.0.2 use the same offsets.
That means that the Secure monitor patches for 3.0.0 should work on 3.0.1/.2 but they don't.

Well I'm back from the weekend, so I can try things now.

Thank you in advance for your hard work if you do figure it out ^-^

 

[CTCaer]

Support for ALL current firmware is now available:
https://gbatemp.net/threads/rcm-payload-hekate-ctcaer-mod.502604/

 

[Azel]

thank you so much !!