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...
Related
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.
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.
Hey guys,
I have my tablet since one week. I love it, all works fine, Xposed offers me OBB move and so on. But now I have a question:
How can I get the new Updates for my Tablet with ROOT/TWRP?I know OTA can't be updated due to TWRP, but is there any way to flash updates dirty?! (like with LineageOS, OxygenOS, ... )
At the moment, if I try to search for new updates, I get following message:
The operating system on your device hase been modified in an unauthorised way. Try downloading softwar updates using Smart Switch on PC or visit a customer service centre.
Maybe someone got an early version of the Tab S3 with early factory Android and can give some enlightenment.
Greetz,
CM
First, this should be posted in the q&a section. You're going to have to flash the upgrade firmware tar in odin. Then re-set up your device and re-root. It's a pita. Google has gotten better at saving your apps and data, which helps, or use something like titanium backup
isn't it enough flashing stock recovery and uninstall supersu via app?
I've been away from Samsung devices for awhile, I've been using Nexus but just got a tab3. I haven't tried this but it's possible that you could flash the update.zip that would be pushed to your device using flashfire. You would probably also be able to retain root and TWRP. Maybe someone with more recent samsung use could confirm that. However, based on the message you're getting the update looks like it won't be pushed to your device. And afik samsung doesn't publish the ota, only the full firmware so someone here would have to capture the ota and post it. Whenever samsung gets around to providing an update we can play around with it and see.
PS, do you have a flashable copy of the stock recovery?
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
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
drickles said:
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
Click to expand...
Click to collapse
Personally I would not do the OTA as it may not update properly (if even at all). Every phone I have rooted before this was one of the cautions usually posted... I would double check in what ever tutorial, thread, utility faq you used to make sure.
I would suggest you wait for an update to be made that is flashable with your custom recovery. If your custom recovery has the feature (like TWRP) make a backup of what you have installed, flash the update and if things don't work you can restore your backup.
I miss having that kind of backup/restore ability via custom recovery on my phone.. sure comes in handy when things go sideways
Nothing happens. According to my experience and contents in the OTA zip, twrp will simply just spit it out. No dm-verity re-lock or bricking too.
You can always download one of the custom systems which are regularly updated.
Example would be Soldier ROM.
I recommend find your new firmware and flash it. You will lose all of your file and root-recovery you can have them all back