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.
Related
Just checked for update under settings and there was an update, but when the phone restarts and tries to install the update, it fails. Anyone else?
"Software Update: Install Interrupted - The software update could not be installed at this time."
Are you on a completely stock phone?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
^yup, complete stock phone.
I checked for updates and there was one, downloaded, update failed.
Just bought my I777 from ATT and powered it up. Completely stock and experienced the same failure.
Same here. Completely stock. Tried my Girlfriends SGS2.....same deal.
Guess I wasn't the only one with the failure.. lol.. wonder what's the update about..
Mine failed also, completely stock as well. Out of curiosity what is this update include?
OTA updates probably aren't a good thing for you to try and do. They have been known to brick the og gs line. If there is an update you should try over Samsung Kies
Sent from my SAMSUNG-SGH-I777 using Tapatalk
CB650 Wolf said:
OTA updates probably aren't a good thing for you to try and do. They have been known to brick the og gs line. If there is an update you should try over Samsung Kies
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
I just tried Kies. No update there.
Same thing here, just tried on my wifes phone and after restart says update failed.
Just talked to AT&T. The rep said there wasn't an update for the I-777 only for the Skyrocket.
Samsung also says there is no update.
Same old stuff........AT&T says talk to Samsung......Samsung says talk to AT&T.Should have know that's how it would go.
lol, so AT&T pushed the update to the wrong devices or something?
I think what happened was that the update application glitched out. Or maybe they're testing the machines for a bigger update. Maybe KK6 or whatever just came out.
It seems like everyone at at&t has left the original GS2 And just focused on the skyrocket.. (Noting that at&t announced the skyrocket would be updated to ICS but have yet to say anything on the original gs2..)
- At&t Galaxy S II Running
***ICScrewD V1.3***
Unless, my searches and searches have just missed over something completely hahah. Inform me if I'm wrong!
- At&t Galaxy S II Running
***ICScrewD V1.3***
It's just AT&T trying to secretly install CIQ on the 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"
}
^Possibly xD
I ran into this problem too, but after 3 attempts (2 fails and 1 success) to install the update, I got it to work!
First of all, this update is NOT the SkyRocket's... after all, we are on the Orignal SGS2, and the SkyRocket and OSGS2 have COMPLETELY different model numbers.
Second of all, the update brings the phone to 2.3.6 and firmware I777UCKK6. If I am correct, 2.3.6 is also supposed to have better battery life
So, to get the update to work, here is what I did:
*NOTE* I too was 100% stock, but rooted and removed some of the bloatware on the phone. It seems that this may have caused the update failure.
1) Flash one of the kernels found on Entropy512's post on how to return to stock. It seems that whether you choose the rooted or non-rooted one does not matter (EX: I was already rooted and installed the non-rooted Kernel, but remained rooted afterwards). This will return all bloatware to the phone.
2) Wait 24Hrs OR change the date forward a day
3) look for an update again and install
4) Enjoy the update!
5) If rooted, then you will need to root again
6) Once rooted, you can remove the bloatware again. I recommend copying it to a separate folder so that future OTA updates can be done by simply copying the apk files back to system/apps.
I hope this works for everyone else too
spexwood said:
I ran into this problem too, but after 3 attempts (2 fails and 1 success) to install the update, I got it to work!
First of all, this update is NOT the SkyRocket's... after all, we are on the Orignal SGS2, and the SkyRocket and OSGS2 have COMPLETELY different model numbers.
Second of all, the update brings the phone to 2.3.6 and firmware I777UCKK6. If I am correct, 2.3.6 is also supposed to have better battery life
So, to get the update to work, here is what I did:
*NOTE* I too was 100% stock, but rooted and removed some of the bloatware on the phone. It seems that this may have caused the update failure.
1) Flash one of the kernels found on Entropy512's post on how to return to stock. It seems that whether you choose the rooted or non-rooted one does not matter (EX: I was already rooted and installed the non-rooted Kernel, but remained rooted afterwards). This will return all bloatware to the phone.
2) Wait 24Hrs OR change the date forward a day
3) look for an update again and install
4) Enjoy the update!
5) If rooted, then you will need to root again
6) Once rooted, you can remove the bloatware again. I recommend copying it to a separate folder so that future OTA updates can be done by simply copying the apk files back to system/apps.
I hope this works for everyone else too
Click to expand...
Click to collapse
Or just flash UnNamed 2.0
Well, yeah, but some prefer to stay on official stock firmwares... like myself lol.
I've been trying to download the JB Update and am unable to do so due to the authentication error.
My history:
I've run Nexus Conversion and switched back
I'm on 11c rooted and relocked.
Error still happens
Please, if you're getting the error too, lets see if there's a common denominator around it.
Post your circumstances.
Thanks
Unlocked on T-Mobile network.
Unlocked and rooted with freegee 10o.
LGNPST back to stock 10o to update to JB. Unrooted locked bootloader. Failed auth.
LGNPST to 11c. Unrooted locked bootloader. Failed auth.
East coast location issue perhaps? Anybody on the EC update to JB yet?
Unlocked on AT&T network.
Unlocked and rooted with freegee 10o.
LGNPST back to stock 10o to update to JB. Assumed this automatically re-rooted and re-locked. Failed auth.
LGNPST to 11c. Failed auth.
Im in San Antonio, TX
i've also done the n4 conversion and came back. but i LGNPST'ed the 11c and was able to get the update. does you camera work for you in the 10o version or the 11c version? for me it did from lgnpst but it wouldnt in snowjb version so i did the camera fix found here http://forum.xda-developers.com/showthread.php?t=2146816 and that allowed me to see camera on snowjb rom. then att official 20j just came out so i lgnpst'ed back to the 11c version and got the update right away.
---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------
kevbach said:
Unlocked on AT&T network.
Unlocked and rooted with freegee 10o.
LGNPST back to stock 10o to update to JB. Assumed this automatically re-rooted and re-locked. Failed auth.
LGNPST to 11c. Failed auth.
Im in San Antonio, TX
Click to expand...
Click to collapse
cant be rooted or unlocked and have to be on 11c version. have to lgnpst back to the 11c version found in this thread. http://forum.xda-developers.com/showthread.php?t=2219953 then you will be able to get the update.
gunnyman said:
I've been trying to download the JB Update and am unable to do so due to the authentication error.
My history:
I've run Nexus Conversion and switched back
I'm on 11c rooted and relocked.
Error still happens
Please, if you're getting the error too, lets see if there's a common denominator around it.
Post your circumstances.
Thanks
Click to expand...
Click to collapse
Can someone post a screenshot of the authentication error?
Bortzer said:
Unlocked on T-Mobile network.
Unlocked and rooted with freegee 10o.
LGNPST back to stock 10o to update to JB. Unrooted locked bootloader. Failed auth.
LGNPST to 11c. Unrooted locked bootloader. Failed auth.
East coast location issue perhaps? Anybody on the EC update to JB yet?
Click to expand...
Click to collapse
i live in michigan and have the 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"
}
install error - 0x13e
i'm getting an installation error message 0x13e.. i bought the phone second hand, so i'm not quite sure what it's status is.. i've checked to see if it's rooted, but it's not.. not sure if it's unlocked or not.. the phone seems to be basic stock.. i've even did a factory reset few times, but i'm still getting the install error.. i'm on software version E97011c and i'm on ATT..
any help would be great..
youngkuw said:
i'm getting an installation error message 0x13e.. i bought the phone second hand, so i'm not quite sure what it's status is.. i've checked to see if it's rooted, but it's not.. not sure if it's unlocked or not.. the phone seems to be basic stock.. i've even did a factory reset few times, but i'm still getting the install error.. i'm on software version E97011c and i'm on ATT..
any help would be great..
Click to expand...
Click to collapse
i'd recommend lgnpst to 11c since you got it second hand, just to be sure.
freebee269 said:
i'd recommend lgnpst to 11c since you got it second hand, just to be sure.
Click to expand...
Click to collapse
I was getting the same error on 11c when I restored my back up. I had to use lgnpst
Sent from my LG-E970 using Tapatalk 2
---------- Post added at 08:19 PM ---------- Previous post was at 08:17 PM ----------
Bortzer said:
Unlocked on T-Mobile network.
Unlocked and rooted with freegee 10o.
LGNPST back to stock 10o to update to JB. Unrooted locked bootloader. Failed auth.
LGNPST to 11c. Unrooted locked bootloader. Failed auth.
East coast location issue perhaps? Anybody on the EC update to JB yet?
Click to expand...
Click to collapse
I'm in Massachusetts so it's not a east coast thing. I've dled the update atheist 10 times by now
Sent from my LG-E970 using Tapatalk 2
gunnyman said:
View attachment 1858075
Click to expand...
Click to collapse
I'm getting the same error:crying:
I used LGNPST and installed version 11c...
Are you guys with the authentication errors using smart limits? I used to use it for blocking spam calls, but it broke wifi tethering, bringing a very similar failed authentication message
Sent via LG E970 SlickROM v6
I'm not.
I'm starting to wonder if using the N4 conversion may be the culprit.
I never used the n4 conversion and I still have this issue
Sent from my LG-E970 using Tapatalk 2
youngkuw said:
i'm getting an installation error message 0x13e.. i bought the phone second hand, so i'm not quite sure what it's status is.. i've checked to see if it's rooted, but it's not.. not sure if it's unlocked or not.. the phone seems to be basic stock.. i've even did a factory reset few times, but i'm still getting the install error.. i'm on software version E97011c and i'm on ATT..
any help would be great..
Click to expand...
Click to collapse
same thing, on 11c, rooted and boot unlocked.
I did the N4 conversion and I'm fine
Before you lngpst back to 11c, try fastboot -w. Thata what I do everytime before I do lgnpst
Sent from my LG-E970 using xda premium
I've said screw it and installed snowJB's stock rooted version.
Well, I was perusing the interwebs and have been following this thread on ATT support website. Check out the last post: http://forums.att.com/t5/Android-Di...Bean-update-for-Optimus-G/td-p/3378427/page/5
Guy was dealing with the same authentication error we have been, borrowed an ATT sim card from a friend, and got it to work. Anybody have any friends with a sim card they can borrow
Only info I have found at all regarding any sort of resolution.
Well i went around every corner and through every hoop possible with 2 ATT reps and 3 LG reps, the only thing i ever did to my phone was root it, i completely reverted to stock and factory reset but was still getting the ox13e error. Finally ATT said they are shipping me a refurb, which i'm not ecstatic about but what the hell other option is there? I ran Snowjb on my first OG but the stability just wasn't a daily driver for me. Soooo, if you guys get it figured out in the next 2 days, let me know, if not, looks like i'm getting a refurb! Any fix would be welcome at this point now! hell, i even tried the sim card thing but that failed too ahh well.
You guys are really taking refurbs over flashing the stock JB rom Snow posted?? Wow.... :what:
Sent from my LG-E970 using xda app-developers app
I've looked around and seen that Kingroot PC is the way to go to root my VRUGOC1 galaxy s4.
However every time I plug my phone in to Kingroot I get a screen with a phone and a few sentences in Chinese on it.
The PC app doesn't even start trying to root, it just skips straight to that screen. I think that it's getting me to use the mobile app version given the phone picture, but if that's the case then I've found myself in a dilemma since the app tells me to use the Desktop version every time too.
How do I get the PC Kingroot to actually start rooting? Or can someone translate this for me?
I tried for a long time to get either of the Kingroot programs to work but both the PC and app failed. I quit trying a month or so back but tried again last night. It did the same thing you're talking about, it installed the app even though I was using the PC. It seemed like it could no longer use the PC version, only the app version so I don't know what's going on.
Do you reckon theres something different about our phones? Also did you ever try reflashing oc1?
I'm not sure if there's a difference. The one I currently have is a refurb, my last one the volume button was stuck in the up position. I have flashed OC1 several times but that didn't work either.
Same thing happening to me. It really sucks. I rooted fine less than a month ago and then in soft bricked and odined the "revert to oc1" from muniz's post. Now I can't root no matter what I try.
Sent from my SCH-I545 using Tapatalk
araucaria said:
I've looked around and seen that Kingroot PC is the way to go to root my VRUGOC1 galaxy s4.
However every time I plug my phone in to Kingroot I get a screen with a phone and a few sentences in Chinese on it.
The PC app doesn't even start trying to root, it just skips straight to that screen. I think that it's getting me to use the mobile app version given the phone picture, but if that's the case then I've found myself in a dilemma since the app tells me to use the Desktop version every time too.
How do I get the PC Kingroot to actually start rooting? Or can someone translate this for me?
Click to expand...
Click to collapse
Have you tried enabling USB Debugging under Developer Options?
I just rooted my S4 yesterday using Kingroot. I did clean flash OC1 through Odin and then did a Factory Data Reset through Recovery before rooting.
haza12d said:
Have you tried enabling USB Debugging under Developer Options?
I just rooted my S4 yesterday using Kingroot. I did clean flash OC1 through Odin and then did a Factory Data Reset through Recovery before rooting.
Click to expand...
Click to collapse
Kingroot would not have let me click the root button if I didn't enable it. I guess I forgot to mention that I clicked the button, haha. I will try re-flashing this weekend. Maybe the OTA I took messed something up?
Also, could I get the OC1 tar and the version of Odin that you used?
Does not work for me
Trying to use desktop version of KingRoot. Did clean flash of OC1 with odin, did factory reset after that then enable usb debugging. This is what I get.
{
"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"
}
Apk version does not work either. Please help me...I need root back.
beavis5706 said:
Trying to use desktop version of KingRoot. Did clean flash of OC1 with odin, did factory reset after that then enable usb debugging. This is what I get
Apk version does not work either. Please help me...I need root back.
Click to expand...
Click to collapse
hey beavis, I got the exact same thing as you did. and when I clicked the blue button it just launched kingroot on my phone, which doesnt work either. I read on another thread that kingroot suddenly stopped supporting the vzw sgs4 on oc1 for some reason. unfortunately I've given up, heh. I hate to say it but I believe root for our outdated phones on 5.0.1 is a lost cause. sorry.
Hey everyone, for those of you who downgraded back to OC1 from OF1 and lost root as well as the ability to root again via KINGROOT, I found a way to re-root.
I used WonderShare MobileGo one click root and I now have superuser again.
http://www.wondershare.com/mobile-phone/how-to-root-android.html
If you could figure out king root in all Chinese you should have no problem figuring this out.
I should mention this is a Windows application that you need to install. Connect your phone via USB with debugging enabled. The rest should be self explanatory.
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...
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