[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Restoring TWRP Backup possibly breaks your system

The last days I had extremly high battery drain when screen was on. Like 33% in an hour (aproximately).

When I opened a terminal and checked whats going on, one CPU was used by logd, one CPU was used by /system/bin/pm-service. The phone was notably warm, even though I was just reading news.

Later I found out, that the system log (aka logcat) was spammed by the line

E/QMI_FW (634): xport_reg Failed for service_id=0x35 version=0x1001 on 10

I already wiped my phone and restored non-system apps via titanium backup. Thats usually the number one solution for anything like this. Not in this case. Not knowing what to do, I asked google and found this post, claiming, its an issue with TWRP restoring system partition. exactly what I did out of lazyness after switching to ext4 (i could have only restored data, but left defaults enabled and just restored the living crap out of it)

That post then states that flashing the original firmware AGAIN fixes the issue. I confess, I didnt believe it. A recovery not properly restoring system image? Well, I tried it, and yes, its fixed. No changes to data partition, just flash full 4.0.2 ROM (or in my case 4.0.1 ROM and 4.0.2 OTA), then SuperSU, Pixel Launcher, reboot, done. No log daemon running wild, no pm-service taking one cpu, no nothing.

I have no idea what the reason is, and if it can be fixed, but wanted to leave this story here, since I am probably not the only one running into this. I already found the same issue happend to someone else 2 pages back.

---------- Post added at 13:37 AM ---------- Previous post was at 23:23 AM ----------

reconnect your usb cable. it should work then.

---------- Post added at 01:30 AM ---------- Previous post was at 01:17 AM ----------

might be an f2fs problem. might. read first post "WHY DOES MY SCREEN TURN BLACK AND TWRP DOESN'T BOOT?" and also "HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?"

---------- Post added at 01:34 AM ---------- Previous post was at 01:30 AM ----------

it IS possible, you never really flashed TWRP.

if you use "fastboot boot twrp-blah.img" then you boot into the recovery image. even if you didnt flash it, it would start. next time, just do the "fastboot flash recovery twrp-blah.img" and chose "recovery" with volume buttons. confirm with power button. when it then enters stock recovery, you never had twrp flashed. for whatever reason. but its the second time i hear a similar story here.

---------- Post added at 01:35 AM ---------- Previous post was at 01:34 AM ----------

if you dont have a VERY good reason (or are just dangerously lazy), you should always be encrypted. IMHO it just has advantages.

---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------

had the same, yes. great I already have confirmation it was not only me. solution: flash rom again, maybe flash su, problem solved. more info to come. (update: see above)

---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------

latest is twrp 3.0.3-1 from official site twrp.me as linked in OP

---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------

with stable, like vendors use it.

rant: shame on linux kernel to make a filesystem not backward/forward compatible without changing the version number. like ext, ext2, ext3, ext4 etc. (for everything else i LOVE linux, so no hard feelings)

---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------

yes, it works. i like this guide and explaination more: http://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/