[Samsung Galaxy Nexus] xTorment:
TL;DR; version on the bottom.

Hi everyone. I'm long time user of xda, though I rarely post, because I've always found the solution for my android problems until today.

I've bricked many phones in the past and always managed to get them back up working, including my Galaxy Nexus that has been bricked easly over 10 times... possibly over 15.

Anyway, yesterday I was testing some Kitkat 4.4 stuff on my phone. my daily ROM as been paranoid android for a long time. since they were on 2.8 or something.

First I installed nexus 5 launcher on my gnexus because I really wanted to test the new google experience thing.

Then I thought it was a bit slow, and decided to install a full 4.4 ROM. ended up deciding I couldn't miss some of the paranoid android features and flashed my paranoid android rom back (3.99 RC2), installed the GEL (google experience launcher) installed xposed framework and put my device the way it was pretty much.

To make GEL a bit more faster and fluid I decided to overclock a bit (I've overclocked alot in the past up to 1900+ Mhz and never had problems though I know it's not healthy for the phone.)

I've overclocked it to about 1500... I just wanted to see how it would work and then turn it back to normal again.

I got distracted for some reason and forgot to turn it off (and I think it might have been that... something burned inside or something...)

At night I was checking something on the browser, and then the phone suddenly reboots, which happened in the past several times (people that flash alot should know).

the phone started boot looping on google logo and from my previous bricks I knew it was bricked and I did what I usually do.

Went to recovery mode, wiped everything expect internal storage, dalvik cashe, system, cashe and data.

tried flashing paranoid android and gapps, didn't work. Then proceeded to flashing stock rom, didn't work either.

From that point and from my previous bricks, I knew it was something more serious than just rom.

So then I did a odin flash, and I thought it would be fine after because odin never failed me before. I did odin flash, it did the google logo boot, and then started the boot animation from the stock rom and after 3 seconds looped google logo again followed by the stock nexus bootanimation (before it only looped the google logo boot).

I searched a bit on xda, and found this thing called OMAP (I used this post http://xdaforums.com/showthread.php?t=2146790), which apparently is something you do when your phone has no software at all (for people that somehow mess their bootloaders and/or downloading modes )from what I understood.

I tried it out, it kind of worked I believe though I found odd that my device kept reconnecting to my pc as "omap4460 usb device" every 3 seconds.

After that I did a odin flash again and didn't work.

After all this I'm thinking that the problem is not software but hardware because of that little overclock I did and forgot to undo.

Any help would be appreciated.

TL;DR; Version:

Was running paranoid android 3.99 RC2, installed the new GEL (google experience launcher);

Overclocked a bit to make GEL faster but intended to put the clock speeds to normal after;

Forgot to set the clock speeds to normal (though I'm not 100% sure that's what messed my device);

At night while using the browser the device rebooted and got stuck in google logo bootloop.

wiped everything except internal storage and flashed paranoid android, didn't work, flashed stock rom, didn't work either;

Did a odin flash, device appeared to boot, at least got over google logo boot, and started the stock bootanimation, but kept looping that.

Did OMAP (I don't know the right term for this... OMAP flashing? I don't think that's correct)thing to see if would fix the phone, then odin flash again but didn't work.

Any help would be appreciated