Hi,
I've followed various posts on here and have managed to compile and install my own kernel build. I am using the leshak initramfs and would like to be able to modify the init executable that lives in the sbin folder.
I've had a search around and can't work out if there is any source code available to build this or if it just pulled directly from the device. Can anyone confirm if and how it is possible to build this executable?
Thanks in advance,
Jamie
Theres no source from Samsung available.
You can try official android sources:
http://android.git.kernel.org/?p=pl...dc717ed167482c09f342730f1c1f64b90d19c;hb=HEAD
I have AOKP on my s3 AT&T and like the blackberry 10 lockscreen, which is HERE
Can anyone tell me how to instal patches on my phone ? Do I need to instal linux on my windows pc ? do I need to add some code on my phone ? if yes, how ?
Do I need complete source code of s3 ? if yes, where can I get it and what to do with source code ?
I am new and want to learn if anyone can guide me ?
http://forum.xda-developers.com/showthread.php?t=1748297
CZ Eddie said:
http://forum.xda-developers.com/showthread.php?t=1748297
Click to expand...
Click to collapse
So this is where I will install patches - from original source code ? I can't install patches by opening system files from my phone and adding custom code or lines there ?
So adding any kind of patched (for example what I mentioned above) what I will need to do ?
1- download the source code and add patch there ? if yes then how come I will be able to keep the custom rom if I download the source code of factory version of my phone and then add patch ? then the result will be factory android version + that patch = no custom rom
OR
2- Add code on the custom ROM that I have on my phone - AOKP ? if yes, how to do that ? how to instal patch on my current custom ROM ?
anyone ?
iamsuper123 said:
anyone ?
Click to expand...
Click to collapse
Refer to this: http://forum.xda-developers.com/showpost.php?p=32423965&postcount=16
As it is ROM specific, you have to compile it yourself on the ROM you're using. There are plenty of guides on how to do it, just search around.
I would like to explain this a little bit:
What is kexec?
It is a function which allows you to boot an alternative kernel without needing to flash it or using `fastboot boot`. I am not going to write a thousand words to explain this, so if you want more info, search it yourself.
What is kexec hardboot?
It does the same as what kexec aims to do, but instead of booting another kernel directly, it reboots the device before doing so so that the hardware can be reinitialized by the bootloader. Normal kexec boots the kernel with the hardware in an unclean state, which is not very healthy. Kexec hardboot is somehow healthier.
I know I am not explaining very well, so please refer to the original thread by @Tasssadar
So what is this post about?
At this moment, there aren't any non-stock ROM, CAF or CM kernel isn't ported yet, so this is pretty useless actually.
In the future, if there are any custom ROMs, this will come in handy because it will allow "installing" multiple ROMs without having to flash them to the device memory.
Basically, this is just to prepare for the future.
Who should be reading this?
Well, developers who can properly compile a kernel.
Patches:
Kernel patch: https://gist.github.com/alvinhochun/7945428
Or, if you cloned my github stock kernel tree, check this: https://github.com/alvinhochun/sony-xperia-m-kernel/commit/2e818d81f21f6a627bc629e477052045426b0663
This is the kernel patch. Only the host kernel needs to be patched.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_ATAGS_PROC=y
All these options must be enabled.
Userspace kexec binary: Use the one compiled by @Tasssadar on http://forum.xda-developers.com/showthread.php?p=46223952
Usage:
I have wrote a simple shell script to automatically set the correct cmdline here:
https://gist.github.com/alvinhochun/7945270
Basically, the most important thing is to make sure the addresses are correct and the cmdline has the proper information in it.
The script requires kernel to be packed with CWM which also provides /boot/busybox. You can use this tool: http://forum.xda-developers.com/showthread.php?t=2481864
Just download the kexec binary and put it in place.
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices.
My patch is based on the one by @Tasssadar on http://forum.xda-developers.com/showthread.php?p=46223952
So, are this is like 'Live CD' for android?
Richardsentosa said:
So, are this is like 'Live CD' for android?
Click to expand...
Click to collapse
Well, that analogy can't exactly be used. It's more like the kernel acts as a bootloader that is used to boot another kernel.
alvinhochun said:
Well, that analogy can't exactly be used. It's more like the kernel acts as a bootloader that is used to boot another kernel.
Click to expand...
Click to collapse
after see N4 multiboot, i think this is a great feature.
alvinhochun said:
I would like to explain this a little bit:
What is kexec?
It is a function which allows you to boot an alternative kernel without needing to flash it or using `fastboot boot`. I am not going to write a thousand words to explain this, so if you want more info, search it yourself.
What is kexec hardboot?
It does the same as what kexec aims to do, but instead of booting another kernel directly, it reboots the device before doing so so that the hardware can be reinitialized by the bootloader. Normal kexec boots the kernel with the hardware in an unclean state, which is not very healthy. Kexec hardboot is somehow healthier.
I know I am not explaining very well, so please refer to the original thread by @Tasssadar
So what is this post about?
At this moment, there aren't any non-stock ROM, CAF or CM kernel isn't ported yet, so this is pretty useless actually.
In the future, if there are any custom ROMs, this will come in handy because it will allow "installing" multiple ROMs without having to flash them to the device memory.
Basically, this is just to prepare for the future.
Who should be reading this?
Well, developers who can properly compile a kernel.
Patches:
Kernel patch: https://gist.github.com/alvinhochun/7945428
Or, if you cloned my github stock kernel tree, check this: https://github.com/alvinhochun/sony-xperia-m-kernel/commit/2e818d81f21f6a627bc629e477052045426b0663
This is the kernel patch. Only the host kernel needs to be patched.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_ATAGS_PROC=y
All these options must be enabled.
Userspace kexec binary: Use the one compiled by @Tasssadar on http://forum.xda-developers.com/showthread.php?p=46223952
Usage:
I have wrote a simple shell script to automatically set the correct cmdline here:
https://gist.github.com/alvinhochun/7945270
Basically, the most important thing is to make sure the addresses are correct and the cmdline has the proper information in it.
The script requires kernel to be packed with CWM which also provides /boot/busybox. You can use this tool: http://forum.xda-developers.com/showthread.php?t=2481864
Just download the kexec binary and put it in place.
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices.
My patch is based on the one by @Tasssadar on http://forum.xda-developers.com/showthread.php?p=46223952
Click to expand...
Click to collapse
can we use this to boot cm10 cm11 on sony Xperia z?
nabelar82 said:
can we use this to boot cm10 cm11 on sony Xperia z?
Click to expand...
Click to collapse
I guess you are mislead this is a kernel feature and is not at all related to booting of a rom
SpinXO said:
I guess you are mislead this is a kernel feature and is not at all related to booting of a rom
Click to expand...
Click to collapse
Well I read that but I been looking the way that we can install cm11 on our xperia z with locked bootloader and this seems to help cause we can't flash boot img on locked bootloader
nabelar82 said:
Well I read that but I been looking the way that we can install cm11 on our xperia z with locked bootloader and this seems to help cause we can't flash boot img on locked bootloader
Click to expand...
Click to collapse
Not really.
But Recognized Developer @Rachit Rawat has explained how the Locked Bootloader CM is booted and I see @Olivier have worked on the same for Xperia S you can try to contact him
Explanation Link: http://forum.xda-developers.com/showthread.php?p=49073506#post49073506
nabelar82 said:
Well I read that but I been looking the way that we can install cm11 on our xperia z with locked bootloader and this seems to help cause we can't flash boot img on locked bootloader
Click to expand...
Click to collapse
Surely there is a way known as 2nd-init, with which we can change the ramdisk without changing the kernel.
Xperia SP has 3-4 ROMs booted with the same method on locked bootloader. You can search in SP forums and contact the respective persons for porting the feature.
aweosomeabhijeet said:
Surely there is a way known as 2nd-init, with which we can change the ramdisk without changing the kernel.
Xperia SP has 3-4 ROMs booted with the same method on locked bootloader. You can search in SP forums and contact the respective persons for porting the feature.
Click to expand...
Click to collapse
Well I am very interested on this patch but I am not a developer it will be very interesting if someone apply on a xperia z an we can test can someone try? I can test
aweosomeabhijeet said:
Surely there is a way known as 2nd-init, with which we can change the ramdisk without changing the kernel.
Xperia SP has 3-4 ROMs booted with the same method on locked bootloader. You can search in SP forums and contact the respective persons for porting the feature.
Click to expand...
Click to collapse
Contact Skrilax_CZ on freenode at channel #motomagic and he might be able to help us.
Hi,
Amazon release source code as is required by GPL. That is great but to reproduce a binary needs compiler information.
All the stuff I find here on modifying these devices seems to be based on downloading someone else's binaries and hoping they are clean and actually relate to the OS version I have. This info does not always seem to be provided.
If I want to build busybox and su using gcc and copy them across using adb , where can I find the required build info ?
I guess guys here building ROMs must be doing this.
Thanks.
Was wondering if anybody has worked on any type of a redmi 7 rom based on lineage since we just got a twrp solution.
My boot loader is going to be unlocked in 12 days, so if any developers are working on anything let me know and i can test it out.
Thanks!
Devs need from Xiaomi to open source the kernel at least to make things easier.
It is good that we are having TWRP now without source code.
The phone is still very new and it is already catching a lot of development attention.
mylove90 said:
Devs need from Xiaomi to open source the kernel at least to make things easier.
It is good that we are having TWRP now without source code.
The phone is still very new and it is already catching a lot of development attention.
Click to expand...
Click to collapse
Does xiaomi have a track record on how long they give an open source kernal?
mylove90 said:
Devs need from Xiaomi to open source the kernel at least to make things easier.
It is good that we are having TWRP now without source code.
The phone is still very new and it is already catching a lot of development attention.
Click to expand...
Click to collapse
Agreed. I'm waiting to build it too
Kernel to be open-sourced by the end of this month
My estimate is that the kernel will be open-sourced around the 20th of May, hopefully. I've got all the gear ready to build a custom ROM, for a Redmi device, for the first time. I'm looking to build Lineage (but I don't know whether I'd succeed). I got the device on the 8th of May, and still waiting for that 360h to go by, as my bootloader is still locked. In the meantime, I'm looking for what else I can try out!
looks like the kernel source is released
kernel source are released already
Anyone was courage enough to try to compile the kernel source on his own ?
The sources released are not official or final.
The sources released doesn't compile as is and some fixing because of some errors.