[Galaxy S 4 i9505 Original Android Development] egendomligt:
I don't think that'll make any difference (and "tail -f | dmesg" doesn't really work, does it..?). Backgrounded stuff dies with the shell session since they're subprocesses, no? (I did a small test with a backgrounded sleep command, it wouldn't let me exit the shell session)

Anyways, I tried getting some logs for you but.. I actually can't reproduce getting status 7 / set_perm error. I installed official cwm 6.0.3.2 through ROM Manager and I'm using cm-10.1-20130619-NIGHTLY-jfltexx.zip to try it. I've got some other errors and a couple of freezes, but the ROM flashes just fine.

Here's what I did:

* I formatted /system, /data and /cache and powered off the phone (reboot -p from adb shell), booted to cwm, flashed the file. No problems.

* I then formatted data/cache with "factory reset", formatted /system and flashed again. No problems.

* Advanced -> reboot recovery

* Flashed the file again. No problems.

I thought maybe this issue is actually fixed in this build(!?), so I downloaded cm-10.1-20130618-NIGHTLY-jfltexx.zip.

* adb pushed that (I'm still in the same recovery session as last flash here)

* Flashed it straight away without any wipes. Recovery froze up after this: (Captured with adb shell tail -F -n +0 /tmp/recovery.log > recovery.log)

-- Installing: /sdcard/0/Download/cm-10.1-20130618-NIGHTLY-jfltexx.zip
Finding update package...
I:Update location: /sdcard/0/Download/cm-10.1-20130618-NIGHTLY-jfltexx.zip
I:using /data/media for /sdcard/0/Download/cm-10.1-20130618-NIGHTLY-jfltexx.zip.
Opening update package...
Installing update...
Warning: No file_contexts
about to run program [/tmp/backuptool.sh] with 2 args
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 11/176704 inodes and 23193/706560 blocks

* I hard rebooted into cwm and tried to flash it again. Worked fine, apart from a few things in recovery.log that didn't look too good:

-- Installing: /sdcard/0/Download/cm-10.1-20130618-NIGHTLY-jfltexx.zip
Finding update package...
I:Update location: /sdcard/0/Download/cm-10.1-20130618-NIGHTLY-jfltexx.zip
I:using /data/media for /sdcard/0/Download/cm-10.1-20130618-NIGHTLY-jfltexx.zip.
Opening update package...
Installing update...
Warning: No file_contexts
mount: failed to mount /dev/block/mmcblk0p16 at /system: Invalid argument
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 10.1
run_program: child exited with status 127
unmount of /system failed; no such volume
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 11/176704 inodes and 23193/706560 blocks
... (snip - just extracting files) ...
about to run program [/tmp/backuptool.sh] with 2 args
/tmp/backuptool.sh: cd: line 72: can't cd to /tmp/addon.d/
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
cp: can't stat '/tmp/addon.d/*': No such file or directory
script result was [/system]

* Rebooted into system to see if it worked. It powered up fine.

I think I need some specific instructions as to what to do to get these errors...