CM seems to me to be more to do with the 'most widely used' phones and not down to chip or Android version as vendors can add/change boot up to Android and each vendor can be different even down to mtd partition order/naming.
I've been trying to figure out what exactly the 0:MIBIB means (as I haven't found anything relevant towards what it stands for or what it does do via googling it, the closest thing I have come across is two separate acronyms, they being:
MI - Machine Instruction .... Which will be slightly obvious although would separate it from other machine code instructions for operation.
BIB - Backwards Indicator Bits ....
The Forward Indicator Bits (FIBs) and Backward Indicator Bits (BIBs) are used for retransmissions. Under normal conditions (no link errors), the FIB and BIB have the same value. As illustrated in Figure 4-9, the field length is 1 bit; therefore, only two values are possible: 0 or 1.
To me thinking about it, what if the option to edit this FIB/BIB would now be locked for greater security whereas before those Bits may have been ignored or unset?. Looking at the diagram on the linked page I can see to a certain degree the block layout of the systems partitions used on Android, seeing as we may have to delve deeper
to attain S-OFF may as well find out all we can from whatever we can even if it seems odd
---------- Post added 3rd May 2012 at 12:01 AM ---------- Previous post was 2nd May 2012 at 11:56 PM ----------
Could the longer reboot times be down to verifying the installed hboot because maybe a pointer/signature/whatever wasn't set before it was installed whereas the original and official updates may be verified before installing therefore no check so shorter boot time?
Added this as well to the found docs