Develop Bugs

Factory Firmware or OTA

I'm just interested in people's opinion on this matter. When manually updating your phone, do you choose to Flash the Factory firmware or sideload the OTA image using adb through the stock recovery? Why do you choose that option? Just interested in others responses.
DU 9.0

I use the factory image with the -w removed. I root so need the boot.img to patch, which the factory image has and the ota doesn't.

jd1639 said:
I use the factory image with the -w removed. I root so need the boot.img to patch, which the factory image has and the ota doesn't.
Click to expand...
Click to collapse
+1 for the same reasons! Easier and more convenient IMHO.
Cheers...
Sébastien.

I'm completely stock, and plan on staying that way, so I just wait for the OTA.

bobbyphoenix said:
I'm completely stock, and plan on staying that way, so I just wait for the OTA.
Click to expand...
Click to collapse
Same here stock rooted on Android 10, I just take OTA and follow magisk steps to update and keep root. No need to ever touch a PC or patch boot.img.

For monthlies I sideload the OTA.
It is quick easy and has no impact on my current setup.
I flash factory when there is a substantial change like 9->10 or I done f*cked up and just need a do over.

parakleet said:
For monthlies I sideload the OTA.
It is quick easy and has no impact on my current setup.
I flash factory when there is a substantial change like 9->10 or I done f*cked up and just need a do over.
Click to expand...
Click to collapse
Same here. With the OTA it's no fuss, no muss. Just download the OTA and sideload it. It doesn't wipe so no need to open anything in a file editor and worry about messing something up.

I've been doing factory images each month since the original Pixel release. Sometimes I'll remove the -w, sometimes I won't.
The biggest drawback is that Google Play Music thinks its a new device every time and counts against the limit of devices. You can also only remove a few devices per year. I've had to contact support a few times to have them clear out my device list.

boostedduece said:
Same here stock rooted on Android 10, I just take OTA and follow magisk steps to update and keep root. No need to ever touch a PC or patch boot.img.
Click to expand...
Click to collapse
How do you take the OTA while rooted?
Edit: Nvm, found the tutorial. Now the question is, would that tutorial work with a custom kernel installed?

Yes, I have done it multiple times on pie and Android 10 using a custom kernel, you need to reflash the kernel though, since it gets replaced with stock.
I used to do the flash all method, now I just update from my couch, lol.
Works every time.
Edit: disable all modules before hand
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md

Would someone mind laying out the steps to take the OTA without using a PC and messing with the patched boot img?

Androider4Life said:
Would someone mind laying out the steps to take the OTA without using a PC and messing with the patched boot img?
Click to expand...
Click to collapse
Google, magisk XDA

Androider4Life said:
Would someone mind laying out the steps to take the OTA without using a PC and messing with the patched boot img?
Click to expand...
Click to collapse
Hi,
Just go to the link in the post above yours..! ?
Here it is for the lazy guys/girls:
Simply disable automatic updates in Dev options if not already > restore stock boot.img using uninstall option in bottom main screen of Magisk > take ota "without" clicking reboot now! > Go back in Magisk and select install > install to "inactive slot" > reboot> done!
Cheers,
Sébastien.

5.1 said:
Hi,
Just go to the link in the post above yours..!
Here it is for the lazy guys/girls:
Simply disable automatic updates in Dev options if not already > restore stock boot.img using uninstall option in bottom main screen of Magisk > take ota "without" clicking reboot now! > Go back in Magisk and select install > install to "inactive slot" > reboot> done!
Cheers,
Sébastien.
Click to expand...
Click to collapse
This is butter

I followed this procedure but when I exited the OTA, Magisk was gone. What step did I miss? How do I restore root? Thank you!

STraver said:
I followed this procedure but when I exited the OTA, Magisk was gone. What step did I miss? How do I restore root? Thank you!
Click to expand...
Click to collapse
Did you reboot after restoring the stock boot image and before taking the ota? Now you'll have to get the stock boot.img on your device and patch it with magisk. Then flash the patched image from your pc using fastboot.

jd1639 said:
Did you reboot after restoring the stock boot image and before taking the ota? Now you'll have to get the stock boot.img on your device and patch it with magisk. Then flash the patched image from your pc using fastboot.
Click to expand...
Click to collapse
Okay lesson learned! Thanks for responding. I did reboot after restoring stock image but not after the OTA as the directions said.

5.1 said:
Hi,
Just go to the link in the post above yours..!
Here it is for the lazy guys/girls:
Simply disable automatic updates in Dev options if not already > restore stock boot.img using uninstall option in bottom main screen of Magisk > take ota "without" clicking reboot now! > Go back in Magisk and select install > install to "inactive slot" > reboot> done!
Cheers,
Sébastien.
Click to expand...
Click to collapse
When i go into Magisk and Choose Uninstall> Restore Images, I get "Stock backup does not exist"
EDIT: Ended up just pulling a boot.img from the latest factory image, flashing that via fastoot, flashing the lastest factory image with -w removed from the flash-all.bat, patching the boot.img with magisk and flashing that patched img in fastboot.

Androider4Life said:
When i go into Magisk and Choose Uninstall> Restore Images, I get "Stock backup does not exist"
EDIT: Ended up just pulling a boot.img from the latest factory image, flashing that via fastoot, flashing the lastest factory image with -w removed from the flash-all.bat, patching the boot.img with magisk and flashing that patched img in fastboot.
Click to expand...
Click to collapse
Hello,
Strange you didn't have the backed up stock boot.img. It is located in /data if you scroll at the bottom, you should see it! :good:
{
"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"
}
Glad you got it sorted anyway!
Cheers...
Sébastien.

How To Guide TWRP + Root

Hi all. Hope you are good and safe from Covid-19.
If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP as your recovery and if you flash TWRP then you will lose root access. For the advance users, they probably already know how to do this but I haven't seen any guides so I am creating one myself.
Disclaimer:
I am a Textile engineer and do not have the slightest idea about computer engineering but my passion for computers and gadgets has taught me all this.
So, if anything happens to your device, it's not on me. I have done this on my device and it worked, so I am sharing this knowledge with you guys.
Let's cut to the chase and start our work:
Before we start, I am hoping you have your bootloader unlocked and have previous experience on flashing roms.
Step 1: Installing Stock/Xiaomi.EU/Custom rom
Go ahead and install one for your favorite roms from the threads. Luckily, Poco F3 has so many roms to choose from and they're all good.
Step 2: Installing magisk.apk
Install Magisk.apk from here
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
Step 4: Backing up your boot image
- Boot into TWRP recovery and select backup.
{
"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"
}
- Tick on boot and untick rest of the boxes.
- This will create 3 files in your TWRP folder on the phone. "boot.emmc.win" is your main file that you want to patch via magisk.
- After creating a backup of your boot image, boot into system normally.
Step 5: Patching the backed up boot image
- Open Magisk app and tap on install next to magisk.
- Now select "Select and Patch a file".
- Go ahead and select the boot.emmc.win file that is in your TWRP folder created earlier via TWRP backup.
- This is patch the boot.emmc.win and name it something like "magisk_patched-23000_randomalphanumeric.img"
- Rename the file via any file explorer to boot.img because something when the phone is plugged into the pc, your pc can't read the file. So, just to be safe, unplug the phone and re-plug to read the drive again.
- Copy this boot.img and take it to the folder where fastboot is installed/saved.
Final Step: Flashing the boot.img
- Reboot your phone to fastboot mode via pressing and holding the volume down + power buttons (or if you have custom roms installed and have the option to boot into fastboot mode directly).
- Once in fastboot mode, type following to flash the boot.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
- once the flashing is done (in about 5-10 seconds), type the following:
fastboot reboot
Click to expand...
Click to collapse
Congratulations! you now have TWRP installed as your recovery and have root access as well. To verify this you should have the below screen in your magisk app
If my guide helped you in any way, please do like it as it motivates me to write more guides to take my time out from my busy work life.
Thanks.

Very detailed and comprehensive guide indeed, however I just unlocked my almost a week now. Initially, I have 3 choices on how I will run my device after unlocking bootloader.
Either I use XiaoMi.EU testing non-root, AOSP non-root or worse can scenario I'll root and run it on stock firmware.
No I do not think that F3 users are lucky, instead I think the reality is the trend of really good coders and programmers have past. You think F3 have a huge variety of custom roms to choose? 90%+ above are based on AOSP, which I don't understand why we have 10+ AOSP roms, with only 1-2 difference. It's such a waste of time. They are only interested in making new custom roms, never in maintaining them. Always abandon project and go missing after a while. This generation is full of "enthusiasts", "wanna-be" developers most noticeable after POCO entered India's market. You can try search in YouTube, poco f3 then you will get 70-80% of tech/mobile influencers with tons of guides. The sad part is, most of them are literally talking about the same stuff, and what I hate the most they love to decorate their website with tons of ads.

Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?

pegasoc said:
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
Click to expand...
Click to collapse
No, you won't lose your data.

regedit12345 said:
...
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
...
Click to expand...
Click to collapse
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?

pegasoc said:
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
Click to expand...
Click to collapse
Yeah, once you boot from pc and "install current twrp", you dont have to do it again.

When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?

__halvar__ said:
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
Click to expand...
Click to collapse
You have to install TWRP through fastboot, look for a guide, there's a couple

still works like a charm

thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?

katcj said:
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
Click to expand...
Click to collapse
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.

regedit12345 said:
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
Click to expand...
Click to collapse
PLEASE stop patching the BOOT image
.
.
.
DIRECT INSTALL (Recommendend) is the option on your screen.
that's all you needed.
and your TWRP is OLD
please, use new officel TWRP from
and there you will find the correct instructions for installing TWRP
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com

Thank you for taking your time to contribute value to community resources!
There seem to be so many different guides and methods
I followed nebrassy's guide for TWRP
0. miflash latest stock -> flash desired rom
1. fastboot boot twrp.img (3.6 official)
2. advanced -> flash current twrp (now its permanent)
3. flash latest magisk alpha zip (usb otg or put in storage pre fastboot)
4. reboot.. launch magisk app -> update -> direct install -> reboot
5. profit

Hello. Could you help me with rooting my phone, please?
I'm on Xiaomi.eu 21.12.8 (the last android 12 weekly update). I tried flashing Magisk.zip with the TWRP but it didn't work at all.
It's like I never flashed it. So I decided to try your method to see if it would go any different, and it didn't.
I could root Evolution X (android 12), ArrowOS 11 and 12 with this method of flashing Magisk.zip on TWRP but I can't understand why it didn't worked on Xiaomi.eu 21.12.8. I could even root Xiaomi.eu 21.9.17, which was the last android 11 weekly update.
Desperate, I went to the "advanced" section of TWRP and there was an option of "Flash magisk alpha" and it ended up rooting the phone but I don't understand why the previous 2 methods didn't work.
Could you help me understand that?

Root only works with magisk canary in Android 12
Latest Magisk Canary release adds support for Android 12, drops MagiskHide
The newest update on Magisk's "bleeding edge" canary release channel brings in support for Android 12 and the new Zygisk feature. Read on!
www.xda-developers.com

Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?

Wiilsoonj said:
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Click to expand...
Click to collapse
yes the new "hide" is zygisk in the options

How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.

Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
Either use usb OTG.

Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
You can use this TWRP.
Download this: twrp-3.6.0_11-v3.2_A12-alioth-skkk.img
From this link: https://androidfilehost.com/?w=files&flid=322193
This one is able to see the internal storage of the phone with android 12. But you need to remove your screen lock to do so, you must not have a password set up so TWRP can see your internal storage, then just flash magisk normally and afterwards set up your screen lock again. Everytime you want to see the internal storage, disable screen lock. Also, you could follow the tutorial in the first post, but instead of making a backup of boot with TWRP, just use boot.image from the desired ROM, patch it with magisk and then flash the boot using adb.
Hope it helps.

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.

Cant install last version of Magisk 26.1 on my phone

When im try to download and install Magisk 26.1 on my phone nothing happend then when i close Magisk and i open again i receive this message : "Update to the full version of Magisk Manager to complete the installation. Do you want to proceed with the download and instrallation?" then i press ok and nothing happend....any tip?

roberto_1986 said:
When im try to download and install Magisk 26.1 on my phone nothing happend then when i close Magisk and i open again i receive this message : "Update to the full version of Magisk Manager to complete the installation. Do you want to proceed with the download and instrallation?" then i press ok and nothing happend....any tip?
Click to expand...
Click to collapse
It seems Magisk can´t redirect to your custom recovery. If your recovery can admit flash the latest Magisk apk as a zip, you can install it directly from there.

SubwayChamp said:
It seems Magisk can´t redirect to your custom recovery. If your recovery can admit flash the latest Magisk apk as a zip, you can install it directly from there.
Click to expand...
Click to collapse
Hi and ty for answer!
Im using custom recovery LR TWRP and i dont know if i can flash from there anyway i never had issue by updating magisk!
i saw other ppl with my same problem and seems like i can fix by unROOT and then install last magisk update 26.1 from zero!
Now im busy and cant unROOT my phone but tomorrow i will doing a fresh install and i let u know if all was good ty!!!

roberto_1986 said:
Hi and ty for answer!
Im using custom recovery LR TWRP and i dont know if i can flash from there anyway i never had issue by updating magisk!
i saw other ppl with my same problem and seems like i can fix by unROOT and then install last magisk update 26.1 from zero!
Now im busy and cant unROOT my phone but tomorrow i will doing a fresh install and i let u know if all was good ty!!!
Click to expand...
Click to collapse
Just to add more on this, waiting for your feedback, it seems to me, not an issue with Magisk itself, but with the inability of the device to be sent to recovery using scripts (Magisk is updated using recovery scripts, not on-the-go), versus the ability to boot to recovery using hardware buttons.

SubwayChamp said:
Just to add more on this, waiting for your feedback, it seems to me, not an issue with Magisk itself, but with the inability of the device to be sent to recovery using scripts (Magisk is updated using recovery scripts, not on-the-go), versus the ability to boot to recovery using hardware buttons.
Click to expand...
Click to collapse
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
{
"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"
}
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!

roberto_1986 said:
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
View attachment 5891073
View attachment 5891075
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!
Click to expand...
Click to collapse
Like device can´t sent to recovery, then no way to do it manually, because it´ll pass first for the off state, the script will be lost, probably, flashing first the app, and then flashing the zip through the recovery it is fine.
Anyway, TBH, not updating, atleast for now, won´t suppose a non-go.

roberto_1986 said:
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
View attachment 5891073
View attachment 5891075
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!
Click to expand...
Click to collapse
Ok > Direct install > "Let's go"

SubwayChamp said:
Like device can´t sent to recovery, then no way to do it manually, because it´ll pass first for the off state, the script will be lost, probably, flashing first the app, and then flashing the zip through the recovery it is fine.
Anyway, TBH, not updating, atleast for now, won´t suppose a non-go.
Click to expand...
Click to collapse
OK so u think its not worth update to 26.1 because there is nothing of relevant yet?
How about Madisk delta instead?
When i install recovery LR TWRP 3.3.1 - 1210 i can ROOT directly from there and its auto install Magisk v20.0.
Ty again for your support!!!

roberto_1986 said:
OK so u think its not worth update to 26.1 because there is nothing of relevant yet?
Click to expand...
Click to collapse
Probably, but what I´m saying is that you won´t have issues if you don´t update, only that annoying message.
roberto_1986 said:
How about Madisk delta instead?
Click to expand...
Click to collapse
Magisk is not the culprit.
roberto_1986 said:
When i install recovery LR TWRP 3.3.1 - 1210 i can ROOT directly from there and its auto install Magisk v20.0.
Ty again for your support!!!
Click to expand...
Click to collapse
I can´t remember what version I was using when succesfully updated Magisk, but, I couldn´t, the same as you, with other version.
The whole issue is that device can´t go directly to the recovery, adb reboot recovery is executed silently, but device can´t reach recovery, all resides in the recovery, try a different recovery, maybe OFR, if you care, and with the same Magisk, and you´ll see that you can.

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