Related
Hello,
Yesterday my Diamond had died I think
It was frozen and I did a soft reset, screen stays black and nothing happend anymore.
Pulled out the battery, put it back in, and try to turn it back on. It vibrates after a few seconds but the screen stays black.
every help would be great!
Greetings!
Michiel
It might be low on battery so have you tried recharging it?
when i connect it to the power cable nothing happens, the enter button isn't lighting up.
when i connect it to my pc I can browse to the internal storage normally, but it won't charge the battery.
now I'm really confused...
Take out your battery and sim card and leave it out for about 20 minutes and then put it back. During this time, also have your device plugged in (without the battery).
Reflash Everthing
I've pulled out the battery + sim for more than 30 minutes, reloaded the official HTC rom and still the screen is black.
It starts up, vibrates, makes the start sound but the screen remans black.
Now I want to put the orginal HTC SPL back on it, but it doesn't completes the procedure.
Anyone? thnx again!
I got exactly same problem
this has happened to me twice during the past year. the screen was black, although it did vibrate when I turned it on. both times it fixed by itself overnight, very strange.
what I saw is that both times it happened after a long ride with the car, I suspected that due to the prolonged exposure to air conditioning, when I took it out it condensed on the warm motherboard (it was used as a GPS) and some shortcircuit occured.
Unfortunately, 3 weeks ago, again after a long trip with the car, when I took it out it 'died' in 5 minutes (with 100% battery), did not even vibrate anymore when powered on, and never woke up eversince. It is now in service since the 15th of August, with a status on the website of the official HTC service company in Romania (Cirma Electronics) of: "waiting for spare parts" for 5 days...
My guess is that either the MB or the screen fried because of a design issue which caused the condensed vapors to form on some contacts inside...
It sounds as if the device is 100% operational with the exception that the LCD is out. Correct? Or, have you experienced other problems? Try powering up you Diam, then shine a flashlight directly at the screen. If you can see your interface then you have a dead backlight & need a new LCD. If you do not see the image then the LCD itself is defective {Apparently a common problem} & you'll need a new LCD. Either way you should contact HTC service as you have a 2 YR warranty.
@ cocomic: Where is Your Diam on these trips, A windscreen mount or a console mount? If it's a console mount, most likely you have an air vent blowing directly at it & that's just asking for moisture build up. But, if it was a "moisture" issue as you stated, then HTC would not be fixing it for free. They would see the oxidation from the moisture & say that it's your fault for getting it wet, & charge you out the ass for that part. {That's why ALL devices have LDIs} If you use a windscreen mount, then you have your device sitting in the sun for a long time! Sunlight KILLS LCDs!!! It may be more likely that you burned your screen by having it exposed for long periods. But it's probably just the issue that many people have. If you go to HTCforums you will see a lot of people have LCD issues.
If you have warranty return it to the store.
Humblehippie said:
@ cocomic: Where is Your Diam on these trips, A windscreen mount or a console mount? If it's a console mount, most likely you have an air vent blowing directly at it & that's just asking for moisture build up. But, if it was a "moisture" issue as you stated, then HTC would not be fixing it for free. They would see the oxidation from the moisture & say that it's your fault for getting it wet, & charge you out the ass for that part. {That's why ALL devices have LDIs} If you use a windscreen mount, then you have your device sitting in the sun for a long time! Sunlight KILLS LCDs!!! It may be more likely that you burned your screen by having it exposed for long periods. But it's probably just the issue that many people have. If you go to HTCforums you will see a lot of people have LCD issues.
Click to expand...
Click to collapse
I have a windscreen mount, the air vent doesn't blow directly on the device. furthermore, the sun couldn't have burnt the LCD as the last time it died (for good), it was 11 PM.
the phone is in service and has the online status on their website: "the phone is in the lab, waiting for spare part". this means that whatever the issue is, hopefully it's gonna be fixed under warranty.
nevertheless, I find it appalling that a device built in 2008 has huge design and construction faults causing it to malfunction whenever used in a car with the AC turned on...
I'll keep you posted on the outcome
later edit: update: I've just got off the phone with a secretary at the htc service. apparently the motherboard fried and they ordered a new one. from what she said only the case will remain the same, it may be that the lcd display was caught in the chain reaction . the bad thing is that I will probably have to wait for another week, the good thing is that I will get an almost new phone...
as they didn't say anything about the LDI, it's either that the condensed vapors didn't touch it, only the circuits, or the fault did not come from the humidity... one can only guess...
It may not have been condensation that caused the problem. It could be that your Mainboard had a problem that was amplified by your trips in the car. Either way, you get a factory refurbished Diamond, & that's jus' sweet. I have to call them this week about my Diam because my front cam isn't working. I never really use it, but if it's covered, I might as well make them flip the bill while I can.
no, really, do that... i remember that a few weeks before the 'incident' my rear camera stopped working, too... i never payed too much attention as i considered it to be just a spb mobile shell software issue which would have eventually gone away after a hard reset or something...
you are probably right, my MB was slowly dying, organs failing (i have just watched a house md rerun, sorry )... if you have the possibility to have it checked while it's still in warranty and have the camera fixed while at it, why not?
I'm moving this, as it has no pertinece to the original topic. This link; http://forum.xda-developers.com/showthread.php?p=4476473#post4476473 is a post I started to see if anyone else had these issues. Read the update on the first post
Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.
So, my girlfriend's D3 went for a brief swim (but, any swim is too long a swim) a few weeks back. She immediately snatched it out of the water, took it apart, and put it rice for, roughly, 48hrs. I took it out of the rice, put it back together, and booted it up. To her/our relief, it worked fine. Zero issues with it. So, she's been using it (and LOVING it, it being her first Android phone), without issue, up til today. For some reason, when she hits the power button, the screen comes on, but she can't unlock it. Sometimes it'll work, sometimes it won't. She can't answer calls because of this. I installed No Lock from the Market, but the screen still won't respond to touch input about 50-75% of the time. So, D3 Gurus, what could be the cause and can we fix it?
P.S. She just updated her phone today, OTA, if that might matter.
The ota update wont matter. There is still water in there. This same thing happens with the ipod touches and iphones, water damage then screen turns on but no response.
But, it has been working fine for weeks since it took a dip.
It may have not come in contact with any critical hardware until now. That's all I can think of. Try a replacement screen, battery, anything.
ourtut said:
The ota update wont matter. There is still water in there. This same thing happens with the ipod touches and iphones, water damage then screen turns on but no response.
Click to expand...
Click to collapse
A verizon rep told me this morning the ota could've caused my phones ear piece to stop putting out sound. Idk if that's true but I completely denied the possibility water could've got into it and she thought it was the ota until I told her I reprogrammed it like 3 times. Then again it was a woman.. hm.
Sent from my DROID3 using XDA App
Also check the phone and batt for water detectors. a un damaged phone/batt will be white or white with red x's. A damaged phone/batt will blead a red die onto the white square
The water detectors are definitely goners, but we've known that since it happened. I just don't see why it worked perfectly for roughly 3 weeks, then all of a sudden decides to sh!t the bed today.
No one else have any ideas?
Well, it had gotten to where it would respond to input at all, so I booted into recovery and did a factory reset. It seems to have helped, at least somewhat, because now the screen will respond again, but still not always.
To try and clarify: when she wakes the phone up, the screen will either respond 100% to each and every input (like a good screen should) or give us the middle finger and refuse to acknowledge any inputs, leaving her stuck at the lock screen. It's feast or famine. All or nothing. Once she gets it to register that first touch, it's golden...til she locks it again, then the cycle starts over.
Does she charge it through the wall or usb plugged into a computer? I have an issue where if my phones connected to my comp the touch is all over the place and I basically can't unlock it or drag the notification bar down unless I disconnect it.
Sent from my DROID3 using XDA App
Wall. I'm not sure if she's ever even hooked it up to her Mac. lol
stick1300 said:
Wall. I'm not sure if she's ever even hooked it up to her Mac. lol
Click to expand...
Click to collapse
Lol okay. Sorry I had no advice. That's something I experienced w/ my d3, tho.. other than that never had the issue. But I also never gave my d3 a bath. I'm surprised my girlfriend hasn't given hers one yet.
Sent from my DROID3 using XDA App
My girlfriend is a one person demolition team. I'm just going to go ahead and file an insurance claim.
My girlfriend's N1 has gradually developed some problems. At first the headphones were not being recognized properly. Then camera stopped working. Now that I've taken a look at it the flash light does not work either. If you call someone, 4 times out of 5 the screen goes blank and you cannot end the call. Sometimes this happens when receiving calls as well.
I was using CM7 before and no additional apps were installed. Tried with or without SD card, rebooting, resetting to factory defaults, putting another ROM, restoring to factory ROM.
The symptoms:
- any camera app starts with a black screen and later throws wait/close dialog
- flashlight apps seem to work but no light is coming out
- headphones do not get recognized, tried 4 brands, compressed air, pushing, pulling, pressing. Not a lint issue.
- immediately after pressing a call I get a black screen which I can come out of by pressing a random combination of keys
I tried moving the camera and LED modules with my finger but nothing happened.
Everything else works: calls, trackball with led, bluetooth, wifi.
I had a similar problem with the flash and camera and it was fixed when I swapped out the main board which also has all the ports your having problems with
Sent from my Nexus One using Tapatalk 2
That sounds unfortunate because the original seller has now closed the shop: site is offline, amazon and ebay products are delisted, does not respond to email.
Even worse, I'm located in Germany and bought the phone here, but I don't really speak the language well enough to contact consumer protection authority and even the HTC support site is all in German. Original box and warranty are in my home country. Sounds like a recipe for disaster.
I've written a mail to HTC support since GooglePhone has closed shop as well.
Since I'm still on a rant, touchscreen has been acting up since day one, upon heating it registers wrong touches, but this is already a known issue.
It was a nice phone while it lasted, but in hindsight I wouldn't recommend it to anyone anymore. It still looks like new fwiw.
locorito said:
I had a similar problem with the flash and camera and it was fixed when I swapped out the main board which also has all the ports your having problems with
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
same problem
Hardware
Its hardware issue caused mayb y dropping the N1
so try to replacing ur main board or mayb u can get it repaired if u have a good engineer around u
Thank If my reply helps u ..
Just as an update, the issue with all these phones is the ribbon cable connecting headphone jack, camera, proximity sensor and perhaps [front] speaker. It's probably an easy replacement and the part cost is around 25-40$. The cellphone repair guy said that he has done it a lot of times for this phone type, so it's probably a production/engineering issue.
A month ago I ended a call with Verizon custotmer service only to find the touchscreen on my D4 had stopped working. There was no ghosting, no other problems I knew of at the time besides a speaker that wouldn't work. Rebooting didn't work. Factory reset didn't work. The only thing different was that the phone had recently upgraded to Jellybean. Now when the phone is rebooted the WiFi automatically comes on. I could still use it attached to the lap dock, or by using the keyboard to bypass the touchscreen. I switched to my backup phone and searched for answers.
I ended up getting a new-to-me D4 from eBay. I took the slider half of the phone with the screen and switched the whole thing to my D4. Phone
was fixed, seemed to be fine.
Today rooted my phone. All was well until I was playing a game, then again the touchscreen just stopped working. I am at an utter loss, what happened to the touchscreen? Neither one was dropped, both had screen protectors on and were in cases. I was using the phone at the time both times. The picture is clear, screen uncracked. I just can't get it to accept touch input anywhere on the screen. And the WiFi is turning on again when I restart the phone.
I have never seen this happen before on any other phone, I have heated the glass and pressed where the flex cable is in case of a loose connection, nothing happens. Removing the sim and SD cards didn't help either. Any suggestions or fixes? Will replacing the glass again fix it, or should I try a factory reset again? Stock ROM, rooted jellybean, using atrix lap dock to type this.