Database Info

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.

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.

[flashing lineage OS] I am sitting here with a pixel 4a bootloader unlocked and get an error when I try to flash TWRP. Help please?

While trying to flash Lineage OS I'm encountering a ton of hurdles. The current guide I'm on: https://www.getdroidtips.com/resurrection-remix-google-pixel-4a/
Says I need to install some Resurrection Remix image? I think I may be missing something. The alternative is GrapheneOS which appears FAR FAR FAR FAR FAR simpler to flash onto a device. But I don't want my first step to be such a big one where I lose so much.
How to Install TWRP Recovery on Google Pixel 4a and Root it
On this page, we will guide you to install the TWRP Recovery on Google Pixel 4a (sunfish). This guide contains both the written instruct
www.getdroidtips.com
I'm following those instructions.
I am currently;
Code:
fastboot flash recovery twrpname.img
I get an error. I wish I had written it down but it was essentially command failed.
For "twrpname.img" I substituted "twrp201017-test5.img" which is the twrp image I was pointed to elsewhere.
Help would be greatly appreciated.

{
"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"
}
this is what I see

... Now when trying to flash grapheneOS I get that my android tools are too old. This is amazing.

anticlutch said:
... Now when trying to flash grapheneOS I get that my android tools are too old. This is amazing.
Click to expand...
Click to collapse
Are you on Android 11 stock? TWRP will only work on a phone with Android 10. So you will have to downgrade before flashing TWRP.
Probably easier to check out the rom section in the Pixel 4a forum than to install TWRp.

anticlutch said:
View attachment 5252207
this is what I see
Click to expand...
Click to collapse
I see a typo in that command, FYI. I don't know if that fixes your problem or not but it should probably be recovery, not recoery.
Did you download SDK Platform-Tools from here? https://developer.android.com/studio/releases/platform-tools
When I downloaded, it was platform-tools_r31.0.1-windows.zip.
This guide might be helpful if you really want TWRP (and Android 10, not Android 11): https://forum.xda-developers.com/t/guide-unlocking-downgrading-to-a10-twrp-root.4233275/
If you just want Lineage 18 then maybe follow this one: https://forum.xda-developers.com/t/...-patch-for-pixel-4a-sunfish-20210308.4208931/
I don't think TWRP is really necessary.

Question ROG 5s Update after Converting from CN to WW

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.

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.