Due to the operation error, my phone lost DL and TWRP, and I need the next ota update to retrieve the DL
随波逐流啊 said:
Due to the operation error, my phone lost DL and TWRP, and I need the next ota update to retrieve the DL
Click to expand...
Click to collapse
October 7 + 3 months. Can be sooner, but that's the rough deadline.
Last KDZ arrived October 7. OTA a few days before that.
There were times on Oreo that T-mobile delivered updates every two months, to fix issues, but the Android Enterprise requirement for V30 is at least every 90 days.
Related
Has anyone received thus OTA yet? Google posted the images for 5.1.1 online 29 days ago, but I haven't received it yet.
Germany lte version using 5.1.1 since ca. 2 weeks or so
Translated with my own brain to English
I still have not received the Android 5.0.2 update to upgrade
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
stock not rooted lte nex 9 -- received the ota to 5.1.1 over two weeks ago i think - los angeles
swcampbell said:
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
Click to expand...
Click to collapse
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
DonDerham said:
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
Click to expand...
Click to collapse
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Click to expand...
Click to collapse
No loss of data assume the bootloader is already unlocked. In my case, it's still locked. Obviously, I can back up everything and flash, but part of the reason for buying a Nexus device includes prompt OTAs.
The device downloaded and installed 5.0.2 without a hitch. On reboot, it downloaded the 5.1.1 OTA, but errored on installation. I cleared the cache, rebooted and it repeated the process with the same error result. Nexus tech support, when they hear OTA, pretty much say "we know nothing."
So, I'll backup the device as best I can, do a factory reset and try the OTA again.
Now, I can unlock the device and ADB the images manually. Why not do so? You'd have to be married to understand. This is my wife's tablet. If I unlock the bootloader or root it or do anything other than "normal" Google stuff and anything ever goes amiss, my lovely wife will complain that my tinkering has caused her Candy Crush and Facebook to malfunction.
has anyone lost root updating to current this month? i know my v10 became an ad filled, stock navbar, paper weight after it's last forced update.
I'm curious about this as well.
I finally got around to rooting my Stylo 3 Plus for the first time over the weekend, after closely following the developments in this forum for the past 6 months. It took a lot of trial and error and reflashing of TWRP before I got the timing down right, but I finally got it rooted (using Magisk 15.2).
And of course, luck would have it that within a few hours of my rooting success, a new system update notification (which I had never heard of until now!), pops up and asks me to restart to install it. I am using Titanium Backup to force stop the particular Google service involved, which makes the notification go away and I can reboot without it upgrading. But it always come back within 24 hours or so.
Has anyone installed this update yet (MP45010f) and successfully re-rooted? I'm currently using Magisk 15.2 with systemless hosts, Ad-Away, and Xposed with Greenify & MinMinGuard enabled. I would welcome any advice on how to proceed after the update to restore root and continue using Ad-Away, Xposed, etc. Or even how to disable the update notification for good so I can stay on MP45010e a while longer.
eliaslear said:
has anyone lost root updating to current this month?
Click to expand...
Click to collapse
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
yeah thats what i did was revert back to stock so u can update then i update it then re rooted my phone
if you update using the LG Bridge computer program, it will update a rooted phone. but you will need to reroot afterward.
joetbd said:
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
Click to expand...
Click to collapse
Thanks for testing this out. If you don't mind me asking, which method do you use to root? And do you also use Xposed?
To anyone else who might know, does everything Magisk- or Xposed-related get removed by the security updates (frameworks, modules, configs, etc)? Just trying to get an idea how many of my modules I should expect to reinstall and configure from scratch if I decide to update from 10e to 10f.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
Yeah, I thought this was kind of weird too. I've never used LG Bridge to update. The notification just appeared on my phone shortly after rooting.
Is Xposed only for Magisk or can it be used on the rom, if so can I get a link to how to do so
LG Bridge
DM.IDOL said:
root?
Click to expand...
Click to collapse
Im using Magisk 16.1 (no Xposed) and TWRP 3.2.1
I have not run into any issues.
It appears to simply be a security patch update.
I doubt it should cause any new headaches.
The original method still works to reroot and reinstall TWRP.
Using the LG Bridge program is about as easy as an update can be. You install it on your computer, plug your phone into the computer, and click "update" on the computer program. Its all automatic.
I've got an AT&T Galaxy S9+. I didn't get any updates since July 2019. I was able to flash the October release with Odin a few days ago. However, I still get the "software is current" when I check for updates. I checked initially before anything else installed, so it's not like there was anything on my phone. I've cleared cache, factory reset, and still cannot pull the December OTA update. Any ideas or suggestions? As anyone who has dealt with AT&T, they are of no help at all.
Robjohn764 said:
I've got an AT&T Galaxy S9+. I didn't get any updates since July 2019. I was able to flash the October release with Odin a few days ago. However, I still get the "software is current" when I check for updates. I checked initially before anything else installed, so it's not like there was anything on my phone. I've cleared cache, factory reset, and still cannot pull the December OTA update. Any ideas or suggestions? As anyone who has dealt with AT&T, they are of no help at all.
Click to expand...
Click to collapse
they literally are no help at all and their phones are the absolute worst when it comes to updates. Very common complaint about them. Most folks just manually flash the update while swearing at at&t
I'm looking to update to the november update by using adb since my phone doesn't seem to be getting the update. It's an unlocked version from Google but I use it on Verizon. Do I need to download the verizon version of the update or just the generic?
download the google AND the verizon. Flash google, then verizon over it?
Krusej23 said:
I'm looking to update to the november update by using adb since my phone doesn't seem to be getting the update. It's an unlocked version from Google but I use it on Verizon. Do I need to download the verizon version of the update or just the generic?
Click to expand...
Click to collapse
Verizon version. I just did it, for some reason it's not getting pushed out. Same situation as you, Google device VZW provider.
Pachacouti said:
download the google AND the verizon. Flash google, then verizon over it?
Click to expand...
Click to collapse
There is no reason to do that.
Thanks, I just sideloaded the November update and it worked. It looks like it's a major issue for Verizon users and the Pixel 6 and some others at launch.
Krusej23 said:
Thanks, I just sideloaded the November update and it worked. It looks like it's a major issue for Verizon users and the Pixel 6 and some others at launch.
Click to expand...
Click to collapse
Yeah I saw that on Reddit.. Easy enough to do the side load until they figure it out.
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Hi all, I've got this same issue (unlocked P6 being used on VZW unable to get the Nov security update). Seems like the official guidance is to sideload the VZW version (SD1A.210817.036.A8) and then you'll be on the VZW update path. However, I'm getting an error when trying to sideload. On my phone, it says:
Code:
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
I've verified that I'm using the correct file (oriole-sd1a.210817.036.a8-factory-65854912.zip) and verified the file with the SHA-256. Any suggestions for how I might fix this?
Krusej23 said:
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Click to expand...
Click to collapse
Mine did that only once. Rebooted and it's never happened again. Also by sideloading the VZW version we should then get the OTAs moving forward from what I understand.
meberko said:
Hi all, I've got this same issue (unlocked P6 being used on VZW unable to get the Nov security update). Seems like the official guidance is to sideload the VZW version (SD1A.210817.036.A8) and then you'll be on the VZW update path. However, I'm getting an error when trying to sideload. On my phone, it says:
Code:
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
I've verified that I'm using the correct file (oriole-sd1a.210817.036.a8-factory-65854912.zip) and verified the file with the SHA-256. Any suggestions for how I might fix this?
Click to expand...
Click to collapse
Are you sure it's the correct file? That looks like the full factory image and not the OTA.
Krusej23 said:
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Click to expand...
Click to collapse
So you lost network connectivity completely it seems. As per the previous poster reboot and it shouldn't happen again. Same thing happened here some days ago.
bobby janow said:
Are you sure it's the correct file? That looks like the full factory image and not the OTA.
Click to expand...
Click to collapse
-_- I'm an idiot, can you tell it's been a while since I sideloaded an OTA?
Thanks for pointing that out. Sideloaded the OTA no problem.
robn30 said:
Mine did that only once. Rebooted and it's never happened again. Also by sideloading the VZW version we should then get the OTAs moving forward from what I understand.
Click to expand...
Click to collapse
I rebooted multiple times, reseated the sim card and it was still doing it randomly. Took it to Verizon and they got me a new sim card. Seems to have fixed it now. Part of it was that it didn't look like it was fully activated either. I logged in MyVerizon and it still showed my 2XL as my phone instead of the 6.
Krusej23 said:
I rebooted multiple times, reseated the sim card and it was still doing it randomly. Took it to Verizon and they got me a new sim card. Seems to have fixed it now. Part of it was that it didn't look like it was fully activated either. I logged in MyVerizon and it still showed my 2XL as my phone instead of the 6.
Click to expand...
Click to collapse
Glad it's fixed. Faulty SIM was gonna be my next option. I thought that's what mine was gonna be but luckily the reboot seems to have squared it away.
So is everyone on Verizon with an unlocked phone from Google using the Verizon version of the OTA? I've been on a locked 3XL for almost three years, so it's taking me a bit to get used to things again. I've got root working perfectly and am afraid I'm going to mess it up when I sideload the OTA.
deercreek said:
So is everyone on Verizon with an unlocked phone from Google using the Verizon version of the OTA? I've been on a locked 3XL for almost three years, so it's taking me a bit to get used to things again. I've got root working perfectly and am afraid I'm going to mess it up when I sideload the OTA.
Click to expand...
Click to collapse
I used the Verizon version cause they are my carrier. I'm not rooted but I would imagine flashing the OTA via sideload would kill root. So would flashing the factory image via fastboot.
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
deusfaux said:
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
Click to expand...
Click to collapse
You're rooted so you're failing the pr-OTA block verifications, thus the OTA is failing, is the likely scenario.
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
deusfaux said:
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
Click to expand...
Click to collapse
I normally manually flash updates with fastboot.
Only use OTA update on one or two devices.
You have to restore the original boot image.
Run the update and patch the new boot image with Magisk.
Normally the steps are something like this.
1. Open the Magisk app and restore images.
--- Do not reboot ---
2. Open the OTA Updater
- Download and install the OTA -
--- Do not reboot to continue ---
3. Open the Magisk app and install to inactive slot (after OTA).
4. Switch back to the OTA updater and select reboot to continue.
Cheers.
You could use PixelFlasher to make the process a little easier If you don't want to do everything manually each month.