I hav had the mi 9t for some time and I'm considering installing a custom ROM, EU variant of the ROM or maybe the screen overclock. As it's my first xiaomi device, could someone confirm wether this affects the warranty in any way? Before this phone I've unlocked my every previous phone and haven't had any problems.
Also: do I have to unlock the "official" way by using xiaomi's app or should I just unlock it with adb (fastboot)?
If you don't use Google Pay then I don't see any downside.
Yes I know there is Magisk but it's a cat and mouse game. One day it works, then Google patches it and it will break Google Pay.
In my case I decided to leave it locked because of Google Pay and another Banking App that won't work if I have a rooted phone.
What do you mean "don't use google play"? I've always had google play working on my rooted devices. Or do you mean just services that straight up don't want a rooted phone (banking apps...)?
slole said:
What do you mean "don't use google play"? I've always had google play working on my rooted devices. Or do you mean just services that straight up don't want a rooted phone (banking apps...)?
Click to expand...
Click to collapse
He's talking about "Pay" not "Play" [emoji6]
Envoyé de mon Mi 9T en utilisant Tapatalk
Hahaha totally missed the lack of an l.
cincin27 said:
Unlocking bootloader = Losing Widevine L1 and Netflix app from Google Play + losing Google Pay (this one could work with magisk fix).
Click to expand...
Click to collapse
OK then. I was mostly concerned with xiaomi's warranty policy and such. The unlock tool is showing me 168h now, wich is kind of unfortunate.
cincin27 said:
Unlocking bootloader = Losing Widevine L1 and Netflix app from Google Play + losing Google Pay (this one could work with magisk fix).
Click to expand...
Click to collapse
I think Mi 9T Widevine stays at L1 after unlocking comparing to OnePlus devices for example. They're going L3.
Sinaptik said:
He's talking about "Pay" not "Play" [emoji6]
Envoyé de mon Mi 9T en utilisant Tapatalk
Click to expand...
Click to collapse
pok5 said:
I think Mi 9T Widevine stays at L1 after unlocking comparing to OnePlus devices for example. They're going L3.
Click to expand...
Click to collapse
I intend to install a custom rom anyways, so ...
cincin27 said:
No. After unlocking and installing for example xiaomi.eu you have L3 on Mi 9T and you aren't able to install Netflix from Google Play.
Click to expand...
Click to collapse
But it is not a downside of unlocking bootloader. It's a downside of installing EU rom because It's based on Chinese software which has no support for Widevine L1. Unlocking for a root/ some mods / etc. should stay L1.
cincin27 said:
No. After unlocking and installing for example xiaomi.eu you have L3 on Mi 9T and you aren't able to install Netflix from Google Play.
Click to expand...
Click to collapse
No. You have L1 on official global and eea_global. Unlocked BL and root doesn't matter. You can always flash one of them to get widevine L1 back. All other roms based on official china (xiaomi.eu mi-globe and so on) are not certified for L1.
And btw: You can't install Netflix because of unlocked BL, no matter which rom. Same for some other apps. You can still sideload them but it sucks to check for updates manually.
Scarface1991 said:
Yes I know there is Magisk but it's a cat and mouse game. One day it works, then Google patches it and it will break Google Pay..
Click to expand...
Click to collapse
There is at least one alternative method for Google Pay which is working even if current Magisk version can be detected by Google Pay and GMS: https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
xaktyc said:
There is at least one alternative method for Google Pay which is working even if current Magisk version can be detected by Google Pay and GMS: https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Click to expand...
Click to collapse
This is interesting. However like with Magisk a solution like this isn't guaranteed to work forever. One day you could have a full cart of groceries and then look like a dumbass not being able to pay for it because Google Pay decided not to work anymore because Google patched something.
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
slole said:
I intend to install a custom rom anyways, so ...
Click to expand...
Click to collapse
Is there already one that is stable enough for daily use? I think the ones that are available are in very early development. Correct me if I'm wrong.
Scarface1991 said:
Is there already one that is stable enough for daily use? I think the ones that are available are in very early development. Correct me if I'm wrong.
Click to expand...
Click to collapse
Most of everything is in early development, but I'll just test out a couple of the ROMs, maybe some GSIs and maybe even help out with testing. Otherwise I'll at least install the EU ROM and the 75hz overclock.
fabsen said:
No. You have L1 on official global and eea_global. Unlocked BL and root doesn't matter. You can always flash one of them to get widevine L1 back. All other roms based on official china (xiaomi.eu mi-globe and so on) are not certified for L1.
And btw: You can't install Netflix because of unlocked BL, no matter which rom. Same for some other apps. You can still sideload them but it sucks to check for updates manually.
Click to expand...
Click to collapse
I have a Chinese Redmi K20 and I'm trying to decide between official global and xiaomi.eu roms. (just waiting for bootloader unlock)
Sounds like Netflix is out whatever - I can live with sideloading.
Google Pay would be nice but as discussed, cat and mouse game that's arguably not worth it.
So what does L1 bring me? I'd like my UK banking apps to work and want Google safetynet passed as having in-app purchase issues with chinese rom.
Will official Global/Euro rom give me that?
kent-spurs said:
I have a Chinese Redmi K20 and I'm trying to decide between official global and xiaomi.eu roms. (just waiting for bootloader unlock)
Sounds like Netflix is out whatever - I can live with sideloading.
Google Pay would be nice but as discussed, cat and mouse game that's arguably not worth it.
So what does L1 bring me? I'd like my UK banking apps to work and want Google safetynet passed as having in-app purchase issues with chinese rom.
Will official Global/Euro rom give me that?
Click to expand...
Click to collapse
Global: Yes. It will. It will also give you L1. If your BL is unlocked your banking app may disappear from playstore -> sideload, hide with magisk
EU (based on chinese): Same as above but without L1.
You can sideload Netflix on any of them, but those with L1 will stream in HD/UHD. Same for all other streaming platforms (e.g Amazon) which use DRM.
Related
Got a message from Google Pay saying that my phone is rooted or is running uncertified software.
I have a T-Mobile variant that I converted , without root, to international. Anyone else see this issue?
Read. This is an old problem for years. Is your bootloader unlocked? Not rooted? Yes this breaks GPay. Hence, Magisk, root, systemless and Hide.
Easy fix.
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
coolmaster121 said:
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
Click to expand...
Click to collapse
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
plasmamax1 said:
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
Click to expand...
Click to collapse
Thanks for the suggestion.
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
coolmaster121 said:
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
Click to expand...
Click to collapse
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
p51d007 said:
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
Click to expand...
Click to collapse
It was a zip I downloaded and did a local update.
Caltinpla said:
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Click to expand...
Click to collapse
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
Yep
No, works fine. But I don't have a converted variant - all stock.
If you go back to stock as it is with T-variant (search for MSM tool), is it certified again?
https://forum.xda-developers.com/showpost.php?p=80844361&postcount=7
noideas4thisname said:
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
Click to expand...
Click to collapse
Nope, I tried everything I heard of but nothing worked. Hopefully, OP releases an update with the fix soon!
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
Seems to be working just like everyone else's T-Mobile Android 10 OP6T. This is a known issues on our devices.
bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
It's a bug, you're going to have to wait until it's patched, no ETA from OnePlus yet.
Sent from my ONEPLUS A6013 using Tapatalk
I converted my T-Mobile phone using the MSM tool (no root) a while ago and never had trouble with Google Pay. It stopped working only after the latest update (Android 10.0). I hope OP will fix this in their next update.
Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?
Scott said:
Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?
Click to expand...
Click to collapse
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...
cultofluna said:
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...
Click to expand...
Click to collapse
The latest magiskhide props module has a valid 6T A10 fingerprint, I'm using it and my device is certified.
Hi all, I have just updated to the latest MIUI 11.0.2 from MIUI.eu just to realise that I was unable to use Netflix. (Takes extremely long at loading, end off with a "Device Failure Occured - 501 109"). Does anyone has the same issue?
Thanks!
Mine actually loads with widevine l3
But the play store can't update apps for some reason, it can't download anything too
Sent from my Redmi K20 using Tapatalk
Clear all cache and data from playstore
Tazreean Shahariyr said:
Mine actually loads with widevine l3
But the play store can't update apps for some reason, it can't download anything too
Click to expand...
Click to collapse
If unlocked your bootloader your device becomes uncertified by Google. Which means you can install or even update the Netflix app that came pre installed.you can check this at play store settings then scroll down.
Benfatica said:
If unlocked your bootloader your device becomes uncertified by Google. Which means you can install or even update the Netflix app that came pre installed.you can check this at play store settings then scroll down.
Click to expand...
Click to collapse
Actually, if you use .EU ROM without root you can still be certified by Google. I'm using latest weekly without root and my device is certified, I can download Netflix from PlayStore etc..
VzQzZ said:
Actually, if you use .EU ROM without root you can still be certified by Google. I'm using latest weekly without root and my device is certified, I can download Netflix from PlayStore etc..
Click to expand...
Click to collapse
Rooted with Magisk and PlayStore is certified too.
Micdu70 said:
Rooted with Magisk and PlayStore is certified too.
Click to expand...
Click to collapse
Yep! Me too
VzQzZ said:
Actually, if you use .EU ROM without root you can still be certified by Google. I'm using latest weekly without root and my device is certified, I can download Netflix from PlayStore etc..
Click to expand...
Click to collapse
I ment stock miui, in Xiaomi EU or any other ROM they trick the system so it behaves as if it's locked, you can see this when you connect you device to the miui debloating tool. You can see that it will say your device is locked but it isn't.
Micdu70 said:
Rooted with Magisk and PlayStore is certified too.
Click to expand...
Click to collapse
Hi, how did you install magisk? I have made a patch file, installed with twrp but no matter what I get a recovery bootloop. Only way past was in twrp to allow permissions on busy box and faulity to 644. This lets me get the root and can get magiskhide but none of he other modules will install and save to the modules menu. MIUI 11
So what is the case here, with the same rom version some phones have widevine L1 and others L3?
atabertass said:
So what is the case here, with the same rom version some phones have widevine L1 and others L3?
Click to expand...
Click to collapse
We speak about Google Play Certification and not Widevine, that's not related.
Xiaomi.eu 11.0.2 has unfortunately L3 widewine and this can cause problems (maybe)
Ps: but dev version xiaomi.eu 9.11.28 has full support L1 and also the device is certified on google play. if not, there is a "safety patch magisk module" and it changes the fingerprint of the device (it changes as Huawei phone ) and works awesome
I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
You can get it to pass by installing a couple modules in Magisk. The first one is busybox as a requirement. The second on is MagiskHideProps; it does the work. Use it to change the fingerprint to a Pixel 3 on Pie. I do not know the drawbacks of doing this, but you will pass the ctsprofile check and be able to use GPay.
Meatmassuse said:
I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
Click to expand...
Click to collapse
cmrntnnr said:
You can get it to pass by installing a couple modules in Magisk. The first one is busybox as a requirement. The second on is MagiskHideProps; it does the work. Use it to change the fingerprint to a Pixel 3 on Pie. I do not know the drawbacks of doing this, but you will pass the ctsprofile check and be able to use GPay.
Click to expand...
Click to collapse
Yea, that's the eventual option I came too as well. Haven't noticed any ill effects yet but who knows if it'll work forever. One amusing side effect was a free 100gbs on google drive when I opened the app. Some pixel promo ot said, haha.
Meatmassuse said:
I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
Click to expand...
Click to collapse
From stock AT&T V35 with latest PIE and security update. These should work with the Magisk props module to pass CTSProfie. I haven't cross-flashed, unlocked or rooted mine due to concerns with widevine L1 and the lack of an AT&T stock backup ROM.
[ro.build.fingerprint]: [lge/judyp_lao_com/judyp:9/PKQ1.181105.001/200341345c8c9.FGN:user/release-keys]
[ro.build.version.security_patch]: [2020-02-01]
Config attached (remove txt extension and place in sdcard directory, then choose custom fingerprint in props module).
rlw6534 said:
From stock AT&T V35 with latest PIE and security update. These should work with the Magisk props module to pass CTSProfie. I haven't cross-flashed, unlocked or rooted mine due to concerns with widevine L1 and the lack of an AT&T stock backup ROM.
[ro.build.fingerprint]: [lge/judyp_lao_com/judyp:9/PKQ1.181105.001/200341345c8c9.FGN:user/release-keys]
[ro.build.version.security_patch]: [2020-02-01]
Config attached (remove txt extension and place in sdcard directory, then choose custom fingerprint in props module).
Click to expand...
Click to collapse
I want you too know that I'd divorce my wife for you sir haha. For real though, thanks bruv.
Meatmassuse said:
I want you too know that I'd divorce my wife for you sir haha. For real though, thanks bruv.
Click to expand...
Click to collapse
Glad to help. I learned a while back to back up my props before hacking on my android devices...
Does anyone have the Oreo fingerprint for AT&T V35? I would very, very much appreciate it. I have cross-flashed to Oreo ULM and can't get CTSprofile to pass using the Pie version.
Edit:
Nevermind. Fixed it by upgrading to ULM Pie and flashing FTM, modemst1 and modemst2 from AT&T.
Hey,
Long time. Rooter (since HTC desire HD) here.
I remember on my older Oneplus phones, installing an beta would stop you passing Safetynet, so banking apps wouldn't work etc. Is this still the case? Can anyone on the 11 betas see if it passes safetynet? I'm not rooted currently!
Anyone?
Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.
mapester said:
Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.
Click to expand...
Click to collapse
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!
manor7777 said:
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!
Click to expand...
Click to collapse
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.
efex said:
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.
Click to expand...
Click to collapse
Ah OK, that makes sense. Most of the OnePlus betas I've installed n the past have been after Google. Released the OS to pixels, and they still failed Safetynet, but I also know Google is constantly changing safetynet stuff so that's why I wondered. Thanks anyway!