Hi guys, this is my first time posting problems like these as I've never encountered anything I can't fix by myself or with help from fine developers and the community here, but now I'm desperate so I wanted to give it a shot.Anyways here's what happened. My battery died, along with my USB port (the latter of physical damage - it's not burned just the port got damaged from usage I guess). Anyways, I got original replacement parts, put them in all good. And now when I plug in the charge cable, the LED briefly flashes green and after that nothing happens. However, I found out that if I hold power and volume down and plug in the USB cable then, bootloader turns on. It's interesting how the bootloader was marked as locked even though I unlocked it ages ago. Anyways, when I try to start it normally it shows the Google logo, and after a second or so, it shuts down completely (after the screen goes off, the green LED flashes again). I tried doing rebooting bootloader and recovery, same thing occurs. I tried using factory images and here's the weird/interesting part. When I manually flash the images from the latest 5.1.1 set, everything passes except when I tried doing fastboot flash data userdata.img . It downloads as it should, but it stops after the write part (it says that it can't flash a filesystem with type ' ' - Same goes for fastboot format and fastboot wipe and fastboot erase). However, when I use flash-all batch, it passes as it should (write phase included - or that's at least what it says), but still, the phone won't turn on. I can't do fastboot boot recovery.img as it gives the same result. I should note that I did try fastboot oem unlock, and it pops up the confirmation screen and all, and when I press yes, it works as it should, unlocks the bootloader (I know since when I booted into bootloader again, it showed that it's unlocked, and on the Google logo it shows the little symbol on the bottom), but shuts down on the Google logo again. Flashing any other custom made image (for example this http://dmitry.gr/index.php?r=06.+Tho...%20on%20Nexus4 Android M image) gives the same outcome. I really ran out of ideas and could appreciate any help or at least ideas on what could be broken on it so I can let it rest in peace.Also might be noteworthy that my Ubuntu didn't recognize anything when I attached it in fastboot. As in nothing happened.Here are screenshots of the fastboot output if someone's interested (ignore the red marking on the screenshot, it was for a friend :P ):