Hi guys. Over the weekend, I was running Android O beta, just to give it a spin and see how it was. Everything was working ok, but then I missed the good features of AOSP, so I decided to come back to it. So on Sunday night, I flashed back the previous rom, including the vendor, bootloader and radio as requested on the OP. But the problem was that the screen rotation wasn't working, no matter what I tried. I even tried other roms, to see if the problem was from the rom, but no, the problem persisted. I flashed stock again, and the problem was also there. I gave Google a call and they sent me some steps to go through and none of them solved my problem as well. So, I decided to flash back the O Beta, and voila, the problem was gone. My question, have I done anything wrong, any step that I may have missed? Or is it the drivers? Any help/suggestion is highly appreciatted
Did you factory reset or wiped data? It's sometimes necessary when downgrading.
I did yes. It was the first thing I did as soon as I got TWRP installed on it,because it was asking for the encryption key, to which it never what it was(tried my password and my lock screen code,but none of them worked,so just ended up wiping the whole data)
Related
Hi Guys,
I am not sure if I am posting in the right place, but I could use some assistance on the Team EOS nightlies. They won't let me post in the DEV section yet, becuase I am mostly reader, not a poster. Anyway....
I've been running the EOS roms for a while, but I can't seem to run any nightly past 74. 74 runs great, when I tried to update to 75 (rom/gapps/wipe cache) it won't get past the "DUAL CORE" logo. I thought I bricked my xoom, but I am able to boot to recovery, reflash 74 (gapps/wipe) and it boot with no issue. I did a full wipe, and tried again with 76 but no joy (77 wasn't out at the time). I thought it was a problem with n75 and n76. I flashed back to n14 and it works fine, and I can upgrade back to n74. Tonight I tried to update again to n77, but still no dice. I let it sit for 15 minutes at the "Dual Core" logo, and all I noticed is that is got warm, but still no boot.
Any thoughts? All advise is welcome!
BTW, this is for a Stingray 4g xoom
And while I have your attention, I love the work you guys do, and this community, it really makes Android something special!
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Still not working right, very frustrated, but I have new information
dellenrules said:
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Click to expand...
Click to collapse
bigrushdog said:
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Click to expand...
Click to collapse
Thanks to both of you. I did try this. What I have discovered so far is that some of the flashing fun I have been doing with my may have caused so minor issues with my external SD Card. I backed up the internal to it, and pulled it. I went through the process of nuking the xoom entirely. I.E. Wiped Cache, dalvik, full wipe, factory reset, reset permission, and deleted everything off the internal SD (wasn't in this order, but it all got done) I was able to flash N77, without GAPPS fine. It seemed to run faster with nothing else installed. Rebooted a few times, no problem. I was stoked. I flashed gapps, 03-17 version (the latest). factory reset again so that it was fresh and wiped the cache (just in case). It booted again no problems, ran me through initial config, and then began downloading my apps back. It seemed to run much faster than it ever did before.
Then I rebooted it, without doing any titanium backup restores, just fresh tablet, N77 with my 90 or so apps freshly installed from the market, and it froze again at the "Dual Core" boot screen. I waited hoping for some delayed joy, but none came.
So I went back through the process once again, factory reset, N77 install, wipe cache, install GAPPs. Booted.....initial config, auto downloaded 90 apps from market, reboot......dead.
So then I just flashed N74 again, wiped cache, install GAPPS, initial config, app download.....reboot.......works fine.
<general frustration directed at tablet, not anyone here/>
What gives???? I can't tell what the difference in internal apps in the ROM are that could be conflicting with the ones installed from the market.
Why the hell is N74 working and N77 not, when the apps in both ROMs look the same?
Why does N77 work great when the apps aren't restored?????
Why don't I make a million dollars?????
Why aren't I emperor of the universe???????????????
</general frustration directed at tablet, not anyone here>
Thanks much for all your help!
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
fkntwizted said:
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
Click to expand...
Click to collapse
He has the STINGRAY not the WINGRAY Xoom.
N77 is the latest for the 4G version. The version he has.
Read the OP
EOS Nightlies hate my xoom, my Xoom wanted CM9 I guess
joshndroid said:
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
Click to expand...
Click to collapse
Thanks much for this. I had already attempted the formatting of everything except the SD card before.....but for sh*ts and giggles I tried it one more time. unfortunately that didn't work.
Using the second option, of reverting stock, I went through sleeplessnija's tutorial on reverting. It really didn't seem that bad, taking me longer to setup my work machine than it did to send the fastboot commands. I was able to get it to boot stock (of course I didn't re-lock it) just fine, and it was quick....so it seems like my hardware is fine.
I used fastboot to put the replacement tiamat recovery, and formatted everything in the mounts menu again. I also mounted my SD card as USB storage and used the full format for it under windows. Then i copied N77 and GAPPS back to it, and re-installed them. It got to the second boot logo (first was the shaking team eos, the second is the square thing with rounded corners that moves). It hung for about 10 minutes, and I shut it off. annoyed.
So I went back into recovery, mounted my SD for USB access from my desktop, and copied the unofficial (which I think is now official) CM9 distro from Team Rogue (Steady's Rom I believe?). I formatted everything, and wiped everything (except the SD) again, and installed CM9 and gapps. Booted fine. Configured account, downloaded 90 apps, rebooted, no problems. Played with it for a while, rebooted....no problems.
I like that my xoom is back up and running......however it seemed that Steadies rom is just a little less fully featured than Team EOS. THAT IS NOT A KNOCK AGAINST TEAM ROGUE OR CM9.....my Xoom is working again (so far) thanks to him (them), and I run CM9 on my AT&T GSII. I just really like Team EOS on my Xoom, and have been with them since the beginning. I would love to know why my xoom suddenly hates the latest nightlies (everything since 74).
Edit: I forgot to ask, Joshndroid.....you mentioned running logcat to see what going on. If it can't boot past the dual core logo or the second boot logo from Team EOS....how do I get the logs? I am not familiar with android's logging.....even though I am a flash-a-holic. I am just thinking that if this is happening to me, maybe I can help out the devs (and myself, and maybe someone else) with the log output.
Edit 2: And Josh.....I forgot to tell you .....good call on the revert to stock answer. I didn't think about that before and thought I was screwed!
Thanks!!
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
Hello all
I am having a little bit of trouble with my TWRP recovery after flashing an updated version of a custom ROM, i have been using for a while.
I am using the latest version of the Pure Nexus ROM, and am currently un-rooted. I earlier want to try and clear my davlik cache as i was having a few little issues with some things, and wiping this has previously fixed the issue, i rebooted into the TWRP, and was asked for a password, which i thought would have been the PIN i use to unlock my phone. This then failed, and it proceeded to try and decrypt the partition. I left it doing this for about 20 mins, but nothing happened.
After reading up a little more, and trying a few different potential passwords to no avail, i read up that the password that TWRP was asking me for was related to the fact i had my phone set to ask for password on boot.
I removed this, and tried again. This time, TWRP just got stuck on the splash screen when trying to boot. Nothing happened for a good 10 minutes.
After putting the PIN settings back on, it goes back to asking for a password, that it wont take.
Whats my next option here, im kinda stuck. I really dont want to have to wipe the phone as i have just spent the best part of a week after flashing my new ROM getting it all back to how it was after flashing the new custom ROM i am using..
All help, much appreciated, thanks in advance
What version of TWRP are you using ?
No issues on TWRP 3.2.0.3
Sent from my Nexus 6P using Tapatalk
I'm on version 30.20
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!