I can answer for him, because i know what he wishes to avoid as unlikely as it might be. He had a [Only registered and activated users can see links. ] previously with an AU 2014.20 image which was only finally resolved when he unlocked and used an untouched original image from a similar LM device. On reviewing that thread, i see that the problem was repeated when he compiled his own image using MI. That's how pietu has compiled his images in Post #3 no doubt. Be a little like lightning striking twice if it happened again with this CN though.