Related
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Post #3 has the instructions you need
Long story short you need to flash the update via TWRP.
unknown00 said:
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
Click to expand...
Click to collapse
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
RASTAVIPER said:
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
unknown00 said:
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
Click to expand...
Click to collapse
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Like above.
Flashing ROM Will also flash stock recovery so after ROM you need to flash twrp again,if you reboot without it it's lost.
Also why magisk isn't flashed right away is because: when you choose to reboot to twrp after the twrp flash it Will change slot, this way you Will get magisk on the correct slot.
All this can be done from the OS.
Install the ROM upgrade as usual,don't reboot.
Open magisk app
Search for a module a/b twrp (you Will only find one module) and install it.ndont reboot just yet.
Go to main screen of magisk
Press install, install, install to inactive slot (after OTA). After this install you can reboot.
Both works, I find the twrp way to be more convenient
I don't about stable i am on open beta 10 i root every beta without twrp using patch boot image i got update every time around 1.5 GB because i am rooted after update i just lose root everything same before update phone not wipe anything
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
akxak said:
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
Click to expand...
Click to collapse
No need to reinstall TWRP in the first method?
unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
I do not have TWRP installed, it is basically not necessary as OOS can be updated with the settings/manual update tool and Magisk can be reinstalled via Magisk manager.
I had to use TWRP solely to downgrade to Magisk 17.2 from Magisk 18 as this cannot be done with Magisk Manager. But for that purpose, it's enough to temporarly make TWRP available via fastboot boot command without permanently installing it.
If you have TWRP and want to keep it, that easy process doesn't work to upgrade the OS.
unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
If you wanna keep TWRP you do the way I described few posts up.....
tabletalker7 said:
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Click to expand...
Click to collapse
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
thejase said:
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
Click to expand...
Click to collapse
As promised, I'm writing back with my findings. I believe some enabled module in magisk was the issue. What I did was uninstall magisk 18 with the latest uninstaller. Thinking it was V18 itself that was the problem, I then proceeded to install v17.3 on both slots (reboot to recovery in betweene). This worked and booted! It started to occur to me that I had not disabled any of my modules before installation of the rom/magisk. This is a big mistake as a lot of magisk modules are still using old formatting and cause new installations to fail if left enabled. Since an uninstall also disables all modules, I believe using 17.3 was not necessarily the solution but rather either disabling modules before an install, or uninstalling whatever version magisk was installed to begin with (which essentially disables/uninstalls those modules anyway). After installing 17.3 and getting it to boot, I just updated via magisk manager to v18 with no issues to speak of! Now comes the part where I need to remember all the installed modules I had and test them one by one.
For uninstallation of modules in twrp, you can use https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 Or https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
I hope this helps someone!
So I finally pulled the trigger on updating my Oneplus 6 to the latest OTA PIE update, but when the phone reboots it goes to the system for 2 seconds then immediately reboots to TWRP recovery. I followed the instructions from a thread here that said to immediately flash the TWRP A/B zip from Magisk, followed by clicking install for Magisk to the inactive slot. Now I can't get my system to boot up properly and I'm only able to access TWRP recovery. What should I do, I'm basically locked out of my phone now?!
Module or theme error, flash magisk uninstaller, flash magisk and boot.
If it still doesn't boot, flash magisk uninstaller boot system and remove theme overlays (like substratum or Swift installer)
whizeguy said:
Module or theme error, flash magisk uninstaller, flash magisk and boot.
If it still doesn't boot, flash magisk uninstaller boot system and remove theme overlays (like substratum or Swift installer)
Click to expand...
Click to collapse
I've tried flashing magisk uninstaller 5 times, same result no matter what I do. I finally just wiped the Data partition from twrp and then system boots. I just have to set everything back up on my phone now.
Hi
In every rom thread I see about a million different answers on how to properly install the rom. Usually the official instructions are very vague. I've been flashing roms for years but this ab partition is very confusing to me. I just got my oneplus 6 a few days ago. It would be great if someone very knowledgeable in how to do this could make a how to guide for both stock and custom roms. I think it would really help everyone and threads for each rom wouldn't be full of people asking it over and over (and getting different answers). Thank you devs for all that you do.
Custom if you don't know if you have the recommend base installed to both slots:
Flash OOS
Flash twrp
Reboot to twrp
Flash OOS
Flash twrp
Reboot to twrp
Wipe data, dalvik cache
Flash custom
Flash twrp
Reboot to twrp
Flash gapps
Flash magisk
Boot system
Custom update:
Flash updated custom rom
Flash twrp
Reboot to twrp
Flash gapps (not needed, but updated gapps is most likely better to use anyhow..)
Flash magisk.
From custom back to OOS:
Info: Format data needed because you will trigger encryptionsince you're on different securety patch. This is also the same way to go from beta branch of oos to stable since the securety patches is lower (in general) on stable.
How to:
Boot twrp
Plug phone in to pc and take backup of everything
When done format data
Transfer oos, twrp, magisk to phone
Flash oos
Flash twrp
Reboot to twrp
Flash magisk
Update oos from... Let's say 9.0.4 to 9.0.5
From Twrp:
Flash oos
Flash twrp
Reboot to twrp
Flash magisk
Boot
From oos:
Use ota update, let it install until it asks you to reboot.. DON'T DO IT.
instead go to magisk and search for "a/b" one module will be found, install it. DON'T REBOOT
Go to main screen of magisk and press install, install, install to inactive slot (after ota) when it's done you can reboot.
General ****ups:
Don't boot after update?
Flash magisk uninstaller
Try to boot (yes.. Without magisk)
If it boots you know it was magisk issue, most likely you had substratum overlays installed or modules that messed it up.
Reboot to twrp and flash magisk again and set up your modules one by one or apply themes or whatever you do with your root.
Phone currently rooted and using xxxNolimits rom and Smurf kernel
Update available and getting below warning.
So if I update do I have to start from scratch again and re root.
So download update and then don't reboot system but reboot to twrp and flash Magisk again or do I flash updates and then Magisk
Confused dot com
Come on man, any amount of threads and answers to this throughout the forum via the search box.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
hallo dare said:
Come on man, any amount of threads and answers to this throughout the forum via the search box.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Click to expand...
Click to collapse
Fair cop on my behalf?
Just was not sure what to remove in Magisk as have few modules installed including substratum, you tube vanced theme, systemless hosts and xxxNolimits.
Take it just first 2 I remove
I always flash TWRP as a magisk module before rebooting, reboot into recovery, flash TWRP again, reboot into recovery again (unnecessary I'm sure, but i'm paranoid), then flash magisk, reboot into system and good to go.
funkyirishman said:
Fair cop on my behalf
Just was not sure what to remove in Magisk as have few modules installed including substratum, you tube vanced theme, systemless hosts and xxxNolimits.
Take it just first 2 I remove
Click to expand...
Click to collapse
To be sure to be sure i always remove all modules and reboot phone before doing any updates.
aNGERY said:
I always flash TWRP as a magisk module before rebooting, reboot into recovery, flash TWRP again, reboot into recovery again (unnecessary I'm sure, but i'm paranoid), then flash magisk, reboot into system and good to go.
Click to expand...
Click to collapse
That's what I've done wrong and lose twrp after updates. I need to reboot to recovery with adb commands and install twrp.
sportytony said:
That's what I've done wrong and lose twrp after updates. I need to reboot to recovery with adb commands and install twrp.
Click to expand...
Click to collapse
TWRP is installed to boot partition on this device (no discrete recovery partition). So anytime you update, the boot partition is overwritten with a new stock boot partition (therefore, no TWRP). To update and stay rooted and with TWRP, simply OTA update, do NOT reboot. Go to Magisk Manager. Flash TWRP installer zip as if it were a Magisk module. It will say you are unrooted, so (again, in Magisk Manager) install Magisk again, picking the option "Install to inactive slot (after OTA)". Reboot, and you should be updated and still rooted.
That's how I update everytime. But sometimes just for hahas, I've rebooted to recovery, just because, and it would reboot to factory recovery , and twrp wasn't there. I was rooted, just no twrp. ( I know weird)
Hello everyone,
I recently installed Magisk and TWRP and at first everything was working completely fine, than I installed the f-droid privileged extension module the device started bootlooping.
I managed to fix the issue through TWRP (Fix bootloop option) and completely uninstalled Magisk through the official uninstaller. Thing is every time I'm trying to reinstall Magisk the problem returns.
Please help.
Happened to me to....you need to uninstall that exact module from your system....
You can uninstall any modules even from TWRP...
go to file explorer on TWRP
Open data then adb an then modules and delete unnecessary folder otf module...
James Blode said:
Happened to me to....you need to uninstall that exact module from your system....
You can uninstall any modules even from TWRP...
go to file explorer on TWRP
Open data then adb an then modules and delete unnecessary folder otf module...
Click to expand...
Click to collapse
Thank you for replying but the adb folder is empty.
Anyone?
PsyCoil said:
Hello everyone,
I recently installed Magisk and TWRP and at first everything was working completely fine, than I installed the f-droid privileged extension module the device started bootlooping.
I managed to fix the issue through TWRP (Fix bootloop option) and completely uninstalled Magisk through the official uninstaller. Thing is every time I'm trying to reinstall Magisk the problem returns.
Please help.
Click to expand...
Click to collapse
This is strange normally when you flash magisk uninstaller every module will be uninstalled, it's used to do a clean flash of magisk, infact when you reinstall magisk no module will be there and you need to reinstall everything
Hitman478™ said:
This is strange normally when you flash magisk uninstaller every module will be uninstalled, it's used to do a clean flash of magisk, infact when you reinstall magisk no module will be there and you need to reinstall everything
Click to expand...
Click to collapse
Indeed. How should I proceed then? Could the "Fix bootloop option" in TWRP caused the issue?
PsyCoil said:
Indeed. How should I proceed then? Could the "Fix bootloop option" in TWRP caused the issue?
Click to expand...
Click to collapse
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way
I have just tried the first method and unfortunately it did not work. The device keeps booting into fastboot instead of system. I will try the second method tomorrow and report here. Just to make sure I have it right, dirty flash is flashing the ROM without wiping the data first?
Magisk version is latest stable v20.3
Hitman478™ said:
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way
Click to expand...
Click to collapse
Thanks! The second solution did the trick. I'm pretty sure TWRP "Fix bootloop option" somehow caused the issue.
Hitman478™ said:
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way
Click to expand...
Click to collapse
PsyCoil said:
Thanks! The second solution did the trick. I'm pretty sure TWRP "Fix bootloop option" somehow caused the issue.
Click to expand...
Click to collapse
Great! :good:
Because once you flash "Fix bootloop option" it will stay in system partition and the only way to remove is to reflash system through oos zip
hahaha i think magisk rooting method fail from safetynet check and module install. After a bootloader from specific module (disablerliboemencrypto) i restore my stuff to try another module (Bluetooth ..) a bootloop again happen
sorry but,GOOGLE beats YOU @topjohnwu.