Hi, I have a problem with my OnePlus 2. My phone is running Lineage OS 14.1 and I can't play Pokemon go. My phone has been rooted but I uninstalled it so Pokemon should work right? I also did a safetynet check and I didn't pass it. I hope anyone here can help me with this.
michiel.dj said:
Hi, I have a problem with my OnePlus 2. My phone is running Lineage OS 14.1 and I can't play Pokemon go. My phone has been rooted but I uninstalled it so Pokemon should work right? I also did a safetynet check and I didn't pass it. I hope anyone here can help me with this.
Click to expand...
Click to collapse
You need a factory reset, probably.
NLBeev said:
You need a factory reset, probably.
Click to expand...
Click to collapse
Thanks I'll try it
Apart from root, there are also other things that trigger SafetyNet. Most common suspects:
Bootloader needs to be locked or you'll need something that masks/doesn't report the bootloader state. Some custom kernels do this.
SELinux need to be enforcing.
Thanks, is it possible to lock the bootloader again?
michiel.dj said:
Thanks, is it possible to lock the bootloader again?
Click to expand...
Click to collapse
The OnePlus Two does not report bootloader lock status to SafetyNet so it does not matter if it is unlocked.
I would try reflashing the rom and making sure it is not rooted. If you want root you will want to flash Magisk via TWRP.
driverdis said:
The OnePlus Two does not report bootloader lock status to SafetyNet so it does not matter if it is unlocked.
I would try reflashing the rom and making sure it is not rooted. If you want root you will want to flash Magisk via TWRP.
Click to expand...
Click to collapse
Thank you, I will try to reflash it and see if it is working. I'm sure my phone is not rooted anymore, I have uninstalled the root in the SuperSU app.
michiel.dj said:
Thank you, I will try to reflash it and see if it is working. I'm sure my phone is not rooted anymore, I have uninstalled the root in the SuperSU app.
Click to expand...
Click to collapse
I reflashed the ROM and everthing is working fine now. But my camera is a little laggy. But that is not something to talk about in this thread. Thank you guys for helping me with my problem
Related
Hi, All!
Are there any custom ROMs that have Android Pay working? I don't necessarily need root access; however, wouldn't mind having it with ability to turn it off.
Thanks!
PashaF said:
Hi, All!
Are there any custom ROMs that have Android Pay working? I don't necessarily need root access; however, wouldn't mind having it with ability to turn it off.
Thanks!
Click to expand...
Click to collapse
Lineage OS works fine. Rooted with magisk so I pass safetynet.
I was flashing the official Lineage OS with Magisk v11.1 . i was install the MagiskManager and the phh superuser also. However if i check my device status on MagiskManager the SafetyNet does not pass. It just looping and looping... Iam having MultiROM and my Internal ROM is OOS4.0.2 and Magisk works well, it giving SafetyNet pass.
So why does not work with official LineageOS??
Also was trying different LOS ROMs not just the official but none of them working.
Maybe you need to remove the unlocked bootloader notification before the phone boots.
Someone i read a post and this solved his prob.
Maybe try that. The process to do that in guides section
Navi44 said:
Maybe you need to remove the unlocked bootloader notification before the phone boots.
Someone i read a post and this solved his prob.
Maybe try that. The process to do that in guides section
Click to expand...
Click to collapse
Thanks.
However i was checking the guide section but have not find the tutorial about removing the unlocked bootloader notification. Only the dm-verity notification removal i have found what i have got already.
A link would be appreciated :good::victory:
Hi guys how I pass the safetynet?
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
tyler19820201 said:
Thanks.
However i was checking the guide section but have not find the tutorial about removing the unlocked bootloader notification. Only the dm-verity notification removal i have found what i have got already.
A link would be appreciated :good::victory:
Click to expand...
Click to collapse
UPDATE
I have solved the issue. I am using multiROM and have realized ONLY the Internal ROM getting the safetynet pass!! So i was swap my internal OOS4.0.2 ROM with the Lineage OS. And now the Lineage is the internalROM and the oxygen is the secondary. The Lineage getting safetynet pass but the oxygen does not. Before swapping Oxygen having pass but Lineage does not...
Hope will help this who want to set it up in the future.
Hi,
I'm running stock ROM with TWRP recovery.
I've managed to successfully root my Note with Magisk.
Somehow I noticed that my device loses root after a reboot and sometimes even randomly. When I go into the custom recovery and flash Magisk 14 or 14.3 everything works fine for while, till it loses root again.
Could someone shed some light on my issue, please?
Thanks in advance.
I've also themed Magisk Manager with Substratum could that be the issue?
I'm also running stock rom, losing magisk root from time to time.
When root is lost, I'm getting a notification that "new magisk V14 is available.
Reinstalling with TWRP only to lose it again a day or two later.
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Are you using the hide root feature?
If so then that is probably your issue.
opasha said:
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Click to expand...
Click to collapse
This worked for me, thank you!!
ALEXRUSS55 said:
This worked for me, thank you!!
Click to expand...
Click to collapse
Welcome :highfive:
jpasint said:
Are you using the hide root feature?
If so then that is probably your issue.
Click to expand...
Click to collapse
What issue does this cause?
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
stiffis said:
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
Click to expand...
Click to collapse
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
kenpaci said:
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
Click to expand...
Click to collapse
Looks like that worked, thanks!
stiffis said:
Looks like that worked, thanks!
Click to expand...
Click to collapse
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
webgurru said:
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
Click to expand...
Click to collapse
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
stiffis said:
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
Click to expand...
Click to collapse
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
hshah said:
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
Click to expand...
Click to collapse
Try closing those apps first, I think it goes ok as long you don't start the apps yourself because most off the apps checks root at startup, but I can't guarantee you anything
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
hshah said:
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
webgurru said:
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
Click to expand...
Click to collapse
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
hshah said:
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
Click to expand...
Click to collapse
Any luck or help from this thread to resolve?
webgurru said:
Any luck or help from this thread to resolve?
Click to expand...
Click to collapse
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
hshah said:
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
Click to expand...
Click to collapse
Thanks. In my point of view this look to be a bug in Magisk. Did you tried some older version?
If I unlock my XL when I get it will it prevent Google Pay from working?
I thought Google deemed an unlocked phone as being insecure.
Assuming by unlock, you mean unlocking the bootloader, yes, using stock software, it will prevent you from using google pay as long as the bootloader is unlocked.
uicnren said:
Assuming by unlock, you mean unlocking the bootloader, yes, using stock software, it will prevent you from using google pay as long as the bootloader is unlocked.
Click to expand...
Click to collapse
Unless you follow these instructions: https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
magisk will make gpay work
GPay
sudoxd said:
magisk will make gpay work
Click to expand...
Click to collapse
Got mine working this afternoon
OK, so I have to root. Understand. Thanks all.
m+a+r+k said:
OK, so I have to root. Understand. Thanks all.
Click to expand...
Click to collapse
If you root with SuperSU I will come over there and throat punch you
I rooted using magisk when i 1st got my phone and followed the steps to get gpay to work. unfortunately it never worked had to go back to stock and relock the bootloader. anyone else having this issue?
manson1994 said:
I rooted using magisk when i 1st got my phone and followed the steps to get gpay to work. unfortunately it never worked had to go back to stock and relock the bootloader. anyone else having this issue?
Click to expand...
Click to collapse
Works fine for me with magisk and the tick checked under magisk hide for gpay. Your rom may be causing issues if you have one.
sudoxd said:
If you root with SuperSU I will come over there and throat punch you
Click to expand...
Click to collapse
I still remember the glory days of superSU
Ahh how times have changed
sudoxd said:
If you root with SuperSU I will come over there and throat punch you
Click to expand...
Click to collapse
Wow, and no emoji.
Replaced SU for Magisk years ago
sudoxd said:
Works fine for me with magisk and the tick checked under magisk hide for gpay. Your rom may be causing issues if you have one.
Click to expand...
Click to collapse
I will try again I did Mark it as hide in magisk, however when I disabled the permissions when they popped back up I think I hit allow. That may be the issue. I just used the stock room with root
manson1994 said:
I will try again I did Mark it as hide in magisk, however when I disabled the permissions when they popped back up I think I hit allow. That may be the issue. I just used the stock room with root
Click to expand...
Click to collapse
why did you disallow any permissions? everything gets setup as it would normally, just with gpay checked in magisk hide.
I just freshly installed LineageOS 17.1 (unroot) on my Mi 8 and planned to stay unroot.
I just can't get banking apps works, it keep crashed/FC and said apps not working on rooted device.
Or did I missed something and LineageOS came prerooted as default now?
I need your suggestions guys.
R324D said:
I need your suggestions guys.
Click to expand...
Click to collapse
It is caused by unlocked bootloader. Hide that state with Magisk or use unofficiall LOS.
mar.ur said:
It is caused by unlocked bootloader. Hide that state with Magisk or use unofficiall LOS.
Click to expand...
Click to collapse
I see.. thanks for your response.
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Backup your data, then do a factory reset.
Thanks, I've tried that multiple times actually. Unfortunately it doesn't fix it
Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?
hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
I have this exact same issue.....
I dont know why this happend and how to fix this annoying issue!!
Which ROM do you have installed?
Oceanone said:
Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?
Click to expand...
Click to collapse
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.
Same issue, same topic:
Phone-Root boots into the Miui recovery with root (NON-TWRP)
Hi, Im testing my phone without, NON-TWRP. After root, and shutdown/restart the phone, the phone boots automaticly to Miui recovery instead of starting the phone normally... After 10 min, the phone starts in the normall mode with root. How to...
forum.xda-developers.com
aygul12345 said:
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.
Click to expand...
Click to collapse
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
I'm smashing my head around....
Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
I'm smashing my head around this... Exact same issue....
Flashing the latest EEA from, and installing 2 modules to hide that I'm being unlocked the boat loader, from that point if I restart than occurs the recovery boot loop.
Same moment not 30 days later.
Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).
hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.
aygul12345 said:
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).
Click to expand...
Click to collapse
I didn't text that, because I need to use both Android Auto and Google Pay. To use AA, I have to unlock bootloader. To use google pay, I have to install a module to hide root.
Oceanone said:
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.
Click to expand...
Click to collapse
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?
aygul12345 said:
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?
Click to expand...
Click to collapse
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.
aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for the confirmation!!
aygul12345 said:
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.
Click to expand...
Click to collapse
I saw your post on Github. Thanks for the effort! https://github.com/kdrag0n/safetynet-fix/issues/216
hympe said:
Thanks for the confirmation!!
Click to expand...
Click to collapse
hympe said:
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs
Click to expand...
Click to collapse
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
The cause of this issue is being logged on to the author github:
Xiaomi Mi 11 Pro - Installing this module boots into the recovery continuously · Issue #216 · kdrag0n/safetynet-fix
Describe the bug A clear and concise description of what the bug is. After having Root enabled by TWRP OR Flashing Magisk_modified_boot.img, there is no problem with Root on this device. But after ...
github.com
@Oceanone
@hympe Don't need to update, if it happens below then it also is happening on the latest version.
But @hympe can you confirm when you disable the Safetynet fix module, the phone reacts normally and boots normally?