Device is not Google certified phh GSI how to fix? - Treble-Enabled Device Questions and Answers

Hello,
I have a brand new device which has not officially been released yet. Therefore, there is no stock firmware image available or recovery image. Just wanted to get that out of the way. I could not remove a lot of the manufacturers bloatware because i could not root or port TWRP without a stock image or recovery image.
I stumbled onto Project Treble. I flashed phh treble and it worked. Well, I managed to get everything to work with some workarounds. The only thing I am having trouble with is when I install phh with gapps. After booting I get the "Your device is not Google certified" message repeatedly spammed.
The only workaround I have been able to get to work for the uncertified device message is to remove phh superuser. I have tried using the Google device registration page. It does not work for my device. I want to keep root so I can pull the recovery image and port TWRP for this device. Are there any other fixes that will work? In order to pick up in some of my games I think I need Google Play?
Thanks,
Rocky

What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)

LR7875 said:
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
Click to expand...
Click to collapse
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?

bigroc2223 said:
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
Click to expand...
Click to collapse
No no no, you need to patch boot.img for magisk, not system. Go to www.apkmirror.com (app repository), search and download 'magisk ' app(that is magisk manager), click and install the downloaded .apk file, allow install from browser, and after installing use the app to patch the boot.img(search Google), and flash patched boot.

I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.

bigroc2223 said:
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
Click to expand...
Click to collapse
I am sorry to hear that.It is pretty much beyond what I can solve so I will try find similar threads.

Related

Magisk No root prompts

^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for

Keep Play Certification with Unlocked Bootloader?

I had to completely wipe my phone since recently the battery life started tanking hard, and I couldn't figure out why. I decided to just start over from a clean slate, since I had the same configuration since I got the phone about a year or two ago (stock Android 9, unlocked, and rooted with Magisk and EdXposed).
I figured that I would flash the July image without wipe first, but the battery issue persisted. I then decided to just flash it with the wipe (after backing up data, of course), and the battery seemed to be a bit better while I was setting up.
The problem I'm now having is that my device seems to be missing Play Certification. I noticed this when I was unable to install Netflix from the Play Store (although Google Pay seemed to work fine?). I've tried flashing the image several times, and even tried older images, but I can't seem to keep Play Certification.
I tried locking the bootloader after flashing the July image, and that finally gave me Play Certification and I was able to download Netflix.
Obviously however, I need to keep an unlocked bootloader for other things too.
Is there any way to get Netflix (and Play Certification) to work with an unlocked bootloader?
Doesn't MagiskHide provide just what you're asking for? If you don't want to use Magisk, maybe try PeNoire's SafetyNet Spoofer which works without Magisk but still requires a custom recovery like TWRP.
nitrous² said:
Doesn't MagiskHide provide just what you're asking for? If you don't want to use Magisk, maybe try PeNoire's SafetyNet Spoofer which works without Magisk but still requires a custom recovery like TWRP.
Click to expand...
Click to collapse
How would I get MagiskHide to work with Netflix without being able to install the app from the Play Store? Would enabling hide for the PS work, or do I need to sideload the app and then use Hide on the app?
Latiken said:
How would I get MagiskHide to work with Netflix without being able to install the app from the Play Store? Would enabling hide for the PS work, or do I need to sideload the app and then use Hide on the app?
Click to expand...
Click to collapse
Netflix doesn't care about the existence of Magisk once it is already installed on your device. So don't get confused there. You're problem is with the Play Store, specifically with SafetyNet. One step at a time;
When you unlock your bootloader, you are going to fail some SafetyNet checks. This will result in a restricted Play Store, meaning, certain apps won't be visible to you. To circumvent that, you flash something like Magisk or PetNoire to hide your bootloaders state to SafetyNet checks. This will result in an unrestricted Play Store. Unlock, install Magisk or PetNoire and then you should be able to get unrestricted access to Play Store apps.
Unlock the bootloader of your device
Install the latest version of Magisk
MagiskHide should be enabled by default, if not:
Download and install PetNoir's SafetyNet Spoofer
nitrous² said:
Netflix doesn't care about the existence of Magisk once it is already installed on your device. So don't get confused there. You're problem is with the Play Store, specifically with SafetyNet. One step at a time;
When you unlock your bootloader, you are going to fail some SafetyNet checks. This will result in a restricted Play Store, meaning, certain apps won't be visible to you. To circumvent that, you flash something like Magisk or PetNoire to hide your bootloaders state to SafetyNet checks. This will result in an unrestricted Play Store. Unlock, install Magisk or PetNoire and then you should be able to get unrestricted access to Play Store apps.
Unlock the bootloader of your device
Install the latest version of Magisk
MagiskHide should be enabled by default, if not:
Download and install PetNoir's SafetyNet Spoofer
Click to expand...
Click to collapse
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Latiken said:
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Click to expand...
Click to collapse
You just need to install Netflix through apk, not playstore. it is working well
Latiken said:
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Click to expand...
Click to collapse
I'v been been having the same issue for about 5-6 months now with both Android 9 and 10. It was working fine on Pie and showing up in Google Play, but then after I flashed one of the monthly system images with a wipe, the app no longer showed up in the play store. And after I restored the most recent Netflix app at the time from a backup, it would constantly crash. I have all Google Play Services, Google Play and Netflix selected in Magisk hide. Google Play says my device is certified. Magisk SafetyNet test passes along with any SafetyNet test app. Logged out of my Google account, wiped data for Google Play, Google Play services and Netflix, rebooted and signed back in but still not showing up. Downloaded and installed the newest Netflix app from their site but I get an error stating the device is not supported with the app which clearly isn't the case.
Can you select this link and have it open in the Google Play app on your phone: https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en_US
It shows up for me but says in red font: "This app isn't compatible with your device anymore. Contact the developers for more info". Which I did...went back and forth with Google and Netflix for hours yesterday, but both of their support is completely useless.
The newest version of the app that works for me is version 6.26.1. You can download it here if you haven't already: https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
The only thing is how long is it going to continue to work. A future update will most likely break that version as well.
Have you made any progress since July?
giants8058 said:
I'v been been having the same issue for about 5-6 months now with both Android 9 and 10. It was working fine on Pie and showing up in Google Play, but then after I flashed one of the monthly system images with a wipe, the app no longer showed up in the play store. And after I restored the most recent Netflix app at the time from a backup, it would constantly crash. I have all Google Play Services, Google Play and Netflix selected in Magisk hide. Google Play says my device is certified. Magisk SafetyNet test passes along with any SafetyNet test app. Logged out of my Google account, wiped data for Google Play, Google Play services and Netflix, rebooted and signed back in but still not showing up. Downloaded and installed the newest Netflix app from their site but I get an error stating the device is not supported with the app which clearly isn't the case.
Can you select this link and have it open in the Google Play app on your phone: https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en_US
It shows up for me but says in red font: "This app isn't compatible with your device anymore. Contact the developers for more info". Which I did...went back and forth with Google and Netflix for hours yesterday, but both of their support is completely useless.
The newest version of the app that works for me is version 6.26.1. You can download it here if you haven't already: https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
The only thing is how long is it going to continue to work. A future update will most likely break that version as well.
Have you made any progress since July?
Click to expand...
Click to collapse
That's actually the exact same version of Netflix that I was able to get working, and I've been using it since July.
It works exactly as it should, but the resolution seems to be capped at 480p or 720p, as I notice a lot of blurriness. It's still usable, but I'm considering getting rid of Magisk and going to 10 to avoid these issues.
Reading on what you've done, it's exactly what I went through in July.
I'm not sure what's changed since prior to updating to another security patch, Netflix was working completely fine from the Play Store with Magisk.
Latiken said:
That's actually the exact same version of Netflix that I was able to get working, and I've been using it since July.
It works exactly as it should, but the resolution seems to be capped at 480p or 720p, as I notice a lot of blurriness. It's still usable, but I'm considering getting rid of Magisk and going to 10 to avoid these issues.
Reading on what you've done, it's exactly what I went through in July.
I'm not sure what's changed since prior to updating to another security patch, Netflix was working completely fine from the Play Store with Magisk.
Click to expand...
Click to collapse
Yeah and also after a few minutes of watching a video, the screen dims like right before your phone auto-locks itself due to inactivity. So far the only way I was able to get it to show back up in Google Play was re-locking the bootloader, but that's not really an option for me since I want to stay rooted. But it really doesn't make any sense since all the SafetyNet compatibility tests pass and the device is certified. Maybe I'll try reaching out to the Magisk dev and see if he's willing to take a look into it.
giants8058 said:
Yeah and also after a few minutes of watching a video, the screen dims like right before your phone auto-locks itself due to inactivity. So far the only way I was able to get it to show back up in Google Play was re-locking the bootloader, but that's not really an option for me since I want to stay rooted. But it really doesn't make any sense since all the SafetyNet compatibility tests pass and the device is certified. Maybe I'll try reaching out to the Magisk dev and see if he's willing to take a look into it.
Click to expand...
Click to collapse
I don't seem to have that screen dimming issue, so it's possible that something else is going on on your end for that.
It's possible that Netflix is able to detect root through some other way that's irrelevant to Google Play Protection. And it could also be a thing where the resolution is limited if you're not on the latest version.
If I do figure something out in the future, I'll be sure to post here again.
Latiken said:
I don't seem to have that screen dimming issue, so it's possible that something else is going on on your end for that.
It's possible that Netflix is able to detect root through some other way that's irrelevant to Google Play Protection. And it could also be a thing where the resolution is limited if you're not on the latest version.
If I do figure something out in the future, I'll be sure to post here again.
Click to expand...
Click to collapse
I don't think the issue is because of being rooted, but instead the unlocked bootloader as it still doesn't show up after uninstalling Magisk or after a system image flash with wipe. Like I mentioned earlier, the only way I can get it to show in Google Play or have the newest version work when side loaded at this point is when the bootloader is locked. So if you don't mind not being rooted or being able to manually flash updates without a factory reset each time, just re-lock your bootloader (just remember to backup your data since it wipes your phone) and Netflix should work normally again.
But I'll be sure post here as well if I come across anything that works.
What you both need is to install/flash a custom kernel...
On top of many multiple things a custom kernel can do, one significant thing is to be able to mask root on many/most root detecting processes. When I first rooted 2 years ago, I couldn't get Google Pay to work because of the root detecting. I had inadvertently flashed a custom kernel, and was pleasantly surprised that Google Pay began to work (back then, but now more than a custom kernel is required).
The best general all-around custom kernel was called Flash, but that became EOL and stopped development, but one called Caesium was built based off of Flash and continued from there; even collaborated with the maker of Flash.
Give it a try, and see how it works wonders for both your issue (root detection) battery life, and even responsiveness of the system!
Hope this helps...
simplepinoi177 said:
What you both need is to install/flash a custom kernel...
On top of many multiple things a custom kernel can do, one significant thing is to be able to mask root on many/most root detecting processes. When I first rooted 2 years ago, I couldn't get Google Pay to work because of the root detecting. I had inadvertently flashed a custom kernel, and was pleasantly surprised that Google Pay began to work (back then, but now more than a custom kernel is required).
The best general all-around custom kernel was called Flash, but that became EOL and stopped development, but one called Caesium was built based off of Flash and continued from there; even collaborated with the maker of Flash.
Give it a try, and see how it works wonders for both your issue (root detection) battery life, and even responsiveness of the system!
Hope this helps...
Click to expand...
Click to collapse
Thank you for the suggestion, I'll make sure to try this after updating to the latest Pie build. I'm sure that this will work, as I remember using a custom kernel last time that Netflix was working just fine for me.
I also just found a thread with a stock kernel infused with a SafetyNet patch that says that Netflix and other apps refused to work on unlocked bootloader devices because something trips in SafetyNet, leading me to believe that this is what me and @giants8058 have been experiencing.
I will let everyone know if this works later this week.
Latiken said:
Thank you for the suggestion, I'll make sure to try this after updating to the latest Pie build. I'm sure that this will work, as I remember using a custom kernel last time that Netflix was working just fine for me.
I also just found a thread with a stock kernel infused with a SafetyNet patch that says that Netflix and other apps refused to work on unlocked bootloader devices because something trips in SafetyNet, leading me to believe that this is what me and @giants8058 have been experiencing.
I will let everyone know if this works later this week.
Click to expand...
Click to collapse
You have to flash a custom Kernel to hide bootloader unlock. After you flash the custom kernel the play store will still show as not being certified. You will have to force stop the play store then delete the cache and storage. When you reboot it will show that it is certified.
murphyjasonc said:
You have to flash a custom Kernel to hide bootloader unlock. After you flash the custom kernel the play store will still show as not being certified. You will have to force stop the play store then delete the cache and storage. When you reboot it will show that it is certified.
Click to expand...
Click to collapse
I flash the August stock build along with the Sultan kernel (as I couldn't get Caesium or the SafetyNet patched kernel to flash), and followed your instructions, but my Play Store isn't showing my device as certified yet.
Is there something else I need to do?
Latiken said:
I flash the August stock build along with the Sultan kernel (as I couldn't get Caesium or the SafetyNet patched kernel to flash), and followed your instructions, but my Play Store isn't showing my device as certified yet.
Is there something else I need to do?
Click to expand...
Click to collapse
1. Download TWRP 3.3.0 img file
2. Download TWRP 3.3.0 zip file (optional)
3. Download Magisk 19.3
4. Download kernel of choice. (I use Sultan)
5. Boot to fastboot
6. Boot to TWRP. (fastboot boot TWRP. Img) I shorten the file name to make it easier.
7. Flash kernel first if using Sultan
8. Flash TWRP zip. (optional)
9. Flash Magisk 19.3
10. Let phone boot then delete data/cache in play store.
11. Reboot phone
These are the steps I use. If I remember correctly there was a couple of versions of the play store that showed uncertified no matter what. The latest play store version is 16.5.15. I can confirm it works. I also hide Google Play services in Magisk hide but I don't think that's needed unless you want Google Pay to work.
murphyjasonc said:
1. Download TWRP 3.3.0 img file
2. Download TWRP 3.3.0 zip file (optional)
3. Download Magisk 19.3
4. Download kernel of choice. (I use Sultan)
5. Boot to fastboot
6. Boot to TWRP. (fastboot boot TWRP. Img) I shorten the file name to make it easier.
7. Flash kernel first if using Sultan
8. Flash TWRP zip. (optional)
9. Flash Magisk 19.3
10. Let phone boot then delete data/cache in play store.
11. Reboot phone
These are the steps I use. If I remember correctly there was a couple of versions of the play store that showed uncertified no matter what. The latest play store version is 16.5.15. I can confirm it works. I also hide Google Play services in Magisk hide but I don't think that's needed unless you want Google Pay to work.
Click to expand...
Click to collapse
Those steps are actually exactly what I did, but the certification label in the settings is missing, and Netflix won't appear.
If it means anything, I noticed that I actually had Sultan kernel installed before doing any of this, so it might be that the kernel isn't working on my end.
Latiken said:
Those steps are actually exactly what I did, but the certification label in the settings is missing, and Netflix won't appear.
If it means anything, I noticed that I actually had Sultan kernel installed before doing any of this, so it might be that the kernel isn't working on my end.
Click to expand...
Click to collapse
Well...I can say, at least, that I am having the same experience as murphyjasonc and am able to get "Play Protect Certification" certified and I have an unlocked bootloader with root and even a custom recovery.
I would make sure you do as he suggests and at the very least disable or "uninstall updates" for the Play Store and Google Play Services. But, also, custom kernels are things that also need to be updated; so this might be the explanation on it no longer working. But I know you had recently reflashed Sultan, so it is rather puzzling that you are still having those issues.
Just making sure, you are using TWRP to install the latest version of those kernels, correct? Also, when you had ran the August patch, did you use the Full Factory version? Are you able to pass safetynet currently?
Hopefully retrying these will get things up and running...
simplepinoi177 said:
Well...I can say, at least, that I am having the same experience as murphyjasonc and am able to get "Play Protect Certification" certified and I have an unlocked bootloader with root and even a custom recovery.
I would make sure you do as he suggests and at the very least disable or "uninstall updates" for the Play Store and Google Play Services. But, also, custom kernels are things that also need to be updated; so this might be the explanation on it no longer working. But I know you had recently reflashed Sultan, so it is rather puzzling that you are still having those issues.
Just making sure, you are using TWRP to install the latest version of those kernels, correct? Also, when you had ran the August patch, did you use the Full Factory version? Are you able to pass safetynet currently?
Hopefully retrying these will get things up and running...
Click to expand...
Click to collapse
I used the latest version of TWRP to install the August OTA patch, as well as to install the latest Sultan kernel.
I just ran a SafetyNet test in MagiskManager and it passed correctly.
Latiken said:
I used the latest version of TWRP to install the August OTA patch, as well as to install the latest Sultan kernel.
I just ran a SafetyNet test in MagiskManager and it passed correctly.
Click to expand...
Click to collapse
Give this a try...
instead of the OTA, try the Full Factory version -- and be sure to remove the "-w" in the flash-all to keep your data intact -- and then, also, be sure to disable/"uninstall updates" for both the Google Play Store and the Google Play Services (you can enable it after disabling it of course). After that, boot up TWRP and flash the Sultan kernel and Magisk and see if you don't have the certification after all that.
If you don't know; you can't simply run the Full Factory .zip's in TWRP, so if you don't know how to do a Full Factory version, I can point you in the right direction...
Good luck!

[GSI][UNOFFICIAL] LineageOS 17.1 Modified [TEST][XT1952-2]

MODIFIED EXCLUSIVELY FOR MOTO G7 PLAY
WARNING
Do not try to install this via fastboot, remove the magisk, to remove just reinstall the Stock Rom
MAIN FEATURES
Root modified by Spaceminer
More speed
Added multiple apps
Several useless apps removed
Black theme automatically enabled in all supported applications
Gapps already installed
Notch fix
And more
DOES NOT WORK
Fingerprint
Automatic brightness
INSTALLATION INSTRUCTION
1. Download and extract
2. Put the GSI on your memory card
3. Restart your phone in Bootloader / Fastboot mode
4. Open fastboot on your computer
use the command: fastboot -w
use the command: fastboot boot twrp.img
5. TWRP: Install> Install image> Choose image file> Flash on the system
DOWNLOADS
TWRP by Spaceminer: https://mega.nz/#!roRzBCTK!THHq0VMWqgtowJNkY-Id3b9S9H9dhzsJhE83k0Kvt2k
GSI: https://www.drive.google.com/file/d/1000HaJJqMdGyOtEd7ribp4n5Eb9l-3my/view
Works great apart from when I make calls the microphone doesn't work...whatsapp calls are fine it only seems to be a problem on cellular!
When I select the image I get 4 options and it does not let me install with any
With this my G7 play stay 32bits or can change for 64 bits?
RafaelItape said:
With this my G7 play stay 32bits or can change for 64 bits?
Click to expand...
Click to collapse
until we get a 64 bit kernel, it'll stay 32. i want to build a 64 kernel cause i want to bring ubuntu touch to this phone, that requires a 64 bit boot image, if we are to use erfan's (only method for android 9 devices rn)
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
CFKod said:
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
Click to expand...
Click to collapse
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
BobbyBlunt said:
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
Click to expand...
Click to collapse
yup... sorry, forgot to post... I assumed it was after installing modules.
Lockscreen not work for me, in all gsi roms.
Only stock works.
rom works great, feels like a new phone.
model XT1952-4.
not working unfortunately is the FM radio.
based on the error message when trying to install FM apps, it looks like the kernel driver was not included in the rom?
I can deal with the fingerprint not working, it would be really nice to get the FM driver included so I don't have to use data.
Overall the phone is so much better with this rom, Thank You!!!!
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Thanks for all the work
Everything seems stable been using on daily driver for 2 days now. Only issue is bluetooth audio not working. I'm wondering if the Motorola face unlock app would work however current version isn't available.
gadolf said:
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Click to expand...
Click to collapse
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
XxLilJeepXx said:
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
Click to expand...
Click to collapse
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
workin on fixing phone
yashor said:
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Click to expand...
Click to collapse
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
XxLilJeepXx said:
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
Click to expand...
Click to collapse
Why not just boot into bootloader mode and fast boot stock firmware to recover your device ?
PoochyX said:
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
Click to expand...
Click to collapse
Hi,
From your experience which GSI is better for MOTO G7 Play 1952-2:
Havoc or Lineage ?
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
PoochyX said:
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
Click to expand...
Click to collapse
Thank you for your reply.
I favor stability and performance over Magisk.
In my case, do your recommend Lineage as my best option to try?

[How To] Flash GSI ROMs

Requirements:
- Stock Clean Firmware: https://mirrors.lolinet.com/firmware/moto/kane/official/
- TWRP: https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
- GSI ROM (arm64, A/B versions): https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
- Permissiver_V5 Flashable Zip: https://androidfilehost.com/?fid=6006931924117940902
- Google Play Services APK - Whenever you boot into a GSI the first thing you should do is install the Google Play Services APK. Installing it will clear the "System Updating..." notification and you will be able to login to your Google account.
Google Play Services for Android 9 GSI: https://www.apkmirror.com/apk/googl...-24-13-100400-316577029-android-apk-download/
Google Play Services for Android 10 GSI: https://www.apkmirror.com/apk/googl...-24-13-120400-316577029-android-apk-download/
Instructions:
- Flash Stock firmware
- Wipe system and data in TWRP
- Reboot to bootloader
- Run the following command in the command line:
Code:
fastboot flash system [yourGSI.img]
- While still in fastboot mode run:
Code:
fastboot -w
- Reboot to TWRP and flash Permissiver_V5 zip file
- Reboot to the system
Notes:
Look at the size of the downloaded GSI.img file (Not the zip file), If it's larger than 3GB you won't be able to flash it because the system partition is limited to 3GB)
Permissiver_V5 is required for some GSI to successfully boot, some of GSIs might work without it but if you don't flash it and the GSI doesn't boot that might be the main problem.
GSI ROMs might have some bugs, the most known bug at least on One Vision and maybe Action is the Bluetooth Freeze Bug that might happen when you try to play music over Bluetooth. Be prepared for anything.
Not every GSI will successfully boot. Some of them might not boot but don't worry as there are a lot of GSIs for you to try on.
Same procedure works for both One Action and One Vision
FAQ:
Do I need to flash GAPPS after I install an GSI?
No. Flashing GAPPS is an optional step, most of the GSIs might already come with GAPPS installed and all you have to do to enjoy your ROM is to install the Google Play Services apk mentioned in my post.
You must install GAPPS if the GSI you're using doesn't have the Google Play Store app and you want to install any apps from the Play Store, but even then there are alternatives to install Play Store apps even without installing any GAPPS package
After installing a GSI my phone it's stuck in a bootloop, what do I do?
The main reason for your android not booting up is that some vendors enforce SELinux which stops GSIs from booting and the fix for that is by flashing the Permissiver_V5 zip file to be able to boot into GSI.
But if you can't boot even after you flashed Permissiver_V5, you either downloaded the wrong GSI or the GSI isn't compatible with your device so you have to find another GSI to flash. Remember that not every GSI can successfully boot.
The X GSI has the Y problem! How do I fix it?
Even after your GSI finished booting there's no guarantee that everything will work as it should. The best thing you can do is to find support on google, or if the creator of the GSI has provided any contact links (Email, Telegram, etc) you can contact him and ask him if there's a fix for your problem or not.
This is something new for me, I was used to install rom and gapps, is this something similar?
simije97 said:
This is something new for me, I was used to install rom and gapps, is this something similar?
Click to expand...
Click to collapse
Flashing GAPPS is totally optional, GSIs will work even without flashing them. Most of them already have GAPPS installed, other might not work with GAPPS.
Is totally up to you if you want to flash GAPPS on a GSI, but as I said most of them don't need it, the most important thing to install after flashing a GSI is to install the Google Play Service to login into your Google account and fix any issues related to Android Setup
[Edit] I've added a small FAQ section to my post above
simije97 said:
This is something new for me, I was used to install rom and gapps, is this something similar?
Click to expand...
Click to collapse
There are 2 main reasons why you should install GAPPS:
1: The GSI you're flashing doesn't have any google apps and in that case to be able to login into a google account and install apps using Play Store you have to install a GAPPS package to have access to google play store
2: The GSI has access to PlayStore but you just want to have other apps like YouTube, Gmail installed in your system. In this case I myself, I prefer to install the Google apps that I need from play store rather than installing a GAPPS package that bloats my phone with apps I don't use.
Anyway, flashing GAPPS is totally optional and it's up to you if you want it or not.
The most important thing when installing a GSI is to look if it has any google apps, if yes then it's important to install Google Play Services apk listed in my post.
To give you a small example Google Experience comes with google apps included so you never have to install GAPPS. I'm using Google Experience and everything worked out of the box, it didn't require the Google Play Services but I guess I just got lucky.
This can't be said for when I've installed an Android 11 Pixel-based GSI, where I had to install the Google Play Services to be able to use my Google Account and finish the android setup.
After few weeks I decided to try this and it works just fine, thank you. Unfortunately ROMs are not created for that big hole on the screen. It hides time, notifications etc., otherwise it works pretty well.. Any sugestions how to repair it? Thank you again
Go to developer settings. You find notch settings.
rhaavin said:
Go to developer settings. You find notch settings.
Click to expand...
Click to collapse
I installed Descendant X, there are some options for notch, but it doesn't work for One Vision.
Put the apk attached in /system/overlay and it will correct the values for the punch hole. Don't forget to reboot after. Also I've made this a long time a go but I didn't had time to test it as I'm on Android 8 due to working on something.
Report back if it works or not thanks.
SnoopDoggyStyleDogg said:
Put the apk attached in /system/overlay and it will correct the values for the punch hole. Don't forget to reboot after. Also I've made this a long time a go but I didn't had time to test it as I'm on Android 8 due to working on something.
Report back if it works or not thanks.
Click to expand...
Click to collapse
Unfortunately, I had to install stock firmware because of my work and Google pay. I was trying to hide root but I was unsuccessful. Anyway, thank you very much for sharing this
I installed GSI ROM, I have been trying to root it for 3 hours. Can someone here tell me what to do?
[Q][RECOVERY][3.4.0-0][kane] Official TWRP & Root for Motorola One Vision
Root & TWRP 3.4.0 for Android 10. Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html Installation Instruction 1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and...
forum.xda-developers.com
WellThisSucks1 said:
I installed GSI ROM, I have been trying to root it for 3 hours. Can someone here tell me what to do?
Click to expand...
Click to collapse
You can take the "Magisk-v20.x-phh.zip" for root
Magisk-v20.3-phh.zip | by shumway66 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Should work
simije97 said:
Unfortunately, I had to install stock firmware because of my work and Google pay. I was trying to hide root but I was unsuccessful. Anyway, thank you very much for sharing this
Click to expand...
Click to collapse
This works
alphalog said:
This works
Click to expand...
Click to collapse
How do I make it work?
Como lo hago funcionar xd
ChriisTBv said:
How do I make it work?
Como lo hago funcionar xd
Click to expand...
Click to collapse
Copy the apk to system/vendor/overlay
and reboot
Thank you very much for continuing to support and improve this smartphone

[OOS13] IN2023_11_F.13 Patched boot.img

Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
fastboot flash boot IN2023_11_F13-Patched.img
Click to expand...
Click to collapse
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Thanks for this. Where can you download the oos13 firmware?
MR0808 said:
Thanks for this. Where can you download the oos13 firmware?
Click to expand...
Click to collapse
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Thanks. Looks like I'm getting IN2025, so will have to do the patched boot.img myself.
Time to find my old notes somewhere
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
GhostRider86 said:
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
Click to expand...
Click to collapse
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Neil_Armstrong_ said:
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Click to expand...
Click to collapse
I keepted mine as well, SafetyNet and gPay are working, but Unlock with Fingerprint Sensor is not. No reaction to sensor at all, not able to register new Finger...
Edit: Working now. Needed to disable USNF module, no reboot, Fingerprint Sensor working, register Fingers, screen lock, test, enable USNF module, enjoy
Neil_Armstrong_ said:
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Click to expand...
Click to collapse
I already have the fil, but I can't install it from system update apk,
am I missing something ?
EDIT:
re-downloaded the file again from Oxygen updater, but still it fails to install nd also "verification failed" in system local update.
Edit 2:
I re MSM back to OOS11 and upgraded directly to OOS 13 F3.
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
VBBoston said:
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
Click to expand...
Click to collapse
I updated from oos 13 unrooted. Lost my root using oos12
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
VBBoston said:
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
Click to expand...
Click to collapse
They have already been shared here.
Thank you very much!
stell52 said:
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Click to expand...
Click to collapse
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Neil_Armstrong_ said:
Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Click to expand...
Click to collapse
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
MrBloB said:
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Click to expand...
Click to collapse
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
MrBloB said:
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
Click to expand...
Click to collapse
Flash Universal SafetyNet module in magisk (kdrag0n) and Magisk Bootloop Protector (just in case)
Check your status after a reboot with YASNAC from Play Store
Force the Magisk DenyList, and when configuring it, develop the apps and check all the tick boxes manually (to be sure)
Uninstall Netflix and install the latest .apk from APKMirror, can't help as other app (banking too) works fine
Isn't vanced dead ?
YouTube Premium Argentina is very affordable fyi ....
stell52 said:
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
Click to expand...
Click to collapse
stell52 said:
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
Click to expand...
Click to collapse
Yes i have done this. Tried shamiko as well. M passing safetynet checks, still it doesnt work.

Categories

Resources