Retired Recognized Developer
Thanks Meter 2,096
Join Date: Dec 2010
Location: Queen City of the West
Originally Posted by LibertyMonger
CBW's has a flashing tool that makes it easier for someone who doesn't know what they are doing to flash it easier, it does the root and openrecovery steps automatic so that's why it's much bigger. We just use need the nandroid file here as we are mostly already rooted and have open recovery installed. In other words cbw package has training wheels lol
pydave isn't saying the size is different. The files have changed.
md5sums compute identifying strings (i.e. 2c8a3b5452f9eddfa46217e61679d0d7) that can be used as fingerprints. If the md5sums are different, then the content of files is different. What pydave has found is that the nandroid files don't match what rev posted anymore. So, possibly ultimobile's modified or updated something. The md5sum of the system.img could easily have changed simply by rev making making a backup nandroid and posting it. But, there's no way we can change the boot.img because of the bootlock.
What's strange is that the md5 sum of the boot.img again doesn't match anything I've seen before and it's different from the first one that CBW shipped.
I'm going to see if I can find out some more about this kernel. I'm still looking for the msi I downloaded the day it was released by CBW to compare.