Database Users

Bell 6P not updating past 7.0

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 did a factory reset while on the Nougat beta

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.

Help me to prevent digitizer locking on my third PH-1

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+

Help Needed - Pixel 4 - No WiFi+Data after update

Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.

Did u solve this?

Question [Question] New phone 1, unable to communicate with Google servers

I received by nothing phone 1 via beta membership (I'm in the US) and for some reason it refuses to communicate with Google servers. Whether during initial setup, trying to add a Google account, or trying to access the Play Store I am always faced with the error: There was a problem communicating with Google servers. Please try again later. I also am unable to check for updates. I get the error message: Updates are temporarily unavailable. Try again later.
I've tried two different SIMs/carriers, and three different known working WiFi networks. I did notice my phone is running Spacewar-S1.1-220813-1608EEA which implies is it's running the European firmware. Could this be what is causing the issue? Do I need to cross flash? I checked downdetector and Google doesn't appear to be having server issues at the moment. Any help or suggestions are greatly appreciated. Thanks!

wwwryan said:
I received by nothing phone 1 via beta membership (I'm in the US) and for some reason it refuses to communicate with Google servers. Whether during initial setup, trying to add a Google account, or trying to access the Play Store I am always faced with the error: There was a problem communicating with Google servers. Please try again later. I also am unable to check for updates. I get the error message: Updates are temporarily unavailable. Try again later.
I've tried two different SIMs/carriers, and three different known working WiFi networks. I did notice my phone is running Spacewar-S1.1-220813-1608EEA which implies is it's running the European firmware. Could this be what is causing the issue? Do I need to cross flash? I checked downdetector and Google doesn't appear to be having server issues at the moment. Any help or suggestions are greatly appreciated. Thanks!
Click to expand...
Click to collapse
For some reason when the sim card is inserted, it cannot connect to Google Update servers.
These are the steps I took to get my beta version working:
1. Removed sim card, factory reset, and followed the startup instructions with wi-fi only !important!.
2. After start up is complete check for updates and you should be able to connect to Google Servers/play store and download/update.
3. Then, after updates, you can shut down and insert your sim, and turn on. You can still access the Google Play store as normal, but the OS updates are still buggy.
I still have to figure out how to update with a new release is out.

Who-Lep said:
For some reason when the sim card is inserted, it cannot connect to Google Update servers.
These are the steps I took to get my beta version working:
1. Removed sim card, factory reset, and followed the startup instructions with wi-fi only !important!.
2. After start up is complete check for updates and you should be able to connect to Google Servers/play store and download/update.
3. Then, after updates, you can shut down and insert your sim, and turn on. You can still access the Google Play store as normal, but the OS updates are still buggy.
I still have to figure out how to update with a new release is out.
Click to expand...
Click to collapse
Thank you for your reply. I did just manually update to 1.1.1 via sideload. If on device OTA updates are buggy that is not a big deal. I don't mind manually updating as this phone is mostly just a test/play device and not my daily driver.
I will attempt the steps you mentioned and setup with WiFi only with no SIM card installed and see if that helps. Thanks again!
Random side question: Are you running 1.1.x latest or 1.5.x? If 1.5.x, is it worth upgrading for Android 13 or is it more buggy? Thanks!

@Who-Lep thank you so much, that indeed fixed the issue. Once I factory reset and completed all setup without any SIM card inserted communicating with Google servers worked correctly. Much appreciated!

wwwryan said:
@Who-Lep thank you so much, that indeed fixed the issue. Once I factory reset and completed all setup without any SIM card inserted communicating with Google servers worked correctly. Much appreciated!
Click to expand...
Click to collapse
Awesome, no problem, glad it worked out!
I went straight through all the updates to the latest beta 1.5.1 Beta 2, so I can't really compare but, no major bugs on newest release, only had to reboot once because of UI glitch and hasn't happen again.