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!
Related
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!
Dears,
I have a OnePlus 6 unlocked and rooted with magisk and TRWP.
Currently I'm running stock firmware: oxygenos 10.3.
I got a message from system to update to 10.3.1.
Last time (when I have to update to 10.3) I tried to update in every way but without success and at the end I had to format everything and I lost my data.
So here is my question: which is the correct procedure to update software?
Thanks!
Look in TWRP and Root for OnePlus 6 on Oxygen OS 10 Stable/Beta thread
So you need to download latest Oxygen zip which is 042 buil if I'm not wrong...put it on your phone if you already didn't done that...then reboot to TWRP...and here starts the procedure....I HIGHLY RECCOMEND TO DO A WIPE WITHOUT FORMATTING INTERNAL STORAGE ONLY DATA...FOR AVOIDING ISSUES...but you can go without it...so here we start
Boot into twrp
Flash oxygen os zip(latest)
Flash twrp
Reboot to twrp(if it says no os installed just ignore it and swipe reboot anyway)
Flash magisk
and your done...thats it...nothing could go wrong.... I'm always doing it this way....
ilpratti said:
Dears,
I have a OnePlus 6 unlocked and rooted with magisk and TRWP.
Currently I'm running stock firmware: oxygenos 10.3.
I got a message from system to update to 10.3.1.
Last time (when I have to update to 10.3) I tried to update in every way but without success and at the end I had to format everything and I lost my data.
So here is my question: which is the correct procedure to update software?
Thanks!
Click to expand...
Click to collapse
For me, the phone downloaded the whole package instead of just the little OTA. I let it install it, bit did not let it restart it. Then I went to magisk modules and installed "twrp-keep". Then in magisk manager I had it install magisk on the other slot. Then I restarted the phone. Everything worked great.
tabletalker7 said:
For me, the phone downloaded the whole package instead of just the little OTA. I let it install it, bit did not let it restart it. Then I went to magisk modules and installed "twrp-keep". Then in magisk manager I had it install magisk on the other slot. Then I restarted the phone. Everything worked great.
Click to expand...
Click to collapse
Try this method... im also done my update like this!
my way of doing it
Here's what i did and it didn't took me long at all i'm a newbie
I unroot my phone via magisk
install os 10.3.1 then flash twrp and root my phone again.
Dears,
Thanks for the replay.
I forgot that I was without TWRP.
What I did, and it worked, is:
- uninstall magisk manager by magisk
- install full update
- reboot
- flash by fastboot boot.img patched by magisk.
Thanks again
Hi, I'd like to upgrade from last stable version of Android 10 to the stable version of 11. Can someone confirm that the method of installing Magisk on inactive slot before rebooting phone after installation works beetween different version of Android?
Thanks
unvisigoth1 said:
Hi, I'd like to upgrade from last stable version of Android 10 to the stable version of 11. Can someone confirm that the method of installing Magisk on inactive slot before rebooting phone after installation works beetween different version of Android?
Thanks
Click to expand...
Click to collapse
Answer myself if can help someone.
Open Magisk and uninstalled magisk image (image NOT all Magisk)
Downloaded and installed update
DO NOT REBOOT
Open Magisk and install to inactive slot
Reboot
Done
My cell: 0p6, rooted, android 10.3.12, magisk 23 and twrp 3.4.0-11
Any actual complete guide to upgrade to A11 stable, and preserving root and twrp?
Thanks
As long as update won't lock bootloader reinstalling magisk should be a 5 minute process.
unvisigoth1 said:
Answer myself if can help someone.
Open Magisk and uninstalled magisk image (image NOT all Magisk)
Downloaded and installed update
DO NOT REBOOT
Open Magisk and install to inactive slot
Reboot
Done
Click to expand...
Click to collapse
Twrp?
Roy Ken Robryk said:
Twrp?
Click to expand...
Click to collapse
After flashing OOS11 if your recovery in A10 was twrp it will be lost. And I am afraid that your device will get unrooted.
I´never updated across OTA, I have heard that by OTA your bootloader becomes locked, I am not sure.
So, IMO and the way I did it from A10, TWRP as recovery and rooted:
In TWRP, flash OOS11 (to inactive slot, let´s say B)
flash twrp (3.5.2_9-0 in my case) (in both slots)
reboot recovery (changing to inactive slot, B)
flash OOS11 (to new inactive slot, A)
flash twrp
reboot recovery (changing to slot A)
flash magisk (in slot A) If Magisk-23.zip fails (in my case is always this) try magisk 21.4.
In reboot menu select slot B and then reboot recovery.
Now, in slot B, flash magisk
Reboot system.
And as always, backup all your data before starting.
Ok guys
Here's the summary of what I know after performing the update to Android 11
my phone is OP6, rooted, android 10.3.11, magisk 23 and twrp 3.3.1-16 (not the latest one)
I just followed this guide, as I always do.
TWRP and Root for OnePlus 6 on Oxygen OS 10 Stable/Beta
A. If you are on OOS 10 I. If you are on OOS 10.3.0, OB4, or higher Prerequisites: TWRP image TWRP installer zip Latest Magisk zip Unlocked bootloader Reboot to fastboot mode. Boot to TWRP using the following command: fastboot boot...
forum.xda-developers.com
The process was completed without any errors of any sort.
So yeah, follow the above guide. I guarantee it (the aforementioned post) would not let you down.
So far I have observed few other things
OP launcher is (has become) sluggish
Brightness slider does not decreases brightness instantly when reduced to minimum (takes a second or two)
The most awesome substratum theme Liv Dark doesn't work perfectly
So far so good! ?
ALWAYS REMEMBER TO BACKUP YOUR DATA!
Fully working twrp (which twrp) on A11?
Roy Ken Robryk said:
Fully working twrp (which twrp) on A11?
Click to expand...
Click to collapse
I didn't get your question exactly
But still, the twrp remained the same as before i didn't flash a new one ( version mentioned above)
or
if you are asking for a fully working twrp on A11, I think this version is working fine; no hiccups
You can try to find one that is tailor made for A11 on xda in some or the other posts ( i might have seen one)
One more thing,
Maybe i am being paranoid but the faster battery drain is real and MX Player is bugged ( not only on op6 but every A11 phone out there, you will have to downgrade)
Greenify also doesn't work on A11 (PROPERLY YET!)
Cheers to google for always messing up!
I believe he was indeed asking if TWPR is working from the existing version, or if there was a new one that works.
I too prefer clarification. Does the existing TWP continue to work?
Thanks
I have 10 latest with twrp 3.3.1-18 enchilada and magisk 21.4.
Anyone has step by step guide to upade to stable 11 via twrp and to retain root?
Fully working nebrassy twrp on A11.1.1.1?
Ulises31 said:
After flashing OOS11 if your recovery in A10 was twrp it will be lost. And I am afraid that your device will get unrooted.
I´never updated across OTA, I have heard that by OTA your bootloader becomes locked, I am not sure.
So, IMO and the way I did it from A10, TWRP as recovery and rooted:
In TWRP, flash OOS11 (to inactive slot, let´s say B)
flash twrp (3.5.2_9-0 in my case) (in both slots)
reboot recovery (changing to inactive slot, B)
flash OOS11 (to new inactive slot, A)
flash twrp
reboot recovery (changing to slot A)
flash magisk (in slot A) If Magisk-23.zip fails (in my case is always this) try magisk 21.4.
In reboot menu select slot B and then reboot recovery.
Now, in slot B, flash magisk
Reboot system.
And as always, backup all your data before starting.
Click to expand...
Click to collapse
Hi man, can you elaborate how do you change slots, install to inactive slot, boot to specific slot a/b and such? I'm not as familiar with twrp stuff, I'm afraid i will screw something up.
Also where can I get twrp 3.5.2-9.0 that you are using. I have 3.3.1 enchilada.
Thanks,
Is there a way to easily update magisk rooted P11?
Like with Oneplus you can run the local update and install magisk to second slot and everything works.
You can just download current and latest version ROM from mirrors.lolinet.com
Enter fastbootd to flash original boot.img
Moreover, you can choose to let Magisk to revert boot and run OTA, and go back to Magisk to install on unused slot when you're promoted to reboot, and reboot after installation has been done
mingkee said:
Moreover, you can choose to let Magisk to revert boot and run OTA, and go back to Magisk to install on unused slot when you're promoted to reboot, and reboot after installation has been done
Click to expand...
Click to collapse
Thanks! This advise was more that helpful!
One more ... may you have to flash stock recovery too. That was the case on my rooted P11 Pro with update from 220312.
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?