Database Info

Rooted OTA update behavior

Hello everyone, 2 questions:
I have a rooted Oneplus 6 with Official TWRP and Magisk. Yesterday I wanted to update to 5.1.6, so, with a VPN it downloaded the full zip through the update app. As soon as it finished downloading, it started to update directly.. Omg! I restarted immediately in recovery because I wanted to update from there, afraid of losing TWRP.
Question 1: what would have happened if I would had left the update app to finish installing?
From TWRP I updated the ROM, reflashed TWRP, and Magisk. Everything was up and running (slot b).
This morning I woke up and found that root was missing and phone had switched to slot a. I simply reflashed Magisk from recovery (slot a) and everything is good now.
Question 2: What happened? Another mysterious update during the night?
Thank you!

Hurizen said:
Hello everyone, 2 questions:
I have a rooted Oneplus 6 with Official TWRP and Magisk. Yesterday I wanted to update to 5.1.6, so, with a VPN it downloaded the full zip through the update app. As soon as it finished downloading, it started to update directly.. Omg! I restarted immediately in recovery because I wanted to update from there, afraid of losing TWRP.
Question 1: what would have happened if I would had left the update app to finish installing?
From TWRP I updated the ROM, reflashed TWRP, and Magisk. Everything was up and running (slot b).
This morning I woke up and found that root was missing and phone had switched to slot a. I simply reflashed Magisk from recovery (slot a) and everything is good now.
Question 2: What happened? Another mysterious update during the night?
Thank you!
Click to expand...
Click to collapse
1 you would've went completely stock.
2 a/b partitioning is for faster integration of system updates and only flashes on one of the 2 partitions.

mikex8593 said:
2 a/b partitioning is for faster integration of system updates and only flashes on one of the 2 partitions.
Click to expand...
Click to collapse
Hello, thanks for you reply.
I know it flahhes only on one partition, but after I flashed from TWRP I was rooted and on slot B. Then, something happened while I was sleeping and woke up with the phone not rooted and on slot B. This is very strange to me. Can you explain what happened? It updated?

This phone has no recovery partition. The kernel and recovery share the same partition. So when you flashed the full ota in twrp, recovery was overwritten and you lost root.
You should have just let it update, then reinstalled twrp and magisk. You are going to lose twrp and root with every ota anyway, which is how the update process is intended by OP. It gives you a clean stock slot with everything where it belongs. Reinstalling twrp and magisk is really not that hard.
This isn't like other phones where taking an ota w/root can cause a brick. OP has specifically designed the ota process on this phone to accommodate rooted users.

Hurizen said:
Hello, thanks for you reply.
I know it flahhes only on one partition, but after I flashed from TWRP I was rooted and on slot B. Then, something happened while I was sleeping and woke up with the phone not rooted and on slot B. This is very strange to me. Can you explain what happened? It updated?
Click to expand...
Click to collapse
you asked what happened:
if you are in one slot and fash mods, root, or anything else vie twrp it will behave like always, you will stay on that slot, reboot into sustem and all good.
the moment you fash a rom/update it will flash ti the other, non-current slot while your rdcovery zlsession will still show and be in the currently active slot
only upon reboot the device will decide to boot into the new slot.
to avoid loosing root and kernel, you have to manually change the slot and flash kernel and root in the new slot with the new system installed.
need more input? you'd have to pk because i won't come back here very often :highfive:

How to remove Magisk module from recovery?

I just installed a module (Active Edge) for the pixel 3 and now my phone is stuck in a bootloop.
Specifically its stuck on a page that says: Can't load Android System. Your data may be corrupt.......
The only options are:
Try Again
Factory Data Reset
I can get it into fastboot mode, but wanted to know if there is a way to disable the modules or uninstall magisk and start over. The instructions that I have found only reference TWRP when uninstalling and I don't have that. Any help is appreciated before I wipe this thing.

Flashing stock boot img will remove magisk
Sent from my Pixel 2 using XDA Labs

I ran into this same issue and solved it, check out my post here:
https://forum.xda-developers.com/showpost.php?p=78075483&postcount=121

thanks guys. I am back into the OS. I used the Sept boot.img as I haven't updated yet. I assume I have to flash the Nov update prior to using the patche_boot.img you linked. In any case, I have a usable phone that is ready for magisk again. Thank you, much appreciated.

In fact, you can just flash Magisk Uninstaller in TWRP then flash Magisk zip again, this will remove all modules installed.

TWRP problem / update

My OnePlus 7 Pro is rooted at 9.5.8 trying to update to 9.5.9
When i try to install OTA it removes TWRP as it would but i can't boot into the system again without booting into TWRP and switching back to slot A. And when i boot to the system settings say that update failed.
I've tried different update methods like
Install update (dont reboot) - Magisk install inactive slot
Download update zip with oxygen updater app - boot into recovery twrp - flash update zip
I rooted my phone a few days ago and for some reason it won't update and i'm stuck on 9.5.8
Slot b is also not readable. SDCARD shows 0mb

What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot

Yayodroid said:
What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot
Click to expand...
Click to collapse
Tried this too.
When I install oxygen update zip through TWRP and I reboot it goes over to slot b where I can't boot to the system and when I go back to slot a and boot to system update failed

First i disable all magisk modules then I download the full 2gb update, go into twrp, flash the update, flash twrp.zip then flash magisk.zip. Reboot and then re-enable the modules.

if you have Magisk module OOSNativeCallRecorder, you need to remove that module. If still issues then remove all modules.
Guide how to remove magisk modules via TWRP

equlizer said:
First i disable all magisk modules then I download the full 2gb update, go into twrp, flash the update, flash twrp.zip then flash magisk.zip. Reboot and then re-enable the modules.
Click to expand...
Click to collapse
This doesnt work. After flashing it reboots to slot b and update failed

Bradl79 said:
if you have Magisk module OOSNativeCallRecorder, you need to remove that module. If still issues then remove all modules.
Guide how to remove magisk modules via TWRP
Click to expand...
Click to collapse
Okay, this is weird
I chose to remove magisk, twrp and go back to stock with locked oem. Installed the new update perfectly fine. Then I regretted it. So I rooted my device again and set it up only to look under device info where it says that I now have 9.5.8. So basically my phone downgraded itself after rerooting and unlocking bootloader.
I'm now stuck in 9.5.8

PikachuLover said:
Okay, this is weird
I chose to remove magisk, twrp and go back to stock with locked oem. Installed the new update perfectly fine. Then I regretted it. So I rooted my device again and set it up only to look under device info where it says that I now have 9.5.8. So basically my phone downgraded itself after rerooting and unlocking bootloader.
I'm now stuck in 9.5.8
Click to expand...
Click to collapse
Probably switched back to old slot.

Bradl79 said:
Probably switched back to old slot.
Click to expand...
Click to collapse
So I should just try and flash the update, twrp and magisk in this order on the slot I am using now?

Having same problem. No work around?

The best way to update? Personally, I recommend taking full manual control of the update process. Use TWRP to update your ROM (that includes stock OOS) when you want to, and when you need to fix stuff.
- Flash ROM
If you are on slot A and flash a ROM, it goes to slot B.
- Flash TWRP installer zip
Keeps TWRP on both slots, patches boot.img
- Reboot to TWRP, not system
- Flash ROM again
This installs the ROM to the other slot, so now both slots are updated
- Flash TWRP installer zip again
Keeps TWRP on both slots, patches boot.img
- Flash Magisk
Patches the TWRP-patched ROM, allowing it to boot.
- Wipe dalvik
You can wipe data and dalvik instead for a clean flash
- Now reboot to system
Consider flashing BOTH slots (A and B) whenever you update OOS, for two reasons.
First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base.
The second reason is more compelling: the way the data partition changes encryption every update has nearly obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!

reaper000 said:
.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!
Click to expand...
Click to collapse
I was actually going to do this permanently for better performance, I did test it out for a while and definitely noticed things faster, boot is quicker, battery lasted longer also.
I just hate all the work required to keep decrypt between updates.
I wish Google allowed us to choose whether we want encryption or not.

This maybe a silly question and the form trolls may come out. However ??, decrypting, will we have to do it to both slots? A and B? Or will twrp take care of decrypting both slots. Coming from a one plus 5 we didn't have to deal with this whole slot a and b. Boy what a headache.

virtyx said:
I was actually going to do this permanently for better performance, I did test it out for a while and definitely noticed things faster, boot is quicker, battery lasted longer also.
I just hate all the work required to keep decrypt between updates.
I wish Google allowed us to choose whether we want encryption or not.
Click to expand...
Click to collapse
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.

harpin14789 said:
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.
Click to expand...
Click to collapse
He likely means backing up and starting fresh. I hated that process on my oneplus 5 but after works it was great. This whole slot A and B, is a pesky little bugga.

Yayodroid said:
What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot
Click to expand...
Click to collapse
This is what I did as well. Worked beautifully.

harpin14789 said:
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.
Click to expand...
Click to collapse
I manually decrypted
I don't know if the zip works on the 7 Pro
I'd update via twrp
Flash twrp
Flash magisk (after echo KEEPVERITY=FALSE > /data/.magisk)
ADB pull both fstab files in vendor/etc to my pc
And change fileencryption to encryptable and move back
I always kept the fstab files on my internal storage so I didn't need a PC but I always did just incase.

What happens if you have and F2FS formatted /data and
A custom kernel?
Thanks in advance
reaper000 said:
The best way to update? Personally, I recommend taking full manual control of the update process. Use TWRP to update your ROM (that includes stock OOS) when you want to, and when you need to fix stuff.
- Flash ROM
If you are on slot A and flash a ROM, it goes to slot B.
- Flash TWRP installer zip
Keeps TWRP on both slots, patches boot.img
- Reboot to TWRP, not system
- Flash ROM again
This installs the ROM to the other slot, so now both slots are updated
- Flash TWRP installer zip again
Keeps TWRP on both slots, patches boot.img
- Flash Magisk
Patches the TWRP-patched ROM, allowing it to boot.
- Wipe dalvik
You can wipe data and dalvik instead for a clean flash
- Now reboot to system
Consider flashing BOTH slots (A and B) whenever you update OOS, for two reasons.
First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base.
The second reason is more compelling: the way the data partition changes encryption every update has nearly obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!
Click to expand...
Click to collapse

so I think I did a dirty flash idk

So I was on tmobiles firmware rooted and something happened last night. It shut off and wouldn't boot up into system or recovery so after being frantic about it for about an hour and after some googling. I decided I was going to try a dirty flash (I think that's what I did)
I downloaded the latest ota zip from OnePlus 9.5.11 and used the all in 1 tool to boot to twrp and installed the ota zip there and installed twrp. Now the phone booted up to 9.5.11 on the international version and asked me to update to 9.5.13 which I let it. Then I rebooted back to twrp and installed magisk and reboot again. Bootloop happened so I went back to twrp and deleted my modules and rebooted again and it was fine and then reinstalled my modules....
Now for the actual question, should I be worried about corrupt data by doing what I did?
I really didn't want to lose my data, I have titanium backup but I can't get twrp to make any backups because I use OOS parallel apps

Bump
Anyone have an answer or any info to add?

If you didn't lose anything, then you didn't lose anything.

OnePlus 7 Pro OTA Bootloop [Help!]

Woke up this am to an OOS update and remembered that there's a process to go through to not lose root and magisk, so I look up the thread and follow the simple directions.
Allow the OTA but do not reboot.
Go into Magisk and install again to internal
Stay in Magisk and install to inactive slot
Reboot
I did exactly that and upon reboot, my phone booted to my lockscreen pic and just flashes every second. Even in safe mode it bootloops at a flashing lockscreen.
I followed exactly what I was supposed to do, so is there a step missing? Or was I not supposed to take the OOS update that was being pushed today?
I can access TWRP still, and I do have a full backup available if I need it, but I'd much rather figure out how to move forward.
Thanks for any help you can give me!
OnePlus 7 Pro
stock ROM
TWRP & rooted

Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.

FlipmodeBG said:
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
Click to expand...
Click to collapse
What exactly did you do to uninstall magisk from TWRP? I don't know how to do this...
Did you go into TWRP file manager and just delete /data/adb/magisk folder?

Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.

FlipmodeBG said:
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
Click to expand...
Click to collapse
Thanks for that, didn't work for me though. I keep bootlooping at insecure bootloader warning.
I have messed something up pretty bad, after the last reboot, I'm met with the Qualcomm CrashDump mode -- dmverity device corrupted force dump
kernel_restart
Now I'm stuck, because I've tried to recover my backup, it goes through the process at just over 1000 seconds, has no errors or failures but still won't boot.
I need some help here.

Nevermind, I have to have this phone back up and running ASAP, so I used MSM Tool and started over. I figured spending a few hours setting it back up from scratch was the best way forward at this point.
I'm unclear on what caused this problem... maybe I had a magisk module that didn't disable, or maybe I forgot to disable a substratum layer or something, but I really borked myself all because of an OTA update.
Any further advice on what I might have done or what might have corrected it will still be appreciated because I'm sure there will be another OTA someday and I'd really like to avoid this happening again.
Thanks!

What I do when there is a new Ota is
download the update from the updater app
remove any passwords or finger prints
reboot to twrp
install the Ota
do no reboot
install twrp installer
do no reboot
install magisk
wipe dalvick
reboot
check if Magisk is installed and if not reboot back into twrp and install Magisk again

Hi. Magisk 20.4 not working my device. Has anyone managed to get it working?