This is something seemingly understandable but I never get a clear idea how they relate to each other: 1. A locked bootloader, like the one in D3, prevents the deployment of customized kernel; 2. Safestrap provides a way to backup/restore, in addition, deploy update.zip; With the help of Safestrap, can we deploy customized kernel in the form of update.zip? If yes, does it mean the locked bootloader not longer an issue in AOSP development? Can someone walk me through the connections between these concepts? Thanks a lot.