[Samsung Galaxy Nexus] drdnght mrk lazarus:
Hi all

I'm am writing this because I have an issue which I can't seem to resolve on my own, my galaxy nexus, after 2 months of faithful flashes and service, suddenly wont start up anymore.

a bit of a prelude: my data connection was on and I was surfing a bit, I was done, put the phone in my pocket.. then suddenly after 5 or so minutes I felt a vibrate. When I took my phone out, it seemed to be rebooting. but it just kept on the initial screen of the boot process for like 5 minutes of longer (the image with google and a unlocked padloc at the bottem)

In this case, maybe I'll try and wipe the cache and so on, then I realised I couldn't boot into recovery mode, I still saw the icon of rom manager, but couldn't get further. (no options etc)

in that case I figured, lets just remove the battery for a bit and see what happens, so I did, after and hour of 2 I put it back in, still didn't get past the google bootscreen, still couldn't acces recovery...

although, the bootloader seemed to be working, I can access that part, can select the different boot options (to no avail)

so I tought, lets just reflash a recovery from the stickied thread through fastboot..

sadly no dice, when attempting to do this I get

G:\android\android-sdk-windows\platform-tools>fastboot.exe flash boot yakju-jro0
3c\image-yakju-jro03c\boot.img
sending 'boot' (4366 KB)... OKAY [ 0.786s]
writing 'boot'... FAILED (status read failed (Too many links))
finished. total time: 0.814s

and the bootloader screen comes all jittery (horizontal ghosting kind of) pics to follow

that's with each command I use in fastboot mode, only

fastboot reboot-bootloader

works like described.

grave mistake I did while in bootloader, tried to flash a bootloader in fastboot mode, the device wouldn't even turn on whatever I did...

luckely, omapflash resurrected my phone so now I still have acces to bootloader and download mode

tried to access download mode, while it works, and I get odin to recognize the device, I get the same screen after reaching a certain point in odin

<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!

at that point I can only disconnect my phone...

so now I'm heading home, to my spot where I know the drivers are working (because I used it to flash different recoveries and upgrade to jb) and hope for the best.

tl;dr

phone went into a bootloop

tried to access recovery which didn't load

tried fastboot to flash recovery, jittery screen

fastboot bootloader, killed my phone completely

omapflash resurrected my phone

ODIN mode, download mode accessible, stuck on NAND Write Start!!, same jittery

do any of you have something to add, something I didn't think of doing?

going to add pics of the jittery screen when I arrive home, also keeping you guys updated on the development of things.

EDIT: got the pictures

gallery: https://www.dropbox.com/sh/yjdm819tsiscpbd/QgM43CK4dy

normal bootloader:

after fastboot flash command

on screen:

next odin:

when trying the flash the file

bootloader after odin