**** BEGIN LOGGING AT Sat Jan 05 02:59:56 2019 **** BEGIN LOGGING AT Sat Jan 05 06:03:04 2019 Jan 05 07:51:47 Morning! Jan 05 07:52:22 JaMa: I'm home and more available now; would a dd if=/dev/block/mmc... be enough for a dump of the partitions ? Jan 05 07:52:55 (I naively thought flash was just a dd in disguise) Jan 05 08:29:50 Tofe: probably not, e.g. persist is accessible when doing dd in twrp, but not all of them I believe Jan 05 08:31:02 I got the backup from elvis Jan 05 08:31:42 still better for you to do this low level backup, because if you brick yours you can always restore with EDL (even when you cannot get to twrp to restore with dd) Jan 05 08:37:09 ok, will do Jan 05 08:37:28 btw, doesn't elvispre have a weird partitionning, like with userdata{_a, _b} ? Jan 05 08:37:57 maybe it's just his onyx Jan 05 08:39:29 I've asked him to skip userdata and system partitions to make it smaller Jan 05 08:41:16 ok yes, of course Jan 05 08:43:40 FYI, I do get exactly the same size as the input images for original flash_all Jan 05 08:43:53 (I just tested modem_a) Jan 05 08:44:06 but I'll dump the whole thing with EDL Jan 05 08:44:51 ... which is Windows-only procedure /o\ Jan 05 08:49:48 JaMa: FYI, there is no "hidden" partition; everything is visible from recovery Jan 05 08:50:14 yes, it should be identical for most partitions, but it's still a bit unknown what some more hidden partitions (like efs) actually holds and if they are any different in the running system Jan 05 08:50:34 efs ? I didn't see that one in the xml Jan 05 08:50:39 I'm going to reboot to windows to restore elvis's backupt to see Jan 05 08:51:28 ok Jan 05 08:51:30 my bad efs isn't partition name https://forum.xda-developers.com/mi-a1/help/efs-backup-mi-a1-t3741757 Jan 05 08:56:47 if it's in persist.img, I'm not sure how this works, as persist.img is part of what is flashed by flash_all; I'll need to do more reading... Jan 05 08:57:26 ah, but modemst* isn't flashed by flash_all. So maybe that's the one. Jan 05 09:00:40 unfortunately didn't help :/ Jan 05 09:00:44 ok well, and these partitions might have a write-lock at the firmware level, only lifted by the EDL drivers; that would make sense Jan 05 09:01:25 so either it's HW issue or the ts calibration is stored somewhere else, not on EMMC Jan 05 09:01:35 JaMa: did you already try elvispre's backup ? Jan 05 09:02:23 yes Jan 05 09:02:29 ah... _o_ Jan 05 09:02:48 it takes only few mins to restore Jan 05 09:03:29 do you have some ts related error in twrp's dmesg ? Jan 05 09:03:46 like a firmware crc issue, or I don't know what Jan 05 09:04:13 I haven't noticed anything suspicious Jan 05 09:04:27 not even when running full android system Jan 05 09:05:40 I don't mind using mouse instead of touchscreen, but when trying to sideload I need the USB connector to be in host mode for mouse at the same time as device mode to connect to desktop :/ Jan 05 09:05:51 here's a working dmesg grepped on "TS" https://paste2.org/NGgkf5Zm Jan 05 09:06:03 so the only option is flashing with fastboot Jan 05 09:06:16 or need to find command line interface for recovery Jan 05 09:06:53 unfortunately the guys stopped doing non-touch versions of recoveries... Jan 05 09:06:54 JaMa: i heard it's possible to recalibrate touchscreen in android by entering some magic code Jan 05 09:07:19 nizovn: I hope you don't enter it by touch interactions ;) Jan 05 09:07:30 yes, but it only recalibrates the touches (like single, double, pinch, ..) Jan 05 09:07:49 I've already tried 3 apps (which claim to recalibrate) and tissot service menu Jan 05 09:08:02 ah.. Jan 05 09:08:16 in your case it's the coord system which is wrecked ? Jan 05 09:09:03 Tofe: you entre it by *#*#64663#*#* which I can do with mouse Jan 05 09:09:59 yes, and it's not only rotated, it's split in half, then rotated in some parts and some parts are showing two points far away from each other when presing just one dot Jan 05 09:10:42 oh. Jan 05 09:11:05 when I enable the touch visualization in developer menu in android I can sort of guess where it touches, but some parts of the screen aren't accessible at all Jan 05 09:11:14 including the "buttons" Jan 05 09:11:35 some lowlevel mapping seems completely off yes Jan 05 09:11:58 took me almost an hour to enable adb connection (which I had to disconnect mouse to connect to desktop) Jan 05 09:12:11 yes I was hoping that it's in one of these hidden partitions.. Jan 05 09:12:18 bbl, family arrived Jan 05 09:12:23 ok Jan 05 09:14:08 good news from the other front is that disabling NCQ completely helps with the 860 EVO drive Jan 05 09:15:51 :) one issue solved, one left ! Jan 05 09:18:52 worked around, still need to find out why I'm the only one seeing this issue, will try different sata controller and maybe different PC to see if it's because of my old MB Jan 05 09:19:51 my dmesg | grep TS is much longer Jan 05 09:20:45 https://paste.pound-python.org/show/lycGm9xlf55HYITRrZEN/ Jan 05 09:22:49 <3>[ 2.010588] [FTS]fts_ts_init: Exit(1506) Jan 05 09:22:49 <3>[ 2.220140] i2c-msm-v2 78b7000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x20 MSTR_STS:0x0d1300c8 OPER:0x00000090 Jan 05 09:22:54 looks like the culprint Jan 05 09:23:23 your exit init with different code <3>[ 1.500661] [FTS]fts_ts_init: Exit(1504) Jan 05 09:26:47 do you know what TS chip do you have? it's shown in the service menu (there are 4 options in various tissot batches) Jan 05 09:35:42 JaMa: I... didn't boot android for quite a while, but let me see Jan 05 09:49:08 JaMa: where in the menu ? Jan 05 09:55:58 meh, I don't even have the touchscreen tests in the hardware tests list... Jan 05 10:08:29 Tofe: let me find it Jan 05 10:22:06 god I hate this xda forum and a way how android binaries are shared around without sources, still it's the best information I've come across Jan 05 10:22:29 cannot find that topic which was showing 4 possible ts drivers Jan 05 10:27:00 Morning! Jan 05 10:28:26 Tofe: found it https://forum.xda-developers.com/showpost.php?p=74723385&postcount=30 Jan 05 10:28:55 I have the FocalTouch controller Jan 05 10:29:47 how to check is written a bit later in that thread: "Go to dialer and press *#*#6484#*#*, then tap version information, then scroll down to see LCD. Mine says **********(focal) so my touch panel is focal" Jan 05 10:34:35 i have focal too Jan 05 10:46:41 My touch panel is focal too. Jan 05 11:14:18 focal too Jan 05 12:05:28 Tofe: did you grep just uppercase TS? Can you please check case-insensitive? Jan 05 12:05:31 dmesg-2019-01-05:<6>[ 1.241609] ft5435_ts 3-0038: Current firmware: 0x0a.0.0 Jan 05 12:05:34 dmesg-2019-01-05:<6>[ 1.241615] ft5435_ts 3-0038: New firmware: 0x0a.0.0 Jan 05 12:05:36 this is from mine ^ Jan 05 12:06:22 or better send whole dmesg from twrp please Jan 05 12:07:00 there are some lines during firmware upgrade which doesn't have TP nor tp Jan 05 12:08:37 JaMa: https://bpaste.net/show/801e684b0602 Jan 05 12:09:01 ah, full dmesg, a moment Jan 05 12:09:46 full dmesg twrp: https://bpaste.net/show/354ddbce2b49 Jan 05 12:13:30 thanks Jan 05 12:13:59 what twrp version are you using? Jan 05 12:14:19 Linux version 3.18.31 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 SMP PREEMPT Thu Dec 20 14:49:40 UTC 2018 Jan 05 12:14:35 <5>[ 0.000000] Linux version 3.18.71-perf-gba69a07d5414 (lineage@jenkins.justbeca.us) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Jul 25 10:22:46 UTC 2018 Jan 05 12:15:22 mine is from twrp-3.2.3-1-tissot.img (the only twrp which worked for me now) lets see if the older twrp started to work now after restoring elvispre's backup Jan 05 12:17:53 e.g. twrp-3.2.1-0-tissot.img twrp-3.1.1-0-tissot.img still don't work for me (the screen shows the fastboot logo) and neither fastboot nor adb can comunicate with the phone Jan 05 12:44:15 interesting, cosmicdan's twrp supports OTG and now I have a mouse in twrp Jan 05 14:08:16 TS is working again! stock tissot_images_7.12.19_7.1 and/or cosmicdan's twrp helped! Jan 05 14:11:27 upgraded ft5435_ts fw to 16 seems to do the trick Jan 05 14:12:10 fw upgrade log in dmesg https://paste.ubuntu.com/p/Gnf8nffGs4/ Jan 05 14:39:53 The stock tissot_images_7.12.19_7.1 are what I always use to recover (thanks Tofe) Jan 05 14:40:28 JaMa: What on earth did you do to your tissot in the first place? Jan 05 18:35:24 elvispre: just left twrp over night and in the morning ts was br0ken Jan 05 18:35:57 elvispre: and I'm not alone, someone on xda reported the same Jan 05 18:36:43 https://forum.xda-developers.com/mi-a1/help/touch-t3769226 Jan 05 18:50:19 JaMa: Wow! I trust TWRP less and less with every new revelation :) Jan 05 19:41:04 back to windows to restore my EDL backup, then my original persist partition and then to test if it breaks TS again (and if it does then trying if tissot_images_7.12.19_7.1 fixes it again) :) **** ENDING LOGGING AT Sun Jan 06 02:59:57 2019