Hello girls and guys,
I am looking for a method to safely sign my own custom ROM the same way the "stock" system/recovery gets signed, so that I still have the feature to relock the bootloader after installing a recovery that only accepts zips signed with my private key.
What I have found so far are the following resources:
Android Specific:
https://source.android.com/devices/t...gn_builds.html
https://mjg59.dreamwidth.org/31765.html
http://www.cs.cuhk.hk/~cslui/PUBLICA...14DROIDRAY.pdf
http://wiki.rootzwiki.com/Signing
Device/Bootloader specific:
https://developer.qualcomm.com/downl...r-overview.pdf
https://www.codeaurora.org/blogs/lit...oid-bootloader
https://github.com/littlekernel/lk
https://www.w3.org/2012/webcrypto/we...mission_25.pdf
https://sturmflut.github.io/mediatek...and-preloader/
https://sturmflut.github.io/mediatek...little-kernel/
https://groups.google.com/forum/embe...el/cafLHDWTOiE (some explanation)
http://newandroidbook.com/Articles/aboot.html http://newandroidbook.com/index.php (book about it)
http://forum.xda-developers.com/andr...oader-t3276098
http://forum.xda-developers.com/onep...oader-t3269111
Goal of my reasearches is to have a locked down experience just like when I have bought a device.
I currently have a Oneplus 2 and a Nexus 5 for research and testing purposes.
Excuse me if I have not any technical expertise in this area in future posts,
all I want is to collect documentation, understand how the concept works
and maybe build my own ecosystem where I compile or only sign things I want to have on my phone and possible third partys can't modify anything.
I am looking for a method to safely sign my own custom ROM the same way the "stock" system/recovery gets signed, so that I still have the feature to relock the bootloader after installing a recovery that only accepts zips signed with my private key.
What I have found so far are the following resources:
Android Specific:
https://source.android.com/devices/t...gn_builds.html
https://mjg59.dreamwidth.org/31765.html
http://www.cs.cuhk.hk/~cslui/PUBLICA...14DROIDRAY.pdf
http://wiki.rootzwiki.com/Signing
Device/Bootloader specific:
https://developer.qualcomm.com/downl...r-overview.pdf
https://www.codeaurora.org/blogs/lit...oid-bootloader
https://github.com/littlekernel/lk
https://www.w3.org/2012/webcrypto/we...mission_25.pdf
https://sturmflut.github.io/mediatek...and-preloader/
https://sturmflut.github.io/mediatek...little-kernel/
https://groups.google.com/forum/embe...el/cafLHDWTOiE (some explanation)
http://newandroidbook.com/Articles/aboot.html http://newandroidbook.com/index.php (book about it)
http://forum.xda-developers.com/andr...oader-t3276098
http://forum.xda-developers.com/onep...oader-t3269111
Goal of my reasearches is to have a locked down experience just like when I have bought a device.
I currently have a Oneplus 2 and a Nexus 5 for research and testing purposes.
Excuse me if I have not any technical expertise in this area in future posts,
all I want is to collect documentation, understand how the concept works
and maybe build my own ecosystem where I compile or only sign things I want to have on my phone and possible third partys can't modify anything.