Related
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?
if this not the right section kindly link me to the correct section
Yesterday my wife's phone capacitive buttons stoped working on OXYGEN OS 9.0.0 OP5
so i tried downloading from oneplus site the latest update and i have ended downloaded 8.1.0 instate of 9.0.2
and i flashed it locally but unfortunately things got worse and every thing stopped working wifi, launcher, apps, google, almost every thing stopped working and i realized what i just did
then i have searched for 9.0.2 from external website and downloaded and installed locally on op5 and things was good buttons came to work and every thing was fine except one little issue the contacts app and phone app is not working any more even i tried to install google contact with no luck
after every update i have wiped cash and rebooted
kindly advice and any help will be appreciated
yosry said:
if this not the right section kindly link me to the correct section
Yesterday my wife's phone capacitive buttons stoped working on OXYGEN OS 9.0.0 OP5
so i tried downloading from oneplus site the latest update and i have ended downloaded 8.1.0 instate of 9.0.2
and i flashed it locally but unfortunately things got worse and every thing stopped working wifi, launcher, apps, google, almost every thing stopped working and i realized what i just did
then i have searched for 9.0.2 from external website and downloaded and installed locally on op5 and things was good buttons came to work and every thing was fine except one little issue the contacts app and phone app is not working any more even i tried to install google contact with no luck
after every update i have wiped cash and rebooted
kindly advice and any help will be appreciated
Click to expand...
Click to collapse
Try wiping cache and data on those two apps from settings/apps
Already tried no change and i forgot to mention that in sync setting contracts showing (something went wrong)
yosry said:
Already tried no change and i forgot to mention that in sync setting contracts showing (something went wrong)
Click to expand...
Click to collapse
Oh, you've downgraded 9.0.0 to 5.1.7 and then updated to 9.0.2
That isn't a good idea... Anyways, let's see how we can help you.
Is your wife's phone rooted and has unlocked bootloader and TWRP? Anything?
strongst said:
Oh, you've downgraded 9.0.0 to 5.1.7 and then updated to 9.0.2
That isn't a good idea... Anyways, let's see how we can help you.
Is your wife's phone rooted and has unlocked bootloader and TWRP? Anything?
Click to expand...
Click to collapse
Nope its not rotted
And if there is a way to avoid rooting would be better
yosry said:
Nope its not rotted
And if there is a way to avoid rooting would be better
Click to expand...
Click to collapse
So it also means the bootloader is NOT unlocked and you don't have a twrp recovery installed?
strongst said:
So it also means the bootloader is NOT unlocked and you don't have a twrp recovery installed?
Click to expand...
Click to collapse
Right
yosry said:
Right
Click to expand...
Click to collapse
You can reboot to stock recovery and wipe cache and reboot. Let's see if it works.
strongst said:
You can reboot to stock recovery and wipe cache and reboot. Let's see if it works.
Click to expand...
Click to collapse
Done no change i mentioned in the 1 St post that i cleared cache after every install
yosry said:
Done no change i mentioned in the 1 St post that i cleared cache after every install
Click to expand...
Click to collapse
I'm sure the issue is cause of down and updating in a dirty way. You can maybe try again install 9.0.0 then 9.0.2
Otherwise a factory reset is the next option you should consider cause there's no way to wipe separate partitions or backup anything with stock recovery and without root or external help.
strongst said:
I'm sure the issue is cause of down and updating in a dirty way. You can maybe try again install 9.0.0 then 9.0.2
Otherwise a factory reset is the next option you should consider cause there's no way to wipe separate partitions or backup anything with stock recovery and without root or external help.
Click to expand...
Click to collapse
Ok i will try to install 9.0.0 then 9.0.2 again lets see if it will work thanks
Hey there i tried downgrading to 9.0.0 then to 9.0.2 with no luck leaving me with no choice but to factory reset and thankfully it worked eventually after talking a backup
So thank you all guys for support and appreciate your help
Hey,
so i ****ed up my 6t (stock rom, twrp installed and rooted with magisk) yesterday after ota updating to 9.0.17., got stuck in a bootloop.. i guess it was the lawnstep magisk module that caused the **** up... but im not sure. normally i could do a ota just fine. so after unbricking and flashing 9.0.17 manually i cannot Access my storage outside from TWRP (when in recovery i can access the storage just as normal and it shows also on my pc as normal), apps cannot Access, pc - same. And i have no clue whats causing it.
Obviously i switched to file transfer in the notification area, usb Debugging enabled, reboot pc, 6t, switched usb ports, wiped the whole good damn phone again. nothing.
Any clues?
help would be greatly appreciated!
best,
T
Solved
TanakaX5 said:
Solved
Click to expand...
Click to collapse
Thanks for the very descriptive resolution to your issue. This will definitely help out anyone else that has this issue in the future!
Jager said:
Thanks for the very descriptive resolution to your issue. This will definitely help out anyone else that has this issue in the future!
Click to expand...
Click to collapse
Haha OK ok.. you are quite right...
It wasn't really a solution, did full reset of software with the unbrick tool provided here in the forum.
After that updated via Ota rooted and all is good again,
Peace
Haven't had that issue with 9.0.17, but I have had the issue where I'll go to use an app that requests root permission, it'll fail. Check magisk manager it says magisk isn't installed. A reboot fixes it, but I never had that issue on 9.0.16
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
I updated from magisk canary my devicesis still rooted everything working even i have the widevine L1 bt the wifi is not enabling and i try to open the wifi settings by long press it hang for 30 to 40 seconds ... I updated from IN 10.5.10 DA to 10.5.11 DA. can someone help me. I have no complaints from anything just my wifi not turning on. Thanks
Bdw i tried to reboot clear cashe and clear data of wifi application nothing works.
Dev Saxena said:
I updated from magisk canary my devicesis still rooted everything working even i have the widevine L1 bt the wifi is not enabling and i try to open the wifi settings by long press it hang for 30 to 40 seconds ... I updated from IN 10.5.10 DA to 10.5.11 DA. can someone help me. I have no complaints from anything just my wifi not turning on. Thanks
Bdw i tried to reboot clear cashe and clear data of wifi application nothing works.
Click to expand...
Click to collapse
Had that to one update ^^
I could fix it by:
1. Downloading the update ZIP (had deleted it)
2. Flashing it via the System Settings (this flashes the update onto the inactive slot) (don't reboot yet)
3. Using magisk manager to install magisk into the inactive slot
4. rebooting via magisk
I'm still not sure what went wrong cause I couldn't reproduce the bug yet, so I guess good look fixing it
KanayeNet said:
Had that to one update ^^
I could fix it by:
1. Downloading the update ZIP (had deleted it)
2. Flashing it via the System Settings (this flashes the update onto the inactive slot) (don't reboot yet)
3. Using magisk manager to install magisk into the inactive slot
4. rebooting via magisk
I'm still not sure what went wrong cause I couldn't reproduce the bug yet, so I guess good look fixing it
Click to expand...
Click to collapse
Yes bro i did this when i updated the phn from 10.5.10 to 10.5.11
Dev Saxena said:
Yes bro i did this when i updated the phn from 10.5.10 to 10.5.11
Click to expand...
Click to collapse
Yeah, I did too. And had the problem when I did it the first time.
You can try to redo it, at least for me it helped out ^^
KanayeNet said:
Yeah, I did too. And had the problem when I did it the first time.
You can try to redo it, at least for me it helped out ^^
Click to expand...
Click to collapse
I got it bro I'm updating from magisk canary bt this time i updated from magisk 20.4 fist i direct install the then i rebooted frm inactive slot thanks to everyone one