Related
From AT&T Website:
Update summary
Effective September 29, 2015, AT&T released a software update for the LG G2 (D800). This update will be made available to customers to download via Firmware Over The Air (FOTA). Wi-Fi is required.
Software update includes
Device security improvements
What to expect after the update
Although there should be no impacts to settings or data, we recommend that you sync or backup your contacts and files to a PC or with AT&T apps.
How to update
Select Menu or pull down the notification shade.
Select All Settings > General.
Select About phone > Software update > Update Now.
If not connected to Wi-Fi, message reads A software update is available for your device that requires Wi-Fi connectivity for download process to begin. Connect to Wi-Fi network? (If already connected, skip and go to step 5)
A new software update from AT&T is available for your device. This software update will take several minutes and will not delete any personal data on your device. All services (including emergency calls) will be suspended during the install.
Tap Continue
Status Message The software has been successfully installed. Your device is now ready to use.
Tap OK.
How to verify the update
From the home screen, press the Menu key, and then tap All settings.
From the "General" tab, scroll to and tap About phone.
Tap Software information.
Your phone's software version information will be displayed.
Android Version: 5.0.2
Baseband version:M8974A-AAAANAZM-1.0.190128
Kernel version: 3.4.0
Build Number: LRX22G
The Software Version: D80030g
Update File size: 17.1MB
http://www.att.com/esupport/article.jsp?sid=KB423381&cv=820
One thing i noted is that phone is much more snappy afterward. maybe it's because of the cache rebuild that every build do or maybe there is some secret ingredient added in this update.
Very surprised to see another update from AT&T for the G2. I wonder if there's any chance of seeing 5.1.1 or 6.0.
Does this mess with root?
Scribe'd on my awesome OG2
4ty-phive said:
Does this mess with root?
Scribe'd on my awesome OG2
Click to expand...
Click to collapse
You can't update with root, at least I haven't been able to.
When updating it will just kick you back to the home screen with a message telling you, you're suspected of rooting and updates are not supported for rooted devices.
I also tried the method discribed in http://forum.xda-developers.com/att-g2/general/links-manually-forcing-ota-20c-to-20u-t2828874 to force an update but I was unable to succeed
I'm waiting for dlpkgfile to update
How does one make this file root friendly? Wouldn't mind taking the time to do this.
Scribe'd on my awesome OG2
chp said:
Very surprised to see another update from AT&T for the G2. I wonder if there's any chance of seeing 5.1.1 or 6.0.
Click to expand...
Click to collapse
i think thats the answer for no 5.1.1 i dont see why leave g2 at lollipop if its has bugs.. since they fix the stagefright on 5.1.1. so we need it 5.1.1 to get rid of this bug but aparently with this update theres no need to update to 5.1.1 but does this still have the memory leak bug?
limpbizkit78 said:
I'm waiting for dlpkgfile to update
Click to expand...
Click to collapse
here is a link to the dlpkgfile from my LG G2, but if you have root you cannot update through either the normal OTA method or by using the root adb command method described in
http://forum.xda-developers.com/att-g2/general/links-manually-forcing-ota-20c-to-20u-t2828874 or at least I could not get it to work
http://d-h.st/6IWx
:good: thanks my friend
gmuller1234 said:
here is a link to the dlpkgfile from my LG G2, but if you have root you cannot update through either the normal OTA method or by using the root adb command method described in
http://forum.xda-developers.com/att-g2/general/links-manually-forcing-ota-20c-to-20u-t2828874 or at least I could not get it to work
http://d-h.st/6IWx
Click to expand...
Click to collapse
gmuller1234 said:
here is a link to the dlpkgfile from my LG G2, but if you have root you cannot update through either the normal OTA method or by using the root adb command method described in
http://forum.xda-developers.com/att-g2/general/links-manually-forcing-ota-20c-to-20u-t2828874 or at least I could not get it to work
http://d-h.st/6IWx
Click to expand...
Click to collapse
I could not get it to work ehiter.
I think that the root adb command method does not work in Lollipop.
Enviado desde mi LG-D800 mediante Tapatalk
Command adb not work
Maybe changed files from cache
The name is recovey mistake
limpbizkit78 said:
:good: thanks my friend
Click to expand...
Click to collapse
No Problem, my pleasure
andresrodolfo said:
I could not get it to work ehiter.
I think that the root adb command method does not work in Lollipop.
Enviado desde mi LG-D800 mediante Tapatalk
Click to expand...
Click to collapse
The last command appears to force a package on the phone to start the update process without (or possibly after) a check for root, however when I run the command the nothing appears to happen making me think that the original Lollipop update(30f) either nerfed the command to prevent this kind of thing from happening, or they replaced the package with a new one for the 5.x iterations of Android. so it is a matter of waiting for people smarter than me to find out how to force the updates in the Lollipop update
TL;DR: yup I agree with you
Is there no way to unroot, install this update and then root again?
Negative
spikyshotgun said:
Is there no way to unroot, install this update and then root again?
Click to expand...
Click to collapse
As far as I know you can't unroot a device. The way I'm doing it is reinstalling the original KK, then going trough the process of updating till the lastest update then rooting again.
I do hope someone could come up with way to install the latest update on rooted.
That did come to my mind but I felt it's just too much of a pain going that far back for a patch!
Can you people provide me the "D80030F" lollipop OTA Package file... i can not download it from any where all links says file is deleted or not available
meshobi said:
Can you people provide me the "D80030F" lollipop OTA Package file... i can not download it from any where all links says file is deleted or not available
Click to expand...
Click to collapse
Update 20y to 30f
https://mega.nz/#!UAcEGAKI!lTcWznZDMs20jeYBzKvtwa6j2MOCPeOVXrx29LNpxVY
30f to 30g
https://mega.nz/#!RB8UVArR!zwooiM32eKlRKN6gsfn9PiCUvF1-1V12l5UZ99ngonE
I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.
No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.
captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?
themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.
Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.
I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper
Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170
I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180
Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...
bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install
Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8
Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks
I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
I had a Moto X 2013 Developer Edition (5.1 with XPosed) that recently died. As a stop gap until I can get something newer and nicer I bought a Droid Mini on Ebay. Here is the information on what it came with:
System version: 19.6.3.obakem_verizon.Verizon.en.US
Android version: 4.4
Baseband version: MSM8960PRO_BP_2323.031.111.00R
Kernel version: 3.4.42-gel1d6506-00006-g9ddacc8 [email protected] #1
Build number: SU2-3.3
It looks like my build number is older than those that seem to block unlocks. I was hoping to find a way to at least get root (get XPosed), and at most unlock the bootloader (flash a newer ROM). I am avoiding all system updates just in case they could ruin my chances of an exploit.
I have enabled loading 'other' applications and disabled verifying apps.
I've tried reading some of the threads here - some talk about loading tools like RockMyMoto onto the device and then using Impactor, but Impactor fails to access using telnet as a system level user. I tried installing PwnMyMoto 1.4.3 but I get certificate parse errors. I may be doing something wrong.
Does anyone know which threads I should be using for my build, or if I can't even do anything? I feel sort of lost. Any help would be appreciated.
ohioDroid said:
I had a Moto X 2013 Developer Edition (5.1 with XPosed) that recently died. As a stop gap until I can get something newer and nicer I bought a Droid Mini on Ebay. Here is the information on what it came with:
System version: 19.6.3.obakem_verizon.Verizon.en.US
Android version: 4.4
Baseband version: MSM8960PRO_BP_2323.031.111.00R
Kernel version: 3.4.42-gel1d6506-00006-g9ddacc8 [email protected] #1
Build number: SU2-3.3
It looks like my build number is older than those that seem to block unlocks. I was hoping to find a way to at least get root (get XPosed), and at most unlock the bootloader (flash a newer ROM). I am avoiding all system updates just in case they could ruin my chances of an exploit.
I have enabled loading 'other' applications and disabled verifying apps.
I've tried reading some of the threads here - some talk about loading tools like RockMyMoto onto the device and then using Impactor, but Impactor fails to access using telnet as a system level user. I tried installing PwnMyMoto 1.4.3 but I get certificate parse errors. I may be doing something wrong.
Does anyone know which threads I should be using for my build, or if I can't even do anything? I feel sort of lost. Any help would be appreciated.
Click to expand...
Click to collapse
Your best bet is Sunshine:
http theroot.ninja
I agree. Sunshine and Kingroot are the ways I rooted and unlocked my Droid Ultra on Android 4.4.4 (SU 4.21)
These are the steps I took:
1 ) I downloaded Kingroot and rooted temporarily with that, since Sunshine does a check to see if you're rooted. I was getting an error with Sunshine as it tried to temp root, but it would just restart the phone and nothing happened. This is the work around I found.
2 ) Downloaded Sunshine and let it do all it's tests that it runs, including the workaround in the previous steps
3 ) Bought the access code for $25. If you think about it, it's worth the $25 since a new phone with a newer OS is far more expensive than $25. Therefore you can keep up with the newest OS through free ROMs
4 ) Let Sunshine do it's thing
5 ) Install TWRP, CWM, or Philz
6 ) Have fun
pbarrette said:
Your best bet is Sunshine:
http theroot.ninja
Click to expand...
Click to collapse
xjewpacabrax said:
I agree. Sunshine and Kingroot are the ways I rooted and unlocked my Droid Ultra on Android 4.4.4 (SU 4.21)
Click to expand...
Click to collapse
I did download Sunshine and ran it through the tests - it says that it can get root and could unlock my phone if I paid. I'm surprised it didn't have in-app purchases - I was going to use Google Play but I guess you have to buy from the developers online or send them an Amazon Gift Card? Or maybe there is a way to use Google Play?
ohioDroid said:
I did download Sunshine and ran it through the tests - it says that it can get root and could unlock my phone if I paid. I'm surprised it didn't have in-app purchases - I was going to use Google Play but I guess you have to buy from the developers online or send them an Amazon Gift Card? Or maybe there is a way to use Google Play?
Click to expand...
Click to collapse
The only way that I am aware of is through the app using a debit/credit card. I wouldn't worry about it too much, since this app has been confirmed by multiple people on a myriad of devices as working and legitimate
If there is another way, hopefully someone else can chime in and let you know.
This has already discussed in other posts here BUT I continue to see A LOT of people waiting for Nougat OTA like Santa Claus should bring to them... (or, even worse, trying to push it in their phones... )
So, I make this post just to give more visibility to all...
I'll try to write it clear...
Don't update your Z to Nougat by OTA!
Is it clear enough? :laugh:
Now some explainations...
Over the the common generic motivations (difficulties when not in full stock conditions, risk to brick it during process, OTAs that are the Evil... ), there is a strong one in this case: Nougat OTA for Moto Z (silently...) upgrades your bootloader too, from v. 90.xx to v. 91.xx...
This isn't really needed (Nougat runs flawlessly on v.90.xx too... ) BUT it introduces some tighter rules on what you can and what you can't anymore boot on it, limiting hacking and upgrading (to developed third part ROMs...) possibilities...
One of this rules is that with v. 91.xx bootloader you can't anymore boot to MM ROM!
Considering that as of today it seems that bootloader can't be donwgraded (some have soft/hard bricked their Z trying to downgrade it...), Nougat upgrade by OTA is a one way process.
If you consider that stock Nougat seems to have some bugs and issues (and, as of today, no Xposed available...!) and that some (all?) third part Nougat ROMs requires "MM" (v. 90.xx) bootloader to work, it seems not to be a great idea leave that Motorola upgrades silently your bootloader...
So?
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
Considering we on the Moto Z droid don't have an unlockable bootloader and/or ability to root I don't see it effecting you negatively, other than an exploit that may be discovered for marshmallow that would allow for root. We are at the mercy of a kind developer taking on the task. I really miss my hotspot without a fee... But I can go back to my Moto X if it is necessary.
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
I agree with dap... proposed solution can't be used since of unlocked bootloader, BUT if I had a Droid I would have remained sticky to first SW release as long as possible because of the higher probabilities of a flaw to hack and root it...
With Nougat and newer (even more "locked"...) bootloader it will be harder...
those are a lot of steps... is there a way to just hide the nag/update screen that pops up? it keeps wanting to update or ask for a time to update or reminds me to update etc
enetec said:
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
Click to expand...
Click to collapse
Does the method you linked to even work with the VZW variant? It looks like it used to, but the Verizon stuff is all marked through and I'm not clear on the process.
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
aatjitra said:
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
Click to expand...
Click to collapse
Hello did you try to get down to MM? Thank you
regards
iron maiden said:
Hello did you try to get down to MM? Thank you
regards
Click to expand...
Click to collapse
No. I didn't.
I read in other thread that bootloader v91 won't work with MM.
Moto Z ( UAE ) no OTA yet
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
yanniclord said:
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
Click to expand...
Click to collapse
You can't. The only thing you *can* do is tap the "Later" and then "Done" buttons. That will defer it for another 24 hours since it automatically fills in the phone's current time for the next check.
It's annoying, but it's only once a day.
EDIT: I thought you were referring to the VZW variant. If you're not and your phone is rooted, you might be able to disable or remove "Motorola Update Services". To do so, go to Settings > Apps > select "Show system" from menu (3 dots at top right) > scroll down and tap "Motorola Update Services"
I can't disable it on my VZW unit, but you might be able to. Or maybe you can remove the app via root (though I have no idea if that will cause further problems).
I too can confirm thr disabling motoservice in settings method. But you have to do it everytime you reboot your phone, it does t hurt me doing that.
I found a simple fix, get Titanium Backup and freeze that crap app, done.
yanniclord said:
I found a simple fix, get Titanium Backup and freeze that crap app, done.
Click to expand...
Click to collapse
There is another way for users with root eventually...
saif_khans said:
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
Click to expand...
Click to collapse
Simply use the method linked in OP. It uses retmx sw.
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
sam564 said:
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
Click to expand...
Click to collapse
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Variants doesn't matter all moto z is using same kernel source (I have Chinese moto z)
Let me explain, I'm trying to port farm-root for moto z
Here's the source : https://github.com/freddierice/farm-root
If anyone knows how to deal with ndk and other Stuffs, can install TWRP with this version of farm-root
But I'm trying to make it easier and here's big barrier called SELinux
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Hope it happens. The phone (accidentally?) Downloaded the update and is now asking to install. I'm afraid one day it'll just automatically update on it's own.. I can't seem to find where the system update got downloaded to, otherwise I'd delete it
Does anyone know how to root? Till yet ?
Today IT was my Christmas.present
Thanks
Daniel
No source from motorola, nor updates yet.
Hello you can root your moto with magisk.
Mounib BOULAABI said:
Hello you can root your moto with magisk.
Click to expand...
Click to collapse
If you have a copy of the boot.img
Sent from my mata using XDA Labs
Thanks by the way. I found i way to root my Device.
Please do tell, how?
Danieldergrosse said:
Thanks by the way. I found i way to root my Device.
Click to expand...
Click to collapse
Would you mind sharing your way to root your device? Every piece of knowledge can help other users here on XDA.
Sent from my Moto G5 Plus using XDA Labs
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Danieldergrosse said:
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Click to expand...
Click to collapse
*
your link seems dead or not correct. - edit: link correct, was not working due to my vpn...
I assume he patched a G8+ boot.img with magisk manager.
boot image can be extracted from official Doha firmware found here: https://mirrors.lolinet.com/firmware/moto/doha/official/
manual on how to do this can be found on official magisk manager website.
be aware that when unlocking bootloader your phone will reset to factory settings.
This is what I did. Yes..
Worked great for my G8+. I guess people should just check which stock ROM file they get from lolinet to make sure it's the right one. I say that because, in my case, lolinet list had two files for the Brazilian stock ROM. I went to Settings / About / Version number and downloaded the matching file. Don't know whether the other file would work the same or not. Just didn't want to risk having any issue since G8+ is somewhat new and there's not much info on solving root problems on the Internet.
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
carl.13 said:
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
Click to expand...
Click to collapse
Hello, Carl. I guess it's not possible unless there's a flaw in the security. There are some articles on the Internet about that. Google "is-there-a-way-to-root-an-android-phone-without-unlocking-the-bootloader". I can't post URLs yet.
As for Motorola devices, I was able to unlock the bootloader without problems on my G8+, last week. The only caveat, I'm my case, is that I had to wait some days for the unlock bootloader option be available under developer options. It was disabled by default in my G8+. And, yes, they're releasing bootloader unlocking codes.
THANKS!
Have anybody with a rooted device tried to get wide angle camera working in gcam ports?
Thanks.
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
esrd43 said:
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
Click to expand...
Click to collapse
magisk module debloater and also sdmaid helped with most of the bloatware, the only thing I could not remove was google files but I just deactivated it.
a really weird thing happened with the April 1st update, basically the update started automatically and it failed at 3/6 so I tought I should restart my phone and test it again, but it got stuck in bootloop and I had to reflash a rom with fastboot cmd.
I think that's because I unlocked the bootloader and rooted my phone, cause u lose the right for updates after you do that, but for some reason lenovo/moto update system goes automatically the next second u connect to the internet and fails halfway thru so u have a higher chance to ruin your phone or something, instead of denying the update from the start
so the solution I found was to try and delete "moto update service" app that I can't force stop or disable but I couldnt find it in system/app or system/priv-app, that's because the app name is "3c_ota", so deleting that with SD Maid app worked and the "update system" option in settings is reverted to a sort of default android one that lets you check manually.
Had a similiar issue. I soft bricked my phone (bootloop) and installed a stock rom from an unofficial source. The funny thing is, this version did make like 3 or 4 system upgrades to PPSI.29.65-51 without any issue. But the 1st April updated failed to install. I then flashed the official 1st april stock image with the moto rescue and smart assistant. After that, the official ROM tells me my phone is not allowed to do updates because the security of this phone is compromised and I should contact lenovo support
Those upates are kinda annoying if they don't work, I guess I'll just completey flash the phone every 6-12 months with the moto assistant.
yeah you should always have a backup rom that you can download with moto assistant or from lolinet g8 roms (https://mirrors.lolinet.com/firmware/moto/doha/official/)
I also got the same message saying that my phone is compromised ( unlocked bootloader + rooted) and it won't receive any further updates, but I just deleted the "3c_ota" app (the moto update service) which is bad cause if forces automatic updates the second u connect to internet.
I'm not going to touch any further updates or security patches until android 10, which I will attempt to flash via moto assistant