Develop Bugs

Gpay OTP issue.

Hello,
I am using miui 11 indian stable rom, after i rooted my phone via LRtwrp when i want to login in my Gpay account the app is unable to send OTP.
I have checked all possible things , magisk hide, securitynet check is true, also gave all permission to gpay.
When i click send OTP the timer doesn't move on, attaching a clip of it. Please reply with working solution.

You can follow up this process , this might help:
SafetyNet Cts False Fix ?
Method 1
.................
1.) Install Riru - core from the Magisk downloads then reboot.
2.) Install Riru - EdXposed (Yahfa) from the Magisk downloads then reboot.
3.) Install EdXposedManagerv4.5.7.apk.
Download EdXposedManagerv4.5.7 : https://t.me/RedmiNote8ProOfficial/294276
Once installed, you should see EdXposed Framework is active after opening the app.
4.) Close the app then install HiddenCoreModule.apk
Download HiddenCoreModule :https://t.me/RedmiNote8ProOfficial/294277
5.) Open EdXposed manager. Then, from menu, select modules, activate hidden core module
6.) Reboot device
7.) Confirm from Magisk that ctsProfile is true and SafetyNet is passed.
Method 2
.................
1.)Install Busybox and MagiskHideProps from Magisk Download page
2.)Install terminal app from PlayStore and reboot
3.)Terminal app example: https://play.google.com/store/apps/details?id=jackpal.androidterm
4.)Open terminal and type as follows:
su
props
1
f
Seek for your OEM(Redmi) and type it's number.
Seek for your device(Redmi note 8pro) and type it's number.
if asked choose number of Android version you want to use
y
5.)reboot and enjoy
y (to reboot)
Still CTS profile false or have issues read this by our Magisk Dev
https://twitter.com/topjohnwu/status/1245956080779198464?s=19

Psambitk1 said:
You can follow up this process , this might help:
SafetyNet Cts False Fix
Method 1
.................
1.) Install Riru - core from the Magisk downloads then reboot.
2.) Install Riru - EdXposed (Yahfa) from the Magisk downloads then reboot.
3.) Install EdXposedManagerv4.5.7.apk.
Download EdXposedManagerv4.5.7 : https://t.me/RedmiNote8ProOfficial/294276
Once installed, you should see EdXposed Framework is active after opening the app.
4.) Close the app then install HiddenCoreModule.apk
Download HiddenCoreModule :https://t.me/RedmiNote8ProOfficial/294277
5.) Open EdXposed manager. Then, from menu, select modules, activate hidden core module
6.) Reboot device
7.) Confirm from Magisk that ctsProfile is true and SafetyNet is passed.
Method 2
.................
1.)Install Busybox and MagiskHideProps from Magisk Download page
2.)Install terminal app from PlayStore and reboot
3.)Terminal app example: https://play.google.com/store/apps/details?id=jackpal.androidterm
4.)Open terminal and type as follows:
su
props
1
f
Seek for your OEM(Redmi) and type it's number.
Seek for your device(Redmi note 8pro) and type it's number.
if asked choose number of Android version you want to use
y
5.)reboot and enjoy
y (to reboot)
Still CTS profile false or have issues read this by our Magisk Dev
https://twitter.com/topjohnwu/status/1245956080779198464?s=19
Click to expand...
Click to collapse
I already mentioned that safetynet is true.

[Tutorial][How to] SafetyNet with root

My device: SM-M315F (M31), Android 11, OneUI3,1
SafetyNet can detect if you have rooted your device. If you don't pass the SafetyNet check, some secure apps (e.g. Google Pay) wont work!
Here's how I got around it (starting from stock):
Install TWRP and flash Magisk (root): https://forum.xda-developers.com/t/recovery-unofficial-3-5-2-twrp-for-galaxy-m31.4260181/
Make changes with Magisk to bypass SafetyNet: https://www.droidwin.com/pass-magisk-safetynet-android-11-root/
Make sure to also do Step #5 in the second link! Without that, my device failed the ctsProfile test.

M315FXXU2ATIC (Android 10) Magisk v23 stable. Google Pay.
Enabled Magisk hide, then installed modules - Riru v26.1.3 (from repo), LSPosed v1.6.5 (from repo), Universal SafetyNet Fix v2.1.2 (Riru version), then reboot. Now Google Pay accepted the card but still reported the device was not compliant. Clearing data (not cache) of Google Pay and Google Services helped.
PS: updated to M315FXXU2BUAD (Android 11) via ODIN and HOME_CSC, flashed Magisk again - all modules remained - Google Pay works.

Question magiskhide props config bootloop

Hi, i've messed up my device! I've rooted my f3 (enhanced 12.5.7.0 GLOBAL) with magisk and attempted to get google call screening working by changing props using magiskhide props config module. I've set my device fingerprint to pixel 5 and set the device emulation/simulation options by following another thread (admittedly a oneplus thread).
How can I get Google dialer's call screening?
Has anyone been able to get Google's call screening to work? I've seen some guides for older OnePlus devices, I was wondering how it would work for the 9.
forum.xda-developers.com
Now i'm stuck in a bootloop, however if i flash the stock boot.img i can boot into the OS and my phone works as normal but obviously without magisk and root.
Now if i uninstall magisk app then try to reflash the magisk patched boot.img to try to get root i get bootloops again. Is there a way i can revert the fingerprint/emulation settings somehow without root or access to magisk or edit props without root? When i flash the standard boot.img does this reset the fingerprint and device emulation setting but when i reflash magisk pathed boot.img this reactivates the props changes i made with magisk?
Can someone help!

I have attempted to boot into safe mode using the recovery menu, which should disable all magisk modules?, but no joy. The phone booted into safe mode for about 10 seconds then shut off and went back into recovery mode/meu.
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
As per the documentation it says i can create a "disable_mhpc" file and place it on the device but i don't have root and i also don't have /data/cache in the root folder only /android/data/cache. Also what file type is this? an empty .txt file or does it need to have commands within it?
MagiskHidePropsConf/README.md 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

How To Guide How to root and pass SafetyNet on XQ-BT52 62.0.A.3.163

How to root and pass SafetyNet on Sony Xperia 10 III (XQ-BT52)​Tested on firmware 62.0.A.3.163.
Disclaimer:
This guide assumes you're familiar with the concepts of rooting, Magisk, SafetyNet, fastboot, adb and so on. I will explain why things are done but if I explained everything it would become too long.
This guide is limited to getting root and apps working on the stock Sony ROM. It doesn't cover installing other ROMs.
You can mess up your phone if you don't know what you're doing. This is not a beginner's guide.
Before you do anything else, do these preparations:
Make sure your device is updated to the latest firmware. Getting updates after you unlock the bootloader will be more complicated.
Use XperiFirm to grab a copy of your current firmware (after you've updated it). It can run on Linux too, either via Mono or in a virtual machine. It's basically just a downloader, it doesn't need any fancy hardware access.
Screenshot everything under Settings > System.
Open the dialer and enter *#*#7378423#*#*. Screenshot everything in the service submenus.
Unlock developer options (tap Settings > About > Build number 7 times) then find it under Settings > System > Advanced. Activate USB debugging. Activate OEM unlocking.
Install the Android SDK Platform Tools. On Linux they're most likely in a package provided by your distro.
Copy the screenshots to your PC because the phone will be reset at some point.
Boot into fastboot by turning the phone off, then connect it to PC via USB, and press POWER and VOLUME UP together. The phone led will turn blue. On PC run fastboot devices and make sure it lists your phone and has the serial number you got from the service menu.
Unlocking the bootloader:
This is the point of no return as far as warranty is concerned!
This will factory reset the phone! Make sure you got everything you needed off it.
Obtain the unlock code (you will need the IMEI of the 1st SIM slot).
Boot into fastboot, check again that fastboot devices lists the phone.
Issue the unlock command using the code you got earlier: fastboot oem unlock 0x<unlock code here>
Reboot the phone (you can say fastboot reboot). It will say "can't check for corruption" and "erasing" a couple of times but will eventually boot up to the factory setup.
Enabling Magisk & root:
Download the latest Magisk apk to the phone and install it. Right now that means v24+.
Open boot_X-FLASH-ALL-8A63.sin from the original firmware with any archive manager (it's a tar.xz), 7zip will work fine.
Extract boot.000, rename it to boot.img and put it on the phone.
Open the Magisk app, next to "Magisk" tap "install", choose "Select and patch a file", pick the "boot.img" file.
Download the patched img to PC (will be next to boot.img called something like magisk_patched-24100_MKPRJ.img).
Boot into fastboot, check again that fastboot devices lists the phone.
Flash the patched boot image: fastboot flash boot magisk_patched-24100_MKPRJ.img
Must say OKAY. Can then reboot the phone (you can say fastboot reboot).
Open the Magisk app again, it should say "installed" now next to "Magisk". Also the Superuser and Modules buttons should now be enabled.
Go into Magisk settings and activate "Hide the Magisk app". This is NOT MagiskHide, it does not hide Magisk from other apps, it hides the Magisk Manager app from other apps. More on this later.
Go into Magisk settings and activate Zygisk. This is a built-in replacement for Riru going forward.
Reboot!
Install a root checker app and verify that you get a prompt from Magisk to give root and that the checker says it got root.
Important changes about Magisk:
Riru is now obsolete. It has been replaced by a feature built-into Magisk called Zygisk (which is essentially Riru running in Zygote). It is strongly recommended to go into Magisk settings and activate Zygisk (even if you don't use Riru modules). Do not install Riru anymore. All modules that needed Riru should have Zygisk versions by now unless they're abandoned.
Magisk no longer maintains a module repository, To find and install modules install Fox's Magisk Module Manager. It's a dedicated module management app that supports the old Magisk repo as well as new ones. Inside Magisk you can still enable/disable/remove/install manually and can also update if the module has an update URL, so you can do without Fox if you get your modules directly from their XDA or GitHub pages.
MagiskHide has been replaced by a new feature called Deny list (it's in Magisk settings). It's much more powerful because the apps & processes added to the deny list will be completely excluded from anything based on Magisk so it's impossible for them to detect leaks anymore. On the downside, excluded apps can't be affected by any Magisk or LSPosed modules (LSPosed will grey out such apps and say "it's on the deny list".) This feature should be used sparingly (see below) because Magisk still does a good job of evading detection.
Passing SafetyNet:
Install YASNAC to check your SafetyNet status. At this point you're probably not passing either Basic or CTS check.
Go into Magisk settings. Enable "Enforce deny list". Enter "Configure deny list", find Google Services, check it, expand it, and select only the process ending in .gms and the one ending in .gms.unstable.
Reboot. Check YASNAC. At this point you should be passing Basic check but probably not CTS.
Install Universal SafetyNet Fix (aka USNF) by kdrag0n in Magisk. (Some GIS ROMs already include what this module does, so if you install a GIS ROM you may not need it.) This module hijacks the CTS verification and drops an error which causes the Google service to fall back to Basic verification, which we already fixed in the previous step.
Reboot. Check YASNAC. At this point you should be passing both Basic and CTS. That's it!
You may need to clear storage & cache for Google Play & Services. Go to Settings > Apps & notifications > See all apps, select "All apps", find them in the list, clear storage/cache and reboot. After that try searching for a restricted app such as Netflix on the Play store, if it shows up in results you're all good.
Remember to also add to deny list other apps that try to detect if you're using root, like banking apps.
Other SafetyNet related fixes:
People using non-stock GIS ROMs will probably need module MagiskHide Props Config by Didgeridoohan. This will install a props command line util that you can use (as root) to force Basic attestation, apply extra Magisk hiding techniques, spoof device fingerprint, change the way fingerprinting is checked, or even impersonate another device altogether. Install, reboot, enter adb shell, type su to go root (will need to grant root to shell on the phone when prompted), then run props and follow the options.
People running extra-stubborn banking apps (or other apps that try to detect root extra-hard) that don't work even when added to the Magisk deny list can try module Shamiko by LSPosed. This module adds extra hiding techniques for the apps on the deny list. Please note that Shamiko will disable the Magisk "enforce deny list" option but that's ok, that's an extra feature, the deny list is in effect even without it.

Working apps and modules​Please note that this list is limited to stuff that I personally use. I can't and won't install other stuff to test it.
Root apps:
AFWall(+): Works, but configure it to use its own internal busybox and iptables. Applying rules fails occasionally and you need to retry.
Call Recorder by skvalex: Recording works out of the box, no fiddling required with either headset of mic recording.
JuiceSSH, Termux etc. and other terminal apps: No issues getting root with su.
Busybox: you can install zgfg's module which exposes Magisk's internal Busybox to the rest of the system (bonus: will be updated with Magisk); or you can install osm0sys's module which contains a standalone separate Busybox. As of now both of them provide Busybox 1.34.
MyBackup Pro: Works fine. Used it to transfer 15k+ SMS messages from Android 8.
Solid Explorer: Can access root partitions without issues.
Tasker: No issues.
Titanium Backup: Works but will hang when restoring APKs whose target API doesn't support the ROM's Android version (ie. APKs you can't install directly either).
OAndBackupX: Modern alternative to Titanium, works perfectly.
XPERI+: Version 6 works well and allows you to remap the assistant button and has another couple of features. Version 7 crashes.
Magisk modules:
AFWall Boot AntiLeak
Backup
Builtin BusyBox
Magisk Bootloop Protector
MagiskHide Props Config
Shamiko
SQLite for ARM aarch64 devices
Systemless Hosts (comes with Magisk, enable it in settings)
Universal SafetyNet Fix
Zygisk LSPosed
LSPosed modules:
App Settings Reborn: Works well. May require a couple of reboots before the targeted apps start showing the modifications.
Disable Flag Secure: com.varuns2002 is working, sort of. Please read the module's page. Apps got wise to rooted devices ignoring FLAG_SECURE so now they use hardware DRM or detect screenshots and show you something else (Netflix). So it works only in older versions of apps, or apps that haven't bothered to detect screenshots.
GravityBox [R]: Everything I tried works perfectly.
Physical Button Master Control: The module works as intended, the companion config app has some issues, hopefully they'll be solved soon.
XPrivacyLua: Works perfectly. No issues with SafetyNet.
Not working:
...

Other tested and working Root Apps:
AdAway
Fox's Magisk Module Manager
Franco Kernel Manager
Termux
Not testet yet:
Call Recorder
FolderSync
Total Commander
Vanced Manager
WireGuard
Other tested and working Magisk modules:
1Controller - 1 Module to support all Controllers
Call Recorder - SKVALEX
F-Droid Privileged Extension
Move Certificates (version by Androidacy)
Other tested and working LSPosed modules:
BubbleUPnP AudioCast

Question How to convert asus rog phone 6 pro chinese version to global rom?

how to convert asus rog phone 6 pro chinese version to global rom?

root the phone then flash it, but i dont think there is anyway to root it

concorduser said:
root the phone then flash it, but i dont think there is anyway to root it
Click to expand...
Click to collapse
until now still dont have 1 proper guide to root for 6 pro

I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.

tuannghia1985 said:
I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.
Click to expand...
Click to collapse
thanks