hello, my screen right side 1cm touch screen not working anymore idk how it happend, phone isnt dropped or scrached or damaged. please if anyone know about this help me, how to fix ?
Solved
I have same issue. Everything was working fine until I tried to restore my backup via safestrap recovery. I ended up to a bootloop because the backup was corrupted. The phone got really messed up and didn't charge anymore for some reason. Then I flashed stock JB build via RSD Lite. I used "VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip" file. Phone booted up normally but the backlight of recents app and home buttons were not working. However, the backlight of back and search buttons are working.
I don't mind about the backlights because I would turn them off anyway. The biggest problem is that there is about 1cm thick line on the screen which doesn't regognice touch. Everything else seems to work. I didn't drop the phone or anything like that.
I tried to flash Lineage 14.1 and different kernels but without any luck. Also I just reflashed the stock JB rom via RSD Lite. Still same situation. Is there anything else I could try? Thanks!
EDIT: Whoa!
I was able to fix this and is was very simple. I just followed this YouTube video :good:. I just had to try twice and turn off screen after doing that.
Related
Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?
Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didn´t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.
Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/
Hardware problem.
That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??
I was using JB 4.1.1 previously and decided to flash to a new 4.1.2 rom this morning. Everything was fine until the Samsung animation screen. There is no display. My screen is completely dark. But the phone responds when I touch the screen and the home button as well as the power button.
I thought this is the LCD problem but when I boot to Recovery, the display turns on and everything is fine. So I decided to flash to another rom but the same problem occurs. Did I brick my phone? Any solution guys? Some help would be very much appreciated.
IlDivinCodino said:
I was using JB 4.1.1 previously and decided to flash to a new 4.1.2 rom this morning. Everything was fine until the Samsung animation screen. There is no display. My screen is completely dark. But the phone responds when I touch the screen and the home button as well as the power button.
I thought this is the LCD problem but when I boot to Recovery, the display turns on and everything is fine. So I decided to flash to another rom but the same problem occurs. Did I brick my phone? Any solution guys? Some help would be very much appreciated.
Click to expand...
Click to collapse
Try to do checksum on the ROM zip file you flashed, if it was correct.. then try to do a fresh new flash of the ROM:
1- Make sure you're on a safe kernel .. if not, please flash a safe kernel (I prefer Abyss GB Kernel)
2- flash the file in the attachments
3- flash your ROM file
my xt890 lcd screen and digitizer were broken so i changed them and the phone was working fine for a week, i then wanted to update to kitkat through oem update; everytime i tried it would give me error . i then read that since i unlocked bootloader and rooted my phone and installed cwm recovery i couldnt do an oem update and i had to do a factory reset in order to update through oem, so i did just that ; after the phone finished factory reset and booted i proceeded with oem update while the phone was charging, everything was going fine the file was downloading, i went to the bathroom and came back the display was black, but touch screen was working fine...through more searching i read that this could be from the update, and i should do another reset... since i couldnt see anything even recovery menu. i downloaded moborobo so i can see my screen on pc and proceeded to factory reset ... now i cant even see through moborobo and im stuck. i think im stuck in recovery screen, but no way to be sure , hence i cant get usb debug.Please help.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
Im at a loss here so I come to you guys in desperation. The home button and power button work fine in TWRP but do nothing in the actual operating system. Also the capacitive buttons dont light up or work for that matter. I havent succesfully flashed a custom rom yet as I kept having boot loop issues but I did a fresh install with kies and still no go. Anybody seen anything like this? Its a T-813 if that matters...
I have my rog 2 stuck in a bootloop. I don't really know why in the first place, because I don't like to change and mess around with custom roms. So i've never done that.
The case was that I was watching a video on YouTube and suddenly the touch screen stopped responding, the phone kept responding to other inputs such as the power button and the volume rocker. So I decided to restart the phone. And then it didn't turn on again. Got stuck in a boot loop.
I've been trying to fix it for a long time. But I just can't do it. Nor am I able to see what is happening with the phone. I have used this guide.
EVERYTHING works perfectly, it doesn't give me any errors during flashing or anything like that. Even the program tells me that the rom has been flashed correctly, and even the rog logo during boot, changes (I suppose because it is a version of the rom prior to the one I had.). The fact is that even with that the phone is still stuck in the bootloop. I have tried more things but this is the one that has taken me the furthest. I don't know what else to try. If anyone has any ideas, please tell me.
P.D. Sorry if my English is a bit rusty.
go back to stock and try other rom.
atoyu said:
go back to stock and try other rom.
Click to expand...
Click to collapse
Any suggestions which rom I can use? I have tried the rom of the guide and the ones that Asus has on their website. None of them have bailed me out.
@Arnau17 Any Updates? I am facing the same issue. Mine reaches till boot logo and then freezes and reboots again. Tried flashing stock ROM as well but no Luck
I am in the same situation, tried several raw rom files, still in bootloop
USB plug correctly on side USB port? can you enter recovery or fastboot mode?
i have same problems before, if fixed after flash RAW rom, hope this help.
is there a guide to fix AVB VERIFY FAIL on Rog Phone 2