so im completely lost. after flashing a new rom yesterday, custumizing i have seem to have "lost root". superuser was working fine and i was doing things that require root. today it just stops working and i cant get root access on anything. i installed a root checker and it says i dont have root. what gives? so i was rooted yesterday and today im magically not rooted? should i just start all over and root my phone again using de la vegas tool? any suggestions to what the problem and solution will be greatly appreciated
by the way this has happened to me on quite number of roms but not to this extent where i literally have no root acess. on the other roms superuser just decided it didnt want to work anymore and i was able to fix it by unistalling it and installing a different superuser. but know i can even uninstall this one since it built into the system and you need root to unistall/delete the apk
Sent from my SM-N900T using XDA Premium 4 mobile app
Friend of mine just lost root on his Note 3 too. I wanted to show him some program requiring root and he was surprised he had no root anymore. Could be some Samsung silent update?
After you flash you lose root. That's how it is. Unless you use custom ROM that it's rooted by default. If you flashed Stock Rom, just go ahead and root it again.
Sent from my SM-N9005 using Tapatalk
You may have to reinstall super user and / or make super user a systems app. See screen shot from super user
Sent from my rooted Note 3 (N900T) using XDA Premium
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
ex-28 said:
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
Click to expand...
Click to collapse
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
@rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
FYI, on my stock AT&T S5 I had S Health "go bad" a little bit, finishing building a Samsung ID and updating it from their store fixed it.
Don't know if that helps or not, just a data point.
ex-28 said:
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
Click to expand...
Click to collapse
You forgot to use the @ to mention @rovo89.
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Greycloak42 said:
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Click to expand...
Click to collapse
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
Xeio said:
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
Click to expand...
Click to collapse
so you have s health running with xposed or wanam installed ?
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
siyue78 said:
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
Click to expand...
Click to collapse
I don't think root is the problem , as my phone and many others arerooted with twrp installed and shealth was working 100 % something to do with the xposed and / or wanam
divineiniquity said:
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Click to expand...
Click to collapse
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
after you reinstalled s health is it running ok now with xposed installed ? if so could you please give more details on the steps you took and it is just xposed or wanam you have
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yah it took me a while to get s health working again as well , hoping for a fix soon.
Can confirm this on a Sprint S5. Rooted with chainfire autoroot and installed xposed and TWRP 2.7 and had S Health and Healthservices crashing like a drunk teenager. Uninstalled xposed and rebooted, S health now works. Guess I have to sit through Youtube ads for a while.
Ahh... Thought the problem was only for me. Hope @rovo89 could fix it soon.
may be can help to find the problem
hi everybody, i am a noob in android ect, BUT maybe it can help you : i am on i9500 omegaV20 perseus18, i modded my phones with root explorer, i add libs, perms, framework ect, modify my build prop /SM-G900F/kltexx/jfltexx , i did a lot of upgrade in samsung app store, AND I GOT S5 APPs WORK perfect, health widget work ect all works, and i got xposed ...
so to resume : i got S5 healths WORKING perfectly with xposed. hope it can help you.
Yup I also installed a different rom all working great now
Sent from my Sm-G900W8 using Tapatalk
I had the same concern, and after installing a new firmware on the SM-G900f .
I took the opportunity to not do the update shealth and securestorage..I can enjoy and wanam, Xposed
no problems with health
Short hand is that I deperately want the 4k camera upgrade, but can't stay rooted since I use my phone for work. Can I load a stock rooted (Sprint) rom, update the camera, and the use SuperSU to unroot? Would the camera still work or would it just fail to launch after root is killed?
Thanks!
Gonz
drgonzo1337 said:
Short hand is that I deperately want the 4k camera upgrade, but can't stay rooted since I use my phone for work. Can I load a stock rooted (Sprint) rom, update the camera, and the use SuperSU to unroot? Would the camera still work or would it just fail to launch after root is killed?
Thanks!
Gonz
Click to expand...
Click to collapse
well it should work after it's unrooted but that's kind of a gamble there, why can't you have your phone rooted as long as you don't do anything with root except camera than you can hide the su app/download an app that hides root
XxZombiePikachu said:
well it should work after it's unrooted but that's kind of a gamble there, why can't you have your phone rooted as long as you don't do anything with root except camera than you can hide the su app/download an app that hides root
Click to expand...
Click to collapse
Looks like rootcloak might do the trick. Didn't know it existed so thanks for the assist! ? Just hope our MDM solution isn't overly sneaky.
Gonz
Hey guys, sorry if I'm posting to the wrong thread. When using Amplify on my rooted 6p on marshmallow, I had no issues with it. App was running fine. After upgrading to nougat and rooting my phone, the app says that my device is not rooted. However, root checker says my device is rooted and all my other root apps (greenify, titanium back up, kernel adiuter etc) all work fine. Any ideas as to why Amplify says that my phone isn't rooted?
youarescientist said:
Hey guys, sorry if I'm posting to the wrong thread. When using Amplify on my rooted 6p on marshmallow, I had no issues with it. App was running fine. After upgrading to nougat and rooting my phone, the app says that my device is not rooted. However, root checker says my device is rooted and all my other root apps (greenify, titanium back up, kernel adiuter etc) all work fine. Any ideas as to why Amplify says that my phone isn't rooted?
Click to expand...
Click to collapse
Have you set all required permissions for amplify? Some apps just don't ask on MM and N.
youarescientist said:
Hey guys, sorry if I'm posting to the wrong thread. When using Amplify on my rooted 6p on marshmallow, I had no issues with it. App was running fine. After upgrading to nougat and rooting my phone, the app says that my device is not rooted. However, root checker says my device is rooted and all my other root apps (greenify, titanium back up, kernel adiuter etc) all work fine. Any ideas as to why Amplify says that my phone isn't rooted?
Click to expand...
Click to collapse
Isn't Amplify an Xposed module? Xposed doesn't work yet on 7.0.
Sent from my Nexus 5X using Tapatalk
Amplify is an Xposed module and Xposed is not on Android 7 yet, if ever.. Also I noticed if you have your root in "system-less" mode it can cause this problem with amplify.
Hi.
I currently have a nexus 6p running Android 7.1.2 thats rooted. I am currently not able to sign into my snapchat and other apps. Is there anyway of bypassing without using xposed (not supported yet)? Let me know.
Zyhto said:
Hi.
I currently have a nexus 6p running Android 7.1.2 thats rooted. I am currently not able to sign into my snapchat and other apps. Is there anyway of bypassing without using xposed (not supported yet)? Let me know.
Click to expand...
Click to collapse
Either use magisk root with magisk hide OR unroot your device, sign into Snapchat, re root your device.
Hiding with Magisk doesn't work last I checked. Which was a few weeks ago. You'll need to be unrooted to sign in. After that you're good. I'd suggest making a backup with Titanium so you won't have to deal with signing in again, should you be signed out for whatever reason.