[Q] S Health stopped working after restore from Titanium Backup - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

So, I backed up and then removed S Health and Sensor Service a while back with Titanium Backup. I bought a Gear 2 and I have decided that I want to actually setup and use it. I did a restore in Titanium Backup but now I get a window saying S Health and/or Sensor Service has stopped working. I tried deleting the cache and data, restoring data and app back, uninstalling and reinstalling, etc. Nothing is working. I have not updated or changed anything since my backup, so a different Android version/backup conflict is not the problem as stated in other threads. What could I have done? How can this be fixed? I've looked everywhere and read all the other threads regarding both Titanium Backup and S Health and still can not figure out what to do. Links to stock software in older threads are all broken. I have an SPH-L720, Android 4.4.2, S Health 2.5.4.066, Sensor Service 2.33.

Related

Titanium backup restore APP+DATA doesn't seem to work

Hi,
I just updated my Desire Z from Virtuous Sense to CM7.1. I previously backed up all my apps with Titanium Backup, and after I flashed CM7.1, I downloaded Titanium Backup and restored some apps (App+Data). However, when I launched these restored apps, the data didn't seem to be restored. I'm still presented with a login screen.
Does anyone know how I can get app+data restore to work? Is there some setting that needs to be done during the backup process to get Titanium Backup to also back up my data, or is it incompatible with CM7.1?
Thanks.
Have you used Titanium for this before? Titanium doesn't always restore login data for apps that need it. For some apps, it just doesn't work for some reason. And its always the same apps.
For instance, Titanium seems to restore my Netflix and Pandora login data just fine (so I don't have to enter it again after flashing a new ROM). But HBO GO never does, and I have to enter it again.
Actually, yes I have. For example, I've tried it with Whatsapp, and it worked before. I didn't need to login with my phone number. This is useful since my whatsapp was registered to an old number. Skipping the login step would allow me to continue using the account.
For some reason it doesn't work this time.
Reflash the ROM or reinstall Titanium

Restore Titanium Backups

Hello,
i tried to restore my titanium backups from my note 2 on my note 3.
Restore Apps might probly work sometime but not with data. With data the apps will stuck und i must replace the battery.
And de-install the apps is horrible to. Every time at every app i must replace the battery to.
Have anyone a solution?
Already answered.
http://forum.xda-developers.com/showthread.php?t=2463116

[Q] Unable to restore S Health data since Kit-Kat update

Greetings All,
I’ve run across a problem restoring all my S Health data since the update to Kit Kat. I wanted to do a factory reset after getting the 4.4.2 update last week, since I had something that was draining the battery…it was down to 50% at noon then 30% after I get home from work with very light use. I figured it might have been some app that I had installed that was draining the battery since I had the battery drain issue on 4.3 as well.
I have lots of S Health data stored since I got the phone last year and I didn’t want to lose it. The S Health app was doing the regular auto-backups. But, before doing the factory reset I did a manual backup from within the app. I did the factory reset and then went back to the S Heath app and signed in with my samsung account.
When I went to restore the data, I keep getting an error (screenshot attached) that says:
Restoration Failed
Restoration is not possible because current version is low​
The S Health app shows to be on version 2.5.0.66, is this the right version on 4.4.2? Checking from within the app doesn’t show any updates available.
I don’t recall the app version before I did the factory reset, but I don’t remember it getting updated since I did the backup or after the factory reset.
Anyone else have a problem restoring the S Health data after the update to 4.4.2? I don’t remember having this error before on 4.3. I’ve restored the data on earlier versions of Jelly Bean a few times and didn’t have a problem.
I’ve talked to samsung about it, they had me clear the caches for the app, which didn’t help.
Has anyone else seen this error before and if so, did you find a way to restore the S Health data?
I have a backup of the phone in Kies from about a week ago, but I didn’t see anything about restoring the S Heath data, on the S memo data.
Thank you kindly,
Chris
I have same problem
Odesláno z mého GT-I9505 pomocí Tapatalk
Same problem here. I tried just about everything and couldn't get it to restore. Eventually just gave up and restarted the auto backup, which cleared my previously backed up data. Oh well. Looks like Samsung messed up the ability to restore from backups made before the 4.4.2 update. I hate to say it, but it looks like you might be screwed unless Samsung fixes this and pushes an update out.
On another note, I had similar battery drain when I updated, which was why I also did a factory reset and lost my S Health data as well. The factory reset didn't fix the battery drain, but I disabled sync for some Google services that I don't use, and my battery life is significantly better. I'd try that if you are still suffering from bad battery life.
You might try pulling the app from an MK2 rom. Uninstalling the new one and installing old. Restore data and then update or install new apk. I don't use this app ... so I'm not sure. If it's still a problem maybe I will do some digging.
Sent from my SPH-L720 using Tapatalk
I have the same problem also.
I tried a second factory reset and still can't get my data to restore.
Greetings,
I'm wondering if this is just a bug in 4.4.2 since I did the backup from 4.4.2 and attempted to restore from the same rom. The only difference is I did a factory reset before I attempted the restore. I'm wondering if I can root and flash back to a previous 4.3 rom and restore s-health, then backup using titanium, flash 4.4.2 then restore from titanium? I've not had any problems restoring the backups before on any of the previous stock roms. I'm also tempted to create another samsung account and try saving and restoring a backup of the S-Health data to test to see if the restore even works at all.
The error message is somewhat ambivalent on which is the lower version, the data or the app?
On a side note, does anyone know of a good pedometer app that at least has the ability to do a local backup of data? I really like having the history of my travels. I like the ability to just turn it on and have it logging in the background.
I may also give samsung support another go and/or post in the sprint s4 support forum to see if anyone's having the same problem.
Thank you kindly,
Chris
Any solutions?
How typical.
S-Note Documents from Samsung Note 10.1 with Android 4.1.2 don't transfer over to the Note 3 and Note 10.1 with S-Note and Android 4.3
Given yet another example, we know this is not even an isolated problem.
Samsung's software is intended to be nothing more than a tech demo without actual customer usability in mind.
Greetings,
No luck so far. I've pretty much given up hope of ever recovering the data. I've posted about the problem on the sprint community S4 forum. They were helpful, but ultimately no luck. One person says the version should be 2.5.5, but my phone only has 2.5.4 with no update showing up. I've talked with Samsung and they say that I do indeed have the current version.
What version of the SHealth app do you guys have? Did you get an update to it after the 4.4.2 update? In case this helps, I do see that the Kies 3 finally supports backing up the SHealth data now without having to rely on backing up to the "cloud" thru the SHealth app.
I've done a test backup and restore from the shealth app and it did work. I'm not sure what could have happened before, perhaps just a glitch that prevented the restore from occurring.
That's where I am at this point. I'm leery at this point to rely on the in app backup/restore process since I lost all the data going back to May of last year when I got the phone. I'm definitely going to rely on alternative backup methods. I've rooted and will use Titanium Backup to keep a good backup going forward.
It would be interesting to see if everyone has the same version of the SHealth app. Again, I'm on a sprint SPH-L720 NAE kit-kat.
That's all I have for now.
Thanks,
Chris
cbrand said:
Greetings,
No luck so far. I've pretty much given up hope of ever recovering the data. I've posted about the problem on the sprint community S4 forum. They were helpful, but ultimately no luck. One person says the version should be 2.5.5, but my phone only has 2.5.4 with no update showing up. I've talked with Samsung and they say that I do indeed have the current version.
What version of the SHealth app do you guys have? Did you get an update to it after the 4.4.2 update? In case this helps, I do see that the Kies 3 finally supports backing up the SHealth data now without having to rely on backing up to the "cloud" thru the SHealth app.
I've done a test backup and restore from the shealth app and it did work. I'm not sure what could have happened before, perhaps just a glitch that prevented the restore from occurring.
That's where I am at this point. I'm leery at this point to rely on the in app backup/restore process since I lost all the data going back to May of last year when I got the phone. I'm definitely going to rely on alternative backup methods. I've rooted and will use Titanium Backup to keep a good backup going forward.
It would be interesting to see if everyone has the same version of the SHealth app. Again, I'm on a sprint SPH-L720 NAE kit-kat.
That's all I have for now.
Thanks,
Chris
Click to expand...
Click to collapse
BTW, do you have the Galaxy Gear?
I was wondering if it is syncing to the Walking Mate instead of the Exercise Mate.
klau1,
Nope, I don't have the galaxy gear.
Thanks,
Chris
Bummer. I found this thread because I'm having the same issue.
same problem for me upgrading rom... and now, I've bought S5. Same problem again with S Health 3.0!!!!
problem solvend update to S Health 3.1
Odesláno z mého GT-I9505 pomocí Tapatalk
prucdo said:
problem solvend update to S Health 3.1
Odesláno z mého GT-I9505 pomocí Tapatalk
Click to expand...
Click to collapse
This worked for me as well. I went through the setup after pretty much writing off all the data I've been collecting the past few months and was very surprised when it informed me that an update was available (even though I couldn't find it in the samsung apps store). Updated to the latest version, then the restore worked perfectly!
I just reset my Verizon Galaxy S4 after some time running with the Android 4.4.2 update. I was using the online data backup option through my Samsung account. The stock android 4.4.2 ROM comes S Health version 2.5.4.154 in it. I attempted to restore my data from the Samsung cloud but it failed saying there was a "network error." I could not find the Samsung Galaxy App store after the update so I followed this a droid life guide called "download: Samsung Apps Store With Access to Photo Editor, Wallet, and Others for the Verizon Galaxy S3" and installed the latest Galaxy Apps apk right from Samsung. After getting Galaxy Apps installed I logged into my Samsung account opened the store and clicked on purchases which detected that S Health needed to update. So I update S Health to 3.5.1.0693 and open it and it says I need to update HealthService to the latest (2.0.0.009) which I did. After launching the app it asked me if I wanted to restore my data which I said yes and it proceeded act like it was restoring it. It turns out it just nuked my data rather than restore it. It seems like I am SOL, unless you can get a previous version of your backup from Samsung. Anybody have any ideas? It really sucks because it was more than a year of data.

[Q&A] Action Memo restoring using Titanium Backup Pro multiple versions

I managed to successfully upgrade my Note 3 from 4.3 to 4.4.2 (which in retrospect seems like a bad idea due to the battery drain problem).
Nonetheless, I have rooted my phone for the most part (binaries won't update properly though).
The issue I am facing though is that I used Titanium backup pro to backup pretty much everything. However, when I go to restore my action memos, It shows multiple memos as attached.
Upon restoring all 4, it shows the notes, but they are all blank.
I simply need to access the data so I can write it down. Any ideas?
Thanks!
Have exactly the same problem. Did you ever get access to the data that you had on the Action Memos?

Titanium Backup: why do I keep getting errors when restoring data?

I've noticed two problems that crop up when I use Titanium Backup to restore my apps/data
1) If I try to restore the missing apps + data, sometimes everything gets restored, and sometimes it gives me "X elements failed", where some apps will not be installed. This happens whether I restore on the same ROM that I backed up on (backup on Cloudy G2, restore on Cloudy G2) , or if I use a different ROM (backup on NDM 5.5, restore on Cloudy G2). I thought I found a work around, where I just install the app from the Play Store first, and THEN I would restore the app data. That worked a few times until....
2) When I tried restoring my app data last night after a fresh KDZ wipe, the apps that I restored data on all couldn't start (Snapchat, Amazon, Wechat, SwiftKey). I would tap them, they would try to open for half a second, then they would close. I tried restarting my phone, but with that, I got "UIDs on your system are inconsistent, you need to wipe your data partition or your device will be unstable". I was stupid, and decided to wipe my data partition so I had to restore all my apps from scratch, but that at least hasn't lead to any problems yet.
Does anyone know what I did wrong, or what I can do to fix this? I know for number 1, some threads mentioned that your Android I.D. changes when you flash a new ROM (that MIGHT explain number 2?), but not a lot of people mention this, and it seems like the majority of people don't have this problem. For number 2, I found this thread, but it was too late already.
If possible, I'd like to find a backup app that avoids ALL of these and just lets me back things up and restore easily. Is there one out there?
tdk0117 said:
I've noticed two problems that crop up when I use Titanium Backup to restore my apps/data
1) If I try to restore the missing apps + data, sometimes everything gets restored, and sometimes it gives me "X elements failed", where some apps will not be installed. This happens whether I restore on the same ROM that I backed up on (backup on Cloudy G2, restore on Cloudy G2) , or if I use a different ROM (backup on NDM 5.5, restore on Cloudy G2). I thought I found a work around, where I just install the app from the Play Store first, and THEN I would restore the app data. That worked a few times until....
2) When I tried restoring my app data last night after a fresh KDZ wipe, the apps that I restored data on all couldn't start (Snapchat, Amazon, Wechat, SwiftKey). I would tap them, they would try to open for half a second, then they would close. I tried restarting my phone, but with that, I got "UIDs on your system are inconsistent, you need to wipe your data partition or your device will be unstable". I was stupid, and decided to wipe my data partition so I had to restore all my apps from scratch, but that at least hasn't lead to any problems yet.
Does anyone know what I did wrong, or what I can do to fix this? I know for number 1, some threads mentioned that your Android I.D. changes when you flash a new ROM (that MIGHT explain number 2?), but not a lot of people mention this, and it seems like the majority of people don't have this problem. For number 2, I found this thread, but it was too late already.
If possible, I'd like to find a backup app that avoids ALL of these and just lets me back things up and restore easily. Is there one out there?
Click to expand...
Click to collapse
is a supersu issue, open supersu than go to is setting and not select "name space mount separation" that is selected by default.
Now titanium can work as intended
Romagnolo1973 said:
is a supersu issue, open supersu than go to is setting and not select "name space mount separation" that is selected by default.
Now titanium can work as intended
Click to expand...
Click to collapse
That will fix both problems that I have?
Try, I was unable to use it untill I change the SuperSu setting and now Titanium is working perfectly, so probably your problem is the same.
Oh I mean, I can use it just fine. It can perform backups. But restoring is a when I get those errors. I'll keep this in mind in case I need to restore to a new ROM, thanks!

Categories

Resources