Android O Carrier OTA and Data - Google Pixel Questions & Answers

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.

Related

Moto has apparently released a software update

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.

[Q] VoLTE OTA update from AT&T - do I need to un-root to be able to install this?

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.

New security update OTA issues LMY47X.N920VVRU2OJ3

Anybody else having issues receiving the latest OTA released today? I've tried 3 times now with it returning an error on the recovery screen and when it boots back into the OS it says the update failed with no explanation.
Mine worked first try. Software update complete. It even mentioned making sure to charge the battery as the update may have drained it...
Mine worked Ok. How much memory do you have remaining free? Maybe that is an issue...?
New firmware update huh? I have not gotten my notifcation yet. I'll do a manual check, but I'm stll on the default OGJ firmware and modem.
KruseLudsMobile said:
Mine worked Ok. How much memory do you have remaining free? Maybe that is an issue...?
Click to expand...
Click to collapse
4.01 GB free and the funny thing is I actually just did a fresh restore using the previous AOJ2 firmware via ODIN and I used the PIT file as well. I'm gonna try again and see what happens in a moment.
Manually checked for the update. Went without any hiccups.
Sent from my SM-N920V using Tapatalk
Just tried again, it's giving me error code 410. A Google search is suggesting a factory reset. :silly:
enzyne said:
Just tried again, it's giving me error code 410. A Google search is suggesting a factory reset. :silly:
Click to expand...
Click to collapse
Have you disabled anything that could be causing a conflict? If not, I'd do the FDR and then try again.
Good luck.
What does it do? Any significant changes?
Sent from my VK700 using Tapatalk
Geezer Squid said:
Have you disabled anything that could be causing a conflict? If not, I'd do the FDR and then try again.
Good luck.
Click to expand...
Click to collapse
On a couple of other devices I had, I had stuff disabled and that was the cause of the OTA failure. I currently used the debloater on my Note 5 to disable/hide a bunch of stuff. I will try to re-enable all those, and then try the update.
toskabab said:
What does it do? Any significant changes?
Sent from my VK700 using Tapatalk
Click to expand...
Click to collapse
I don't see any changes as to what we interact with, but new Android security patches and does have a new kernel with a different date, not sure if anything changed on the internals of it. Have new entry in about device of android security patches and November 1st date.
Sent from my SM-N920V using Tapatalk
Just an update I also had alot of apps disabled as well and re-enabling them did not fix the issue. I had to install samsung smart switch on my pc and do the update manually and it worked with no factory data reset which was optimal because transferring my music collection via MTP is a pain in the a$$. I will post the firmware if anyone needs it, but there is also a firmware thread that should be updated momentarily.
Android security patch = hogwash
They are just making it harder to achieve root. ?
Sent from my VK700 using Tapatalk
Did my update over lte.
I noticed major lag for like a couple hours after. Now it works smoother and it seems like my standby drain is fixed. 11% in 7 hours with 45mins SOT.
I'm using the Verizon note 5 on AT&T and I can't update? Do I need a Verizon sim card to be able to update?
I'm on OJ2 BTW
jacky37 said:
I'm using the Verizon note 5 on AT&T and I can't update? Do I need a Verizon sim card to be able to update?
I'm on OJ2 BTW
Click to expand...
Click to collapse
Do you have a computer? Plug it in and install the updater. You might be able to pull the update from there.
Sent from my SM-N920V using Tapatalk
jacky37 said:
I'm using the Verizon note 5 on AT&T and I can't update? Do I need a Verizon sim card to be able to update?
I'm on OJ2 BTW
Click to expand...
Click to collapse
As these updates are often specific to carriers, I'd be surprised if the installer did not look for the sim card to absolutely verify carrier. Just my guess. Good luck.
Didn't work. I think I need a Verizon sim
I wonder if you can get a hold of an old non-working Verizon sim and see if it works. If so, you can just switch them out any time you want to update. Try eBay or something.
Sent from my SM-N920V using Tapatalk
Will give it a try

Android OS Data Usage

Lately my Android OS has been using A LOT of data. I'm just curious to see if anyone else has had the issue.
In the last 30 days, my Android OS has used approx. 27 GB.
I am rooted, and was on NDE63V when this occurred.
I am currently in the process of updating my phone to the latest firmware for (what I believe is) only Canadian carriers. So I am hoping the solves the issue.
I downloaded a data usage app which helps limit apps from using data, and tells me which ones are doing it.
Currently, through this app my usage falls under:
Android System - 11 GB
com.qti.service.colorservice - 6.8 GB
com.qualcomm.atfwd - 6.8 GB
com.qualcomm.fastdormancy - 3.8 GB
At first it was just the fastdormancy one that was getting me, until I went into TiBU and froze it. After that, it stopped using data but the other 3 really started eating up my data.
I feel like I was going to post more in this, so if anyone wants more relevant information, please let me know. I really need this figured out. I have had to upgrade my plan from 10gb to 25 gb and now I am already 8gb over my limit. Last night I was 4gb under it. My phone has somehow used 12 gb in roughly 14 hours.
I checked my brothers stock Pixel XL, and Android OS has used only (but still seems like a lot) 300mb. Which I attributed to his update to the latest firmware for Canadian carriers, which was roughly 260mb.
Can anyone help shed some light onto what is happening with my data?
Possibly related to the seemless update function failing because of root. The pixel can't apply the update and keeps downloading it over and over again. for me applying the latest OTA fixed the issue. another solution is to disable the automatic updates in the developer options
Sent from my Pixel using XDA-Developers mobile app
My mobile data usage has doubled after moving to the PIxel despite near identical usage to previous phone.
For me com.qti.service.colorservice is the culprit but have no idea why or what it is for.
Alex
noonecanhide said:
Possibly related to the seemless update function failing because of root. The pixel can't apply the update and keeps downloading it over and over again. for me applying the latest OTA fixed the issue. another solution is to disable the automatic updates in the developer options
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
That's what I was thinking. I just applied the update last night and re rooted. Everything seems fine so far. I'll have a better idea at the end of the day.
GeekMcLeod said:
That's what I was thinking. I just applied the update last night and re rooted. Everything seems fine so far. I'll have a better idea at the end of the day.
Click to expand...
Click to collapse
Any update on this? I'm rooted, so it's a little inconvenient for me to apply the update.
ryan4a said:
Any update on this? I'm rooted, so it's a little inconvenient for me to apply the update.
Click to expand...
Click to collapse
You need to apply the update for the issue to be resolved. I too had this problem.
drocny87 said:
You need to apply the update for the issue to be resolved. I too had this problem.
Click to expand...
Click to collapse
Bummer! I was hoping it was a setting fix. Still not sure why it started happening for no reason. I'll have to back up my data, wipe, sideload the update, re-root, then restore my data. I was hoping to avoid all that mess, but it seems to be the only way to apply the update.
ryan4a said:
Bummer! I was hoping it was a setting fix. Still not sure why it started happening for no reason. I'll have to back up my data, wipe, sideload the update, re-root, then restore my data. I was hoping to avoid all that mess, but it seems to be the only way to apply the update.
Click to expand...
Click to collapse
I never had to do that to update to the latest. I just followed this guide.
http://forum.xda-developers.com/showpost.php?p=69576990&postcount=7
You do lose root and that sorta thing but you do not lose any data doing this.
GeekMcLeod said:
I never had to do that to update to the latest. I just followed this guide.
http://forum.xda-developers.com/showpost.php?p=69576990&postcount=7
You do lose root and that sorta thing but you do not lose any data doing this.
Click to expand...
Click to collapse
That is a guide to manually update your phone through fastboot. The toolkit will do all of that without typing any commands just choose no when it asks to format data and you will not lose data.
drocny87 said:
That is a guide to manually update your phone through fastboot. The toolkit will do all of that without typing any commands just choose no when it asks to format data and tou will not lose data.
Click to expand...
Click to collapse
To each their own. Just simply stated the way that I did it to not lose data as I prefer manually doing it.
I had the EXACT same issue that I struggled with. There's a bug on the build you're on and it'll keep trying to download that OTA as long as you have data enabled (regardless if Wifi is enabled - ARG!!!).
I just got over $50 in usage charges that I know of, then I left my phone on with data and my bill says $600..... I flashed NMF26Q and it corrected the issue. Only a mb or two every few hours. With this bug, I was downloading a gig a day! Need to call my carrier and see if they'll credit some of those charges. Hope this helps!
my phone used over 110gb of data last month because of this error I am getting a refund from verizon now but has anyone figured out the problem? I just updated to the latest version and hope it stops killing my data otherwise i dont know what to do
Sideloaded 7.1.1 from 7.1 tonight.
Hope this fixes my issue!
Thanks for the help gents!
Artnig said:
my phone used over 110gb of data last month because of this error I am getting a refund from verizon now but has anyone figured out the problem? I just updated to the latest version and hope it stops killing my data otherwise i dont know what to do
Click to expand...
Click to collapse
Wow, 110gb of behind the scenes data is a lot to go unnoticed!

Taking September security update on rooted Oreo

I'm on rooted Oreo 8.0. In UK. Security update has appeared. Anyone tried taking it on a rooted Oreo Pixel? I'm not too bothered about losing root, that's easy to put right, I just want to avoid a time consuming disaster.
All working fine here, of course have to reroot and whatnot. But no problems.
It won't let me install it. Whatever no big deal
cgrimm9 said:
It won't let me install it. Whatever no big deal
Click to expand...
Click to collapse
It won't let me install it as well. Don't want to have to update by flashing factory image and losing data. But. It wouldn't be the first time. So, yeah no big deal, just a bit of a pain.
Horgar said:
It won't let me install it as well. Don't want to have to update by flashing factory image and losing data. But. It wouldn't be the first time. So, yeah no big deal, just a bit of a pain.
Click to expand...
Click to collapse
Before flashing factory script, edit the script to remove "-w"
It is the "-w" that wipes device, not the factory firmware.
This has been discussed again and again since November 2016.
Sent from my sailfish using XDA Labs
I downloaded the full image and removed the -w in the flash-all then saved it and updated, rerooted, added back su hide no problem at all. Even kept my theme installed!
Archangel said:
I downloaded the full image and removed the -w in the flash-all then saved it and updated, rerooted, added back su hide no problem at all. Even kept my theme installed!
Click to expand...
Click to collapse
Did you have to wipe the internal storage in TWRP as the root guide suggests again? Or was that a one time deal for when we first move to Android O?
Sent from my Pixel using Tapatalk
Nope didnt wipe internal storage. But I assume that was needed coming from N to O and I modded the flash all bat to not erase my system for this Sept full image. So far so good, if i see anything bad I will report back here.
mike86325 said:
Did you have to wipe the internal storage in TWRP as the root guide suggests again? Or was that a one time deal for when we first move to Android O?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Same here. Used the image from the Google site with the -w removed and no wipe. Re-roooted with no issue and it even kept suhide and it functioned after the root. Did this on an XL and a Pixel last night with no issues so far. No Google Play Services crashes on reboot either, so that is a win.
Does anyone know what are the issues with september update? Or google just fixed everything with this new release?
I can't find the changelog anywhere :/
Anyone actually had the Sept update yet?
I haven't.
Update: just unenrolled from the Beta and the update popped up.

Categories

Resources