Database Info

[Q] Compiling Kernel

Hi All,
I take notes with my Tab2, and sometimes the Default behaviour of the Touchscreen annoys me.
So i decided to recompile the kernel with 3 lines of code added. When done i replaced the zImage in the boot.img of the kkboot stock zip and flashed it trough clockworkmod.
Then i got stuck, my tablet gets stuck inside a boot loop (only the logo comes up, and then reboots after 3 seconds).
The kernel compilation was done by:
- Download Ubuntu, follow the guide on Andriod to setup a build enviorment
- Download Doomlord's toolchain
- Download source from Samsung Open Source
- Adjust code
- Compile using samsungs instructions
How can i resolve this?

http://forum.xda-developers.com/showthread.php?t=1859227 Use Sourcery G++ Lite 2010q1-202 as per Samsung instruction.

ketut.kumajaya said:
http://forum.xda-developers.com/showthread.php?t=1859227 Use Sourcery G++ Lite 2010q1-202 as per Samsung instruction.
Click to expand...
Click to collapse
So, retry compiling with Codesourcery. What parameters do i need to pass to mkbootimg?

Plis man do oc kernel to 1,4 ghz for g tab 7

gieltjev said:
So, retry compiling with Codesourcery. What parameters do i need to pass to mkbootimg?
Click to expand...
Click to collapse
I have my own script base on http://forum.xda-developers.com/showthread.php?t=1241005

ketut.kumajaya said:
I have my own script base on http://forum.xda-developers.com/showthread.php?t=1241005
Click to expand...
Click to collapse
So i downloaded "arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2" and your toolkit.
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
This time the booting takes around 6 seconds, but still resetting.
dawidex444 said:
Plis man do oc kernel to 1,4 ghz for g tab 7
Click to expand...
Click to collapse
If the result is positive i will share my adjustments here so that the real cooks can bake a decent kernel

gieltjev said:
So i downloaded "arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2" and your toolkit.
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
This time the booting takes around 6 seconds, but still resetting.
If the result is positive i will share my adjustments here so that the real cooks can bake a decent kernel
Click to expand...
Click to collapse
So what "adb shell dmesg" output?
EDIT: Incompatible PVR kernel module, disable MODVERSION and add "-blackhawk" string to LOCALVERSION in your kernel config file or you can extract my config file from "/proc/config.gz" by "insmod /system/lib/modules/configs.ko".

ketut.kumajaya said:
So what "adb shell dmesg" output?
EDIT: Incompatible PVR kernel module, disable MODVERSION and add "-blackhawk" string to LOCALVERSION in your kernel config file or you can extract my config file from "/proc/config.gz" by "insmod /system/lib/modules/configs.ko".
Click to expand...
Click to collapse
Wow, how did you find that out?
So i set, CONF_MODVERSION=n, LOCALVERSION='-blackhawk'
Let's recompile
EDIT: Recompiled, added into the CORE kkboot image. Still resetting. while the logo shows i cannot execute "adb shell dmesg". If executed from CWM it adb shell dmesg works.

Code:
$ cp android_espresso10_omap4430_r02_user_blackhawk_defconfig.txt kernel/arch/arm/configs/android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ cd kernel
$ make mrproper
$ make ARCH=arm android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ make -j4 ARCH=arm

ketut.kumajaya said:
Code:
$ cp android_espresso10_omap4430_r02_user_blackhawk_defconfig.txt kernel/arch/arm/configs/android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ cd kernel
$ make mrproper
$ make ARCH=arm android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ make -j4 ARCH=arm
Click to expand...
Click to collapse
Ok, that works! i've got my own kernel running on the device. Now i will continue getting the fix to work.

gieltjev said:
Ok, that works! i've got my own kernel running on the device. Now i will continue getting the fix to work.
Click to expand...
Click to collapse
Congratulations :good:

gieltjev said:
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
Click to expand...
Click to collapse
What you've done is exactly what I'm trying to do now.
But I'm stuck in unpacking boot.img in kk-boot.
Which unpack/repack tool did you use? Can you plz share them?

CM13 compiling error?

I'm trying to compile CM13 for the OPO, and I keep coming with an error, I've tried to compile 3 times, and each time getting the same error. I wiped ccache and tried make clean and still have had the same results, any ideas?
http://pastebin.com/CvJT8RKZ

These could be the culprit :
Code:
expr: syntax error
stat: illegal option -- c
usage: stat [-FlLnqrsx] [-f format] [-t timefmt] [file ...]
[...]
/Volumes/CM/android/system/kernel/oneplus/msm8974/scripts/xz_wrap.sh: line 23: exec: xz: not found
The second error could be fixed by properly setting up xz binary (either by installing it or exporting it to the current terminal window). Can you also mention what operating system you're using to compile the ROM ?

F4uzan said:
These could be the culprit :
Code:
expr: syntax error
stat: illegal option -- c
usage: stat [-FlLnqrsx] [-f format] [-t timefmt] [file ...]
[...]
/Volumes/CM/android/system/kernel/oneplus/msm8974/scripts/xz_wrap.sh: line 23: exec: xz: not found
The second error could be fixed by properly setting up xz binary (either by installing it or exporting it to the current terminal window). Can you also mention what operating system you're using to compile the ROM ?
Click to expand...
Click to collapse
I'm using OS X 10.11.4, and this is my first-ish time creating a ROM (well from source anyway) so I have no idea what that means, any chance you could walk me through it (I'm reasonably competent, just need some general direction).

Vekhez said:
I'm using OS X 10.11.4, and this is my first-ish time creating a ROM (well from source anyway) so I have no idea what that means, any chance you could walk me through it (I'm reasonably competent, just need some general direction).
Click to expand...
Click to collapse
Are you trying to build on OS X, or are you running a Linux VM? Either way, I think you might be missing some packages like the above poster mentioned. Here's a guide I found for setting up your OS X environment: http://forum.xda-developers.com/showthread.php?t=2510898, make sure you grab the required packages for compiling android. Good luck!

ryanmat said:
Are you trying to build on OS X, or are you running a Linux VM? Either way, I think you might be missing some packages like the above poster mentioned. Here's a guide I found for setting up your OS X environment: http://forum.xda-developers.com/showthread.php?t=2510898, make sure you grab the required packages for compiling android. Good luck!
Click to expand...
Click to collapse
Following all those instructions everything has already been done, all the brew things have been installed, everything is up to date etc. So I'm assuming the error will be the same?

Vekhez said:
Following all those instructions everything has already been done, all the brew things have been installed, everything is up to date etc. So I'm assuming the error will be the same?
Click to expand...
Click to collapse
You can always sync the repo again and retry the build. If it doesn't work you can always ask in the thread I linked. The other place to check out is here: https://source.android.com/source/initializing.html
Here's a link to the xz package for Mac you seem to be missing: http://macpkg.sourceforge.net/

[HELP] Can't flash compiled AOSP

Hey guys, thank you in advance. I have an LG X Power (K220) and I started to develop the stock AOSP from source (Android 6.0.1). I followed all the instruction from LG and Google (downloaded both google and LG source and then merged them). After seven hours of compiling I got my image file: system.img, cache.img, userdata.img and ramdisk.img. It was the time to flash and test the new build, so I used these command:
Code:
fastboot flash cache cache.img
Code:
fastboot flash ramdisk ramdisk.img
But when I have to flash the system.img and the userdata the device tell me that the images are too big and the message “Invalid sparse file format at header magi”. So I googled it and I tried with:
Code:
fastboot -S 256M flash system.img
But nothing. I also read that I could try to modify the BoardConfig.mk and add:
Code:
TARGET_USERIMAGES_SPARSE_EXT_DISABLED := true
But I do not know what BoardConfig.mk I have to modify becouse when I merge the file and go to /device/lge/k7 there isn't the mk file, so I think that use the generic aosp for arm devices.
How could I solve this problem? Thank you another time :fingers-crossed:

Hi I'm also building AOSP for X Power. You need to change SYSTEM IMAGE partition size in aosp/device/generic/armv7-a-neon/BoardConfig.mk. That's beacouse we use "lunch 1" which mean "lunch aosp_arm-eng". If u need help send me message.

kko7 said:
Hi I'm also building AOSP for X Power. You need to change SYSTEM IMAGE partition size in aosp/device/generic/armv7-a-neon/BoardConfig.mk. That's beacouse we use "lunch 1" which mean "lunch aosp_arm-eng". If u need help send me message.
Click to expand...
Click to collapse
Are you able to build debug versions? That may help things for you.

Maybe I will be able but I'm getting clang error, so I need to fix it first.
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [build/core/host_shared_library_internal.mk:51: out/host/linux-x86/obj/lib/libartd.so] Error 1

kko7 said:
Maybe I will be able but I'm getting clang error, so I need to fix it first.
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [build/core/host_shared_library_internal.mk:51: out/host/linux-x86/obj/lib/libartd.so] Error 1
Click to expand...
Click to collapse
I fixed it. Now I am waiting for the compilation to finish.
If someone want I can upload it to AFH

kko7 said:
I fixed it. Now I am waiting for the compilation to finish.
If someone want I can upload it to AFH
Click to expand...
Click to collapse
How did you fix the error?

Modify build/core/clang/HOST_x86_common.mk
android-review.googlesource.com/c/platform/build/+/223100/1/core/clang/HOST_x86_common.mk
If that doesn't work then
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/bin/ld
But you need to be in aosp folder

kko7 said:
Modify build/core/clang/HOST_x86_common.mk
android-review.googlesource.com/c/platform/build/+/223100/1/core/clang/HOST_x86_common.mk
If that doesn't work then
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/bin/ld
But you need to be in aosp folder
Click to expand...
Click to collapse
Excellent, thank you! ?

Sands207 said:
Excellent, thank you! ?
Click to expand...
Click to collapse
No problem

kko7 said:
Maybe I will be able but I'm getting clang error, so I need to fix it first.
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [build/core/host_shared_library_internal.mk:51: out/host/linux-x86/obj/lib/libartd.so] Error 1
Click to expand...
Click to collapse
How do you fix it?
I trying make a build for my Xperia X and Xperia M2 Aqua, but, justly, launch that error...

sebasrock156 said:
How do you fix it?
I try to make a build for my Xperia X and Xperia M2 Aqua, but, justly, launch that error...
Click to expand...
Click to collapse
Modify core/clang/HOST_x86_common.mk
https://android-review.googlesource.com/c/platform/build/+/223100/1/core/clang/HOST_x86_common.mk
If this doesn't work then try this command:
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/bin/ld
But you need to be in the aosp folder

Kernel compilation/booting troubleshooting for beginners

I've only recently after lot of struggle compiled my first kernel. While the information is still fresh in my mind, I want to share all the problems I encountered and what to do if you are in the same situation.
This guide is mainly for Linux users since that is what I am familiar with.
I've used this amazing guide to learn the basics. If you haven't yet, read it first.
Errors from scripts/gcc-wrapper.py
Open the file and change the first line from
Code:
#! /usr/bin/env python
to
Code:
#! /usr/bin/env python2
Kernel won't compile
* Did you forget to set and export the variables ARCH and CROSS_COMPILE?
* Do you have the right .config file present?
Try extracting the .config file from the original boot kernel and use it instead
* Are you sure you are in the correct branch?
Run git branch inside kernel's source code to verify that
* Are you using a very recent or very old version of the compiler? Some old kernels for example would only compile with gcc-4 but not gcc-7 or 8. Most kernels - at the time of writing - won't compile with gcc-8
Kernel compiles fine but won't boot
* Are you using wrong kernel configuration (.config) ?
* Try different compiler or different compiler version.
I've tried to compile my current with Android's prebuild gcc 4 compiler and it wouldn't boot, switched to gcc 7 and it booted perfectly fine.
Kernel starts but system crashes somewhere during boot
You can enable adb during boot so that you can see what causes the error.
Find this file in your extracted boot image ramdisk/default.prop
Set or update the following values
Code:
ro.adb.secure=0
ro.secure=0
persist.sys.usb.config=adb
Then you can do adb shell logcat or adb shell dmesg to see what is going on
My phone won't boot after flashing my new kernel, how do I boot to recovery?
First of all, you shouldn't have! You should test your new kernel without flashing it using fastboot.
Simply reboot to bootloader then run the command
Code:
fastboot boot /path/to/my/new-image
So what can I do now? Try to reach bootloader screen. the method differs from device to device but it involve pushing certain physical phone buttons while turning on the phone.
Once you are in the bootloader screen, you can do adb fastboot /path/to/twrp-recovery.img or even path to original boot image if you kept a backup.

ramast_ said:
I've only recently after lot of struggle compiled my first kernel. While the information is still fresh in my mind, I want to share all the problems I encountered and what to do if you are in the same situation.
This guide is mainly for Linux users since that is what I am familiar with.
I've used this amazing guide to learn the basics. If you haven't yet, read it first.
Errors from scripts/gcc-wrapper.py
Open the file and change the first line from
Code:
#! /usr/bin/env python
to
Code:
#! /usr/bin/env python2
Kernel won't compile
* Did you forget to set and export the variables ARCH and CROSS_COMPILE?
* Do you have the right .config file present?
Try extracting the .config file from the original boot kernel and use it instead
* Are you sure you are in the correct branch?
Run git branch inside kernel's source code to verify that
* Are you using a very recent or very old version of the compiler? Some old kernels for example would only compile with gcc-4 but not gcc-7 or 8. Most kernels - at the time of writing - won't compile with gcc-8
Kernel compiles fine but won't boot
* Are you using wrong kernel configuration (.config) ?
* Try different compiler or different compiler version.
I've tried to compile my current with Android's prebuild gcc 4 compiler and it wouldn't boot, switched to gcc 7 and it booted perfectly fine.
Kernel starts but system crashes somewhere during boot
You can enable adb during boot so that you can see what causes the error.
Find this file in your extracted boot image ramdisk/default.prop
Set or update the following values
Code:
ro.adb.secure=0
ro.secure=0
persist.sys.usb.config=adb
Then you can do adb shell logcat or adb shell dmesg to see what is going on
My phone won't boot after flashing my new kernel, how do I boot to recovery?
First of all, you shouldn't have! You should test your new kernel without flashing it using fastboot.
Simply reboot to bootloader then run the command
Code:
fastboot boot /path/to/my/new-image
So what can I do now? Try to reach bootloader screen. the method differs from device to device but it involve pushing certain physical phone buttons while turning on the phone.
Once you are in the bootloader screen, you can do adb fastboot /path/to/twrp-recovery.img or even path to original boot image if you kept a backup.
Click to expand...
Click to collapse
good job!
Do you have any general tutorials on kernel optimization?

wangyiling said:
good job!
Do you have any general tutorials on kernel optimization?
Click to expand...
Click to collapse
I am afraid not, sorry. I am just a beginner

@ramast_
The information you provided has solved pretty much all of the problems I was having. We need more content like this. Everything I find about kernel building explains things like you're a Linux expert, where as your post is much more layman friendly. I can't thank you enough for this.
Quick question; which version of Linux do you use?

You are very welcome, happy someone found it useful.
By Linux version I suppose you mean Linux distro (distribution).
I use Gentoo which is certainly not for beginners.
I'd suggest Ubuntu for beginners. Not because it's the best but because it has a very big community and you are more likely to find help when facing any problem.
This article explain how to cross compile arm code (how to compile code so that it can run on an arm device). Should get you started.
Best of luck
Spaceminer said:
@ramast_ I can't thank you enough for this.
Quick question; which version of Linux do you use?
Click to expand...
Click to collapse

ramast_ said:
You are very welcome, happy someone found it useful.
By Linux version I suppose you mean Linux distro (distribution).
I use Gentoo which is certainly not for beginners.
I'd suggest Ubuntu for beginners. Not because it's the best but because it has a very big community and you are more likely to find help when facing any problem.
This article explain how to cross compile arm code (how to compile code so that it can run on an arm device). Should get you started.
Best of luck
Click to expand...
Click to collapse
Thanks again. Distro is what I meant. I was thinking I should use Ubuntu, but I wanted to see what you had to say about it.

Question Bootloader Unlocked Warning

Has anybody figured out how to get rid of the Bootloader Unlocked warning when booting this phone? It certainly slows down the booting process.

I haven't figured it out yet. To be honest I've been trying to figure out what apps are safe to uninstall and a custom ROM or how to update to Android 12. But I'll definitely let you know if I figure a way out.

dfreedom834 said:
I haven't figured it out yet. To be honest I've been trying to figure out what apps are safe to uninstall and a custom ROM or how to update to Android 12. But I'll definitely let you know if I figure a way out.
Click to expand...
Click to collapse
I have been trying to build TWRP for this device. I am very close, but the mkbootimg command script is issuing a bad argument and I have been unable to trace it down so far.
Code:
[100% 4/4] Target boot image: /mnt/audio/android/twrp/out/target/product/minsk/boot.img
FAILED: /android/twrp/out/target/product/minsk/boot.img
/bin/bash -c "(/android/twrp/out/host/linux-x86/bin/mkbootimg --kernel /mnt/audio/android/twrp/out/target/product/minsk/kernel --ramdisk /android/twrp/out/target/product/minsk/ramdisk.img --base 0x00000000 --pagesize 4096 --cmdline \"console=ttyMSM0,115200n8 androidboot.hardware
=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 servic
e_locator.enable=1 swiotlb=1 androidboot.usbcontroller=a600000.dwc3 earlycon=msm_geni_serial,0x880000 loop.max_part=7 printk.devkmsg=on androidboot.ha
b.csv=10 androidboot.hab.product=minsk androidboot.hab.cid=50 firmware_class.path=/vendor/firmware_mnt/image buildvariant=user buildvariant=eng\" --os
_version 16.1.0 --os_patch_level 2099-12-31 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --dtb device/motorola/minsk/prebuilt/dtb.img --header
_version 2 --output /mnt/audio/android/twrp/out/target/product/minsk/boot.img ) && (true )"
mkbootimg: error: unrecognized arguments: --dtb device/motorola/minsk/prebuilt/dtb.img
ninja: build stopped: subcommand failed.
15:01:24 ninja failed with: exit status 1
So the --dtb should be --recovery_dtbo I believe. Not sure where this command is being generated in order to fix it.

I was running into problems like that I factor rest it and turned it off. Where did you compile the boot.img from? And ya it would work better if it was trying to go to the right path. I had to find a boot.img from one of the over seas ones I kept getting it were it would root but the screen did respond.

lexridge said:
So the --dtb should be --recovery_dtbo I believe. Not sure where this command is being generated in order to fix it.
Click to expand...
Click to collapse
I could be wrong but the recovery I'm using (orange fox) does use a kernel_dtb. So it seems your recovery image kernel doesn't have the right path to the dtb binary it needs. Try searching the build directory for any _dtb/.dtb and rename accordingly. I'd you need to alter the dtb from a related SoC there are tools for unpacking and modifying those.
The recovery and boot ones would be similar I imagine since those files are a map of the device's hardware.

dfreedom834 said:
I was running into problems like that I factor rest it and turned it off. Where did you compile the boot.img from? And ya it would work better if it was trying to go to the right path. I had to find a boot.img from one of the over seas ones I kept getting it were it would root but the screen did respond.
Click to expand...
Click to collapse
I took the boot.img from the full device A11 factory image.
MINSK_RETUS_11_RPCS31.Q2-109-16-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I used the same one to create my magisk boot.img as well. I used dumpyara to build the device tree using the above file for my source which seemed to work properly. No errors in other words.

elrod16 said:
I could be wrong but the recovery I'm using (orange fox) does use a kernel_dtb. So it seems your recovery image kernel doesn't have the right path to the dtb binary it needs. Try searching the build directory for any _dtb/.dtb and rename accordingly. I'd you need to alter the dtb from a related SoC there are tools for unpacking and modifying those.
The recovery and boot ones would be similar I imagine since those files are a map of the device's hardware.
Click to expand...
Click to collapse
I have a dtbo directory containing these files:
Code:
00_kernel
01_dtbdump_amxbr.dtb
02_dtbdump_amxbr.dtb
03_dtbdump_amxbr.dtb
04_dtbdump_amxbr.dtb
05_dtbdump_amxbr.dtb
I also have a dtb.img in the root of the device tree. I will copy it to dtbo.img and see what happens. Thanks for the hint.

lexridge said:
I have a dtbo directory containing these files:
Code:
00_kernel
01_dtbdump_amxbr.dtb
02_dtbdump_amxbr.dtb
03_dtbdump_amxbr.dtb
04_dtbdump_amxbr.dtb
05_dtbdump_amxbr.dtb
I also have a dtb.img in the root of the device tree. I will copy it to dtbo.img and see what happens. Thanks for the hint.
Click to expand...
Click to collapse
I think dtb.img probably has all of the dtb files compiled together

elrod16 said:
I think dtb.img probably has all of the dtb files compiled together
Click to expand...
Click to collapse
That is my thought as well.

lexridge said:
That is my thought as well.
Click to expand...
Click to collapse
I just recently had to deal with all this crap because I didn't know GPD changed which revision of the mediatek SoC they used in the GPD XD while keeping the serial numbers the same. Flashed my old one's backup on it and half the cores were stuck offlined when it booted up. Ended up having to get ahold of the stock kernel for that board revision and patch in the correct dtb for that SoC.
I don't have links but some of the sites that delve into generic Linux kernel porting have tools for decompiling kernel_dtb files to an editable form that you can then recompile if you do have device/driver issues. Also the magisk module for enabling TWRP sdcard storage backups has some Android arm64 native binaries in it that can help with tearing apart kernel/recovery images. (They both are technically kernel images, just one boots a minimal OS).
Edit: I think any dtbo files would be individual compiled object files that get linked into the final dtb image.
Edit 2: I just saw your other comment above. Congrats, that sounds like a viable (and probably long term stable) way you found.

On another topic, I have been trying to mount /system as r/w (thru adb). It appears /system is not actually a mount point but under a different mount point. Any idea what that might be? Doing a cat on /proc/mounts yeilds a crapload of mounts, with many belonging to magisk, but no /system.

I know its been 4 month since last activity, but has there been any progress on this?

There does not seem to have been much progress on this, but I read somewhere recently that the G Stylus (2021) was either the most popular or best-selling Moto phone in 2021. Who knows if that is exactly true, but if it is indeed so popular, here's to hoping that some capable developers will take an interest in it eventually!

Several folks have mentioned that loading a GSI (Generic System Image) should be possible, but I have not had any extended downtime myself to be able to try this. But if you do, you can find some guidance for the 2020 version of the G Stylus at:
https://forum.xda-developers.com/t/...ic-system-image-on-the-moto-g-stylus.4131199/