The other day I swapped my batteries an upon reboot, got a splash screen indicating an update was being installed. I had been rooted for over two years and I had SDM frozen via Titanium Backup. There was no confirmation prompt or ability to defer the update offered. After boot, SU had been uninstalled and Titanium Backup wouldn't run at all.
Has anyone else had this happen? Verizon pushing past disabled SDM to pwn a phone?
Sent from my SM-T520 using Tapatalk
Danzdroid said:
The other day I swapped my batteries an upon reboot, got a splash screen indicating an update was being installed. I had been rooted for over two years and I had SDM frozen via Titanium Backup. There was no confirmation prompt or ability to defer the update offered. After boot, SU had been uninstalled and Titanium Backup wouldn't run at all.
Has anyone else had this happen? Verizon pushing past disabled SDM to pwn a phone?
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
this is a serious problem , since for the vzw the bootloader unlocking usually take place on bpb1's and it would make sense that they would aim there first. I think it might be time for you to update your bootloader or switch over to custom roms instead of staying on samsung's firmware , and also this post just saved me from thinking of switching back to stock for the time being so now im def staying on nougat and hope android can be brought to the S5 as well.
I'm surprised there isn't anyone else reporting this. It seems VZW has a secondary backdoor into the stock firmware that isn't SDM or Knox. I didn't have the Verizon app installed either. On a different build on another S5 phone, the Verizon app asked for root from SU, and I shut it down immediately, figuring it wss trying to insert a backdoor.
It's just strange after two years of zero updates to my image, it suddenly allows VZW in to perform non-consentual sodomy on my phone...
Sent from my SM-G900V using Tapatalk
Danzdroid said:
I'm surprised there isn't anyone else reporting this. It seems VZW has a secondary backdoor into the stock firmware that isn't SDM or Knox. I didn't have the Verizon app installed either. On a different build on another S5 phone, the Verizon app asked for root from SU, and I shut it down immediately, figuring it wss trying to insert a backdoor.
It's just strange after two years of zero updates to my image, it suddenly allows VZW in to perform non-consentual sodomy on my phone...
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
its because the s5 is still widely used all over the world , its just another tactic for them to screw up older samsung devices to get users to upgrade to the latest ones. which is why using samsung software is not always a good thing. Injecting micro-codes are not UN-common for companies
I wanna know how they did that so it can be prevented.
Related
What used to be a simple patch to permit AT&T Galaxy Tabs to download apps from sites other than the Google Market is no more. We recently got our Tab back from the Samsung repair facility and it was wiped clean and loaded with a new Android version that now puts your Tab in an endless boot loop if you attempt to patch the config setup to permit downloads from outside Google Market.
Simple solution: DON'T BUY AT&T-BRANDED GALAXY TABS.
If there were some sort of unlimited data plan, this kind of behavior might be warranted but since AT&T charges by the amount of data you consume, there's really no excuse for crippling these devices... other than just being assholes!
Not entirely sure what you're referring to here. I have an AT&T SGT and it works just fine with sideloaded apps.
Did you run SuperOneClick root and then enable non-market apps?
Either way, nuke that horrid stock ROM with one of the Euro roms and you'll never have to worry about AT&T's crippled version again.
Yeah, but...
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
What version of firmware did your Tab come back with?
What method did you attempt to enable side loading?
I find this very hard to believe because every single ATT Android device to date has been able to side load after a simple 1 bit edit of the device settings db.
I believe that you had problems with the SuperOneClick app but there is a much cleaner / safer way to do it.
Sent from my SGH-I987 using Tapatalk
NerdUno said:
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
Click to expand...
Click to collapse
I don't believe my ATT SGT came with a protected bootloader, and if I'm not mistaken, AT&T hasn't released any firmware updates via KIES or OTA. So while there's always the possibility of Samsung "screwing" us all with that mess, it's only been seen on the leaked firmwares. Not that I don't put it past the big blue DeathStar to opt to use something like that to prevent people from avoiding their preloaded garbage....
I'm happy I liberated my device from the clutches of the Evil Empire, and will gladly look to XDA for my future upgrade paths.
Could just be a bad software flash from factory. A number of t-mobile vibrants couldn't get to restore via volume up/down power because of a buggy flash file they put on a certain build date
Sent from my Galaxy Tab
Hello, maybe somebody can help me understand. After rooting with kingo, installing safestrap, updating superSU, Making back up of Standard Rom that came from factory and updating via OTA to MJE, Installing Clean Rom 1.5 on Verizon on slot 1. Now I plug the note 3 via usb to my desktop and up pops Verizon wireless software repair assistant, What does this mean? I have not studied any further as I am charging my Zero Lemon Battery and don't want to take any chances with rootability in the future. I know I can ignored the Verizon Repair assistant but I am curious if anybody else had this peculiar event happen to them?
Thanks
Cellc said:
Hello, maybe somebody can help me understand. After rooting with kingo, installing safestrap, updating superSU, Making back up of Standard Rom that came from factory and updating via OTA to MJE, Installing Clean Rom 1.5 on Verizon on slot 1. Now I plug the note 3 via usb to my desktop and up pops Verizon wireless software repair assistant, What does this mean? I have not studied any further as I am charging my Zero Lemon Battery and don't want to take any chances with rootability in the future. I know I can ignored the Verizon Repair assistant but I am curious if anybody else had this peculiar event happen to them?
Thanks
Click to expand...
Click to collapse
Check and see if SDM app is in your app list. If it is freeze it with titanium. It might be SDM 1.0 also.
Harleydroid said:
Check and see if SDM app is in your app list. If it is freeze it with titanium. It might be SDM 1.0 also.
Click to expand...
Click to collapse
I did not see SDM app or SDM 1.0, I checked using titanium back.
Thanks for the suggestion.
I just started to receive messages yesterday that AT&T is pushing an update to my phone. I don't want to install it because I don't know how it will affect my root status. I'm still on stock ROM, but rooted and de-bloated. Anyone know if this is safe to install? Has anyone with root accepted it?
Silently got this update pushed to mu phone because I forgot to freeze software updater in Tibu. Luckily the update failed. I do not know if it was because I had done the v15 fixes mod/pack, or because of root, but I got lucky.
I would not update period, until somethind is released to keep, or reroot. If I am not mistaken, updates have a kernel in them, so it would over write the engineer kernel.
My bet is ATT did something to block flashing the kernel back.
Good call, I'd better not update. I connected WiFi and it just downloaded the whole package and kept on my bar asking me to update. I just froze the AT&T Software Update too, all better.
It's the pg1 update and the engboot kernel still works for root.
Sent from my VK815 using XDA-Developers mobile app
Ok so my Verizon S5 is running on Kitkat using the NI2 firmware and rooted using the towelroot method - flashing the NCG, rooting and reflashing the NI2.
The phone keeps wanting to take the OTA and my son keeps hitting accept forcing me to reflash about once a month.
Haven't really researched this too much as she's happy with the phone, but I would like for the sake of my sanity and wifi tethering to update this phone to the most recent firmware possible and keep root. Also getting tired of the annoying update notifications.
Would like to keep a stock ROM as I have had some issues with custom ROMS.
I'm sure someone can point me in the direction of an already established thread.
Thanks.
You could disable the system update app and that will stop you from getting the update notification. I used titanium backup to freeze it
Sent from my SM-G900V using Tapatalk
I would recommend updating to marshmallow (PF4) if you have the 15xxxx eMMC and can unlock your bootloader.
I just upgraded from KitKat over the weekend and a bunch of my issues with my phone (lots of Force Closes) were resolved.
Follow this excellent guide: http://forum.xda-developers.com/ver...ewbies-guide-to-install-pb1-rom-root-t3481826
Either way, whether you choose to update or not, you should use Titanium Backup to freeze SDM 1.0 (according to guides. But showed up as "System Updates 1.0" (the one with the icon) on my phone with Marshmallow). That will block the OTA installer/notifier.
Royal2000H said:
I would recommend updating to marshmallow (PF4) if you have the 15xxxx eMMC and can unlock your bootloader.
I just upgraded from KitKat over the weekend and a bunch of my issues with my phone (lots of Force Closes) were resolved.
Follow this excellent guide:
Either way, whether you choose to update or not, you should use Titanium Backup to freeze SDM 1.0 (according to guides. But showed up as "System Updates 1.0" (the one with the icon) on my phone with Marshmallow). That will block the OTA installer/notifier.
Click to expand...
Click to collapse
Seconded. I followed this guide step by step and was able to update my phone as well.
Odin to root. Xposed. Custom gapps. After about a week, multiple apps will begin to force close at random. Reboot in a bootloop on the att screen. Only solution is to master reset and start again. This has happened twice now. Is the problem in busy box? Xposed?
had this happen to me too, exactly the same deal. in fact happened just now ugh. att s7, not the edge model but whatever.
Same thing here but this is the third time. Tried different root methods each time. Xposed framework is the only common denominator so far, doesn't seem to make any sense as the phone runs great and it's always around day 7 of the root that the phone starts stopping apps and services and that's when I know I have time to move any important photos or app information and perform a complete overhaul. Any ideas what could be causing this?
has nothing to do with root. in package disabler, disable policy updates and system updates and att updater
the policy updater was doing what you are describing to my phone
Awesome! Thanks for the info, I disabled the policy updates. Appreciate the help!!
demoicurn said:
Odin to root. Xposed. Custom gapps. After about a week, multiple apps will begin to force close at random. Reboot in a bootloop on the att screen. Only solution is to master reset and start again. This has happened twice now. Is the problem in busy box? Xposed?
Click to expand...
Click to collapse
I tried to master reset my s7 edge att version and its still stuck in boot loop. Also I tried odin too. Any ideas?
demoicurn said:
Odin to root. Xposed. Custom gapps. After about a week, multiple apps will begin to force close at random. Reboot in a bootloop on the att screen. Only solution is to master reset and start again. This has happened twice now. Is the problem in busy box? Xposed?
Click to expand...
Click to collapse
I had the same problem back on android 6.0.1 and on 7.0. The problem is with the engboot. It's not stable enough to be used everyday. If you wan' t root, I recommend flashing stock firmware and waiting for this guy named Nitay Artenstein to come out with a root. He is currently testing s7 Qualcomm variants to see if his exploit works.
TomatoesOnBluRay said:
I had the same problem back on android 6.0.1 and on 7.0. The problem is with the engboot. It's not stable enough to be used everyday. If you wan' t root, I recommend flashing stock firmware and waiting for this guy named Nitay Artenstein to come out with a root. He is currently testing s7 Qualcomm variants to see if his exploit works.
Click to expand...
Click to collapse
Beyond that his exploit is aimed to be a bootloader unlock which will open the flood gates for development.
Is bootloop when it's stuck on att logo screen and pulsating and won't turn off unless from recovery? Because if so I'm having that problem. I didn't know my s7 edge was rooted until this problem started
First off.
1. There is a search button for a reason. Please use it guys.
2. The boot loop is caused by the Security policy updater trying to force the policy to update on the Engboot. The Engboot Security policy and the ATT stock Policy dont mix well when trying to be over written.
3. The engboot is perfectly fine for daily use. been using it for months with no issue. Its all the extra add ons people keep trying to Mess with and install that make it unstable.
To fix:
Odin stock firmware.
ReRoot with Engboot and disable security policy updates.
Also. There will NEVER be an unlocked bootloader for the ATT Variant of this device. Whoever tells you that they are working on a bootloader exploit is lying. Whoever says they have an unlocked att bootloader is also lying. This goes back to step one of this post. USE THE SEARCH BUTTON!!!!!!!!
Mod/Admin Please close this post.