Develop Bugs

Phone got wet, now boots into black screen and no response

Title sums up my problem. I've got a T-Mobile Touch Pro 2 and I've got some water on it a few weeks ago. The wet seal on the battery and phone are both pink. I got a new battery and now the phone boots. It goes through the pink little T-Mobile screen, and then onto the black screen that says the phone wasn't shut off properly and this and that. It gives me the option to press the Volume-up key to do a hard reset, or press any other button to turn off or restart. The problem is that pressing volume-up, or any other key does not do anything. In fact, the only way to turn the phone off at this point, is by taking the battery out.
Can somebody please advise as to what I can do with this phone that is only 2 months old?

I believe the life/fate of your phone will depend on how quickly you acted right after the phone got wet. For instance did you immediately remove the battery and place the phone under a light or in a window where it could dry out? I even here sticking the phone in a bag of rice will help to draw out moisture. But if the phone has sat for weeks I would say it's safe to assume you phone has seen its last days. If you can take it apart and leave the individual components out to dry out and clean off any corrosion with alcohol and re-assemble. I wish I could offer better advice... Good luck it brings a tear to my eye to hear about a touch pro 2 broken down
Edit: Sorry I didnt realize you said that the screen does display. I would definitely try taking it apart and thoroughly cleaning things out and leaving it apart to dry for awhile. sending it in will get you no where (since pink water marks) and chances are HTC/T-mobile wont even send your broken phone back.

8gkl said:
Title sums up my problem. I've got a T-Mobile Touch Pro 2 and I've got some water on it a few weeks ago. The wet seal on the battery and phone are both pink. I got a new battery and now the phone boots. It goes through the pink little T-Mobile screen, and then onto the black screen that says the phone wasn't shut off properly and this and that. It gives me the option to press the Volume-up key to do a hard reset, or press any other button to turn off or restart. The problem is that pressing volume-up, or any other key does not do anything. In fact, the only way to turn the phone off at this point, is by taking the battery out.
Can somebody please advise as to what I can do with this phone that is only 2 months old?
Click to expand...
Click to collapse
You could also try connecting the phone to your pc, and run mymobiler. When the screen goes blank, maybe you will be able to have access to your phone through the program. You could back up whatever you needed, and would tell you if the lcd went out. Just a thought. Sorry to hear about that though.

Mymobiler says that it needs activesync functional in order to work. Activesync doesn't work for me. I tried it anyway and it wouldn't detect. Is there a stock htc touch pro 2 rom out there that is in NBH format so that I could stick it on my SD card?

The very same thing happened to my Touch Pro 2 a few days ago too!
My story is different. I had never had any water damage to the phone. On the 23rd of March, I installed the Deepshining ROM. It worked fine. The next morning, I went into T-Mobile to get the new HTC HD2. I turned off the Touch Pro 2 to retreive the SIM card, and then have been using the HD2 since. I tried to turn on the Touch Pro 2 for a few nights now. It just stays at the T-Mobile Stick Together screen until the battery is dead. I tried a soft reset while it was stuck on that screen, and received the error message just like the OP.
Can someone help me too? I am really worried that the phone is bricked. I can't get a new Touch Pro 2 under warranty since I am running on a custom ROM/radio.
I'm not sure if I can blame Deepshining. None of my previous ROM installs ever failed on me, and people seem to be installing the roms just fine.

Are you trying to conquer my thread? It's nice and all that you've got the same problem, but thread hijacking is frowned upon.

Sorry, the phone is physically damaged. There's not much you can do at this point.

Just as an update. Somehow, after installing the deepshining mod and trying it after a few days, it works fine now. It became very responsive, and I was able to install the original tmo 6.1 stock rom. Everything works fine, the only problem is that some of the physical qwerty keys either don't work or draw more than the needed letter/number. The power button doesn't function to turn the screen off, which really is about the only bummer. Everything works fine. Yay.

Screen died?

Last night I was out and during the night I pulled my desire z out of my pocket to find that the screen was dead, the soft touch buttons were still lit up and working but no display. I pulled the battery and tried to reboot and no luck, you can hear it booting and even unlock/receive calls and txts etc once it has booted up just the screen stays blank the whole time so have to do everything on feel.
Essentially does this just mean my screen has a hardware fault? is it worth trying to fix? I assume the only option would be to purchase a replacement screen and dissemble and reassemble it?
(warranty is not worth it as I live in New Zealand and would have to send my phone back to the UK where I bought it from, also I have dropped it quite a few times so probably voided anyway...)
Thanks in advance for any input

Does it never display anything? So not even a flash during boot or something?
Because then it is probably a hardware problem.
Since the soft touch buttons do still work I think there might be a little crack or something in the flat cable that connects the bottom half with the top.
Maybe you could check whether you can see if the cable is broken or not?
The best thing to do then is to look for a replacement and try to fix it yourself or bring it to a shop where they can do it for you.

No it never displays anything, completely dead the whole time. The touch input is still working though as I answered a phone call this morning on it by making the usual gesture just without being able to see anything. Doesnt seem to be anything wrong with the cable itself as far as I can see. Yea might have to get someone to have a look at it.

My phone is acting the same. I dropped my phone in the pond before, but pulled battery out on time and had it in rice for a day. My phone was still working for about two weeks after that incident. I dropped it and had one little crack at the top of the screen and about a week after that it died when I had a water balloon fight with the phone in my pocket. D;
Do any of you know if the replacement lcd screen/digitizer for the Desire Z would work for the G2?

I had the same thing happening to my G2 screen, only it was intermittently working for a little while, then just completely died and wouldn't work. It was doing this crazy flickering thing then the back light wouldn't go on at all. If I held the phone at a certain angle in the sun, I could see that the pixels were indeed working on the display, but there was no backlight to make them normally visible.
So I purchased a replacement screen from ebay and carefully followed the directions on a youtube video for a G2 take apart. Its not a hard task to take apart and get down to the screen itself. It was rather easy. After putting it back together the screen still didn't work! Sounds work, i can also receive calls etc. But the screen still doesn't work!
Is there any way that this could be a software issue?

Oh and PS, I believe the LCD replacement would work for both the desire Z and the G2. They are identical phones after all right? I'd say its a safe bet. The screen I bought was only 35 bucks. Didn't think that was a bad deal.

Another dead screen or something else?
Few days ago my phone fell of the couch onto a rug - no big deal, so far it has survived much worse, but when I picked it up, the colors were all messed up - overly green and red. Tried restarting - no luck. Everything worked fine, except the colors, but then the screen turned of completely. I could hear notifications, phonecalls, but the screen was dead. After some tapping on the screen, it turned on again - with ****ed up colors. Then started flickering and was gone again. Few more times I could turn it on by tapping before it was dead for good.
Figured, after all these drops it survived, maybe the screen connector is a bit loose. I mean, I could sometime get a contact when tapping it, so I dissasambled it completely, secured all the connection, put it all back tougether and fired up - same thing: dead screen, phone working.
Has anyone had such problem before? Is it screen that is dead, or connector or... I have no clue... I would like try to fix it on my own, with some replacement parts I could get on ebay - but, what gave?

[Q] power button not working/always on

hi guys i have a real bad problem...woke up this morning and my desire wouldnt wake up when pressing the power button...screen turned on after i put the charger in but when the auto screen off turns the screen off i cant wake again until i attach the charger.also with a battery pull the phone turns off but then when i put the battery back in the phone automatically boots without touching the power button
thanks

bailz2506 said:
hi guys i have a real bad problem...woke up this morning and my desire wouldnt wake up when pressing the power button...screen turned on after i put the charger in but when the auto screen off turns the screen off i cant wake again until i attach the charger.also with a battery pull the phone turns off but then when i put the battery back in the phone automatically boots without touching the power button
thanks
Click to expand...
Click to collapse
My money is on a hardware failure. Do you have a stock ROM ?

hey yea i went and unrooted and reinstalled my carriers stock ruu....still same problem.looks like taking it back to the shop for them to fix

Hey actually exactly one week ago my Desire started the same exact thing, and I could not find help anywhere. Best info I can find is that it might be moisture, but at least for me I don't think that is the case.
I ended up taking the whole phone apart (been taking stuff apart all my life, but i was still nervous) to clean it out since I've had dust in the screen for a while... I think I cleaned it out pretty well, but did not take the plastic tape off the button. This did not immediately help, but after playing with it for a while it now works most of the time, but is quite sensitive usually.. the button "presses" before it mechanically "clicks".
Anyway, If you were to become desperate enough to try this, I would recommend pulling that black plastic tape off the button when cleaning, then stick it back on. Good luck
I've been lusting after the Sensation anyway

yea im not into pulling stuff apart that i got no idea about...took it back still under warranty n its getting sent in for repair...now stuck with a piece of **** samsung omina icon....windows phone sucks the big one very hard...ill be going back and asking for at least an android as a loaner while its in for repair

ohh well that's good that it's still under warranty. I was actually using the camera at a beach during hurricane Irene and that night the power button went berserk.. continuously turning the screen on and off... before eventually just staying "pressed" all the time again. So maybe the moisture theory isn't all that far fetched in my case (I was at a beach the first time it happened, but never went near the water)
Currently trying to get a broken Desire on ebay to harvest for parts :/

Moisture - Htc Desire Power Button.
Hello,
I've met with that problem.
I've unscrewed the device, I've remove the black tape, and I've used a cotton swab to clear it.
But the problem was solved, but later withing the 24hrs, It's back to auto on/off without pressing the button.
I would like to know, Should I remove the yellow transparent tape on the button for cleaning?
Thanks.

[SOLVED] Black Screen Issue

Hi. I am not sure this is the BSOD problem that others have had.
I bought a second hand i747. It came with 4.3. It will work fine for a few minutes when first turned on, then the screen will go dark. The menu and back buttons stay lit, and the touchscreen still works, the LCD just cuts off.
If I hit the power button, it sleeps the phone. When I hit again, the screen will come on, but only for about 5 seconds, then it's black again. Everything works, just black screen.
Is it possible for it to overheat or something? It doesn't feel hot at all, but if I turn it off and leave it for awhile, it will again work for about 2-3 minutes, then only about 5 seconds at a time again.
I swapped batteries, and it's the same. The battery had pink on it. I opened it up, and none of the other stickers showed water exposure, and the board itself was clean.
It has stock 4.3, and is not rooted.
I did go to phone settings and turned off the "darken screen during calls" checkbox.
I am wondering if the proximity sensor heats up and shuts the screen off. Grasping at straws I suppose.
Any idea of how to fix this?
Thanks

Perhaps a bad capacitor in the digitizer/lcd assembly? My TV had an issue with a bad capacitor that would cause the screen to blank out after a few minutes???
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I'll try swapping boards in it later, and maybe at least narrow down if it's the board or the screen assembly. I have an extra proximity sensor I could swap, but it doesn't seem like it's that to me.
thanks, will post more after the board swap

Update: I switched boards (different carriers), and I could not replicate the problem in either phone. I had hoped that would show that either the board or the LCD assembly was bad, but I didn't learn anything useful either way.
I put the boards back in their respective bodies. It still happens now, but not as often. It also appears to be totally random. I did switch batteries in the problem phone, and it doesn't seem as bad. I will try another battery switch and see if that helps it more.
When the screen goes dark, the menu and back buttons are lit. When it went out last night, I could see that there was still some faint background light that I can't see in the day. I pulled up Youtube and did a video, and when the screen went dark, I could still see movement, but couldn't make anything out. So, the phone is still going in the background.
If I push the power button, it sleeps, then push it again, and it wakes up just fine. Sometimes I have to do that 4 or 5 times for the screen to stay on. Sometimes it goes dark after 10 minutes of use, sometimes a half hour, sometimes just a few.
Any help is appreciated.

Well, right before throwing the phone into the wall, I noticed a partially removed liquid exposure indicator. I pulled the phone apart to check the motherboard.
In the process of taking it apart, I forgot to take out the SD card. In so doing, it pulled the sim/sd card module off the motherboard. Low and behold, there was a very light corrosive glaze in a few spots under the module.
So, I got out the 99% IPA, and a toothbrush, and cleaned the whole entire board. Since then, it seems to be working fine.
I don't know exactly what part getting cleaned fixed it, because I just cleaned the whole board.
Anyways, maybe that'll help someone with inexplicable issues downstream.

Thanks for following up with how you fixed the problem. In retrospect, water damage makes sense.
I dropped a Captivate into an ice chest full of melted water last year. I immediately pulled it out and the phone was mostly okay for a while but then the microphone didn't seem to work so well and occasionally the right third of the screen wouldn't respond to touch until I cycled the screen on and off. The water damage sticker and phone interior showed no signs of water.
I will probably sell the old captivate but with full diclosure about the history. Would have been nice if the seller had done the same for you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Thanks, I should have thought of it sooner, but it didn't seem to have any signs of water damage otherwise.
I ordered the 99% IPA online, because I couldn't find any locally. It works wonders with previously wet boards. You might be able to bring it back.

Got an interesting problem.

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.