[WORKING] Broken htc Sensation Digitizer? READ HERE FIRST!!

[sgb32]

Tried to replace my digitizer.
It's in place but the weird thing is, it doesn't work in Android but it does work in 4ext touch recovery....
Tried to calibrate, but I get this message: Pg58DIAG.nbh not here or wrong image.
Anybody any ideas?

Update:

Managed to flash via fastboot, but after the countdown I get the error: "Launch App fail"....
Getting sick of this, anybody, please help

Update 2:

Tried a different digitizer, this one does work

I have exactly the same issue. Works in 4EXT Recovery but not in Android. Perhaps 4EXT Recovery is using a generic driver and Android is using a driver written specifically for the OEM digitizer?

If we could find the relevant drivers, maybe we could do something similar to this: http://forum.xda-developers.com/showthread.php?t=2189569 for the Sensation?

 

[bourbon79]

I have exactly the same issue. Works in 4EXT Recovery but not in Android. Perhaps 4EXT Recovery is using a generic driver and Android is using a driver written specifically for the OEM digitizer?

If we could find the relevant drivers, maybe we could do something similar to this: http://forum.xda-developers.com/showthread.php?t=2189569 for the Sensation?

Similar problem here. The digitizer works perfect in 4EXT recovery and it does not work in android. I installed the ruu "RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed" and the digitizer works perfect. If I installa any Ics ruu, even if I update to Ics via OTA, the digitizer stops working again, so I am afraid that it is a driver problem. I wonder if there is any possibility of install the same digitizer drivers of the 1.45 ruu into an ICS ruu. Perhaps there is a way to put the drivers ino a custom rom, or make an update.zip to install from the recovery

 

[sgb32]

Similar problem here. The digitizer works perfect in 4EXT recovery and it does not work in android. I installed the ruu "RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed" and the digitizer works perfect. If I installa any Ics ruu, even if I update to Ics via OTA, the digitizer stops working again, so I am afraid that it is a driver problem. I wonder if there is any possibility of install the same digitizer drivers of the 1.45 ruu into an ICS ruu. Perhaps there is a way to put the drivers ino a custom rom, or make an update.zip to install from the recovery

Inside 4ndroid is using ADB Shell to inject drivers in the link I posted. Would need to find the location of the touch drivers within Android and deal with any permission issues. Then there may well be computability issues with different flavours of Android but it's worth a punt!

How did you intall the RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe by the way? It flakes out on my Win8 Pro box,even in compatibilty mode.

 

[bourbon79]

Inside 4ndroid is using ADB Shell to inject drivers in the link I posted. Would need to find the location of the touch drivers within Android and deal with any permission issues. Then there may well be computability issues with different flavours of Android but it's worth a punt!

How did you intall the RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe by the way? It flakes out on my Win8 Pro box,even in compatibilty mode.

I have downloaded tue source code of the gingerberead kernel from the HTCdev web and there is a folder with every dryver, included the touchscreen, but the dirvers have a .c extension (in ex: touchdriver.c), not a .ko like in the link you posted, so I don't know how to use the drivers. I think that one solution could be to download the sourcecode of one ics kernel, add the drivers founded in the gingerbread kernel and compile it to install using fastboot, but I don't know hot to compile the kernel from the sourcecode.

I installed the ruu 1.45 with windows 7 64 bits with no problem, I don't know if win 8 could be the problem. I downloaded the ruu from here:

***shipped-roms.com/download.php?category=android&model=Pyramid&file=RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe

If anybody is able to compile a kernel from its sourcecode will be welcome...Perhaps it coul help other people with the same problem.

 

[piepolitb]

Unlocked but S-ON?

Hello everyone

I have a sensation XE and I'm experiencing some latency and a huge offset of the screen: can't type the q on portait mode!!! I found this thread and I realized that my digitizer is gone... so I have few questions before buying a new one:

1. how do I check the model of my digitizer? do I have to disassemble everything and read on the little label?
2. my device is unlocked with root permission acquired (I have CM 10.1 running on), but it is S-ON because the HBOOT 1.29 is a bad guy... Is there any chance the new digitizer will work? Or am I no longer able to type my beloved q?

thank you

Giuseppe

 

[Sgt.Incontro]

Hello everyone

I have a sensation XE and I'm experiencing some latency and a huge offset of the screen: can't type the q on portait mode!!! I found this thread and I realized that my digitizer is gone... so I have few questions before buying a new one:

1. how do I check the model of my digitizer? do I have to disassemble everything and read on the little label?
2. my device is unlocked with root permission acquired (I have CM 10.1 running on), but it is S-ON because the HBOOT 1.29 is a bad guy... Is there any chance the new digitizer will work? Or am I no longer able to type my beloved q?

thank you

Giuseppe

Should work, there are some excellent YouTube guides out there on replacing digitizers, search for it. Good luck.

 

[redback_rsa]

Hello everyone

I have a sensation XE and I'm experiencing some latency and a huge offset of the screen: can't type the q on portait mode!!! I found this thread and I realized that my digitizer is gone... so I have few questions before buying a new one:

1. how do I check the model of my digitizer? do I have to disassemble everything and read on the little label?

1. Yes, the model is on the ribbon part. But you might not need an exact model if you use the software provided in the OP.

2. no idea sorry

Sent from my HTC Sensation using xda app-developers app

 

[walle4893]

Running a JB ROM on my Sensation. Shattered digitizer...new one order. New one installed. Screen calibration is horrible!! Flashed this, it ran without errors. But now phone wont boot. Just stays on boot animation. Is it because im using JB? Would appreciate the help

Anyone has solution for this? I am currently stuck on the bootloop too (the calibration however went well)

 

[AkhmenHotep]

Awesome, will have to remember if I need to fix my sensation

 

[mnajjar]

Hello

I have HTC sensation xe from UK, unlocked without any logo.

S-off. It has CWN recovery now. I couldn't find stock zip rom with 150, all what I found was 153, when I flash this rom it will jammed on the beat logo.

With cyanogenmod jelly bean it works but no touch too..

I tried the method to calibrate the screen. After asking to put on horizontal surface it give me this error message:

i2c fail

I got the digitizer from US ebay for arround $20
www .ebay.com/itm/140852472020?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649

any idea???

 

[bourbon79]

Hello

I have HTC sensation xe from UK, unlocked without any logo.

S-off. It has CWN recovery now. I couldn't find stock zip rom with 150, all what I found was 153, when I flash this rom it will jammed on the beat logo.

With cyanogenmod jelly bean it works but no touch too..

I tried the method to calibrate the screen. After asking to put on horizontal surface it give me this error message:

i2c fail

any idea???

That is exactly what happens to me. Try installing the ruu 1.45, you yave a link in the post nº 260 (change the *** with www). I think it will work. Anyway, I am waiting to somebody who read this and could help to install the drivers of the touchscreen in the ruu 1.45 into the ruu ICS (or any other rom)

 

[mnajjar]

That is exactly what happens to me. Try installing the ruu 1.45, you yave a link in the post nº 260 (change the *** with www). I think it will work. Anyway, I am waiting to somebody who read this and could help to install the drivers of the touchscreen in the ruu 1.45 into the ruu ICS (or any other rom)

I tired the ROM you mentioned same error !!

 

[maxidodies]

So can I just go and pick up any digitizer and recalibrate it? Or does it have to be the same as the original?
edit : i opened up my phone and found the code on the digitizer:

PYD V1.0
E219454 <>1
ICAC ichia
94V-0 1116

 

[bubu782001]

I TRIED THE ABOVE METHOD WITH PG58DIAG.NBH AND GOT A "i2c read fail" MESSAGE... ANY INSTRUCTIONS ON HOW TO GET OVER THIS. ( MEANWHILE MY LCD + DIGITIZER WAS ORDERED FROM AMAZON.COM AND I FOLLOWED THE INSTRUCTIONS ON YOUTUBE .HOWEVER TOUCH SCREEN WAS NOT WORKING AT ALL).THANKS

This mean the connector of touchscreen have some problems OR the cable of touchscreen is NOT have a good contact into connector. Try to reconect cable.

 

[palka1]

Hello

Long time ago I had broken my digitizer and decided to fix it by myself.
Despite the fact that s/n of the new digitizer differed from the old one, after replacement everything worked perfectly even without calibration, except for the lcd which used to turn off randomly. After some time it got so frequent that I decided to open the phone again and check what was wrong. I noticed I hadn't removed the bottom sheet of the digitizer so I did it and reassembled the phone. Now the lcd doesn't turn off randomly anymore, but digitizer doesn't work at all and attempt to calibrate gives "i2c read fail" error. I tried to reconnect the digitizer twice, with no results. I even tried to install 1.45 firmware, with no results too. Does it mean that I damaged my digitizer during second disassembly and only thing I can do is buying another one?

 

[raananh]

i2c read fail error disappeared

First I'll say my replacement digitizer is now working OK after the calibration succeeded.

I too got the "i2c read fail" error during my first attempt to run the calibration. At that time the digitizer was also completely unresponsive as if it was dead.
After leaving the phone without its battery for about 8 hours, and then turning it on again, I noticed the digitizer was not totally dead anymore, just having the usual issues with the HTC ring that was hard to to pull it to the top to unlock. So I thought the I2C must be working again, and indeed, when I ran the calibration again it worked OK, and now the ring pulls up fine, and the digitizer works like new.

I think I messed up the I2C during my attempts to perform the JuopunutBear S-OFF process (in order to run the calibration). I tried the wire trick for timing on a live phone (with the battery inside) - after those tries I noticed the digitizer became completely dead (and not just problematic as before) - which agreed with the I2C read fail error from the calibration that I tried later after I managed to get it S-OFF and superCID.

So basically leaving the phone without the battery for several hours made my i2c read fail error disappear, and the calibration actually worked in my case.

Hope this helps, and thanks for this helpful thread.
raananh

 

[raananh]

I spoke too soon - I2C read fail returned

First I'll say my replacement digitizer is now working OK after the calibration succeeded.

I spoke too soon. After an hour of working fine, the digitizer suddenly turned dead, and I got the I2C read fail error again during calibration.
I'll buy another digitizer. I really hope its not an issue with my mainboard.
raananh

 

[sibozzy1811]

i also bought a new digitizer for my sensation but didnt match my old one as i couldnt find one at all, when trying to re calibrate with pg58diag.nbh, i press vol down and get this message.. TP_ATT always keep in high
anyone know what this is please

 

[maxidodies]

Welp, I got screwed over. Was sent the wrong screen and on top of that it was used, scratched and you could see the old glue.

 

[wauwter]

conclusively determine whether digitizer is broken?

I am experiencing problems as shown in this video: http://www.youtube.com/watch?v=Bk1BlXZQDrU. I was wondering whether there is any way to conclusively determine if the digitizer is broken, or whether it could be an alternative issue? I obviously dont want to go through repair, when this may not be the underlying cause of problems.. Thanks!