I have installed incremental upgrades for 9.0.2 and 9.0.3 and been able to do a TWRP less root using Magisk. For the upgrade to 9.0.4 I downloaded and installed the full upgrade. Following installation of oos_9.0.4_patched_boot.img, my phone reboots to recovery so I am unable to load Magisk. So I have to reinstall oos_9.0.4_stock_boot.img and stay unrooted. I can't find a similar problem - am I unique? Any solutions?
Solanoantuna said:
I have installed incremental upgrades for 9.0.2 and 9.0.3 and been able to do a TWRP less root using Magisk. For the upgrade to 9.0.4 I downloaded and installed the full upgrade. Following installation of oos_9.0.4_patched_boot.img, my phone reboots to recovery so I am unable to load Magisk. So I have to reinstall oos_9.0.4_stock_boot.img and stay unrooted. I can't find a similar problem - am I unique? Any solutions?
Click to expand...
Click to collapse
Flash Full OOS via fastboot (Guide: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 )
Then use fastboot to enter twrp blu_spark (TWRP: https://forum.xda-developers.com/devdb/project/?id=27466#downloads )
Then flash magisk (Magisk: https://forum.xda-developers.com/ap...k-v7-universal-systemless-t3473445?styleid=21 )
After magisk installed, reboot phone and install magisk app
Done.
PeterSmusi said:
Flash Full OOS via fastboot (Guide: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 )
Then use fastboot to enter twrp blu_spark (TWRP: https://forum.xda-developers.com/devdb/project/?id=27466#downloads )
Then flash magisk (Magisk: https://forum.xda-developers.com/ap...k-v7-universal-systemless-t3473445?styleid=21 )
After magisk installed, reboot phone and install magisk app
Done.
Click to expand...
Click to collapse
My apologies for the late reply. I'm not heavily into these things so I was reluctant to go into TWRP. So I ended up resetting my phone and now it all roots quite happily. But thanks for the ideas.
hii i have one plus 6 oxygen 9.0.6 but am not able to find out patched file
image
Deleted
Seems I am not finding a definitive guide to flash OTA or full OOS v9.5.4 on GM1917-GM21AA
Current setup:
OOS v9.5.3, rooted with Magisk patched boot, Magisk app and TWRP "non-decrypt"
Plan for upgrade to v9.5.4:
Place all files on USB OTG, TWRP zip, Magish v19.2, Magisk un-installer v2.0, OTA v9.5.4 182mb/Full 1.99gb "in case"
Boot to TWRP, access OTG, flash Magisk un-installer
Flash OTA v9.5.4
Flash TWPR zip, reboot TWRP
Flash Magisk v19.2
Am I on the right track? Am I missing some steps?
I want to minimize any bootloop scenario.
Tx guys.
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!
Hi, I am trying to flash magisk. I patched my boot.img and flashed it via fastboot. But it didn't work, Magisk app was still showing as not installed. Then, I tried the Recovery method (flashing the magisk zip), it tells that magisk patched to the boot.img file but this method didn't work too. But it said magisk patched to the boot.img. What can cause it?
My rom: Xiaomi.eu 21.12.8, Android 12
My device: Xiaomi Mi 10T (apollo)
CaganAgabey said:
Hi, I am trying to flash magisk. I patched my boot.img and flashed it via fastboot. But it didn't work, Magisk app was still showing as not installed. Then, I tried the Recovery method (flashing the magisk zip), it tells that magisk patched to the boot.img file but this method didn't work too. But it said magisk patched to the boot.img. What can cause it?
My rom: Xiaomi.eu 21.12.8, Android 12
My device: Xiaomi Mi 10T (apollo)
Click to expand...
Click to collapse
Flashing the Magisk patched boot.img only installs the necessary binaries to gain root access, you have to manually install the Magisk Manager app to take advantage of the binaries that it installs. Flashing the patched boot.img does not automatically install the Magisk app on your device as part of the flashing process.
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?