I've searched and searched and seems no one wanting to stay with Android 10 has run into this problem (unless no one wanted to stay with 10!) I can't seem to figure out how to stop the update nag screen. My fear is that it is going to get accidentally tapped and then I'll be in for a world of work to get back. I've tried disabling all Play notifications but that's not working. The nag usually pops up about once a week. If anyone can help me out I'd appreciate it. Yes, rooted.
There was a thread here a while back about people trying to stay on nine and I believe there was a solution.
see if you can find that thread. same solution may apply to your issue.
Sent from my Pixel 3 XL using Tapatalk
Update: found it!
Not sure if this link will work for you...
https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
If the link fails, The previous thread was started by @KUSOsan on Dec 24 2019. You should be able to find it in search.
@chetqwerty
https://forum.xda-developers.com/pixel-3-xl/help/how-to-stop-date-update-pop-t4024669/page2
If the Tapatalk link doesn't work for ya
Many thanks to both of you, I'll give that a try.
Update with a hiccup:
C:\adb\XL\platform-tools _r30.0.3>Adb shell
crosshatch:/ $ su
Permission denied
Make sure to grant Shell SU rights in Magisk - Then don't freak out after the pm command runs successfully but Magisk keeps crashing until you force stop it, clear it's cache, and restart it to be able to disable Shell SU again.
Will report back if anything wonky results from shutting down the popup.
chetqwerty said:
Many thanks to both of you, I'll give that a try.
Update with a hiccup:
C:\adb\XL\platform-tools _r30.0.3>Adb shell
crosshatch:/ $ su
Permission denied
Make sure to grant Shell SU rights in Magisk - Then don't freak out after the pm command runs successfully but Magisk keeps crashing until you force stop it, clear it's cache, and restart it to be able to disable Shell SU again.
Will report back if anything wonky results from shutting down the popup.
Click to expand...
Click to collapse
If you are rooted you can just do it right from a terminal app on your phone without bothering with ADB. That's how I did it
@chetqwerty
I used terminal emulator which I think was just on the play store but f droid has some as well and there are plenty of other places
KUSOsan said:
If you are rooted you can just do it right from a terminal app on your phone without bothering with ADB. That's how I did it
Click to expand...
Click to collapse
Haha yeah I guess that would have been smart. Saw the ADB command in one of the links you and @CruelSun sent me and followed like a sheep without thinking of terminal. All good short of the Magisk scare which I thought at the time could have been related to changing a system file. A couple more days should tell me if the popup block worked which I would have no reason to think it wouldn't. Next project is to get Miracast working on this thing.
chetqwerty said:
All good short of the Magisk scare which I thought at the time could have been related to changing a system file..
Click to expand...
Click to collapse
Can't really help you with the Miracast but I didn't have any issues with magisk. What magisk are you using?
KUSOsan said:
Can't really help you with the Miracast but I didn't have any issues with magisk. What magisk are you using?
Click to expand...
Click to collapse
Sorry for ghosting you, been a busy month. Not sure which version as I hadn't updated Magisk since I decided to stop updating Android in April. I was using the current release channel at that time. Held off on that too because of the bad press that the revamped version was getting. Anyway it too is current now for what it's worth. I also wanted to update that as you reported in the other thread the method to kill the nag worked with no side affects. Three weeks and no pop-up. Thanks again.
@KUSOsan
Hey Friend - I'm thinking I might have found a side effect maybe? SafetyNet ctsProfile failure. Can you run Magisk SafetyNet check and see if you still pass please? Play Store had a security update last week which I believe may have flagged the state change for the popup. I can be totally wrong but curious if you are seeing ctsProfile failure also.
Thanks,
chetqwerty said:
@KUSOsan
Hey Friend - I'm thinking I might have found a side effect maybe? SafetyNet ctsProfile failure. Can you run Magisk SafetyNet check and see if you still pass please? Play Store had a security update last week which I believe may have flagged the state change for the popup. I can be totally wrong but curious if you are seeing ctsProfile failure also.
Thanks,
Click to expand...
Click to collapse
This may be a coincidence - first three weeks of this month there have been many reports of magisk safetynet check failures. Google seems to be hardening safetynet. Last week my pixel 2 started failing safetynet ctsprofile check and most banking apps and even amazon app would not work. Had to use universal safety net fix by kdrag0n (https://github.com/kdrag0n/safetynet-fix) installed through magisk, plus hide magisk in the app drawer, which I never had to do prior to last week.
Actually the amazon app issue was caused by adaway - adding *amazon* to the allowed list fixed that.
I had considered that, and still maybe the most logical solution, except that all apps including banking, (2 of them and both cloned so 4 fingerprint authenticating banking accounts working fine), Lastpass, Credit Karma, LifeLock, Netflix, all working with no problems. OCD Me hates it but other than the red box in Magisk (confirmed with other cts checkers), phone works great.
Related
Update: Thanks to spotmark's discovery, DirecTV Now is working with root.
spotmark said:
Hide My Root Apk works. :good:
Click to expand...
Click to collapse
spotmark said:
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
Click to expand...
Click to collapse
There's a write-up and link to the apk for this on aftvnews: http://www.aftvnews.com/how-to-use-directv-now-on-a-rooted-amazon-fire-tv-or-fire-tv-stick/
If your rooted FireTV can't see the DirecTV Now app, use this link: https://www.amazon.com/AT-T-Services-Inc-DIRECTV/dp/B01J62Q632 and sign in to your Amazon account. On the right side, select your rooted device and click "Deliver".
----
Original post:
I signed up today for DirecTV Now only to be greeted on my FireTV with the following error:
Code:
This video failed to load. Restart the app and launch your content again. Or search for Error 40 in the Help Center. (QP1005)
Hrmm.. that's weird. So I looked up Error 40, and it says there's a network problem. I tried it on my non-rooted Nexus 6P and it worked flawlessly. So I jumped in to logcat and found some interesting messages:
Code:
I/drm_oal ( 4862): IsDeviceRooted: 0x0000000000000002
and
Code:
D/NewRelicGateway(14071): ERROR event was recorded. Error description = Failed preparing the player because device security check failed due to: (FileSystem)(com.quickplay.vstb.core:1005)
So I installed xposed and RootCloak 2 hoping it would help. I added it to the list of apps and it still had the same problem.
Next thing I did was pull the apk from my Fire TV. After some digging, I found that lib/armeabi/libdrmagent_downloadable_jni.so had some interesting strings in it, including a check for Cyanogen:
Code:
ro.build.product
ro.build.tags,release-keys,OnePlus3#%?OnePlus2#%?OnePlus#%?Z26CL#%?STUDIO_C,ro.build.type,user,#%?
ro.build.display.id,cm_,#%?,ro.build.display.id,cyanogen,#%?,ro.build.type,debug,#%?,ro.build.type,userdebug,#%?,ro.build.host,cyanogenmod,A0001#%?
and a list of strings for paths it might check:
Code:
/system/bin/su,#%?,/system/xbin/su,#%?,/sbin/su,#%?,/system/su,#%?,/system/bin/.ext/.su,#%?,/system/usr/we-need-root/su-backup,#%?,/system/xbin/mu,#%?
su,#%?,busybox,#%?
type %s
test -u `whence -p %s`
/data,#%?,/system,#%?,/system/bin,#%?,/system/sbin,#%?,/system/xbin,#%?,/vendor/bin,#%?,/sys,#%?,/sbin,#%?,/etc,#%?,/proc,#%?,/dev,#%?
/isdrmXXXXXX
Why do they even care if you're rooted?? So lame...
Since they appear to be checking for root in a C/C++ .so file, is Xposed useless here?
jkchr1s said:
I signed up today for DirecTV Now only to be greeted on my FireTV with the following error:
Code:
This video failed to load. Restart the app and launch your content again. Or search for Error 40 in the Help Center. (QP1005)
Hrmm.. that's weird. So I looked up Error 40, and it says there's a network problem. I tried it on my non-rooted Nexus 6P and it worked flawlessly. So I jumped in to logcat and found some interesting messages:
Code:
I/drm_oal ( 4862): IsDeviceRooted: 0x0000000000000002
and
Code:
D/NewRelicGateway(14071): ERROR event was recorded. Error description = Failed preparing the player because device security check failed due to: (FileSystem)(com.quickplay.vstb.core:1005)
So I installed xposed and RootCloak 2 hoping it would help. I added it to the list of apps and it still had the same problem.
Next thing I did was pull the apk from my Fire TV. After some digging, I found that lib/armeabi/libdrmagent_downloadable_jni.so had some interesting strings in it, including a check for Cyanogen:
Code:
ro.build.product
ro.build.tags,release-keys,OnePlus3#%?OnePlus2#%?OnePlus#%?Z26CL#%?STUDIO_C,ro.build.type,user,#%?
ro.build.display.id,cm_,#%?,ro.build.display.id,cyanogen,#%?,ro.build.type,debug,#%?,ro.build.type,userdebug,#%?,ro.build.host,cyanogenmod,A0001#%?
and a list of strings for paths it might check:
Code:
/system/bin/su,#%?,/system/xbin/su,#%?,/sbin/su,#%?,/system/su,#%?,/system/bin/.ext/.su,#%?,/system/usr/we-need-root/su-backup,#%?,/system/xbin/mu,#%?
su,#%?,busybox,#%?
type %s
test -u `whence -p %s`
/data,#%?,/system,#%?,/system/bin,#%?,/system/sbin,#%?,/system/xbin,#%?,/vendor/bin,#%?,/sys,#%?,/sbin,#%?,/etc,#%?,/proc,#%?,/dev,#%?
/isdrmXXXXXX
Why do they even care if you're rooted?? So lame...
Since they appear to be checking for root in a C/C++ .so file, is Xposed useless here?
Click to expand...
Click to collapse
I've read other posts from fellow rooted ftv users reporting the same thing. It would seem as if directv is following suit with PSVue in blocking rooted firetvs. It could be possible that it just won't run on any fireos older than 5.2.2.0
.
Same issue here. I hope someone figures out a workaround soon. I may just have to wait for my Apple TV to arrive.
d3adpool said:
I've read other posts from fellow rooted ftv users reporting the same thing. It would seem as if directv is following suit with PSVue in blocking rooted firetvs. It could be possible that it just won't run on any fireos older than 5.2.2.0
.
Click to expand...
Click to collapse
I was able to get the PSVue up and running using RootCloak but ended up cancelling it due to them ditching Viacom.
Hide My Root Apk works. :good:
spotmark said:
Hide My Root Apk works. :good:
Click to expand...
Click to collapse
Ahh nice! I will try it out tonight when I get home. Thanks!:highfive:
spotmark said:
Hide My Root Apk works. :good:
Click to expand...
Click to collapse
What did you do to get it to work? I installed Hide My Root 4.0 and hid the su binary but it still doesn't work.
ryknow27 said:
What did you do to get it to work? I installed Hide My Root 4.0 and hid the su binary but it still doesn't work.
Click to expand...
Click to collapse
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
spotmark said:
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
Click to expand...
Click to collapse
That did it. Thanks!
I tried Hide My Root 4.0 on a nexus 6 with android 7.0 and the app i guess doesn't work on on 7.0. Which makes sense since it hasn't been updated since 2013. It can't find my root at all.
I ended up just unrooting to try directtv now since I am currently not using the root for anything specific, but obviously I am going to want to root my phone again. Hopefully there is something found to bypass this on android 7.0.
Not even sure why they want to stop root users. I paid just like everyone else. Why crap on us? I am definitely less likely to recommend the service in the future.
eureca said:
I tried Hide My Root 4.0 on a nexus 6 with android 7.0 and the app i guess doesn't work on on 7.0. Which makes sense since it hasn't been updated since 2013. It can't find my root at all.
I ended up just unrooting to try directtv now since I am currently not using the root for anything specific, but obviously I am going to want to root my phone again. Hopefully there is something found to bypass this on android 7.0.
Not even sure why they want to stop root users. I paid just like everyone else. Why crap on us? I am definitely less likely to recommend the service in the future.
Click to expand...
Click to collapse
I believe I saw someone post that Sony does it as well with Vue.
spotmark said:
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
Click to expand...
Click to collapse
This didn't work for me for some reason. I have a 6P that's still on 6.0 due to Xposed. I was able to get around ps vue with root cloak though.
I unrooted my phone just so I could test it out, but it still doesn't work for me because I'm on CM13.1 and I think there is a check on Cyanogen too? That really sucks, I hope someone figures a way around it.
I've tried using RootCloak with the keyword 'cyanogen' added to the blacklist as well as the string 'com.att.tv' added to the list of apps to block, alas without any success.
I also tried suhide with a fresh install of Marshmallow and systemless root, but it didn't work.
I am currently running 6.0.1, rooted 2.76, with Xposed installed.
loloudoudara said:
I've tried using RootCloak with the keyword 'cyanogen' added to the blacklist as well as the string 'com.att.tv' added to the list of apps to block, alas without any success.
Click to expand...
Click to collapse
In the nexus 6p section someone found out that changing build prop got it to work.
http://forum.xda-developers.com/showpost.php?p=69885082&postcount=2
venelar said:
In the nexus 6p section someone found out that changing build prop got it to work.
http://forum.xda-developers.com/showpost.php?p=69885082&postcount=2
Click to expand...
Click to collapse
This didn't work for me.
The build prop edit didn't work for me either
venelar said:
In the nexus 6p section someone found out that changing build prop got it to work.
http://forum.xda-developers.com/showpost.php?p=69885082&postcount=2
Click to expand...
Click to collapse
I have a Nexus 6P and use Magisk Hide to get the app to stream. After flashing Magisk v9 and enabling Magisk Hide, I rebooted the phone and added the Directv NOW app. Works perfectly.
Sent from my Nexus 6P using Tapatalk
xstahsie said:
I have a Nexus 6P and use Magisk Hide to get the app to stream. After flashing Magisk v9 and enabling Magisk Hide, I rebooted the phone and added the Directv NOW app. Works perfectly.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I tried this on my Nexus Player and still didn't work
montajd said:
I tried this on my Nexus Player and still didn't work
Click to expand...
Click to collapse
Could you outline the steps that you took?
xstahsie said:
Could you outline the steps that you took?
Click to expand...
Click to collapse
Installed Magisk v9 manager, and flashed Magisk zip in TWRP. Still get the error 40 qp1005 error. Oh yeah, and enabled Magisk Hide and selected Directv Now. Now I will mention that I also have superSU and Xposed installed if that makes a difference
^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
FIX:
1. Add Google Services to Magisk Hide (if you're on Magisk 18.1 use "su magiskhide --add com.google.android.gms" in terminal)
2. Add Google Pay and Google Services Framework to Magisk Hide
3. Go to data/data and rename com.google.android.gms to com.google.android.gms.bak for example (or delete it altogether, but backing up seems safer)
Reboot and do whatever you like in GPay, it should work now. That's all I've done. I don't think you need to reinstall Magisk.
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
mine is fine
try re flash your rom
i42o said:
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
Click to expand...
Click to collapse
Long thread and a lot of moving parts, so work backwards on the thread. Personally, I am just waiting until a final and formal fix is found on stable Magisk and up to date Play apps.
https://forum.xda-developers.com/app...ssion-t3906703
My experience with this issue is I run GPay, go back to Magisk, safetynet fails on both.. So I force close Magisk, clear cache and data.. reboot. Open Magisk back up, Safetynet passes.. Gpay sets up fine. Sometimes you have to do this several times and it's a real pain but it's always worked for me..
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
dipstik said:
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Click to expand...
Click to collapse
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
jbarcus81 said:
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
Click to expand...
Click to collapse
Get a 2.83 build. Xda shortens links and you lose them on copy text
dipstik said:
Get a 2.83 build. Xda shortens links and you lose them on copy text
Click to expand...
Click to collapse
I know.. it's ridiculous, appreciate the clarification!
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
rob42ert said:
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
Click to expand...
Click to collapse
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
TonikJDK said:
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
Click to expand...
Click to collapse
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
sliding_billy said:
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
Click to expand...
Click to collapse
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
TonikJDK said:
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
Click to expand...
Click to collapse
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
sliding_billy said:
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
Click to expand...
Click to collapse
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Bogega said:
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Click to expand...
Click to collapse
And the doubt kicks back in, LOL. Luckily, I just carry a real card until this is formally solved (hopefully).
Bogega said:
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
Click to expand...
Click to collapse
Sadly this method only works for a limited time.
Overnight GPS updates to version 15 by its own self and GP stops working.
I'm not sure I'm ready to to this procedure daily just for Google pay. For the time being I'll use my card until Magisk developer finds solution to this problem.
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
yeah nothing worked for me even when I uninstalled magisk and tried the steps above on stock. Ended up factory resetting. but thats the last move to do
TonikJDK said:
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
Click to expand...
Click to collapse
Google Pay is a real asshole and doesn't let you know something is wrong until you actually tap to pay.
It's happened to me a couple of throughout my ownership of Pixels.
5T would rooting gain access to Samsung gear and control Gear 2 (R280) & Gear 360?
I've looked all over for a tutorial.
TIA.
Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device? I had that issue with my 6T and my Gear S3. If that is indeed the case you just need to root with Magisk and use:
Magisk Hide Props Module
That module will let you change your device fingerprint to a certified one or something else if necessary. I can test this theory tonight on a rooted 5T with this module if you know what apps you are looking for. (I know what apps are needed for my Gear S3)
Both Magisk and that Module are installed in TWRP. However that module is activated and run from a terminal emulator on the phone. Personally I use this one:
Terminal Emulator
Once running that type:
su <--Hit enter, hit ok when Magisk asks, this will give terminal emulator root.
Now type:
props <--This runs the module you will now get menus choose pick certified fingerprint. It should be pretty self explanatory from here. Any questions ask.
Normal Magsik stuff I recommend hiding Google stuff from Magisk and renaming it with a random name.
Yea, Tried using Wear but doesn't find the R-280 or Gear 360. I remember a modded Gear apk a while back but it didn't work non-root.
So I should root. Is there a good tutorial link that incorporates this props list in the process? Or what rom would be good for this?
I've fairly familiar with the rooting process but it's been a bit.
Thanks for your help.
I've found on several devices now, that sometimes, my cars, headsets, watches, may not pair if the device has been on for some time. A restart and all the sudden everything connects no issue. My Gear S3 is no exception. Restart the phone and my watch and all the sudden it finds it. Your location can be off (my is always off except when using navigation), but those apps do need location permission.
Your best bet is to use FunkWizard's Guide. It doesn't have the props module stuff in it, however once TWRP is installed and you flash magisk, it's just reboot once so magisk will be installed, fully, and then go back to recovery. Then flash the module, then flash busy box. You'll be good to go. (I did realize I left out an important piece of information, that module needs BusyBox to work. You can get that here at the bottom of this post. <-- That BusyBox installer is also installed in TWRP. )
As for ROMs I use Lineage on everything. The privacy guard is the big seller for LOS for me. However that props module works in OOS, on the 5T I used it until LOS came out, back when it was first released. Also used it on my 6T until LOS was fully working with my watch. So all this stuff should work fine in OOS if you want to stay "stock".
Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!
djphooka said:
Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!
Click to expand...
Click to collapse
When you go into Magisk go to Modules in the menu, does the MagiskHide PropsConfig and BusyBox appear under Modules? I would guess they do not if "props" does not work.
Have you ever used APK Mirror ? It is a very handy site sometimes. It's from Android Police, so at least it's not a completely unknown source. That's not to say you shouldn't use direct sources whenever possible.
OhioYJ said:
Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device?
Click to expand...
Click to collapse
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?
djphooka said:
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?
Click to expand...
Click to collapse
I don't know that version would help, but you can try other versions on ApkMirror if you want. I know even in stock form connecting my watch sometimes takes some persistence. Sometimes it takes rebooting both devices to get it recognized, sometimes it just a matter of going back and forth and scanning multiple times. It basically never finds it the first time. Been through it many of times, as you can't just reconnect a the watch after a clean install, it's always completely reset the watch and reconnect as a new device.
Hey guys, I've disabled update notifications through play store and I've disabled auto update system under developer settings as well but this keeps popping up every now and then and I can't figure out to block it. I'm rooted on August 2019 pie build. I've searched the services for play services and play store and can't find anything related to what this update might be from.
I've searched around Google and XDA and haven't found anything regarding this specific pop-up. Anyone have any info?
Following..
I have same issue, but mine is more out-of-date than yours! [emoji16]
Hopefully we'll get some answer here, I have not been able to prioritize this issue in normal life, and this holiday season is not giving me any more time for sure...
Sent from my Pixel 3 XL using Tapatalk
@CruelSun
The annoying part is it doesn't pop up as a notification or an app that would show up in overview mode otherwise I could just long press on it and figure out what process it's coming from. I gotta figure it's from one of the play services but there's so many different ones and nothing I've seen really stands out like updater or anything like that.
Just letting you know, if it pops up & you accidentally hit the update button, turn off wifi & data, then clear the cache/storage on Google Play Services to stop the update.
xnifex said:
Just letting you know, if it pops up & you accidentally hit the update button, turn off wifi & data, then clear the cache/storage on Google Play Services to stop the update.
Click to expand...
Click to collapse
Mine just fails because I cannot connect to google without a VPN.
KUSOsan said:
Hey guys, I've disabled update notifications through play store and I've disabled auto update system under developer settings as well but this keeps popping up every now and then and I can't figure out to block it. I'm rooted on August 2019 pie build. I've searched the services for play services and play store and can't find anything related to what this update might be from.
I've searched around Google and XDA and haven't found anything regarding this specific pop-up. Anyone have any info?
Click to expand...
Click to collapse
I think the process is android system, notification section, it should be listed as download or update or very similar, just turn it off.
boe323 said:
I think the process is android system, notification section, it should be listed as download or update or very similar, just turn it off.
Click to expand...
Click to collapse
Looks like your right. ? Appreciate it. Any idea how to make it changeable? It's greyed out so I cant uncheck it
How about updating?? Problem solved
thatsupnow said:
How about updating?? Problem solved
Click to expand...
Click to collapse
This is funny. People are here denying updates, and I'm here wondering where my Dec update is. I still haven't gotten it along with a ton of others.
bobbyphoenix said:
This is funny. People are here denying updates, and I'm here wondering where my Dec update is. I still haven't gotten it along with a ton of others.
Click to expand...
Click to collapse
I'm on a 3a xl and I got my update Dec 2nd. You can always manually Flash the update it's all ready to download
Also interested in blocking this popup.
Bump
Just found this command to try in another system update blocking thread. Trying it out now. Not sure how often the pop-up appears but I usually see it about twice a week
pm disable com.google.android.gms/.update.phone.PopupDialog
I haven't seen any negative side effects to using this yet but if someone thinks so please let me know.
@CruelSun @ShatteredHalo
Just to let you guys know the command I previously posted has worked. It's been over 2 weeks now and it has not popped back up at all and nothing is broken that I've noticed so far.
KUSOsan said:
@CruelSun @ShatteredHalo
Just to let you guys know the command I previously posted has worked. It's been over 2 weeks now and it has not popped back up at all and nothing is broken that I've noticed so far.
Click to expand...
Click to collapse
If your rooted you can always delete updater apk in system app or priv app
billyt1 said:
If your rooted you can always delete updater apk in system app or priv app
Click to expand...
Click to collapse
There is nothing with update or updater listed that I can delete when I use titanium. I think Google combined it with play services.
Any idea where it would be located for manual deletion? I've searched through both system and priv apps folders and found nothing that would indicate it is the system updater?
KUSOsan said:
@CruelSun @ShatteredHalo
Just to let you guys know the command I previously posted has worked. It's been over 2 weeks now and it has not popped back up at all and nothing is broken that I've noticed so far.
Click to expand...
Click to collapse
Thank you!
Sent from my Pixel 3 XL using Tapatalk
Does the "pm disable com.google.android.gms/.update.phone.PopupDialog" need to be run on a rooted device?
I tried on my unrooted pixel 5, but get the following error. Unfortunately I can't root because of my banking apps.
Code:
adb shell pm disable com.google.android.gms/.update.phone.PopupDialog
Exception occurred while executing 'disable':
java.lang.SecurityException: Shell cannot change component state for com.google.android.gms/com.google.android.gms.update.phone.PopupDialog to 2
at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:21042)
***
I found the answer myself. YES it needs root
I have tried to run this 'pm disable' command and run into the Java error. I am rooted, though with ADB, trying to gain root or anything, everything seems to get a 'permission denied' error.
AutomaticFailure27 said:
I have tried to run this 'pm disable' command and run into the Java error. I am rooted, though with ADB, trying to gain root or anything, everything seems to get a 'permission denied' error.
Click to expand...
Click to collapse
Your device need to be rooted for it to work