Database Users

Help! IMEI=0 only 4.2.2 boots no signal

I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.

liquidmetal88 said:
I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
Click to expand...
Click to collapse
try this for reference http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html

But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.

liquidmetal88 said:
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
Click to expand...
Click to collapse
Your IMEI information should be on your box if you still have it. Now there has to be a tutorial out there somewhere to enter IMEI info for your phone. I know I found some stuff when trying to this to a Galaxy S3.... I would keep looking or contact Google for a RMA

Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country

Any Luck yet?
liquidmetal88 said:
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Click to expand...
Click to collapse
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help

sambitshankar said:
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
Click to expand...
Click to collapse
Am also facing this issue...only the 4.2.2 boots with no basebanc versiono no IMEI no. and doesn't detects any Sim card

Unlike Samsung phones, the imei cannot be re-injected into the phone's file system. People have had to return the phone to Google to have it fixed.
If you try to install a stock 4.3 or 4.4 ROM, the phone will not even boot to the desktop.

[Q] Having trouble updating to Lollipop

I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.

SimonP2 said:
I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
Click to expand...
Click to collapse
I would flash the factory image using fastboot to 5.0.1. You'll have to unlock the device again. I'm not a fan of tool kits
Sent from my Nexus 9 using XDA Free mobile app

SimonP2 said:
I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
Click to expand...
Click to collapse
In the toolkit options enable "Force Flash Mode" and try again; this will fastboot flash the img files individually and overcome the issues with Google's new Lollipop factory packs, where the fastboot update cmd, is not working properly (as written in their own incldued flash-all.bat).
In the future.. rather than PM'ing me and making a thread.. just post in the NRT threads.
{{ WugFresh }}

It took a lot of fiddling about and several boot loops but eventually I managed to install 5.0 (using NRT) and it updated to 5.0.1 (which is what I wanted to see to be sure it was working alright before I sell it) so all is well at last. Thanks for the suggestions.

[Q] Quick Question If Someone Has a Moment, Please

I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1

Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk

There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.

bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...

N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help

Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.

Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.

mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?

WARNING - Do not use OTA to get Android N Beta Preview before reading this!

UPDATE: Solution below!
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
UPDATE: Google posted signed OTA zips that can be used to recover from this situation. You can now use adb sideload to side load the full OS in OTA form. Go to https://developer.android.com/preview/download-ota.html to download.

Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.

kalinskym said:
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
Click to expand...
Click to collapse
If you unlock the bootloader and enable USB debugging prior to installing the Android N preview (via OTA), you should be fine. You're essentially leaving yourself a backdoor to flash the factory image should the OTA fails.

Yes, I wish I know this earlier, and now I have a bricked Nexus 9 with me. :sad

Ouch, had that issue and went here looking for help. Should have waited before I tried it ?

THIS IS CRAZY! OTA should work :-\
So crazy to hear that you are all having the same issue with the Android N Developer Preview on Nexus 9!
I have had exactly the same experience today when I enrolled my device for the OTA. It downloaded and started to install fine, but got stuck with the android on his back with the red exclamation mark. It then rebooted and is now stuck on the Google logo. I have tried using adb to push files, factory reset/wipe cache & nexus root toolkit. However, I had NEVER set the OEM unlock option and that seems to have left me stuck!
I'm hoping someone will figure out an amazing fix! Just in case no one does, I called Google and as I purchased it from the play store they have offered me a replacement. Sadly I'm living in Thailand and they can only arrange it to my home country, Australia. So sorry they wouldn't help you Naddie

I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?

sashinde said:
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
Click to expand...
Click to collapse
Gee, I hope we're still on MMB29V... But since the OTA seemed to have failed during the update, the system partition may be partially whatever build this Android N preview is and partially MMB29V - which is to say ... It's completely borked for ANY OTA update to fix it via side loading.
Does anyone even have the OTA zip for MMB29V to N preview for we poor souls to try?
Sent from my iPad using Tapatalk

Hello. Sorry for my english. The same from here. I called Google and they offered me a replacement. I said yes. Waiting for a new Nexus 9. I hope you will find the solution.
Enviado desde mi Nexus 6P mediante Tapatalk

Naddie, have you contacted HTC or Google yet about getting a replacement?

My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.

I tried updating via the beta program, but there was an error and now my Nexus 9 is softbricked. I can get to fastboot and recovery, but can't boot into Android. And, worst of all, I don't have USB debugging enabled, so I can't do an ADB flash or even OEM unlock.
Can anyone help me out?

naddie said:
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
Click to expand...
Click to collapse
Nexus 9 is FAMOUS for OTA's failing and leaving you with a "brick".
The good news is that the sky IS NOT falling, even with the bootloader locked and debugging OFF, you can still recover it. All you need to do is reboot into recovery, and "adb sideload" the update.zip again.
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
greiland said:
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
Click to expand...
Click to collapse
The switch unflips every reboot anyway, so that wouldn't have helped you to begin with.

What "Update" would I sideload? I did my original update via OTA.

Fixed Brick on Nexus 9 OTA Android N update
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !

Good to know. I just signed up for the beta program. My bootloader is unlocked from day one because I always flash the stock image of the security updates. The USB debugging is on
Sent from my Nexus 6 using Tapatalk

inthelandofnod said:
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Click to expand...
Click to collapse
Can you please explain more detailed? Are you sure it's volume up because recovery is volume down. And what to do then in recovery?

Please, give us more info!!!!
Enviado desde mi Nexus 6P mediante Tapatalk

I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?

So this might be resolvable if someone has found the Android N OTA...
srideep said:
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
Click to expand...
Click to collapse
OTAs won't apply if you don't have stock recovery.

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+