Related
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...
Soo I have a big problem,
My sidekick 4g suddenly shut off and directly went into Download Bootloader. It would only stay in that window for about 3 seconds then restart. So I tried doing Odin but it would never stay in download mode long enough. After a while, the phone stopped turning on and now it does not even charge. I believe I have hard bricked the phone. When I leave it on the charger. I see no indication that it is charging but the battery gets warm. Is there any hope for me to fix this phone?
Please let me know ASAP. Thanks!
helodavelo said:
Soo I have a big problem,
My sidekick 4g suddenly shut off and directly went into Download Bootloader. It would only stay in that window for about 3 seconds then restart. So I tried doing Odin but it would never stay in download mode long enough. After a while, the phone stopped turning on and now it does not even charge. I believe I have hard bricked the phone. When I leave it on the charger. I see no indication that it is charging but the battery gets warm. Is there any hope for me to fix this phone?
Please let me know ASAP. Thanks!
Click to expand...
Click to collapse
Does the device even show up as a USB vendor/product id? See that with `lsusb` on Linux or the Device Manager on Windows.
It might be worth trying ayoteddy's FOOL PROOF WAY TO GET INTO DOWNLOAD MODE here:
http://forum.xda-developers.com/showthread.php?t=1186954
Perhaps if you trigger the phone to enter download mode that way, it won't just continually reboot...
Beyond that, I think you'll be looking at hardware-level fixes. If the phone isn't literally fried, it can almost certainly be repaired with JTAG. But that would involve a JTAG interface which I am guessing you don't already have.
You might be able to find someone who will JTAG for you for free, or for a fee. A local phone repair shop might have this capability.
If you're damn good with a soldering iron, or have a friend who is, there's also AdamOutler's "UnbrickableMod":
http://forum.xda-developers.com/showthread.php?t=1347984
That mod is not for the feint of heart, you need to take the phone almost entirely apart and do soldering work within the area of a grain of rice... but it is possible.
But all the options assume that the only problem with the device is a bad flash -- damaged boot loader, bad kernel/recovery, etc. The way you describe your phone's demise, a hardware failure certainly seems like a possibility.
Good luck, I hope your device is not dead.
FWIW, SK4G goes for ~$100-200 on eBay these days depending on condition. Locally you could probably find lower prices.
Wow thanks for all the info but i tried ayoteddy. Since the phone doesnt even power on , i cant do what teddy says. And no, after a few failed odins, the comp doesn't even see the phone. But that's also because the phone doesn't turn on. I even put a charged bat. Still no go
helodavelo said:
Wow thanks for all the info but i tried ayoteddy. Since the phone doesnt even power on , i cant do what teddy says. And no, after a few failed odins, the comp doesn't even see the phone. But that's also because the phone doesn't turn on. I even put a charged bat. Still no go
Click to expand...
Click to collapse
It really sounds like a hardware failure.
If you are committed to trying everything to rescue your particular device, you could double down and try a new battery. You risk wasting whatever money you spend on it, of course.
If I recall correctly, the SK4G can't operate properly without some battery current, even when plugged into USB. And the other symptoms seem to leave the door open on battery problems -- sudden power down, brief signs of life which eventually cease, hot battery. The sudden failure of a lithium battery would hardly be unusual.
I have seen an issue very similar to this before. It turned out to be a loose connection inside the phone. Might want to disassemble and reassemble carefully to ensure that the connections are secure. Youtube has dis-assembly videos to guide you. You don't have to completely disassemble the phone, just til you reach the main board and secure the connections to it. If you don't feel like you can hand the task of dis-assembly you could always search for a local phone repair business, or even computer repair shop (they often do some phone repairs). Hope this helps
Hey there, I am trying to fix a SK4G with the exact same problems... download mode will show up, but then the screen will go blank again. I'm gonna look into what blk2dr suggested... did you ever fix yours, OP?
root? so Warranty it, not saying its the most "ethical way"
out of curiosity what was the last, well as samsung would put it, hac...ERRRR unsupported warranty voiding modification known to us as upgrade/flash eg. via cwm odin rom app add on modem kernel etc. that was done to the ol SK? or is it just straight up faulty craftsmanship from samsung...nooooo on a SK4g??? is that possible? lol moving a rom around from folder to root of sd once (zip prev passed md5 check) my 2nd or was it 3rd t839 had a lil hiccup that i didnt realize at the time made my custom Roms zip like 47kb smaller then it previously was and should of been, when flashing is 2nd nature and ur just moving it within the same sd card its already checked out on the md5 sum and ur dealing with a 200+/-mb file, whos gonna notice that minor change? to make a really long story just kinda long, into voodoo cwm flash, let it marinate... phone ran great for 4 days, then i decided i was going to clear cache davlik fix permish and reboot...yea went into cwm wiped wiped and half way thru fix permish phone crashed rebooted back into recov, when i tried to reboot sys it had your same exact issue. DL mode for just a second...then all black yet slightly backlit screen. could never get it to stay long enuff to odin back to stock, fullproof DL mode was a no go and of course the battery died, wouldnt recharge. i played dumb went to tmo store dude tesed phone with new batt my batt in other sk etc etc...anyways he charged my battery up enuff it flared back into dl mode for a few sec...my fix? hours and days headin into weeks of jackin with this thing i went with my cure all root REUPwarranty fix...flash a bad freakin bootloader thru odin and kill it once ad for all, DL mode only needs to be on about 4 sec, not long enough to go back to stock rom but long enuff to kill that B. prefered bootloader is i9000 haha works like a champ everytime to every rooted phone that had issues i needed a warranty exchange on(only been 4) seeing how i get a new phone every 3months on avg and always pay full price the ratio is tiny. yeah i know the trickle down effect raising costs from manufacture in long run yadayada. all is true, but i figure ive been kicked in the groin so many times by samsung,lg,moto,htc etc they can eat 1 every now and then. as a tmo employee in 07/08 i paid 500 upfront for the mda that got back ordered for 6 months had 2 bad dead spots in the touch screen within a month and screen went completely white in 3mnths. some employee/warranty fine print screwed me out of a new phone. and dont even get me started on the sidekick. 399 bucks for a phone that basically got abandoned 3 months later cuz it was junk compared to what it should be and breaks in high quanities. theyll still tax u 20 bucks and make u keep ur old battery and cover charger etc so im not losin any sleep, for real kill it for good, run it to the store get ur new err rebuilt refurb SK4g in 2 days then save up for a t989 s2 dl gmote/spashtop and poweramp on ur SK4g and let her roll as a wireless keyboard/mousepad for ur pc and let the voodoo and Pamp rock as a killer mp3 player. thats all the T-urd-839 is really good for anyways, oh yea and a mediocre bt controller for playin games on my S2's lol do the warranty, its samsung/TMOs fault for lettin this junk product get released, abandoning it and overcharging so many of us. Just do it, do it lol
pull battery, connect usb, hold power, volume up, volume down, camera, and tackpad and insert battery. It should FORCE the phone into download mode.
try it lol~
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.