Related
I had to completely wipe my phone since recently the battery life started tanking hard, and I couldn't figure out why. I decided to just start over from a clean slate, since I had the same configuration since I got the phone about a year or two ago (stock Android 9, unlocked, and rooted with Magisk and EdXposed).
I figured that I would flash the July image without wipe first, but the battery issue persisted. I then decided to just flash it with the wipe (after backing up data, of course), and the battery seemed to be a bit better while I was setting up.
The problem I'm now having is that my device seems to be missing Play Certification. I noticed this when I was unable to install Netflix from the Play Store (although Google Pay seemed to work fine?). I've tried flashing the image several times, and even tried older images, but I can't seem to keep Play Certification.
I tried locking the bootloader after flashing the July image, and that finally gave me Play Certification and I was able to download Netflix.
Obviously however, I need to keep an unlocked bootloader for other things too.
Is there any way to get Netflix (and Play Certification) to work with an unlocked bootloader?
Doesn't MagiskHide provide just what you're asking for? If you don't want to use Magisk, maybe try PeNoire's SafetyNet Spoofer which works without Magisk but still requires a custom recovery like TWRP.
nitrous² said:
Doesn't MagiskHide provide just what you're asking for? If you don't want to use Magisk, maybe try PeNoire's SafetyNet Spoofer which works without Magisk but still requires a custom recovery like TWRP.
Click to expand...
Click to collapse
How would I get MagiskHide to work with Netflix without being able to install the app from the Play Store? Would enabling hide for the PS work, or do I need to sideload the app and then use Hide on the app?
Latiken said:
How would I get MagiskHide to work with Netflix without being able to install the app from the Play Store? Would enabling hide for the PS work, or do I need to sideload the app and then use Hide on the app?
Click to expand...
Click to collapse
Netflix doesn't care about the existence of Magisk once it is already installed on your device. So don't get confused there. You're problem is with the Play Store, specifically with SafetyNet. One step at a time;
When you unlock your bootloader, you are going to fail some SafetyNet checks. This will result in a restricted Play Store, meaning, certain apps won't be visible to you. To circumvent that, you flash something like Magisk or PetNoire to hide your bootloaders state to SafetyNet checks. This will result in an unrestricted Play Store. Unlock, install Magisk or PetNoire and then you should be able to get unrestricted access to Play Store apps.
Unlock the bootloader of your device
Install the latest version of Magisk
MagiskHide should be enabled by default, if not:
Download and install PetNoir's SafetyNet Spoofer
nitrous² said:
Netflix doesn't care about the existence of Magisk once it is already installed on your device. So don't get confused there. You're problem is with the Play Store, specifically with SafetyNet. One step at a time;
When you unlock your bootloader, you are going to fail some SafetyNet checks. This will result in a restricted Play Store, meaning, certain apps won't be visible to you. To circumvent that, you flash something like Magisk or PetNoire to hide your bootloaders state to SafetyNet checks. This will result in an unrestricted Play Store. Unlock, install Magisk or PetNoire and then you should be able to get unrestricted access to Play Store apps.
Unlock the bootloader of your device
Install the latest version of Magisk
MagiskHide should be enabled by default, if not:
Download and install PetNoir's SafetyNet Spoofer
Click to expand...
Click to collapse
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Latiken said:
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Click to expand...
Click to collapse
You just need to install Netflix through apk, not playstore. it is working well
Latiken said:
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Click to expand...
Click to collapse
I'v been been having the same issue for about 5-6 months now with both Android 9 and 10. It was working fine on Pie and showing up in Google Play, but then after I flashed one of the monthly system images with a wipe, the app no longer showed up in the play store. And after I restored the most recent Netflix app at the time from a backup, it would constantly crash. I have all Google Play Services, Google Play and Netflix selected in Magisk hide. Google Play says my device is certified. Magisk SafetyNet test passes along with any SafetyNet test app. Logged out of my Google account, wiped data for Google Play, Google Play services and Netflix, rebooted and signed back in but still not showing up. Downloaded and installed the newest Netflix app from their site but I get an error stating the device is not supported with the app which clearly isn't the case.
Can you select this link and have it open in the Google Play app on your phone: https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en_US
It shows up for me but says in red font: "This app isn't compatible with your device anymore. Contact the developers for more info". Which I did...went back and forth with Google and Netflix for hours yesterday, but both of their support is completely useless.
The newest version of the app that works for me is version 6.26.1. You can download it here if you haven't already: https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
The only thing is how long is it going to continue to work. A future update will most likely break that version as well.
Have you made any progress since July?
giants8058 said:
I'v been been having the same issue for about 5-6 months now with both Android 9 and 10. It was working fine on Pie and showing up in Google Play, but then after I flashed one of the monthly system images with a wipe, the app no longer showed up in the play store. And after I restored the most recent Netflix app at the time from a backup, it would constantly crash. I have all Google Play Services, Google Play and Netflix selected in Magisk hide. Google Play says my device is certified. Magisk SafetyNet test passes along with any SafetyNet test app. Logged out of my Google account, wiped data for Google Play, Google Play services and Netflix, rebooted and signed back in but still not showing up. Downloaded and installed the newest Netflix app from their site but I get an error stating the device is not supported with the app which clearly isn't the case.
Can you select this link and have it open in the Google Play app on your phone: https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en_US
It shows up for me but says in red font: "This app isn't compatible with your device anymore. Contact the developers for more info". Which I did...went back and forth with Google and Netflix for hours yesterday, but both of their support is completely useless.
The newest version of the app that works for me is version 6.26.1. You can download it here if you haven't already: https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
The only thing is how long is it going to continue to work. A future update will most likely break that version as well.
Have you made any progress since July?
Click to expand...
Click to collapse
That's actually the exact same version of Netflix that I was able to get working, and I've been using it since July.
It works exactly as it should, but the resolution seems to be capped at 480p or 720p, as I notice a lot of blurriness. It's still usable, but I'm considering getting rid of Magisk and going to 10 to avoid these issues.
Reading on what you've done, it's exactly what I went through in July.
I'm not sure what's changed since prior to updating to another security patch, Netflix was working completely fine from the Play Store with Magisk.
Latiken said:
That's actually the exact same version of Netflix that I was able to get working, and I've been using it since July.
It works exactly as it should, but the resolution seems to be capped at 480p or 720p, as I notice a lot of blurriness. It's still usable, but I'm considering getting rid of Magisk and going to 10 to avoid these issues.
Reading on what you've done, it's exactly what I went through in July.
I'm not sure what's changed since prior to updating to another security patch, Netflix was working completely fine from the Play Store with Magisk.
Click to expand...
Click to collapse
Yeah and also after a few minutes of watching a video, the screen dims like right before your phone auto-locks itself due to inactivity. So far the only way I was able to get it to show back up in Google Play was re-locking the bootloader, but that's not really an option for me since I want to stay rooted. But it really doesn't make any sense since all the SafetyNet compatibility tests pass and the device is certified. Maybe I'll try reaching out to the Magisk dev and see if he's willing to take a look into it.
giants8058 said:
Yeah and also after a few minutes of watching a video, the screen dims like right before your phone auto-locks itself due to inactivity. So far the only way I was able to get it to show back up in Google Play was re-locking the bootloader, but that's not really an option for me since I want to stay rooted. But it really doesn't make any sense since all the SafetyNet compatibility tests pass and the device is certified. Maybe I'll try reaching out to the Magisk dev and see if he's willing to take a look into it.
Click to expand...
Click to collapse
I don't seem to have that screen dimming issue, so it's possible that something else is going on on your end for that.
It's possible that Netflix is able to detect root through some other way that's irrelevant to Google Play Protection. And it could also be a thing where the resolution is limited if you're not on the latest version.
If I do figure something out in the future, I'll be sure to post here again.
Latiken said:
I don't seem to have that screen dimming issue, so it's possible that something else is going on on your end for that.
It's possible that Netflix is able to detect root through some other way that's irrelevant to Google Play Protection. And it could also be a thing where the resolution is limited if you're not on the latest version.
If I do figure something out in the future, I'll be sure to post here again.
Click to expand...
Click to collapse
I don't think the issue is because of being rooted, but instead the unlocked bootloader as it still doesn't show up after uninstalling Magisk or after a system image flash with wipe. Like I mentioned earlier, the only way I can get it to show in Google Play or have the newest version work when side loaded at this point is when the bootloader is locked. So if you don't mind not being rooted or being able to manually flash updates without a factory reset each time, just re-lock your bootloader (just remember to backup your data since it wipes your phone) and Netflix should work normally again.
But I'll be sure post here as well if I come across anything that works.
What you both need is to install/flash a custom kernel...
On top of many multiple things a custom kernel can do, one significant thing is to be able to mask root on many/most root detecting processes. When I first rooted 2 years ago, I couldn't get Google Pay to work because of the root detecting. I had inadvertently flashed a custom kernel, and was pleasantly surprised that Google Pay began to work (back then, but now more than a custom kernel is required).
The best general all-around custom kernel was called Flash, but that became EOL and stopped development, but one called Caesium was built based off of Flash and continued from there; even collaborated with the maker of Flash.
Give it a try, and see how it works wonders for both your issue (root detection) battery life, and even responsiveness of the system!
Hope this helps...
simplepinoi177 said:
What you both need is to install/flash a custom kernel...
On top of many multiple things a custom kernel can do, one significant thing is to be able to mask root on many/most root detecting processes. When I first rooted 2 years ago, I couldn't get Google Pay to work because of the root detecting. I had inadvertently flashed a custom kernel, and was pleasantly surprised that Google Pay began to work (back then, but now more than a custom kernel is required).
The best general all-around custom kernel was called Flash, but that became EOL and stopped development, but one called Caesium was built based off of Flash and continued from there; even collaborated with the maker of Flash.
Give it a try, and see how it works wonders for both your issue (root detection) battery life, and even responsiveness of the system!
Hope this helps...
Click to expand...
Click to collapse
Thank you for the suggestion, I'll make sure to try this after updating to the latest Pie build. I'm sure that this will work, as I remember using a custom kernel last time that Netflix was working just fine for me.
I also just found a thread with a stock kernel infused with a SafetyNet patch that says that Netflix and other apps refused to work on unlocked bootloader devices because something trips in SafetyNet, leading me to believe that this is what me and @giants8058 have been experiencing.
I will let everyone know if this works later this week.
Latiken said:
Thank you for the suggestion, I'll make sure to try this after updating to the latest Pie build. I'm sure that this will work, as I remember using a custom kernel last time that Netflix was working just fine for me.
I also just found a thread with a stock kernel infused with a SafetyNet patch that says that Netflix and other apps refused to work on unlocked bootloader devices because something trips in SafetyNet, leading me to believe that this is what me and @giants8058 have been experiencing.
I will let everyone know if this works later this week.
Click to expand...
Click to collapse
You have to flash a custom Kernel to hide bootloader unlock. After you flash the custom kernel the play store will still show as not being certified. You will have to force stop the play store then delete the cache and storage. When you reboot it will show that it is certified.
murphyjasonc said:
You have to flash a custom Kernel to hide bootloader unlock. After you flash the custom kernel the play store will still show as not being certified. You will have to force stop the play store then delete the cache and storage. When you reboot it will show that it is certified.
Click to expand...
Click to collapse
I flash the August stock build along with the Sultan kernel (as I couldn't get Caesium or the SafetyNet patched kernel to flash), and followed your instructions, but my Play Store isn't showing my device as certified yet.
Is there something else I need to do?
Latiken said:
I flash the August stock build along with the Sultan kernel (as I couldn't get Caesium or the SafetyNet patched kernel to flash), and followed your instructions, but my Play Store isn't showing my device as certified yet.
Is there something else I need to do?
Click to expand...
Click to collapse
1. Download TWRP 3.3.0 img file
2. Download TWRP 3.3.0 zip file (optional)
3. Download Magisk 19.3
4. Download kernel of choice. (I use Sultan)
5. Boot to fastboot
6. Boot to TWRP. (fastboot boot TWRP. Img) I shorten the file name to make it easier.
7. Flash kernel first if using Sultan
8. Flash TWRP zip. (optional)
9. Flash Magisk 19.3
10. Let phone boot then delete data/cache in play store.
11. Reboot phone
These are the steps I use. If I remember correctly there was a couple of versions of the play store that showed uncertified no matter what. The latest play store version is 16.5.15. I can confirm it works. I also hide Google Play services in Magisk hide but I don't think that's needed unless you want Google Pay to work.
murphyjasonc said:
1. Download TWRP 3.3.0 img file
2. Download TWRP 3.3.0 zip file (optional)
3. Download Magisk 19.3
4. Download kernel of choice. (I use Sultan)
5. Boot to fastboot
6. Boot to TWRP. (fastboot boot TWRP. Img) I shorten the file name to make it easier.
7. Flash kernel first if using Sultan
8. Flash TWRP zip. (optional)
9. Flash Magisk 19.3
10. Let phone boot then delete data/cache in play store.
11. Reboot phone
These are the steps I use. If I remember correctly there was a couple of versions of the play store that showed uncertified no matter what. The latest play store version is 16.5.15. I can confirm it works. I also hide Google Play services in Magisk hide but I don't think that's needed unless you want Google Pay to work.
Click to expand...
Click to collapse
Those steps are actually exactly what I did, but the certification label in the settings is missing, and Netflix won't appear.
If it means anything, I noticed that I actually had Sultan kernel installed before doing any of this, so it might be that the kernel isn't working on my end.
Latiken said:
Those steps are actually exactly what I did, but the certification label in the settings is missing, and Netflix won't appear.
If it means anything, I noticed that I actually had Sultan kernel installed before doing any of this, so it might be that the kernel isn't working on my end.
Click to expand...
Click to collapse
Well...I can say, at least, that I am having the same experience as murphyjasonc and am able to get "Play Protect Certification" certified and I have an unlocked bootloader with root and even a custom recovery.
I would make sure you do as he suggests and at the very least disable or "uninstall updates" for the Play Store and Google Play Services. But, also, custom kernels are things that also need to be updated; so this might be the explanation on it no longer working. But I know you had recently reflashed Sultan, so it is rather puzzling that you are still having those issues.
Just making sure, you are using TWRP to install the latest version of those kernels, correct? Also, when you had ran the August patch, did you use the Full Factory version? Are you able to pass safetynet currently?
Hopefully retrying these will get things up and running...
simplepinoi177 said:
Well...I can say, at least, that I am having the same experience as murphyjasonc and am able to get "Play Protect Certification" certified and I have an unlocked bootloader with root and even a custom recovery.
I would make sure you do as he suggests and at the very least disable or "uninstall updates" for the Play Store and Google Play Services. But, also, custom kernels are things that also need to be updated; so this might be the explanation on it no longer working. But I know you had recently reflashed Sultan, so it is rather puzzling that you are still having those issues.
Just making sure, you are using TWRP to install the latest version of those kernels, correct? Also, when you had ran the August patch, did you use the Full Factory version? Are you able to pass safetynet currently?
Hopefully retrying these will get things up and running...
Click to expand...
Click to collapse
I used the latest version of TWRP to install the August OTA patch, as well as to install the latest Sultan kernel.
I just ran a SafetyNet test in MagiskManager and it passed correctly.
Latiken said:
I used the latest version of TWRP to install the August OTA patch, as well as to install the latest Sultan kernel.
I just ran a SafetyNet test in MagiskManager and it passed correctly.
Click to expand...
Click to collapse
Give this a try...
instead of the OTA, try the Full Factory version -- and be sure to remove the "-w" in the flash-all to keep your data intact -- and then, also, be sure to disable/"uninstall updates" for both the Google Play Store and the Google Play Services (you can enable it after disabling it of course). After that, boot up TWRP and flash the Sultan kernel and Magisk and see if you don't have the certification after all that.
If you don't know; you can't simply run the Full Factory .zip's in TWRP, so if you don't know how to do a Full Factory version, I can point you in the right direction...
Good luck!
Global Update is there.
For those who installed it already, give us some feedback.. and one question, should factory rested be done before or after installing update? What is better, because i never did reset before, just apply update, but now would like to do reset also..
Works fine without reset. Smartphone was very hot during update. After installation I made a reboot. All Apps are working and Dark Mode is now available for most Apps.
This update broke my GooglePay, no longer passing ctsProfile in safetynet.
Seems to work fine. Before this update I was getting more and more bugs, but they seem to be gone now. Rebooting after the update took a long time, however. I was stuck on the Mix logo for 5-10 minutes.
There are some visual tweaks here and there, but that's all I can notice.
Themes available, region uk!
Latest update has caused my home launcher to crash. Am only able to use it cause of 3rd party launcher.
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
*update*
I had an out of date version of exposed installed that caused boot loop.
I can't install work email, and because my phone is CN region, of course, Google Pay not working. Not sure if boot options for the kernel changed, going to look and see if I need to update my flashable patcher zip.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Yes...work perfectly.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Not with the latest stable version. Take a look here so solve your problem: https://github.com/topjohnwu/Magisk/issues/2492#issuecomment-593149828
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Anybody found a solution for viper4android? I tried rootless 2.7 but driver will not install.
Quality_con_troll said:
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Click to expand...
Click to collapse
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
spyke180 said:
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
Click to expand...
Click to collapse
Just went through this process myself and came back here now to report on it.
This was my process for anyone also looking for guidance.
This will work for the new android 10 updated. I came from MIUI10 (10.0.3.2.0) using system update to go to MIUI11 and android 10 (11.0.3.0) via OTA update, which reverted to stock recovery and obviously lost root as well.
1. Saved most recent twrp 3.3.1-7-recovery.img for perseus by mauronofrio found in these XDA threads, magisk 20.3.zip found on magisk site and repository, and just to be sure disable forced encryption-treble.zip (just search for it) to my phone AND adb directory on Windows 10 computer.
ENSURE USB IS PLUGGED INTO 2.0 or 2.0 COMPATABILE HUB (Flashing recovery failed when connected to a USB3.0 port) and ADB/FASTBOOT is installed on your computer.
2. Booted into fastboot. (Power + Volume down)
3. Ran cmd.exe and entered "cd C:/(wherever you installed/platform-tools" without quotes.
4. Entered "fastboot devices" to ensure fastboot is connected. It should show device_id# and fastboot next to that.
5. Flashed TWRP3.3.1-7 for MiMix3 perseus (latest unofficial TWRP) by entering "fastboot flash recovery twrp3.3.1-7-recovery.img"
6. Entered "fastboot reboot recovery" the phone will reboot now, ENSURE YOU HOLD VOL+ ASAP or you will lose TWRP with stock recovery.
7. After booting into TWRP, entered password, wiped data and cache only.
8. In TWRP go to install and choose your disable_forced_encryption-treble.zip and flash it but do not select reboot device, it is selected by default.
(NOTE: Don't know if #8 is a necessary step especially for Global devices but did it anyways and it didn't hurt anything)
9. Go to install again and choose magisk20.3.zip, this time you can select reboot device.
10. After completing android setup download magisk manager 7.5.1 from play store and verify 20.3 is installed, if it is then congrats, you're rooted.
That's it! Like the above post said ctsProfile is reading false meaning you most likely will not be able to use Pay apps like Google Pay, etc.
Other apps that use google play services for verification may not work as well like Pokemon GO, Mario Kart, Harry Potter, or other banking/security apps. (Not sure about this one yet, try MagiskHide in the manager. Spyke180 is reporting above they do not work currently.) So if you can't live without Samsung Pay, or one of these games wait until a ctsProfile:true/SafetyNet passes solution is available.
Hopefully the next magisk update or someone in the community will be able to solve these issues in a timely manner, shouldn't be much of a wait.
Hope this made sense and can help some peeps out there perhaps.
CTSProfile is failing on my device as well. I tried using the boot cmdline patcher I made and it's still failing. I am wondering if Xiaomi released this update before getting the fingerprint in the CTS approved list. I can't think of anything else. My device is a CN device, so the BL is unlocked. I don't know if flashing Magisk with CN device and Global software still results in a boot loop but may try it.
Also, Magisk is detected through some methodology. I read all the posts made in both the release and beta threads in the last 3 days and it seems broken for everyone.
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
siuyan187 said:
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
Click to expand...
Click to collapse
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
spyke180 said:
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
Click to expand...
Click to collapse
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
siuyan187 said:
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
Click to expand...
Click to collapse
I see.
If you're rooted, you could try using the systemize module to make it a system app.
I verified my Google Messages and its notifications are working for me, even with both Wi-Fi and mobile data turned off.
Developer Preview is up if anybody wants to try it
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Holy Moly.
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
DoobyDroid said:
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
Click to expand...
Click to collapse
Seems like for now, most UI and user facing changes in general are hidden behind flags, this one is meant for the devs, so it's to be expected. The beta, on the other end, will be aimed at users, and then we will see what changes
I upgraded last night. Had to reboot twice after restart. Then everything was stable. First time it rebooted after install, nothing seemed to want to work and kept FCing. Second reboot, everything is fine now. Sometimes, Nova needs to be indicated when I press the home button that it's default, otherwise, everything is working fine.
Is it me or does the Android version still say 11 but the build is "S"?
I downloaded the 12 DP1... and it just isn't ready yet (understandably so) for the daily driver use I need.f
Rooting it requires disable verity and verification. You'll need magisk 23 or canary to patch boot.img as well. Not disabling verity/verification, it will only boot back into fastboot and list the reason as something like, "unable to load boot image".
Once rooted, I moved on to installing edxposed --- using riru, riru edxposed, and edxposed manager. Everything installs without problems. Final reboot, and reboots as normal. But then about 90 seconds later, you'll start getting FC after FC after FC. All apps too, and background apps, and systemui, etc.
Removing the riru components and edxposed manager, doesn't correct this problem.
Did fresh format and reinstall of the DP1... rooted again... and then tried Viper4Android. I use a very simple version. You just flash it, and its done (no manual driver install either). Rather than the 3 reboot, AML, driver install, etc.
V4A installs with good logs. Reboots without a hitch. But I noticed the v4a icon in the status bar is missing. I open it up manually, and start getting freezes and fc's. Within 5 minutes, I get kernel panic reboots -- and non-bootloop freezes on the working G screen.
Reboot manually with long press power, get it loaded back up and immediately remove V4A. Reboot and now I'm back to stock.
Get FC's every hour or two. Random reboots too. Battery life is struggling.
I decided to wait until a better version drops, perhaps the beta or at least a DP2.5 or 3.0. As of right now, having Android S is mostly just a status thing -- to show people how cool we are to have access to it as such an early stage. But unless you are dedicated to helping improve the ROM through daily use and reporting... I highly recommend that you stick with Android R.
Just flashed the 1st public android 12 beta bramble-ota-spb1.210331.013-3c294b13.zip with adb sideload. Listed as android S atm, surprised 5G was enabled as this wasn`t the case with android 11 in the Netherlands. All apps working fine so far and still finding out the new stuff.
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
ekowwillis said:
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
Click to expand...
Click to collapse
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
galza said:
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
Click to expand...
Click to collapse
Clean wipe and follow the OP instructions in this Pixel 5 thread. Make sure you use the images for 4a5g where needed
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
Hello,
I have a brand new device which has not officially been released yet. Therefore, there is no stock firmware image available or recovery image. Just wanted to get that out of the way. I could not remove a lot of the manufacturers bloatware because i could not root or port TWRP without a stock image or recovery image.
I stumbled onto Project Treble. I flashed phh treble and it worked. Well, I managed to get everything to work with some workarounds. The only thing I am having trouble with is when I install phh with gapps. After booting I get the "Your device is not Google certified" message repeatedly spammed.
The only workaround I have been able to get to work for the uncertified device message is to remove phh superuser. I have tried using the Google device registration page. It does not work for my device. I want to keep root so I can pull the recovery image and port TWRP for this device. Are there any other fixes that will work? In order to pick up in some of my games I think I need Google Play?
Thanks,
Rocky
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
LR7875 said:
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
Click to expand...
Click to collapse
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
bigroc2223 said:
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
Click to expand...
Click to collapse
No no no, you need to patch boot.img for magisk, not system. Go to www.apkmirror.com (app repository), search and download 'magisk ' app(that is magisk manager), click and install the downloaded .apk file, allow install from browser, and after installing use the app to patch the boot.img(search Google), and flash patched boot.
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
bigroc2223 said:
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
Click to expand...
Click to collapse
I am sorry to hear that.It is pretty much beyond what I can solve so I will try find similar threads.
Hello, yesterday I rooted my phone since I needed to hide the fact that my bootloader was unlocked from GPay, but after installing the magisk app, patching my boot.img and installing the boot.img with fastboot, GPay does not detect NFC, the option for nfc also disapeared from my settings and notification center. Is this a known issue, is there a solution, where would I start looking? Thank you in advance
I've had zero issues myself due to magisk itself, both android 11, and now 12, work just fine, I do not use GPay, but my bank app, and some rfid-and-nfc reader apps work just fine
perhaps just re-getting the boot img, and patching and flashing it again helps? SYSTEM not seeing nfc is real weird (obviously assuming stock rom, and not messing around with custom rom stuffs), magisk itself will NOT touch any partitions containing drivers or system files, it will just patch the boot proccess to load custom stuff, and the custom modules and such might in turn mess a bit with the system