Corrupt JPG and MP4 headers from a faulty microSD card - any solution?
Long story short: I bought a faulty microSD card a few weeks ago to expand my Android phone's storage and since then, most if not all of the pics and videos I've taken are unreadable either from the phone or from the computer (and either connecting it via usb cable or extracting the microSD and plugging it into the computer's card reader).
It's not that they've been erased or anything; the files are there, they weigh and they have correct size/timestamp/name properties, but they're just unreadable, they cannot be opened no matter the software I try to open them with.
I've done some Recuva stuff and it seems that the problem is on the files' header. Look at these two different headers: first one is from an MP4 file that is ok and readable, and the other one is from one of the corrupt MP4 files. That FF FF FF ý ý ý ý ý ý pattern is repeated on all corrupt files, including the JPG ones:
Is there any way to reconstruct these broken headers so I can re-gain access to the files?
headers
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
add a comment |
Long story short: I bought a faulty microSD card a few weeks ago to expand my Android phone's storage and since then, most if not all of the pics and videos I've taken are unreadable either from the phone or from the computer (and either connecting it via usb cable or extracting the microSD and plugging it into the computer's card reader).
It's not that they've been erased or anything; the files are there, they weigh and they have correct size/timestamp/name properties, but they're just unreadable, they cannot be opened no matter the software I try to open them with.
I've done some Recuva stuff and it seems that the problem is on the files' header. Look at these two different headers: first one is from an MP4 file that is ok and readable, and the other one is from one of the corrupt MP4 files. That FF FF FF ý ý ý ý ý ý pattern is repeated on all corrupt files, including the JPG ones:
Is there any way to reconstruct these broken headers so I can re-gain access to the files?
headers
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
(3rd pic os from a good header, 4th one is from the first corrupt file, just right after I inserted the faulty microSD on Jan 3rd): i63.tinypic.com/dwuk28.png /// i65.tinypic.com/2hyf9kn.png
– Sergio Santos
Feb 28 '17 at 22:31
add a comment |
Long story short: I bought a faulty microSD card a few weeks ago to expand my Android phone's storage and since then, most if not all of the pics and videos I've taken are unreadable either from the phone or from the computer (and either connecting it via usb cable or extracting the microSD and plugging it into the computer's card reader).
It's not that they've been erased or anything; the files are there, they weigh and they have correct size/timestamp/name properties, but they're just unreadable, they cannot be opened no matter the software I try to open them with.
I've done some Recuva stuff and it seems that the problem is on the files' header. Look at these two different headers: first one is from an MP4 file that is ok and readable, and the other one is from one of the corrupt MP4 files. That FF FF FF ý ý ý ý ý ý pattern is repeated on all corrupt files, including the JPG ones:
Is there any way to reconstruct these broken headers so I can re-gain access to the files?
headers
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
Long story short: I bought a faulty microSD card a few weeks ago to expand my Android phone's storage and since then, most if not all of the pics and videos I've taken are unreadable either from the phone or from the computer (and either connecting it via usb cable or extracting the microSD and plugging it into the computer's card reader).
It's not that they've been erased or anything; the files are there, they weigh and they have correct size/timestamp/name properties, but they're just unreadable, they cannot be opened no matter the software I try to open them with.
I've done some Recuva stuff and it seems that the problem is on the files' header. Look at these two different headers: first one is from an MP4 file that is ok and readable, and the other one is from one of the corrupt MP4 files. That FF FF FF ý ý ý ý ý ý pattern is repeated on all corrupt files, including the JPG ones:
Is there any way to reconstruct these broken headers so I can re-gain access to the files?
headers
headers
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
edited Mar 12 '17 at 21:23
DavidPostill♦
104k25225260
104k25225260
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
asked Feb 28 '17 at 22:31
Sergio Santos Sergio Santos
11
11
(3rd pic os from a good header, 4th one is from the first corrupt file, just right after I inserted the faulty microSD on Jan 3rd): i63.tinypic.com/dwuk28.png /// i65.tinypic.com/2hyf9kn.png
– Sergio Santos
Feb 28 '17 at 22:31
add a comment |
(3rd pic os from a good header, 4th one is from the first corrupt file, just right after I inserted the faulty microSD on Jan 3rd): i63.tinypic.com/dwuk28.png /// i65.tinypic.com/2hyf9kn.png
– Sergio Santos
Feb 28 '17 at 22:31
(3rd pic os from a good header, 4th one is from the first corrupt file, just right after I inserted the faulty microSD on Jan 3rd): i63.tinypic.com/dwuk28.png /// i65.tinypic.com/2hyf9kn.png
– Sergio Santos
Feb 28 '17 at 22:31
(3rd pic os from a good header, 4th one is from the first corrupt file, just right after I inserted the faulty microSD on Jan 3rd): i63.tinypic.com/dwuk28.png /// i65.tinypic.com/2hyf9kn.png
– Sergio Santos
Feb 28 '17 at 22:31
add a comment |
2 Answers
2
active
oldest
votes
You've got bigger problems than corrupt headers.
1) The block of FFs is considerably larger than the size of a JPEG header unless it has a thumbnail embedded in it.
2) Note the file size. Only a few kb. Even if it were perfectly intact that's not much data.
3) I see no method by which the damage would magically hit only the start of the files. Rather, it's hitting the start of a chunk of data on disk--which means it's likely repeated at other points in the file (except, note point #2--you don't have much there.) Also, your screenshot only shows bad data, I see no reason to think there's any good data.
4) I don't think you have a faulty card at all. If it really were doing that it would have blown up the directory. Rather, I think you have a fraudulent card that is masquerading as something far bigger than it really is. They work normally up to their real size and then do this sort of thing once they go past that point.
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
Thank you for your detailed response, Loren. 1) All my JPEGs feature thumbnails - unless I'm missing/misunderstanding something. 2) Look at the 2nd screenshot.. It's clear that the size of these JPG and MP4 files vary strongly. There are a couple of 100 - 400MB MP4s (these are video recordings from a concert) and also very small ones (home recordings of pets and kids of a few seconds each). Maybe you got confused by the . (dot) instead of the , (comma) but here in Spain 428.443KB is 428MB, not 428-and-a-half KB.
– Sergio Santos
Mar 17 '17 at 13:44
3) Can you explain this a little more? Do you mean that if I find a way to reconstruct the header and make it readable, the rest of the file will be equally damaged? 4) That is interesting. I bought it in Amazon from a reputed seller, but we know how things go with SD and microSD cards... you can get a faulty/fraudulent one easily. Do you think that's what happened? That is corrupted everything past its real capacity? Thanks again.
– Sergio Santos
Mar 17 '17 at 13:45
@SergioSantos You're right--I was fooled by your punctuation. And, yes, I strongly suspect you have a fraudulent card. Here's a discussion of what I'm talking about: rmprepusb.blogspot.com/2013/10/…
– Loren Pechtel
Mar 17 '17 at 18:20
add a comment |
Although it's name may not suggest it, JPEG Recovery LAB can recover (fragmented) MP4 video files as well.
Files filled with a FF FF byte patterns are beyond repair/recovery. However it looks like Recuva did a file system scan (vs RAW scan). So JPEG Recovery LAB may pull up some JPGs as well as it uses a different method.
Please note that system requirements are steep, 8 GB minimum and that it will keep your PC occupied for a few hours.
Can be found here: https://www.disktuna.com/jpeg-recovery-lab-digital-photo-recovery/
really hope this helps.
answered Jul 4 '18 at 13:27
ArchArch
173
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1183824%2fcorrupt-jpg-and-mp4-headers-from-a-faulty-microsd-card-any-solution%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You've got bigger problems than corrupt headers.
1) The block of FFs is considerably larger than the size of a JPEG header unless it has a thumbnail embedded in it.
2) Note the file size. Only a few kb. Even if it were perfectly intact that's not much data.
3) I see no method by which the damage would magically hit only the start of the files. Rather, it's hitting the start of a chunk of data on disk--which means it's likely repeated at other points in the file (except, note point #2--you don't have much there.) Also, your screenshot only shows bad data, I see no reason to think there's any good data.
4) I don't think you have a faulty card at all. If it really were doing that it would have blown up the directory. Rather, I think you have a fraudulent card that is masquerading as something far bigger than it really is. They work normally up to their real size and then do this sort of thing once they go past that point.
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
Thank you for your detailed response, Loren. 1) All my JPEGs feature thumbnails - unless I'm missing/misunderstanding something. 2) Look at the 2nd screenshot.. It's clear that the size of these JPG and MP4 files vary strongly. There are a couple of 100 - 400MB MP4s (these are video recordings from a concert) and also very small ones (home recordings of pets and kids of a few seconds each). Maybe you got confused by the . (dot) instead of the , (comma) but here in Spain 428.443KB is 428MB, not 428-and-a-half KB.
– Sergio Santos
Mar 17 '17 at 13:44
3) Can you explain this a little more? Do you mean that if I find a way to reconstruct the header and make it readable, the rest of the file will be equally damaged? 4) That is interesting. I bought it in Amazon from a reputed seller, but we know how things go with SD and microSD cards... you can get a faulty/fraudulent one easily. Do you think that's what happened? That is corrupted everything past its real capacity? Thanks again.
– Sergio Santos
Mar 17 '17 at 13:45
@SergioSantos You're right--I was fooled by your punctuation. And, yes, I strongly suspect you have a fraudulent card. Here's a discussion of what I'm talking about: rmprepusb.blogspot.com/2013/10/…
– Loren Pechtel
Mar 17 '17 at 18:20
add a comment |
You've got bigger problems than corrupt headers.
1) The block of FFs is considerably larger than the size of a JPEG header unless it has a thumbnail embedded in it.
2) Note the file size. Only a few kb. Even if it were perfectly intact that's not much data.
3) I see no method by which the damage would magically hit only the start of the files. Rather, it's hitting the start of a chunk of data on disk--which means it's likely repeated at other points in the file (except, note point #2--you don't have much there.) Also, your screenshot only shows bad data, I see no reason to think there's any good data.
4) I don't think you have a faulty card at all. If it really were doing that it would have blown up the directory. Rather, I think you have a fraudulent card that is masquerading as something far bigger than it really is. They work normally up to their real size and then do this sort of thing once they go past that point.
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
Thank you for your detailed response, Loren. 1) All my JPEGs feature thumbnails - unless I'm missing/misunderstanding something. 2) Look at the 2nd screenshot.. It's clear that the size of these JPG and MP4 files vary strongly. There are a couple of 100 - 400MB MP4s (these are video recordings from a concert) and also very small ones (home recordings of pets and kids of a few seconds each). Maybe you got confused by the . (dot) instead of the , (comma) but here in Spain 428.443KB is 428MB, not 428-and-a-half KB.
– Sergio Santos
Mar 17 '17 at 13:44
3) Can you explain this a little more? Do you mean that if I find a way to reconstruct the header and make it readable, the rest of the file will be equally damaged? 4) That is interesting. I bought it in Amazon from a reputed seller, but we know how things go with SD and microSD cards... you can get a faulty/fraudulent one easily. Do you think that's what happened? That is corrupted everything past its real capacity? Thanks again.
– Sergio Santos
Mar 17 '17 at 13:45
@SergioSantos You're right--I was fooled by your punctuation. And, yes, I strongly suspect you have a fraudulent card. Here's a discussion of what I'm talking about: rmprepusb.blogspot.com/2013/10/…
– Loren Pechtel
Mar 17 '17 at 18:20
add a comment |
You've got bigger problems than corrupt headers.
1) The block of FFs is considerably larger than the size of a JPEG header unless it has a thumbnail embedded in it.
2) Note the file size. Only a few kb. Even if it were perfectly intact that's not much data.
3) I see no method by which the damage would magically hit only the start of the files. Rather, it's hitting the start of a chunk of data on disk--which means it's likely repeated at other points in the file (except, note point #2--you don't have much there.) Also, your screenshot only shows bad data, I see no reason to think there's any good data.
4) I don't think you have a faulty card at all. If it really were doing that it would have blown up the directory. Rather, I think you have a fraudulent card that is masquerading as something far bigger than it really is. They work normally up to their real size and then do this sort of thing once they go past that point.
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
You've got bigger problems than corrupt headers.
1) The block of FFs is considerably larger than the size of a JPEG header unless it has a thumbnail embedded in it.
2) Note the file size. Only a few kb. Even if it were perfectly intact that's not much data.
3) I see no method by which the damage would magically hit only the start of the files. Rather, it's hitting the start of a chunk of data on disk--which means it's likely repeated at other points in the file (except, note point #2--you don't have much there.) Also, your screenshot only shows bad data, I see no reason to think there's any good data.
4) I don't think you have a faulty card at all. If it really were doing that it would have blown up the directory. Rather, I think you have a fraudulent card that is masquerading as something far bigger than it really is. They work normally up to their real size and then do this sort of thing once they go past that point.
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
answered Mar 12 '17 at 21:50
Loren PechtelLoren Pechtel
2,0461621
2,0461621
Thank you for your detailed response, Loren. 1) All my JPEGs feature thumbnails - unless I'm missing/misunderstanding something. 2) Look at the 2nd screenshot.. It's clear that the size of these JPG and MP4 files vary strongly. There are a couple of 100 - 400MB MP4s (these are video recordings from a concert) and also very small ones (home recordings of pets and kids of a few seconds each). Maybe you got confused by the . (dot) instead of the , (comma) but here in Spain 428.443KB is 428MB, not 428-and-a-half KB.
– Sergio Santos
Mar 17 '17 at 13:44
3) Can you explain this a little more? Do you mean that if I find a way to reconstruct the header and make it readable, the rest of the file will be equally damaged? 4) That is interesting. I bought it in Amazon from a reputed seller, but we know how things go with SD and microSD cards... you can get a faulty/fraudulent one easily. Do you think that's what happened? That is corrupted everything past its real capacity? Thanks again.
– Sergio Santos
Mar 17 '17 at 13:45
@SergioSantos You're right--I was fooled by your punctuation. And, yes, I strongly suspect you have a fraudulent card. Here's a discussion of what I'm talking about: rmprepusb.blogspot.com/2013/10/…
– Loren Pechtel
Mar 17 '17 at 18:20
add a comment |
Thank you for your detailed response, Loren. 1) All my JPEGs feature thumbnails - unless I'm missing/misunderstanding something. 2) Look at the 2nd screenshot.. It's clear that the size of these JPG and MP4 files vary strongly. There are a couple of 100 - 400MB MP4s (these are video recordings from a concert) and also very small ones (home recordings of pets and kids of a few seconds each). Maybe you got confused by the . (dot) instead of the , (comma) but here in Spain 428.443KB is 428MB, not 428-and-a-half KB.
– Sergio Santos
Mar 17 '17 at 13:44
3) Can you explain this a little more? Do you mean that if I find a way to reconstruct the header and make it readable, the rest of the file will be equally damaged? 4) That is interesting. I bought it in Amazon from a reputed seller, but we know how things go with SD and microSD cards... you can get a faulty/fraudulent one easily. Do you think that's what happened? That is corrupted everything past its real capacity? Thanks again.
– Sergio Santos
Mar 17 '17 at 13:45
@SergioSantos You're right--I was fooled by your punctuation. And, yes, I strongly suspect you have a fraudulent card. Here's a discussion of what I'm talking about: rmprepusb.blogspot.com/2013/10/…
– Loren Pechtel
Mar 17 '17 at 18:20
Thank you for your detailed response, Loren. 1) All my JPEGs feature thumbnails - unless I'm missing/misunderstanding something. 2) Look at the 2nd screenshot.. It's clear that the size of these JPG and MP4 files vary strongly. There are a couple of 100 - 400MB MP4s (these are video recordings from a concert) and also very small ones (home recordings of pets and kids of a few seconds each). Maybe you got confused by the . (dot) instead of the , (comma) but here in Spain 428.443KB is 428MB, not 428-and-a-half KB.
– Sergio Santos
Mar 17 '17 at 13:44
Thank you for your detailed response, Loren. 1) All my JPEGs feature thumbnails - unless I'm missing/misunderstanding something. 2) Look at the 2nd screenshot.. It's clear that the size of these JPG and MP4 files vary strongly. There are a couple of 100 - 400MB MP4s (these are video recordings from a concert) and also very small ones (home recordings of pets and kids of a few seconds each). Maybe you got confused by the . (dot) instead of the , (comma) but here in Spain 428.443KB is 428MB, not 428-and-a-half KB.
– Sergio Santos
Mar 17 '17 at 13:44
3) Can you explain this a little more? Do you mean that if I find a way to reconstruct the header and make it readable, the rest of the file will be equally damaged? 4) That is interesting. I bought it in Amazon from a reputed seller, but we know how things go with SD and microSD cards... you can get a faulty/fraudulent one easily. Do you think that's what happened? That is corrupted everything past its real capacity? Thanks again.
– Sergio Santos
Mar 17 '17 at 13:45
3) Can you explain this a little more? Do you mean that if I find a way to reconstruct the header and make it readable, the rest of the file will be equally damaged? 4) That is interesting. I bought it in Amazon from a reputed seller, but we know how things go with SD and microSD cards... you can get a faulty/fraudulent one easily. Do you think that's what happened? That is corrupted everything past its real capacity? Thanks again.
– Sergio Santos
Mar 17 '17 at 13:45
@SergioSantos You're right--I was fooled by your punctuation. And, yes, I strongly suspect you have a fraudulent card. Here's a discussion of what I'm talking about: rmprepusb.blogspot.com/2013/10/…
– Loren Pechtel
Mar 17 '17 at 18:20
@SergioSantos You're right--I was fooled by your punctuation. And, yes, I strongly suspect you have a fraudulent card. Here's a discussion of what I'm talking about: rmprepusb.blogspot.com/2013/10/…
– Loren Pechtel
Mar 17 '17 at 18:20
add a comment |
Although it's name may not suggest it, JPEG Recovery LAB can recover (fragmented) MP4 video files as well.
Files filled with a FF FF byte patterns are beyond repair/recovery. However it looks like Recuva did a file system scan (vs RAW scan). So JPEG Recovery LAB may pull up some JPGs as well as it uses a different method.
Please note that system requirements are steep, 8 GB minimum and that it will keep your PC occupied for a few hours.
Can be found here: https://www.disktuna.com/jpeg-recovery-lab-digital-photo-recovery/
really hope this helps.
answered Jul 4 '18 at 13:27
ArchArch
173
add a comment |
Although it's name may not suggest it, JPEG Recovery LAB can recover (fragmented) MP4 video files as well.
Files filled with a FF FF byte patterns are beyond repair/recovery. However it looks like Recuva did a file system scan (vs RAW scan). So JPEG Recovery LAB may pull up some JPGs as well as it uses a different method.
Please note that system requirements are steep, 8 GB minimum and that it will keep your PC occupied for a few hours.
Can be found here: https://www.disktuna.com/jpeg-recovery-lab-digital-photo-recovery/
really hope this helps.
answered Jul 4 '18 at 13:27
ArchArch
173
add a comment |
Although it's name may not suggest it, JPEG Recovery LAB can recover (fragmented) MP4 video files as well.
Files filled with a FF FF byte patterns are beyond repair/recovery. However it looks like Recuva did a file system scan (vs RAW scan). So JPEG Recovery LAB may pull up some JPGs as well as it uses a different method.
Please note that system requirements are steep, 8 GB minimum and that it will keep your PC occupied for a few hours.
Can be found here: https://www.disktuna.com/jpeg-recovery-lab-digital-photo-recovery/
really hope this helps.
answered Jul 4 '18 at 13:27
ArchArch
173
Although it's name may not suggest it, JPEG Recovery LAB can recover (fragmented) MP4 video files as well.
Files filled with a FF FF byte patterns are beyond repair/recovery. However it looks like Recuva did a file system scan (vs RAW scan). So JPEG Recovery LAB may pull up some JPGs as well as it uses a different method.
Please note that system requirements are steep, 8 GB minimum and that it will keep your PC occupied for a few hours.
Can be found here: https://www.disktuna.com/jpeg-recovery-lab-digital-photo-recovery/
really hope this helps.
answered Jul 4 '18 at 13:27
ArchArch
173
answered Jul 4 '18 at 13:27
ArchArch
173
answered Jul 4 '18 at 13:27
ArchArch
173
answered Jul 4 '18 at 13:27
ArchArch
173
173
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1183824%2fcorrupt-jpg-and-mp4-headers-from-a-faulty-microsd-card-any-solution%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
(3rd pic os from a good header, 4th one is from the first corrupt file, just right after I inserted the faulty microSD on Jan 3rd): i63.tinypic.com/dwuk28.png /// i65.tinypic.com/2hyf9kn.png
– Sergio Santos
Feb 28 '17 at 22:31