Related
Hello,
I've just installed the new OOS4.0, and I also wanted to update the filesystem to F2FS:
I've managed to get everything working with twrp-3.0.2-1.28 (ext4 cache/system - f2fs userdata) but then, I enrcypted the data via the settings menu, and now the TWRP fails to decrypt (password invalid). I understand that this is some kind of incompatibility since if I try with the official recovery it decrypts without problems.
Since I still have to copy all my userdata to the phone and install everything, what should I do before?
a) Keep data encrypted and wait for a TWPR fix, and eventually flash with the official recovery if needed?
b) Reformat and keep the data unencrypted?
c) You tell me?
Thank you for your help.
This is the only reason why I am still waiting for a proper twrp first. Don't want to decrypt my storage, and move all the data from my phone to laptop and then back to phone. Too much of a hassle.
Hurizen said:
Hello,
I've just installed the new OOS4.0, and I also wanted to update the filesystem to F2FS:
I've managed to get everything working with twrp-3.0.2-1.28 (ext4 cache/system - f2fs userdata
Click to expand...
Click to collapse
I can't answer your question, but can I ask how you converted the data partition from ext4 to f2fs? I have TWRP 3.0.2-1.28 and OOS 4.0 already installed, and was wondering what the best way to do it is.
Do custom ROMS such as CM14.1 and XenonHD support f2fs?
Now, if I'm on OOS 4.0, no root, stock recovery; how can i get F2FS?? Thanks!
Hurizen said:
Hello,
I've just installed the new OOS4.0, and I also wanted to update the filesystem to F2FS:
I've managed to get everything working with twrp-3.0.2-1.28 (ext4 cache/system - f2fs userdata) but then, I enrcypted the data via the settings menu, and now the TWRP fails to decrypt (password invalid). I understand that this is some kind of incompatibility since if I try with the official recovery it decrypts without problems.
Since I still have to copy all my userdata to the phone and install everything, what should I do before?
a) Keep data encrypted and wait for a TWPR fix, and eventually flash with the official recovery if needed?
b) Reformat and keep the data unencrypted?
c) You tell me?
Thank you for your help.
Click to expand...
Click to collapse
Well, I have tested this method both on OpenBeta9/10 and OSS4.0-
MOST IMPORTANT - FLASH TWRP .23, .28 HAVE BUGS WITH DECRYPTION AND F2FS (TESTED AND REPORTED BY MANY USERS)
1.) Flash 4.0 through stock recovery for dm verity error or flash 4.0 modem + firmware through twrp, skip this step if u r already on 4.0
2.)Copy all internal data to pc and make nandroid backup if needed.
3.)Wipe data to f2fs and cache/system to ext4.
4.)As wiping all these partitions, decryption will be gone and rom will be wiped, flash ur OSS 4.0(I prefer Builds like Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 OR HyperStock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-t3521946 , this one doesn't tiggers encryption and dm verity error.)
5.)Wipe cache and dalvik and reboot.
6.)Setup and install DiskInfo app to check partitions.
I know this method is bit lengthy, but u will get as u needed, decryption and f2fs for data with no dm verity errors.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
abhibnl said:
This is the only reason why I am still waiting for a proper twrp first. Don't want to decrypt my storage, and move all the data from my phone to laptop and then back to phone. Too much of a hassle.
Click to expand...
Click to collapse
Pachulongui said:
Now, if I'm on OOS 4.0, no root, stock recovery; how can i get F2FS?? Thanks!
Click to expand...
Click to collapse
Well, u can try flashing stock recovery and do factory resets for 1-2 times.
I have tested this on ob9 and got f2fs without wiping storage( As told by devs)
If this method doesn't works, then simply unlock bootloader, flash twrp and decrypt data with fastboot or through twrp cos someday u have to decrypt ur data.
Grab a holiday or sunday, copy all data and backups.
Enjoy F2FS life. :good:
LELBOT said:
Well, I have tested this method both on OpenBeta9/10 and OSS4.0-
MOST IMPORTANT - FLASH TWRP .23, .28 HAVE BUGS WITH DECRYPTION AND F2FS (TESTED AND REPORTED BY MANY USERS)
1.) Flash 4.0 through stock recovery for dm verity error or flash 4.0 modem + firmware through twrp, skip this step if u r already on 4.0
2.)Copy all internal data to pc and make nandroid backup if needed.
3.)Wipe data to f2fs and cache/system to ext4.
4.)As wiping all these partitions, decryption will be gone and rom will be wiped, flash ur OSS 4.0(I prefer Builds like Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 OR HyperStock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-t3521946 , this one doesn't tiggers encryption and dm verity error.)
5.)Wipe cache and dalvik and reboot.
6.)Setup and install DiskInfo app to check partitions.
I know this method is bit lengthy, but u will get as u needed, decryption and f2fs for data with no dm verity errors.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Well, u can try flashing stock recovery and do factory resets for 1-2 times.
I have tested this on ob9 and got f2fs without wiping storage( As told by devs)
If this method doesn't works, then simply unlock bootloader, flash twrp and decrypt data with fastboot or through twrp cos someday u have to decrypt ur data.
Grab a holiday or sunday, copy all data and backups.
Enjoy F2FS life. :good:
Click to expand...
Click to collapse
I was using OOS 3.2.7 official and yesterday I thought of getting OOS 4.0 on my OP3. And I did flash the Experience ROM via Twrp - 3.0.2-1.28, but I was still on ext4 file system.. And I was getting a dm-verity error.. Then I decided to change the /data file system to f2fs and reflashed the Experience ROM. Now Diskinfo does shows my file system as f2fs but how to get rid of this dm-verity error with this Rom intact as I've done the setup of all my apps that I had before...
sanjeevrai97 said:
I was using OOS 3.2.7 official and yesterday I thought of getting OOS 4.0 on my OP3. And I did flash the Experience ROM via Twrp - 3.0.2-1.28, but I was still on ext4 file system.. And I was getting a dm-verity error.. Then I decided to change the /data file system to f2fs and reflashed the Experience ROM. Now Diskinfo does shows my file system as f2fs but how to get rid of this dm-verity error with this Rom intact as I've done the setup of all my apps that I had before...
Click to expand...
Click to collapse
Brother, as u have flashed experience rom which already contains 4.0 modem + firmware, then dm verity shouldnt pop up.
Try to download and flash 4.0 modem+ firmware again through twrp, if this didnt help then try Hyper Rom.
If nothing helps, then follow the procedure i mentioned, backup all apps through titanium backup and sync all google stuff, make nandroid if any thing goes wrong, download official 4.0 full zip, flash stock oxygen recovery and do a adb side load.
Then flash twrp and clean flash experience or hyper rom u needed and restore apps back with titanium backup.
Report if something goes wrong
LELBOT said:
Brother, as u have flashed experience rom which already contains 4.0 modem + firmware, then dm verity shouldnt pop up.
Try to download and flash 4.0 modem+ firmware again through twrp, if this didnt help then try Hyper Rom.
If nothing helps, then follow the procedure i mentioned, backup all apps through titanium backup and sync all google stuff, make nandroid if any thing goes wrong, download official 4.0 full zip, flash stock oxygen recovery and do a adb side load.
Then flash twrp and clean flash experience or hyper rom u needed and restore apps back with titanium backup.
Report if something goes wrong
Click to expand...
Click to collapse
I did try to do the last thing that you mentioned. I flashed the official 4.0 through sideload. And dm-verity issue did vanish. But I thought of changing everything to f2fs. So I changed the type of system, data and cache. And flashed the Experience rom. But then, a strange thing started to happen. I just couldn't save any screenshot or pics I click but I was able to install or delete apps. So, I again went to TWRP (was really a hassle because I had to delete everything on phone and change system and cache to ext4 leaving just the data on f2fs and then doing several reboots and factory resets to get everything working). And then I flashed Experience Rom and I'm back to square one with dm-verity...
Still, I'd try to flash 4.0 firmware + modem files explicitly. And then I'll report. Thanks for the info, brother. :good:
EDIT: I tried to flash the 4.0 firmware + modem files but no luck with dm-verity issue..
Btw, I've a question. What's the downside of having this issue besides having that splash screen of warning on every boot up?
Can anyone properly give instruction on how to install OOS 4.0 without getting dm error + F2FS?
there's a lot of instruction in other thread that making this confusing.
sanjeevrai97 said:
I did try to do the last thing that you mentioned. I flashed the official 4.0 through sideload. And dm-verity issue did vanish. But I thought of changing everything to f2fs. So I changed the type of system, data and cache. And flashed the Experience rom. But then, a strange thing started to happen. I just couldn't save any screenshot or pics I click but I was able to install or delete apps. So, I again went to TWRP (was really a hassle because I had to delete everything on phone and change system and cache to ext4 leaving just the data on f2fs and then doing several reboots and factory resets to get everything working). And then I flashed Experience Rom and I'm back to square one with dm-verity...
Still, I'd try to flash 4.0 firmware + modem files explicitly. And then I'll report. Thanks for the info, brother. :good:
EDIT: I tried to flash the 4.0 firmware + modem files but no luck with dm-verity issue..
Btw, I've a question. What's the downside of having this issue besides having that splash screen of warning on every boot up?
Click to expand...
Click to collapse
As, I posted above, wipe data to f2fs and sys/cache be ext4, no changing them.
you have to follow the procedure i mentioned.
U can check this also, he posted almost the same as mine - https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
burningDew said:
Can anyone properly give instruction on how to install OOS 4.0 without getting dm error + F2FS?
there's a lot of instruction in other thread that making this confusing.
Click to expand...
Click to collapse
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-SuperSU-v2.79-20161211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-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.
^thanks for the instructions
LELBOT said:
As, I posted above, wipe data to f2fs and sys/cache be ext4, no changing them.
you have to follow the procedure i mentioned.
U can check this also, he posted almost the same as mine - https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
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=0BzS3nWITUqU_Sk5yQkRqWkhFY3c&export=download
Official Recovery ( Oxygen OS ) - http://oneplusroms.s3.amazonaws.com...694818&Signature=DSUZrSJyV46Dd/JKBmI3Z1Dri5Q=
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-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.
Thank you for root users.
But if you flash Oxygen recovery & Oos 4.0 via adb you have just to wipe all in Oxygen recovery and your partition data make f2fs ?
After flash Twrp and custom Oos build.
I read in many post for flash Oos 4.0 you must have Twrp modify 28 ? With the 23 work too.
The problem they are no solution for root user to format data f2fs and flash custom Oos 4.0 directly with Twrp ?
Many root users flash custom Oos 4.0 with Twrp 27 but don't format to f2fs ! Stay in Ext4 and that run great. Ex : Fos.
---------- Post added at 06:49 AM ---------- Previous post was at 06:22 AM ----------
Hi ! Every body good news the dev blu_spark realese the new Twrp work with encrypt f2fs ?
Thanks blu_spark ?
Twrp-3.0.2.0_blu_spark_vll-op3
Click to expand...
Click to collapse
i used this method to solve the problem
On my phone what ever oos i install, 4.0, 4.0.1, 4.0.2, data it's formated to F2FS.
To remove DM-verity message it's easy.
Boot to FASTBOOT and type this commands one after another:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Now i'm on FreeDom 2.3 (oos 4.0.2) with twrp-3.0.3 x v.15 blu spark 23.01.17
null0seven said:
On my phone what ever oos i install, 4.0, 4.0.1, 4.0.2, data it's formated to F2FS.
To remove DM-verity message it's easy.
Boot to FASTBOOT and type this commands one after another:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Now i'm on FreeDom 2.3 (oos 4.0.2) with twrp-3.0.3 x v.15 blu spark 23.01.17
Click to expand...
Click to collapse
For dm_verity, only the enable command is necessary, not the disable one.
It was like that in original post.
Hey XDA m8s,
i want to decrypt my OP 3. So i completely cleared it and fresh installed OOS Beta 10. Now its still encrypted. I did this 5-10 times.
Bootloader: Unlocked
Recovery now: Stock
1. Tried fastboot wipe userdata
2. Tried TWRP Data Reset
3. TriedAndroid normal Factory Reset
4. Tried to install OOS with Stock and TWRP Recovery
Everytime I install OOS 4 or Beta 10 TWRP asks me for a password after installation to decrypt File System. I dont have any password and i dont encrypted my device.
And now there is coming a dm-verity error everytime i boot. I dont know what that means...
The device is working but i cant flash TWRP and install SuperSU or other Zips cause of this ****ty password that i dunno.
Any ideas??
thx m8s
blackjan
blackjan said:
Hey XDA m8s,
i want to decrypt my OP 3. So i completely cleared it and fresh installed OOS Beta 10. Now its still encrypted. I did this 5-10 times.
Bootloader: Unlocked
Recovery now: Stock
1. Tried fastboot wipe userdata
2. Tried TWRP Data Reset
3. TriedAndroid normal Factory Reset
4. Tried to install OOS with Stock and TWRP Recovery
Everytime I install OOS 4 or Beta 10 TWRP asks me for a password after installation to decrypt File System. I dont have any password and i dont encrypted my device.
And now there is coming a dm-verity error everytime i boot. I dont know what that means...
The device is working but i cant flash TWRP and install SuperSU or other Zips cause of this ****ty password that i dunno.
Any ideas??
thx m8s
blackjan
Click to expand...
Click to collapse
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process
Hw4ng3r said:
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process
Click to expand...
Click to collapse
I flashed the official nougat update yesterday using the stock recovery and I somehow got the dm-verity error? I heard somewhere that I had to reflash the stock recovery even tho I already have it? I used to have TWRP but that was back in 3.2.2 of Oxygen OS but I switched back because I wanted OTA updates too work
Hw4ng3r said:
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process
Click to expand...
Click to collapse
Is the Dm verity error cause of android 7?
blackjan said:
Is the Dm verity error cause of android 7?
Click to expand...
Click to collapse
That DM verity screen is not an "Error" screen its just "Warning" screen meaning that the FW files were not digitaly signed. Its something Google introduced a while ago but has really started pushing since Nougat. There's no way to avoid it (except to flash a seperate script to disable it) theres one floating around here but might have been in Nexus thread. Personally i flashed 3.2.8 Fw after flashing OOS 4 and it got rid of the "Warning" but that might cause issues down the road. As of now though all is running as it should. hope this helped
Sent from my OnePlus Pixel using XDA Labs
blackjan said:
Hey XDA m8s,
i want to decrypt my OP 3. So i completely cleared it and fresh installed OOS Beta 10. Now its still encrypted. I did this 5-10 times.
Bootloader: Unlocked
Recovery now: Stock
1. Tried fastboot wipe userdata
2. Tried TWRP Data Reset
3. TriedAndroid normal Factory Reset
4. Tried to install OOS with Stock and TWRP Recovery
Everytime I install OOS 4 or Beta 10 TWRP asks me for a password after installation to decrypt File System. I dont have any password and i dont encrypted my device.
And now there is coming a dm-verity error everytime i boot. I dont know what that means...
The device is working but i cant flash TWRP and install SuperSU or other Zips cause of this ****ty password that i dunno.
Any ideas??
thx m8s
blackjan
Click to expand...
Click to collapse
Goto TWRP and wipe>factory reset
copy SuperSU zip using TWRP MPT support and flash now boot systems the twrp wont ask for password nor wil you ge DM-verity error
Hw4ng3r said:
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process
Click to expand...
Click to collapse
Scronix said:
Goto TWRP and wipe>factory reset
copy SuperSU zip using TWRP MPT support and flash now boot systems the twrp wont ask for password nor wil you ge DM-verity error
Click to expand...
Click to collapse
is there a method to flash systemless SuperSU without doing a Factory Reset? // What is the password when i boot to TWRP when Android installed? On Android 6 was it possible? Is it new that Android encrypt the Filesystem or what??
blackjan said:
is there a method to flash systemless SuperSU without doing a Factory Reset? // What is the password when i boot to TWRP when Android installed? On Android 6 was it possible? Is it new that Android encrypt the Filesystem or what??
Click to expand...
Click to collapse
ich hab gerade das selbe problem aber ich fürchte das nur ein entschlüsseln hilft ( also fastboot format userdata ). Und vor dem 1. start der systems eben supersu flashen.
english: I have the same problem and I think the only solution is a complete decrypt. And after this, flash supersu before you boot the system the first time.
blackjan said:
is there a method to flash systemless SuperSU without doing a Factory Reset? // What is the password when i boot to TWRP when Android installed? On Android 6 was it possible? Is it new that Android encrypt the Filesystem or what??
Click to expand...
Click to collapse
The New Android 7.0 Nougat Introduced a bit of a secure partition Which Encrypt the system without asking The New Twrp Isnt Completely Compatible yet Due to New Kernel Sources not released This is a workaround to have root you have to factory reset in TWRP once to get it working
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,encryption and dm verity will be gone and 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.
oneplus fooling us??
is the open beta 10 and oxygen os OTA same????? they havent uploaded any links on the oneplus downloads page
You worry to much for a 2 seconds message...
Hello,
it seems to be that sth went wrong today. I wanted to factory reset my OP3 but right now nothing is working.
The initial set up was the following:
Unlocked bootloader with TWRP installed. Oxygen OS + several custom ROMs installed
What I did:
I deleted the data from system partition since I thought that they Oxygen OS system data will be deleted.
Problem:
Right now I get a encryption hint without the possibiity to factory reset my OP3 since I don´t get access to the data partition in order to upload a Oxygen OS .zip on my OP 3 from my PC.
What can I do in oder to factory reset my OP3 with the help of my PC? I want to install the OnePlus 3 OxygenOS Open Beta 28.
Search mega unbrick guide method 2 and then flash the last OnePlus recovery and then flash OB28
I managed to flash the most current Oxygen OS on my OP3 by doing a factory reset within TWRP and flashing the Oxygen OS .zip and Magisk 4.5.
BUT after rebooting, the file system seems to be encrypted again in TWRP (even allowing explicitly file modifications!). This means that I am not able to flash another .zip.
How can I manage that the file system remains decrypted also in TWRP?
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
king0r said:
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
Click to expand...
Click to collapse
If you boot OOS without any force encryption disabling mod them it will encrypt. It's not a problem at all if you use the right TWRP. Pick the TWRP from the Bluspark thread and you should be fine.
king0r said:
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
Click to expand...
Click to collapse
Well, there is a way to decrypt the device, but you'll lose everything. Reboot do fastboot and connect to pc, then type from CMD "fastboot erase userdata" or "fastboot format userdata"
Puddi_Puddin said:
If you boot OOS without any force encryption disabling mod them it will encrypt. It's not a problem at all if you use the right TWRP. Pick the TWRP from the Bluspark thread and you should be fine.
Click to expand...
Click to collapse
Please send me a link to the thread. I can't find it.
king0r said:
Please send me a link to the thread. I can't find it.
Click to expand...
Click to collapse
http://lmgtfy.com/?iie=1&q=Bluspark+oneplus+3t
If you pay attention, it also explains how searching in the internet works. It's littery the first result if you google "Oneplus 3 Bluspark".
I was already using
twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img !!!
BUT nevertheless I don't have access to any file (e.g. .zip) even using the newest version of the Bluspark TWRP. Every directory is listed with 0 Bytes.
When accessing TWRP an Error message comes up but I can allow file modifications. But this doesn't help to get access to any file.
Flash the stock recovery
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Then after flash stock recovery boot to recovery all wipe (internal storage will be deleted). Done!
Flash official or Blu spark twrp. Go to Mount>check the internal storage.
madsponge26 said:
Flash the stock recovery
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Then after flash stock recovery boot to recovery all wipe (internal storage will be deleted). Done!
Flash official or Blu spark twrp. Go to Mount>check the internal storage.
Click to expand...
Click to collapse
Thanks, but this means that I will lose all my data located on my phone??
Will at least the already installed OOS remain?
king0r said:
Thanks, but this means that I will lose all my data located on my phone??
Will at least the already installed OOS remain?
Click to expand...
Click to collapse
Well, if you can't access your data with TWRP then you are ****ed any way.
I can only not access the data in Recovery! In OOS no peoblems at all!!
I don't understand why in Recovery nö data access is possible.
Hi, yesterday i've got OTA on stock rom, i reflash stock because i was rooted before, and after succesfully update, i tried to flash no verity from twrp 3.2.3.0 and magisk. I booted ok, the root is present, everything is fine but the phone is encrypted. I knew that no verity decrypt the phone but for me doesnt. Somebody knows or tried to root oreo stock? Thank you
To start with flashing magisk should mean you don't need to flash the no verity zip
Also only the official twrp from my thread will support encryption
Also if you change roms you must format data to remove encryption else the phone will boot to the encryption screen & will tell you the password is wrong
You can either format data in twrp - wipe format data (not advanced wipe. The option to the right of advanced wipe)
Or in fastboot enter the command
fastboot erase userdata
Note this will format everything on internal storage
Once you have booted the new rom you can encrypt again
I have official twrp 3.2.3.0, the phone is encrypted and rooted, but i want to be decrypted and i can't do that. I formated all phone, all data, in magisk appear checked preserved encryption.
I don't want to change rom, I only want stock and root, but not encryption
woozie.2007 said:
I don't want to change rom, I only want stock and root, but not encryption
Click to expand...
Click to collapse
If it was previously encrypted you still need to format data
This will remove encryption and everything on internal storage will be deleted
Then it should just be a case of flashing the latest version of Magisk
I don't have this device so I can't test it
The stock kernel may require forced encryption so you may not have a choice with stock but I can't check that
I just update ota 8.1, after that i flashed twrp via fastboot, then magisk 15.3. latest magisk didnt work, but i tried to flash no verity but the encryption still there even i formated all data and i configured the phone from zero
woozie.2007 said:
I just update ota 8.1, after that i flashed twrp via fastboot, then magisk 15.3. latest magisk didnt work, but i tried to flash no verity but the encryption still there even i formated all data and i configured the phone from zero
Click to expand...
Click to collapse
If you formatted data in twrp
Wipe - select option on right
Or
Format data as a different partition type then format it back to what it was
Will remove encryption
Also
fastboot erase userdata
Should do the same
You should get no prompt to enter decrypt key as device should no longer be encrypted
TheFixItMan said:
If you formatted data in twrp
Wipe - select option on right
Or
Format data as a different partition type then format it back to what it was
Will remove encryption
Also
fastboot erase userdata
Should do the same
You should get no prompt to enter decrypt key as device should no longer be encrypted
Click to expand...
Click to collapse
doesn't work...
woozie.2007 said:
doesn't work...
Click to expand...
Click to collapse
Without your device I can only put it down to user error as that's how I've always removed encryption
TheFixItMan said:
Without your device I can only put it down to user error as that's how I've always removed encryption
Click to expand...
Click to collapse
i know and i understand, i do it for many times on nougat, but now on oreo doesnt works, anyway thank you for help me
So, every method i tried i didnt succeed to make the phone unencrypted. I root it with magisk 17.1, in play store appears to be not certified. Is any problem? I mention before with 7.0 and magisk the phone was certified. Sugestions? Thanks
woozie.2007 said:
So, every method i tried i didnt succeed to make the phone unencrypted. I root it with magisk 17.1, in play store appears to be not certified. Is any problem? I mention before with 7.0 and magisk the phone was certified. Sugestions? Thanks
Click to expand...
Click to collapse
Change the device fingerprint
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Install above magisk module
In a terminal emulator (playstore) run the following
su
props
Select option to change fingerprint & change to a working moto g5 (or similar) fingerprint
Restart phone
Thank you sir, now appear certified in play, is still encrypted but rooted, i think is ok, right?
Hello guys,
I'm a bit confused now from reading through different posts, each describing different methods.
Why can't we just Flash the IMG of Oreo like we would do with Stock Nougat?
Is this because it's still soak and hasn't really been released yet or am I missing something?
Also, where's the difference to just flash Stock Nougat and update to Oreo via the System Update button in the settings (that's called OTA, right?)?
Also I read "Flashing bootloader of equal or minor version will hardbrick your device"
Does that mean if I Flash that 2 times I Flash the same bl Version and I hardbrick my device?
I'm from Germany btw.
NPPS25.137.7 2.4 (I read, I have to be on 137.93.2.5 but I can just either flash it directly or flash an earlier stock and update until I'm there I guess?)
XT1676
Boot loader: B8.23
Note: I thought it would be better to post that in q&a instead of the reply section of the stock Oreo fastboot update post, since this are kind of general questions to the Oreo update topic.
Greetings,
7080
Flashing an oero stock rom firmware image is exactly the same as flashing a nougat stock rom firmware image (although there's a few more img_sparsechunks to flash)
You won't brick your phone if the firmware you are flashing the the same or newer
You will brick your phone if you try and flash a gpt & bootloader that is lower than the version currently on your phone
You can downgrade by flashing everything except these parts
There's no difference to flashing an ota via stock recovery to doing it via system update - however you must be on a fully unmodified stock rom else it will fail and potentially brick your phone
Don't confuse flashing an ota with flashing a complete stock rom firmware image
And ota must meet certain requirements - eg must be on a certain stock firmware version
A stock firmware image (complete stock firmware) can be flashed on any device (to which the image is for) that has the same or older bootloader version
TheFixItMan said:
Don't confuse flashing an ota with flashing a complete stock rom firmware image
And ota must meet certain requirements - eg must be on a certain stock firmware version
A stock firmware image (complete stock firmware) can be flashed on any device (to which the image is for) that has the same or older bootloader version
Click to expand...
Click to collapse
Thank you!
It took me some time to find out that OTA's only apply from one specific version to an other (the post from "tfwboredom" with all OTA's he was able to catch was a big help) and when i didnt get any OTA's (after flashing stock Nougat) i did an OTA update via adb. After that, my phone offered me OTA's again and i could upgrade until Oreo --.13 i guess. I rediscovered a thread with the full fastboot stock Oreo firmware --.16 then (forgot i already had downloaded it with my phone to my sd ^^) and flashed this then with the computer.
My Problem right now is the thing with the auto encryption.
Im on OPP28.85-16 now with TWRP64bit installed and was also able to get root by flashing newest Magisk (18.0) and the f2fs-loopback-bug-workaround (I dont really know for what that is) and installing MagiskManager v6.1 after booting system.
However, when i return to twrp after booting into system it asks me for a password to disable encryption and also wont flash things properly until i format data or do a factory reset. But after booting into system this encryption will be applied again. Flashing no-verity-encrypt didnt solve the problem.
What i want to find out now is:
1. Why is it automatically encrypting again and how can i disable that?
2. When i disabled that, can i encrypt my phone in the settings and use that password then to unlock twrp?
3. Where is the difference between this auto encryption and when i click in system settings on encrypt phone?
As far as i understood, in Nougat no-verity-encrypt was to prevent the dm-verity...thing to encrypt your phone but i could still enable encryption in the system settings.
(4. what is the purpose of f2fs bug fix?) - and has it enything to do with encryption?
G5-User7080 said:
Thank you!
It took me some time to find out that OTA's only apply from one specific version to an other (the post from "tfwboredom" with all OTA's he was able to catch was a big help) and when i didnt get any OTA's (after flashing stock Nougat) i did an OTA update via adb. After that, my phone offered me OTA's again and i could upgrade until Oreo --.13 i guess. I rediscovered a thread with the full fastboot stock Oreo firmware --.16 then (forgot i already had downloaded it with my phone to my sd ^^) and flashed this then with the computer.
My Problem right now is the thing with the auto encryption.
Im on OPP28.85-16 now with TWRP64bit installed and was also able to get root by flashing newest Magisk (18.0) and the f2fs-loopback-bug-workaround (I dont really know for what that is) and installing MagiskManager v6.1 after booting system.
However, when i return to twrp after booting into system it asks me for a password to disable encryption and also wont flash things properly until i format data or do a factory reset. But after booting into system this encryption will be applied again. Flashing no-verity-encrypt didnt solve the problem.
What i want to find out now is:
1. Why is it automatically encrypting again and how can i disable that?
2. When i disabled that, can i encrypt my phone in the settings and use that password then to unlock twrp?
3. Where is the difference between this auto encryption and when i click in system settings on encrypt phone?
As far as i understood, in Nougat no-verity-encrypt was to prevent the dm-verity...thing to encrypt your phone but i could still enable encryption in the system settings.
(4. what is the purpose of f2fs bug fix?) - and has it enything to do with encryption?
Click to expand...
Click to collapse
You need to format data to remove encryption
Wipe - option on the right
If you encrypt again once booted you need to use a twrp that supports encryption - the 64bit version posted in most rom threads don't support encryption but I did post the source code to my test version which someone compiled which may have encryption support
You can try it
https://drive.google.com/file/d/1kgFyYfjEyqAEXOGjg_UfeedlQwaLVF1F/view
All you should need to do is flash magisk - try version 17
You probably will need to change the device fingerprint to pass CtsProfile
Use this module
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
TheFixItMan said:
You need to format data to remove encryption
Wipe - option on the right
Click to expand...
Click to collapse
- Yes, i did that, but when i boot system after it and return to twrp its again encrypted, but ill try a clean stock oreo flash -> twrp -> format data -> reboot -> return to twrp
If you encrypt again once booted you need to use a twrp that supports encryption - the 64bit version posted in most rom threads don't support encryption but I did post the source code to my test version which someone compiled which may have encryption support
You can try it
https://drive.google.com/file/d/1kgFyYfjEyqAEXOGjg_UfeedlQwaLVF1F/view
Click to expand...
Click to collapse
- Oh ok, i switched to 64bit version because of efs backup when still on Nougat, but i read somewhere that the 32bit version has that now, too, so could i also go just back to 32bit twrp?
As far as i remember, i never had a Problem with encryption on Nougat with 64bit.
- What does that mean that twrp supports encryption, when data gets encrypted every time, how should twrp be able to read that then?
All you should need to do is flash magisk - try version 17
Click to expand...
Click to collapse
- why 17 and not 18? i mean 18 worked when i tried it?
You probably will need to change the device fingerprint to pass CtsProfile
Use this module
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
- I have currently no lock enabled, because i want to do a twrp backup after everything is done, what is the problem with fingerprint and what is CtsProfile?
I'll try that things out, thank you, and edit this when i find some things out
What i want at the end is a rooted Oreo (done) with a working twrp, where i can still flash and backup and restore without wiping data every time and if possible i want to use the normal encryption (the one when i boot system and set it up in settings).
I still dont really get what this auto encryption is.
As far I was aware the 64bit twrp cannot decrypt data apart from the test one I posted
If you don't have a twrp that supports data encryption your phone will still work, you just won't be able to use/flash zips to the data partition or backup/restore that partition
If you get a decrypt data when you boot your phone normally and it doesn't decrypt then you must remove encryption and boot the rom first before applying encryption again
My official 32bit twrp does support data encryption and will work on any 32bit rom including stock oero
Use any version of Magisk that works for you - I no longer own this device & only tested with magisk 17
Everything worked pretty well until i wanted to restore an older backup, I tried to format data before doing the restore but it failed.
After i flashed twrp (official 32bit this time) i did a factory reset to remove decryption and rebooted recovery to prevent the system fromr eplacing it. But when i use format data after that (or already in first place, could be that i tried that, too) it fails, it sais data successfully decrypted and continues and then theres an error. And when i try then a factory reset, too it fails, too.
However, after changing file system to ext4 and than formatting again (i dont remember exactly) i endet up with a working f2fs data partition and was able to use format data and restore backup,...
I am very confused now, because i dont get at all what the heck is the problem, should i not format data and do factory reset or does this happen when i flash the f2fs bug workaround before or is it because i booted the system and begun to change the settings, i have no idea,.. but ill try out and write you when i find something out!
EDIT:
Ok i found some things out, still dont understand at all, but it seems that
format data fails after booting into system
but works after rebooting twrp again
factory reset fails after format data fails
but works after format data works
works not after rebooting twrp, only if format data was successfull before (bec that works again after rebooting twrp)
rebooting system after format data failed will result into a bootloop into recovery with error when trying to enter recovery after manually going to bootloader -> recovery it works
It may help to see it in a table:
After flashing Oreo(boots up) and then twrp:
format data failed
factory reset failed
After flashing Oreo(boots up) and twrp and rebooting twrp:
format data successfull
factory reset successfull
reboot system
reboot twrp
format data failed
factory reset failed
reboot system results in bootloop into recovery with error
reboot twrp
factory reset failed
format data successull
reboot system
reboot twrp
factory reset successull
format data failed
factory reset failed
reboot twrp
factory reset failed
format data successull
factory reset successull
Output when format data fails:
Code:
[CODE]Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
I guess thats the log from twrp start and what followes is the one for format data
Code:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 /dev/block/mmcblk0p54 process ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount Storage
[/CODE]
And for factory reset after it:
Code:
Failed to mount '/data' (Device or resource busy)
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount storage
Try a
fastboot erase userdata
Type this in cmd on pc with phone connected via USB in bootloader mode
This will erase everything on internal
TheFixItMan said:
Try a
fastboot erase userdata
Type this in cmd on pc with phone connected via USB in bootloader mode
This will erase everything on internal
Click to expand...
Click to collapse
when should i do that?
Instead of using frmat data?
So when i flash twrp and boot into it first thing i should do is format data right? So i should just after flashing erase userdata and THEN enter twrp or what?
I'll copy in my reply from an other thread where 2 ppl tried to help me.
G5-User7080 said:
hmm, i did as follows:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery and factory reset
reboot recovery
flash magisk 18
reboot system
install magisk 6.1 apk
The thing is, when i dont reboot recovery after its installation the system will overwrite it with stock recovery and as far as i understood i need to reboot twrp for that.
I just did as i did for Nougat there regarding the post from 'Johny Cipeli':
6. In the Decrypt /data screen, press cancel, then "Swipe to Allow Modifications"
7. Go to WIPE, then "Swipe to Factory Reset"
8. Come back to TWRP main menu, go to REBOOT, then RECOVERY, then DO NOT INSTALL
So should i do then:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery
reboot recovery
format data
flash magisk 18
reboot system
install magisk 6.1 apk
or is this irrelevant if i first format data, then reboot twrp and then flash magisk?
Why do you flash no-verity? I tried that out earlier but it made no difference on the standard encryption.
I tryed a bit around with the data errors and found some things out, would you mind switching to this thread for the following?
Thank you for helping me, I just get totally confused by the Oreo process,.. worked so easy on nougat
Click to expand...
Click to collapse
As I rooted the device it was on Oreo OPS28.85-13-3 by OTA and I did it like this:
flash latest official twrp 3.2.3.1
make a backup of EFS and persist
boot recovery (now it prompts you to give in a decryption code, just press skip)
format data (F2FS)
don't reboot now
flash magisk 18 (I flashed 17.2 and updated later, no clue why)
reboot to system
install magisk 6.1 apk (if it's missing, in my case it was present)
if you reboot to twrp now it shouldn't prompt you to give in a decryption key anymore
G5-User7080 said:
when should i do that?
Instead of using frmat data?
So when i flash twrp and boot into it first thing i should do is format data right? So i should just after flashing erase userdata and THEN enter twrp or what?
I'll copy in my reply from an other thread where 2 ppl tried to help me.
Click to expand...
Click to collapse
It's the same as format data in twrp
To have it all in one Thread:
Wolfcity said:
So if you can't decrypt your data partition by formatting it (F2FS) and flashing magisk right after it without a reboot in between it may be possible that the bug is still present.
In that case you can give it a try and flash the fix from TWRP, maybe one of the older versions because the latest ones doesn't work for everyone.
Click to expand...
Click to collapse
hmm, i did as follows:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery and factory reset
reboot recovery
flash magisk 18
reboot system
install magisk 6.1 apk
The thing is, when i dont reboot recovery after its installation the system will overwrite it with stock recovery and as far as i understood i need to reboot twrp for that.
I just did as i did for Nougat there regarding the post from 'Johny Cipeli':
6. In the Decrypt /data screen, press cancel, then "Swipe to Allow Modifications"
7. Go to WIPE, then "Swipe to Factory Reset"
8. Come back to TWRP main menu, go to REBOOT, then RECOVERY, then DO NOT INSTALL
So should i do then:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery
reboot recovery
format data
flash magisk 18
reboot system
install magisk 6.1 apk
or is this irrelevant if i first format data, then reboot twrp and then flash magisk?
woozie.2007 said:
i dont think so, I rooted in that method, after update to oreo 8.1 stock, i flash official terp, then I flashed no verity 6.0 adn then format data partition. After that i booted in android, it say is encrypted, i can't decrypt it, but it works very well. I rooted two moto g5 stock oreo in that mode. Good luck
Click to expand...
Click to collapse
Why do you flash no-verity? I tried that out earlier but it made no difference on the standard encryption.
woozie.2007 said:
i flashed no verity because i want to decrypt the phone, but i didnt do that, not works, but works twrp for flashing, backup and restore without any problems. I cant say because of no verity or not, but it works. My phone is encrypted, but rooted with magisk 18.0 and i can install any module i want
Click to expand...
Click to collapse
As far as i know from 'TheFixItMan', he said that the 32bit twrp is able to surpass the encryption somehow.
But i guess this is kind of a standard encryption and not the "real encryption" could that be?
Because, i thought encryption means, you have to enter a password on boot to decrypt it.
When you set up your password under security you can choose to enter it on boot and then it will ask you for this password everytime BEFORE booting your system, and this will also be your password to decrypt data for twrp then. But i dont know if thats the "real encryption" or that standatd thing is, too, but just decrypts automatically on boot.
Thank you for helping me, I just get totally confused by the Oreo process,.. worked so easy on nougat
in security option, the phone appear to be encrypted, in nougat after flash no verity the phone was decrypted. In oreo i dont know why is appear encrypted and i cant decrypt with no verity....
Wolfcity said:
As I rooted the device it was on Oreo OPS28.85-13-3 by OTA and I did it like this:
flash latest official twrp 3.2.3.1
make a backup of EFS and persist
boot recovery (now it prompts you to give in a decryption code, just press skip)
format data (F2FS)
don't reboot now
flash magisk 18 (I flashed 17.2 and updated later, no clue why)
reboot to system
install magisk 6.1 apk (if it's missing, in my case it was present)
if you reboot to twrp now it shouldn't prompt you to give in a decryption key anymore
Click to expand...
Click to collapse
I dont have the option to backup efs,.. im using twrp 3.2.3-0 (the latest i could get from official twrp site) but i already did backup efs and persist in nougat, isnt that enough? DO i have to do that again on Oreo?
Also its not asking me for a decryption code, are you using 64bit twrp then?
And i remember that twrp got overwritten 2 or 3 times by stock recovery, and i thought that was because i didnt rebooted twrp again, since i rebooted twrp after formatting data it didnt happen again.
Also it did work for me using the 1. method i wrote earlier, i successfully rooted my phone, im just wondering now which is the "better" or "correct method to either
boot recovery, reboot recovery, format data and flash magisk
boot recovery, format data, reboot recovery, flash magisk
boot recovery, format data, flash magisk, boot system (but i guess next time you enter twrp it gets overwritten by stock recovery then)
boot recovery, format data, flash magisk, reboot recovery and boot system
or stay in bootloader (after flashing twrp) fastboot erase userdata, boot recovery, -data, -magisk, -system
or -recovery, -bootloader fastboot erase userdata, -recovery, -magisk, - system,.... you get the idea
woozie.2007 said:
in security option, the phone appear to be encrypted, in nougat after flash no verity the phone was decrypted. In oreo i dont know why is appear encrypted and i cant decrypt with no verity....
Click to expand...
Click to collapse
Because theres some sort of auto encryption which everytime reencrypts your phone.
I just dont get the sense of formatting data if it gets reencrypted anyway and twrp can surpass encryption.
G5-User7080 said:
After flashing Oreo(boots up) and then twrp:
format data failed
factory reset failed
After flashing Oreo(boots up) and twrp and rebooting twrp:
format data successfull
factory reset successfull
. . .
Click to expand...
Click to collapse
Had to correct that!
So in general after booting system, formatting data fails, maybe it works with fastboot erase userdata (didnt test it, cause i dont want to reflash Oreo again, i wanna go to bed.
But just rebooting recovery after booting first time in twrp works, so after that format data works. Works not..
Now im confused,.. after being in system and returning to twrp format data fails, but it seems when you fail it and then reboot recovery then it works...
So boot recovery, reboot recovery -> format data wont work BUT
boot recovery, format data fails, reboot recovery, format data will work WTF
So i guess either do factory reset instead of formatting data (thats also fine, or not?) or use fastboot erase userdata after flashing twrp in bootloader (i mean i do this while flashing oreo,.. so i dont really get why i have to do that again but i also dont really get why i have to format data a all)
Good night guys, thank you for your help,.. ill continue tomorrow.
G5-User7080 said:
Had to correct that!
So in general after booting system, formatting data fails, maybe it works with fastboot erase userdata (didnt test it, cause i dont want to reflash Oreo again, i wanna go to bed.
But just rebooting recovery after booting first time in twrp works, so after that format data works. Works not..
Now im confused,.. after being in system and returning to twrp format data fails, but it seems when you fail it and then reboot recovery then it works...
So boot recovery, reboot recovery -> format data wont work BUT
boot recovery, format data fails, reboot recovery, format data will work WTF
So i guess either do factory reset instead of formatting data (thats also fine, or not?) or use fastboot erase userdata after flashing twrp in bootloader (i mean i do this while flashing oreo,.. so i dont really get why i have to do that again but i also dont really get why i have to format data a all)
Good night guys, thank you for your help,.. ill continue tomorrow.
Click to expand...
Click to collapse
Latest official TWRP recovery is 3.2.3.1 for potter:
https://eu.dl.twrp.me/potter/
It has the ability to backup EFS and persist (see attached screenshot). I would make a backup just to be on the safe side.
To prevent the device from encrypting again the trick is to flash magisk after formatting data and before rebooting, it deactivates the "force encryption" flag (unless you tick the "keep force encryption" box in magisk manager).
Also I hadn't any problems to make TWRP stick.
Edit: A factory reset won't reformat data.
If you want your data partition decrypted or not depends on your needs. Encrypted is safe but you're not able to access it to make any changes unless you decrypt it again....
Wolfcity said:
Latest official TWRP recovery is 3.2.3.1 for potter:
https://eu.dl.twrp.me/potter/
It has the ability to backup EFS and persist (see attached screenshot). I would make a backup just to be on the safe side.
To prevent the device from encrypting again the trick is to flash magisk after formatting data and before rebooting, it deactivates the "force encryption" flag (unless you tick the "keep force encryption" box).
Also I hadn't any problems to make TWRP stick.
Edit: A factory reset won't reformat data.
If you want your data partition decrypted or not depends on your needs. Encrypted is safe but you're not able to access it to backup data or make any changes unless you decrypt it again....
Click to expand...
Click to collapse
I have the G5 not plus, theres no 3.2.3.1 yet. (Aber lustig, dass du auch aus deutschland bist (denk ich mal) ).
Ahh so i have to flash magisk right after decrypting by formatting data? But i cant successfully format data when i come from system as i wrote earlier so the question is if it works when i fastboot erase userdata to decrypt data and if data doesnt get reencrypted when i boot then twrp.
I guess if the force encryption reencrypts when i boot recovery, too it wont work, then i guess the only way is to enter recovery, do a failed attempt, reboot recovery, and successfully format data.
Edit:
It deactivates the "force encryption" flag (unless you tick the "keep force encryption" box).
Click to expand...
Click to collapse
Also after installing magisk and booting system it still says encrypted in settigns so i thought its not removing the force encrypt. And i dont have found that switch yet..
Wolfcity said:
To prevent the device from encrypting again the trick is to flash magisk after formatting data and before rebooting, it deactivates the "force encryption" flag (unless you tick the "keep force encryption" box in magisk manager).
Click to expand...
Click to collapse
Hi,
If i already have the phone encrypted and rooted with magisk, "keep force encryption" is tick, if I will untick the option will booting decrypted?
G5-User7080 said:
I have the G5 not plus, theres no 3.2.3.1 yet. (Aber lustig, dass du auch aus deutschland bist (denk ich mal) ).
Ahh so i have to flash magisk right after decrypting by formatting data? But i cant successfully format data when i come from system as i wrote earlier so the question is if it works when i fastboot erase userdata to decrypt data and if data doesnt get reencrypted when i boot then twrp.
I guess if the force encryption reencrypts when i boot recovery, too it wont work, then i guess the only way is to enter recovery, do a failed attempt, reboot recovery, and successfully format data.
Edit:
Also after installing magisk and booting system it still says encrypted in settigns so i thought its not removing the force encrypt. And i dont have found that switch yet..
Click to expand...
Click to collapse
Ah ok, I thought your device is a potter.
The checkbox is found inside magisk manager but it is unticked by default so the device should decrypt.
Have you tried the official twrp instead of the 64bit unofficial version?
Maybe try magisk 17.2 too as I did.
And yes, I'm from good old Germany too.
woozie.2007 said:
Hi,
If i already have the phone encrypted and rooted with magisk, "keep force encryption" is tick, if I will untick the option will booting decrypted?
Click to expand...
Click to collapse
I think you will have to decrypt data by formatting it, unticking the checkbox just prevents the device from encrypting itself again. You should find some additional informations:
https://www.didgeridoohan.com/magisk/MagiskInstallationIssues