Database Info

Wiped and back to stock recovery... Sigh.

Hi!
I have a OP6. Running rooted stock with BluSpark TWRP and Magisk. Some months ago I rooted it and I was running 9.0.1 or 9.0.0, not sure which one. I then updated to 9.0.2 OTA a week or so later. I can not remember the exact procedure, but everything worked fine. Today I installed 9.0.3 OTA and then used Magisk (18.0) before reboot to install it to slot A (9.0.2 was on B). Somehow, I ended up with a wiped device and stock recovery. Can anyone help me to find my potential fault in this? I don't want it wiped during the next OTA, it's a real hassle to set up everything again. I remember that I checked a guide that had tips on OTA, but I can't seem to find it.
Best.

yogra1921 said:
Hi!
I have a OP6. Running rooted stock with BluSpark TWRP and Magisk. Some months ago I rooted it and I was running 9.0.1 or 9.0.0, not sure which one. I then updated to 9.0.2 OTA a week or so later. I can not remember the exact procedure, but everything worked fine. Today I installed 9.0.3 OTA and then used Magisk (18.0) before reboot to install it to slot A (9.0.2 was on B). Somehow, I ended up with a wiped device and stock recovery. Can anyone help me to find my potential fault in this? I don't want it wiped during the next OTA, it's a real hassle to set up everything again. I remember that I checked a guide that had tips on OTA, but I can't seem to find it.
Best.
Click to expand...
Click to collapse
I had the same thing happen to me. I missed the part where I flash TWRP right after the OTA. That probably triggered the factory reset

So instead of rebooting, I should do a "fastboot boot IMAGE" and then install the bluspark twrp zip from inside that one? I guess I can boot up to TWRP and install Magisk as well after this while I'm at it?

Are you flashing from twrp?
If so,flash ROM zip
Flash twrp zip
Reboot to twrp
Flash magisk
Done.
If ur doing it from Android
Install ROM,when it asks you to reboot, DON'T
go to magisk app
Go to modules
Search for a/b twrp (you should only find one module)
Install it ,don't reboot
Go to main magisk screen
Press install,install, install to inactive slot (after OTA) after it's done you can REBOOT.
The module keeps your twrp
Flashing magisk to inactive slot will root the update you just installed

I was installing the OTA normally, without TWRP. It worked just fine last time.

You shouldn't install any OTA if you are rooted.
Only full roms.
yogra1921 said:
I was installing the OTA normally, without TWRP. It worked just fine last time.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk

I understand. But it doesn't change the fact that it worked like a charm last time. I just assumed there might be a general way.

RASTAVIPER said:
You shouldn't install any OTA if you are rooted.
Only full roms.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
On OOS it knows if you are rooted and will download full ROM,so it's fine if you install a/b twrp magisk module after (keeps twrp) and then install magisk to inactive slot .
What happened here is he probably forgot to install twrp and magisk probably got to the wrong slot, hence the wipe

Not only probably. I did not install TWRP after the OTA. And I probably got the Magisk slot right (I installed it to other slot though the manager). Thanks for your help!
So next time:
OTA
Check if all dev USB-settings are enabled (?)
Shut off
Boot to TWRP
Install TWRP
Install Magisk to new slot
Boot up
Seems right?

yogra1921 said:
Not only probably. I did not install TWRP after the OTA. And I probably got the Magisk slot right (I installed it to other slot though the manager). Thanks for your help!
So next time:
OTA
Check if all dev USB-settings are enabled (?)
Shut off
Boot to TWRP
Install TWRP
Install Magisk to new slot
Boot up
Seems right?
Click to expand...
Click to collapse
no.... you do what i wrote like 3 posts up.. DO NOT REBOOT!!
After every single rom flash, TWRP, from android or fastboot or whatever way you install any rom TWRP will be replaced, aswell as boot.img (magisk is there)
OTA
DONT REBOOOOOOTT!!!
go to magisk, search for A/B twrp module, install it
DONT REBOOT
Go to main screen of magisk
install, install, install to inactive slot.
done..
your way will wipe TWRP.
From twrp:
Flash rom zip
flash twrp
reboot to twrp
flash magisk
done

Oh yeah. I completely forgot about that the TWRP retention script exists. Perfect. This is exactly what I did last time. Thanks!

Losing TWRP and Magisk after update

I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?

Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk

So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.

Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.

MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.

I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot

Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K

I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running

Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?

On a CONVERTED T-Mobile OP7 and currently on Android 10 with Magisk but no TWRP

Was thinking about downgrading to 9.5.13 and re-flashing TWRP and upgrading through the common "flash to inactive slot" from magisk method. On the fence cause i figure TWRP for Android 10 will come out. To recap. I have a Converted Tmobile OP7 running android 10. I am rooted with magisk but stock recovery (No TWRP) just wanting to see what you guys think i should do. and if you comment for me to downgrade... would i just go through MSM tool and revert back to 9.5.13? and would it REVERT my OP7 back to TMOBILE? Thanks in advance

TimmyLe7 said:
Was thinking about downgrading to 9.5.13 and re-flashing TWRP and upgrading through the common "flash to inactive slot" from magisk method. On the fence cause i figure TWRP for Android 10 will come out. To recap. I have a Converted Tmobile OP7 running android 10. I am rooted with magisk but stock recovery (No TWRP) just wanting to see what you guys think i should do. and if you comment for me to downgrade... would i just go through MSM tool and revert back to 9.5.13? and would it REVERT my OP7 back to TMOBILE? Thanks in advance
Click to expand...
Click to collapse
There is TWRP for OxygenOS 10.
Check the thread. It's a -70 release.
If you already have root you can flash TWRP then do a direct flash of Magisk.
I keep both my slots at the same OS revision and rooted the same way, so if something gets messed up I can boot to thew other slot and not even notice.

tech_head said:
There is TWRP for OxygenOS 10.
Check the thread. It's a -70 release.
If you already have root you can flash TWRP then do a direct flash of Magisk.
I keep both my slots at the same OS revision and rooted the same way, so if something gets messed up I can boot to thew other slot and not even notice.
Click to expand...
Click to collapse
Oh I saw that and wasn't sure on it! Thanks man. And is there a tutorial to flash on both slots? And how do I check to know what firmware is on each slot?

TimmyLe7 said:
Oh I saw that and wasn't sure on it! Thanks man. And is there a tutorial to flash on both slots? And how do I check to know what firmware is on each slot?
Click to expand...
Click to collapse
I don't know of a tutorial.
The process I use is the following:
1. Download latest or firmware later than what you have installed. Youcannot use this method to roll back.
2. Local install. Don't reboot yet.
3. Install Magisk using the option to root after OTA upgrade in Magisk Manager.
4. Reboot.
5. You will now have the OS installed in the current booting slot.
6. Local install again. Yes, it fails. Local install again, it will work the second time. -> Don't reboot
7. Use Magisk Manager to flash TWRP. Do not reboot.
8. Using Magisk Manager, install Magisk into the current slot. When that is done, se the install after OTA option.
9. You can now reboot.
You can use TWP to switch slots if you like, but both slots now have same OS and are rooted.

tech_head said:
There is TWRP for OxygenOS 10.
Check the thread. It's a -70 release.
If you already have root you can flash TWRP then do a direct flash of Magisk.
I keep both my slots at the same OS revision and rooted the same way, so if something gets messed up I can boot to thew other slot and not even notice.
Click to expand...
Click to collapse
tech_head said:
I don't know of a tutorial.
The process I use is the following:
1. Download latest or firmware later than what you have installed. Youcannot use this method to roll back.
2. Local install. Don't reboot yet.
3. Install Magisk using the option to root after OTA upgrade in Magisk Manager.
4. Reboot.
5. You will now have the OS installed in the current booting slot.
6. Local install again. Yes, it fails. Local install again, it will work the second time. -> Don't reboot
7. Use Magisk Manager to flash TWRP. Do not reboot.
8. Using Magisk Manager, install Magisk into the current slot. When that is done, se the install after OTA option.
9. You can now reboot.
You can use TWP to switch slots if you like, but both slots now have same OS and are rooted.
Click to expand...
Click to collapse
Thanks for the help man! I just flashed TWRP -70 and I got everything up and running. Gonna do the second "boot" when I got some time. And to recap.. you just have two boots setup as a precaution right? I'm not doing too much with my rom except for viper and that's it!

[Pixel 3a][Android 11][ROOTED][TWRP 3.6.0] Install OTA without reverting to stock

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?

Question OOS13 - How to update rooted phone? LE2115 F.18 - No full ROM?

I'm new to OnePlus again, had a Pixel as my last phone. Got the notice there's a new update for OOS13. I am rooted and, if possible, want to stay on stock ROM.
I checked the process and it seems the two ways to update are applying the full image or temporarily deinstalling Magisk, running the OTA, then reinstalling Magisk to other slot. Well, OxygenOS Updater and the OnePlus website show no full image for this latest update, so I tried the second method and that did not work at all, it went straight to the Qualcomm bugcheck screen on boot and then basically wouldn't start until I went back to fastboot and got back to Slot A.
So, am I missing something or is there just a lag before the full ROM gets posted? Or will OnePlus just never post it and I need to go to a third party ROM?

thx1200 said:
I'm new to OnePlus again, had a Pixel as my last phone. Got the notice there's a new update for OOS13. I am rooted and, if possible, want to stay on stock ROM.
I checked the process and it seems the two ways to update are applying the full image or temporarily deinstalling Magisk, running the OTA, then reinstalling Magisk to other slot. Well, OxygenOS Updater and the OnePlus website show no full image for this latest update, so I tried the second method and that did not work at all, it went straight to the Qualcomm bugcheck screen on boot and then basically wouldn't start until I went back to fastboot and got back to Slot A.
So, am I missing something or is there just a lag before the full ROM gets posted? Or will OnePlus just never post it and I need to go to a third party ROM?
Click to expand...
Click to collapse
Uninstall magisk restore images only. Don't reboot ,start ota let it install. Don't reboot. Go into magisk install and apply to ota . Boots into other slot. Qualcomm crash dump is probably because you left modules enabled. Disable and reboot before you start all of this. All your doing is supplying an apparent stock boot.img to allow ota to install. I just did process going to F-18 and all is well. Actually I msm back to A10 patch boot there. And carry it all the way to latest update. !! Pm me if you have any questions and gl.

mattie_49 said:
Uninstall magisk restore images only. Don't reboot ,start ota let it install. Don't reboot. Go into magisk install and apply to ota . Boots into other slot. Qualcomm crash dump is probably because you left modules enabled. Disable and reboot before you start all of this. All your doing is supplying an apparent stock boot.img to allow ota to install. I just did process going to F-18 and all is well. Actually I msm back to A10 patch boot there. And carry it all the way to latest update. !! Pm me if you have any questions and gl.
Click to expand...
Click to collapse
I did everything except disable modules. Do I disable modules first, then do "restore images?" Is there a reboot after disabling modules? [EDIT: nevermind, i see you did say to reboot after disabling modules]
How do I start over? Right now the other slot doesn't boot and in the OS the system update just says "reboot to apply update" as in it won't reinstall it. I've also tried flashing the boot image over with stock so I've sort of already messed up the inactive slot, probably.

thx1200 said:
I did everything except disable modules. Do I disable modules first, then do "restore images?" Is there a reboot after disabling modules? [EDIT: nevermind, i see you did say to reboot after disabling modules]
How do I start over? Right now the other slot doesn't boot and in the OS the system update just says "reboot to apply update" as in it won't reinstall it. I've also tried flashing the boot image over with stock so I've sort of already messed up the inactive slot, probably.
Click to expand...
Click to collapse
https://onepluscommunityserver.com/list/Unbrick_Tools/
If it was me I'd start fresh. Run msm tool will take you back to Android 10. 11.2.4.4 patch boot here and carry all the way through. Won't have modules to disable. In A10 you just use 23.1 magisk version . Patch boot.img. fastboot boot patched.img direct install then it backs up stock properly. You really need working msm tool handy anyway.

In order to update through A13/f18 you need magisk 25.2 stable to carry it through. Just start with 23.1 to patch . Then update magisk version.

I want to avoid wiping and starting over if possible. My Slot A boots fine, has root (I reflashed the Magisk modified boot image and it came right back), and everything is working on OOS13 F17. I just need to get the new update into Slot B which the updater seems to think is already applied.
Can I just redo the OTA or flash the full OOS13 F17 through OOS Updater?

thx1200 said:
I want to avoid wiping and starting over if possible. My Slot A boots fine, has root (I reflashed the Magisk modified boot image and it came right back), and everything is working on OOS13 F17. I just need to get the new update into Slot B which the updater seems to think is already applied.
Can I just redo the OTA or flash the full OOS13 F17 through OOS Updater?
Click to expand...
Click to collapse
Have you tried updating to build through system updates ? Instead of third party app.

mattie_49 said:
Have you tried updating to build through system updates ? Instead of third party app.
Click to expand...
Click to collapse
I'm sorry, I don't understand what you are asking. I have only used system updates so far. About -> Update. Currently that is saying it's installed and to reboot.

OK, I dug myself out of the hole. Here is how I fixed my situation and successfully updated to F.18 without any data loss.
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!

thx1200 said:
OK, I dug myself out of the hole. Here is how I fixed my situation and successfully updated to F.18 without any data loss.
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!
Click to expand...
Click to collapse
Very nice. Glad you got it. Very frustrating these devices and their A& B partitions.

thx1200 said:
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!
Click to expand...
Click to collapse
way to complicated, is there an easy way?
mattie_49 said:
In order to update through A13/f18 you need magisk 25.2 stable to carry it through. Just start with 23.1 to patch . Then update magisk version.
Click to expand...
Click to collapse
does you mean downgrade magisk to 23 will help?

Nobody ever was able to install F.18 on a rooted phone?

Suncatcher16 said:
Nobody ever was able to install F.18 on a rooted phone?
Click to expand...
Click to collapse
Its not hard as I have done it. Just use latest canary magisk.

Suncatcher16 said:
Nobody ever was able to install F.18 on a rooted phone?
Click to expand...
Click to collapse
I transfered root from f17 to f18 with 25.2 not canary. It works sir..you uninstall magisk only restore images. Start internal ota . Use install feature on magisk to install to inactive. Real simple.

This is how I have been doing it, not the quickest though.
1. Download OOS update from Oxygen Updater.
2. Disable all Magisk modules.
3. Flash stock boot.img
4. Flash OOS update via Local OOS System Update app.
5. Reboot
6. Extract boot.img using MSM readback
7. Patch boot.img through Magisk
8. Flash patched boot.img
9. Turn all Magisk modules back on.
When I was on OOS 12, I did try using the restore image option in Magisk but it never worked for me, this is why I had to do it this way. However, I have not tried on OOS 13 so I will give this another crack on the next update. If it does work, its way easier.

Z-Blade said:
This is how I have been doing it, not the quickest though.
1. Download OOS update from Oxygen Updater.
2. Disable all Magisk modules.
3. Flash stock boot.img
4. Flash OOS update via Local OOS System Update app.
5. Reboot
6. Extract boot.img using MSM readback
7. Patch boot.img through Magisk
8. Flash patched boot.img
9. Turn all Magisk modules back on.
When I was on OOS 12, I did try using the restore image option in Magisk but it never worked for me, this is why I had to do it this way. However, I have not tried on OOS 13 so I will give this another crack on the next update. If it does work, its way easier.
Click to expand...
Click to collapse
That is because you did not let magisk make the backup in the first place. After you patch the img, you are supposed to fastboot boot patch img not flash.

MrSteelX said:
That is because you did not let magisk make the backup in the first place. After you patch the img, you are supposed to fastboot boot patch img not flash.
Click to expand...
Click to collapse
Ahhhh... I take it after you boot into the patched image, you go into Magisk and do a direct install?

Z-Blade said:
Ahhhh... I take it after you boot into the patched image, you go into Magisk and do a direct install?
Click to expand...
Click to collapse
Yes

mattie_49 said:
I transfered root from f17 to f18 with 25.2 not canary. It works sir..you uninstall magisk only restore images. Start internal ota . Use install feature on magisk to install to inactive. Real simple.
Click to expand...
Click to collapse
Did you do any additional steps after you restored images and saw "restoration done" message? I tried several times and installation fails anyway. I did all according to these steps
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io

MrSteelX said:
Just use latest canary magisk.
Click to expand...
Click to collapse
Where did you download it? Could you drop the link please?