Database Develop

unable to install January security path update

I updated my moto x4 from Oreo to pie using flash using boot loader. my boot loader is still locked and software status is official too. It still is unable to update to January security update. Please help !!

yes I have also facing same issue... i have also try by safe mode but shows something not right .... reconnecting to server... might be Moto update Services try to connect moto server which has not able to connect due some issue in server... hope so this is issue...
you can connect to moto support team let me know what they are say for this issue.

They told to reset and try again.. to do that I got to backup my data which LL take time.. so on hold as of now

Yup, same here. I got the Android 1 Google Fi model (Bootloader unlocked, unrooted). I'll try again in a week and see if it resolves itself.

And another ~ bought 2, mine showed the update 3 days before my wife's but won't start (download and install now, via wifi only and it reverts back to the settings screen). She got the notification last night and it took first try. First time I've had this issue in the 4 months I've had the phone, just glad I'm not alone here....

Since you're official/fully stock, there's not really any alternatives besides factory reset or await for full image is available to manually flash via fastboot method. You do not need to unlock long as you stick with motorola firmwares. Links in FAQs thread.

Nothing new here? Mine keeps nagging me to do the update, start it and it shows getting to 17% on step 3 of 6, then just kicks me back out to the setting screen.
This is my first android phone (from a flip), couldn't get lineageos to work with my provider (RedPocket) and have neutered as much of the google crap as possible. Right on down to disabling all permissions for Play Store. Could that be part of my issue?

It has been nagging me since last few weeks, no solution apparently

New Update:
Could actually able to fix the issue by installing a vpn and set it as a USA based server.
My phone was bought in US and I was using it elsewhere. After using an USA based IP it downloaded the update and voila.

Youtube Vanced not sending notifications, can't install older versions

Hello everyone!
I have an issue which is driving me crazy. I'm not getting notifications from Youtube Vanced on my Note 9 SM-N960F (Oreo december patch). I tried everything basically, every notification setting is on, and nothing. I came across a solution which seemed to work for other people, but for me it's not working. It said to install Youtube Vanced 13.10.55 first, and then update to 13.50.52. For some reason, when I tried to install that older version, my phone said "Application not installed." every time. I also tried with other versions, and it refuses to install any other than the latest version. Same with microG. What could be causing both of my problems and how could I fix them?

Did you remove the previous version?

Rog Phone 2 Issues

I have encountered several bugs with the Rog Phone 2
First of all I am unable to create a Google account with Mobile Data. Everytime I try to create an account, I get the message: "There was a problem communicating with Google servers". However, with WiFi it works just fine
The second issue is that my LED notification light does not seem to flash when I get a text message or any kind of notification. The only time the LED is on is when the phone is charging (amber colour) or when battery is low (flashes red)
The third issue I am facing is that YouTube sometimes will not load with mobile data. I have to first open YouTube with WiFi, then, and only then will it load/open with mobile data. If I don't use YouTube for around 2 hours, the same thing happens again, I need to open it with WiFi first and only then it will open with mobile Data.
Last and final issue is that I have the old software with the July 2019 security patch. When I spoke to ASUS Chat on the phone, they told me to download the new firmware from their website. I downloaded the firmware and attempted to flash it via placing the room in the "Root" folder and restarting the phone. When I restarted the phone, on the too left corner of the screen it said there was a software update available (the Rom which I downloaded from ASUS) However, after tapping update, I got the message "unable to update"
Can anyone please help? Any advice/solutions would be highly appreciated!
I have the Tencent version of the Rog Phone 2 however it has the Global Rom on it (the WW ROM)
Apart from these "issues" the phone is perfect. I cannot fault the phone in any other aspect.
I look forward to some solutions ?

Thanos88 said:
I have encountered several bugs with the Rog Phone 2
Last and final issue is that I have the old software with the July 2019 security patch. When I spoke to ASUS Chat on the phone, they told me to download the new firmware from their website. I downloaded the firmware and attempted to flash it via placing the room in the "Root" folder and restarting the phone. When I restarted the phone, on the too left corner of the screen it said there was a software update available (the Rom which I downloaded from ASUS) However, after tapping update, I got the message "unable to update"
Can anyone please help? Any advice/solutions would be highly appreciated!
I have the Tencent version of the Rog Phone 2 however it has the Global Rom on it (the WW ROM)
Apart from these "issues" the phone is perfect. I cannot fault the phone in any other aspect.
I look forward to some solutions ?
Click to expand...
Click to collapse
Although you may have WW Rom flashed, you probably still need to change the fingerprint to WW too, have a read of that thread for instructions...

reg66 said:
Although you may have WW Rom flashed, you probably still need to change the fingerprint to WW too, have a read of that thread for instructions...
Click to expand...
Click to collapse
Sorry which thread are you referring to? And when I purchased the phone it had the WW flashed already. Do you have any solutions for my problems I'm facing ?

Thanos88 said:
Sorry which thread are you referring to? And when I purchased the phone it had the WW flashed already. Do you have any solutions for my problems I'm facing ?
Click to expand...
Click to collapse
this thread, have a read of it and other posts. install device info HW from playstore and you'll probably see that the product id and fingerprint (under system) are both CN, although the rom itself is WW. you need to change to everything to WW following that thread... then you can update

reg66 said:
this thread, have a read of it and other posts. install device info HW from playstore and you'll probably see that the product id and fingerprint (under system) are both CN, although the rom itself is WW. you need to change to everything to WW following that thread... then you can update
Click to expand...
Click to collapse
Thanks !!!

Enrollment was not completed

Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong

WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Apparently happens to some users when they update to December.
Just delete your old face data as it says and rescan.

WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Some have reported the same issue when updating to December via fastboot with a wipe and clean install. Sometimes a factory reset works, other times not. Luckily, the January update is around the corner. Hopefully it is fixed by then

WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Mine happened a little different when updating to this version. My Face info was saved from the previous version but wasn't working 100% of the time. I deleted my cached face data and tried to retake but the blocks weren't showing on the face capture. So I then disabled all unlock methods, rebooted the phone and then tried to set up a pin and face again and everything worked as it should.

enrollment was not completed ( face enrolment didn't work)
ibphantom said:
Mine happened a little different when updating to this version. My Face info was saved from the previous version but wasn't working 100% of the time. I deleted my cached face data and tried to retake but the blocks weren't showing on the face capture. So I then disabled all unlock methods, rebooted the phone and then tried to set up a pin and face again and everything worked as it should.
Click to expand...
Click to collapse
It happened for me as well ( Pixel 4) after I've downgraded from Android 11 Beta to the latest stable 10.0.0 (QQ3A.200605.002, Jun 2020) via the Android Flash Tool.
I tried to factory reset my phone few times, even deleted Esim. Nothing helped ( could do register my face during phone setup or later after I skipped it)
I tried different builds but the only 1 which worked for me 10.0.0 (QD1A.190821.007, Oct 2019). I was able to register my face-unlock, lock bootloader and receive the latest OTAs.
I flashed this build with Platform Tools and also changed the configured security key instead of the Pin during setup.
Not sure if this was an issue with Android Flash Tool or Pin security.

Update
xorwin said:
It happened for me as well ( Pixel 4) after I've downgraded from Android 11 Beta to the latest stable 10.0.0 (QQ3A.200605.002, Jun 2020) via the Android Flash Tool.
I tried to factory reset my phone few times, even deleted Esim. Nothing helped ( could do register my face during phone setup or later after I skipped it)
I tried different builds but the only 1 which worked for me 10.0.0 (QD1A.190821.007, Oct 2019). I was able to register my face-unlock, lock bootloader and receive the latest OTAs.
I flashed this build with Platform Tools and also changed the configured security key instead of the Pin during setup.
Not sure if this was an issue with Android Flash Tool or Pin security.
Click to expand...
Click to collapse
Actually it stopped working in a few hours or so. Found out that this issue started from DP4 when you fastboot back to stable.
As a workaround, I opted to Beta again, where Face-Unlock Works. Then I opted out and received OTA stable and issues with Face recognition were gone. Yaaay

The latest Telstra june image fix the face id issue when downgrading from Android 11, the buid number is QQ3A.200605.002.A1

gm007 said:
The latest Telstra june image fix the face id issue when downgrading from Android 11, the buid number is QQ3A.200605.002.A1
Click to expand...
Click to collapse
What is the difference between this one and the standard version?

Help! Failed to update April patch on MI 9 Lite.

Yesterday afternoon I received a 2.3 GB update, which turned out to be the security patch for April. It installed normally but immediately started causing system and app failure. The problem arises when scrolling, as if the update time on the screen is reduced. It is a continuous stutter. I have restored the factory settings and the problem persists. Did something similar happen to them? Solutions? The truth is, I don't know what to do anymore. Will it be hardware? The phone has 3 months of use and prior to the update it worked perfectly.
Sorry if my post violates any forum rules, I'm new to this.

You could try going in to the system update again. Then click the menu top right and download latest package and try flashing it again