the bin directory contains quite a few symbolic links, so it is quite possible that could be the reason. Are you doing this on Windows or Linux?
which .img extractor are you using?take a look here ---> http://jiggawatt.org/badc0de/android/index.htmlnchntrman said:Has anyone else seen md5 chechsum errors when unpacking the Firmware system.img? Using the official release of both 7_24 and 7_4 extracting the system.img to a folder then checking with the system_check.md5 included in the official release. I get about 49 failed files (mostly in the /bin directory). I was wondering if anyone else had this problem as well. Trying to determine if it is my md5summer application my .img extractor, OR is it possible that the system_check.md5 is not correct as included in the firmware zip file.
See how they're all exactly the same? That's because in Linux they're all linked to toolbox, the "real" one. In windows, the symlinks dump as empty files, so that's why he gets a mismatch. If he went through the trouble to copy "toolbox" to all those filenames , they would be correct again.c86b1c1e257266a7995cf070964160af ./bin/catc86b1c1e257266a7995cf070964160af ./bin/chmodc86b1c1e257266a7995cf070964160af ./bin/chownc86b1c1e257266a7995cf070964160af ./bin/cmpc86b1c1e257266a7995cf070964160af ./bin/datec86b1c1e257266a7995cf070964160af ./bin/ddc86b1c1e257266a7995cf070964160af ./bin/dfc86b1c1e257266a7995cf070964160af ./bin/dmesgc86b1c1e257266a7995cf070964160af ./bin/geteventc86b1c1e257266a7995cf070964160af ./bin/getpropc86b1c1e257266a7995cf070964160af ./bin/hdc86b1c1e257266a7995cf070964160af ./bin/idc86b1c1e257266a7995cf070964160af ./bin/iftopc86b1c1e257266a7995cf070964160af ./bin/insmodc86b1c1e257266a7995cf070964160af ./bin/ioctlc86b1c1e257266a7995cf070964160af ./bin/killc86b1c1e257266a7995cf070964160af ./bin/lnc86b1c1e257266a7995cf070964160af ./bin/logc86b1c1e257266a7995cf070964160af ./bin/lsc86b1c1e257266a7995cf070964160af ./bin/lsmodc86b1c1e257266a7995cf070964160af ./bin/mkdirc86b1c1e257266a7995cf070964160af ./bin/mountc86b1c1e257266a7995cf070964160af ./bin/mvc86b1c1e257266a7995cf070964160af ./bin/netstatc86b1c1e257266a7995cf070964160af ./bin/newfs_msdosc86b1c1e257266a7995cf070964160af ./bin/notifyc86b1c1e257266a7995cf070964160af ./bin/printenvc86b1c1e257266a7995cf070964160af ./bin/psc86b1c1e257266a7995cf070964160af ./bin/rebootc86b1c1e257266a7995cf070964160af ./bin/renicec86b1c1e257266a7995cf070964160af ./bin/rmc86b1c1e257266a7995cf070964160af ./bin/rmdirc86b1c1e257266a7995cf070964160af ./bin/rmmodc86b1c1e257266a7995cf070964160af ./bin/routec86b1c1e257266a7995cf070964160af ./bin/schedtopc86b1c1e257266a7995cf070964160af ./bin/sendeventc86b1c1e257266a7995cf070964160af ./bin/setconsolec86b1c1e257266a7995cf070964160af ./bin/setpropc86b1c1e257266a7995cf070964160af ./bin/sleepc86b1c1e257266a7995cf070964160af ./bin/smdc86b1c1e257266a7995cf070964160af ./bin/startc86b1c1e257266a7995cf070964160af ./bin/stopc86b1c1e257266a7995cf070964160af ./bin/syncc86b1c1e257266a7995cf070964160af ./bin/toolboxc86b1c1e257266a7995cf070964160af ./bin/topc86b1c1e257266a7995cf070964160af ./bin/umountc86b1c1e257266a7995cf070964160af ./bin/vmstatc86b1c1e257266a7995cf070964160af ./bin/watchpropsc86b1c1e257266a7995cf070964160af ./bin/wipe