[Android Q&A, Help & Troubleshooting] samunders.core:
Hello

I've been using Vernee Thor Plus with stock firmware for almost 2 years now. I have not applied OTA update, just regular app updates from Google Play. Then one evening it was impossible to accept incomming call, swiping the screen did not work. I tried browsing the menu, closing background applications (here touch+swiping did work). So I chosen Hard reset and since then phone is in bootloop. When pressing Power+VolumeUp on boot I get menu with 3 options:

recovery - behaves the same as normal boot: vernee logo for ~30 seconds and reboot. I know I'm supposed to see green robot when choosing recovery, no such thing happens

fastboot - this is the only working option, variable list below

normal boot - loops after showing logo for ~ 30 seconds

sam_@herkales:~$ fastboot getvar all
(bootloader)	max-download-size: 0x8000000
(bootloader)	partition-size:flashinfo: 1000000
(bootloader)	partition-type:flashinfo: raw data
(bootloader)	partition-size:userdata: 32000000
(bootloader)	partition-type:userdata: ext4
(bootloader)	partition-size:cache: 1a800000
(bootloader)	partition-type:cache: ext4
(bootloader)	partition-size:system: d0000000
(bootloader)	partition-type:system: ext4
(bootloader)	partition-size:metadata: 2100000
(bootloader)	partition-type:metadata: raw data
(bootloader)	partition-size:nvdata: 2000000
(bootloader)	partition-type:nvdata: ext4
(bootloader)	partition-size:frp: 100000
(bootloader)	partition-type:frp: raw data
(bootloader)	partition-size:custom: 12c00000
(bootloader)	partition-type:custom: ext4
(bootloader)	partition-size:tee2: 500000
(bootloader)	partition-type:tee2: raw data
(bootloader)	partition-size:tee1: 500000
(bootloader)	partition-type:tee1: raw data
(bootloader)	partition-size:keystore: 800000
(bootloader)	partition-type:keystore: raw data
(bootloader)	partition-size:secro: 600000
(bootloader)	partition-type:secro: raw data
(bootloader)	partition-size:oemkeystore: 200000
(bootloader)	partition-type:oemkeystore: raw data
(bootloader)	partition-size:seccfg: 80000
(bootloader)	partition-type:seccfg: raw data
(bootloader)	partition-size:expdb: a00000
(bootloader)	partition-type:expdb: raw data
(bootloader)	partition-size:logo: 800000
(bootloader)	partition-type:logo: raw data
(bootloader)	partition-size:recovery: 1000000
(bootloader)	partition-type:recovery: raw data
(bootloader)	partition-size:boot: 1000000
(bootloader)	partition-type:boot: raw data
(bootloader)	partition-size:para: 80000
(bootloader)	partition-type:para: raw data
(bootloader)	partition-size:lk: 80000
(bootloader)	partition-type:lk: raw data
(bootloader)	partition-size:protect2: a00000
(bootloader)	partition-type:protect2: ext4
(bootloader)	partition-size:protect1: a00000
(bootloader)	partition-type:protect1: ext4
(bootloader)	partition-size:nvram: 500000
(bootloader)	partition-type:nvram: raw data
(bootloader)	partition-size:proinfo: 300000
(bootloader)	partition-type:proinfo: raw data
(bootloader)	partition-size:preloader: 40000
(bootloader)	partition-type:preloader: raw data
(bootloader)	off-mode-charge: 1
(bootloader)	warranty: yes
(bootloader)	unlocked: no
(bootloader)	secure: yes
(bootloader)	kernel: lk
(bootloader)	product: K19NTS_A
(bootloader)	version-preloader: 0.1.00
(bootloader)	version: 0.5
all: Done!!
finished. total time: 0.005s
sam_@herkales:~$

I know my way around linux, I assumed there will be some file/partition inaccessible. So I opened the device and accessed its UART, boot log produced with

fastboot oem p2u on && fastboot -c printk.disable_uart=0 continue

is here: bb67fad5eada1793f471b88f9aa8a993 @ gist.github.com/samunders-core

When buying I haven't planned any sort of tweaking/flashing, so I have no backup, neither data (no problem, just a few photos) nor firmware, therefore complete re-flashing is out of options as OTA is the only update available online. Still I have extracted boot.img file from official OTA (cannot post link), and flashed boot using SP Flash Tool. Nothing changed (wrt to bootloop/recovery doing nothing). I tried to flash modified logo just to confirm actual writes to flash are happening (notice locked bootloader in getvars), and yes, boot logo changed.

Log in gist @ github suggests instead of missing/corrupt file it's kernel panic? How can this happen with stock kernel?

Can anyone point me in right direction/otherwise help me? Thanks in advance, sam_