Related
This thread is for SuperSU releases that are still in testing, and are not yet available through the Play store. The main thread for stable SuperSU releases is located here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703. The changelogs are in the old release thread.
Please keep track of the version numbers in the thread titles, as the latest test release may not always be newer than the latest stable release.
The latest test release is:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
RELEASE NOTES
That is a recovery flashable ZIP (I recommend FlashFire or TWRP). If you want to install via APK, it is also present inside the ZIP, in the common folder.
--- reserved ---
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
StupidIdea said:
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
Click to expand...
Click to collapse
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Chainfire said:
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Click to expand...
Click to collapse
No pressure. Its up to you if you decide to publish it before L release or not but I will be glad to test it on L and report if functions that I use in my apps work with it. As for xposed in theory these 5 points rovo89 posted should work with "permissive" but I guess he will verify it himself.
Of topic: I understand its beyond su binary but did you even thought about adding an option to start activity in system or root process? Benefits are simpler interaction with system services and improved service life (faster restarts). Let me know if question is not clear.
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
cioce said:
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
Click to expand...
Click to collapse
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Have you tried completely removing the com.sec.knox.seandroid package from your device?
MasterMind33 said:
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
Click to expand...
Click to collapse
The reason device default theme is not selected by default is because a lot of OEMs have some godawful themes set by default that everybody would nag me about ...
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
MikeRL100 said:
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
Click to expand...
Click to collapse
#realworldproblems
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Chainfire said:
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Click to expand...
Click to collapse
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Chainfire said:
Have you tried completely removing the com.sec.knox.seandroid package from your device?
Click to expand...
Click to collapse
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
cioce said:
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Click to expand...
Click to collapse
I'm not talking about not having root at all. The problem (as I understand it) is caused by having any packages at all in a "disabled" state. This may ultimately cause a crash which triggers a reboot.
At the same time, keeping that package enabled in combination with root, will break various root commands, which you may not even notice (root apps will just appear to randomly fail and be unreliable) which in turn is also known to cause reboots.
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
Click to expand...
Click to collapse
Just because you haven't noticed the issue doesn't mean it isn't there. As for using it, having root prevents KNOX from working anyway.
...
The point is, solving this problem is not as easy as making that popup optional.
dhampire said:
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Click to expand...
Click to collapse
Please clarify what happens in the following circumstances:
- in-app binary update: normal, and reboot
Keeps saying binary needs updating? Or also results in bootloop?
- in-app binary update: TWRP/CWM
Bootloop?
- latest flashable ZIP with TWRP/CWM
Also bootloop?
It's strange if they don't all result in bootloops...
I know testing is very annoying for you because you need to reflash your system every failed test, but if you want to help solve this problem it's going to require some work.
First test:
- If you have SuperSU 1.94 installed, use the "full unroot" option from settings to remove it.
- Reboot into CWM/TWRP
- Install the latest BETA ZIP but do not reboot
- Adb shell into the device
- "mount /system"
- "ls -l /system/xbin/*su*", post the output here
- "ls -lZ /system/xbin/*su*", post the output here
- Remove /system/app/Superuser.apk
- Reboot into Android
- See if there is a bootloop
Sorry for my poor english. not bootloop. never bootloop. but su binary update loop -> need su binary update again on every boot after update su binary....continue...keep saying need update.
---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
If 1.9.4, there are no problem like that. but only twrp use su binaly update. normal update makes unroot.
dhampire said:
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
Click to expand...
Click to collapse
Not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
dhampire said:
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
Click to expand...
Click to collapse
Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
...
Please:
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Frank
Frank Westlake said:
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Click to expand...
Click to collapse
No it was not a busybox issue, it was an odd bug somewhere in the binary
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
dhampire said:
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
Click to expand...
Click to collapse
Please confirm the app actually says 2.06
This logcat does not list the output I expect. Did you open SuperSU again after rebooting?
How did you make the logcat? "adb logcat > logcat.txt" ?
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
newuzer1 said:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
Click to expand...
Click to collapse
Do you have TWRP installed? If so try to get it to reflash the binaries again.
mjones73 said:
Do you have TWRP installed? If so try to get it to reflash the binaries again.
Click to expand...
Click to collapse
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
newuzer1 said:
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
Click to expand...
Click to collapse
I would assume not installing the SuperSU binary updates correctly broke SuperSU. You didn't lose root per say, you broke SuperSU which apps need to be able to run as root.
I downgraded my Xperia M2 dual d2302 to 4.3 and rooted with towelroot and then flash 4.4.4 followed by flashtool force towelroot using super su. This would uninstall super su on my phone and install its own super su binaries and busybox content. The super su pro would however, remain installed. So, I would have to redownload the super su and as soon as i would open it, it would ask for binary update and then ask for reboot. I would just follow the prompt without question. As soon as it reboots,though the root would be there but sd card and system rewriteable will be gone and there is no way to make my system rewriteable without flashtool reflashing back to 4.3 and following the long procedure. I till now, would blame kitkat and sony for that. This continued for over 8 days till I realised that the real culprit was not sony or kitkat but super su binary update followed by reboot. This is highly anoying. What is the point of root if system or sd card writing is not allowed? For now, I am living with super su by canceling the binary update everytime I open it. I have OCD and I find it highly annoying. I tried searching for an option to cancel auto search for updates bur in vain. My phone works just fine without update. I need no updates and need a way to stop super su asking for update everytime. Please suggest me something.
I have now discovered that even if I cancel binary updates, supersu auto updates causing the same problem. So, now I have decided to live without Supersu as supersu is not needed for root. I have an unlimited root access for all my apps which have root permission now and to add icing to the cake, my bootloader is locked. If anyone else is searching for a way to make Sony Xperia M2 dual 4.4.4 system writebale without unlocking bootloader, just follow:
LOCKED BOOTLOADER
1. Downgrade to JB, Root your Phone using Towel Root in Jelly Bean
2. Update via OTA to KK 4.4.2 or KK 4.4.4 whatever you need (4.4.4 is recommended)
3. In this process, don't try to install or uninstall anything
4. Wait for booting finish
5. Install latest SuperSU from Play Store
6. Open Flashtool in PC
7. Connect your phone to PC
8. Now flashtool will describe your phone information, then click Root Tab in top, after that choose force root by TowelRoot
And after this, do not install supersu or any other root control app. Just let your phone be as such without updating binaries or anything and you will have root. You will have unrestricted root on Xperia M2 dual, Enjoy and remember not to install supersu, kingsu, cm superuser or any similar app.
I was thinking to help you, but then i was worried if something else goes wrong, then you will blame me, just like you blame super su.
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
gauthamraob said:
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
Click to expand...
Click to collapse
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
---------- Post added at 02:42 PM ---------- Previous post was at 02:31 PM ----------
BTW, tell us what do you need on your device that will make you feel better. (About the superuser @ root thing of course)
NeoLogY said:
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
Click to expand...
Click to collapse
No, I am already having root . I have integrated most of the updates to my system app to my sys/app folder through lucky patcher and have installed the modded play store . I can even edit and delete system files in "ES explorer" file manager and stop items from startup using "all-in-one-toolbox" boot manager. I have an older version of su binaries which was installed automatically into my phone by "flashtool by androxide" using the force root mode using towel root :good: . But the supersu app was not installed and if the app existed before rooting, flashtool would uninstall it and also replace the new su binaries with an older version ! So, I already have full root access without the supersu app.
As far as i know, supersu is not needed for root. It is only a gatekeeper app which restricts the unlimited access of root to any app by making the apps that need root to ask for permission first. Without supersu installed, root apps get root access without asking permission provided binaries (any version) are already present. Also, for normal people who don't know or can't install binaries directly, they rely on apps like supersu, CM etc for installing the binaries. But once the binaries are installed, the supersu app is no longer needed for root (except in cases of OTA updates or updation of binary to a newer version) but instead works as a security guard for root.
Edit:
What I want is a way to make supersu submissive and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like.
What I want is a way to make supersu submissive to my command and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like and must not be done
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
NeoLogY said:
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
Click to expand...
Click to collapse
At present I am using my phone without supersu as I will have to spend a lot of time downgrading to 4.3 and then rooting followed by painfully slow 4 OTAs in succession (there is no single direct OTA from 4.3 to 4.4.4 on Xperia M2 dual, unfortunately :crying: ) followed by installation of all my apps. I too wish there was a fix for supersu but the time I'll have to spend on that will be enormous and also considering that in this september my phone will mostly get lollipop 5.1, the 4.4.4 woes will soon be history.
Also, I want to mention that I haven't unlocked my bootloader yet. If I unlock my bootloader, all these problems with supersu will vanish. The actual difficulty I am facing is because there is no single post on the internet that says how to get system to be rewriteable without unlocking bootloader in Xperia M2 devices. Every post I have read of only has people with unlocked bootloader saying what to do and people with locked bootloader complaining that they aren't able to make their system rewriteable. I am probably one of those rare people who managed to get complete root with locked bootloader and hence facing the issue of lack of peer help.
Anyways, I really appreciate your interest shown in helping me. If I ever have to update my binaries in the future I will definitely take a log of it and pm it to you in case similar situation arises.
Cheers.
Same thanks to you. Actually, i think it is better to put the log here, as more hands and mind will be able to reach it, meaning higher percentage on discovering any hidden in the log. You are right about the lock bootloader, even until now i still unable to manage to truely understand about bootloader, as i didn't have any device with it to get inhand with the system. As always, i do appreciate any kinda knowledge exchange. Thanks in any way.
That's exactly why your system is read only and you can't move apps/data to sd ect without supersu installed and the binaries updated and Sony ric killed you don't have full root r/w access to system. The way you have rooted your device is the same way I did mine it's the easiest way there is if you can't get it right doing that way then maybe you should put your Phone back to stock. Flash jb, root with towelroot apk(at this point do not update anything), now update over the air to 4.4.2 then again to 4.4.4(again update nothing but phone)root will stick after each update. Download supersu connect your phone to flashtool and click on the force root tab(kills Sony ric installs supersu binaries and busybox) making system r/w
Search on here for the m2 forum if you still have problems
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
I rooted my LG g3 (stock Lollipop) and flashed Supersu. It's been working well for some time, but lately, Supersu seems to be uninstalled (?) by the system, denying then root access to my apps (sd maid, titanium... ). What i do then is flash supersu again from TWRP , and all is back to normal... Untill Supersu is uninstalled again...
Is there anything i should do to avoid that? I'm thinking about installing Supersu as a system app. Would that matter?
Sent from this galaxy
pr1jker said:
I rooted my LG g3 (stock Lollipop) and flashed Supersu. It's been working well for some time, but lately, Supersu seems to be uninstalled (?) by the system, denying then root access to my apps (sd maid, titanium... ). What i do then is flash supersu again from TWRP , and all is back to normal... Untill Supersu is uninstalled again...
Is there anything i should do to avoid that? I'm thinking about installing Supersu as a system app. Would that matter? Sent from this galaxy
Click to expand...
Click to collapse
Your best bet is to post this question within the following thread.
https://forum.xda-developers.com/showthread.php?t=2947298
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
pr1jker said:
I rooted my LG g3 (stock Lollipop) and flashed Supersu. It's been working well for some time, but lately, Supersu seems to be uninstalled (?) by the system, denying then root access to my apps (sd maid, titanium... ). What i do then is flash supersu again from TWRP , and all is back to normal... Untill Supersu is uninstalled again...
Is there anything i should do to avoid that? I'm thinking about installing Supersu as a system app. Would that matter?
Sent from this galaxy
Click to expand...
Click to collapse
I have seen this on several Android 5.1 based systems following the release of SuperSU 2.7.9. I don't know if the most recent builds (2.8.2 SR5 as of this post) solved it. In my case I either reverted to the native root solution (for CM/Lineage based ROMs) or fell back to SuperSU 2.7.6
Hi,
I came across a bug that might be related to Magisk and the boot.img patch.(see below for details)
Pixel 3 with latest October Q firmware and root.
Error message: Device personalization crashed when trying to type or get a notification from the default sms app after a Boot.img patch by Magisk
Steps to reproduce:
I install the latest official October rom
I write something in the default SMS app, no problem
I patch the boot.img via magisk (canary channel)
I patch the boot with modified boot.img on my phone and gain root and Magisk full functionalities.
Now, any access to the sms app or even a notification to it ends up with a crash. stating that device personalization has crashed
No other apps seem to have the same problem.
If I revert to the original Boot.img, I don"t have a problem anymore
Previous Q rom didn't generate such error
IT might be related to the way Magisk patches boot.img? Or some security ?
Hope It can help to find a solution.
Thanks
That's odd . I'm on latest Q, pixel 3 , rooted. I don't have this issue . Have you tried force closing the app and starting again?
Sent from my Pixel 3 using Tapatalk
Xdevillived666 said:
That's odd . I'm on latest Q, pixel 3 , rooted. I don't have this issue . Have you tried force closing the app and starting again?
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Yes,
I tried to kill it, to clean cache, uninstall/re install( well update in this case), always the same result.
The only 2 things I didn't try:
- Do a clean full install of the rom and not an update from September's Q release
- Disable Swiftkey,
I'll try to check that later today