Where can I find information regarding low level kernel hacking on Android? For example, I'd like to know how the device boots and follow the execution path from that point. Where exactly is the code that runs after I press the power button?
-
androidenea.com/2009/06/android-boot-process-from-power-on.html (This link contains the parts where you can intervene / add your own functionality) The rough flow is Power On > Bootloader > Kernel > Init Process > System Server > Boot Complete Here's another link on the topic with references: elinux.org/Android_Booting– RossCCommented Dec 16, 2013 at 12:56
-
@RossC Perhaps you'd like to make that comment into an answer.– Dan HulmeCommented Dec 16, 2013 at 13:03
Add a comment
|
1 Answer
This link contains the parts where you can intervene / add your own functionality
The rough flow is Power On > Bootloader > Kernel > Init Process > System Server > Boot Complete
At the bootloader stage, the following is run:
A. The first boot loader stage will detect and set up external RAM.
B. Once external RAM is available and the system is ready the to run something more significant the first stage will load the main boot loader and place it in external RAM.
C. The second stage of the boot loader is the first major program that will run. This may contain code to set up file systems, additional memory, network support and other things. On a mobile phone it may also be responsible for loading code for the modem CPU and setting up low level memory protections and security options.
D. Once the boot loader is done with any special tasks it will look for a Linux kernel to boot. It will load this from the boot media (or some other source depending on system configuration) and place it in the RAM. It will also place some boot parameters in memory for the kernel to read when it starts up.
E. Once the boot loader is done it will perform a jump to the Linux kernel, usually some decompression routine, and the kernel assumes system responsibility.
Here's another link (more on the Linux side) on the topic with references: eLinux website answer
This comment stood out to me:
In general it is quite tricky to create a boot loader for an existing phone since they often come with tailor made boot loaders from the manufacturer. To add to the difficulty they also have security features that aim to prevent you from downloading your own bootloader. However, if you have an open platform you need an initial bootloader stage and a main bootloader able to start and/or flash software to the device. For the main bootloader you probably want to check out u-boot, http://www.denx.de/wiki/U-Boot. The initial bootloader stage needed to start u-boot need to be aware of the boot-protocol in the hardware requiring some documentation or reverse engineering in order to create or download a suitable one. To sum things up reprogramming of existing phones is often more work than its worth unless you are really interested in which case there are a lot of forums dedicated to that sort of thing.
-
A Chinese brand unlocked b/l android 11 that used high end h/w but did a shoddy job with their OS . There's no TWRP or root solution available so I can rid the stock of
Chinawarewhich reboots the phone every few mins.Magiskattemptbootloops. KernelSU-it wont part with source .ApatchI tried out but sinceCONFIG_KALLSYMS_ALLis not set, &patched bootset it , it , will not boot. I dunno what my opts are. There is another exact same h/w specs phone save so minor camera differences. What If I flash that entire ROM to this ? b/l unlocked can another ROM b/l fit & load its Kern Commented Aug 26 at 2:24