Alright, I had an all black G1 that broke and I sent it back to HTC for repairs. Got it back worked perfectly, Had it since August then gave it to my dad since I felt bad for him (LG Vu). Rooted with latest radio and Danger SPL.
This activity just recently started happening. The phone if powered on wouldn't wake up from sleep and now when I try to power it on the phone's backlight just turns on. No vibration or G1 Screen.
He always had wifi on and screen at 100% but I don't see how that could of damaged the phone considering HTC did stess tests on the device before it was even released.
I took out the old mobo and put in a new one and it seems to work but I really don't want to give up my G1 mobo since my G1 has a dead camera flex port.
obviously sounds like there is something wrong with the motherboard but could this be fixed?
I can't access fastboot, recovery or normal phone.
only random times it will decide to boot.
Any ideas?
*******BUMP*******
Related
I have done a reasonable amount of searching on this and have not found anything specific to my problem so figured I should post a question.
I have an issue with my Dimaond when it gets hot generally either using Wifi or Phone Data connection that the screen goes out. Basically everything goes to the left side of the phone so if you hit the Task Icon in the top right corner you get the Start Menu. Phone is basically useless at this point and you have to wait for it to cool down. Has happened since day one and is generally worse when using it when charging. I was watching Utube on it the other night 5min video while on AC charge and it went out. I am running Dutty 2.5 Rom and 25.07 radio have tryed 25.08 and 25.05 no difference was happening when the phone had orginal HTC ROM as well. Also will happen on a long call if the screen is on.
Basically feel issue is hardware related and maybe faulty screen still under warrenty so wanted to know peoples opinion on weather I should send back. Problem is will take a couple of weeks and I don't really wnat to wait that long if I can help it. Also assume it would be best to flash standard ROM back, should I do anything with HARDSPL eg should this be changed back as well if I send it back.
And before anyone says it I have tryed searching this topic and have found lots about HOT dimaonds but nothing related to screen going out at the same time :-(
Thanks
I had this issue in my JasJam (Hermes) whre the screen would simply go white after a while of use and I would have to leave it for a while for it to work again.
Unfortunately it sa hardware issue and you should claim a warranty repair on it
I can't see how this could be a software problem so I figured it must be the screen eg hardware related. Would be nice to know if anyone has had the same issue with a dimaond... Seems we may be spending some time apart, just hope it doesn't take long to fix..
I've had the same issue
http://forum.xda-developers.com/showthread.php?t=428976
My first device had been replaced recently (i.e. today) by my network provider (o2) and the new device seems to work without any problems now even if it's "hot".
(i.e. default screen adjustment + creating heat by activating the phone, wlan, bt + recharging it)
I sent an email to HTC regarding the fault and they said it would have to go back for a warrenty repair. I brought it through a resellar so has to go back to HK from NZ so will be away three weeks uurggghhh... Just seems odd I don't have any physical damage on the screen but hte problem has been around since day one as I remember having the problem the first day I got it. Juyst seems to be getting worse and is easily reproduced by usiung utube over wifi gets hot and it is all over. Just wondering if I should put an offical ROM from HTC back on the device before I send it back as I currenty am running Dutty ROM, what do you think....
i put the original rom back on and they still found out the the rom had been flashed, and would not repair on warranty
yep, i also asked about this problem
http://forum.xda-developers.com/showthread.php?t=438733
there are some youtube video's of how the phone behaves
my phone seems to do it less frequently since stopping using panosha's rom
im using alpha zero 7 at the moment..
i've also noticed that it isnt necessarily a heat issue, my phone does it completely at random
yesterday i found though, that when the phone did the alignment issue, i gave it a good shake.. and hey.. its all aligned again?!
maybe it was just a fluke, it hasnt freaked out since..
holding thumbs
Hey,
I also have the same screen problem, but my Alignment goes to right.
If I press on the left side, a press on the right side is recognized.
Good to know that Im not the only one with this problem.
greets doena
I got my phone back a week ago replaced the screen has been away for over two months, complete disaster, anyway all sorted now and I have not had the problem since....
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Minus-1 said:
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Click to expand...
Click to collapse
Hardware's fault ? Most likely not. I will give u an example of why I think it was software related. My device ran hot as well but I simply switched roms and now it's the complete opposite. Your most recent device most likely come with a different Rom in the phone.
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.
Alright so my g1 screen has stopped working properly. It still works some times but when I attempt to swipe to a new screen the whole thing gets shakey and stops working and in order to get any response from my g1 I have to press down hard and then swipe. I have tried switching roms but nothing any ideas???
It may be a hardware problem then, have you dropped your phone or damage it in any way?
Thats what I was thinking.. I may have dropped it a little to hard. Is it possible something just came loose in there??
Yes, it is possible. I just had to get a new phone from T-mobile because I dropped my old one.
ok heres my problem. happened about 7+ days ago... well i took it off my computer charger and the screen was messed up when it was closed but when i opened it "Flipping keyboard out" the screen worked fine... so posted on here i had this issue... I at first thought it was a battary problem so i purchased 3700 MaH Tripple life battary... once i got it 2 days ago same problem yet worse.... so heres how it looks
~Turn On Phone
-No T-Mobile Screen Showing
-once Rom Loads it shows yet its Fuzzy like its missing pixels but cant be the problem because i never dropped it.
~Rom Loads
-Screen Still Fuzzy or Scribbly if that helps... can do some basic functions can mount it when I hibernate it and turn screen back on... but doesnt do much
From there tried going into BootLoader "Camera+Power"
Took out battery a few Times Placed it back in
bootloader will come up with backlight but thats it so its a black screen... cant make any Functions.
I can however get into Recovery Mode... yet it looks Fuzzy aswell...soo
what Im asking all of you guru's is... "is my phone bricked..."
Running SuperBad CM5 1.2.5 Test 4 currently not sure if i installed Danger SPL and I cant Check... i had the radio 2.23.02 etc... please reply dont wanna spend 150$ for a new g1... when there could possibly be hope
*Bumping* i had to bump my last like this aswell... Moving out of state in 7 days so Kinda wanna Fix this issue a little Faster Can anyone take a Look Into This
You're phone is not bricked. Sounds hardware, though, not software. You can either warranty if you still have one, or open it up and make sure all cables are securely connected. If both of these fail, you're in the market for a new G1.
ok so what kinda screw driver do i need lol.. i know sounds n00by i used a eyeglass one that seems to be no help... looks like a allen wrench..?
You're going to void the warranty by opening it. Recovering your phone back to stock and sending it in will most likely get you a replacement if you're still under warranty. If you want to disassemble it, you can try this video hxxp://youtube.com/watch?v=3PdhXx3g9nU just replace hxxp with http.
I've replaced my phone twice, and each time I get another they extended my warranty. I've had it since Nov 08 and my warranty is still good for that reason. You might wanna check if your warranty is still good before opening it.
It does sound hardware related but since you can get to recovery can you try a wipe and see if that will do any good.
Hi!
I'm trying to fix my Google Nexus One replacing damaged hardware from an accident it suffered months ago. So far, I've changed the flex cable ribbon, the gps antenna, the lcd display and the digitizer.
After changing all of that, the phone seemed to work fine, but the desktop dock connection wasn't working because the connector at the mainboard was damaged. I tried to fix it solding it with tin (VERY BAD IDEA...) and instead I got the motherboard damaged. Somehow, the bootloader wouldn't boot after showing the X logo...
Therefore, I bough a broken nexus on ebay and replaced the motherboard. Now the phone boots fine, but there seems to be a problem when turning on the display.
Not every time that I switch the phone on the lcd display does too... 60% of the times the phone boots without showing anything on the display, and when it does show the boot process and boots, the display doesn't come back after the phone goes to sleep mode. It's like a black screen of death, but not only once the phone is booted, but also when turning it on.
I've tried changing the default HBOOT to blackrose,switching between different ROMS, or even repartitioning the sdcard with no success. I know that most of you would think that I should stop trying to fix the phone and get a new one, but I really want to fix it, it means a lot to me (and I'm also learning a lot from this!).
I'm kind of stuck now... I need your wise advice... what do you think is causing that behavior? The motherboard? The LCD? Any advice on what to do to fix it?
Thanks for everything!
Sounds like the connection between the LCD and board.
Sent from my Nexus One using xda premium