[SIZE="4"]/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */[/SIZE]
fastboot boot twrp-3.3.0-v2-evert-jlb.img
Hmm, Bluetooth calls are working for some, so I've been told. Anyway, if you're trying to return to stock, you need to flash the correct firmware for your device variant. The PPW29.116-20 is only for certain variants, not the "latest" update as a lot of users mistake it for. If you wanna stay on Pie, then try the 116-11 or 116-16 firmware.Hi, thanks for the ROM. But i also had issues with BT calls and sound quality during phone calls, so i reverted to stock. I tried flashing the newest Pie stock firmware(reteu PPW29.116-20) and relocking the bootloader afterwards. But i had the message "This device has loaded a different operating system", and "Verity mode disabled" during boot. And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates.
I've got a question, how to revert to stock in corect way and eable GooglePay. Wanna to sell the device.
Is it because of when i came from stock for the first time, I flashed "copy-partitions-AB.zip" from second post?
Yes, absolutely. The Updater has been fixed in latest build and does support seamless updates (same as stock). I tested it last night as I was running a test build from a couple days ago.
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.