Database Develop

Managed to get microG working on OxygenOS 9.5.11

First I made a full backup because I didn't think it would work. You should too if you're going to attempt it.
- I patched my rom's services.jar using the Smali Patcher found HERE, enabling the option for signature spoofing in the app
- I pushed the resulting magisk module to my sdcard
- I flashed the module in magisk (using magisk 19.4-736729f5), rebooted, and confirmed that signature spoofing was working using Signature Spoofing Checker
- I downloaded the microg unofficial installer found HERE, making sure it was available on my sdcard for flashing
- I booted into TWRP recovery, mounted the System partition, and using the file manager found under "Advanced", I deleted Google Play Services, Google Services Framework, and Google Play Store from my /system/priv-app directory (I had already deleted Chrome, Play Movies/Music, Duo, etc. a long time ago, so I'm not sure if that's necessary for this to work)
- I went back to the main menu and installed the microg unofficial installer and rebooted the phone
- microg settings was now visible in my launcher, so i opened it and enabled device registration.
- I opened the the patched Play Store app provided by the microg unofficial installer and added my account when prompted
- I downloaded a previously purchased app to test if the app purchases could be validated. It was successful.
That's it. I read a lot of posts claiming that microg wouldn't work on OxygenOS, but I've been using it for 2 1/2 days now with no issues. UnifiedNLP still doesn't work unless you use the xposed module, but this seems to be an issue on every android pie rom that i've tried so far.
UPDATE:
Due to request, I uploaded my generated Magisk module which replaces services.jar with a patched version as requested. It was generated from OOS 9.5.11.
Please be aware that I cannot guarantee it will be compatible with your particular setup

Thanks for this, will give this a try , cheers.

Just a warning, I noticed I'm not passing safetynet after doing this. I've personally never encountered a situation where safetynet is relevant, but I know it'a a concern for a lot of you. I'll let you know if I figure out what's triggering it.

Hi,,may u share your service jar or signature spoofing magisk module here?

I managed to get UnifiedNlp working on custom ROMs. The culprit is the 'NLP Combo feature' commit present in all major OnePlus 7 Pro ROMs' frameworks/base. I made a custom build with this patch and backported Q animations in LineageOS if anyone is interested.
https://forum.xda-developers.com/oneplus-7-pro/development/rom-lineageos-16-microg-support-t3960116

muphetz said:
Hi,,may u share your service jar or signature spoofing magisk module here?
Click to expand...
Click to collapse
Done. Check original post for attachment.

bsimpson1 said:
Done. Check original post for attachment.
Click to expand...
Click to collapse
Tks,,its work with stock oss 9.5.11,,signature checking was enabled,,

Anyone know how to get UnfiedLP working on 10.0.3 without edexposed?

How To Remove Multiple Magisk (In Android 9.x Phone) ??

I noticed something strange, on my phone and I'm trying different ways to solve it, but it just does not "work".
I have 2 x Magisk icons in my phone and I cannot remove them, so that I only have 1 x Magisk.
Here's some background,...
My phone: OnePlus 6 [OP6], with stock Oxygen OS 9.0.9 [OOS 9.0.9] Android and running custom kernel [Omega].
I had been running a ROM [xXx NoLimits] which is a Magisk Module.
For last 11+ months, I have had no issues with my phone, no issues with Magisk, and no issues with root really.
I updated to Magisk v20.0 (but it seems it was the Beta / Canary channel) and also,
I had used the "Hide Magisk Manager" feature, for 1 specific app. to work.
Just this week, I noticed some issues with my phone or that I had 'lost' root
This happens rarely, and I just reinstall Magisk, but it resolves itself.
So, I went looking and saw an odd thing: 2 x Magisk icons.
Since then, I have tried:
- Magisk Uninstaller [Magisk-uninstaller-20191011.zip]
- Flashed unpatched BOOT.img file, Flashed TWRP. Then, rebooted to TWRP.
- Flashed Magisk, flashed the custom kernel.
Still, I saw 2 x Magisk icons.
I could see 1 Magisk was on STABLE channel, while other was on CANARY channel.
This was strange.
So, I changed the CANARY to STABLE, etc. etc...
Anyway, too many combinations of uninstalling and removing root, reinstall Magisk, etc... and I still don't know how to really uninstall Magisk and start from ZERO again.
I have lost Magisk's association to my Magisk modules too.
Can anyone help or advise?

Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers

I think I resolved my issue now...
I uninstalled Magisk using the official Magisk Uninstaller.
I also uninstalled the 2 x Magisk apps in my launcher, using this .APK ---> "Uninstalled SystemApps" ( https://github.com/nicolaserlonghi/UninstallSystemApps )
Then, I had to go through re-installing the BOOT.img, Magisk and most importantly, the ROM (which itself was a Magisk module).
Slowly, it populated the Magisk module list and 'SuperUser' lists, and I think I got the phone back into how I had it.

Didgeridoohan said:
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
Click to expand...
Click to collapse
Yes, exactly.
Thanks for this tip, but I reached this conclusion anyway...
and used another .apk (Unsinstall SystemApps) to remove the Magisk Manager (which was the result of using "Magisk Manager Hide",
but then I must have mixed up Stable & Canary builds of Magisk on the phone, etc.)

Didgeridoohan said:
Sounds like you just have two Managers installed.
Click to expand...
Click to collapse
One thing weird though is, quite a few modules that were previously installed are missing from the Magisk "modules" section.
When I 're-install' them, they still don't show in the "modules" section.
For Example:
Vanced, Advanced Charging Controller, etc... all have been installed, but not showing up in Magisk.
I just had a weird situation of 2 different Magisk installs (at first it seemed like 2 x Managers), but it could be 2 different Magisk builds:
stable and canary
I don't know how to explain it, but maybe the Magisk Uninstaller doesn't work properly on Canary builds?
Anyway, my issue now is modules don't get listed in the Magisk Manager.

No, you did not have two different Magisk builds installed at the same time. Can't happen...
And without more to go on (logs, etc) it's gonna be real hard to help with the module issue.

microG installer Revived major issue - pls help!!!

Guys I'm in a major fix here. Any help would be appreciated.
K20 Pro Global Version - Currently on MIUI Global 11.0.1.0(QFKMIXM)
Rooted via Magisk
Everything was perfectly fine until I noticed 'microG installer Revived' on Magisk and decided to install it.
After I rebooted, Youtube Vanced wouldn't open stating that it won't run without Google Play Services. Same issue with Gmail as well. I went into the microG settings and accepted all the missing permissions. Added my Gmail account, signed in and accepted all the other permission pop-ups that came after.
Despite this everything is still messed up. Gmail and Youtube still gives the same error msg and Chrome keeps crashing.
I tried uninstalling microG but that was an even bigger mistake as the Google Play Services I installed via apk kept crashing.
If someone could pls guide me on how to get the system to how it was prior to the microG installation :crying:

So I managed to fix it somewhat. Uninstalled microG then installed the right version of Google Play services as well as the calendar and contacts sync apks.
No more crash messages but the issue I'm having now is that some app notifications don't work and others (such as Whatsapp) work only sometimes.
And for some really weird reason my Gmail no longer is (or has the option) in dark mode.
Anyway to fix these issues guys?

I've the same problem with my Huawei Mediapad M5 tablet. I've tried to reflash the original "SYSTEM.img" from fastboot mode, but nothing changed. I don't want to do a full reinstall because of this mistake, is there any solution?

Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine

heynando said:
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
Click to expand...
Click to collapse
It's an absolute nightmare, not sure why the devs don't just update the Magisk version, and I agree the Magisk version works perfectly fine

MicroG works only on systems that don't have GAPPS. That should have been included in the documentation.

I had the same problem (I installed the microG installer revived on a cell phone that had google play services, which caused me that error; I installed the magisk module without knowing what it was for), I solved it by doing the following:
1. Uninstall micro-g and google play services and then restart the terminal.
2. Download and Install (install as system application with lucky patcher) the latest version of the google play services apk, restart.
3. Log out or remove google account from device, reboot device.
4. Login or add google account on the device again, restart the device for the last time; and voila problem solved.

I can't remove my account for some reason, and also I can't add a new google account

Hi Guys, have the same problem. has anyone found a solution? would hate to reset it

Trying to work out what it could be for the first post. It sounds like MicroG was installed while the Google Play services were already on the device.
I have actually manually removed Google Services using the debloater magisk module and run it via terminal.
I'm currently using CrDroid Android 12 and it's working fine with MicroG revived version. I have been testing the Android 13 with MicroG and have issues with the Play Store signing in

[MODULE] fakestore2playstore - microG with License Verification + In-App-Purchases

microG works great until a paid app tries to verify the license or when it comes to in app purchases. Using existing tools like NanoDroid and microG Installer Revived has disadvantages (see Readme below). That's why I created a Magisk module that replaces FakeStore with a patched version of the PlayStore. After installing the module, licenses can be verified and even in-app-purchases are possible with microG.
Visit on Github or download v0.1 directly.
Readme:
FakeStore 2 PlayStore​This is a Magisk module that replaces FakeStore with the patched Play Store by Nanolx and is mainly intended to be used with LineageOS for microG, which already ships with microG and FakeStore. I only tested it on LineageOS 18.1 for microG. Use at your own risk, if you are on a different ROM.
The module uses fixed permissions settings from nift4's microG Installer Revived. Additionally it adds the Nanolx's NanoDroid companion F-Droid repository to F-Droid for automatic updates of the patched Play Store.
Why you want to use it​You want to have License Verification and In-App-Purchases with microG and already have a system with microG + FakeStore (like LineageOS for microG)
Installation​
Install LineageOS for microG
Install Magisk
Install the module through the Magisk Manager App
Important: Do NOT flash in TWRP, you need to use the Magisk app and have an active internet connection for downloading the patched PlayStore.
NanoDroid or microG Installer Revived already do the job, don't they?​Yes and no. After several tries with combinations of LineageOS 18.1, Lineage OS 18.1 for microG, NanoDroid and microG Installer Revived, I always ended up with either an unbootable system or with configurations that don't survive OTA upates or that would render microG upgrades useless or install too much.
NanoDroid's patcher (currently?) isn't able to successfully patch signature spoofing into LOS 18.1 and I didn't want to fiddle around with deodexing. My intention was to have a ready-to-use solution for LineageOS that survives OTAs. So I had to use LOS for microG, which already has the signature spoofing patch. However installing the patched PlayStore in LOS 18.1 for microG using NanoDroid always resulted in an unbootable system - even when disabling every other feature in .nanodroid-setup and hiding FakeStore with .nanodroid-overlay.
Though microG Installer Revived does a better job (the system was bootable after installing the patched PlayStore , it isn't able to hide FakeStore on it's own. So I had to still hide FakeStore somehow. Additionally microG Installer Revived installs DroidGuard as a system app, which is not what I wanted. Furthermore, it overwrites GmsCore with it's own version and therefor any OTA updates by LineageOS for microG would've been overwritten by the Installer's version.
That said, it's possible to use NanoDroid's .nanodroid-overlay feature to hide FakeStore in combination with microG Installer Revived to install the patched PlayStore and live with the DroidGuard and OTA issues. But I decided to make a Magisk module that does no more than replacing FakeStore with a patched version of PlayStore. Here it is.
Build​Linux, BSD, macOS, Android​Requires wget.
wget -O META-INF/com/google/android/update-binary https://raw.githubusercontent.com/topjohnwu/Magisk/master/scripts/module_installer.sh && zip fakestore2playstore.zip -9r *
Other​Download this and put it into META-INF/com/google/android/update-binary. And ZIP it.
Credits​
Nanolx for the PlayStore patch.
nift4 for microG Installer Revived

wait does this still use the google play in-app purchase dialogue or are in-app purchases just free now?

MirageSteezyBoi said:
wait does this still use the google play in-app purchase dialogue or are in-app purchases just free now?
Click to expand...
Click to collapse
Negative, nothing is for free! Otherwise it'd be considered warez! This means, this modificated Google Play Store allows you to make the same purchases like the "normal" play store despite the lack of Google Play Services and the use of µG.

Oswald Boelcke said:
Negative, nothing is for free! Otherwise it'd be considered warez! This means, this modificated Google Play Store allows you to make the same purchases like the "normal" play store despite the lack of Google Play Services and the use of µG.
Click to expand...
Click to collapse
cool. works great. vouch

now this is helpful - thank you for releasing this!
for me only worked the one to download directly (1.0). generating or updating the zip like described led to "unzipping failed" message in magisk. i don't know, where the pitfall could be, just mentioning this here.

klaasklever said:
now this is helpful - thank you for releasing this!
for me only worked the one to download directly (1.0). generating or updating the zip like described led to "unzipping failed" message in magisk. i don't know, where the pitfall could be, just mentioning this here.
Click to expand...
Click to collapse
Thanks for reporting. However, I double checked the build steps and ended up with the same file as the released one. I guess it doesn't have to do anything with fakestore2playstore, but may be due to your "zip" executable. In fact, Magisk also complains about the unzipping progress itself. Anyway, I'm happy you find this module helpful!

You should check out https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases they already include the same PatchedPhonesky along with a minimal microG setup similar to the revived version from the Magisk repo, all in one package.
As for signature spoofing and all that if your ROM doesn't support it the easiest way is to use f0mey's Smali Patcher:
[MODULE] Smali Patcher 7.4
Smali Patcher WHAT THE HELL IS THIS THING? :: To sum things up this is an application I developed that pulls the android framework from your device, applies what I (or other users) consider useful patches to the sourced files and then...
forum.xda-developers.com

Thank you a big bunch. Very easy to install, and works pretty good. Some paid apps can't be installed for some reaaon, but you can install them with means, and the licence verification later works! Which is the main point.

I've been using this on 3 phones running gappless + microG. All with different custom ROMs and it appears to work wonderfully for license verification on the few apps I have paid for - except one (titanium backup). FWIW 2 are running A10 and one A11.
Thank's to the developer for this useful app!

It used to work for me, but after I reset my phone a few days ago and tried to install the module again I get error message "download failed and installation failed". I use /e/os (a fork of Lineage OS 18.1) on a Galaxy S10+ and Magisk 24.3. Any ideas?

thegreekfreak said:
It used to work for me, but after I reset my phone a few days ago and tried to install the module again I get error message "download failed and installation failed". I use /e/os (a fork of Lineage OS 18.1) on a Galaxy S10+ and Magisk 24.3. Any ideas?
Click to expand...
Click to collapse
Fixed in fakestore2playstore-0.2.zip
The wget version that ships with the busybox provided by Magisk 24 somehow can't download the patched playstore from Nanolx's repository. The server closes the connection because of a tls error. Now the patched playstore is included in this module and a download isn't required any more.
By the way: I'm on Android 12 now, but the Playstore doesn't work properly. Seems like some permissions/settings are missing. Unfortunately I'm quite busy currently and can't look into this deeper right now. Hope to find some sparetime soon.

sn00x said:
Fixed in fakestore2playstore-0.2.zip
The wget version that ships with the busybox provided by Magisk 24 somehow can't download the patched playstore from Nanolx's repository. The server closes the connection because of a tls error. Now the patched playstore is included in this module and a download isn't required any more.
By the way: I'm on Android 12 now, but the Playstore doesn't work properly. Seems like some permissions/settings are missing. Unfortunately I'm quite busy currently and can't look into this deeper right now. Hope to find some sparetime soon.
Click to expand...
Click to collapse
Please fix Android 12 issue! Please!

Hello, your module is running perfetcly on my device. Thanks!
But I'm still have some questions. Is it possible to install the Original PlayStore with microG installed?

I might have the exact case described here (LOS 18.1 for MicroG), but this does work perfectly. Thanks a lot

Well, doesn't work on Android 12+... Any chance for an update ? This was really a neat module :/

lPolarisl said:
Well, doesn't work on Android 12+... Any chance for an update ? This was really a neat module :/
Click to expand...
Click to collapse
I made it work again, but can't really remember how... first thing is enable network access for playstore in app-setting, it was disabled by default. also, try microG_Installer_Revived-Revived_3.0.0. and mess around with it, somehow it turns out ok ...

Jackson Karloff said:
I made it work again, but can't really remember how... first thing is enable network access for playstore in app-setting, it was disabled by default. also, try microG_Installer_Revived-Revived_3.0.0. and mess around with it, somehow it turns out ok ...
Click to expand...
Click to collapse
It works... Can't believe I missed that, that was all, network access was disabled x(
Thanks a lot, I had completely given up on this !

@sn00x In case you're still around... I now have trouble with your module, for some reason, it installs fine and the Play Store's there on the first reboot, but after the second reboot, it still shows up as active in the Magisk module list, but no Play Store app to be found, only FakeStore...
IodéOS, Android 12

Question Mi 11 Pro - Chines Offic. ROM -> Global ROM Passing SafetyNet?

Hi All,
Im having the Chinese Mi 11 Pro, with the default ROM on to it.
Unlocked, flashed to the Global ROM. BUT its not passing SafetyNet, Logical because the phones bootloader is being unlocked.
No, I don't wanna go using Xiaomi.EU ROM, I just want to use the Global ROM
How to pass SafetyNet on this point? (inc.Root)
Please help me with this..

{Mod edit: Quoted post deleted}
You are unethical person and selfish and should be reported for guiding others with incorrect information.

aygul12345 said:
Hi All,
Im having the Chinese Mi 11 Pro, with the default ROM on to it.
Unlocked, flashed to the Global ROM. BUT its not passing SafetyNet, Logical because the phones bootloader is being unlocked.
No, I don't wanna go using Xiaomi.EU ROM, I just want to use the Global ROM
How to pass SafetyNet on this point? (inc.Root)
Please help me with this..
Click to expand...
Click to collapse
Don't lock the bootloader ever if not stock rom installed, I assume you know already, but worth to mention because others might not know.
I can't help with an answer regarding your question, sorry. Others will be able to help.

{Mod edit: Quoted post deleted}
No, I cant lock the boatloader because that's coussing Bootloop, because its not the default ROM (Chinese).

Hi,
what you need to do to pass Safety Net (assuming you have installed Magisk 23001, so the one still containing Magisk Hide):
1. Install the modules "Magiskhide Props Config" and "Universal Safety Net Fix" (current is 2.1.1)
2. in Magisk enable Magisk Hide and select Google Play, Play Services and (if used) Googe Pay
3. reboot
4. open a terminal, enter root mode ("su") and then "props", changing to the proposed Mi11 Ultra fingerprint
5. go to "Settings->Apps", find "Google Play Services", clear data & cache on that
6. reboot again (you will see a dialogue asking to confirm your Google account for backups if that is configured)
At least on my phones this procedure worked nicely (also on non Xiaomi, of course selecting another fingerprint ), hopefully also for you - and also despite an unlocked bootloader !!

aygul12345 said:
Hi All,
Im having the Chinese Mi 11 Pro, with the default ROM on to it.
Unlocked, flashed to the Global ROM. BUT its not passing SafetyNet, Logical because the phones bootloader is being unlocked.
No, I don't wanna go using Xiaomi.EU ROM, I just want to use the Global ROM
How to pass SafetyNet on this point? (inc.Root)
Please help me with this..
Click to expand...
Click to collapse
Flash magisk + magic hide module

s3axel said:
Hi,
what you need to do to pass Safety Net (assuming you have installed Magisk 23001, so the one still containing Magisk Hide):
1. Install the modules "Magiskhide Props Config" and "Universal Safety Net Fix" (current is 2.1.1)
2. in Magisk enable Magisk Hide and select Google Play, Play Services and (if used) Googe Pay
3. reboot
4. open a terminal, enter root mode ("su") and then "props", changing to the proposed Mi11 Ultra fingerprint
5. go to "Settings->Apps", find "Google Play Services", clear data & cache on that
6. reboot again (you will see a dialogue asking to confirm your Google account for backups if that is configured)
At least on my phones this procedure worked nicely (also on non Xiaomi, of course selecting another fingerprint ), hopefully also for you - and also despite an unlocked bootloader !!
Click to expand...
Click to collapse
Im gonna try this at this moment, I will flash Magisk with the image. And follow the steps you mentionend. Let you know if its worked yes or no.

s3axel said:
Hi,
what you need to do to pass Safety Net (assuming you have installed Magisk 23001, so the one still containing Magisk Hide):
1. Install the modules "Magiskhide Props Config" and "Universal Safety Net Fix" (current is 2.1.1)
2. in Magisk enable Magisk Hide and select Google Play, Play Services and (if used) Googe Pay
3. reboot
4. open a terminal, enter root mode ("su") and then "props", changing to the proposed Mi11 Ultra fingerprint
5. go to "Settings->Apps", find "Google Play Services", clear data & cache on that
6. reboot again (you will see a dialogue asking to confirm your Google account for backups if that is configured)
At least on my phones this procedure worked nicely (also on non Xiaomi, of course selecting another fingerprint ), hopefully also for you - and also despite an unlocked bootloader !!
Click to expand...
Click to collapse
MagiskHidePropsConf/common/prints.sh at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Xiaomi Mi 11 Pro is not listed.
Using Magisk 23011, I can't search modules in this build? How?

aygul12345 said:
MagiskHidePropsConf/common/prints.sh at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Xiaomi Mi 11 Pro is not listed.
Using Magisk 23011, I can't search modules in this build? How?
Click to expand...
Click to collapse
I used magisk 23.0 and worked fine

speedtripler said:
I used magisk 23.0 and worked fine
Click to expand...
Click to collapse
But my phone fingersprint is not listed. I only see:
Xiaomi Mi 11 China (11):Xiaomi:M2011K2C=Xiaomi/venus/venus:11/RKQ1.200928.002/V12.0.22.0.RKBCNXM:user/release-keys__2021-01-01Xiaomi Mi 11 Lite Indonesia (11):Xiaomi:M2101K9AG=Xiaomi/courbet_id/courbet:11/RKQ1.200826.002/V12.5.1.0.RKQIDXM:user/release-keys__2021-06-01
Xiaomi Mi 11 Pro is other codename: Star
Xiaomi Mi 11 Pro with SD888 and code name “Star” is launched in Europe
newsbeezer.com
How can I submit or obtain the correct fingerprint?

Indeed, I just checked and saw that there is no longer any Mi11 Ultra fingerprint.
I'd just take the next closes certified fingerprint, in that case Mi 11 China.....

s3axel said:
Hi,
what you need to do to pass Safety Net (assuming you have installed Magisk 23001, so the one still containing Magisk Hide):
1. Install the modules "Magiskhide Props Config" and "Universal Safety Net Fix" (current is 2.1.1)
2. in Magisk enable Magisk Hide and select Google Play, Play Services and (if used) Googe Pay
3. reboot
4. open a terminal, enter root mode ("su") and then "props", changing to the proposed Mi11 Ultra fingerprint
5. go to "Settings->Apps", find "Google Play Services", clear data & cache on that
6. reboot again (you will see a dialogue asking to confirm your Google account for backups if that is configured)
At least on my phones this procedure worked nicely (also on non Xiaomi, of course selecting another fingerprint ), hopefully also for you - and also despite an unlocked bootloader !!
Click to expand...
Click to collapse
Also If I wanna install the Universal Safetynet Fix 2.1.1 its fails because you need to have installed the module " Riru", 26.1.3 version from github. Is that correct?
So Im having in totall 3 modules installed.
- Magisk Hide props config module from Magisk
- Universal Safety net Fix .2.1.1 from Github
- Riru module installed from 26.1.3 from Github
Is that correct?
Just want to be sure.

Ok, thanks for the addition/correction and apologies for my incomplete list - as I always install Riru for Edxposed I wasn't aware it's also needed for the safety net fix ....
I always installed Riru from the Magisk repo, but of course taking it from the official GitHub is also fine....

s3axel said:
Ok, thanks for the addition/correction and apologies for my incomplete list - as I always install Riru for Edxposed I wasn't aware it's also needed for the safety net fix ....
I always installed Riru from the Magisk repo, but of course taking it from the official GitHub is also fine....
Click to expand...
Click to collapse
Thanks for the confirming.
- But what to do when you install a bank app? Do I need select that App in the MagiskHide? Or what process/handeling I need to walkthrough?
- Do you use the setting: " Hide the Magisk App "? When you use this? Is it useful?
Sorry for these newbie question but wanna be sure that I'm doing it right!

aygul12345 said:
Thanks for the confirming.
- But what to do when you install a bank app? Do I need select that App in the MagiskHide? Or what process/handeling I need to walkthrough?
- Do you use the setting: " Hide the Magisk App "? When you use this? Is it useful?
Sorry for these newbie question but wanna be sure that I'm doing it right!
Click to expand...
Click to collapse
Hi again
yes, you most possibly would need to select the banking app within MagiskHide... In addition some apps check for a ".TWRP" folder on the SDCARD, so in case the app still detects a modified system you could try removing this folder (if its there ).....
Also many apps detect Magisk when the Magisk Manager is not "hidden", so yes, using this setting is advisable as well...
Cheers,
Axel

s3axel said:
Hi again
yes, you most possibly would need to select the banking app within MagiskHide... In addition some apps check for a ".TWRP" folder on the SDCARD, so in case the app still detects a modified system you could try removing this folder (if its there ).....
Also many apps detect Magisk when the Magisk Manager is not "hidden", so yes, using this setting is advisable as well...
Cheers,
Axel
Click to expand...
Click to collapse
Ah I dindt know that... I saw a dir of "TWRP" I deleted this.
- Check always in the folder for the dir. "TWRP" and delete this.
- So I need to select some apps such as a banking app to apply in the list of "MagiskHide", next to the following apps that are already listed such as; "Google Play Store(com.android.vending), Google Play-services(com.google.android.gms)" -*Just ticking/enabling the app it enable one of this services (com.xxx)
- Enable "Hide the Magisk app" in the settings, to be sure that is being hidden.
@s3axel Could you give me advise what to do when there is an OTA update, what is the process or handling to walkthrough? Do you still get Root? Or will it broken? If so, Do I need to reinstalla every module again?
Could you give a view what to do when you execute a Firmware upgrade / OTA?
Thanks so far budyy.

@aygul12345 as you are on Stock Global ROM keeping Root should be pretty straight forward (this is from memory as I'm on Xiaomi.EU where the procedure is slightly different, so others are welcome to chime in as well ) : just take the OTA, install it from within the system menu but DONT reboot just yet. After the update got installed and before reboot go to Magisk Manager and select direct installation - that should be everything you need to do.....

s3axel said:
@aygul12345 as you are on Stock Global ROM keeping Root should be pretty straight forward (this is from memory as I'm on Xiaomi.EU where the procedure is slightly different, so others are welcome to chime in as well ) : just take the OTA, install it from within the system menu but DONT reboot just yet. After the update got installed and before reboot go to Magisk Manager and select direct installation - that should be everything you need to do.....
Click to expand...
Click to collapse
Yes, I'm sitting at the Stock - Global ROM instead of the default Chinese ROM (Bootloader - unlocked)
Thanks to you I'm finally passing the CTS - Profile check. By changing the fingerprint to "Xiaomi mi 11"
The strange thing was that I did this before but didn't worked out.. And now finally it worked out by the steps you mentioned. So many thanks!
I flashed also TWRP as recovery, and Download Magisk (23) 23000, changed it to .zip and installed it from TWRP - Also this gives me root access.
Before I did pathing the boot.img of the ROM, but its not needit anymore.
Thats why I don't know what is the logical, practical way to achieve the goal.
So back to point xD, When installing the OTA from STOCK - Menu I need to go to Magisk Manager and select direct installation. After that I can reboot the phone?

Hi, glad this worked out fine for you
Yes, after OTA installation and Magisk installation you can reboot.....

Please clarify which firmware did you use to convert it to Global?
I can't seem to find any official Global for Mi 11 Pro.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
This link shows the name for both 11 Pro/Ultra, that seems a bit risky to flash.