• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Kexec

chicle

chicle

Well-Known Member
I'm not sure if this works for us or not, but I saw a thread about it in the touchpad section in xda. I googled it, but I really don't understand it. I'm posting this because I'm sure someone here will know if it's useful for our Motion.
 
chicle said:
I'm not sure if this works for us or not, but I saw a thread about it in the touchpad section in xda. I googled it, but I really don't understand it. I'm posting this because I'm sure someone here will know if it's useful for our Motion.
Click to expand...

From what i see it looks promising in the right hands.
 
This method may work since we boot on a boot.img when the system is running I don't know if it will but im guessing not. This method was used on the Droid razr and worked but there where problems such as one core not functioning I believe data broke and some other kinks
 
zimlokks said:
This method may work since we boot on a boot.img when the system is running I don't know if it will but im guessing not. This method was used on the Droid razr and worked but there where problems such as one core not functioning I believe data broke and some other kinks
Click to expand...

it was also used on teh verizon note 2 and sgs3 with no issues to bypass the bootloader
 
From Wikipedia, the free encyclopedia

In computing, kexec (kernel execution) is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running kernel. kexec skips the bootloader stage (hardware initialization phase by the firmware or BIOS) and directly loads the new kernel into memory, where it starts executing immediately. This avoids the long times associated with a full reboot,[1] and can help systems to meet high-availability requirements by minimizing downtime.

While feasible, implementing a mechanism such as kexec raises two major challenges:

1: the new kernel will overwrite the memory of the currently running one, while it is still executing.

2: the new kernel will usually expect all physical devices to be in a well-defined state (as they are after system reboot, when the BIOS (or firmware) resets them to a "sane" state). Bypassing a real reboot may leave devices in an unknown state, and the new kernel will have to recover from that.
 
well figuring the motion is only $49 right now after rebates...i'll test out any attempts at this on my phone...

just do me a favor, please remind me to back up my stuff...i always forget and then spend days getting everything back in order...
 
You must log in or register to reply here.
Back
Top Bottom