Develop Bugs

OOS 4.0 with F2FS, help me decide please..

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.

Cannot Install Any Custom Rom

I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?

I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data

prospektus said:
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
Click to expand...
Click to collapse
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?

thrustaxehandle said:
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
Click to expand...
Click to collapse
yes.. delete internal memory. rom board. format data.

thrustaxehandle said:
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
Click to expand...
Click to collapse
You need to upgrade to a higher version for twrp. 3.2.2

prospektus said:
yes.. delete internal memory. rom board. format data.
Click to expand...
Click to collapse
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
esiv129 said:
You need to upgrade to a higher version for twrp. 3.2.2
Click to expand...
Click to collapse
I'm already using TWRP version 3.2.3

thrustaxehandle said:
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
I'm already using TWRP version 3.2.3
Click to expand...
Click to collapse
try again unlock

prospektus said:
try again unlock
Click to expand...
Click to collapse
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.

thrustaxehandle said:
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
Click to expand...
Click to collapse
When you get the mount error, come to the home page and get to the mount. speak enable all options enable all options. speak restart recovery restart recovery. make format data
Not sure if the link is forbidden? I can't tell you sorry. https://www.youtube.com/watch?v=dzrWkjOfndA&t=501s

I have read replies and everyone is sharing his bit of suggestions, here are mine
1. boot redwolf as FASTBOOT BOOT recovery.img - (if you arent already)
2. change file type of /data partition to-from (xFat to ext4) and wipe all partitions (internal storage can be skipped)
3. instead of linage15.1 same package, try downloading some other custom rom, i recomend DotOS2.5 or Crdroid4.6.2
4. uncheck enforce md5 bla bla while flashing zip.
i hope you will succeed

Ended up in a bootloop during restoring twrp backup

I was on pixel experience rom and wanted to try out other pie based roms on my device. So i backed up all the partitions from twrp recovery and went on with flashing arrow os. But when i wanted to revert back to pixel experience by restoring the previously made backup, it showed that system partition mount was failed during the restore process. So i tried booting into twrp again but the device just bootloops. I tried entering recovery mode by using volume up and power combo. But twrp starts bootlooping after the logo appears on the screen. I also tried flashing redwolf twrp but it also fails to boot. Any help would be appreciated.

Enter fastboot, and boot twrp from adb then try again to flash it

Destinyg133 said:
Enter fastboot, and boot twrp from adb then try again to flash it
Click to expand...
Click to collapse
I already did that. But the result was the same.

Rahul Choudhury said:
I already did that. But the result was the same.
Click to expand...
Click to collapse
Try this:
Go into twrp, wipe, advance wipe, select system filesystem only and the option to repair/resize file system and repair it...

can u factory reset it? Using stock recovery

luck2ang said:
can u factory reset it? Using stock recovery
Click to expand...
Click to collapse
I flashed the fastboot rom. It is working fine now

seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!

i am in the exact situation please someone help me.i tried to reboot twrp with pc as well the same thing happens. please tell me how you did it
---------- Post added at 02:15 PM ---------- Previous post was at 02:02 PM ----------
YasuHamed said:
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
Click to expand...
Click to collapse
i cant find orange fox img file everytime i end up with zip file which can be flash in twrp. plz can you help me asap
---------- Post added at 02:27 PM ---------- Previous post was at 02:15 PM ----------
YasuHamed said:
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
Click to expand...
Click to collapse
i backed up my pixel experience rom in twrp then installed liquid remix. but i did not like it so i went into twrp wiped the phone, not inernal and all, but everything we wipe before installing rom, then i went into restore and restored my backup and reboot after that im stuck in bootloop and everytime i try to go into twrp the 1st twrp bootscreen shows up then goes back into bootloop. please help me i would be really greatful

Rahul Choudhury said:
I was on pixel experience rom and wanted to try out other pie based roms on my device. So i backed up all the partitions from twrp recovery and went on with flashing arrow os. But when i wanted to revert back to pixel experience by restoring the previously made backup, it showed that system partition mount was failed during the restore process. So i tried booting into twrp again but the device just bootloops. I tried entering recovery mode by using volume up and power combo. But twrp starts bootlooping after the logo appears on the screen. I also tried flashing redwolf twrp but it also fails to boot. Any help would be appreciated.
Click to expand...
Click to collapse
I experienced that too.. i think some ROM does something to vendor partition, example:
1. You backup data,system,boot etc...lets say u do that on "A" rom..
2. then u install "B" rom, and u like not satisfied on that..
3. Then u wipe everything and restore your "A" backup..
if you do that like what i said.. you will ended with bootloop or just stuck on mi screen..
I found a workaround ..
You just need to re-flash the "A" rom (clean install), then wipe everything again , and restore your backup..
? Sorry for my english btw

In my 16GB model, when I did a recovery through TWRP, I had a bootloop problem.
However, 'OrangeFox Recovery' does not cause this issue.
And, SD card with 'exFAT' format is recognized as normal.
I strongly recommend.
https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3900471

How to flash GSI in RN8P/HMN8P?

I flashed AOSP_10_Quack_Phh-Treble_v208 many times last night.
but always failed,bootloop.
My step:
unlocked + TWRP
1.factory reset + format /data(or not)
2.flash V208.img to system image
3.format /data or not,reboot
My phone showed Redmi-logo and dm-verity error,
and bootloop.
anybody successed?
Could Somebody teach me how to flash GSI?
Maybe to flash AOSP 9?

It's reassuring to see you have attempted multiple times to flash another ROM and haven't hard bricked your phone.
My guess is you need to flash the dm-verity remove zip file. I'm assuming you have selected AVB 2.0 in TWRP? That's all I can think of but I haven't tried anything as clearly I don't have balls as big as yours

I used these following steps from tvardero :
Flash stock
Flash twrp
Make a backup of system and data (to get back into stock if needed)
Format data -> yes
Flash GSI you want to
To flash another GSI or revert to stock you use your backup of system partition.
NEVER EVER RESTORE ANYTHING ELSE THAN SYSTEM OR DATA, softbrick imminent

I try many GSI-ROM
Most bootloop,even I format /data,disable dm-verity/AVB 2.0 (TWRP by wzsx150)
My steps is
fomat /data,reboot to twrp
wipe /system ,2cache and flash gsi.img(Maybe resize /system to flash gapps)
flash magisk
disable dm-verity/AVB 2.0 with TWRP by wzsx150,or flash disabler.ZIP
GSI ROMs had some different bugs,brightness control,NO mobile signal,
sound,nfc-sim support,googlepay ,bank app etc.,

Really nice to see some testings. I hope we have some some development for our devices

I'm having problems with TWRP and OrangeFox, permission errors all the time

I'm facing some permissions problems and thus being unable to install Paranoid Android Q5. I was using MIUI 12 (Xiaomi.EU).
The steps I took to change the ROM:
Formated data (errors started right away) then I did the usual wipes (cache, dalvik, data)
Whenever I try to wipe or format data I get error messages like: Error opening /data/XXX (Operation not permitted).
System is always mounted read-only no matter what I try and after I install any ROM many of these error messages pop up.
Orange Fox gives some error about key.
Flashing of the ROM suceeds, but system cannot boot, loading screen forever.
Can anyone point me some directions?
Thanks in advance and sorry about any possible bad grammar.
[ ]s
;-)

Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.

Pavello said:
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Click to expand...
Click to collapse
Well , i have the same problem..and used pitch black also

Any update on this?

I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)

jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
i gusse thats a problem in miui12.0.3
i was using pixel experience 10 then i flash miui 12.0.3 in fastboot when i tryd to flash orange fox i had the same problem
so i gusse u can downgred to miui 11 and flash twrp and it will work

I solved this by downgrading to 12.0.1

jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...

I am having this exact problem.
Under internal storage (sdcard) I see a bunch of hashed folders I cannot open.
Format data returns a multitude of "Error opening '/data/somefolder/asdf/asdf' (Operation not permitted) and marks the wipe as Failed. The attempted formatting also mentions "E:Error making /sdcard/Fox directory: Required key not available." "Failed to unmount '/data' (Device or resource busy)
I can wipe anything except Data. I also tried downgrading to 12.0.1 firmware but it does not fix it for me.
The ROM can be booted into, and magisk managed to be installed, but no google apps were installed.
Dibbo Sarker said:
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
Click to expand...
Click to collapse
I tried this, but no luck on my side.

Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!

A problem like this was the one I had since TWRP had the device encrypted but it did not inform me and it did not give me any sign that I had to write a password (password that I have no idea what it is).
What I did so that it did not give me an error was to install Orangefox and while there delete everything and install a file of these that I got from google.
I had to try one by one and restart to see if it asked me for a password in orangefox, luckily one worked and it no longer asked me to decrypt the files and I could install the rom and gapps normally

jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
Thank youuuuuuuu! You have rescued my phone!

jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
THANK YOU!

Why is my orange fox is not showing Vendor, System Etc ? How can i fix this ? I really need to wipe those as well..

Jona'san - sama said:
Why is my orange fox is not showing Vendor, System Etc ? I really need to wipe those as well..
Click to expand...
Click to collapse
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
Jona'san - sama said:
I really need to wipe those as well..
Click to expand...
Click to collapse
if you want to flash a rom = yes

loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Can't wipe it still, I already try the Mount > ✓ Vendor ✓ System.. but in formatting it say's "Cant Mount the....blah..blah.."
I try to uncheck the "Mount System vendor, system as read-only" from the settings of mount.. but for some reason, if you go back to Mount options again, you can't check the system, vendor now

loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Yes, I need it to flash a ROM

try this it worked

Had the same issue.
1. I installed twrp via ADB
2. Restarted to recovery mode into twrp
3. Installed the latest OrangeFox and restarted into recovery again.
4. It asked me for a password which is the pin I set then proceeded to format data.
5. After formatting data I restarted again to recovery.
Then I was able to install custom roms.

I am using derpfest Android 12 on my Poco x3 pro. I want to install magisk.zip through orange fox recovery installed on my phone. But I am not getting storage data on recovery, only a fox folder is there. Can somebody tell me is it a glitch or any Android 12 restrictions or something.