Related
My Dash recently got wet (it was my 21st birthday), and now I have some (major) issues.
For a while it wouldn't turn on, at all. Then, after taking everything out (battery and sim card) and letting it sit for a few days, then recharging the batteries, my Dash turns on as soon as I put the battery in (rather than waiting for me to push the on/off button).
Then all my alarms from the past 2 weeks start to go off. As soon as I push ANY button, the Dash shuts down. End of story.
Is my beloved Dash completely FUBAR?
Thanks in advance,
David
Magic 8 Ball says: Signs point to yes
My opinion.
Remove the battery from it for 3 days.
Open it up (the phone)
Air dry the whole phone for the same amount of days.
proceed to assemble the phone back, insert the battery back.
Clear Storage command and hopefully it will set everything back to normal.
Cross your fingers.
Most likely its dead if that is happening. Probably fried some of the circuits on the board. If it is still under warrenty, you can try calling customer service and just tell them it stopped working. Don't offer up any information as to the cause.. This worked when i broke my screen.
"Customer service? Yes. My screen no longer works... Ok, we will replace it"
However, you may get dinged with a replacement fee of $100 (t-mobile) if they find that it was not the fault of the actual hardware. However, this is usually far cheaper then buying the phone again.
Interesting tho, my dash survived being fully emursed in a bucket of water. Never turned off, and still have never had any further issues. I still laff at it, i wish I coulda seen my face as I watched it sink to the bottom.
I would just call customer service and see what they say from there.
If you tell customer service what actually happened, you will have to buy a new phone. That is something I know they won't cover. Be vague and unsure of why its doing what it is doing and most likely you will be taken care of.
Thanks guys. I'll let you know how this goes (crossing fingers... but not expecting much)
I just got this tablet (to replace the garbage SGH-I467) a few days ago (Thu., May 15th). For the first couple of days it worked like a dream. However, the last 4 nights/3 days, I have been encountering some strange issues. What I will do here is describe the issues I've been having, what I have done in attempts to fix them, list some of the things I think may have caused it, and include any additional info/questions.
Before all that though, I would like to mention that I am not a developer, but I am a bit 'tech savvy' and am more familiar with/knowledgeable of technology than the average user. Also, I have spoken with Samsung tech support and even had the support guy access my Tab Pro 12.2 remotely (I will explain what I learned from that below). So, without further ado (I apologize in advance for the long winded nature of this post, but I want detailed):
The Issues:
1) Screen "flickering"—By flickering I mean that it is shutting off and turning on rather rapidly and sporadically, though inconsistently.
I first encountered the problem 3 days ago (the 18th).
Four nights ago (the 17th), before going to bed, I plugged the device into the same outlet I have used for all my mobile devices, when I woke up (on the 18th) the screen was doing exactly what I described. I hit the home button a few times and it stopped.
That night (the 18th) I plugged it back in to the usual spot before going to bed. The next morning (yesterday, the 19th), the screen was "flickering" again. I tried to press the home key a few times, as well as both the soft keys, nothing. In between "flickers" you can see the lock screen, where I have to enter a pin, but even while visible I can't type anything. So this time, to try to solve the problem, I held the power button + volume up to get to recovery and wiped the cache partition, rebooted the device, and viola, it worked again. Thinking that I may have to factory reset the device if the problem persists, I used Kies to backup all my data. I used the tablet the rest of the day, even plugged it in (in a different outlet than the one next to my bed) for a while and had no issues.
Last night (the 19th) I did pretty much the same thing, but this time, thinking that it might be an issue with the device getting too much power (the Quick Start Guide says: "Note: Connecting the travel adapter improperly may cause serious damage to the device."), I used a travel adapter from one of my other, USB 2.0 devices (the only difference between the adapters is the output: 2.0 = 5.0V—2.0A vs. 3.0 = 5.3V—2.0A, and output was specifically what I was concerned with). This morning (the 20th) the problem has returned, but now includes my second issue: the hard home button and both soft keys, back and recent apps, no longer function. So I immediately tried to wipe the cache partition and reboot, but this time it didn't work. Thankfully I had anticipated this yesterday and had that Kies backup, so I wiped the entire device back to factory settings. But alas, it was unsuccessful and the problem persists, including the loss of button functionality, with the exception of the power and volume buttons.
It is important to note that when I first got the Tab Pro 12.2 and set up the lock screen, I used the option that delays the actual locking of the device 10 minutes after screen timeout, but set it so that if I lock the screen with the power button it ISN'T delayed and immediately locks. That being said, a couple of times when the "flickering" stopped long enough to momentarily use the device, I was able to enter my pin and unlock. But when the screen starts flickering again, it locks the device, so the power button must be affected as well. Though since the first factory reset of the device, I haven't set up a pin. I have done several factory resets and none of them have worked. The best result has simply been limited (no back, recent apps or home key) and momentary functionality. I tried using Kies to do emergency firmware recovery, but every time I click the option it disconnects the device.
When Samsung tech support remotely accessed by device (I used one of the momentary functionality windows to download the required application) the agent was able to utilized soft and home key functionality, even though I couldn't. This tells me that it was hardware related, not related to UI/software.
So there are a couple of things I think may have caused/contributed to the problem:
The first, which I vaguely touched on above, is the power issue. Perhaps I have shorted the device out somehow. The outlet I use to charge things while I'm sleeping is on the wall behind my bed, so I have to use a common extension cord, one that has 3 outlets at the end. I have a light plugged into that and in the past have charged both my SGH-I467 (AT&T Note 8.0) and my SGH-I747 (AT&T S4 Active) with that cord and outlet. That is the only place I have charged the SM-T900 overnight, but none of the other power sources I have used have caused these issues.
The second possibility is a virus some sort. I have never used the Samsung app store on any of my other devices, but in order to update the Hancom Office suite I had to. Since I had an enjoyable time using it to that end, I decided to see what else I could find on Samsung's store. I downloaded a couple of things (the "Official Captain America game" and a couple wallpaper/theme apps) and was looking around the store to see if there was anything else I wanted to download. I found several apps that had reviews claiming they were trojans, so I immediately checked the reviews for the apps I had downloaded, but none of them had similar reviews. However, that does not mean they didn't have viruses.
So, what do the resident Android gurus of XDA think about these issues?
I tried searching all over the forums and elsewhere online for people having the same issues, but couldn't find anything. Have any of you ever encountered something similar to this?
Until recently, I hadn't ever heard of anyone getting a virus on an Android device. Are they common? What is the nature of Android viruses?
If these issues do have something to do with overcharging/shorting the device, how can I mitigate that problem? Tonight when I charge the tablet, instead of using the USB 3.0 charging cable, I am going to try just using the 2.0 cable. As I understand it, that can be done by simply plugging it into the right side of the port. Hopefully that will stop exacerbating the problem.
Again, I apologize for such a long winded post. I would like to thank you all in advance. If ever I have problems with an Android, you guys are the ones to ask!
*UPDATE* Before I started typing this I was attempting to run the Kies 'Firmware Upgrade and Initialization', as opposed to 'Emergency Firmware Recovery', to see if that too would disconnect the device. Unfortunately it said that my device needed to be charged first. So I shut it down and plugged it into a surge protected strip and began typing this post. Occasionally I would go over an check the charge. While it was shut down and charging I was able to use the home key to bring up the green battery. Once the charge looked like it was about 75% complete I turned it back on and lo and behold, the "flickering" issue looks resolved and so does the button issue. I can go back, enter the recent apps and task manager, and use the home key functions. For how long this will last, however, is unknown. I guess we'll see in the morning. I'll post what happens tomorrow.
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
RE: Case?
dodo99x said:
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am not using a case or cover at all...
same issues here
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
VeinkWiles said:
So, what do the resident Android gurus of XDA think about these issues?
Click to expand...
Click to collapse
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Mike Austin said:
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Click to expand...
Click to collapse
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
VeinkWiles said:
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
Click to expand...
Click to collapse
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Re: developer settings; display touches
dottat said:
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Damn! That's an outstanding idea! The only downside is that last night I sent the tablet to Samsung's repair department, so I can't test that out. But once I get it back, if the problem persists I will definitely be doing that first. Thanks for the advice dottat.
Fw:Re: developer settings; display touches
mikegbg said:
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
Click to expand...
Click to collapse
Hey dude, check out dottat's reply. He's got a really good idea that may shed some light on the source of the problem. Unfortunately, I can't try it out. If you do it, let me know how it goes. Maybe you can take some screenshots? Either way, hopefully you can get something out of it.
Hello all...
Ive had my m8 since the end of april. It's worked and charged fine up until last Thursday. I started to notice that when I have it plugged in, the led will come on and it'll say it's charging, but it doesn't actually charge, most of the time it continued to decrease. After playing with different cables and the gsam app I found that it won't actually charge unless I put pressure or weight on top of the end of the cable that is plugged in to my phone. Even then, I have to mess with it quite a bit and hope when I wake up, it'll be charged.
This has become increasingly frustrating every time I plug it in to charge now. Has anyone else experienced this problem with your device? Also does anyone know of a fix, besides paying the $149 to get it replaced with my ATT insurance plan? I really just want to wait until around April and get a new phone, preferably with a snapdragon 810 processor, however, at this point, I don't think I can make it until then.
mattprice86 said:
Hello all...
Ive had my m8 since the end of april. It's worked and charged fine up until last Thursday. I started to notice that when I have it plugged in, the led will come on and it'll say it's charging, but it doesn't actually charge, most of the time it continued to decrease. After playing with different cables and the gsam app I found that it won't actually charge unless I put pressure or weight on top of the end of the cable that is plugged in to my phone. Even then, I have to mess with it quite a bit and hope when I wake up, it'll be charged.
This has become increasingly frustrating every time I plug it in to charge now. Has anyone else experienced this problem with your device? Also does anyone know of a fix, besides paying the $149 to get it replaced with my ATT insurance plan? I really just want to wait until around April and get a new phone, preferably with a snapdragon 810 processor, however, at this point, I don't think I can make it until then.
Click to expand...
Click to collapse
If you are. Comfy tearing the phone apart the charging port is on its own board/cable.
Are you sure nothing is buried in the port preventing you from pushing the cable the entire way in?
dottat said:
If you are. Comfy tearing the phone apart the charging port is on its own board/cable.
Are you sure nothing is buried in the port preventing you from pushing the cable the entire way in?
Click to expand...
Click to collapse
Nothing is blocking the inside, I checked. It will plug in all the way fine, but I have to put pressure down on top of the cable where it connects to the port to make it work.
Ive taken mobile devices apart before, but from what I've seen on ifixit, it looks like a pretty daunting process for the m8 and I'm not so sure I'll be able to do it without damaging anything else.
I was just seeing if anyone else may if had this same issue and they knew of a way to get it going. I'll probably just have to take it in and get it replaced
mattprice86 said:
Nothing is blocking the inside, I checked. It will plug in all the way fine, but I have to put pressure down on top of the cable where it connects to the port to make it work.
Ive taken mobile devices apart before, but from what I've seen on ifixit, it looks like a pretty daunting process for the m8 and I'm not so sure I'll be able to do it without damaging anything else.
I was just seeing if anyone else may if had this same issue and they knew of a way to get it going. I'll probably just have to take it in and get it replaced
Click to expand...
Click to collapse
To be honest if the phone is otherwise in good shape they will probably warranty it if it doesn't look like abuse. Just make sure you are stock, locked, and s-on.
mattprice86 said:
Nothing is blocking the inside, I checked. It will plug in all the way fine, but I have to put pressure down on top of the cable where it connects to the port to make it work.
Ive taken mobile devices apart before, but from what I've seen on ifixit, it looks like a pretty daunting process for the m8 and I'm not so sure I'll be able to do it without damaging anything else.
I was just seeing if anyone else may if had this same issue and they knew of a way to get it going. I'll probably just have to take it in and get it replaced
Click to expand...
Click to collapse
If the usb port is not moving around out of the ordinary, then dirt is usually the culprit, and sometimes it gets hardened around the metal contacts with each attach / detach of the usb cable. Try using a tiny pin to carefully clean away the dirt from the metals.
I found it to be pretty useful in the past when i had likewise problems.
mattprice86 said:
Hello all...
Ive had my m8 since the end of april. It's worked and charged fine up until last Thursday. I started to notice that when I have it plugged in, the led will come on and it'll say it's charging, but it doesn't actually charge, most of the time it continued to decrease. After playing with different cables and the gsam app I found that it won't actually charge unless I put pressure or weight on top of the end of the cable that is plugged in to my phone. Even then, I have to mess with it quite a bit and hope when I wake up, it'll be charged.
This has become increasingly frustrating every time I plug it in to charge now. Has anyone else experienced this problem with your device? Also does anyone know of a fix, besides paying the $149 to get it replaced with my ATT insurance plan? I really just want to wait until around April and get a new phone, preferably with a snapdragon 810 processor, however, at this point, I don't think I can make it until then.
Click to expand...
Click to collapse
So in your country you don't have warranty? Even if there is a 12 months since April... Let me think?...
Sent from my HTC One_M8 using XDA Free mobile app
dottat said:
To be honest if the phone is otherwise in good shape they will probably warranty it if it doesn't look like abuse. Just make sure you are stock, locked, and s-on.
Click to expand...
Click to collapse
Agree, that unless the phone has obvious signs of physical damage or water damage, AT&T will replace it (with a refurb) under warranty, and it won't cost the OP anything. AT&T also typically won't check for software mods. Although, its a good idea to return to mostly stock, just in case.
redpoint73 said:
Agree, that unless the phone has obvious signs of physical damage or water damage, AT&T will replace it (with a refurb) under warranty, and it won't cost the OP anything. AT&T also typically won't check for software mods. Although, its a good idea to return to mostly stock, just in case.
Click to expand...
Click to collapse
Yea I was able to get a free replacement. They listed it as a defect. It comes in next Thursday, thank god. I just ran the 4.4.3 ruu. I'm going to try and relock my boot loader, but I don't know if I'll be able to BC I can't get it to recognize when I plug into the computer anymore.
Thanks for all the help
mattprice86 said:
Yea I was able to get a free replacement. They listed it as a defect. It comes in next Thursday, thank god. I just ran the 4.4.3 ruu. I'm going to try and relock my boot loader, but I don't know if I'll be able to BC I can't get it to recognize when I plug into the computer anymore.
Click to expand...
Click to collapse
Try to go to Windows Device Manager (with phone connected) find the device, and pick the option to manually select drivers, the select the MTP USB driver (not HTC drivers). For some reason, I lose fastboot/adb connectivity, and have to do this very frequently (even when no changes on the phone).
But this is only if you really want to relock the bootloader. Which is not stock whether its UNLOCKED or RELOCKED. Unless you want to do the mod to change the flag to LOCKED.
In any case, good to hear they will replace the phone (and rightfully so, as it seems to be a hardware failure not caused by physical damage). So good luck.
redpoint73 said:
Try to go to Windows Device Manager (with phone connected) find the device, and pick the option to manually select drivers, the select the MTP USB driver (not HTC drivers). For some reason, I lose fastboot/adb connectivity, and have to do this very frequently (even when no changes on the phone).
But this is only if you really want to relock the bootloader. Which is not stock whether its UNLOCKED or RELOCKED. Unless you want to do the mod to change the flag to LOCKED.
In any case, good to hear they will replace the phone (and rightfully so, as it seems to be a hardware failure not caused by physical damage). So good luck.
Click to expand...
Click to collapse
Thanks. The problem isn't detecting the drivers, BC I've connected it and used adb tons of times, but now, since it takes a lot of time messing around to charge, I have to do the same when I connect it to the comp.
I think I'll probably just leave the bootloader unlocked and s-off. I read some other threads about having issues turning s back on. I have it on 4.4.3 unrooted. Thanks for everyone's help
mattprice86 said:
Thanks. The problem isn't detecting the drivers, BC I've connected it and used adb tons of times, but now, since it takes a lot of time messing around to charge, I have to do the same when I connect it to the comp.
Click to expand...
Click to collapse
Gotcha. I completely spaced on the (obvious) fact that your connectivity issues could be related to the original issue of the damaged MicroUSB port!
Driver issues are so common, its like a knee jerk reaction for me now!
Not sure if it would help but you can get ADB WiFi on play store
Sent from my Nexus 7 using Tapatalk
Thanks. I had heard about adb WiFi but I want exactly sure what that was. I always just connected my phone to the computer before this happened.
I think I'm just going to leave the boot loader unlocked and s off. Seems like it shouldn't be a problem going back to ATT, as red point mentioned
It seems like the charging port is the cause
Update: I received my replacement phone last Thursday and mailed back my old one today. I did leave the boot loader unlocked and kept it s off, so we'll see if ATT tries to charge me for it. I'll let everyone know after they receive it.
My replacement was still running 4.4.2, so instead of going thru htcdev again to unlock the bootloader, I immediately downloaded, paid, and ran sunshine. It worked like a charm, unlocking my boot loader and turning s off. From there, I changed my cid to supercid, ran the ATT 4.4.3 ruu, then the Dev edition 4.4.4 ruu, then finally the Dev edition 5.0 ruu.
It's so great not having to mess with my phone for 20 min just to get it to charge. I also ordered a charger with Qualcomm quick charge 2.0 and it charges my phone amazingly fast.
This a strange one to say the least. I have a Nexus 7, Zenfone 2 ZE551ML and a Padfone-x so I'm certainly an Asus fan and I decided to buy the ZE550 16gb Zenfone 2 for my son. He loves it. I took it from him for a few days and put it in my bedside drawer. Yesterday I took it out to charge it with my THL 5000t charger (this is the same charger I use on my padfone-x without any issues). I left it charging for about 4 hours, tried to switch it on and found a crack in the lower left third that stretches almost all the way across the screen with that purple ink stain blob running up the left side. There is ZERO physical surface damage to the screen. Nothing. Not a scratch or blemish on the outside of the phone, front, back, sides, screen NOTHING.
The screen is blank now when it's "on" and it's also relatively warm. I can only conclude that the phone overheated and damaged the screen. Did a Google search and found something similar with a Zenfone 5 from last year I think. But I've never heard of it apart from that. The phone is less than two months old so it's still covered by Asus USA but the problem is that I'm in Africa and won't be back for another month or more. Unfortunately I get the feeling Asus are going to dispute my problem based on using a thl charger and/or saying I damaged the phone. I've ordered a screen anyway but I'm going to take it up with them tomorrow and see if they step up. Has anyone else encountered this type of issue with any brand before?
I have no issue with other chargers. i have owe many phone.and many chargers. All of them work but without quick charge option
I suppose its possible that the battery got too hot, expanded and cracked the screen but not the panel...
Wow is all I can say. Asus are replacing the phone completely. No quibbling, just a description of the circumstances and the physical condition of the phone along with the serial number. Excellent, excellent customer service. I'm impressed.
Now, since I'm returning it, can someone tell me how to flash/wipe this phone via pc without a screen?
I would say your best bet is to get the phone into fastboot mode and go from there. This is pretty easy since all you have to do is hold the volume up button while it powers on. In fastboot, you can issue commands from your computer while the phone is connected by USB.
Look in the [index] or around the forum for a guide on flashing either stock or something similar and it should go through all the steps of getting ADB/fastboot working and go through the basics of fastboot. If I find the time, I'll try find one for you in case you don't know where to start.
funkencool said:
I would say your best bet is to get the phone into fastboot mode and go from there. This is pretty easy since all you have to do is hold the volume up button while it powers on. In fastboot, you can issue commands from your computer while the phone is connected by USB.
Look in the [index] or around the forum for a guide on flashing either stock or something similar and it should go through all the steps of getting ADB/fastboot working and go through the basics of fastboot. If I find the time, I'll try find one for you in case you don't know where to start.
Click to expand...
Click to collapse
I'll try it and get back to you. Thanks.
Hi, my apologies if my HTC is in the wrong forum, not sure where the Desire would fit, if anywhere.
Nonetheless this is a useful phone to me and worked fine till the day I had to jump in a lake to save my 5 year old boy from drowning. Naturally didn't have the time to remove the phone from my pocket before jumping in the lake. Kid was fine after swallowing some water but phone "swallowed" a lot of water. Let it dry in a bag of rice and baking soda for several days to fully dry. But when trying to turn it on, the screen just flickers non stop. However when connecting it to the computer using a USB cable, I get what appears to be a boot screen (see pic in address below). Phone was rooted and run CyanogenMod 7. Maybe someone that's familiar with the procedure could guide me? Tried a couple of the options shown but to no avail. Old but still decent phone, would like to get it working again. I've transferred the sim to another phone and I've saved the micro SD card. Just need to get the phone to boot again. PS: could the battery be toast? Maybe it got shorted when I first tried to turn the phone on while still wet?
Any help is appreciated.
I'm too new here, won't allow me to post external links. Please go to h-t-t-p://tinyurl.com/p4dmgej (remove dash from http)
I'd say leave it to dry naturally for a week or so and try again. If no joy then you could try a new screen but it's probably something really tiny and sensitive that cannot be replaced..
Glad you saved your boy!.
Sent from a stolen HTC M9
It's been 2 months. But I did make a crucial mistake: I tried to turn the phone on while still at the lake. This likely caused more damage than it needed.
However I suspect the issue is with the battery. It won't charge past 3.85 volts. And the display works just fine, once I press the key combo to enter the boot screen as seen in the pic above. Will try and track one down locally, hopefully a shop will be able to test it a battery in the phone before I buy it.
And yes, the boy was fine. But it was a close call. it is amazing how quickly something can go wrong. I neglected the lake rule of staying within arm's reach. Let this be a lesson to anyone with small ones: it only takes seconds for things to go badly wrong, even at a supposedly safe, man made lake intended for kids.
PS: 2 months prior an adult died on the same lake after falling off his boat. Another lesson: invest in swimming lessons. Scary stuff, indeed.
Right, i thought you were seeing that over usb via sdk or something.. You could always try opening it and inspecting for blown components. What damage can be done.. It's already useless.
I still think it's worth leaving it to dry naturally.
Sent from a stolen HTC M9