I keep getting notifications about an ota update for 4.3. It's about 16 MB. When I get sick of seeing it and hit install the phone reboots into recovery where I then get a warning about an unverified package. I then get chicken and don't wow it to install and reboot (it asks to fix root then to for some reason)
Is this safe to install? If not, can I make it stop telling me there is a system update available?
The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/
well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.
Hi
When I first got my S5 I updated OTA to 4.4.2. Hated the restrictions but batt life was good at that point.
So after playing with the phone and installing apps batt life became bad so I reset the phone.
My Batt was still draining more quickly even after a factory reset even though restore option was unticked and no new apps after the reset I ran titanium backup and froze most of the user apps but batt drain was still bad.
In settings>battery it shows Android System as the highest percentage.
When i reset the device to factory settings when it loads up i see SuperSU and GSAM battermonitor root companion installed along with the other essential bloatware apps from Samsung . It also auto updates Chrome as well as Samsung apps like Chaton , wallet even though I turned off Autoupdate apps in the play store ?
How do I stop those Stock Apps (eg ChatOn ) from Updating ? - Chrome is not stock iirc but it also gets updated.
Im guessing my batt drain after a reset is being affected because of updates to system/bloatware apps. Whilst playing around somehow maybe have unknowingly integrated those system updates into the system rom ?
So if I accepted that OTA (guessing 4.4.4) update will all system software be fully reset to stock (whilst still retaining root via SuperSU Survival mode ) so that I can get the similar batt life/drain like when I first got the phone ?
Or what other options do i have so I can reset all the factory software to stock (no updates) ?
I have purchased and installed SuperSU and enabled survival mode.I also installed buzybox.
My second question : How do I stop Chat on ,Samsung Wallet etc from auto updating after a fresh reset ?
AzNDuD3 said:
Hi
Click to expand...
Click to collapse
The update will most likely be downloaded but not installed because you are rooted. You can however flash the entire 4.4.4 rom with Mobile Odin Pro and keep root IF your device is suported. Better check that first.
Hi thx for the reply.
I just dled mobile odin and it said device not supported ? SM-G900i
What are my other options ?
Going to the Sammobile site for the rom it shows the latest 4.4.2 G900IDVU1ANG3 firmware for my device SM-G900i is Android 4.4.2 not the 4.4.4 i guessed
IIs it safe If i flash from my current firmware G900IDVU1ANE1 June to an earlier dated firmware like the G900IDVU1ANC6 April ] [/I]
EDIT/B]
Sp Ive been doing abit of searching and i found Rashr as well Phils Touch Recovery that work on the Galaxy S5. Phils recovery is installed and I can boot into it . The options look similar to CWM Recovery
Im not sure which steps i should take for a fresh firmware install. And I dont want to just choose the wrong option and brick my phone
Should I choose Wipe Data/Factory Reset and then install Zip ?
Latest Firmware Reference for Galaxy S5 SM-G900I
Country/Carrier Date Version PDA Kies
Australia (Optus) 2014 August 4.4.2 G900IDVU1ANG3
Australia (Optus) 2014 June 4.4.2 G900IDVU1ANE1
Australia (Optus) 2014 April 4.4.2 G900IDVU1ANC6
I was on 5.0 but it ran crappy so went back to 4.4.2, It downloaded 2 OTA updates but now is prompting for another which is Lollipop, the damn thing bugs me all day to install. Is there anyway to disable this without root?
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk
i have troubles as well. i unrooted, installed stock recovery (via n4 toolkit) and tryed to install. it takes longer then before but i stell get an error. SuperSU is gone in my app drawer.. any other help?
PS: i am on stock rom 5.0.1
i tryed to use sideload ADB update. it says: "/system/bin/app_process32" has unexpected contents. Error in sideload/package.zip. Status 7
any tipps?
I used the excellent Wug Nexus Toolkit http://www.wugfresh.com/nrt/
Through there I unrooted. Then applied the new update.
rowdybeans said:
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk[/Q
I tray everything but don't work, it tell me , cache file fail.
Click to expand...
Click to collapse
In my case, this did the trick: aaronhastings.me/updating-to-android-5-1-0-on-rooted-nexus-5
I hope it will help you, too.
Regards.