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.
Related
I have a doubt about xposed systems on A/B partitions, for if anyone knows about this (maybe Pixel users):
Let's say you have your full setup on any slot rocking it (let's say huge modifications like xposed & maybe others (twrp, magisk/supersu, custom kernel, etc) on slot A) and suddently an OTA comes and flashes new full stock rom version on slot B and tries to run it succesfully on next reboot. And suddently after the reboot you find yourself on the updated new stock version on slot B without xposed (and without twrp&others too) in a clean instalation.
Now in this scenario..
a) slot A (which should have the xposed system you were rocking before the OTA and the succesfull slot change) is untouched or it is ruined with a copy from slot B after the succesfull boot??
b) if slot A survived untouched, can you just do a "fastboot --set-active=a" command and just reboot into the xposed system like before the OTA, or this doesnt work after the OTA and is ruined in some way?
c) if b) works (it should right.. right?), will the system try do download the OTA again asap you boot the old version on the slot A?
d) there's any way to block the Update Engine from updating, for example to wait till xposed is adapted for new version. For us Xposed users, waiting till new xposed version comes is a mantra that we have to do, and if we can't block OTAs or just undo what the Update Engine does... we're screwed?
Anyone on this scenario? I'm considering getting an A/B phone but this thing looks like a headache for anyone who likes to flash stuff and specially xposed.. since everything else you can reflash it on the new version mostly in a matter of hours/few days, xposed takes months to adapt.
I'd be glad if any Pixel xposed user could shed light onto those questions.
Thanks!
Noone seriously?
I have p2xl. I am not sure how a/b slots work for sure.
What I do know is that I have turned off automatic automatic updates under developer settings. I manually flash the stock ota image from google via twrp. Then reflssh twrp, custom kernel, and then magisk, the m ahisk installer has an Xposed built for magisk.
I usually just check google ota domtime around the 5th or 6th of each month.
smartymcfly said:
I have p2xl. I am not sure how a/b slots work for sure.
What I do know is that I have turned off automatic automatic updates under developer settings. I manually flash the stock ota image from google via twrp. Then reflssh twrp, custom kernel, and then magisk, the m ahisk installer has an Xposed built for magisk.
I usually just check google ota domtime around the 5th or 6th of each month.
Click to expand...
Click to collapse
Interesting, so if you disable automatic updates, you never turned on the phone and found a clean installation without xposed and such?
thanks!
RusherDude said:
Interesting, so if you disable automatic updates, you never turned on the phone and dounf a clean installation without xposed and such?
thanks!
Click to expand...
Click to collapse
If there is an update, it sends me a notification to ask if I want to update. And because xposed is installed I do not think it can actually follow through with the update on it's own because it breaks google's safetynet.
The only time I have turned on my phone and found it without magisk and root and xposed was when I 1st turned it on, and one time I had to do a factory restore when I did unlock bootloader because I also had to send another command that is only on pixel 2xl that to unlock_critical in addition to it. That is it.
smartymcfly said:
If there is an update, it sends me a notification to ask if I want to update. And because xposed is installed I do not think it can actually follow through with the update on it's own because it breaks google's safetynet.
The only time I have turned on my phone and found it without magisk and root and xposed was when I 1st turned it on, and one time I had to do a factory restore when I did unlock bootloader because I also had to send another command that is only on pixel 2xl that to unlock_critical in addition to it. That is it.
Click to expand...
Click to collapse
Awesome to hear
Btw, I don't think it would have a problem updating even if xposed is installing, normally the problem with incremental OTAs are if partitions are touched or not, and unlocking bootloader per se already breaks safetynet but OTAs can be installed, so safetynet is ignored, and in this A/B layout stuff would probably just be flashed on the other slot like if it had happened in the background. This is an interesting question if anyone knows it.
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...
Same problem and I didn't find any solution yet.
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli
It worked for me mate! Thank you
k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...
jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?
Worked for me too, thanks!
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader
wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.
Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse
whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.
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.
So, as title says, i'm rooted with the first october update and now i want to go with november one, but i'm rooted and of course OTA isn't working. How to correctly do it with factory image? With oneplus was easy, flash update package .zip with internal updater and then install magisk on the other slot but here is different (i think). Anyone already did it?
Thanks
Hitman478™ said:
So, as title says, i'm rooted with the first october update and now i want to go with november one, but i'm rooted and of course OTA isn't working. How to correctly do it with factory image? With oneplus was easy, flash update package .zip with internal updater and then install magisk on the other slot but here is different (i think). Anyone already did it?
Thanks
Click to expand...
Click to collapse
Hi Dude,
PIXEL-Flasher is your friend.
📳🔥PixelFlasher for Google Pixel 7 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
How to use the Pixel flasher tool is perfectly explained in the OP's!
For me the Update (Nov fact-img) worked w/o any problems inclusive keeping root! (in PixelFlasher you can patch the init_boot and will be flashed automatically)
Just updated with pixel flasher keeping root with magisk and xposed and all modules, everything works without any type of issues! Absolutely reccomended to those who have my doubts. Amazing software for pixel users!
If somebody is looking for an alternative method, check out this video tutorial.
It worked perfectly for me.
I only just got my pixel 7, but the pixel flasher way seems way more simple than that alternative method.
Well, I just updated using the pixelflasher...
That was just about as simple as it gets. I recommend!
Can you skip a monthly update using pixel flasher? Say you're on October/rooted. Could you update to December/rooted or should you update to November first?
happynexuss said:
Can you skip a monthly update using pixel flasher? Say you're on October/rooted. Could you update to December/rooted or should you update to November first?
Click to expand...
Click to collapse
hi,
yes you can go directly Oct > Dec!
Can't we just use the old way mind u haven't had any updates since I rooted but can't we I stall to a inactive slot threw magisk?
rob420p said:
Can't we just use the old way mind u haven't had any updates since I rooted but can't we I stall to a inactive slot threw magisk?
Click to expand...
Click to collapse
Unfortunately not. See https://forum.xda-developers.com/t/...vember-update-with-magisk-ota-method.4515951/
I gave it a shot going to qpr2. Freak07's solution works to recover.
rob420p said:
Can't we just use the old way mind u haven't had any updates since I rooted but can't we I stall to a inactive slot threw magisk?
Click to expand...
Click to collapse
No, because it's not working. You need to use flash-all.bat (after editing and deleting the "-w") from stock when updating and re-root. Faster than the OTA upgrade, takes less time.
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
You can update any way you want. You might find sideloading the OTA to be easiest.
The only way you can "accidentally" brick your device is if you break the bootloader by flashing the wrong image...but if you're not sure what that means, you probably shouldn't be attempting this anyway.
.
I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.
scuzzo500 said:
I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.
Click to expand...
Click to collapse
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's not bricked and is recoverable
V0latyle said:
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's
Click to expand...
Click to collapse
I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.
I definitely bet on Pixelflasher. It is idiotproof and very handy.
I like sideloading OTA's when I'm stock. A couple commands from any device with current platform tools and it's done. It's also arguably the documented "Google way". Different strokes for different folks I guess...
Thank you to everyone. I've muddled through pixel flasher and I have updated to TD1A.221105.001. Now I'll jump in the pixelflash thread and ask a few questions.
H
scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
There is no problem if you install the last update without having installed the previous updates?
alsansan said:
There is no problem if you install the last update without having installed the previous updates?
Click to expand...
Click to collapse
If It's an OTA, i supose there is no problem. If the system gives you the option. Otherwise you can avoid previous justo using flasher. If you keep your init_boot patched It's easy to root again once used the flasher.
oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Just followed your instructions and it worked flawlessly. I totally forgot this and figured I would need to reflash each time.
oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Followed your steps. It was easy and worked well.
Thank you
scuzzo500 said:
I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.
Click to expand...
Click to collapse
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.
oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
I thought the problem here was that the patching from magisk doesn't back up the boot_init (Yet). If I recall correctly pixel flasher ensured the backup being there.
That would mean next time the attempt to restore images might fail again. Unless if this issue of magisk has already been addressed. I didn't check.
fivefour said:
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.
Click to expand...
Click to collapse
That's because you don't root just to block adds.
oscarcam said:
That's because you don't root just to block adds.
Click to expand...
Click to collapse
I know plenty of other uses of root, I have developed several root apps and maintained various kernels over the years.
Read what I quoted.
I read, but I didn't understand the same. Sorry.