Develop Bugs

[RECOVERY][unofficial][anthias / zenwatch] TWRP 3.0.2

TWRP recovery 3.0 zenwatch
How to install ​Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!​
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"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"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master

acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install ​
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!

btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.

Ups , i fix this today ...
Sorry

hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry

Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.

CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!

Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.

Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.

itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.

hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)

itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)

Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..

Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).

Boooooo moto 360. It's sooo damn big.

@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).

itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github

Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2

Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.

I need a link to the stock recovery.IMG file

Install OTA with root

I have a doubt. What should I do if I have magisk installed and I want to update by OTA?

Ruvahkiin said:
I have a doubt. What should I do if I have magisk installed and I want to update by OTA?
Click to expand...
Click to collapse
1. Update and DONT reboot.
2. In magisk: install --> install to inactive slot (after OTA)
3. Reboot.

Shouldn't it be like this?
1.Turn off all modules in Magisk
2.Uninstall Magisk / Restore Image /DON'T Reboot
3.Install OTA / DON'T Reboot
4.Start Magisk Manager and click Install to inactive slot / Reboot.
Because if you update before restoring stok boot.img your phone gets many many problems and perhaps you must perform factory reset to let it work properly after OTA.
Tapatalk via OnePlus 7T

Riski3Run said:
Shouldn't it be like this?
1.Turn off all modules in Magisk
2.Uninstall Magisk / Restore Image /DON'T Reboot
3.Install OTA / DON'T Reboot
4.Start Magisk Manager and click Install to inactive slot / Reboot.
Because if you update before restoring stok boot.img your phone gets many many problems and perhaps you must perform factory reset to let it work properly after OTA.
Tapatalk via OnePlus 7T
Click to expand...
Click to collapse
No. You can do it like you said but it's not necessary.
I heard on other phones you will get issues but not with OnePlus.

I just uninstall magisk and leave modules installed, update, install magisk to inactive slot, reboot.

I did not uninstall Magisk, just disabled the one module that I was using. My steps:
In Magisk Manager: Disable all Magisk modules, reboot
Install OTA update / DON'T Reboot
Open Magisk Manager: click on Install/Install/Direct Install, DON'T Reboot
Once again in Magisk Manager: click on Install/Install/Inactive Slot
Reboot

Kollachi said:
1. Update and DONT reboot.
2. In magisk: install --> install to inactive slot (after OTA)
3. Reboot.
Click to expand...
Click to collapse
Can you confirm this works with the 10.0.12 update? I'm honestly confused because every answer is different.
And also, should I let my phone download the whole update, which it wants me to because it detects the root, or should I do only the OTA via Oxygen Updater?
Thanks in advance.

kaeptn1 said:
Can you confirm this works with the 10.0.12 update? I'm honestly confused because every answer is different.
And also, should I let my phone download the whole update, which it wants me to because it detects the root, or should I do only the OTA via Oxygen Updater?
Thanks in advance.
Click to expand...
Click to collapse
Mine was from 10.0.11 to 10.0.12 HD65AA. I let the phone update though the OTA. Root was detected and it downloaded the entire update, i proceeded with install, just did not reboot when it completed.

I am also getting confused now...
Someone says if we are rooted we won't get OTA but full ROM update.
Tell me what I have OTA or full ROM update? (see screenshot) Which steps with Magisk must I take to update from 10.0.11HD65BA to 10.0.12HD65BA without loosing any data.
Thanks in advance.
{
"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"
}
Tapatalk via OnePlus 7T

Riski3Run said:
I am also getting confused now...
Someone says if we are rooted we won't get OTA but full ROM update.
Tell me what I have OTA or full ROM update? (see screenshot) Which steps with Magisk must I take to update from 10.0.11HD65BA to 10.0.12HD65BA without loosing any data.
Thanks in advance. View attachment 5077859
Tapatalk via OnePlus 7T
Click to expand...
Click to collapse
2.6 GB is the full rom.
As it was written:
- Disable all modules, reboot
- Do the full download as suggested and the upgrade via system updater and DO NOT REBOOT
- install magisk to inactive slot, reboot
- boom Chaka laka!
Gesendet von meinem HD1903 mit Tapatalk

So no need to restore first via Magisk stock boot.img coz update will overwrite to stock anyway?
I am so "scared" coz last time I did wrong from 10.01.09 to 10.01.10 and I had to factory reset and waste whole day to install everything again and root it again.
Edit:
I don't have TWRP so after update must simply flash via fastboot magisk_patched.img 10.0.12HD65BA or what?
Tapatalk via OnePlus 7T

Updated from 10.0.11 to 10.0.12 and all I did was:
1. Disable all magisk modules
2. Updated from normal ota, didn't reboot
3. Back to magisk manager and click on Install/Install/Direct Install
4. Again in magisk manager click on Install/Install/Inactive Slot
5. Reboot
6. Activate all modules.
Done no patching no nothing

danielud said:
Updated from 10.0.11 to 10.0.12 and all I did was:
1. Disable all magisk modules
2. Updated from normal ota, didn't reboot
3. Back to magisk manager and click on Install/Install/Direct Install
4. Again in magisk manager click on Install/Install/Inactive Slot
5. Reboot
6. Activate all modules.
Done no patching no nothing
Click to expand...
Click to collapse
3. Step isn't needed because OTA will install to the other partition and your active one will be untouched. And I personally didn't deactivate modules.
---------- Post added at 12:50 PM ---------- Previous post was at 12:43 PM ----------
Riski3Run said:
I don't have TWRP so after update must simply flash via fastboot magisk_patched.img 10.0.12HD65BA or what?
Tapatalk via OnePlus 7T
Click to expand...
Click to collapse
You can also do this:
1. fastboot boot magisk_patched.img
2. Magisk manager --> Install --> install --> direct install
3. Reboot
With this method you wont get bootloops or anything. Because if you boot the image only it's not temporary. That's why you install in magisk manager.

Question [CLOSED] POCO F3 GLOBAL STUCK ON BOOT LOGO. HELP NEEDED.

Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, NFC did not work for me even on stock bl locked firmware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.

just flash a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there

metalspider said:
just faslh a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
Click to expand...
Click to collapse
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.

Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
{
"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"
}
Free phones welcomed.

pl1992aw said:
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
Free phones welcomed.
Click to expand...
Click to collapse
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.

Ghostface009 said:
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Click to expand...
Click to collapse
As you wrote earlier, you had root access before MIUI update.
Once you get root, use Debloater to debloat the updater.
Code:
com.android.updater
is one of it.
Maybe there's other ones, but I don't have this phone, can't tell much about it.

Ghostface009 said:
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
Click to expand...
Click to collapse
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?

Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.

Issue solved after flashing unmodified boot.img, thanks all.
laid1995 said:
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Click to expand...
Click to collapse
Unfortunately it doesn't boot, I entered the fastboot command and it's just a black screen. I guess this doesn't work with MIUI 12.5.1, and that means Im stuck without root thanks to xiaomi
I also tried the adb command to remove magisk modules, didn't work, says inaccessable or not found

Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.

Alin45 said:
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Click to expand...
Click to collapse
...But they did tho
The phone boots now, but still, I lost magisk and now I cannot install it on this update.
The phone also can't pass safetynet for some reason, despite having stock boot.img restored and leaving no trace of magisk.
All that could've been avoided if the device just did as it was told to, not to automatically update itself.

reg66 said:
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Click to expand...
Click to collapse
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails

Ghostface009 said:
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Click to expand...
Click to collapse
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?

Alin45 said:
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Click to expand...
Click to collapse
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.

Ghostface009 said:
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Click to expand...
Click to collapse
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol

Alin45 said:
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Click to expand...
Click to collapse
Maybe due to the difference between global and eu roms
Ik you gave all you can but what would you suggest to do for my situation in order to root this phone and pass safetynet again?

have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here

Download the TWRP again.
Follow the guide with pictures: https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs steps up to step 13. Ignore step 8, 9 and the flash part of 12.
If this way still can't get you TWRP, then you might want to try latest MIUI by Xiaomi.eu. Read somewhere it has built in TWRP, so once flashed, you have TWRP. Verify yourself by reading in other posts though.
Remember
EEA (official) is different from Xiaomi.eu (custom ROM)
Click to expand...
Click to collapse

reg66 said:
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Click to expand...
Click to collapse
yep, the one I used was '2' version. I double checked for corruption and downloaded the same twrp again with same result :/

pl1992aw said:
Do Clean Flash custom ROMs
Click to expand...
Click to collapse
So my only way to get magisk again is flashing custom roms? it is how it is? :/

Question installation failed w/ magisk active (pixel 6 pro, magisk v24.3)

I'm always getting this error while i trying to download & install updates via the pixel updater.
It always returns "Installation failed"
Im currently downloading the ota & sideloading it and reflashing the latest stock boot to re root.
Is there any fix to just use magisk ota patcher instead of the workaround im using?
{
"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"
}

Venipa said:
I'm always getting this error while i trying to download & install updates via the pixel updater.
It always returns "Installation failed"
Im currently downloading the ota & sideloading it and reflashing the latest stock boot to re root.
Is there any fix to just use magisk ota patcher instead of the workaround im using?
Click to expand...
Click to collapse
You pretty much have to be completely stock to use the "Install to Inactive Slot" method (except being rooted with Magisk of course). That means no modifications of /system, /vendor, etc.. Having a custom kernel will also make it fail because dtbo, vendor_boot & vendor_dklm images are usually modified with custom kernels on the Pixel 6 series. Any modifications like these will make the pre-OTA verification check fail and thus the installation fail.
Also, if you are using Canary versions 24304/5, it's been reported that these versions aren't playing well with the "Install to Inactive Slot" method for the March and April builds.

Lughnasadh said:
You pretty much have to be completely stock to use the "Install to Inactive Slot" method (except being rooted with Magisk of course). That means no modifications of /system, /vendor, etc.. Having a custom kernel will also make it fail because dtbo, vendor_boot & vendor_dklm images are usually modified with custom kernels on the Pixel 6 series. Any modifications like these will make the pre-OTA verification check fail and thus the installation fail.
Also, if you are using Canary versions 24304/5, it's been reported that these versions aren't playing well with the "Install to Inactive Slot" method for the March and April builds.
Click to expand...
Click to collapse
im on stock + magisk 24300, it still showed the (ota) install failed error
edit: could it be that the "Universal SafetyNet Fix" module could alter system or smth related to the pre-ota verification process?

Venipa said:
im on stock + magisk 24300, it still showed the (ota) install failed error
Click to expand...
Click to collapse
Not really sure then. Since that method was re-added to Magisk (in January I believe), it seems to be hit or miss for a lot of folks.

Venipa said:
edit: could it be that the "Universal SafetyNet Fix" module could alter system or smth related to the pre-ota verification process?
Click to expand...
Click to collapse
Anything is possible. Try all Magisk Modules disabled, then reboot, and then try it again.

roirraW edor ehT said:
Anything is possible. Try all Magisk Modules disabled, then reboot, and then try it again.
Click to expand...
Click to collapse
I'll try that on the next update

roirraW edor ehT said:
Anything is possible. Try all Magisk Modules disabled, then reboot, and then try it again.
Click to expand...
Click to collapse
new update dropped and yet the issue persists, i've disabled magisk modules and it still happened
i guess its time to manually flash the update again :sigh:

Venipa said:
new update dropped and yet the issue persists, i've disabled magisk modules and it still happened
i guess its time to manually flash the update again :sigh:
Click to expand...
Click to collapse
If I were in your shoes, I would first try updating using the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own), and choose the option to not wipe (and don't flash all partitions, and don't relock the bootloader). And then try rooting using Magisk Stable v24.3. The Android Flash Tool has fixed many folks' problems, even when manually flashing the full firmware zip didn't fix the problem.
Good luck!

roirraW edor ehT said:
If I were in your shoes, I would first try updating using the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own), and choose the option to not wipe (and don't flash all partitions, and don't relock the bootloader). And then try rooting using Magisk Stable v24.3. The Android Flash Tool has fixed many folks' problems, even when manually flashing the full firmware zip didn't fix the problem.
Good luck!
Click to expand...
Click to collapse
Ah that's not what I meant, I've already everything setup to manually patch the ota without wiping my data. It's just inconvenient to do the ota and downloading the stock firmware to patch only the boot again for magisk.

How To Guide OxygenOS 13.1 (LE2125_13.1.0.500) for global with boot.img files

Hi,
I share with you the files for those who want to update from F21 to Android 13.1 and root the phone.
LE2125 OxygenOS 13.1.0.500
For those who get the message that the backup does not exist when uninstalling magisk by selecting image restore, you will not be able to install the update by uninstalling magisk completely , it will fail.
Here's how to do.
-uninstall magisk by selecting uninstall completely
- once the phone restarts, restart in fastboot mode
- flash the original F21 version boot image (9Pro_F21_Global ) by typing these two command lines
fastboot flash boot_a original_F.21_boot.img
fastboot flash boot_b original_F.21_boot.img
- restart the phone
-now you can install the update (you will need this apk to install the update OPLocalUpdate_For_Android13.apk)
- once the update is installed, you can root the phone.
{
"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"
}

Thanks for share

this update available for op9? if yes then can you provide me link of this latest ota?

Daniha said:
this update available for op9? if yes then can you provide me link of this latest ota?
Click to expand...
Click to collapse
NO, for op9 pro...don't use them for op9.

buu'buu said:
NO, for op9 pro...don't use them for op9.
Click to expand...
Click to collapse
no no I'm asking for this ota rom for op9?

@Daniha
Sorry, I don't have the op9, you have to wait OnePlus or Oxygen Updater provide it.

buu'buu said:
Hi,
I share with you the files for those who want to update from F21 to Android 13.1 and root the phone.
LE2125 OxygenOS 13.1.0.500
For those who get the message that the backup does not exist when uninstalling magisk by selecting image restore, you will not be able to install the update by uninstalling magisk completely , it will fail.
Here's how to do.
-uninstall magisk by selecting uninstall completely
- once the phone restarts, restart in fastboot mode
- flash the original F21 version boot image (9Pro_F21_Global ) by typing these two command lines
fastboot flash boot_a original_F.21_boot.img
fastboot flash boot_b original_F.21_boot.img
- restart the phone
-now you can install the update (you will need this apk to install the update OPLocalUpdate_For_Android13.apk)
- once the update is installed, you can root the phone.
View attachment 5914697
View attachment 5914699
View attachment 5914703
Click to expand...
Click to collapse
Thanks for the info... unfortunately I don't have a computer but, what I do is install F21 stock boot image using Ex Kernel manager and after doing that it allows me to install the update. It's doing the same thing that flashing thru fastboot does except I'm just flashing the stock boot image with a kernel flasher...

TENlll423 said:
Thanks for the info... unfortunately I don't have a computer but, what I do is install F21 stock boot image using Ex Kernel manager and after doing that it allows me to install the update. It's doing the same thing that flashing thru fastboot does except I'm just flashing the stock boot image with a kernel flasher...
Click to expand...
Click to collapse
Thanks, i'll test that at next update.

It keeps displaying: System update installation failed at 0% progress. I have removed magisk completely

Pourek said:
It keeps displaying: System update installation failed at 0% progress. I have removed magisk completely
Click to expand...
Click to collapse
Are you using the System update application? (system update apk.for Android 12)
If not use that...
Also, if you have TWRP installed that will keep the update from working correctly you'll have to install the stock boot image in a kernel manager like EKM. Besides that I'm not sure what else would cause that.. I just updated no problem it took like 2 minutes I didn't even have to flash my stock boot image this time. I thought I would have to after reading
Buu buu's post earlier.

TENlll423 said:
Are you using the System update application? (system update apk.for Android 12)
If not use that...
Also, if you have TWRP installed that will keep the update from working correctly you'll have to install the stock boot image in a kernel manager like EKM. Besides that I'm not sure what else would cause that.. I just updated no problem it took like 2 minutes I didn't even have to flash my stock boot image this time. I thought I would have to after reading
Buu buu's post earlier.
Click to expand...
Click to collapse
I am, i'm probably just going to factory reset and apply the update

Can we assume that updating to this, if rooted, can take the usual route?
1. Restore images in magisk
2. Download update in oxygen updater.
3. Install the update using that other update tool, not the system one.
4. Install magisk to inactive stlot
5. And only then reboot?

nabril15 said:
Can we assume that updating to this, if rooted, can take the usual route?
1. Restore images in magisk
2. Download update in oxygen updater.
3. Install the update using that other update tool, not the system one.
4. Install magisk to inactive stlot
5. And only then reboot?
Click to expand...
Click to collapse
Yeah and I guess you can skip "Restore images" part.
At least I did that every time i updated OSS before I went to a custom rom.

Smedslund said:
Yeah and I guess you can skip "Restore images" part.
At least I did that every time i updated OSS before I went to a custom rom.
Click to expand...
Click to collapse
I was asking about those of us on OOS.

nabril15 said:
I was asking about those of us on OOS.
Click to expand...
Click to collapse
I was on OSS until 2 weeks ago. But nvm.

Did you buy a 2125 model in Europe or are you from Canada?

Thank you for sharing this! How can I use this without root. Thank you

naxos said:
Thank you for sharing this! How can I use this without root. Thank you
Click to expand...
Click to collapse
Can you tell me what exactly you want to do. Version installed? Root?

buu'buu said:
Can you tell me what exactly you want to do. Version installed? Root?
Click to expand...
Click to collapse
Thank you for your time to answer me, I want to install just the new version. My firmware version is LE2123_11.F.75_2750_202303081536
Thanks