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.
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
Hi,
I can't seem to get the new update via OTA but KiES shows that I have an update. is that normal. mine is running Xxalf2 (BTU).
I had just updated but kies cannot backup my phone anymore. It brings up an error message
sent with WSGS3
I have unlocked and unbranded S3, checked on on phone no updates available, kies tells me that update available
Here is message:
Current firmware version: PDA:LF2/PHONE:LF2/CSC:LF2 (BTU)
Latest firmware version: PDA:LFB/PHONE:LFB/CSC:LFB (BTU)
Shall I go ahead and update or hold for while?
bakili said:
I have unlocked and unbranded S3, checked on on phone no updates available, kies tells me that update available
Here is message:
Current firmware version: PDA:LF2/PHONE:LF2/CSC:LF2 (BTU)
Latest firmware version: PDA:LFB/PHONE:LFB/CSC:LFB (BTU)
Shall I go ahead and update or hold for while?
Click to expand...
Click to collapse
I just updated through KIES cause I couldn't wait. I am on BTU too. Maybe OTA updates for that firmware will come in a while.
I upgraded as well but I hate the fact that I cannot backup my phone anymore. Although I connect to kies, when it comes to backing up Colin get an error message while kies is trying to read through my phone to start the process.
sent with WSGS3
vasp3690 said:
I upgraded as well but I hate the fact that I cannot backup my phone anymore. Although I connect to kies, when it comes to backing up Colin get an error message while kies is trying to read through my phone to start the process.
sent with WSGS3
Click to expand...
Click to collapse
It's weird. Never got that issue. Did you try updating KIES to the latest version. Even KIES got a new update.
No idea how do you get that, for me no change at all. using international version of S3
{
"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"
}
circuit89 said:
Hi,
I can't seem to get the new update via OTA but KiES shows that I have an update. is that normal. mine is running Xxalf2 (BTU).
Click to expand...
Click to collapse
I was in exactly the same situation.
I think it is because they roll out the OTA updates progressively (probably by serial number groups) to avoid server overloads. You would probably get it in the next few days.
I updated mine via KIES, no problems at all. (Actually, I loaded a new update to KIES itself first, then updated the phone)
Will updating through kies erase all data?
bakili said:
Will updating through kies erase all data?
Click to expand...
Click to collapse
No it won't.
I've just gone through the whole update process with kies all completed both on the pc and on the phone, it rebooted but there was no sign of the update the firmware on the phone is still the old one and now kies says it's upto date.......... Weird.
Sent from my GT-I9300 using xda app-developers app
Sweet :good:
Just updated.
Does anyone know, what improvements we will get with this update?
bakili said:
Sweet :good:
Just updated.
Does anyone know, what improvements we will get with this update?
Click to expand...
Click to collapse
I think the battery life is better. It's discharging slower than usual for me. And a few improvements here and there. The biggest seems to be the brightness slider in notification center.
Support please!!
Samsung support is terrible, would it hurt them to post a change log? I had the OTA update available, but chose to leave it an hour until I read what was in the update. When I couldn't find anything I tried OTA again but it wasn't available - updated through Kies in the end.
Nocombneeded said:
Samsung support is terrible, would it hurt them to post a change log? I had the OTA update available, but chose to leave it an hour until I read what was in the update. When I couldn't find anything I tried OTA again but it wasn't available - updated through Kies in the end.
Click to expand...
Click to collapse
Lol. Atleast they try to provide a better user experience. Some manufacturers don't even provide updates after you have purchased the phone.
Is this resolve the cell stanby issue?
Sent from my GT-I9300 using Tapatalk
Nope, they have not fixed that bug yet. It's really not draining that much battery, just the values that are showing up is wrong. It should display the proper reading eventually.
Why is it that I do not get an OTA update ever. Kies takes ages.
Last time around, there was no OTA update for me. Same this time. I hate kies.
circuit89 said:
It's weird. Never got that issue. Did you try updating KIES to the latest version. Even KIES got a new update.
Click to expand...
Click to collapse
Yes. Both kies and phone now have been updated.
sent with WSGS3
circuit89 said:
I think the battery life is better. It's discharging slower than usual for me. And a few improvements here and there. The biggest seems to be the brightness slider in notification center.
Click to expand...
Click to collapse
Yes. Seems like the 100%is staying up more now
sent with WSGS3
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.
I had received a refurbished phone from Verizon after I had to send my old phone. My phone was still under warranty so instead of taking the time to fix it I exchanged it. When I powered it on it was running on 24b with no problems. I was informed that there were OTA updates so I began to update it as usual. After I downloaded one of the updates and began installing the update, I saw something off. The installer looked completely different from my old phone (including others that I know that have the phone) and looked like it was custom. (I posted some pictures for some visual aid.) After the update completed, I checked the android version and it updated correctly using the OTA update. Looking through the settings, I found out that it is apparently modified before I even got the chance to root or make any Rom changes. Does anyone know anything about this particular installer? Also, should I even attempt to root the phone not knowing what to expect from it? I don't want it to get bricked after just receiving the phone. Thank you .
{
"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"
}
That looks like the normal OTA installation screen to me. I don't recall if it was always that way through all the OTAs on the VS985, but it's been like that at least since 23A/B/C. I think it's always been basically like that though.
I did a lot of experimenting recently with flashing the 35B KDZ and taking the two following OTAs to get to 47A, that's why it's fresh in my mind.
As far as "Modified" status. There can be very minor things which manage to tweak the Official status into Modified. Even though I had recently flashed the 35B KDZ several times, I found that my status remained "Modified" both before and after taking the following OTAs. It was only after I restored to 10B via the TOT method (and 35B .DLL) and then re-flashed the 35B KDZ that my status remained "Official". The reason I had done so was actually because I was experiencing some very weird problems that flashing KDZs didn't solve, and it turns out flashing the 10B TOT solved all the issues. @xdabbeb explained and I've since noticed myself, that TOTs flash more partitions than KDZs, so they're really superior as a method to putting your phone back to a known good state.
Obviously we pay more attention to the details than Verizon does.
So I recommend you do the same that so you know for certain there's nothing wonky left behind, although I wouldn't overly worry about it either.
I happen to not have re-rooted since 47A came out just because I've been busy.
Edit: By the way, I had also run several experiments with using the Kingroot app to root 35B, 46A and 47A so it's very possible Kingroot was the cause of whatever corruption had occurred with my software that required flashing the TOT to solve.
roirraW "edor" ehT said:
That looks like the normal OTA installation screen to me. I don't recall if it was always that way through all the OTAs on the VS985, but it's been like that at least since 23A/B/C. I think it's always been basically like that though.
I did a lot of experimenting recently with flashing the 35B KDZ and taking the two following OTAs to get to 47A, that's why it's fresh in my mind.
As far as "Modified" status. There can be very minor things which manage to tweak the Official status into Modified. Even though I had recently flashed the 35B KDZ several times, I found that my status remained "Modified" both before and after taking the following OTAs. It was only after I restored to 10B via the TOT method (and 35B .DLL) and then re-flashed the 35B KDZ that my status remained "Official". The reason I had done so was actually because I was experiencing some very weird problems that flashing KDZs didn't solve, and it turns out flashing the 10B TOT solved all the issues. @xdabbeb explained and I've since noticed myself, that TOTs flash more partitions than KDZs, so they're really superior as a method to putting your phone back to a known good state.
Obviously we pay more attention to the details than Verizon does.
So I recommend you do the same that so you know for certain there's nothing wonky left behind, although I wouldn't overly worry about it either.
I happen to not have re-rooted since 47A came out just because I've been busy.
Edit: By the way, I had also run several experiments with using the Kingroot app to root 35B, 46A and 47A so it's very possible Kingroot was the cause of whatever corruption had occurred with my software that required flashing the TOT to solve.
Click to expand...
Click to collapse
I panicked when I saw the way it installed the update plus the modified status. My previous phone had more of a basic installation, I remember it would just be black with the Android logo in the middle. I even compared it with my father's phone and it was different from the refurbished one I just received. I'll look into doing a ToT flash when I can. Thank you for the quick response!
Supernic100 said:
I panicked when I saw the way it installed the update plus the modified status. My previous phone had more of a basic installation, I remember it would just be black with the Android logo in the middle. I even compared it with my father's phone and it was different from the refurbished one I just received. I'll look into doing a ToT flash when I can. Thank you for the quick response!
Click to expand...
Click to collapse
You're welcome! Good luck.
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.