[Galaxy Note GT-N7000 Android Development] nursoda:
Yet, it does not. When i enter recovery, and only immediately before PhilZ Touch is ready to be used, I get the device. Before that (that is, e.g. after shutting down the phone regulyrly, and restarting it) the device list is empty (although I hear from Windows that it found an USB device).

The one I was referring to was not, it was captured using the app when system was up.

First I tried randomly to capture the bootloop but did not succeed. I once managed to have adb logcat running while in bootloop, but without redirecting output to a file. Thus, I only have some remnants from terminal window cut+paste left.

I then tried systematically to start the logcat at different stages:

in recovery: then it wites "/sbin/sh: exec: line 1: logcat: not found" to the file and exits

immediately after screen goes black when pressing "reboot system" in CWM": creates a 0 byte file since adb stays in "- waiting for device -" state. adb terminates after entering decryption credentials.

immendiately after entering credentials: stays in "- waiting for device -". Ctrl-C, adb devices -> shown, logcat logs -- so I shall not start IMMEDIATELY after device startup? What is the correct time to start it??

when system is up: started logcat and shut phone down. 2MB

while phone is off: "- exec '/system/bin/sh' failed: No such file or directory (2) -"

after starting it I get no device no matter when I try - until either encryption credentials are entered or recovery is up and user accessible

NOTES:

Currently I can always enter encryption credentials, no error. I aborted there and entered recovery too wipe cache and ART cache to force the bootloop.

Wipe Cache gives some lines "formatting ... complete". Wipe ART cache does not give any line -- OK?

I cannot save recovery settings since they are stored within data (which is encrypted).

Further steps:

issue "adb devices" all the time as long as system boots up: only IMMEDIATELY before home screen appears, the device is shown. If I do the "adb logcat" before the device is shown, I get "- waiting for device -" but even as the device IS up, nothing is logged or shown!? So: how can I capture an error log on boot?

I immediately issued an "adb logcat" and captured the rest of the startup. I then called deskclock which FCed and checked the log. I see LOTS of permission issues there (I did not touch any of these!):

W/PackageManager( 3618): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x48be45)
W/PackageManager( 3618): Unknown permission com.android.deskclock.worldclock.permissions.WRITE_DATABASE in package com.android.deskclock

I also did not understand these:

W/PackageManager( 2301): Failed to parse /system/app/DeskClock: Not a coreApp: /system/app/DeskClock

I'm mentioning these because I saw that there is a "Terminal" app in /system/app but I cannot start it. It's not shown in the launcher, at least not in Nova.

The log gave me an idea what might cause the FC: I set density to 280 - setting to 288 (which I had in SlimSaber 4.4.4 before) did not resolve it, neither did setting to 320 (default). So that seems not to be the cause here:

I/ActivityManager( 3618): Config changes=200 {1.0 ?mcc?mnc de_DE ldltr sw457dp w457dp h706dp 280dpi nrml port finger -keyb/v/h -nav/h s.5 themeResource=null}
W/BroadcastQueue( 3618): pending app [foreground]ProcessRecord{37cbed87 0:com.android.deskclock/u0a37} died before responding to broadcast

BUT deskclock DID work once, right after installation, when I did not alter anything. Hmmm.

Anyway: after setting density to 320 and restarting, I HAD a bootloop - but "only" three (or four?) times - then it stopped. So was your original comment "wait for 15 Minutes" meant to wait that long while in bootloops also?

I managed to capture this (partially looped) boot!

ZIP attached