Okay, so I rooted my phone with clockwork mod recovery and pushed superuser. After I was rooted, I listened to someone that I shouldnt have and downloaded some post root tools, one of which was vm heap. I set it to the recommended setting (either 24 or 28--I think it was 28. Whichever said recommended) and it asked me to reboot, which sent me into a boot loop. A couple of important notes to take: 1) after rooting, I couldn't get back into my clockwork recovery. Whenever I tried getting into recovery, it would only show an android with a red exclamation mark. Someone told me the trick was to download root explorer and add a 1 to a certain file/path and that it would work fine. I never did do this (WHY?!?!?!? I have no good excuse) before I started playing with these root tools, and so now I can't flash the factory image for my 4.0.2 version. Another important note: while I was rooting, adb was only recognizing my phone while it was in the normal state; as soon as I gave it the command to put my phone in the bootloader, it would stop recognizing my device. I realized it was a driver problem, and went thru my device manager and reinstalled the driver software and it finally worked. Since it bricked, it is doing the same thing again...it recognizes my device while its in the bootloop, and responds to the adb reboot bootloader command, but as soon as I am in the bootloader the computer no longer recognizes the device, and this time my little driver update fix isn't working. So, I am bricked and I have no custom recovery. I managed getting into my android system recovery <3e> but my only options are to A) reboot system now, B) apply update from/cache, C) wipe data/factory reset, and D) wipe cache partition. I don't see an option to flash anything ( I was going to try and re-push clockwork mod so I could go into recovery and flash the factory image) and so I have no idea what to do. I'm thinking that the factory reset is my best option, but am not sure what it will do to my root state and whether or not it will even fix the problem that (I think) the vm heap has caused. If anyone has any ideas I am totally up to suggestions, otherwise I am going to have to go to verizon tomorrow and hope they don't notice that its bricked. I was going to try to tell them that I went with the update to 4.0.2 this morning finally, and that once it restarted it sent me to a bootloop. The only problem is, if they pull the battery and restart it they will see the unlocked symbol, and know that its rooted. BUT, I live in hickville virginia and as long as they have a nexus in stock I really don't think they'll have any clue what Ive done. If verizon finds out I've rooted, will they contact assurion and tell them not to replace my device if I claim it stolen? I'm just not sure what to do. Someone please help me get my phone back to life from the stock recovery.