Leaderboard

So ... last update: after applying some regular minor system update (58 megabytes) and a restart, the touchscreen started working again. It seems everything works now as expected, though it is weird I had to do something in order to be able to use "fastboot set_active a". Edit: locking it again (as it was supposed to be), worked, too. Why? Because in general I'd like to be able to use banking apps, that might not work otherwise. Thanks everyone for their efforts! Also: locking the phone erases the data.

Alright: so in order to repair it - sort-of - I had to use a certain package. After that I was able to do "fastboot set_active a" and reboot - AND it started booting again. I've still got another problem: somehow the touchscreen of the display does not work at all (hardware keys do though - don't ask me why). I'm gonna research more and since this won't be my daily driver anymore, I might as well just try SailfishOS or the likes. Anyhow: a massive thank you to @tdm and @EskeRahn - wouldn't be able to make it even this far without you!

Just for the sake of voicing what I have tried and done: Stuck in Fastboot Mode (probably after the last update) Booted into EDL-Mode (ABL/XBL using keys, 3rd option in tdm's instruction guite) Flashed while keeping data --> one of the boot partitions still was marked "not-unbootable:yes" Flashed without keeping data --> stats-wise everything looks fine to me --> Phone does not yet boot into anything else than Fastboot Mode and EDL-Mode (upon powering off and restarting into EDL-mode). If anyone attempts to use Q Flash Tool, I recommend the following:

I have a package to set the unlock flag without losing data. PM me.

Not necessarily electrical. It can be a problem of some kind of glue I think. I mean a glue inside the screen module - not screen assembly but in the screen itself which you can buy from 3rd-party sources. ...and that can be an aging problem and both @Milly and me are started having the same issue after about eight months of usage and the difference of our phone's age seems to be only this about one month (time elapsed since manufacturing is about the same) which is the difference of appearing these ghost inputs for us. However, fortunately, it seems only a small number of phones

The keys are double because there is one entry for press and one entry for release. Backspace, DEL, and a couple others will show "?". Yes, in your log, at the start of the second line, it missed the "i" completely. I find it interesting that most of the time you hold a key for about 10 to 20 jiffies, but those particular lines are the same timestamp: 0000551c <D 0000551c >E 0000551c > In other words, the log says you released D, then pressed E and space all within the same 0.01 second interval. That seems unlikely. But only you can know for

I think it is at similar position for me: https://youtu.be/BpIaO-91PGg

It looks like one of the slots is marked bootable and the other is not. I think they were both marked unbootable before? Try switching slots via "fastboot --set-active=b". If that still does not work, you may have bad flash memory or some other problem that I can't help you fix. EDIT: Also try booting to recovery and see what happens. And last resort, try doing a full flash including userdata. If the device won't boot and it needs to go back to the factory, your data is probably irretrievable anyway. 😞

Have flashed persist.img now. For doing it i need first unlock bootloader (and unlocking is full wipe), then flashing persist, then lock again - with unlocked BL Google pay doesn't work 😞 But, now i has worked fingerprint! Thanks

Hmm, it is more than interesting. I still curious if cleaning will help but this problem seems to have similar root cause, be it anything... dust, physical damage or screen aging issue... The same type and position of this problem is suspicious, but it still can be caused by some factors.

Try my factory restore tool first. If you cannot get that to work, send me a PM and I can try to help you fix it.

Yes, that thread. I guess he thought persist was not necessary. Here is a copy: http://files.nwwn.com/android/pro1/persist.img

Yes! Same position for sure.

Here a better video of the issue. It doesn't change our discussion much I guess, but it's good to have it in case 🙂 https://photos.app.goo.gl/YSi4MMPszJ3TbouA6

Maybe my suspicion of some dust can go below or near the screen can also be the cause. I don't know if there is some glue between screen and its frame or how it is applied, but I think my first try will be a cleaning of the bottom/side part of the display and the internal edges of the frame. So if I can separate the display and its frame without breaking (I have a high chance but should be prepared for the opposite), clean and reapply (and there is no damage can be seen on the screen itself), then I think the original display will work again perfectly. I am curious anyway and it may

Already have locked. Now i need only restore all previous apps and settings - not big problem

Yes, Pay and Netflix and some banking apps require a locked bootloader. You can lock it again from fastboot.

Here's something I just noticed is also fixed in the latest 0825 update: Android PhotoScan finally works. Before it would freeze or crash - not sure I saw anyone else report this bug (some other photo scan apps would crash too).

I'm not sure exactly where rollback protection data is stored, but I have never run into issues with it. If we do, I guess I can figure it out. But I try to keep the latest images available. Currently my latest is 20200707, as I haven't gotten a copy of the most recent update yet.

My issue was around that same line too.

Hm.. I tried flashing, but it says: target reported max download size of 536870912 bytes sending 'boot_b' (65536 KB)... OKAY [ 2.088s] writing 'boot_b'... FAILED (remote: Flashing is not allowed in Lock State) finished. total time: 2.089s remoteadmin@base:/mnt/storage/Temp/QX1000_user_20191028191838_0a493a1_Fastboot$ So .. I cannot flash? I am stuck in bootloader and I cannot chose to unlock it (I know the pattern). Any help here is greatly appreciated.

Sorry, still busy renovating my garage 🥴. Flashed the boot just this morning. Everything I type shows up double in de keylog. Some keys how up as question marks. This is what I typed: die overgang De moet ik nu dus gaan herstellen voordat ik de berging kan afmaken Ai, ben echt veel tegengekomen Log included.... In the second line, "De moet" it should state "Die moet". keylog

I examined the screen and its frame very closely from all sides, but I really cannot seem to find any form of damage whatsoever. I did notice that I can elicit the ghost inputs by very gently pressing, rather than merely touching, the screen on the strip where the ghost inputs would pop up. After that, the ghost taps may go on for a while without me touching it. So somehow it seems as if internally, some connections are made that should not be made upon applying a minimum amount of force - the amount of force I would also apply when simply taking the device out of my pocket.

Here is the debug kernel: http://files.nwwn.com/android/pro1/boot-keylog.img The file /sys/devices/soc/c17a000.i2c/i2c-6/6-0058/keylog records the last 256 key press/release events, one per line. The line format is: xxxxxxxx dK Where: xxxxxxxx is the time stamp in jiffies (1/100 sec), in hex. d is the direction, > for press, < for release. K is the key (without modifiers). It will only log the normal keys, not the gpio keys (shift, ctrl, alt, logo). You will need root access to read the file. I suggest an adb root session.

Indeed it looks like the greenish tint it was taking in very low brightness using Fx Service is mostly gone.