anthwlock / untrunc

Restore a truncated mp4/mov. Improved version of ponchio/untrunc
GNU General Public License v2.0
1.9k stars 182 forks source link

Need help #46

Closed 4dvn closed 4 years ago

4dvn commented 4 years ago

Can you upload the source of windows gui? I wanna add more function

anthwlock commented 4 years ago

https://github.com/anthwlock/untrunc/tree/master/src/gui

What do you want to add?

4dvn commented 4 years ago

https://github.com/anthwlock/untrunc/tree/master/src/gui

What do you want to add?

I have some infected video files by ransomware is encrypted the 150kb of header and 334 bytes of the end of files need to recover: video.zip

anthwlock commented 4 years ago

I still don't understand what function you want to add.

The latest commit I added (23490c6) should be helpful in your case. I think it removed some of the audio noise at the beginning. Btw, you know about -s, right?

4dvn commented 4 years ago

I still don't understand what function you want to add.

The latest commit I added (23490c6) should be helpful in your case. I think it removed some of the audio noise at the beginning. Btw, you know about -s, right?

Oh is -sm option from gui missing, can you add repair all corrupt files on the folder and output repaired save file with original name without *-fixed

anthwlock commented 4 years ago

I added a -range option, it is used like this: untrunc -s -range 725000:-350000 good.mov bad.mov

Additionally I noticed that the original trak atom seems to be fully contained in the .mado file. You can take advantage of this: untrunc -range 32: -u bad.mov bad.mov

Oh is -sm option from gui missing

It probably won't find the start of the mdatatom, since the first ~150kb are encrypted.

can you add repair all corrupt files on the folder and output repaired save file with original name without *-fixed

Hmm.. why not just write a little script?

4dvn commented 4 years ago

I added a -range option, it is used like this: untrunc -s -range 725000:-350000 good.mov bad.mov

Additionally I noticed that the original trak atom seems to be fully contained in the .mado file. You can take advantage of this: untrunc -range 32: -u bad.mov bad.mov

Oh is -sm option from gui missing

It probably won't find the start of the mdatatom, since the first ~150kb are encrypted.

can you add repair all corrupt files on the folder and output repaired save file with original name without *-fixed

Hmm.. why not just write a little script?

Can you tell the way to compile it on windows? I can't find to recompile source code 😭

anthwlock commented 4 years ago

The windows build is updated automatically.

4dvn commented 4 years ago

i got error on line 230 of mp4 file on mp4.cpp `Info: version '7e38461' using ffmpeg '3.3.4' Info: range: 32:9223372036854775807 -> 24:10161796 (10161764) Warning: start of moov not found Assertion failed!

Program: C:\Users\My PC\Downloads\Compressed\untrunc_x64\untrunc_x64\untrunc.exe File: src/mp4.cpp, Line 230

Expression: findAtom(fmoov, "moov", moov)`

anthwlock commented 4 years ago

This means that the file you provided as second argument has no moov atom. Please check with a hexeditor.

Maybe that file is from a different camera? If the moov atom comes before the mdat atom, it will probably be contained in the first 150kb, and thus get encrypted. Nikon also adds a (relatively) large udta (~385KB) atom at the end, which further "protects" the moov atom, since the file end also gets encrypted. Though in the case where only the last 334 bytes get encrypted, this shouldn't matter.

Have you tried: untrunc -s -range 725000:-350000 good.mov bad.mov?

DRCRecoveryData commented 2 months ago

This means that the file you provided as second argument has no moov atom. Please check with a hexeditor.

Maybe that file is from a different camera? If the moov atom comes before the mdat atom, it will probably be contained in the first 150kb, and thus get encrypted. Nikon also adds a (relatively) large udta (~385KB) atom at the end, which further "protects" the moov atom, since the file end also gets encrypted. Though in the case where only the last 334 bytes get encrypted, this shouldn't matter.

Have you tried: untrunc -s -range 725000:-350000 good.mov bad.mov?

is encrypted extractly 153605 bytes by default from header