Related
Hi guys, i've installed Aosp Extended ROM but my safetynet is broken, i can't install any safetynet module from Magisk, from TWRP show "error 1 can't mount /system" but system is already mounted...
Any help? Thanks
N1ck474 said:
Hi guys, i've installed Aosp Extended ROM but my safetynet is broken, i can't install any safetynet module from Magisk, from TWRP show "error 1 can't mount /system" but system is already mounted...
Any help? Thanks
Click to expand...
Click to collapse
safety net has nothing to do with the ROM, but with Magisk and root. Maybe your Magisk installation isn't correctly configured ( Do not install Xposed Modules )
Re-flash the ROM and Reinstall latest Magisk (16.4).
ali-k95 said:
safety net has nothing to do with the ROM, but with Magisk and root. Maybe your Magisk installation isn't correctly configured ( Do not install Xposed Modules )
Re-flash the ROM and Reinstall latest Magisk (16.4).
Click to expand...
Click to collapse
Thanks, i've reinstalled magisk and now it's fixed
ali-k95 said:
safety net has nothing to do with the ROM, but with Magisk and root. Maybe your Magisk installation isn't correctly configured ( Do not install Xposed Modules )
Re-flash the ROM and Reinstall latest Magisk (16.4).
Click to expand...
Click to collapse
What's the problem with xposed? I had it in my previous phone and it passed safetynet with no issues.
Potus ThePlant said:
What's the problem with xposed? I had it in my previous phone and it passed safetynet with no issues.
Click to expand...
Click to collapse
Not sure but some of the modules break safety net. I've read it multiple times on different threads, people complaining wbout it.
ali-k95 said:
Not sure but some of the modules break safety net. I've read it multiple times on different threads, people complaining wbout it.
Click to expand...
Click to collapse
Ok, I'll try disabling the modules I have to see if that fixes the issue. I mostly have it to use GravityBox and Youtube Background Playback. The first one because I use the volume keys to skip songs (I'm using the stock rom) and the other one because Youtube vanced doesn't seem to install properly. Do you know of alternatives to any of those?
Potus ThePlant said:
Ok, I'll try disabling the modules I have to see if that fixes the issue. I mostly have it to use GravityBox and Youtube Background Playback. The first one because I use the volume keys to skip songs (I'm using the stock rom) and the other one because Youtube vanced doesn't seem to install properly. Do you know of alternatives to any of those?
Click to expand...
Click to collapse
Did you disable YouTube before + remove the playstore updates of YouTube too then install Vanced.
I don't use xposed at all as my ROM has everything i need, i just use a couple of Magisk modules ( font, vanced, iOS11 emojies and MiAi camera lag fix ). If nothing is broken, don't try and fix it
ali-k95 said:
Did you disable YouTube before + remove the playstore updates of YouTube too then install Vanced.
I don't use xposed at all as my ROM has everything i need, i just use a couple of Magisk modules ( font, vanced, iOS11 emojies and MiAi camera lag fix ). If nothing is broken, don't try and fix it
Click to expand...
Click to collapse
Where did that come from? I'm not trying to "fix" anything. All I want is to add is song skipping with the volume keys (something that should've been added to stock android by now). I tried what you said with vanced but it's still not working.
Alternative to Vanced youtube is "OGYoutube" (https://plusmods.com/ogyoutube) - installed as a standard app, so you can keep official updated Youtube (best of both worlds). I don't know about functional alternative to Gravitybox though, so you can't get rid of Xposed (the only module which breaks Safetynet by design).
Edit: if you use Gravitybox only for media control with volume keys, you might have luck with this app https://play.google.com/store/apps/details?id=frinky.volumeKeys.music.controller&hl=en. I didn't like it too much, but it's worth trying if Safetynet is your priority.
Edit2: Automation via Tasker is an option as well, but it was pain in the a** to use it on my previous phone.. https://www.xda-developers.com/tasker-pro-skip-music-tracks-using-volume-keys/
Edit3: Just realized that Button mapper pro (https://play.google.com/store/apps/details?id=flar2.homebutton&hl=en) offers this option as well and seems to be working fine. I guess that I can disable Xposed now, thank you for creating this topic
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
Hi,
So a bit of a noob question, but I was on beta OOS11 prior to going over to Open Beta and my Widewine support is L3 and not L1. I thought this was a result of unlocking the bootloader but was told this should not be the case. Any chance I can fix this as the Oneplus 8 Pro should have L1?!
Thanks in advance.
Shredz98 said:
Hi,
So a bit of a noob question, but I was on beta OOS11 prior to going over to Open Beta and my Widewine support is L3 and not L1. I thought this was a result of unlocking the bootloader but was told this should not be the case. Any chance I can fix this as the Oneplus 8 Pro should have L1?!
Thanks in advance.
Click to expand...
Click to collapse
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
efex said:
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
Click to expand...
Click to collapse
My bootloader is unlocked, I'm rooted, magisk and magiskhidr props config is installed and safety net passes but still I'm on L3
Shredz98 said:
My bootloader is unlocked, I'm rooted, magisk and magiskhidr props config is installed and safety net passes but still I'm on L3
Click to expand...
Click to collapse
Did you try clearing data/cache for Netflix (or whatever app you're using)? Does DRM Info (app) also show L3? Then I'm out of ideas.. Always worked for me on all versions since OOS 10.5.10. I'm on EU model IN2023
efex said:
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
Click to expand...
Click to collapse
efex said:
Did you try clearing data/cache for Netflix (or whatever app you're using)? Does DRM Info (app) also show L3? Then I'm out of ideas.. Always worked for me on all versions since OOS 10.5.10. I'm on EU model IN2023
Click to expand...
Click to collapse
Yeah that's the the thing the DRM info (app) shows L3 as does Netflix, tried clearing cache, uninstalling and reinstalling, everything but lock my bootloader again.
Thanks for your help in any case
Shredz98 said:
Yeah that's the the thing the DRM info (app) shows L3 as does Netflix, tried clearing cache, uninstalling and reinstalling, everything but lock my bootloader again.
Thanks for your help in any case
Click to expand...
Click to collapse
One more thing, is your play store certified? Shouldn't make a difference, but worth a try.
If not certified, clear data för Play store and Play services and it should be after self-updating.
efex said:
One more thing, is your play store certified? Shouldn't make a difference, but worth a try.
If not certified, clear data för Play store and Play services and it should be after self-updating.
Click to expand...
Click to collapse
Play store is certified. I wonder whether it is because I bought the 8 pro and it immediately updated to 10.5.12EU i believe it was but then I unlocked bootloader and went to OOS 11 DP3 though I didn't root nor check my Widewine status then, then updated to DP4 and then to OB1. It was only on OB1 that I rooted my phone and installed Magisk and only then that I checked Widewine status.
So I'm thinking I'm one of the unlucky ones who lost their L1 status via official update from OnePlus.
Shredz98 said:
Play store is certified. I wonder whether it is because I bought the 8 pro and it immediately updated to 10.5.12EU i believe it was but then I unlocked bootloader and went to OOS 11 DP3 though I didn't root nor check my Widewine status then, then updated to DP4 and then to OB1. It was only on OB1 that I rooted my phone and installed Magisk and only then that I checked Widewine status.
So I'm thinking I'm one of the unlucky ones who lost their L1 status via official update from OnePlus.
Click to expand...
Click to collapse
I was L3 until update 10.5.10 (or maybe 10.5.9). After that L1 all the way. I even clean installed DP4, updated to unrooted OB1, rooted, and still L1.
I would suggest that you MSMDtool back to an earlier OOS, unlock and root (and fix fingerprint issue that relocking BL causes), and then check L1 status. If it's L1 you should be good to update to OB1 again and root. I know I was L3 before that one update från OP so it's definetly reversable.
efex said:
I was L3 until update 10.5.10 (or maybe 10.5.9). After that L1 all the way. I even clean installed DP4, updated to unrooted OB1, rooted, and still L1.
I would suggest that you MSMDtool back to an earlier OOS, unlock and root (and fix fingerprint issue that relocking BL causes), and then check L1 status. If it's L1 you should be good to update to OB1 again and root. I know I was L3 before that one update från OP so it's definetly reversable.
Click to expand...
Click to collapse
Had a feeling you would say this and honestly the only reason I didn't MSMDtool back to an earlier OS is because of the whole fingerprint issue and scared of not being able to fix it.
I'll see what I can do, thanks mate!
Shredz98 said:
Had a feeling you would say this and honestly the only reason I didn't MSMDtool back to an earlier OS is because of the whole fingerprint issue and scared of not being able to fix it.
I'll see what I can do, thanks mate!
Click to expand...
Click to collapse
The fingerprint issues is easy to fix, I've done it a couple of times myself.. The instructions are good so just do what it says.
efex said:
The fingerprint issues is easy to fix, I've done it a couple of times myself.. The instructions are good so just do what it says.
Click to expand...
Click to collapse
Does the fingerprint issue always happen when relocking the bootloader or just sometimes? Anything I can do to avoid it?
Shredz98 said:
Does the fingerprint issue always happen when relocking the bootloader or just sometimes? Anything I can do to avoid it?
Click to expand...
Click to collapse
Not sure about that.. I've run the msmdtool twice, had to fix the reader both times.
efex said:
Not sure about that.. I've run the msmdtool twice, had to fix the reader both times.
Click to expand...
Click to collapse
Ugh, I'll now need to figure out whether L1 is worth it ?
Can anyone check this, My DRM app is showing widevine as L1 while as Netflix is showing Widevine L3 on oneplus 6T. Even the system id's are different(check ss) . I thought it would have been fixed in the new hotfix released today but No. I have tried every possible troubleshooting way, clearing data, cache, Reinstalling, restarting. Everything.
xubairsarwar said:
Can anyone check this, My DRM app is showing widevine as L1 while as Netflix is showing Widevine L3 on oneplus 6T. Even the system id's are different(check ss) . I thought it would have been fixed in the new hotfix released today but No. I have tried every possible troubleshooting way, clearing data, cache, Reinstalling, restarting. Everything.
Click to expand...
Click to collapse
L3
SOK seila said:
L3
Click to expand...
Click to collapse
Is your bootloader locked. What Rom are you on?
xubairsarwar said:
Is your bootloader locked. What Rom are you on?
Click to expand...
Click to collapse
Locked with oxygen 11 beta.
Is there any way of making Netflix work with magisk? Phone passes all the safety checks and app still ends up with 15001 issue.
nomtix said:
Is there any way of making Netflix work with magisk? Phone passes all the safety checks and app still ends up with 15001 issue.
Click to expand...
Click to collapse
Did you hide the Magisk app?
yes i did
nomtix said:
yes i did
Click to expand...
Click to collapse
Try using this app. It will tell you everything that could indicate that your phone is rooted. Add it to denylist first.
I use
Universal Safteynet Fix MOD https://forum.xda-developers.com/t/...tynet-fix-2-4-0.4217823/page-91#post-87198517
with liboemcrypto.so disabler 1.5 https://www.androidacy.com/magisk-modules-repository/
nomtix said:
Is there any way of making Netflix work with magisk? Phone passes all the safety checks and app still ends up with 15001 issue.
Click to expand...
Click to collapse
Im having the exact issue. I have the OnePlus 10 Pro running Android 13 + in Rooted with all safetynet in place. However i continue getting this error, (15001). (-93). I tried EVERYTHING, but NOTHING seems to fix my issue. Any help will be truly appreciated. Thanks.
LowaEastSide said:
Im having the exact issue. I have the OnePlus 10 Pro running Android 13 + in Rooted with all safetynet in place. However i continue getting this error, (15001). (-93). I tried EVERYTHING, but NOTHING seems to fix my issue. Any help will be truly appreciated. Thanks.
Click to expand...
Click to collapse
LowaEastSide said:
I tried EVERYTHING, but NOTHING seems to fix my issue.
Click to expand...
Click to collapse
So you're using the liboemcrypto.so disabler as well? Also try wiping data for Google Play Services/Store and Netflix.
Wiped everything as well. Even went into Configure DenyList, checked the google playstore, framework, plus services. noting seems to work. I tried some steps I found online but that didn't work as well. Its Crazy Cause i have my Oneplus 8 Pro running Android 11 and its working Fine on the Rooted device, with the Bootloader unlocked as well. So im assuming it has to be Android 13 O.S. Has anyone been able to get it working on there Rooted Device, with an Unlocked Bootloader, running Android 13? Any Help would Be Apricated. Its honestly bugging me Cause i cant get it working. Truly appreciate any Feed Back, Bless..!!
ethical_haquer said:
So you're using the liboemcrypto.so disabler as well? Also try wiping data for Google Play Services/Store and Netflix.
Click to expand...
Click to collapse
Yes, i am using liboemcrypto.so disable Plus Saftynet and a Couple Other Modules.