[Galaxy Note GT-N7000 General] Morality:
Allright, I'm here with some 'xplaining to do :P

Ok so first of all I apologize about being so vague about the freezing issue, I just assumed you would've heard about that by now :) From what I read, it's a bit less common issue with notes recovering from superbricks. Never had anything like that before the superbrick occurred. Quite frankly, the phone just comes unresponsive, except for that you can turn off the screen or enter the power menu ONCE, before a removal of battery/forced reboot is required. The likelihood of it occurring seems to be completely random, although it seems to happen more often during the "Preparing SD Card" -phase of boot. Another symptom of it seems to be eternal boot animations from time to time. Also, very rarely I've ran into a situation, where upon reboot I would get an error "Encryption unsuccesful", which forces a factory reset. This is very rare, however and I assure you, it has nothing to do with actually encrypting, since I haven't done anything of the kind :). I haven't tested if USB still works in this unresponsive state and currently am unable to (you'll see why if you stick by this post :) )

So yesterday prior the major battle between me and the odd freezing issue, I had found an app called "emmc check", which basically ran "dd if=/dev/block/mmcblk0 of=/dev/null", which didn't run properly on Asylum v09, so I tried to flash Paranoid Android .02 to test out if it ran right there. Unfortunately it didn't but something mindboggling happened though:

I did not have the freezing issue with PA. During the 10 hour period I had the ROM before going head to head with the freezebug, I had absolutely zero freezes. I've had the issue with Kingdroid 2.0, with stock ICS, with stock GB, with Kingdroid 7.0, with Asylum v08 and v09, but PA didnt freeze once. Well, unless you count one instance of the "Encryption unsuccesful" that followed a SOD (which is a very rare issue on my phone).

So now the battle begins:

I initially flashed the stock partition table .pit, so I could pinpoint exactly where all of my bad blocks were. The results showed that I had some in /system and another set in /data. UMS was free of errors, as was cache. This confused me, as in most of the partition schemes I attempted to fix the freezing issue with started after where stock /data ended. I didn't think much into it.

I had alot of problems trying to repartition manually, which most likely were due to the PC I was using, so I eventually gave up with that as it seemed to lead me nowhere. I just flashed your "*-patched.pit", after which I installed Paranoid Android yet again, since it seemed to work well before. After several reboots reinstalls and reflashes from different kernels, I was able to boot into it just fine, and haven't had a single freeze yet.. It seems to be a miracle of the PA rom, which still confuses me alot.

Anything else I could tell you that would shed some light into this issue?

Small update of what I think might be a related symptom: I'm currently unable to copy my 3gb music folder to the internal sdcard, after a certain point in media device Windows pops up with an error "The target device is not responding" and the copying stops, also the phone needs to be rebooted. Same goes for storage mode, but there the copying wont even start. It just fails right away and requires a restart of the phone. However, flashing Thor kernel v10 and mounting USB I was able to copy anything I wanted to the internal SDcard, but the default kernel of the Paranoid Android refuses to mount USB. Any ideas? I'll report back when I use stuff from the internal sdcard, if anything out of the ordinary happens. Or when nothing happens.