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
Related
Hey all,
Everytime I root my 1.2 device with manual nooter 4.5.6 (haven't tried .18), I get one download out of the Android Market. After that the Market.apk disappears from the system/app directory and I can no longer download apps. The end result of this is that I'm pretty much hosed. I've tried putting SU File Manager on to sideload apps, but it can't installed BusyBox because of the market problem, so no luck with that. I've reproduced this issue at least half a dozen times, using CWR to delete all the user data, re-registering the stock install, and then rooting again.
At this point I'm staying stock until I feel confident I can download more than one app from the market on a rooted device.
So, has anyone else experience anything like this, and if so, is there a solution?
I have this same problem. No solution yet.
It may be related to a download directory bug which has been fixed. I updated to MN4.5.18 over 4.5.6. Everything worked well untill a recent update to 4.5.25. The market crashed again. This issue seems not solved yet. So I had to flash back 4.5.18.
Same here - .18 works very well once you figure out you have to uninstall the apps that want to update and then reinstall clean to remove the chance of bootloops. I was considering doing a complete wipe again and flashing .25, but I've decided to stick it out with .18 until they get squared away.
Overall, MN4.5.18 kicks ass for all intents and purposes, and I'd suggest moving up to that.
mjbelknap said:
.18 works very well once you figure out you have to uninstall the apps that want to update and then reinstall clean to remove the chance of bootloops.
Click to expand...
Click to collapse
Can you elaborate on this?
Can ANYONE elaborate on this
hi
\i have tried installing the framework in order to use the Xposed Installer mods\ \
ALWAYS ALWAYS immediately after reboot i get the "Unfortunately SYSTEM UI has stopped" error ALWAYS
i have done full wipes data, cache, dalvik AND SYSTEM only to come back with the same error time and again
i have installed crash rom from galaxy s4 gt- i9500
again as i said completely wiped and yet the error is there
also and this is absolutely baffling - i downloaded several new cusoms roms for the galaxy s4 gt-i9500 *wanamlite, phoenix, cobra"
and for the life of me cobra would not start at all - again after full wipes - system, data, dalvik cache and with full battery - zim\
phoenix loaded once only to fully freeze after and no go and wanamlite loaded only to come up with nottach mods from lord knows where that made the system unstable and rebooted into oblivion
again i reload this rom as downloaded fresh from full wipes.
i am luckily using crash version 11 but unable to do the framework install
PLEASE PLEASE HELP, i am new and am not allowed to post into the developper's area to find an answer please please
thanks from the bottom of this 68 year old geek
exlaval said:
hi
\i have tried installing the framework in order to use the Xposed Installer mods\ \
ALWAYS ALWAYS immediately after reboot i get the "Unfortunately SYSTEM UI has stopped" error ALWAYS
i have done full wipes data, cache, dalvik AND SYSTEM only to come back with the same error time and again
i have installed crash rom from galaxy s4 gt- i9500
again as i said completely wiped and yet the error is there
also and this is absolutely baffling - i downloaded several new cusoms roms for the galaxy s4 gt-i9500 *wanamlite, phoenix, cobra"
and for the life of me cobra would not start at all - again after full wipes - system, data, dalvik cache and with full battery - zim\
phoenix loaded once only to fully freeze after and no go and wanamlite loaded only to come up with nottach mods from lord knows where that made the system unstable and rebooted into oblivion
again i reload this rom as downloaded fresh from full wipes.
i am luckily using crash version 11 but unable to do the framework install
PLEASE PLEASE HELP, i am new and am not allowed to post into the developper's area to find an answer please please
thanks from the bottom of this 68 year old geek
Click to expand...
Click to collapse
Why u dont try to install a STOCK ROM and try install Xposed?
stock rom
Joku1981 said:
Why u dont try to install a STOCK ROM and try install Xposed?
Click to expand...
Click to collapse
i don't like predigested food, and that's wiat a stock kernel is, it's bland, locked
also i want to keep on top of what are the developpers working on, it's interesting work and many times
these guys bring refinements to the OS that the majors don't bother with because they have to offer something with the LEAST
chances of goofups and yet many times their errors are 1000 times worse than the customs.
i like doing it, and i've been doing it since my last sony {i forget their last os} and then the first samsung galaxy note n7000
exlaval said:
i don't like predigested food, and that's wiat a stock kernel is, it's bland, locked
also i want to keep on top of what are the developpers working on, it's interesting work and many times
these guys bring refinements to the OS that the majors don't bother with because they have to offer something with the LEAST
chances of goofups and yet many times their errors are 1000 times worse than the customs.
i like doing it, and i've been doing it since my last sony {i forget their last os} and then the first samsung galaxy note n7000
Click to expand...
Click to collapse
It could be an incompatibility with the ROM you are using. Soe ROMs just do not like their core components messed with.
Try a different ROM. See if you get better results.
samsung galaxy s4 gt-i9500
Skipjacks said:
It could be an incompatibility with the ROM you are using. Soe ROMs just do not like their core components messed with.
Try a different ROM. See if you get better results.
Click to expand...
Click to collapse
as i said I ONLY AND ONLY TRY ROMS FROM THE THREAD OF THE GT-I9500 {THE INTERNATIONAL VERSION} NOT TTHE 95005 IN AVY VERSION. having said that, and i mentioned earlier i tried the wanamlite, the cobra and the phoenix and the crash. and for some reason only the crash was stable enough and yet i read a ton of replies of satisfied users so i come back why me- THANKS
system ui crash
exlaval said:
as i said I ONLY AND ONLY TRY ROMS FROM THE THREAD OF THE GT-I9500 {THE INTERNATIONAL VERSION} NOT TTHE 95005 IN AVY VERSION. having said that, and i mentioned earlier i tried the wanamlite, the cobra and the phoenix and the crash. and for some reason only the crash was stable enough and yet i read a ton of replies of satisfied users so i come back why me- THANKS
Click to expand...
Click to collapse
i've tried ALL CUSTOM ROMS everysingle one of them causes the same error, somehow the size of the screen grows TALLER and there is no space left for the status bar.
something causes the screen size to enlarge, is there a spec in the developer page that may cause this?
anyone, thanks
Are the errors coming after you installed the actual framework, or after you install a module?
framework causes system ui stop
Lennyz1988 said:
Are the errors coming after you installed the actual framework, or after you install a module?
Click to expand...
Click to collapse
i install the framework and then it asks for a reboot, during the reboot and at the restart i keep getting the "system ui has stopped" error, i can make it go away ONLY by removing the framework , i have a couple of aps that have a "restart UI" option even this doesn't work either.
at this moment, i am in the modules, page and at the top i have the message "the latest version of xposed currently not active, did you install the framework and reboot"? if i go into the framework, press install and then reboot, at reboot i get the error message, ALWAYS
any ideas, really puzzled
thanks for your time, much appreciated
What are the excact steps you take for installing Xposed? And what version are you using?
xposed installer
Lennyz1988 said:
What are the excact steps you take for installing Xposed? And what version are you using?
Click to expand...
Click to collapse
first off thank you so much for taking the time to try to help, very very much appreciated, now this being said
i installed arrow rom v10 android 4.3 ubuemk1
in it there's an option in the settings page that has the xposed installer framework by going in it , it says thre are 46 app_process bundled and 42 xposedbridge.jar and active none,
i click on install/update and do the soft reboot, period, at this moment and after the reboot, i notice that the homepage is slightly taller and thre's no space for the status bar, and i presume that's the reason i get the "system ui has stopped" error. i can't imagine what setup causes the change in dimentions
btw i use apex as launcher. but that also happened with the standard (i forget the name) android launcher
i can undo the system ui error by going into the same settings page and removing the framework install
and that's it, i can't tell what framework version it's installing,, but know how frustrating this is, i just don't feel like dwelling further on it by trrying to find out what version that is, i hope you understand and just to put you in the proper frame of mind, let me tell you that i am 70 and at times the excess info becomes at times a bit overwhelming, i try to keep up but not been very versed in programming it becomes at times a bit hard
thanks so so much for your time and i hope we can find the root of this
exlaval said:
it says thre are 46 app_process bundled and 42 xposedbridge.jar and active none,
Click to expand...
Click to collapse
Thats not correct. If you The bundled part is correct, but the active part is missing. It should also say 46 app_process bundled and 42 xposedbridge.jar.
Are you sure it has root acces? Check Supersu. And you start with an absolute fresh rom? No backups restored from any app etc.
Can you post the log of Xposed here? After you installed the framework you can go to the main menu of Xposed and there is the log.
xposed, not really
Lennyz1988 said:
Thats not correct. If you The bundled part is correct, but the active part is missing. It should also say 46 app_process bundled and 42 xposedbridge.jar.
Are you sure it has root acces? Check Supersu. And you start with an absolute fresh rom? No backups restored from any app etc.
Can you post the log of Xposed here? After you installed the framework you can go to the main menu of Xposed and there is the log.
Click to expand...
Click to collapse
first off, thank you for the effort, truly appreciated
second, checked su and xposed is listed
third the version that came with arrow v11. is 2.3.1
fourth i went thru every single option in xposed and can't find the log. in a previous rom i remember seeing it, but in this one i have framework, modules, download, settings, about, under settings there's only the option to allow downloads, and under framework if i allow the install which brings in the actual modules numbers under the active column and reboot at this point i get the system ui stop error and have to uninstall it in order to get the status bar back on the screen
matter of fact y'day i downloaded the new arrow v11 and before installing it i did a wipe system and the rom install does the wipe cache, and dalvik so we're starting with a fully clean slate, even further in previous custom roms install i went even further by doing a full system reset
nothing helps, i always wind up with the same system ui stop. i returns my apps with a titanium apps restore after wiping the user data erase.
i must must be doing somthing wrong or must have a setting somewhere else that is interfering with xposed, i have in dev pate the msaa ticked and the turn off hardware overlays also ticked. those are the ONLY AND ONLY settings that i have outside the apex basic drawers settings.
thanks so much for your help, also let me know how i can locate the log in the actual physical location in the drive, not only just be able to read it
xposed, not really
exlaval said:
first off, thank you for the effort, truly appreciated
second, checked su and xposed is listed
third the version that came with arrow v11. is 2.3.1
fourth i went thru every single option in xposed and can't find the log. in a previous rom i remember seeing it, but in this one i have framework, modules, download, settings, about, under settings there's only the option to allow downloads, and under framework if i allow the install which brings in the actual modules numbers under the active column and reboot at this point i get the system ui stop error and have to uninstall it in order to get the status bar back on the screen
matter of fact y'day i downloaded the new arrow v11 and before installing it i did a wipe system and the rom install does the wipe cache, and dalvik so we're starting with a fully clean slate, even further in previous custom roms install i went even further by doing a full system reset
nothing helps, i always wind up with the same system ui stop. i returns my apps with a titanium apps restore after wiping the user data erase.
i must must be doing somthing wrong or must have a setting somewhere else that is interfering with xposed, i have in dev pate the msaa ticked and the turn off hardware overlays also ticked. those are the ONLY AND ONLY settings that i have outside the apex basic drawers settings.
thanks so much for your help, also let me know how i can locate the log in the actual physical location in the drive, not only just be able to read it
Click to expand...
Click to collapse
hi
i reinstalled xposed and as predicted it caused the system ui to stop as usual but this time i got a log which i attached, i am keeping my fingers crossed that someone will be able to decipher it and provide a clue as to what i am doing wrong
thanks so much for anyone's help- btw the file reads well in Word
I was having the same issue using the Stock Launcher on GPE 4.4 android. Using another launcher I didn't get the issue. You might want to disable all modules and reboot to see if the issue goes away, then enable one by one to see what module is causing the issue.
nailed it on the headq
dratsablive said:
I was having the same issue using the Stock Launcher on GPE 4.4 android. Using another launcher I didn't get the issue. You might want to disable all modules and reboot to see if the issue goes away, then enable one by one to see what module is causing the issue.
Click to expand...
Click to collapse
hi and thank you so much for resolving the mystery
i was hung up on using Apex and decided to remove Apex and used Nova, and followed your advice. and lo and behold i can activate Xposed and started by activating Wanam and still no problem then i checked the 3 dots and here i got the System UI stopped error, unchecked it and problem gone so it was the 3 dots.
i don't know if also the 3 dots were causing the problem in combination with Apex, but funny story with Apex even though i got the system ui stopped error, which in theory would cause the complete disactivation of all the modules, the 3 dots module DID work WITHOUT the xposed being activated. i am no planning to go back to apex to check the 3 dots thing, not by a million shot.
also nova does not by itself give the transparent system bar option, i found another module that give that option, so i am finally putting that baby to rest and move on.
thank you so much for coming with the PERFECT ADVICE that really made my day, truly very very much appreciated
Thank you!
exlaval said:
hi and thank you so much for resolving the mystery
i was hung up on using Apex and decided to remove Apex and used Nova, and followed your advice. and lo and behold i can activate Xposed and started by activating Wanam and still no problem then i checked the 3 dots and here i got the System UI stopped error, unchecked it and problem gone so it was the 3 dots.
i don't know if also the 3 dots were causing the problem in combination with Apex, but funny story with Apex even though i got the system ui stopped error, which in theory would cause the complete disactivation of all the modules, the 3 dots module DID work WITHOUT the xposed being activated. i am no planning to go back to apex to check the 3 dots thing, not by a million shot.
also nova does not by itself give the transparent system bar option, i found another module that give that option, so i am finally putting that baby to rest and move on.
thank you so much for coming with the PERFECT ADVICE that really made my day, truly very very much appreciated
Click to expand...
Click to collapse
I was having the same problem. Thank god you guys figured it out! Sure enough I disabled 3 dots and I stopped getting the UI fc.
yeah not unique
silrosriv said:
I was having the same problem. Thank god you guys figured it out! Sure enough I disabled 3 dots and I stopped getting the UI fc.
Click to expand...
Click to collapse
up until your message i was sure i was the only and only noob (or dumb) with this problem, you made me feel so not alone and happy it helped someone else this also made my day
exlaval said:
up until your message i was sure i was the only and only noob (or dumb) with this problem, you made me feel so not alone and happy it helped someone else this also made my day
Click to expand...
Click to collapse
I'm a noob to my s4. I was flashing daily on my s2 and weekly on my note 2. It's easier when you have a custom recovery and the stock rom as backup. And since there are no custom recoveries for our s4 I don't want to take the risk of flashing addons. Apk's I don't mind.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
exlaval said:
i've tried ALL CUSTOM ROMS everysingle one of them causes the same error, somehow the size of the screen grows TALLER and there is no space left for the status bar.
something causes the screen size to enlarge, is there a spec in the developer page that may cause this?
anyone, thanks
Click to expand...
Click to collapse
dunno if you fixed it but have you tried cm?
i am getting the same error after installing a module "cyan lockscreen"... im having custom marshmallow rom.. need help!!!
Howdy,
I got a new Note 4 from Bell Mobility about a month ago...
I updated the software, rooted it and installed the Wanam modified Xposed framework.
I have lost the automatic rotation, except for the built in camera software. Nothing else will auto-rotate. Checked the gyroscope and checked a few 'leveler' applications - all tests pass. Oddly I noticed the camera software still auto-rotates, no idea why it is special.
I tried the Wanam Xposed module to 'Enable all rotation angles' it has made no difference. With screen rotation software, currently have "Rotation - Orientation Manager by Pranav Pandey" installed. Auto-Rotate On and Forced Auto-Rotate neither option will rotate the screen when I turn my phone. If I choose Forced Landscape, it will go into Landscape mode. The only way to return to Portrait though is to use one of the Force Portrait options though.
My other issue is with turning on Device Encryption... Using SuperSU Pro for su..
If I just go through the prompts without changing anything, it reboots but doesn't encrypt.
First I tried installing as a system app so I could use the Disable function in the Android Application Manager, as I did with my Note 2, SuperSU tells me "Not (currently) available in system-less root mode".
If I turn off "Enable Superuser" in SuperSU, encryption enables properly, but I am unable to turn the "Enable Superuser" again, it says it has to update, but the fails. Suggests a reboot and try again. Sadly, this did not help.
I had success with one of the exploit root methods, KingRoot. While this worked when my phone was encrypted, it wasn't stable and kept popping up stuff. I tried to replace it with SuperSU, there are a few guides written to do just that, but they all indicate that it is very hard to get rid of, regardless, none of the guides worked for me. I ended up resetting the phone and starting over...
I tried the CLI command to start the device encryption from a # prompt..
vdc cryptfs enablecrypto inplace password 1234567890abcdef
The phone rebooted a couple times, but took a very long time (hour plus) to come back to the Android Lock-Screen.. But still a non-encrypted device. If I intrupted the process because I thought it had crashed, it started up and immediately told me something when wrong with the encryption and I need to use Recovery to reset the device..
As for root methods, I was using the CF-Auto-Root at first, trying to look for solutions to both issues, I tried a few ways of getting SuperSU installed.. The last time I reset I tried the "SkipSoft Unified Android Toolkit" method. 'Grasping at straws' to get SuperSU installed into /system so can use the Applicaiton Manager to disable and enable it...
My mobile's specifics, if it matters..
Samsung Galaxy Note 4
Model number - SM-N910W8
Android Version 5.1.1
Baseband version - N910W8VLU1COK3
Build number - LMY47X.N910W8VLU1COK3
Currently have the Team Win Recovery Project v2.8.7.0 recovery software installed.
I am looking for suggestions for both issues, but really want to avoid resetting the phone if I can at all possible... Yes, I have Titanium Backup Pro installed, but have never actually gotten a restore to properly restore all my applications and data... I rely on it now just for the Uninstall and Freeze features.
For an update,
I also noticed that rotation works on the Lock Screen and in the camera applicaiton.
If I rotate my screen on the Lock Screen, the red handset picture and camera icons rotate.
If I rotate in the camera application, nothing changes position, but all the icons rotate as well.
I'm still completely stuck though, open to suggestions...
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
uchihakurtz said:
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
Click to expand...
Click to collapse
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
kevinds said:
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
Click to expand...
Click to collapse
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
kevinds said:
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
Click to expand...
Click to collapse
This is amazing, can you please post the odin flashable file? I am having this exact problem right now because I removed it in TB. Is it just the facebook file that are flashed? Thanks so much in advance, you're saving my life here
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
Root same way as you rooted marshmallow. Flash twrp, flash supersu 2.79. everything is the same. it will take a while to boot though be patient.
Flash TWRP in Odin
Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
no its not working......After install recovery stuck in Samsung Flashing logo....
TWRP is making the devices get stuck on Samsung logo....
I think what is happening is that when you install only the twrp the encryption of the device conflicts and leaves in bootoolp. When you install twrp and root , root already comes with a tool that takes out the encryption. But if you just want twrp, as was my case, you should, first of all, on your own twrp, wipe data and then flash no-verity-opt-encrypt.
Having root and no encryption sucks. Think I'll wait
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
sriszone said:
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
Click to expand...
Click to collapse
You can root but you have to disable encryption. Not a fan of that personally so I'll wait for another solution. If I lose my phone at least I'll have secure power up enabled. There is no bypassing that. There are too many FRP exploits on Youtube so having no encryption and simply a password isn't enough in my opinion.
---------- Post added at 10:29 PM ---------- Previous post was at 10:29 PM ----------
Mystero said:
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
Click to expand...
Click to collapse
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Galactus said:
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Click to expand...
Click to collapse
Hi, i cannot manage to unistall S Health, tried already two apps, after reboot app is still there and if i try to install older version i get corrupted file error.
guys please explain what is encryption and unencription here.... how can i disable ? can we flash this no-verity-opt-encrypt-5.0.zip
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
I got fully working root and TWRP on Nougat G935FXXU1DPLT.
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
Mystero said:
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
Click to expand...
Click to collapse
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
CuBz90 said:
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
Click to expand...
Click to collapse
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Mystero said:
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Click to expand...
Click to collapse
Try titanium. Backup the app first and then uninstall.
CuBz90 said:
Try titanium. Backup the app first and then uninstall.
Click to expand...
Click to collapse
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Mystero said:
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Click to expand...
Click to collapse
i have tried to remove the s health app with titanium but everytime i try to install vesrion 4.8 phone says that i can not install this app beacuse there is a package with the same name
what verison did you install before s health 5 and how did you install it.
and can anyone tell me how do i make lucky patcher to work properly
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