How to root my phone ( redmi k20 pro) - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

Since recently my warranty period is over and so I wanted to root my phone and last time I rooted my galaxy tab S2 it was in an system recovery loop, so I wanted to know how to root my k20 pro and also it's been updated to android 11 and will the universal safety net works on it

As soon as you tamper Android OS the SafetyNet pass will fail.

jwoegerbauer said:
As soon as you tamper Android OS the SafetyNet pass will fail.
Click to expand...
Click to collapse
So either stay on MIUI crap or lose Google play?

Your decision.

I have saw some hacks using magisk and successfully passed safetynet and use Google play, is that fake?

Related

SafetyNet flags Z2Pro?

Hello!
The SafetyNet check was updated again - now my Zuk Z2 Pro does not pass the check anymore. The main problem here is, that I already tried a fully unroot it (before the SafetyNet update it was working fine with Magisk v6) and it is still not passing the test. So I have the suspicion, that maybe they blocked the Z2(P) completely, which wouldn‘t be that odd, because (as far as I know) several other devices from chinese manufacturers are blocked already. (The other reason would be, that I messed up my device and still have some root-leftovers remaining.)
Because of that I wanted to ask, if you could check if SafetyNet is passing for you on you Z2(P) and post the results here with your device info (Rom, unlocked?, rooted and if so, which method used?). To do this, I used the following app: SafetyNet Playground
My results:
Device: Zuk Z2 Pro
Rom: ZUI 2.1.120 ST
Unlocked: Yes
Rooted: Magisk v6 + phhsupersu and also without root
Result: Safetynet not passing
Thanks in advance for your help!
I guess you still have some some root-leftovers
Device: Zuk Z2 Pro
Rom: ZUI 2.0.048 ST (international from oppomart)
Unlocked: Yes
Rooted: unrooted
Result: Safetynet is passing
zendertrick said:
I guess you still have some some root-leftovers
Device: Zuk Z2 Pro
Rom: ZUI 2.0.048 ST (international from oppomart)
Unlocked: Yes
Rooted: unrooted
Result: Safetynet is passing
Click to expand...
Click to collapse
Thank you and you were right: I still had some leftovers on my device. Don‘t know exactly what was causing the issue, but managed to get it work by rooting my device again with the TWRP method and then unrooting it, by using the supersu app. What this does, is, to flash the stock image, that was automatically backuped before installing Supersu.
SafteyNet is working fine now! So, I can also confirm that this is not a device specific issue.

Samsung Pay and Magisk

Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Same. Then this droidx program protecting pay app
Sent from my SM-N910V using XDA-Developers Legacy app
Try the universal safteynet net module
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
grymkmb said:
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
Click to expand...
Click to collapse
I'm on an LG
I've got the same issue with galaxy tab 3
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Same problem here; Magisk works but Samsung pay won't work
Even tried freezing magisk. Though still no go must be detecting something.
hkbladelawhk said:
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Click to expand...
Click to collapse
I tried the same thing but couldn't make it work. I think it is due to the fact that the "System Status" is custom (or modified) since magisk modifies the "boot" partition, and that you probably installed a custom recovery to install magisk. That's why OTA also don't work without first flashing back the original boot and recovery images. I don't have an LG to verify that the "System Status" appears on those.
If it does, what could be tried is to install xposed and a module that fakes the system status (if you've got marshmallow or before)
sevenday4 said:
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Click to expand...
Click to collapse
Sorry, once knox is tripped there is no going back. However, installing Magisk fools the phone into thinking knox is still untriggerred (0x0). By reflashing the original firmware, what you did is restore the "boot" partition that was modified by magisk. By doing that, your phone should get back its "official status", allowing OTA. However, Knox will stay tripped. Anyway, Knox does little... and is only used by samsung softwares.
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Booo!
someone please made an apps that can hide or fake the Knox status.
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
This is possible by disabling safetynet check at boot level before compiling the kernel
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
gghose said:
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
Click to expand...
Click to collapse
Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.
Doesn't work for me on a OnePlus 3T, OOS 4.1.7, rooted with Magisk 14.0. This stopped working after the Samsung Pay (Gear version) was updated right around August 21st. Maybe I'm just missing one or more binaries or apps that still must be hidden. I don't have any busybox apps installed, though I previously did, and I removed the busybox binaries where I knew to find them. Maybe it's detecting Magisk's su install, or some other binary I still need to remove. SafetyNet passes just fine, and I can use AndroidPay and CapitalOneWallet on the phone, but I can't use the SPay tab in the Gear app without getting the "rooted phone" message.
Magisk hide 14
Hi Yeti47: I have a samsung galaxy s8 sm-g950f. It is rooted wit renovate ice and magisk 14. What modules I have to check in magisk hide to make samsung pay working? Please answer me in [email protected]. Thank you so much. Bye.
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Spot on fella, just got it working on OP5 with lineage ROM.
dcbii said:
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Click to expand...
Click to collapse
Root explorer won't let me remove it from xbin. How exactly did you do it?
Sent from my iPad using Tapatalk

Google Pay with unlocked Bootloader without root (Android 10)

Hello,
I just flashed Xiaomi.eu ROM 9.10.17. How can I use Google Pay with it? I guess the unlocked Bootloader is preventing Google Pay? When I install Magisk Manager to check if I pass safety net it passes.
My experiences with google pay on Xiaomi.EU roms aren't great...
What you need to install is the magisk manager & hide all the google stuff.
Also you need to hide magisk itself.
https://github.com/davidramiro/gpay-gms-patch/blob/master/README.md
I guess you also need to do this.
But, for me it ain't working.. I guess the problem was with my bank.
Don't know why but I guess it had to be something with Android 10.
I went back to the official miui rom & Google Pay is working again.
I use Google Pay every day so I'm sticking with official rom.
Hope it will work when Miui 11 with Android 10 will be released.
My opinion if you want to do bankstuff & google pay. Stick to official rom.
Hello. for me, no worries. Google play works.
Did you delete your cards then reload them? The instructions said load your cards, but probably should've said delete your cards from Gpay first, follow that patch guide, then entire your cards onto Gpay from scratch.
Running MIUI 11 xiaomi.eu with unlocked bootloader, magisk rooted. Gpay works
So I have to be rooted with Magisk? Because I didn't want to have root anymore.
me it works without Magisk. I had to put the cards passing by miui 11. safetynet ok
Magisk+safety net module
meuhmeuh51 said:
Hello. for me, no worries. Google play works.
Click to expand...
Click to collapse
Google play? Or Google pay?
Works great on RevolutionOS Q
Use hce option under NFC switch in connection menu in the settings if gpay does not tell you that you cannot add any card. Otherwose there is a ton of posts on how to make gpay work on rooted devices
stock miui 11 EU google pay doesn't work (root or no root) something about the unlocked bootloader detection. i have for the life of me never got it to work besides one time it glitched and i did rot hide and extremely fast added a card. it added but never was able to pay with it.
xdarkmario said:
stock miui 11 EU google pay doesn't work (root or no root) something about the unlocked bootloader detection. i have for the life of me never got it to work besides one time it glitched and i did rot hide and extremely fast added a card. it added but never was able to pay with it.
Click to expand...
Click to collapse
Folks, check this thread:
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Method works great. Root needed. See steps that were successful for me at post #764 (4th post page 77) there. PW

Google Pay fix Android 12

Updated to Android 12 and now the GPay doesn't work.
Stock ROM, Cleanslate kernel, no root. Is there a fix? Or do I need to relock the bootloader?
Hi! You will need to root with Magisk and use safetynet fix module. I am affraid that other way doesn't exist with unlocked bootloader...
This doesn't work with the new google pay. For the official android 12 you have to use magisk canary and there is no more magisk hide. They've gone to whats called the deny list. There isn't even a section to view safety net status on the new magisk canary build. I'm on a rooted pixel 4 with official android 12 and I can get every other banking and money app i use to work fine but just not google pay. Google is looking for disabled verity and verification and for unlocked bootloader status. Even if you don't have root, just the fact your bootloader is unlocked will not let google pay to work.
Magisk alpha on T
It works with Pixel 3XL on Android 12. Root / install Magisk, enable SafetyNet (https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/), add Google Pay to deny list and that's it. No SQL hack required...
Search 'google pay' within thread in the link if you're unsure how to set everything up.
This fixed my 4 XL which is running Android 12 November 2021. Been racking my brain the past two days trying to figure out how to get GPay working since upgrading two A12. I NEVER carry my cards, I'd die without GPay.
All I needed was Canary, the newest SafetyNet and to hide GPay.
No SQL hack BS required here either.
Side note, A12 sucks. The layout looks like it was designed for a 70-year-old that has bad vision. I see I'm not the only one that shares these thoughts though, Google's forums and Reddit are littered with people complaining about the same thing.
This may be the first time in history and I'd been a Nexus and Pixel owner for years, I may downgrade back to a previous version of Android, it's THAT bad.
.
updated Android 12 on motorola edge 20 .. rocks .. all smooth good experiance
google pay DOWN
unlocked bootloader .. my OEM UNLOCKINg is greyed out so i didnt root
researched SHIZUKU but doesnt allow me to (use google pay)
strange thing . BANK MILLENIUM has activated my NFC functionality so i can pay in store
WE DONT NEED GOOOGLE PAY ... i just need to get REVOLUT WORKING SAME WAY

Question Netflix issues on rooted Redmi Note 10S

So I installed Netflix on my rooted device after changing device fingerprint and fixing safety net and hiding root using Zygisk + Shamiko (Enforce Disabled) + LSPosed + Hide My Applist + Universal Safetynet Fix. The app runs and logs in, but whenever I try playing ANY video it gives me an error "5.7.6" and says "There is a problem playing this video. Please try again". I am convinced this is a root issue as my sister has the exact same phone I have and it's working fine with her (She is not rooted). Does anyone have any idea what's going on?
I am using a Xiaomi Redmi Note 10S device, Running Android 11 + Custom ROM (LiteE 1.3) + MIUI 12.5
Note: I have done extensive modifications and gone out of my way to hide my root status. I edited the device fingerprint to a Samsung Galaxy S10 Plus and I now pass Safetynet perfectly and Netflix shows up in my Playstore, and I am able to install it and log in fine. My banking apps work, My device shows as certified in Playstore and I even have Widevine L1. So I don't understand why it won't let me play videos. (Screenshot attached)
Laezimir said:
So I installed Netflix on my rooted device after changing device fingerprint and fixing safety net and hiding root using Zygisk + Shamiko (Enforce Disabled) + LSPosed + Hide My Applist + Universal Safetynet Fix. The app runs and logs in, but whenever I try playing ANY video it gives me an error "5.7.6" and says "There is a problem playing this video. Please try again". I am convinced this is a root issue as my sister has the exact same phone I have and it's working fine with her (She is not rooted). Does anyone have any idea what's going on?
I am using a Xiaomi Redmi Note 10S device, Running Android 11 + Custom ROM (LiteE 1.3) + MIUI 12.5
Note: I have done extensive modifications and gone out of my way to hide my root status. I edited the device fingerprint to a Samsung Galaxy S10 Plus and I now pass Safetynet perfectly and Netflix shows up in my Playstore, and I am able to install it and log in fine. My banking apps work, My device shows as certified in Playstore and I even have Widevine L1. So I don't understand why it won't let me play videos. (Screenshot attached)
Click to expand...
Click to collapse
use stock firmware and done
tutibreaker said:
use stock firmware and done
Click to expand...
Click to collapse
Stock firmware = Oversharpened videos
Laezimir said:
Stock firmware = Oversharpened
Click to expand...
Click to collapse
btw why that a lot of steps for enable safety net pass? dude you are doing everithing like 4 years ago, maybe that the problem, in xiaomi for safetyney you only need this magisk module, enable ziygik and delete play store cache
tutibreaker said:
btw why that a lot of steps for enable safety net pass? dude you are doing everithing like 4 years ago, maybe that the problem, in xiaomi for safetyney you only need this magisk module, enable ziygik and delete play store cache
Click to expand...
Click to collapse
Oh that's what I did, but for some reason SNF only doesn't really work, My banking apps never worked until I did all the steps I mentioned.
have you tried this:
GitHub - Magisk-Modules-Repo/liboemcryptodisabler: liboemcryptodisabler
liboemcryptodisabler. Contribute to Magisk-Modules-Repo/liboemcryptodisabler development by creating an account on GitHub.
github.com
clear netflix data after installing
Warning (from readme.md)
A consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1, which means that Netflix will not display content in HD or higher quality, regardless of your subscription type. Of course, without this module, Netflix will not play at all on a rooted device. If this is important to you, you will need to unroot your device.

Categories

Resources