So I reverted back to stock, unrooted firmware since I wasn't happy with the battery drainage I was getting mainly because of the engineering kernel on root. I know there was a new update that came out recently and I saw that there wasn't much of a difference so I just updated to that anyway. That's when I noticed this morning that the Verizon intruding bloatware, DT Ignite, is actually rooted into the system and cannot be uninstalled like before.
I think I had Package Disabler Pro disabled it, but I checked my Wi-Fi Data usage and saw it used some data overnight. I went ahead and Disabled it in app manager and then again through Package Disabler.
Just giving you guys a tip on what I found!
Related
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.
I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.
System Updates Frozen
I have the System Updates App frozen in Ti BU. Haven't gotten any hint of an update and I hope it stays that way.
Same thing happened to me it tried installing the update all on its own luckily it said waiting for wifi network to update so I froze the system updates app with titanium back up.
RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
RyanEJ25 said:
I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.
Click to expand...
Click to collapse
trailrunner76 said:
RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
Click to expand...
Click to collapse
The main thing that threw me off was that USB charge modes have changed. Charge and internet connection are removed from PC connections other than that its general improvements to the keyboard and docs and stuff.
You can temp unroot, take the update, then reroot assuming Verizon didn't load a bullet that kills root.
Voodoo OTA Root Keeper
Sent from my VS985 4G using XDA Free mobile app
I'd tend to avoid the update, at least for now, if you want to keep root and twrp. Seems to be a number of people mentioning issues, including trouble reverting to 10b.
I also froze "System updates" with TiBU, going to stay on 10b until things clear up. Freezing that app seems to do the trick.
Why are you posting here, instead of the Verizon forum: http://forum.xda-developers.com/verizon-lg-g3/general
If you take the update, you can't re-root and you can't roll back.
Some people have maintained root after updating.
I've had my Note 4 for a while and after a few Lollipop update incidents I finally after a lot of hesitation decided to root my phone (with the TWRP bootloader) and disable the update notifier. Since then, I've always stuck to the latest stock version of KitKat 4.4.4.
Since I've rooted my phone, I made the following modifications that require root priviliges: I installed XPrivacy mod, YouTube AdAway mod, NoSafeVolumeWarning mod, PlayPermissionsExposed mod, and CrappaLinks mod for the Xposed framework. I also installed Titanium backup to freeze/uninstall the updater and AdAway. After XPosed was installed I had to change a line in /system/build.prop to 'ro.securestorage.support=false' to make 'S Health' work again. I did that with the 'FX' app.
That's it, I had made no more modifications and the phone seemed to work quite well for a month or so.
Two days ago I decided to try out Instagram, I've been quite wary with social apps but figured Instagram shouldn't hurt and everything was fine. Then I installed a bunch of dating apps, I started with Match.com and Tinder. Tinder didn't work because it required FB and Match didn't work because it refused to, probably because of denied permissions with XPrivacy so I gave up on them and uninstalled them.
But I also installed OkCupid and Motesplatsen and enjoyed playing around with these apps. They didn't seem to interfere with XPrivacy and worked rather fine. Motesplatsen was rather intense with sending me notifications of girls who watched my profile and sent me (rather strange) messages whereas OkCupid was rather calm.
Then something strange happened.
Yesterday I started noticing that the battery was draining considerably faster than normal during normal day. It was almost empty whereas it usually is half full after a full day, I also noticed that the phone was unusually warm. I forgot to put it on the charger and woke up today with a dead phone. I put it on charge and after about an hour the battery was full again.
When I tried to turn on the phone it was stuck on boot loop. I first tried disabling XPosed by "touch /data/data/de.robv.android.xposed.installer/conf/disabled" using the 'terminal' tool in the TWRP bootloader. It didn't help. I tried flushing the cache/dalvik cache but it didn't work either. Then I did a total factory reset, but that didn't work. I noticed that during boot, the phone froze so hard that it doesn't even respond to button pushes. I had to take out the battery to reboot (that's one reason why I never will buy S6).
So then I decided to flash the phone with stock KitKat once again using Odin and that finally restored the phone.
Now, here's one of my questions, how can things go so bad with a phone that not even a factory reset will fix it? We're talking stock firmware here, albeit it is rooted.
What boot logs could be worth looking into when such a thing occurs and what is the easiest way to extract them? The terminal tool in the bootloader seems promising, plus I saw a 'copy log to SD' option which I neglected this time.
I'm puzzled, does anyone know what happened? I made no root modifications in the process of installing these apps and they don't advertise themselves as needing root privileges. How can a seemingly inconspicuous app directly from Google play **** a phone up like that?
I HAVE NEVER rooted my S7 E and when I tried to check for updates today I got the message you see below. I am running package disabler, I enabled all packages and tried again-same result. Wtf
ike_1985 said:
I HAVE NEVER rooted my S7 E and when I tried to check for updates today I got the message you see below. I am running package disabler, I enabled all packages and tried again-same result. Wtf
Click to expand...
Click to collapse
Factory reset your phone, if your not rooted ever and running stock only..Many users complaining about this after updating latest 7.0 firmware..It might be bug in update..By the way factory reset your phone and report here if it helps or not
I would also add that I bought the phone new not used. It took me hours to setup my phone the way I like not wanting to lose everything...I have smartswitch on my Macbook pro will SS restore it after I back it up? Does SS back it up to cloud or local? Not interested in cloud backups.
After a restart I am getting "this device is up to date" from the update app.
Curiously my device status has changes feom CUSTOM to OFFICIAL. It was custom when the update app wasn't working. Also now my package disabler ia giving me an error "unable to disable package deactivate administrator". Now I cant disable anything in PD.
See below
Hi, it happened to my s7 phone,one weekbefore i checked for update, it showed update available. I just waited for weekend to update but it showed same messages in above blog, i checked about device-status it showed customized , i wondered how it happend, i didn't do any change to phone, and i start to uninstall the app and apk which down loaded from web (not from playstore) , and few downloaded files also i deleted from my files-download- from internal storage. Again i checked softerupdate, yes it worked, status also shows official. I hope this information may help someone.
:laugh::laugh:
I was getting ready to root my phone, but found a thread referring to an app called BK Disabler, in the play store. I downloaded the app, and froze the two SDM service apps.
From what I understand, I have prevented my phone from ever updating. Is this correct?
My only goal in rooting was prevent the update because i use FoxFi. Assuming it works i wanted to share an easier method for avoiding the update. Thoughts?