Hey guys..This website has solved a lot of problems..So I hope it solve this too
My problem started when I flashed Cm12.1 on my s3 neo gt-i9031I
The ROM was flashed and it worked perfectly..And then I installed SuperSu app from the play store
And here the problem comes..the app said that it needs to update Su binary
I tried the normal way but then it said "Installion failed,Please reboot and try again"
And after rebooting several times it keeps saying the same thing
I tried using option twrp (I have twrp recovery installed)
It said that the app will attempt to reboot my phone to recovery..But then nothing happened. didn't reboot or do anything.. I booted into recovery but nothing happened either
Then I saw a YouTube video that has Su bb installer
I downloaded a zip and flashed it via recovery.. And the problem got worser..After I booted..I found that SuperSu icon has changed..To the old version.. The superman icon..When I try to open it...It doesn't open and lags the phone..
Tried to update via play store
Successfully updated but it doesn't wanna open and it made the phone laggy
I had to uninstall updates..Force stop and disable and the phone returned back to normal..No lags
But now I am in unrooted status I think.. can't open the app or remove it cuz it was a system app
I think the problem got worser when I flashed the Su Bb installer which the video said that it works for every phone
I think it was too old..I don't know..please help..Sorry for the too long topic..I am afraid of rerooting cuz I am already rooted but I can open the app..HELP..HELP..HELP
The Su bb installer link that I used
https://www.androidfilehost.com/?fid=9390233485161005747
Don't do anything. Just re flashed CM 12.1 or any CM ROM. before do anything read their instructions carefully. Ok
In all CM based ROMs the root is disabled by default. Go to settings>About Device and click on Build Number 7 times. Return back and you will have Developers options just above About Device menu. Go in there and there you can unable root access. After that do whatever you want.
Anyone else having an issue with Android Pay. I am rooted (systemless) and finally decided to add a card to Android Pay. I've been able to get into Android Pay and tap the plus button to add the card just to test that it would work. I'm just now getting around to setting it up now. This time however tapping the plus button, I get the error message when you are rooted the traditional way. I didn't install any new apps that weren't directly from the Play store or that use root in any way.
I checked and noticed Android Pay was updated though. I went ahead and rebooted and was now able to add a card. But in the middle of adding another card I got the same error message. I dismissed it and was able to add another card. For some reason I could not add my Bank of America Visa though. So I haven't used it yet at a terminal. Anybody seen this issue?
synnyster said:
Anyone else having an issue with Android Pay. I am rooted (systemless) and finally decided to add a card to Android Pay. I've been able to get into Android Pay and tap the plus button to add the card just to test that it would work. I'm just now getting around to setting it up now. This time however tapping the plus button, I get the error message when you are rooted the traditional way. I didn't install any new apps that weren't directly from the Play store or that use root in any way.
I checked and noticed Android Pay was updated though. I went ahead and rebooted and was now able to add a card. But in the middle of adding another card I got the same error message. I dismissed it and was able to add another card. For some reason I could not add my Bank of America Visa though. So I haven't used it yet at a terminal. Anybody seen this issue?
Click to expand...
Click to collapse
Ugh. I was going to post that I hadn't seen this before, but before doing so I removed my discover card from AP and tried to add it again - got that dang error message you're referring to. Then rebooted my phone and tried to re-add it, and this time got further to where it says "contacting your bank" before again failing. Ugh Google why! Might try side loading the old version of AP see if that makes a difference.
EDIT: Very, very odd. I rolled back to the previous 1.1.1 version and tried adding the card again. The first time it failed instantly, but the 2nd time I tried (immediately after) it went through fine.
EDIT2: Just tried adding a completely different card after RE-updating to the latest version and it added perfectly fine right away the first time I tried. No idea what's going on here.
I might try going to a terminal later today to see if it works with the cards I already have added and I want that free Chromecast
I can't seem to add any more cards. They both say failed to verify info.
I was able to use Android Pay at the grocery store today. I still haven't been able to add any other cards thoug,even though I've waited 24 hours since adding the last two.
Decided to root today for the first time on this phone and I am also having this issue, so I went back to stock. I am on MMB29P. I had installed twrp, then flashed the systemless root version 2.66. Root was working fine, but the safteynet checker failed and I tried adding a card and got the Android Pay error. I have not tried the old method of installing the modified boot / SU... I just let 2.66 patch the boot image for me. I really just wanted to use Adaway too.
Edit: I guess adaway modifies the system partition, so that is probably why this wasn't working for me. Since that was the main reason for me to root, guess I'm staying on stock.
Read this thread on systemless root.
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105
If it were me though I would just flash the /unSU zip, then flash SuperSU 2.61 http://download.chainfire.eu/746/SuperSU/BETA-SuperSU-v2.61-20151207213702.zip . Then AP should just work without having to run any terminal commands. I've done it this way numerous times and it worked every time.
As for Adaway, if you flash the systemless hosts zip before installing Adaway AP will be unaffected.
Adaway thread http://forum.xda-developers.com/showthread.php?t=2190753
systemless hosts download https://www.androidfilehost.com/?fid=24269982087016285
I only ever add one card though.
And I don't have busybox installed (although I did install it previously and AP worked without issue)
So I can't add my Bank of America card because it can't verify my system, but I can still use android pay with the card I already have added. Not sure what to do at this point. Also want to point out the safety net app passes.
After downloading the Android 10 OTA via the Oxygen Updater App I performed a local upgrade upon which everything worked perfectly. Then after installing Magisk via TWRP and a second time via a patched Magisk based boot / recovery image via ADB my SIM card is not being recognized preventing me from making and receiving calls. After returning to stock OOS Android 10 everything works. Its just when I install Magisk that my SIM card is not recognized.
Anyone know why when I install Magisk my SIM card is not found?
That's probably because of the Magisk Module to record OOS calls. Disable that module and restart, issue should fix. For call recording use joneplus tools from Play store.
rezapatel said:
That's probably because of the Magisk Module to record OOS calls. Disable that module and restart, issue should fix. For call recording use joneplus tools from Play store.
Click to expand...
Click to collapse
Thank you very much @rezapatel THAT WORKED!
How did u installed twrp and magisk without decrypting data plz tell
That worked for me too. Although now I cannot access the SIM & network settings. The com.android.phone.PhoneApp crashis instantly.
Thank you! Also work for me
Although now I cannot access the SIM & network settings. The com.android.phone.PhoneApp crashis instantly
Click to expand...
Click to collapse
. SAME HERE
Worked for me too, and I am able to access SIM settings.
rezapatel said:
That's probably because of the Magisk Module to record OOS calls. Disable that module and restart, issue should fix. For call recording use joneplus tools from Play store.
Click to expand...
Click to collapse
My man ! you saved the day,Thanks!!!! ! So i guess we have to live without this module? Is there a way to use it somehow without sim issues?
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
Not sure whether to post here or under ROMs.
Phone was working fine this morning, had a couple of missed calls. I update Magisk and noticed both of my sim cards are showing a square icon w a line through it. When I go to settings, sim card, the app keeps crashing.
I am hoping I have overlooked something stupid and simple. Airplane mode is off, cycled it off and on just in case. Google play services was checked under Magisk Hide, unchecked it and rebooted. Still no phone modem.
I have XXX no limits installed and elemental kernel.
Only change I have made was updating Magisk. Thought I would post here before I uninstall Magisk.
***UPDATE****
I have the patience of a 2 yr old.
So this is what I did:
Unistalled all my Magisk modules
rebooted
phone is working
added my 3 modules back in 1 at a time and rebooted each time.
Got a weird reboot about a minute after my last reboot ( after I added XXX back in ).
I am using OS14 Laucher and got a couple of weird restarts there also.
But the phone and both sims are working.
This last update has been strange. After I updated my phone passed safety net for the 1st time in ages. My banking app still detected root and I can't use it, but I passed safety net.
After removing then re installing each of my modules I no longer pass safety net.....but that is a whole other post.