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!
Related
So I unlocked by Bootloader and Rooted my OP6, the question I have is will the OTA updates be installed without any problems or will I have to install it manually?
Also when I install twrp (I have not installed yet) how will I need to update my phone through OTA?
Sorry if this is a noob question because the last time I rooted and flashed roms the software support was over so I never had any OTA updates.
Thanks
It will download the update but it most probably will download the Full 1.4GB ZIP
Meaning it will install the full rom and not the small update package.
It will install normally to the other slot and after reboot you should be updated.
This should work just fine with TWRP because it updates your other slot within Android, not in recovery.
After update, reboot phone, then reboot to TWRP and install Magisk!
I updated while being rooted and TWRP installed. Just download the update, then reflash twrp and root and everything works fine.
So if u want update your system but don't need TWRP you can just download OTA with system updater and install it.
If you want magisk don't reboot! Open magisk and press install and install to second slot. Then reboot. You will have an updated system with working magisk!
Kollachi said:
So if u want update your system but don't need TWRP you can just download OTA with system updater and install it.
If you want magisk don't reboot! Open magisk and press install and install to second slot. Then reboot. You will have an updated system with working magisk!
Click to expand...
Click to collapse
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
zappomax said:
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
Click to expand...
Click to collapse
I didn't even remove root. I can't explain you how this a and b is working. but what I know is, that every OTA is change the partition. And no u won't have 2 systems.
zappomax said:
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
Click to expand...
Click to collapse
If your current system runs for example on slot "a" the update will be installed on slot "b "...the slot that you currently not using
Nick502 said:
It will download the update but it most probably will download the Full 1.4GB ZIP
Meaning it will install the full rom and not the small update package.
It will install normally to the other slot and after reboot you should be updated.
This should work just fine with TWRP because it updates your other slot within Android, not in recovery.
After update, reboot phone, then reboot to TWRP and install Magisk!
Click to expand...
Click to collapse
So if I flash twrp now, then update OOS, only my root will be removed right which can be again flashed by twrp?
Harsh Keswani said:
So if I flash twrp now, then update OOS, only my root will be removed right which can be again flashed by twrp?
Click to expand...
Click to collapse
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Nick502 said:
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Click to expand...
Click to collapse
Thanks
Nick502 said:
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Click to expand...
Click to collapse
One more thing, everytime I update, it's going to download the full ROM?
Harsh Keswani said:
One more thing, everytime I update, it's going to download the full ROM?
Click to expand...
Click to collapse
If I'm not wrong, on a rooted device OTA installs a full rom. On a not-rooted phone OTA installs just the incremental update.
I only unlocked the bootloader to prepare for TRWP and root (So no TWRP and root yet) and it tells me it will download full update.
TaranQ said:
I only unlocked the bootloader to prepare for TRWP and root (So no TWRP and root yet) and it tells me it will download full update.
Click to expand...
Click to collapse
I guess it recognizes the unlocked bootloader and then it always downloads and installs full update.
Why would you unlock your bootloader and then don't root :laugh:
---------- Post added at 01:15 PM ---------- Previous post was at 01:13 PM ----------
[/COLOR]
pdppdp said:
I guess it recognizes the unlocked bootloader and then it always downloads and installs full update.
Why would you unlock your bootloader and then don't root :laugh:
Click to expand...
Click to collapse
Because I was not sure I wanted root again there are always apps that even with Magisk hide won't work.
But just to make sure I prepared by unlocking bootloader so if I decide to go for TWRP and root my data and storage won't get wiped which would mean starting all over again and losing app-data.
So, if I update from a ROM rooted with TWRP, will not the user data be deleted? Should we just root again and install the TWRP?
I had rooted 5.1.5 with TWRP and Magisk. I just downloaded the full package, copied it to phone storage. Then went to system update, update locally, picked the file and it ran the update.
However after reboot and update complete I lost TWRP and root. So I went to fastboot, booted the official TWRP (fastboot boot twrp.img). Then flashed the official TWRP and Magisk for root, rebooted and all was good again.
I'm pretty sure there's an easier way of doing this but this worked for me.
marvel79 said:
I had rooted 5.1.5 with TWRP and Magisk. I just downloaded the full package, copied it to phone storage. Then went to system update, update locally, picked the file and it ran the update.
However after reboot and update complete I lost TWRP and root. So I went to fastboot, booted the official TWRP (fastboot boot twrp.img). Then flashed the official TWRP and Magisk for root, rebooted and all was good again.
I'm pretty sure there's an easier way of doing this but this worked for me.
Click to expand...
Click to collapse
In theory, with the Oxygen Updater application you can install the OTA and Magisk in 1 step.
sakun-ice said:
In theory, with the Oxygen Updater application you can install the OTA and Magisk in 1 step.
Click to expand...
Click to collapse
Yeah probably but it has a lot of mixed reviews and this takes me 10 minutes more or so oh well. I'll rather do it like this It's not like we get a new update every week
maybe to help you all
me: 5.1.5, unlocked bootloader, unofficial TWRP from thread by wuxianlin, magisk 16.4
my procedure was to change to official twrp which can be done easily by
downloading the twrp installer from official site, put to internal storage
flash twrp official installer
still in recovery, select reboot: recovery
flash magisk
boot system
now download full 5.1.6 signed flashable zip
recovery: flash 5.1.6
reflash recovery
reboot recovery
flash magisk
boot system
now you have rooted 5.1.6 with official twrp and magisk, no wipe needed
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?
https://developers.google.com/android/images
Still 9.0, but it's starting a new quarterly build so might have some updates. No change log yet
There is this
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."
i did clean install of the recovery image this morning. all seems fine. nothing visually different
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Atomregen said:
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Click to expand...
Click to collapse
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
208.9mb too! Quite large for just a small incremental update too!
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
virtyx said:
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
Click to expand...
Click to collapse
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Atomregen said:
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck. After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
Click to expand...
Click to collapse
I had some issues getting the May update, TWRP 3.3.0-1, Kirisakura 2.3.0, and Magisk 19.1 to play nicely together. Lots of "rescue party" reboots at the "G" logo of booting after trying to install everything together. I basically did what you did to solve the issue too. Installed the May update (removing -w) then installed TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 18.1 and restarted back to system to make sure it all worked (which it did). After that I upgraded to Magisk 19.1 via the Magisk app and everything seems to be fine now. My temp solution until this was just use TWRP 3.2.3-3 which I had been using up until this point. That worked too and allowed everything to play nice from the initial installation.
Aren't you supposed to boot system before flashing magisk?
Atomregen said:
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
Click to expand...
Click to collapse
wangdaning said:
Aren't you supposed to boot system before flashing magisk?
Click to expand...
Click to collapse
I was wondering the same thing about whether you finished booting before installing Magisk. I completely boot after every step (Image, TWRP, Magisk, Kernel - ElementalX installed with EX Kernel Manager) and don't stack installs in TWRP. Been doing that for years, and it has saved me some time long term despite the couple of extra minutes during installs. My other thought was possibly a bad 19.1 file.
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
sstanton86 said:
208.9mb too! Quite large for just a small incremental update too!
Click to expand...
Click to collapse
Looking at new apps to backup in TB, there were about 7 new system apps that I saw and one that had been removed.
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Sent from my Pixel 3 XL using XDA Labs
Atomregen said:
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Click to expand...
Click to collapse
I always reboot to the system after the factory image/monthly update is installed and allow it to finish setup. Then I fastboot into TWRP to install TWRP recovery, my kernel, and Magisk via the "add more zips" option in TWRP. I've been doing this ever since I got the device and never ran into issues until this May update. Doing this with the May update, TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 19.1 caused reboots like I described. However, reverting to TWRP 3.2.3-3 instead (my initial solution/fix) or Magisk 18.1 then upgrading Magisk to 19.1 (like @sliding_billy suggested) worked fine. This to me implies a compatibility issue of some type and not an issue with the method of installation.
Tulsadiver said:
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Click to expand...
Click to collapse
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
virtyx said:
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
Click to expand...
Click to collapse
This is the way Freak recommends flashing his kernel. Did Freak change something?
Freak07 said:
Flash factory image with -w removed (if you want to keep data intact)
Do a reboot
Then you can boot to twrp and flash twrp, magisk and kernel (in that order)
Afterwards all should be fine.
I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel...
Click to expand...
Click to collapse
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
I always flash kernel before magisk. I've never had issues.
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
not saying either way is right or wrong
but it makes sense to flash magisk LAST.
Anyone try to sideload the OTA? I believe the file is too big to sideload?
lucky_strike33 said:
Anyone try to sideload the OTA? I believe the file is too big to sideload?
Click to expand...
Click to collapse
I sideloaded. Worked fine.
Anyone else unable to root the May update? I installed the update, TWRP, and the kernel I use and everything was fine. After installing Magisk 19.1 the phone boots straight to a "System UI has stopped" dialog box. Substratum overlays were uninstalled before updating and uninstalling Magisk fixes the issue, leading me to believe that it is the cause.
I tried installing Magisk 18.1 instead to see if it would work, but oddly it doesn't seem to install at all. When I boot the phone Magisk Manager was installed, but it claims that Magisk is not installed and no apps can get root access.
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!
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