Related
*** THIS IS NOT JUST ANOTHER EFFORT TO CREATE YET ANOTHER CUSTOM ROM***
Though Android is opensource, a lot of things are unknown regarding ROM development/modification. There are many custom ROMs available for Galaxy 3 (and also other phones) and lot of people are flashing them and making their phone more responsive, productive and faster; but very few people actually knew how to go about developing the ROM.
What I intend here is to find out and document correct way to build ROM for our favorite Galaxy 3, which is very popular in India.
The goal will be to develop the ROM from Android source + Drivers from stock ROM while documenting the process so that large number of people can contribute to the development.
I will shortly update the posts with what I have done.
Reserved
Can anyone help me convert system.img and userdata.img file into files flash-able by ODIN?
Thanks
Third post
Reserved for future use
Fourth post
Fourth post.. reserved
Fifth post
Reserved 5th post goes here...
looking forward to what you come up with
Making one aint difficult keeping it bug free might get sometimes
Thanks rudolf895
I have experience in Android SDK and NDK development, but I am a noob when it comes to ROM development. Thats why this effort.
I have fetched android source using repo as well as I have also downloaded source for I5801 from Samsung open source website. After this I will look into extracting drivers from stock ROM and successfully compiling it for Galaxy 3.
rudolf895 said:
looking forward to what you come up with
Making one aint difficult keeping it bug free might get sometimes
Click to expand...
Click to collapse
abhijeet.pathak said:
thanks rudolf895
i have experience in android sdk and ndk development, but i am a noob when it comes to rom development. Thats why this effort.
I have fetched android source using repo as well as i have also downloaded source for i5801 from samsung open source website. After this i will look into extracting drivers from stock rom and successfully compiling it for galaxy 3.
Click to expand...
Click to collapse
best of luck
Looking forward to it!
abhijeet.pathak said:
Thanks rudolf895
I have experience in Android SDK and NDK development, but I am a noob when it comes to ROM development. Thats why this effort.
I have fetched android source using repo as well as I have also downloaded source for I5801 from Samsung open source website. After this I will look into extracting drivers from stock ROM and successfully compiling it for Galaxy 3.
Click to expand...
Click to collapse
Do not fell shy to ask for help u need. Together we can make it better. We are with you whenever u need us.
ARMVK Dev Team
Thanks!
Thanks a lot for your support guys..
arunmcops said:
Do not fell shy to ask for help u need. Together we can make it better. We are with you whenever u need us.
ARMVK Dev Team
Click to expand...
Click to collapse
hehe, cant wait to see what you come up with, sounds promissing btw... i am also willing to help whereever i can, whereas this wont be too much in this case i guess.
good luck and thanx...
TY ..!
Thanx alot
This would be really helpful to alot of members here
interesting ! waiting ....
I applaud your thread, I myself was thinking about such a concept.
I wanna help, but I cant do that much (basic knowledge of C and basic/little knowledge of linux and adb).
I think first there should be a list of basic stuff. Like compiling the sources, extracting factoryrfs and co from your phone etc... Sometimes if you wanna start doing something and you dont know the basics you get scared off because of their apparent tremendous lack of knowledge.
I'd probably start dabbling if somebody told me how to compile the sources.
can you also specify your work environment, toolchain and such stuff, so anyone can start from zero? there is a kernel building vm image with all tools by sztupy somewhere on the forum that is eventually of interest, and there is also an extended version containing eclipse and some more tools for full android development:
http://forum.xda-developers.com/showthread.php?t=882010
hope this helps somebody...
Did you try using it? I think the scripts are specific and cant be used by us (without altercation)
no, i have absolutely no idea of kernel compilation and all that advanced stuff, but i guess it can be adapted for our use
Yup...me too in waitin line...Now i can say i dint made a mistake by buying it...
Sent from my GT-I5801 using XDA App
abhijeet.pathak said:
Can anyone help me convert system.img and userdata.img file into files flash-able by ODIN?
Thanks
Click to expand...
Click to collapse
maybe you can create a ".tar" package including all those files.. .tar is flashable in odin..
Hi All.
I am Abhisek and I am trying to build CyanogenMod from source for our Micromax A70.
Micromax A70 is quite popular in India as a budget phone, but this device is stuck with Froyo. No more updates from Micromax as well as no kernel source from Micromax. So I am trying to build CyanogenMod from source for Micromax A70.
I am choosing CyanogenMod over AOSP as CyanogenMod supports more devices and have many patches over AOSP. So building CyanogenMod will be easier than AOSP. If successful, I will port a Oxygen/AOSP build.
I was about to give up hope until I found out how to enable ADB on Micromax A70. So I have successfully enabled ADB & obtained the system dumps. Now I can start on this project.
Current Status:
1. ADB is working perfectly.
2. System dump obtained.
3. Hardware info obtained.
4. Firmwares obtained.
5. CyanogenMod sources download in progress.
6. Currently creating the device & vendor folders.
I will keep the progress updated here. Lets hope for best.
P.S. Mods if this thread is inappropriate or in wrong forum, please do the needful. Couldn't find a better place to post this.
Reserved for future use
Reserved for future changelogs
I will provide the adb tutorial in case anyone is interested ( that is how I got the system dump ). All credits go to mastermind1024 of androidforums.com. It's not my work, so if you have to thank, thank him. He is the one did all the adb working stuff. You can read the original post Here.
Update:
mastermind1024 is here on XDA. You can see the tutorial Here.
For me, I have to manually run /sbin/adbd from Android terminal emulator to get a working adb connection. You also have to give permission for adbd in SuperUser. FYI I use ubuntu.
If you need the boot.img & recovery.img You can follow the tutorial Here
abhis3k said:
Hi All.
I am Abhisek Mukherjee and I am trying to build CyanogenMod from source for our Micromax A70.
Micromax A70 is quite popular in India as a budget phone, but this device is stuck with Froyo. No more updates from Micromax as well as no kernel source from Micromax. So I am trying to build CyanogenMod from source for Micromax A70.
I am choosing CyanogenMod over AOSP as CyanogenMod supports more devices and have many patches over AOSP. So building CyanogenMod will be easier than AOSP. If successful, I will port a Oxygen/AOSP build.
I was about to give up hope until I found out how to enable ADB on Micromax A70. So I have successfully enabled ADB & obtained the system dumps. Now I can start on this project.
Current Status:
1. ADB is working perfectly.
2. System dump obtained.
3. Hardware info obtained.
4. Firmwares obtained.
5. CyanogenMod sources download in progress.
6. Currently creating the device & vendor folders.
I will keep the progress updated here. Lets hope for best.
P.S. Mods if this thread is inappropriate or in wrong forum, please do the needful. Couldn't find a better place to post this.
Click to expand...
Click to collapse
you mean this rom is under development? I don't have a70 just asking. And you are on right place. Also microsoft needed to open kernel source.
cips gokhle said:
you mean this rom is under development? I don't have a70 just asking. And you are on right place. Also microsoft needed to open kernel source.
Click to expand...
Click to collapse
You meant Micromax right
Yes the ROM is under development. The repo sync is taking forever. I have a pathetic BSNL BB Connection here.
abhis3k said:
You meant Micromax right
Yes the ROM is under development. The repo sync is taking forever. I have a pathetic BSNL BB Connection here.
Click to expand...
Click to collapse
sorry yes i mean micromax. and best for your rom. i think it's first 2.3 a70 rom?
Good!
How much % is the sync complete?
Moreover who are u on androidforums?
varun.chitre15 said:
Good!
How much % is the sync complete?
Moreover who are u on androidforums?
Click to expand...
Click to collapse
I have same userid abhis3k. Sync seems to be complete at 70%, I can only see the directory size, Fetching projects is showing 89%
cips gokhle said:
sorry yes i mean micromax. and best for your rom. i think it's first 2.3 a70 rom?
Click to expand...
Click to collapse
Yes AFAIK if I succeed, this will first GB ROM for A70.
------------ edit -------------
I have tried to run ADB with root permissions. It works, but somehow adb remout does not work.
P.S.: I found the problem, the system was already r/w.
I would say NO bcoz i m from a secret team and we had ported GB to A70 and touch doesn't work in any of the Ports
Moreover u will wonder that touch doesn't work in Android 1.5,1.6 which i had ported from HTC G1 also it doesn't work in 2.1 which i ported from Micromax A60
So we need to build ROM from source which u r doing. Moreover that is not enough because as soon as sync completes then we need to enable touch drivers in BoardConfig.mk
varun.chitre15 said:
I would say NO bcoz i m from a secret team and we had ported GB to A70 and touch doesn't work in any of the Ports
Moreover u will wonder that touch doesn't work in Android 1.5,1.6 which i had ported from HTC G1 also it doesn't work in 2.1 which i ported from Micromax A60
So we need to build ROM from source which u r doing. Moreover that is not enough because as soon as sync completes then we need to enable touch drivers in BoardConfig.mk
Click to expand...
Click to collapse
Great!! I had no idea A70 had a GB port. If you can share the details It would be easier to compile for A70.
abhis3k said:
Great!! I had no idea A70 had a GB port. If you can share the details It would be easier to compile for A70.
Click to expand...
Click to collapse
I think akshay is uploading that port now.he has made a thread n uploading right now.i dont know if it's the same that varun is talking abt but mostly it is.
http://forum.xda-developers.com/showthread.php?t=1540104
mastermind1024 said:
I think akshay is uploading that port now.he has made a thread n uploading right now.i dont know if it's the same that varun is talking abt but mostly it is.
http://forum.xda-developers.com/showthread.php?t=1540104
Click to expand...
Click to collapse
Sure I will check it out. It will speed up the development.
--------- edit ------------
This seems like a binary port using kitchen. Right?
Binary port?
Its ported using kitchen which involves replacement of kernel.
And when sync completes, inform us here,a we will make two roms.
One with unchanged boardconfig.mk and second with modded boardconfig.mk
Sent from my Micromax_A70 using Tapatalk
Replacement of kernel includes replacing binary files including so ko and firmware files. Which are all binary. Only recompile includes a output which is not binary replacement.
Download is still at 93%. I will come back when its finished.
Sent from my LG-P500 using XDA
I am also at 91% since a week..i am getting fatal errors on sync now n then..project downloads upto abt 86%(abt 650mb) n then I get error...i had to do all again..still no luck.i wish i can finish it tonight.we (me,varun,akshay) eager to lunch rom from cm source as we have hope that changing boardconfig will give us working touch.let's see.
extract-files.sh
I have completed sync & also made extract-files.sh
I want others to examine & complete it if I have missed something.
mastermind1024 said:
I have completed sync & also made extract-files.sh
I want others to examine & complete it if I have missed something.
Click to expand...
Click to collapse
@mastermind I have checked the file. Seems so good so far. I hope my sync will also complete by tonight. I am going crazy with these BSNL broadband problems
Have you started the build? Let me know the boardconfig.
mastermind1024 said:
I have completed sync & also made extract-files.sh
I want others to examine & complete it if I have missed something.
Click to expand...
Click to collapse
the script doesnt have adb pull for the binary akmd2.without which sensors wont work .
and in a70 there is also a file called Focal touch.kcm and this is used by the kernel at boot i checked in dmesg .
so add this two files two ..
akmd2
focaltouch.kcm [from usr/keychars]
First post in the Dev section but this seemed to be the place to talk about kernel compilation and module development.
I have twice now, and am working on my third kernel compilation for the purposes of custom module building for the TF700 and the TF201.
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all. Is this normal for kernel compilations? I would have thought that it would be fully compilable out of the box ( so to speak). Is it ASUS or just android/Linux in general that works out this way?
Is there a better way to do it? Should I use some generic source with the same version numbers? The current source is just not working at all. I am using an Ubuntu distro. Have the cross compile tools etc... but it just fails. I have already resolved two missing definition references and it just keeps on failing in new places
Hopefully this question doesn't offend developers. I have moved from WinPhone to here and want to better my understanding of how this should all work but need to start with some basics before I can make a meaningful contribution.
Thanks.
P.S... I looked and didn't find a "Compiling android kernels for dummies" book
hx4700 Killer said:
I looked and didn't find a "Compiling android kernels for dummies" book
Click to expand...
Click to collapse
"Dummies" doesn't write a book on kernel dev. Too wrapped up in telling people how to download iTunes.....
Use your "Google". And when you find it, Google XDA University.
There, you will find steps for setting a build environment and kernel and cross arm.
Understand, all kernels are different, but a good place to start. Plus, you learn how to use Google. An added bonus.
Oh... and... as an extra bonus, I will move this to Q & A, as this post has no development work attached. :silly:
MD
My question wasn't HOW to cross compile. I have done it.
My question is WHY are there so many errors that need correcting when compiling the ASUS downloadable kernels and if this is typical of the source from any device or just ASUS?
hx4700 Killer said:
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all.
Click to expand...
Click to collapse
I had to fix exactly one pair of quotes vs. angle brackets somewhere in the RIL - get the patch pack from my kernel and apply the ril include fix. Then it should compile. If not, you are doing something wrong.
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
alexcass4 said:
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
Click to expand...
Click to collapse
Step 1: Get a suitable ARM toolchain. I can't help you here with Ubuntu because I'm using Gentoo and their crossdev tool (http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1).
Step 2: Cross-compiling the kernel works just as for native kernels (make menuconfig, make), but you have to pass parameters to each make, e.g. make ARCH="arm" CROSS_COMPILE="arm-gentoo-linux-gnueabi-" (or whatever your toolchain is called)
Step 3: For the TF700-specific blob stuff I have written a detailed tutorial here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
Dear all Dev
I am a noob. but i want to learn.
I want create a ROM for myself, and like me there must be many user with the same desire of building there own ROM but the problem is lack of information.
I tried many guides but want's successful.
So i request all the Devs to create a Tutorial for porting different ROM to our device, this tutorial should be device specific and OS specific.
There are many Dev who could contribute to this like
@SuperDroid-BOND, @ibshar, @sagarwep could contribute in guiding the rom porting from MTK6589 device to MTK6577 device.
@mufti.arfan, @anand_mmx could highlight on porting Lewa ROMs
@Akhilendra Gadde, @Ak****banta on porting Miui ROMs
@Dark4Droid, @khan_frd2002, @jigarmpattani, @dhiarya, @bsuhas and other great dev could help also in their respective field of specialization.
This would be the greatest contribution for our section if we could create a thread like this.
This just a thought and a request.......
Using windows is advised as you need to download a program called notepad++ on it. But you can use Ubuntu too.
First of all, make sure that you have two rom.zips that are
Base
The rom that was originally developed for our canvas 2 . Basically cm roms
Port
The rom that you want to run on our phone. That is developed for other phones. The android version of base and port roms have to be same.
Must have
Notepad++, base rom, port rom
Step 1
After you're done downloading both base and port roms, extract them into two different files and rename them as base and port.
Step 2
Open system folder in the base rom folder and delete
App
Fonts
Framework
Media
Open system folder in the port rom folder and copy
App
Fonts
Framework
Media
Then paste the copied files into system folder of base
Step 3
Open system-etc-permissions in both port and base folders. Delete every permission in base EXCEPT platform and handheld_hardware.
Copy all permission except platform and handheld_hardware and paste the copied files into the permission folder of base rom.
Step 3b (if there is an tweaks in port rom)
Go into system-etc-init.d in both port and base rom folders.
Copy everything from init.d in port EXCEPT banner and paste them into init.d in base
Step 4
Go to META-INF-com-google-android and open updater script using notepad++
(In both port rom and base rom folders)
Delete all the lines that has set perm or setperm recursive in base rom updater script
Copy all the lines that have setperm or setperm recursive in port rom updater script. Paste the copied lines into base rom updater script, where the original setperm lines of base rom was.
Step 5
Save the updater script and zip the contents of base rom.
Step 6
Flash and test
If Rom is having a bootloop then go into lib folder of port Rom and copy these files
Libandroid_runtime.so
Libandroid_servers.so
Libandriod_driod.so
BEST OF LUCK (Y) :good:
dhiarya said:
Using windows is advised as you need to download a program called notepad++ on it. But you can use Ubuntu too.
BEST OF LUCK (Y) :good:
Click to expand...
Click to collapse
Thanks for the info, but i want devs to develop a device specific Tutorial / guide.
I tried the procedures to port ColorOS ROM from A116 to our device but stuck on boot. i dont known which files do i need to edit to get it boot.
Porting is basically very much same for most of the devices,and there are many threads for that ...
[GUIDE] Porting Guide - How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs
This one is most basic and easy.
[GUIDE]How To Port Different ROMS to Your Device (Simplest and Fastest)
If I can make a guide for LeWa , I surely would.
:good:
subhashdas said:
Dear all Dev
I am a noob. but i want to learn.
I want create a ROM for myself, and like me there must be many user with the same desire of building there own ROM but the problem is lack of information.
I tried many guides but want's successful.
So i request all the Devs to create a Tutorial for porting different ROM to our device, this tutorial should be device specific and OS specific.
There are many Dev who could contribute to this like
@SuperDroid-BOND, @ibshar, @sagarwep could contribute in guiding the rom porting from MTK6589 device to MTK6577 device.
@mufti.arfan, @anand_mmx could highlight on porting Lewa ROMs
@Akhilendra Gadde, @Ak****banta on porting Miui ROMs
@Dark4Droid, @khan_frd2002, @jigarmpattani, @dhiarya, @bsuhas and other great dev could help also in their respective field of specialization.
This would be the greatest contribution for our section if we could create a thread like this.
This just a thought and a request.......
Click to expand...
Click to collapse
+1
I like this idea. This is a great idea. There should be a nice guide which describes the steps, methods, exceptions etc. that are involved in ROM porting.
Maybe a more MTK oriented guide since there are already many generalized porting guides. A guide that acknowledges do's and don'ts, a guide that informs what we can and can't do.
However, this guide should also, preferably, detail on the "why's" and the "why not's" and not just provide a copy-paste tutorial seen in profound quantities throughout xda...
Now, this is a theoretical idea and not possibly/necessarily a one-man job. Therefore, the devs could perhaps collaborate on this hypothetical guide also giving their personal experiences on android development (tips, tricks, pointers, notes and stuff).
How about a guide on porting mtk 6589 Rom to mtk 6577..
Sent from my A110 using XDA Premium 4 mobile app
subhashdas said:
Thanks for the info, but i want devs to develop a device specific Tutorial / guide.
I tried the procedures to port ColorOS ROM from A116 to our device but stuck on boot. i dont known which files do i need to edit to get it boot.
Click to expand...
Click to collapse
All Guide are Some How Same Bro.... You can port MT6589 AOSP easily but other one like color os, sony etc are hard you can only port it by debugging...
I am trying to port A110Q Rom to canvas 2 but I don't have the cwm flashable zip .All I have I'd the sp flashable Rom . I know how to extract the Rom from it . But how do I make the meta inf folder that had the updater script .
Sent from my A110 using XDA Premium 4 mobile app
Matthew_Farrell said:
I am trying to port A110Q Rom to canvas 2 but I don't have the cwm flashable zip .All I have I'd the sp flashable Rom . I know how to extract the Rom from it . But how do I make the meta inf folder that had the updater script .
Sent from my A110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
use any custom rom meta folder of same version
Very Helpful
Thank u .. very helpful guides
Guide to Mediatek Building(Guide 2:=boot.img)
A common misconception on XDA is that mediatek devices have boot.img similar to qualcomm.. I'll try to explain why it isn't and how to make one.
Mediatek appends a header to its Ramdisk(initramfs) and its kernel so that the board can figure out that its a ramdisk/kernel. Without these headers the boot.img you build will won't work; If you've been getting bad results when making a boot.img this could be one of the reasons
Requisite
Any Linux based system
the mkimage i've attached in the post
Adding the MediaTek header
A executable named the 'mkimage' is needed for this(attached in post). If you're one of the kernel devs or for the ones who have the mediatek kernel source, this file is present in the kernel_source/mediatek/build/tools/mkimage.
What does it do?
it appends the mediatek header to the first 512 bytes of your ramdisk/kernel
Adding the meditek header
For the kernel,
Code:
mkimage kernel KERNEL > kernel_with_meditek_header
For the ramdisk,
Code:
mkbootfs ./root/ | minigzip >ramdisk.gz
mkimage ramdisk.gz ROOTFS > ramdisk.img
Removing the MediaTek header
If you want to remove header from kernel,
Code:
dd if=kernel of=kernel_without_header bs=1 skip=512
If you want to remove header from ramdisk
Code:
dd if=ramdisk of=ramdisk_without_header bs=1 skip=512
the bs tells dd how many bytes to read and write at a time.
the skip tells it that how many bytes to skip at start. here its 512 since the mediatek header occupies 512bytes. we can use count if you want
Here's how you manually pack boot.img after adding headers
Code:
mkbootimg --kernel zImage_with_header --ramdisk ramdisk_with_header.img -o new_boot.img
You can now use this boot.img to flash to your phone
Modules!!
Modules are very important, Read previous guide(Building kernel) about how to build modules(Guide attached to signature). Modules are very kernel specific and the rom wont boot if you don't push these modules to the /system/lib/modules replacing the ones currently there.
Extra Information!
to delete parts of file from the end of file which is 100 bytes. for example:
Code:
dd if=file of=file1 bs=1 skip=10 count=85
/*count=filesize-startsskip-endskip*/
here,count=100-10-5=85.
Hope this guide helped you.
All questions are welcome in the thread
Regards and Good luck
Links to my next Guides
Building the ROM{MediaTek}
Building the Kernel{MediaTek}
Nice guide
... but that was already explained on this thread
The thread was for the MT6577, but concerning this issue (and others) its also valid for the other's MT65xx ; MT81xx ; MT83xx SoC's.
Also this thread is the best resource on @xda concerning Mediatek kernel / issues , etc.
But this should help, the users that are new on the "Mediatek" Platform.
Regards
superdragonpt said:
Nice guide
... but that was already explained on this thread
The thread was for the MT6577, but concerning this issue (and others) its also valid for the other's MT65xx ; MT81xx ; MT83xx SoC's.
Also this thread is the best resource on @xda concerning Mediatek kernel / issues , etc.
But this should help, the users that are new on the "Mediatek" Platform.
Regards
Click to expand...
Click to collapse
I'm making a guide for building an rom from source step by step for the new developers. I've started off with the boot.img. Not sure if that's the way to go, but I'll try my best to make people understand the build process and how mediatek works
Sent from my Moto G using XDA Free mobile app
MasterAwesome said:
I'm making a guide for building an rom from source step by step for the new developers. I've started off with the boot.img. Not sure if that's the way to go, but I'll try my best to make people understand the build process and how mediatek works
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Your more than welcome we are only an few working with Mediatek's.
We all know how MTK works, and their Closed Source / Anti-GPL Atittude...
Best Regards
superdragonpt said:
Your more than welcome we are only an few working with Mediatek's.
We all know how MTK works, and their Closed Source / Anti-GPL Atittude...
Best Regards
Click to expand...
Click to collapse
My aim is to increase that number
Sent from my Moto G using XDA Free mobile app
W0W its good to see more Devs started to work for MTK devices ^_^ nice guide
EnerJon said:
W0W its good to see more Devs started to work for MTK devices ^_^ nice guide
Click to expand...
Click to collapse
You're quite welcome :laugh:
Kernel Development guide coming today
MasterAwesome said:
Kernel Development guide coming today
Click to expand...
Click to collapse
i am kind of porter and developer of a110 aka micromax canvas 2 community.....
i would love to learn about making kernal and mediatek code....
waiting for it.....
thanks in advance..:laugh:
Avenger4droid said:
i am kind of porter and developer of a110 aka micromax canvas 2 community.....
i would love to learn about making kernal and mediatek code....
waiting for it.....
thanks in advance..:laugh:
Click to expand...
Click to collapse
I've added the links to my signature. Be sure to check it out
MasterAwesome said:
I've added the links to my signature. Be sure to check it out
Click to expand...
Click to collapse
thank you...Checking....
Suggestions for new guides are welcome and I'll try my best to do them.
Sent from my Moto G using XDA Free mobile app
Nice tutorial but still not clear for me. So i have built zImage, and then what? I need to use mkimage on zImage I have to produce boot.img, then push boot.img to my device?
giaur said:
Nice tutorial but still not clear for me. So i have built zImage, and then what? I need to use mkimage on zImage I have to produce boot.img, then push boot.img to my device?
Click to expand...
Click to collapse
yes you apply mkimage on the zImage and ramdisk The we mkbootimg for converting it into a boot.img and then you push to device.
MasterAwesome
Sent from my Moto G
Should I add mediatek headers to zImage and ramdisk and then pack them into boot.img?
giaur said:
Should I add mediatek headers to zImage and ramdisk and then pack them into boot.img?
Click to expand...
Click to collapse
Yes use
Code:
mkbootimg - -kernel zImage - -ramdisk ramdisk.img -o boot.img
Sent from my Moto G
Thanks, I think now it's clear. I think it would be useful for newbies if you also add this to first post. Also - don't I need any modules (.ko) also to push to device?
giaur said:
Thanks, I think now it's clear. I think it would be useful for newbies if you also add this to first post. Also - don't I need any modules (.ko) also to push to device?
Click to expand...
Click to collapse
Yes, you need to push the modules to your phones since they are kernel specific. To reduce size strip them off of unneeded assembler messages.
Regards
MasterAwesome
Sent from my Moto G
More information about pushing boot.img to phone and important stuff added to first post
Regards
MasterAwesome
WOW! good guide, I only have one problem, if I have a premade boot.img and I want to change the kernel, how do I do that? Thanks for this guide