So about a year ago, I did a factory reset while on the last beta, about a month before the final release was pushed out to everyone. I was properly enrolled in the beta program, so I didn't flash it myself.
After the reset, I was still on the beta but once the update was pushed out, I never received it. Manually checking for updates didn't find anything.
Security patch level: 12/1/2016
Baseband: 4ZPLN
My kernel version is is from "Fri Dec 23" which I'm assuming is 2016?
I have a Mac on High Sierra and I tried using Smart Switch but it would not find my phone. It would tell me to unplug the phone and try again, but I still got the same message.
What are my options now, since it has been a whole year like this. I put up with being on older software for all this time but now I think I've definitely pushed my luck with security patches, as well as getting the full features from Sprint in regards to optimization.
How do I get myself back up to speed? I'm already on 7.0, as I mentioned, so I'm hoping whatever needs to be done won't require a clean wipe.
PS, I took a look at my Samsung Members app and Samsung account and it had two devices listed as tied to my account. I think it's the same device, my S7, but one that has a check mark next to it was "last accessed" on the day I performed the factory reset, last January. The second one was last accessed currently, so I'm assuming it's the same device but Samsung sees it as two different devices.
Related
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.
First thing this morning, my phone insisted on a password instead of fingerprint for "first attempt after restart". But the Status page shows that the phone has been running for more than 600 hours, and I'm still on API2, Sept. 1 security update. But the Update page has a greyed-out "Continue update". When I click on Software Update, it says up-to-date and tells me as usual that I have to wait a few hours to check again (until 24 hours after my last manual attempt, which also said up-to-date).
The Continue Update is typically greyed out when an update hasn't already been downloaded, so you probably didn't have a failed update. I'm just getting a little upset that the October update is taking so long. Just saw this morning that the Nexus phones are already getting their November update...
Gary02468 said:
First thing this morning, my phone insisted on a password instead of fingerprint for "first attempt after restart". But the Status page shows that the phone has been running for more than 600 hours, and I'm still on API2, Sept. 1 security update. But the Update page has a greyed-out "Continue update". When I click on Software Update, it says up-to-date and tells me as usual that I have to wait a few hours to check again (until 24 hours after my last manual attempt, which also said up-to-date).
Click to expand...
Click to collapse
My device started the update this morning, it ran in around 253mb, so I would guess its a minor update. I haven't let it finish, I want to give the 935U a run
Got it now:
http://forum.xda-developers.com/att-s7-edge/how-to/g935aucu4apj4-oct-1-2016-security-update-t3496395
I got the update. They sneaked in Fullscreen app.
I manually checked for the update and got it just now. It's so irritating that ATT takes so long to release these updates to us!
Hurricane Andrew said:
The Continue Update is typically greyed out when an update hasn't already been downloaded, so you probably didn't have a failed update. I'm just getting a little upset that the October update is taking so long. Just saw this morning that the Nexus phones are already getting their November update...
Click to expand...
Click to collapse
Over 200MB ... should be more then just security update. Security update is usually something around 40-60MB
norbarb said:
Over 200MB ... should be more then just security update. Security update is usually something around 40-60MB
Click to expand...
Click to collapse
Yup, I got it yesterday afternoon as well. I noticed they finally removed the deprecated Milk Music app as well.
Here is the current update: Android 6.0.1 Marshmallow
The details
Release date: November 8, 2016
Android version: 6.0.1
Security patch level (SPL): October 1, 2016
Baseband version: G935AUCU4APJ4
Kernel version: 3.18.20-9439621
Build number: MMB29M. G935AUCS4APJ4
File size: 285MB
The updates
What's new: Full Screen – Mobile Video Service and Android device security enhancements
What's changing: Improved volume for Enhanced Push To Talk (ePTT) and fix for calls failing to go to Voice Mail when calling non LTE devices
What's going: Milk Music
Via AT&T
All they put in the update was the Full screen App which can be disabled with Package Uninstaller
I have a Bell Canada Nexus 6P running Android 7.0 and it tells me that there are no updates available when we're already past 7.1 to 7.11. This is a work phone, so installing custom ROMs won't be acceptable, but I do want it up to date (otherwise I would have gotten a Samsung ). Any suggestions as to what might be wrong?
I have recently gone through 2 full resets, one when I came off the developer beta stream for hardware troubleshooting and one when encryption failed and I would really not want to go through that again.
I checked my work policies and while they want me up to date, developer beta channel is frowned upon. As well, coming off the beta program was painful as none of my apps or settings were remembered. So I'd like to avoid that route.
Thanks
Peter
Is there a problem unlocking the device , flashing the full factory image and relocking the device?
That would be the easiest and simplest route in my opinion.
peliopoulos said:
I have a Bell Canada Nexus 6P running Android 7.0 and it tells me that there are no updates available when we're already past 7.1 to 7.11. This is a work phone, so installing custom ROMs won't be acceptable, but I do want it up to date (otherwise I would have gotten a Samsung ). Any suggestions as to what might be wrong?
I have recently gone through 2 full resets, one when I came off the developer beta stream for hardware troubleshooting and one when encryption failed and I would really not want to go through that again.
I checked my work policies and while they want me up to date, developer beta channel is frowned upon. As well, coming off the beta program was painful as none of my apps or settings were remembered. So I'd like to avoid that route.
Thanks
Peter
Click to expand...
Click to collapse
Enable "USB Debugging" in Developer Options then boot into stock recovery and ADB sideload the December 7.1.1 OTA image:
https://developers.google.com/android/ota
Sent from my Nexus 5X using Tapatalk
Thanks for the suggestions:
@ibsk8: Unlocking, flashing and relocking is something I have tried before but the monitoring software detected it (different phone but don't want to risk red flags)
@SlimSnoopOS Great suggestion, but I was reluctant to reset my phone again...
...however, I didn't get much choice but to reset as I got another decryption error with the only choice being to factory reset. After the reset, I was able to upgrade to 7.1.1 OTA
Thanks!
Peter
I considered posting on the main question thread, but I am requesting a comprehensive response and therefore feel a standalone post was warranted.
I am on my third PH-1 and am now scared of touching it. I need your help.
Here is my background: I received my first PH-1 in October 2018; I used it stock with a Verizon sim card and had no intention of rooting it or doing anything custom. A nice solid phone. Then, at the start of November, it rebooted and the digitizer froze out of nowhere. I knew that it had recently ran a System Update to Pie that had been prompted (apparently an OTA update). I got it to unfreeze via Safe Mode. Then it soon rebooted again out of nowhere and the digitizer froze a second time; completely unresponsive. I did another couple reboots and it unfroze, then froze a third and final time that evening. I thought it was my fault; that some app I loaded from the store killed the phone. I contacted essential support; I erased the phone via the factory reset, but the digitizer did not respond. Essential warranty replaced the phone.
I received my second phone at the end of November. I did not check what version or anything and like a good user, I ran the prompted System Update (to Pie) and reduced the number of apps I installed to the bare minimum. At the end of that week, the digitizer on this new second phone ceased working immediately after a reboot. I got it to come back two more times (again), but it eventually froze just like the first one. Essential support explained that this may be due to not having the correct kernel updated on my phone prior to accepting the OTA update. Essential warranty replaced the second phone.
I now hold in my hands the third Essential phone.
It is 7.1.1, Kernel 4.4.21-perf+
System Update keeps prompting me to download and install PPR1.181005.099
I am technically proficient, however am new to rooting and updating Essential phone firmware.
As I understand it, I need to get to the latest kernel version before I can update the Android version, as updating to the latest Android would again disable the digitizer.
How do I do that?
I have done the following so far:
Read through this guide: https://mata.readthedocs.io/en/latest/
Read through this firmware dump post: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Own a Windows 10 machine
Purchased a non-stock USB C cable - Monoprice Essentials USB Type C to USB-A 2.0 Cable - 480Mbps, 3A, 26AWG, Black, 0.5m (1.6ft) #27932 https://www.monoprice.com/product?p_id=27932
Installed Essential-PH1-WindowsDrivers.exe
Unpacked platform-tools_r28.0.1-windows.zip
Charged my phone
Activated developer options
Enabled OEM Unlocking
Disabled automatic updates (system and apps)
I am completely lost as to what my next step(s) need to be and I truly would appreciate being walked through this. At worst, I just want to disable the prompt to run a System Update and then survive like a Neanderthal on Nougat.
Can someone please help. Thank you.
Of note, I actually fear for new, non technical, PH-1 owners who, upon receiving phones during the window I also received mine, have had their digitizers fail. So far, I feel alone as the only one with this problem.
I am also prompted to update Essential Services and Essential Resources from Google Play Store, but I am hesitant to do so.
This is the thing.. Unless you want to root your phone and or flash custom roms? Don't do anything but take the friggin OTA. Period, The second you unlock your bootloader and start messing with stuff it becomes your brick and not Essential's problem. That's my two cents bud.
Sent from my mata using XDA Labs
JayLosh said:
.
It is 7.1.1, Kernel 4.4.21-perf+
System Update keeps prompting me to download and install PPR1.181005.099
Click to expand...
Click to collapse
I got my ph1 (halo grey) in Sep 2018, from Amazon during sale period, it came with 7.1.1 installed, I immediately took all updates (incl Essential ones from Play store) & am now on Android 9 build you list above & dec security patch. No problems with digitizer, but I've not rooted this phone or unlocked BL, as yet. No problems with digitizer. This doesn't seem like a common problem (not that I've read all the older posts) so maybe it is due to some other mod or app on your phone, though not sure what kernal my phone come with, now its 4.4.162-perf+
I have been an XDA member/ reader for over 10 years but this is the first time I think I have ever asked a question.
I have a Tab A 510 WiFi that I rooted back in Dec 2019. Since then I have done no other updates except to my installed apps. I want to basically unroot it and install updates that are desperately needed. I then want to reroot it correctly. Plus install a Android ROM that is a much newer version. When I originally rooted, I am pretty sure I didn't get the process correctly done. I have been running it with TWRP, and MAGISK, installed but I am pretty sure I didn't use the correct kernel or build. The tablet has been slowly loosing app compatibility with newer apps. I really just want to start fresh. I also want to remove system apps that are unneeded.
Is the best way to just reset the device, then let it update to the most current security and Android version then reroot it? I have rooted multiple devices in the past but for some reason on this tab A, I have been intimidated by kernel versions and build numbers so I have just ignored any OS updates and have kept the option in settings to automatically update turned off. And have really done nothing with TWRP. I am pretty sure the version is way out of date on my tablet.
Will resetting, updating to correct build and kernel and then rerooting following the directions posted work still? I just want to make sure that what I end up with is an updated and easier to manage tablet. I know how to unlock bootloader, and how to use Odin. And can follow the instructions for in the forum for rerooting. But, I have not been able to find this question answered anywhere in the Tab A forums.
Any advice would be appreciated.
Thank you
The build numbers I have is *** treble_a64_bvS-userdebug 10 QQ2A.200305.003 200314 test-keys**** my kernel is ****4.4.111# 2 Sun Mar 1 15:16:12 PST 2020 and my security patch level is from November 1, 2019. And serial number is *** R52MA0ZH01R****hope that is enough information to at least show how out of date the system is.