Develop Bugs

[Q] LCD Screen Problems

Ok so I bought the wife a new G2 about a month ago from T-Mobile. The phone is great and we have both been loving it. Earlier this week the wife mentioned that she was unable to use her phone a couple times because she couldn't get the screen to come up. I messed around with it for a while and eventually it started acting up again. While using the phone, the screen would start to flicker (go between the expected image and a black screen), almost as if the backlight was going out (yes I know there is no backlight with OLED), and then the screen went blank. The screen was black for almost half an hour. I tried pulling the battery and rebooting, the screen never came on and the phone booted up completely. Since it was still useless I went ahead and pulled the battery again. I let it sit for 3-5 minutes and powered it back up. The screen came on, started to flicker a bit and then went black (this is at the HTC boot screen). Eventually the phone came back and now it hasn't exhibited the problem in a couple days. I have noticed that this doesn't seem to be a problem with the Z-hinge (seemed like a likely cause at first), as playing with the hinge doesn't seem to make it flicker or reduce the flicker when its happening. At this point I am 90% confident this is a hardware issue unrelated to the z-hinge. Perhaps a faulty LCD driver chip or a improperly seated ribbon cable on the motherboard side. Feel free to offer any other suggestions.
so... the phone has been rooted and has Cyangenmod installed. In order to get a warranty claim on this I will need to flash the phone back to the original TMO rom. This should be as simple as just flashing the stock .nbh file through the boot loader right? I need to do this before the screen permanently dies on me and I have an expensive paperweight. My other question is if anyone knows whether T-Mobile will send me a new phone replacement for this? I'm under the impression that when you do a warranty exchange you are sent a refurbished model that has been repaired. The phone is only 1 month old and I don't want a refurbished 6 month old phone to replace it, although I don't know if I really have many options.

Okay what method of prem root and s-off did you do? Because if u used the 1st method of prem rooting and s-off useing unforgivens way you need to hex edit to properly flash the PC10IMG.zip stock rom or u will get simi bricked phone. Am not familer with rage so I can't really explain that. As for gfree method you should be fine flashing the orginal stock rom but have more procedure to turn on S-on
Sent from my HTC Vision using XDA App

I used the gfree method described here http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 using the full method that does the radio S-OFF, Super-CID and simunlock.
Hopefully I can just do something like what they discuss here: http://www.addictivetips.com/mobile/how-to-unroot-t-mobile-g2-htc-desire-z-complete-guide/
Thanks

I advice following this
http://forum.xda-developers.com/showthread.php?t=835971
It worked for me. Well hope everything works out
Sent from my HTC Vision using XDA App

The backlight may very well be faulty. This is not an OLED screen. Its just a standard LCD display.
I would get it exchanged if I were you.
Sent from my T-Mobile G2 running Cyanogenmod.

Just got the new G2 in the mail, rooting it now. I was under the impression that the H2o had an amoled display and not a standard backlit lcd. Is this incorrect?
Sent from my HTC HD2 using XDA App

No the g2 has a normal lcd
Sent from my HTC Vision using XDA App

The G2 has an S-LCD. An better LCD screen developed by Sony.
HTC started to use S-LCD because samsung couldn't make enough AMOLED screens for HTC's Desire phones.

Realllly Need Help .... Phone Crashed :(

I am using My Touch slide for almost past 6 months. Yesterday I was clicking some pics and it suddenly started acting weird and after some time the screen stopped reacting . Now the screen s not reacting at all. I tried to reset. Didn't work. I tied to update the software , but since than the MOBILE is not reading he SD card. Neither I am able to SYNC the phone. Please Please Please tell me what should I do .????? It's almost dead and I am not able to use it . I cant afford a new one right now so, please help .....

For the screen being unresponsive would usually mean that your digitizer is broken

medonly1 said:
I am using My Touch slide for almost past 6 months. Yesterday I was clicking some pics and it suddenly started acting weird and after some time the screen stopped reacting . Now the screen s not reacting at all. I tried to reset. Didn't work. I tied to update the software , but since than the MOBILE is not reading he SD card. Neither I am able to SYNC the phone. Please Please Please tell me what should I do .????? It's almost dead and I am not able to use it . I cant afford a new one right now so, please help .....
Click to expand...
Click to collapse
I have the exact same problem :/

how to repair that. please tell ..

6 months old? Can't you then just let it repair for free or get a new one where you bought it?
If its a hardware problem, and it rather sounds so, then you probably can't do much on your own (and don't break it if you have guarantee).

Arjoma said:
6 months old? Can't you then just let it repair for free or get a new one where you bought it?
If its a hardware problem, and it rather sounds so, then you probably can't do much on your own (and don't break it if you have guarantee).
Click to expand...
Click to collapse
Well the problem (for me) is that I do not live in the US, so the shipping fee would be one thing, and then I'd actually have to pay customs to get it back again, so that's a no go. I might try to replace the digitizer though, although I allready replaced it.

You could conceivably order and replace the digitizer yourself, however, it is very difficult and you run the risk of permanently damaging the phone. If you are under warranty still, return it. If rooted search xda for the factory update.zip and follow the instructions to do a factory restore, then return it.
Sent from my T-Mobile myTouch 3G Slide using XDA App

Touch Screen Problem on HTC Desire Z

Hi All
For the last couple of months my desire has had an intermittent problem with the touch screen. All of a sudden it decides you're trying to pull down the "notifications" screen when you're just touching the touch screen, sometimes it also decides you're trying to hold and drag when you're just tapping the screen, sometimes it simply stops responding. These problems are usually solved by tapping the top button and putting the phone on standby then tapping it again and waking it up - although sometimes it then won't let you drag down the screen unlock until you repeat the on/off standby procedure a couple of times. The problem varies on connecting my phone to my computer.
Given that in between these instances the touch screen works as normal I'm guessing it shouldn't be a hardware issue, but the intervals between these problems appear to be getting shorter (either that or I'm just getting more annoyed by it recently). I've had a quick search of the forums and haven't immediately found anyone having this precise problem. Is it likely a question of trying factory reset and if that fails sending it for repair?
Thanks in advance

Similar issues. Don't think this is hardware.
Sent from my HTC Vision using xda premium

Gotta know more about the phone first. Is there a custom rom? Have you tried flashing to stock?

Dukenukemx said:
Gotta know more about the phone first. Is there a custom rom? Have you tried flashing to stock?
Click to expand...
Click to collapse
I'm having same problem, mine started couple weeks after I installed cm7.2, I tried another rom, no luck

Its definitely not software. I've tried froyo, gb stock with s-on and no root. I've been on ics roms cm7 roms but this problem occurs on all. I'm giving mine for service today.
Sent from my HTC Vision using xda premium

Well since the OP didn't respond here's my suggestions. If you think it's software then just flash to a stock rom. You should find a number of them lying around the forums, and instructions on how to flash. This will mean your phone is unrooted and will need to be rooted, as well as taking care of installing a recovery and etc. This should correct anything wrong with the software.
Otherwise you busted the digitizer, which is actually very cheap to buy on Ebay. You will have to take the phone apart which can be time consuming.

strawmetal said:
Its definitely not software. I've tried froyo, gb stock with s-on and no root. I've been on ics roms cm7 roms but this problem occurs on all. I'm giving mine for service today.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Hello,
Any luck with the Tocuh Input, is your phone back from service? I am also facing the same issue....

I had this problem on my G2 a while back. It was a hardware problem so I ordered a new touchscreen and replaced it myself.
Sent from my Nexus 7 using xda app-developers app

htc desire z touchscreen details
Whiskey_Tango said:
I had this problem on my G2 a while back. It was a hardware problem so I ordered a new touchscreen and replaced it myself.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hello Whiskey_Tango / Others,
Can you please let me know the details of the touchscreen component that you ordered for your G2? My HTC desire Z touch screen has also gone bad (unresponsive at multiple points) and I feel that changing the hardwre should do the trick.
If possible, let me know the touchscreen specs (model / part number) as well as any online website from where I can order it !
Many Thanks !!

From eBay search for HTC g2 digitizer
Be careful to get the one for the vision not for the magic
should be about $20
Sent from my Nexus 7 using xda premium

demkantor said:
From eBay search for HTC g2 digitizer
Be careful to get the one for the vision not for the magic
should be about $20
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the quick response. Before coming here, I had a mobile service shop take a look at my handset and he had mentioned that for HTC desire z, the "touch screen" comes with the "display" attached to it. Did he meant the digitizer only or (digitzer + LCD screen) or he was simply trying to rip me off ?
I am very sure that there is nothing wrong with the display on my handset, its only the touch functionality that is not working properly.
Which one of the following do I need to search on EBay?
gultek.eu/htc-spare-parts/digitizer-touchpad/desire-z.html
or gultek.eu/genuine-parts/lcd-modules/htc/desire-z-hd3.html
or both?
Thanks again in advance !!

You need just the digitizer, if you're doing it yourself it takes about an hour if you've never done it before, don't buy the lcd if you don't see a flaw in it.
Some people sell the whole front chasis with lcd, digitizer, front bezel all connected for ease of replacement. May be easier but you will only shave of 30min tops and spend 3x as much
Sent from my HTC Vision using Tapatalk 2

yeah this happens to my G2 a lot. I got my phone fixed a while back (2-3 months ago) becuase the colors on my screen were screwed up and the ear piece was broken. i took it in and he replaced a couple of cables. it worked fine but now sometimes the screen is just having a straight up seizure. it flips through pages so fast and it goes from page 1-2 and back and forth and then the virtual keyboard presses multiple keys and just its crazy. i feel like the guy that fixed my phone didnt plug in a cable all the way. but yeah thats my problem. i dropped my phone the other day and ever since my phone hasn't gone into a seizure lol

Hi, did you solve your problem? I have the same with my desire Z. It click alone in several place on my screen.
And I ask me if the problem don't come from the lcd digitizer control instead of the touch screen digitizer

strawmetal said:
Its definitely not software. I've tried froyo, gb stock with s-on and no root. I've been on ics roms cm7 roms but this problem occurs on all. I'm giving mine for service today.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Hi, did u fixed your phone? can you tell me what was the problem.. even my phone is acting crazy.. wil that be fixed if i change the screen digitizer?

ahmedrzvi said:
Hi, did u fixed your phone? can you tell me what was the problem.. even my phone is acting crazy.. wil that be fixed if i change the screen digitizer?
Click to expand...
Click to collapse
Yes replacing the digitizer did fix my problem. And a year later the replaced digitizer started giving problems. So I ordered 2 extra digitizers off ebay. Both of them turned out to be duds. Surprisingly the second digitizer(which I replaced a year ago) fixed itself.

I think Im having the same problem,
bottom part of screen (including the home, menu, back, search buttons) aren't functioning half the time,
is there any service manual, or link to information as to what I need to tear apart on my DZ?
should this be enough? EBAYLINK
what do I need to replace the digitizer?

Digitiser non-reponsive, need to root.

Okay, I haven't actually used this phone in ages, over a year, but a friend of mine is long-suffering with a BlackBerry and I feel obliged to end her suffering. There are two problems:
1) She wants Sense 4.0.
2) The digitiser is smashed and non-responsive. (A replacement has been ordered)
Now, I am sure that there is a few Sense 4.0 ROMs lying around here due to the fact that HTC released the Desire C, which has the same resolution screen.
So, I started to go through the process of unlocking bootloader, flashing recovery etc and fell at the first hurdle. When I had this, I didn't even look at the developer options, which seems to have screwed me over, because USB bugging is disabled.
So, basically, does anybody know how to enable USB debugging without actually using the screen? Or anything that could enable me to get all of this done now, so I can just replace the screen when I get it and give her the phone?

Nope. Gotta have the screen! And there's not a single sense 4 rom and there never will be. Desire C is armv7 the WFS is only armv6; it's not a case of screen size, but processor compatibility
Sent from my Wildfire S A510e using xda app-developers app

Ouch.
Indeed, you're going to have to fix the screen first.

I faced a similar problem some time ago. Unfortunately, the digitizer has to be fixed first

Alrighty then. I've seen many reviews saying the far right side of the screen often does not respond on replacement, is this true? I was looking at one on Amazon, although the seller is "HTC" I don't buy that for a second.
Sent from my HTC One S using xda premium

I'm very curious on how you proceed on this. I got the same phone and exchanged a non-responsive (shattered) digitizer to a new one which also seems like it is totally unresponsive.
I have read that you need to go into diag mode and calibrate the phone after exchanging digitizer, which seems impossible without USB debugging is set to ON. Unfortunately mine is set to OFF and I'm stuck with an unresponsive digitizer...
Did you get it to work?

[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