Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
SeeTurtle said:
Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
Click to expand...
Click to collapse
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Click to expand...
Click to collapse
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
SeeTurtle said:
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
Click to expand...
Click to collapse
Did you also flash a custom kernel?
mattie_49 said:
Did you also flash a custom kernel?
Click to expand...
Click to collapse
Yes but I reflashed the stock kernel
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
This doesn't matter
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Unfortunately still getting the same error
I am in the same situation. I only had my OP 9 for a couple of weeks and I came from a OP 5 where rooting and flashing was much easier. It would be good to know what you did to get OOS updated.
So when you download the package, you can use Oxygen Updater to install it. Choose the root package and it will install with Magisk, you will lose Twrp recovery. But you can just flash that back afterwards. Worked like a charm for me
I don't have TWRP cause it's not compatible with Android 12. I've had to factory reset the last 3 updates because of this same issue. When I had TWRP I could update with oxygen update and keep root. Being android 12 I also don't have the option to manually update via the phones update system. I don't mind factory resetting again because I have swift backup. I'd just like to know how to avoid it. Like if I could just flash it with fastboot or something
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Z-Blade said:
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Click to expand...
Click to collapse
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
SeeTurtle said:
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
Click to expand...
Click to collapse
Sweet! I have downloaded the full OTA and extracted the boot.img so I can use Magisk to patch it to get root again. I still haven't gone through the process yet but thanks for letting us know this method works. Also thanks to @illusiveairforce for leading us to the Oxygen Updater app.
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Hi,
What else should I reflash to make sure all root traces are removed ?
abl.img
aop.img
bluetooth.img
boot.img
boot.on mobile.img
cpucp.img
devcfg.img
dsp.img
dtbo.img
engineering_cdt.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
oplusstanvbk.img
oplus_sec.img
product.img
qupfw.img
qweslicstore.img
shrm.img
splash.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor.img
vendor_boot.img
vm-bootsys.img
xbl.img
xbl_config.img
Related
Can anyone upload a Magisk patched boot image for 10.0.1GM57AA? The model that I have is GM1900. When I try to patch it myself on Magisk, I get an error saying "process error"
Anyone able to help?
Heelixx said:
Anyone able to help?
Click to expand...
Click to collapse
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
meltbanana said:
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
Click to expand...
Click to collapse
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Heelixx said:
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Click to expand...
Click to collapse
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
meltbanana said:
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
Click to expand...
Click to collapse
I flashed the 4.14.117-perf+.img that you uploaded and then I booted in TWRP and flashed my original stock boot image. While still in TWRP, I flashed the zip of Magisk and then I rebooted. That got it working. So I'm rooted now. Thanks for sending me the image. I appreciate it!
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
lvints said:
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
Click to expand...
Click to collapse
I was rooted on 10.0 and then I upgraded to 10.0.1
There is a procedure for upgrading to 10.0.1 and still keeping root. I wasn't aware of this and after I got the update, I restarted my device and ended up without root access.
A Magisk patched boot image is important for getting your device rooted.
If you're asking for the procedure to root your device, then you can follow this link which explains it, https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
First off I'm not responsible for anything that happens to your device
Attached below is the patched image for OnePlus 9 global 11.2.6.6
Flash via fastboot
For support and faster answer look here
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Sorry for newbie's question, what's the difference between the two files? one is stock and one is patched?
Yes. Stock has to be flashed to take next ota. And patched is for root on current rom. Since op9 now uses google ota if any partitions are modified including the boot image ,it will fail.
Jg1234 said:
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Click to expand...
Click to collapse
When did they remove OTA install? Mine still has it....
illusiveairforce said:
When did they remove OTA install? Mine still has it....
Click to expand...
Click to collapse
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
mattie_49 said:
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
Click to expand...
Click to collapse
What are the shell commands to extract the stock boot?
Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
we are making a group for global only and help can be found there
Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
'dd' command in Linux - GeeksforGeeks
Edit- I got it, I had to flash original images and then updates showed up. Thanks for posting these images.
Hi, thanks for posting the images. I assume global as in the US AA model since that is the only model with OTA from googles server right? The reason I was asking is I am on 11.0.4.4 and never received the notification for the update yet, but using oxygen updater, when I go in settings and check advanced mode, it shows a incremental update. My system under local file of course can't see it or will not show the update. I figured I could fastboot boot the stock image and then maybe it system could see the update, but when I try, the device just hangs on the fastboot screen(right before normally booting). I tried with my image and it booted. Do you have any suggestions? Thanks
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
TheBurgh said:
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
Click to expand...
Click to collapse
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
mattie_49 said:
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
Click to expand...
Click to collapse
Appreciate the input. I have been out of the game since the 6t so I am still trying to catch up
UPDATED POST
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.*
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img**
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*this step presupposes that Magisk has a STOCK boot.img to restore for the unroot procedure. If it does not have that, you're obligated to use the process described in post #11.
**you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
So doing it this method backs up stock untouched current boot image and reflashes during uninstall of magisk to allow ota to go through.? Since the op9 uses google ota all partitions have to be stock including boot image. Or it fails
reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
this will fail
FizzyAps said:
this will fail
Click to expand...
Click to collapse
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
TheBurgh said:
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
Click to expand...
Click to collapse
Fastboot flash boot boot.img
mattie_49 said:
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks. Got the command to work this time. Tried a few times yesterday but had no luck
Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?
blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after
It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...
LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.
Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.
Thanks for the precisions, I'll know for the next time. TWRP really is awesome
hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
Click to expand...
Click to collapse
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
TheNewHEROBRINE said:
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
Click to expand...
Click to collapse
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
kevinco1 said:
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
Click to expand...
Click to collapse
I think that Magisk backups the currently flashed boot image, so if you just boot the stock image it would backup the patched image.
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
Click to expand...
Click to collapse
Update straightforward to F.62