Database Info

[Q] Symptoms of a bricked phone? (related to all skyrocket users)

background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*

Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk

Did you try booting into recovery mode instead of odin?

Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.

silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3

if u can boot into cwm flash darkside

OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?

Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...

I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727

Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.

Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts

DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe

Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!

skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.

heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/

Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.

plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727

The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA

DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....

xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m

G2x - overheat, won't reboot

Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks

Xura08 said:
Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks
Click to expand...
Click to collapse
If you don't mind losing your internal sd card data you can try this and then flash the rom again to see if it fixes it.
http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA

I tried that (Thanks btw!). It formatted everything and sent the files over but it still does the same exact thing.
If I can't put a rom on it will they know I formatted everything? If so, will that void the warranty?

Xura08 said:
I tried that (Thanks btw!). It formatted everything and sent the files over but it still does the same exact thing.
If I can't put a rom on it will they know I formatted everything? If so, will that void the warranty?
Click to expand...
Click to collapse
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA

mansa_noob said:
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Actually most of the time you will be fine if you send in a rooted phone. There was a thread about this.
Sent from my Handheld Portal Device

mansa_noob said:
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Yes, I forgot about cwm. I can flash stock t-mo recovery on before I send it in. How would I go about pushing a stock rom onto it?
Also, I don't think I have a stuck vol- button. I've messed with it countless times. I suppose I could take the phone apart and see if it's really stuck. Do you have any other advice? As of now the phone only turns on (it displays the LG screen but after about 5 seconds the logo disappears and the touch buttons at the bottom flash and it repeats. ONLY while plugged into a power source, though)
@zlopp - thanks!

Xura08 said:
Yes, I forgot about cwm. I can flash stock t-mo recovery on before I send it in. How would I go about pushing a stock rom onto it?
Also, I don't think I have a stuck vol- button. I've messed with it countless times. I suppose I could take the phone apart and see if it's really stuck. Do you have any other advice? As of now the phone only turns on (it displays the LG screen but after about 5 seconds the logo disappears and the touch buttons at the bottom flash and it repeats. ONLY while plugged into a power source, though)
@zlopp - thanks!
Click to expand...
Click to collapse
You can use the reference link in the batch cleanup op. That one pushes stock 2.3.3. I don't think it is rooted either.
Does your phone boot loop or does it boot back into recovery?
Sent from my LG-P999 using XDA

bootloop. I can't get it to go into recovery. It won't bootloop, or boot at all, unless plugged into a power source. Does that sound like possibly a failed battery? It was taking forever to charge and whatnot a few weeks prior..

Unplug the phone. Plug it into the wall. Hold the battery in the socket, but dont let it touch the copper conntectors. Turn the phone one. It'll show the lg screen. Before it turns itself off, plug the battery in.

let it charge for $15 mins and redo CWM recovery again.
6 month ago one of my friend g2x fried up the main boardduring charge, I have to paid $100 for broken phone to get the main board replaced

Blazing angel said:
Unplug the phone. Plug it into the wall. Hold the battery in the socket, but dont let it touch the copper conntectors. Turn the phone one. It'll show the lg screen. Before it turns itself off, plug the battery in.
Click to expand...
Click to collapse
I can't believe it but it worked! However, once I flashed a rom and loaded it started giving problems. The battery indicator said 999% and the mainboard began getting a lot warmer than usual. Then it shut off. I turned it back on and the LG logo came up for 1 second then the screen flashed (A brief flash full of what looks like artifacts if a videocard were to fry) and it repeated the cycle. It looks like im sending this POS back to t-mobile

Xura08 said:
I can't believe it but it worked! However, once I flashed a rom and loaded it started giving problems. The battery indicator said 999% and the mainboard began getting a lot warmer than usual. Then it shut off. I turned it back on and the LG logo came up for 1 second then the screen flashed (A brief flash full of what looks like artifacts if a videocard were to fry) and it repeated the cycle. It looks like im sending this POS back to t-mobile
Click to expand...
Click to collapse
No problem. I was pulling my hair out when my phone did it too. It took a lot of experimentation to figure it out!
Now, onto the next problem. I suggest you run the g2x nullifier script to clean out anything on the rom. It might be messing with the phone. Then flash something known to be stable!
My phone also did the 999% thing. It was messing up a lot too, but the nullifier fixed it. Try it out

Xura08 said:
Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks
Click to expand...
Click to collapse
This SAME EXACT thing is happening to me except I had NO issues with the phone before. The battery had died down after a normal day of use, I charged it that night and then I wake up to it not powering on. Then with charger only a continuous bootloop of the white LG logo

Bootloop, nothing works. Please help!!

I have been running Zeus Rom for months now and everything has been fine. Until today. I was just on my phone today and it cut off. Then it went into a boot loop. Won't go past the Samsung screen. I can't find any solution to get the phone into download mode. I have read everything. Switched computers, tried different ports and even switched usb cords. Even tried several combinations of buttons to no avail.
Here is what happens when I try to get into download mode:
I hold down up and down volume, insert battery and then plug in usb cord. I see a spinning wheel and empty battery sign. Then it cuts right back off and does it all over again. Could this be a battery issue or what?
My phone has been bricked before I fixed it with no problems. This has got me stumped. Something is preventing me from getting into download mode and keeping me in boot loop.

Infuser86 said:
Here is what happens when I try to get into download mode:
I hold down up and down volume, insert battery and then plug in usb cord. I see a spinning wheel and empty battery sign. Then it cuts right back off and does it all over again. Could this be a battery issue or what?
Click to expand...
Click to collapse
To get to download mode, be sure to plug in USB before putting the battery in, and keep holding down the volume buttons down for some time.
If the battery isn't showing a charge, though, then let it charge. If it isn't charging, try another cable, and then maybe a new battery.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

Tried another battery I had, not fully charged, and the first time I put it in the bottom buttons lit up and the phone booted up, only to cut back off and do the same thing again with the boot loops. It too showed this battery to be completley dead. I am not sure if that is so or not as I have't used this battery in a while.
I am charging both batteries now to try to get them charged. I have one in a wall charger and hte other in the phone plugged into the wall. The one in the phone is still showing no charge as the phone keeps cutting on and off and showing the battery sign witha spinning circle.
I have no idea whats going on but need to find out soon!

jscott30 said:
To get to download mode, be sure to plug in USB before putting the battery in, and keep holding down the volume buttons down for some time.
If the battery isn't showing a charge, though, then let it charge. If it isn't charging, try another cable, and then maybe a new battery.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
You dont have to plug it in before puting the battery in...i never do...
How i get in download
1) pull battery
2) put battery back in
3) hold volume up + down simutaniously
4) while holding volume plug usb cord into phone
it sounds like he is pretty much doing it the way i do except for the volume he does before putting in battery...should work either way
Could it be a problem with your motherboard/mainboard whatever you wanna call it? When did you get the phone? If its been under a year i would file warranty with samsung...not att. If it is the mother board they probably will never even know its rooted or anything since it wont even turn on...and no software will fix it...
There still is a chance they will find out its rooted and has a custom rom on it...but i think the chances of that are highly unlikely...so i would go for warranty...
Sent from my SAMSUNG-SGH-I997 using XDA

UPDATE:
This is so weird. After nothing working all day, I finally remembered something. About 15 mins before my phone started this today, I dropped my phone while getting out of my truck. I didn't think anything about because I have a double layer case on it. But this evening, I remembered that and I thought maybe that had somethign to do with it. So what else could I do? Bang the phone on the ground again. So I tapped it a few hard times on the ground and sure enough the lights on teh bottom on the phone came on and it booted up and has stayed up.
Apparently the drop this morning has done something inside the phone. Do you guys have any idea what this could be? What could dropping the phone have to do with a boot loop and what could be solved by banging it on the ground again?
Maybe it is luck, but it is working. I just feel it will happen again soon as something is wrong inside the phone.

mg2195 said:
You dont have to plug it in before puting the battery in...i never do
Click to expand...
Click to collapse
Oh, okay, cool. I always do it how I described, so it must work either way. I was just trying to help the OP not go into the battery charging screen.
And to the OP: Bummer, it sounds like you have some busted hardware, but hopefully it will keep working now.
Sent from my HTC_Flyer_P512_NA using Tapatalk 2

Infuser86 said:
UPDATE:
This is so weird. After nothing working all day, I finally remembered something. About 15 mins before my phone started this today, I dropped my phone while getting out of my truck. I didn't think anything about because I have a double layer case on it. But this evening, I remembered that and I thought maybe that had somethign to do with it. So what else could I do? Bang the phone on the ground again. So I tapped it a few hard times on the ground and sure enough the lights on teh bottom on the phone came on and it booted up and has stayed up.
Apparently the drop this morning has done something inside the phone. Do you guys have any idea what this could be? What could dropping the phone have to do with a boot loop and what could be solved by banging it on the ground again?
Maybe it is luck, but it is working. I just feel it will happen again soon as something is wrong inside the phone.
Click to expand...
Click to collapse
loose connection insider vs corrosion issue I mentioned to you earlier.
if you're under warranty, flash a stock package and warranty.
if you're not under warranty, learn how to drop your phone correctly.

Infuser86 said:
UPDATE:
This is so weird. After nothing working all day, I finally remembered something. About 15 mins before my phone started this today, I dropped my phone while getting out of my truck. I didn't think anything about because I have a double layer case on it. But this evening, I remembered that and I thought maybe that had somethign to do with it. So what else could I do? Bang the phone on the ground again. So I tapped it a few hard times on the ground and sure enough the lights on teh bottom on the phone came on and it booted up and has stayed up.
Apparently the drop this morning has done something inside the phone. Do you guys have any idea what this could be? What could dropping the phone have to do with a boot loop and what could be solved by banging it on the ground again?
Maybe it is luck, but it is working. I just feel it will happen again soon as something is wrong inside the phone.
Click to expand...
Click to collapse
Oh my god. the same thing happened to me last night. I've been searching all day trying to figure out how to fix it and I came across your post saying you just banged it on the ground a few times and it started working. I did the same thing and sure enough, it started working again! It's so weird. What I don't get is that I didn't drop my phone at all yesterday. It just did it randomly while i was texting.

I think my phone is dead but I thought I would ask anyway

Can I just run this by you to see if there is anything you can add?
My wife’s phone started misbehaving recently it froze up and wouldn’t charge. On inspection I found it had had a little drink of water, only a very small splash but there was definitely some inside when I took the battery out to investigate. It was in her bag where a drink bottle spilled a little.
Anyway did all the usual stuff once I realised: stripped it out and put it in the airing cupboard overnight, still problems. With the remaining battery I managed to reload a clockwork backup I had on it and it seemed to start working, started charging and run for a while. It then froze. It seems the screen stops working but the vol and pwr buttons still function. Booting into recovery ALL functions work perfectly, I can run the tests (the lower screen buttons work) reload roms etc but as soon as I boot into the rom, mostly the screen refuses to work but sometimes it works for a minute or so (enough time to restore the user account after a factory reset). But after a while and always after the screen time out, nothing will work again, not even the power button. Needs a battery pull to allow it to run again.
Any ideas? I assume it is shagged. I was going to try a complete wipe and re install a new different rom. Any suggestions which one to try?
Thanks for any help.
Keith.

you said that you've pulled battery while the phone was running...you could fry the eMMC chip ("E: can't mount /cache/...." error in recovery) does your recovery show that error?

441Excelsior said:
you said that you've pulled battery while the phone was running...you could fry the eMMC chip ("E: can't mount /cache/...." error in recovery) does your recovery show that error?
Click to expand...
Click to collapse
No I am pretty sure it isn't fried. I know it is dodgy to pull the battery but since I recon the thing is buggered any way I have actually now done this dozens of times. The chip seems to be ok. How do I know for sure? I can mount and unmount the cache from within the revolutionary loader screen but it doesnt do anything or give any messages. Where would I see the error message?
I just loaded the new cm10 rom. It seems to work sort of ok running this though it did freeze once and the screen behaves funny. presses take a long time to register - like it is running really slowly and single taps usually respond as long pushed. I am going to try an old rom (3.5) with a full wipe and see if it is any better with this.
Thanks.

Also I had this error and also because of wather and the phone maked like yours. But....I put older recovery non touch clasic version of 4ext and after I recover a older backup and start working normal.... I think this you can do and don't cost nothing.
Sent from my HTC Desire S using Tapatalk 2

Water damage conundrum

I was pushed into a pool with my Nexus 5 on me. I took my phone out of my pocket right away but it was submerged in water of course. I was not able to put it in rice or silica until the next day. I took apart the phone, removed the battery, cleaned lightly with 99% alcohol and put the phone in silica gel packs for 4 days. I am able to turn on the phone and boot into Android KitKat, but it shuts down immediately.
I am able to boot into recovery and flash and it stays on indefinitely. I tried wiping the phone, do a restore from backup, etc. While all the tasks of the recovery work, the phone will boot up and immediately shut down. I don't understand why the phone will work in recovery and is able to perform heavy tasks like backup and restore, but will not stay powered on in Android.
Is it possible my battery is at fault here? I noticed that even though I have it plugged into the charger, it doesn't seem to be replenishing. Or at least the is what the indicator tells me.
Any thoughts? Thanks.

rldev said:
I was pushed into a pool with my Nexus 5 on me. I took my phone out of my pocket right away but it was submerged in water of course. I was not able to put it in rice or silica until the next day. I took apart the phone, removed the battery, cleaned lightly with 99% alcohol and put the phone in silica gel packs for 4 days. I am able to turn on the phone and boot into Android KitKat, but it shuts down immediately.
I am able to boot into recovery and flash and it stays on indefinitely. I tried wiping the phone, do a restore from backup, etc. While all the tasks of the recovery work, the phone will boot up and immediately shut down. I don't understand why the phone will work in recovery and is able to perform heavy tasks like backup and restore, but will not stay powered on in Android.
Is it possible my battery is at fault here? I noticed that even though I have it plugged into the charger, it doesn't seem to be replenishing. Or at least the is what the indicator tells me.
Any thoughts? Thanks.
Click to expand...
Click to collapse
Did you try to flash 4.4.4 stock via fastboot?
https://developers.google.com/android/nexus/images
Do you have the warranty?

t-shock said:
Did you try to flash 4.4.4 stock via fastboot?
https://developers.google.com/android/nexus/images
Do you have the warranty?
Click to expand...
Click to collapse
No I didn't. Don't know why that would make a difference, but I will try it since I can do it. I have no warranty that covers water damage.