[Guide] How to port kernel modules - Sprint HTC EVO 4G LTE

Hey all, I thought I would put together a quick guide on how to port modules built for other devices. Since we share the same CPU as the One X and many other phones it's possible some of the mods for them are compatible with our phones too. In this case I was wanting to give coolbho3000's overclock module a try to see if it would work.
Please keep in mind that this will not always work and it's still better to try and use a module built specifically for your setup. Using a module that's not made for your device can cause all kinds of issues and seriously affect system stability. Always make sure you read the original instructions to make sure you understand how it works and how it's intended to be used.
Neither me, XDA or the module's author are responsible for anything that happens to your device. You and you alone are responsible for your actions.
First thing you'll want to do is try to load it as is, it probably won't work but it'll at least give you a place to start. In this case I'm using the overclock module from the One X so I used:
Code:
adb push krait_oc.ko /data/local/krait_oc.ko
adb shell
su
insmod /data/local/krait_oc.ko
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it is successful it won't say anything, but there you can see it failed as expected. In order to find out why it failed we'll need to run dmesg and look for where it tried to load it.
Code:
dmesg | grep "krait_oc"
There we can see module_layout is where the issue is. What we can do now is pull one of the already installed modules off of the device and use it as a reference, in this case I used lcd.ko since it has an easy name to type. Grab your two modules and using linux run modprobe to find a value for module_layout. (If you only have Windows available skip to next step)
Code:
modprobe --dump-modversions lcd.ko
Now that we know what to look for open up the module in a hex edit and search for "module_layout." Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Change those four bytes to match and then save the module under a new name so it is not confused with the original.
Once you save the edited module its time to push it to the device again and try once more.
And success! Sometimes you'll also need to edit the module to accept the current kernel version you are using, but the process should be similar as to what's here.

---

So, uhhhh . . . you gonna share that modded kernel?

---

utnick said:
So, uhhhh . . . you gonna share that modded kernel?
Click to expand...
Click to collapse
Kernel is still the same, this is just for the modules

---

*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?

---

Got overclock working fine. Great thanks Haus

---

Can anyone make a zip? Pretty please.

---

You can't make a zip. you have to mod the ko file yourself and launch it yourself.

---

utnick said:
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Click to expand...
Click to collapse
Think of modules as sort of like an add-on for kernels, except that they're saved as part of the ROM instead of on boot. I used the one-x overclock module here, but since it's not made for the evo it may not be completely stable. Plus there are other changes that need to be made to the thermal profiles according to his original post.
Ideally coolbho3000 will be willing to create one for us and officially support it. I've already reached out to him about it so hopefully we'll hear something back soon.

---

Hey I know quadrants don't mean much but do you think you could get us a screenshot of our phones scores when overclocked?
Thanks for the guide by the way I will definitely try this when I have time...
Red.

---

So glad you're here haus :thumbup:
Sent from my EVO using xda premium

---

it there a way to remove a module, and replace a new edited ported *.ko?
all of this is done in recovery?
if trying to replace a module should just get to modding the kernel itself?

---

Great guide, I've been looking for something like this. So could I use this method to get USB hosting working? I know the one x (AT&T), has a custom kernel that supports it.

---

XDA University is Coming! Can't wait to learn more...

---

Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Click to expand...
Click to collapse
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.

---

exSD said:
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
Click to expand...
Click to collapse
Thank you, but "byte size orders?"

---

xHausx said:
Thank you, but "byte size orders?"
Click to expand...
Click to collapse
Byte value order. Hex value.

---

thanks a lot
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?

---

hackerse7en said:
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
Click to expand...
Click to collapse
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.

---

xHausx said:
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
Click to expand...
Click to collapse
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me

---

hackerse7en said:
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
Click to expand...
Click to collapse
i just cant undestand, if someone can help me.