Database Users

Trying to root NBD91K sends the phone into a bootloop

I am running NBD91K build, but every time I flash supersu, it sends my phone into a bootloop. I am running the latest TWRP and tried SuperSu 2.78 SR5. Anyone having the same problem?

dewhashish said:
I am running NBD91K build, but every time I flash supersu, it sends my phone into a bootloop. I am running the latest TWRP and tried SuperSu 2.78 SR5. Anyone having the same problem?
Click to expand...
Click to collapse
Are you using suhide by any chance?

I've been stuck at bootloop when i tried to force system (not systemless) root on nougat. So my first thought was to delete /data/.supersu... then I've managed to reinstall root systemlessly, but after a few tries it stayed on the bootloop.... I had to reflash system.img and then I flashed the supersu once again and it works like magic.

Yes, I am using suhide

dewhashish said:
Yes, I am using suhide
Click to expand...
Click to collapse
Suhide does not work with 7.0+ roms with the November security patch. You need to flash the suhide Uninstaller and just use supersu

You're right, unintalling suhide and I can boot my phone after rooting, thanks. Too bad suhide doesn't work with the november patch, otherwise I can't get android pay working.

dewhashish said:
You're right, unintalling suhide and I can boot my phone after rooting, thanks. Too bad suhide doesn't work with the november patch, otherwise I can't get android pay working.
Click to expand...
Click to collapse
did you try Magisk v9 + phh Superuser?
Android Pay works like a charm for me on 7.1.1 DP2

blank

boqonx said:
did you try Magisk v9 + phh Superuser?
Android Pay works like a charm for me on 7.1.1 DP2
Click to expand...
Click to collapse
I installed magisk manager and phh superuser, how do I get Android Pay to work with it? do I need a custom kernel?

dewhashish said:
I installed magisk manager and phh superuser, how do I get Android Pay to work with it? do I need a custom kernel?
Click to expand...
Click to collapse
Ensure that you have uninstalled SuperSU prior to flashing Magisk v9 and phh Superuser.
After, install Magisk Manager apk posted on its thread and phh Superuser manager & SafetyNet Helper from playstore.
You can then hide Magisk from SafetyNet within Magisk Manager setting. Run SafetyNet Helper to test whether you pass the SafetyNet check or not. If everything is passed, then you should be able to use Android Pay & Pokemon Go .

boqonx said:
Ensure that you have uninstalled SuperSU prior to flashing Magisk v9 and phh Superuser.
After, install Magisk Manager apk posted on its thread and phh Superuser manager & SafetyNet Helper from playstore.
You can then hide Magisk from SafetyNet within Magisk Manager setting. Run SafetyNet Helper to test whether you pass the SafetyNet check or not. If everything is passed, then you should be able to use Android Pay & Pokemon Go .
Click to expand...
Click to collapse
that worked! thank you so much for your help!

Magisk v11.6/Systemless Root works for our Moto X

Tested on a clean install of CypherOS. It installs and passes SafetyNet without doing anything complicated. Assuming it should work on any rom without root built in like Lineage OS.
Grab it here and thank @topjohnwu. Remember to enable Magisk Hide in settings or it will not pass SafetyNET.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

I tried this on an existing install but no luck.
On the new install did you have to flash the remove root zip from Lineage, or just ROM GAPPS and Magisk zips?
Thanks.

rsocon said:
I tried this on an existing install but no luck.
On the new install did you have to flash the remove root zip from Lineage, or just ROM GAPPS and Magisk zips?
Thanks.
Click to expand...
Click to collapse
On a clean install I just flashed rom, gapps, and magisk in that order.
BTW over night Magisk lost root, a reboot and root was back though. Might be bug, might be a one time thing, I don't know.

After trying everything listed still no luck getting this to work.
Guess no Android Pay for me

I tried to install on stock ROM, it seem it dosn't work, i'll try with a custom ROM

i'm running this just fine with just the core AND the latest version of magisk. safetynet check passes too on cypherOS.

Bluetooth not Working at all.

Hi, im using a T-Mobile converted to the International and now with the OOS 10.3.0 and the Bluetooth is not working, since im new in here let me know what information about my phone should i add in here.
OOS - 10.3.0
Compilation Number - ONEPLUSA6013_34_191214
I have installed 3Magisk Modules.- Looki75 Product Sans Font, OPFPControl Module and YouTube Vanced - Magisk Repo

Try to uninstall magisk using magisk uninstaller through TWRP

sukhi376 said:
Try to uninstall magisk using magisk uninstaller through TWRP
Click to expand...
Click to collapse
Can that be a problem?

cts profile fail

i went from stock everything, oem unlock, fastboot install of twrp fajita, flash stock rom downloaded from oneplus, then magisk
then i was having an issue with magisk , viper audio wasnt working properly
restarted to recovery, meant to wipe dalvik but pressed something else and borked the phone.
wiped everything, re installed the twrp recovery, re flashed zip. re flashed magisk again
now, i have to turn on magisk hide ( to pass cts profile ), which is something i never had to do before and i cant find netflix on the play store.
what can i do to correct the cts profile fail please.

Use this module: Magisk Hide Props Config
It requires: BusyBox, installer in this thread first post.
To activate the module and chose your new certified fingerprint you will need a terminal emulator, you can use any one you want really, personally I use this one.
Any questions ask.

Hi
I tried this, everything went through smoothly enough but it did not resolve the issue. To be clear this is what i did.
downloaded the magiskhide props module, installed through magisk
downloaded the busybox installer , installed through magisk
restarted
opened terminal, ran command 'props'
went through the process or redoing the files for the fingerprint reader according to make and model of my phone.
restarted
disabled magiskhide in magisk
restarted
still failing cts
did i miss something
it also mentioned that i am using a custom rom, i am using a stock rom downloaded from oneplus. i have unlocked the bootloader and am rooted using magisk .
do i need to re download and start again?
OhioYJ said:
Use this module: Magisk Hide Props Config
It requires: BusyBox, installer in this thread first post.
To activate the module and chose your new certified fingerprint you will need a terminal emulator, you can use any one you want really, personally I use this one.
Any questions ask.
Click to expand...
Click to collapse

leonzon said:
disabled magiskhide in magisk
Click to expand...
Click to collapse
Why are you disabling this? You need Magisk hide enabled. I rename Magisk as well. My phone passes safetynet and CTS. On the latest version of Magisk MagiskHide is off by default, it used to be on by default. TopJohnWu announced that a while back here.

OhioYJ said:
Why are you disabling this? You need Magisk hide enabled. I rename Magisk as well. My phone passes safetynet and CTS. On the latest version of Magisk MagiskHide is off by default, it used to be on by default. TopJohnWu announced that a while back here.
Click to expand...
Click to collapse
ok , so maybe thats all this is? damn, im sorry for wasting your time. What do you mean by you rename magisk, in the app drawer? the process?
thanks

leonzon said:
ok , so maybe thats all this is? damn, im sorry for wasting your time. What do you mean by you rename magisk, in the app drawer? the process?
thanks
Click to expand...
Click to collapse
In recent versions when you choose hide and it picks a random name for the Magisk Manager app it lets choose a name for the app instead of just Manager.

[GUIDE] Update and root RealmeUI 2.0 with Safetynet-fix (RUI 2.0 | Android 11) [Global/Indian]

[GUIDE] HOW TO UPDATE TO RUI 2.0 AND ROOT IT​
--> Disclaimer: I'm not responsible if you brick your device. Use at your own risk and always backup your data! <--
0. Download links​F.14 OTA: Download
Magisk app: Download
OrangeFox beta: Download
ADB/Fastboot tool: Download
Patched boot.img: Find attached
vbmeta.img: Find attached
Patched safetynet fix: Find attached
1. Update your device​Update your device to the latest firmware version (F.14). Therefor flash the provided OTA zip via stock recovery or OrangeFox beta recovery.
It is recommended to use the stock recovery. You can also update your device to the latest firmware by using the build in update function.
2. Root your device​Boot into fastboot mode. To boot into fastboot mode, shut down your device and then press the volume down button while clicking on the power button.
Now you have successfully booted into fastboot mode. Connect your device with your computer and flash the patched boot.img and also disable verified boot.
Therefor just type following 3 commands:
1. fastboot flash boot patched_boot.img
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot reboot
Your device should boot up. Now install the Magisk app and you have successfully rooted RUI 2.0.
3. Fix Safetynet​Install the patched "safetynet-fix-v.2.2.0-zip" module via Magisk. It will fix safetynet (Basic integrity and CTS). It works perfectly and won't brick your fingerprint etc. Thanks to @osm0sis
4. Get Widevine L1​If you have unlocked your bootlader, Widevine will be set from L1 to L3. This will reduce the quality of certain streaming apps like Netflix from FullHD to SD quality.
However, you can get Widevine L1 back by contacting the Realme support. For more info, check the guide from @hack-os: Widevine L1 FIX

Reserved

DarkImperator said:
3. Fix Basic integrity check (Safetynet)​Unfortunately, it is not possible to pass safetynet with rooted RUI 2.0. However, you can still pass basic integrity, which should be fine for most banking apps.
To do so, open the Magisk Manger app and click on the settings button on the top-right corner. Enable "Zygisk" and "Denylist". Then click on "Configure DenyList".
Click on the 3-dots on the top-right corner and select system-apps. Now search for "gms". You should find "Google Play Services". Click it and enable "com.google.android.gms" and "com.google.android.gms.unsuable". Now reboot your device and it should pass basic integrity.
Click to expand...
Click to collapse
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.

Eng.Raman said:
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.
Click to expand...
Click to collapse
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?

DarkImperator said:
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?
Click to expand...
Click to collapse
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.

Eng.Raman said:
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.
Click to expand...
Click to collapse
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.

DarkImperator said:
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.
Click to expand...
Click to collapse
What is your Momo app and magisk Detector results? Can you screenshot ?

Eng.Raman said:
What is your Momo app and magisk Detector results? Can you screenshot ?
Click to expand...
Click to collapse
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.

DarkImperator said:
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.
Click to expand...
Click to collapse
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.

Eng.Raman said:
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.
Click to expand...
Click to collapse
EDIT: @Eng.Raman had to install MomoHider and add config "app_zygote_magic". Now Momo gives me the message.

DarkImperator said:
Installed MomoHider, but it still said "The environment is broken". So I disabled MagiskHide. Only as MagiskHide was disabled, I received a message from Momo. Screenshot attached.
Click to expand...
Click to collapse
That's weird you can't even hide magisk and su file.

Eng.Raman said:
That's weird you can't even hide magisk and su file.
Click to expand...
Click to collapse
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.

DarkImperator said:
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.
Click to expand...
Click to collapse
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.

Eng.Raman said:
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.
Click to expand...
Click to collapse
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.

DarkImperator said:
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.
Click to expand...
Click to collapse
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.

Eng.Raman said:
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.
Click to expand...
Click to collapse
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060

DarkImperator said:
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060
Click to expand...
Click to collapse
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.

Eng.Raman said:
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.
Click to expand...
Click to collapse
With enabled Magisk Hide it will fix basic integrity check, but not CTS. And it also bricks my in-display-fingerprint. Guess I'll stay with Magisk Canary, till there might be an update to fix those issues.

Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.

jalal.sy said:
Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.
Click to expand...
Click to collapse
I have the same issue with my banking app that doesn't allow NFC payments even though I've done everything to hide root.