[Q] Cannot adb pull despite appearing to have adb root privilege topic

I have a Galaxy S4 (GT-I9507) which is rooted with busybox installed and the CWM custom recovery. I recently made a Nandroid backup and since I don't have an sdcard, it was stored in /data/media/clockworkmod/backup/ or /mnt/shell/emulated/clockworkmod/backup/. Now, I can't move this using a root explorer app to an area accessible via USB to back it up to my computer since I don't have enough room left on my phone, so I've been trying to copy it to my PC using adb pull. Thing is, I'm on a stock ROM so my original adbd binary does not allow adb root. So I installed Chainfire's adbd Insecure app and enabled it. Now when I run adb root I'm told that adbd is already running as root. When I do adb shell, I get

Code:

---

root@jftdd:/ #

---

. However, adb is not actually running as root. It just appears to run as root. It says it's running as root but if I try

Code:

---

adb shell ls /data/media/

---

I get Permission Denied. Until I actually do

Code:

---

adb shell
su
ls /data/media/

---

I continue to get Permission errors. This means that

Code:

---

adb pull /data/media/clockworkmod/

---

or

Code:

---

adb pull /mnt/shell/emulated/clockworkmod/

---

both fail too because despite adb saying it's running as root and looking like it's running as root it does not actually have root privilege. My question is how on earth do I actually get it to have root privilege so I can pull my CWM backups without permission errors?

Spec info:
Samsung Galaxy S4 (GT-I9507) running KitKat 4.4.2 connected via USB Cable to a PC running Windows 7. Command prompt with Administrator privileges is used to access adb.