Database Info

Rooted, Running Revolver, Screen Problem

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...

Screen not turning on, but HDMI works

Hey everyone.
My dads TF101 all of a sudden decided not to turn on. Now we were trying to fix it and he decided to plug the HDMI in to a computer and voila the screen pops up and the touchscreen works, but not on the tablet. I'm wondering if reflashing a rom (I'm running Eos 2-21 (not the latest I know..)) would possible fix the problem, if not putting it to stock and warrantying the tablet. But i'm also wondering does CWM work via HDMI. Any help would be appreciated =D

Dark lord me said:
Hey everyone.
My dads TF101 all of a sudden decided not to turn on. Now we were trying to fix it and he decided to plug the HDMI in to a computer and voila the screen pops up and the touchscreen works, but not on the tablet. I'm wondering if reflashing a rom (I'm running Eos 2-21 (not the latest I know..)) would possible fix the problem, if not putting it to stock and warrantying the tablet. But i'm also wondering does CWM work via HDMI. Any help would be appreciated =D
Click to expand...
Click to collapse
My guess - your backlight or screen stopped working. It could be a loose connection, the display cable runs around the battery and if it is dropped it can come unplugged.
Flashing a different ROM or re-flashing is not going to fix a hardware issue like the screen not working. Just to be sure, do you see the Eee Pad logo when you turn it on?
Also, if you shine a flashlight on the screen, can you see the screen faintly? If so, then it is the backlight that went. If you cannot see anything, most likely it is the screen that stopped working.
If you are still under warranty, the easy thing to do is to flash back to stock. You can try using recovery, but I am not sure the HDMI will work with that. If not, you can use EasyFlasher and flash the stock firmware via APX mode. See the EasyFlasher thread in the dev section.

When i turn it on there is a light but its as if it's a black screen.
Never saw that EasyFlasher, that will make things a lot easier. And yeah three year wanrrenty, makes me feel a lot better about dropping the cash on one of those now that I actually need to use it

Dark lord me said:
When i turn it on there is a light but its as if it's a black screen.
Never saw that EasyFlasher, that will make things a lot easier. And yeah three year wanrrenty, makes me feel a lot better about dropping the cash on one of those now that I actually need to use it
Click to expand...
Click to collapse
If it lights up, but no screen, then it is your TFT that has gone, the backlight is still working.

frederuco said:
If it lights up, but no screen, then it is your TFT that has gone, the backlight is still working.
Click to expand...
Click to collapse
Well wither way the screens gone. seriously thank you so much least now I know what is wrong
One more question, does CWM work while in HDMI mode because i could flash the stock software that way

Dark lord me said:
Well wither way the screens gone. seriously thank you so much least now I know what is wrong
One more question, does CWM work while in HDMI mode because i could flash the stock software that way
Click to expand...
Click to collapse
I can't answer your CWM question (my guess would be no), but if you use easyflasher, all you need is working APX mode and a windows computer. All the details are in the tread.

[Q] Tf300t Ghost Touches

Hello there,
I've had several issues with my tf300t that really annoyed me. Well, first off, all of a sudden the touchscreen stopped working. I tried a hard reset, then a cold boot, no success. Then i had it sent to be fixed. After one entire month i got my tf300t back and verified if everything was back to normal. The touchscreen was working properly but after just one hour i noticed that i have ghost touches once again. I know what ghost touches are, i did a lot of research.
I had ghost touches before i had my tf300t sent to be fixed. Is it really a hardware issue? Because theese annoying ghost touches stop everytime after i do a cold boot. Sadly, they come back after a while, mostly after i turn my wifi on. Everything goes haywire.
What should i do? Send it back? The thing is that i rooted my tf300t and this kinda voids my warranty.
Sometimes i even experiment dead zones on my touchscreen. They go away everytime after i do a cold boot but this thing is really starting to piss me off. How did you guys manage to get rid of theese ghost touches?

You could try to update the digitizer firmware. Check out the threads about digitizer replacement. Basically you just need to run the touch_fw_update command. Either with the firmware already installed or download the 4820 version. Could also be a loose cable. Before messing with any cables, turn off your service switch.

I have a nexus5 as well as a TF300T and have noticed on the N5 that when charging you can get ghost images its like the digitizer goes a little mental when charging. It is a known bug (various reports to google) and something they are working on. Could the TF300T have a similar bug?

SM-P900 Wifi Touch Screen has Malfunctioned

Hello All,
In my attempt to root the device which I was successful in doing somehow things went south when i tried to flash TWRP on my device. I performed the .img to tar.md5 conversion with the CWM Tool on another thread then i flashed the file to my device, afterwards the devices were rebooted and now I am unable to touch the screen with my fingers and only my S-Pen works, which tells me hardware wise the screen is ok but something software wise is causing this issue. Can someone please help me in troubleshooting this issue. I seen another user have this same exact issue but it ended with him sending it to the service center. I have performed a full dat/factory reset.... I have performed a full reflashing of the stock rom i have re-rooted. I am all out of options.
See video i made regarding this issue.
https://www.youtube.com/watch?v=orLEnWhlATo
Thanks in advance!

Can anyone help with this

Capacitive touch and spen use 2 totally different chips inside the tablet. The spen uses a Wacom digitizer, while touch interaction is processed using standard methods.
In fact, each one has their own ribbon cable from the screen to different points on the motherboard.
I have no idea how rooting broke your touch ability, but the spen working is not an indication that the touch interaction is not damaged in some way.
I can tell you that on mine (especially when using papyrus) it has a tendency to lose touch until I shut the screen off and turn it back on. Maybe something screwy is going on with the touch driver. Flash back to stock and see if it's still broken

Did the reset work?
I ask because we just got a used tablet off ebay and it is doing the same thing to me. My wife emailed Samsung who said blah-blah-blah so we are stuck with it. I know enough to brick a phone really fast, but I have been running custom Roms a long time and have replaced screens so I may check the cables on my day off.
But it was doing it before I rooted it, recovery, and Hyper-drive Rom.
though the knox had been tripped before I got it, so I don't know what has been done to it before this. So please let me know what you think even if you try it and it does or doesn't work and I will gladly do the same for you.
Thanks--Rick

Unresponsive Touch Screen. Some Ghost Touches.

Hi,
My TF300T stopped responding to my touches and has some ghost touches now occurring just under the ASUS logo in the bezel. Has anyone else experienced this and can offer a fix? Is this a shot digitizer?
FYI, I've tried a cold start, cleaning the screen, and resetting the tablet using the small hole on the left. None of those worked. The track pad still works so I can still use the tablet as a netbook, but that sucks.
Any other suggestions?

DoughMucker said:
Hi,
My TF300T stopped responding to my touches and has some ghost touches now occurring just under the ASUS logo in the bezel. Has anyone else experienced this and can offer a fix? Is this a shot digitizer?
FYI, I've tried a cold start, cleaning the screen, and resetting the tablet using the small hole on the left. None of those worked. The track pad still works so I can still use the tablet as a netbook, but that sucks.
Any other suggestions?
Click to expand...
Click to collapse
Please look at this thread http://forum.xda-developers.com/showthread.php?t=2021701!

ebonit said:
Please look at this thread http://forum.xda-developers.com/showthread.php?t=2021701!
Click to expand...
Click to collapse
I've tried all the fixes in that thread. And in that thread, their screens still work for them ... mine doesn't at all.
FYI, I also don't use a screen protector

DoughMucker said:
I've tried all the fixes in that thread. And in that thread, their screens still work for them ... mine doesn't at all.
Click to expand...
Click to collapse
I can understand. There is also a lot of trash in that thread and no convincing solution except via RMA from Asus. It's still a mystery!
I don't know what rom do you use and what recovery. What do you think about format data (not wipe or factory reset) and then a clean reinstallation of your current rom. If it is a soft ware problem it might be solved. If not it might surly be a hard ware problem. That means to swap the touch screen. On the other hand before realize such a decision you could try get back to the last Asus stock rom JB and look what happened then. Trial and error is the only way to figure out the cause in order to solve it. Please keep us posted whatever you are going to try. Thanks!

I'm using KatKiss MM v28 and Kang TWRP 2.8.7.2. I launched TWRP, but was unable to use either the touchscreen nor trackpad. The trackpad is unsupported in the version I use, I guess. I suspect this is a hardware issue as the touchscreen didn't work in TWRP.
I'm travelling now and don't have a suitable place to open up the tablet to look for loose connections. I'll do that when I get home.

DoughMucker said:
I'm using KatKiss MM v28 and Kang TWRP 2.8.7.2. I launched TWRP, but was unable to use either the touchscreen nor trackpad. The trackpad is unsupported in the version I use, I guess. I suspect this is a hardware issue as the touchscreen didn't work in TWRP.
Click to expand...
Click to collapse
Regarding your suspicion about the track pad support I may tell you the inverse. I'm also using #28 and the same TWRP like you. The track pad of the dock works fine and the USB mouse as well either wireless or with cable. I have tried both.

ebonit said:
The track pad of the dock works fine and the USB mouse as well either wireless or with cable. I have tried both.
Click to expand...
Click to collapse
Hmm. I wonder if the ghost touches are interfering with the trackpad. I'll try a USB mouse when I'm back at home. Thanks for confirming they work in TWRP.

Tried a USB mouse in TWRP. It works. Flashed v29, but the issue remains. I may try formattig data later.
I took the back off the tablet and disconnected a couple connections on the digitizer. I first disconnected the two smaller ribbon cables. The ghost touches remained after rebooting. I then disconnected the larger cable above them and the ghost touches stopped.
I think I'll look into a replacement digitizer.