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.
Related
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.
Successfully Done
✓ bootloader unlock
✓ TWRP Recovery twrp-merlin-2.8.7-r7.img
All most try all super user
{
"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"
}
but after flash super user zip phone stop work at bootloader warning
same thing happen to me too..plz someone answer.
Prior to flashing supersu.zip, open twrp>advanced>terminal and enter (without quotes) enter the command
Code:
"echo SYSTEMLESS=true>>/data/.supersu"
Now SuperSU would install in systemless mode. The latest betas automatically install in systemless mode (I am using 2.74). Check if now it works.
Broadcasted from Zeta Reticuli
@Gravemind2015 is correct, that is the command needed to make it work... note that since you already tried flashing several SuperSU versions the old way, if it continues to be a problem you may need to reflash the factory images and verify booting prior to trying the mentioned systemless method.
mindjek07 said:
...after flash super user zip phone stop work at bootloader warning
Click to expand...
Click to collapse
I had the exact same issue on my 16 GB xt1540, running stock, fresh 6.0. Trying to root with SuperSU's (over TWRP), several versions up to 2.74, earlier versions down to 2.4 ish... I'd freeze at boot logo every time, after what appeared to successful installs.
After reading somewhere about someone else's luck, I gave 2.65 a go, a version I must not have tried (and one I notice is not on your screen shot), and it worked. I certainly didn't expect it to, and obviously it could be completely coincidental. I'm pretty sure, however, that I did nothing differently on that install to what I had done other times.
HTH
Buena suerte
Love you!!!
You pacified my pain.
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!
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")
I have been trying to update my phone for a while now but for some reason I am unable to, when I got the phone I followed this guide to convert it from CN to WW, and it worked well
But right now I am stuck at at version 18.1220.2109.126,
Every time I try to update to android 12 I am greeted with this
{
"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"
}
if anyone could help me with this I would be really grateful, no matter what version I use I am always getting the same message
Update incrementally up to the version you want to get to.
Andrologic said:
Update incrementally up to the version you want to get to.
Click to expand...
Click to collapse
its not working man, i almost tried every firmware
Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com
twistedumbrella said:
Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried both, but every time I try to run a script, be it flash raw or the flash_all, I keep getting waiting for devices, even though my phone is connected to my pc(through the side port) and is in fastboot/bootloader.