Database Info

[Q] White screen of death?

Has anyone encountered the following issues with their SHIELD?
Mine was working just fine after updating to 4.3 and rooting with CWM. I performed multiple reboots in this configuration, played games, etc. - everything was fine.
I had a pretty busy weekend so didn't touch the SHIELD at all for a few days. When I got back:
When I opened it up, I saw the screen backlight turn on but nothing displayed on the screen. The SHIELD button was glowing green.
I long-pressed the SHIELD button to turn off the device. When I turn it back on, I get a white screen that is dark around the edges (mostly vignetting around the corners). The brightness of the screen here and degree of vignetting seem to change every time I try and turn on the device.
If I enter fastboot mode via the key combo, the same thing happens - white vignetted screen. The device DOES appear to enumerate as a fastboot device on my PC in this configuration.
At one point I figured it might be due to a low battery, so plugged it into the charger. 30 minutes later, when I opened the lid, I actually came up to a launcher screen with 65% battery.
However, after closing the lid and reopening it again - black screen again, with the "white vignette of death" coming back if I reboot.
Has anyone else seen similar behavior? Searching results in no one complaining about a white screen like this, at least not on this device.

Screen of Death
This just happened to me today. Did you find a fix for this problem?
Entropy512 said:
Has anyone encountered the following issues with their SHIELD?
Mine was working just fine after updating to 4.3 and rooting with CWM. I performed multiple reboots in this configuration, played games, etc. - everything was fine.
I had a pretty busy weekend so didn't touch the SHIELD at all for a few days. When I got back:
When I opened it up, I saw the screen backlight turn on but nothing displayed on the screen. The SHIELD button was glowing green.
I long-pressed the SHIELD button to turn off the device. When I turn it back on, I get a white screen that is dark around the edges (mostly vignetting around the corners). The brightness of the screen here and degree of vignetting seem to change every time I try and turn on the device.
If I enter fastboot mode via the key combo, the same thing happens - white vignetted screen. The device DOES appear to enumerate as a fastboot device on my PC in this configuration.
At one point I figured it might be due to a low battery, so plugged it into the charger. 30 minutes later, when I opened the lid, I actually came up to a launcher screen with 65% battery.
However, after closing the lid and reopening it again - black screen again, with the "white vignette of death" coming back if I reboot.
Has anyone else seen similar behavior? Searching results in no one complaining about a white screen like this, at least not on this device.
Click to expand...
Click to collapse

Might be just bad luck for me.....
nmerc001 said:
This just happened to me today. Did you find a fix for this problem?
Click to expand...
Click to collapse
So ive already gotten two shields and they both got the same effect. my guess is the ribbon cable when you open and close the screen, is wearing off? because when i open my shield in a certain way, it works... when i open it at around 100 degrees or open correctly then tilt it forward, the screen tears and slowly shows the white screen. I do admit that i open and close the screen more than i should, but i do it carefully. Ill look over at the ifixit site to see how the cable is connected to the board.

This is what has me worried about buying a shield, the ribbon cable, did you confirmed this was the problem?

DJNinja1625 said:
So ive already gotten two shields and they both got the same effect. my guess is the ribbon cable when you open and close the screen, is wearing off? because when i open my shield in a certain way, it works... when i open it at around 100 degrees or open correctly then tilt it forward, the screen tears and slowly shows the white screen. I do admit that i open and close the screen more than i should, but i do it carefully. Ill look over at the ifixit site to see how the cable is connected to the board.
Click to expand...
Click to collapse
I am a tech by trade and bought one of ebay for 40 bucks cuz it would not power up so the guy claimed. After getting it I found the issue was actually the display was not coming on and once it did. Then went out in a few moments. Connect it to HDMI and the unit runs all day of you want to be cabled. ]
So I tore it down and found that the issue is the flex cable. The problem is that the flex cable is part of the LCD and you cannot just replace the cable. Also since the unit is so new there are no sources as of yet to by the LCD from.
So if you have this issue I suggest just holding out till a source of LCD's at hopefully a reasonable price become available.

So it's soldered to the screen and not replacable right?

nex86 said:
So it's soldered to the screen and not replacable right?
Click to expand...
Click to collapse
That is correct.. The flex cable is actually an integral part of the display and even has much of the driver circuitry placed right on it at the LCD. In the business we call it a flex circuit since it is a flexible circuit board and not just a cable.

I pretty much know what you mean.
On my old Archos Gamepad I ripped the flex that connected the left side of the controler to the logic board by accident.
It was a pain in the ass to fix it by soldering seperate wires, I guess it's impossible to do this with the display connection in the Shield.

nex86 said:
I pretty much know what you mean.
On my old Archos Gamepad I ripped the flex that connected the left side of the controler to the logic board by accident.
It was a pain in the ass to fix it by soldering seperate wires, I guess it's impossible to do this with the display connection in the Shield.
Click to expand...
Click to collapse
Might be possible if you used 32 gauge magnet wire. It is enamel coated so it won't short, but it to will break over time.

hi, flash factory image
Sent from my LT25i using XDA Free mobile app

dragxdk said:
hi, flash factory image
Sent from my LT25i using XDA Free mobile app
Click to expand...
Click to collapse
How are you supposed to flash a factory image when the screen won't let you see what you are doing? When you are in the bootloader screen the HDMI drivers are not loaded yet so not even hooking it to an external monitor will work. You might want to fully read and understand the problem next time before offering advice.:good:

fastboot tells you if you were sucessful or not.
just for relocking the bootloader you have to do some button combinations, you can look up some tutorial videos to see what you have to press.

nex86 said:
fastboot tells you if you were sucessful or not.
just for relocking the bootloader you have to do some button combinations, you can look up some tutorial videos to see what you have to press.
Click to expand...
Click to collapse
Even still, it is not a software problem that causes this. I know because if I move my display to a certain angle it will start to work sometimes. A software issue would not cause this. I also have taken my apart since I am a tech and can actually see the traces in the flex cable that have broken..
Any device with a folding display is a bad idea and a failure waiting to happen. Flex cables have a limited number of flex cycles that is even usually published. So the idea of using them in a device that may get heavy use is just dumb.

Solarenemy68 said:
Any device with a folding display is a bad idea and a failure waiting to happen. Flex cables have a limited number of flex cycles that is even usually published. So the idea of using them in a device that may get heavy use is just dumb.
Click to expand...
Click to collapse
I agree, they used flex in the Nintendo DS and 3Ds as well, but they don't break that fast.
I find it still better if they have used recular cables like what they use for Laptops.

Solarenemy68 said:
Even still, it is not a software problem that causes this. I know because if I move my display to a certain angle it will start to work sometimes. A software issue would not cause this. I also have taken my apart since I am a tech and can actually see the traces in the flex cable that have broken..
Any device with a folding display is a bad idea and a failure waiting to happen. Flex cables have a limited number of flex cycles that is even usually published. So the idea of using them in a device that may get heavy use is just dumb.
Click to expand...
Click to collapse
What you are saying is the EXACT same thing that happened to my SHIELD. I can tell its a hardware problem because when I tilted my screen it would work, and sometimes it wouldn't. Now my SHIELD's display does not even show any signs of picture. HDMI still works, however. Like one of the previous posts said, there is not a screen available for purchase, so my next step is NVIDIA customer support. Maybe if they would sell these screens, I wouldn't even have to have a warranty claim. sigh.

White screen of death?
yes mine too same as
i tried connecting my via HDMI from power cable to large HDMI to plug it works fine on my galaxy tab
thought id be clever try it on nvidia shield never worked sould of bought mini HDMI so now White screen of death
i cant get into recovery or anything i had this on charge for 12 hrs yesterday still no green button on charge only orange .. i too cant find anything on internet to help with this White screen of death situation

Solarenemy68 said:
How are you supposed to flash a factory image when the screen won't let you see what you are doing? When you are in the bootloader screen the HDMI drivers are not loaded yet so not even hooking it to an external monitor will work. You might want to fully read and understand the problem next time before offering advice.:good:
Click to expand...
Click to collapse
This. I'm having a similar issue. My wife's SHIELD has an unresponsive touch screen. So I tried to flash the factory image (It was never rooted to begin with) and I got the white screen issue when in the bootloader screen. I have to keep restarting it to get the screen to show up as normal when the device boots to the home screen. But the bootloader screen is still blank and white. I was able to watch a video and mimick the steps to flash the factory image but that did not fix the issue. It's definitely a hardware issue. I live in Cincinnati OH, anywhere I can go to have this fixed? I have a portable myself and i know this is going to happen to mine soon.

[Q] 5158N replaced with 5158N.. no joy

I decided to learn tablets..so I took on a TF300T repair for a friend to start learning.Looks like this TF300T was the wrong choice.
Background.
TF300T Original digi was shattered and was barley working. possible ghost touches
Andriod 4.2.1
Original Digi 5158N FPC-1 06WW 2010 on the sticker JA-DA5158N-IBB 18140-10120500
I did check a few post before I bought a digitizer saw the issues with mixing different versions. So I went with an ebay digi from china with the 5158 model. I received the new on visual inspection it looks exactly the same. New Digi revived no white label but printed in small black ink on the new digi says 5158 12.28 D4\ 11205019701012D. At the bottom in white ink it says 5158N FPC-1 06WW 1225. seems like a match
I replaced the cracked screen went pretty smoothly. I put double sided tape on the digitizer plastic frame after cleaning the old junk off. I did not remove the top cover from the new tape,I just put the unit back together without screw so I could make sure it worked the plan was to test, re tear down then glue/tape the new digitizer down after I tested. Well I get no touch after the 5158N to 5158N swap.
unit loaded the first time and updated the camera firmware but not the touch
I did check the fuse on the main PCB around the LCD/touch connectors and found no burning.
the first time I powered the unit up with the new digi the screen jitterd a bit but no touch. after resetting the cables still no touch. the jitters stopped.. So at this point I ordered a USB adapter to connect a mouse.
This morning I received the mouse connector. went into settings it said. Touchpanel version ELAN-3011-4822 Kernal version 3.1.10-g215ac8bf
Also had a message about DMClient has stopped on first boot. went away after a few reboots.
Today I tried a cold boot after reading some post. It booted up showing the three icons RK/ANDRIOD/WIPE.. up at the top I got the following line:
andriod cardhu-user bootloader <1.00 e> released by "U5_epad-10.6.1.27.5-20130902" A03
key driver not found...booting 05
starting Fastboot USB download protocol
at this point in the cold boot booting the mouse and keyboard seem to be unresponsive. If I hit vol up I get booting kernal recovery image then i get an android logo and big error message sits there and then boots up normal.Still no touch.
After 1st cold boot I went back to check the touchpanel version and now it says ELAN-0000-0000 the Kernal version is a tad different now its 3.1.100-G215ae8bf
Is this normal and Ive missed something? Could it not be working because I ave not glued the new 5158 to the plastic frame?
Do i need to root the device then flash the touch firmware? Seems to me that it should have just accepted the new 5158 and worked that's why i spent the extra cash to avoid this kind of issue.
Any words of wisdom from some TF300T gurus would be a big help!

Forgot to mention at the time i replaced the touch digitizer I did not know to turn the service switch off. the battery was drained as it had ran down to nothing because I could not touch the power off. hopefully this didn't screw me?

CompJock said:
Forgot to mention at the time i replaced the touch digitizer I did not know to turn the service switch off. the battery was drained as it had ran down to nothing because I could not touch the power off. hopefully this didn't screw me?
Click to expand...
Click to collapse
Barring any hardware malfunction, the only way to find out is to root the thing and flash the firmware anew through ADB. This issue has been discussed so many times, it hardly warrants a new thread.

graphdarnell said:
Barring any hardware malfunction, the only way to find out is to root the thing and flash the firmware anew through ADB. This issue has been discussed so many times, it hardly warrants a new thread.
Click to expand...
Click to collapse
Thanks for the response. I apologize for the new thread, most of the other threads seem to deal with swapping mis matched digitizers and then flashing the rom. I thought because mine was an exact digitizer match it may be a different situation. i was just hoping that my experience had rung a bell and someone may point out my error.
At this point I'm pretty sure its not hardware the microsd card reader that shares the touch digitizer board works. and the touch ELAN chanaged to 0000-0000 only after I did a cold boot.

CompJock said:
Thanks for the response. I apologize for the new thread, most of the other threads seem to deal with swapping mis matched digitizers and then flashing the rom. I thought because mine was an exact digitizer match it may be a different situation. i was just hoping that my experience had rung a bell and someone may point out my error.
At this point I'm pretty sure its not hardware the microsd card reader that shares the touch digitizer board works. and the touch ELAN chanaged to 0000-0000 only after I did a cold boot.
Click to expand...
Click to collapse
Hi, i have the exact same issue. Also the system/etc/firmware/touch folder does not exist. I made it and put inside fw. The device whenever reboots it doesnt automatically update fw from the touch folder as it should. Through adb shell i always get error. Seems like the mobo not recognising digitizer. I also put the old broken one and still the same ELAN-0000-0000 i also forgot the off switch but i cant find any "weird" coil. Any help would be appreciated. I have read the other thread and learned a lot but nothing specific to this problem. Also my micro sd port was not working and i really thought was the pcb, but then i manually updated to the latest asus fw (from 4.1.1 to 4.2.1) and instantly micro sd works. When it wan on 4.1.1 i could find the touch folder and 04-3021-7038.ekt was inside (no label digitizer was the broken one and the new i bought as well). After the 4.2.1 update the touch folder disappeared and had to remake it. Tried with 04-3021-7038 and 02-3011-4820

[Q] XT925 killed during attempt of downgrade from OTA 4.4.2

Hello,
I've had recently broke my XT925 and have question if it’s possible to bring it back to life...
Well from the beginning... I've had glass smashed and during tearing screen from the glass I damaged it, so I've ordered new screen with glass and digitizer. When it arrived, after putting it all together it appears that screen doesn't respond on any touch. My friend read somewhere that it could be solved by flashing the phone again(now I don't know is it truth, and right now it feels like one of the smallest problem I have).
I flashed my Milestone 2 and Droid 4 before so I didn't suspect it be so troubling now.
Because my Motorola had been updated to 4.4.2 and I couldn't find firmware in that version I've decided to downgrade the version to 4.1.2. I found some video with how to modify XML file to be flashable. Unfortunately the video is in foreign to me language (Spanish I guess) and at the time I don't realize, that phone has to be unlocked to do that.
It, start to flash, but when it gets to "boot" it stop saying that it can't be downgraded. So right now My XT925 starts to AP Flash mod with text Flash Failure. I'm able to get to recovery mode and from there try to update phone but like in AP Flash it just don't want to flash Android 4.1.2.
Is there any way to bring it back to life?
I'm guessing that it should run if I could flash files for 4.4.2 but I don't know from where I can get them...
Please tell me do I have nice looking brick or there is a hope for my phone?
Phone is locked, has no other then stock tools installed, and it had system version 180.46.117.XT925.CCE-Retail.en.EU before I started to mess with it.
I tried flash it with 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml. When it begin starting in AP Flash mode I have removed every line that cause stopping the process (technically everything except "partition", "tz", "boot" and "system" is loaded from 4.1.2) so now its very messy. Right now I don't know what I was hoping for. What's done is done, so now I can only hope that it can be fixed.

If its even fixable, there is no way to fix it without the stock kk fxz, unless you can get it unlocked using Moto's site.
Sent from my G3 Rockin Cyanogen

Thank you for your reply.
I'll try unlocking by web when I get home. I'm only hoping that it can be done without working properly touch screen, or buy connect keyboard via OTG. Otherwise I'm doomed...

Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard

It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
CoinCoin88 said:
Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard
Click to expand...
Click to collapse
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.

M_Kwiatkowski said:
It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.
Click to expand...
Click to collapse
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)

CoinCoin88 said:
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)
Click to expand...
Click to collapse
The second one is for front camera, speaker and light sensor. I don't count that one because is actually separate part from the screen witch is screwed to the front frame of the phone. To be clear I had problems with that cable and I had to put it few times before camera and sensor start work correctly. That is why I paid special attention to the good fitting of these cables to the motherboard. That was before I smashed software by trying downgrade locked phone so I was pretty sure that it was fitted correctly.
Now my Motorola still works fine. After replacing the screen it actually lived longer in one piece then when I bought it. I scratched the screen next day from purchase... then it fell of my hands few times(usually with the help of other people)... That is why I decided to change glass and front frame... and then during the peel-off old glass from screen I broke the screen... It all happened in period shorter than two months... I'm guessing this particular XT925 is very unlucky... or... it's just unlucky to have me as the owner...
I'm very careful with carrying it with me now, so I don't have to replace the screen again... it cost alto... :|
Well, at least now I know how to bring it safely back to life. And I must admit that my friends are quite impressed that I managed get it work again.

Xperia Z3-Black backlight only,no image.

Hello. I got this Z3 with a broken screen, when I got it it had only black backlight, no image, but the LCD cable on the bottom was cut, so I thought that was why it had no image.
So I replaced the screen with a new one, but the issue remains, no image, only black backlight.
Tried restoring the software with Sony PC companion, updated to latest version, but it didn't help.
The phone boots fine, touch works, I can select options and sometimes I even get audio readouts of what is on the screen, just no image.
Is this a dead motherboard or something else? Because I went through a couple of new screens, none worked, so I'm out of the ideas.
I haven't encountered a case like this before, the screen either works or doesn't, the fact that the touch works and I have backlight puzzles me. No backlight or no touch issues are a common case to me, but this is a new one.
Can someone help here?
Thnx

Same problem....

Hi all.I have the same problem and tried few screens with no luck.If I get z3 compact on hd tv via hdmi cable I can see that it works but no image on lcd only backlight and touch works.Did you find out what causes this problem?

egres said:
Hi all.I have the same problem and tried few screens with no luck.If I get z3 compact on hd tv via hdmi cable I can see that it works but no image on lcd only backlight and touch works.Did you find out what causes this problem?
Click to expand...
Click to collapse
It's a faulty LCD connector on the motherboard, in my case. Not the connector itself but the small jumper just above it, it gives power to the LCD, it was broken off.
I had it resoldered. Works fine now.

Could ju point me a bit closer whitch one it was?Did you get no image at all or something like the one on my picture?https://drive.google.com/open?id=0Bym65RPW_fIpeXlkX2NTYUw5SVk This is how mine looks like around the lcd connector.https://drive.google.com/open?id=0Bym65RPW_fIpTXZpWTFKby1Ua3c

egres said:
Could ju point me a bit closer whitch one it was?Did you get no image at all or something like the one on my picture?https://drive.google.com/open?id=0Bym65RPW_fIpeXlkX2NTYUw5SVk This is how mine looks like around the lcd connector.https://drive.google.com/open?id=0Bym65RPW_fIpTXZpWTFKby1Ua3c
Click to expand...
Click to collapse
No image at all, only black backlight ant the touch was responding.
The three square fuses on the bootom of the picture, it's similar in Z3, in my phone one of those was broken off.

Hi guys. I have almost the same problem but inverted. My display and touch is working but i dont have backlight. I can see the screen only if i put light on it.

Maybe u guys have a faulty digitizer responsible for image faulty(no image), better for send repair, flashing new stock firmware will not help

I tried with new digitizer, no luck. Tried jumping the fuse with no luck. Don't know what to try anymore.

GreatVortex said:
I tried with new digitizer, no luck. Tried jumping the fuse with no luck. Don't know what to try anymore.
Click to expand...
Click to collapse
egres said:
Could ju point me a bit closer whitch one it was?Did you get no image at all or something like the one on my picture?https://drive.google.com/open?id=0Bym65RPW_fIpeXlkX2NTYUw5SVk This is how mine looks like around the lcd connector.https://drive.google.com/open?id=0Bym65RPW_fIpTXZpWTFKby1Ua3c
Click to expand...
Click to collapse
Put the motherboard in the oven and bake it for a few minutes, it resold everything, if that's the problem, it will fix it.
For more infos and temperature / time, google it

Same problem here! i have tried new lcd, new flex cable. nathing works, lcd backlight turn on but no image, touch work cause i feel vibration while touching the lcd.
Pleas Helpppp Anyone with the genius mind??????

I'm facing the same problem with my Z3C, a friend of mine told me he applied this method on his phone and it worked but i'm not sure how to do it.
http://www.mobilerdx.com/2015/03/sony-xperia-z3-display-lighting-problem-repair-solution.html

z3 no display but backlight on
by jumperig the fuse near lcd conector it turns on the backlight .There is another fuse surrounding power manager ic which may got open & display ic is not powering.

Replacement touch screen not working

Hi,
I've bought a new screen + digitizer and replaced it with my broken screen. At first it didn't work...but after updating my N5 device with a OTA cable and a mouse i worked for about a day. But this morning it was unresponsive again.
I've opened it up and checked that every ribbon cable is correctly installed.
The screen turns on fine, but the touch screen is unresponsive.
Any one who has a fix for this or know what to do?

Sounds like a hardware problem to me.

Your previous screen is completely dead ? If the previous screen worked try to put it back and see if it's ok. Maybe you damaged the flex cable or something. The nexus's connectors are really bad...

I've a very similar situation here. Where did you get the screen? Mine seems to work fro a couple minutes then it's unresponsive.

I think the screen is defective. I have replaced the screens on 6 or 7 nexus 5 phones with 3rd party frame/LCD/glass units from Aliexpress and they all continue to work after several months of use.

i have this question also. i can use my touch screen at the first time but not after reboot . Display works very fine to my new screen with digitizer.