Hey there, my1stSmartPhone!
Been a while since I saw your first post here!
Sorry for the lateness of this reply--I saw yours while going through the Android System Mods, Scripts and Hacks area and moving some threads to their root-specific forums as appropriate.
[I saw/see you are in conversation with
@EarlyMon here--let me know if you want that thread moved to the Moto G all-things-root area]
In regards to your question above/here, it seems that the various manufacturers hide their bootloader lock state/status in a variety of ways and locations.
For example, on the Samsung Galaxy Nexus in the /param partition as a single byte (1=locked, 0=unlocked) in a seemingly obscure location (decimal byte 124). Other devices like the Nexus 5 use the /misc partition; the 2nd gen (2013) Nexus 7 uses the /aboot partition, etc.
These locations (for various Nexus devices) were gleaned and tested by
some brave and enterprising folks who unlocked and re-locked their bootloaders, taking partition dumps in-between and comparing the differences to identify the byte offsets and values. That method won't always reveal the locking method as evidenced by the 2012 N7 which has a confusing series of byte strings that (unfortunately) differ for each user.
Anyway, these partitions are indeed not typically backed-up with a custom recovery's Nandroid backup function. Indeed, only the partitions that would typically change for a given user (/system, /data, /cache; sometimes the boot and recovery partitions).
I've even seen that there can be hidden (diagnostic?) partitions on the device that the partition table in Android does not reveal--those can sometimes be seen and pulled from fastboot, by again, this is all very device-dependent.
That's all I got--hope that helps!
Cheers!
