I've been given an OP2 64GB as a project from a friend to try and return to stock and working. It was running a custom ROM which wasn't working particularly well, so I did the full reload to stock 3.0.2 via the Qualcomm download described here by @fareed_xtreme which downloaded okay, booted up, and the touchscreen seemingly didn't work. I've come across that before where there's been driver or firmware mismatches, but then I realised that if I held my finger on the screen for between 2 and 4 seconds, it'd start responding, right up until I let my fingers up off the screen. I could do multiple scrolls by adding a second finger to the mix, and it'd keep responding until I let go, at which point I'd have to hold down for another 2-4 seconds to make it do anything. The digitiser is fine, I enabled the overlays in dev tools (painfully clicking item by item!), and it shows the traces fine. They don't show up at all as screen presses until said delay happens, which is very odd. It also responded fine in the recovery, which was plain odd.
After a while, I tried returning it to 2.2.0 courtesy of @fareed_xtreme's other guide, which then worked fine, booted up, had 2.2.0 installed, touchscreen worked fine. Did notice the baseband version claimed it was unknown, though I'm unsure if this was related to me having no SIMs in it. It did initially offer me an OTA upgrade to the latest Marshmallow, which I allowed it to do, and promptly had the same issues again.
I've tried flashing various ROMs - Resurrection Remix etc, to find they've got the same problem. Any Marshmallow-based ROM seems to suffer from this weird input lag. The capacitive buttons are fine, it's just the display. Also, weirdly, it works if I touch the screen just as I wake the phone with the power button - so I can hit the power button and immediately swipe the lockscreen off, but then it reverts to the previous behaviour.
I've tried re-flashing the firmware for the various ROMs (matching with the installed ROM obviously). I've also repeatedly wiped the system/data/cache partitions etc, and have backups of EFS via TWRP saved off the phone. I also spotted two threads on the OnePlus forums describing this exact issue here and here, both with no solution. I also noticed people have had similar issues long ago when they tried installing H2OS and then returning to stock, without doing the full qualcomm download, but they seemed to be mostly solved with the full ROM reload and a cache wipe.
My next step is to flash back to 2.2.0, and incrementally upgrade with the OTAs, see if it works, but I suspect the second I make the jump to 3.0.2, I'll lose the touchscreen again. I've left it OEM unlocked, and got TWRP and original recoveries available.
To be honest, worst case, I just reflash the phone back to the final 2.x version, at least it actually works then, but... I'd really love to know why I can't fix this, and what the actual issue is, if anyone out there knows. There doesn't seem to be much on here in the way of people experiencing the issue - either that, or my search-fu has repeatedly failed me. My gut feeling is something kernel/driver related, but I don't understand why it wouldn't get fixed with the full firmware download via QC.
Help me, XDA, you're my only hope!
N2A said:
I've been given an OP2 64GB as a project from a friend to try and return to stock and working. It was running a custom ROM which wasn't working particularly well, so I did the full reload to stock 3.0.2 via the Qualcomm download described here by @fareed_xtreme which downloaded okay, booted up, and the touchscreen seemingly didn't work. I've come across that before where there's been driver or firmware mismatches, but then I realised that if I held my finger on the screen for between 2 and 4 seconds, it'd start responding, right up until I let my fingers up off the screen. I could do multiple scrolls by adding a second finger to the mix, and it'd keep responding until I let go, at which point I'd have to hold down for another 2-4 seconds to make it do anything. The digitiser is fine, I enabled the overlays in dev tools (painfully clicking item by item!), and it shows the traces fine. They don't show up at all as screen presses until said delay happens, which is very odd. It also responded fine in the recovery, which was plain odd.
After a while, I tried returning it to 2.2.0 courtesy of @fareed_xtreme's other guide, which then worked fine, booted up, had 2.2.0 installed, touchscreen worked fine. Did notice the baseband version claimed it was unknown, though I'm unsure if this was related to me having no SIMs in it. It did initially offer me an OTA upgrade to the latest Marshmallow, which I allowed it to do, and promptly had the same issues again.
I've tried flashing various ROMs - Resurrection Remix etc, to find they've got the same problem. Any Marshmallow-based ROM seems to suffer from this weird input lag. The capacitive buttons are fine, it's just the display. Also, weirdly, it works if I touch the screen just as I wake the phone with the power button - so I can hit the power button and immediately swipe the lockscreen off, but then it reverts to the previous behaviour.
I've tried re-flashing the firmware for the various ROMs (matching with the installed ROM obviously). I've also repeatedly wiped the system/data/cache partitions etc, and have backups of EFS via TWRP saved off the phone. I also spotted two threads on the OnePlus forums describing this exact issue here and here, both with no solution. I also noticed people have had similar issues long ago when they tried installing H2OS and then returning to stock, without doing the full qualcomm download, but they seemed to be mostly solved with the full ROM reload and a cache wipe.
My next step is to flash back to 2.2.0, and incrementally upgrade with the OTAs, see if it works, but I suspect the second I make the jump to 3.0.2, I'll lose the touchscreen again. I've left it OEM unlocked, and got TWRP and original recoveries available.
To be honest, worst case, I just reflash the phone back to the final 2.x version, at least it actually works then, but... I'd really love to know why I can't fix this, and what the actual issue is, if anyone out there knows. There doesn't seem to be much on here in the way of people experiencing the issue - either that, or my search-fu has repeatedly failed me. My gut feeling is something kernel/driver related, but I don't understand why it wouldn't get fixed with the full firmware download via QC.
Help me, XDA, you're my only hope!
Click to expand...
Click to collapse
I would suggest you to open a ticket with OnePlus Support (Live Chat). Inform them of the touchscreen scenario (Do not mention about the Quallcomm Flashing or they may start giving you a hard time for taking matters in your own hands). They will schedule you for the process and hopefully, they may be able to resolve it possibly with a newer Stock Reset.
Cheers, I'll give them a shot!
Unfortunately got no dice there - they reflashed it with OnePlus2_14_A.27_161227 (annoyingly, didn't get the decrypted files due to a screwup with my file mirroring), but still had precisely the same issue, up-to-date, no working touchscreen. If I can't get it working, it's not the end of the world, it's more annoying me that I can't figure it out... suggestions of a ROM to flash that might work would be most welcome!
Related
My wonderful wife gave me an Acer a500 for Christmas. Awesome gift. I had rooted it immediately with no problems, since all of my phones and families phone are rooted, it just seemed to be the natural thing to do.
As someone that "plays" with their android a lot I did all of the backups. Well, the time came to have my tablet "approved" for use at my company and also have the appropriate "encryption" software and keys added. Just as a precaution I decided to restore the original backup and unroot the tab.
All was going well until I received the update message. I went ahead and downloaded the update and ran it. During the install process it froze. I thought it was just busy so I left it for a good 20 minutes and finally realized it was frozen. I rebooted and it went through a couple of reboots and finally settled on the lock screen. But now I find the touch screen unresponsive.
I plugged in a mouse and keyboard in hopes that I could get back into it and start over, but, although, the mouse shows up, it is jumpy sluggish and will not grab the lock to slide open and eventually freezes.
I have tried all of the "update.zip" files I could find and they all fail at one point or another.
ADB allows me to explore in shell but since I unrooted, I cannot get su privileges.
Acer is of course, useless and the vendor it was purchased from is worthless.
I have been through every thread I could find and tried every trick I could come up with. Now I'm just stuck.
Any help is appreciated
I've had this a couple of times already. Usually just turning the screen off and on a couple of times does the job (the issue seems to be with the driver, also on various custom roms). Just try it after each off-on cycle, most of the time it takes no more than two or three tries, though there are exceptions.
Thanks, but it has been rebooted many many times since it's demise.
Decided to skip sleep tonight and keep plugging away.
I found an update.zip recovery file for an a501. Figured I can't do much worse so I went ahead and ran it.
It froze at about 95% but.........
Good News:
The tablet is responsive and touch panel works again.
Bad News:
It boots straight into system settings and although you can open the settings menu, nothing actually launches.
Decided to try all of the old update.zips and still everything fails.
No more ADB response.
When you originally unrooted your device did you revert back to the stock recovery or did you leave cwm on your device?? If you left cwm on your device that may be the problem with the update.zips and OTAs.
You are sooo right. I've never gone back to a stock rom before and I completely forgot about reverting to the stock recovery.
As a matter of fact, I was on Civato's Flexstriker 3.2.1 rom with the new CWM before I reverted back to the stock rom.
Well, at least we've determined my stupid mistake, but now the question lies: "How do I get back to any working rom?"
Here's an update. I did find an update.zip file that also begins to load but does not finish. It stops at 95% still.
I will attach the photos in case someone notices something otherwise I am at a loss. In addition to all of the above, I tried everything I could to get into APX mode but nothing. I am willing to try almost anything at this point, so all suggestions are appreciated.
Something I noticed was the recovery for the a501 was android with gears spinning in the body. The recovery I have now is a package with an arrow. The recoveries are different. The current update file is Acer_A500_1.145.05_COM_GEN1
So this brings me to a question: Can I put Thor's 1.6 CWM back on the a500 and at least work from there? I do have my original backups and thought I might be able to get somewhere that way.
Verizon Note 3 here, I received the Lollipop ota today and thought no harm in taking it as I was already stuck without root on 4.4.4.
It worked ok for the first couple minutes, then a reboot, then same thing, about 5 minutes and a reboot. Sometimes ~2 minutes, seems using it in any situation made the reboots happen. I did a factory reset thinking that would clear things up. Unfortunately now it is even worse, as it's rebooting anywhere from the first touch to the screen, to about 15 seconds of activity, literally dozens of reboots.
I downloaded the update on my pc and installed via Odin hoping that the ota was just corrupted or some bad luck like that. Nothing changed at all.
It will idle after booting just fine, I just can't do much of anything, every touch of the screen feels like a roll of the dice. Every few reboots or so I can make it to settings maybe but haven't been able to actually change much of anything, not that it would seem to matter here.
I've flashed via Odin twice, cleared the cashe many times, factory reset 3 or 4 times. Am I screwed here? What else to try?
*UPDATE* I flashed back to 4.4.4 with Odin and no more issues. It appears that my device alone is completely incompatible with the new firmware.
I should also note that I tried airplane mode, safe mode, and removing the sd card with no improvements.
After hours of messing with this thing and nearly giving up, not half an hour after I post here for help, I seem to have found a solution, although hopefully not a permanent one. The problem was happening when I would touch the screen, not scrolling ever, but making selections. On a whim I turned off sound and bam, no crashes.
I would still love it if someone had some insight about this problem, or better yet a solution.
I'm not sure yet if it is just the keypress sound that is killing it, or all sounds. I never did have any issues with the stock keyboard clicks now that I think of it, only the menu press sound. In any case it's not every time it made the sound, just half the time or so. Anything anybody could add to this would be appreciated.
*Edit* Not a solution, but it did help.
Well it's not as stable as I'd hoped. More like before the first factory reset now, but still not good at all. The various sounds definitely trigger crashes quickly(menu options, volume pings, mp3 songs from sd card), but regular silenced menu presses do sometimes as well still. Phone also bootloops several times often before it can get booted stable and 100% always crashes immediately if I try to unlock the screen in the first 5-10 seconds after booting up. Not sure if I'll be able to call or text as it's too late to test that atm. I'll update tomorrow, any insight appreciated.
I would say a bad download but I don't remember if ODIN checks MD5 sums (pretty sure it does). I would do a full wipe and reflash the stock image with odin
I am 100% stock not rooted never been rooted 5.0 vzw and I have had a couple of reboots. Never ever had one on this phone before. My old note 3 was rooted but I got this replacement after the root exploits had all been closed.
ehh not all have been closed
What is the root exploit for Verizon Note 3 with 5.0?
recDNA said:
What is the root exploit for Verizon Note 3 with 5.0?
Click to expand...
Click to collapse
None at the current time but CVE-2014-8609 seems like it could be some use
I spoke too soon when I said the phone was usable now. At best 5 minutes of light use as anything seems to crash it now. I did get a fresh image and used it with Odin with exactly the same result which makes me think its my phones hardware or something. Just seems crazy that it was working just fine before the update. The reason I pushed to 4.4.4 and lost root is because my phone suddenly started an issue where it would crash when making or receiving calls. It wasn't caused by any new apps or anything, just out of nowhere. I tried everything then updated as a last resort, carelessly I went to 4.4.4 instead of staying at 4.4.2 and lost chance of root, but it solved the problem I was having. I wonder if the issue is related somehow.
I was able to odin back to 4.4.4 and it's working fine so far, I assumed that you would not be able to revert back like the last ota and just tried it as a nothing to lose last effort. This is very important news to anybody that is having major issues with 5.0. Maybe, just maybe I'll try it again if they make an update patch for reported issues.
But for now, 4.4.4 it is for me.
VZW Note 3 update to Lollipop
I just finished the Lollipop update and my phone is working great for the past 30 minutes. Seems a little slower then usual but have had no issues besides my phone locking up after downloading the update, may have been due to my phone running down to 14%, but after removing the battery for 20 secs and putting it back on, phone came back on, I plugged into charger and started the update. Will post later if I have any issues.
I have been trying unsuccessfully through odin to downgrade but it keeps failing in odin, I downloaded the official firmware from sammobile.
Just curious if u r tried reinstalling newer odin? Try different USB port and cable. At this point maybe even try different pc if u have access to 1
I have flashed an unofficial build for the ZTE ZMax (Z970) and have been having a few issues with it. Hope fully someone can help even though it is "unofficial." Alright, so I'm having an issue with lag. Upon a fresh flash, reboot recovery flash to flash an add-on, a soft boot, or anytime the device leaves the operating system for whatever reason, it takes an average of 5 - 7 minutes for for the o.s. to apply boost, settings, or for the kernel auditor to begin doing its job. By that time I've already began having force closers on most apps, both system and downloaded. Also, I am having a buttons issue. Mainly the back button is the one to completely stop working but all have began having an issue with the amount of pressure it takes to have the device recognize you touching it. You know, as in I'll have to double tap the button with more pressure than it should ever take on the second tap after noticing the first tap was unsuccessfully sufficient. Then, I realize this really isn't an issue for this forum or its dev's but, maybe someone can help anyhow. When flashing the device I'm speaking of, I've got to flash a switcher.zip file to place the o.s. in the recovery position to be able to Mount it as r/w, which as I'm sure you already know also places the recovery in the o.s.'s partition. The problem I'm having is that the switcher.zip will quit switching after "x" amount of flashes. The restore.zip has always worked but the switcher.zip will quit on me. I've always been a huge fan of the ROM and would really like to stay with it so some assistance in helping to resolve these problems would be greatly appreciated!
Question
countryboy092782 said:
I have flashed an unofficial build for the ZTE ZMax (Z970) and have been having a few issues with it. Hope fully someone can help even though it is "unofficial." Alright, so I'm having an issue with lag. Upon a fresh flash, reboot recovery flash to flash an add-on, a soft boot, or anytime the device leaves the operating system for whatever reason, it takes an average of 5 - 7 minutes for for the o.s. to apply boost, settings, or for the kernel auditor to begin doing its job. By that time I've already began having force closers on most apps, both system and downloaded. Also, I am having a buttons issue. Mainly the back button is the one to completely stop working but all have began having an issue with the amount of pressure it takes to have the device recognize you touching it. You know, as in I'll have to double tap the button with more pressure than it should ever take on the second tap after noticing the first tap was unsuccessfully sufficient. Then, I realize this really isn't an issue for this forum or its dev's but, maybe someone can help anyhow. When flashing the device I'm speaking of, I've got to flash a switcher.zip file to place the o.s. in the recovery position to be able to Mount it as r/w, which as I'm sure you already know also places the recovery in the o.s.'s partition. The problem I'm having is that the switcher.zip will quit switching after "x" amount of flashes. The restore.zip has always worked but the switcher.zip will quit on me. I've always been a huge fan of the ROM and would really like to stay with it so some assistance in helping to resolve these problems would be greatly appreciated!
Click to expand...
Click to collapse
What was the unoffical build you used i would like to flash my zte zmax z970
Hey all,
First post here on XDA and I'm hoping someone with more experience than me will be able to give me a hand! Until last week or so, I was running an up-to-date version of Lollipop (5.1.1), when my tablet started randomly freezing up on me, requiring "soft resets" to get it going again, or simply shutting off on me. Thinking it was software related, I tried wiping the cache with no success, so ended up doing a full factory reset. The issues *seemed* to clear up for a day or so, but came back, and so figuring it was Lollipop related, I wiped out the OS and installed CM12.1 (which was my first experience working with ADB and fastboot, and first time installing a non-stock ROM) with a TWRP recovery. A few days later, the freezing and shutting down issues began popping up again, with the shutdowns *usually* happening during sleep, but the freezing happening at anytime from initial "Google" logo to boot animation, to the middle of running an app. I had made a backup on TWRP when I got CM12.1 configured the way I wanted it, so I performed a soft reset when it froze on me, and booted into the bootloader. The tab kept freezing in the TWRP window before I could select a restore, so out of desperation I tried just doing a factory reset from within TWRP. Long story short, something must have happened during that reset, because it kept hanging on the boot screen. I thought I may have unknowingly messed something up, so I tried downloading and flashing a stock KitKat (4.4) ROM from Google's site, but kept encountering bootloader errors during the flashing and ended up only being able to boot to the bootloader screen (apparently got a faulty 4.3 bootloader in that ROM, which gave me a headache until I was able to get straightened out). I have been able to get a stock bootloader (4.23) up and running now, along with a stock recovery (going with Lollipop now, so stock for LMY47V) going, but that's it. I've tried flashing the stock lollipop image via shell script (I'm running a Fedora 23 machine), via individual commands, and via "fastboot update -w factory_image.zip" without success. ADB sideload still works via recovery, but I wasn't able to sideload the OTA packages for 5.1 either. The common errors that pop up seem to indicate an error (corruption? fragmentation?) on the cache partition, but I'm not a dev when it comes to Android, so I'm at a loss here... I keep getting "E: failed to mount /cache (Invalid argument)", and other errors associated with accessing/opening files further down the /cache tree. Would this error be more likely to be a hardware issue, or would it be a software/firmware issue? I've had similar errors before with USB drives, when they would start to bad and partitions begin failing, but have always been able to rebuild them and get my data back. If something like this is happening on my N7 and the cache partition has indeed become somehow corrupted and failed (but not physically....), is it possible at all to rebuild partitions on Android in a similar manner? I've scoured the web, but haven't been able to find anything that can help me out with something like that, so I figured my best bet before condemning the N7 to the junk drawer was to see if any of the pros around here had any words of wisdom that *might* get me back up and running. Thoughts and advice much appreciated!!
Thanks!
(Oh, I apologize for the lengthy post, but I wanted to be sure to provide enough background info..... Sorry for the lengthy read!!)
Honestly that sounds more like a hardware problem than a software problem.
During the early stages of booting, everything that happens is extremely deterministic - meaning that it should be completely repeatable in terms of the order & timing in which activities occur.
So, for it to behave erratically during early boot suggests that it is not software, but marginal hardware. If hardware is barely meeting logic levels or timing requirements, a small amount of random noise (which is always present) can cause a fault to occur at any time - and that sounds approximately like what you are observing.
Further, you replaced your ROM entirely and the problem persists - again suggesting that the problem is hardware, not software.
The most cost effective way of dealing with repair of a $200 tablet is - unfortunately - disposing of it and buying a replacement.
Sorry.
Thanks for the reply!! Shoot, that's what I was leaning towards too. What is the life expectancy of these tablets? I mean, I got 3 good years of use out of it, so I'm not going to complain, but it seems like they should have lasted longer... Would it be worthwhile to maybe grab a cracked screen N7 off eBay for parts and try to get my tab working with those parts maybe? I'm hoping the rumors are true about Google coming out with a new tab this fall, but I'd love to get mine working before then lol...
Hi! I have an issue with a 64gb Nexus 6p (running stock android 8.1, latest patch, unlocked bootloader)
The phone consistiently runs extremely slow (taking 5 minutes to boot) and animations heavily lag, to the point where they are displayed over the top of the phone (I can unlock my phone using my passcode while the phone is still displaying its boot animation, for example, as it has booted but the animation has not stopped)
Also, occasionally half of the screen flashes white, back to normal, white twice, then the entire screen goes black, at which point it then returns to normal. This stopped when I flashed Lineage, however I have since restored the phone to stock and it has come back.
So far, I have tried to:
reflash updates
install a seperate kernel
install different ROMs
but nothing has worked
Would anyone be able to help?
It seems to most likely be a board issue, but I am still holding out hope that it could be related to software.
Try flashing its original stock firmware no updates. Load nothing else. If it's still doing it, it's hardware.
Some rootkits can survive a factory reset but not a firmware reflash; pre Pies OS's are vulnerable.
blackhawk said:
Try flashing its original stock firmware no updates. Load nothing else. If it's still doing it, it's hardware.
Some rootkits can survive a factory reset but not a firmware reflash; pre Pies OS's are vulnerable.
Click to expand...
Click to collapse
I already have tried that, several times.
Guess it's a hardware issue, then - regardless, thank you very much for the help.
I wonder what specific part of the hardware could cause this issue. I remember reading a user on this forum at one point have a similar issue, however he unrooted his 6p and the issue went away.