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.
So today, I got my Canadian GS4 back after about a year without it... So the first thing I did was hop on the play store and start updating apps. It got about halfway done updating the over 80 apps, then I had to leave WiFi. When I came back to it, anytime I started an update, Google play store crashed no matter if I clicked update all, or picked an individual app to update. My phone is currently:
Samsung Galaxy S4 (SGH-I337M)
Android 4.4.2
Rooted
I am really loathe to do a factory reset as I don't have regular access to a computer to re-root in the near future. Any help is greatly appreciated.
You could try clearing cache and data for google play and then try updating apps
Sent from my A0001 using Tapatalk
Hey guys,
Wanted to try and find out whether anyone else is experiencing issues with Google Play Services (9.4.52) crashing after upgrading to Nougat OTA?
I thought I may have a botched install so tried the following:
- Cleared cache
- Reset and didn't restore from backup
- Reset and only installed stock apps
- Safe mode
- Cleared Google Play Services data
- Unsubscribed from all Google beta testing apps
I still can't figure this one out, even after a hard reset back to stock it still kicks up a play services crash about once ever 10-20 minutes... very weird... and frustrating
Anyone else had this issue? Or got any suggestions?
I had the exact same problem after accepting OTA yesterday via the beta program. I was on 6.0.1 on my 6P (no root, no custom rom, locked boot-loader). All Google Apps and Services crash including Messenger (SMS). I performed a hard reset with no luck. I flashed OTA with no luck. Only solution was to unlock boot-loader, flash recovery, and go back to stock. I will try again today.
cybrdude said:
I had the exact same problem after accepting OTA yesterday via the beta program. I was on 6.0.1 on my 6P (no root, no custom rom, locked boot-loader). All Google Apps and Services crash including Messenger (SMS). I performed a hard reset with no luck. I flashed OTA with no luck. Only solution was to unlock boot-loader, flash recovery, and go back to stock. I will try again today.
Click to expand...
Click to collapse
Will try that method instead, the crashes have died down again but I can't find any correlation between specific apps and what's causing the crashes! If I find a solution I'll post.
I think there may be a problem with the final release. It seems Google pulled 7.0 from their factory images site. I downloaded 7.0 for nexus 6, 6P and 9 earlier today and only the download for the Nexus 9 is still available. I don't know which version is giving you a problem but on the Nexus 6P Google earlier posted version MTC20F. I was going to flash it this evening but I think I'll wait and see what version they post back to the factory image site.
Google has finally posted the OTA and Full ROM images for 7.0. Both have the exact same problem on my 6P. All Google Services and Apps crash and the phone reboots randomly (often). I am at a loss. Obviously issues exist with 7.0 and 6P. Google seriously needs to address this non-sense.
Hello. I have a Sprint s7e. Yesterday I updated my phone to the Nougat Beta and everything was going good. This morning I got a notification that an update was available so I accepted and it once it finished my phone keeps rebooting. It will fully load and within a minute of use, it will reboot. Even if I don't use the phone after the reboot, it will reboot in about a minute. Anyone else experiencing this? Possible fixes? I tried Safe Mode and it still rebooted. One mistake I made was I have items disabled with EZ Disabler which I forgot to re-enable. Ive done this before on Marshmallow and it never gave me any issues. Could this be the problem?
Is there a way to revert back to the older Beta Version, or even Marshmallow? Thanks
I would try a factory reset
Sent from my SM-G935P using Tapatalk
I would either try a factory reset or clearing the Cache. The last option would be a factory reset back to Marshmellow and then re-download the beta.
This happens on my wifes s7 edge. I assume its because of the (snapdragon 820) bootloader not liking root. Factory reset didnt solve issue for me because it threw up dm verity argument errors. Only thing that worked was flash combination firmware to completely wipe.
I had a similar issue. I would wipe data and clear cache. Start fresh. Android 7.0 vs 6.01 might have had compatibility issues or data corrupt caused bootloop. This is just my opinion. It sucks redoing everything, trust me. I had the Note 7 then got the s7 edge on Thursday, set it up on the stock 6.0.1. Then Friday found the Nougat beta and did my 1st download. It keeper rebooting constantly after It had finished set up.of course. So, I had to reset it up. I was able to go a day then reboot stuff happened again. So I data wiped and did it all over but this time I did not restore apps. I did fresh install and happy to report no issues thus far.
Sorry for long drawn out personal response, was just trying to share my experience in the event that it is useful to you.
Sent from my SM-G935P using Tapatalk
Has anyone had a problem with "Android Wear has stopped"? It started with the last update to PL3. I've tried clearing app cache and data as well as clearing cache from recovery. Hopefully the next update will fix it, but I've been wondering if anyone with a android watch has had a problem.
After last update , new TouchWiz from s8 can't install . Before update she's working perfect. I tried to clean catch partition and nothing.
Please help me.
Same here. If you do factory reset and dont sign into your accounts it should let you install it.
clear the launcher data then try again
June update or May
Same problem after factory reset.
In 9 june receive firmware update.
Another problem.