@moh.96
Right, probably best to leave the native EC alone and create a fake one, I should start doing that from now on, I don't know why I was so stubborn about that.
What I mean is the following... When you write the ACPI source language for a new method, thus a method definition, it will look something like this:
Method (name, argCount, Serialized/NotSerialized)
You *define* a method there, you don't invoke it. An invocation would be name (). If this code gets assembled to bytes, there is an operation-code for "make method", which is 0x14 in HEX. Open up an .aml in HexFiend, f.e.
It should be built up like this: 14 + method size + method name, in short: 14<size>5F42424E, would be method _BBN. <size> can be either one byte or multiple, I don't yet know how to automatically determine how many will follow.
But be careful, if a 14 is inside the size, you need to ignore it and get the 14 before that. That's what can throw you off. But by coping from the preamble 14, you will *always* only replace the definition, no invocations. That's how I did it until now, it may need further research.
I hope that made any sense, I kind of have a hard time concentrating right now...