I followed the instructions here to sim-unlock my Verizon XT1528 and am now using it on Consumer Cellular. I have disabled most of the built-in verizon and moto apps, however it seems that the OTA updater has already downloaded a system update, as it keeps repeatedly prompting me to install the update.
Will installing the update cause any issues with my current service? Will it need to be re-unlocked? Or will it continue working the way it is after the update has been installed? Or will the "other improvements" make it useless to me.
The current software version is 23.11.17.survia_verizon.verizon.en.US.vzw, build # LPI23.29-17, android version 5.1 (screenshot)
The new software version it wants to install is 23.16.5.en.US. (and it really wants to install it!).
Part of the reason I'm concerned is that according to the page on their website, "This update brings Android™ 5.1 Lollipop to your phone along with other improvements", however the phone already has 5.1 on it.
To be clear, I am talking about the verizon XT1528 Moto E 2nd Generation with the locked bootloader--it is not possible to root it or install another ROM.
Lastly, if updating will lock me out of using Consumer Cellular on it, is there any way to remove the update and/or prevent the prompt from showing up again.
@StanSt
For what it worth this is what mine is running. I'm on AT&T though. I don't know if that would make any difference or not.
Worked Fine
I updated my wife's xt1528. GSM still works.
crazyjim_68 said:
I updated my wife's xt1528. GSM still works.
Click to expand...
Click to collapse
Note that the original post was inquiring about a previous update.
There is an update in the past couple of days or so (late April - early May 2016) that brings it up to 23.201.2 etc etc , build LPIS 23.29-17.5.-2
Moto says changes are "Includes the updates of Android security patches until April 1st 2016."
GSM still works after this latest May update.
I have a completely stock Nexus 9. My wife's Nexus 9 took Android 7 a couple of weeks ago. I was checking my today and noticed that mine is still sitting at the June 1, 2016 security patch level. When I check for a system update it says my system is up to date. I tried booting to recovery and clearing the cache, but it still isn't seeing the need to update. Is there anything else I can do to "clear" the system so it can realize there are a few security updates to install (and of course android 7)? I am just trying to avoid installing ADB and such to install it manually.
Thanks in advance.
Is yours an LTE, by any chance? N still isn't posted. The easiest for you to do at this point is join the beta, take the download/install, then, remove your tab from beta. As long as it installs nougat NRD90R , it won't wipe your device when you uninstall. In fact, even before, it wouldn't wipe your device unless you installed the 6.1 package Google would send after leaving nougat.
http://www.howtogeek.com/268299/how-to-upgrade-your-nexus-now-without-waiting-for-the-rollout/
Sent from my Nexus 5 using Tapatalk
It is the WiFi only version.
radcpuman said:
It is the WiFi only version.
Click to expand...
Click to collapse
To clarify when I said leave beta, I didn't mean uninstall but rather unregister your device from Beta program.. That would have been confusing.
Sent from my Nexus 9 using Tapatalk
Because I didn't get OAT update I downloaded the complete firmware
"XT1941-4_DEEN_RETEU_9.0_PPK29.68-16-8-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" (date 2019-01-08) and flashed it using this script. https://forum.xda-developers.com/showpost.php?p=78287372&postcount=18
All went well. And root with Magisk wasn't a problem.
But why does security level show security update of November???
Sylvia said:
Because I didn't get OAT update I downloaded the complete firmware
"XT1941-4_DEEN_RETEU_9.0_PPK29.68-16-8-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" (date 2019-01-08) and flashed it using this script. https://forum.xda-developers.com/showpost.php?p=78287372&postcount=18
All went well. And root with Magisk wasn't a problem.
But why does security level show security update of November???
Click to expand...
Click to collapse
I don't know what that firmware is all about. Build date is from end of November if I remember it right. I never flashed it.
December patch is 29.68-16-21. Unfortunately it doesn't seem that the RETEU December update is available for download anywhere.
Sent from my H9436 using Tapatalk
Because the file is dated "2019", I thought that is is the actual firmware. Some of the files inside the zip are from November, some from December...
Ok, so I have to wait if I'll get the update the next days. There is no way to "force" that, is it???
You should have got it already, but it needs full stock without root to install without error.
Go to settings / system / advanced and check for update.
Sent from my Motorola One.
Don't know if anybody had the same problem with OAT Updates: Meanwhile the full firmware with security level 1st January can be downloaded here
https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/XT1941-4_DEEN_RETEU_9.0_PPKS29.68-16-21-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Haven't seen anything about a March update. Aren't they released on the 1st Monday of the month?
samnada said:
Haven't seen anything about a March update. Aren't they released on the 1st Monday of the month?
Click to expand...
Click to collapse
Yo last month the update came on 5 february (tuesday)
it's live.
https://source.android.com/security/bulletin/pixel/2019-03-01.html
Updated and re-rooted the wife's Pixel 3 today. Magisk 18.1 with TWRP 3.2.3-0 (.img only). ElementalX 1.05 with EX Kernel Manager direct flash. All worked normally. Couldn't do my 3XL this month since I am on dotOS. I did have to clear cache and app data (hide with Magisk of course) to get Play Store to re-certify the device which then showed a Google Pay update. Even though they claim no security fixes, clearly there are some.
anthony_dumas said:
Yo last month the update came on 5 february (tuesday)
Click to expand...
Click to collapse
The Feb bulletin was published on Mon the 4th. Patch is dated the 5th. I had read they always patch on the first Mon, but apparently sometimes not quite. March bulletin is out, so good to go.
Guys, upon checking for updates, my phone seems to be stuck on "Preparing system update.." while the spinner just keeps going.. Any suggestions?
Prasad said:
Guys, upon checking for updates, my phone seems to be stuck on "Preparing system update.." while the spinner just keeps going.. Any suggestions?
Click to expand...
Click to collapse
I'm not sure you want to update at this time. I just did the update and now my screen has that weird green flash when ambient display is on. Might want to hold off if you can.
bobby janow said:
I'm not sure you want to update at this time. I just did the update and now my screen has that weird green flash when ambient display is on. Might want to hold off if you can.
Click to expand...
Click to collapse
Actually I just sideloaded it and all seems well! I'll keep an eye out for the aforementioned issue though.. thanks!
Personally, I'm not seeing a noticeable camera app loading time improvement..
Prasad said:
Actually I just sideloaded it and all seems well! I'll keep an eye out for the aforementioned issue though.. thanks!
Personally, I'm not seeing a noticeable camera app loading time improvement..
Click to expand...
Click to collapse
Just updated my wife's phone and it's not happening on hers yet. Some are saying it takes a little time. We'll see. Camera app was never an issue for me.
For those rooted with twrp, did you download the 1.7gb zip from Google and flash through fastboot, then reinstall twrp and magisk?
codygs83 said:
For those rooted with twrp, did you download the 1.7gb zip from Google and flash through fastboot, then reinstall twrp and magisk?
Click to expand...
Click to collapse
I just got my pixel 3 today. It had the January update installed on it. I downloaded the March factory image, removed the -w and flashed via fastboot and then unlocked bootloader and installed twrp and magisk 18.1 with no issues. I was not rooted before hand though being as the phone was brand new. Only issue is slow charging at the moment but I'm not sure if it was like that before the update since I rooted right away out of the box.
I have my pixel 3 rooted and TWRP installed. Can i flash the march ota.zip via TWRP and then install TWRP and magisk again? will that work?
Would love if someone could share their patched_boot.img please
Here Ya go (problem uploading
I tried to do the update yesterday (like i've done it the last 3 times before), but came into bootloops to the point, where i had to factory reset everything. After resetting and reflashing in fastboot, it would start again. Today I wanted to flash magisk 18.1 and went straight into bootloops again. So that seems to be the problem. How do I get the uninmod.zip from my phone to my computer? I tried the command push adb "file" "sdcard" but it gave me a "adb: error: failed to get feature set: no devices/emulators found"
thanks for your help!
Anybody else has problems with google pay on march update?
i got magisk 18.1 installed, magisk hide checked for g pay, cleaned cache and everything, but g pay still tells me phone is rooted.
any help appreciated.
Bluffer94 said:
Anybody else has problems with google pay on march update?
i got magisk 18.1 installed, magisk hide checked for g pay, cleaned cache and everything, but g pay still tells me phone is rooted.
any help appreciated.
Click to expand...
Click to collapse
GPay now seems to be reporting if your device in not showing as certified by Play Store. Hide Pay store, clear app cache and data for Play Store, and reopen it and check settings to see if it is certified. Did you get the new GPay the other day? That update didn't show immediately after the update because you needed to re-certify.
sliding_billy said:
GPay now seems to be reporting if your device in not showing as certified by Play Store. Hide Pay store, clear app cache and data for Play Store, and reopen it and check settings to see if it is certified. Did you get the new GPay the other day? That update didn't show immediately after the update because you needed to re-certify.
Click to expand...
Click to collapse
Play Store is certified. Google pay is up-to-date.
Gesendet von meinem Pixel 3 mit Tapatalk
Bluffer94 said:
Play Store is certified. Google pay is up-to-date.
Gesendet von meinem Pixel 3 mit Tapatalk
Click to expand...
Click to collapse
Is GPay reporting the root when you open the app or when you touch a terminal to pay? My wife's Pixel 3 (which I updated) is able to open GPay with no issue, but she hasn't used it at a terminal since the update. My 3XL is running a custom ROM, so it got the GPay update but not the March update. Mine also opens fine but I haven't used it at a terminal.
I am rooted with Magisk and running the Raviole kernel. My Play System will not update past July no matter what I do. I delete all but one account on my phone and followed those instructions and still nothing. I have a 24MB update available and I've tried 20 times to download and install it but on reboot I just have the same level still. Anyone have a similar issue or know of a workaround? I even did a factory image install with the update to A13...twice.
I got on September 14(!) also the 24MB update, but then it showed I am now on August patch level.
Maybe it has something to do with your kernel?
Cheers
I checked on the kernel and that shouldn’t be the issue. I don’t know if Magisk would have any effect on it. I’m kind of out of ideas for the time being.
stock unrooted, and I just got the August Play system update yesterday. Prior to that I got 3 updates that were all dated July.
have you tried installing the apk from apkmirror ?
Fytdyh said:
have you tried installing the apk from apkmirror ?
Click to expand...
Click to collapse
The apk is only a "visual" update and only displays August update, too small for the complete PlaySystem Update.
But some reported after installing, it triggered something and after a while the "real" system update was downloaded and installed.
Cheers