Actually, trying to fsck a BTRFS partition is a VERY BAD idea. (Same applies for other CoW filesystems like ZFS and log-structured filesystems like UDF and F2FS).
The best is to always simply try to get an early version (before the "copy" part of Copy-on-Write). For BTRFS, things that might help : - mounting with "recovery" (will scan back the older copies until it finds the latest usable) (for kernel 4.6 and newer, its now called "usebackuproot") - mounting with "nologreplay" (completely ignore the journal log) - using "btrfs restore -s -x -m -S -i " on an image transfered to a laptop.
By write, you mean you DD an image file over the raw device. Not that you mount the (perhaps corrupted) partition and untar your files inside ? By check you mean mount and "btrfs scrub start" ?
To me, that looks like a broken btrfs partition. If you have some place where I can send you the file (FTP server ? Something else ?) I can send you my recovery partition. I just can't post it publicly, because it contain non-public code (mostly driver and blobs from Qualcomm which make it illegal to post online).