I'm rooted on OE2 and I'm not planning on updating. I searched and found that Verizon users can freeze SDM.apk and it'll stop updates but it looks like that apk doesn't exist on the AT&T version. I don't really want to flash a custom ROM, is there any other way to stop these forced updates?
On my active, the file com.ws.dm is called at&t update manager. That might be a good place to start.
Note that I haven't tried this.
Bump
On my s6 active, Its called AT&T Software Update but its the same app: com.ws.dm. The icon is a red and blue arrow under a grey textbox with an exclamation point in it. Freeze, disable, rename, or remove that, and you should be good. I used Package Disabler Pro in the app store to disable this app and i haven't had any forced updates since. In fact I wanted OF4 and had to re-enable that specific app to get the OTA to download. It's worth noting that you don't need root to use Package Disabler Pro, for those of us stranded on the S6 Active with no root exploit.
Related
I've decided to get my phone ready to accept the (hopefully soon) OTA update for my 2013 X. Right now it's on 4.4.4, bootloader unlocked (thanks Sunshine!), and rooted. I had it rooted to take advantage of Xposed and Secure Settings with Tasker integration. I also used TitaniumBackup to freeze the Verizon and some Moto apps I never used.
Currently, I have uninstalled every Xposed module I downloaded, then unistalled Xposed itself and finally the Xposed installer app. After that I went into Titanium and defrosted everything that was frozen. Now I have a fair amount of updates coming in from the Play store for all those apps that were frozen. Should I go ahead and update them?
From what I've read, there's been talk on whether or not I have to un-root my phone. I thought I just had to use the toolkit to flash back the stock recovery? That should be the only thing left to do? What about some apps that are device administrators like Cerberus? Do I need to remove them from that list?
Thank you for any advice. I plan on flashing stock recovery when I get home this evening.
Generally speaking an OTA will probably fail if apps it expects to be present are missing or modified in the /system partition. I don't know if having additional items (like Cerberus) will halt the OTA or not. Custom recovery may also interfere with the OTA.
It sounds like you already did all the work, but I personally wouldn't have done any of that until the OTA was actually rolling out. I know they said it will be soon, but it could still be weeks away. I wouldn't give up my phone that was setup how I like it, but that's just my preference.
When the OTA drops, if you try and install it will do all of the validation before it installs anything. If the validation fails, it will tell you it has an error and it won't work. Then you'll have to fix whatever was modified, or reflash the stock firmware to be compatible with the OTA.
I don't believe updating the apps is necessary. I don't even think they need to be active (you can use the Disable function in the App Info screen to hide them), they just need to be present in your /system folder with the correct signature, is how I understand it.
did anyone tried to use V3.90 Debloater to remove all the ATT bloatware? I am curious as I am getting the phone next week
http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
calvinleeabc said:
did anyone tried to use V3.90 Debloater to remove all the ATT bloatware? I am curious as I am getting the phone next week[emoji14]
http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
I use package disabler pro (play store) on my AT&T S6. Works great and lets you disable whatever you want without root and without a computer.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Any worry about disabling something essential and causing a boot loop?? Usually the solution is to reflash the stock rom back on, but as far as I know, the Active stock rom still isn't released yet
Ditto on Package disabler pro, it almost makes me not need root. Granted I still want it, cause when someone won't let me have control of my own system.
I have SuperSU on my S5 phone, and I need to turn that off to use an online money transfer app called Vipps. When I do that, I get a popup saying "uninstalling". My son has the same SuperSU version (2.46) on his S4 Active, and he does not get that popup. And I can use Vipps, while he can't. Any idea why this is? Can it be because we are on different Android versions? Or are there different versions of SuperSU at play here? And what version would I need to bring my son's phone up to so I can get it workingthe same way there?
Get systemless root.
Thanks, but in the meantime I found that with the the latest version of SuperSU it's sufficient to turn off SuperSU to fool the program I needed to fool.
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
I am buying a unlocked note8. And I require root as a lot of my apps require it.... and it’s my understanding that I am going to need to stop the ota update in order to achieve root.
Can someone please tell me how to stop the ota update so I can root the device.
Hello,
Curious if are you going to run a custom rom or root and remove apps you don't want?
Tinythejuggalo said:
I am buying a unlocked note8. And I require root as a lot of my apps require it.... and it’s my understanding that I am going to need to stop the ota update in order to achieve root.
Can someone please tell me how to stop the ota update so I can root the device.
Click to expand...
Click to collapse
Which model do you have? Snapdragon?
Generally you can disable the software update using a Package Disabler from the Play Store, or freeze it using Titanium Backup once rooted. Simply turning off the update option in Settings will not work long-term, as it would eventually update anyways. That's why you need to disable or freeze it.
In developers options you can also turn off auto update system. Usually after you root OTA updates won't function anymore anyway after the device status changes to custom. Or does that not apply for US Snapdragons & SamFail?
Can I temporarily disable it just long enough so I can root. Via samfail
Yes, just go in settings - software updates, there change to download updates manually... Job done: nothing will be updated unless you initiate it yourself...
Can update be stopped without root?
Most package disablers are not working,dev option not working.
Have gone back to oreo from pie don't want be forced back onto pie.
I have a rooted Galaxy s10+ with android pie. Doesn't freezing "Software Update" system apps of my android by Titanium Backup make booting problems for my device? Is it safe for me to freeze those apps? I ask because I've heard freezing some system apps like "Device Care" stops the device from booting. As other fellas I get ota update notifications and I wanna get rid of them by freezing those apps.
MystaMagoo said:
Can update be stopped without root?
Most package disablers are not working,dev option not working.
Have gone back to oreo from pie don't want be forced back onto pie.
Click to expand...
Click to collapse
I am disabling apps with a package disabler for them to still keep updating! So I have gone back to the method of disabling apps via ADB (no root needed this way)
It uninstalls it for the current user, but a factory reset will bring the app back if so needed. You can uninstall the update app with this method, or any other app for that matter. (Just be careful with what you disable)
https://forum.xda-developers.com/ga...nstall-potentially-unneeded-unwanted-t3731062