I just got my Pixel XL today through Verizon. It arrived with the following system:
Android Version 7.1
Security Patch Level: October 5, 2016
Build Number: NDE63P
Kernel Version: 3.18.31g895c4a6
Before taking any updates, I unlocked the bootloader. I have not rooted yet.
My questions are:
Should I take the new 01-2017 update?
Would it fail because the bootloader is unlocked?
If I can successfully update, will I be able to root on the new update?
Should I just say screw it and root on current system and just start flashing ROMs?
Any input or advice is appreciated!
Thank you!
bendrum30 said:
I just got my Pixel XL today through Verizon. It arrived with the following system:
Android Version 7.1
Security Patch Level: October 5, 2016
Build Number: NDE63P
Kernel Version: 3.18.31g895c4a6
Before taking any updates, I unlocked the bootloader. I have not rooted yet.
My questions are:
Should I take the new 01-2017 update?
Would it fail because the bootloader is unlocked?
If I can successfully update, will I be able to root on the new update?
Should I just say screw it and root on current system and just start flashing ROMs?
Any input or advice is appreciated!
Thank you!
Click to expand...
Click to collapse
Yes
No
Yes
Probably not
bendrum30 said:
I just got my Pixel XL today through Verizon. It arrived with the following system:
Android Version 7.1
Security Patch Level: October 5, 2016
Build Number: NDE63P
Kernel Version: 3.18.31g895c4a6
Before taking any updates, I unlocked the bootloader. I have not rooted yet.
My questions are:
Should I take the new 01-2017 update?
Would it fail because the bootloader is unlocked?
If I can successfully update, will I be able to root on the new update?
Should I just say screw it and root on current system and just start flashing ROMs?
Any input or advice is appreciated!
Thank you!
Click to expand...
Click to collapse
With your unlocked bootloader, you can take the new OTA without issues. New OTAs (so far) do not relock the bootloader. The January OTA runs very nice.
If you want to put TWRP recovery, you can do that and root or custom kernel next after installing the Jan. OTA.
If you flash TWRP, a custom kernel, or root it, it will not take another OTA because only an unmodified system
can receive it.
Related
Hi!
I have a question:
If I'll just unlock the bootloader (no root or recovery), will I be able to install OTA updates?
If yes, can I root it and still install OTA's?
I'm ok with having to reroot, but can I install OTA's while I have a custom recovery and root?
Thank you!
EDIT:
Thanks to ollie_o I found a solution, see below for details
I was wondering the same - I've had one small OTA update when I first turned the phone on, but nothing since I unlocked the bootloader - has there been a December security update yet?
Can anyone confirm what the most recent OS version / security update is?
Mine's running the LMY48B build (Oct 7) with the November security update (2015-11-01)
Found out the solution!
benjymous said:
I was wondering the same - I've had one small OTA update when I first turned the phone on, but nothing since I unlocked the bootloader - has there been a December security update yet?
Can anyone confirm what the most recent OS version / security update is?
Mine's running the LMY48B build (Oct 7) with the November security update (2015-11-01)
Click to expand...
Click to collapse
Thanks to olli_o, I was able to find the answer:
You can't update with root, I don't know about unlocked bootloader, but you can install updates manually even if you are rooted. You just need to re-install the root after each update
Link to guide: http://forum.xda-developers.com/wileyfox-swift/general/rom-wileyfox-swift-t3267037
:good: Thank you olli_o :good:
Hey, just bought brand new 5x and I'm still on 6.0 with oct 1sr 2015 security patch. When I go to system updates it says I'm up to date. Am not getting OTA update automatically. Im on Telenor in Serbia. Should I wait or do I have to root and flash the latest update manually?
Btw, looove the handset and OS is lagfree, no issues, but still wonder why I'm not getting the latest update. No root, LB, brand new OTB device.
5ageman said:
Hey, just bought brand new 5x and I'm still on 6.0 with oct 1sr 2015 security patch. When I go to system updates it says I'm up to date. Am not getting OTA update automatically. Im on Telenor in Serbia. Should I wait or do I have to root and flash the latest update manually?
Btw, looove the handset and OS is lagfree, no issues, but still wonder why I'm not getting the latest update. No root, LB, brand new OTB device.
Click to expand...
Click to collapse
to update it manually u don't need to have root access.
But if u like to try some new 3rd party ROMs root it :good:
Geeks Empire said:
to update it manually u don't need to have root access.
But if u like to try some new 3rd party ROMs root it :good:
Click to expand...
Click to collapse
How do I update manually? Any recommended guides? I dont feel the need to flash a custom rom, I like what google is doing with android as is for now. Just want the lates and greatest, thats why I bought a nexus.
Also would like to know the reason why I am I not getting updates automatucally. I have the international H791 model. Firmware version MDA89E. Its two OTAs outdated.
Quick thought: Shut down, remove SIM, Start the device, Connect to Wifi, Check for updates.
Just unboxed a brand new 5X 10 minutes ago and have the exact same problem...
Tried to reboot and added a Google account, charged the battery to 100% but the thing still won't find a new system version...
marioemp2k7 said:
Quick thought: Shut down, remove SIM, Start the device, Connect to Wifi, Check for updates.
Click to expand...
Click to collapse
Tried that too. I activated the device without the SIM and used it that way yesterday, inserted it just today.
Than I guess you can't do anything else unless you unlock the bootloader. At this point you can fastboot \system \boot \radio \vendor from the latest factory image or you can sideload ota zip through stock recovey.
I am having the same issue, my new nexus 5x is on 6.0 MDB08L, securiry patch level: November 1, 2015.
When I check for updates it says that my device is up to date...
The OTA will show up eventually. Or update manually.
Same thing for me in Canada. I just ended up enrolling in the Android Beta to get N preview.
Issue solved!
I got a ton of OTAs overnight while device was charging. I think it was 5 OTAs one by one that had to be installed separately, now I am on the latest April security patch and loving my nexus even more. No noticable performance difference, smooth and snappy and now up to date. So I guess updates will come you just have to be patient so google can activate them for your device. In my case it was 2 days since activation.
Info
5ageman said:
How do I update manually? Any recommended guides? I dont feel the need to flash a custom rom, I like what google is doing with android as is for now. Just want the lates and greatest, thats why I bought a nexus.
Also would like to know the reason why I am I not getting updates automatucally. I have the international H791 model. Firmware version MDA89E. Its two OTAs outdated.
Click to expand...
Click to collapse
[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot
http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
How to download and install the Android Marshmallow OTA update on Nexus devices
http://www.digitaltrends.com/mobile/how-to-install-ota-updates-on-google-nexus-devices/
:good:
Can anyone grab the OTA either from DP2 to stock 7.0 (Beta unenroll) or DP2 to final 7.1.1? (yet to come) please?
I'm stuck on this situation:
http://forum.xda-developers.com/nex...device-corrupted-screen-t3511780#post69945696
Flashing 7.1.1 DP2 went wrong and now the device is stuck with a corrupt device right to recovery scenario and a 11 november 2016 date for otas, that means that there is not any ota able to flash over it (because new otas from december are from 26october and 1november... wtf). The bootloader is locked.
So I would need the ota that google sends back to unenroll from 7.1.1 Android Preview DP1 or DP2, because they presumably don't check for build dates and just flash the stock partitions .
The device is stuck corrupted until google wants to release an OTA flashable in recovery (not staged) with a >11 nov date.
Thanks in advance!
---
EDIT: The OTA from DP2 to final 7.1.1 may also work if it's not staged! if someone can, please capture it to help me
Thanks!!!!
RusherDude said:
Can anyone grab the OTA either from DP2 to stock 7.0 (Beta unenroll) or DP2 to final 7.1.1? (yet to come) please?
I'm stuck on this situation:
http://forum.xda-developers.com/nex...device-corrupted-screen-t3511780#post69945696
Flashing 7.1.1 DP2 went wrong and now the device is stuck with a corrupt device right to recovery scenario and a 11 november 2016 date for otas, that means that there is not any ota able to flash over it (because new otas from december are from 26october and 1november... wtf). The bootloader is locked.
So I would need the ota that google sends back to unenroll from 7.1.1 Android Preview DP1 or DP2, because they presumably don't check for build dates and just flash the stock partitions .
The device is stuck corrupted until google wants to release an OTA flashable in recovery (not staged) with a >11 nov date.
Thanks in advance!
---
EDIT: The OTA from DP2 to final 7.1.1 may also work if it's not staged! if someone can, please capture it to help me
Thanks!!!!
Click to expand...
Click to collapse
OP request to close...
THREAD CLOSED
Does anyone have the latest security pacth update from February 1 2019 to download moto g5s?
I've download and installed successfully but the security path is still on feb 2019
And that the bootloader is unlocked and I can not block again because it is not the latest rom
keerthi perumal said:
I've download and installed successfully but the security path is still on feb 2019
Click to expand...
Click to collapse
Yeah, it doesn't do anything except apply so-called "security enhancements" :laugh:
My phone's actually rooted with bootloader unlocked, but I still got the notification for the update. Will it work?
JarlPenguin said:
Yeah, it doesn't do anything except apply so-called "security enhancements" :laugh:
Click to expand...
Click to collapse
Can't understand Moto these days
deivarchangel said:
My phone's actually rooted with bootloader unlocked, but I still got the notification for the update. Will it work?
Click to expand...
Click to collapse
i did it, same thing, bootoader unlocked and normal OTA update, working fine so far
I've got this too and still february patch. Weird releasing an update with no security patch, especially the current one is quite dated.
I updated mine too and it's normal, but I wanted to take it with me and I wanted to block the bootloader, and it's only possible with the latest rom
Maybe this was posted already, but my search skills seem to be failing me at the moment. :silly:
Is there a way to do an in place OTA update from pie to Android 10 Q keeping Magisk root?
Or do I have to do the old way and revert pie, take the OTA, then apply the patched boot.img?
Thanks for any help!
You could revert and take the update or revert and flash Q via fastboot. Either way you'll have to root again after.
Pixel 3 XL, Yep, Crashed It.....
..... Again.
What I usually do is grab the current months image (in this case november), move the boot.img to my device, patch it with Magisk, move it back to my computer. Grab the OTA for the current month, sideload via fastbootd, after successful reboot I just go back into fastboot and flash the patched_boot.img.
Sounds like a lot, but usually takes only a few minutes after the downloads are complete.
In case anyone was wondering, now that Magisk is updated to 20.1, I was able to do an in place OTA upgrade from Android 9 to Android 10 following the Magisk tutorial here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
My laziness paid off and I only waited a couple of months! :laugh:
ilikecl said:
In case anyone was wondering, now that Magisk is updated to 20.1, I was able to do an in place OTA upgrade from Android 9 to Android 10 following the Magisk tutorial here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
My laziness paid off and I only waited a couple of months! :laugh:
Click to expand...
Click to collapse
Has your Pixel taken the January 2020 update yet?
statustray said:
Has your Pixel taken the January 2020 update yet?
Click to expand...
Click to collapse
Yup. Did an in-place OTA upgrade for the Jan 2020 update as well.
ilikecl said:
Yup. Did an in-place OTA upgrade for the Jan 2020 update as well.
Click to expand...
Click to collapse
I'm with vzw, and my device has not listed the January 2020 update. In fact, via OTA, I am on:
Build number: QP1A.191005.007
statustray said:
I'm with vzw, and my device has not listed the January 2020 update. In fact, via OTA, I am on:
Build number: QP1A.191005.007
Click to expand...
Click to collapse
I'm on Visible, which should be the same as VZW.
But I guess maybe Visible doesn't have to go through testing the bloatware that comes on VZW builds before releasing the OTA...?
Dunno.
ilikecl said:
I'm on Visible, which should be the same as VZW.
But I guess maybe Visible doesn't have to go through testing the bloatware that comes on VZW builds before releasing the OTA...?
Dunno.
Click to expand...
Click to collapse
Yeah that very well could be. I'm going to check my better half's phone and see if her has taken a new OTA yet. We're both vzw with google edition phones - my model is Pixel 3 XL, and hers is Pixel (OG).
Thanks.