Bootcamp not showing in Devices & Can't transfer files between.

What did you use to resize the NTFS volume?

The problem is that the tool you used to resize the NTFS volume updated the MBR but didn't update the GPT. OS X only uses the GPT, and since the partition is invalid in the GPT, the NTFS volume doesn't mount. The MBR must have the correct entry, and that's why you can still boot.

Only tools explicitly designed for resizing Bootcamp'd disks know to update both the MBR and the GPT. So you're kinda lucky this hasn't totally hosed both systems. I suggest backing up before you do anything else. Use Windows backup or even file copy to get the most important stuff off the Windows side, and also make sure you have a current OS X backup also. Then you can proceed.

What you need to do is delete GPT entry #4, and use the information from the MBR entry #4 to create a new GPT #4 entry. You can do this with gdisk. The basic steps in gdisk:

1. p to print the GPT partition table

2. Confirm in the list that partition 4 starts at LBA 732149760, and if so delete this partition. That's d <enter> then enter the partition number to delete.

3. n to create a new partition. The start sector is 588019712, the end sector is 976773119. The partition type code is 0700.

4. r to get to the recovery/transform menu.

5. h to create a new hybrid mbr

6. 2 3 4 to add GPT partitions 2 3 4 to the MBR.

7. y to put EFI GPT as the first MBR entry.

8. For all prompts to enter an MBR hex code, just hit return, which will accept the default.

9. For GPT partition 2 and 3, do NOT make them bootable.

10. For GPT partition 4, DO make it bootable.

11. type o <return> p <return> and post the results if you want and I'll proof read it before you commit. Just leave gdisk at that prompt don't close Terminal or quit gdisk. The changes are in memory.

When you're ready to commit, you'll type w to write it out to disk. Then you need to reboot.

Yes, write it out.

w

You can boot Windows, and see also see the Windows volume when booted in OS X?

You somehow managed to escape a nasty case of data loss. Often what happens in these cases is the various parts overlap. And the NTFS resize is only noted in the MBR. Further the NTFS resize causes corruption of the backupt GPT at the end of the disk. When fixing the GPT corruption, it corrupts the NTFS volume, and also replaces the MBR, which contains the correct entry for the NTFS volume. Now, the correct values for the NTFS volume aren't available, and the NTFS file system is corrupt. So it's a huge mess.

If you aren't doing regular backups of both environments, this really, really should scare you into doing it now.