DP2 7.1.1 update weirdness - Nexus 6P Q&A, Help & Troubleshooting

I want to ask a few things, I'm trying to get this phone all working on the latest things and I can't seem to find concrete answers for why its not working when searching around.
So the first issue is that I'm stuck on 7.0. I enrolled in the beta program and all, but it starts to try to download the update and then suddenly kicks off and goes 'you are up to date' even though I've still only got 7.0. What does that mean? I'm not sure what I'm doing wrong.
Second, I really, really want to use the google assistant. If I do this OTA update will I be unable to root the phone. If I root the phone, can I update to the final release of 7.1 when it comes out in december? And, as I am unfamiliar with this sort of thing, if I change the build.prop to be of a Pixel so I can use google assistant, will that adversely affect anything else on the phone?
Do I even use the OTA update method when I root the phone with TWRP or do I now have to flash things manually?

Related

SM-G870A Failing to Update Past 4.4.2

Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.

My 6P WILL NOT update to 7.0

Long story short, my Nexus 6P will not update to 7.0. I just got the OTA update notification today but when I downloaded it and waited forever for it to optimize my apps, my phone boots into 6.0.1. I tried getting 7.0 from the android developer program about a month ago and I was able to download it then too, but again, the phone just goes back to 6.0.1 for some reason. I decided to just wait until I get the OTA but the problem has still persisted. Any ideas on why its stuck on 6.0.1? Any way to fix this?
Also, I bought this phone about 1 and a half months ago used from eBay. It has been working perfectly fine. Just wanted to put that info out there.
It's possible you bought the phone rooted and/or with a custom ROM or recovery? If you aren't completely stock, an OTA update will fail. This isn't necessarily a single 'right' answer question, but you should probably flash the factory image for a completely fresh install. Grab the factory image at https://dl.google.com/dl/android/aosp/angler-nrd90u-factory-7c9b6a2b.zip and follow the guide, section 14 at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and you should be able to update.
I just got the 7.0 OTA myself completely stock and when it rebooted it's still on 6.0.
Nobody else is having this problem?
I think you've both misread the update info. I received MTC20L update yesterday, which said that it contains September security patches and also prepares the device for Android 7.0.
The update never claimed that your device will update to Android 7.0. But don't worry, we'll get it soon, at least I hope so!
MTC20L is the Aug security update and the factory image has been posted for 1.5 months, so odd that you're getting it now. Most people would have been receiving N OTA updates. The only way for us to guess what is going on with the OP is if he edits it to include the build number.
I also just got MTC20L yesterday.6.0.1. No idea why no 7.0. Waiting sucks..........It's been a month since "rollout".
It's true I didn't read what the update was yesterday, but I'm 95% sure it had something with "7.0" on there. How do I know what I installed yesterday? I'm on 6.0.1, with the Sept 6 security patch, and MTC20L.
MTC20F was the August update, MTC20L is September one, released 6.9.
I took the developer preview (mistake as it was a hassle that I had to fix) but remember guys, Android N updates in the background, so while it reboots to update, it doesn't take forever with the whole "android is upgrading" screen. I got the NRD90T OTA yesterday (wierd because the NRD90U is on the webpage) and later in the day I gave it a reboot just the set it straight again. I forget the actual wording but there is a secondary partition for updates so they do it in the background, and then revert back after a reboot.

How to OTA update from 6.0.1 with "modified software" (rooted) to Nougat?

So I've been using 6.0.1 since I got this phone last year. I rooted it pretty much immediately, but then Samsung pushed out one of their security patches, which basically "bricked" the software. Whenever I try to update the phone, I get a fine:
The operating system on your device has been modified in an unauthorized way. Try downloading software updates using Smart Switch on your computer or visit a customer service center
Click to expand...
Click to collapse
Basically I rooted my phone, so OTA updates aren't available.
Apparently the new Nougat update is now live in Denmark, so I really want to update my phone, but I don't want to lose my apps, documents, images, and so on. I basically want to do an update, just like I never rooted my phone. I don't care about keeping my root.
How do I go on about this? I just want to "remove my root" and do an OTA update to get Nougat the most legit way possible.
Thanks!
EDIT: I should probably also say, that when I open SuperSU, I get a:
There is no SU binary installed, and SuperSU cannot install it. This is a problem
Click to expand...
Click to collapse
Since that security update from Samsung last summer, my root magically disappeared, but it's still there apparently.

Unable to update 6P

Last ota update is from Nov. 2017 Update keeps saying phone is up to date. Google is no help. They have told me that they don't know why my phone won't update. I am on Google fi. Been told by others that I just need to sideload the latest update and it might kickstart the phone into accepting ota updates. Never done this so am concerned about mucking up my stock phone.
Anyone have any suggestions?
Was the phone in the Beta program? If so, that ended for the 6P as it isn't part of Android P beta and you won't get any further updates, even by coming out of the beta program.
Sideloading the OTA should fix it and you can do it without losing any app and personal data.
Link with OTA's and instructions from Google is at https://developers.google.com/android/ota
Nope, no beta program.
Still trying to decide if it is worth the risk for me to try the sideload......

Downgrade question - possible upgrade upon restart?

Hey all,
I am very much willing to wipe my phone to do a downgrade.
I have the OP8 Pro, unrooted (never rooted/never unlocked bootloader).
The scenario I see is - I downgrade my phone to 10.15.13 (I have the INAA modell). I'm sure at some point the phone will check for an OTA.
My question - Is it all possible for the phone to upgrade itself if it restarts?
Meaning, is there a time limit that the update is sitting in the queue waiting for the user to press reboot to install? Or can I just somehow figure out a way to silence the system notification of an update pending?
Not sure if that makes sense but my hope is to just go back to 10 and enjoy certain things that just worked out better for me unrooted vs 11 unrooted until some things are ironed out.
Thanks for your time.
No you would need to initialise the upgrade, unless you have automatic updates on.
You would have seen the initial installation begin.
Least that's my experience of it. The update is stored on the phone so you may also be able to delete it.
Turn off automatically download updates.
I downgraded using the special firmware I found (couldn't find official to do it ) and then installed the official EU/UK firmware straight after with no problem
dladz said:
No you would need to initialise the upgrade, unless you have automatic updates on.
You would have seen the initial installation begin.
Least that's my experience of it. The update is stored on the phone so you may also be able to delete it.
Turn off automatically download updates.
Click to expand...
Click to collapse
Thanks for that, much appreciated
Shipoftheline said:
I downgraded using the special firmware I found (couldn't find official to do it ) and then installed the official EU/UK firmware straight after with no problem
Click to expand...
Click to collapse
Nice - noted. I think I can start my search as well. Looking to do this tonight.

Categories

Resources