Related
For building own custom stuff for my Gen8 Device I set up an Ubuntu 10.10 32bit Virtual Machine, so everything in here refers to it, may be different on other linux system.
[disclaimer]This is only a HowTo, if you brick your android device with some custom kernels or other stuff, don't blame me! I'm not responsible for anything you do![/disclaimer]
Notice: ** = you only have to do this step once
Prerequisites for Ubuntu 10.10 32 Bit: **
Code:
# sudo apt-get install git-core flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl automake autoconf libtool gettext texinfo libmpfr1ldbl
Prepare environment: **
Code:
# mkdir -pv $HOME/{archos,bin}
# echo export ARCHOS=\$HOME/archos >> ~/.bashrc
# echo export PATH=\$HOME/bin:\$PATH >> ~/.bashrc
# cd $HOME/archos
# wget -Oavos_env.tgz http://archos-gen8-dvb.googlecode.com/files/avos_env_20110415.tgz
# tar xzf avos_env.tgz
# install -m755 cross $HOME/bin/
# rm -f cross avos_env.tgz
RESTART CONSOLE OR REBOOT COMPUTER!
Toolchain: **
Code:
# cd $ARCHOS
# make all
Configure kernel:
Code:
# cd $ARCHOS
# make kernel-config
Restore kernel config:
Code:
# cd $ARCHOS
# make kernel-reset
Build kernel:
Code:
# cd $ARCHOS
# make kernel-build
CrossCompile: (this is just an example for if you want to build some linux libraries or tools)
Code:
# echo $ARCHOS
# cd ..xyz../..zyx../
# cross make
I followed your instructions, and I got all the way to the end, but when I did 'make kernel-build' it ended with this:
drivers/built-in.o: In function `archos_dpm_suspend':
/home/zyntax/archos/gen8-gpl-froyo/linux/drivers/usb/storage/archos_hdd.c:261: undefined reference to `usbsata_power'
make[3]: *** [.tmp_vmlinux1] Error 1
make[2]: *** [sub-make] Error 2
make[2]: Leaving directory `/home/zyntax/archos/gen8-gpl-froyo/linux'
make[1]: *** [/home/zyntax/archos/gen8-gpl-froyo/buildroot//linux/arch/arm/boot/zImage] Error 2
make[1]: Leaving directory `/home/zyntax/archos/gen8-gpl-froyo/buildroot'
make: *** [kernel-build] Error 2
[email protected]:~/archos$
This is on a fresh install of Ubuntu 10.10 32-bit in Virtualbox. I installed it, updated the OS, then started your steps. Not sure if this is normal and I'm holding off on the last step. I did do one extra step: in 'make kernal-config' I deselected all the Archos boards under System Type except for the A101IT since that's what I have.
jbradshw said:
This is on a fresh install of Ubuntu 10.10 32-bit in Virtualbox. I installed it, updated the OS, then started your steps. Not sure if this is normal and I'm holding off on the last step. I did do one extra step: in 'make kernal-config' I deselected all the Archos boards under System Type except for the A101IT since that's what I have.
Click to expand...
Click to collapse
can you please try again without modifying kernel config?
Did that, now I get this:
CC [M] drivers/usb/musb/omap2430.o
/home/zyntax/archos/gen8-gpl-froyo/linux/drivers/usb/musb/omap2430.c:221: warning: 'omap_phy_read' defined but not used
LD [M] drivers/usb/musb/musb_hdrc.o
LD drivers/built-in.o
make[2]: *** [sub-make] Error 2
make[2]: Leaving directory `/home/zyntax/archos/gen8-gpl-froyo/linux'
make[1]: *** [/home/zyntax/archos/gen8-gpl-froyo/buildroot//linux/arch/arm/boot/zImage] Error 2
make[1]: Leaving directory `/home/zyntax/archos/gen8-gpl-froyo/buildroot'
make: *** [kernel-build] Error 2
I don't believe I changed anything besides what I mentioned earlier. Is there anyway to get back a default kernel-config?
hehe, I thought you should try with default kernel-config
I added a section for restoring kernel config in the start posting :
chulri said:
[*]Restore kernel config:
Code:
# cd $ARCHOS
# tar xzf gen8-gpl-froyo.tgz gen8-gpl-froyo/linux/linux.config
Click to expand...
Click to collapse
Well I did poke around in the config, but as far as I remember I only removed those extra archos systems. I'll restore the default and run it again later tonight.
Thanks.
jbradshw said:
Well I did poke around in the config, but as far as I remember I only removed those extra archos systems. I'll restore the default and run it again later tonight.
Click to expand...
Click to collapse
You can't remove other devices (like A32, A101 etc) from Linux kernel config because Archos made bad dependencies for different parts of the kernel and even 70S requires some USB kernel code, it's only compiled when you choose A101 - so either you clean it up manually, or you are required to leave checked other archos devices :/
Thanks for this howto, this is gonna be useful for me, should be a sticky.
OK the make kernel-build worked without errors. Now I'm just questioning the command 'cd ..xyz../..zyx../' I don't have any files or directories called that, and running that reports the same. Can I just skip that and do the make cross?
@jbradshw that's just a sample if someone wants to crosscompile something (e.g. some linux library or application like linuxtv-dvb-apps or w_scan)
you don't have to do everything mentioned in the howto. it's a HowTo not a HaveTo
Ahh OK. So I guess I'm done then. I haven't installed the SDE on my Archos yet, but what's the final 'thing' that came out of this procedure that I'll be placing on the tablet?
Also I don't have an microSD card yet, and I know there was talk of putting stuff on there - can this be done using just the internal memory (8 GB for me)?
you have to install the SDE to install a custom kernel. follow this guide: http://forum.xda-developers.com/showthread.php?p=10157349#post10157349
Yeah I saw that guide, my question is where is the zImage and initramfs.cpio.gz that I assume was part of the compiling I just did? And also if a microSD card is needed for any of this?
no microsd is needed
initramfs.cpio.gz can be extracted from current installation ( /dev/mmcblk0p1 -> init ), read this: http://forum.xda-developers.com/showthread.php?t=880321&page=5
zImage is compiled at this location: $ARCHOS/gen8-gpl-froyo/buildroot/linux/arch/arm/boot/zImage
Shouldn't it be
Code:
cross make kernel-build
?
Here I have to use cross, which makes sense to find gcc arm binaries.
No you don't. In case of building stuff which comes with the gen8-gpl-froyo.tgz (e.g. kernel) the env vars are set up by the supplied makefiles
chulri said:
No you don't. In case of building stuff which comes with the gen8-gpl-froyo.tgz (e.g. kernel) the env vars are set up by the supplied makefiles
Click to expand...
Click to collapse
If I don't use cross, here is what I get:
[email protected]:~/archos$ make kernel-build
make -C gen8-gpl-froyo/linux mrproper
make[1]: arm-linux-gcc: Command not found
make[1]: Entering directory `/home/ubuntu/archos/gen8-gpl-froyo/linux'
make[3]: arm-linux-gcc: Command not found
But using cross it compiled fine, though I followed carefully your directions !
Apparently I was too frightened by the error messages, since it does work in the end
Thank you very much, hope some good things come from this !
Cheers !
desiresush said:
Apparently I was too frightened by the error messages, since it does work in the end
Click to expand...
Click to collapse
Yeah it's just an annoying bug, it doesn't hurt because "mrproper" only cleans the build directory and doesn't need compiler at all
2.6.29 kernel for Froyo?
Does anybody know, why Archos releases the SDK with a 2.6.29 kernel?
Shouldn't 2.2 Froyo be a 2.6.32 kernel?
Code:
No private recovery resources for TARGET_DEVICE mako
host C: mkbootimg <= system/core/mkbootimg/mkbootimg.c
prebuilts/tools/gcc-sdk/gcc: line 40: prebuilts/tools/gcc-sdk/../../gcc/linux-x86/host/i686-linux-glibc2.7-4.6/bin/i686-linux-gcc: No such file or directory
make: *** [/home/karishnu/android/omni/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o] Error 127
real 2m7.172s
user 0m57.349s
sys 0m20.914s
[email protected]:~/android/omni$
I am using ubuntu 13.10.
What I have tried :
1. Reinstalling GCC and build-essentials
2. checked if i686-linux-gcc is present (it is)
3. resynced the repo many times
What I found :
mkbootimg.o is missing from the directory.
.................................................. .............................
Pls temme what to do. I have tried a lot to fix this problem but in vain. There are no other threads mentioning the same problem also.
Hi,
I've wanted to use the app "limbo-android" ( https://code.google.com/p/limbo-android/ ) on my Intel Atom (x86) android tablet.
Unfortunatly, I have only found an apk for arm devices that crashes when I start a VM in the app. So, I have tried to build the app myself (I was following this https://code.google.com/p/limbo-android/source/browse/README ).
So far, I have downloaded the tools (SDK, NDK r8e, Eclipse + Eclipse Android plugin) and the source ( https://code.google.com/p/limbo-android/source/browse/ ) and unpacked all of it. After that, I have tried to follow the README file. So, i have competed steps 3, 4a, but I am stuck at point 4b. (I have also copied the NDK to /usr/local/bin because even when i have configured the right folders in step 3, it sayed something like ndk-build not found)
now with that done, if i type 'make' into the terminal, this is what i have got:
Code:
mkdir -p /home/sobotkama/limbo-android/jni/..//obj/local/x86/
rm -rf /home/sobotkama/limbo-android/jni/..//libs/armeabi ../libs/armeabi-v7a ../libs/x86 ../libs/mips \
mkdir -p /home/sobotkama/limbo-android/jni/..//libs/x86/
cd /home/sobotkama/limbo-android/jni/../ && ndk-build V=1 LIMBO_JNI_ROOT=/home/sobotkama/limbo-android/jni
make[1]: Entering directory `/home/sobotkama/limbo-android'
jni/Application.mk:10: ARCH_CFLAGS = -std=gnu99 -ffunction-sections -O3 -fomit-frame-pointer -fstrict-aliasing -funswitch-loops -finline-limit=300 -DANDROID_X86
jni/Application.mk:11: LOCAL_ARM_MODE =
jni/Application.mk:12: LOCAL_ARM_NEON =
jni/Application.mk:13: NDK_DEBUG =
jni/Application.mk:14: APP_OPTIM =
jni/Application.mk:15: APP_ABI = x86
/usr/local/bin/build/gmsl/__gmsl:512: *** non-numeric second argument to `wordlist' function: ''. Stop.
make[1]: Leaving directory `/home/sobotkama/limbo-android'
make: *** [sdl] Error 2
Running both Ubuntu and Windows 8.1 on my PC, doing this on Ubuntu.
Any help like what should I do or is there anyone that would build it for me, please?
Thanks, Sobotkama
Anyone?
First of all, I didn't modified any file so it seems that it was already downloaded with syntax error. I followed the instructions from here and here when preparing the building environment. When I run make -j8 I got the error:
FAILED: out/target/common/obj/all-event-log-tags.txt
/bin/bash -c "build/tools/merge-event-log-tags.py -o out/target/common/obj/all-event-log-tags.txt frameworks/base/core/java/android/app/admin/SecurityLogTags.logtags frameworks/base/core/java/android/content/EventLogTags.logtags frameworks/base/core/java/android/net/EventLogTags.logtags frameworks/base/core/java/android/speech/tts/EventLogTags.logtags frameworks/base/core/java/android/webkit/EventLogTags.logtags frameworks/base/core/java/com/android/internal/logging/EventLogTags.logtags frameworks/base/packages/SettingsProvider/src/com/android/providers/settings/EventLogTags.logtags frameworks/base/packages/SystemUI/src/com/android/systemui/EventLogTags.logtags frameworks/base/services/core/java/com/android/server/EventLogTags.logtags frameworks/base/services/core/java/com/android/server/am/EventLogTags.logtags frameworks/ex/common/java/com/android/common/GoogleLogTags.logtags frameworks/native/services/surfaceflinger/EventLog/EventLogTags.logtags frameworks/opt/telephony/src/java/com/android/internal/telephony/EventLogTags.logtags packages/apps/QuickSearchBox/src/com/android/quicksearchbox/EventLogTags.logtags packages/apps/Settings/src/com/android/settings/EventLogTags.logtags packages/providers/CalendarProvider/src/com/android/providers/calendar/EventLogTags.logtags packages/providers/ContactsProvider/src/com/android/providers/contacts/EventLogTags.logtags packages/services/Telephony/src/com/android/phone/EventLogTags.logtags system/bt/main/../EventLogTags.logtags system/core/liblog/event.logtags system/core/libsysutils/EventLogTags.logtags system/core/logcat/event.logtags system/core/logd/event.logtags"
File "build/tools/merge-event-log-tags.py", line 51
except getopt.GetoptError, err:
^
SyntaxError: invalid syntax
[ 0% 92/35341] host C++: aapt <= frameworks/base/tools/aapt/Main.cpp
ninja: build stopped: subcommand failed.
16:27:01 ninja failed with: exit status 1
make: *** [build/core/main.mk:21: run_soong_ui] Error 1
#### make failed to build some targets (53 seconds) ####
Click to expand...
Click to collapse
In this merge-event-log-tags.py file, at line 51, it has:
try:
opts, args = getopt.getopt(sys.argv[1:], "ho:m:")
except getopt.GetoptError, err:
print str(err)
print __doc__
sys.exit(2)
Click to expand...
Click to collapse
Also, this is my first time posting here and also first time trying to build android so if you guys need more information to help troubleshoot this, please let me know
fabiotk said:
First of all, I didn't modified any file so it seems that it was already downloaded with syntax error. I followed the instructions from here and here when preparing the building environment. When I run make -j8 I got the error:
In this merge-event-log-tags.py file, at line 51, it has:
Also, this is my first time posting here and also first time trying to build android so if you guys need more information to help troubleshoot this, please let me know
Click to expand...
Click to collapse
I've got this same problem trying to build 8.1.0. Did you (or anyone else) ever figure this out?
http://dpaste.com/0C1QWKE
UnderSampled said:
I've got this same problem trying to build 8.1.0. Did you (or anyone else) ever figure this out?
http://dpaste.com/0C1QWKE
Click to expand...
Click to collapse
Hello, yes, I solved it by making Python2 the default version instead of python3
Code:
sudo ln -sf /usr/bin/python2 /usr/bin/python
Introduction :
I'm not an expert in kernel development, but would like to share the steps that I followed to build my kernel. If any of other kernel developers out there would like to add on some tips or correct something, please do!
Pre-requisites :
Ubuntu or any other Linux based OS
Stable Internet Connection
Patience
Step 1 : Setup Build Environment
Open the terminal and enter the following :
Code:
sudo apt-get install git ccache automake flex lzop bison \
gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 \
g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev \
libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush \
schedtool dpkg-dev liblz4-tool make optipng maven libssl-dev \
pwgen libswitch-perl policycoreutils minicom libxml-sax-base-perl \
libxml-simple-perl bc libc6-dev-i386 lib32ncurses5-dev \
x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev xsltproc unzip
Step 2 : Download Required Files
Download device source :
Code:
git clone --depth=1 https://github.com/MiCode/Xiaomi_Kernel_OpenSource.git -b raphael-p-oss raphael-p-oss
Download a compatible GCC toolchain (Using AOSP's GCC for this guide) :
Code:
cd raphael-p-oss
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9 toolchain
Download a compatible CLANG toolchain (Using AOSP's CLANG for this guide) : Download
Move the downloaded file in the raphael-p-oss folder manually and then extract using the following command :
Code:
tar vxzf linux-x86-android-9.0.0_r48-clang-4691093.tar.gz
Download the device-tree-compiler attached below and place it in /usr/bin
Step 3 : Make device specific changes
Make these changes in the /kernel/module.c file.
If you are not familiar with github, you can check out many github guides available on XDA, for now you can just download the module.c file attached to this thread and replace the one in /kernel folder with the downloaded one!
Now, browse back to raphael-p-oss directory, and open the raphael_user_defconfig located in \arch\arm64\configs
Add the following lines :
Code:
CONFIG_BUILD_ARM64_DT_OVERLAY=y
CONFIG_MODULE_FORCE_LOAD=y
WIFI & Audio won't work if you don't make these changes, apparently Xiaomi decided to skip wlan & audio drivers in pie sources.
Step 4 : Building The Kernel
Code:
cd raphael-p-oss
rm -rf out
mkdir out
export ARCH=arm64
export SUBARCH=arm64
export DTC_EXT=dtc
make O=out ARCH=arm64 raphael_user_defconfig
PATH="${PWD}/bin:${PWD}/toolchain/bin:${PATH}" \
make -j$(nproc --all) O=out \
ARCH=arm64 \
CC=clang \
CLANG_TRIPLE=aarch64-linux-gnu- \
CROSS_COMPILE=aarch64-linux-android- | tee kernel.log
Step 5 : How To Get Help If You Encounter Errors
A kernel.log file will be generated in raphael-p-oss folder, find the line which says error.
If you can't figure out the solution, attach the kernel.log in your reply to this thread.
Step 6 : Booting The Kernel
Once you're done with Step 4, browse to /out/arch/arm64/boot & you'll find the Image-dtb file (compiled zImage)
Download the anykernel template for raphael from attachments and add your Image-dtb file to the archive.
Boot in TWRP, backup your stock kernel & flash the anykernel zip.
References :
Information on compiling Android kernels with Clang by nathanchance
How to compile kernel standalone by Xiaomi
Kernel Builder Virtual Machine & device specific changes by mslezak
AnyKernel3 Template by osm0sis
Wahoo Kernel Tools by frap129
Regards,
acervenky
Using QCom Clang To Compile Kernel [Xiaomi's Guide]
Step 1 : Setup Build Environment
Open the terminal and enter the following :
Code:
sudo apt-get install git ccache automake flex lzop bison \
gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 \
g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev \
libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush \
schedtool dpkg-dev liblz4-tool make optipng maven libssl-dev \
pwgen libswitch-perl policycoreutils minicom libxml-sax-base-perl \
libxml-simple-perl bc libc6-dev-i386 lib32ncurses5-dev \
x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev xsltproc unzip
Step 2 : Download Required Files
Download device source :
Code:
git clone --depth=1 https://github.com/MiCode/Xiaomi_Kernel_OpenSource.git -b raphael-p-oss raphael-p-oss
Download a compatible GCC toolchain (Using AOSP's GCC for this guide) :
Code:
cd raphael-p-oss
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9 toolchain
Download a Qcom CLANG : Download
Move the downloaded file in the raphael-p-oss folder manually and then extract using the following command :
Code:
tar vxzf snapdragon-llvm-compiler-android-linux64-609.tar.gz
Download the device-tree-compiler attached below and place it in /usr/bin
Step 3 : Make device specific changes
Make these changes in the /kernel/module.c file.
If you are not familiar with github, you can check out many github guides available on XDA, for now you can just download the module.c file attached to this thread and replace the one in /kernel folder with the downloaded one!
Now, browse back to raphael-p-oss directory, and open the raphael_user_defconfig located in \arch\arm64\configs
Add the following lines :
Code:
CONFIG_BUILD_ARM64_DT_OVERLAY=y
CONFIG_MODULE_FORCE_LOAD=y
WIFI & Audio won't work if you don't make these changes, apparently Xiaomi decided to skip wlan & audio drivers in pie sources.
Step 4 : Building The Kernel
Code:
cd raphael-p-oss
rm -rf out
mkdir out
export ARCH=arm64
export SUBARCH=arm64
export DTC_EXT=dtc
export CROSS_COMPILE=${PWD}/toolchain/bin/aarch64-linux-android-
make O=out REAL_CC=${PWD}/toolchains/llvm-Snapdragon_LLVM_for_Android_6.0/prebuilt/linux-x86_64/bin/clang CLANG_TRIPLE=aarch64-linux-gnu- raphael_user_defconfig
make -j$(nproc) O=out REAL_CC=${PWD}/toolchains/llvm-Snapdragon_LLVM_for_Android_6.0/prebuilt/linux-x86_64/bin/clang CLANG_TRIPLE=aarch64-linux-gnu- 2>&1 | tee kernel.log
Step 5 : How To Get Help If You Encounter Errors
A kernel.log file will be generated in raphael-p-oss folder, find the line which says error.
If you can't figure out the solution, attach the kernel.log in your reply to this thread.
Step 6 : Booting The Kernel
Once you're done with Step 4, browse to /out/arch/arm64/boot & you'll find the Image-dtb file (compiled zImage)
Download the anykernel template for raphael from attachments and add your Image-dtb file to the archive.
Boot in TWRP, backup your stock kernel & flash the anykernel zip.
This method is mentioned in Xiaomi's Wiki, you can choose any according to your preference!
Regards,
acervenky
How To Compile Custom DTBO
DTBO files have been used on our device primarily to change the refresh rates.
Pre-requisites :
Compiled kernel without any errors
Step 1 : Download Required Files
Download libufdt utils from this link.
Open the terminal in the downloaded file's location.
Code:
tar vxzf libufdt-master-utils.tar.gz
Step 2 : Compile dtbo.img
Code:
cd libufdt-master-utils/src
python mkdtboimg.py create /home/user/raphael-p-oss/out/arch/arm64/boot/dtbo.img /home/user/raphael-p-oss/out/arch/arm64/boot/dts/qcom/*.dtbo
Step 3 : Flash The Compiled dtbo.img
The compiled dtbo.img file will be located in /raphael-p-oss/out/arch/arm64/boot/ (same output folder of zImage)
Backup your stock dtbo.img and flash the newly compiled dtbo.img
References :
Kernel Builder by mslezak
Regards,
acervenky
reserved3
Nice guide bro...
acervenky said:
Introduction :
I'm not an expert in kernel development, but would like to share the steps that I followed to build my kernel. If any of other kernel developers out there would like to add on some tips or correct something, please do!
Regards,
acervenky
Click to expand...
Click to collapse
awesome guide bro. I will try with my free time. Thanks
Quick question, would the same procedure work for Mi 9T Pro EEA?
I'd like to take a look in that DTBO.img
The phone runs the European Rom and the device ID is the Raphael_EEA.
Thanks in advance!!
acervenky said:
DTBO files have been used on our device primarily to change the refresh rates.
Pre-requisites :
Compiled kernel without any errors
Step 1 : Download Required Files
Download libufdt utils from this link.
Open the terminal in the downloaded file's location.
Step 2 : Compile dtbo.img
Step 3 : Flash The Compiled dtbo.img
The compiled dtbo.img file will be located in /raphael-p-oss/out/arch/arm64/boot/ (same output folder of zImage)
Backup your stock dtbo.img and flash the newly compiled dtbo.img
References :
Kernel Builder by mslezak
Regards,
acervenky
Click to expand...
Click to collapse
Do you have any idea how the display OC mod was done? If you understand it, it would be great if you shared that information, the more people know, more chances of improving it
Build failed
Made no modification, followed your steps exactly, after about 7-10mins of compiling I got this error in terminal:
Code:
make[1]: Leaving directory '/home/rituj/raphael-p-oos/out'
make: *** [sub-make] Error 2
Makefile:146: recipe for target 'sub-make' failed
After searching "error" it only returned a couple of modules that had "error" in their names.
attached the kernel.log
rituj_b said:
Made no modification, followed your steps exactly, after about 7-10mins of compiling I got this error in terminal:
Code:
make[1]: Leaving directory '/home/rituj/raphael-p-oos/out'
make: *** [sub-make] Error 2
Makefile:146: recipe for target 'sub-make' failed
After searching "error" it only returned a couple of modules that had "error" in their names.
attached the kernel.log
Click to expand...
Click to collapse
DTC Compile error, uninstall any pre-installed DTC and use the one provided in attachments!
Regards,
acervenky
acervenky said:
DTC Compile error, uninstall any pre-installed DTC and use the one provided in attachments!
Regards,
acervenky
Click to expand...
Click to collapse
Replaced dtc file with attached in post. Got the same error. Kernel.log in attachment
nevermind, changed permissions on dtc in /usr/bin
Build finished with this log
pemaster said:
Replaced dtc file with attached in post. Got the same error. Kernel.log in attachment
nevermind, changed permissions on dtc in /usr/bin
Build finished with this log
Click to expand...
Click to collapse
Got it to boot?
Regards,
acervenky
acervenky said:
Got it to boot?
Regards,
acervenky
Click to expand...
Click to collapse
Not yet. Need to flash pie miui first because I am on q now.
Hey acervenky I saw you used my same defconfig for F2FS and the same F2FS zip on your repo, but I compiled for a buddy of mine (Mi9T Pro EEA) and it refuses to boot F2FS? Did you change anything else? Head scratching here why it works on a Mi9 and your QUAX but not when I build this way. Thanks.
mslezak said:
Hey acervenky I saw you used my same defconfig for F2FS and the same F2FS zip on your repo, but I compiled for a buddy of mine (Mi9T Pro EEA) and it refuses to boot F2FS? Did you change anything else? Head scratching here why it works on a Mi9 and your QUAX but not when I build this way. Thanks.
Click to expand...
Click to collapse
Upstreamed F2FS, arter has a post dedicated to this maybe you can check that out?
Regards,
acervenky
after compile i found some error on kernel.log
DTC arch/arm64/boot/dts/qcom/apq8016-sbc.dtb
scripts/Makefile.lib:325: recipe for target 'arch/arm64/boot/dts/qcom/apq8016-sbc.dtb' failed
../scripts/Makefile.build:678: recipe for target 'arch/arm64/boot/dts/qcom' failed
arch/arm64/Makefile:184: recipe for target 'dtbs' failed
CC lib/iomap_copy.o
Xeniel768 said:
after compile i found some error on kernel.log
DTC arch/arm64/boot/dts/qcom/apq8016-sbc.dtb
scripts/Makefile.lib:325: recipe for target 'arch/arm64/boot/dts/qcom/apq8016-sbc.dtb' failed
../scripts/Makefile.build:678: recipe for target 'arch/arm64/boot/dts/qcom' failed
arch/arm64/Makefile:184: recipe for target 'dtbs' failed
CC lib/iomap_copy.o
Click to expand...
Click to collapse
Did you use the DTC attached to the OP?
If you're still facing issues try changing the permissions to 755 & try again.
Regards,
acervenky
acervenky said:
Did you use the DTC attached to the OP?
If you're still facing issues try changing the permissions to 755 & try again.
Regards,
acervenky
Click to expand...
Click to collapse
yea, i use dtc from attachment but still error
i already upload some log and screenshot link below
*drive.google*com/open?id=1YRZ912cDuWCGNlyfQXQKyfnEpl_2eJNi
Xeniel768 said:
yea, i use dtc from attachment but still error
i already upload some log and screenshot link below
*drive.google*com/open?id=1YRZ912cDuWCGNlyfQXQKyfnEpl_2eJNi
Click to expand...
Click to collapse
Checked out your screenshots, seems like you placed the dtc inside the source folder.
Placing it in root/usr/bin will fix your error!
Regards,
acervenky
nice guide.