Related
Please already tried looking in various places and couldn't find anything to help me.
Got the Galaxy S5, before I wore only the S3, my problem with the S5 is that I can't update the S-Health, when I do a message pops up saying you must also update the Health Service, when I do this the S-Health crashes.
Just after returning all factory settings S-Health back to work without the update.
Use the Gear Fit and when using S3 with Fitness with Gear there was this problem, could show the data in the pedometer, exercise and heartbeats without problems.
Can someone help me? SM-G900M stok version 4.4.2
rickaoi said:
Please already tried looking in various places and couldn't find anything to help me.
Got the Galaxy S5, before I wore only the S3, my problem with the S5 is that I can't update the S-Health, when I do a message pops up saying you must also update the Health Service, when I do this the S-Health crashes.
Just after returning all factory settings S-Health back to work without the update.
Use the Gear Fit and when using S3 with Fitness with Gear there was this problem, could show the data in the pedometer, exercise and heartbeats without problems.
Can someone help me? SM-G900M stok version 4.4.2
Click to expand...
Click to collapse
Try updating it directly in Samsung Apps.
drakester09 said:
Try updating it directly in Samsung Apps.
Click to expand...
Click to collapse
already did that, did not work, always gives the same problem.
Usually the update also requires you to update the s health service, have you tried searching for the s health service and updating manually?
Also if you are using xposed or rooted you gotta change a line in build.prop, let me know if you are and I'll search for it.
Sent from my SM-G900H using Tapatalk
drakester09 said:
Usually the update also requires you to update the s health service, have you tried searching for the s health service and updating manually?
Also if you are using xposed or rooted you gotta change a line in build.prop, let me know if you are and I'll search for it.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Yes, I use root and Xposed
Set these two lines since we no longer have Knox and Private Mode won't work.
Code:
ro.config.tima=0
ro.securestorage.support=false
Search for them in build.prop and change the values to those.
drakester09 said:
Set these two lines since we no longer have Knox and Private Mode won't work.
Code:
ro.config.tima=0
ro.securestorage.support=false
Search for them in build.prop and change the values to those.
Click to expand...
Click to collapse
Thanks for the help, but I couldn't make it work. I Give Up.
rickaoi said:
Thanks for the help, but I couldn't make it work. I Give Up.
Click to expand...
Click to collapse
Rooting the phone breaks the S-Health app and the associated services, because the Knox counter is tripped.
You can use the Rom posted here and the add-on package it has in the second post and that will put the apps back on to it. Hopefully that helps.
luriert said:
Rooting the phone breaks the S-Health app and the associated services, because the Knox counter is tripped.
You can use the Rom posted here and the add-on package it has in the second post and that will put the apps back on to it. Hopefully that helps.
Click to expand...
Click to collapse
Thanks, I keep trying.
I removed root and xposed beyond titanium backup, now shealth works perfectly
drakester09 said:
Set these two lines since we no longer have Knox and Private Mode won't work.
Code:
ro.config.tima=0
ro.securestorage.support=false
Search for them in build.prop and change the values to those.
Click to expand...
Click to collapse
Just confirming that I did this and it worked; updated my S Health and Health Service via Samsung Apps and it isn't crashing (so far).
@rickaoi: You can try searching up how to access and edit the build.prop file and make the changes suggested. Remember to reboot after making changes.
divineiniquity said:
Just confirming that I did this and it worked; updated my S Health and Health Service via Samsung Apps and it isn't crashing (so far).
@rickaoi: You can try searching up how to access and edit the build.prop file and make the changes suggested. Remember to reboot after making changes.
Click to expand...
Click to collapse
Hi, to those who still searching solution for that, this is the correct solution,
I have tried and it works on me.
Here is the guide on how to edit build.prop
http://forum.xda-developers.com/showthread.php?t=1948558
Hope it helps.
There is also an option in wanam xposed where you can get both S-Health and private mode working, there is also a separate module available.
drakester09 said:
Set these two lines since we no longer have Knox and Private Mode won't work.
Code:
ro.config.tima=0
ro.securestorage.support=false
Search for them in build.prop and change the values to those.
Click to expand...
Click to collapse
Try deleting all Knox apps and rewrite the build.prop.. Restart the phone and ready to actualize..
Hi,
I have a S5 (G900F) and I have never been able to use the heart rate sensor. S-Health app crashes every time I try to open it.
I updated to ANG9 but the issue is still there. Anyone with the same problem?
I have tried to find clues in the Logcat but there are no logs from s-health there.... :crying:
Use a build.prop editor and change "ro.securestorage.support" from true to false and then clear the cache in S Health and it will work.
Do I need to be root for that? I tried but the setting goes back to true... Thanks for the help!
Yeah you need root... But that usually only happens when you install Xposed so I assumed you already had root.
If not just go into application manager and clear cache and uninstall updates.
Did you tried the stress option? Does it works?
Inviato dal mio SM-G900F utilizzando Tapatalk
I did already the unistalling of updates with no luck...
Opening the stress crashes the app the same way
Your problem could be due to any number of reasons or conflicts. To narrow down the possibilities, backup anything that is important to you, then temporarily revert to full stock e.g. the oldest, full firmware version, followed by a factory data reset. Confirm that it works as it should barring an unlikely hardware issue.
Then install you primary apps, one by one until you presumably run into a conflict.
.
That I have already thought about. But I will try to avoid as it is very time consuming to reset and reinstall everything.
I was thinking to try to debug first. But I find kind of strange that an app crashes and there are no errors in logcat...
kulaki0 said:
That I have already thought about. But I will try to avoid as it is very time consuming to reset and reinstall everything.
Click to expand...
Click to collapse
It's also very time consuming to try and assist people who don't explicitly state their intent at the outset. There are dozens of threads that detail how to troubleshoot or reinstall shealth as a search would have revealed. It's good practice to take advantage of the wealth of information in existing threads prior to posting a query.
Why not just restore your last backup to resolve the shealth issue? That way you wouldn't need to restore 99% of your apps. Also you didn't post your logcat, build.prop, a detailed description of what changes you have made, a list of installed apps or anything else about your configuration that would aid troubleshooting.
.
Don't take me wrong, I really appreciate your help. I didn't mean to offend and I apologize if I did.
I did search and found several threads about s-health issues but they were all in custom roms or rooted phones. I am on stock rom without root. The app never worked so there is no restoring I could do. I have installed mostly regular apps (facebook, Skype, messenger, whatsapp, ebay, tradera, Amazon, momondo, booking.com) plus the Sony Smartband and Lifelog. I did install some of the apps before I tried the heart rate monitor for the first time (at least the Sony ones) because it asked to create a Samsung account and I didn't do that immediately.
I was looking at geting a dump of the logcat but seems I need root access the logcat viewer app only shows logs of itself (that explains I don't see the s-health crash info)
A similar issue with the build.prop although the app can read it I don't manage to access the file.
It looks like I really have to do the reset anyways
Resolved by a factory reset. I have installed all the apps one by one but the HR still works.
The only difference is that this time I set up the Samsung account from the beginning and tested the HR before installing anything
I have same problem with HR monitor
Mine stopped working again. So there is some app update or other app that is messing things
Yeah since the update my pedometer and heart rate monitor don't work
Hello everybody
I just updated my Nexus 4 to Lollipop 5.0.1 by wiping it and installing the factory image from Google
The most annoying bug I found is that when the UI prompts me a dialog, it doesn't work.
For example, when I try to install an APK file, this pops up (see Screenshot_2014-12-13-12-27-42.png in attachments), and I can only tap on "cancel". the "install" button doesn't work. Everything else seems to work fine, the navigation bar and scrolling the notification menu from the top of the screen give no problem whatsoever. This doesn't seem to depend on the APK file, nor on how do I send the command (I tried installing with ES file explorer, Dropbox, and an app called Easy Installer). I can't figure out a workaround, so I am unable to install APK's on the phone.
Another example are SuperSU requests (see Screenshot_2014-12-13-12-35-17.png ). Here the situation is worse: nothing in the dialog works, neither "deny", nor "grant", nor the box or the menu that read "ask again". Luckily there is an obvious workaround, as I can just open SuperSU and grant the permissions from there (the dialog in the SuperSU app seems to be proprietary and not from the Lollipop UI)
Probably useful info: I am using stock Android 5.0.1, rooted, with TWRP recovery and I installed Busybox (in /xbin).
I have no idea how to repair this. Can you give me some advice? If not, is there some workaround to the problem of installing APK's?
Thanks for the help and the attention.
P.S. This is my first post on this forum. I looked at the rules, but am new. So if I unknowingly broke some rules or posted offtopic I beg your pardon in advance. I also looked for other threads reporting the same problem, but found none.
I've read some posts where the user experienced the same or similar issues as yours. If I'm not mistaken, the issue was caused by some sort of a screen dimming software.
janedoesmith said:
I've read some posts where the user experienced the same or similar issues as yours. If I'm not mistaken, the issue was caused by some sort of a screen dimming software.
Click to expand...
Click to collapse
You were right. I was using an app called Lux 1.75 (sometimes called Lux Dash) that is an automatic screen dimmer. As soon as I stopped it, everything started working again.
Thanks a lot!
Lux Dash prevents Greenify to automate hibernate
ganileni said:
You were right. I was using an app called Lux 1.75 (sometimes called Lux Dash) that is an automatic screen dimmer. As soon as I stopped it, everything started working again.
Thanks a lot!
Click to expand...
Click to collapse
Yep- it was driving me crazy. Worked fine in KitKat but not Lollipop. Uninstalled Lux Dash and now hibernate works automatically after turning on Greenify in Accessibility.
thanks for the tip- prevented me from going crazy!!
steve
Hi All,
As usual it is the first place for me to look for help.
I updated my A5 2016 device with the latest security update. While installing, I was assured that i would be able to uninstall that update.
I couldn't.
But this is not the actual problem.
Now I am unable to grant permissions to apps like Camera, Storage etc because whenever I try to do that it says Screen Overlay Detected on which screen none of the apps are turned on including the system apps. I am really annoyed with this feature (or bug) of the Android Marshmallow. I seek your help in solving this.
I am rooted with custom Xposed ver 86.
Try unchecked all screen overlays, even system app ones? Also, there might be another screen overlay that might not hv been listed. Eg: if u hv pie with gravitybox enabled you have to disable it in the app itself.
Arathergreendroid said:
Try unchecked all screen overlays, even system app ones? Also, there might be another screen overlay that might not hv been listed. Eg: if u hv pie with gravitybox enabled you have to disable it in the app itself.
Click to expand...
Click to collapse
Thank you so much for the valuable Help.
I recently found that some of my apps crashed suddenly and that the following error popped up: Unfortunately Phone has Stopped, Unfortunately ES File Explorer Has Stopped.
After I click OK it pops up again. So in a wonderfully foolish step I uninstalled the Phone App and now the phone will not reboot.
I uninstalled Xposed but nothing helped. Finally after lots of research on XDA and otherwise I flashed The Stock Firmware for my Phone SM-A510FD.
It rebooted just as fine but now the same problem is there and is not resolved. Moreover if i Open some app like Play Books while i am getting the error, the popup of the error stops until i open the Phone app again. I opened my phone in Safe MOde and saw that the same problem is also there which means it is not caused by some third party apps. PLease help.
deepray said:
Thank you so much for the valuable Help.
I recently found that some of my apps crashed suddenly and that the following error popped up: Unfortunately Phone has Stopped, Unfortunately ES File Explorer Has Stopped.
After I click OK it pops up again. So in a wonderfully foolish step I uninstalled the Phone App and now the phone will not reboot.
I uninstalled Xposed but nothing helped. Finally after lots of research on XDA and otherwise I flashed The Stock Firmware for my Phone SM-A510FD.
It rebooted just as fine but now the same problem is there and is not resolved. Moreover if i Open some app like Play Books while i am getting the error, the popup of the error stops until i open the Phone app again. I opened my phone in Safe MOde and saw that the same problem is also there which means it is not caused by some third party apps. PLease help.
Click to expand...
Click to collapse
I seem to have found the solution for the problem regarding crashing of the Phone App. The Phone App uses Screen Overlay in which we select SIM1 or SIM2. Turning that off would result in hampering its functionality. After i did turn on the screen overlay for Phone App, it is functioning just as fine and no crashes for atleast the phone app. I wonder to what lengths i went to solve this issue and the issue lied in my thing only.
Thanks to @kryz who managed to generalize the Dirty Cow exploit, XT1528 now has a way to get temporary root : link Notice that the /system will still be read-only, but at least full access to /data is available. Given the state of XT1528, this looks like a pretty good progress!
Steps to get temp root (in Lollipop):
0) uninstall SuperSu apk if you have it installed, see thisfor the reason to uninstall
1) install Croowt.apk, use the 2nd option in the menu : "Get root"
2) install SuperSu apk from the playstore (don't update the binary)
3) install RootChecker apk from the playstore
4) enjoy temporary root (until hard reboot)
I've tested this on 5.0.2, but should probably work on 5.1.1 as well (as long as it was not patched since the end of Oct). Here is the output of Root Checker (where everything looks nice and green !) :
Device: XT1528 (MOTO E Verizon prepaid)
Android Version: 5.0.2
Additional - SELinux
Status: NOT enforcing
Status stored in /sys/fs/selinux/enforce
SuperSu works (untill hard reboot) !!!
@9acca9, @dreyeth, @Whoareyou, @bendrexl, @docna, @caspar347, @Dishe, @hp79
This is great!
Thank you @kryz
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
jcpowell said:
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
Click to expand...
Click to collapse
This looks like the old Kingroot behavior - temp root which is highly unstable. Once after a Kingroot attempt I had to factory reset the device due to the "junk" left behind, at least here it's all nice and clean ! I wonder if forcing a soft reboot right after root may help to make it more stable ... Or perhaps something else is going on ?
No idea if anyone is looking into unlocking this phone's bootloader still but hopefully this leads to it. Happened with my Droid Turbo. The initial process was use Kingroot for temp root and sunshine to unlock.
Tried sunshine and after second test it gives an error. Won't even try
jcpowell said:
Tried sunshine and after second test it gives an error. Won't even try
Click to expand...
Click to collapse
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
bibikalka said:
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
Click to expand...
Click to collapse
There is a bug if you have SuperSU is installed before get the root, the restore init function will not work properly.
So the instructions in this post should be changed, and clarify that is required uninstall it.
Also ive fixed another bug related to clean the state of the system, the apk is updated in the main post.
Really after the restore clean the phone should be in a clean state, but if supersu is installed i don't know why is denying the access to the app.
Can you check this issue please?
@kryz I'm actually finding it more unstable with the updated app.
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Idk, as soon as I attempt to use my phone after root it freezes and reboots. If I let it sit it'll last an hour at least, lol
jcpowell said:
@kryz I'm actually finding it more unstable with the updated app.
Click to expand...
Click to collapse
Let's see what's going on
-Are you using the apk or adb script?
-If you use the apk and don't restore init what happens?
-If you restore init is laggy or reboot?
-Can you try the adb script and tell me if you also get a reboot?
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Regards,
---------- Post added at 01:33 AM ---------- Previous post was at 01:16 AM ----------
fenlon said:
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Click to expand...
Click to collapse
First about the sdcard, i will look after that bug that i know what's happening,please don't remove/mount/umount for now.
Do you have a computer to do some checks?
You say that with the new version there is not reboot but laggy, can you check if there is some process eating the cpu with top:
Code:
/data/local/tmp/busybox top
I suspect there is the last process restauring init that is eating the cpu, check for this or ;
Code:
ps | grep dirtycow
If that is the case kill it and we will know if is the responsible of that lag.
In other hand can you attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Guessing that you are using the apk, what happen if you don't restore init?
Is laggy or just unstable, don't start wifi/bluetooth you can't change settings are like locked.
Have you tried the script adb version, can you try and tell me if you have the same issue?
Best regards,
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
jcpowell said:
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
Click to expand...
Click to collapse
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
kryz said:
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
Click to expand...
Click to collapse
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
jcpowell said:
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
Click to expand...
Click to collapse
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
kryz said:
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
Click to expand...
Click to collapse
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
jcpowell said:
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
Click to expand...
Click to collapse
If it reboots just checking permissions the problem is the fsck_msdos process not the shellcode in init, i saw in the files that you attach all is ok.
I've updated the apk in the main post, now it will release the sdcard, please check that version in the same way, first before get root, click "check perm" wait to see the results and work with the phone to see if reboots again for a while.
If all is working with "check perm" and you don't get reboot, try get root, is very probably that now doesn't reboot.
I think with the adb script will work because it overwrites run-as, anyways ive updated the apk for release the sdcard check process and it'll return ok status.
The instructions for the rar and adb.
First you need adb installation in your computer, i mean connectivity with the device via adb.exe.
When you have adb working you need to put all the content of the rar in the path /data/local/tmp/.
So extract the rar in your computer in a folder and with adb push copy all the files to that folder:
(in the folder of the rar contents)
Code:
adb push * /data/local/tmp/
Then get a shell with adb:
Code:
adb shell
Execute the script to exploit it:
Code:
cd /data/local/tmp
./exploit.sh
Wait the logs and if all is ok execute:
Code:
run-as -s2
Wait 5 seconds and:
Code:
su
If all is ok you will have a root shell, this method is more stable even doesn't clean the init you can do it in the app, but test all before.
That last apk causes me immediate reboot. Maybe it was not the fsck_msdos cause I was able to do a check and not get a reboot with the debug apk you gave me. I am trying the adb method but I think I am messing up some steps. Will let you know when I get through it.
@kryz I should have some time tomorrow to test the shell commands. Thank you again for taking your time to do this.