Hello, I've registered especially for that problem, so what happens is after I get the cool NVIDIA bootscreen, I instantly come up with a message saying "Turn off" or some kind of shutdown message.
Before you ask, yes, my bootloader is unlocked, and it was rooted until I do a factory reset, since it was doing this auto shutdown, I also currently have CWM Recovery, which is quite a nice recovery !
Here's a list of things I tried and that didn't do anything:
Try to cancel the shutdown somehow
Booting the tablet multiple times
Factory Reset
Also, I can't seem to use it with my computer since, well, that damn shutdown on startup.
So what can I do ? I still have access to the recovery. Could it work to give it some ADB in the tablet's face ? I really need this beautiful piece of hardware to play vidyagames.
And also, the battery is full, and working properly (I can kind of see the battery on top, it's probably at 80% or something.)
I'd also like to point out that it suddenly started doing that. And there's also a SD card in it. And also, when I access the fastboot, well, I can hear it on my computer, guess it's a good sign !
And yes, it's the one with Wi-Fi, so if I have to use a ROM, I don't think I would have much choice. Also Android version is Lollipop.
EDIT: Nevermind for the ADB, it requires my tablet to be on, at least I can still use CWM Recovery and fastboot ! yay
EDIT 2: The message is:
Power Off
Shutting Down...
WavingStory said:
Hello, I've registered especially for that problem, so what happens is after I get the cool NVIDIA bootscreen, I instantly come up with a message saying "Turn off" or some kind of shutdown message.
Before you ask, yes, my bootloader is unlocked, and it was rooted until I do a factory reset, since it was doing this auto shutdown, I also currently have CWM Recovery, which is quite a nice recovery !
Here's a list of things I tried and that didn't do anything:
Try to cancel the shutdown somehow
Booting the tablet multiple times
Factory Reset
Also, I can't seem to use it with my computer since, well, that damn shutdown on startup.
So what can I do ? I still have access to the recovery. Could it work to give it some ADB in the tablet's face ? I really need this beautiful piece of hardware to play vidyagames.
And also, the battery is full, and working properly (I can kind of see the battery on top, it's probably at 80% or something.)
I'd also like to point out that it suddenly started doing that. And there's also a SD card in it. And also, when I access the fastboot, well, I can hear it on my computer, guess it's a good sign !
And yes, it's the one with Wi-Fi, so if I have to use a ROM, I don't think I would have much choice. Also Android version is Lollipop.
EDIT: Nevermind for the ADB, it requires my tablet to be on, at least I can still use CWM Recovery and fastboot ! yay
EDIT 2: The message is:
Power Off
Shutting Down...
Click to expand...
Click to collapse
Since you have access to CWM, I'd recommend you do what I recommended another user
http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2
NaminatoR1254jaime.sier said:
Since you have access to CWM, I'd recommend you do what I recommended another user
http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2
Click to expand...
Click to collapse
So... do I have to reflash a new recovery image and put a new OTA ? Or just a new OTA ?
EDIT: Of course not.. I got it, I have to flash a new OTA with CWM right ? So.. it means that my current OTA is corrupted or something. Nice... but how do I flash it ?
EDIT 2: Ok found how, I sideloaded the OTA, which is quite a new thinig to me.. I never ever did modifications to my tablet without a tutorial, it was upgrading... so I guess that's good... And it didn't do jack s***. It stills power off... weird.
WavingStory said:
So... do I have to reflash a new recovery image and put a new OTA ? Or just a new OTA ?
EDIT: Of course not.. I got it, I have to flash a new OTA with CWM right ? So.. it means that my current OTA is corrupted or something. Nice... but how do I flash it ?
EDIT 2: Ok found how, I sideloaded the OTA, which is quite a new thinig to me.. I never ever did modifications to my tablet without a tutorial, it was upgrading... so I guess that's good... And it didn't do jack s***. It stills power off... weird.
Click to expand...
Click to collapse
Very weird. Must be defective. Did you try reflashing stock images via fastboot? (I've never done it, fyi)
NaminatoR1254jaime.sier said:
Since you have access to CWM, I'd recommend you do what I recommended another user
http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2
Click to expand...
Click to collapse
Well, I don't think it works by fastboot, I don't even think the tablet is bricked, could it be on the hardware level ?
WavingStory said:
Well, I don't think it works by fastboot, I don't even think the tablet is bricked, could it be on the hardware level ?
Click to expand...
Click to collapse
I have the same problem. I've tried flashing the recovery 2.1 files, sideloaded the 2.2 ota, etc. The last thing i'm going to try is wiping the system with trwp then installing the 2.1 recovery again.
-that did not work. I have initiated the RMA process.
Anyone has some instruction how to safely open a NVIDIA Shield Tablet ? I woud love to check if some hardware went off so I can rebuild it.
EDIT: Wait, it can't be hardware... It just can't ! Why ? Well... simply because right now i'm in TWRP recovery, everything is working exept... oh wait... CPU temperature is going crazy. 429491929 C... yep... I don't think that's right.
Ok, sorry for the double post, I know it's really bad... BUT I THINK I KNOW WHY !
Bad thing, it's the CPU thermometer, it has gone crazy.
So, I installed you know, that TWRP recovery, and I checked the CPU temperature.
Wanna know what it is ? It's hotter than plasma, or lava, or anything. Heck even the big bang.
CPU: 429491899 C.
That's right, that much, so... any idea how to fix the CPU Thermometer ? I knew it was something with the hardware. My theory is that it is not connect properly to the CPU. Since everything on TWRP is working... TOO FAST COOL! like all the apps I had on that tablet.
So here, problem half-solved. The tablet shuts down because of the CPU temperature, to prevent it from overheat !
EDIT: Finally fixed it ! ;v; Like I said, it was the CPU Temperature, since it kinda fell off my bed now that I remember, what is the CPU thermometer ? Well, it's a small bar near your stylus slot. Inside the thing, also, when you insert you stylus you insert it directly into the hardware part, next to that CPU Temperature thing, maybe that caused it, but well, basically, I opened my tablet with a cool little trick, basically, I took the back of my stylus and I forced softly on the tablet in the stylus slot. And what happened ? It opened a little ! So, what I did is slowy remove the plastic around to to not cause any crack of damage and it worked perfectly ! I saw that little CPU thermometer going off and what I did is basically push it back into where it was ! Also, the wi fi antenna is next to the camera, it's pretty small for your information ! But yeah, I putted back the plastic case after that and booted my tablet... and IT WORKED!!! It booted perfectly ! So: It was not the ROM or the OTA, it was the auto shutdown to prevent overheat. Also, it seems like recovery mode and fastboot don't care about temperature... so they won't be shutting down ! I'd like to thank the creators of that TWRP Recovery, it's the thing that helped me find out that it was the CPU Temperature ! It's also the first time of my life I touched to some hardware. And i'm really proud of myself even for such a small thing ! Hope it helps someone in the futur ! Thanks for trying to help me !
WavingStory said:
Ok, sorry for the double post, I know it's really bad... BUT I THINK I KNOW WHY !
Bad thing, it's the CPU thermometer, it has gone crazy.
So, I installed you know, that TWRP recovery, and I checked the CPU temperature.
Wanna know what it is ? It's hotter than plasma, or lava, or anything. Heck even the big bang.
CPU: 429491899 C.
That's right, that much, so... any idea how to fix the CPU Thermometer ? I knew it was something with the hardware. My theory is that it is not connect properly to the CPU. Since everything on TWRP is working... TOO FAST COOL! like all the apps I had on that tablet.
So here, problem half-solved. The tablet shuts down because of the CPU temperature, to prevent it from overheat !
EDIT: Finally fixed it ! ;v; Like I said, it was the CPU Temperature, since it kinda fell off my bed now that I remember, what is the CPU thermometer ? Well, it's a small bar near your stylus slot. Inside the thing, also, when you insert you stylus you insert it directly into the hardware part, next to that CPU Temperature thing, maybe that caused it, but well, basically, I opened my tablet with a cool little trick, basically, I took the back of my stylus and I forced softly on the tablet in the stylus slot. And what happened ? It opened a little ! So, what I did is slowy remove the plastic around to to not cause any crack of damage and it worked perfectly ! I saw that little CPU thermometer going off and what I did is basically push it back into where it was ! Also, the wi fi antenna is next to the camera, it's pretty small for your information ! But yeah, I putted back the plastic case after that and booted my tablet... and IT WORKED!!! It booted perfectly ! So: It was not the ROM or the OTA, it was the auto shutdown to prevent overheat. Also, it seems like recovery mode and fastboot don't care about temperature... so they won't be shutting down ! I'd like to thank the creators of that TWRP Recovery, it's the thing that helped me find out that it was the CPU Temperature ! It's also the first time of my life I touched to some hardware. And i'm really proud of myself even for such a small thing ! Hope it helps someone in the futur ! Thanks for trying to help me !
Click to expand...
Click to collapse
Glad you fixed it!!!
So thats the little thing bar right to the stylus...
You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet
NaminatoR1254jaime.sier said:
Glad you fixed it!!!
So thats the little thing bar right to the stylus...
You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet
Click to expand...
Click to collapse
Well, I would have taken a picture, but I have nothing to capture pictures with... so.. yeah. Else I would have taken photos, it's pretty safe to open it by the way.
If the "bar" you're referring to is the one just off center on the right side, then that's where a Sim card is installed on the LTE model...
Sent from my SHIELD Tablet using XDA Free mobile app
NaminatoR1254jaime.sier said:
Glad you fixed it!!!
So thats the little thing bar right to the stylus...
You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet
Click to expand...
Click to collapse
An Droid said:
If the "bar" you're referring to is the one just off center on the right side, then that's where a Sim card is installed on the LTE model...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Nope, it's a sort of small bar near the camera, just on the top of it, it's made of some steel I think !
2 questions
I'm having the same problem. I already have opened the cover based on how you described it.
1. I can't find the thermometer and what kind of fix should I do with it?
2. How did you install TWRP when the device couldn't even boot properly.
Thanks
---------- Post added at 06:39 PM ---------- Previous post was at 06:01 PM ----------
I blindedly pushed some components back (dangerous) and decided to put back the cover. I rebooted and yeah, it booted properly! However,after a few minutes it auto shut down again. So I guess the theory that it's about the CPu thermometer might be true.
The question is, where is it really located and what should be it's position? Thanks.
Finally Fixed!
After several sessions of tinkering the unknown components of the hardware, I finally decided to take it to the next level. So I carefully removed the electrical tape covering the perimeter of the battery. Lo and behold - there's a white wire that is loose and I've determined its correct connection through its length.
Since I didnt have a soldering iron and I'm too afraid to use it should I have one, I used brute force connection via electric tape. I peeled more skin to secure conductivity.
Apparently, it's the connection to the CPu thermometer. When it is unlinked, it should register as weirdly high value, triggering hard reset. During the boot up and initialization, the firmware takes note of the value. After studying the behaviour of the problem, apparently the firmware in the chip also occasionally checks the temperature esp when an app is launched. This explained why I couldn't boot at the beginning or if ever boot was successful, antutu causes shut down. So as a solution, I made sure the contact between that freaking white wire and the solder placement on the board MUST be secure.
I'm using my fixed shield tablet to post here Btw. Apparently it has become faster. Antutu is 55,000. But charging the battery seems slow. I must have accidentally messed up something with the battery.
Boy I love my Shield tablet!
Thanks many many times!!
It fall down of the carpet and later that evening I noticed that it s off.
thanks the happenstance that TWRP shows the CPU Temperature it was fast located.
so I was able to search for.. and finally xda did it again..
Thanks all of you
Same problem
Well, my tablet got the same problem
Here some pictures, can you tell me where is the temeprature sensor?
Faced the same problem and I fixed it as suggested by soldiering the white wire behind the tape. Look at the picture to know where it is located.
First attachment with the tape on. Second image with the tape off and after soldiering the white wire to the board. I hope that helps.
SalehCoder said:
Faced the same problem and I fixed it as suggested by soldiering the white wire behind the tape. Look at the picture to know where it is located.
First attachment with the tape on. Second image with the tape off and after soldiering the white wire to the board. I hope that helps.
Click to expand...
Click to collapse
wow ... excellent post. this also solved my restart problem. thank you very much.
interesting side-fact: this only affected stock images. all alternative roms (bliss, etc. ...) started fine ...
I've got this exact problem as well but even after soldering this white wire, it keeps shutting down..
Edit: after some more attempts, I got a new temp: 92c. But I still got shut downs.. So I managed to switch it back to that weird 42516516161 etc temperature and now it wont turn off with the Custom Rom Bliss Pop.
I had the same issue. The device started to shut down by itself, sometimes right after boot. Luckily I stumbled to this thread while googling for the issue. Then I verified the problem by installing cpu-z and watching the temperature while waiting for the device to power off. Indeed, just before powering off the sensor jumped to -46 C. So with your help I found the culprit and soldered it back. No shutdowns ever since!
Related
Does anyone know what the DIP switch located in the transformer is for? The only thing I found is a post mentioning a different wifi setup.
My experience messing with it is that the transformer won't turn on when it is in the up position unless the tablet is plugged into its charger.
Please see post 7 for the issue I am experiencing and how the Dip switch is involved.
thatton13 said:
Does anyone know what the DIP switch located in the transformer is for? The only thing I found is a post mentioning a different wifi setup.
My experiance messing with it is that the transformer won't turn on when it is in the up position unless the tablet is plugged into its charger.
Click to expand...
Click to collapse
Search Been discussed before
I did search, here and Google many times over the past month. Only found 1 post with the info that I mentioned.
"The only thing I found is a post mentioning a different wifi setup"
If I overlooked something I would appreciate a push in the rite direction. Or is that all the info there is?
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
gee one said:
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
Click to expand...
Click to collapse
While the OP might not...I found your response highly amusing
Post 90-94
http://forum.xda-developers.com/showthread.php?p=16812367#post16812367
Its use is still unknown, but at least the post confirms the behavior that the OP is seeing.
gee one said:
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
Click to expand...
Click to collapse
Nice! Especially the Back to the Future reference. Allow me to explain my situation and why I am so interested in that tiny switch.
I purchased my Transformer from Newegg back in July or August. It was an open box and I saved around $150 because of that. Unfortunately that means it only had a 1 month warranty, this brings us to my problem. It runs great but every once in a while a lot of the apps, including the browser, will force close. Also if I go in to settings once this problem starts and shut off the WiFi and then try to turn it back on it just says error. Trying to turn on Bluetooth also does not work.
The solution is to reboot, however, it will only run for a short while before the problem returns. I have tried the stock rom rooted and unrooted, I have tried various roms, revolution, prime, revolver. After flashing a rom or doing a factory reset the transformer will run for around 12 hours without the above mentioned problem but it always comes back and it happens more and more frequently until I do a factory reset.
I have tried countless things. Various roms as mentioned, factory resets, freezing as much as I can using titanium backup, not adding a Google account, turning off gps, different wireless networks, assigning a static ip address, using ExtSd2InternalSd v2.1 to install apps on an sd card. All of this with no success.
Enter that dip switch. I decided since my warranty was over I would open it up and do some poking around. I discovered if I put that switch in the up position and boot the transformer with it plugged into the charger it runs perfectly stable. The issue is gone. only problem is that I can only use it plugged in. This situation lead me to the conclusion that it is a power supply issue, maybe a defective battery (Not getting the full 1.21 gigawatts . So.... I switched out the battery in my dock with the one in the transformer and put the dip switch in its original down position..... No Luck, the problem persisted. Return the switch to up and plug it in, runs great.
Anyone have an idea?
How does it run while the switch is down (in the crappy position) and plugged in?
gee one said:
How does it run while the switch is down (in the crappy position) and plugged in?
Click to expand...
Click to collapse
The problem is still there. I even tried it in the down position with the battery disconnected and the transformer plugged into the charger but the problem continued.
I guess it could be a power/hardware issue or maybe a sleep/software issue. Perhaps it doesn't sleep while it's plugged in?
Regardless, it's quite an interesting problem.
gee one, thanks for your help. Maybe someone will come up with a fresh idea, I have tried most of what I can think of.
I might try the dual boot Ubuntu thing to see if I have the problem in Ubuntu. I figure that mite help narrow down if it is a software or hardware problem. I lean towards hardware because I have not been able to find others with this issue. Then again, maybe others that have had this problem had a warranty and returned it for an exchange.
gee one said:
Perhaps it doesn't sleep while it's plugged in?
Click to expand...
Click to collapse
Forgot to mention, I tried setting the screen to never shut off in hopes that it would prevent the transformer from sleeping. Not sure if there is another way to prevent it from sleeping? Whatever the case leaving the screen on did not prevent the problem from surfacing.
Install ROM Manager and tell it to Fix Permissions?
I've had extensive FCs on some devices I've rooted and fixing the permissions has helped.
Col.Kernel said:
Install ROM Manager and tell it to Fix Permissions?
I've had extensive FCs on some devices I've rooted and fixing the permissions has helped.
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately I have cwm installed and have ran fix permissions and while it did help with some of the apps force closing it did not fix my problem.
I was about to ask where this switch was at because I've never seen it, then I read that it's inside the unit. I have no reason to crack this bad boy open yet so that's why I had no idea about it.
It is a battery kill switch, makes it easier to work on without blowing the **** out of the unit by bridging the wrong points on the board for what ever reason. basically with the switch up it is a "service mode"
Need Help with ASUS TF101 back light Out . ! An dip witch . ?
So did u ever find out what the Dip Switch was my friend . ? I'm working on the same unit as this at the min with the back light out so Screen is Dark But it works sound shining a Torch on it, . ? Fing is I'm a Self Tougt Tablet fixer an not bad at it, . But this 1 is full of stuff I've never seen before lol . So im looking to see if any 1 can shed some light on this . lol . ( sorry for the pun there ) . & To help me get this back light for the screen working again on this TF101, . ! An then I find this dip Switch Fing an a Small battery like a Com's battery in a lap top that I've Never seen in a tablet before, . ? So if u can help or any 1 else i would be so Greatfull . Nice 1 . DAY . ! But what is this DIP SWITCH 4 . . ?
Hi,
Yesterday (08/02/2013) I updated my tf700t, everything seemed to be fine after it rebooted, I was playing a game, the battery was low, and it turned off abruptly. I assumed it automatically shutdown because of the battery, so I put it in the dock and plugged in the charger. Several hours later I tried turning it on and nothing. I held down the power button for 8 seconds felt the double vibration, but no display. I tried various combinations of docked/undocked, power cord plugged in, holding the power button for 30-60 sec. etc. but nothing.
Out of curiosity I connected the HDMI to my computer monitor and sure enough, it was there, I could unlock it and everything seems to be functioning fine, just no display. The digitizer seems to work fine, although guessing where things are at is pretty tough.
I think I tried the cold boot, volume up/down (I tried both) plus power, and it didn't make a difference.
In order to do the update I had to flush the DMC Client and CMClient data and cache, I had been getting errors from DMC Client crashing.
Also I'm not certain this is update related, as the tablet had been acting wierd, which is why I did the update. I would press the power button to turn the screen on and nothing would happen, so I'd hold it down longer and the tablet would reboot and finally the screen would come on, or it would come on a few seconds after I pressed the button. I was getting a lot of reboots etc... I thought the update might resolve this.
I'm not sure if the problem is hardware, firmware, or software related.
I'm wondering if when I flushed the DMC and CM Client cache, maybe I deleted the drivers for the display or something?
My options seem to be:
1.) Factory reset by feeling around the digitizer while connected to HDMI
2.) Factory reset via the pinhole
3.) Install new (old) firmware via usb/computer. (the device is recognized by Windows 7 so I think this is doable.)
4.) Send it off to Asus. (would this be free?)
So my questions are:
1.) is there something else I should try?
2.) what order should I do the above in?
*Note: I'd like to save my data somehow.
*Edit: I forgot to mention I was on 4.2.1, no root or anything. Also I bought this in July of '12 so I'm pretty sure it is out of warranty. Any idea how much it might cost to send it off? Perhaps I could replace the LCD myself? I replaced the digitizer/screen on an ipod touch, although I'm sure this LCD is much more expensive and much harder to replace. This is turning into a nightmare. So much for trying to keep my data, now I hoping to keep this from becomming a paperweight.
Thanks.
A bloke at work had this issue. He let it rundown and left it for 3 days. It worked fine again after that.
zpyatt said:
I'm not sure if the problem is hardware, firmware, or software related.
Click to expand...
Click to collapse
If you don't even see the boot logo, it cannot be software related.
Thanks for the replies.
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
zpyatt said:
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
_that said:
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
Click to expand...
Click to collapse
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
zpyatt said:
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
Click to expand...
Click to collapse
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
sbdags said:
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
Click to expand...
Click to collapse
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
zpyatt said:
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
Click to expand...
Click to collapse
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Having the same problem
I am having almost the same problem, except that the tablet screen works when the wall charger is plugged in. THe HDMI display and the digitizer work fine. It is just the tablet's screen dispaly when the charger is unplugged.
sbdags said:
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Click to expand...
Click to collapse
So I didn't have any luck letting it run all the way down.
I contacted customer support, the warranty is only 1 year, but fortunately for this there is an extra 3 months, so I just managed to squeak by, although I'm keeping my fingers crossed.
same problem as you both
i have d same problem well until last week the screen displays when conne ted to wall charger now its all blank but iy works via hdmi, digitizer works fine but all blank, this tf201, does anyone know if i change d whole display it will work?
i already bought the tf701
any suggestions is welcomed and did you get youra to work?
zpyatt said:
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL.
Click to expand...
Click to collapse
I have not seen people mentioning VHDL and verilog for a while, hahaha... It sounds like you are a low level or physical layer programmer. Any way, a firmware is in general a low level program that communicating with the hardware and the software or high level program ( level 7).. If you will, a firmware is a management levels (level 2 and 3). A VHDL is a level 1 which generates a 0's and 1's or mapping the transistors in the FPGA chip for example.... Oh well, it is just my definition...
zpyatt said:
I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
If you can get the output from the HDMI port, it is more likely you have a hardware problems. I think that the problems are your display related hardware. If you really want to troubleshoot your issues, you can look on the mother board to locate all the electrolytic caps and check to see any abnormal signs of those capacitors. Those caps are the one that will blew up first before any others parts go....Good luck...:fingers-crossed:
Hey guys I've had my N5 for almost a year now but it seems to have gone kaput on me recently...
On Monday I was on a skype call, (just audio) when my phone suddenly restarted, I didn't pay much mind to it as that happened before and it would usually just cut back on, but this time, it restarted, and restarted and just didn't stop. That lead me to think its the power button being stuck so i checked it out and made sure its not being depressed and well yeah it wasn't. And soon after that the phones screen was sometimes on during the reboots and sometimes off. I knew it was rebooting because the N5 vibrates a bit when Google pops up on the loading screen in a certain way, but yeah now the screen doesn't light up at all, there's still vibrations and sounds like when I call or when I say Okay Google a few times, the LED will even light up during a call. I know the phone is "on and working" in the background but the screen doesn't light up and as such I can't touch it, any ideas and or advice friends?
bump de bump?
Possibly your backlight burnt out? Water damage?
if you are running cyanogenmod, you could be experiencing sod "sleep of death". thats when you know the phone is on and working, but the screen doesnt turn on. ive been reading lots of complaints about cm and the sod.
TheROMGuy said:
Possibly your backlight burnt out? Water damage?
Click to expand...
Click to collapse
As the phone kept rebooting it went from seeing everything, to seeing nothing but the back light to dark, so maybe? It was just by me on my desk too so I was doubtful about the water damage but I put it in the sealed rice bag for about 24 hours just in case but still no luck.
I actually am running cyanogenmod and whenever I do have a problem I always feel that its related to CM as the phone doesn't have any physical damage...maybe I should look into that, any other ideas friends?
P.S I am using the ElementalX Kernel and UNFORTUNATELY I turned on the FAST CHARGE USB option and that makes the phone play funny with the computer, if you guys have any advice as to how I could turn off that option please do let me know
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
dynamo147 said:
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
Click to expand...
Click to collapse
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
simms22 said:
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
Click to expand...
Click to collapse
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
dynamo147 said:
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
Click to expand...
Click to collapse
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
simms22 said:
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
Click to expand...
Click to collapse
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
dynamo147 said:
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
Click to expand...
Click to collapse
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
simms22 said:
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
Click to expand...
Click to collapse
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
dynamo147 said:
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
Click to expand...
Click to collapse
send back the rma? honestly, i dont know. i dont know anyone thats ever had to pay. unless its obvious that you did something, youll be fine.
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
I will chat it up with one of the customer service peeps and see what they think then, and maybe even hopefully one will know about the replace anything deal
anactoraaron said:
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
Click to expand...
Click to collapse
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
dynamo147 said:
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
Click to expand...
Click to collapse
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
anactoraaron said:
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
Click to expand...
Click to collapse
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
dynamo147 said:
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
Click to expand...
Click to collapse
See here http://forum.xda-developers.com/showthread.php?t=2513701.
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??
semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.
Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?
Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it
I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.
Rma
Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.