I've got an error in kernel makeing process. Even when I just unpack an archive, apply a defconfig (our is sp7731gea_hdr-dt_defconfig) and doing make nconfig with then just saving (to refresh config) it, then make interrupts with an error.
Kernel version 3.10.65, building with HYPER Linaro 6.0 (it is here somewhere in XDA), gcc6.
The screenshot is attached.
Help me solve this problem please!
Looks like this is solved by switching from Linaro HYPER gcc 6.0 to normal Linaro gcc 4.9.
Please do not close this thread as the problem at all may be incomplete (building is in process at the moment)...
igoryan94 said:
Looks like this is solved by switching from Linaro HYPER gcc 6.0 to normal Linaro gcc 4.9.
Please do not close this thread as the problem at all may be incomplete (building is in process at the moment)...
Click to expand...
Click to collapse
This problem is solved, kernel compiles, but now this kernel does not boot. Maybe I've taken incorrect config variant.
igoryan94 said:
This problem is solved, kernel compiles, but now this kernel does not boot. Maybe I've taken incorrect config variant.
Click to expand...
Click to collapse
Update. Kernel is good but the problem is boot, it does not boot even when I just unpack, pack and try to boot it... How must I pack it then? I use a kernel kitchen for now..
Thanks for (non-)helping, everyone who could but did not :crying:
Related
Hello together,
I hope someone maybe can help me out. In the past I comiled the standard CM11 kernel by myself. I just add a few minor tweaks for my display color calibration and so on. Nothing special.
Since CM11 I'm always stuck in a bootloop after the "Google" logo. Even if I try only the stock CM11 kernel without any changes. Same toolchain (4.7) and so on. Why is that the case?!
I hope someone, maybe from all the experiencened kernel creators here, can give me a hint where's my problem? Is it maybe something with all the SELinux stuff? It was also the case in CM10.2 if I tried to comile with modules enabled.
Help here would be very appreciated. Thanks in advance.
Regards, Fred
OK, I answer this question myself. Just found out you have to compile the kernel inline with cyanogenmod. Sync the whole repo, initialize your device, make the changes to the kernel and compile it with make bootimage. This way I also have no need to use Anykernel script anymore.
Hello guys,
My kernel ( KTmanta) is compiled by myselif suing a a15 optimized toolchain. Boots, working nice, however, any build with 4.8, 4.9, will stay at loading screen forever.
Any one can help me out , or might know the source of the problem?? I used once adb bugreport but haven't found interessting stuff(or at least I think)
Thank you.
Suggestion: have you tried building the kernel with another (prebuilt) toolchain, that includes GCC 4.8, 4.9? Maybe you missed something?
Search in forum "JustArchi's ArchiDroid Optimizations" (sorry, I cannot post links).
In that thread there are some patches for fix not booting kernel with gcc 4.8.
Unofficial CM12.1 kernel for Galaxy S4 Mini (3G|LTE|DUOS)
Features:
Based on official CM12.1 kernel source
Hotplug thread infrastructure
Sweep2Sleep
Fast charge
Upgraded taus88 to taus113 algorithm for entropy generator
Frandom (fast random number generator)
Krait optimized strcmp and memcmp
Motorola MSM memcopy enhancements (memutils) to improve of the memory subsystem performance
Optimized ARM RWSEM (read/write semaphore) algorithm
CPU-boost
Quickwakeup
UKSM (Ultra Kernel SamePage Merging)
Timer slack controller
Speedup late resume patch for faster wakeup of the device
Updated F2FS
Updated exFAT
NTFS with full support read/write access
init.d support
zRAM
LZ4 compressor/decomressor for zRAM
TCP-cong: westwood, vegas, reno and etc.
Set SELinux always into "Permissive mode"
Faux123's Simple GPU governor
Faux123's IntelliThermal
Faux123's GPL Sound Control 3.5
Dynamic FSync
Dynamic dirty page writebacks
Dynamic LowMemoryKiller with management of not killable processes
Compiled with Linaro GCC 4.9.4-2015.06 Toolchain
CPU hotplugs:
Faux123's Intelliplug
MyFluxi's MSM-hotplug
Alucard-hotplug
Lazy-hotplug
Governors:
Alugard
[*]lteracative
[*]Dancedance
[*]Darkness
[*]Impulse
[*]Intelliminmax
[*]Intellidemand
[*]Intelliactive
[*]Lionheart
[*]Nigtmare
[*]Ondemandplus
[*]Optimax
[*]Preservative
[*]Slim
[*]Smartmax
[*]SmartAssV2
[*]SmartAssH3
[*]Uberdemand
[*]Wheatly
[*]Yankactiv
I/O Schedulers:
Noop
[*]Daedline
[*]ROW
[*]CFQ
[*]FIOPS (Fair Input/Output Per Second)
[*]SIO (Simple I/O)
[*]BFQ
[*]Tripendriod
Credits:
@arco68
@Christopher83
@F4k
@junkyde
@SilviuMik
@GrarakInstallation instructions:
1. Copy XXXX-ALX-x.x.x.zip to your sdcard
2. Reboot into CWM recovery
3. Choose "Install zip from sdcard"
4. Select XXXX-ALX-x.x.x.zip kernel and confirm installation.
XDA:DevDB Information
Custom CM12.1 Kernel for I9190/I9195/I9192, Kernel for the Samsung Galaxy S 4 Mini
Contributors
alexax66
Source Code: https://github.com/alexax66/CM12.1_kernel_serranodsxx
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: ALX-0.2.7
Stable Release Date: 2015-11-23
Created 2015-11-24
Last Updated 2015-11-24
Reserved
Reserved
Hi, all!
I start new thread for my CM12.1 kernel
alexax66 said:
Hi, all!
I start new thread for my CM12.1 kernel
Click to expand...
Click to collapse
Nice features and impressive number of governors :good:
Testing then report back.
Thank you very much ,our friend !!!!
woow...for to find the best governor/scheduler/hotplugg.... for best battery-life (with correct performance )
i cant compile on this pc
Has anyone compiled it for the I9195?
if so can i have a copy please as i cant get to my own pc until the weekend.
download link ? Also why is thread not is android development section ?
sasank360 said:
download link ? Also why is thread not is android development section ?
Click to expand...
Click to collapse
i think we have to compile it ourselves.
Having in mind the fact that 99% of us won't even dare to think about installing a kernel compiled by ourselves, is there a chance for someone more experimented to compile this kernel for all 3 versions?
I personally only need the lte version, but...
Thank you in advance.
Can not compile (newbie)
I would love to test this kernel and give feedback but I have no knowledge on how to compile. What's the chances on someone doing this with experience? I'm after the LTE version myself, I'm excited for a new kernel to play with. Or maybe someone can send meva walk through guide on his to compile.
Thanks in advance ☺
Has anyone tried it yet?
@alexax66
Please upload the kernel .zip or change Installation instruction
Installation instructions:
1. Copy XXXX-ALX-x.x.x.zip to your sdcard
2. Reboot into CWM recovery
3. Choose "Install zip from sdcard"
4. Select XXXX-ALX-x.x.x.zip kernel and confirm installation.
Click to expand...
Click to collapse
piskor said:
@alexax66
Please upload the kernel .zip or change Installation instruction
Click to expand...
Click to collapse
I had random reboot with this kernel after applied last patches
I will be find what is problem and will build new version
alexax66 said:
I had random reboot with this kernel after applied last patches
I will be find what is problem and will build new version
Click to expand...
Click to collapse
Any luck yet bud?
Can you uploud the .ZIP file ?
I wanna test the Gaming performance and compare the results with the lombartz kernel
improves battery?
Well i think thats the end of that.
Kernel is not stable, so we must wait. Patience, patience and one more time patience
piskor said:
Kernel is not stable, so we must wait. Patience, patience and one more time patience
Click to expand...
Click to collapse
Could you update the OP so we all know what we are waiting for, change (stable) to its current title etc etc, all I'm seeing is disinterest in this thread. Maybe release a pre-release version so someone else can help you, there is no point to compile this myself or I might as well start my own thread.
Looking forward to your clarification and thanks in advance.
I'm trying to build a ROM for this device and i'm stuck on this stupid error, it is about dex2oatd, the compiler does not give an dex file as input, please somebody help me.
Java JDK,JRE 1.8.0_111
My Distro is: Ubuntu 14.04.5 LTS (I've had 16.04 before)
CPU: Intel Xeon E5 2.3Ghz (3 cores (because VM))
RAM: 5 GB
And yes it's a vps.
i will attach a part of the build log.
redknight65 said:
I'm trying to build a ROM for this device and i'm stuck on this stupid error, it is about dex2oatd, the compiler does not give an dex file as input, please somebody help me.
Java JDK,JRE 1.8.0_111
My Distro is: Ubuntu 14.04.5 LTS (I've had 16.04 before)
CPU: Intel Xeon E5 2.3Ghz (3 cores (because VM))
RAM: 5 GB
And yes it's a vps.
i will attach a part of the build log.
Click to expand...
Click to collapse
Try to not build with ninja, I've had issues with ninja wrapper before and after disabling it in bashrc fixed my issues.
But not sure, though. You might still get errors even after disabling ninja.
What rom are you trying to build?
XTutorials said:
Try to not build with ninja, I've had issues with ninja wrapper before and after disabling it in bashrc fixed my issues.
But not sure, though. You might still get errors even after disabling ninja.
What rom are you trying to build?
Click to expand...
Click to collapse
I'm trying to build Dirty Unicorns and that is the only error that stay in my way I think. (as you can see it stopped at 62%) but now I deleted the source and I'm retrying to build AOSPA with haky86's device tree.
redknight65 said:
I'm trying to build Dirty Unicorns and that is the only error that stay in my way I think. (as you can see it stopped at 62%) but now I deleted the source and I'm retrying to build AOSPA with haky86's device tree.
Click to expand...
Click to collapse
, I am building AOSPA with OK source, but let me know if you succeded and it boots, I think I will leave this project and retry MIUI or other ROM, because right now I have many exams and I will pause developing for 2 weeks.
XTutorials said:
, I am building AOSPA with OK source, but let me know if you succeded and it boots, I think I will leave this project and retry MIUI or other ROM, because right now I have many exams and I will pause developing for 2 weeks.
Click to expand...
Click to collapse
I tried the OK source and I've had a bunch of errors so I tried other ROMs and now I want to retry with haky86's source
Regarding this thread https://forum.xda-developers.com/moto-g4-plus/development/kalilinux-nethunter-t3639411
The OP tywinlannister did not patch the kernel source code with Android USB HID PATCH To use the Android device as keyboard or mouse..This should be applied for nethunter ROM, But he didn't..
And I asked resurrection remix ROM maintainer Jleeblanch for Athene to look at this issue he did it , after applying the patch it didn't successfully compile ,there were errors..By seeing the error he said that the official kernel is partially patched already,so it is causing those errors..
If anybody looks into the problem it would be appreciated just in your free time only ...
The link to kernel source of Jleeblanch is the "Kali branch" https://github.com/Jleeblanch/android_kernel_motorola_msm8952
Any problem or suggestions regarding to this can be discussed here itself , that others can address the issue..
I too have been waiting for a working kernel so I am going to attempt to compile a working kernel with hid with my limited kernel development knowledge. I think it probably won't work as two far better devs than me have yet been unable however I will try anyway
Any help from fellow devs would be greatly appreciated
Dougleplex said:
I too have been waiting for a working kernel so I am going to attempt to compile a working kernel with hid with my limited kernel development knowledge. I think it probably won't work as two far better devs than me have yet been unable however I will try anyway
Any help from fellow devs would be greatly appreciated
Click to expand...
Click to collapse
I am also a newbie to kernel development but I manually patched the hid sources to kernel source..
But when we complied it all those errors.
First I think we should delete all those hid patches all applied to the stock kernel source. Then compile it and then apply the patch by pelya...
My ROM s kernel developer say MM kernel will be easy but it is also partially patch
You may give it a try
Dhanush-raj said:
I am also a newbie to kernel development but I manually patched the hid sources to kernel source..
But when we complied it all those errors.
First I think we should delete all those hid patches all applied to the stock kernel source. Then compile it and then apply the patch by pelya...
Click to expand...
Click to collapse
I'm going to attempt to patch jleeblanch's rr kernel and then work backwards depending on the errors as last time I did something like this (s7 edge nethunter kernel) the error was a corrupted source and could easily have been fixed by finding a different repository rather than starting from scratch (what we did). I'm unsure as to what will happen after that however your idea is just as valid and I will try straight after (if you haven't already)
Test this kernel
Note that this is the Invicta kernel. You need a revert before the actual patch. Both commits are available on my gitlab.
Merged both into a single commit. Note that Invicta kernel is still 3.10.84. Upstream kernels may need additional changes. Test and let me know.
If you want to apply the patch to your kernel, you can use the attached patch file or use the commands below. ( using lineage kernel as example )
Code:
git clone https://github.com/LineageOS/android_kernel_motorola_msm8952.git
cd android_kernel_motorola_msm8952
git checkout cm-14.1
git remote add invicta https://gitlab.com/sileshn/android_kernel_motorola_athene.git
git fetch invicta
git cherry-pick 04aa0b10521b76e57226b2d1633e2b91cfa40263
If you don't get errors, you are good to go. If it errors, it needs more changes.
Silesh.Nair said:
Note that this is the Invicta kernel. You need a revert before the actual patch. Both commits are available on my gitlab.
Merged both into a single commit. Note that Invicta kernel is still 3.10.84. Upstream kernels may need additional changes. Test and let me know.
If you want to apply the patch to your kernel, you can use the attached patch file or use the commands below. ( using lineage kernel as example )
Code:
git clone https://github.com/LineageOS/android_kernel_motorola_msm8952.git
cd android_kernel_motorola_msm8952
git checkout cm-14.1
git remote add invicta https://gitlab.com/sileshn/android_kernel_motorola_athene.git
git fetch invicta
git cherry-pick 04aa0b10521b76e57226b2d1633e2b91cfa40263
If you don't get errors, you are good to go. If it errors, it needs more changes.
Click to expand...
Click to collapse
Kernel version 3.10.105 was initially the kernel I tried patching. I was easily able to merge the patch, but compiling it was a different story. According the errors I got, a lot of thing we're duplicated. I told the guy above that the MM based kernel (3.10.84 - which is the same version for MM thru Nougat on stock) would probably be the best bet. Looks like you had little trouble at all with merging into your Invicta Kernel (which is also kernel version 3.10.84).
Good job and thank you [emoji41]
Silesh.Nair said:
Note that this is the Invicta kernel. You need a revert before the actual patch. Both commits are available on my gitlab.
Merged both into a single commit. Note that Invicta kernel is still 3.10.84. Upstream kernels may need additional changes. Test and let me know.
If you want to apply the patch to your kernel, you can use the attached patch file or use the commands below. ( using lineage kernel as example )
If you don't get errors, you are good to go. If it errors, it needs more changes.
Click to expand...
Click to collapse
Thanks @Silesh.Nair I have been waiting long time for this patch. Once again thank you sir...
The patch is working perfectly in 3.10.105 i.e jleeblanch kernel source..
Linux version 3.10.107-lineageOS ([email protected]) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) ) #1 SMP PREEMPT Sat Aug 5 04:20:04 PDT 2017
And thank you @Jleeblanch Also
boot tool
Silesh.Nair said:
Note that this is the Invicta kernel. You need a revert before the actual patch. Both commits are available on my gitlab.
Merged both into a single commit. Note that Invicta kernel is still 3.10.84. Upstream kernels may need additional changes. Test and let me know.
If you want to apply the patch to your kernel, you can use the attached patch file or use the commands below. ( using lineage kernel as example )
Code:
git clone https://github.com/LineageOS/android_kernel_motorola_msm8952.git
cd android_kernel_motorola_msm8952
git checkout cm-14.1
git remote add invicta https://gitlab.com/sileshn/android_kernel_motorola_athene.git
git fetch invicta
git cherry-pick 04aa0b10521b76e57226b2d1633e2b91cfa40263
If you don't get errors, you are good to go. If it errors, it needs more changes.
Click to expand...
Click to collapse
Hey which tool did you used to make boot.img.
Marella ram_youtubr said:
Note that this is the Invicta kernel. You need a revert before the actual patch. Both commits are available on my gitlab.
Merged both into a single commit. Note that Invicta kernel is still 3.10.84. Upstream kernels may need additional changes. Test and let me know.
If you want to apply the patch to your kernel, you can use the attached patch file or use the commands below. ( using lineage kernel as example )
Hey which tool did you used to make boot.img.
Click to expand...
Click to collapse
I am using lazyflasher
https://github.com/jcadduono/lazyflasher
Just clone this repo and place the zimage in there and type make, you will get a zip file. Just flash it through twrp recovery. Because only the kernel is changed , so i am just replacing the zimage. No need of unpacking and repacking of boot image.:good:
i have compiled a zimage from kali_defconfig from above source.but when i flased it to phone the phone is not booting.
I NEED A FIX FOR THIS
Marella ram_youtubr said:
i have compiled a zimage from kali_defconfig from above source.but when i flased it to phone the phone is not booting.
I NEED A FIX FOR THIS
Click to expand...
Click to collapse
Which toolchian did you use, and what kernel source and rom you are using .
Give me as detailed information as possible!
Dhanush-raj said:
Which toolchian did you use, and what kernel source and rom you are using .
Give me as detailed information as possible!
Click to expand...
Click to collapse
Kernel Source:-https://github.com/Jleeblanch/android_kernel_motorola_msm8952/tree/kali-nougat
toolchain:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8 nougat-release
rom:- lineage 14.1 official
Marella ram_youtubr said:
Kernel Source:-https://github.com/Jleeblanch/android_kernel_motorola_msm8952/tree/kali-nougat
toolchain:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8 nougat-release
rom:- lineage 14.1 official
Click to expand...
Click to collapse
Don't use that source it isn't patched correctly, although i said mr. Jleeblanch to try , so he created it. The hid patch is merged into his resurrected kernel, but for mac injection i dont remember. So you better start from the first.
Use lineage kernel source and apply the patch from this thread #6th post, and see what toolchain is used to build lineage 14 kernel and use it. And additionally you have to make some changes in the defconfig, which is explained in the kali-nethunter github page.
Dhanush-raj said:
Don't use that source it isn't patched correctly, although i said mr. Jleeblanch to try , so he created it. The hid patch is merged into his resurrected kernel, but for mac injection i dont remember. So you better start from the first.
Use lineage kernel source and apply the patch from this thread #6th post, and see what toolchain is used to build lineage 14 kernel and use it. And additionally you have to make some changes in the defconfig, which is explained in the kali-nethunter github page.
Click to expand...
Click to collapse
thanks buddy
Dhanush-raj said:
Don't use that source it isn't patched correctly, although i said mr. Jleeblanch to try , so he created it. The hid patch is merged into his resurrected kernel, but for mac injection i dont remember. So you better start from the first.
Use lineage kernel source and apply the patch from this thread #6th post, and see what toolchain is used to build lineage 14 kernel and use it. And additionally you have to make some changes in the defconfig, which is explained in the kali-nethunter github page.
Click to expand...
Click to collapse
sileshn has removed his source
Marella ram_youtubr said:
sileshn has removed his source
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...ustom-kernel-developers-t3641363/post73257121
Dhanush-raj said:
https://forum.xda-developers.com/mo...ustom-kernel-developers-t3641363/post73257121
Click to expand...
Click to collapse
He had deleted his repo from gitlab
Marella ram_youtubr said:
He had deleted his repo from gitlab
Click to expand...
Click to collapse
use this bro...
Dhanush-raj said:
use this bro...
Click to expand...
Click to collapse
Actually my orginal phone is honor 6x.I love portable hacking.Like with nethunter.I tried to build nethunter kernel for honor 6x.But i failed at HID.So i took by brothers old phone That is moto g4 plus.later i found that moto g4 plus at android 7 is 32 bit.As there is no nethunter for 32 bit i have decided that atleast i should use linux deploy.But later i suck at wifi drivers.When i enable wifi drivers in kernel then phone doenst boot.
The final thing is can anyone help me in fixing this so that i can build a complete usable kernel with Net Hunter support