How To Guide [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13-F13/F74

[RASTAVIPER]

no short way for temporarily root?

You mean other than the adb way with the flash boot command?

 

[Andsie]

No - I am searching for the shortest way for temporarily root - preferring no steps for unrooting afterwards...

 

[HorizonZero]

Hi everyone,
quick question. I might have missed the same question in a previous contribution. Can I do the same process on a OnePlus 9 not pro? I have a 9 that I've never moved to Android 12 so still 11 and I'm thinking now to directly skip the 12 and go to 13 but keeping my root on with magisk.

Is it possible to do so? If I'm in the wrong thread can someone indicate me the right way to procede?
Thank you

 

[Fishawy]

Hi everyone,
quick question. I might have missed the same question in a previous contribution. Can I do the same process on a OnePlus 9 not pro? I have a 9 that I've never moved to Android 12 so still 11 and I'm thinking now to directly skip the 12 and go to 13 but keeping my root on with magisk.

Is it possible to do so? If I'm in the wrong thread can someone indicate me the right way to procede?
Thank you

Hey there,

Not sure if it's the same, but I couldn't update directly from 11 to 13 on my 9 Pro. Had to jump through OOS12 which is apparently a stepping stone that cannot be skipped. I would just follow the phone prompted updates.

 

[HorizonZero]

Hey there,

Not sure if it's the same, but I couldn't update from 11 to 13 on my 9 Pro directly. Had to jump through OOS12. I would just follow the phone prompted updates.

Hi man, thank you for greeting me in this conversation.

I just want to add that I once tried ( some time ago ) to upgrade to OOS 12 with poor results and bricking my phone. Never had problems before. I managed to solve the problem but now I'm a bit worried to do some mistake I don't understand and not able to go back. ( not really a programmer here, just a nerd that likes to retrain control of his phone xD )

 

[Fishawy]

Hi man, thank you for greeting me in this conversation.

I just want to add that I once tried ( some time ago ) to upgrade to OOS 12 with poor results and bricking my phone. Never had problems before. I managed to solve the problem but now I'm a bit worried to do some mistake I don't understand and not able to go back. ( not really a programmer here, just a nerd that likes to retrain control of his phone xD )

I've had all kinds of problems with OOS12, which made me roll back to OOS11 for a while. However when trying to flash the OOS13 zip directly from OOS11 using the OPLocalUpgrade apk, it failed.

I didn't 'stay' on OOS12 per se. Just followed the updates (11.2.10.10, then C48 which was prompted by the system, then C63, and then OOS13 zip using the OPLocalUpgrade apk).

Keep in mind that this was on 9 Pro, I'm not sure if the same thing applies to the 9 non-pro. You might wanna test it by trying to flash OOS13 directly if you have the zip.

 

[Steve0007]

Hi man, thank you for greeting me in this conversation.

I just want to add that I once tried ( some time ago ) to upgrade to OOS 12 with poor results and bricking my phone. Never had problems before. I managed to solve the problem but now I'm a bit worried to do some mistake I don't understand and not able to go back. ( not really a programmer here, just a nerd that likes to retrain control of his phone xD )

Same as Oneplus 9 Pro. Just flash the full OTA prompted by the system upto latest OOS 13. Get the latest OOS OTA file, grab the original boot using payload exe, patch the boot with magisk and get the temporary root access in order to patch your boot directly using magisk application

 

[HorizonZero]

I've had all kinds of problems with OOS12, which made me roll back to OOS11 for a while. However when trying to flash the OOS13 zip directly from OOS11 using the OPLocalUpgrade apk, it failed.

I didn't 'stay' on OOS12 per se. Just followed the updates (11.2.10.10, then C48 which was prompted by the system, then C63, and then OOS13 zip using the OPLocalUpgrade apk).

Keep in mind that this was on 9 Pro, I'm not sure if the same thing applies to the 9 non-pro. You might wanna test it by trying to flash OOS13 directly if you have the zip.

Yep, OOS 12 was really bad. I'll try the process following the steps of the first post to retain my magisk. I'll let you know how it goes just to share my experience

Thanks for the support everyone. Let you know soon

 

[RASTAVIPER]

Yep, OOS 12 was really bad. I'll try the process following the steps of the first post to retain my magisk. I'll let you know how it goes just to share my experience

Thanks for the support everyone. Let you know soon

A12 was perfectly fine for me and thousands other users.
Just because some people had a bad flash noone can generalize that the OS was bad for everyone.

In any case, u know the steps now to upgrade to A13, so it shouldn't be an issue for u.

 

[magogo]

Are there any boot and magisked images available for the T-mobile variant?

 

[r4p70r]

I updated to the F.72 build with the built in system update didntd get a chance to use magisk before it restarted to patch the new partition. I tried boot the patched F.72 but in magisk i dont have the install option just patch a file.. I realy appriciate any help.

edit- I got it working

How did you got it working.

I have the same problem.
Neither booting nor flashing my patched boot image works.

 

[Thomas.swe]

I kinda panicked and did a lot. I'm trying to remember. I'm on Holliday's and not rly sober. I have 9Pro_EU_F.72_boot.img in my download folder. I don't think I flashed it, just booted it. Sorry for not being that helpful. If you screw things up you can restore the phone withe the tool from OnePlus.

 

[r4p70r]

I kinda panicked and did a lot. I'm trying to remember. I'm on Holliday's and not rly sober. I have 9Pro_EU_F.72_boot.img in my download folder. I don't think I flashed it, just booted it. Sorry for not being that helpful. If you screw things up you can restore the phone withe the tool from OnePlus.

I also just booted my boot image.
After it didn't work I flashed it.

But both remain without effect. The device boots without problems but Magisk only shows Installed: N/A

Interestingly enough root works for apps which had the Permission before the Update to A13. But in Magisk you can not manage permissions nor customize the zygisk list.

Does nobody else with F.72 on the EU 9Pro have this problem??

 

[2019registered]

Good afternoon to you Guys, I am currently on

• Android 12
• LE2123
• C.61
• Magisk 25201

I currently have issues with the deny list, which means that although some of the apps have been added to the deny list, those apps still recognize the presence of magick aka root.
I saw that there is a potential fix for the deny list in the newer version of magisk. How can update to latest magisk without loosing root?

Install to Inactive Slot (After OTA) and reboot?

Thanks for your answers, much appreciated.

 

[immortalwon]

Can you please re-upload untouched /magisked files again for oneplus pro 9? It says deleted by the uploader.

OOS 11.2.5.5 boot :
Untouched/magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)

 

[HorizonZero]

A12 was perfectly fine for me and thousands other users.
Just because some people had a bad flash noone can generalize that the OS was bad for everyone.

In any case, u know the steps now to upgrade to A13, so it shouldn't be an issue for u.

Absolutely, I'm sorry I didn't want to offend anybody or impose my view. I didn't like OOS 12 and I had a really bad experience with it. But it was absolutely personal and it might have been caused by my mistakes

Hope so! xD

 

[phynesse]

When I install Magisk with patched file, I end up with Qualcom Dump.

• MSM to stock A11, then updated all the way to A13 F.72.
• unlocked bootloader, installed 25.2 and patched the file from post #1939 (BA for EU version)
• flashed the patched file (fastboot boot file.img) and then rebooted
  = Qualcom Dump

after a while it does reboot normally, but i lost root. tried again, same result.
If someone could point me in the right direction, would be much appreciated.

EDIT: i noticed in the guide it says "fastboot boot boot magisk_patched.img" ... this produced error for me, so I removed 1x 'boot'. I assume that was correct and not the cause..?

thanks.

 

[r4p70r]

When I install Magisk with patched file, I end up with Qualcom Dump.

• MSM to stock A11, then updated all the way to A13 F.72.
• unlocked bootloader, installed 25.2 and patched the file from post #1939 (BA for EU version)
• flashed the patched file (fastboot boot file.img) and then rebooted
  = Qualcom Dump

after a while it does reboot normally, but i lost root. tried again, same result.
If someone could point me in the right direction, would be much appreciated.

EDIT: i noticed in the guide it says "fastboot boot boot magisk_patched.img" ... this produced error for me, so I removed 1x 'boot'. I assume that was correct and not the cause..?

thanks.

fastboot boot magisk_patched.img is correct

But I can't get Magisk to recognize the patched boot image either.
That's why I flashed it.

I have root (with the apps that had root before the update to A13).

Of course, that doesn't do you any good with a completely reinstalled system.

Unfortunately, no one here could give me an answer as to why Magisk behaves so strangely. I assume not many have updated to A13. Otherwise the problem should be more widespread.

 

[Smedslund]

fastboot boot magisk_patched.img is correct

But I can't get Magisk to recognize the patched boot image either.
That's why I flashed it.

I have root (with the apps that had root before the update to A13).

Of course, that doesn't do you any good with a completely reinstalled system.

Unfortunately, no one here could give me an answer as to why Magisk behaves so strangely. I assume not many have updated to A13. Otherwise the problem should be more widespread.

I would say that many of us have update with out any issues.

 

[RASTAVIPER]

When I install Magisk with patched file, I end up with Qualcom Dump.

• MSM to stock A11, then updated all the way to A13 F.72.
• unlocked bootloader, installed 25.2 and patched the file from post #1939 (BA for EU version)
• flashed the patched file (fastboot boot file.img) and then rebooted
  = Qualcom Dump

after a while it does reboot normally, but i lost root. tried again, same result.
If someone could point me in the right direction, would be much appreciated.

EDIT: i noticed in the guide it says "fastboot boot boot magisk_patched.img" ... this produced error for me, so I removed 1x 'boot'. I assume that was correct and not the cause..?

thanks.

If your patched file doesn't do the job, just find the file from someone else.

This method works fine for many other people.