On mi a2 I got android 10 update and I decided to first reset my phone and then install the update, but after the reset it got lost. Anything?
Adv5 said:
On mi a2 I got android 10 update and I decided to first reset my phone and then install the update, but after the reset it got lost. Anything?
Click to expand...
Click to collapse
Maybe it got pulled out. I'm the same as you, although I didn't update because the Camera 2 Api cannot be enabled just yet with ANDROID 10 so I stayed in Android 9 for now. IT WAS STILL AVAILABLE in my settings as well, all I had to do is INSTALL the update then reboot. NOW I TRIED to check the settings and the UPDATE IS MISSING. It's showing "Your system is up to date" Android Version: 9
Can anyone also confirm this. Because I did NOT Factory reset, I just held the update. Then after I checked the settings, the update is missing/Not showing ANYMORE.
Syncsilent said:
Maybe it got pulled out. I'm the same as you, although I didn't update because the Camera 2 Api cannot be enabled just yet with ANDROID 10 so I stayed in Android 9 for now. IT WAS STILL AVAILABLE in my settings as well, all I had to do is INSTALL the update then reboot. NOW I TRIED to check the settings and the UPDATE IS MISSING. It's showing "Your system is up to date" Android Version: 9
Can anyone also confirm this. Because I did NOT Factory reset, I just held the update. Then after I checked the settings, the update is missing/Not showing ANYMORE.
Click to expand...
Click to collapse
Same problem here. Update is missing. Still on Pie December security patch...
jdhelman said:
Same problem here. Update is missing. Still on Pie December security patch...
Click to expand...
Click to collapse
Don't worry, it might be for the best that they pulled it out. Because a lot of people have been encountering BUGS just by updating. Some people said, to avoid those bugs they must Fully reset their devices, but that's just non sense for many people because they want "Convenience". An update supposed to bring improvements and new features, NOT Bugs. So we can't really blame them now if they've Pulled it out. LET'S WAIT FOR Official Announcement from Xiaomi about this.
Let's hope they pulled it to adress reported bugs.
Also, if you want to factory reset to minimise the chance of bugs with an update, I believe it's best to do so after you update, not before
akpe said:
Let's hope they pulled it to adress reported bugs.
Also, if you want to factory reset to minimise the chance of bugs with an update, I believe it's best to do so after you update, not before
Click to expand...
Click to collapse
Yeh but strange doing a factory reset before and not after ?
I didn't get any update, didn't even tried to reset my device. What's the issue?
ArmanAfridi said:
I didn't get any update, didn't even tried to reset my device. What's the issue?
Click to expand...
Click to collapse
They apparently halted the update.
Στάλθηκε από το Mi A2 μου χρησιμοποιώντας Tapatalk
akpe said:
They apparently halted the update.
Στάλθηκε από το Mi A2 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I see
Xiaomi hold the 10 update on MiA2,
Syncsilent said:
Maybe it got pulled out. I'm the same as you, although I didn't update because the Camera 2 Api cannot be enabled just yet with ANDROID 10 so I stayed in Android 9 for now. IT WAS STILL AVAILABLE in my settings as well, all I had to do is INSTALL the update then reboot. NOW I TRIED to check the settings and the UPDATE IS MISSING. It's showing "Your system is up to date" Android Version: 9
Can anyone also confirm this. Because I did NOT Factory reset, I just held the update. Then after I checked the settings, the update is missing/Not showing ANYMORE.
Click to expand...
Click to collapse
It can be enabled editing build.prop.
I'm on Android 10 and using GCam and HyperCam normally here.
Mena404 said:
Xiaomi hold the 10 update on MiA2,
Click to expand...
Click to collapse
Will we get the update within January?
pfss said:
It can be enabled editing build.prop.
I'm on Android 10 and using GCam and HyperCam normally here.
Click to expand...
Click to collapse
Stock working? ?
Mena404 said:
Stock working? ?
Click to expand...
Click to collapse
Unfortunately, no. It breaks stock.
I think the stock can also be installed with a Magisk Module but I don't know if it works.
Related
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
lorreca said:
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
Click to expand...
Click to collapse
sounds like a bad update.. you could restore via erecovery
lorreca said:
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
Click to expand...
Click to collapse
Have you Factory Reset it?
.156 had 3 patch updates to it, so I would suggest to install until they go away. Not sure how many times you have seen this?
fregor said:
.156 had 3 patch updates to it, so I would suggest to install until they go away. Not sure how many times you have seen this?
Click to expand...
Click to collapse
I already updated several times...
oxfordmark said:
Have you Factory Reset it?
Click to expand...
Click to collapse
I would like to avoid to do a factory reset and set all the phone again. If when stable 9.0 Pie arrived I won't be able to update because of this, so I will do a factory reset.
fuzziion said:
sounds like a bad update.. you could restore via erecovery
Click to expand...
Click to collapse
Have you got a link for the guide?
lorreca said:
I already updated several times...
Click to expand...
Click to collapse
Wich patch are you on then? .157 is out as well, so you could just wait until you get that one.
fregor said:
Wich patch Are you om then? .157 is out as well, so you could just wait until you get that one.
Click to expand...
Click to collapse
I should already have received the september Google patch, but nothing at the moment...
fregor said:
Wich patch are you on then? .157 is out as well, so you could just wait until you get that one.
Click to expand...
Click to collapse
157? Country?
I'm on 156 (patch3) in Croatia and there is no update when I check...
install magisk with both checkboxes activated
lorreca said:
Have you got a link for the guide?
Click to expand...
Click to collapse
Turn off your phone hold volume up + power until your phone boot to erecovery after that it's pretty simple just click on restore and follow the instructions
i had the exact same issue. i don't recall exactly, since i tried multiple different things, but i either did a factory reset or reflashed the entire .156 from firmware finder to get the update to stick.
i did rebrand to C432 and had twrp installed if you're in the same boat.
Danchibald said:
157? Country?
I'm on 156 (patch3) in Croatia and there is no update when I check...
Click to expand...
Click to collapse
Norway, C432
Looks like .159 is just around the corner as well.
I'm also on C432 but latest i recieved is 156 (patch3)... nothing further
IceFoxX said:
install magisk with both checkboxes activated
Click to expand...
Click to collapse
With Magisk I will lost OTA update...
fuzziion said:
Turn off your phone hold volume up + power until your phone boot to erecovery after that it's pretty simple just click on restore and follow the instructions
Click to expand...
Click to collapse
Ah ok, is like to do a factory reset right?
Im going to wait for 10 november (pie release) and of doesnt receive the OTA i will do that
bravo261 said:
i had the exact same issue. i don't recall exactly, since i tried multiple different things, but i either did a factory reset or reflashed the entire .156 from firmware finder to get the update to stick.
i did rebrand to C432 and had twrp installed if you're in the same boat.
Click to expand...
Click to collapse
I'm already on C432 (rebrended from demo/retail) but I would prefer to keep stock with OTA until root for Pie coming. Then i will root again.
lorreca said:
With Magisk I will lost OTA update...
Click to expand...
Click to collapse
Yeah got the same issue..uninstall magisk.. install magisk manager activate both checkboxes ( keep force encryption + keep dm verity (without keep dm verity you will lose the patches)) download the zip and flash magisk with twrp and you will still have patch03
Sadly i dont know the source anymore
lorreca said:
I'm already on C432 (rebrended from demo/retail) but I would prefer to keep stock with OTA until root for Pie coming. Then i will root again.
Click to expand...
Click to collapse
i'm not talking about root. i'm suggesting you perform a factory reset with the stock recovery, and if that doesn't work, then install twrp and use hurupdater with the firmware files to really go back to the freshest install. using hurupdater will install the stock recovery as well. that got my updates to finally stick
Hi,
I am done with the android 10 update as it is full of bugs and I do not have any wifi.
is there a smart easy to go back to latest stock android 9 ?
bootloader is locked
meisterlampe2000 said:
Hi,
I am done with the android 10 update as it is full of bugs and I do not have any wifi.
is there a smart easy to go back to latest stock android 9 ?
bootloader is locked
Click to expand...
Click to collapse
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Baron60 said:
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Click to expand...
Click to collapse
What errors were fixed?
mh, i cannot connect to any wifi network, even the open without password,cypher...
That is still the case in the Jan Update, will try the factory reset now.
meisterlampe2000 said:
mh, i cannot connect to any wifi network, even the open without password,cypher...
That is still the case in the Jan Update, will try the factory reset now.
Click to expand...
Click to collapse
hi.
u want connect with share internet with Bluetooth
very easily
****oonn said:
hi.
u want connect with share internet with Bluetooth
very easily
Click to expand...
Click to collapse
sure, thanks. But what i really want is a working operating system
Baron60 said:
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Click to expand...
Click to collapse
Ok, dude, stop misleading people. Maybe it is 100% bugfree for you. Which I doubt, unless you do have device personalization services installed as a system app and can use 5 GHz hotspot; both of these problems present in mine and my wife's phone, who upgraded today, thus not coming from 13 jan upgrade. Or maybe it doesn't have any bugs that bother you, but it's enough to go quickly through the the various threads to see that you're wrong in claiming that's 100% clean of bugs.
Hey i just wiped the phone (factory reset) and now WiFi is working fine again. So definitely a SW migration bug, to those who suffer the same (wifi not connecting at all), you may have to do that or wait for a proper fix (Jan 2020 patch did not solve for me).
Thx!
hugohenry16 said:
What errors were fixed?
Click to expand...
Click to collapse
Slow WiFi fixed. UI glitches with gestures and other UI things fixed. Too early to tell but battery seems slightly better
Baron60 said:
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Click to expand...
Click to collapse
No, you shouldn't do a factory reset unless you want an annoying banner at the Settings page
I have unlocked bootloader for starts. I loaded the beta when it came out and attempted to root but wasn't successful. Downloaded June image to go back to 10 but now it always goes to fastbootd and it will set pin but fails face registration. Factory reset same, flash may all the same. I have no idea what's going on. Anyone seen this before? TIA very much.
rzracer2 said:
I have unlocked bootloader for starts. I loaded the beta when it came out and attempted to root but wasn't successful. Downloaded June image to go back to 10 but now it always goes to fastbootd and it will set pin but fails face registration. Factory reset same, flash may all the same. I have no idea what's going on. Anyone seen this before? TIA very much.
Click to expand...
Click to collapse
I had the same problem.
When downgrade to android 10 no face recognition working.
Thank God went to Android 11 again and works fine.
Στάλθηκε από το Pixel 4 XL μου χρησιμοποιώντας Tapatalk
Well went back to Jan and face unlock worked fine, took 2 update to get back to June and face unlock stopped working again.
Darudakos said:
I had the same problem.
When downgrade to android 10 no face recognition working.
Thank God went to Android 11 again and works fine.
Στάλθηκε από το Pixel 4 XL μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
rzracer2 said:
I have unlocked bootloader for starts. I loaded the beta when it came out and attempted to root but wasn't successful. Downloaded June image to go back to 10 but now it always goes to fastbootd and it will set pin but fails face registration. Factory reset same, flash may all the same. I have no idea what's going on. Anyone seen this before? TIA very much.
Click to expand...
Click to collapse
rzracer2 said:
Well went back to Jan and face unlock worked fine, took 2 update to get back to June and face unlock stopped working again.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-4-xl/how-to/module-fix-broken-unlock-t4095233
This fixed it for me
Hi, when i reverted back to android 11 from android 12 beta 1 my play store system update is stuck on January patch. How do i get to the latest security patch? i've checked for update but nothing happens.
Is this after the June update? Mine is currently on May 1st after the June update. If unlocked I would try dirty flashing a full image. If locked, sideload the latest OTA via recovery.
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Same here with Pixel 4
gm007 said:
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Click to expand...
Click to collapse
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
v12xke said:
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
Click to expand...
Click to collapse
I said everything
I had to ask also in Google pixel community https://support.google.com/pixelpho...gle-play-system-update-stuck-at-january?hl=en
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
2WildFirE said:
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
Click to expand...
Click to collapse
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
2WildFirE said:
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
Click to expand...
Click to collapse
I suspect people don't want to lose their data by properly wiping & restoring their phone to its factory state.
U don't know how often I did a full factory image flash.
But nothing worked!
v12xke said:
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
Click to expand...
Click to collapse
I met the same issue with 4a5g. I tried flashing 5 times but issue still come. Google play services system update will automatically display 1 jan 2021 when i log in google account ( the account i was enroll to using android 12beta via OTA, but i've cancelled android 12beta)
I think issue need to be resolve by google or we can use other google account.
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
So that mean, we need to enroll pilot update 12beta again via OTA or flashing, right?
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Strange how it is behind. I thought new beta versions came out after the general release so they could roll the new security release into the beta. This would mean A12 beta would also be current. But I also haven't been running the betas for a couple years. Interesting.
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Please share your solution with android 11.
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
The solution on Android 11 is to simply install the "Main components" APK from APK mirror
It's basically you're just updating manually.
Main components APKs - APKMirror
Main components APKs - APKMirror Free and safe Android APK downloads
www.apkmirror.com
2WildFirE said:
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
Click to expand...
Click to collapse
There is a solution check my post.
Alexisnotfrommars said:
There is a solution check my post.
Click to expand...
Click to collapse
This isn't a solution. It only change the date not more or less!
Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Update: I attempted the system update again and left it overnight. This morning it's still stuck on the same installing screen.
Can someone share the Android Version screen of an unlocked Pixel 7. I think I might be updated and the update is just a bug?
Update: I determined I had an OTA update failure. So I just adb sideloaded the OTA file and it's fixed now.
KillerDroid96 said:
Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Click to expand...
Click to collapse
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
ern88 said:
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
Click to expand...
Click to collapse
It's set to mobile data and that should only impact the downloading not installing. 4 hours now and still stuck. I'm considering rebooting at this point.
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Giovanni9518 said:
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Click to expand...
Click to collapse
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
KillerDroid96 said:
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
Click to expand...
Click to collapse
My Google play system also states that too.
Well I give up. I restarted and I'm just not going to update for the time being.
ern88 said:
My Google play system also states that too.
Click to expand...
Click to collapse
I think I'm actually fully updated and its just a bug?
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
KillerDroid96 said:
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
Click to expand...
Click to collapse
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
ern88 said:
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
Click to expand...
Click to collapse
Thanks! I determined I had an OTA
update failure. So I just adb sideloaded the OTA file and it's fixed now.
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
gorilla p said:
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
Click to expand...
Click to collapse
They've covered this in the two big threads regarding unlocking / rooting in the 7 Pro-forum.