Verizon is pushing out an OTA update for VCast, Slacker, and other stuff.
Anyone have some experience with this? Is it going to un-root my phone? Because that would be, well, a pain.
I'm pretty sure that it won't unroot it, but if you made any modifications to the stock applications, it won't even run. It would fail the md5 or signature tests or whatever.
At least thats how I remember it working last time.
And wrong section.
The update has been pushed to my phone. Now I'm getting that annoying popup every 30 seconds to update my software. I'm running the warm two point two rom which is based off of the evo framework. Should I try to do the update and let it fail or not?
Sent from my ADR6300 using Tapatalk
That pop up is annoying. Where is the update stored? I checked the root of my SD and it is not there. I was thinking of just deleting it.
tech9ne said:
The update has been pushed to my phone. Now I'm getting that annoying popup every 30 seconds to update my software. I'm running the warm two point two rom which is based off of the evo framework. Should I try to do the update and let it fail or not?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Me too! I wonder what we can do.
I chose Restart & install,but nothing happen
http://forum.xda-developers.com/showpost.php?p=9150733&postcount=5
Tried replacing text in build.prop folder as link above suggests. No dice pesky update in notification bar still present.
Sent from my ADR6300 using Tapatalk
I'm running Myn's 2.2,too. Choose to update with the OTA. I think it tried to update but failed. Didn't get an error message. The best thing is the nagging message went away and I still have root.
Sent from my Incredible using XDA App
val1121 said:
I'm running Myn's 2.2,too. Choose to update with the OTA. I think it tried to update but failed. Didn't get an error message. The best thing is the nagging message went away and I still have root.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Same here. I see no changes at all as of now.
Moved to Q&A as not development
Kinda new but I had to hack a lot to get it installed
I was getting the popup as well and it was failing every time. You can download the OTA and try installing it from the recovery but if you removed any VZW app's it will fail more specifically VzNav.apk in my case.
I did some poking around the OTA update once I downloaded it. The file "updater-script" in META-INF\com\google\android is the file I modified to remove the asserts for the apk's I removed once rooted.
After the install was complete I used the instructions on the site below to redo root, but I have s-off so I believe if you don't have that it won't work for you.
solo.dc3.com/dinc/
Related
http://rapidshare.com/files/447278039/e1f2c3c89878.update_DJ30_to_EA24.zip
is it ok to do OTA if you're rooted?
Yup works fine. sofar sogood..
How bout if u have Cwm and voodoo kernel installed?
Sent from my PC36100 using Tapatalk
I installed the update, lost root and haven't been able to run z4root to root my device since then. However this update fixed the problems I had with using gmail exchange servers in the samsung e-mail app. Now I just need to get rooted again and figure out how to disable gmail app notifications.
you tried one click root?
Not yet, I'm at work right now and my work machine is running linux. I was planning on trying it tonight when I got home
Update and info
Baseband - S100.08.EA24
Build - SPH-P100.EA24 2/7/2011 This update offers:
- QIK software update to 0.04.77
- Addition of Sprint start up and shut down screens
- Fixes intermittent email count missing issue
- Fixes problem with addresses in "to" field displaying incorrectly
- Addresses email hang-up in low coverage
- Offers ability to add contact to address book
http://support.sprint.com/support/a...2-20101102-163753#__highlight&id16=galaxy+tab
Does this update have a locked bootloader?
After the update it still rooted
Sent from my SPH-P100 using XDA App
OT
For those of you who are rooted, which method seems to be best right now.
I want to do it but was waiting to see some rom action
Also is everyone using the same recovery these days?
I was looking for Sprint specific info but its kind of muttled up in here.
Thanks
Im having the same issue. I am really keaning toward a T-Mobile Tab or the ipad2.
Sent from my SPH-P100 using XDA App
I definitely LOST root when I applied the update, I tested and retested with multiple root apps, also I couldn't unroot or root using z4root at all after this, z4root would simply crash. However using oneclickroot on PC I was able to root the device again after the update and I was able to run lcd density and all my other root apps again.
might i ask how you actually pulled this update and zipped it up? Where are ota updates located on the system?
any modem files in this.
I did not lose root when I installed the system update that came OTA. I originally rooted with z4root.
Sent from my SPH-P100 using XDA App
how strange, did you confirm that the update actually installed successfully? I wonder why mine would lose root and yours wouldn't.
IMPORTANT INFO ABOUT UPDATE
If you guys changed your WPA_SUPPLICANT file to allow AD-HOC networks, the update FILL FAIL.
So restore the original/stock WPA supplicant file before you try the update, or itll just fail and made no difference. I'll keep you posted, im going to do the update right now
Also make sure your using STOCK DPI LCD Density or it will fail as well. Its stock 240.
go back in to your about galaxy tab and check for updates and check for new firmware; if it hasn't installed yet then I believe that it should attempt to install again. You can match the new baseband version, build number, and qik version to see if you are running the new update.
it tried to install before OTA but failed due to different WPA_supplicant and LCD Density change (give a buildprop error).
Now im doing the manual update, i just changed the zip to update.zip. Now it seems to be working.
UPDATE COMPLETE: btw, the new sprint logo is CRAP. i liked the original Samsung Logo! anyway to change that back. I'll keep you guys posted on any new things i find.
Ok this does Break ROOT!
If it doesnt break root for you, then the update did not go through. Check your settings "about my galaxy tab".
My update is failing because I'm running a modified Gallery. Like an idiot I didn't backup the original app. Anyone know where I can snag a copy of the stock Gallery3D.apk and .odex?
-edit-
Nevermind... found a modified ROM that was using the stock Gallery app. Just pulled it from that and presto, update applied without errors.
-edit
Hmm... though when it rebooted it said the update failed to apply and I should try again. Though the sprint logo at boot the version numbers tell a different story. Odd.
Hi Guys and Girls,
I got a little popup today to tell me that my phone is due an upgrade to 2.51.1 -
I selected download, then realised this might not be a bright idea.
The upgrade hasn't been done yet, but I'm being continually prompted to "Install now" and I have to keep selecting "Install later".
1. Where is the update that downloaded to my phone (so I can delete it)
2. How can I disable future OTA updates
I believe if you rename the BlurUpdater.apk in /system/app, that should stop it. This thread should help (http://forum.xda-developers.com/showthread.php?t=856104).
For example, I just renamed BlurUpdater.apk to BlurUpdater.rem.
Ok, I moved Fota.apk and BlurUpdater.apk - hopefully that should stop the nagging.
AFAIK 2.51.1 has been rooted now, but there's no JIT/DEOX build available yet (ala Frozen Eclair)?
Doesn't seem like there is. But if you check out the Frozen Eclair thread in Android Dev, looks like someone was able to load the 2.34 JIT onto a phone with 2.51.
http://forum.xda-developers.com/showpost.php?p=11168992&postcount=153
Well after reading that 2.51.1 is supposed to be much better than 2.21 I figured I may aswell upgrade, especially since it has been rooted.
So I removed the permanent root and tried the OTA update, but it failed about one third in on the progress bar and displayed an exclamation mark with the little android robot. Any ideas?
Sent from my MB525 using XDA App
I'm not sure about the 2.51 update as I'm on T-mobile USA. But I remember some people saying that if you remove any of the original apks, you'll need to replace them to stock. Again, I know that applies to the T-Mo USA update, not sure about anything else.
Oh, its worth mentioning that I did put the stock applications back on.
Sent from my MB525 using XDA App
can someone point me i'm the direction of this thread? i've seen it b4 but haven't been able to find it now. Thanks in advance.
Sent from my SPH-D700 using Tapatalk
Let it install it will fail pop out the battery and it will boot into cwm then just reboot
Sent From My "epic" SPH-D700 via XDA Premium
What Biggie said. The threads you are looking for are in General. As long as you are not fully stock it will fail and probably boot into CWM after popping battery and rebooting. Just hit reboot system.
Sent from my SPH-D700 using XDA App
I have allowed it to fail, let it boot to CWM, but it just keeps coming back. It is quite annoying. Does anybody have a way to stop it?
mikebarr said:
I have allowed it to fail, let it boot to CWM, but it just keeps coming back. It is quite annoying. Does anybody have a way to stop it?
Click to expand...
Click to collapse
Google Fotakill. It is an app you have to put in your system\app directory.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Google Fotakill. It is an app you have to put in your system\app directory.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I tried FOTAKILL, it worked when I was on EC05 to stop the OTA prompt.
But it's not working for me this time. The only thing that stops it for a while is doing like you said. Accepting the update & letting it fail. It came back again one time since then & I did the same thing, this has fixed it for now. But I do still have foatakill installed if that matters.
At least I have a way to stop the prompt for a week or so. I'm just waiting for CleanGB MTD to be updated.
Not sure if it's any help, but according to the Sprint Rep I spoke with, all security updates come from Samsung. If that is true, its very disturbing. I have used the superfreeze and am running a gingerbread based rom already that does NOT have Carrier IQ. I did find the update zip in the system cache and deleted it, but no luck. The update pops up less often though, but still annoying. With that said, Samsung still has access to download files without consent, dispite a root command to freeze updates. Again very disturbing. []
jerm1027 said:
Not sure if it's any help, but according to the Sprint Rep I spoke with, all security updates come from Samsung. If that is true, its very disturbing. I have used the superfreeze and am running a gingerbread based rom already that does NOT have Carrier IQ. I did find the update zip in the system cache and deleted it, but no luck. The update pops up less often though, but still annoying. With that said, Samsung still has access to download files without consent, dispite a root command to freeze updates. Again very disturbing. []
Click to expand...
Click to collapse
Check the op of my thread in general on how to stop the update message for a PERMANENT fix to the update message...
Sent from my CM9'd epic!
I copied this from a thread in development. This works great. Open up an adb shell. Copy/paste this and run it. It modifies the build.prop file to identify your system as 2.3.6, which will stop the update prompts.
Code:
su
remount rw
sed -i 's/SPH-D700-user 2.3.5 GINGERBREAD EI22 release-keys/SPH-D700-user 2.3.6 GINGERBREAD EL30 release-keys/g' /system/build.prop
sed -i 's/sprint\/SPH-D700\/SPH-D700:2.3.5\/GINGERBREAD\/EI22:user\/release-keys/sprint\/SPH-D700\/SPH-D700:2.3.6\/GINGERBREAD\/EL30:user\/release-keys/g' /system/build.prop
remount ro
DaggettBeaver said:
I copied this from a thread in development. This works great. Open up an adb shell. Copy/paste this and run it. It modifies the build.prop file to identify your system as 2.3.6, which will stop the update prompts.
Code:
su
remount rw
sed -i 's/SPH-D700-user 2.3.5 GINGERBREAD EI22 release-keys/SPH-D700-user 2.3.6 GINGERBREAD EL30 release-keys/g' /system/build.prop
sed -i 's/sprint\/SPH-D700\/SPH-D700:2.3.5\/GINGERBREAD\/EI22:user\/release-keys/sprint\/SPH-D700\/SPH-D700:2.3.6\/GINGERBREAD\/EL30:user\/release-keys/g' /system/build.prop
remount ro
Click to expand...
Click to collapse
Yep same method in my thread in general
Sent from my SPH-D700 using Tapatalk
Noooo...your method was in General so it must not be right...only the one from Development should work...LOL.
Sent from my SPH-D700 using XDA App
DeviceManagement.apk
I have an epic 4g on rooted with cwm and cleangb. I have been irritated with the frequent system update messages I have been rec'ing lately. Yes, letting it install and then pulling the battery works fine. But I have also been looking for a way to stop the update service from running in my phone. Here's what I did:
I checked Titanium Backup ( free version ) and found "System Updates" in the list of apps under the backup/restore tab. The list wasn't sorted so I had to scroll and carefully scan each app-name to find it. Then I started to uninstall it, but I cancelled when I was prompted whether or not to uninstall DeviceManagement.apk. Now that I know the apk, I don't need to uninstall, I can rename, right? Then I went to root-explorer and browsed to /system/app. Then I hit the button to mount r/w; then I renamed DeviceManagement.apk to DeviceManagement.apk.bak. Rebooted and checked menu -> settings -> Applications to see if System Updates was running. And it's not.
Hopefully this means no more firmware updates... time will tell
hope this helps someone else out there
-disc-
Why not just edit the build.prop as suggested? Can you still update PRL? I think you will get a network error.
Just a quick update, I'm still getting update notices. So renaming the .apk def did not work.
Re: build.props
I'm totally ignorant on how to do this. Ill re-read this post from the beginning. I must have missed it.
Thanks to all,
Disc
Sent from my SPH-D700 using Tapatalk
discodan7700 said:
Just a quick update, I'm still getting update notices. So renaming the .apk def did not work.
Re: build.props
I'm totally ignorant on how to do this. Ill re-read this post from the beginning. I must have missed it.
Thanks to all,
Disc
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
With something like root explorer you just long press on build.prop , choose edit text, change all EI22 instances to EL30 and all 2.3.5 to 2.3.6, save and exit then reboot.
Why the hell would this annoying pop-up repeatedly come up in the first place... so much for the "users" right to custom ROMS. They always have to sneak some b.s. in to annoy the XDA community. Theres a conspiracy going on at Samsung {-_-}
RealTic said:
Why the hell would this annoying pop-up repeatedly come up in the first place... so much for the "users" right to custom ROMS. They always have to sneak some b.s. in to annoy the XDA community. Theres a conspiracy going on at Samsung {-_-}
Click to expand...
Click to collapse
I think it is because they consider it a security update to remove CIQ.
Sent from my SPH-D700 using xda premium
Hi,
I finally got back to this. As previously stated, renaming devicemanagement.apk didn't do anything regarding the autoupdate notification. I was indeed nolonger able to do a prl or profile update via home-screen -> menu -> settings -> about phone -> updates. Not only that, but, I got a little foolhardy renaming stuff in /system/app when I started getting the update notices. Long story short, I've gone back thru, re-renamed everything back from .bak to .apk with rootexplorer, and I'm still not getting my vmail downloaded to my phone.
Back on track now... as suggested, I used rootexplorer to edit /system/build.prop. only 2 instances needed to be updated. 1 from EI22 to EL30, and one more a few lines down from that, updating 2.3.5 to 2.3.6. Hopefully this will quiet the autoupdate gremlins.
Sent from my SPH-D700 using Tapatalk
Update: rebooted phone, and I still had the update to el30 in my notifications. I suspect that since the update was auto-downloaded pre-updating build.prop that I would continue to get update nags till I did the "go ahead and install update / pull battery" trick one last time.
So I did that one last time hoping that the update will nolonger auto-download since build.prop references the current versions.
Thanks for everyone's help. Hope someone else finds it useful.
-disc-
Sent from my SPH-D700 using Tapatalk
Uh-oh, rebooted my phone today and was greeted with an auto-update nastygram. Ill recheck my build.prop. to see if I missed anything. If not, I think there's an adb method described earlier in this thread. Ill try that and report back.
Sent from my SPH-D700 using Tapatalk
Sending from my phone.
Problem #1: I'm running RandomRom EI22 and I've done every step to prevent the System Update message, however it's still popping up. Definitely made sure I erased the systemupdate apk and everything else. What other methods are there to make it stop being such a nuisance?
Problem #2: I uninstalled regular Swype and installed the beta, ever since the original kept asking for a system update. After installing the beta, it worked fine. Now everytime I try, it keeps saying "Try again".
Volknochi said:
Sending from my phone.
Problem #1: I'm running RandomRom EI22 and I've done every step to prevent the System Update message, however it's still popping up. Definitely made sure I erased the systemupdate apk and everything else. What other methods are there to make it stop being such a nuisance?
Problem #2: I uninstalled regular Swype and installed the beta, ever since the original kept asking for a system update. After installing the beta, it worked fine. Now everytime I try, it keeps saying "Try again".
Click to expand...
Click to collapse
Do a search here on "FOTAKill.apk" - that was the only thing that helped me on both my phone and my wife's - but we are on Froyo so this might not work for you.
With that being said, all of what you tried has been suggested for Froyo users also, but didn't work - so give it a try. Sometimes the search on XDA doesn't seem to work well for me - so what I do is use Google, and in the search terms I type "XDA FOTAKill.apk"
You have to edit your build.prop to say 2.3.6 and EL30 in all places where it says EI22 and 2.3.5. Then reboot.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
You have to edit your build.prop to say 2.3.6 and EL30 in all places where it says EI22 and 2.3.5. Then reboot.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Okay.....so how do I go about doing that?
Volknochi said:
Okay.....so how do I go about doing that?
Click to expand...
Click to collapse
With Root Explorer. Edit build.prop in system directory.
Sent from my SPH-D700 using xda premium
EDIT: I did the trick of allowing it to do an update, then I let it reboot, it goes to the "Triangle !" mode, wiped Dalvik and rebooted, and so far, it hasn't popped up yet.
Now to fix Swype...
Volknochi said:
EDIT: I did the trick of allowing it to do an update, then I let it reboot, it goes to the "Triangle !" mode, wiped Dalvik and rebooted, and so far, it hasn't popped up yet.
Now to fix Swype...
Click to expand...
Click to collapse
It will be back within a week.
Sent from my SPH-D700 using xda premium
If it'll be back within a week, then does that mean that there's no way of getting rid of that update message?
Volknochi said:
If it'll be back within a week, then does that mean that there's no way of getting rid of that update message?
Click to expand...
Click to collapse
I mentioned what has to be done before. Build.prop has to be edited.
Sorry, thought I mentioned that I did. My fault.
Yes, I did edit the build.prop file through Root Explorer, per your advice. Even after I did the final editing (missed a couple), the message still popped up. But, that's when I did the cache clearing and it didn't pop up again upon reboot.
Volknochi said:
Sorry, thought I mentioned that I did. My fault.
Yes, I did edit the build.prop file through Root Explorer, per your advice. Even after I did the final editing (missed a couple), the message still popped up. But, that's when I did the cache clearing and it didn't pop up again upon reboot.
Click to expand...
Click to collapse
Ok, that makes sense because the message was still in your phone's queue.
Sent from my SPH-D700 using xda premium
If you are on a MTD rom, someone in another thread suggested going back to regular swype. You can get the appropo files from the Starsky ROM, this is one of the few MTD roms that uses swype still, and the only files that I found work.
http://forum.xda-developers.com/showthread.php?t=1242335
system/app/swype.apk
system/lib/swypecore.so
I pushed using Root Explorer and got mine working again
The 'Android Update to EL30' is not removed by uninstalling system updates.apk that apk is meant to provision your Epic to Sprint. The Update Notification is caused by the 'Google Framework' Service. There may be ways to fool it, such as the buildprop edit suggested.
Sent from my piece of **** SPH-M910 using xda premium while my CM9 Alpha 4 Epic is resting in my pocket. (Very Handy) it's like having a spare battery but better.
My phone is rooted and it wont update OTA. How can i permanently ignore this stupid dialog box popping up every 2 minutes on my phone about the upgrade to 4.0.4?
You could try freezing the update process through your task manager/etc. Hope this helps.
Sent from my Amazon Kindle Fire using XDA
Just change your build prop and add the latest version to it. Its a quick 2 second text change. I just don't have the exact text to be copied. Its around here somewhere in one of the threads though.
cleoent said:
My phone is rooted and it wont update OTA. How can i permanently ignore this stupid dialog box popping up every 2 minutes on my phone about the upgrade to 4.0.4?
Click to expand...
Click to collapse
Rooting has no impact on OTA updates' ability to install. You must have something else that is not stock on your device.
As for how to disable it, you need to edit your build.prop file. Change the line that starts with ro.build.fingerprint to whatever it is on an IMM76K ROM. Ask someone who is already running it for the correct text.
Sent from my Galaxy Nexus using Tapatalk 2
is this all you need?
ro.build.fingerprint=google/mysid/toro:4.0.4/IMM76K/336647:user/release-keys
slimb9 said:
is this all you need?
ro.build.fingerprint=google/mysid/toro:4.0.4/IMM76K/336647:user/release-keys
Click to expand...
Click to collapse
Yup, that is what the OP needs. All he has to do is change his ro.build.fingerprint to match that, and he will no longer get the OTA notification.
I dont know anything about build props. Damn.
I also have nothing else done to my phone, just root. I dont think i even have any programs that need root, just did it to do it.
Ballarous said:
You could try freezing the update process through your task manager/etc. Hope this helps.
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
Bingo, freeze the Software update app with some like ROM toolbox.
cleoent said:
I dont know anything about build props. Damn.
I also have nothing else done to my phone, just root. I dont think i even have any programs that need root, just did it to do it.
Click to expand...
Click to collapse
Build.prop is just a text file in the root directory. You can browse to it with root explorer and edit it. Just make a copy of the original and stick it somewhere sexy before doing your edits incase you change something incorrectly.
That way you can come back and ask how to copy a backup to another location when your phone wont boot .
And heres some props for rooting just to root.
Sent from my Galaxy Nexus using Tapatalk 2
cleoent said:
My phone is rooted and it wont update OTA. How can i permanently ignore this stupid dialog box popping up every 2 minutes on my phone about the upgrade to 4.0.4?
Click to expand...
Click to collapse
I encountered the same thing after rooting. I know there are ways to force the message to stop, but it will time out after a few days. I no longer get the pop-up.
Also, even though your phone is rooted, if you click the OTA dialogue box, your phone will attempt to download the OTA update. And this could brick your phone or put you into a boot loop. So be careful not to activate it.
OTA updating a rooted phone shouldn't brick or boot-loop it. Only thing that should happen is that you won't have root after the update.
That is, unless you install OTA Rootkeeper from the app store.