hello, try to compile cm kk, on a Chinese tablet, the vendor doesnt give the sources, and I will have to create my own device, the main board is a k8028-v4 sun7i, I will not change the kernel, but I need to create mk's files , Where I can find how to do it?, I have the partitions, i extracted the boot.img from thetablet with dd, I extracted /system whit push, I have the build.prop from the tablet, information processor a20, I have a generic kernel suni7 3.3, compatible with stock, but when I build, I havent support for my tablet, so how I can create the device and vendor to compile, i must create mk files, but cannt find a detailed guide to do it, it's like port a new device, help
Tablet is a TechPad C981, sun7i allwinner a20 mp3 mali-400 gpu
a7 cortex 1Ghz dualcore cpu, vpu cedarx simd neon, hdmi cec
k8028-v4 mainboard. Extracted / system boot.img
when execute mkvendor.sh TechPad C981 ~ / boot.img in cm11
I do not work, only if I run mkvendor.sh techpadc981 ~ / boot.img
and creates the directories linux
as the device port
step by step guide
Olintonatiuh said:
hello, try to compile cm kk, on a Chinese tablet, the vendor doesnt give the sources, and I will have to create my own device, the main board is a k8028-v4 sun7i, I will not change the kernel, but I need to create mk's files , Where I can find how to do it?, I have the partitions, i extracted the boot.img from thetablet with dd, I extracted /system whit push, I have the build.prop from the tablet, information processor a20, I have a generic kernel suni7 3.3, compatible with stock, but when I build, I havent support for my tablet, so how I can create the device and vendor to compile, i must create mk files, but cannt find a detailed guide to do it, it's like port a new device, help
Tablet is a TechPad C981, sun7i allwinner a20 mp3 mali-400 gpu
a7 cortex 1Ghz dualcore cpu, vpu cedarx simd neon, hdmi cec
k8028-v4 mainboard. Extracted / system boot.img
when execute mkvendor.sh TechPad C981 ~ / boot.img in cm11
I do not work, only if I run mkvendor.sh techpadc981 ~ / boot.img
and creates the directories linux
as the device port
step by step guide
Click to expand...
Click to collapse
I see that you have already asked this in Cgef Central forum (http://forum.xda-developers.com/chef-central/android/help-help-compile-kernel-make-manifest-t2894423).
That's a good place to ask IMO.
You can find some general guides for porting CM ROM here:
1. Android Development and Hacking > Android Software Development > [GUIDE]How to port roms to your Device
2. Android Development and Hacking > Android Software Development > [GUIDE] How To Port Different Roms to Your Device - For CM, AOSP & AOKP
And there are some instructions on the CM website itself.
Maybe that can help you to port CM for your device.
Thread closed and thank you !
Hello all,
Well, I just start to compile a kernel source for my Homtom HT17 (I need UVC support).
I found a source code (google HT17 kernel git)
and I compile it with success (I hope) on arm architecture (if I am not wrong, actual rom didn't use aarch64 even if the mt6737M is 64 bits)
So I have a zimage and try to flash it.
So I try to use kitchen and I am able to get to things : a new zip update that I made from a boot.img/system.img from a stock rom and I try to flash it with twrp but I had an error message (something wrong with META-INF\com\google\android\update-script)
Then I try to flash only the boot.img I made with the zimage with twrp. The phone loop at boot... (I restore it with mt flash tool and the rom I had)..
So I am very frustrated, 'cause I spent a lot of time to be able to compile the kernel...
I search a lot on Internet how to deploy correctly my kernel zimage but as now I am not able to get it running!
The problem is like I am newbies in kernel build, I dont know if my process is incorrect or my kernel is incorrect.
So finally I search somebody who could give me steps to deploy correctly my zimage on my phone...
(HOMTOM HT17 MT6737 chip)
Thanks for your reading.
Emmanuel,
Aix En Provence, France
Greeting,
Thank you for using XDA-Assist, you might get more help by others expert in here Homtom HT17-MT6737
XDA-Assist-Team
Hello , I have a problem, I can not unpack the .img files, the roms are the original ones and the 4.2.2, I need to unpack to change parameters, the model is unknown and an allwinner a13, the board and 706-a13 -v1.0, I do not know the brand represented by the logo.
The original rom
drivers.multilaser.com.br/comex/NB083-ISO-05112013_v1.rar
The modified rom
4shared.com/rar/1KPlj3fXba/ROOM422allwiner_a13_.html?cau2=0322&ua=WINDOWS
hey guys, im new to porting new kernels to my phone
i flashed kali nethunter on my MTK device but when i try to flash the kernel it fails when it comes to decompressing boot.img and it show this error (Unpacking boot image failed) using this command :
"$bin/bootimg" xvf boot.img "$split_img"
i tried to flash this kernel in both stock and custom rom but the same error appears
i think nethunter kernel installer isn't made for MTK devices because when i decompressed boot.img it listed files that's not present in the installer like this one (boot.img-ramdisk) it only shows compressed (kernel.gz) and (ramdisk.gz) and (cpiolist) and (bootinfo) and (initrd) folder.
i saw some going modifies boot.img to make a flashable compatible kernel of nethunter depending on given boot.img so
pleaaaaaase guys help me in this situation im really excited to test my alfa in kali nethunter :crying: :crying: :crying:
my phone:
Gionee M5 Lite
kernel version: 3.18.19
rom: lineage os 14.1
nethunter generic-arm64-kalifs-full-rolling-2017.11-18-1618
boot.img:
htt ps: // drive.goo gle. com /file/d/1FN5ogaRRboCKS2ap2_dzYpLdxenJjbse/view?usp=sharing
Before I start, here's what I have and what I don't have:
What I have:
BLU R1 PLUS
BLU R1 PLUS Kernel Source
A possible port device (An Intex Infie 3, to use the vendor from)
Experience with the linux command line
What I DO NOT have:
A kernel source for the Intex Infie 3
Now for the explaination:
I found several ARM64 devices and vendors, however the kernel source for my device is ARMv7 (even though the SoC is ARMv8).
I soon learnt that trying to build an ARM64 kernel would be a waste of time, so I decided to go searching for the needle in a haystack (which of course was another device, with android Oreo and an ARM kernel+vendor) I eventually found this Intex Infie device which I noticed did not have any arm64-related prop lines and ONLY had the zygote32 in boot.img
However I then discovered that even if the vendor would work, Marshmallow drivers in the stock kernel for the BLU R1 Plus will cause issues to boot any GSI because of the many changes between android versions AND I need "Binderised HALs"
I intend to use my cache partition as the vendor partition (which of course, I'll have to add early mount to the DTB in the kernel for)
I struggle with kernel editing and compiling as this is my first shot at developing for an unknown or unpopular device.
What I'm asking for:
I'm not asking for it to be done for me, but rather a hand that can point me in the right direction that would at least allow me to boot a GSI.