Question Android 13: APKs not from PlayStore now crashes at the opening - Google Pixel 6 Pro

Hi
I was on Android 12 and signed in to the beta program 10 days ago.
I've noticed that APKs that were fine on Android 12 are not working anymore on Android 13 Beta.
APKs are crashing at opening.
I thought that may have been an issue related to the beta version of Android but couple of days ago Android 13 stable rolled out (I've signed out from the beta) but those apps are still not working.
I've found older APKs for a couple of apps and one works and one not.
How can I solve this without a factory reset?
Thank you in advance

What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.

skymera said:
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
Click to expand...
Click to collapse
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.

Lughnasadh said:
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Click to expand...
Click to collapse
Wasn't aware of this, thanks!

I don't have any issues with manually installed apks...

Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them

Waiting till the weekend to update, but what APKs are giving the error?

skymera said:
Wasn't aware of this, thanks!
Click to expand...
Click to collapse
Can't find this

Jeff_N said:
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Click to expand...
Click to collapse
Do those apps need Accessibility and/or Notification Access permissions? If not, then I don't think the 3 dot menu needs to be there as it is only for those specific permissions (or whatever other permissions Google might add to the list in the future).
For example, I have Adaway installed but it doesn't have the 3 dot menu because it doesn't need either of those permissions. The same for App Manager.

I am really confused with this new "session-based install" security.
What are "session-based install" and "non-session-based install"
Play store app install --------- surly "session-based install" 100%.
3rd-party store install --------- is said also to be "session-based install".
Firefox download an apk --------- is said to be "non-session-based install",
But how the firefox different from a 3rd-party store????? a system white list something?
safetynet, selinux, forcing many settings, anti-rollback, non-store app restrictions.........
I enjoyed so much that google throws sht tons of troubles to billions of advanced users, to fight an enemy that may not even exist.
(how many people have their phone bootloader secretly unlocked remotely by a hacker and installed root malware, unknowingly?)
Gives a warning is good eg. bootloader locked warning is great IMO. But force the hands and keep finding ways to screw the advanced users as hard as they can, to get the "everything is under my control" status is the wrong path.
I read the news that malware devs have already found a way to bypass this restriction.
In the end, like many others, It achieved nothing, except giving trouble to advanced users and devs.
A global bypass must be also on the way, especially from China. Millions like 90% of APPs are not store-based in China since the google ban, and people are used to download apk from every companies' websites as we do on Windows PC.

somethingsomethingroot said:
Waiting till the weekend to update, but what APKs are giving the error?
Click to expand...
Click to collapse
3 APKs from the company I'm working for (not on PlayStore) 2 sideloaded apps, and a LADB signed sideloaded APK

For example you cut and CC cleaner keeps crashing all the time.

Same here. Almost every app not from Play Store keeps closing right on tap to start them.
Tried to sideload them per USB with full rights. Same.

My company apps that didn't come from the play store are opening without a problem

Thats Vers Strange, indeed.
Every sideloaded App, modded or Not does Not work

Thought it was me...this is bs!
What's the next step...start posting logs I assume?
It's not EVERY sideload for me but about 1 in 3 I'd say.
btw...I got an 'install failed' trying to install/flash the viper4android mod not realizing how old it was...now I'm seeing lotsa audio/sound related crap in logcat reader. If I AM 'currupt' somehow, will just a rom re-flash fix a magisk issue or do I need a full wipe?
Tia for any guidance offered!

Zaxx32 said:
Thought it was me...this is bs!
Click to expand...
Click to collapse
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12

salamala893 said:
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
Click to expand...
Click to collapse
12 won't work right on the 13 bootloader, and you can't downgrade the bootloader.
When I initially tested flashing only the 13 bootloader on my Pixel 6 Pro, while still running Android 12, it booted fine, I unlocked the phone, and all looked normal. But I didn't launch apps, especially Chrome, YouTube, and plenty of other things. If I had, I would have noticed problems that others have had since then. It was since found that certain/many kinds of apps will not work right running on Android 12 when you have the 13 bootloader installed.
I know this above is not what this thread is discussing, but since you mentioned it, I just wanted to point out that if you're on any Pixel 6/Pro/a with Android 13's bootloader flashed, you won't be able to use stock Android 12 on it. You'll be able to flash everything but the bootloader, boot it up, and unlock it, but before long you would discover problems that you wouldn't be able to work around and would effectively make your phone unuseable for many things that we take for granted.
By the way, hopefully you have the 13 bootloader flashed to both slots. Having the 13 bootloader on only one slot is a little dangerous.
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img

Guys, but are you talking of sideloaded apps, or apps installed as apk?

gpvecchi said:
Guys, but are you talking of sideloaded apps, or apps installed as apk?
Click to expand...
Click to collapse
Apks

Related

GPay Can tell root now???

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.

how to stop System out of date update pop-up

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

Question Cannot update Chrome application on global Poco F3 due to unfinished configuration of brand new Android device

Hi all,
I've tried to update my chrome application (the pre-installed on my Global Poco F3 which is under MIUI Global 12.02 stable global) I have tried multiple times to update the Chrome app from the Google Play Store with no success to this day.
I've investigated using adb logcat and I've seen a specific error trigger itself :
4-10 00:34:14.008 17140 17170 E Finsky : [993] tvh.apply(44): IQ::GROUP_INSTALL: Error validating group. Rejecting requests: [com.google.android.trichromelibrary, com.android.chrome]
04-10 00:34:14.008 17140 17170 E Finsky : com.google.android.finsky.installqueue.impl.preprocessor.GroupInstallValidator$InvalidGroupException: GROUP_INSTALL: Group com.google.android.trichromelibrary and com.google.android.trichromelibrary have overlapping module [com.google.android.trichromelibrary, com.android.chrome]
Obfuscated long Java backtrace...
Click to expand...
Click to collapse
I have tried to update chrome on a Redmi Note 8 pro without success as well. However, under LOS (Lineage OS 18.1) another phone has successfully updated the Chrome app, meaning this issue is probably not due to a weird Google Play Store bug but most likely due to MIUI 12.
Anyone has encountered this issue ? And is there any way we could work around this ? (instead of waiting for a potential fix in MIUI 12.5)
Thanks for any help on this matter, I can provide the whole backtrace if anyone want to see it but I doubt it would help anyway since she looks pretty obfuscated to me (the only thing I could understand was some execute function being called but all the classes names have been randomized and most functions call names too).
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
UPD: Or you can download right now from apkmirror.com, if you want
Xoby said:
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
Click to expand...
Click to collapse
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
AkechiShiro said:
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
Click to expand...
Click to collapse
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
I cannot understand the mistake. I updated Chrome to the latest version 3 days ago.
Xoby said:
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
Click to expand...
Click to collapse
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
AkechiShiro said:
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
Click to expand...
Click to collapse
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Fabio Bertelli said:
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Click to expand...
Click to collapse
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
AkechiShiro said:
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
Click to expand...
Click to collapse
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Fabio Bertelli said:
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Click to expand...
Click to collapse
Good thing you figure it out, and also thanks for explaining how for others who will face this issue, maybe sometimes the notification disappears for some reason or the configuration doesn't finish successfully and this issue happens.

Question Unable to install Netflix after rooting

So, I managed to root this beauty 1+9 Pro relatively easily.
I got Magisk installed, and hid all the Apps that needed hiding.
Even Google Pay works.
But I can't for my sanity figure out why Netflix or Android OS 11 is refusing to let me install Netflix.
Everytime I try to install the Netflix App latest APK, extracted from my old working phone ( Razer Phone 2 also rooted), it will just give me the error message " Sorry No Application Available "
Does anyone have a clue what can be done to make Netflix install in a rooted 1+9 Pro ?
Thanks.
BTW i tried several Netflix App version already.
Also I do know the APK works because I used it to install on another Tablet that will not show up Netflix on Google store.
AllGamer said:
So, I managed to root this beauty 1+9 Pro relatively easily.
I got Magisk installed, and hid all the Apps that needed hiding.
Even Google Pay works.
But I can't for my sanity figure out why Netflix or Android OS 11 is refusing to let me install Netflix.
Everytime I try to install the Netflix App latest APK, extracted from my old working phone ( Razer Phone 2 also rooted), it will just give me the error message " Sorry No Application Available "
Does anyone have a clue what can be done to make Netflix install in a rooted 1+9 Pro ?
Thanks.
BTW i tried several Netflix App version already.
Also I do know the APK works because I used it to install on another Tablet that will not show up Netflix on Google store.
Click to expand...
Click to collapse
Is Netflix currently installed as a system app? I wasn't able to uninstall that or get it working, so when I was on 11.2.2.2 I managed to fix it by installing a *newer* version of the Netflix apk that I grabbed from apkpure.com, over top of the system app. Then I had the same issue again on 11.2.4.4, and that method didn't work anymore. However, that time it let me uninstall updates to the app and then update in the play store.
I dont know how exactly, but Netflix still detects the rooted device and denies the install from google play, I think based in the unocked boot loader not sure.
I managed to install from apkmirror and is working fine now.
there is a catch though.
They are moving away from simple apk install and using apk bundles, like some sort of tarball with several apks in it, so you will need this apkm installer app for it to install the newer version. to get this installer working you need to disabled MIUI optimizations from dev options. thats all, I got mine working this passed saturday that way
EDIT: never mind with that MIUI option i thought this was a diffirent model, none the less the apkmirror is still worth a shot
I some how managed to force install it via Titanium Backup, but then it gives me another error when I try to run Netflix App.
" This device is not supported by the app "
it's running the latest version Netflix v7.102.0 build 12 35461
You have to install Magisk Canary, once you do so reboot the phone. Wipe Google play stores data and cache.. magisk hide Netflix and the Google Play Services reboot once more. That's how I got mine to work.
Install: liboemcrypto disabler
from Magisk, reboot ....enjoy
luckylui said:
You have to install Magisk Canary, once you do so reboot the phone. Wipe Google play stores data and cache.. magisk hide Netflix and the Google Play Services reboot once more. That's how I got mine to work.
Click to expand...
Click to collapse
This worked for me too w/ Disney Plus
I used Aurora Store to install it and haven't had an issue even with updating
thats_the_guy said:
I used Aurora Store to install it and haven't had an issue even with updating
Click to expand...
Click to collapse
This sort of worked for me, it game me a failed message, but at least it tried to install, unlike the other Apps that wouldn't even let me try to install.
avid_droid said:
For those of you having issues with Netflix after rooting, install this version over the Netflix you have and it should work fine. It's just a version before the latest...
Netflix 7.102.0 build 12 35461 (nodpi) (Android 5.0+) APK Download by Netflix, Inc. - APKMirror
Netflix 7.102.0 build 12 35461 (nodpi) (Android 5.0+) APK Download by Netflix, Inc. - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Click to expand...
Click to collapse
Just tried, it did not work unfortunately, it's probably related to that SafetyNet error I have in Magisk.
avid_droid said:
Make sure you have magisk canary installed to pass safetynet. Stable magisk doesn't work.
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
I use magisk hide and everything works fine
Click to expand...
Click to collapse
Yeah, I got the SafetyNet thing fixed.
However still unable to install Netflix.
still getting "App Not Installed" error, when I try to install the APK.
I tried installing the "liboemcrypto disabler " as suggested a few messages back, and also doesn't seem to make any difference.
AllGamer said:
Yeah, I got the SafetyNet thing fixed.
However still unable to install Netflix.
still getting "App Not Installed" error, when I try to install the APK.
I tried installing the "liboemcrypto disabler " as suggested a few messages back, and also doesn't seem to make any difference.
Click to expand...
Click to collapse
Have you tried to look for it on the play store after fixing safetynet?
craznazn said:
Have you tried to look for it on the play store after fixing safetynet?
Click to expand...
Click to collapse
I just did after reading this.
It's not showing up in Google Play store.
It's just so weird, everything else works, Google Pay (wallet), Pokemon Go, Banking Apps, everything else that usually will complain and refuse to run when Root is detected, are all working fine, except for Netflix.
avid_droid said:
Try clearing cache and data then try reinstalling app over current Netflix. That's what I do and it works everytime
Click to expand...
Click to collapse
I'm thinking maybe I'll need to un-root my phone, update Netflix, see if it runs without root, if it works, then try to root again and figure how to go from there.
... what a hassle
AllGamer said:
I'm thinking maybe I'll need to un-root my phone, update Netflix, see if it runs without root, if it works, then try to root again and figure how to go from there.
... what a hassle
Click to expand...
Click to collapse
I did this and had the same problem while unrooted, so it turned out to be a waste of time. It seems to have an issue with the unlocked bootloader, not just root. At least with root you can hide unlocked status, which is a step in the right direction. Hide root from Netflix, and also hide magisk app itself in magisk settings.
If you're trying to install Netflix over the system app, make sure to first uninstall updates to the system app so it's the oldest possible version. Then make sure whatever version you're installing on top (whether from play store or APK download) is newer than your installed version. Older versions will not install over newer ones.
terlynn4 said:
I did this and had the same problem while unrooted, so it turned out to be a waste of time. It seems to have an issue with the unlocked bootloader, not just root. At least with root you can hide unlocked status, which is a step in the right direction. Hide root from Netflix, and also hide magisk app itself in magisk settings.
If you're trying to install Netflix over the system app, make sure to first uninstall updates to the system app so it's the oldest possible version. Then make sure whatever version you're installing on top (whether from play store or APK download) is newer than your installed version. Older versions will not install over newer ones.
Click to expand...
Click to collapse
There are sai versions floating around here that work search xda also make sure you magisk hide Netflix before you open it initially. Or hide them clear cache and data on netflix
terlynn4 said:
I did this and had the same problem while unrooted, so it turned out to be a waste of time. It seems to have an issue with the unlocked bootloader, not just root. At least with root you can hide unlocked status, which is a step in the right direction. Hide root from Netflix, and also hide magisk app itself in magisk settings.
If you're trying to install Netflix over the system app, make sure to first uninstall updates to the system app so it's the oldest possible version. Then make sure whatever version you're installing on top (whether from play store or APK download) is newer than your installed version. Older versions will not install over newer ones.
Click to expand...
Click to collapse
Update.
Minor good news.
I wiped the phone from recovery mode.
So, the phone is kind of factory mode, I completed the "new" phone setup thing, and the first thing I went to try was Netflix and it worked.
So... it appears to be something to do with Root and/or Magisk being detected.
Update 2
More good news, I rooted it again, installed Magisk and Netflix is still working.
Not sure why it wasn't working before, also not quite sure what was the actual fix.
I don't really consider a full system wipe a "fix" but well that did it for me.
avid_droid said:
A wipe isn't necessary but glad you got it working
Click to expand...
Click to collapse
So, I just imported Apps and Data from the old phone again via Google "setup my device" transfer, and now Netflix got disabled again.
I'll try again and skip Google transfer to find out if that helps.
I can always use One+ Switch App to see if that is better.
avid_droid said:
OnePlus switch will still result in the same issue. Clear data and cache,install the app link I provided and make sure magiskhide is set to on.
Click to expand...
Click to collapse
Seems like it worked,
I installed a full APK from my old phone and now it's able to run.
However it still doesn't show up in Google Play store when I search for Netflix.

Question T-Mo Forced Update to A12, any way to block?

Been asking T-Mobile and OnePlus on how to block this update as it breaks creation of a work profile and I can no longer us my phone for work. I've downgraded to A11 using MSM but then as soon as I connect to WiFi, the device starts downloading the A12 update. Pausing it says it will update after midnight.
I've forbidden data usage to Android Setup (there is no system update app that I've been able to find in any of the apps even after "show system" is checked) and disabled those apps. I've disabled "allow automatic updates when rebooting". Going into System update there is no gear to stop the update. I've turned data off to anything I can find, i've also done this in safe mode. I can't not be able to use this phone for work and it's basically brand new.
If it's rooted it won't work for Work Profile either. Microsoft documentation states that OnePlus, Oppo, Realme, and Nokia phones do not work with Android 12 and work profiles and that they should not be upgraded yet, so I assume there's a way to stop this upgrade.
Anyone have any luck?
Install NetGuard, go to settings > advanced options > enable system apps.
In NetGuard, search for updater and turn off network for it, then turn NetGuard on and leave the VPN on while you use the phone.
Thanks! When I searched for updater on my phone, under system apps, only Mobile Installer and ConfigUpdater showed up. Searching for update, it's built-in app updates and Dynamic System Updates, both of which I believe are not the right ones to block. I did try blocking all four and the update still applied (I set my time to midnight and left it plugged in)
Any suggestions? I feel like T-Mobile makes this too difficult
For what its worth, I used an app called Island to create a work profile on my device while it still had A11. My phone upgraded to A12 and the work profile and all of its associated apps were still there. I haven't noticed any problems with the apps or accounts on that work profile, either (although A12 is a dumpster fire).
My phone is currently a bone stock LE2127 from T-Mobile.
Strange Vexings said:
Thanks! When I searched for updater on my phone, under system apps, only Mobile Installer and ConfigUpdater showed up. Searching for update, it's built-in app updates and Dynamic System Updates, both of which I believe are not the right ones to block. I did try blocking all four and the update still applied (I set my time to midnight and left it plugged in)
Any suggestions? I feel like T-Mobile makes this too difficult
Click to expand...
Click to collapse
You could use shelter on android 12, it works fine. If you still need to block updates, use PCAPdroid, turn on its VPN, then attempt an update. You should get the update server and you could block it via DNS.
Ok, so I've tried a couple of the above. unfortunately I need to run company portal for it to create the work profile so when I went to use shelter it didn't take as running Company Portal immediately killed it. We use Intune and compliance and all that fun stuff.
I also went and checked PCAPdroid, and I couldn't tell where the update server was, so I went and I blocked network traffic from everything with NetGuard, and slowly removed things to see what app was doing the downloading. The only thing that stopped the update from downloading was blocking Google Play Services.
I have a couple PCAP files but I'm not sure if they are even capturing the download of the update file.
[TABLE]
[TR]
[TD]10.215.173.1[/TD]
[TD]10.215.173.2[/TD]
[TD]mtalk.google.com
googleads.g.doubleclick.net
pagead2.googlesyndication.com
play.googleapis.com
cm.g.doubleclick.net
sync.search.spotxchange.com
s0.2mdn.net
googleads4.g.doubleclick.net
partners.tremorhub.com
www.google.com
pixel.advertising.com
ups.analytics.yahoo.com
play-fe.googleapis.com
play-lh.googleusercontent.com
connectivitycheck.gstatic.com[/TD]
[/TR]
[/TABLE]
[TABLE]
[TR]
[TD]10.215.173.1[/TD]
[TD]10.215.173.2[/TD]
[TD]gateway.oneplus.net[/TD]
[/TR]
[/TABLE]
I suppose I could live life for a few months turning on and off google play services connectivity when I need to install stuff. I just can't believe that T-Mobile knowingly forces this on you.
I don't remember where I found it, I think it may have been some random 8 Pro subforum.
They said to use this command.
I'm crossing my fingers.
Code:
adb shell pm disable-user com.oneplus.opbackup
Unfortunately tried that as well, doesn't exist on the OP9 Pro T-Mo edition. It's almost as if they castrated this version lol.
I appreciate the help though!
Exception occurred while executing 'disable-user':
java.lang.IllegalArgumentException: Unknown package: com.oneplus.opbackup
at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:21670)
Strange Vexings said:
Ok, so I've tried a couple of the above. unfortunately I need to run company portal for it to create the work profile so when I went to use shelter it didn't take as running Company Portal immediately killed it. We use Intune and compliance and all that fun stuff.
I also went and checked PCAPdroid, and I couldn't tell where the update server was, so I went and I blocked network traffic from everything with NetGuard, and slowly removed things to see what app was doing the downloading. The only thing that stopped the update from downloading was blocking Google Play Services.
I have a couple PCAP files but I'm not sure if they are even capturing the download of the update file.
[TABLE]
[TR]
[TD]10.215.173.1[/TD]
[TD]10.215.173.2[/TD]
[TD]mtalk.google.com
googleads.g.doubleclick.net
pagead2.googlesyndication.com
play.googleapis.com
cm.g.doubleclick.net
sync.search.spotxchange.com
s0.2mdn.net
googleads4.g.doubleclick.net
partners.tremorhub.com
www.google.com
pixel.advertising.com
ups.analytics.yahoo.com
play-fe.googleapis.com
play-lh.googleusercontent.com
connectivitycheck.gstatic.com[/TD]
[/TR]
[/TABLE]
[TABLE]
[TR]
[TD]10.215.173.1[/TD]
[TD]10.215.173.2[/TD]
[TD]gateway.oneplus.net[/TD]
[/TR]
[/TABLE]
I suppose I could live life for a few months turning on and off google play services connectivity when I need to install stuff. I just can't believe that T-Mobile knowingly forces this on you.
Click to expand...
Click to collapse
Hi,
It seems like gateway.oneplus.net is the update server, you can try to block that only.
razercortex said:
Hi,
It seems like gateway.oneplus.net is the update server, you can try to block that only.
Click to expand...
Click to collapse
I'm cautiously optimistic right now. Blocked that through no root firewall, tried to download the update and it wouldn't go through. Currently have the phone set to 12 am and sitting on it's own to see if it'll actually auto update over the day. If it doesn't, woo hoo! Thank you so much! If it does, sad face.
You're welcome!
If it doesn't work, let me know and I'll be more than happy to assist you.
Argh! I was wrong, I accidentally had everything blocked and not just gateway.oneplus.net. PCAPDroid isn't picking up any different dns servers or IP addresses when I run it other than what I've posted. I ended up finding a way to block the download when the screen is off (apparently app "Root" in NetGuard stops it from downloading) and I think I should be ok until T-Mo releases a better update with OnePlus that works.
Thanks for the help, hopefully it doesn't and up somehow finding it's away around my network block!
Strange Vexings said:
Argh! I was wrong, I accidentally had everything blocked and not just gateway.oneplus.net. PCAPDroid isn't picking up any different dns servers or IP addresses when I run it other than what I've posted. I ended up finding a way to block the download when the screen is off (apparently app "Root" in NetGuard stops it from downloading) and I think I should be ok until T-Mo releases a better update with OnePlus that works.
Thanks for the help, hopefully it doesn't and up somehow finding it's away around my network block!
Click to expand...
Click to collapse
Is this working for you? Do you still get the notifications about an update being available?
The fix I posted above has worked to prevent notifications & updates on global but I want to go back to T-mobile ROM now due to some odd network behavior.
Oh geez, I just MSM'd back to TMO and I see that TMO is now forcing the first update to be to 12 instead of a newer version of 11.
Global will let you step up to the most recent version of 11 before forcing you to 12.
But TMO just skips right to 12 without giving you a newer 11 first.
Anyone know how to install the most updated version of TMO 11?
CZ Eddie said:
Oh geez, I just MSM'd back to TMO and I see that TMO is now forcing the first update to be to 12 instead of a newer version of 11.
Global will let you step up to the most recent version of 11 before forcing you to 12.
But TMO just skips right to 12 without giving you a newer 11 first.
Anyone know how to install the most updated version of TMO 11?
Click to expand...
Click to collapse
In order to get the latest OOS 11 version, first you need to MSM. Then, you need to update, make sure it's around ~460 MB or so, it will look like it's an update to OOS 12 but it's not. Then you should end up on 11.2.9.9 and then you need to block the update that's around 4000 MB and you should be good to go.
razercortex said:
In order to get the latest OOS 11 version, first you need to MSM. Then, you need to update, make sure it's around ~460 MB or so, it will look like it's an update to OOS 12 but it's not. Then you should end up on 11.2.9.9 and then you need to block the update that's around 4000 MB and you should be good to go.
Click to expand...
Click to collapse
I MSM'd and the current version was 11.2.6.6.le5acb.
Then, I went to the update tab and it says the update available is for le2127_11_c-16, which is the 12 version.
I don't remember the size on it though and I've already moved on to a custom ROM to test something.
Are you saying this was telling me it would be 12 but would have actually done an 11 update?
Yes, at least in my experience.
I was skeptical at first but then thought to myself there was no way an Android 12 upgrade was ~400 MB. Also, given the fact that I tested on global and it forced an upgrade to the latest Android 11 version BEFORE doing an Android 12 upgrade, I figured it wouldn't really have upgraded to Android 12.
CZ Eddie said:
Is this working for you? Do you still get the notifications about an update being available?
The fix I posted above has worked to prevent notifications & updates on global but I want to go back to T-mobile ROM now due to some odd network behavior.
Click to expand...
Click to collapse
That file doesn't exist on T-Mobile from what I've seen. I am just living with the pop up every once in a while.
I found a downgrade thread for T-Mobile to Android 11. I used it and it worked for me. it also fixed my serial number that was missing the leading 0. search for the OnePlus 9 Pro downgrade using the MSM Tool!
TheGhost1951 said:
I found a downgrade thread for T-Mobile to Android 11. I used it and it worked for me. it also fixed my serial number that was missing the leading 0. search for the OnePlus 9 Pro downgrade using the MSM Tool!
Click to expand...
Click to collapse
Yeah that's what I used but then it kept upgrading on its own. Had to do it a couple times then block network connectivity to specific addresses.

Categories

Resources