Related
I don't know what caused this.
I got my G1 today. It worked for probably 2-3 hours perfectly fine.
I had an app freeze (either Barcode Scanner or Lock 2.0) and had to do a full hard reset.
Now, whenever the phones screen darkens or I put it to sleep manually, it WILL NOT come back up.
I have factory reset three times now to try and get this to work.
When the screen is black, all buttons on the phone still light up and so does the LED indicator up top. I had my phone set to use a locking pattern screen at one point during one reset to test out and when the screen went black, I was still able to try and log in by doing my pattern. It unlocked, but still showed nothing on the screen.
Please help!
I've tried:
Turning Wi-Fi off
Turning 3g Off
Disclaimer: Yes, I've searched. I can find other users with the same problem but none of them seem to have a solution.
Phone is NOT ROOTED and has the factory ROM.
Update 1: Update: It only freezes/blacks out when I try to wake the phone from one of the front key buttons.
If I'm sliding to unlock, it seems to be fine.... (but if I've already tried to open from the front it doesnt)
Update 2: If I mash all the buttons in random orders for about a minute or two it seems to come back. Anyone have any idea?
Update 3: I'm thinking this has to be an issue with none of the buttons waking the phone up when closed. If I lock the phone with the "END" key, and then click the front "END" Key again, nothing happens. If I slide the phone open, and click it twice - the phone wakes up.
Update 4: Confirmed update 3. Phone will not unlock via front keys unless it's slid open (or open enough to trigger).
I would really, really appreciate help with this.
Hate to bump this, but I've added some detail on the top and bottom. Have to leave for work, hopefully someone might have an idea by the time I get back.
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Karolis said:
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Click to expand...
Click to collapse
Removed the SD card and rebooted the phone.
No change ( still acts the same way ).
Did you factory reset after or was it an instant change?
I don't mind losing data to fix this.
supremeteam256 said:
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
Click to expand...
Click to collapse
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
zeabrid said:
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
Click to expand...
Click to collapse
If you use the official update you don't have to have root. There are some links on here. I'll see if I can find it for you.
https://android.clients.google.com/updates/signed-gfh-CRB43-from-CRB21.c88b03d2.zip
That should be it, but can't confirm since I'm on my work computer.
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
The link didn't work, btw.
derfolo said:
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
Click to expand...
Click to collapse
Zero water damage.
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
derfolo said:
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
Click to expand...
Click to collapse
Do you have a link to a guide that teaches how to do this (with the stock rom)? I can only see a few that're spread out.
I'm not entirely sure my phone can boot into safe mode/disk mode, so we'll see about that.
Another update: When I boot into safe mode, the same problem exists.
Edit: Just emailed HTC.
This can officially no longer be considered a software issue.
I just rooted and installed a standard ROM. Same issue.
It happens all the way at boot now, just realized this.
HTC emailed me back and told me to call them directly. Will do that tomorrow.
if I find a solution I'll post it immediately.
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
zeabrid said:
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
Click to expand...
Click to collapse
Yea it defitenly sounds like a hardware issue and needs to be fixed. Glad your getting it fixed and you'll be covered no problem.
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
zeabrid said:
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
Click to expand...
Click to collapse
To be honest I don't know the answer but would like to say they would pay for it. But they would have to let you know of the charge before they apply a charge to a credit card.
wow its weird cause im just having a similiar issue now.. in landscape mode.. phone and back light work perfectly. but one i close the screen everything goes virtually blank, everything is running perfectly just the screen light wont turn on..
will try some of your previous methods.. hopefully it works on mine..=/
thanks, for the info zeabrid
Hello gentlemen! I would like to hear your opinion about my problem, hopefully there is a good soul outhere that knows how to help me. A couple nights ago I was at the club where an asrsehole bouncer knocked my phone out of my hands while chasing some crackhead. By the time I picked up my x1 those three guards were gone. My device fell onto carpeted area and battery cover came off taking the battery with it. THe device does not have any visible physical damage, but when I try to turn it on, I only receive one vibration but nothing happens afterwards. Tried everything (soft/hard reset), it is not recognised by any pc, and it wouldn't flash a single LED just that one vibration. I'd send it to SE for repair but I have HardSPL on it and I'm unable to flash it in this condition. The boot loader isn't coming up either.... Please help me find a solution, i searched these forums but haven't met a single similar problem !!!!
Warranty would not cover dropping the phone anyway, so what's the problem ? Send it to the SE, you will just have to pay something. In case they change whole board, it's gonna be a lot.
Hmm, I just took it apart and cleaned it from inside. Noticed there is a little button cell battery next to optical joystick on the front piece.
-Is it similar to CMOS/RTC backup, does it perform the same thing in X1 as if it was a PC?
-What would happen if I temporarily disconnected it from a circuit would the device lose it's HardSPL?
Can anyone please tell me what it does for Xperia?
Ihh, why on earth did you take it apart by yourself?
If there were NO visible damages on the phone the warranty should have kicked in ... even though it says that it doesn't cover falls. If there are no visible marks on the phone, it's really really hard to prove that the device actually fell.
In anyway you should have sent it to SE.
And to answer your question ... i think the small battery is indeed what powers the flash memory when the battery empty or missing. Disconnecting it would probably have the same results as a hard reset...I doubt that the HARD-SPL would be erased.
stormlv said:
Ihh, why on earth did you take it apart by yourself?
If there were NO visible damages on the phone the warranty should have kicked in ... even though it says that it doesn't cover falls. If there are no visible marks on the phone, it's really really hard to prove that the device actually fell.
In anyway you should have sent it to SE.
And to answer your question ... i think the small battery is indeed what powers the flash memory when the battery empty or missing. Disconnecting it would probably have the same results as a hard reset...I doubt that the HARD-SPL would be erased.
Click to expand...
Click to collapse
yea how would it get erased if u took all batteries out.
Also you shouldnt have taken it apart that would have voided the warrantly compleatly!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Just send it back and say it stopped working - i am supprised a fall broke it though - i've dropped mine loads and nout has been damaged :S
but yea send it to SE center
So the phone (XT860 Bell) has problems when I unlock it the screen stays black. The phone works though cause when someone calls I can still pick up as I know somewhat where the green button is. But for the rest I can't do anything.
The only way to get the phone back is to remove the battery and restart the phone. Then it works again.
Anyone else had this problem?
have you tried hard resetting it?
No will do so. But before doing that I thought maybe there is some simple solution.
After the update to 2.3.6 things went all a bit wrong I think.
If you got this after the update, I am quite confident data wipe will solve your problem. You can try wiping cache only first - this way you won't lose your configuration and might solve the problem. The update supposedly wipes cache, but maybe that didn't work properly while you were updating. Enter stock recovery and give it a try.
Hey thanks for the help. But just did a reset. Not sure what went wrong when I did the update. Did wipe. Annnnyways. Right now it's stable. Let's see if it stays like this.
Ok sadly the reset didn't fix it. It took a whole day to go black again but still happened.
Any other solutions? I am scared that it's a hardware failure...but let's hope not cause I am in Holland.
I have the droid 3 and the same exact thing is happening to me. Sorry to tell you this but it has to deal wit the connector between the keyboard and screen. I've taken mine to get checked by a "phone doctor" and they told me that. I will tell you this now ,since it is still in the early stages, it's going to get worse to the point that it will stay black. Get it fixed by a techy or get a replacement soon. Mine reached it's point today and I am going to need to get it fixed. Hope it helps.
Johnny2293 said:
I have the droid 3 and the same exact thing is happening to me. Sorry to tell you this but it has to deal wit the connector between the keyboard and screen. I've taken mine to get checked by a "phone doctor" and they told me that. I will tell you this now ,since it is still in the early stages, it's going to get worse to the point that it will stay black. Get it fixed by a techy or get a replacement soon. Mine reached it's point today and I am going to need to get it fixed. Hope it helps.
Click to expand...
Click to collapse
Doesn't sound good man :-(......
Though it happened a lot the passed days since the reset ( knock on wood) only once. Do wonder why it happens less now.
Yea you can reset all you want it's going to go blank. I had to right the dial pad numbers with marker on the screen just to make calls. I say get it fixed or replaced soon
I've got the same issue here. I know the thread is old, but I'm from the Netherlands (just like eezdva) and would like to know how to repair this.
lucaspr said:
I've got the same issue here. I know the thread is old, but I'm from the Netherlands (just like eezdva) and would like to know how to repair this.
Click to expand...
Click to collapse
If you can't take it back and want to try to fix it yourself you need to search for a droid 3 flex cable. The one you want has the front facing camera, front sensors and earpiece speaker on it. Then head on over to ifixit for a teardown guide (sorry no repair manual yet, I plan on working on one).
I have to add that taking this phone apart to replace this part is no small feat, and it would probably be better finding a phone doctor to do it for you, or just getting a new phone.
When you buy the part, request an OEM part, I have been sent cables where the front facing camera displays sideways, or doesn't work at all. Most also don't come with the front button deflector, and that has to be transferred from the old cable.
Hope this helps
Ok . Well I don't really know what the problem is. But it went away. Actually it started I think after applying the update . I got myself another external sdcard . At a certain moment I decided to remove it and things cooled down. It now actually never happens anymore.
Well I gues you're lucky!
My screen sometimes starts all scrambled and the phone doesn't power on. Sliding the screen a couple of time sometimes helpes, but most of the time I don't really know howto get the phone working again. I think it's more stable when I leave the phone 'slided out' (don't know the right word now).
And I searched Motorolas website and found 2 reparing companies in the Netherlands. They both are authorized by Motorola, as of such I think this repair will be in warranty.
I do have to send it for repair. I don't want to take it apart because of what bitz_dv said. I'll let you know!
No Fix
When I was gone on a short holiday my college got a call from the 'authorized' motorola repair center. They can't fix my phone. I need to pay 11 euro to get it back and that's it. I tried calling them but there was no answer.
I sended my phone in on 22 may 2012 and now they decided they can't repair it. I spoke to Ted from Negri Electronics who told me to get in touch with Motorola as my warranty is still valid.
I'm a little confused, where should I go if an official repair center can't fix my phone but do tell me the repair is within warranty..
What can I do? Besides ordering the parts and take the phone apart myself..
I started my search for the flex cable... I did repair a N97 once, within the warranty period and later on sended it in and they repaired it under warranty....
Is this the cable I'm searching for:
http://www.globaldirectparts.com/Motorola-Droid-3-XT862-Motherboard-Flex-Ribbon-p/mot1040660.htm
I am from Netherlands, and have the same problem with the screen, looks like many users from Netherlands do.. coincidence?
When i jst slide out the keyboard , a little bit is enough, and the screen goes black ( black screen of death ) it doesnt power on with power button.
I looked for a flex cable at ebay, and it surprised me , that cable is also doing the front camera, and speaker... My front camera wasnt working too, and speaker made strange sounds many times, so it could be that cable, but not sure.
Check my thread, i have also uploaded a video to make it more clear
http://forum.xda-developers.com/showthread.php?t=1955892
Hello, before proceding to explain the problem I have to say a few things:
- the phone I'm gonna talk about is not mine YET, it's a faulty Xperia T I want to purchase if I find a 80% clear and cheap solution. This means I cannot try any idea you give me on it, 'cause I don't have it.
- I'm not a total noob in firmware and hardware fixes, but not yet an expert, so I'd appreciate a few explanations in the procedures you comment.
- I'm Spanish, so don't expect perfect texts from my posts
- sorry if a thread exactly like this is already solved, but I couldn't find any clear information about this problem on a Xperia device, so that's why I asked.
Now, the problem:
This Xperia T, as the owner explains, suddenly turned off and never woke up again. When he tries to turn it on it just vibrates, but no image displays. And when he plugs it on a red LED shows up (as if the phone was charging normally), but no more life signs.
Now, these are the fixes I would try:
- reset battery, because the owner is a normal user, and, as the battery is a "non-removable" piece, I don't think he tried to pull it off and on again.
- buy a new battery because this one could be damaged and non-functional.
- jtag is discarded because this happened in a stock rom, with no root, custom recovery, flashing or anything like that.
- get a new (or, at least, functional) motherboard, because this could be sudden death.
So now you could say "if you already know which could be the problem and the solution, then why you ask?". Well, what I'm searching for is opinions, what of those problems I mentioned has the highest likelihood to be the winner, because if you all guys think the most likely problem it could be it's the motherboard, then I won't purchase the phone, because motherboards are terrifically expensive.
So thanks in advance for reading all this
laumapu said:
Hello, before proceding to explain the problem I have to say a few things:
- the phone I'm gonna talk about is not mine YET, it's a faulty Xperia T I want to purchase if I find a 80% clear and cheap solution. This means I cannot try any idea you give me on it, 'cause I don't have it.
- I'm not a total noob in firmware and hardware fixes, but not yet an expert, so I'd appreciate a few explanations in the procedures you comment.
- I'm Spanish, so don't expect perfect texts from my posts
- sorry if a thread exactly like this is already solved, but I couldn't find any clear information about this problem on a Xperia device, so that's why I asked.
Now, the problem:
This Xperia T, as the owner explains, suddenly turned off and never woke up again. When he tries to turn it on it just vibrates, but no image displays. And when he plugs it on a red LED shows up (as if the phone was charging normally), but no more life signs.
Now, these are the fixes I would try:
- reset battery, because the owner is a normal user, and, as the battery is a "non-removable" piece, I don't think he tried to pull it off and on again.
- buy a new battery because this one could be damaged and non-functional.
- jtag is discarded because this happened in a stock rom, with no root, custom recovery, flashing or anything like that.
- get a new (or, at least, functional) motherboard, because this could be sudden death.
So now you could say "if you already know which could be the problem and the solution, then why you ask?". Well, what I'm searching for is opinions, what of those problems I mentioned has the highest likelihood to be the winner, because if you all guys think the most likely problem it could be it's the motherboard, then I won't purchase the phone, because motherboards are terrifically expensive.
So thanks in advance for reading all this
Click to expand...
Click to collapse
Does the red LED light stay lit up while charging? Maybe you'd want to google the "rubberband method"; it's for charging the phone when it can't charge on it's own while off.
Antiga Prime said:
Does the red LED light stay lit up while charging? Maybe you'd want to google the "rubberband method"; it's for charging the phone when it can't charge on it's own while off.
Click to expand...
Click to collapse
Yes, the red LED keeps lit up. I've searched for that method and I'll try it if I purchase the phone, thank you so much
But what's your opinion about what the problem could be? Or which is the most likely?
EDIT: this is the thread I found about the rubberband trick http://forum.xda-developers.com/showthread.php?t=1849170, but is it called soft-bricked even when no firmware/modding stuff is involved?
RE-EDIT: ok, yes, even when no firmware/modding stuff is involved (lol)
RE-RE-EDIT: but still, if it's a hardware issue then all those tricks won't work, because there's physical damage, so that's why I asked for opinion x)
In my opinion, that behaviour is 90% due to a battery that is fried.
A broken battery is not able to supply the power needed for loading the kernel (that's why you don't see Sony logo and you can't recharge).
If you're lucky you can repair that phone with 15 euros for a new original battery.
ok guys, new information:
Apparently, the owner has way more knowledge about hardware repairing than I have, so we started talking about our ideas about all this thing and he said he already tried to reset battery, and he even replace it with a new one, so the fried-battery theory is discarded. Now I (we) think the problem could reside in the power IC, but that leads to a weld repairing, and I don't have the tools to deal with that.
So the thread is almost closed with this new info, but I still accept suggestions/opinions/ideas/whatever you wanna say, even if you enjoy typing the Macarena, at least we'll laugh with that xp
laumapu said:
ok guys, new information:
Apparently, the owner has way more knowledge about hardware repairing than I have, so we started talking about our ideas about all this thing and he said he already tried to reset battery, and he even replace it with a new one, so the fried-battery theory is discarded. Now I (we) think the problem could reside in the power IC, but that leads to a weld repairing, and I don't have the tools to deal with that.
So the thread is almost closed with this new info, but I still accept suggestions/opinions/ideas/whatever you wanna say, even if you enjoy typing the Macarena, at least we'll laugh with that xp
Click to expand...
Click to collapse
If I were you, I wouldn't buy that phone.
istux said:
If I were you, I wouldn't buy that phone.
Click to expand...
Click to collapse
Now that I know this, buying that phone has lost positions in my what-to-do list, just after the "comb my turtle's hair" thing lol
Thanks for caring
laumapu said:
Yes, the red LED keeps lit up. I've searched for that method and I'll try it if I purchase the phone, thank you so much
But what's your opinion about what the problem could be? Or which is the most likely?
EDIT: this is the thread I found about the rubberband trick http://forum.xda-developers.com/showthread.php?t=1849170, but is it called soft-bricked even when no firmware/modding stuff is involved?
RE-EDIT: ok, yes, even when no firmware/modding stuff is involved (lol)
RE-RE-EDIT: but still, if it's a hardware issue then all those tricks won't work, because there's physical damage, so that's why I asked for opinion x)
Click to expand...
Click to collapse
What I thought it might be was that the battery wasn't charged. It happened to me once, so I kept the power button pressed while connecting it and after a few hours I was able to use flashtool, and keep in mind that sometimes new batteries don't come charged.
But if that's not the case, then that method won't help you.
My phone's screen just went black suddenly while i was using the phone last night. Nothing i do will wake the screen up, i tried rebooting by holding the power button, tried power+volume down also to boot into recovery .. no response. However the phone seems to be functioning as i can hear the screen lock sound. I think im stuck on the pin screen (the one to pass the boot-up-encryption). theres some vibration and feedback when i randomly press on the screen too.
The device is running Stock 6.0.1 , unrooted , stock kernel. Has this ever happened to anyone else ? could it be a software issue ?
I believe the LCD panel just went dead ..
Thanks!
Have you hooked it up to a computer and tried to see if it's recognised by ADB?
moses992 said:
My phone's screen just went black suddenly while i was using the phone last night. Nothing i do will wake the screen up, i tried rebooting by holding the power button, tried power+volume down also to boot into recovery .. no response. However the phone seems to be functioning as i can hear the screen lock sound. I think im stuck on the pin screen (the one to pass the boot-up-encryption). theres some vibration and feedback when i randomly press on the screen too.
The device is running Stock 6.0.1 , unrooted , stock kernel. Has this ever happened to anyone else ? could it be a software issue ?
I believe the LCD panel just went dead ..
Thanks!
Click to expand...
Click to collapse
I had a nexus that had a faulty screen and randomly shut off or something half the screen will glitch out and one day it just stopped working but I could hear the lockscreen sounds. Your best bet would be to send it in for service maybe its a loose connecting or a hardware issue. When mine started acting up it was a loose connecting so if I hit the phone with my hand it would go back to normal and then it stopped working. Its a common issue if you do a google search many people have encountered this
That sounds to me like a return-under-warranty job. If you were in the UK you could quote the Sale of Goods Act, which specifies that an item must be of suitable quality and last a reasonable amount of time, but in my case when I returned my faulty N5 to Google after 18 months they were as good as gold, didn't quibble, simply replaced it with a refurbished one which appeared to me to be indistinguishable from brand new.
Since by definition your phone must be very close to its warranty period, depending on when you got it, I'd start with that. This is the link I used from the UK - maybe different if you're elsewhere, but you should find a link called "Get a call from a hardware specialist":
https://support.google.com/store/co...roid_help&cfnti=escalationflow.c2c&cft=5&rd=1
Didgeridoohan said:
Have you hooked it up to a computer and tried to see if it's recognised by ADB?
Click to expand...
Click to collapse
Havent done that yet. Only thing that would be good for is making sure its a hardware defect right ?
jazz995756 said:
I had a nexus that had a faulty screen and randomly shut off or something half the screen will glitch out and one day it just stopped working but I could hear the lockscreen sounds. Your best bet would be to send it in for service maybe its a loose connecting or a hardware issue. When mine started acting up it was a loose connecting so if I hit the phone with my hand it would go back to normal and then it stopped working. Its a common issue if you do a google search many people have encountered this
Click to expand...
Click to collapse
That makes sense. could be just a loose connector between the LCD panel and the MoBo ..
Problem is i live in Jordan and I got the phone from Dubai. Its still under warranty of the seller (Souq.com ; an online store .. kind of like Amazon of the middle east ), So i have to send my phone to Dubai to fix it. Now i could just go to a local phone repair shop and ask the guy to check the connectors, but im afraid that would void the warranty and not solve the problem ;( .
dahawthorne said:
That sounds to me like a return-under-warranty job. If you were in the UK you could quote the Sale of Goods Act, which specifies that an item must be of suitable quality and last a reasonable amount of time, but in my case when I returned my faulty N5 to Google after 18 months they were as good as gold, didn't quibble, simply replaced it with a refurbished one which appeared to me to be indistinguishable from brand new.
Since by definition your phone must be very close to its warranty period, depending on when you got it, I'd start with that. This is the link I used from the UK - maybe different if you're elsewhere, but you should find a link called "Get a call from a hardware specialist":
https://support.google.com/store/co...roid_help&cfnti=escalationflow.c2c&cft=5&rd=1
Click to expand...
Click to collapse
I submitted the form , although i live in Jordan which has no presence of Google whatsoever but what the heck !
thanks all for your suggestions.
Google is supposedly a global company...
Let us know how it goes, and good luck.
Well, if you figure out that it is just the screen, you can use this program for basic control with a lot of latency
http://forum.xda-developers.com/showthread.php?t=2786395
It's a little rough and confusing but, it's workable. If you need help setting it up feel free to shoot me a PM.