So, I've rooted my TF and been running the latest Revolver ROM for about a week. Everything ran awesome with very few flaws. I also recently RMA'd my dock for the sleep issue and just got it back yesterday.
I hooked up the dock to my TF and it ran great all last night and this morning. Everything charged just fine. I packed it up to take to work, took it out at work and...nothing.
My TF would not wake from sleep. I thought maybe I had suddenly encountered the sleep of death issue that I had heard about but never experienced, so I held in the power button and restarted.
The TF restarted just fine. Booted past the first screen and the custom animation screen. But as soon as it was supposed to boot into the homescreen, it goes blank. The TF is on as I can hear email notifications and stuff, but there is nothing on the screen. I tried booting and re-booting with the same result.
So I wiped cache. Same result.
After getting an MD5 Checksum error from the one backup I had of my system through CWM, I wiped data/factory reset. I actually got past the boot animation and started setting up my TF again. However, the screen was set to auto-bright (I like it at fairly bright) so I started to adjust it. As soon as I touched the brightness controls, the screen went black. TF still on, just no screen.
I booted back into recovery again, wiped data/factory reset again and again it booted up just fine and took me to setup. Went to adjust brightness in the actual settings menu and as soon as my finger touched the brightness bar, the entire screen went black.
WTF? Has anyone else gotten similar experience with your TF, either rooted with a new ROM or not? Not a whole lot I can do with a tablet with no screen.
Here are the things it is not based on my observations:
1. It is not a dead screen. On boot up, the screen works. Animation plays well. I can access the CWM recovery menu.
2. It's not a dead touch screen. I can factory reset and go into the setup using the touchscreen.
Here are the things I suspect it COULD be:
1. Something up with the Revolver ROM. I had refrained from applying the 2.1.1 update as the update immediately after that just reverts it back to the version before the 2.1.1. update. However, I did apply the update after the second time of factory resetting.
2. Something up with my dock/dock software? I didn't have any of this issue before I received my dock back.
Please, can anyone help me out here? Sorry for the long post, but wanted to include as many details as possible.
Does the issue occur not docked? Can you use the dock brightness buttons to bring back the screen?
It happens both docked and undocked . Dock brightness buttons do nothing.
I left the tablet alone for about twenty minutes and when I came back the screen was on. Brightness was at max. But again as soon as I touched the brightness controls no screen.
Sent from my DROIDX using XDA App
Actually (after wiping and restarting yet again) I found that even the dock brightness buttons cause the screen ti go blank.
Sent from my DROIDX using XDA App
Okay so after searching high and low for others with this issue i found two unresolved threads. It seems to be a software problem that will not allow the backlight to go beyond 50% brightness when not plugged into the charger. I'm at work now so I can't test this for sure until I go home later this evening. If this is the case, then it could be a problem with my root and ROM installation. I will try the following things in order.
1. Restore from backup done right after I gained root access. This is basically my system with the original software. After gaining root, I did delete some things through Titanium Backup that I felt were bloatware. This might have had something to do with it so restoring the original backup should return these things to their normal state. The only problem with this is that when I tried to restore from recovery, the MD5 checksum gave me an error. I have found a thread that allows you to override using ADB and will try once I get home.
2. Unroot completely and flash back to stock. It worked when I was unrooted and stock, so theoretically it should work again.
3. If the above two methods don't work, I'll just RMA it back to ASUS. I already called in and got an RMA number for the issue. At least by doing the above two things I can ready the tablet to be within warrany specs in case it's just a dud and needs to be replaced.
Will update with results.
Results
1. When plugged into the charger (with or without the dock) I can up my tablet to full brightness just as the other couple of threads I read stated. Even with brightness up at full and running on battery (blank screen) there is still HDMI out. Wish I had realized this BEFORE I did a complete data wipe.
2. Had to use terminal emulator and the following link to recover the CWM backup with the checksum error: http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/70519-md5-sum-mismatch.html
It worked awesomely to bring my precious tablet back to stock with all applications I ran previously. Still no change in the brightness issue though
Now on to try to unroot and see what I get...
sounds like you're taking the right steps.
I hope so Malandro2011.
Looks like I will have to RMA after all. I unrooted, went back to stock recovery and a completely new install of the most current firmware. No dice. The issue is still there.
My tablet's all packed up and ready to ship off to the god awful Texas facility for repair/replacement. Since they sent my dock back with a bend in the metal near the adapter port, I made sure to take pictures of the entire tablet before replacement as well as leaving a note to them under the RMA slip about the condition of the tablet when I shipped.
My biggest question is what triggered this to happen. Was it rooting and installing a new ROM? So many people have done this without incident it is hard to believe this was the problem. Was it whatever changes they made to my dock? I was running smoothly for a week before charging it in the dock overnight.
many people have rooted and your the first I've heard with this particular issue so i doubt these roms caused it...but could be wrong.
Seems power related since adjusting the brightness sends more power to the screen or less then the screen fails.
I reckon its just faulty...
I wonder if they'll replace it with the newer models that cant be rooted yet..
Yeah, I agree it seems power related. My unsubstantiated theory is that when they adjusted the I/O board in the dock, perhaps it changed some of the power settings and caused some sort of overload/short in my tablet when I used the dock.
Such a shame to send it back. It was one of the earliest models and beyond this was one with the fewest problems. No light bleed, no stuck pixels, no sleep of death, good QC on the hardware. Here's hoping that what I receive back will be just as good (and hopefully not one of the unrootable new models).
Update for anyone following this thread. Received my repaired TF two days ago. Total away time was around 2weeks. It looks like hey had to replace the entire screen. Looks nice with even less lightbleed than before but the screen has a faint yellow tint that I have heard is common with later model TFs. Not sure if I should send back again as I really don't want it gone for any longer time...
Related
I'm looking for a magic solution to this.
My rooted (Prime 1.8) went into the sleep mode when connected to the dock. Never had any issues previous with this. Its been a great tablet.
I played about with it somewhat. Can go into APX mode, can see the internal flash etc. All works except screen won't come on.
I even reverted (nvflashed) back to stock in case of having to send it in.
After reading a few more posts this morning, someone mentioned about the backlight being the problem.
He was right. When holding up a flashlight to the screen, you can see the text on the screen. It is actually booting fine, just can't see it. It doesn't actually go to sleep.
Anybody know how to rectify this? I have a product replacement plan from the shop I bought it, I'm just concerned about getting one of the newer non rootable devices. Would rather try to fix this one first.
Thanks for any help.
Mike
Hi everyone, this is my first post here. Thanks in advance for any help that you folks can provide.
I've had the TF101 for about six months now, and it's been fine. I was using it yesterday on the train and all was good, but when I got home and took it out of my bag it didn't seem to start up. I thought it might have been a battery issue, so I let it charge overnight. Tried starting it up this morning and I got the same results. So I started looking in to other issues.
The tablet is definitely starting, adb will recognize it in its list of devices, and if I plug it in to my tv or desktop monitor w/ HDMI, I can see and interact w/ the Transformer UI (of course this is kind of painful since I have to do some guessing about where to put my fingers).
I had rooted it using rebound821's scripts and directions here, so tried an unroot to see if that was the problem. I ended up with the same results.
Does anyone here have any insights as to what the problem may be? I'm hoping to avoid sending it back to ASUS, so I'm fine w/ opening it up to look for loose cables.
So I thought that brightness might be the problem. Maybe it was set to 0 and I just wasn't seeing anything on my screen. Sadly, that doesn't seem to be the case.
I tried setting brightness at the path below to to 0, 50, 100.
/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
Still no luck.
Has anyone encountered anything remotely similar to this (even if similar is just a dead screen)?
There have been others with dead screens reporting what you are, at least I have read a few reports, I think they just had to get them RMA'd, I don't recall anyone 'fixing' a dead screen, especially if you still have adb and touch working then the screen itself and backlight seem to have broken completely- some have reported the backlight dying and thinking the screen was broken, but it was just the backlight (I guess in bright light they could see pixels working, but couldn't make out what was on the screen without the backlight). I still think they had to get it repaired either by Asus or by someone who was capable of doing internal repairs with replacement parts..sorry for your luck
Looks like I'll have to send it back. I took it into the brightest light I could find and couldn't see anything at all. Guess it's the screen and maybe the backlight too. I'm pretty disappointed this happened, the only thing I can think of is that the bag I had it in was hanging from the chair in front of me on the train and it was swaying a little, and that shouldn't be enough to dislodge a connection. Either that or just some freak hardware failure. Still, I guess it's not that common of an occurrence. Thanks for the reply, I'll slink off and try to get in touch w/ Asus now.
I have experience same
My TF101 broke in the same way, screen blank. Conected to tv I`ve got image digital touch work. I shut down my TF101 normaly and screen never go back to live again. Tablet was in a protective bag (when I trave by car), just no reason for not working ( no problem at screen, previously, screen perfect - no dead pixels)
Did you guys get this resolved? I had the EXACT same thing happen yesterday. Was working just fine. Put it in its sleeve, into a protective case, into a briefcase, got home and dead.
HDMI works. I tried to call Asus but they say i'm out of warranty.
Thanks in advance.
Must be something wrong with the connections that it decays over time. I've had mine since October last year and its been fine except for today when I brought it home it wouldn't work.
I was able to fix it though. I held it vertically with the bottom edge down and tapped it firmly on my desk a couple of times. The screen came back on. There is a strong possibility that this will happen again and my tap fix won't work, but it's working at the moment
Asus Transformer screen
elementalfire23 said:
Must be something wrong with the connections that it decays over time. I've had mine since October last year and its been fine except for today when I brought it home it wouldn't work.
I was able to fix it though. I held it vertically with the bottom edge down and tapped it firmly on my desk a couple of times. The screen came back on. There is a strong possibility that this will happen again and my tap fix won't work, but it's working at the moment
Click to expand...
Click to collapse
I had exactly the same problem discussed in this thread. I was also able to bring the screen of my TF101G to life by tapping it firmly on my desk with the bottom edge. It works for now. But it is certainly disconcerting to know that some connection in this rather expensive gadget are loose and all this can happen again. I guess I will not carry my transformer around any more - just leave it at home...
spokey said:
My TF101 broke in the same way, screen blank. Conected to tv I`ve got image digital touch work. I shut down my TF101 normaly and screen never go back to live again. Tablet was in a protective bag (when I trave by car), just no reason for not working ( no problem at screen, previously, screen perfect - no dead pixels)
Click to expand...
Click to collapse
Same problem here had my unlocked bootloader tf101 for awhile now, one of the first ones out... had a great life gave it to my girl when i got the transformer prime and the screen just went out yesterday, still goes in apx mode and still recognized by computer, screen just straight up died, think it's too late for a manufacture warranty, maybe ill look but think it's gonna be no dice... sucks obviously something in the design to make this happen to so many of them...
My TF101 appears to have a dead screen. I am rooted and running Revolver Custom Rom. When connected to my pc, I am able to recognize my device. My screen will not turn on so I cannot use recovery to go back to stock. I am set up to use ADB, however, I am not very knowledgable with ADB. I am convinced I have a bad screen and I am still under warranty. Is there a way to return the TF101 back to stock using ADB? If anyone can point me in the right direction, I can probably figure it out. Otherwise, I may just try and replace my screen and see how that works out. Thanks for the help.
My backlight died on Tuesday. Similar situation of working in the morning, headed into work with it in my bag, no brutal knocks or anything but one jolt just must of finished it off after a year and 2 weeks abuse (yes 2 weeks out of warrenty).
Going to attempt to take it apart this afternoon and play with the ribbon cable as reseating it has solved quite a few peoples problems.
Woo! It worked! Very happy chappy.
Sent from my SK17i using Tapatalk 2
Same thing happened too me, first time i sent it to service, but last time i opened it myself and pushed the connector for the screen thightly in place.. worked nicely
Sent from my Transformer TF101 using xda app-developers app
Screen goes derp
I don't know if I have the same problem or not.
Backstory: I own a Transformer TF101 that I got for my birthday from my girlfriend. It was meant for travel and bs'ing around at home. Took it into work and quickly realized that I could use this for work. That went over so well that the rest of the office became intrigued. Once these came on sale on groupon, the office manager went all in on 10. These are all refurbished transformers with docks.
They have all been handed out and I now have a transformer for home and work. Kind of nice...but I do a lot of site observation so using my personal transformer was a risk that I had to take all on my own (survived a 5' fall off of a parapet wall already).
The problem: From the first 5 minutes that I had the thing, the transformer screen went blank. I opened up google play to download a few apps that I could use for work. Scrolling down I saw some choppyness which I considered the processor/memory having issues loading everything on the screen. Before I knew it - boom blank screen. Rebooted and the loading screen stays on for 2 seconds before the screen goes blank. I can tell it's working because it plays a sound at start up. I can also tell the screen is lit up (it's like it's showing a grey screen because it can't show true black colors). If I hit the power button again it goes completely black. I hit the power button again and the screen flashes to the lock screen and immediately goes blank again. I could do this over and over and over again.
Anybody having the same problem? It's refurbished....I'm guessing apparently I got the dud.
I ran into pretty much the same problem. One morning, the tablet screen would just not turn on. Sometimes, it came on and immediately shutdown, but it is still on the "On" mode. Hit the power button again will bring it to the off mode. Toggle it one more time, sometimes, will turn on the screen a off again. I was able to get it back to work with a factory restore. However, it has the following problems.
1) As soon as I adjust the brightness, the screen will go off again. And there is nothing I can do to bring it back except another factory restore.
2) The screen will flicker (and sometimes produces some clicking sound) when charging with the screen on.
Looks like my TF101 is having same issue, screen gone off suddenly (hdmi shows up in TV fine)...I am going give a try on reseating the cable hoping it resolves the issue.
leonpr, is there some tips/things I have to make sure before attempting this. I found a guide here and another youtube video on this issue as a reference...
Thanks..
Screen won't turn on unless factory reset "fix"
My girlfriend has an ASUS TF101. If the brightness goes up to 60%, the screen is blanked (no backlight either) and the only way to get it to turn back on again is to hard reset. This coincidentally happened at the same time as an update from ASUS. After lots of Googling it does not appear to be related. I was hoping it was and installed several custom ROMS which all experienced the same issue.
As a temporary work around, until I get the guts & the money to be able to replace her tablet if I break it, I found and installed AutomateIt. I set a trigger so that when the screen is turned off, the brightness is set to 50%.
Why trigger when the screen is off instead of when the screen hits above 59%? If you have this same problem, hold the brightness and go all the way until the screen blanks and then still holding your finger on the screen, move it all the way to the left and you will notice that the screen did not come back on. Press the power button once to turn it off and then again to turn it on and you will see the screen at the lowest brightness setting.
So, with the trigger in place, if you accidentally (or one of your rotten kids intentionally:angel raises the brightness above the threshold, simply press the power once to turn off the screen and then press it again to turn the screen on.
Just a note, I ended up installing AutomateIt Pro, Available for $1.60 from the Play Market. The free version works fine, but my girlfriend has been struggling with this issue for a couple of months and after so many hard resets, the little app is more than worth the money.
Have you tried Power + Volume Down for 15 seconds, and then leaving it alone for one minute? It will cold boot. Try that and it may work. Just saying; Hope it will help
Sorry for the necro-bump but here's the actual solution.
Problem: The video cable inside the Transformer comes loose and just needs to be pushed back in.
I can't post a link since I don't have 10 posts yet so just search youtube for the following key words:
blank or no display issue on the asus transformer - fix
The user who posted the video is DoCWaSaBe
Tokyudo said:
Sorry for the necro-bump but here's the actual solution.
Problem: The video cable inside the Transformer comes loose and just needs to be pushed back in.
I can't post a link since I don't have 10 posts yet so just search youtube for the following key words:
blank or no display issue on the asus transformer - fix
The user who posted the video is DoCWaSaBe
Click to expand...
Click to collapse
Just fixed my blank display problem on a TF101 which is well out of warranty. Here is the link. I found the connector loose after dropping my TF101.
Thanks!
Fix lasted for a few days, now backlight dead, tried all cables again. No joy . I hate intermittent faults so ordered a Samsung Galaxy TabPRO 10.1.
Hi all,
I have flashed a CM10 (obviously unofficial) build to see what JB would bring to the TF700. Well, I'm impressed and very much looking forward to it.
However..........
The portrait-orientation bug (currently, portrait apps do not resize correctly) precludes me from reading on the 700 (since it clips the screen in 1/3 / 2/3 parts and repeats content -- absolutely horrible), and that's one of the main things I use it for at the moment.So, I decided to get back to Zeus34's ICS (and otherwise excellent ) ROM. I wiped data / cache / Dalvik cache / system in between installs, mostly multiple times (and obviously system only before an install, thank you ).
I can install Zeus ROM v4.0 from recovery -- Google setup plays nicely for the most part (had one crash in several installs), but whenever I have the keyboard dock connected (whether I boot it without and then connect it, or boot it with it connected from the start) my screen goes black and won't react to the power button anymore. If I then disconnect the dock, I can turn the screen of the tablet on again with the power button.
:silly:
It does the same thing after restoring my backup of the stock .26 ROM, by the way, with the added problem of the keyboard not reacting anymore several times. I then installed CM10 again, and the keyboard dock was functional again. <?>
One admission up-front: I have a depleted keyboard dock, and I forgot the charger at home (I am now at work, approx. 100 kilometers from base).
Ok, question time: could the keyboard dock's depletion play a role in this? Why doesn't it do that under stock ROM? Any suggestions? Have I done something stupid? Could my keyboard be dying on me (although it works now again under Cm10)?
I loved CM10 (and I tried Black Bean as well -- did the same thing with the orientation, so had to go for now as well) -- boy, are we in for a treat when they start supporting the TF700 more fully....
For what it's worth, I basically did the exact same thing - tried CM10 and didn't feel like dealing with the issues (and also really missed the Asus-specific customizations), so I then restored back to my Zeus 4.0 setup (using a full TWRP backup, including the boot partition).
Anyway, everything is 100% back to "normal" for me now. So, if you backed up the boot partition with TWRP before installing CM10, it's probably something to do with the fact that the keyboard dock is out of juice...
Did you backup the boot partition in TWRP before installing CM10?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Technically he installed the Zeus ROM which should have formatted the boot partition with the respective boot image. I know zeus ROM has it. So I am guessing its the dock being depleted.
Sent from my Galaxy Nexus using xda app-developers app
Thanks for the replies! I came home tonight after work and didn't have the energy left to tackle the problem then and there, and figured out charging the dock would at least eliminate that factor from troubleshooting this. This morning, however, I booted up the now fully charged combo, and under yesterday's fresh Zeus install... same thing happens -- to my joy, it booted normally, but about thirty seconds in, it lowered brightness drastically, and a few seconds later, it completely borked out on me again. In frustration, knowing what that would mean, I did a clean install of the .26 update with TWRP -- obviously, I lost everything root and such, and I too do now experience even more extreme lag and choppiness than the "stock stock experience" showed me.
So, in the end, I do not think the depleted dock was the problem, and I thought that before because stock ROM doesn't give a damn if it has juice or not (it is powered by the main if depleted, so it runs down the battery that much faster, maybe, but it will function). Explicitly: this is NOT meant as an ITYS (I Told You So), but I'm trying to figure out what is wrong here, because the current situation is.... slightly undesirable.
MartyHulskemper said:
Thanks for the replies! I came home tonight after work and didn't have the energy left to tackle the problem then and there, and figured out charging the dock would at least eliminate that factor from troubleshooting this. This morning, however, I booted up the now fully charged combo, and under yesterday's fresh Zeus install... same thing happens -- to my joy, it booted normally, but about thirty seconds in, it lowered brightness drastically, and a few seconds later, it completely borked out on me again. In frustration, knowing what that would mean, I did a clean install of the .26 update with TWRP -- obviously, I lost everything root and such, and I too do now experience even more extreme lag and choppiness than the "stock stock experience" showed me.
So, in the end, I do not think the depleted dock was the problem, and I thought that before because stock ROM doesn't give a damn if it has juice or not (it is powered by the main if depleted, so it runs down the battery that much faster, maybe, but it will function). Explicitly: this is NOT meant as an ITYS (I Told You So), but I'm trying to figure out what is wrong here, because the current situation is.... slightly undesirable.
Click to expand...
Click to collapse
Interesting - so before you loaded CM10, you did a full TWRP backup of your Zeus 4 install, correct (including Boot)? I'm just trying to determine why you are seeing different results than myself being that it sounds like we did the exact same process (TWRP backup, CM10 install, TWRP restore) but yet we are seeing different results. I did make sure that Boot was selected in TWRP before doing my backup - I'm wondering if that is possibly the difference?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Interesting - so before you loaded CM10, you did a full TWRP backup of your Zeus 4 install, correct (including Boot)? I'm just trying to determine why you are seeing different results than myself being that it sounds like we did the exact same process (TWRP backup, CM10 install, TWRP restore) but yet we are seeing different results. I did make sure that Boot was selected in TWRP before doing my backup - I'm wondering if that is possibly the difference?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Yes, I believe boot was included, but I am not sure, since it may have been before we were actually able to include the boot partition when backing up with TWRP. I'll take a look.
I am back to .26 stock, rooted and with TWRP. I am going to dip my toes in Zeus ROM again and see if I bump my head again. I'll be holding off on the otherwise absolutely great AOSP/CM10 builds for now, as the portrait bug is really killing those for me. I have found a reference to a TF(101?) AOSP-based ROM of which the dev states (s)he fixed the screen tearing and portrait bug, and I spammed the threads with the link. If it's of use to even one of those ROMs, I'll take the penalty of an infraction if need be. I hope it results in something, since I do notice a tremendous difference in smoothness and responsiveness between my current .26 and the AOSP/CM10 builds
M'kay, here goes. Wish me luck....
EDIT: So far, everything seems back to normal now (every time the time-out kicks in and the screen goes off, I'm having palpitations. Hahahaha! So far, I've been able to revive both tablet and myself by hitting the power button and seeing the screen turn on again. ). I guess flashing the stock .26 and then Zeus fixed it. I still do not know what the issue was though,'so it isnt very helpful. :S
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
rock1324 said:
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
Click to expand...
Click to collapse
Update:
I can now rarely get it to vibrate for even a second holding the power for a long long time. Screen does not come on at all. Looks completely dead.
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Thats OK said:
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Click to expand...
Click to collapse
I was hoping it wouldn't lead to something like this. I got my tablet from Amazon around the first week of september. I have treated it very well.
I'm not quite sure how it could have burned out, my brightness is usualy <50% and I have used the super IPS+ more less time than I can count
on one hand. If this is the case, Is it possible that a technical problem like this would still be repaired on warranty seeing as it has nothing to do
with the bootloader?
Also I'm not sure how this explain the constant vibrating that does not turn off untill the battery runs out. The way I see it is you could be right, the tablet is trying to tell me it's not going to work, or there is really some kind of software glitch.
Have you ever had LCD problems with a tablet? any idea how much this could cost?
rock1324 said:
Have you ever had LCD problems with a tablet? any idea how much this could cost?
Click to expand...
Click to collapse
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Thats OK said:
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Click to expand...
Click to collapse
Thanks for the advice, I have heard some terrifying stories of Asus customer support (never had a problem with them myself) and of devices just being completely lost in their care.
To answer your question, no the back lights are not visible at all. The only way I know the Infinity is somewhat alive is by the led coming on while charging and the somewhat random vibrating patterns that happen when trying to boot up.
I got this Tablet on Xmas. I rooted and updated, 1st thing, and began experiencing sleep of death (won't wake from sleep and you have to long press the power button to power down, then power back up the tablet again). I thought it might be due to rooting so I went back to the factory image through fastboot, flashing the original OS, recovery and everything and I still get sleep of death on this thing. I've got a new one coming from Tigerdirect but I'm wondering if this issue is common or not. I'm hoping not cause I can't find much info on it online. Thanks for any info.
CeeJayII said:
I got this Tablet on Xmas. I rooted and updated, 1st thing, and began experiencing sleep of death (won't wake from sleep and you have to long press the power button to power down, then power back up the tablet again). I thought it might be due to rooting so I went back to the factory image through fastboot, flashing the original OS, recovery and everything and I still get sleep of death on this thing. I've got a new one coming from Tigerdirect but I'm wondering if this issue is common or not. I'm hoping not cause I can't find much info on it online. Thanks for any info.
Click to expand...
Click to collapse
I've been having this issue stock, no root. I feel like Nvidia left out some polishing. But I will say that I didn't have this issue before the 5.0.1 update.
I suspect constant sleep death to be a physical fault of some shield tablets. My first tablet had it occasionally, but my RMA replacement has never had it. Ever.
That being said, sleep death can be caused by some apps, too. Try to diagnose it assuming its an app running wild, if you cant track it down contact nvidia for a replacement.
CeeJayII said:
I got this Tablet on Xmas. I rooted and updated, 1st thing, and began experiencing sleep of death (won't wake from sleep and you have to long press the power button to power down, then power back up the tablet again). I thought it might be due to rooting so I went back to the factory image through fastboot, flashing the original OS, recovery and everything and I still get sleep of death on this thing. I've got a new one coming from Tigerdirect but I'm wondering if this issue is common or not. I'm hoping not cause I can't find much info on it online. Thanks for any info.
Click to expand...
Click to collapse
Yep, I had this issue only after updating to 5.0.1 stock, no root. But after a few reboot cycles, the issue resolved itself.
I do not have this issue - its a LTE purchased on blackFriday. In fact I have NEVER had even a single app crash. I just rooted last week and no issues their either (on 5.01).
Have you tried doing a clean install?
Load CWM - Format all partitions
Then flash NVIDIA 1.2 recovery Image
Then upgrade to 5.01 (direct upgrade now - 5.0 is no longer an incremental from OTA).
if it still does this after a full wipe then I would suspect its hardware related.
Thanks for the input. I have formatted everything and the issue still persisted, I never did try staying on kitkat though. Is Kitkat still best for this tablet? I see a lot of people down on lollipop. I wonder if it would have worked itself out but a new one is on the way already. I just hope it's as good as this one in terms of light bleed and cracked corners. The one I have has the most minimal of bleeds in one corner and no cracks whatsoever.
You reformatted and reloaded 501 full?
I reflashed the Nvidia recovery image (1.2 KitKat) and it performed like a dog in comparison to 5.01... So I re-upgraded back to 5.01.
5.01 has a few glitches (battery stats, battery life in general, Graphical Corruption) but in general I have no stability issues and have no issues while its in a deep sleep.
Have you tried turning off wifi when the tablet is sleeping? Leaving WiFi running while in deep sleep seems to be a culprit of various issues. Try that..
CeeJayII said:
Thanks for the input. I have formatted everything and the issue still persisted, I never did try staying on kitkat though. Is Kitkat still best for this tablet? I see a lot of people down on lollipop. I wonder if it would have worked itself out but a new one is on the way already. I just hope it's as good as this one in terms of light bleed and cracked corners. The one I have has the most minimal of bleeds in one corner and no cracks whatsoever.
Click to expand...
Click to collapse
I've tried everything you mentioned and more. Believe me, I wanted to keep this thing but nothing seems to work.
CeeJayII said:
I've tried everything you mentioned and more. Believe me, I wanted to keep this thing but nothing seems to work.
Click to expand...
Click to collapse
I had the exact same problem. Factory reset did not resolve. Contacted Nvidia support and they told me to return for replacement. Thankfully I purchased mine through Amazon and they sent me a new one right away. No problems with the new tablet. I love this tablet!
Sent from my SHIELD Tablet using Tapatalk
Even though the solution seems to be getting a replacement, I'll post my scenario here in case it helps anyone identify their problem:
I have been having this sleep of death issue since I got the tablet with KitKat back in October, and it has persisted through the upgrade to Lollipop. It happens almost every other day at least. I have always run completely stock, no root or anything.
I've noticed this same issue on my tablet as well. It's not very frequent (maybe once every couple days). It is my 1st RMA, and I dont recall it happening before the 5.0.1 upgrade. If the next update doesn't fix the issue I will probably go for my 2nd RMA.
mine does it. It's infrequent, but it does it. Running 5.0.1.
Yea I have this problem on mine, I got mine the week the tablet came out so I am not surprised there are some faults here and there with mine.
Update
Got my replacement Shield from tigerdirect and haven't experienced the issue in the 3 days I've used it (knocks on wood). Running lollipop just like the previous tablet, same apps installed through TBU. The last one I had would sleep of death about 2-3 times a day or more depending on use. Very happy with the product now I wish all my android devices were so smooth. My Transformer infinity is now nothing but a Netflix machine during cardio at the gym.
Unsure if this is valid info or not but on the 1st tablet I rooted using towelroot on kitkat, then used flashify to boot cwm and installed lollipop through cwm. On the new/2nd tablet I upgraded to lollipop through normal software updates, then unlocked bootloader and rooted. I don't think this makes a difference as I flashed back to factory image and stock bootloader on the 1st tablet, then upgraded using the same process I did on the 2nd and still got sleep of death. It seems to be a hardware related issue but thought I'd share anyhow.
Have same problem on my tablet. I think this is more software problame than hardware. All my hopes too new update/
I am having this same problem. I am totally stock LTE model. Trying to single out an app but it is doing it multiple times a day sometimes which makes it difficult to single out an app that could be the culprit(that and not being rooted). Hoping they release an upgrade soon.
Edit: this sleep of death problem did not occur before 5.0.1 BTW.
I had the problem from the start in August, when I got it. actually quite annoying and frequently. Resolved when I did a factory reset on the last 4.4 OTA. After upgrading to 5.0 I have had performance issues and some sleep of deaths again. But I did not come around to do a factory reset again since I am too lazy to back everything up . I am not sure if it is solely hardware related since at least for me, the factory reset cleared my problems once...
Mine only SODs when I change the performance mode and don't reboot, if I reboot after changing the performance mode it's fine.
Sent from my HTC One_M8 using Tapatalk
I have it also.. On 5.0.1 here.. But I solved it when I installed "ultimate on off" I think it prevent the device to be on deep sleep.. Ultimate on off helps me with the annoying power button..
seems like I fixed it
I think I narrowed it down to the app Tegra Zone. It had crashed a few times but the service was still running in the background. Uninstalled and my battery is lasting a bit longer and it hasn't wake locked on me in over 24 hours. The service is probably gimping the tab in the background.