Hey guys,
So last night I get home late, been diggin' the bop at local jazz joint, had some 4 Roses in me, entered the bedroom using my Qtek 9090 as a flashlight so I don't have to wake up my girlfriend by turning on the light. She had been a little sick earlier so had a bucket with some water by the bed, just in case. I make too much noise so I do wake her up, she recognises me and wants to move over to make room; struggling with blankets, she accidentally hits my hand. There goes my Qtek, falls on the matress, bumps to the side, down next to the bed, splashes into the bucket.
Damn.
So here's my problem.
My Qtek was completely immersed in clear water for a very short time. I let it dry, taking out the battery and SD card to allow air in and out of the device; but now, I can't turn it on. With the battery inserted, the flashing led on the top right is not working and I only get the 'Qtek 9090' boot screen. It's stuck there, backlight doesn't work. With the battery taken out and the device on mains power, the led on the top right is red but I get nothing on the screen. Hard reset not working either.
What do you guys think? Is it worth getting this repaired? Or does it seem that everything is damaged?
Thank you thank you
Sniffles
Robrecht
I would suggest to keep the battery off the device, open it, blow all the corners with hairdryer, close it, and test your luck. If it's under guarantee, I would do the same, and if it does not work, send it back.
Related
So, today I was getting in the car right. My phone was battery back-less because I broke the old one and was waiting for a new. I live in south florida, and it's spring-time. The morning was a bit humid but I thought nothing of it. I turn my phone on and try to listen to some music right, but it wont let me open WM player. So I go and open something else and try to exit out. The X button won't work but the touchscreen does... weird. I then try to restart the phone. I keep holding the power button but no luck! So I'm worried and go to pull the battery out but to my surprise see a little condensation on the back of the phone. I pull the battery out and when it goes off I see CONDENSATION ON A RIGHT STRIP ON THE SCREEN. I go to turn it back on and try to do the same stuff. No buttons work, the X button and lock softkeys do not work, no hardware buttons do what their supposed to but they light up, turn the backlight on and everything!!!! I can't even do input with the touchscreen keyboard even though the screen works. Some programs I can and can't open. The phone was on for a MAXIMUM of 5-7 minutes, if that! I'm very surprised because It worked last night what leaves me to believe "Moister damage". Am I correct or is it a software problem. I cant hard reset because no way to type input. Haven't tried the sequence or mymobiler yet.... can someone tell me if the culprate to the death of my phone is moisture damage? I'm really angry now......
froggylover1345 said:
...... can someone tell me if the culprate to the death of my phone is moisture damage? I'm really angry now......
Click to expand...
Click to collapse
seems like sort of thing that could happen if moisture entered into your phone as that could cause electric shocks and considering the inner hardware and electrical components are very delicate even the slightest exposure to water vapors or moisture is a enough to damage them especially considering your scenario where you had no battery (and i am assuming you didn't have back cover either or you did?) but regardless as far as my understanding is this behavior seems in line with what you are thinking.
So no way to fix it.... I'm now phoneless. I'm so mad at myself right now....
I live in SWFL and unless you dropped the thing in a puddle I cant imagine the humidty down here doing that to your phone. Did you drop the thing in a puddle? The back cover is by no means air tight so I dont think NOT having a back cover did that too your phone.
Turn the phone on and plug it into your charger and see how long it stays on. There's a trick discussed here that talks about wrapping the phone up in paper towels and then putting it in a bowl of rice for 24 hours. That should suck any moisture you have in your phone out. Just do a search in the forum for "rice" or something.. I dont know.
Good Luck Though!!!
This is the thread you want to read http://forum.xda-developers.com/showthread.php?t=669472
i wouldn't think humidity would cause that much damage.
have you installed any recent app(s) that you might suspect causing these issues?
I thought the SAME THING. That's why I thought nothing of it! I just did a hard reset on it the night before so no apps installed. I did go on Android but, I do that about 1-2 times a week. Only reason I think it's moisture is because of the "white smoke" I saw thinking it was condensation. It wasn't really taken care of for a few hours because I was in disney. When I got to the hotel I put it in paper towels. The touchscreen works, and I can open apps on the menu but not use them. Wont let input through. No hardkeys work either. I'm gonna try a hard reset.
I WAS WRONG! I just did a hard reset, and it fixed the problem! Had to do it the button sequence way but it worked! The last thing I did on it, the night before was go on Android. Everything functioned well their and had no problems. What I'm guessing is I got a bad boot or something that stopped some drivers from working. I figured this out by trying to download mymobiler on the phone so I could do a hard reset and it wouldn't let me open it because it wasn't signed with a trusted certificate. Whew.... this is A HUGE RELIEF.
ight just wanna ask everyone since the topic is mainly on "Moisture damage" i have a habit of using my phone as a shower radio...no i dont put it in the shower, i leave it on the sink farthest away from the shower stall, my question is....will this do any damage to my phone because of the moisture and heat!? because this is the 2nd time ive done it and i dont wanna continue until i get a word of approval from you guys
XERO_Racer said:
ight just wanna ask everyone since the topic is mainly on "Moisture damage" i have a habit of using my phone as a shower radio...no i dont put it in the shower, i leave it on the sink farthest away from the shower stall, my question is....will this do any damage to my phone because of the moisture and heat!? because this is the 2nd time ive done it and i dont wanna continue until i get a word of approval from you guys
Click to expand...
Click to collapse
I wouldnt think it would damnage the phone. Unless you actually submerge the unit or dump water on it it should be able to withstand the humidity. It's not like its in the moisture for hours and hours just a few minutes while you shower. Keep your fan running while you shower and that should help even more; although the fan should be on while you shower anyway AND for at least 5 minutes after you shower (little known fact) to protect the drywall and structure of the bathroom.
Humid place
Where I live some times in summer we have 98% of ambient humidity!
So it´s almost impossible to have anything dry here
froggylover1345 said:
So, today I was getting in the car right. My phone was battery back-less because I broke the old one and was waiting for a new. I live in south florida, and it's spring-time. The morning was a bit humid but I thought nothing of it. I turn my phone on and try to listen to some music right, but it wont let me open WM player. So I go and open something else and try to exit out. The X button won't work but the touchscreen does... weird. I then try to restart the phone. I keep holding the power button but no luck! So I'm worried and go to pull the battery out but to my surprise see a little condensation on the back of the phone. I pull the battery out and when it goes off I see CONDENSATION ON A RIGHT STRIP ON THE SCREEN. I go to turn it back on and try to do the same stuff. No buttons work, the X button and lock softkeys do not work, no hardware buttons do what their supposed to but they light up, turn the backlight on and everything!!!! I can't even do input with the touchscreen keyboard even though the screen works. Some programs I can and can't open. The phone was on for a MAXIMUM of 5-7 minutes, if that! I'm very surprised because It worked last night what leaves me to believe "Moister damage". Am I correct or is it a software problem. I cant hard reset because no way to type input. Haven't tried the sequence or mymobiler yet.... can someone tell me if the culprate to the death of my phone is moisture damage? I'm really angry now......
Click to expand...
Click to collapse
Just let it do some thorough drying out. I had an old Kaiser i dropped completely in the toilet at work..lmfao You know i was pissed but..after some thorough drying and TLC, it just started wrking again like nothing ever happened. I let my father have the Tilt cuz i had already had a replacement one sent to me. Just told them i lost it. cuz u say water, they like warranty voided..lol Still wrks to this day, its his new toy till he get that new EVO 4g for sprint. he got the tilt to work with a prepaid sim card. im like dayumm..he showing something new..lol
demandarin said:
. I had an old Kaiser i dropped completely in the toilet at work..lmfao You know i was pissed
Click to expand...
Click to collapse
No pun intended right?
Hiya,
my Desire HD got wet in the front pocket of my fleece, not drowned just some droplets of water that got inside the Otterbox case and into the phone. I did try and turn it on before I realised it had got wet, it wouldn't power up.
I removed the phone from the Otterbox and dried everything and tried to turn it on again as there was only very slight traces of moisture apparent. There was condensation and a couple of little drops of water inside. I discovered there must have been enough moisture to short out the battery as there was a little residue mark above the contacts on the inside of the casing. I then noticed the liquid indicators had turned red.
I removed the battery cover and dried the phone gently using an electric room heater for hours, I also put the phone in a bag of rice for a couple of days.
I tried to power it up again after a few days in the rice and it wouldn't start up. I measured across the battery contacts with a multi meter and found the battery was open circuit, so I know it must have shorted. Hoping that this was the only damage I bought a new replacement battery. When I fitted the new battery nearly a week later and switched on the phone, everything seemed to be fine but the display seemed to flash, and as I had a Leedroid rom installed I heard R2D2 chirping and could see the device start to boot up as normal on the screen. Then the display went dark and hasn't worked since. I stripped the phone and cleaned a couple of patches of residue, one of which was right in the lcd connector.
Now when I try and start the phone there is no display, the phone vibrates once when I hold in the power button. Approximately 40 or 50 seconds later I can hear R2D2 making his tweeting noises which always happens on boot up. I didn't think it took so long to hear R2D2 but maybe the phone is checking the file system or something now, and I just can't see it.
It may be that I just need a new screen & digitizer to repair the phone, but I can't tell what might be on the display - maybe it's the phone unlock screen asking for my pin number etc. I can't see any image on the screen, that you would normally see when the baclight is faulty, I have tried to view it with a desk lamp, but it's just black. The capacitive buttons at the bottom don't seem to have any effect, perhaps they are not enabled if it's sitting at the password screen, if it is at that screen.
The l.e.d's don't light up at the top when I turn it on or plug in the charger.
I might have also damaged the volume key switch/ribbon slightly.
What would you do with this phone, any advice on how I could proceed ?
Would it be working just with no display, as R2D2 is squeaking(Leedroid rom has this when the device boots and has an animation of a pc booting up with the post screen) ?
No l.e.d's is a bit worrying and it doesn't seem to know when on charge etc. but perhaps they only work once the phone has booted, I can't remember DOH!
I just thought I would ask, as there are a lot of knowledgeable people on here and it might be possible to save my droid.
Grateful for any help or advice
kind regards
Barry
So during my holiday my HOX got splashed with a bit of water from a wave. The battery was running on fumes and, when I looked at it, the phone was dead. It did turned on later while in my pocket and I happened to press the power button.
I let it dry on rice and nothing. I made the potential mistake of trying to charge it so it would heat up and it wouldn't charge. I then bought another mobile and, just to try it, I took opened the HOX and hoovered. Nothing.
Miracle happened yesterday when, just for kicks, I tried the charger again. It power up!! Everything seems fine, no visible screen damage, wifi works, everything works just fine but... screen won't respond to touch on the very bottom, say, the capacitive and menu buttons (the ones just above the capacitive ones).
What do you guys think? Is the screen dead there, maybe I didn't put the screen back properly or should I wait as some moister might yet be there?
Cheers!
Kutusov said:
So during my holiday my HOX got splashed with a bit of water from a wave. The battery was running on fumes and, when I looked at it, the phone was dead. It did turned on later while in my pocket and I happened to press the power button.
I let it dry on rice and nothing. I made the potential mistake of trying to charge it so it would heat up and it wouldn't charge. I then bought another mobile and, just to try it, I took opened the HOX and hoovered. Nothing.
Miracle happened yesterday when, just for kicks, I tried the charger again. It power up!! Everything seems fine, no visible screen damage, wifi works, everything works just fine but... screen won't respond to touch on the very bottom, say, the capacitive and menu buttons (the ones just above the capacitive ones).
What do you guys think? Is the screen dead there, maybe I didn't put the screen back properly or should I wait as some moister might yet be there?
Cheers!
Click to expand...
Click to collapse
This is a flashback to me. Same thing happened to me few weeks ago - first 3 bottom buttons stoped working, and now 7 days ago part of touch screen is not working anymore. I am going to replace lcd+digitizer+frame, lucky me nothing else need to be fixed. And IMHO trying to heat closed HTC when water was in it doesn't make a sense as a water will condense (as it is closed) so it would make more damage. Oxidation sucks :/
I do have the SIM slot opened but yeah, that's a tinny opening, not much space for water vapour to escape... it's been a few weeks since I thought it had died though, it's pretty amazing to me that it came back at all. Some tough phones, these...
Anyway, I think I'll try to take the screen out again, I wasn't too careful putting it back in because I saw it wasn't charging or powering up or anything at all.
My wife dropped her Moto Z Play into a puddle and the bottom half of the phone was submerged. Initially the phone continued to work and she wasn't concerned, so she did not properly dry the phone off. Eventually the screen stopped working and she plugged it in before she told me about it. I dried the phone off as best I could, removing the cover and taking out the sim card. I placed it into rice, where it has been for about a week now. The phone will not power on at all, it makes no noises when plugged in (the phone usually makes a high pitched, very quiet tone when charging). The forward facing light does blink white when it is plugged in but it makes no other response. I do not know what that means and I have not seen anything about it at any forums. The battery is not removable. Any suggestions on what to do now and any explanation on what the blinking white light means? Thanks
same exact situation...
Same thing happened to a friends' moto z play this weekend when she was tubing at a local river. The battery had died so her's was not on when it hit the water and was only submerged for a few seconds. She dried it off best she could and plugged the charger in to see if it would charge. It just blinks the white light on the front three times and then the battery lightning bolt graphic displays momentarily and repeats this. Phone will not turn on as well. We haven't left it on the charger for any period longer than a minute or two. Found this thread, looking for similar situations hopefully for a solution.
FWIW - we did find this youtube video water testing the Z play and it seems as though this phone should be relative water resistant.
since i haven't made 10 posts I cant include url but if you enter watch?v=dxvLKskmkg8 after you tube dot com you can find that video. THIS IS NOT SPAM and very relevant to this thread.
Thanks for sharing @ABTF16 anyhow... Hopefully someone knowledgeable to this scenario will be able to provide an answer at some point in the near future.
ABTF16 said:
My wife dropped her Moto Z Play into a puddle and the bottom half of the phone was submerged. Initially the phone continued to work and she wasn't concerned, so she did not properly dry the phone off. Eventually the screen stopped working and she plugged it in before she told me about it. I dried the phone off as best I could, removing the cover and taking out the sim card. I placed it into rice, where it has been for about a week now. The phone will not power on at all, it makes no noises when plugged in (the phone usually makes a high pitched, very quiet tone when charging). The forward facing light does blink white when it is plugged in but it makes no other response. I do not know what that means and I have not seen anything about it at any forums. The battery is not removable. Any suggestions on what to do now and any explanation on what the blinking white light means? Thanks
Click to expand...
Click to collapse
Quite weird!
It passes the water test with no problem.
Speaker working fine camera working fine touch working fine.??
And in the video he said that the Motorola claims that it has advanced nano coating technology which can protect it from accidental spills or splashes.
Trust me, my Moto X Force went the same way
One second drop in water, it was upright and it was only the bottom inch and for less than one second as I immediately removed it, continued to work for the rest of the day but died in the evening and would not turn on
Sent to Moto and returned with 'unit beyond economical repair' along with a photo and half of the components were corroded
WTF!! one second in water
Don't get me wrong I love Moto's (I have a Z Play now) but they are rubbish if they even get moist
If your phone gets wet you are supposed to leave it off for at least a day in a dry area. I left mine in a hot car with leather seats. You need to let all the components dry out. You could achieve the same affect with a hair dryer.
Turning it on, or trying to charge it is no good idea.
Sent from my Moto Z Play using XDA Labs
ABTF16 said:
My wife dropped her Moto Z Play into a puddle and the bottom half of the phone was submerged. Initially the phone continued to work and she wasn't concerned, so she did not properly dry the phone off. Eventually the screen stopped working and she plugged it in before she told me about it. I dried the phone off as best I could, removing the cover and taking out the sim card. I placed it into rice, where it has been for about a week now. The phone will not power on at all, it makes no noises when plugged in (the phone usually makes a high pitched, very quiet tone when charging). The forward facing light does blink white when it is plugged in but it makes no other response. I do not know what that means and I have not seen anything about it at any forums. The battery is not removable. Any suggestions on what to do now and any explanation on what the blinking white light means? Thanks
Click to expand...
Click to collapse
I had accidently taken my MZP under a running tap and with the pressure the water went all the way inside my MZP but then at first it worked fine for 1 hour or less. Then it switched off automatically and started rebooting. I still managed to get it on then it started to show results like camera stopped working and fingerprint scanner stopped working. I shaked the phone and then removed the water which was remaining. Then I managed to switch it off and then put it in rice for 2 days. After that its working fine, only fingerprint scanner was not working but yesterday it started working and now everything is back to normal. Try isopropyl alcohol which is 99% pure alcohol and then dip your phone in and then put it again for 2 days in rice. I hope this works. However I just needed rice to do its work and mine worked. Hope yours work but if its damaged go to the service centre asap.
:good:
Hey there. I'm a bit new to this side of XDA. Honestly with how long I've been AWOL from this site nothing is familiar anymore. How time flies. Well my first post back in years couldnt be more unfortunate phone wise, I've had my Z2 for a couple of months now and as a mechanic it's been treated like all my others phones prior, rough. I've been locally recognized as the guy who has a new phone every couple of months because he can't not shatter a phone. An expensive hobby of breaking phones. Well luckily I didn't shatter my Z2. I just water logged it. Gotta change things up right? So here's where the interesting problem comes in, I let the phone sit in rice for 30 hours, switching the rice out half way through. It acted up like you would expect in the first couple of hours but then stopped. When I pulled the phone out I scraped the rice out of all the books and crannies and tried to power it on, to no avail. Dead battery I assume, so I plug it in. Charge icon pops up, a sign of life! How glorious. So I let it sit for a minute as I assume the battery probably dropped below minimum voltage when the LEDs were freaking out. Went back to the phone, held the power button and no screen, but "Hello, Moto!" So at this point I'm convinced the screen is dead, so I force it off with the volume down method and pry off the screen. To find what? More water. Good Lord. This phone is incredibly water resistant just in reverse. So I do the only thing that makes sense at this point, I remove the ribbion connector from the board for the display and put the phone back in new rice as 2 separate pieces. I then leave it in there for another 30 hours switching the rice halfway. Bringing us to now. I took the phone out, cleaned all the rice out of the 2 pieces and off the remaining adhesive and connected the ribbion back to the board. Plug the charger in, and again, charging logo. But then I hold the power button and the TMobile splash screen pops up! Then the screen goes dead and once again, "Hello, Moto!". But whats different is now when the boot sequence is finished I can interact with the phone and it works, shake for flashlight, enter my passcode (just by feel cause I'm good like that, ladies hmu), and the button responds with vibration. The phone is working but no screen. So at this point I'm sure, the display driver is done. I murdered it in cold daylight. So I shut it off and start looking around for new screens, in the midst of this I knock the phone and accidentally hit the power button, and it starts to boot up. T-Mobile spash screen, screen death, "Hello, Moto!", and nothing. Now that seems weird. Why would it work twice on the TMobile splash? So I decide I'll try putting it in fastboot for S&G's. Restart, put it in fastboot and the screen stays on. Beautiful and clear as day, all buttons work, everything reads fine, but, if I go to boot it or do anyother action than "retart bootloader", the cycle continues. T-Mobile, death, hello Moto, nothingness. Now at this point I'm okay with the phone being dead, it's fine, but I'm intrigued now. What would cause the screen to work just fine when in the bootloader and the TMobile splash screen, but die when it boots? The phone is very clearly working in the background. I logged in, used Google assistant, used the flashlight, pressed buttons on the dialer, all without the screen but with haptic feedback and audio. Could the graphical side of the main partition just be corrupt, or maybe the display driver is dead but the main board interacts with it differently during fastboot? I'm far from being knowledgeable on the hardware side of these things but I'm really genuinely interested in getting feedback here from anyone with an idea of what is going on. I'll post a video here in a half an hour or so when I finish up with dinner.
AFAinHD said:
...snip...
Click to expand...
Click to collapse
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.
Uzephi said:
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.
Click to expand...
Click to collapse
Well see I would think that as well but the screen does work. Just only in fastboot, and the boot logo.
I got the video here.
Fastboot is a pretty low level and most likely uses basic hardware. I mean really what is there to see but a simple background with some text. Once you load the OS then all the hardware and it's drivers into play. Have you tried booting into safemode? Ultimately you'll probably have to repair or replace, but there could be a slim chance that there's still a little moisture in there and it still has a short somewhere.