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.
Related
Our MiA1 is fast, I know.. but can be faster (I think)
Does someone have an image with forced encryption disabled? December boot.img? I tried with "format data" option in twrp but I get bootloop and haven't tried with magisk
I also want boot image with forced encryption disabled.
Have you tried dm-no-verity.zip?
zeyaan said:
Have you tried dm-no-verity.zip?
Click to expand...
Click to collapse
No, I haven't tried that. I am running Oreo latest January patch rooted with Magisk.
Please guide me step by step:
how to disable forced encryption
Restore my Data with TWRP (I already have TWPR backup of Data).
Kindly also provide link of flashable zip.
I have tried the following steps to disable forced encryption with magisk but it didn't worked.
Factory Reset / Data wipe with TWRP
flashing of Magisk15.3.zip
Restoration of Data
Reboot
I think I can use latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ but main issue is that I also want my Data back using TWRP. I don't want to backup and restore apps using Titanium Backup.
armujahid said:
No, I haven't tried that. I am running Oreo latest January patch rooted with Magisk.
Please guide me step by step:
how to disable forced encryption
Restore my Data with TWRP (I already have TWPR backup of Data).
Kindly also provide link of flashable zip.
I have tried the following steps to disable forced encryption with magisk but it didn't worked.
Factory Reset / Data wipe with TWRP
flashing of Magisk15.3.zip
Restoration of Data
Reboot
I think I can use latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ but main issue is that I also want my Data back using TWRP. I don't want to backup and restore apps using Titanium Backup.
Click to expand...
Click to collapse
We gotta wait as the zips are device specific as per my understanding. Unless some builds it we have no option but wait.
Any news about this? I'm interested
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.
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Ebeninyo said:
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Click to expand...
Click to collapse
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
DrCow said:
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Edit: after flashing magisk reboot your phone once more. (i didn't knew it before. I booted into my os and checked magisk app to see if root was successfull but it didn't show me. I wiped everything down and flashed magisk again. Same thing happened. Rebooted my phone and saw root was on )
Ebeninyo said:
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Click to expand...
Click to collapse
Will try it on the weekend.. I had some problems restoring my previous backup so i rather be home when i do it
Sent from my ONEPLUS A5000 using Tapatalk
Edit:
Wait the wifi and the LTE problem can be caused by the recovery?
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
i ended up giving up..
im trying to do a clean flash
but the moment i flash the recovery and trying to go into the recovery
boom
black screen
i tried it multiple times both with codework 3.2.3 and blu_spark
Edit: Flash universal codework 3.2.1 does get me into recovery
im gonna restore my backup...for now
Z-Blade said:
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Click to expand...
Click to collapse
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
lorrdvader said:
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
Click to expand...
Click to collapse
No, it wont because all of that is stored in the Internal Storage. So as long as you don't check that, you will still have your data. However, I personally wipe everything including the internal storage when moving to a new rom. I prefer to start with a complete clean slate but it is optional.
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!
Please give me instruction!
What I have done to there:
1. Unlocked bootloader
2. Boot TWRP .img file
3. Install recovery ram disk from the same .img file
4. Reboot to TWRP
5. Install TWRP installer .zip file
6. Reboot to TWRP
7. Wipe system, data, dalvik partitions
8. Flash Havoc and TWRP installer
9. Reboot to TWRP
10. PARTITIONS ENCRYPTED/UNABLE TO FLASH GAPPS
I'm using TWRP UNOFFICIAL BY MAURONOFRIO.
What to do now?
I'm tired! Give me instruction!
You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.
Maybe this thread will help.
dj_ooms said:
You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.
Click to expand...
Click to collapse
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION
ALYSKY said:
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION
Click to expand...
Click to collapse
Its the third post (link) in the thread I linked to....