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

[Q] Screen Black But Touch Buttons Lit?

I thought I had a bricked infuse...but after unnecessarily removing the screen/components from the plastic casing and reassembling it, I tried recovering it again. I was FINALLY able to get it into download mode and then heimdal one click it back to stock. Everything went smoothly, but now when it "turns on" (I'm guessing), only the touch buttons at the bottom light up and respond to touch. The screen is absolutely black, except for the random FLASH that lasts a quarter of a second whenever I pull the battery and try rebooting it.
Has anyone ever had this problem before? I'm at a point where when it's on,( or at least I think it's on?), the touch buttons will light up and seem to respond to my touch (dim when touched). No vibrations of any sort though.
Please help
PS: If it is of any use..I used CM9 before all of this happened and I initially attempted to wipe it back to stock multiple times in the past, each time resulting in a frozen ODIN wipe. When I disconnected the phone during the process of wiping it, it no longer turned on or responded to charging the battery (I now have an external battery charger).
Also..when it is connected to my windows laptop, I get an error saying the USB device is malfunctioning.

At the very least it sounds like your internal drive is messed up. Try using the back to stock again - you could even try Odin again. However the problem could be more severe than that. You may want to make sure you reconnected all the components properly. One slightly loose connection can cause problems like you're having. I'm thinking that you might have a loose screen connector.

Pok3rr said:
but after unnecessarily removing the screen/components from the plastic casing and reassembling it
Click to expand...
Click to collapse
Also.may have something to do with that...not saying it is but that's a possibility, if you were to.rough with something or gave off a static discharge (computer motherboards are extremely sensitive to static...I'd assume mobile motherboards are too...)
Anyways try running Odin/heimdall again...
Sent from my HTC PH39100 using Tapatalk 2

I'm having the same problem
Pok3rr said:
I thought I had a bricked infuse...but after unnecessarily removing the screen/components from the plastic casing and reassembling it, I tried recovering it again. I was FINALLY able to get it into download mode and then heimdal one click it back to stock. Everything went smoothly, but now when it "turns on" (I'm guessing), only the touch buttons at the bottom light up and respond to touch. The screen is absolutely black, except for the random FLASH that lasts a quarter of a second whenever I pull the battery and try rebooting it.
Has anyone ever had this problem before? I'm at a point where when it's on,( or at least I think it's on?), the touch buttons will light up and seem to respond to my touch (dim when touched). No vibrations of any sort though.
Click to expand...
Click to collapse
My Infuse is doing the same thing, black screen, but touch buttons on. Every once in a while the lock screen pops up and you can get into the phone, but then it goes black again. My phone is not rooted and we haven't done anything except install some programs, but nothing recently. It only happens intermittently, so I think this may be a hardware related problem, but it would be great if anyone has any other ideas on the cause or a fix. Otherwise I suppose we'll have to see about having it repaired or get a new phone.

[URGENT] Touch Screen Unresponsive in Recovery

Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...

I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time

thelestat said:
I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time
Click to expand...
Click to collapse
It's weird...I flip back between AK and the stock CM kernel, and the touchscreen works for maybe an hour, then it goes completely dead again (including when in recovery). And the touchscreen is dead no matter which recovery I use, whether it be TWRP or CWM.

Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it

demkantor said:
Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it
Click to expand...
Click to collapse
I've got it back to working by messing with the kernel a little bit. How's the progress with the LOGO partition going? I saw that in the other thread, you almost bricked your OPO

Yeah it was an unfortunate mistake on my behalf while digging into it deeper, luckily all worked out in the end
Haven't had the chance to make more progress, the wife and I had our first child on Friday and I still have one more week of finals left (until I'm done with college for good!)
I hope to have some more time this next week to figure the rest out, I'm sure its doable but I don't want to risk anything before I know more!

Touch screen unresponsive
Any solution to this problem? Running 11.0-XNPH30O
Android 4.4.4 that was updated two days ago.
The touchscreen becomes unresponsive every hour or two and need to force turn off the phone by holding down the power and restarting.
Have had the phone for a little over a week and annoyed by little issues here and there. The orientation change (when turning phone for auto rotate) on a picture takes too long. Speaker phone was a problem initially, fixed with an update and now this touch screen unresponsiveness.
Doesn't matter if it's Synaptics or not. cyanogenmod and one plus need to figure out a solution and not sell a buggy phone on the most important features of a touch screen phone. ITS TOUCH SCREEN.
If I don't see a fix in 48 hours, I'll be returning the phone or selling it on eBay.
treChoy said:
Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...
Click to expand...
Click to collapse

treChoy said:
I've got it back to working by messing with the kernel a little bit.
Click to expand...
Click to collapse
I've got a touchscreen dead zone at the bottom, just all the navbar area. I wonder if it could be possible to get it back to working by messing with the kernel as you did. Which kernel and tweaks.
Thanks.
Edit: now the dead zone has extended to the hardware buttons. I have to rotate the screen 180° in order to be able to use the navbar.
Thanks

Touch screen no longer responsive

My wife had her portable for 13 months and the touchscreen decides to not work. I did a factory data reset and nothing. Everything else works fine. It's not ever been dropped. The screen just doesn't respond to touches. The thumbstick works though for the mouse and the trigger works for clicking. The device has never been rooted.
I was told by Nvidia to flash the recovery image. So I try this, and man it was a pain in the ass because I've never done this before and the bootloader screen had the white screen of death described in another thread. So for me to flash the recovery image, I had to watch a video of someone doing it and then blindly follow the inputs and mimic them on my blank white screen.
Well I finally got it flashed and still no dice. From what I have been reading the flex cable on the LCD screen is the issue. Because when I power it on, if I don't have it flipped all the way open, I will have the white screen of death.
Anyone know where I can have this repaired? I live in Cincinnati OH. Also I have another portable myself and I know this is going to eventually happen to it as well :-/

Anything I can about my broken pixel xl

I think saltwater damaged my pixel. It endlessly boots, showing the Google logo on white screen then "turns off" and boots it again. One time, randomly, somehow it made it to the lock screen and did show my custom wallpaper, but seemingly nothing was responsive - swiping, buttons, fingerprint.
Anything I might be able to try or diagnose to possibly save the phone? Anyway I could at least recover the photos (not everything had finished backing up).

This is probably hardware damage. Maybe insurance will cover it, maybe not due to water. Everyone knows Bout the indicator for water damage. But, factory reset in recovery mode is worth a try. If you can even get that much functionality. Or better, if the bootloader was unlocked or that be attained. Try to flash a stock factory image.