Database Info

Magisk killed my OnePlus 6

I installed the latest Pix3lify using Magisk, and I was not pleased with the results. So I went back into Magisk and removed Pix3lify. Now it is stuck at the OnePlus animation during boot.
Any ideas?

Try uninmod in twrp and make sure it's completely removed, u may be able to just reflash OS, twrp reboot and flash magisk
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242

Fixed it
TWRP saved my bacon. I reflashed the Pix3lify and it rebooted nicely.

ButtonBoy said:
TWRP saved my bacon. I reflashed the Pix3lify and it rebooted nicely.
Click to expand...
Click to collapse
Magisk has an uninstaller, might want to download it and keep it with your files.

Thanks, I will look for it

I almost came close to that bootloop result, but in the magisk repo with pixelify, the dev put to properly uninstall the module, you'll need to reflash it again using magisk's temp recovery or manually boot into TWRP and reflash it, and it'll uninstall without any side effects.

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

Oneplus 7 Pro Bootloop after overlay install, still booting into recovery

Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?

Bxperiaz3 said:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Click to expand...
Click to collapse
Can you boot in TWRP? if can try changing slot and boot from it

Mervingio said:
Can you boot in TWRP? if can try changing slot and boot from it
Click to expand...
Click to collapse
Hi,yes I can. Its loading the logo now so i'll wait and see what happens. If that works then what should be the next thing I do?
Edit: Slot B seems to be bootlooping on the logo unless its meant to take a few minutes
Is there a way to recover without wiping my data?
So slot A sits on the caution device rooted screen then defaults to the fastboot rescue mode which allows me to select reboot to recovery which is twrp. From there I have full access to the phone but still not booting to system. Slot B passes the fastboot screen and hangs on the one plus logo just circling around. This is my first rooted phone and I haven't had any problems until now so I'm hoping its something simple because I didnt do anything big to cause it. Hopefully someone has some insight.

Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?

Bxperiaz3 said:
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Click to expand...
Click to collapse
Yes

MrSteelX said:
Yes
Click to expand...
Click to collapse
Will I lost root or relock the bootloader? I'm trying to find the least destructive way to get back to what I had which was oos 10 with twrp and magisk.

Uninstalled magisk and was able to reboot. However reflashing it as i want to retain root makes it bootloop again. Any possible fix for this that isn't a factory reset and reroot?

I can't get substratum or substratum themes to work on any rom or stock, nothing happens after reboots.....or everything turns this weird orange theme. Then one time it corrupted the whole OS and I had to wipe.

try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage

i6rb said:
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
Click to expand...
Click to collapse
Thanks, i'll try this. Will I need to install TWRP again once I do this or is it unaffected?

Tried to dirty flash the same stock rom from TWRP but I don't think it did it properly. Can I dirty flash stock rom, flash magisk then try reboot to system?
Any help greatly appreciated.

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?

Question How do we update Tmo variant

I know this has been asked but since the xda app is so atrocious now I can't find any answers.
I'm rooted on the Tmo OP9 variant but can't remember how to update from the ota. Can someone run me through it?

Make sure you are using the T-Mobile boot.img and not any other variant. Depending on how you rooted it in the beginning..
The
way I updated my t-mobile one plus 9
Is go to magisk, uninstall, restore images. Go to system update. Download and install. DO NOT REBOOT!!
go to magisk and reinstall magisk in inactive slot after ota , now reboot!

Jg1234 said:
Make sure you are using the T-Mobile boot.img and not any other variant. Depending on how you rooted it in the beginning..
The
way I updated my t-mobile one plus 9
Is go to magisk, uninstall, restore images. Go to system update. Download and install. DO NOT REBOOT!!
go to magisk and reinstall magisk in inactive slot after ota , now reboot!
Click to expand...
Click to collapse
Thanks for the reminder! I remember now but somehow my phone is confused. I did the exactly as you said, which is the correct way, and then I hit the switch slots on magisk after ota when it was done, and it restarted but the OTA wanted to restart too so I guess I let the wrong one restart after updating?
So it wouldn't boot after that so I had to switch slots. Now it tried to update but says something went wrong and to update to finish installation. I'm not real sure how to proceed here other than master reset at this point.

I don't know what happened. Sounds like you did exactly like I did. I let magisk reboot for me and everything went just fine. I have heard problems with magisk having issues with inactive slot and was removed in the canary build... You can try flashing stock boot.img before doing a factor reset and see if that helps at all.