Related
I went to check for system updates today and my pixel initially started to download the latest patch and then after a couple of seconds went straight to telling me that there is no update available. Anyone else have this issue and/or successfully update to the March 2020 OTA via the process below?
Updating Phone Once Rooted:
- Check for device updates, when found:
- Tap uninstall in 'Magisk Manager'
- Tap restore images
- install OTA (do not reboot)
- Back to magisk, tap install > select install to inactive slot
- When magisk installed, press the reboot button in it. It'll force to the other slot AND you'll be updated AND rooted
I assume I should be able to go under 'System' -> 'Advanced' and get the OTA under 'System Update'. I've already disabled 'Automatic system updates' under 'Developer Options'. Just making sure google is somehow not blocking the update on rooted devices and that the above steps are correct. Thank you in advance!
Found similar thing on reddit here.
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, the initial boot may take quite a while. I've seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take a regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just be patient and let the phone complete the process.
Click to expand...
Click to collapse
sic0048 said:
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Click to expand...
Click to collapse
Thanks for the reply! I'm very used to sideloading/dirty flashing the updates, was hoping to use the Magisk method . Seems like google is getting smarter with their updates. I am guessing the current inability to see the OTA is due to the updates with google pay and google wanting to ensure banks it is safe.
I just finished sideloading March's OTA and patching the boot.img and everything seems to work, just a bit more effort than leveraging Magisk.
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
I experienced same exact thing. Looks like it saw the update at first then after a few seconds reverted to No updates available. About to try uninstalling Magisk, if no bueno, then gonna just sideload.
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Gooch4130 said:
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Click to expand...
Click to collapse
Yes I disabled automatic updates. It didn't do it automatically, I clicked the check for update button. Normally when I do that it says there's a download available and then I know to check online for the flash file. This time it updated without stopping.
FAILED (remote: Failed to write to partition Not Found)
what i am doing wrong ????
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Boot loader is unlocked...
10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)
this version i did ota update
i am from germany.
okay, i found a way to root, but how is it with safety net fix ???
anyone an idea ???
Deleted
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
It installed the OTA for me too, now I'm afraid to restart my phone.
mattcoz said:
It installed the OTA for me too, now I'm afraid to restart my phone.
Click to expand...
Click to collapse
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
I successfully rooted the March update, using the boot.img method.
Spookymyo said:
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
Click to expand...
Click to collapse
I rooted with boot.img method, as well
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
I got it rooted. It ended up taking a factory reset. It must have been some file interfering with the process. Once I reset my phone the rooting process went without incident.
As I'm searching for a more Phone based update wy, I'm thinking about to use maybe the Implemented OTA Process, but download the OTA-File manually... But for that We must know,how the OTA process is working. Did someone know:
- Where the update stores the download fine (I found a OTA and a OTA_Packge directory in the /Data/ folder)
- is there maybe a setting or information which must be injected somewhere (maybe a txt file)
- after that the ota update could then maybe started by hand
Has someone informations on that? If maybe someone where the ota still works and stil has root could check the files and places?
Chris.C said:
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
Worked like charm!! Thanks!! :good:
Click to expand...
Click to collapse
I unlocked the bootloader, sideloaded the August 2020 OTA and flashed the patched boot image. Kept bootlooping, then I restored to the original, booted in, installed Magisk Manager and then flashed the patched image again. Just leaving this here in case it helps someone.
Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance.
EDIT:
I have now upgraded to Android 11 and installed google apps, here's how I did it.
The usual disclaimers apply: DO NOT DO THIS IF YOU ARE NOT FAMILIAR WITH ADB, FASTBOOT ETC. I will not be held responsible for bricked devices.
If you wish to void your warranty the command to unlock the bootloader and allow flashing with fasboot the command is "fastboot oem nubia_unlock NUBIA_NX627J"
1. Backup the data you want to keep from your phone. Wipe the phone using stock recovery or TWPR
2. Upgrade to 2.24 using full zip. As I had previously rooted my device so the stock recovery wasn't working and I had to flash TWRP.
3. Upgrade to 3.11 using full zip. Either use the stock recovery or TWRP. This will be the last time you can use TWRP for flashing due to changes in Android 11. TWRP does not support Android 11 yet. If I'd have realised this before I would have tried to flashed google apps at this step. Can't confirm if this works but I wish I'd have tried it.
4. If you need root, install the APK for magisk "canary" (or any version that supports patching boot.img)
5. Open the zip for 3.11 and extract boot.img, copy to your device
6. Patch the boot.img using Magisk. I used these instructions. Reboot.
7. Congratluations, you have Android 11 with root!
If you need gapps and didn't install them yet, it's still possible. Flashing without TWRP was a challenge, but after a lot of hours wasted, I found that BiTG apps was working which I downloaded from this page. I flashed using EX Kernel Manager but I would imagine other apps that allow root flashing will work similarly.
Currently, I have not been able to get SafetyNet checks to pass. I will update this thread with details as I uncover them.
For WhatsApp verfication to pass make sure you have granted Google services framework SMS permissions.
Hope this is helpful for some people who are thinking about making the move to Android 11. No major issues to report yet, will update this thread if anything comes up.
EDIT 2021/02/22: I have repeated this process successfully for V3.15.
thais rom support to flash twrp or google app?
someone who helps? very ugly problem that notifications from whatsapp do not arrive
mmason75123 said:
Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance
Click to expand...
Click to collapse
All work fine in this version (NX627J_CNCommon_V2.23 build)? notifications whatsapp? names of calls?
updated OP now, I have finally managed to upgrade to Android 11!
mmason75123 said:
Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance.
EDIT:
I have now upgraded to Android 11 and installed google apps, here's how I did it.
The usual disclaimers apply: DO NOT DO THIS IF YOU ARE NOT FAMILIAR WITH ADB, FASTBOOT ETC. I will not be held responsible for bricked devices.
1. Backup the data you want to keep from your phone. Wipe the phone using stock recovery or TWPR
2. Upgrade to 2.24 using full zip. As I had previously rooted my device so the stock recovery wasn't working and I had to flash TWRP.
3. Upgrade to 3.11 using full zip. Either use the stock recovery or TWRP. This will be the last time you can use TWRP for flashing due to changes in Android 11. TWRP does not support Android 11 yet. If I'd have realised this before I would have tried to flashed google apps at this step. Can't confirm if this works but I wish I'd have tried it.
4. If you need root, install the APK for magisk "canary" (or any version that supports patching boot.img)
5. Open the zip for 3.11 and extract boot.img, copy to your device
6. Patch the boot.img using Magisk. I used these instructions. Reboot.
7. Congratluations, you have Android 11 with root!
If you need gapps and didn't install them yet, it's still possible. Flashing without TWRP was a challenge, but after a lot of hours wasted, I found that BiTG apps was working which I downloaded from this page. I flashed using EX Kernel Manager but I would imagine other apps that allow root flashing will work similarly.
Currently, I have not been able to get SafetyNet checks to pass. I will update this thread with details as I uncover them.
For WhatsApp verfication to pass make sure you have granted Google services framework SMS permissions.
Hope this is helpful for some people who are thinking about making the move to Android 11. No major issues to report yet, will update this thread if anything comes up.
Click to expand...
Click to collapse
how can i unbloat this **** and get the stock rom? Are they going to release a global rom android 11?
B4$Q said:
how can i unbloat this **** and get the stock rom? Are they going to release a global rom android 11?
Click to expand...
Click to collapse
you can uninstall most of the bloat without root, and even more of it with
obviously I don't work for nubia but at this point a global ROM seems a way off, especially given there has been nothing since 2.03
here is the forum post for release 3.11
【2020年11月30日】Android R V311 for Z20 小批量更新公告-努比亚Z20-努比亚/红魔社区 - 手机版
mmason75123 said:
you can uninstall most of the bloat without root, and even more of it with
obviously I don't work for nubia but at this point a global ROM seems a way off, especially given there has been nothing since 2.03
here is the forum post for release 3.11
【2020年11月30日】Android R V311 for Z20 小批量更新公告-努比亚Z20-努比亚/红魔社区 - 手机版
Click to expand...
Click to collapse
I want to make it stock. Is there a tutorial for that? Their rom has too many issues, including the notifications and that ugly skin with their useless chinese features.
B4$Q said:
I want to make it stock. Is there a tutorial for that? Their rom has too many issues, including the notifications and that ugly skin with their useless chinese features.
Click to expand...
Click to collapse
"stock" for this phone is what you have installed now. There is no custom ROM, which is your real complaint. To be honest, I would also much prefer a custom ROM, if you find one let me know! Anyway this is completely off topic for this thread
mmason75123 said:
"stock" for this phone is what you have installed now. There is no custom ROM, which is your real complaint. To be honest, I would also much prefer a custom ROM, if you find one let me know! Anyway this is completely off topic for this thread
Click to expand...
Click to collapse
Yeah, stock is what I have installed right now, which is Android 9. I would like to get the stock Android 11, without their skin. Maybe a GSI rom could fix it, but I was not able to install it. As soon as you flash the gsi rom on nubia ui 8, the system breaks.
B4$Q said:
Yeah, stock is what I have installed right now, which is Android 9. I would like to get the stock Android 11, without their skin. Maybe a GSI rom could fix it, but I was not able to install it. As soon as you flash the gsi rom on nubia ui 8, the system breaks.
Click to expand...
Click to collapse
Yeah I hear you - it's incredibly annoying that you can't set the default launcher to anything else. Well, I'm sure you can probably! But I'm going to leave my phone to settle for a few days at least before messingw ith it any more
Good luck.
mmason75123 said:
Yeah I hear you - it's incredibly annoying that you can't set the default launcher to anything else. Well, I'm sure you can probably! But I'm going to leave my phone to settle for a few days at least before messingw ith it any more
Good luck.
Click to expand...
Click to collapse
I'll stay on Android 9 for the moment, but I will never buy from this brand again. Apple proved me again that their phones are the best from the market. And Google Phones of course.
I have updated my phone from Android 9 to Android 11 V3.11 everything works fine but can I install gapps and how?
mmason75123 said:
Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance.
EDIT:
I have now upgraded to Android 11 and installed google apps, here's how I did it.
The usual disclaimers apply: DO NOT DO THIS IF YOU ARE NOT FAMILIAR WITH ADB, FASTBOOT ETC. I will not be held responsible for bricked devices.
1. Backup the data you want to keep from your phone. Wipe the phone using stock recovery or TWPR
2. Upgrade to 2.24 using full zip. As I had previously rooted my device so the stock recovery wasn't working and I had to flash TWRP.
3. Upgrade to 3.11 using full zip. Either use the stock recovery or TWRP. This will be the last time you can use TWRP for flashing due to changes in Android 11. TWRP does not support Android 11 yet. If I'd have realised this before I would have tried to flashed google apps at this step. Can't confirm if this works but I wish I'd have tried it.
4. If you need root, install the APK for magisk "canary" (or any version that supports patching boot.img)
5. Open the zip for 3.11 and extract boot.img, copy to your device
6. Patch the boot.img using Magisk. I used these instructions. Reboot.
7. Congratluations, you have Android 11 with root!
If you need gapps and didn't install them yet, it's still possible. Flashing without TWRP was a challenge, but after a lot of hours wasted, I found that BiTG apps was working which I downloaded from this page. I flashed using EX Kernel Manager but I would imagine other apps that allow root flashing will work similarly.
Currently, I have not been able to get SafetyNet checks to pass. I will update this thread with details as I uncover them.
For WhatsApp verfication to pass make sure you have granted Google services framework SMS permissions.
Hope this is helpful for some people who are thinking about making the move to Android 11. No major issues to report yet, will update this thread if anything comes up.
Click to expand...
Click to collapse
You may want to add in the instructions the command to unlock the bootloader of the z20 since users wouldn't be able to flash otherwise.
I managed to get this working and trying to de-china-fy to have english only. Will report back if I can somehow replace the default launcher.
Edit: got a my total launcher running by placing the apk inside the folder where the default nubia launcher is sitting. With root, just place the apk under system/app/nubia launcher folder. It's not working 100% perfect for me as nubia edge gestures stop letting me pull up recent apps so I can't multi task anymore
aso89 said:
I have updated my phone from Android 9 to Android 11 V3.11 everything works fine but can I install gapps and how?
Click to expand...
Click to collapse
See OP "If you need gapps", here's the link again to get them again. BiTGApps-arm64-11.0.0-R17_signed-20200923.zip is the name of the file I have.
[GAPPS] Download GApps for Android 11 (JUNE 2021 UPDATE)
Google Apps (GApps) for Android 11 based ROMs needs to be flashed separately. Here is a direct link to download Android 11 compatible GApps.
www.cyanogenmods.org
xda-nitro said:
You may want to add in the instructions the command to unlock the bootloader of the z20 since users wouldn't be able to flash otherwise.
I managed to get this working and trying to de-china-fy to have english only. Will report back if I can somehow replace the default launcher.
Edit: got a my total launcher running by placing the apk inside the folder where the default nubia launcher is sitting. With root, just place the apk under system/app/nubia launcher folder. It's not working 100% perfect for me as nubia edge gestures stop letting me pull up recent apps so I can't multi task anymore
Click to expand...
Click to collapse
Thanks that's a good idea, I'll try it out. Can you explain a little more around the gestures issue, is it that you show the navbar and the nubia controls are now somehow in the way? I've been a fan of the nubia navigation since I gave it a go and became used to it. Having the back button at any point in the screen is useful I find.
I've added the command to unlock the bootloader to the OP btw.
mmason75123 said:
Thanks that's a good idea, I'll try it out. Can you explain a little more around the gestures issue, is it that you show the navbar and the nubia controls are now somehow in the way? I've been a fan of the nubia navigation since I gave it a go and became used to it. Having the back button at any point in the screen is useful I find.
I've added the command to unlock the bootloader to the OP btw.
Click to expand...
Click to collapse
With the stock nubia launcher even with the Chinese app taken out, swiping left always tries to get you to the Chinese google feed like page. I didn't care for that so I replaced the launcher with total launcher which worked.
The problem is that the swipe up gesture that usually pull up the recent apps to allow switching between application is not working. Even switching the navigation from gestures to 3 button navigation and pressing the recent apps button does nothing.
Perhaps I took one too many Chinese system apps out which caused this error or it is somehow tied into system and nubia launcher itself. Will have to test further.
xda-nitro said:
With the stock nubia launcher even with the Chinese app taken out, swiping left always tries to get you to the Chinese google feed like page. I didn't care for that so I replaced the launcher with total launcher which worked.
The problem is that the swipe up gesture that usually pull up the recent apps to allow switching between application is not working. Even switching the navigation from gestures to 3 button navigation and pressing the recent apps button does nothing.
Perhaps I took one too many Chinese system apps out which caused this error or it is somehow tied into system and nubia launcher itself. Will have to test further.
Click to expand...
Click to collapse
Thanks makes sense. Yes it sounds like you've uninstalled the Recents app, either reinstate or there are alternatives out there I believe
mmason75123 said:
Thanks makes sense. Yes it sounds like you've uninstalled the Recents app, either reinstate or there are alternatives out there I believe
Click to expand...
Click to collapse
Just to confirm, I have just tried to set a new default launcher as you suggest above by replacing the APK. Replacing with SmartLauncher I couldn't return to the home screen using the swipe up gesture so have rolled back.
mmason75123 said:
Just to confirm, I have just tried to set a new default launcher as you suggest above by replacing the APK. Replacing with SmartLauncher I couldn't return to the home screen using the swipe up gesture so have rolled back.
Click to expand...
Click to collapse
It's weird, the recent apps and swipe up are linked to the nubia launcher for some reason. Despite this, I'm staying with with my launcher as I can't stand the apple like nature of the nubia launcher. I think I have managed to get rid of all the Chinese apps though so all good for now.
xda-nitro said:
It's weird, the recent apps and swipe up are linked to the nubia launcher for some reason. Despite this, I'm staying with with my launcher as I can't stand the apple like nature of the nubia launcher. I think I have managed to get rid of all the Chinese apps though so all good for now.
Click to expand...
Click to collapse
Do you get notifications from apps? When I had that rom, I was not receiving any notification.
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!
Updating from an update fileI have been seeing a lot of posts about people not receiving the OTA on their phone, and got tired of linking my instructions, so I decided to make a separate post
Download the version that you need from the Asus Zenfone 8 Support page (Note that if you are not on the latest Android 11 firmware (30.12.112.72), you will not be able to Android 12. So you need to do these steps with the latest Android 11, and then re-do them for the Android 12 firmware)
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
not work for me :/
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
eVen123 said:
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
Click to expand...
Click to collapse
I think that what is needed is to update to the latest firmware, then Android 12. So if you are already on Android 11, but not latest firmware, install it with the instructions, then do the same to update to Android 12's latest version.
drum94 said:
not work for me :/
Click to expand...
Click to collapse
What part does not work? Please be more specific and also, you should re-read the steps more carefully, in case you missed something
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
drum94 said:
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
Click to expand...
Click to collapse
It also depends what prefix your installation has. See the first letters
UL-...
If you are from some other region, it could be that UL- is not a fitting upgrade option for you. As far as I can tell, it's not possible to tell which of the versions you have.
I give you the build number which is marked in the software information:
RKQ1.2021022.002.30.12.112.72
I have the right version or not suddenly?
Thank you for the quick tutorial. I was doing this via fastboot till now.
However: I upgraded to the latest firmware BEFORE Android 12. No issues.
Then I upgraded to the Android 12 firmware: stuck. Gave me some kind of ram dump, reboot returned me to the same error: bootloop. I was able to reboot and get to the bootloader. After selecting "recovery" it actually booted Android. And now for the weird part: it looks like I have a mix of Android 11 and Android 12 now! The phone is all but unusable for how slow it is. But the main UI looks like Android 11 still, but things like the reboot screen now look like Android 12. Bizarre...
I was at least able to enable ADB debug again, so I think I will be able to recover the phone. Still a weird issue though. Don't know if flashing with fastboot would have prevented it...
If anything fails, you can always try the Asus flash script it will solve most of the issues with your phone, just note that it installs Android 11 (30.11.51.115)
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
EDIT: nvm, I saw your other reply, you alreay tried that. Were you able to get it working again?
Going from WW-30.12.112.82 to WW-31.1004.0404.107 worked flawlessly, i did not lose settings or data on that upgrade (but I want to stress that a good backup is STILL a very good thing to have!) It then started downloading the 31.1010.0410.43 upgrade on its own. (shown in the ui as SKQ1.210821.001.31.1010.0410.43)
Why didn't I upgrade to the latest one myself? Simple: I goofed up and downloaded the older one.
change the name in UL-ASUS_I006D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Hi, has anyone tried to upgrade a firmware that has Magisk and TWRP installed? Today Android 13 has been released for the Zenfone 8, but I wouldn't really like to do something really dumb such as upgrading, rebooting to recovery to reinstall Magisk only to discover that TWRP has been replaced by the stock recovery and the phone completely erases any data it has stored.
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Rokcy98 said:
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Click to expand...
Click to collapse
Thank you! As this is my first phone with A/B slots, I wasn't completely sure about how to proceed. I'll follow your instructions! The only thing I don't get is where is TWRP stored and why it won't be overwritten by the update.
EDIT: installed successfully, thanks!
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
awambawamb said:
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
Click to expand...
Click to collapse
Google fastboot flash with PC or recovery flash via custom Recovery.
For both the bootloader has to be unlocked. In my opinion there's no other way to rollback .
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
awambawamb said:
....
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide......
Click to expand...
Click to collapse
I advise to search for the right information on XDA and the downloads from Xiaomi servers.
awambawamb said:
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
Click to expand...
Click to collapse
Downgrading using the rename trick is not possible now due to OTA validation. But still, downgrading is still possible as long as the bootloader is unlocked (you can re-lock bootloader afterwards btw so no worry about banking apps).
Procedure might be something similar to this:
1. Unlock bootloader
2. Flash any latest OSS ROM (this is just to remove MIUI)
3. Use MiFlash and fastboot method to install old versions (re-lock if you want)
Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.
PS: Just to add, Anti-Rollback is not yet enabled for sweet so no worries with getting bricked while downgrading. Just be careful and flash appropriately.
Thanks for the kind reply, @BigChungus321 . Glad to hear that I can still unlock and lock the bootloader! at least for those 6 months of warranty.
Just one thing, in the step you suggested you said:
1. Unlock bootloader2. Flash any latest OSS ROM (this is just to remove MIUI)3. Use MiFlash and fastboot method to install old versions (re-lock if you want)Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
awambawamb said:
Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
Click to expand...
Click to collapse
It is the same but I do encounter people who face anti-rollback error rejecting the downgrade if flashing from MIUI to MIUI. But going from OSS to MIUI, this arb check does not seem to occur.
awambawamb said:
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
Click to expand...
Click to collapse
No clue if that prevents the issue/bug you encounter. I usually just dirty flash the full rom update (not the incremental which is around ~200mb) in recovery and I don't seem to get issue this way, aside from recovery being replaced because dm-verity is getting activated again.
awambawamb said:
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
Click to expand...
Click to collapse
I've seen many people who have this issue too. Again, no clue how to fix this. Maybe reboot, and just enable mobile data. Try changing sim card or switching sim card slots. Use other Mi Account for unlocking. I did see discussions about how using the same sim card and same Mi account can on a different device can cause this. I still have no clue how to fix this though so sorry. Might be a good idea to use a fresh sim card and mi account if you still encounter it.