Database Info

Bypassing SafetyNet

Hey guys...
So as some of you may know, Pokemon GO recently released in India. I wish to play the game, but am unable to do so due to the SafetyNet checks it uses...
I read somewhere that the SafetyNet API uses a feature called "Verified Boot" in order to check whether the bootloader is unlocked or not. Obviously my device has an unlocked bootloader and I'm running CM14.1 as of now.
Any ways to get Pokemon GO working?

Adrao123 said:
Hey guys...
So as some of you may know, Pokemon GO recently released in India. I wish to play the game, but am unable to do so due to the SafetyNet checks it uses...
I read somewhere that the SafetyNet API uses a feature called "Verified Boot" in order to check whether the bootloader is unlocked or not. Obviously my device has an unlocked bootloader and I'm running CM14.1 as of now.
Any ways to get Pokemon GO working?
Click to expand...
Click to collapse
* After flashing, delete the su directories (/system/bin/su or /system/xbin/su).
* Then flash supersu in systemless mode (echo SYSTEMLESS=true>>/data/.supersu command)
* Then flash suhide
* Then flash Xposed Framework, the systemless version.
* Install rootswitch, then toggle "stop all SU daemons" on, then disable root.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
http://www.asus.com/zentalk/tw/thread-173542-1-1.html

moralesnery said:
* After flashing, delete the su directories (/system/bin/su or /system/xbin/su).
* Then flash supersu in systemless mode (echo SYSTEMLESS=true>>/data/.supersu command)
* Then flash suhide
* Then flash Xposed Framework, the systemless version.
* Install rootswitch, then toggle "stop all SU daemons" on, then disable root.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
http://www.asus.com/zentalk/tw/thread-173542-1-1.html
Click to expand...
Click to collapse
The Xposed Framework does not support SDK25 yet...

Adrao123 said:
The Xposed Framework does not support SDK25 yet...
Click to expand...
Click to collapse
Sorry, I didn't pay attention to the CM version.
You have to go back to CM13 or another 6.x equivalent at least

moralesnery said:
Sorry, I didn't pay attention to the CM version.
You have to go back to CM13 or another 6.x equivalent at least
Click to expand...
Click to collapse
It still does not work... suhide is facing issues flashing
it says something about /system/xbin/su still being present... when I try to manually rm -rf it, /system is a ro mounted directory... even if I mount it manually with rw it still doesnt delete

you can use magisk with phhs superuser, works fine with that

aldanopolis said:
you can use magisk with phhs superuser, works fine with that
Click to expand...
Click to collapse
Flashed it... still not working... I flashed with phh superuser... any chance it is conflicting with CMs inbuilt root system. If so, how can I disable CMs root...
Also are there any AOSP 7.1.1 ROMS out there?

Adrao123 said:
Flashed it... still not working... I flashed with phh superuser... any chance it is conflicting with CMs inbuilt root system. If so, how can I disable CMs root...
Also are there any AOSP 7.1.1 ROMS out there?
Click to expand...
Click to collapse
you need to remove su binary from /system/bin and /system/xbin
sorry for the late answer

In CM14 you have two choises
* After fresh install download SuperSU and do a full unroot
* Download and install iSu to hide root
Both of those options work as I have used them before.

LineageOS + Magisk SafetyNet

Hello,
can anybody help me for my Problem with my Galaxy S4 GT-I9506
i have do the following
1. TWRP install the actual version
2. flash lineage-16.0-20190609-UNOFFICIAL-ks01ltexx https://forum.xda-developers.com/galaxy-s4/i9506-develop/rom-lineageos-16-0-unofficial-galaxy-s4-t3848597
3. flash open_gapps-arm-9.0-pico-20190612 TWRP
4. flash Magisk-v19.3 mit TWRP
But i have problems with them
https://prntscr.com/o7onem
https://prntscr.com/o7oneu
https://prntscr.com/o7oner
i have no idea what i can do can anybody help me please?

Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case

I had a look at the device tree and I can see a couple of things for your dev @kyasu to possibly add
- we had safetynet start failing a few weeks back on i9505 and these were the fixes I found
- Product_name - Samsung never released a product called full_ks01ltexx - will need to be set to correct product that google recognises by a build_prop_override ("GT-I9506" or similar).
- Change build fingerprints to pixel3 versions.
- hide permissive with init script.
these 2 commits here show what needs done:
https://github.com/JDCTeam/android_...mmit/ea27cf29e4084d860fb8549be2e3cdb1599a6d08
https://github.com/PixelExperience-...mmit/045dc32219172a288c10f503478deb3eb3b2aee5

andrew2432 said:
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
Click to expand...
Click to collapse
is this tool correct? https://forum.xda-developers.com/showpost.php?p=63615067
is the rom correct what i use?

OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem

tuvok1981de said:
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
Click to expand...
Click to collapse
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.

Buff99 said:
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Click to expand...
Click to collapse
- yes i have make with MagiskHidePropsConf-v.4.0.3 and terminal props S4 and S4 Active variante but it will not do this
- it will not work all the time where i have flash my S4
- i have no idea iam not the developer from the rom iam only a User

1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?

andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
Point 1. is on the Phone
ähm where must i make Point 6 ?

andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
OK i have make flash new all 5 Points
but ctsProfile: false / basicIntegrity: false on Magisk Manager

tuvok1981de said:
-
- i have no idea iam not the developer from the rom iam only a User
Click to expand...
Click to collapse
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.

Buff99 said:
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Click to expand...
Click to collapse
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!

tuvok1981de said:
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
Click to expand...
Click to collapse
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
stecko said:
Can you guide me how to switch selinux to enforcing?
Click to expand...
Click to collapse
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260

andrew2432 said:
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
Click to expand...
Click to collapse
Very Nice .. this part have help ..
Code:
su;
setenforce 1;
https://prnt.sc/o9gchi
thank you!

[UPDATE/KEEP ROOT GUIDE] SEP 2020 (RP1A.200720.009) "CORAL" Magisk/Stock Boot Images

[UPDATE/KEEP ROOT GUIDE] SEP 2020 (RP1A.200720.009) "CORAL" Magisk/Stock Boot Images
**Huge thanks to @murphyjasonc for sharing the pre-patched boot image, and @sidhaarthm for testing this method and his detailed notes!**​
PLEASE READ ALL ADDITIONAL NOTES IN THE FIRST 3 POSTS. THIS IS A MAJOR UPDATE TO A NEW VERSION OF ANDROID AND CONSEQUENTLY COMES WITH A MUCH HIGHER RISK OF BOOTLOOPING IF YOU'RE NOT CAREFUL. I PERSONALLY AM WAITING TO UPDATE TO ANDROID R (WAITING ON GRAVITYBOX GOODNESS) SO I WON'T BE ABLE TO HELP AS MUCH - PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! =)
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.200720.009, Sep 2020, All carriers except IN"!
Magisk Canary v20424 (11f254e5) Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682933259
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682933258
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682933260
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.

READ THIS ENTIRE POST BEFORE PROCEEDING!
ADDITIONAL PRELIMINARY STEPS COMPARED TO PREVIOUS MONTHS - DO NOT SKIP!!!!:
A. Make sure all of your Magisk / EdXposed modules are updated for compatibility with R. For example:
* Magisk Module: Riru (Riru - Core) v21.3
* Magisk Module / EdXposed version: EdXposed v.0.5.0.6-android_r (4561) [this is a Canary build]
B. Recommend disabling any Magisk and/or Xposed modules that have not been tested with Android R.
C. Install latest Magisk Manager Canary build: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
D. Regular reboot the phone to make sure updates are applied before proceeding with the rest of the update process.
---------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200805.001, Aug 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq3a.200805.001-factory-dtbo.img: https://androidfilehost.com/?fid=8889791610682906527
coral-qq3a.200805.001-factory-boot.img: https://androidfilehost.com/?fid=8889791610682906525
September 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.200720.009-b447daff.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq3a.200805.001-factory-boot.img
3. fastboot flash dtbo coral-qq3a.200805.001-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rp1a.200720.009-b447daff.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rp1a.200720.009-magisk_patched-c20424.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
---------------------------​
ADDITIONAL NOTES FROM @sidhaarthm, WHO TESTED FOR ME - THERE'S SOME GOOD INFO HERE TO HELP PREP YOU BEFORE UPDATING YOUR PHONE:
Okay, so I just successfully completed the steps and I'm booted into Android 11 without issues.
Here are my observations, notes and findings:
Pre-requisites:
- I installed the Canary Build of Magisk apk - it basically overwrote the existing installation of Magisk and worked straight away. I remained on the 'stable' update channel.
- I uninstalled all the Accent and Colour Mods from Tulsadiver as he is yet to update the mods for R11 (although he's confirmed its' possible and will publish it soon).
- I also deleted the AK3 Helper module from Magisk that gets flashed with Kirisakura Kernel since I was about to to flash the stock kernel anyway.
- I left the GPay SQlite Fix, Systemless Hosts, Busybox, V4A and AML Modules in Magisk enabled and as is.
Upgrade Notes:
- Followed your instructions to the T and the upgrade process was a breeze.
- I did extract the boot file from the factory ROM and patched it in Canary Magisk myself on my P4XL, but I chickened out at the last minute and flashed the boot file you had provided anyway. Reason being the flashed boot IMG I generated was 33,292 KB vs the one you had provided (and the ones I saw posted in other threads) were all 33,332 KB. So there was definitely some differences there and I just didn't want to risk it at that point.
- The phone got a bit hot during the upgrade process - around 40C+ but I suppose that's alright. Its' cooled down now and running okay.
- I did not flash any Kernel yet since I am waiting for the next official Kirisakura Kernel release for R11.
Findings:
- My P4XL booted first time, no bootloops etc - finalised the upgrade in a couple of minutes and everything thereafter seems smooth as butter.
- GPay works perfect without any tinkering (that's a big plus!)
- Device is rooted and all Root apps (AdAway, TiB etc), all work as normal. Camera, WiFi, Bluetooth, everything works, no issues whatsoever.
- Face Unlock works as normal and so do all the apps that use the biometric API to unlock (banking apps etc).
- SafetyNet fails on ctsProfile (evalType Hardware) but it was the same before upgrading to R11, so not surprised.
- Viper FX doesn't work post upgrading to R11 - that's expected and people have already reported the same 'failed at patching system' error on the main thread. Hopefully we get an upgrade at some point. Really gutted about this one as I love V4A!
Click to expand...
Click to collapse
Big thanks to @sidhaarthm for being an awesome and detailed tester!

Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
* Looks like Tulsadiver uploaded a boot image for A11, although it hasn't been tested yet: https://forum.xda-developers.com/showpost.php?p=83462451&postcount=150
Coming from an earlier build than August 2020?
Download the September 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
Since this is a major jump to a new version of Android, I don't want to recommend this yet until someone tests it. If anybody tries this way successfully, please let me know so we can update this part. Thanks!

I just updated from Android 10 August (I use your method since, what, April now?) and everything worked without a problem. For security purposes I deactivated Edxposed beforehand, though. The first booting takes a while after the updating, maybe 3-4 minutes, don't be afraid to wait. I was. Lol.
Edit: Jea, Android4Viper is broken. Needs fix asap

Also a big thanks from me, all went well! A little reminder for people running lawnchair & quickswitch: disable both and set stock recent provider to pixel launcher! Both are not compatible yet... Almost had to factory reset because of this ?

An other big thanks from me, I used your guide again and everything is working.
I used Magisk from the Canary channel and installed MagiskHide Props Config.
Safetynet : Basicintegrity V, ctsProfile V and evalType BASIC., this is good.
When the Kirisakura Kernel is available I will install this kernel for Android 11.

when you install latest Magisk Manager Canary build, is this supposed to overwrite the current stable build or ad an additional separate magisk app?

has anyone installed riru and edxposed (if so what version you using) after root from a fresh update (Full wipe update, root, then install modules) any issues?
***EDIT (for dummies like me)*** can confirm works via fresh install too
-Just download / install riru core 21.3 via magisk.
-Download latest edXposed manager v4.5.7.
-Download v0.5.0.6 4561 from canary tab in edXposed manager.
-Flash that zip in magisk.
-Just make sure you don't flash and exposed directly from the download module list in magisk those are not the canary builds. You have to flash the zip from internal storage you just downloaded.

So I went with the fresh install and now the patches boot img returns a "partition not found" error.
I've tried powershell, cmd and same error. Does anyone have another command that could get me up and running? I re-root several times a year and never have this kind of problem.
Just to check that I'm using the correct command. - Fastboot flash boot patched boot img-
Would the patches image name make a difference?

bigmatt503 said:
So I went with the fresh install and now the patches boot img returns a "partition not found" error.
I've tried powershell, cmd and same error. Does anyone have another command that could get me up and running? I re-root several times a year and never have this kind of problem.
Just to check that I'm using the correct command. - Fastboot flash boot patched boot img-
Would the patches image name make a difference?
Click to expand...
Click to collapse
fastboot flash boot magisk_patched.img --slot all

Homeboy76 said:
fastboot flash boot magisk_patched.img --slot all
Click to expand...
Click to collapse
Thanks for the help. I got working by flashing "_a" after img

bigmatt503 said:
Thanks for the help. I got working by flashing "_a" after img
Click to expand...
Click to collapse
No problem, glad you found a solution to the problem. :good:

Ok, the first time I did this, it didn't change anything(after I finished I was still on Android 10, with the August update), so I may have did something wrong, I'm not sure. Anyway, I did it a second time, and voila, it works. Your guides are always the best bro!

Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks

Not able to boot after flashing the patched img says no valid slot to boot

bluedog220 said:
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Click to expand...
Click to collapse
Google Pay works - I utilised the GPay SQlite fix method (look it up, plenty of threads on it) but I actually had that before I upgraded to R11. Once I successfully upgraded using the steps provided in this thread, I didn't have to do a thing and GPay still works
As for banking apps, depends where you are. I'm in the UK and with Magisk Hide and some trickery, I've manged to get Monzo, Starling, Amex, HSBC and Tesco Banking apps to work on my Pixel 4 XL. The only ones I seem to struggle with (that have strong root detection) are Barclaycard and Lloyds Banking Group apps such as Halifax, MBNA etc.
Hope that helps :good:

bluedog220 said:
Any chance someone could say if Google Pay is working (and banking apps) with this method? Want to jump to 11 but everything works great on Aug 10 right now.
Thanks
Click to expand...
Click to collapse
I'm in the USA and G-pay works without doing anything. All of my banking /credit card apps work too

Has anyone had SafetyNet randomly stop passing for both basicIntegrity and ctsProfile together? When I first upgraded to 11 and set everything up, I was able to pass even with EdXposed installed, then it stopped passing with EdXposed a few days later, but would pass both with it disabled. Now it won't pass at all even with EdXposed disabled.
Anyone have any ideas before I resort to wiping and starting over?

has anybody with android 11 and magisk able to use smali patcher or app systemizer? i cannot get either to work yet

This guide worked perfectly for me, cheers.
Just need to wait for YouTube vanced

[GUIDE]Magisk, SuperSU and Xposed for MEmu 7.3.2 or LDPlayer 4.0.45

A new tool is available which can install Magisk in emulators. See Delta Magisk​
This tool is depreciated. No support will be provided.​
Magisk
Note:- This is a experimental feature. I made this guide only for SuperUser management in MEmu. If you want modules then don't expect it to work. Modules like MigiskHideProps are not working. So don't expect much.
As of now there is no working way for passing SafetyNet for playing games and apps that use it.​
For someone who want to install Magisk in emulators MEmu v7.3.2/LDPlayer v4.0.45 which is based on Android-x86, follow below guide.
What is this method?
-This method is used by exploits like mtk-su, qu1ckr00t without patching boot.img. I used this method because I don't know how to modify .vmdk as seen in here. Drawback of this method is that, many modules like MagiskHideProps are not working.
If you are using MEmu then follow https://forum.xda-developers.com/t/...-3-2-or-ldplayer-4-0-45.4222919/post-84574053
If you are using LDPlayer then follow https://forum.xda-developers.com/t/...-3-2-or-ldplayer-4-0-45.4222919/post-84580333
Reference:-
-https://forum.xda-developers.com/t/...diatek-armv8-2020-08-24.3922213/post-82081703
-https://github.com/grant-h/qu1ckr00t/blob/master/app/src/main/res/raw/magisk_install
Credits:-
@topjohnwu
@diplomatic
Enjoy!
SuperSU
If you want SuperSU instead of Magisk, then follow below guide
Enable Root mode
Download SuperSU zip from here
Download and install BusyBox from here
Download update-binary script from here. We can save this with CTRL + S if using browser in Windows OS
In Terminal Emulator run below commands
Code:
su
export PATH=/system/xbin:/system/bin
cd /sdcard/Download
sh update-binary 2 1 $PWD/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Restart MEmu. Enjoy!
Credits:-
@Chainfire
Xposed
I have modified youling257's xposed at Github. Since it is not flashable zip by default, we have to do it our own. Made it x86_64 flashable zip like x86 one. Nothing is changed. Just added x86_64 files to x86 system folder after deleting its contents, changed `arch` to x64 and signed.
We can also install Xposed in MEmu/LDPlayer Android 7.1.2(25) by below
Download last version of Xposed from
x86 => https://dl-xda.xposed.info/framework/sdk25/x86/xposed-v89-sdk25-x86.zip
(Tip:- 32bit users can directly install Xposed from Xposed Installer app without this manual flashing)
x86_64 => https://forum.xda-developers.com/attachments/xposed-v89-sdk25-x86_64-signed-zip.5197651/
copy it to /data/local/tmp
extract only META-INF/com/google/android/update-binary from the zip to /data/local/tmp
Run below commands in Terminal Emulator app with root.
Code:
su
cd /data/local/tmp
chmod 777 update-binary
if your arch is x86, then run below one
Code:
NO_UIPRINT=1 ./update-binary 2 1 xposed-v89-sdk25-x86.zip
rm update-binary xposed-v89-sdk25-x86.zip
if your arch is x86_64, then run below one
Code:
NO_UIPRINT=1 ./update-binary 2 1 xposed-v89-sdk25-x86_64-signed.zip
rm update-binary xposed-v89-sdk25-x86_64-signed.zip
Download Xposed apk from https://forum.xda-developers.com/attachments/xposedinstaller_3-1-5-apk.4393082/ and install it and restart.
Reference:-
XposedInstaller/app/src/main/java/de/robv/android/xposed/installer/installation/FlashDirectly.java at 8f8f2d7072d1f7b02f237e4ac864e767b7aa6e4c · rovo89/XposedInstaller
Contribute to rovo89/XposedInstaller development by creating an account on GitHub.
github.com
Credits:-
@rovo89
@youling257
@Camlin3 for initial thread.
Enjoy!

Deprecated Guide
Spoiler
Start MEmu/LDPlayer and enable Root mode in Settings
Download and install latest Magisk Manager from here
Download Magisk.zip from here and take magiskinit file from it according to your architecture and place it like /sdcard/init.d/bin/magiskinit.
Download the script from here. We can save this code with CTRL + S in Browser in Windows OS.
Install Terminal Emulator app and run below code in it
Code:
su
sh /sdcard/Download/magisk-boot.sh
Now, you have successfully installed Magisk.
You have to execute the script on every boot. We can use 'Termux:Boot' or 'init.d scripts support'(don't forget to turn off battery optimization for the app)

please, would it be possible for you to record a step by step video?

rickkarpov said:
please, would it be possible for you to record a step by step video?
Click to expand...
Click to collapse
I can't do that, because of my Internet issues to upload. You can message at Telegram with username 'HemanthJabalpuri', so that I can guide you.
Thanks

after running script, it says magiskinit not found. I followed all steps, please help.

Anubhav001 said:
after running script, it says magiskinit not found. I followed all steps, please help.
Click to expand...
Click to collapse
Ok, tell me if /storage/emulated/0 is there or not.
If it is there, then make sure that magiskinit in placed in /storage/emulated/0/init.d/bin
Thanks

Nice guide.
Thank you very much

This is cool magisk was installed and everything was fine... I expected it to be
But the Modules are the issue, can't make them to work..... any help??
I have installed the magisk hide module and its shown activated but can't bypass safteynet, is that because of the superuser within the emulator?

rushi12565 said:
This is cool magisk was installed and everything was fine... I expected it to be
But the Modules are the issue, can't make them to work..... any help??
I have installed the magisk hide module and its shown activated but can't bypass safteynet, is that because of the superuser within the emulator?
Click to expand...
Click to collapse
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks

HemanthJabalpuri said:
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks
Click to expand...
Click to collapse
I'm using HiddenCore-module with Android 6.0, Android 7.0, Android 8.1, Android 9.0 and Android 10.0.
It is working perfectly on all them.
MagiskHideProps has a FANTASTIC intention, but a poor execution.
It has conflicts inside itself.
Unhappy, I can't suggest it to anybody.
Certainly, HiddenCore-Module will work for you.
HiddenCore Module | Xposed Module Repository
repo.xposed.info

HemanthJabalpuri said:
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks
Click to expand...
Click to collapse
Oh ok.
abt the exposed doesn't it just show that safetynet is passed and not actually fix the safetynet right?

rushi12565 said:
Oh ok.
abt the exposed doesn't it just show that safetynet is passed and not actually fix the safetynet right?
Click to expand...
Click to collapse
If the app see that safetynet is passed, what does matter if it is fixed or not?
If you've rooted your device, your safetynet will be broken forever, until you unroot it.
That's simple.
Just fake it and everything will works perfectly.

Umm i'll try then

rushi12565 said:
Umm ill's try then
Click to expand...
Click to collapse
Don't forget to share result after trying.

Yea so i was trying to see if by passing saftey net on emulator I could play pokemon go on it (was just curious) and i failed xposed doesn't help. it's shown that safetynet is passed but it isn't i guesss.

rushi12565 said:
Yea so i was trying to see if by passing saftey net on emulator I could play pokemon go on it (was just curious) and i failed xposed doesn't help. it's shown that safetynet is passed but it isn't i guesss.
Click to expand...
Click to collapse
Did you try to check safetynet on magisk app?
Can you try on others app too?
Are you sure xposed is properly working?
Are you sure hiddencore is activated in modules tab?
Try checking logs too

VD171 said:
Did you try to check safetynet on magisk app?
Can you try on others app too?
Are you sure xposed is properly working?
Are you sure hiddencore is activated in modules tab?
Try checking logs too
Click to expand...
Click to collapse
Yea i've checked that hidden core is activated in the modules tab
The safteynet test in magisk is passed but it couldn't pass the test from a normal safteynet test app
this one https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en_IN&gl=US

rushi12565 said:
Yea i've checked that hidden core is activated in the modules tab
The safteynet test in magisk is passed but it couldn't pass the test from a normal safteynet test app
this one https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en_IN&gl=US
Click to expand...
Click to collapse
Did you rename magisk app?
Did you enable magisk hide?
Did you select the desired app for hiding by magisk hide?
There are many steps for hiding root, magisk, xposed or anything on android.
You need to try everything you can.

VD171 said:
Did you rename magisk app?
Did you enable magisk hide?
Did you select the desired app for hiding by magisk hide?
There are many steps for hiding root, magisk, xposed or anything on android.
You need to try everything you can.
Click to expand...
Click to collapse
Hided magisk
Enabled magisk hide when I tried to hit the reboot the emulator just struck so I had to close and restart the emulator itself and when I checked the modules in magisk the magisk hide props was toggled(was shown working)
The thing is when I did this the safety net was not passed, xposed hidden core module was not activated. so now I will try and see if activating both hidden core module and magisk hide will help or not

Yea I have tried it and the results are the same
Safety net is shown passed in magisk but in the actual test it fails
Xposed and magisk modules are activated
(logs in the next msg)

How To Guide [Magisk Universal] How2RW Your /System [One UI or Non-One UI]

Flash this module in magisk and reboot.
Credits:
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com

got me bootlooping, but magisk disabled the module by itself

claudiuo said:
got me bootlooping, but magisk disabled the module by itself
Click to expand...
Click to collapse
what kernel? and what other magisk modules you got?

TringQuack said:
what kernel? and what other magisk modules you got?
Click to expand...
Click to collapse
stock

claudiuo said:
stock
Click to expand...
Click to collapse
lol

got the anykernel kernel. now it works!