Hello, I have been rooted since I got the s3 pretty much around launch. Today around lunch I noticed an update download progress so I swiped down, long-touched, and the process said SDM 1.0. It had just finished downloading and then telling me to install now/later.. I paniced and put Later and then I specified 10am tomorrow... maybe I should have killed it?
Anyway, why the heck did I get this notification? I have been rooted forever loving my Dandroid ROM... will my phone screw me over by installing 4.3 tomorrow?
I have twrp 2.4.4.0 installed and making a backup now just in case, but I'm worried that it's going to install 4.3. I have never had an OTA update since I rooted this phone.
My ROM is 4.1.2 and I like it the way it is.
pwoz said:
Hello, I have been rooted since I got the s3 pretty much around launch. Today around lunch I noticed an update download progress so I swiped down, long-touched, and the process said SDM 1.0. It had just finished downloading and then telling me to install now/later.. I paniced and put Later and then I specified 10am tomorrow... maybe I should have killed it?
Anyway, why the heck did I get this notification? I have been rooted forever loving my Dandroid ROM... will my phone screw me over by installing 4.3 tomorrow?
I have twrp 2.4.4.0 installed and making a backup now just in case, but I'm worried that it's going to install 4.3. I have never had an OTA update since I rooted this phone.
My ROM is 4.1.2 and I like it the way it is.
Click to expand...
Click to collapse
Since you're rooted, use a file explorer to navigate to /system/app and delete "sdm 1.0." Or if you have Titanium Backup, uninstall the system app "sdm 1.0" and you'll be all set. The update.zip downloaded to /cache/fota which you'll want to delete using a file explorer.
By removing "sdm 1.0" in either of these two methods, you will no longer be prompted to update and your scheduled update reminder for tomorrow won't occur. In addition, if you go to Settings/About Phone and "check for update," this will cause your settings to crash. Don't worry, this is intentional because you removed this file.
Edit: Yes, your phone will screw you over and lock your bootloader down in the process if you accept this VRUCML1 4.3 update. Just being honest!
Thanks, SlimSnoopOS!
I did the app/update removals with Root Explorer. I went to Titanium initially, but I did not see an uninstall option, just freeze or remove.. but the remove option gave me some yes/no popup to use some recovery trick and I said to myself... yea going to Root Explorer. I'm just wondering why I got this push in the first place...never got any notifications from VW/Samsung since I rooted this bugger.
pwoz said:
Thanks, SlimSnoopOS!
I did the app/update removals with Root Explorer. I went to Titanium initially, but I did not see an uninstall option, just freeze or remove.. but the remove option gave me some yes/no popup to use some recovery trick and I said to myself... yea going to Root Explorer. I'm just wondering why I got this push in the first place...never got any notifications from VW/Samsung since I rooted this bugger.
Click to expand...
Click to collapse
Hey, as long as it works! :good::good: haha If you're using a VRBMF1 4.1.2 based custom rom, then this is the first update since VRBMF1 was released last year on our S3. Alls well that ends well of course.
SlimSnoopOS said:
Hey, as long as it works! :good::good: haha If you're using a VRBMF1 4.1.2 based custom rom, then this is the first update since VRBMF1 was released last year on our S3. Alls well that ends well of course.
Click to expand...
Click to collapse
For some reason my phone has been very slow since about a day or so after my initial post. I have done nothing except delete the files. I am starting to wonder if maybe my device is just getting old... I've had it since it launched...now I'm really thinking about the S5. LOL
Anyway, just wondering if anyone has had a degradation of performance with their S3 lately... the most noticeable lag has been with Twitter and Facebook. For example, I will click someone's Twitter post to see replies or a picture that they posted with the tweet, but it takes forever for that information to load..Facebook is not as slow, but still noticeable (e.g. clicking to see comments).
Related
So after reading that the 2.3.6 update should not cause loss of root (i used zergrush oneclick), I decided to go ahead and do it OTA.
Unfortunately I was on a conference call for work and forgot to unfreeze the apps I had previously frozen with TiBu.
Started the update, it got to 75% and then said "update failed" and restarted. Everything seems fine.
I went into TiBu, unfroze everything and went back to update. I checked for the update and it is saying I am up-to-date, and to check back in 24 hours, but the phone is still on 2.3.5.
Any thoughts on how to force it tonight (or later if it does not want to do it on it's own)
Figured I would ask first before messing around anymore.
Yes push menu settings date and time uncheck automatic and change your date to a day from now manually then u can get the update
silver03wrx said:
Yes push menu settings date and time uncheck automatic and change your date to a day from now manually then u can get the update
Click to expand...
Click to collapse
Thanks for the quick answer.
Unfortunately, while that did allow me to check again for updates, it is still saying my phone is up to date, despite showing as being on 2.3.5
I don't think the TiBu frozen apps prevented the OTA update... I was rooted using SuperOneClick 2.2 on 2.3.5. I did the OTA 2.3.6 update with 18 apps frozen with TiBu and it updated fine... I retained root... 18 apps still frozen... LauncherPro and all my widgits still functional. We're you on stock Recovery?
Sent from my SAMSUNG-SGH-I727 using XDA App
Vaguely embarrassed but I think so? I have a new kid so much less time to play with phones.
Took a stock phone, rooted with zergrush, added super user so I could use TiBu to freeze bloat and some of the advanced juice defender and widget locker capabilities and that is it.
Sent from my SAMSUNG-SGH-I727 using XDA App
Any solution for this yet?
I did the same thing, had mulitple apps and services frozen. I keep getting the already updated message.
Sent from my SAMSUNG-SGH-I727 using xda premium
[/COLOR]http://api.viglink.com/api/click?fo...us/mNUNsVbYm&jsonp=vglnk_jsonp_13221191523521
HERE PEOPLE 2.3.6 flashable zip uploaded by mikeyinid
mikeyinid said:
OK, here it is. But, after I was about halfway through the upload, I remembered I puller some stuff out. The main thing I was concerned with is the visual voicemail.apk. Hope you guys can get it from the market like we can on tmobile. Anyhow, here is the rooted 2.3.6 rom. Please, after first boot, go back into recovery and fix permissions.
Click to expand...
Click to collapse
Honest ive been searching for an hour, how do i stop the update from happening. Not permanently, hopefully like blocking the update app with Titanium like i did on my Galaxy S3. Also, the location of the already downloaded file so i can delete it. Thanks
Honestly!!?? Is this really that dumb of a question? I honestly still cant find how to block the JB update. Please anybody?
I would love to know that too. I really don't want to hit the update by mistake...
Honestly, just make sure you honestly don't click the update button. Honestly that's all there honestly is to it...honest!:laugh:
Honestly
The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's
After some research I found that renaming otacerts.zip (in /system/etc/security/) with a .bak at the end could prevent the update to start but the notification is still here.
I tried to stop the Firmware Update Utility in app manager, even by renaming it with a .bak in /system/app/ . The notification is still here, but it seems that the popping window is not showing. Time will tell.
I saw somewhere that renaming the fingerprint line in build.prop woud work, luring the update into thinking the firmware is already up to date, but since I never touched this file (android newbie here!) I will wait for someone more experienced in modifying that kind of things...
If you are rooted, edit your build.prop (back up your original) and then tell the tablet to update. The update will fail (red triangle) and will reboot into ICS. The notification should go away and you will have to update manually.
Ok but what to edit in build.prop?
Gamlus said:
Ok but what to edit in build.prop?
Click to expand...
Click to collapse
Check this thread in the development section. There is a tweaked build.prop that I used before my upgrade. That is what caused my OTA update to fail. BE sure to use the correct file and back up your current build.prop.
http://forum.xda-developers.com/showthread.php?t=1641219
Yes !
I didn't actually changed the whole build.prop, but I downloaded the stock JB build.prop to take the fingerprint line.
So, after a backup of my build.prop, I changed this line :
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.3.30-20120604:user/release-keys
With this one :
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.2.9-20120809:user/release-keys
And now, no more notification, after a reboot and a failed install of JB.
Thank you !
turdbogls said:
The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's
Click to expand...
Click to collapse
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers
with my previous returned tf300: after i turned it on the first time it downloaded the ICS .30 firmware and asked me to update, i installed it. then i was curious why it did not download the JB update, so i went to check update manually, it started downloading the jb update and i had to update to jb. after a few days because of hardware problem i returned it.
my new tf300 came yesterday, and the same thing above happened, i updated to ICS .30, now i try to remind myself to not accidentally manually check for update, sounds weird, right? i see cmclient and dmclient always running but it never knows that there's a update lol. and i usually don't go to about tablet so i guess i won't do manual update accidentally.
bige914 said:
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!
Gam3r 4 Life said:
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!
Click to expand...
Click to collapse
Thanks +1
Worked for me too...
neur28 said:
Thanks +1
Worked for me too...
Click to expand...
Click to collapse
Does your stock email app work now? After freezing the DM client the stock email app gets stuck at waiting for sync.
Nevermind. I defrosted the dmclient and email still didnt work. So I rebooted. Saw the update again. So I refroze dmclient, then restored my email app and data in titanium and that fixed it.
I'm glad I helped all of you and enjoy your tablets as I am :3 screw Asus JB update we D block that yo
Sent from my HTC Ruby using xda app-developers app
Ok, this morning my phone started downloading the VZW update. I'm stock-Rooted with Wallet and Google Now running. When the update was finished downloading it gave me a few minutes to accept or to defer. I chose the defer button and then it ask's me to pick a time later today to do it. How do I get out of this? I don't want to run the update.
Thanks
dbow32 said:
Ok, this morning my phone started downloading the VZW update. I'm stock-Rooted with Wallet and Google Now running. When the update was finished downloading it gave me a few minutes to accept or to defer. I chose the defer button and then it ask's me to pick a time later today to do it. How do I get out of this? I don't want to run the update.
Thanks
Click to expand...
Click to collapse
Download Titanium Backup from the Play store, run it, go to the Backup/Restore tab, scroll down to "SDM 1.0" and uninstall it. You should probably make a backup of it first just in case you ever need to get it back, but I've never read of it being used for anything other than pushing Verizon OTAs, which you will probably never want to receive if you're rooted.
If you have the paid version of Titanium Backup, you can "freeze" the app instead, but uninstalling it with the free version works too.
Thanks, I really appreciate your help
I tried freezing it before I received the update and that didn't work. Guess its somehow overridden by Verizon.
Sent from my SCH-I535 using Tapatalk 2
ef-civic said:
I tried freezing it before I received the update and that didn't work. Guess its somehow overridden by Verizon.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had to reboot after freezing it for it to stop downloading
Jacquestrapp said:
Download Titanium Backup from the Play store, run it, go to the Backup/Restore tab, scroll down to "SDM 1.0" and uninstall it. You should probably make a backup of it first just in case you ever need to get it back, but I've never read of it being used for anything other than pushing Verizon OTAs, which you will probably never want to receive if you're rooted.
If you have the paid version of Titanium Backup, you can "freeze" the app instead, but uninstalling it with the free version works too.
Click to expand...
Click to collapse
I have not received any prompts for OTA updates yet and was curious as to why that is. Apparently, some ROMS are coded without the SDM 1.0 file because I am running Clean ROM 2.5 and cannot find SDM 1.0 anywhere in the list. Another reason why Scrosler and CleanROM are boss!
mooremh said:
I have not received any prompts for OTA updates yet and was curious as to why that is. Apparently, some ROMS are coded without the SDM 1.0 file because I am running Clean ROM 2.5 and cannot find SDM 1.0 anywhere in the list. Another reason why Scrosler and CleanROM are boss!
Click to expand...
Click to collapse
Any custom ROM worth its salt should not include the SDM app, CleanROM isn't special in that regard.
About 30 minutes ago my phone was working fine, the last thing I remember doing was sending a text. A few minutes later I look down at my phone and notice it is in recovery. At this point I'm confused wondering how it got there, but figure it's whatever and reboot into system. It reboots back into recovery and at this point I'm kinda freaking out. I do a backup, wipe, and restore from a backup ~2 weeks ago. Again, rebooting just causes my phone to go into recovery.
Earlier today there was a notification on my phone about an update but I just ignored it as I didn't have time to deal with it. I assume that it automatically was applied and that is what caused this problem.
edit: If you have this problem, try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
nest75068 said:
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
Click to expand...
Click to collapse
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
elguy said:
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
Click to expand...
Click to collapse
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
nest75068 said:
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
Click to expand...
Click to collapse
Yeah, worked me too. Not sure what happened either, phone says its still on KVT49L.D85010d.
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I was the same - the zip file fixed my issue - didn't have to start over
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
esoteric1311 said:
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
Click to expand...
Click to collapse
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
nest75068 said:
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
Click to expand...
Click to collapse
Well i had to restore the newest back up, because I restored an old back up to see of it would reboot correctly. All works fine now. Still very weird.
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I mean I still have Root and TWRP, I might have factory reset in my panic last night before finding the fix above. Probably the cause of losing all my apps and data
ATTT Forced UPDATE
It would appear after cruising the forums this morning that ATT forced an update to all users last night. It happened to me and many others like yourself. even people that had turned off updates in the hidden menu. It is total crap and not to happy about it obviously. good thing it sent me into a boot loop, and @autoprime zip fixed me up, even though i was back up on stock rooted, I took this opportunity to move over to the PoweruserV1 international rom to attempt to keep this from happening again. Luckily our DEVS are getting development moving and soon this will be a thing of the past....
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
KennyG123 said:
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
Click to expand...
Click to collapse
whats the name of the apk to freeze? Thanks
Just adding to this, that it was 'forced' onto me as well, and also sent me to soft brick loop (TWRP), so I'm having to use the get out of jail thread. THANKS LG!! YOU GUYS ROCK!!! (#[email protected]%&*!!!!) This is the LAST time I trust another corporate BS liar's announcement that they care about the 'community' and are going to try and be nice 'from here on out'. Moving forward, it will be NEXUS and nothing else for me.
esoteric1311 said:
whats the name of the apk to freeze? Thanks
Click to expand...
Click to collapse
It is called Software Update in TB. I only have it frozen since last night so hopefully this does the trick...it also removes update option from settings FYI.
Anyone else have this happen again last night? Phone was fine at 5am, woke up at 8:30 to recovery. Flashed the same zip and now it's all fine again.
Freeze software update with titanium backup so your phone doesn't try to install the update agian
wow att and their updates f*** with everything, currently having a locked s4 with old firm of mf3. i plan on upgrading my device but on the fence with all this lock down bs. switching to tmobile seems like a decent option...... so confused and undecided
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.
Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.
I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.
I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.
Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.
aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.