Pixel 3 rooted with Magisk - OTA is being downloaded? - Google Pixel 3 Questions & Answers

My Pixel 3 is rooted with Magisk, but I did not install TWRP.
Root is available:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yet, the phone is offering an update:
Since I took this screenshot, the download has completed, and it is offering to install it.
My understanding is that OTA would not happen if the phone is bootloader unlocked and rooted.
Should I let it install this update? How can I find out exactly which update it is? I'm assuming it would be (PQ3A.190605.003, Jun 2019), but how can I confirm?
Where is this 1.2 Gb file stored on the phone once it downloads? I found posts saying it was at root level in folder /cache, but it is not there. Maybe it moved for Android 9? I tried to use Solid Explorer to find files > 1 Gb, but it did not find anything.

I was also surprised today, but let it install. Lost the root afterwards.

moldovanos said:
Lost the root afterwards.
Click to expand...
Click to collapse
Did you have any issues re-establishing root with Magisk after installing the update?
Which version of Magisk? Latest 19.3?

timg11 said:
Did you have any issues re-establishing root with Magisk after installing the update?
Which version of Magisk? Latest 19.3?
Click to expand...
Click to collapse
Rebooted into bootloader, fastboot TWRP, flashed latest 19.3 and that's it. Everything is back to normal

timg11 said:
My Pixel 3 is rooted with Magisk, but I did not install TWRP.
Root is available:
Yet, the phone is offering an update:
Since I took this screenshot, the download has completed, and it is offering to install it.
My understanding is that OTA would not happen if the phone is bootloader unlocked and rooted.
Should I let it install this update? How can I find out exactly which update it is? I'm assuming it would be (PQ3A.190605.003, Jun 2019), but how can I confirm?
Where is this 1.2 Gb file stored on the phone once it downloads? I found posts saying it was at root level in folder /cache, but it is not there. Maybe it moved for Android 9? I tried to use Solid Explorer to find files > 1 Gb, but it did not find anything.
Click to expand...
Click to collapse
Disable auto update in developer options and profit!

Related

failed update :(

So i am trying to update my phone for a few days with the latedt push OTA (6.0)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And when the system reboots, it brings me to the TWRP Bootloader screen.. even if i push the reboot to system button, the update failed to be applied.
Any tips?
(ElementalX Kernel, TWRP & SuperSU - Stock 6.0)
Edit: Sorry for the picture size, i have no idea how to resize)
SebLemery said:
So i am trying to update my phone for a few days with the latedt push OTA (6.0)
And when the system reboots, it brings me to the TWRP Bootloader screen.. even if i push the reboot to system button, the update failed to be applied.
Any tips?
(ElementalX Kernel, TWRP & SuperSU - Stock 6.0)
Edit: Sorry for the picture size, i have no idea how to resize)
Click to expand...
Click to collapse
You have to be stock to update OTA. No special recovery and no root
funnel71 said:
You have to be stock to update OTA. No special recovery and no root
Click to expand...
Click to collapse
So, how can i make sure this message does not appear anymore, or can i just flash the latest image from code.google.com with the update included somehow, and everything will restore like it does now?
(sorry for the uestions, im no pro just yet)
SebLemery said:
So, how can i make sure this message does not appear anymore, or can i just flash the latest image from code.google.com with the update included somehow, and everything will restore like it does now?
(sorry for the uestions, im no pro just yet)
Click to expand...
Click to collapse
You can't flash any official OTAs with TWRP. It's a known fact, nothing you can do about it. Reflash stock recovery, or just use a close to vanilla custom ROM that gets the monthly security updates.

Android 10 root issues?

I updated my pixel 2 to the Android 10 stable release this evening .
First thing I did afterwards was root with magisk .
I pulled the boot file, patched it and flashed it.
I opened magisk everything is checked , used Root check app. That came back positive.
However when I try to modify my host file and install my custom host file I get error messages saying " Can't delete file" .
I tried both root explorer and solid explorer both apps have root access . But can't modify the system files.
I'm starting to thing that I'm getting a false positive on root or something has changed in Android 10 and we can no longer modify system files.
I tried both the stable version and canary version builds of magisk . Both say that I'm rooted but the issue persists .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 2 using Tapatalk
I saw on another thread after you boot twrp in adb, mount everything as read only and then reinstall twrp and magisk zips thru the recovery. I used most recent versions of twrp and magisk and didn't need to alter the zips in any way. I'll see if I can find the thread....
Couldn't link the thread, so here's a ss
donlu30 said:
Couldn't link the thread, so here's a ss
Click to expand...
Click to collapse
Thanks for the quick reply I don't have. Install a custom recovery in a 2 years lol but it thats what's required to get root to work on the pixel 2 with Android 10 then I'll have to do it
Sent from my Pixel 2
I'm having no problem with IanMacd Magisk repo, link below, check readme on bottom of page for instructions on how to configure Magisk for a custom repo.
https://github.com/ianmacd/MagiskBuilds/
ACHILLES R32 said:
Thanks for the quick reply I don't have. Install a custom recovery in a 2 years lol but it thats what's required to get root to work on the pixel 2 with Android 10 then I'll have to do it
Sent from my Pixel 2
Click to expand...
Click to collapse
You can just boot the recovery if you don't want to install it permanently.
Sent from my Pixel 2 using Tapatalk
Thank you for all the replies, turns out I was rooted but I just couldn't write to system. I ended up installing energized pro module for magisk to modify my host file. No more ads lol
Sent from my Pixel 2
I could also root my pixel 2 with canary_magisk but, although its says rooted, some apps say couldn't find the root binary's. Going back to Android 9
So I seem to have an issue with solid explorer. I go in and remove gmail and other google stuff I don't use typically. Solid gets permissions and when I go to delete the gmail folder it errors out. Not certain if this is a root issue with Magisk or perhaps more likely an issue with apps that need root...

Cannot find updates on rooted phone

Hello,
I have a rooted EU phone (4a, not the 5g version). The OTA updater does not find the security updates, and all the rooting guides seem to indicate that they should show.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can I check what's going on?
Long, more detailed version:
I have rooted my Pixel 4a (using Magisk). I think I have done things right¹, but my phone seems to be unable to find the November security update. I thought it was just a lag in the rollout of the update, but I got a message warning me that "it has been two weeks and I haven't installed the update yet".
When I go to Settings → System → Advanced → System update, it tells me my system is up to date, with Android 11 and the security update from the 5th October 2020.
I have tried removing Magisk to no avail, the update still does not show.
Does anybody know what's happening, or what I am missing?
¹ For what it's worth, the flashed version of the OS is sunfish-rp1a.201005.006 (using the flash-all.sh, then I have flashed the bootloader that came with it, patched with Magisk Manager beforehand).
You will need to flash back the stock boot.img and then search for updates, as if you mess with that (you did by rooting) you wont get OTA updates.
Thanks. I'll try that once I've figured how to do a full system backup.
You could simply sidleload the ota since you know it's there
Beware u will need to repatch your boot.img to have root again after applying the dec ota update.
I just tried sideloading the december OTA update (201205.008). It seemed sucessful from adb, but got stuck on the boot animation for a few minutes, and I ended up force-rebooting the phone. When the operating system started, I was still on 201005.006.
To be completely honest, I'm far too unfamiliar with the Android flashing and boot process to be confident in anything I'm doing here. I'm fairly comfortable with Linux and its boot process, but Android albeit similar is too different. I need to read up on that.

Unable to update oxygenOS after unbricking

So I have become member of the bricked-my-phone family. I have followed this tutorial https://www.getdroidtips.com/unbrick-oneplus-6/ and successfully unbricked it.
I have downloaded latest oxygen os (I tried two latest - one with android 11 and one with android 10), I have added the zip to the root directory and from system update I selected it, but in both cases I instantly get "System update installation failed" at 0%. It also says I am up do date from OTA (it it android 8.1 lol)
what should I do?
I want to install latest oxygenOS only for firmware, then I will be installing LineageOS again. I am afraid If I do it the other way around (LOS first than firmware) I will brick it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.
mm_rajesh said:
Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.
Click to expand...
Click to collapse
That's exactly what I did and the result, you see on screenshot..
But later in the evening, I found the solution here https://forums.oneplus.com/threads/oneplus-6-system-update-installation-is-failed.1314311/:
The OP6 must be on 9.0.9 before upgrading to Android 10.
You are still on Oreo/Android 8.
There is a link for 9.0.9 on this website:
https://www.getdroidtips.com/download-oxygenos-9-0-9-9-0-17-update-for-oneplus-6-and-6t/
Click to expand...
Click to collapse
If you are able to boot to Fastboot as well as able to unlock bootloader than do unlock the bootloader and flash this msm file
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
And after that reboot to recovery stock and factory reset. This will fix your issue than after lock the bootloader(if it's unlock after flashing the file) and update to latest rom (download the rom from oneplus updater app with advance setting "on")

Question Stuck in Download Mode: Error verifying vbmeta image

Hey there,
I have a problem with my A52 (SM-A525F/DS): It doesn't boot anymore, as it is stuck in the Download mode, showing the error message: "Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)"
Steps that lead to this:
LineageOS is installed. After installation of a software update, Magisk lost its root. So I tried to install an alternative recovery (TWRP) with Odin. Odin said "Pass", but now this error message occurs.
What can I do now to make the phone work again? Install the Stock ROM?
Would you please help me with this issue? Thank you so much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once again, you need to properly follow all the instructions listed on the thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/
Thank you and please excuse my stupidity.
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
fheba said:
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
Click to expand...
Click to collapse
Not automatically. You would have to reflash magisk every time you install an OTA.
deleted
Simon1511 said:
Not automatically. You would have to reflash magisk every time you install an OTA.
Click to expand...
Click to collapse
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
fheba said:
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
Click to expand...
Click to collapse
The problem is encryption. On the A5 2017 the Magisk re-install script would run after installing an OTA and would install itself again. But since encryption is enabled by default on newer phones (such as the A52) it doesn't work/behave correctly.
I'm fairly sure though it's an issue with Magisk and not with the ROM.

Categories

Resources