MID7012 - Kernel Building ERROR - PLS Help! - Android Q&A, Help & Troubleshooting

so far i have downloaded the tcc8902 kernel, it fails to build...
using ubuntu 11.10
am i missing something in my toolchain???
when i "make menuconfig" i get a few error....
and after that i just run "make" it fails.... see image...
{
"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"
}

i would like to finish this build so i can OC this device...
the kernel come pre-setup with the freqtables and voltages from the mid9200
any help would be nice!
would be very nice if it would just build!!!!!

have a look at the cyanogen wiki about setting up your cross compiler.
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
Sent from my Nexus One using XDA App

i will try this.... i understand now, cant build ARM source with out an arm processor, the ia32 doesnt read or write arm source.... wow....
will try later gotta goto school... preparing for a test.... i pray this works, i got a whole ton of people wanting this kernel and android build....

Hi you can still compile for arm on your pc. you just need a compiler that can output arm code.
first download the ARM EABI Toolchain for your computer
then set the environment variable for the arm build toolchain. such as
export CCOMPILER=[extraction directory]/bin/arm-eabi-
then build kernel with new toolchain
make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
and if your .config is correct that should get you a working kernel.
ps. and by your first screenshot it looks like your .config is the default from /boot/config-3.0.0-14.
so back to the wiki with how to get the .config from your android device
adb pull /proc/config.gz /home/user_name/android/kernel/cm-kernel/config.gz
cat config.gz | gunzip > .config
make ARCH=arm CROSS_COMPILE=$CCOMPILER oldconfig
hope that helps and good luck!

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A

just my luck... i tryed to build the toolchain... and i picked a broken script... stupid download... md5 was correct, just a broken installer script... error code 1 and code 2.... garbage...
recomend any good arm cross-compiler toolchains?

The prebuilt binaries from here should be all you need.
https://sourcery.mentor.com/sgpp/lite/arm/portal/subscription3053
then just make sure to export CCOMPILER=path/to/toolchain/bin/arm-none-eabi-

any progress been made on this? theres a lot of delveopment happening over at the KTZ Forums but not much about developing kernels. you should take a peak.

LemonHead2089 said:
any progress been made on this? theres a lot of delveopment happening over at the KTZ Forums but not much about developing kernels. you should take a peak.
Click to expand...
Click to collapse
I second that, I need a kernel that is OC-able since this rubbish wont run faster than 720mhz.
Has anyone been able to run ICS on this? Any other roms other than the KTZ ones? I really don't like them to be honest (I do appreciate their work) but I would prefer CM7 or something similar, maybe something very light would also be awesome.

Related

anyone wanna beta a sense kernel?

I have been running this kernel and modules all day and all if freaking great. My antutu benchmarks have been in the 8100's to high 8200's on stock CPU clock @ 1.5 with a stock [email protected] ondemand. I mainly want it ran on all different sense roms. Send me a pm if you want to and ill send the link tomorrow. I wanna test myself for a day just for the safety of your device. Thanks all
Yea I see it...I think ill keep the base don't wanna brick downgrading. Ok here it is I'm on mean Rom 6.0 no overclocking 1.5ghz on demand gov sd read ahead 2048 noop.
{
"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"
}
im in there like swim wear! send it my way.. ill run it threw the ropes!
Meanrom is the ****. I'm not usually a fanboy to anyone but myself Lol but that rom is kid tested mother approved! if I didn't run my own stuff that's what me and god would run! Lemme build you a Rom tomorrow to test.
And we can see if it works better for your needs. Or I could get you some different modules to test
Well do share!
Sent from my EVO using Tapatalk 2
I'm going to try build #9 with a different toolchain tomorrow probably linaro and compress the ramdisk and zimage a little more
Evolutionmods said:
I'm going to try build #9 with a different toolchain tomorrow probably linaro and compress the ramdisk and zimage a little more
Click to expand...
Click to collapse
sounds good to me!! linaro is the shizz! :good:
For those that i sent a Download link to, If you dont know how to use fastboot and adb ...I will put these in a flashable zip for you. it will be built with Linaro toolchain instead of the norm. so it will be a totally different stock kernel. I will test for a bit then pass it along. since it will be stock it will be easier for me to post a thread due to the fact that i suck at github.
Evolutionmods said:
For those that i sent a Download link to, If you dont know how to use fastboot and adb ...I will put these in a flashable zip for you. it will be built with Linaro toolchain instead of the norm. so it will be a totally different stock kernel. I will test for a bit then pass it along. since it will be stock it will be easier for me to post a thread due to the fact that i suck at github.
Click to expand...
Click to collapse
Very cool, be looking foreward to it. Thanks
Sent from my Evo LTE because I threw that F***in iPhone out the window on the freeway.
Downloads can be found here
Evolutionmods said:
Downloads can be found here
Click to expand...
Click to collapse
sweet!! can u make a kernel oc to 1.7... i think 1.7 is the best because most phones can run at that with out any problems.. thanks bro!
new oc kernel is running great!! thanks bro :good:

[Tool][Linux] bptool v 2.0 - build prop updater for ROM Chefs

One thing that I have found to be very annoying is adjusting the build.prop file after making edits to the my ROM projects. Because of this I wrote a simple little script to update the build.prop to reflect changes before I build a new flashable.zip
This tool allows you to:
* rename your ROM
* change the product model /device
* update build date, build date UTC, and build incremental version
Place the file bptool in your ~/bin directory or a directory that is in your path and make sure it is executable.
Navigate to your ROM working directory system folder (ex: ~/working_directory/system) and from the terminal execute "bptool"
{
"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"
}
you can get the latest version here: https://github.com/OldSoldier/bptool
For your convenience I've attached the latest version of the script
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
oldsoldier2003 said:
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
Click to expand...
Click to collapse
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
cascio97 said:
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
Click to expand...
Click to collapse
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
oldsoldier2003 said:
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
Click to expand...
Click to collapse
It works. Sorry for not trying before leaving a comment. :crying: Thank you for your work.
updated to include the option to change productmodel / device name and fixed bug where the file was not properly updated if you run the same option more than once in a session.
v2.0 released
Cleaned up and commented code
added view prop settings option
added error handling

[TOOL] Running repo on Android!

repo for Android!
Just go to the point.
Why did i make this?
Well, i don't have any laptop, so i try to find a way, to do repo sync without any laptop, and then i move the files to my PC, and then build it!
Requirements
1. Termux App
2. Internet Connection
How to Install
Manual way
- Install some binaries
Code:
apt update
apt install python2
apt install curl
apt install git
- Setup git
Please refer to here
- Install repo
Code:
mkdir ~/bin
curl [url]http://github.com/Rendyindo/repo-installer/raw/master/repo[/url] > ~/bin
curl [url]http://github.com/Rendyindo/repo-installer/raw/master/shrepo[/url] > /data/data/com.termux/files/usr/bin/repo
chmod +x ~/bin/repo
chmod +x /data/data/com.termux/files/usr/bin/repo
- Done!
Automatic way
- Download this
- Run that script on Termux via:
Code:
./installer-android.sh
The script will automatically download all binaries needed and install it.
And you are ready to go! have fun with repo!
Here are some screenshots:
{
"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"
}
Note:
This is NOT for compiling! Through some binaries doesn't support at Termux, lol, and our phone will explode if it can
Credits:
- Fredrick Fornwall
- Google
RendyAK said:
repo for Android!
Click to expand...
Click to collapse
If we can't compile , there is no use of downloading GB's of data. [emoji14]
gopinaidu77 said:
If we can't compile , there is no use of downloading GB's if data. [emoji14]
Click to expand...
Click to collapse
You didn't get the main thing, huh?
This thing only for syncing! and you can move the files to your PC easily, this helps you when you have limited bandwith, and you find a free WiFi, but you didn't bring your PC
So, this help me much.
PS: Do not quote whole post plz.
RendyAK said:
You didn't get the main thing, huh?
This thing only for syncing! and you can move the files to your PC easily, this helps you when you have limited bandwith, and you find a free WiFi, but you didn't bring your PC
So, this help me much.
PS: Do not quote whole post plz.
Click to expand...
Click to collapse
Thanks,Edited my first post. :highfive:
Hi. My install seems correct and files seem present but repo command will not execute. I've tried from storage, storage/, and su. Any help?
Wow,, great work brother,, this fully helped me because i have problem to turn on my pc like a day for syncing,, but mobile not worry, love you sir
All links are dead. Could you re-share the project, please?

Kernel directory structure at compile time

I'm having trouble compiling this kernel for the Realme 2 Pro:
https://github.com/realme-kernel-opensource/Realme2Pro-kernel-source
Firstly, there were misc build errors based around paths and syntax used for .C and .H driver source code files, which needed to be made "standalone compilable" ala OnePlus5:
https://github.com/adin-k/oneplus5-kernel/commit/ec4ec687ba23609b9c323145c7d509262b0f025f
For example, this source file header needed changing from:
#include "pmic-voter.h"
To this:
#include <linux/pmic-voter.h>
In other words, the pmic-voter.h file was not located in the same folder as the source file - but inside the "linux" sub-folder instead.
Once the paths were corrected it then builds successfully (albeit one final outstanding error relating to the fingerprint driver).
My first question then is how on earth might paths within the kernel tree become so messed up as to require such a drastic clean up operation!? Is it deliberate or are sub-folders being moved around or perhaps special environment variables being set at compile time?
I then went inside the make menuconfig to change some default kernel settings - specifically to enable Virtualization and KVM:
{
"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"
}
The kernel then failed to compile again! The first place it falls over is building the cpu_errata.c, which can be fixed by having more paths updated within that file, but then it soon falls over again elsewhere.
I tried another Snapdragon 660 device with a similar kernel (Nokia 7 Plus) and the KVM parts compile fine. I even tried compiling the exact same kernel used by the Realme 2 Pro:
https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.78.tar.gz
Of course it compiles fine! Here's the typical steps that were taken:
export CROSS_COMPILE=/home/gilius/Desktop/tool/bin/aarch64-linux-android-
export ARCH=arm64
make O=out clean && make O=out mrproper
make O=out defconfig
make O=out menuconfig (note: here is where we enable Virtualization and KVM)
make O=out -j10
The Realme, Nokia and original kernel sources all share the same tree/directory structure - at least in terms of KVM. I don't know how the KVM modules were originally added to the official Linux Kernel (from version 3.11 onwards) because there are no instructions, but I do know from comparison that the files and directory structures are identical:
/arch/arm64/kvm/hyp
/virt/kvm/arm
/include/kvm
etc.
I then discovered that the original KVM files (perhaps finalised way back in 2014) do not depend on any particular directory structure as per what was required to fix standard OnePlus5/Realme compiles. For example, the kvm_main.c includes the following:
#include <kvm/iodev.h>
#include <linux/kvm_host.h>
#include <asm/processor.h>
But these folders (kvm/linux/asm) are located elsewhere in the kernel tree; the folder containing kvm_main.c has no such sub-folders - yet the compile still works for the Nokia kernel! And to complicate matters further, there happens to be several duplicate directories named "linux" containing different files in need of inclusion by various C and H source code files. In other words: they require files from all different linux folders scattered in all different locations - but without knowing exactly where to find them.
Therefore, the issue with enabling KVM in the Realme 2 Pro must be something to do with environment variables set during at compile time? So I'm guessing a whole of list of them (or symbolic links or some such) are set within a file somewhere to be referenced at compile time? Since all 3 kernels contain identical directory structures, how else might the Realme 2 pro kernel in particular have got messed up so that even basic parts of the kernel, such as kvm, do not compile by default? And how might this be undone and fixed?
Any help would be much appreciated.
Hi gilius2k15,
You can try this kernel source, its by Los dev SamarV121:
https://github.com/SamarV-121/android_kernel_oppo_sdm660
If you manage to compile do let us know how to
please let us know if u managed to compile it

Firmware extractor (Samsung)

{
"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"
}
  
  
  
These Badges describe various aspects of this Project.
[>] The Guide about Tool
[>>] Helping the user to extract Samsung firmware and get you Raw images according to your partiton.
[>>] Preparing the System/vendor or Super.img for building Android ROM.
[>>] To automate the entire process the user has undergone, based on the user responses to complete working with the script written by me (@neel0210 ).
[>>] It is meant to be a useful Guide, not a Spoon-Feeder (I'd say this as many times as I could) by virtue of it's Interactive Nature.
[>] What do I require
[>>] A Linux PC (with Bash shell)
[>>] Working Internet Connection
[>>] A Person of Interest (You)
[>>] Device Sources - The Stock Samsung Firmware
[>] Steps to clone and use
[>>]clone repo by hitting "git clone https://github.com/neel0210/Firmware_extractor.git" in terminal.
[>>] Then cd Firmware_extractor
[>>] Then execute it by doing ". extract" or "bash extract" and follow screen instructions.​[>] Note​[>>] if you're using this for the first time do this inside Firmware_extractor folder "bash bin/utils.sh" and make sure you put your SAMSUNG firmware file in Firmware_extractor folder else it won't detect it.​[>] Source code
Github
[>] Credits - Thanks
StackOverflow - For being my Teacher
@DAvinash97 - for helping me in everything and solving my queries on REAL-TIME.
@Astrako : for helping me in everything and keep me motivating to do new stuff.
@yespap : For getting me latest simg2img binaries
and 7z, simg2img and tree: for tool utilities.
* if I forgot to mention anyone, please do let me know by PMing me on telegram @neel0210.
#HappyExtracting
​
Reserved
This too
naice (づ ̄ ³ ̄)づ❤
PingVN said:
naice (づ ̄ ³ ̄)づ❤
Click to expand...
Click to collapse
Haha, ty ping
Amazing work as always! Cheers senpai!
awesome!
Akhil99 said:
Amazing work as always! Cheers senpai!
Click to expand...
Click to collapse
el0xren said:
awesome!
Click to expand...
Click to collapse
OMG! Can't wait to test it!
pruh af, clang kernel when sir?
Astrako said:
OMG! Can't wait to test it!
Click to expand...
Click to collapse
This is huge sirrrrrrr
xXJhunrey7870Xx said:
pruh af, clang kernel when sir?
Click to expand...
Click to collapse
Already released sir
bro its only unpack possible to repack no matter custom rom or back odin file
it's no longer available. What happened?

Categories

Resources