Hi, thanks for all the information here.
Thanks to the guides, I was able to downgrade, backup TA, upgrade, build personal kernel, install twrp, working android pay.... everything is good. But:
I have tested out some modules for Magisk, two I wanted to use boot me in a boot loop/stuck on boot.
I can fix this using TWRP, I just use mount_magisk stored in my download on internal storage.
Then I disable the 'bad' module, by typing in the terminal: /magisk/<module folder>/disable
BUT!
This only works because my data is decrypted.
I want to encrypt my data.
It is true we still don't have a TWRP that supports our encryption?
If I encrypt, is there anyway to disable a bad magisk module?
I think magisk is stored in the boot, correct? So it is not in data, so it does not matter if data is encrypted or not?
I hope someone can clear up some of my worries.
Thanks
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
Ok, so if I wanted to recover my system, I could just reflash boot (my kernel)?
I would have to install magisk again but that is ok.
But would I even be able to install magisk if my data is encrypted?
I think v12 can be installed if no access to /data, but v13 not?
Thanks
ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
I don't have an encrypted partition. Could anybody with encrypted partition try it?
voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
Yes it does say that, but it is talking about fw version 34.1.A.1.198 - which is marshmallow right?
From what I understand TWRP was fine with XC's encryption in marshmallow, but with nougat it doesn't work.
So I think (that version of) TWRP will not work. (but I have not tested myself, but I read a post somewhere saying it didn't)
Related
Hello everyone!
I am wondering how to enable encryption of my P9 Lite running Nougat B370. My phone is rooted, bootloader unlocked and TWRP installed, if that is relevant.
In the menus I don't find any option to encrypt my phone. So, anyone knows if it is possible?
If you mean data encryption, it is already encrypted.
Potato997 said:
If you mean data encryption, it is already encrypted.
Click to expand...
Click to collapse
You sure about that? Because TWRP can access my data partition without pin...
Is there any way to check whether disk encryption is truly enabled?
android_xpert said:
You sure about that? Because TWRP can access my data partition without pin...
Is there any way to check whether disk encryption is truly enabled?
Click to expand...
Click to collapse
It's encrypted unless you unencrypted it with twrp but the latest update of twrp (nouget) lets you backup data unlike twrp on MM.
bghyt said:
It's encrypted unless you unencrypted it with twrp but the latest update of twrp (nouget) lets you backup data unlike twrp on MM.
Click to expand...
Click to collapse
It's strange though, I've never unencrypted my phone with twrp. But when I boot into twrp my whole data partition is open for access without any sort of password/pin. Seems to me there is no encryption active.
TWRP can mount data partition, but it does not mean that it is able to decrypt it.
It can backup/restore or format it which is what usually what a TWRP do, if you install a custom ROM like LOS you will need to format it because the system can't decrypt it while stock ROM can do it.
Potato997 said:
TWRP can mount data partition, but it does not mean that it is able to decrypt it.
It can backup/restore or format it which is what usually what a TWRP do, if you install a custom ROM like LOS you will need to format it because the system can't decrypt it while stock ROM can do it.
Click to expand...
Click to collapse
What I meant by my post is not only that twrp can mount the data partition. I can also access all my files within said data partition.
On a2017u b35, flashed supersu zip 2.82 in two without problem,but when I run supersu, it says root undetected. How to fix this? Thanks
Try magisk 14.3 instead :3
Try SuperSU 2.79 and see if that works.
ZTE Axon 7 A2017U, Stock B32, Tapatalk 4.9.5
marcdw said:
Try SuperSU 2.79 and see if that works.
ZTE Axon 7 A2017U, Stock B32, Tapatalk 4.9.5
Click to expand...
Click to collapse
Tried 2.79 it is the same.
J0nhy said:
Try magisk 14.3 instead :3
Click to expand...
Click to collapse
I tried 15.3 and 16 before, install is OK, running is also OK, I but magisk cannot retain the root request after reboot, i.e. it still prompt the root request pop-up when app runs.
xdataibai said:
On a2017u b35, flashed supersu zip 2.82 in two without problem,but when I run supersu, it says root undetected. How to fix this? Thanks
Click to expand...
Click to collapse
I had the same issue with raystef66"s B35 7.1.1.][stock] SL!M¹ DF!NR. I eventually just went with Magisk.
patio54 said:
I had the same issue with raystef66"s B35 7.1.1.][stock] SL!M¹ DF!NR. I eventually just went with Magisk.
Click to expand...
Click to collapse
Which version magisk? I tried 15.3 and 16,both have the issue that not remember the root request after reboot,i.e. it will prompt again when app runs
xdataibai said:
Which version magisk? I tried 15.3 and 16,both have the issue that not remember the root request after reboot,i.e. it will prompt again when app runs
Click to expand...
Click to collapse
15.3 , I couldn't pass safteynet with 16. I did have to reflash the Magisk zip occasionally to re-root. Don't know why.
You might want to check in TWRP to see if the data and other partitions are formatted as ext4. Myself and a couple of others had a similar problem on Project New World and finally figured out that Magisk didn't like the partitions formatted as F2FS. Once formatted to EXT4 everything ran fine.
robertbarber said:
You might want to check in TWRP to see if the data and other partitions are formatted as ext4. Myself and a couple of others had a similar problem on Project New World and finally figured out that Magisk didn't like the partitions formatted as F2FS. Once formatted to EXT4 everything ran fine.
Click to expand...
Click to collapse
I will check it out, if it is f2fs and I format it as ext4, can I restore twrp back,will restore put the format back? Which partitions should I check beside data? Thanks
robertbarber said:
You might want to check in TWRP to see if the data and other partitions are formatted as ext4. Myself and a couple of others had a similar problem on Project New World and finally figured out that Magisk didn't like the partitions formatted as F2FS. Once formatted to EXT4 everything ran fine.
Click to expand...
Click to collapse
How do I check it? In twrp, didn't see the partition format shown in any options. Thanks
Its been a while and I am not on the Axon anymore but I checked all the partitions that I could, Some will not allow you to change them like cache and one or two others but the rest should be able to show you how they are formatted. As for restoring files I think it will restore it to whatever file system you had before because that's what it was saved as but I am not 100% sure on that. Someone may know more about that than I do. For how to go about checking the partitions to see how they are formatted this YouTube video should be able to give you a guide as to what to do. TWRP may have updated since it was made but it should be able to work for you. You just want to format it as EXT4 if its formatted as F2FS https://www.youtube.com/watch?v=8AbU_2z07Vg
I've never had an issue with F2FS data partition and Magisk/SuperSU. TWRP can format /data,/cache, and /system as F2FS. You just have to look a bit harder, it's in the repair/change filesystem options.
Thanks, it turns out that /data is f2fs,others are ext4. I format data to ext4. Then magisk can retain setting changes now, even though still cannot remember root request after reboot. And adaway works now. Thanks.
Thanks, it turns out that /data is f2fs,others are ext4. I format data to ext4. Then magisk can retain setting changes now, even though still cannot remember root request after reboot. And adaway works now. Thanks.
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
It was released a few days ago, just go with custom or wait for working solution
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
No-verity didn't work for me but remove encryption.zip did.
this didn't work for me, it resulted in a bootloop
ric69 said:
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
Click to expand...
Click to collapse
fre78 said:
this didn't work for me, it resulted in a bootloop
Click to expand...
Click to collapse
Sorry for you. check Mount system or data or enable MTP. Internal storage was probably still at 0
I rebooted more than 10times it's ok here
zainbfaisal said:
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
Click to expand...
Click to collapse
sir may i ask how come ur able to have twrp .
how dd u install twrp on android 8.0 UK firmware?
thanks for help
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
OREO stock keeps encrypting DATA partition
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
NewbieFTW said:
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
Click to expand...
Click to collapse
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
skydivider said:
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
Click to expand...
Click to collapse
Magisk removes the encryption disabler .zip for some reason.
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
zainbfaisal said:
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
Click to expand...
Click to collapse
I'm sorry then, I don't know what to say. It worked for me.
I needed reinstal magisk after boot for root, but worked for me...
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
When this happend to me, i hit format data and typed yes, when i mount on TWRP i can see my storage again
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
miguelan.ruiz said:
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
Click to expand...
Click to collapse
Samsung Pay will, at the moment, probably never work again because it trips Knox.
For Samsung Health the fix is still the same: install a build.prop editor and change the value of RO.Config.Tima from 1 to 0.
not for me
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
doesn't work for me
Apparently there are 2 kind of users here.
One part did manage to install stock Oreo (BTU? other CSC?) , with root (magisk? superSu?) and a working TWRP (3.2.1?) which is not read-only on our beloved S7 Edge (SM-G935F)
The other part did not manage to setup this particular config.
It would be nice to have a detailed step-by-step guide from scratch by someone who managed to do it, so we can reproduce it.
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Akarsh Adithya.K said:
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Click to expand...
Click to collapse
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
strongst said:
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
Click to expand...
Click to collapse
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Akarsh Adithya.K said:
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Click to expand...
Click to collapse
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
strongst said:
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
Click to expand...
Click to collapse
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Akarsh Adithya.K said:
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Click to expand...
Click to collapse
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
strongst said:
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
Click to expand...
Click to collapse
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Akarsh Adithya.K said:
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Click to expand...
Click to collapse
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
strongst said:
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
Click to expand...
Click to collapse
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Akarsh Adithya.K said:
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Click to expand...
Click to collapse
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
strongst said:
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
Click to expand...
Click to collapse
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Akarsh Adithya.K said:
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Click to expand...
Click to collapse
To help others mark this thread as [SOLVED] in the the title :good:
strongst said:
To help others mark this thread as [SOLVED] in the the title :good:
Click to expand...
Click to collapse
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Akarsh Adithya.K said:
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Click to expand...
Click to collapse
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
strongst said:
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
Click to expand...
Click to collapse
Again , thank you soo much man .
Turns out enabling that vendor portion after flash rom for no verity and magisk will cause no trouble
and now i m on OOS 5.1.5!!(uninstalling Magisk before flashing new update was important to).
Now that
how do i mark this thread as Solved.
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Dr4In said:
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Click to expand...
Click to collapse
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
strongst said:
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
Click to expand...
Click to collapse
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Dr4In said:
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Click to expand...
Click to collapse
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
strongst said:
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
Click to expand...
Click to collapse
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Dr4In said:
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Click to expand...
Click to collapse
If you mean your encrypted twrp of your internal storage = no.
I would start from scratch with decrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used this and solved the problem
I was facing to the same problem today, and the problem was the Magisk version! Same problem for Pixel 3/XL users...
The way you can fix it: Install v19.1 BETA (not the stable)! It should boot up!