Magisk can't find stock image, how can I upgrade and fix this issue?

[JustinChase]

I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)


I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...


(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)


...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.


Thanks in advance for any help/guidance doing so.

 

[Nimueh]

Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol

XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it

 

[JustinChase]

Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol

XDA didn't like the .img ending so I had to rename it to .zip - just remove that and you'll be good.

I've never done it that way myself. By just restoring images in magisk, I can do a "normal" update, from settings, and it will download just the update, in this case, about 700MB, then Install to inactive slot in Magisk and done.

This avoids me needing to find the full update to download. Probably not a big deal, but this has always worked fine in the past.

I guess i just installed Magisk incorrectly the last time I wiped, which is now causing me this issue.

I appreciate your suggestion, and perhaps that is the better way moving forward.

I didn't see your attachment, but as I'm typing this, i see you edited to say you renamed it, so I'll see if I see it now.

Thank you for your help.

 

[JustinChase]

Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol

XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it

I just downloaded it, thank you again!

 

[Primokorn]

Note: I've never upgraded this device.

Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933

 

[JustinChase]

Note: I've never upgraded this device.

Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933

Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.

Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.

 

[Primokorn]

Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.

Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.

OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol

 

[JustinChase]

OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol

It normally does, but I apparently installed it 'abnormally' last time, so I didn't have/save the stock boot image.

I just need to research the best way to get the downloaded stock image onto my phone so that Magisk knows and can use it, without screwing something up, and having to wipe and reinstall everything (again).

I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.

 

[Nimueh]

I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.

Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:

• Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
• Vivo S16, S15, S6, X70, X60 and X30 series.
• The Pixel 6 and Pixel 7 series.
• Any vehicles that use the Exynos Auto T5123 chipset.

 

[JustinChase]

Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:

• Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
• Vivo S16, S15, S6, X70, X60 and X30 series.
• The Pixel 6 and Pixel 7 series.
• Any vehicles that use the Exynos Auto T5123 chipset.

I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.

I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.

 

[Nimueh]

I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.

I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.

I don't use my device much and mostly at home on my wifi, so I'm not overly worried. I'm still on the last OOS 11 version mysel, mostly because 1 mod I use only exists for OOS 11. I'm sure I'll update eventually but for now I'm ok with old security patches.
#priorities and all that