Database Users

Magisk problem with oreo and twrp without encryption support

hi, i had successully upgraded my x compact to oreo, installed twrp 3.2.1 (without encrytion support) and rooted with magisk. Everything has been working fine until i messed up magisk with some module (busybox).
My phone hanged at Xperia logo after rebooting, and i had to recover it by flashing the firmware again, but now magisk no longer works. Whenever i install it, boot will hang. Without magisk it can boot, but then i don't have root.
It seems i couldn't uninstall Magisk cleanly, so the problematic module remained there. The magisk uninstaller zip failed at twrp, which i suspect it is because it cannot access some data as twrp does not support decryption.
now i have no idea how to fix this. appreciate any suggestions!
Sent from my F5321 using XDA Free mobile app

dohanin said:
hi, i had successully upgraded my x compact to oreo, installed twrp 3.2.1 (without encrytion support) and rooted with magisk. Everything has been working fine until i messed up magisk with some module (busybox).
My phone hanged at Xperia logo after rebooting, and i had to recover it by flashing the firmware again, but now magisk no longer works. Whenever i install it, boot will hang. Without magisk it can boot, but then i don't have root.
It seems i couldn't uninstall Magisk cleanly, so the problematic module remained there. The magisk uninstaller zip failed at twrp, which i suspect it is because it cannot access some data as twrp does not support decryption.
now i have no idea how to fix this. appreciate any suggestions!
Sent from my F5321 using XDA Free mobile app
Click to expand...
Click to collapse
You can always do a clean install, right?
Time consuming but you'll get your phone back, with Magisk, and have to wait for a fully working TWRP (like many of us X Compact owners, I think).

yes, but wiping everything would cost me a lot of time, and should be the last resort. i didn't even wipe /data when upgrading from nougat to oreo. i was hoping someone can teach me how to remove the problematic magisk module, like using adb or whatever.

just an update... my issue is fixed. Some expert in the Magisk forum suggested me to place a file with name ".disable_magisk" in /cache to disable the modules, and it worked.

dohanin said:
just an update... my issue is fixed. Some expert in the Magisk forum suggested me to place a file with name ".disable_magisk" in /cache to disable the modules, and it worked.
Click to expand...
Click to collapse
I was gonna say that you can disable the module by erasing a cache file, via adb, but here you go.

Magisk + dm-verity + decrypt data partition

So, I wanted to have a stock rom, rooted with magisk, and data partition decrypted, so what I did is the following:
1) wiped data partition
2) flashed stock OOS (latest, 5.1.6)
3) flashed Magisk
4) flashed DM-verity & force encryption disabler (this link)
Now I have a few questions:
1) I tried flashing the dm-verity from this link (no_verity_op5_v2.zip) but it didn't work so I flashed this newer version (disable_dm_verity_forceencrypt_09_02_2018.zip). Any ideas why it didn't work?
2) What should I do when a new OOS update comes up?
3) What should I do when a new Magisk update comes up?
Regadring Magisk: In Magisk there is a option "Preserve AVB 2.0/dm-verity":
1) What does it do?
2) What is AVB 2.0 in the first place?
Thank You all in advance

0v3rl0rd said:
So, I wanted to have a stock rom, rooted with magisk, and data partition decrypted, so what I did is the following:
1) wiped data partition
2) flashed stock OOS (latest, 5.1.6)
3) flashed Magisk
4) flashed DM-verity & force encryption disabler (this link)
Now I have a few questions:
1) I tried flashing the dm-verity from this link (no_verity_op5_v2.zip) but it didn't work so I flashed this newer version (disable_dm_verity_forceencrypt_09_02_2018.zip). Any ideas why it didn't work?
2) What should I do when a new OOS update comes up?
3) What should I do when a new Magisk update comes up?
Regadring Magisk: In Magisk there is a option "Preserve AVB 2.0/dm-verity":
1) What does it do?
2) What is AVB 2.0 in the first place?
Thank You all in advance
Click to expand...
Click to collapse
Answers:
1. It didn't work because you have to flash that zip BEFORE you flash Magisk (it's stated in the thread's first post too). The zip creates the required files which tells Magisk to disable dm-verity and forceencrypt when it is flashed.
2. When a new OOS comes out, all you have to do is dirty flash it, then the universal zip and then Magisk. You should be unencrypted with the new OOS as well.
3. The universal zip will most likely be updated if there are major changes in Magisk, but if not, then just update Magisk as usual, from within Magisk Manager. If you wish to update from TWRP by flashing the latest Magisk zip, then you have to remember to flash the universal zip BEFORE the newest Magisk zip and you should be fine.
Regarding your other queries, AVB refers to "Android Verified Boot". Google it and you'll find lots of information about it (which may be technical). Regarding the option in Magisk, it's for those people who want to let dm-verity intact while using Magisk (because some phones don't boot when dm-verity is disabled and hence this option is there for those people). Don't fiddle with it since you want to stay unencrypted and disabling dm-verity causes no issues on the OnePlus 5.

shadowstep said:
Answers:
1. It didn't work because you have to flash that zip BEFORE you flash Magisk (it's stated in the thread's first post too). The zip creates the required files which tells Magisk to disable dm-verity and forceencrypt when it is flashed.
2. When a new OOS comes out, all you have to do is dirty flash it, then the universal zip and then Magisk. You should be unencrypted with the new OOS as well.
3. The universal zip will most likely be updated if there are major changes in Magisk, but if not, then just update Magisk as usual, from within Magisk Manager. If you wish to update from TWRP by flashing the latest Magisk zip, then you have to remember to flash the universal zip BEFORE the newest Magisk zip and you should be fine.
Regarding your other queries, AVB refers to "Android Verified Boot". Google it and you'll find lots of information about it (which may be technical). Regarding the option in Magisk, it's for those people who want to let dm-verity intact while using Magisk (because some phones don't boot when dm-verity is disabled and hence this option is there for those people). Don't fiddle with it since you want to stay unencrypted and disabling dm-verity causes no issues on the OnePlus 5.
Click to expand...
Click to collapse
Thank You for Your answer
Regarding point 2 - OOS update: should I reboot after every step or no?
I mean:
1. dirty flash OS
2. reboot to recovery
3. flash universal zip
4. reboot to recovery
5. flash magisk
6. reboot to recovery
Or should I do that without rebooting: flash everything and then reboot to recovery?

0v3rl0rd said:
Thank You for Your answer
Regarding point 2 - OOS update: should I reboot after every step or no?
I mean:
1. dirty flash OS
2. reboot to recovery
3. flash universal zip
4. reboot to recovery
5. flash magisk
6. reboot to recovery
Or should I do that without rebooting: flash everything and then reboot to recovery?
Click to expand...
Click to collapse
It's not necessary to reboot to recovery after each step.

Rooting help for OnePlus 6T 9.0.15

A little background: I was rooted before updating my OnePlus 6T from system settings, then after updating (through system settings) I no longer had root and TWRP recovery so what I did was flashed TWRP following this method now I do have TWRP recovery but I am not sure which method to follow for the root process, and I have few concerns as below:
Should I flash Magisk now if so which version and which method will work for 9.0.15?
Before flashing Magisk should I flash Magisk uninstaller as well?
Do I have to flash TWRP again after flashing Magisk?
I might be asking dumb questions but I don't want to mess it up.

Greetings.
Just straight up flash the latest Magisk version, worked for me. Flash it through TWRP.
Why would you flash magisk uninstaller? I mean, I suppose it's optional?
No, you don't have to flash TWRP again.
Cheers.

Flash Magisk.
Next time, without rebooting, use Magisk mod 'TWRP A/B retention script' (search for it in Magisk modules list) just after flashing OTA via local method, and then without rebooting yet, in Magisk manager install again Magisk selecting 'other slot after OTA' option. Then only you reboot, all babies intact and in good health

S5 G-900T rooting with Magisk

I plan to root my Samsung Galaxy S5 G-900T with MAgisk. Some manuals suggests to decrypt the data first by using the Format data in TWRP recovery following by flashing with the no-verity-opt-encrypt.zip and MAgisk.zip files.
1. Should I format Data and install no-verify-opt-encrypt before the flashing the Magisk on Galaxy S5?
2. If answer is "Yes", what version of the no-verity-opt-encrypt I should use: 5.1 or 6.1. I have both. Or it doesn't matter which one to choose?

razes said:
I plan to root my Samsung Galaxy S5 G-900T with MAgisk. Some manuals suggests to decrypt the data first by using the Format data in TWRP recovery following by flashing with the no-verity-opt-encrypt.zip and MAgisk.zip files.
1. Should I format Data and install no-verify-opt-encrypt before the flashing the Magisk on Galaxy S5?
2. If answer is "Yes", what version of the no-verity-opt-encrypt I should use: 5.1 or 6.1. I have both. Or it doesn't matter which one to choose?
Click to expand...
Click to collapse
all you have to do is enable debugging in developer option first. flash twrp using odin and flash magisk in twrp. you should have root.

Hi!
My s5 sont reboot into twrp after flashing it with Odin.
Doe's someone have A clue what to do....?

Upgrading rooted OP6T to OOS 11.1.2.2 - Can I get root without losing my data?

Hi - I have a rooted OP6T on OOS 11.1.1.1.
I want to upgrade to OOS 11.1.2.2, but I am trying to keep root. Installing TWP would be nice, but not mandatory. I definitely don't want to lose my configuration / data during the upgrade.
Can I do it?
I have upgraded my OP 7 Pro to OOS 11 using Payload Dumper and a Magisk patched boot.bin file. Is the process the same with the OP6T?
Thanks!

@¿GotJazz?
Hello,
yes you can,
this is what i done at every update...
Disable all the Magisk modules
and the securities (fingerprints/pin, etc)
Let the OTA comes and install itself.
Do NOT reboot, instead open the Magisk
manager and via internal modules flasher
install the TWRP .zip, (i'm using 3.5.2_9-0,
but there are newer ones).
Do NOT reboot.
Open Magisk again and select install,
then install to inactive slot (after OTA).
When that's done you can reboot your phone
with lastest firmware, TWRP, root and untouched data.
Configure your securities and reinstall your modules.
Cheers

@¿GotJazz?
I saw that you also posted in other threads
with slight variations and the bootloop slot issue.
Well, if I were you I would not risk it
and I would proceed first with a backup
of the important stuff, then
I would use MSM tool with rollback
to the android 10 version, re-root it
via Payload Dumper or using a pre-patched image
and upgrade to android 11 with the method
I have already told you.
Let the community know how it went and
good luck.