Database Users

Apk Parse Error

Bear with me here, tis a long and windy tale!
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)

amaru007 said:
Bear with me here, tis a long and windy tale! [emoji14]
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)
Click to expand...
Click to collapse
Open/install terminal emulator and do "pm install /path/to/application.apk", it will give you aore detailed error about whats going wrong.
Sent from my Tw5ted SM-G900A using Tapatalk

Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.

amaru007 said:
Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.
Click to expand...
Click to collapse
Ah, try doing su first so you are running as root.
Sent from my Tw5ted SM-G900A using Tapatalk

Okay.
tried with su:
pkg: whatever.apk
Failure [INSTALL_FAILED_INVALID_URI]
Looking like Titanium restore hasn't worked properly either, loads of programs needing to be reinstall again.
Dunno if its connected to this problem or not.

Invalid uri means you did the path wrong, tab complete the path(volup+t i think, if not voldown+t) so you have it exactly correct, it doesnt matter if you are already in the directory containing the apk it needs the full path.
Sent from my Tw5ted SM-G900A using Tapatalk

Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.

amaru007 said:
Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.
Click to expand...
Click to collapse
So the error is consistently failed invalid apk? The ones that install fine on other devices?
Sent from my Tw5ted SM-G900A using Tapatalk

Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.

amaru007 said:
Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.
Click to expand...
Click to collapse
No problem, glad you got it figured out.
Sent from my Tw5ted SM-G900A using Tapatalk

I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.

Risk3 said:
I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.
Click to expand...
Click to collapse
No clue, usually if it errors in the visual installer it will also with command line, maybe try a factory reset? I'm not too sure, that's odd.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Turns out that the inability to install from the user interface coincides with a Cyanogenmod 13 (6.0.1) nightly upgrade. I'll either go back to a snapshot or try another nightly next week and see if that helps things along.
Thanks for your reply.

[HELP] There was a problem parsing the package

Hello there,
I am on 7.1.1 rooted with bootloader unlocked.
Everytime I try to install an apk file I get this message "There was a problem parsing the package"
Unknown sources is on!

I found on 6.xx when I turned on unknown sources I had to do a full reboot first and quickly open solid explorer to get the install done. Have you tried that yet?

Can you post a link of one apk failing?

rchtk said:
Can you post a link of one apk failing?
Click to expand...
Click to collapse
Sorry I can't.
I've not seen that exact error or actually any error toast installing an apk from my sd. In the installer the install button would not depress for me unless I did that re-boot and acted quickly. Not used 7.1 yet but hopefully I'll be able to use fdroid on it. I can on 7.0 after the initial install of PureNexus since "unknown sources" checked comes with the rom I've been able to install what I want. I turn if off after that and some updated apks are tricky to get done.

Rooting Galaxy s7 edge (SM-G935F) nougat causes black camera with crash.

Hi!
I rooted my galaxy s7 edge that had stock version of android 7 (nougat) on it using this tutorial: http://www.droidviews.com/install-twrp-root-galaxy-s7-and-s7-edge-on-nougat-g935fxxu1dplt/. Now when I open built-in camera app it shows me a black screen for few seconds and then it says "Camera has stopped" and it offers me to "Open app again" and "send feedback" And it keeps happening over and over again.
Lemma: The reason is rooting.
Proof: Camera app worked perfectly. After I rooted my phone it started to crash like I described above. Then I tried to force quit camera app and delete it's cache/data. It did not help. After that I wiped entire cache partition. Still no help. After that I wiped all partitions except system. That did not work either. Then I re-flashed unmodified original stock ROM. Then camera worked perfectly again. Then again I rooted my phone the using tutorial I linked above. And again exactly the same issue. Camera app show black screen for few seconds and then crashes with exact same error message. ∎
Does anyone know fix for that? And why it happens? Is it some kind of samsung's anti-root thing that prevent camera fromworking on rooted phones or what?
Update [SOLUTION]:
In case someone else has same problem.
My solution was to skip restarts in TWRP steps. No restart between format and installing packages. Restart once when everything in TWRP part is done.

Root doesn't break your camera
I just Rooted my G935F that had Nougat as official firmware and had zero problems with the camera.
Sent from my SM-G935F using Tapatalk

I have international version of samsug with exynos CPU. Maybe this changes anything?
Root doesn't break your camera
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
I downloaded original firmware from here: https://www.sammobile.com/firmwares/database/SM-G935F/ (I chose baltic (only 1 occurrence in the table))
Maybe that specific tutorial I linked is bad one? Could anyone check that?

Rooted my G935F and no problems here for me.
I suggest you follow the tutorial here on xda and try again.

Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?

sysctl said:
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
Click to expand...
Click to collapse
A simple search here you'll find all you need. You are the only person I've ever read of that had camera problems like you've stated after Root. Again rooting won't break your camera.
I've Odin to stock literally hundreds of times testing Rom/Mods/themes as a tester for several teams from my s3 up to and including my G935F.
I've also flashed every Rom available for the G935F and the only ones with camera problems are the Lineage or AOSP Roms which more than likely are kernel related. Start here https://forum.xda-developers.com/announcement.php?a=81
Then this
Here's one
https://forum.xda-developers.com/showthread.php?t=3489011
sysctl said:
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse

Again rooting won't break your camera.
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.

sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Ok here is what you need to do.
Download a logcat app and get a logcat of it forceclosing.
I can't magically look in your device and see what, if anything is wrong.
As far as you saying you've searched well if you really did you would've found several tutorials.
How do I know?? Because I've used them myself.
It took me less than 5 minutes to root my new G935F using the TWRP Guide here on XDA
You seem to be the only one in hundreds that's claiming root broke your camera.
Provide a logcat in the Q&A and maybe a dev can help you.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Sent from my SM-G935F using Tapatalk

You could try to reset your settings

Same issue on smg935w8 lost camera and screen brightness. Also can't mount micro sd... we're you able to fix? I thought it was a bad root then I re flashed and the issue came back...twrp 3.1.0 supersu 2.79 and no verity 5.1
---------- Post added at 10:15 PM ---------- Previous post was at 09:50 PM ----------
im re flashing stock and tomorrow ill redo twrp and super su and skip dm verity patch think that might be the issue as it worked before for me last week and i then messed up by turning dev mode off and disabling oem and when i reflashed after that i have been flashing the dm verity patch....
give that a try if your still having issues

had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too

Gray.Fox said:
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Click to expand...
Click to collapse
Thanks I've tried clearing cache for everything no luck. I originally thought it was because I might have deleted a system app with titanium but when I reflashed it all (firmware,tarp,supersu,no small verity disable 5.1) I still had the issue.
Lastnight I wiped and flashed the entire firmware. Everything works. Tonight I'm goi g to try and only flash twrp then supersu as I only want root. Hopefully that fixes my issues.
OP have your issues been resolved?
I'll let you know once I get it working on mine and we'll get you sorted out. I believe it's something with the steps or order as I had root fine for a day then had to reflash due to messing around and didn't do it my original way and that caused my issues.

flashed twrp 3.1.0 from odin with auto reboot off.
then booted to twrp. swiped right to mount system,
wipe data(format data) type yes.
mount microsd as mtp copy supersu 2.79 over if its not already on you microsd card.
else just install it from zip
cleared cache/delvik
rebooted to system
log in and setup everything and restore
camera and auto brightness...stilll doesnt work.

ok so after multiple tries to fix this (flash stock) everything works,, root and it breaks tried clearing all cache in system and twrp no difference... then i loaded phone info and used the secret codes to find out that my camera firmware is not installed....so im trying Flashfire to reflash the AP only while injecting supersu and maintaining root.... it is just booting up.....and OMG!!!!it works!!!!
so....for some reason...firmware was corrupting..... no clue why tired multiple methods and nothing... and im not a noob either.....
what finallllllllly worked was.... flash your rom and get root how you would normally. camera/auto brightness/and mounting usb doesnt work....boot to twrp. get your ap md5 file on your internal storage
reboot to system,. get flashfire from playstore or chainfires website
install and then click the + select firmware and select the tar file
only install system....uncheck boot and cp
then in the everroot select injject supersu, preserve recovery
and flash.... it will start flshing and boot to syteem once done..
everything is working nice
finalllyyyy!!!!
hope this can atleast help OP
no clue why i was losing firmware on the flashes

@unit68 Tnx for sharing. This time I got camera and brightness adjustment work out of box. But if in any point of time I happen to need your tutorial, I'll give it a try and let you know.
I am not sure if it is by chance or not but what I did differently this time was:
1) I paid attention to step where it asked to disable auto reboot (can anyone explain why?)
Previously I thought it shouldnt matter so I kept auto reboot for convenience.
2) I did format data, install no-verity-opt-encrypt-5.0 and SuperSU-v2.79-201612051815 and wipe dalvik cache with out rebooting between (Anyone know if that matters?).
Previously I had done it: format - reboot - install no enc - wipe dalvik cache- reboot - install super su - wipe dalvik cache - reboot .
Now I did it format - intall no enc - install super su - wipe dalvik cache - reboot.
I'll see for few days if anything else comes up or if camera breaks down again. Btw @unit68 what happens when you try some bloatware remover that run with root access? Do you get rid of bloatware or not? I tried few of them such as no bloat for example. Some complain that uninstall failed some seem to uninstall the app but when they reload app the app is still there and it's also still in app menu. Just curious if you have the same same issue. And is it safe to delete apk file manually? Or would it cause phone to crash/boot loop? When I ran supersu it complained about knox and asked me to disable it but it never managed to (however root checker tells me I am root). Maybe knox is protecting bloatware? Any ideas?

Flash your able too get it working! It was soooo frustrating. So for Knox supersu asks to disable then seems to hang so I go about my business reopen supersu it'll ask again and then is successful.
To remove bloat I normally just go to titanium and remove the ones I don't want
No issues on that and all my apps that require root work fine (titanium,adaway, flashfire)

This time disabling knox worked too... It turned out that all 3 apps that I used were note able to remove bloatware. App you named worked and also ROM toolbox lite works.
Btw when I google bloatware, the lists are incomplete.... Do you happen to know list of apps that must not be uninstalled? I guess white list would be better idea than black list.
Is installing/uninstalling app same as removing/adding apk files? So that I could cut and paste everything expect file manager and launcher to usb memory stick and then start adding required apps back one by one?

ive seen some samsung debloating software around. i honestly just remove stuff based on manually debloating for last fewyears. if i dont know what theapp is for i google it to see if its ok to remove. normally i remove samsung knox, few other samsung apps, some google apps (music, games, videio), briefings some edge panels, live wallpaper, and carrier branding apps(for me rogers) stuff like that. if you are going to i recommend you do a backup first as it ccan mess up your phone if you uninstall an important app. . also once your do uninstall you need to reboot ... the paid version of titanium allows you to freeze applications so you can try that first before removing it.

I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5

ScreAmeR01 said:
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
Click to expand...
Click to collapse
Interesting..ill check that if I need to to Flash. I have 2.79 but maybe I grabbed an old version or a beta. Mine says 20161205 I think it may have been sr3
Edit _ just checked I grabbed sr0 the stable release from 20161215 not the sr3 beta
Maybe it was corrupt when I flashed

Pokemon Go on latest Oreo with ElementalX?

Has anyone gotten latest version of PoGo working on latest Oreo with ElementalX? I've never played but my friends keep asking me to join so I figured what the heck..
Slight problem... Device Not Compatible??
I had magisk and xposed, but I tried disabling, and even fully uninstalling xposed (and all additional xposed modules), and adding PoGo to the MagiskHide options, with no luck.
It still says that my device is not compatible...I would assume that's due to the rooting?
Or is it because I'm using ElementalX kernel?
I read somewhere that there's a (not pokemon go-specific) bypass sort of thing involving SatefyNet, but you have to install Magisk *before* going through initial phone setup, but any guide I've ever read about flashing/rooting ph-1 says to go through setup and then install magisk. I tried to find the post that talks about it but I can't find it right now. Anyway, I would imagine there's some kind of checksum against system and if magisk has been added after the fact, the checksum wont match? I really have no idea, just a guess.
I haven't seen any other posts specifically mentioning Essential being incompatible, so maybe it's just me.
I was originally thinking it was because of root or magisk remnants(?), but maybe it's the non-stock kernel.
If anyone could help, I'd really appreciate it.
I feel silly asking such a noob question, I've just never play PoGo...or any Pokemon...ever.
extra info:
I have successfully created an account using their google auth option.
I get through the first Professor Willow part, then character selection.
Usually part way through character selection, I get the error in the attached image.
Its not on any one specific section, however, it can/has occur at any point during the loading.
I've cleared cache and data a hundred times because it seems to get further each time if I do a fresh data wipe and start over -- I know the next step already so I can get through faster maybe lol
--update--
I finally got through character selection and made it to the first chance to catch pokemon. I hit a squirtle and it was trying to break free, and then that error popped up.
Haven't been able to get back in far enough again to see if it actually added to my PokeDex or not.

Sorry for the late reply, but you have to hide root detection under magisk.
For Pokemon go to work, go to Magisk > MagiskHide > then search for Pokemon go and select it then reboot.

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