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
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
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.
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
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.
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