Database Users

passing safetynet with magisk 10.2 on x727 or x720?

Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?

squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500

squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.

Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.

suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!

robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.

Magisk V10 and phh SU r266 working fine for me on 20s

Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.

Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.

are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)

I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.

I could not pass safety net, got CM13, with MAGISK installed. Dang=)

squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app

You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.

squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks

I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.

Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?

bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?

Magisk 17.3 and/or Intune portal hider on the 6T

Has anyone managed to get the Intune Portal Hider to to work on the 6T. The version for Magisk 18.xxx gets detected in about 15 minutes. I cannot get Magisk 17.3 to pass Safetynet on the 6T, fails with "API error". The aggravating thing is that this worked without a hitch on the 5 with Magisk 17.3

Check which version of Magisk Manager you have installed. Flashing Magisk 17.3 automatically installs MM 6.0.1. Update it to 6.1.0. I ran into the same issue the other night when I updated to OOS 9.0.12. Magisk 18.1 kept failing SafetyNet checks. Uninstalled it and reinstalled 17.3. I got the same API error until I installed MM 6.1.0.

sharksfan7 said:
Check which version of Magisk Manager you have installed. Flashing Magisk 17.3 automatically installs MM 6.0.1. Update it to 6.1.0. I ran into the same issue the other night when I updated to OOS 9.0.12. Magisk 18.1 kept failing SafetyNet checks. Uninstalled it and reinstalled 17.3. I got the same API error until I installed MM 6.1.0.
Click to expand...
Click to collapse
If I could hit the thanks button 10x I would. interesting that I pass Safety Net without issues for 18

SafetyNet will initially pass on 18.x. But for me at least, after some time it will fail. Toggling Magisk Hide off/on will then allow it to pass SN again. I got a bit obsessive in checking it so it was just less to worry about using 17.3. Can't figure out where the problem is exactly since I can't forcibly reproduce it. But the other night after I updated OOS, Magisk 18.1 passed SN. I went to sleep & the next morning checked SN and it failed. I haven't had any such issues with 17.3.

sharksfan7 said:
SafetyNet will initially pass on 18.x. But for me at least, after some time it will fail. Toggling Magisk Hide off/on will then allow it to pass SN again. I got a bit obsessive in checking it so it was just less to worry about using 17.3. Can't figure out where the problem is exactly since I can't forcibly reproduce it. But the other night after I updated OOS, Magisk 18.1 passed SN. I went to sleep & the next morning checked SN and it failed. I haven't had any such issues with 17.3.
Click to expand...
Click to collapse
I have experienced exactly the same issue in both 18.0 18.1. My banking apps seem to detect root also. Got fed up with it and didn't experience any of these issues with 17.3, so just stick with this version as it does what I need it to do.

dj_ooms said:
I have experienced exactly the same issue in both 18.0 18.1. My banking apps seem to detect root also. Got fed up with it and didn't experience any of these issues with 17.3, so just stick with this version as it does what I need it to do.
Click to expand...
Click to collapse
Magisk 17.3 with Manager 6.1.0 so far is the most stable version you can get until v18 gets improved.

For me it's kinda weird. Intune Hider for 18.1 work for me. Hides what I need and all that. But my mobile data doesn't work. Disable the module and poof it's back.
Edit: Never mind. Got it by disabling a couple apps from Magisk Hide.

July Security Happened Automatiically - Deleted Magisk

Well restarted my phone on the weekend and when it started up a notification showed it was being updated. I had automatic updates turned off. I checked and see I am now on July update.
Magisk manager is still installed but it says Magisk has been uninstalled. The strange this is that the Google Camera is still working.
Has anyone else had something similar happen?

Yes magisk and twrp has been removed
Yes it has happened to me too.
Twrp got removed from boot and also magisk was uninstalled.
Gcam app is also not working
Can anyone help me remove the gcam app from boot.
Thanks in advance

ludditefornow said:
Well restarted my phone on the weekend and when it started up a notification showed it was being updated. I had automatic updates turned off. I checked and see I am now on July update.
Magisk manager is still installed but it says Magisk has been uninstalled. The strange this is that the Google Camera is still working.
Has anyone else had something similar happen?
Click to expand...
Click to collapse
No, had updates turned off since early Oreo and its never updated 'automatically'.

Happened to me also. As it didn't behave like a normal update, I am wary of reinstalling magisk/twrp. Has anyone done it, can they post a link to the guide they used?
Thanks all
Sent from my Mi A1 using Tapatalk

I didnt have twrp installed, but i dontbthink i will bother with Magisk reinstall because gcam is still working.. only problem is that my Viper i stall has gone.. so if i get sick of the low volume through headphones, i will install magisk again

Have installed magisk - or at least have root acess, but magisk manager says it's not installed. Maybe I am doing something wrong. or is it a version release issue. Also is Cosmic Dan's twrp the best way to go with July release
Thanks
M

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.

Alternatively is it possible to access the settings of this submenu through a different app or way?

hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen

True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages

Have you got any magisk module active?

estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.

hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP

Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!

@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers

Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.

hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers

Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:

Is there any risk involved concerning the encryption?

hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.

Stuck with the same issue. Did you manage to get it fixed somehow?

Actually the latest available oo update to 10.3.1 fixed it.

hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.

You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.

hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.

Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though

[Guide] LineageOS 18.1, Android 11, Magisk Root, and Passing SafetyNet

I was bored one evening, so I started poking around on XDA Forums, and found a way to fix the battery issue I had with OnePlus 3T that made me switch to another device years ago! I was surprised how usable 3T is to this day. I thought I would breathe some life into it with LineageOS 18.1 that continues to receive security updates and patches. This way I will have a backup phone ready in case something happens to my OnePlus 6. It is unlikely that 3T will receive LOS 19, so this guide should stay relevant for a long time.
1) Get back to the latest version of Oxygen OS if you are on a custom ROM. Use something like MSM Download tool and then upgrade to 9.0.6 with the built-in updater.
2) Follow the instructions on los website to install LineageOS 18.1 and google apps via MindTheGapps. If you do not need google apps, then you probably do not care about SafetyNet and do not need this guide
Now the main issue is the SafetyNet. If you install YASNAC - Yet Another SafetyNet Attestation Checker you will see that the phone is not passing the SafetyNet verification, meaning that Google Pay will not work and some other apps, like banking apps, might not work either. We are going to fix that with Magisk and MagiskHideProps. Feel free to poke around on your own. I will just present that have worked for me.
3) Go to Magisk's Github, download the latest release and follow the installation instructions. (Notes: 3T has RAM Disk, there is no separate vbmeta, boot.img is inside lineage-18.1-xxxx.zip)
4) Once you have Magisk working, got to MagiskHidePropsConf and get the latest release there. Go to Force Basic Attestation Post and follow the installation instructions under the spoiler.
5) Now, let's get Basic Integrity to pass. Go to Basic Attestation Post and make sure to add both com.google.android.gms.unstable and com.google.android.gms to deny list. Reboot. Go to YASNAC. It should say that Basic Integrity is passing. CTS profile match is not, but that's okay.
6) Install terminal app like Termux. Open it, and run su to get superuser privilages. Then run props. Follow the instructions to Edit device fingerprint (option 1).
Edit Device Fingerprint (1)
Pick a certified fingerprint (f)
Pick vendor (OnePlus is 21 at the time of writing)
Pick device (3T is 5 at the time of writing)
Pick the one with Android 9. (It does not matter that the android versions are mismatched)
Follow the instructions to apply changes and reboot.
7) Check YASNAC, everything should be passing now!
Some other suggestions:
GCam is pretty nice alternative to the original camera. I would recommend this one. (It is recommended to also install Google Photos. It is a google camera after all.)
OpenWeather is a nice weather provider.
I would also recommend going to Google's Keyboard, Messages, Phone, and Calendar Apps. AOSP ones are not great, in my opinion.
Hope somebody finds it useful! Good luck!

Ah nicely done, thanks for the effort and work you put into this. How is your 3T performing?

AndyC76 said:
Ah nicely done, thanks for the effort and work you put into this. How is your 3T?
Click to expand...
Click to collapse
Hi, thanks! I was planning to use it as a development device to pick up android app development, but life got in the way and that never got off the ground
My 3T has developed a battery issue which ultimately led to me retiring it. The battery is extremely unreliable. It can be at 1% but work for 3 hours, sometimes the phone refuses to charge and the battery percentage tends to get stuck at 50% regardless of the actual charge level. I tried replacing the battery but the same behavior persisted. I think it is something either with the motherboard or the battery connector on it :/ Still a pretty snappy phone though!