Just to confirm, the kexec hardboot
approach used here is a bit different from the typical kexec. The main difference is that we actually perform a hardware reboot, reinvoking the bootloader just prior to booting the kexec'd kernel.
The advantage to this approach is that it maintains a high-degree of compatibility and minimizes buggy behavior. The disadvantage is that it requires that the bootloader is capable of booting custom recoveries
, which the present Verizon SGS3 bootloader is capable of doing.
Thus, it's very important that folks do not apply any over-the-air (OTA) update
, until it is confirmed that custom recovery booting remains intact.
If it eventually arises that booting from a stock kernel/recovery is necessary, then it's likely a bunch of kernel bugs will have to be fixed, and it might still have compatibility issues observed in previous kexec attempts. It's linked in the blog post, but there's a bit more of a technical description of the hardboot approach in this old thread
Thanks to invisiblek and captjtkirk for testing.