If you are able to download the original rendition and open it (showing
there is nothing wrong with streaming the bits off the original
rendition JCR node) then im not sure ... Since you can update other
Tiff's it sounds like there is something weird w/ this Tif's
manifestation in AEM. You could try re-uploading the downloaded orginal
as a NEW asset and see if that asset has the same problem. If so, maybe
there is something w/ that tiff? All and all, HTTP Assets API supports
PUT requests for Tif...