logo elektroda
logo elektroda
X
logo elektroda

Repair Damaged or Too Large JPG Photos: Solutions for Camera Files & Programs to Use

raroberto 4338 14
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16929421
    raroberto
    Level 2  
    Posts: 4
    Board Language: polish
    I warmly welcome,

    I have a problem with opening photos (message that the file may be damaged or too large) Photos were copied from the camera. One of the files is attached.

    I am asking for help, a hint of what program can be used to repair - maybe someone had a similar problem or knows how to deal with it?

    greetings
    Robert
    Attachments:
    • aaa.jpg (3.54 MB) You must be logged in to download this attachment.
  • ADVERTISEMENT
  • #2 16929562
    dt1
    Admin of Computers group
    Posts: 47947
    Help: 7257
    Rate: 8181
    Board Language: polish
    Welcome. The structure of the file does not resemble a photo at all. Can you upload 2-3 other files?
  • ADVERTISEMENT
  • #3 16929583
    Prot
    Level 38  
    Posts: 2580
    Help: 574
    Rate: 297
    Board Language: polish
    raroberto wrote:
    The photos were copied from the camera


    And from what camera :?: How were they copied (with some software? With some file manager?) :?: Are they all damaged?

    The attached file has a damaged structure in the header, and at the end it has the entire database "attached" - a list of several dozen photos :cry:

    Sometimes even files damaged by ransomware (with only part of the file encrypted) can be recovered by mounting a "healthy" header from a photo (file) taken with the same camera in the hex editor.

    Try it yourself or possibly attach a jpg file that was also subject to this "copying" and you can open it :|
  • #4 16929656
    raroberto
    Level 2  
    Posts: 4
    Board Language: polish
    All files are corrupted, as none of them can be opened. The photos were transferred from the Nikon D90 - I used the move, not copy option, so I don't have a copy on the camera ...

    Attached are the last two photos from this series, the first one was added previously.
    Attachments:
    • DSC_0443.JPG (2.96 MB) You must be logged in to download this attachment.
    • DSC_0442.JPG (3.35 MB) You must be logged in to download this attachment.
  • #5 16929741
    Robert B
    Level 43  
    Posts: 22594
    Help: 2027
    Rate: 1412
    Board Language: polish
    These files also only contain the trash.
    raroberto wrote:
    I used the move not copy option

    Basic error. First it copies itself, checks if it is readable and only deletes it from the source medium. If you have not written anything on the card, this is a chance for recovery.
  • #6 16929866
    raroberto
    Level 2  
    Posts: 4
    Board Language: polish
    It is not exactly like that, because after the transfer I was looking at these photos and they were ok. Interesting is that you can see a thumbnail of some of them, but it is impossible to open the file.

    Another idea is to recover data from the camera's memory card. When looking at the next photos taken on the camera, the numbering goes further, so they were not overwritten. What recovery program can I use?
  • #7 16929873
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    Board Language: polish
    Use Recuva directly on a "camera card" (?) Connected via a reader (?).
    Do not write anything on the card. Do you have a reader for it?
    Or is it the built-in memory of your camera and you are using it in mass storage mode?
    Do you use JPG or JPG + RAW (NEF) write mode?
    Provide detailed information so you don't have to guess.

    Added after 1 [minutes]:

    Prot wrote:
    How were they copied (with some software? With some file manager?)

    You don't answer questions. Did you transfer to HDD, or maybe to flash drives?
    Post SMART Disk from Crystal Disk Info. Enter the pen model.

    Added after 1 [minutes]:

    raroberto wrote:
    Looking at the next photos taken on the camera, the numbering goes further,

    Nothing could be more wrong. Maybe you are just overwriting previous photos "along and across".
    Stop overwriting and start recovering.
  • ADVERTISEMENT
  • #8 16929885
    Anonymous
    Level 1  
  • #9 16929889
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    Board Language: polish
    @ Kraniec_Internetów I had no awareness. At least let him see if anything can be recovered.
    It is known -> how important photos are, first the partition letter deletion and the sector copy ...
  • #10 16929905
    Anonymous
    Level 1  
  • #11 16929925
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    Board Language: polish
    Kraniec_Internetów wrote:
    Sectoral copy is, in my opinion, an unnecessary procedure.

    We have too little information, including no SMART, but it's worth being safe, because if the damage to the JPG format is the fault of the falling disk, there is no time to waste ...
  • #12 16929989
    raroberto
    Level 2  
    Posts: 4
    Board Language: polish
    I will focus on recovering data from the card, but first I skip its contents. The current files are saved on the pendrive and this is probably the source of the problem.

    My entries are quite chaotic but I have no experience with such topics, thank you all for the answers ;-)
  • #13 16929999
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    Board Language: polish
    raroberto wrote:
    The current files are saved on the pendrive

    We developed this theory with a friend @ Kraniec_Internetów .
    Write how much the pen has capacity (on the housing and in My Computer) and the view of the pen from the ChipGenius program.
  • ADVERTISEMENT
  • #14 16930254
    pidar
    Mass storage specialist
    Posts: 11332
    Help: 1568
    Rate: 3554
    Board Language: polish
    raroberto wrote:
    The photos were transferred from the Nikon D90 - I used the transfer option

    I will ask if there was any error moving the files :?:
    raroberto wrote:
    It's not quite like that because after the transfer I looked at these photos and they were ok . The interesting thing is that you can see a thumbnail of some of them, but you can't open the file.

    Show view partitions from DMDE after selecting this flash drive from physical devices. :idea:
    raroberto wrote:
    The current files are saved on the pendrive and this is probably the source of the problem.

    The actual reading itself in Flash Drive Information Extractor will give us more information on "whether the fault is on the side" of the flash drive.
  • #15 16930581
    mati211p
    HDD and data recovery specialist
    Posts: 16915
    Help: 2584
    Rate: 1129
    Board Language: polish
    To which device the files were transferred and the next question that arises is why the files are looped every 128 sectors? If it was a different number, I think that the number 128 is so typical in computer science that maybe we are dealing with damage to the medium to which the files were transferred or, for example, a fake SD card or USB flash drive. This is for the first file. The second one also has repetitions of the same as 256 sectors, and the third file contains the same as the second even.
    Confirmation below, nothing can be recovered from it:
    File 1:
    Repair Damaged or Too Large JPG Photos: Solutions for Camera Files & Programs to Use
    File 2:
    Repair Damaged or Too Large JPG Photos: Solutions for Camera Files & Programs to Use
    File 3:
    Repair Damaged or Too Large JPG Photos: Solutions for Camera Files & Programs to Use
    You have to try to recover from the device you transferred it from.

Topic summary

✨ The discussion revolves around the issue of opening JPG photos that appear damaged or too large after being transferred from a Nikon D90 camera. The user reports that all files are corrupted and cannot be opened, despite having viewed them successfully before the transfer. Various suggestions are made for recovery, including using data recovery software like Recuva, which should be run directly on the camera's memory card without writing new data to it. Participants emphasize the importance of not overwriting files and recommend enabling "Deep scan" in Recuva for better recovery chances. There are also concerns about potential issues with the transfer medium, such as a faulty USB flash drive or SD card, which could have caused the corruption. The conversation highlights the need for careful file management and recovery techniques to salvage important photos.
Generated by the language model.

FAQ

TL;DR: Camera JPGs that loop every 128–256 sectors signal media corruption; “recover from the device you transferred it from.” [Elektroda, mati211p, post #16930581]

Why it matters:** If your photos won’t open, quick actions can prevent permanent loss. This FAQ is for photographers and PC users asking “how do I fix damaged or too‑large JPGs from my camera?”

Quick Facts

How do I fix “file may be damaged or too large” JPGs from my camera?

Stop writing to the source media. Attach the card via a reader. Run recovery to another disk. If recovery fails, try grafting a healthy JPEG header from the same camera using a hex editor. This can revive partially damaged images. If the copy target was a bad USB drive, prioritize recovering from the original card. “Try to recover from the device you transferred it from.” [Elektroda, Prot, post #16929583]

Are these files really photos if their structure looks wrong?

Maybe not. A genuine JPEG begins with a valid header and recognizable markers. If the internal structure does not resemble a photo, the file may be garbage data from a bad transfer or storage fault. In that case, focus on recovering from the original card rather than repairing the broken copies. [Elektroda, dt1, post #16929562]

Why do thumbnails show, but the JPEG won’t open?

Thumbnails can come from embedded previews or folder caches. If the header is damaged or non-JPEG data is appended, viewers may display a thumbnail yet fail to decode the image. Experts observed a damaged header and an appended database listing, which prevents normal opening. Consider header repair or deep recovery from the source media. [Elektroda, Prot, post #16929583]

Did moving files instead of copying cause this?

Yes. Moving deletes originals after transfer. If the destination is faulty, you lose both. Best practice: copy, verify by opening several images, then delete from the source. If nothing was written to the card afterward, recovery remains possible. [Elektroda, Robert B, post #16929741]

What is a sector copy and when should I use it?

A sector copy is a block‑level clone of the device to a safe image. Use it when the disk or flash media may be failing. Work on the clone to avoid worsening damage. “It’s worth being safe, because if the falling disk is at fault, there is no time to waste.” [Elektroda, safbot1st, post #16929925]

How do I recover deleted photos from an SD card with Recuva?

  1. Connect the card via a reader and start Recuva.
  2. Choose Pictures, enable Deep Scan, and scan the card.
  3. Save found files to a different drive, never back to the card. Users reported successful restores even after reformatting when Deep Scan was enabled. [Elektroda, Anonymous, post #16929905]

Why do my files repeat every 128 or 256 sectors?

Repetition at fixed sector intervals indicates corrupted media or a fake/counterfeit capacity device. An expert saw 128‑ and 256‑sector loops and concluded nothing was recoverable from those transferred files. “You have to try to recover from the device you transferred it from.” [Elektroda, mati211p, post #16930581]

Does camera numbering prove my old photos weren’t overwritten?

No. Continuing file numbers do not guarantee data safety. New captures can overwrite deleted areas regardless of numbering. Stop shooting and start recovery immediately to maximize success. “Stop overwriting and start recovering.” [Elektroda, safbot1st, post #16929873]

What is NEF, and does shooting JPG+RAW help recovery?

NEF is Nikon’s RAW format. Shooting JPG+RAW doubles your chances; recovery tools can find NEF even if JPGs are damaged. When asking for help, state whether the camera wrote JPG only or JPG+RAW (NEF). [Elektroda, safbot1st, post #16929873]

Can swapping a healthy JPEG header really fix a file?

Sometimes. If only the header is damaged, pasting a header from a good photo taken with the same camera can restore decoding. Use a hex editor and keep lengths consistent. “Mounting a healthy header from a photo taken with the same camera can help.” [Elektroda, Prot, post #16929583]

How do I test if my USB flash drive caused the corruption?

Check capacity and controller info with ChipGenius. Compare printed capacity with what the OS reports. Mismatches and anomalies suggest counterfeit or failing media. Share the ChipGenius view when seeking support. [Elektroda, safbot1st, post #16929999]

How can I inspect a suspicious card or stick in detail?

Show the partition map in DMDE after selecting the device from Physical Drives. Also run Flash Drive Information Extractor to read low‑level flash details. These tools reveal firmware quirks, partitions, and signs of fakery. [Elektroda, pidar, post #16930254]

All my transferred JPGs look like trash in a hex view—what now?

If the files are only garbage, repairs won’t help. Focus on recovering from the original card, not from the corrupted copies. Verify future transfers by opening samples before deleting originals. [Elektroda, Robert B, post #16929741]

What if I can preview some files but most won’t open?

Preview visibility means little. Viewers may show cached or embedded thumbnails while the main image is corrupted. Proceed with recovery from the card using a reader and Deep Scan, then try header repair if needed. [Elektroda, raroberto, post #16929866]
Generated by the language model.
ADVERTISEMENT