Just wanted to share that there's a new update. Not sure what it does though.
animal7296 said:
Just wanted to share that there's a new update. Not sure what it does though.
Click to expand...
Click to collapse
It's nothing worth taking note of, it's just a security patch no Android N!
Yes it comes with January security patch > https://www.verizonwireless.com/support/samsung-galaxy-note5-update/
Yes, I don't think we will see that update for a while thanks to Verizon..
Sent from my SM-N920V using Tapatalk
So now it's prompting me to install. I don't want to, I want to attempt root if that guy gets back to us. What packages do I need to disable to get rid of update?
So, I disabled the 2 packages called System Updates and then rebooted into recovery and wiped /cache hoping that it will wipe out the contents of the /cache/fota folder. Someone please let me know if I did something wrong or if any additional steps should be taken.
Boring...But good this phone is still getting frequent updates. Really needs some N love ASAP though.
just another security patch
tylerlawhon said:
So now it's prompting me to install. I don't want to, I want to attempt root if that guy gets back to us. What packages do I need to disable to get rid of update?
So, I disabled the 2 packages called System Updates and then rebooted into recovery and wiped /cache hoping that it will wipe out the contents of the /cache/fota folder. Someone please let me know if I did something wrong or if any additional steps should be taken.
Click to expand...
Click to collapse
You didn't do anything wrong. Your phone should be fine.
I cannot disable either System Updates app. I even tried downloading Package Disabler Pro and that didn't work either.
I've been deferring updating for days now and it's starting to really annoy me.
DaRkL3AD3R said:
I cannot disable either System Updates app. I even tried downloading Package Disabler Pro and that didn't work either.
I've been deferring updating for days now and it's starting to really annoy me.
Click to expand...
Click to collapse
You need to get ahold of the guy who owns the app because there's an issue with the way it's trying to stop the updates... The one you're using probably has "com.samsung.sdm.sdmviewer" but you need to stop "com.samsung.sdm" and then it'll go away and the only way I got that to work was, he gave me a link to download a completely different one which stopped it. I'm pretty sure his email address is on the package disabler app on the play store.
Also you could load the root kernel so you at least have the console root and use the pm command to disable it if you need help let me know.
DaRkL3AD3R said:
I cannot disable either System Updates app. I even tried downloading Package Disabler Pro and that didn't work either.
I've been deferring updating for days now and it's starting to really annoy me.
Click to expand...
Click to collapse
Did you figure it out yet?
MrMike2182 said:
Did you figure it out yet?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
See if you can disable the updater.
darksidesh007 said:
Try this https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
See if you can disable the updater.
Click to expand...
Click to collapse
Lol thanks but I don't need that.. I was just trying to ask him if he figured it out for himself yet because otherwise the reason that package disabler and other apps aren't working to stop the upgrade nagging is because they decided to change the name from com.samsung.sdm.sdmviewer to com.samsung.sdm so when package disabler was stopping (or trying to stop the incorrect name) it just kept nagging until the right one was stopped and technically you don't even need package disabler because you could load up the console root kernel and use the pm disable command and it would do the same thing as package disabler but it's easier and faster to just use package disabler.
Related
I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks
jasondhsd said:
I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks
Click to expand...
Click to collapse
Flash a custom recovery/ROM. That should do it
But I'm not sure what else if the fwupgrade freeze didn't work
Yes. How do I stop this crap!?
I have 2 of these both rooted and hers keeps trying to install it. Its already downloaded on hers. I interrupted mine by killing the internet connection as soon as I saw it start downloading.
I'm sure when I'm sleeping it will try to install itself. So ill just shut my phone off.
Grr...
I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.
jasondhsd said:
I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.
Click to expand...
Click to collapse
Thats an issue with no-sympathy.... Most ROM's block the OTAs so you don't even need to worry about them.
This is actually the first ROM i've heard of that allows OTA's to even show up on the prompts.
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
You would have to ask the ROM's developers. Refuse it, and flash to another ROM that does it automatically for you. Obviously No Sympathy didn't think of an OTA... whynot I dunno. But every other developer did.
jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
Install an old version of synergy?
Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.
jasondhsd said:
Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.
Click to expand...
Click to collapse
I just did that. sdm 1.0 frozen. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from my Land Line using xda premium
Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.
Blue6IX said:
Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.
Click to expand...
Click to collapse
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...
shuura said:
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...
Click to expand...
Click to collapse
So far so good on freezing SDM. We'll see tomorrow morning.
My old s3 broke, just got my new s3 today. I just rooted my device, and was wondering if it was ok to update my phone. An annoying prompt keeps asking me to update. Dont know if I'm supposed to disable it or update my phone.
leave it alone..update is useless..unroots your phone..stay away
sent from a DIS-GRUNTLED GS3
Can you or anyone tell me how I can disable it? it keeps popping up on me. its annoying!
Schism169 said:
Can you or anyone tell me how I can disable it? it keeps popping up on me. its annoying!
Click to expand...
Click to collapse
Use an app like Titanium Backup, switch to "System" apps via the filter, then press the specific app. Or use a file explorer, grant it root access, then navigate to /System and rename the file to "sdm 1.0.bak" or delete it.
Thank you guys, Got it frozen
Is there a way to do it without a rooted phone? Titantium backup apparently needs root. This stupid update is so annoying. I plan to root my phone in the future so I dont want the update but I dont have time to figure out how to root it right now.
smalco44 said:
Is there a way to do it without a rooted phone? Titantium backup apparently needs root. This stupid update is so annoying. I plan to root my phone in the future so I dont want the update but I dont have time to figure out how to root it right now.
Click to expand...
Click to collapse
No and if there were a way to do this non-rooted, that would be a very questionable security flaw.
Edit: Use Saferoot to gain root access on VRUCML1, when you find time. Links and info in our TW 4.3 Sticky.
Sent from my SCH-I535 using Tapatalk 4
Am I correct in assuming simply freezing SDM will stop OTA's? I thought there was one other thing that had to be frozen.
gospodinwizard said:
Am I correct in assuming simply freezing SDM will stop OTA's? I thought there was one other thing that had to be frozen.
Click to expand...
Click to collapse
Freezing SDM was all I needed to do on my S3 to stop the update nags. Others have mentioned another file "FWUpdate", but I could not find it on my S3. I would just try freezing SDM 1.0 and see if that does it, if not, then look for the other file.
Anybody know what it is. ..how can I disable it..don't want to update, still hoping for rooted one day
It's listed as the monthly android security patch update.
Sent from my SM-N920V using Tapatalk
Need to do it. Fixes recent security flaws
Verizon Wireless Technician using Tapatalk on Note 5
Jacob11701 said:
Need to do it. Fixes recent security flaws
Verizon Wireless Technician using Tapatalk on Note 5
Click to expand...
Click to collapse
Be nice if it addressed memory management a little.
Sent from my SM-N920V using Tapatalk
Sample
xavierxxx2p said:
Anybody know what it is. ..how can I disable it..don't want to update, still hoping for rooted one day
Click to expand...
Click to collapse
You can block SDM.apk with this debloater if you don't want to be nagged anymore. Seeing that the update was already downloaded you will have to enter recovery mode and clear cache to get rid of the install nag. After you do that and disable SDM.apk you will no longer get the notification. I went ahead and installed it anyways because I'm not too concerned with root. I'd rather have a secure device.
Misterxtc said:
You can block SDM.apk with this debloater if you don't want to be nagged anymore. Seeing that the update was already downloaded you will have to enter recovery mode and clear cache to get rid of the install nag. After you do that and disable SDM.apk you will no longer get the notification. I went ahead and installed it anyways because I'm not too concerned with root. I'd rather have a secure device.
Click to expand...
Click to collapse
Thanks man..I also took the update. .i guess I already got use to not being root. ..besides adguard and ogtube help alot.
xavierxxx2p said:
Thanks man..I also took the update. .i guess I already got use to not being root. ..besides adguard and ogtube help alot.
Click to expand...
Click to collapse
Your welcome. I feel the same here. My S6 lost root the Note 4 never had it except the dev ed I had for a short time so I got used to no root as well. With the debloater it's no big deal for me anymore and being able to theme really settled the issue for me. I can do basically everything I want and still have a secure phone without worrying when root will get killed. I do miss building ROMs a little but I can deal without it.
weird layout after update
So I took the update and since the all my menus are on the right side of screen, my send button in text is now on the left side as well as my statusbar icons. Nobody else mentioned this. Is it just my n5?
deno24 said:
So I took the update and since the all my menus are on the right side of screen, my send button in text is now on the left side as well as my statusbar icons. Nobody else mentioned this. Is it just my n5?
Click to expand...
Click to collapse
Can you post screenshots?
Verizon Wireless Technician using Tapatalk on Note 5
Misterxtc said:
You can block SDM.apk with this debloater if you don't want to be nagged anymore. Seeing that the update was already downloaded you will have to enter recovery mode and clear cache to get rid of the install nag. After you do that and disable SDM.apk you will no longer get the notification. I went ahead and installed it anyways because I'm not too concerned with root. I'd rather have a secure device.
Click to expand...
Click to collapse
It works. If you remember to turn USB debugging on........
Yes, it works just fine.
Sent from my SM-N920V using Tapatalk
billinaz said:
It works. If you remember to turn USB debugging on........
Click to expand...
Click to collapse
Or the app package disabler does it perfectly from the phone itself without root. Easy check and uncheck
Verizon Wireless Technician using Tapatalk on Note 5
My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431
Probably the security patch.
Taken from my 920
It brings us up to 10i where T-Mobile is currently at.
Ant way to block updates on a non rooted phone?
Could we possibly finally get a stock KDZ from this?
I froze that
jetracer said:
Ant way to block updates on a non rooted phone?
Click to expand...
Click to collapse
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Edit: It failed this time.....I just got the update prompt
monke30butt said:
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Click to expand...
Click to collapse
Can you link the apk. Can only seem to find old ones
haris163 said:
My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431
Click to expand...
Click to collapse
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?
ubergeek77 said:
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?
Click to expand...
Click to collapse
I willingly let it install.
AT&T Forced this update on my phone
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
haris163 said:
I willingly let it install.
Click to expand...
Click to collapse
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
mmarsie said:
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
Sorry I don't know about that. My phone is pure stock.
mmarsie said:
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.
ubergeek77 said:
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.
Click to expand...
Click to collapse
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.
mmarsie said:
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.
Click to expand...
Click to collapse
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm not rooted yet. I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.
ubergeek77 said:
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.
Click to expand...
Click to collapse
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off
mmarsie said:
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off
Click to expand...
Click to collapse
This is terrible.
ubergeek77 said:
This is terrible.
Click to expand...
Click to collapse
yeah I'm lived right now, currently with out a cellphone untill i test some of the above options another user posted. Here's hoping
Does anyone know whether a phone with this update can still use the dirtysanta exploit to root, or is that also broken by the security update?
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.