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.
Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??
Do a Google search for sideloading ota images. It's actually pretty easy. I'm unlocked running a rom so I can't give you a step by step off the top of my head.
nissan skyline said:
Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??
Click to expand...
Click to collapse
The instructions are on the download page for the OTA and I have pasted them below. You don't need an unlocked bootloader and there is always a chance that something could go wrong when flashing your phone but this method seems pretty safe.
To update a device using one of the OTA images below, you need the latest adb tool. You can get it from the Android SDK Platform-Tools package, which you can download here.
Don't forget to either add adb to your PATH environment variable or change into the directory containing the executable.
Also be certain that you've set up USB access for your device, as described in Run Apps on a Hardware Device.
To apply an OTA update image:
Download the appropriate update image for your device below.
Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
With the device powered on and USB debugging enabled, execute:
adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device instead, and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
For security, you should disable USB debugging when the device is not being updated.
Were you able to sideload the OTA? I tried on the 8th but got an error -- footer error. I'm on 7.1.1 and attempted to load N6F27E.
Adb sideload
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.
I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!
Here is a link to gdrive with ota zips. Not reall great at this. So, hopefully you can download. I have not experienced any of the issues you have. None https://drive.google.com/drive/folders/0B1PLXsZI0UyjTGJEVDFaRy1ITms?usp=sharing
Liftkit said:
I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!
Click to expand...
Click to collapse
https://developers.google.com/android/ota
Edit:I see that this URL already appears in the first post. Hmmm...
Sideloading the OTA is by far the simplest way of upgrading. You keep everything - data, apps, etc. You lose root, but that's easy to reinstall.
I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?
NCtwin said:
I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?
Click to expand...
Click to collapse
OTAs are complete packages. You can sideload the latest one directly.
Maybe that's why I keep getting an error when trying to use Wug to update. I'll do the sideload option and see what happens. Thanks a lot.
I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
pckarma112 said:
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.
Click to expand...
Click to collapse
what is your build #
Liftkit said:
I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
what is your build #
Click to expand...
Click to collapse
Take a backup and then sideload N6F27H, Jul 2017. You lose nothing, you boot back into pretty much what you had before, but with security enhancements and a few minor feature improvements.
And before you do any more, read my first sentence again.
Hello all,
On my new Pixel 3 XL, I installed Magisk immediately after doing the initial setup. I then tried taking the January 2019 OTA update (the phone was running the original build from September 2018) and installing the update using the instructions here for devices with A/B partitions: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This however did not work and the update still failed to install. I ended up doing the upgrade manually via the bootloader but I would like to ask about how to handle this process for future updates. I am running the latest stable version of Magisk.
Thank you
Is it possible that /system or /vendor have been altered in some way? That would cause the OTA to fail...
Didgeridoohan said:
Is it possible that /system or /vendor have been altered in some way? That would cause the OTA to fail...
Click to expand...
Click to collapse
I still pass SafetyNet though. Wouldn't modifying either of those cause it to fail?
David B. said:
I still pass SafetyNet though. Wouldn't modifying either of those cause it to fail?
Click to expand...
Click to collapse
As a rule, you can do quite heavy modifications to both /system and/vendor and still pass SN. So, not necessarily...
Didgeridoohan said:
As a rule, you can do quite heavy modifications to both /system and/vendor and still pass SN. So, not necessarily...
Click to expand...
Click to collapse
Well I do use the Internal Audio Plugin which may write stuff to /system and/or /vendor. I am not sure though. I do not remember if I had it installed at that point though. I do have it installed now though. If it turns out that the app is the reason it's not working, hopefully I will be able to uninstall it when trying the OTA again.
Hi all. I have searched for information and have seen a lot and varied. I come to confirm more than anything and to know if you have a clear idea.
I have my 3XL pixel rooted with Magisk.
First question: With the root of magisk the system does NOT detect the new monthly update updates. Is this normal? I understood that I would detect it but that it would NOT let me update it.
As a result of that question I found this other ...
https : // topjohnwu. github.io/Magisk/tutorials.html (sorry, there are spaces)
I'm not sure if this tutorial is valid for the Pixel 3XL. I have reproduced it and ... or something I have not done well or is not compatible with our device.
The objective of all this is to know if, with the rooted phone, OTAs can be detected and, in case the answer is no, to know if there is any method like the one that Magisk proposes without having to download the OTA, install by the recovery and re-root with twrp.
I have not used any magisk module, but I do have Es File Explorer installed with root viewer, titanium backup and Swift Insaller. I do not think this has modified / system or / vendor.
Thanks and best regards!
ciltocruz said:
Hi all. I have searched for information and have seen a lot and varied. I come to confirm more than anything and to know if you have a clear idea.
I have my 3XL pixel rooted with Magisk.
First question: With the root of magisk the system does NOT detect the new monthly update updates. Is this normal? I understood that I would detect it but that it would NOT let me update it.
As a result of that question I found this other ...
https : // topjohnwu. github.io/Magisk/tutorials.html (sorry, there are spaces)
I'm not sure if this tutorial is valid for the Pixel 3XL. I have reproduced it and ... or something I have not done well or is not compatible with our device.
The objective of all this is to know if, with the rooted phone, OTAs can be detected and, in case the answer is no, to know if there is any method like the one that Magisk proposes without having to download the OTA, install by the recovery and re-root with twrp.
I have not used any magisk module, but I do have Es File Explorer installed with root viewer, titanium backup and Swift Insaller. I do not think this has modified / system or / vendor.
Thanks and best regards!
Click to expand...
Click to collapse
Hello,
The issue that you are describing is identical to what I observed during the February OTA update. It was not showing up on my phone. Supposedly if you wait long enough it will be detected, but I got impatient with waiting and just did it manually. It is worth noting however that when I got my Pixel 3 XL (I got it in January), I rooted it immediately before installing the January patches, and the behavior that you described as what should have happened is what I observed: the update was detected, but I could not install it. The odd thing about it was that even after uninstalling Magisk, I still could not get it to install and therefore ended up manually sideloading that update as well. It is worth noting that as part of that sideload, I chose to wipe the phone so that whatever modifications I must have made to /system or /vendor would be gone.
I am sorry that I could not provide any real help for this issue since I have been sideloading as a workaround. If you come up with a real solution to this, please let me know. Otherwise, you may want to just sideload manually.
David B. said:
Hello,
The issue that you are describing is identical to what I observed during the February OTA update. It was not showing up on my phone. Supposedly if you wait long enough it will be detected, but I got impatient with waiting and just did it manually. It is worth noting however that when I got my Pixel 3 XL (I got it in January), I rooted it immediately before installing the January patches, and the behavior that you described as what should have happened is what I observed: the update was detected, but I could not install it. The odd thing about it was that even after uninstalling Magisk, I still could not get it to install and therefore ended up manually sideloading that update as well. It is worth noting that as part of that sideload, I chose to wipe the phone so that whatever modifications I must have made to /system or /vendor would be gone.
I am sorry that I could not provide any real help for this issue since I have been sideloading as a workaround. If you come up with a real solution to this, please let me know. Otherwise, you may want to just sideload manually.
Click to expand...
Click to collapse
I see that there is no other option than to do it manually and reinstall magisk later every month ...
ciltocruz said:
I see that there is no other option than to do it manually and reinstall magisk later every month ...
Click to expand...
Click to collapse
Well at this point I will not have a chance to test this belief out until March.
David B. said:
Well at this point I will not have a chance to test this belief out until March.
Click to expand...
Click to collapse
I rerooted the phone with Magisk and it's perfect.
Unfortunately, with the March update, my 3LX pixel will not notify me of this update and I will have to install it manually with adb.
Then I will have to manually re-root magisk. I can not find a way to make the magisk tutorial work so I do not have to do this manual process. I believe that Magisk modifies /vendor and /system and "to uninstall magisk with the boot_patched", to the new pixel 3 or to Android Pie does not matter to him because he knows what is happening.
ciltocruz said:
I rerooted the phone with Magisk and it's perfect.
Unfortunately, with the March update, my 3LX pixel will not notify me of this update and I will have to install it manually with adb.
Then I will have to manually re-root magisk. I can not find a way to make the magisk tutorial work so I do not have to do this manual process. I believe that Magisk modifies /vendor and /system and "to uninstall magisk with the boot_patched", to the new pixel 3 or to Android Pie does not matter to him because he knows what is happening.
Click to expand...
Click to collapse
I am confused. How can you know what is going to happen with the March update when it has not been released yet?
David B. said:
I am confused. How can you know what is going to happen with the March update when it has not been released yet?
Click to expand...
Click to collapse
Nooooo Sorry, maybe I explained wrong.
I want to say that, like in January and February, when the March update is released, the Pixel 3XL, as it is rooted, will not recognize it. It will not give me the notice of a new update.
Better like that?
ciltocruz said:
Nooooo Sorry, maybe I explained wrong.
I want to say that, like in January and February, when the March update is released, the Pixel 3XL, as it is rooted, will not recognize it. It will not give me the notice of a new update.
Better like that?
Click to expand...
Click to collapse
Oh I understand. I suppose we'll just have to wait and see. ?
David B. said:
Oh I understand. I suppose we'll just have to wait and see.
Click to expand...
Click to collapse
I installed the March update via recovery. No problem. Then I have reinstalled Magisk with the TWRP image.
I still do not know how to make this tutorial for Pixel 3 work
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Has anyone succeeded? The objective is:
- That the rooted phone detects the OTA.
- To be able to uninstall the root with the Magisk Manager application.
- To be able to install the OTA like any normal user.
- Be able to reinstall the root via Magisk Manager.
All without the need of adb, sideload, recovery, TWRP or anything "technical".
Greetings!
ciltocruz said:
I installed the March update via recovery. No problem. Then I have reinstalled Magisk with the TWRP image.
I still do not know how to make this tutorial for Pixel 3 work
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Has anyone succeeded? The objective is:
- That the rooted phone detects the OTA.
- To be able to uninstall the root with the Magisk Manager application.
- To be able to install the OTA like any normal user.
- Be able to reinstall the root via Magisk Manager.
All without the need of adb, sideload, recovery, TWRP or anything "technical".
Greetings!
Click to expand...
Click to collapse
I also had to install the update via recovery, as the option to use the built-in updater was not detecting that the update was available again. Perhaps it's time we ask @topjohnwu Magisk Queries/ @topjohnwu about this?
I've seen (and commented in) at least 4 previous threads reporting the same issue with OTA updates and none of them have been taken seriously or prompted any kind of further investigation. Oh well, 5th time lucky perhaps?
Anyway, I have exactly the same issue with my Pixel 2; I used to receive notifications for OTA updates back when I was running on Oreo with Magisk, but after updating to Pie in September 2018 I haven't received a single new OTA notification.
Pie was installed from the factory image, including a device wipe, so it was a completely fresh start. I've also tried reflashing system.img and vendor.img just in case those partitions somehow got modified at some point, but it made no difference. My device simply will not detect new OTA updates, so my only option is to sideload the update and reflash magisk every month.
As per a previous post of mine, I found other reports of the same issue on Reddit and the common factors seemed to be Pixel devices, Pie and Magisk.
nogaff said:
I've seen (and commented in) at least 4 previous threads reporting the same issue with OTA updates and none of them have been taken seriously or prompted any kind of further investigation. Oh well, 5th time lucky perhaps?
Anyway, I have exactly the same issue with my Pixel 2; I used to receive notifications for OTA updates back when I was running on Oreo with Magisk, but after updating to Pie in September 2018 I haven't received a single new OTA notification.
Pie was installed from the factory image, including a device wipe, so it was a completely fresh start. I've also tried reflashing system.img and vendor.img just in case those partitions somehow got modified at some point, but it made no difference. My device simply will not detect new OTA updates, so my only option is to sideload the update and reflash magisk every month.
As per a previous post of mine, I found other reports of the same issue on Reddit and the common factors seemed to be Pixel devices, Pie and Magisk.
Click to expand...
Click to collapse
What's odd about my situation is that when I first got the phone and rooted the image that it came with (September 2018), I did get the OTA notification. I just could not get it to install even after following the Magisk uninstallation steps provided in the official Magisk tutorial. It's only a minor inconvenience and I can live with it, but the fact that it happens still bothers me.
David B. said:
What's odd about my situation is that when I first got the phone and rooted the image that it came with (September 2018), I did get the OTA notification. I just could not get it to install even after following the Magisk uninstallation steps provided in the official Magisk tutorial. It's only a minor inconvenience and I can live with it, but the fact that it happens still bothers me.
Click to expand...
Click to collapse
This happened to me too. I put the root and the first OTA did arrive but, because I had root, I could not install. I had to do it manually with adb.
ciltocruz said:
This happened to me too. I put the root and the first OTA did arrive but, because I had root, I could not install. I had to do it manually with adb.
Click to expand...
Click to collapse
Did you try using the tutorial as well?
David B. said:
Did you try using the tutorial as well?
Click to expand...
Click to collapse
Yes, but with my rooted device the notification of NEW UPDATE does not appear. I know I can not INSTALL it, but is there also no update notice? This is what I need. An update notice.
With that warning I will be able to patch the boot image with magisk and then I will be able to download and install the OTA. Then re-rooted and ready.
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.
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Maybe Oxygen Updater has full download link?
BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.
Did you flash stock recovery to both slots the last time?
g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?
BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.