Nexus 6P angler Feb update which one to chose? - Nexus 6P Q&A, Help & Troubleshooting

Nexus 6P angler Feb update which one to chose?
I am currently on Nexus 6P
8.1.0 (OPM3.171019.013, Jan 2018)
I see 41 MB update. Since my device is rooted therefore I cannot directly update OTA being notified.
However i see on googles developer images that there are two images :
8.1.0 (OPM3.171019.014, Feb 2018) And
8.1.0 (OPM5.171019.015, Feb 2018)
Which one I should update from my current build.
Also any ways to successfully update on rooted Nexus 6P without wiping data?
Kindly help
Thanks in advance

sunandoghosh said:
Nexus 6P angler Feb update which one to chose?
I am currently on Nexus 6P
8.1.0 (OPM3.171019.013, Jan 2018)
I see 41 MB update. Since my device is rooted therefore I cannot directly update OTA being notified.
However i see on googles developer images that there are two images :
8.1.0 (OPM3.171019.014, Feb 2018) And
8.1.0 (OPM5.171019.015, Feb 2018)
Which one I should update from my current build.
Also any ways to successfully update on rooted Nexus 6P without wiping data?
Kindly help
Thanks in advance
Click to expand...
Click to collapse
I flashed OPM5 and everything is working fine..if you dont want to lose data unzip factory image and flash manually system, vendor and boot.img..no need for radio and bl because they are the same as january...

Since you are currently on OPM3, I would go with OPM3.171019.014. That's what I used and all is good. As far as updating without wiping data, you can also flash the full factory image using Flashfire - as long as you're not rooted with Magisk.

newkydawg said:
Since you are currently on OPM3, I would go with OPM3.171019.014. That's what I used and all is good. As far as updating without wiping data, you can also flash the full factory image using Flashfire - as long as you're not rooted with Magisk.
Click to expand...
Click to collapse
Thank you for your help. I am unfortunatelty rooted with magisk.

Related

No OTA since Dec

I can't seem to get the OTA security updates. Maybe this is my problem. My build number is NMF26F which is for everything but Verizon. The build I should have is 7.1.1 (NUF26K, Feb 2017, Verizon Only). How should I correct?
Sideload the OTA image via the instructions here...
https://developers.google.com/android/ota

New Project Fi 6P stuck on MM 6.0.1 and Dec. 1, 2015 security patch

Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Chavezlaw93 said:
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Click to expand...
Click to collapse
Hello,
I would just sideload latest 7.1.2 N2G47H OTA from Google here: https://developers.google.com/android/ota
There is an easy tutorial explaining the process. If you're not sure, let me know...
Otherwise you can wait till you have an update notification. Though there's no time frame as to when it will come to you.
Good luck...
Chavezlaw93 said:
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Click to expand...
Click to collapse
I agree with @5.1. The fastest, least hassle-free way to get to 7.1.2 is to just flash the full April image. You could also try borrowing a SIM from somebody on a different network and popping that in. Let the phone start up and wait for their cellular network to be displayed in the notification bar. Then power down and put your SIM back in. Works, but you are liable to set yourself up for a series of updates. I would also recommend you leave your bootloader unlocked and USB debugging enabled.
5.1 said:
Hello,
I would just sideload latest 7.1.2 N2G47H OTA from Google here: https://developers.google.com/android/ota
There is an easy tutorial explaining the process. If you're not sure, let me know...
Otherwise you can wait till you have an update notification. Though there's no time frame as to when it will come to you.
Good luck...
Click to expand...
Click to collapse
Hi! New to the 6p (completely) but not to flashing/mods/etc. Can this be flashed with TWRP or only via ADB? Anything I should be aware of on an unlocked/rooted nexus w/ProjectFi? Assume I will have to re-root - is this correct?
Thanks!

No SIM After 8.0 update

I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
idbl_fanatic said:
I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
Click to expand...
Click to collapse
Did you try an older radio.img, some people use the boot.img from the previews. If You check the thread search from any Oreo thread you'll see you're not alone.
I believe if you flash boot.img from developer preview 4 can fix this issue.
Exodusche said:
I believe if you flash boot.img from developer preview 4 can fix this issue.
Click to expand...
Click to collapse
Where might one obtain this?
idbl_fanatic said:
I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
Click to expand...
Click to collapse
It might not be anything you did, when I installed the OTA for september and Oreo update I also got a no sim message a few times. Completely stock / unrooted phone. I restarted and it went away but popped up once since. This phone is brand new (just got it as a 6P replacement through a google store RMA) so I know my phone hasn't been messed with, I think they might have a bug in the build. You on projectFi by any chance?
Bounty44 said:
You on projectFi by any chance?
Click to expand...
Click to collapse
No, I am on AT&T
idbl_fanatic said:
No, I am on AT&T
Click to expand...
Click to collapse
Ah alright. Well I just wanted you to know you aren't alone at least lol. Hopefully the october update will include some fixes.

Unroot and Flash OTA update

i have my Mi a1 rooted with Twrp 3.1.1 with Magisk on november 6 2017 security patch , How do i flash ota update after i unroot my phone please help.
It won't be possible, since you flashed TWRP... System should be completely unmodified. Only method I know to get ota from your point is to clean flash newest stock image. And after that I would recommend to flash magisk only, without any Custom recovery.
lmfao009 said:
It won't be possible, since you flashed TWRP... System should be completely unmodified. Only method I know to get ota from your point is to clean flash newest stock image. And after that I would recommend to flash magisk only, without any Custom recovery.
Click to expand...
Click to collapse
how do i do it without losing my data can you pls explain im kinda noobi
Here's the link http://en.miui.com/download-333.html
The latest oficial ROM is oreo January security patch. You need flash manually and wait for february security patch.
Code:
ltf_195 said:
Here's the link
The latest oficial ROM is oreo January security patch. You need flash manually and wait for february security patch.
Click to expand...
Click to collapse
but This will be a Direct update from November 6 17 patch to January Update , wont it brick my phone ?
Kamran47 said:
Code:
but This will be a Direct update from November 6 17 patch to January Update , wont it brick my phone ?
Click to expand...
Click to collapse
Hi, did you flashed the stock rom?
Did you have any issue about the phone was rooted before flashing?
Thank you.
If you are in India , you can go to xiaomi service centre & ask for re-flashing the full software which will automatically unroot your phone & you can install ota updates . They will charge Rs 180 for it

no OTA updates for a long time !

hi everyone,
since i side loaded Android 8.1 image i didint receive any security update! i check for updates regularly but there is no updates !
what should i do ?
fully stock locked bootloader.
lastest patch 5 january.
I just bought another nexus 6p( was enrolled into beta program ). I did flash the latest image from google, and yeah, seems like the last ota security patch is from january. Can someone confirm this ? I forgot to look at my last nexus 6p.
Latest sec Update february 5th here...but flashed myself due to unlocked and rooted...
I updated to Oreo OTA on Sunday. Have February security patch installed.
Sent from my Nexus 6P using Tapatalk
do you guyes know to to downgrade to 8.0??
i've manually flashed all the missing updates i think its the only way.
Yeah, something about the beta program of 8.1 froze updates at the January security patch for me as well.
I ended up dirty flashing the release 8.1 system image and everything works fine now, still don't get OTA update notifications though.
A few days ago, I did get the march 5 security update, after flashing this image 8.1.0 (OPM3.171019.016, Mar 2018) from google .
after flashing all the missing updates , OTA updates started to roll out as normal to me

Categories

Resources