hi .. I would like to integrate a driver for a camera in a uboot.bin, what can you do?
I'll explain:
N7000+ has Android 4.0 anche chipset mediateck 6577
latest versions are 4.1,1 but it 's changed the camera ...
if I upgrade everything works except the camera,,,,
the uboot.bin of 4.1.1 does not have the drivers for the old camera....
how can I remove them from the old uboot.bin and put back in new uboot.bin?
i have found script for unpacking boot and recovery... but no for uboot.bin
thanks a lot
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 !
Porting guide Credits to Dragos Andrei . facebook post credit to IACOB IONUT
You can port from MTK to MSM or from MSM to MTK
For LP :
MSM : Kernel - 3.10.54 to MTK : Kernel - 3.10.65
For MM
MSM : Kernel - 3.10.48 to MTK : Kernel - 3.18.19
First part Boot.Img
1.Replace kernel from stock to port
2.From init.rd all files need compared-named need to be same from stock bootimg and use your brain to change Mount points in init.rc(also init.qcom.rc)
3.Compare all and need to have some knowledge for this.No noobs or beginners.
Second part System
1.Apps.only if is something from mtk or snapdragon replace and delete all which is not for your chipset
2.Bin folder.Delete and replace with Stock.This is need because is different from mtk or snapdragon
3.Etc folder.Delete Firmware Wifi Bluetooth all folders which is like from aosp(for example amigo ui use special folders to boot their rom).Files for custom os need to be not changed.only which is for your soc.
4.Framework.For Snapdragon delete all which begin with mediatek-..... and replace from stock with qc... or qcom... and compare all which is from stock with port.Also fromm framework replace from framework-res.apk(res/xml)-storage.xml
5.All mtk...libs deleted and replace all which have same name in lib...so All which is not for porting os from port need to be deleted and not replaced from stock.(can cause bootloop)
6.Usr.Delete and replace this folder with stock.
7.Vendor.Nothing not need to be changed.Only lib need to be compared and changed if is needed.
8.Rfs.Delete and replace from stock
9.Build.prop.Change especially for your chipset
Final part.Meta Inf
Change only mount points.
For final you need to have some knowledge about all files from your socs......Also a second porting guide will be released for noobers.
Second porting guide
1.From stock delete only app priv-app media fonts tts build prop and framework(move to another dir)
2.Replace from port folders but framework delete mediatek or qc files but copy from
stock missing files and delete files which is in plus.
3.Lib.Delete qc or mtk and replace all which is desired from stock.
4.And all folders like from three step.
This guide is desired for devs which have some experience for porting.Also is not a officially guide can be unstable and not work but need to be tried.For mine worked to port amigo ui from mtk to msm & color os
Credit : DragosAndrei , IACOB IONUT
@jashiovan
first of all i thought it was impossible !
thanks man for hope and tutorial <3
but i want to ask what about nougat kernel ?
am on redmi note 4 SD MIUI 8 N
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
Hello All
I need to build AOSP for AMLogic s905x board (It's a android TV box, based on ARM Cortex A53)
i tried to compiled the AOSP build and it successfully build but at end we have no experience with generating combined img file ....
we want to flash generated cache.img, ramdisk.img, userdata.img, vendor.img to box , but do not know how to flash .. please halp me for this
try make install or make update (depending on your aosp make files)
flash using fastboot