Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 7
    Is the "unexpected end of file" to be expected? Commented Sep 2, 2016 at 23:57
  • The extraction in 2 surprisingly worked on an encrypted file. How is this possible? The decompression then failed with gzip: stdin: invalid compressed data--format violated. I assume the extraction succeeded, as dd reports 22763821+0 records in 22763821+0 records out. Commented Jul 31, 2018 at 2:28
  • @TomRussell The extraction merely trims bytes off the start. Commented Apr 25, 2020 at 22:33
  • 1
    Isn't dd a bit of an overkill to just skip 24 bytes? This is also not failsafe unless conv=noerror,sync iflag=fullblock is added: superuser.com/a/1523120/910769 You might consider this answer: android.stackexchange.com/a/78183/340401 Commented Mar 8, 2021 at 1:08