Database Info

Stock ROM: Root & OTA Updates

My new MOTO G 2015 XT1540 16GB/2GB will be delivered early next week. I have been trying to do all my reading in advance. Ideally I would like to keep the stock ROM, root the device, and keep receiving OTA updates.
My understanding to date is it is possible root without installing (flashing) TWRP. And by fast booting TWRP (vice installing) I can root the phone, keep the stock boot loader, and receive OTA updates as long as I completely unroot the device prior to updating. What is not clear to me is if I can keep receive OTA updates and not break the phone under the following circumstances:
1) custom kernel installed
2) adding apps to the system such as Cerberus (I know it can be elsewhere)
3) adding apps that require root such as Adfree (modifying host file)
4) freezing or removing system apps (bloatware)
Any suggestions how to proceed would be greatly appreciated.

Freezing/adding apps doesn't affect ota's,

HelpMeruth said:
Freezing/adding apps doesn't affect ota's,
Click to expand...
Click to collapse
Uhh, yes it does, at least sometimes. My last OTA failed until a bug report to Motorola traced it to system apps I had frozen. I don't think it matters now, at least with Titanium and Marshmallow. Many of the system apps I uninstall or freeze come un-frozen after a reboot. All that I uninstall become installed again after a reboot. I don't know if that's a Titanium Backup problem with Marshmallow or what.

Tel864 said:
My last OTA failed until a bug report to Motorola traced it to system apps I had frozen.
Click to expand...
Click to collapse
So your update simply failed with no ill effect on the phone?
Were you using the stock kernel?

MrTooPhone said:
So your update simply failed with no ill effect on the phone?
Were you using the stock kernel?
Click to expand...
Click to collapse
No lasting ill effect. Yes, everything stock. I had previously un-rooted which won't stop the OTA download, just the install. When the install still failed, I had forgotten that I'd frozen some Google apps, Gmail, Play Movies & TV, and Google Play Music. When the OTA kept failing to install, Motorola had me send a bug report. After I unfroze the above apps, the update seemed to go through fine. This had not happened on earlier versions of Android, so I'm thinking something changed or maybe it was just a bug in my software, who knows. You don't get a lot of feedback from Motorola. I think you have a better chance of winning the lottery or getting struck by lightning.

Security Update XT1572

Finally the September Security Patch is available for the Style. Hope Nougat is on the way soon.

How many threads about a September security patch that is now 4 months old do we need? Not very impressive to get the September patch in January in my opinion. If anything, the release of a security patch for Marshmallow now doesn't give me much hope that we will see Nougat in the near future. I hope I'm wrong, but I feel like we are getting screwed.

Moto does security patches in 1/4 by 1/4 updates so roughly every three months. Also they are usually a 1/4 behind the most recent.

autosurgeon said:
Moto does security patches in 1/4 by 1/4 updates so roughly every three months. Also they are usually a 1/4 behind the most recent.
Click to expand...
Click to collapse
Motorola/Lenovo never committed to a release schedule.

If u have the captured ota pls share it here
Xt 1572 Retasia Ds

False expectations that it was Nougat update, turns out to be just a security update for September month.
Moto updates slowly turning out to be a just a regular name any oem. No reliability for the software updates.
Day by day getting disappointed by Moto series ??

quakeaz said:
Motorola/Lenovo never committed to a release schedule.
Click to expand...
Click to collapse
I am aware of that however past performance while not indicative or proof of future performance says they have been sticking to an every 3 to 4 month schedule on Moto X line for security updates.

Uninstalled supersu, flashed stock recovery, downloaded security update. But while install getting the dead andi symbol with 'error'. upon reboot says the update install was unsuccessful. phone functions normally.
where did it go wrong? any suggestions.?
thanks

kcnanand said:
Uninstalled supersu, flashed stock recovery, downloaded security update. But while install getting the dead andi symbol with 'error'. upon reboot says the update install was unsuccessful. phone functions normally.
where did it go wrong? any suggestions.?
thanks
Click to expand...
Click to collapse
Uninstalling SU doesn't disable root. Did you unroot?

boxman99 said:
Uninstalling SU doesn't disable root. Did you unroot?
Click to expand...
Click to collapse
I did full unroot from within the su app before remove twrp. Don't want to restore full stock image. May be I will wait till N is released. Now if there is a way to disable the nagging update notification
Sent from my XT1572 using XDA-Developers Legacy app

kcnanand said:
I did full unroot from within the su app before remove twrp. Don't want to restore full stock image. May be I will wait till N is released. Now if there is a way to disable the nagging update notification
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you used root to make any change to the system partition (like Xposed, or even some simple things like the GSAM root battery_stats monitor), you cannot take an OTA successfully. The script checks to see if the system partition has been modified, or possibly just ever mounted R/W, and will refuse to continue and will result in an error in recovery like you see.
If the condition occurs like you are seeing, the only recourse is to restore to pure stock by flashing the factory images or restoring a pre-root TWRP backup.

acejavelin said:
If you used root to make any change to the system partition (like Xposed, or even some simple things like the GSAM root battery_stats monitor), you cannot take an OTA successfully. The script checks to see if the system partition has been modified, or possibly just ever mounted R/W, and will refuse to continue and will result in an error in recovery like you see.
If the condition occurs like you are seeing, the only recourse is to restore to pure stock by flashing the factory images or restoring a pre-root TWRP backup.
Click to expand...
Click to collapse
The only way to do is flash stock.. else wipe cache partition and disable notification for Moto Update app. It wont bother you anymore.

rahul14322 said:
The only way to do is flash stock.. else wipe cache partition and disable notification for Moto Update app. It wont bother you anymore.
Click to expand...
Click to collapse
True, I meant the only way to take the OTA update was to go back to stock... I neglected to mention that you can restore functionality to the device by just wiping caches.

I got the Security Update today too @ XT1572

ATT here got it today as well.

Anyone having problems with calls after this update!?
Since I updated yestarday people complaining they dont hear me well when they call me!

andromobilogy said:
Anyone having problems with calls after this update!?
Since I updated yestarday people complaining they dont hear me well when they call me!
Click to expand...
Click to collapse
No problems here... Spent a good 2 hours on the phone last night after getting the update and no one said anything.

kcnanand said:
Uninstalled supersu, flashed stock recovery, downloaded security update. But while install getting the dead andi symbol with 'error'. upon reboot says the update install was unsuccessful. phone functions normally.
where did it go wrong? any suggestions.?
thanks
Click to expand...
Click to collapse
You can do a minimal factory restore to satisfy the checks for the OTA. Just reflash the partitions most likely modified (recovery, system, boot) and the OTA should succeed. This assumes you're not running an alternate modem or haven't tinkered with any other partitions (besides the logo, that's fine to leave altered).
See ace's nice post @ https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110, and just execute the lines from boot.img to system.img_sparsechunk.8 with the appropriate 6.0 (May) files.

Has anyone from India received this update? I download RETASIA DS verison of this ROM and flashed it, however I'm getting no wifi and can't find an alternate download link. And obviously now I can't flash an older verison and then update using OTA

rahul14322 said:
The only way to do is flash stock.. else wipe cache partition and disable notification for Moto Update app. It wont bother you anymore.
Click to expand...
Click to collapse
What Moto Update app??? I don't see such a thing listed under Apps in settings.

google play uncertified after update to B225

anybody seeing uncertified device in google play after upgrade firmware B225 in mate 9 Chinese version? it was certified in B213

Interesting. I have the same for B225. What does this mean?

not sure, maybe because of the integration of GMS into the FW but so far all gapps work fine without any issues, v8.X supposed to come out yesterday or today so hope it will update without any issues.

May be its a reason that Android pay stop working on this firmware.
Anybody know how to fix this?

MMX2 said:
May be its a reason that Android pay stop working on this firmware.
Anybody know how to fix this?
Click to expand...
Click to collapse
haven't tried it yet but you are correct, some gapps will only work on certified devices

This is a bug of Google or Huawei? Google support can't tell me anything about it.

I am think that firmware not official.

Perhaps you can contact Google support for help. Good luck to you.

anyone got this fixed? been thinking about doing a factory reset and reinstall gapps from scratch but not sure if will work or if its better to wait for a new fw update from huawei whenever that happens

This has been the case for me on the last several releases. I have not experienced any difficulties or even change whatsoever. I don't use Android Pay though.

rbt001 said:
This has been the case for me on the last several releases. I have not experienced any difficulties or even change whatsoever. I don't use Android Pay though.
Click to expand...
Click to collapse
i did in b213 but now I cant also photos and contacts dont sync automatically in the background unless I open the app other than that everything works as expected

I have the same thing installed on the MHA-L29C432B193 via FunkyH, I have had it several times before and over time, and no problems in the applications or their updates have caused it.

Same here on 193. It is because firmware is not certified by Huawei jet.

arminbih said:
Same here on 193. It is because firmware is not certified by Huawei jet.
Click to expand...
Click to collapse
I had just rebranded from C567B190 to C432B193 (for the frequent security updates as it seemed like it was getting updates every month), and now Playstore says uncertified and Google Play is refusing to work, stating:
"Android Pay can't be used on this device
This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM..."
I hope you're right about this, arminbih, I'd hate to lose the ability to run Android Pay because of what I did and I'd hate to have to do another factory reset.
My phone's bootloader is locked after the rebranding script finished flashing the official B193. Did the recommended steps, 2 script runs and factory reset, but I hope nothing was messed up during the process. I should've backed up the original partitions in TWRP before proceeding with flashing. Oh well.
Anyone else have a clue?

lostorbit said:
I had just rebranded from C567B190 to C432B193 (for the frequent security updates as it seemed like it was getting updates every month), and now Playstore says uncertified and Google Play is refusing to work, stating:
"Android Pay can't be used on this device
This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM..."
I hope you're right about this, arminbih, I'd hate to lose the ability to run Android Pay because of what I did and I'd hate to have to do another factory reset.
My phone's bootloader is locked after the rebranding script finished flashing the official B193. Did the recommended steps, 2 script runs and factory reset, but I hope nothing was messed up during the process. I should've backed up the original partitions in TWRP before proceeding with flashing. Oh well.
Anyone else have a clue?
Click to expand...
Click to collapse
193 is unstable, force closes some apps, and camera does not work in RAW mode. I suggest going back to 190 or before, they are certified.

arminbih said:
193 is unstable, force closes some apps, and camera does not work in RAW mode. I suggest going back to 190 or before, they are certified.
Click to expand...
Click to collapse
Thank you for your reply. Off-topic question, would you know if it's easy to go back to 190 without losing data?
(I certainly should look that up myself, I know, but I literally just got the phone yesterday so it's still much of uncharted territory for me)

lostorbit said:
Thank you for your reply. Off-topic question, would you know if it's easy to go back to 190 without losing data?
(I certainly should look that up myself, I know, but I literally just got the phone yesterday so it's still much of uncharted territory for me)
Click to expand...
Click to collapse
Search "firmware finder" on play store and forums. You can upgrade downgrade as much as you like via official upade changing dns.

arminbih said:
Search "firmware finder" on play store and forums. You can upgrade downgrade as much as you like via official upade changing dns.
Click to expand...
Click to collapse
Thank you very much!

lostorbit said:
I had just rebranded from C567B190 to C432B193 (for the frequent security updates as it seemed like it was getting updates every month), and now Playstore says uncertified and Google Play is refusing to work, stating:
"Android Pay can't be used on this device
This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM..."
I hope you're right about this, arminbih, I'd hate to lose the ability to run Android Pay because of what I did and I'd hate to have to do another factory reset.
My phone's bootloader is locked after the rebranding script finished flashing the official B193. Did the recommended steps, 2 script runs and factory reset, but I hope nothing was messed up during the process. I should've backed up the original partitions in TWRP before proceeding with flashing. Oh well.
Anyone else have a clue?
Click to expand...
Click to collapse
I too had B193 installed, and Android Pay wouldn't work. SafetyNet basic integrity passed but not CTS Profile, and probably because of B193 being uncertified. Went back to B190 now that it's certified and Pay works again and SafetyNet passes on both checks.
I have previously used updates the day they were released on hwmt.ru and they have worked fine with SafetyNet, even when it said uncertified. So this might be something new.

That's great to know. Thank you.
Were you able to downgrade without a wipe, and if so, what method did you use?
I've been messing with FF and the proxy method but no dice so far.

Taking September security update on rooted Oreo

I'm on rooted Oreo 8.0. In UK. Security update has appeared. Anyone tried taking it on a rooted Oreo Pixel? I'm not too bothered about losing root, that's easy to put right, I just want to avoid a time consuming disaster.

All working fine here, of course have to reroot and whatnot. But no problems.

It won't let me install it. Whatever no big deal

cgrimm9 said:
It won't let me install it. Whatever no big deal
Click to expand...
Click to collapse
It won't let me install it as well. Don't want to have to update by flashing factory image and losing data. But. It wouldn't be the first time. So, yeah no big deal, just a bit of a pain.

Horgar said:
It won't let me install it as well. Don't want to have to update by flashing factory image and losing data. But. It wouldn't be the first time. So, yeah no big deal, just a bit of a pain.
Click to expand...
Click to collapse
Before flashing factory script, edit the script to remove "-w"
It is the "-w" that wipes device, not the factory firmware.
This has been discussed again and again since November 2016.
Sent from my sailfish using XDA Labs

I downloaded the full image and removed the -w in the flash-all then saved it and updated, rerooted, added back su hide no problem at all. Even kept my theme installed!

Archangel said:
I downloaded the full image and removed the -w in the flash-all then saved it and updated, rerooted, added back su hide no problem at all. Even kept my theme installed!
Click to expand...
Click to collapse
Did you have to wipe the internal storage in TWRP as the root guide suggests again? Or was that a one time deal for when we first move to Android O?
Sent from my Pixel using Tapatalk

Nope didnt wipe internal storage. But I assume that was needed coming from N to O and I modded the flash all bat to not erase my system for this Sept full image. So far so good, if i see anything bad I will report back here.
mike86325 said:
Did you have to wipe the internal storage in TWRP as the root guide suggests again? Or was that a one time deal for when we first move to Android O?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse

Same here. Used the image from the Google site with the -w removed and no wipe. Re-roooted with no issue and it even kept suhide and it functioned after the root. Did this on an XL and a Pixel last night with no issues so far. No Google Play Services crashes on reboot either, so that is a win.

Does anyone know what are the issues with september update? Or google just fixed everything with this new release?
I can't find the changelog anywhere :/

Anyone actually had the Sept update yet?
I haven't.
Update: just unenrolled from the Beta and the update popped up.

Netflix gone?

Can't download Netflix for Pixel 3
In Google store says not available for my phone!
Anyone else?
Any links to most recent APK that I won't destroy my device with?

If your device is showing as not certified in play store settings, Netflix doesn't show for new installs. Hide the Play Store with Magisk, and then clear the Play store cache and data and open it back up. You should then show certified, and Netflix will be available. There is also a version for sideloading on the Netflix website.

sliding_billy said:
If your device is showing as not certified in play store settings, Netflix doesn't show for new installs. Hide the Play Store with Magisk, and then clear the Play store cache and data and open it back up. You should then show certified, and Netflix will be available. There is also a version for sideloading on the Netflix website.
Click to expand...
Click to collapse
My device has shown not certified for awhile. It never seemed to be an issue as I never had any problem with apps. But now I'm good [emoji4]

sliding_billy said:
If your device is showing as not certified in play store settings, Netflix doesn't show for new installs. Hide the Play Store with Magisk, and then clear the Play store cache and data and open it back up. You should then show certified, and Netflix will be available. There is also a version for sideloading on the Netflix website.
Click to expand...
Click to collapse
Play Store doesn't say anything about certification in the settings, but Netflix is missing so I assume I'm not certified. I tried following your instructions with Magisk Hide, but Netflix is still not showing. (If I try to search it from Google to get to the Play Store entry, it says my device is not compatible with this version.) I also tried sideloading the version from their website. It installs fine, but when I launch it, it says the device is not supported. I also tried using Magisk Hide on Netflix to no avail. Additionally, Magisk says my device passes both SafetyNet checks. Any other ideas?

fysix said:
Play Store doesn't say anything about certification in the settings, but Netflix is missing so I assume I'm not certified. I tried following your instructions with Magisk Hide, but Netflix is still not showing. (If I try to search it from Google to get to the Play Store entry, it says my device is not compatible with this version.) I also tried sideloading the version from their website. It installs fine, but when I launch it, it says the device is not supported. I also tried using Magisk Hide on Netflix to no avail. Additionally, Magisk says my device passes both SafetyNet checks. Any other ideas?
Click to expand...
Click to collapse
Not showing anything about certified means that it is not certified. Are you on a Pixel 3? Could be a handful of things causing it. Are you able to clear cache and data in Play Store? If not, you won't be able to get certified. That happens a lot if you have a Magisk Module that greys out that option like Edge Sensor. My sugestion is to flash boot.img to both slots and then clear cache/data in Play Store and get certification back before re-rooting. Once Netflix is installed, it doesn't matter if you are rooted. Keep Play Store hidden though.

sliding_billy said:
Not showing anything about certified means that it is not certified. Are you on a Pixel 3? Could be a handful of things causing it. Are you able to clear cache and data in Play Store? If not, you won't be able to get certified. That happens a lot if you have a Magisk Module that greys out that option like Edge Sensor. My sugestion is to flash boot.img to both slots and then clear cache/data in Play Store and get certification back before re-rooting. Once Netflix is installed, it doesn't matter if you are rooted. Keep Play Store hidden though.
Click to expand...
Click to collapse
Yep, pixel 3.
I'll give your suggestions a try as soon as I get a chance

sliding_billy said:
My sugestion is to flash boot.img to both slots and then clear cache/data in Play Store and get certification back before re-rooting.
Click to expand...
Click to collapse
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?

fysix said:
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?
Click to expand...
Click to collapse
Did it show anything about certification in Play Store Settings (at the very bottom)? It does sometimes take a couple of times entering Play Store and possibly rebooting to show as certified. There really is nothing else other than clearing cache/data in Play Store and being on a device that can show as certified (which clearly the Pixel 3 is). Normally, once you clear cache/data even rooting won't stop the certification (if you hide Play Store with Magisk Hide before opening it again) it just takes some little bit of time that I have not ever been able to completely narrow down to an exact action. I have to do this pretty much every month after loading the monthly update and it always works (Netflix does not need reinstalled or anything after the first time as long as the device is certified if an update shows up).

fysix said:
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?
Click to expand...
Click to collapse
Two other thoughts. Are you passing SafetyNet? If not, that may point to the root cause. The other one just occurred to me, but are you running a custom kernel? If not, your unlocked bootloader is being exposed and may very well be keeping Netflix from showing up. If that is the case, you definitely want to look into one of the custom kernels here. I use ElementalX, and it is the closest to stock with minor adjustments and of course it hides the unlocked BL.

sliding_billy said:
Two other thoughts. Are you passing SafetyNet? If not, that may point to the root cause. The other one just occurred to me, but are you running a custom kernel? If not, your unlocked bootloader is being exposed and may very well be keeping Netflix from showing up. If that is the case, you definitely want to look into one of the custom kernels here. I use ElementalX, and it is the closest to stock with minor adjustments and of course it hides the unlocked BL.
Click to expand...
Click to collapse
Same problem here.
Passing SafetyNet
Play Store get certification
But can't download on Play Store. Try installation apk from Netflix, App does not support this device

beinanchen said:
Same problem here.
Passing SafetyNet
Play Store get certification
But can't download on Play Store. Try installation apk from Netflix, App does not support this device
Click to expand...
Click to collapse
I just looked at the Netflix support page with instructions for side loading the app. It claims it is only compatible up to Android 7.1.2, so clearly the one on their site will not work anymore. They even say to contact them if you are certified, but I am guessing all they are going to ask you is about BL unlocking. To my question of the other user, are you running a custom kernel? I am sure Netflix sees a BL unlock if it is exposed. The only other thing you can do is try APKMirror. https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/

sliding_billy said:
I just looked at the Netflix support page with instructions for side loading the app. It claims it is only compatible up to Android 7.1.2, so clearly the one on their site will not work anymore. They even say to contact them if you are certified, but I am guessing all they are going to ask you is about BL unlocking. To my question of the other user, are you running a custom kernel? I am sure Netflix sees a BL unlock if it is exposed. The only other thing you can do is try APKMirror. https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
Click to expand...
Click to collapse
yes, if my lock bl, I can download it from Play Store and working well, all the problem from Unlock bl

beinanchen said:
yes, if my lock bl, I can download it from Play Store and working well, all the problem from Unlock bl
Click to expand...
Click to collapse
Install a custom kernel. They all (as far as I know) hide the unlocked BL at this point.

sliding_billy said:
Install a custom kernel. They all (as far as I know) hide the unlocked BL at this point.
Click to expand...
Click to collapse
Try to install Proton Kernel, same problem. ?
---------- Post added at 02:33 PM ---------- Previous post was at 02:29 PM ----------
sliding_billy said:
I just looked at the Netflix support page with instructions for side loading the app. It claims it is only compatible up to Android 7.1.2, so clearly the one on their site will not work anymore. They even say to contact them if you are certified, but I am guessing all they are going to ask you is about BL unlocking. To my question of the other user, are you running a custom kernel? I am sure Netflix sees a BL unlock if it is exposed. The only other thing you can do is try APKMirror. https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
Click to expand...
Click to collapse
Already install, it's working now, but still can't update on Play Store

fysix said:
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?
Click to expand...
Click to collapse
beinanchen said:
Try to install Proton Kernel, same problem. ?
---------- Post added at 02:33 PM ---------- Previous post was at 02:29 PM ----------
Already install, it's working now, but still can't update on Play Store
Click to expand...
Click to collapse
I wish I had more insight. I am using ElementalX and Magisk 19.3 with Play Store hidden. I actually factory reset my P3XL about a month ago to return to stock image from custom OS, and after all of the things mentioned was able to get Netflix from the Play Store and got the last update on June 14 (the one listed on the Play Store page). I'm not sure if something has changed since then. I am hesitant to uninstall and see if it is still there. I have 5 devices running Netflix including a P3 and P3XL. The other devices all are rooted with 19.3 as well and are running Nugget or Oreo with stock kernels. Just needed to get them to show certified and hide Play Store. The Pixels have been BL unlocked since the day they arrived last fall.
Fysix (and beinanchen if relevant)- I just read another post of your saying you are running Xposed. I mentioned that some Magisk modules could be an issue. I would disable all Magisk modules and reboot at least for testing.

sliding_billy said:
I would disable all Magisk modules and reboot at least for testing.
Click to expand...
Click to collapse
Currently I'm on a stock boot partition so no Magisk or Xposed is running. I did the little migration wizard from my old Pixel 2 to my Pixel 3 immediately after unlocking the bl and I remember Netflix being omitted then even with just the bootloader unlocked and no Magisk. I haven't had a chance to try ElementalX yet but I'm fairly optimistic that the kernel is ratting me out currently and ElementalX will fix it.

fysix said:
Currently I'm on a stock boot partition so no Magisk or Xposed is running. I did the little migration wizard from my old Pixel 2 to my Pixel 3 immediately after unlocking the bl and I remember Netflix being omitted then even with just the bootloader unlocked and no Magisk. I haven't had a chance to try ElementalX yet but I'm fairly optimistic that the kernel is ratting me out currently and ElementalX will fix it.
Click to expand...
Click to collapse
Either way, EX is a nice kernel. The EX Kernel manager is a really nice app and the dev deserves the financial support. He literally has that kernel updated normally before most folks have even installed their monthly Google update. I have separate copies on both of my Pixels. Plus, it beats the hell out of having to copy/flash the kernel manually. Let me know how it goes.

I have the same issue.
I'm on dirty unicorn with kirishakura kernel and magisk.
I'm passing safetynet thought and downloading the apk doesn't work as the app crash.
Edit: play store says I'm certified.

Same problem here.
Running a custom kernel that is based off of DU with some ElementalX cherry-picks. Rom is custom compiled AOSiP. Latest Magisk canary installed and passing SafetyNet. Only other thing I did was hack gms DB's to allow Google Pay to work. I'm also using Vanced YouTube.

sliding_billy said:
Either way, EX is a nice kernel. The EX Kernel manager is a really nice app and the dev deserves the financial support. He literally has that kernel updated normally before most folks have even installed their monthly Google update. I have separate copies on both of my Pixels. Plus, it beats the hell out of having to copy/flash the kernel manually. Let me know how it goes.
Click to expand...
Click to collapse
Tried ElementalX and it didn't make a difference