I see the system update notification on my v30, are there any way to block it? since i've rooted my phone and have TWRP installed, i don't think i can update over the air.
T-MOBILE H932 SYSTEM UPDATE FREEZE/DISABLE
zrzhu said:
I see the system update notification on my v30 (H932), are there any way to block it? since i've rooted my phone and have TWRP installed, i don't think i can update over the air.
Click to expand...
Click to collapse
No, you cannot take inferior partial image OTA updates, since you are not fully stock (you have custom recovery). If you try it will just boot to TWRP.
Freeze the carrier software update files in Titanium Backup.
ChazzMatt said:
T-MOBILE H932 SYSTEM UPDATE FREEZE/DISABLE
No, you cannot take inferior partial image OTA updates, since you are not fully stock (you have custom recovery). If you try it will just boot to TWRP.
Freeze the carrier software update files in Titanium Backup.
Click to expand...
Click to collapse
I've frozen all the apps (see screenshot) yesterday, but I still saw the notification this morning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/file/d/1DsubXijulcW5mRh2iG1eBtWr8fZN3M30/view
zrzhu said:
I see the system update notification on my v30, are there any way to block it? since i've rooted my phone and have TWRP installed, i don't think i can update over the air.
Click to expand...
Click to collapse
You can't update over the air. Just follow the directions here and update your phone without losing TWRP. Once you're up to date, you won't get the notification.
https://forum.xda-developers.com/lg-v30/development/rom-h932-oreo-v20o-stock-twrp-t3863202
jsgraphicart said:
You can't update over the air. Just follow the directions here and update your phone without losing TWRP. Once you're up to date, you won't get the notification.
https://forum.xda-developers.com/lg-v30/development/rom-h932-oreo-v20o-stock-twrp-t3863202
Click to expand...
Click to collapse
I'm not planning to update to the latest security patch (12/5) over the air. i did install 20o already following the link after I first rooted my phone, but I still see the notification even frozen all the update related apps.
zrzhu said:
I'm not planning to update to the latest security patch (12/5) over the air. i did install 20o already following the link after I first rooted my phone, but I still see the notification even frozen all the update related apps.
Click to expand...
Click to collapse
Oh. I guess there is a new update that came out recently. I didn't know. I haven't gotten a notification yet. Sorry. We'll just have to wait for the next update zip to be made for us.
---------- Post added at 07:56 AM ---------- Previous post was at 07:45 AM ----------
zrzhu said:
I'm not planning to update to the latest security patch (12/5) over the air. i did install 20o already following the link after I first rooted my phone, but I still see the notification even frozen all the update related apps.
Click to expand...
Click to collapse
Also, just a theory, you may still be getting the notification because the update file might have already been downloaded to your device and waiting for you to tell it to update. I don't know where those are stored but if it's on your device and you can delete it, that may cause the notification to go away.
jsgraphicart said:
Oh. I guess there is a new update that came out recently. I didn't know. I haven't gotten a notification yet. Sorry. We'll just have to wait for the next update zip to be made for us.
---------- Post added at 07:56 AM ---------- Previous post was at 07:45 AM ----------
Also, just a theory, you may still be getting the notification because the update file might have already been downloaded to your device and waiting for you to tell it to update. I don't know where those are stored but if it's on your device and you can delete it, that may cause the notification to go away.
Click to expand...
Click to collapse
i think you are probably right. I did remember see "...install..." in the notification. Well, I'll wait for the flashable update then.
zrzhu said:
i think you are probably right. I did remember see "...install..." in the notification. Well, I'll wait for the flashable update then.
Click to expand...
Click to collapse
I just got the notification this morning. Just in case you still are wondering how to get rid of the notification, you can long press the notification and turn the system update notifications off so you don't see it anymore.
jsgraphicart said:
I just got the notification this morning. Just in case you still are wondering how to get rid of the notification, you can long press the notification and turn the system update notifications off so you don't see it anymore.
Click to expand...
Click to collapse
That will not do much since you only ignore the notification. At some point the phone will be forced to install it.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
That will not do much since you only ignore the notification. At some point the phone will be forced to install it.
Click to expand...
Click to collapse
Updates install automatically? I thought you had to hit the update button manually? Either way, the update should fail anyway since I'm rooted and have TWRP installed, right? So it shouldn't matter
jsgraphicart said:
Updates install automatically? I thought you had to hit the update button manually? Either way, the update should fail anyway since I'm rooted and have TWRP installed, right? So it shouldn't matter
Click to expand...
Click to collapse
For people with unrooted phones, OEMs/carriers can force updates no matter what you choose. They own the phone, not you. They are the admin, not you. Samsung proved that a couple years ago with the Galaxy Note forced brick fiasco. OEM/carrier forced update on all unrooted phones to brick it on purpose.
Yes, since you have TWRP installed, the OTA update may try but it will fail.
ChazzMatt said:
For people with unrooted phones, OEMs/carriers can force updates no matter what you choose. They own the phone, not you. They are the admin, not you. Samsung proved that a couple years ago with the Galaxy Note forced brick fiasco. OEM/carrier forced update on all unrooted phones to brick it on purpose.
Yes, since you have TWRP installed, the. OTA update may try but it will fail.
Click to expand...
Click to collapse
That's what I figured. So I just turned off the notification for the update for the time being. And if it tries, I have nothing to worry about.
Since the OTA is probably a large file, I'd say you should look for it and delete it. This should prevent whatever it is in the OS that is trying to apply it. Of course, it may re-download, but then you can keep looking for the app that's causing that to happen?
BROKEN1981 said:
That will not do much since you only ignore the notification. At some point the phone will be forced to install it.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I've seen this happen a lot to people. They don't install, then it starts installing anyway. They hit cancel, and that works a couple of times. Then even cancel doesn't work.
Usually happens to people procrastinating unlocking their bootloader and rooting -- and then some update prevents them from doing that. Verizon was really bad about that with the Droid Turbo phones, when the Sunshine devs found exploit to unlock bootloader. "Forced" update would prevent Sunshine from working. Sometimes would be two or three months before exploit app was updated, but there was never any guarantee it would ever be. Cat and mouse for awhile, and finally Verizon stopped caring when they stopped giving updates for Droid Turbo...
We kept telling people, just go ahead and unlock your bootloader! Verizon can't lock it BACK, but they CAN stop you from unlocking it in the first place. Stop procrastinating and just do it!
schwinn8 said:
Since the OTA is probably a large file, I'd say you should look for it and delete it. This should prevent whatever it is in the OS that is trying to apply it. Of course, it may re-download, but then you can keep looking for the app that's causing that to happen?
Click to expand...
Click to collapse
I tried to find the file, but didn't find it. If anyone knows, i'll happy to delete the downloaded update file.
zrzhu said:
I tried to find the file, but didn't find it. If anyone knows, i'll happy to delete the downloaded update file.
Click to expand...
Click to collapse
I don't have any specific advice, but if you use FX file explorer, it has a "cleanup" function which can scan the entire phone for the largest files. That might be a fast/easy way to see where it is?
mistake
if you're rooted and just want the notification gone, I was able to achieve that on my V20 and now V30 using FOTAKill.
drop FOTAKill.apk into /system/app/FOTAKill.apk perm 644, and it should do the rest by itself. It does not have a UI, but from what I gather, it intercepts the fota ota update message and notification and kills/hides it. It does more than just that I'm pretty sure because the update.zip never downloads either.
.
Sent from my LG-LS998 using XDA Labs
Related
I am running 2.2.2. I have rooted, and completely removed some of the bloat, but I uninstalled it, I did not freeze it.
If I do a hard reset, will that restore the phone to it's factory condition complete with the software I removed? I removed the VCast stuff and most of the included Verizon garbage.
It is 10:24pm EST on July 31, and I have still not gotten the 2.3.3 update. I am manually checking about every 30 minutes.
No, you would need to download the SBF file and restore the phone back to factory condition. There are countless tutorials on how to do it on here. Good luck!
Sent from my DROID X2 using XDA Premium App
SBF installed correctly, all the bloat is back and the phone is no longer rooted, although all of my settings seem the same. I cannot get it to root again. I did a wipe and *228 then reinstalled Gingerbreak 1.2.0 which allowed me to root again. I am unsure of where to go from here. Something about a bootstrap and then update.zip on external sd card to update to the pre-rooted 2.3.3?
Yes download the bootstrap, and p3droids pre rooted gb. Once you get in recovery flash the .Zip. they have more detailed instructions in other threads
Sent from my DROID X2 using XDA App
So from the recovery app I choose which option? I know it isn't going to be Charge, so it is either "Install Recovery" or the second option.
When choosing the second option, my phone does nothing except sit at the "Dual Core Technology" splash screen. I have placed the pre-rooted GB update on the root of my external SD card (not internal) and renamed it "update.zip". It didn't give me an option to install from SD card or anything, just sits there.
It appears to be doing absolutely nothing....just sitting at the dual core logo screen.
I don't want to yank the battery or press any buttons because I am unsure of what the phone is doing and do not want to brick it.
Thanks for all your help BTW. I am an old fart in a tech world, and this is my first Android phone. I love it.
Edit: AHA! I didn't hit "Install Recovery" first! I should have read the screen but I have been reading so many posts and threads I missed it.
View attachment 673039
I got the assert fail message, rebooted, and SUCCESS!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I Like Hearing Success Stories. Thanks Dude.
Now I just hope we can get a stock 2.3.3 SBF...
y0himba said:
Now I just hope we can get a stock 2.3.3 SBF...
Click to expand...
Click to collapse
Gotta Have A Dev. Make An Exploit To Gain Root Off That. Right Now We're Coming Into Gingerbread With Patched Files.
I'm amazed at how easy this was once I actually sat down and did it. In fact, I did it on two phones today.
y0himba said:
Now I just hope we can get a stock 2.3.3 SBF...
Click to expand...
Click to collapse
That would be a terrible thing, unless you don't want to root, then it's a great thing.
Sent from my DROID X2 using XDA Premium App
"SUPER-NOOB" Question of the Day
I am in Orlando and have yet to receive the OTA GB update. I do run LauncerPro Plus on my X2 - would this in any way hamper receiving the OTA update?
Told ya...."Super Noob" question
Many thanks,
Doug
If you aren't rooted you should get the ota update no issues, if you ARE rooted you don't want the ota update
Sent from my DROID X2 using XDA App
EvilTim said:
If you aren't rooted you should get the ota update no issues, if you ARE rooted you don't want the ota update
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
That actually depends on what you changed, just root itself won't stop the OTA, modifying system apps and files will though.
Sent from my DROID X2 using XDA Premium App
juhde said:
That actually depends on what you changed, just root itself won't stop the OTA, modifying system apps and files will though.
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
Reread it, I didn't say having root would stop it, I said you don't want it, you want the prerooted file
Sent from my DROID X2 using XDA App
You want the pre-rooted file, without a doubt. However, we will eventually need a 2.3.3 stock SBF to revert for further updates.
I installed the patched 2.3.3, I wonder if it can be unrooted if necessary.
I am new to this, so excuse the paranoia, but how can I be sure that this update, the pre-rooted patch, is actually 2.3.3? The system info can easily be edited to say it is 2.3.3...
It is running fine, however with the Internet the way it is today there is no telling what we just installed on our phones.
y0himba said:
You want the pre-rooted file, without a doubt. However, we will eventually need a 2.3.3 stock SBF to revert for further updates.
I installed the patched 2.3.3, I wonder if it can be unrooted if necessary.
I am new to this, so excuse the paranoia, but how can I be sure that this update, the pre-rooted patch, is actually 2.3.3? The system info can easily be edited to say it is 2.3.3...
It is running fine, however with the Internet the way it is today there is no telling what we just installed on our phones.
Click to expand...
Click to collapse
We don't need a 2.3.3 sbf because the current one still works. For future updates you'd just sbf back to 2.2.2 then pull any updates from settings. At least that's how we do it for the OG Droid.
For your paranoia cure, lots of ways. The new battery stats menu, phone bars turing colours when internet connection is established, new blur icons. The fact the phone actually runs well without modding the memory settings. All these are telling you it's gingerbread. Plus why would a respected dev like P3Droid want to lie?
Sent from my DROID X2 using XDA Premium App
Oh I agree, and I don't think he would lie, but I am old, and new to Android as well as this being the first time I have done an update in this way. I was around Windows Mobile for a LONG time, and in a lot of ways it was more simple to flash a ROM there.
This was easier however, and retained my settings for the most part. The guides here, while being a bit confusing due to grammar for me, are exactly what I need to get the job done.
How long until I need to worry about updates again?
Knowing motorola. 6 months.
Of course there will be a lot of custom ROMs out in the next few weeks based off gingerbread that you might want to try.
Sent from my DROID X2 using XDA Premium App
I have a rooted ATT M8 running the stock ROM. They recently released new firmware and my phone wants me to install. I can tell when they release one because I get a notice saying that "google services are running in the background."
I do NOT want the new firmware, but I can find no way to turn off the update service and it's causing my phone to reboot. I assume that installing this update will break my root. Anybody got any solutions?
I've been wrestling with this the last 2 nights as well. I also didn't want the firmware update. I also had the google services annoying me.
Here's my advice:
1. Take the firmware update
2. Reboot
3. Update SuperSU immediately (use the app itself, it will boot into TWRP and update as necessary, if you don't follow this step, your root WILL be broken, and your phone will likely get locked into a ~3minute reboot cycle).
You shouldn't be affected beyond this point, unless you're like me and your phone automatically reinstalls all the AT&T bloatware on every reboot.
Install Titanium backup and kill the update service. I think it is "Software Updates"
Then you won't have this problem. At least I don't.
lostangelintx said:
Install Titanium backup and kill the update service. I think it is "Software Updates"
Then you won't have this problem. At least I don't.
Click to expand...
Click to collapse
I use titanium backup and have looked for the service but the only one I see is called updater. And from what I can tell that's not the right one.
Hmm I haven't gotten any updates
Sent from my HTC One_M8 using Tapatalk
Alaris said:
Hmm I haven't gotten any updates
Click to expand...
Click to collapse
1.54 was the software version at release (April), then the started rolling out 1.58 in May. I haven't heard of any other updates rolling out yet, although an update to 4.4.3 or 4.4.4 is supposedly upcoming.
What version is your phone currently?
---------- Post added at 10:51 AM ---------- Previous post was at 10:44 AM ----------
jbwitt said:
I use titanium backup and have looked for the service but the only one I see is called updater. And from what I can tell that's not the right one.
Click to expand...
Click to collapse
Try what is stated in Post #7 here: http://forum.xda-developers.com/showthread.php?t=2752718
You can just "freeze" (instead of uninstall) the service if you're afraid of breaking anything.
Never mind. The poster above me answered it for you.
Ok I froze HTC dm. We will see what happens. I am running 4.4.2. Thanks everybody.
jbwitt said:
Thanks everybody.
Click to expand...
Click to collapse
There's a button for that.
redpoint73 said:
There's a button for that.
Click to expand...
Click to collapse
Mind telling me where? Nowhere do I see a thanks button. I'm not a forum expert, obviously.
Also, none of the above suggestions worked. Today, when I got home, the phone rebooted again. I believe getting on my wifi is what triggered it (like it was trying to download the new firmware again). I also tried accepting the update but that didn't solve it either. All it did was reboot the phone again when told it to install...and I'm still at 4.4.2.
EDIT: Err, never mind. I reloaded the page and the thanks buttons showed up.
jbwitt said:
none of the above suggestions worked. Today, when I got home, the phone rebooted again. I believe getting on my wifi is what triggered it (like it was trying to download the new firmware again). I also tried accepting the update but that didn't solve it either. All it did was reboot the phone again when told it to install...and I'm still at 4.4.2.
Click to expand...
Click to collapse
Interesting, it seemed to work for others. Try freezing updater, FOTA, and/or HTCdrm.
Freeze these
Updater.apk
HtcOMADM_SettingsPlugin_ATT.apk
HtcOMADM_ATT.apk
http://www.droid-life.com/2014/12/05/lg-g3-on-verizon-gets-advanced-calling-1-0-volte-in-update/
The update mainly brings Advanced Calling 1.0 and updates to some LG apps.
It looks like Advanced Calling also needs to be enabled on your account.
http://www.verizonwireless.com/supp...Turning Advanced Calling On/Off on Your Phone
Personally, I'd like to know if someone who is stock/rooted with no system files changed can accept the update and keep root. If anyone gets it and tests that, please report back. Also, include whether or not SuperSU is in survival mode.
With the previous update, I was stock/rooted with 1 system file that dealt with headphone volume changed. I had to restore the original version of that file, then the update completed and root was kept (without SuperSU survival mode being required).
I've done the check for updates on my phone, but nothing yet.
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
david_hume said:
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
Click to expand...
Click to collapse
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
lexluthor said:
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
Click to expand...
Click to collapse
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
I don't think survival mode is required. It wasn't went I went from 10C to 11C.
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
hawkswind1 said:
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
Click to expand...
Click to collapse
From what I read somewhere, I think you can turn it off if you don't like it. My update completed, it's optimizing apps now. Will post once I confirm I've kept root (or not).
I just updated mine. I upgraded from 11C and still have root. I put my SU in survival mode just in case, but I'm not sure if that was necessary or not.
Also, for those that are worried about being stuck on VoLTE. There's a new entry in the Settings menu that lets you turn the "Advanced Calling" on/off at will.
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
EDIT: nvm, got it.
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
xdabbeb said:
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
Click to expand...
Click to collapse
I 2nd this!
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Same thing here. I hope there is something else other than using LG Flashtool to download the stock firmware
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Here's another thing i'm noticing... before, I downloaded a couple UI themes to change the nav buttons at the bottom through g3 tweaksbox and after removing g3 tweaksbox, the buttons changed to stock on the home screen but if I go in to settings or any other app it still shows the "LG" logo as my "home" button... maybe some left behind changes that are preventing update?
lexluthor said:
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
I did this earlier, it shouldn't be difficult for you, assuming your admin isn't a jerk of course. It's a feature that needs to be checked on your account, but it's also a free feature, so I'm not sure what excuse they'd have for denying your request.
taihard said:
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Can't help you with your error code, but I can say that my rooted phone also reported as "modified" status before applying the OTA and it still does afterwards as well.
Please help
Phone is rooted and has oem rom ... and xposed framework for tweakbox philz recovery mode just keeps loading after i treid the update what can i do i cant get back into my phone at all please help
Also tried resotring a backup i made yesterday before any of this and its still doing the same thing please please please helpl
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
No. Xposed will block all OTA and removing system Apps will also.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
lexluthor said:
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
can one of you guys (or anyone else who took the update) use this code to pull the modem for us please?
(use terminal emulator)
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem-12B.img
Thanks!!
tech_head said:
No. Xposed will block all OTA and removing system Apps will also.
Click to expand...
Click to collapse
I had Xposed installed and it updated no problem. But I would think the system apps would make it fail though.
Didn't see this posted anywhere else, seems to have just popped on my phone via the T-Mobile OTA update service. I can't take the update because I have modified the system image heavily and I am using 'Firefds Kit' to trick the system into thinking I am still running an official untouched image.
Figured I would let everybody know this has just come down the pike, hopefully we can get some more info and maybe even something flashable as this gets pushed out to more phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This OTA update is a 90MB update (at least for my device, which is on G900TUVU1GPE1) and upgrades G900TUVU1GPE1 to G900TUVS1GPG2 and G900TTMB1GPE1 to G900TTMB1GPG2.
I also got this update this morning.
As a side note, I was going back and forth between my about device screen and the update screen trying to compare my version to what the update says and after clicking "update later" 3 times the next time I clicked I only had the option to "update now". I wasn't able to hit the back button, home button, or recent apps button at all so I just restarted my phone to avoid having to do the update. Is this normal for all software updates? Is it also normal for it to state that you cannot downgrade after installing due to new security policies? Can this affect rooting my phone in the future?
Fixed Stagefright vulnerabilities
This OTA update fixed all the Stagefright vulnerabilities reported by Zimperium for my T-Mobile Galaxy S5 phone.
Follonwing are the reported vulnerabilities before the update. After the update there were no vulnerabilities found.
Critical
CVE-2016-2863 - Remote Code Execution vulnerability in Mediaserver
High
CVE-2016-2476 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2477 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2478 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2479 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2480 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2481 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2482 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2483 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2484 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2485 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2486 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2487 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2895 - Remote Denial of Service vulnerability in Mediaserver
Moderate
CVE-2016-2499 - Information Disclosure vulnerability in Mediaserver
Just got the update am rooted stock rom exposed installed how do i update with root
Hi Everyone, could you tell me which languages are available in this update ?
Thanks.
R.Simoes88 said:
Hi Everyone, could you tell me which languages are available in this update ?
Thanks.
Click to expand...
Click to collapse
Same ones as always
When I first got the message, I hit Update Now, and... bootloops. Completed the update process and just endless bootloops; at first, they went to the T-Mobile screen, but then cut out the drama and bombed right at initial Galaxy S5 screen. What upset me is that I was running stock; I just disabled some bloat with BK Package Disabler, nothing more. 'course, as with tradition, a long battery pull solved the problem. Seems to be working fine, and the update also seems to have solved that toolbox bug.
ShinySide said:
Same ones as always
Click to expand...
Click to collapse
without Portuguese (pt-BR)?
Never mind! As per tradition, a long battery pull solved the issue.
I wanted to confirm that T-Mobile/Samsung have gotten super aggressive with this update. After a certain amount of time, you won't be able to put off the update (no choices available other than 'Install Now', takes over the screen so you can't do anything else, and it disables the hardware buttons until you tap 'Install Now'.
A workaround, if you need it, (other than rebooting immediately) is to pull down the notification shade and either tap something in your shade, or tap and hold WiFi/Location/Bluetooth, etc. Once you have exited the update dialog, everything should be working as normal.
OK, for someone on gpe1 with twrp/systemless root and systemless exposed, what's the best way to update without losing anything? Preferably not going back to stock recovery...
Nateg900t said:
OK, for someone on gpe1 with twrp/systemless root and systemless exposed, what's the best way to update without losing anything? Preferably not going back to stock recovery...
Click to expand...
Click to collapse
Don't think it's possible unless you have the modem and bootloader tars, and I haven't seen them on the forums. Otherwise, I generally make a full backup and do a full wipe and factory reset. Odin the release, your data may still be intact if you didn't do a factory reset/wipe, root apps won't be functional, recovery will be stock.
Odin TWRP, flash SU, flash Xposed, Backup again at this point as your base. Restore data from previous backup... cross fingers and hope all goes as planned If not you have the base install to start restoring via TB or Play store.
mgp53 said:
Don't think it's possible unless you have the modem and bootloader tars, and I haven't seen them on the forums. Otherwise, I generally make a full backup and do a full wipe and factory reset. Odin the release, your data may still be intact if you didn't do a factory reset/wipe, root apps won't be functional, recovery will be stock.
Odin TWRP, flash SU, flash Xposed, Backup again at this point as your base. Restore data from previous backup... cross fingers and hope all goes as planned If not you have the base install to start restoring via TB or Play store.
Click to expand...
Click to collapse
Here:
ShinySide said:
Everything except system.img, cache.img, boot.img and recovery.img. So full upgrade beside those 4 items.
https://www.androidfilehost.com/?fid=24665509702141030
Click to expand...
Click to collapse
ShinySide said:
Here:
Click to expand...
Click to collapse
Wish I'd seen your post earlier.
Thanks
Man, they've gotten super aggressive with this update and I'm rooted. XDA gang: Before I do something stupid like losing my root, should I take the update or try to get around this?
I'm new to firmware/rom flashing arena. I had received the first Marshmallow update and then I accidently hit the updates option a few weeks later, well the most current update is saying that if I update I wont be able to downgrade. That tells me the if I'm not mistaken the bootloader is being locked like how AT&T and Verizon do it. I specifically bought a SM-G900T (T-Mobile USA KLTE) S5 to prevent from having the boot loader locked. Has anyone verified the bootloader is now locked on this latest update- aka has tried downgrading to a previous version because if you can't downgrade I'm not going to update and rather have the ability to customize my phone.
I am currently back to KitKat 4.4.2.
eidairaman1 said:
I'm new to firmware/rom flashing arena. I had received the first Marshmallow update and then I accidently hit the updates option a few weeks later, well the most current update is saying that if I update I wont be able to downgrade. That tells me the if I'm not mistaken the bootloader is being locked like how AT&T and Verizon do it. I specifically bought a SM-G900T (T-Mobile USA KLTE) S5 to prevent from having the boot loader locked. Has anyone verified the bootloader is now locked on this latest update- aka has tried downgrading to a previous version because if you can't downgrade I'm not going to update and rather have the ability to customize my phone.
I am currently back to KitKat 4.4.2.
Click to expand...
Click to collapse
Incorrect. The not being able to downgrade and locked bootloader are 2 completely different things.
You can still do anything you want. Only thing you can't do is odin back to the pervious version. However That does not include being able to flash an earlier version via a recovery.
Still can flash recoveries, kernels, roms, mods, etc etc. You just can't downgrade via odin or downgrade bootloaders. Anything with you can.
ShinySide said:
Incorrect. The not being able to downgrade and locked bootloader are 2 completely different things.
You can still do anything you want. Only thing you can't do is odin back to the pervious version. However That does not include being able to flash an earlier version via a recovery.
Still can flash recoveries, kernels, roms, mods, etc etc. You just can't downgrade via odin or downgrade bootloaders. Anything with you can.
Click to expand...
Click to collapse
yeah my S4 was locked down so i couldnt do anything to put in newer versions of Android after 5.1.1 let alone downgrade or put in custom roms.
I went ahead and put in 6.0.1 GPE1 (not latest) back into the phone.
I'm running android 5.0 baseband G900TUVU1DOB1 on my g900t stock and roooted because i don't wanna update and lose root. The update to marshmallow does intrigue me though cuz i hear it's a little faster. My question is, If i wan't marshmallow, do i have to update my phone to all the updates between 5.0 and 6.0.1? And also once i get to 6.0.1, is there a way to root it? BTW i am using the G900TUVS1FOJ4 recovery despite having the DOB1 baseband because it was the closest to stock the stock OB1 recovery i could find. I should still be able to update OTA right? If it turns out that i can't root 6.0.1 then i'll prolly just stay on 5.0 with my root.
I used to be on one of the 4.4.2 stock rooted roms without a custom recover so I didn't lose warranty coverage with Knox.
When GPE1 with 6.0.1 came out, I did a full reset, odin'd GPE1, then twrp recovery (flipping the Knox warranty bit, but at this point on a 2+ year old phone who cares), then flashed systemless root and systemless xposed from twrp recovery, then titanium backup restored my backed up apps.
It wasn't too bad, but now I have to restart about once or twice a day when things get really laggy... Like there is a memory leak or runaway process or something... Which was probably Samsung's plan to make me buy a new phone, in which case I'll probably go the nexus/pixel route since I'm tired of waiting forever for and then fighting each update to try and keep the same root functionality...
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
update
heres the link for hte update zip
https://drive.google.com/open?id=0Bw35VbWkMyAhMzA0RUNYVC1sWDA
bangdosa said:
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
Click to expand...
Click to collapse
Most likely just a security update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well ill try to hold off, because last time i took an OTA update i was stuck for months with no root and wifi hotspot.
Still Android 5.0.1 Lollipop
I completed the update this morning. This is still Android 5.0.1 Lollipop.
edboyd59 said:
I completed the update this morning. This is still Android 5.0.1 Lollipop.
Click to expand...
Click to collapse
Any noticeable differences?
Did you loose root after update?
bangdosa said:
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
update
heres the link for hte update zip
https://drive.google.com/open?id=0Bw35VbWkMyAhMzA0RUNYVC1sWDA
Click to expand...
Click to collapse
bilgerryan said:
Most likely just a security update.
Click to expand...
Click to collapse
Is it just me? That's a new bootloader version isn't it? OF1 - PL1.
https://forum.xda-developers.com/verizon-galaxy-s5/general/update-pl1-potential-problem-t3528505
rooted device now bricked
I had rooted my device on OF1 using kingroot, and processed this update. I'm now bricked. It just hangs on the Samsung custom splash screen...
Any advice?
nic boles said:
I had rooted my device on OF1 using kingroot, and processed this update. I'm now bricked. It just hangs on the Samsung custom splash screen...
Any advice?
Click to expand...
Click to collapse
Flash stock with Odin. Follow my stickied thread in this Sub-Forum. If it updated your bootloader you might be hosed. Until the firmware is released.
Just so you know, you're supposed to unroot and then take the update
Ok, I'll try reflashing stock with odin.
I thought I did unroot it, using the kingroot instructions. I went into settings, told it to unroot, and restarted... then applied the update. Unless there was something else I was supposed to do?
nic boles said:
Ok, I'll try reflashing stock with odin.
I thought I did unroot it, using the kingroot instructions. I went into settings, told it to unroot, and restarted... then applied the update. Unless there was something else I was supposed to do?
Click to expand...
Click to collapse
Kingroot sets itself as a system app. Any alteration to the system partition and an OTA will Bork it.
Hey guys, I just got bricked by the OTA as well. 6 months or so ago I flashed the old kernel (OC1 I believe?) and then rooted with kingoroot or whatever. That was a mistake... all kinds of security notices and other weird sh*t that i didn't have time to deal with. So I used kingoroot to remove the root and flashed back OF1 or whatever was current. Still had the custom boot screen which was annoying but I thought I was back to normal... evidently that wasn't the case. Kind of salty right now because I probably just lost all of my data...I guess that's my lesson for getting a Samsung and attempting to make it usable. Currently I cannot get into safe or recovery mode: when i press the volume up and power it just takes me back to the "installing system update" and then "error!!". If anyone knows a way for me to get back in it would be greatly appreciated. If not, does anyone know which version firmware to install and where I could find it?
JoshTehSquash said:
Hey guys, I just got bricked by the OTA as well. 6 months or so ago I flashed the old kernel (OC1 I believe?) and then rooted with kingoroot or whatever. That was a mistake... all kinds of security notices and other weird sh*t that i didn't have time to deal with. So I used kingoroot to remove the root and flashed back OF1 or whatever was current. Still had the custom boot screen which was annoying but I thought I was back to normal... evidently that wasn't the case. Kind of salty right now because I probably just lost all of my data...I guess that's my lesson for getting a Samsung and attempting to make it usable. Currently I cannot get into safe or recovery mode: when i press the volume up and power it just takes me back to the "installing system update" and then "error!!". If anyone knows a way for me to get back in it would be greatly appreciated. If not, does anyone know which version firmware to install and where I could find it?
Click to expand...
Click to collapse
You need to hold volume down and power, then use Odin to reflash to OF1. That is what I just did.
sammobile(dot)com/firmwares/download/53590/I545VRUGOF1_I545VZWGOF1_VZW/
how to unroot?
I rooted using the wondershare method last year.
How do i un root so i can update it without bricking my device? Any help or links would be appreciated.
update: nic boles, that last post worked like a charm,,thanks!
I'll wait a while to try to root again.
foxfi seems to work and that's the most important thing to me.
Has anyone tried rooting on the new update?
bama9393 said:
Has anyone tried rooting on the new update?
Click to expand...
Click to collapse
Maybe I read it wrong, but I think the person that tried said they were bricked.
bilgerryan said:
Maybe I read it wrong, but I think the person that tried said they were bricked.
Click to expand...
Click to collapse
you have to unroot before the update
If you were rooted and made even the slightest change to /system, the update will hose you.
If you want the update, best to Odin back to OF1 stock first, then OTA.
bg260 said:
If you were rooted and made even the slightest change to /system, the update will hose you.
If you want the update, best to Odin back to OF1 stock first, then OTA.
Click to expand...
Click to collapse
Now can i root after the update with wonershare or kingroot?
edwardnizz said:
Now can i root after the update with wonershare or kingroot?
Click to expand...
Click to collapse
I wouldn't try it.
I mirrored the firmware here btw. Like 6 months ago.