{"issue":{"created_at":"2011-12-02T11:37:14Z","state":"closed","updated_at":"2011-12-02T23:42:03Z","comments":2,"user":{"gravatar_id":"19d3ee963fd0aeb4cefaa38b387c2844","id":1225124,"url":"https://api.github.com/users/mali1","login":"mali1","avatar_url":"https://secure.gravatar.com/avatar/19d3ee963fd0aeb4cefaa38b387c2844?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"When making a tar-backup (standard behavior in CWM 5) of the boot-partition (FAT32) on a device with omap-cpu (e.g. Nook) there is a good chance that the filename (in terms of case sensitivity) changes. On other partitions, thats no problem, since FAT should be case insensitive, but the internal microcode of the omap-cpu executes the bootloader only if its name is \"MLO\", a file called \"mlo\" will not get executed.\r\nTo avoid this, I think the backup of the boot-partition should be a raw image.","assignee":null,"number":18,"id":2426351,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"title":"tar backups aren't suitable for boot-partitions on omap-devices","closed_at":"2011-12-02T23:42:03Z","html_url":"https://github.com/koush/android_bootable_recovery/issues/18","url":"https://api.github.com/repos/koush/android_bootable_recovery/issues/18","milestone":null},"action":"closed"}