Develop Bugs

Desire - screen is flickering

Hi guys,
I have a problem, hoping for some advice ^^
I sent my Desire for warranty repair, as the screen has been flickering. I know about the problem with SLCD filckering and it wasn't like that. It's like the whole screen gets bright and dark in high frequency (it's AMOLED). It first appeared like 2 months ago, for half an hour, and then it was back to normal. Then it appeared again 2 days before I sent it in. I've been emailed now, 24 day later, that they could not find the problem and that it's all working fine. I've even sent them a video of the problem. but it doesn't help them, and they'll send it back.
What am I to do? Send it in again as soon as i get it back, or wait another month for the problem to appear again, just to send it back again and to receive the same answer, when there is clearly something wrong? :S
Thanks for your help.
oh, and it looked like that nook color screen flickering.
EDIT: since the device was sent to repair before, to replace the non working camera, is it possible that there could have been some problem with connectors or is this strictly hardware (display) problem?

Could be a problem with anything. Could be the screen, could be the connectors, could be the cables, could be anything.
If the problem is a quick fix problem like a reboot then I don't see the point in asking HTC to do anything. If its a problem that is common, maybe every day then there is a point. If they can't find a problem, they can't fix it. They wont take your word for it unless they can confirm it. Parts cost money and they're not going to throw money away at the expense of customers words, otherwise everyone would be doing it.
Sent from CM7

The thing is that I even recorded while it was happening. And I did it because I knew there was a possibility they would not find nothing wrong with the phone. And it's not a quick fix problem, don't even know what caused it and made it stop (stock rom, factory reset, it was still happening).
Oh well, I guess I'll make another video as a proof and send it in again when the problem returns.
Thanks for the answer ^^

make sure auto brightness is disabled
cant u make them replace the screen somehow

Insureance ftw
Sent from CM7

Here, I've sent it in for repair again. By law, they have 45 day to repair it - if they don't, i get a new phone. The thing is, that if they don't find anything wrong with the phone (and they didn't find anything, as the problem appears once in a while), they have another 45 days if I send it in again.
Luckily, my mobile operator acknowledged my videos (can be seen: alenandrasic.com/desire.html) and gave them only 20 days to repair it, since it took them 25 days last time to find nothing.
So basically, I have to wait 15 more days. I guess i'm really unlucky, since i've been withouth my desire for 2.5 months in the 10 that i own it. Ah well, will post how it gets resolved ^^

HTC Warranty Workaround ?

I read through few posts about people being able to claim their warranty even after unlocking their bootloader , now these people had almost the same problem ..there screen wouldn't display anything or their phone wouldn't boot up at all. So I guess HTC won't check for your warranty if your phone is not booting up ...they'll just check your bill and see if its under warranty and do it for free ...
Sent from my HTC One X using xda app-developers app

Well I've seen people get away with this, but I still darent unlock/root.
Because I know what my luck is like and I would be the only one that doesn't get repaired !!

It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.

Awt67 said:
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Click to expand...
Click to collapse
lol sounds like a good plan, now everyone who needs repair will burn it's phone and get new replacement under warranty

Awt67 said:
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Click to expand...
Click to collapse
Yeah I've been debating for about 3 weeks now, would you really say its worth it?
What ROM you using?
And, about the warranty, what does completely dead mean?
Not booting?
Or bricked etc?
Cheers mate.

I am using Cyanogen Domination 10. It is still work in progress but it stable enough for everyday use. I would also say if you do unlock your phone try roms other as well because they all offer something different.
Dead as in bricked, although if you follow unlock steps carefully there is little chance of bricking your phone

I unlocked my phone the day I bought it ... I'm not regretting it all but the little yellow spot in the bottom left corner is annoying sometimes ..
Sent from my HTC One X using xda app-developers app

lets just make this clear, its certainly posted here already in many many threads...
if you read the unlocking stuff properly on the htc website, it clearly says that the warranty will be invalid for anything caused by unlocking the bootloader
so if you have a blatant hardware problem, ie the wifi antenna problem, they still have to repair it foc
so basically, unless you brick your device, you still have a warranty.
they might try insisting on replacing the main board for a cost, which i've heard quite often. the wifi fix requires changing the main board anyway, so for at least that problem, they shouldn't charge to fix.
still, it does depend on the type of problem as to whether you could convince them not to change the main board..

[Q] Touch Screen gone haywire

After flashing the stock google (yukju) roms on my galaxy nexus, everything went fine for a couple of months and now I am getting weird haywire issues with my touch screen. Without me touching anything, the phone will act like a part of my screen is being touched, it will not respond when I am indeed touching it at times, the screen will flicker back and forth and generally act strangely. Then for the other 70% of the time it is fine. I have re-flashed all stock roms, did a factory reset, and the problem persists.
Is anyone else having these problems?
any idea what to do next.
After contacting my provider, they said they cant help me because I had unlocked the phone. I have since relocked the phone so I might try calling back and seeing if it will fool them, but I doubt it. Now that I have re-locked the phone should I try to deal with Samsung?
Any help appreciated!

It sounds like a hardware issue. Most likely the touchscreen itself is bad. If you still have warranty or insurance coverage then bring it back to the store and tell them it is defective. By the way, NEVER mention that you have ever unlocked or rooted your phone.
Sent from my Xoom using Tapatalk 2

Thanks for the reply. Im worried that, like you say, it is a hardware issue because I bought it used, and therefore will probably have problems with warranty/insurance. My carrier has already said that they wont help me with it so I would have to go right to Samsung. Any tips on dealing with Samsung? I have already returned to stock and re-lock the phone and I never rooted it, I certainly wont say I did anything to it in any way. Anything else I should be aware of? Will they even help me out since I wasn't the one who bought the phone in the first place?

GentlemanBasdard said:
Thanks for the reply. Im worried that, like you say, it is a hardware issue because I bought it used, and therefore will probably have problems with warranty/insurance. My carrier has already said that they wont help me with it so I would have to go right to Samsung. Any tips on dealing with Samsung? I have already returned to stock and re-lock the phone and I never rooted it, I certainly wont say I did anything to it in any way. Anything else I should be aware of? Will they even help me out since I wasn't the one who bought the phone in the first place?
Click to expand...
Click to collapse
Although most manufacturers offer a 1 year warranty on hardware, I doubt they will honor it since you were not the original owner. Your next option is repairing it yourself. It took a look at prices on eBay and it looks like the digitizer (touchscreen) for a galaxy nexus goes for about $30 and the combination of digitizer and LCD screen go for about $150. I don't know how difficult it would be to separate the digitizer from the LCD on your phone, but $150 for the set is still better than buying a new phone.
Sent from my Xoom using Tapatalk 2

As has been said, it is probably a hardware issue - I had an HTC Desire S before my GNex and had the same issue with it, started all of a sudden. (The screen would go haywire as you said, almost as if a ghost was pushing buttons quickly - that's the best way I can describe it). Mine did not have warranty coverage because I had rooted and unlocked it but the HTC rep was helpful and said it happens sometimes because of moisture or humidity or some such thing and to replace the lcd/digitizer. Cost me a little ($110) but phone was as good as new after that, used it for six months before selling it and buying the GNex.

[Q] Nexus 7 Hardbrick! QHSUSB

First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.

Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582

That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app

Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app

Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app

Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?

What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app

Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?

I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:

I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.

That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app

If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.

dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)

Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:

Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.

whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.

OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.

No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app

Nexus 5x screen not working. Display changed ,same issue

Hi All,
This is my nexus 5x. Phone is working. But nothing on display. I have replaced a working display as well ,same issue. Anyone to help me?

Hi, I have the same issue, did u find any fix?

Alizpk said:
Hi, I have the same issue, did u find any fix?
Click to expand...
Click to collapse
not yet brother. I'm really disappointed with this issue Is this happened to you after update to Android O? What did you try?

I don't know the fix for this. I just kept my phone is my drawer for a few months and when I took it out, it was fixed.
Although I did note 1 thing - The display had started to show white noise as soon as it became hot. I had to keep it on a cold plate to make it normal again. The only thing I can recommend is putting it in fridge or something and then turning it on. Listen to me at your own risk. I ain't no mobile fixer, but just a random guy.

AngelousJi said:
The only thing I can recommend is putting it in fridge or something
Click to expand...
Click to collapse
That's literally the biggest no-no with electronics.
When you can't repair something on your own, you would usually seek out a person who can and, eventually, pay for the repair. You do not ask for possible solutions which you would probably not be able to perform on your own.

shhnedo said:
That's literally the biggest no-no with electronics.
When you can't repair something on your own, you would usually seek out a person who can and, eventually, pay for the repair. You do not ask for possible solutions which you would probably not be able to perform on your own.
Click to expand...
Click to collapse
This certain advice is being given everywhere. (Even I'm a bit skeptical on this). On that repair thing- I literally asked every single repair guy in my local city and not a single one could fix it. This nexus had just become my tinkering toy so I had nothing to lose. If anyone still has the value for it, please take it to your repair guy.

I think this is the same issue that I have. I talked to Larry from India at Google. He had the same issue with his phone and LG was fixing the issue for his phone. He said it was a connector from the board to the screen.
So he hooked me up with LG. I talked to Holly and she sent me an label and repair under warr. They extended their normal warranty. LG previously fixed the bootloader issue by replacing the motherboard, so this issue may have been caused when they fixed the phone. May want to try contacting LG, see if it helps.

Hi, i have the same issue on my Nexus 5x. did you find any solution?
This is the second time happened to my Nexus 5X. but it fixed with no reason after about 3-4 days i put into drawer.
then this happen again since last night.
Did you try to clear the delvik cache or something via recovery mode?
sorry for bad english

This is the bootloop of death. Check on the forum for further informations