Per this poster over on S4GRU.com, the new version is 77.8.10.XT897.Sprint.en.US:
http://s4gru.com/index.php?/topic/2507-photon-q-software-update/
Yeah, I had seen someone on the Sprint forums say he got the update last night. He said IM didn't work aterwards, but I wasn't sure if he meant Gtalk, or what.
I am rooted and debloated as well, but from my experience, that shouldn't prevent the device from saying an update is available.... but the update could fail if we try and apply it like this... I always go back to stock unrooted if I wanna install an update.
I think at least one thing they were supposed to address was that VSNCP registratiom error that pops up sometimes, I've seen it pretty much every day, and I've even done the fix of editing my data profile username.
Sent from my XT897 using Xparent ICS Tapatalk 2
Actually, I will be interested to see whether we do receive the update with bootloader unlocked and rooted. I did see Moto say in the FAQs that they are under no obligation to offer updates to unlocked devices. However, that is probably just something they say, and they did also mention the bit about accepting the OTA when rooted/modded causing problems.
Sent from my XT897 using Xparent ICS Tapatalk 2
yogi2010 said:
Actually, I will be interested to see whether we do receive the update with bootloader unlocked and rooted. I did see Moto say in the FAQs that they are under no obligation to offer updates to unlocked devices. However, that is probably just something they say, and they did also mention the bit about accepting the OTA when rooted/modded causing problems.
Sent from my XT897 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
any idea is it JB or stil ICS?
Pretty sure its still ICS, I'm sure the guy would have said if it were JB, plus something that significant would have hit the various sites beforehand most likely.
yeah, if it were JB we most probably would have heard about it beforehand. i haven't seen many people with the update yet, today i keep getting 'check for update not available at this time'.
Probably to fix the vsncp error message problem.
i just got off a chat with Sprint, and they said there is no such update currently
unless maybe it was released, then pulled due to bugs?
I woke up to a notification of the update. Size was about 50mb. I pressed 'later' to cancel it, even though it'll fail if I take it since I'm unlocked.
Sent from my XT897 using Tapatalk 2
yogi2010 said:
i just got off a chat with Sprint, and they said there is no such update currently
unless maybe it was released, then pulled due to bugs?
Click to expand...
Click to collapse
The tech was an idiot, I just got the popup notification and was able to click on the link for the release notes.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/90757
Yeah, I just got the update notice myself. Thanks!
Gonna install and check it out. Can always revert if it's no good.
Sent from my XT897 using Xparent ICS Tapatalk 2
---------- Post added at 08:11 AM ---------- Previous post was at 08:03 AM ----------
dpwhitty11 said:
I woke up to a notification of the update. Size was about 50mb. I pressed 'later' to cancel it, even though it'll fail if I take it since I'm unlocked.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
I'm gonna try restoring the bone-stock backup file, reflashing stock recovery, and then installing the update. From past experience, unlocked bootloader has been ok, it just won't work if your system is rooted/modded.
Sent from my XT897 using Xparent ICS Tapatalk 2
I got the OTA message this morning.
Coming from the shift forum we have learned to never to install OTA updates. However this one looks harmless.
Who knows.. maybe my LTE will start actually working?
Sent from my XT897 using xda app-developers app
anyone do the update with a rooted phone>?
Got the update pushed down around 10:30 am est today.
From the release notes:
Multimedia Texting - Improved MMS texting functionality when the Data Username/NAI has changed to a shorter length
Click to expand...
Click to collapse
This is most likely the data profile extra ".com" fix. I like their wording.
Hey a quick question to everyone. Never really had to deal with Sprint for my epic since XDA had everything I needed but I have gotten very concerned with the information around this and the "VSNCP" stuff. Are the tech's normally this clueless? Is there a quick way to talk to someone that actually knows what they are talking about? They told me I had to get a new phone the other day due to these issues. How could they tell me that if a software update to fix it is going to be release a week later?
ericcire said:
anyone do the update with a rooted phone>?
Click to expand...
Click to collapse
I am rooted and unlocked and the upgrade went through fine. Now I am not rooted anymore, but that shouldnt be hard to fix.
swintec said:
I am rooted and unlocked and the upgrade went through fine. Now I am not rooted anymore, but that shouldnt be hard to fix.
Click to expand...
Click to collapse
I am also rooted (and unlocked, of course you have to be unlocked to be rooted ), but my phone went through a different scenario.
I downloaded the update (was 56MB I believe, somewhere around there. The update is 77.8.10.en.US). Downloaded it via Wi-Fi, then the phone asked if I wanted to install. I pressed Install Now, and it rebooted.
My phone rebooted and went into recovery. I dont remember everything, but it asked if I wanted to install "Unknown.zip", and it had:
No
No
No
No
Yes - Install Unknown.zip
No
No
No
Etc... I clicked No, then it went to the recovery menu (where you have the option to restart the phone, and the other options.. sorry, I've only ever rooted my evo shift so my termoinology is limited). I rebooted the phone via the first option, the phone went through its process, came back up fully, and rebooted by itself! Everything happened again (asking to install the unknown.zip, etc..). Basically, it was in an endless look when I would restart the phone.
First thing I tried was to wipe the Delvik Cache. Did that, rebooted, phone came back up and rebooted by itself again.
Second thing I tried (and I had a feeling I would probably regret this cause it would either brick my phone or unroot it), was to install that Unknown.zip. But that didnt even go through. The install failed (A message appeared at the bottom of the phone along with the other message logs, so I really dont remember exactly what it said. It was just an error message basically).
At this point I didnt know what to do... so I got to the recovery menu (where it said Reboot phone, Advanced, and the other options), and I selected the one that said to Wipe Cache. Not the Delvik cache but the phone cache (I dont think the option said Wipe Cache, but something similar?). Did that, rebooted, and my phone stayed on! The update popped up again, and this time I pressed "Later". Learned my lesson.
I guess the update may be hit or miss for rooted users?
ericcire said:
anyone do the update with a rooted phone>?
Click to expand...
Click to collapse
Yes, clockwork recovery booted up and the update failed.. probably going to flash the stock image..
But my phone says I'm up to date?
Kenneth196 said:
I guess the update may be hit or miss for rooted users?
Click to expand...
Click to collapse
Possibly..I dunno. I used the 2nd method posted only a few weeks ago and a few clicks of the mouse to root...not the first method initially posted when the phone first came out. When I clicked update now it simply rebooted and the android guy came up and did its thing...about 5 minutes later everything was back to normal.
I wiped my phone completely and am not getting a notification about the OTA now.
I'm flashing TWRP and hoping I get notified again.
Is there a way to flash the stock recovery?
I installed this update, all I can confirm is that it's still Android version 4.0.4. Otherwise I've really not noticed anything different or new yet, but I haven't had much of a chance to use it.
Related
I'm noticing in other threads than OTA update has been pushed, but again - WTH? I noticed this morning my Thunderbolt was downloading the update. I hopped on the internet to check this site about what this update would contain. While logging on, I heard my Thunderbold do the short vibrate reboot sound - I looked over and it apparently had not only downloaded the update, but flashed it as well - completely wiping my settings/data in the process!
I had been holding off rooting for lack of time, but now there is no reason to wait. And I can't believe, if I'm not the only one this has happened to, that there won't be a lot of PISSED Thunderbolt owners out there...
This is common practice for OTAs to update automatically. That's why they PUSH the updates.
Sent from my ADR6400L using XDA Premium App
I rejected it error code 401 hopefully it will not update.
If I have to pull battery then I think I'm screwed holding off till bugs surface and they send out patches
Sent from my ADR6400L using xda premium
I found mine updated this morning. But no settings or anything wiped, just the new gingerbread software, new verizon included software (or updated).
Have stock TB. Found OTA new update and downloaded it. Most of my settings were still there. Had old GB update and did a factory reset 2x trying to fix issues. New OTA fixed issues I was having.
Sent from my ADR6400L using xda premium
ibsk8 said:
This is common practice for OTAs to update automatically. That's why they PUSH the updates.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I get that, but wiping the device should require the owner's approval.
An update on this: apparently, it has only wiped the device, as now it wants to do the update. Curious (and maddening) that it's asking permission to do the update but wiped the device without warning. Maybe the wiping is a prep step for the update? Still doesn't justify it.
I could even give Verizon and/or HTC the benefit of the doubt and say that wiping was some sort of bug, but it still should never have happened. I'm in the mood to root it now, so hopefully it will be a moot point...
Mine trys to update, but I just get the "!" with the small blue-android.
I just reboot it, and it says "update failed" and I go on my merry way.
Supposedly someone got the update (the only person to report getting it) and it bricked their phone lol. You make the call if you think this is true or not.
" At about 4:18pm I noticed my phone's icons had changed in the notification bar and it tells me it has an update. I check and it turns out today is the day for Gingerbread. Well the instructions say it'll take 17-18 minutes to install, so I let it go ahead and do the install.
Just 17-18 minutes later it finished installing and rebooted, without me doing a single thing to the phone during the whole process. After a couple of minutes at the loading screen with the red thing in the middle, it rebooted. Then still sat there...and it has been on an endless cycle of this rebooting every like 5 or 10 minutes and doing NOTHING.
I tried holding the power button and it just reset it and did the same thing still, tried the power + home button reset and no change, and even took the battery out of the phone.
Looks like I gingerbricked my STOCK ANDROID charge!!!!! Thanks a lot verizon! Sitting in your store tonight while you fix this is just what I wanted to do. "
Original Post:
http://androidforums.com/samsung-dr...read-ota-update-bricked-my-stock-android.html
Haha for some reason I can foresee that happening. It almost makes me want to go back to stock and wait for the update.
Sent from my SCH-I510 using XDA App
Lockett said:
Haha for some reason I can foresee that happening. It almost makes me want to go back to stock and wait for the update.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
I honestly don't believe him one bit. I've been on stock ee4 for a while and still haven't got the update. This guy is the only person out of all these different forums sites to report getting the update.
i am calling shenanigans... nobody has received the OTA... plus this is too convenient!
lol... nice try guy.
spc_hicks09 said:
I honestly don't believe him one bit. I've been on stock ee4 for a while and still haven't got the update. This guy is the only person out of all these different forums sites to report getting the update.
Click to expand...
Click to collapse
Search droid charge on twitter. There are a few people reporting that they received the OTA. I don't know how truthful they are being, I personally will believe it when it his my device!
Sent from my SCH-I510 using XDA App
I am rooted with a stock ROM but my kernal (2.6.32.9 [email protected] #1) isn't stock. Will I get the OTA update or will the kernal keeping that from hitting my phone? I am also using Titanium Backup to freeze most of the bloatware.
Thanks
The kernel will prevent the OTA from being installed. It checks everything before it installs it as part of the install script for the OTA update.
See this thread...
http://forum.xda-developers.com/showthread.php?t=1365376
Danalo put together a ROM package that can be ODINed to the phone.
Triple Black said:
I am rooted with a stock ROM but my kernal (2.6.32.9 [email protected] #1) isn't stock. Will I get the OTA update or will the kernal keeping that from hitting my phone? I am also using Titanium Backup to freeze most of the bloatware.
Thanks
Click to expand...
Click to collapse
Freezing the bloatware will also prevent you from receiving the OTA. You have to be 100% stock to receive the update
Sent from the Shark Tank using XDA premium app
Why is it so hard to believe someone got an update and it didn't take? if I were updating customers devices, I would do it in very small batches to start with and then mass roll out after it is proven successful; solely for the reason that if it is jacking up devices, I don't want thousands of customers pissed until we could figure out what caused it. even if you tested extensively before pushing it out, there are so many variables that could cause a problem. Real world scenarios can be completely different than lab.
Long story short, why knock a guy who reports a problem or call them a liar when it looks to me they were simply trying to communicate their experience for the betterment of the community?
Hell if it were causing boot loops and master resets were required by even 5% of the people, I'd want to know so I could make sure certain things (contacts, pictures, home screen settings, etc) were backed up before accepting the update!
Sent from my SCH-I510 using XDA App
It got me too.
Well, I think my phone is now bricked. Was running gummy charged and when I woke up this morning the download was already done....I had no options but to resart. Now I'm looking at a triangle with a blue exclimation and a green android guy. Any ideas????
If that's true then... oh God, this is going to be a mess for those of us who have rooted and ROMed our phones.
---------- Post added at 01:25 PM ---------- Previous post was at 01:22 PM ----------
You have two options to fix this...
Download the Stock EE4 Odin ROM Image and redo the update. If you need the PIT file, you can get it here.
Or, you can install Danalo's rooted and deodexed EP4D ROM. It can be found in the thread below...
http://forum.xda-developers.com/showthread.php?t=1365376
oleo1975 said:
Well, I think my phone is now bricked. Was running gummy charged and when I woke up this morning the download was already done....I had no options but to resart. Now I'm looking at a triangle with a blue exclimation and a green android guy. Any ideas????
Click to expand...
Click to collapse
Ugh... I really hope this won't be my fate. What version of Gummy are you running?
Heads up everyone, a member over at Rootz is reporting of receiving OTA notifications while running Gummy GBE 2.1. This is the first time I am hearing of anyone receiving notifications, let alone actually receiving an OTA update while running anything but 100% stock. Be aware.
I was running gummy 2.1
So you guys think I should pull the battery and try to get it into recovery?
UPDATE. I was able to get into CWM Voodoo Lagfix recovery 4.0.0.8
oleo1975 said:
Well, I think my phone is now bricked. Was running gummy charged and when I woke up this morning the download was already done....I had no options but to resart. Now I'm looking at a triangle with a blue exclimation and a green android guy. Any ideas????
Click to expand...
Click to collapse
Are you able to boot into download? if so you should be able to odin stock ee4 and apply the ota update... at least have a usable phone.
Keep us posted!
That would be great for everyone actually. If you are having issues with update please post what happened.
Sent from my SCH-I510 using XDA App
I'd suggest that everyone who is running a custom third-party ROM, no matter who made it, to go back to EE4 as soon as possible to avoid a soft-brick.
Been on complete stock EE4 for the last 3 days. Still no update.
spc_hicks09 said:
Been on complete stock EE4 for the last 3 days. Still no update.
Click to expand...
Click to collapse
Isn't it awful...
BattsNotIncld said:
Isn't it awful...
Click to expand...
Click to collapse
No really lol, I was on the leaked update for a while but I just wanted to actually have a device finally get officially updated to GB lol.
OG Droid - No OTA past 2.2
HTC Eris - No OTA past 2.2
LG Revolution - Got gingerbread OTA..........after mine got stolen lol.
Droid Charge - still waiting lol........VZWSupport said on twitter it could be as long as 30 days before all Charges get the update.
About 30 minutes ago my phone was working fine, the last thing I remember doing was sending a text. A few minutes later I look down at my phone and notice it is in recovery. At this point I'm confused wondering how it got there, but figure it's whatever and reboot into system. It reboots back into recovery and at this point I'm kinda freaking out. I do a backup, wipe, and restore from a backup ~2 weeks ago. Again, rebooting just causes my phone to go into recovery.
Earlier today there was a notification on my phone about an update but I just ignored it as I didn't have time to deal with it. I assume that it automatically was applied and that is what caused this problem.
edit: If you have this problem, try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
nest75068 said:
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
Click to expand...
Click to collapse
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
elguy said:
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
Click to expand...
Click to collapse
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
nest75068 said:
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
Click to expand...
Click to collapse
Yeah, worked me too. Not sure what happened either, phone says its still on KVT49L.D85010d.
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I was the same - the zip file fixed my issue - didn't have to start over
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
esoteric1311 said:
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
Click to expand...
Click to collapse
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
nest75068 said:
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
Click to expand...
Click to collapse
Well i had to restore the newest back up, because I restored an old back up to see of it would reboot correctly. All works fine now. Still very weird.
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I mean I still have Root and TWRP, I might have factory reset in my panic last night before finding the fix above. Probably the cause of losing all my apps and data
ATTT Forced UPDATE
It would appear after cruising the forums this morning that ATT forced an update to all users last night. It happened to me and many others like yourself. even people that had turned off updates in the hidden menu. It is total crap and not to happy about it obviously. good thing it sent me into a boot loop, and @autoprime zip fixed me up, even though i was back up on stock rooted, I took this opportunity to move over to the PoweruserV1 international rom to attempt to keep this from happening again. Luckily our DEVS are getting development moving and soon this will be a thing of the past....
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
KennyG123 said:
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
Click to expand...
Click to collapse
whats the name of the apk to freeze? Thanks
Just adding to this, that it was 'forced' onto me as well, and also sent me to soft brick loop (TWRP), so I'm having to use the get out of jail thread. THANKS LG!! YOU GUYS ROCK!!! (#[email protected]%&*!!!!) This is the LAST time I trust another corporate BS liar's announcement that they care about the 'community' and are going to try and be nice 'from here on out'. Moving forward, it will be NEXUS and nothing else for me.
esoteric1311 said:
whats the name of the apk to freeze? Thanks
Click to expand...
Click to collapse
It is called Software Update in TB. I only have it frozen since last night so hopefully this does the trick...it also removes update option from settings FYI.
Anyone else have this happen again last night? Phone was fine at 5am, woke up at 8:30 to recovery. Flashed the same zip and now it's all fine again.
Freeze software update with titanium backup so your phone doesn't try to install the update agian
wow att and their updates f*** with everything, currently having a locked s4 with old firm of mf3. i plan on upgrading my device but on the fence with all this lock down bs. switching to tmobile seems like a decent option...... so confused and undecided
My G3 has 5.0.1 and I have rooted it. Nothing more.
I got notification of the latest update, which had VoLTE, something about Uber (which is already in my bloatware) and something else.
I have only rooted this phone, however while I was searching around on xda to see if anyone else has gone through this update with root, I found a 1-line fix to disable authentication on WiFi tether. I did that, and then some time later I got a pop-up saying my phone is suspected of being rooted, so the update would be disabled. I then reversed the WiFi tether change, and checked for update and it _seems_ like it is ready to do the update.
But, has anyone out there gone through this update while rooted? Did that work and you only had to root again?
Or do I have to un-root?
pourhaus said:
My G3 has 5.0.1 and I have rooted it. Nothing more.
I got notification of the latest update, which had VoLTE, something about Uber (which is already in my bloatware) and something else.
I have only rooted this phone, however while I was searching around on xda to see if anyone else has gone through this update with root, I found a 1-line fix to disable authentication on WiFi tether. I did that, and then some time later I got a pop-up saying my phone is suspected of being rooted, so the update would be disabled. I then reversed the WiFi tether change, and checked for update and it _seems_ like it is ready to do the update.
But, has anyone out there gone through this update while rooted? Did that work and you only had to root again?
Or do I have to un-root?
Click to expand...
Click to collapse
I'm in the exact same boat as you. Can't finish the update due to being rooted before. Even if you factory reset it will still say you're suspected of rooting.
Here is my thread just in case you want to give it a glance.
http://forum.xda-developers.com/att-lg-g3/development/to-pick-ota-trapped-root-t3106573
Here is the link to unroot back to 10D
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I haven't exactly solved this issue yet but I'm working on it >.<
Btw don't use that unroot link just yet. I need to confirm and read around before finding out if it's a viable method for our situation yet.
pourhaus said:
My G3 has 5.0.1 and I have rooted it. Nothing more.
I got notification of the latest update, which had VoLTE, something about Uber (which is already in my bloatware) and something else.
I have only rooted this phone, however while I was searching around on xda to see if anyone else has gone through this update with root, I found a 1-line fix to disable authentication on WiFi tether. I did that, and then some time later I got a pop-up saying my phone is suspected of being rooted, so the update would be disabled. I then reversed the WiFi tether change, and checked for update and it _seems_ like it is ready to do the update.
But, has anyone out there gone through this update while rooted? Did that work and you only had to root again?
Or do I have to un-root?
Click to expand...
Click to collapse
I had to un-root, update, then root again using one click.
rrktt said:
I had to un-root, update, then root again using one click.
Click to expand...
Click to collapse
To be specific about "un-root".
You don't mean that you simply unrooted via SuperSU, do you? I assume you actually restored back to stock KitKat 10d, correct? And then took the OTA update straight to 21l, correct?
(And where can you tell the phone to check for updates again? or did you just wait for it to pop up in the notification area?)
Thanks
ultrasuper said:
To be specific about "un-root".
You don't mean that you simply unrooted via SuperSU, do you? I assume you actually restored back to stock KitKat 10d, correct? And then took the OTA update straight to 21l, correct?
(And where can you tell the phone to check for updates again? or did you just wait for it to pop up in the notification area?)
Thanks
Click to expand...
Click to collapse
I unrooted back to stock kitkat 10d and took the OTA update to 21l.
To check for the OTA update, go to General --> About Phone --> Software Update --> Update now
I did try to update when rooted before restoring back to stock. It failed during installation with a message about suspicion of rooting.
rrktt said:
I unrooted back to stock kitkat 10d and took the OTA update to 21l.
To check for the OTA update, go to General --> About Phone --> Software Update --> Update now
I did try to update when rooted before restoring back to stock. It failed during installation with a message about suspicion of rooting.
Click to expand...
Click to collapse
Yup I just had to go through all this as well. Luckily it all went smoothly and my phone is back up to spec and loaded the way I use it daily. Took about 12 hours of deliberate effort though haha. I guess I never really knew how much stuff I had on the phone and how much time goes into editing settings and logging into everything. Anyways UltraSuper you're right. Had to use the link I posted above using LG Flash Tool and go back to kit kat then you can upgrade easily to 21l, LG one click root, use AutoRec to flash TWRP then do your first backup just in case something goes south but it's doubtful. My phone is stable as it was out of the box.
So what does this update offer? Is it worth the hassle of redoing everything?
sent from a device using an app
Did you do a twrp restore after the update? did Xposed work in the new update?
I may do this tonight
Thanks.
joeclark said:
So what does this update offer? Is it worth the hassle of redoing everything?
sent from a device using an app
Click to expand...
Click to collapse
To be honest I went through the whole process and I'll probably never use volte. I did it more just to have a clean start. I've been flashing like crazy and things were starting to get buggy. If things are running smooth for you I don't see the value in it unless you're planning on using volte.
Sent from my LG-D850 using Tapatalk
joeclark said:
So what does this update offer? Is it worth the hassle of redoing everything?
sent from a device using an app
Click to expand...
Click to collapse
VoLTE. That is the only notable thing about the update. A couple of pieces of bloat are in there as well. VoLTE is still new and not available everywhere yet and is only able to be used by a select few models of phones. Read up on it and decide. I personally do not see the need for the hassle atm so will wait until another day.
When the Android O OTA update is available from my carrier, will updating wipe out data? I know we can get the update files and manually flash them (right now without having to wait for carriers), but that will wipe data which I'd like to avoid doing. But if the carrier OTA will wipe the data anyways, then there's no reason to wait
As a side note, with other phones I probably would have rooted by now, but it honestly hasn't seemed necessary with the Pixel yet. Since I haven't rooted so far, I'd kind of like to avoid it. The only thing I wish I had right about now is TWRP and Titanium Backup :/... that would make updates wiping data irrelevant.
Sent from my Pixel using Tapatalk
Nevermind, now irrelevant
Enrolling in the beta program (https://www.google.com/android/beta) will give you the update immediately, without wiping anything.
Sent from my Pixel using Tapatalk
That's what I've just done also.
Does frustrate me that they release the carrier supported updates before those with sim free devices
I got the ota update but couldn't update. Keeps telling me that there's an installation problem. Been trying all day. Anyone has the sams thing going? Im on verizon
akksnv said:
Nevermind, now irrelevant
Enrolling in the beta program (https://www.google.com/android/beta) will give you the update immediately, without wiping anything.
Click to expand...
Click to collapse
If I do this and am offered the update from Google, do I first need to return to stock? I'm on PureNexus right now. I assume that would cause issues if I tried to update?
PsiPhiDan said:
If I do this and am offered the update from Google, do I first need to return to stock? I'm on PureNexus right now. I assume that would cause issues if I tried to update?
Click to expand...
Click to collapse
I'm not sure, I was already on stock so I didn't have that issue. I would assume going back to stock would be the recommended method, though.
Sent from my Pixel using Tapatalk
Abaddon said:
I got the ota update but couldn't update. Keeps telling me that there's an installation problem. Been trying all day. Anyone has the sams thing going? Im on verizon
Click to expand...
Click to collapse
What is the installation problem that it shows on the screen?
mcbeat257 said:
What is the installation problem that it shows on the screen?
Click to expand...
Click to collapse
This one. I saw a lot of ppl on XL have this too. :L I'm still waiting for an OTA backup zip from google ot someone with an OTA URL to manually side load it via recovery
Abaddon said:
I got the ota update but couldn't update. Keeps telling me that there's an installation problem. Been trying all day. Anyone has the sams thing going? Im on verizon
Click to expand...
Click to collapse
Have you tried rebooting? I had the same issue and it installed right after rebooting.
Sent from my Google Pixel using XDA Labs
Try cleaning the cache from the "Google Play Services" app so that it can update freshly.
PsiPhiDan said:
If I do this and am offered the update from Google, do I first need to return to stock? I'm on PureNexus right now. I assume that would cause issues if I tried to update?
Click to expand...
Click to collapse
You have to be fully stock and unrooted to take an OTA. There are some mild exceptions but I'm not going to go into all the details. You defnitely can't take stock ROM OTAs when you're running a custom ROM such as PureNexus.