Sure i can!
But, if I can easy handle the Linux side of the job on my PC, I need a step from your phone just before my build action...
...this is true, anyway, only once for a given Kernel Source!
First of All, looking inside Samsung Open Source Release Center
I see three Kernel Sources:
I need to choose the right one for the Region of your Phone (or current firmware):
- MEA (Middle East and Africa);
- SEA (South East Asia);
- SWA (South West Asia).
After that, when I prepare the Kernel tree for build (as I briefly described in the first post) with the following command:
doc@saucy:~/tmp/S5282$ make mint-vlx-rev03_defconfig
I have to check (once
for all) the resulting configuration file with the one extracted from your running kernel!
You must issue one console command
from PC with "adb shell" (difficult to setup) or from a Terminal emulator from the Phone (easy to go) installing, for example, the free App "Terminal Emulator" from Palevich (thanks forever
The phone, of course, must be rooted and busyboxed;
Here what to type:
shell@android:/ $ su
root@android:/ # zcat /proc/config.gz > /data/local/config.txt
This command simply creates a text file in the /data/local
folder with listed all the configuration options!
I need it to check for differences, just to modify the build tree accordingly.
Ah... of course I need a boot.img
file to mod and, maybe, the right PDA code for it... just to prepare an Odin archive with the right naming convention...
After All I'll build the Kernel and prepare two images in my google drive:
- the original boot.img ready for Odin,
- the cpufreq modded boot.img ready for Odin.
You have to test it!
If it doesn't boot, simply flash back the original image in place.
No need to wipe anything before, during and after...