I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?
Unlocked and still certified. I assume it's because I haven't modified the system partition by only using systemless mods in magisk
Sent from my Pixel 3 XL using Tapatalk
Pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 3 XL using Tapatalk
If you've installed overlays, they reside in system/app, and thus you have modified system.
You're certified because Magisk hide is doing its job in relation to SafetyNet.
superchilpil said:
Unlocked and still certified. I assume it's because I haven't modified the system partition by only using systemless mods in magisk
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
diesteldorf said:
I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?
Click to expand...
Click to collapse
I'm bootloader unlocked, rooted, running a Substratum theme and Android Pay works fine plus my device is certified in Google Play.
You have to use Magisk hide on the apps that don't work with root. As far as your device showing up as not certified, use Magisk hide on Google Play store then reboot, then clear the storage and cache on the play store, reboot again and it will show up as device certified.
These are the apps I use Magisk hide on and everything on my Pixel 3 XL works like it's not rooted.
diesteldorf said:
I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?
Click to expand...
Click to collapse
Just clear data in the play store. Thats all it needs....
micmars said:
If you've installed overlays, they reside in system/app, and thus you have modified system.
You're certified because Magisk hide is doing its job in relation to SafetyNet.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Overlays are in the vendor partition not system.
Back on my Pixel C when we didn't have twrp I would unpack the vendor partition and place the overlays.
NVM I guess OMS has changed since I last used it
Sent from my Pixel 3 XL using Tapatalk
No, not on Pie.
superchilpil said:
Overlays are in the vendor partition not system.
Back on my Pixel C when we didn't have twrp I would unpack the vendor partition and place the overlays.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
elreydenj said:
Just clear data in the play store. Thats all it needs....
Click to expand...
Click to collapse
That fixed mine from saying that it was not certified. Thanks!
Related
Dear All,
I was on my way to yet another bootloader unlocked phone of mine, but I happened to have a doubt about a point mentioned on Motorola's official BL unlock link:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My concern lies with the possible loss of encryption support.
My questions are, will my Addison's encryption be lost if:
I unlock the bootloader but don't flash any custom ROM
&
I Root my phone and use system modifications like use Xposed and Viper4Android
Thank you for your patient and relevant help!
Cheers!!
I unlocked my bootloader and am rooted. Device still shows as encrypted. Not sure why they issued that warning.
are you all using the unlocked GSM model?
Milly7 said:
I unlocked my bootloader and am rooted. Device still shows as encrypted. Not sure why they issued that warning.
Click to expand...
Click to collapse
Thanks for that info.
With respect to why that warning by Motorola, I believe it is because once we unlock the bootloader and flash custom ROM that might not be complied to support encryption or there might be some bugs in the custom ROM that doesn't enable encryption or if we modify system in such a way after rooting that the encryption might be lost due to these changes.
Hence, I believe this is why Motorola says "You may lose encryption support."
This was my understanding but I wanted to get it cleared on xda.
Can anyone throw some more light on my understanding?
We can then close this thread after complete clarity to all members so this turns out to be a fruitful discussion to most members here.
Cheers!!
Milly7 said:
I unlocked my bootloader and am rooted. Device still shows as encrypted. Not sure why they issued that warning.
Click to expand...
Click to collapse
Rooted via systemmode Super SU or systemless?
LAst I had checked only systemmode was able to patch the boot image.
hmnk said:
Rooted via systemmode Super SU or systemless?
LAst I had checked only systemmode was able to patch the boot image.
Click to expand...
Click to collapse
Hold up, does systemless root actually work for the Z Play then? I haven't received mine yet, but I was under the impression anything systemless wouldn't work from reading around, like Magisk or systemless SuperSU.
lpchaim said:
Hold up, does systemless root actually work for the Z Play then? I haven't received mine yet, but I was under the impression anything systemless wouldn't work from reading around, like Magisk or systemless SuperSU.
Click to expand...
Click to collapse
I rooted my Z Play (XT1635-02) recently using phh superuser.
Installed Magisk after that, and it seems to me it's systemless
as Adaway wouldn't work till I did the systemless hack - plus /system was read only
ozblogger said:
I rooted my Z Play (XT1635-02) recently using phh superuser.
Installed Magisk after that, and it seems to me it's systemless
as Adaway wouldn't work till I did the systemless hack - plus /system was read only
Click to expand...
Click to collapse
I see, thanks. Yeah, magisk is definitely systemless, good to know it can be used normally.
Just for clarification, you can decrypt by formatting data on twrp. By just unlocking or rooting the encryption does not go away.
Enviado de meu XT1635-02 usando Tapatalk
I'm very frustrated because after updates my play store is uncertified by google while it used to be certified. What do you think?
Everything fine for me. Updated to the latest Nougat and no problems.
Mine is also uncertified and i am not able to update the play store past 7.6.08.N.all. Tried all the tricks to force it but to no avail. the only thing i have not tried is to side load the apk but i would rather i knew it was legit straight from googles servers.
mmm strange !! i havent seen such things.. my playstore is working fine..
What version of play store are you running, is it newer than 7.6.08
I have diabłed play store and enabled and it got fixed.
Wysłane z mojego Lenovo P2a42 przy użyciu Tapatalka
esselite said:
I have diabłed play store and enabled and it got fixed.
Wysłane z mojego Lenovo P2a42 przy użyciu Tapatalka
Click to expand...
Click to collapse
How did you disable Play Store?
Disable and enable is not working for me still stuck on version 7.6.08
Well tried to side load play store to the latest version, guess what, still uncertified. My play services are up to date, and now other than a full reinstall i am out of ideas. my boot loader is unlocked! could that be the reason?
chtsarts said:
How did you disable Play Store?
Click to expand...
Click to collapse
Go to settings>applications>disable it Will unistall and when you enable it Will update version.
FOR the version, i don't think it has anything with version. I'm on same version and it has bęben certitfied.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
esselite said:
Go to settings>applications>disable it Will unistall and when you enable it Will update version.
FOR the version, i don't think it has anything with version. I'm on same version and it has bęben certitfied.
Click to expand...
Click to collapse
It's certified now. Thank you very much
Got it certified. In the end i had to clear cache and data from play services and play store, then disable play store and uninstall its update THEN uninstall my google account completely, reboot and set up my google account again then enable play store and update it.
What a palaver!
All good now
Well I was wrong I thought it was certified as at one point it showed no certification information at all and I assumed that ment it was certified. this is where I am at the moment: I have a Three branded p2 with unlocked bootloader which I have flashed to the row firmware. I have re-flashed the row firmware and updated to the latest N Android. I have tried a full reset and now I have play store 7.7.17.0-all. I do not have Root or TWRP. I have repeatedly wiped cache and data of play store and services as well as cache wipe in recovery.
Anyone have any ideas I am stuck.
Thought i would update my situation one last time. I am now certified i had to install Majisk via TWRP and turn on Majisk hide in settings.
I saw difference on play store for certified device and uncertified device like certified device Android 6.0.1 have super Mario run but uncertified device also Android 6.0.1 can't get super Mario run, I followed disable and enable play store after that automatically update play store for my uncertified device after that i can't see the certified and uncertified column showing now,,,?
Please help..
vermillions said:
Thought i would update my situation one last time. I am now certified i had to install Majisk via TWRP and turn on Majisk hide in settings.
Click to expand...
Click to collapse
Hi vermillions, thanks for your infos !
What version of Magisk zip did you install through TWRP ? The one provided in MM root method thread (one team) or the one provided by Magisk app ?
Defboy said:
Hi vermillions, thanks for your infos !
What version of Magisk zip did you install through TWRP ? The one provided in MM root method thread (one team) or the one provided by Magisk app ?
Click to expand...
Click to collapse
Installed the one from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
vermillions said:
Installed the one from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thank you ! Ok, so I will do it with Magisk app since I'm already rooted.
Do you think it's better to uninstall phh's Superuser and use MagiskSU root management ?
EDIT : It failed. After some research, it seems I cannot install it on deodexed nougat rom. What rom do you use ?
I am using Magisk own root without any problems, i was not rooted before so just flashed zip and used its own root. I think you should be fine with your system less superuser. Any problems just unroot and use Magisk's own root.
vermillions said:
I am using Magisk own root without any problems, i was not rooted before so just flashed zip and used its own root. I think you should be fine with your system less superuser. Any problems just unroot and use Magisk's own root.
Click to expand...
Click to collapse
Do I need to flash stock rom and not use deodexed nougat rom anymore in order to fully use Magisk (and get certified play store) ?
So apparently there has been an update and all my devices are now showing up as uncertified in the Play store. Anyone seen a new work around for this while running custom ROMs?
On the bright side it seems devices that you side load apps too, still get updates for the moment.
Stock OOS 5.1.4 UBL is also uncertified :|
Anyone else have this issue on Stock OOS with unlocked BL??
I've never seen my device be certified since I began using this phone. Is it normal for UBL phones to be uncertified even if they aren't rooted?
TechieTwinToes said:
Anyone else have this issue on Stock OOS with unlocked BL??
I've never seen my device be certified since I began using this phone. Is it normal for UBL phones to be uncertified even if they aren't rooted?
Click to expand...
Click to collapse
Mine is certified with unlocked bootloader and root (on latest openbeta)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A5010 using Tapatalk
alessandro_xda said:
Mine is certified with unlocked bootloader and root (on latest openbeta)
Click to expand...
Click to collapse
Hey alessandro,
Does disabling Play Protect have any role in this? I keep it disabled because I side-load many apps.
OhioYJ said:
So apparently there has been an update and all my devices are now showing up as uncertified in the Play store. Anyone seen a new work around for this while running custom ROMs?
On the bright side it seems devices that you side load apps too, still get updates for the moment.
Click to expand...
Click to collapse
Sorry, your account has been flagged for piracy, so you'll have to reflash every 7 days else your account won't give up updates.
killier2653 said:
Sorry, your account has been flagged for piracy, so you'll have to reflash every 7 days else your account won't give up updates.
Click to expand...
Click to collapse
That's not what it means. Custom ROMs, unlocked boot loaders, rooted devices, etc, can trigger this. Generally custom kernels or Magisk would prevent this. However not anymore . Right now I'm seeing it across 4 accounts, 8 devices, 4 different types of devices, all LOS.
Here is the fix. Just tested this on the latest build of LOS, and it works fine. Direct link to the Magisk module.
Also those directions, say they chose a Pixel fingerprint, I chose the OP 5T fingerprint, it worked just fine. My device is now certified.
OhioYJ said:
Here is the fix. Just tested this on the latest build of LOS, and it works fine. Direct link to the Magisk module.
Also those directions, say they chose a Pixel fingerprint, I chose the OP 5T fingerprint, it worked just fine. My device is now certified.
Click to expand...
Click to collapse
can you pass safetynet ?
try this app
latest safetynet api
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
AlMaghraby said:
can you pass safetynet ?
try this app
latest safetynet api
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Click to expand...
Click to collapse
I tried that app, yes it passes. Both CTS profile and Basic Integrity come back true.
(Obviously adding that app to the hide list)
OhioYJ said:
I tried that app, yes it passes. Both CTS profile and Basic Integrity come back true.
(Obviously adding that app to the hide list)
Click to expand...
Click to collapse
thank you so much that was the only thing preventing me from updating
I've heard it may have something to do with WideVine DRM or something. I've tried the Magisk DRM module with no change.
Seems to be an issue with people who are stock, unrooted, and locked as well.
Any ideas how to get around?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 3 XL using Tapatalk
Yes I am unrooted but unlocked and to no avail I am unable to download it. I even tried to download apk but wouldn't flash.
Installed fine for me. Rooted unlocked.
Sent from my Pixel 3 XL using Tapatalk
lafester said:
Installed fine for me. Rooted unlocked.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Odd, won't even show up in Play store for me
Sent from my Pixel 3 XL using Tapatalk
Don't forget, if you're an unlimited VZW subscriber, we get Disney+ free for a year.
Unlocked and rooted
No changes in MAGISK
Installed and runs without issue
From the phone anyway.
It won't show up in the playstore App for me, but I was able to install from the web, pushing to my device
I think I'm on the beta playstore, fwiw
Sent from my Pixel 3 XL using Tapatalk
spotmark said:
Don't forget, if you're an unlimited VZW subscriber, we get Disney+ free for a year.
Click to expand...
Click to collapse
Thank you for the tip. Signed up, installed from playstore, ran fine. Unlocked and rooted.
Sent from my Pixel 3 XL using Tapatalk
Installed from playstore and playing videos fine.
My wife was able to install it on her 3XL but it doesn't show up in the play store for me. I used this guide to get it installed.
Remove the underscores.
https://www._android_sage_.com/2019...-apk-on-any-android-device-from-any-location/
DarkPhoenix said:
My wife was able to install it on her 3XL but it doesn't show up in the play store for me. I used this guide to get it installed.
Remove the underscores.
https://www._android_sage_.com/2019...-apk-on-any-android-device-from-any-location/
Click to expand...
Click to collapse
I'm having the same problem with Netflix now, I opened the app and it says that I have to install an update. I open the play store and it tells me that the app is not compatible with my phone.
Bone stock here on my 3 XL and doesn't show up in Play Store on the phone and from the web it tells me I have no compatible devices.
thenags said:
Bone stock here on my 3 XL and doesn't show up in Play Store on the phone and from the web it tells me I have no compatible devices.
Click to expand...
Click to collapse
So apparently it has something to do with Google's Play Protect feature, supposedly if you're on stock and have an unlocked bootloader it flags your device as unprotected even though it still scans your apps (at least that's my understanding). I flashed Lineage 17 and was able to download both Disney+ and Netflix without issue with my bootloader unlocked.
DarkPhoenix said:
So apparently it has something to do with Google's Play Protect feature, supposedly if you're on stock and have an unlocked bootloader it flags your device as unprotected even though it still scans your apps (at least that's my understanding). I flashed Lineage 17 and was able to download both Disney+ and Netflix without issue with my bootloader unlocked.
Click to expand...
Click to collapse
I'm stock, unlocked, and rooted. It installed fine.
spotmark said:
I'm stock, unlocked, and rooted. It installed fine.
Click to expand...
Click to collapse
same here
All Android 10 launch devices will no longer have the 2-button gesture navigation that was introduced in Android 9 Pie. If you cared for this and want it back on your Pixel 4, simply flash the Magisk Module attached to this thread and reboot. You should see the 2-button navigation option in Settings > System > Gestures > System navigation.
This Magisk Module simply adds the 2-button navigation overlay from the Pixel 3. No changes are made to any system files or properties.
Thank you so much. Your work makes the Pixel very AWESOME [emoji7]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 4 XL using Tapatalk
Cool man. Thanks for giving us another option. I never tried this but currently getting used to it. Only time will tell if I can break my old habits. Lol.
This is just what I've been missing. Thanks!
Sent from my Pixel 4 XL using Tapatalk
Works great......Thank you
This is great man thanks for this option.
Gotta love root I swear lol
Love this mod. Thanks!
Thank you for this. Was the one thing I was missing.
I really enjoy this mod. Has anyone had problems with it working on the January build? After flashing, I no longer have the option for 2 button.
Sent from my Pixel 4 XL using Tapatalk
MArtyChubbs said:
I really enjoy this mod. Has anyone had problems with it working on the January build? After flashing, I no longer have the option for 2 button.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
One of my favorite mods. Not working here on a fresh install of the January build.
Darn Google!
Sent from my Pixel 4 XL using Tapatalk
Here's an updated one. Uninstall the old one, from the OP, because I probably used a different ID.
MArtyChubbs said:
I really enjoy this mod. Has anyone had problems with it working on the January build? After flashing, I no longer have the option for 2 button.
Click to expand...
Click to collapse
I just went back into settings and navigation, set it to 2 button and worked fine after taking January update.
Was set back to gesture mod on fresh boot.
---------- Post added at 02:49 AM ---------- Previous post was at 02:47 AM ----------
cstark27 said:
Here's an updated one. Uninstall the old one, from the OP, because I probably used a different ID.
Click to expand...
Click to collapse
I'll install this one anyway even though the one in OP works fine.
Pixel4_2ButtonNav_v1.0.zip
cstark27 said:
Here's an updated one. Uninstall the old one, from the OP, because I probably used a different ID.
Click to expand...
Click to collapse
hey idk if this is replying or pm'ing you im new to the website but do you use adb? when i do adb sideload Pixel4_2ButtonNav_v1.0.zip , it says connection failed
Please publish the mod in Magisk, can't find it in the modules to download list. :highfive:
quorn23 said:
Please publish the mod in Magisk, can't find it in the modules to download list. :highfive:
Click to expand...
Click to collapse
Just download from op, in Magisk go to modules, press the + sign at the bottom center, then just find the zip in your downloads folder and select it.
eg1122 said:
Just download from op, in Magisk go to modules, press the + sign at the bottom center, then just find the zip in your downloads folder and select it.
Click to expand...
Click to collapse
:laugh: haha thanks, but my question wasn't how to install it, but Magik modules belong in the Magisk Manager, this way Version tracking etc is simpler and in case newer Magisk versions require a new module template etc :highfive:
quorn23 said:
:laugh: haha thanks, but my question wasn't how to install it, but Magik modules belong in the Magisk Manager, this way Version tracking etc is simpler and in case newer Magisk versions require a new module template etc :highfive:
Click to expand...
Click to collapse
Ah, sorry about that. Just reading it sounded like you were not sure how to install.
gwylius said:
hey idk if this is replying or pm'ing you im new to the website but do you use adb? when i do adb sideload Pixel4_2ButtonNav_v1.0.zip , it says connection failed
Click to expand...
Click to collapse
No you apply it using Magisk app.
cstark27 said:
No you apply it using Magisk app.
Click to expand...
Click to collapse
And you need to be rooted right? I don't think Verizon has their bootloader's unlocked