Related
Hi,
I get on my OP3 this issue when I start the phone.
it dissappeers in 5 sec. Phone is working fine.
"the dm verity is not started in enforcing mode".
Help? kiss
YourTheBest said:
Hi,
I get on my OP3 this issue when I start the phone.
it dissappeers in 5 sec. Phone is working fine.
"the dm verity is not started in enforcing mode".
Help? kiss
Click to expand...
Click to collapse
It is just a warning. This is no issue and from the kernel.
I managed (i do not know how i have done this) to install oos beta 8 with supersu and without this message.
I experimented a little bit. I flashed the extracted beta 8 firmware and flashed the system via fastboot.
But i do not know why this message is completly away from my phone.
If you don't want to see it flash stock recovery
I did the following..
1. Sideload OxygenOS 3.2.6 from TWRP
2. Flash stock recovery from OnePlus downloads
3. Sideload from stock recovery Open Beta 8
Stock recovery is rewritten by new recovery and no more dm error.
Oneplus 3 dm-verity verification failed when i boot
https://forums.oneplus.net/threads/...ailed-when-i-boot.476968/page-3#post-15476095
But what is causing this problem in the first place? Is it because twrp is give permissions to make changes to the /system partition? And this dm-verity thing, will it cause any problems if left as it is?
ali.jujara said:
But what is causing this problem in the first place? Is it because twrp is give permissions to make changes to the /system partition? And this dm-verity thing, will it cause any problems if left as it is?
Click to expand...
Click to collapse
No, you can leave it there, it's just a warning.
Sent from my OnePlus 3 using Tapatalk
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
ZeppeMan said:
I did the following..
1. Sideload OxygenOS 3.2.6 from TWRP
2. Flash stock recovery from OnePlus downloads
3. Sideload from stock recovery Open Beta 8
Stock recovery is rewritten by new recovery and no more dm error.
Oneplus 3 dm-verity verification failed when i boot
Click to expand...
Click to collapse
.
So no more twrp in build 8. you're rocking stock recovery right? if yes, how you're able to gain root? as far as I know, there are no ways to root oxygen os 8/9 from inside.
.
Ps. I wanna lock my bootloader. flash build 9 with stock recovery. like new intact phone. plus, I wanna gain root from inside (without the help of twrp). any help or opinion?
I was on OB10. i unlock bootloader and flashed twrp. after this dm-verity error keeps coming at every boot. I tried formatting to ext4 file system but no luck. After some time i gave up and flashed OB10 again. Any idea on how to unlock and flash custom roms without dm-verity error? If I revert back to 3.2.8, can i flash the nougat roms without error?
Search the forum . Everything is answered
here
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Unlock bootloader.
Use ADB side load to flash stock rom.
Lock back bootloader. Voila!
Hope it helps. Thanks!
i tired
I tired but after the OTA update i get the dm message again
K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
this
cpt.macp said:
this
Click to expand...
Click to collapse
I will try Tomorrow
cpt.macp said:
this
Click to expand...
Click to collapse
When i do this a have to unlock the bootloader so i have 1 message again ...
K3v1990 said:
When i do this a have to unlock the bootloader so i have 1 message again ...
Click to expand...
Click to collapse
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
ill go try that, thanks
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
for full restet u mean Factory restet in the settings?
Edit: found it
Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Official Recovery ( Oxygen OS ) - https://www.androidfilehost.com/?fid=24591000424943319
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
It worked thank you very much
When dm-varity warning is there, i flash openbeta 7 firmware &modem . Problem solved! Never see this warning. Phone works fine.when i flash openbeta 8 firmware &modem,i wil get back the dam-varity warning
LELBOT said:
Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - https://docs.google.com/uc?id=0BzS3n...xport=download
Official Recovery ( Oxygen OS ) - http://oneplusroms.s3.amazonaws.com/...BmI3Z1Dri5Q=
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.
Click to expand...
Click to collapse
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?
m_reyna_16 said:
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?
Click to expand...
Click to collapse
Yes, it will work.
For the new recovery, it supports f2fs decryption and u have flash it to follow the steps.
These methods will work.
Dm-verity
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca
cryptofer said:
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca
Click to expand...
Click to collapse
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk
K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
Hi,
to be synthetic:
From TWRP recovery, change filesystem to Ext4 for both Data and Cache, then full wipe everything (System too);
Go back to OxygenOS v3.2.8;
Be sure to replace TWRP with Stock Recovery (download from 3.2.8 official thread);
Lock bootloader (both from Developer Options and Fastboot);
Sideload via recovery OxygenOS v4.0;
Consider to factory reset for a clean installation.
For more clarifications, I'm at your disposal
https://www.androidfilehost.com/?fid=457095661767116249
flash it
Test by me
millicent said:
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!
cryptofer said:
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!
Click to expand...
Click to collapse
I haven't tried it yet but I read a few reports already about systemless root with magisk being able to preserve Android pay
Sent from my ONEPLUS A3000 using Tapatalk
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?
Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot
Tried to Rooting my Mi Mix 2 with unlocked Bootloader with twrp (latest one 3.2.1 I guess from this forum) but I can't read my internal storage... it is and stays 0 mb.. I wiped everything several times but it didn't help also converting the Data or other folders to FAT or etc didn't help either so can someone recommend me something..
Use Magisk 16.0 for rooting ( you can flash it via twrp)
you don't have to reformat anything. I would restore the phone first to a known state (by restoring the default miui or whatever rom you want to use), then install magisk
rafuxus said:
Use Magisk 16.0 for rooting ( you can flash it via twrp)
you don't have to reformat anything. I would restore the phone first to a known state (by restoring the default miui or whatever rom you want to use), then install magisk
Click to expand...
Click to collapse
I tried with 9.5 miui global latest version and flashed magisk 16.0, boot loop to recovery.. any suggestions?
Make sure you're using the miui version of twrp, so it handles encryption correctly. You should have to enter your pin when you use twrp, if you're not getting prompted, something is wrong.
Re: boot loop. Just for testing, try unplugging your phone, turning it completely off and then back on.
rafuxus said:
Make sure you're using the miui version of twrp, so it handles encryption correctly. You should have to enter your pin when you use twrp, if you're not getting prompted, something is wrong.
Re: boot loop. Just for testing, try unplugging your phone, turning it completely off and then back on.
Click to expand...
Click to collapse
can you provide a link to that specific twrp ?
https://www.nextgen-networks.de/de/...-mix-2/28-twrp-recovery-3-2-1-0-for-miui.html
Disable forced encryption of data partition​
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
To encrypt the rom again, flash encrypt(pie).zip and format /data
What is the meaning of forced encryption on data partition
#ArtFuL said:
Disable forced encryption of data partition
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
Click to expand...
Click to collapse
In which recovery stock or on custom recovery?
Sdsahu101 said:
In which recovery stock or on custom recovery?
Click to expand...
Click to collapse
Custom recovery
Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.
nice_guy75 said:
Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.
Click to expand...
Click to collapse
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data
#ArtFuL said:
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data
Click to expand...
Click to collapse
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....
nice_guy75 said:
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....
Click to expand...
Click to collapse
Then no need to format. You won't loose data
is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.
kayamokid said:
is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.
Click to expand...
Click to collapse
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.
legacy07 said:
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
it meams its just like the updated version of decrypt.zip? thanks sir.
Which one of these two files should be flashed
Karthik kollapureddy said:
Which one of these two files should be flashed
Click to expand...
Click to collapse
Choose according to whether you have to encrypt or decrypt
legacy07 said:
Choose according to whether you have to encrypt or decrypt
Click to expand...
Click to collapse
I'm a beginner so would you please tell me what's encypt and decrypt
---------- Post added at 06:32 AM ---------- Previous post was at 06:29 AM ----------
Karthik kollapureddy said:
I'm a beginner so would you please tell me what's encypt and decrypt
Click to expand...
Click to collapse
I'm confused and the rooting step
Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.
sintoo said:
Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.
Click to expand...
Click to collapse
This mod works in X01BD and X00TD. Not sure if it work for Z01BD. You can flash this patch by following the steps in the thread but success isn't guaranteed. Take a system backup as if anything goes wrong. Also be ready to loose your data
legacy07 said:
... So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
I'm not sure about that... I am flashing this file (decrypt pie) for Oreo just. The phone does not boot in this case. I was forced to flashing old decrypt file for Oreo after and it all worked again.
It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?
anagramgenius said:
It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?
Click to expand...
Click to collapse
I think twrp official has decryption issues. Check with twrp 3.2.3
legacy07 said:
I think twrp official has decryption issues. Check with twrp 3.2.3
Click to expand...
Click to collapse
I checked with Rk585's TWRP 3.2.3 too. Same issue persists. It worked fine when I was in Oreo.
After flashing the zip, I booted back to recovery and copied the fstab.qcom to my PC to check if it has been replaced with the flashed zip. It did replace it. But when I boot to system, it starts encrypting my device and TWRP gets replaced by stock recovery. So I flashed the TWRP again and checked the fstab.qcom. Voila. It was unpatched. I don't know what is happening during the boot. The patched fstab is getting replaced by original fstab.
Edit: Seems there is a problem with the zip I guess. Or more files need to be patched to disable forced encryption in stock Pie rom. I tested in both PBRP and OFRP.
Case 1: I flashed stock rom in Official TWRP, then flashed PBRP zip and booted into PBRP. After booting into PBRP, it doesn't automatically disable forced encryption if no rom zip is flashed in it. So I flashed the decrypt zip provided in this OP. Then I booted to system, it started encrypting my device.
Case 2: I flashed stock rom in Official TWRP, then flashed OFRP zip and booted into OFRP. After booting into OFRP, it automatically disabled forced encryption even though no rom zip was flashed. Hence after booting into system, it didn't automatically encrypt my device as forced encryption was disabled automatically by OFRP.
So PBRP and OFRP do something else to disable forced encryption other than just patching fstab.qcom. Atleast in stock Pie rom. That's why I'm unable to disable forced encryption by flashing decrypt zip in any of the recoveries unless it is patched by recoveries themselves.