Database Users

[Recovery] Twrp 2.8.7.0 Kipper

I have build a twrp recovery for Wileyfox storm (kipper)
Enjoy it.
All credits go to TeamWin developpers.
flash with fastboot
fastboot flash recovery TWRP-2.8.7.0-kipper-recovery.img
TWRP-2.8.7.0-Kipper-brown-recovery
Edit:
TWRP-2.8.7.0-Kipper-blue-recovery

Nice job ;D

Awesome. It works flawlessly Is there any chance of any custom rom? maybe pure AOSP marshmallow with layers support? is the kipper source released?

I saw twrp 3.0.0.0 can you please compile it?

This works very well, backup, restore. Just one thing i just hope would be great to be there is the OTG drive support.

aciupapa said:
I saw twrp 3.0.0.0 can you please compile it?
Click to expand...
Click to collapse
What extra features does twrp3.0.0.0 have please? The current cm13 marshmallow nightly for wileyfox storm require the cm recovery to install the update zip.

You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.

backfire_12 said:
You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.
Click to expand...
Click to collapse
https://s.basketbuild.com/devs/beroid/Wileyfox%20Storm%20-%20Kipper/TWRP
Anyone tried TWRP_3.0.0-0_kipper recovery at all yet? I have the TWRP_3.0.1-0_crackling_20160402 recovery working fine on my Swift, however since my backups are from the TWRP 2.8.7.0 kipper recovery i have not tested the TWRP_3.0.0-0 version on my Storm!

On the 3.0.0 v2 touchscreen doesnt work for me

aciupapa said:
On the 3.0.0 v2 touchscreen doesnt work for me
Click to expand...
Click to collapse
I had a try at installing both test version 1 and 2 however the recovery loads yet none of the tile's responded after installation/ loading up completed.

hi i need video how do this recovery plz

Ok so I tried to install the given 2.8.7 version and it worked, but it always said 'wrong password' when trying to decrypt my phone. The same password worked when regularly booting the system. So I thought I might try a newer version and downloaded the _test.zip from the link provided in the thread. Unfortunately, now my phone seems to be bricked! It always boots into Recovery, which asks for my password but does not react to any input on the touchscreen. I can not boot the system or the bootloader, adb and fastboot do not find the device and if I hold the power button (or volume-down + power button) for several seconds it just again reboots into the broken recovery. Does anyone have an idea how to get out of this? Any help is greatly appreciated.
Edit: OK, now I feel dumb. The key combination to get into the bootloader is volume-up+power, not volume-down+power. Now I can continue to try different recoveries in the hope that one of them can decrypt the phone correctly and reacts to the touchscreen.

saikoa7a8a said:
hi i need video how do this recovery plz
Click to expand...
Click to collapse
If that's how you write, good luck breaking your phone... This thread has good instructions if you want to risk it, just replace the recovery image it has you download and use with this one.
http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992

[GUIDE][How to][custom recovery] [custom rom][Redmi Note 3 SD]

I am not responsible for anything done wrong for you and your device. Sorry!!
You have two options to follow, the 1st one is long, may be difficult to follow. I recommend you to read option 1 and 2 both but to follow option 2
OPTION 1
Hello friend this is a short tutorial for those who have just bought the Beast Red Mi Note 3.
This guide is only for Redmi Note 3(Qualcomm Snapdragon 650 2GB/3GB version) users.
The Device's codename is kenzo. It also called Xiaomi Redmi Note 3 Pro. On MIUI sites Its also mentioned as HMNote3Pro so don't get confused.
The below mentioned MiFlash-Tool is required in emergency. Installing Mi-FlashTool in PC also install all the Quallcomm and Xiaomi Drivers to make your device function with PC at any mode( recovery, fastboot or system mode) Make sure before installing MiFlash-beta setup, You have disabled Driver Signature Enforcement in your Windows PC. To know how to disable check on Microsoft sites for your particular OS.
Requirements
1. A PC with windows 7,8,8.1 or 10 32-bit or 64-bit with .NET Framework version 3.5 installed. Before you install Mi Flash. To download .NET framwork visit the microsoft website.
2.Download Xiaomi MiFlash-Beta(This beta version works good and also support 32-bit Windows OS) http://en.miui.com/forum.php?mod=at...2NGJkfDE0ODE4MTQxMTh8MTU5MjAzMDUwMXwyODE5Nzk=
3.TWRP Recoveries- download all these 3 recoveries
a. Alka TWRP http://en.miui.com/forum.php?mod=at...xMmZifDE0ODE4MTY5NzZ8MTU5MjAzMDUwMXwyODI3NzM= (for emergency backup and restore) (this recovery is most necessary to backup all the partition of our device. RN3 comes with all about 40 partitions, and their are many important files stored their. So at anytime you get any problem just restore. The recovery image file is compressed in a .zip file. Therefore, you may need to firstly extract it using Winzip on your PC or extract it using ES File Explorer on your phone. One more thing, this build is for Redmi Note 3 Qualcomm Snapdragon (Kenzo).
b. Cofface TWRP https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk (zip password www.cofface.com)
c. Official TWRP https://dl.twrp.me/kenzo
If you want to flash custom Rom like Cyanogenmod, xiaomi.eu, Resurrection Remix etc. This tutorial will help you to use all those thing which can be done on our Beast .
:angel: first of all you guys get the Bootloader unlocking permission from en.miui.com/unlock/ (recommended) and always sign in the Mi Account with valid mobile number and e-mail which is used by you currently and can be accessed by you anytime. Goto setting in the phone and register for Mi account and login. Enable Find Device feature.
i have not checked ZC-X TWRP RECOVERY because i have seen some people getting problem from zcx, but now it is upgraded. So it can be universal for everything( like flashing any official/stock/custom rom(as cofface and official do), maybe it supports all partition backup( like alka do) and also it can be used to update or upgrade you MIUI based rom. Check it at your own risk.
3.USB DATA cable (the one that came with your device).
4. device battery charged at least 50%.
5. A good observer and patient most of patient.
I don't think about any other way to unlock bootloader. You can find them on other places but I don't find them easy than this.
So I am supposing that you guys using your phone with stock MIUI Rom that should be MIUI 7 or MIUI 8 with stock recovery and You got the permisssion official to unlock your beast .
So just unlock the bootloader by using MiUnlock tool from PC. Store all these tools in your PC for future process.
Now you have unlocked bootloader to check the status just boot your phone into fastboot mode by pressing volume down+power key when your device is off then use this fastboot command fastboot oem device-info to check the bootloader info if it says bootloader unlocked:true then you are ready to go. If you don't know how to setup adb-fastboot environment and driver check it here http://forum.xda-developers.com/showthread.php?t=2588979
Put unlocked bootloader phone in fastboot mode,connect device to PC using USB cable and check the bootloader status again to verify it is unlocked or not by using command fastboot oem device-info. Now copy(don't cut because you should have a backup plan for each process) all the recoveries ALKA TWRP, CoffaceTWRP and official TWRP recovery to the adb fastboot folder and rename alka twrp to alka.img,cofface twrp to cofface.img and official twrp to official.img. Please copy and rename one by one for don't getting confused. If you accidently rename cofface to alka then it will be not good to you after flashing. So take each step carefully.
(if you have managed environment variables on PC then you can use adb fastboot commands any where in PC, That is a good idea. So if you want to know how to set environment variables just comment here I will give you all the steps.)
Now just press continuously the Shift key and press RIGHT CLICK on the blank area of window.
An option menu will be showed click on open command prompt here.
A black backgrounded command shell will be opened.
Now type fastboot oem device-info and press enter key.
If it shows bootloader unlocked :true then proceed to the step 1 and if shows false then don't proceed unlock your bootloader which is shown above with this symbol :angel:.
Step 1:
A.First of all take backup of internal sd by copying all the folder and files in your PC's folder and name this folder to KenzoInternal you can use any name. And delete more files in internal to get atleast 5GB space.
B.You shuould have atleast 5GB space in your internel to back up your all device partition through ALKA TWRP.
C. copy all three recoverys(cofface.img,official.img and alka.img) in your phone's Internal SD directly or make a folder recovery and place there.
Now go,read and follow the instruction from below
Boot your phone in fastboot mode and connect with PC
open command prompt in adb-fastboot folder where you have copied all the recovery images(official.img,cofface.img and alka.img)
Type on command prompt:
fastboot flash recovery alka.img
it will be flased in atleast 10 seconds.
Now we have to go directly to recovery mode from fastboot mode not in system so care fully press volume up + power key at the same time in your REDMI NOTE 3 and when your device vibrate leave the power key but don't leave the volume up key until the recovery window get shown. If your device get booted to system not in recovery then maybe your flashed 'alka' will be replaced with stock recovery, and may be it get bootloop or maybe it will boot successfully but have some problems like Wi-Fi radio get disabled.
Read the above step again and do everything carefully.
Step 2:
[[ If on welcome screen the language shows in chinese or other, then simply swipe on first screen and touch on the 2nd column and 3rd row in menu and then touch on the icon(shows like earth or sphere) and choose English and then done. ]]
In recovery go to BACKUP and mark all the partition I said all the partitions (you can leave unmarked the DATA partition if you are not wanting to make backup of your own installed applications and their data. It will decrease the backup size and also the TIME) their may be 35+ partitions. And swipe to backup. Their are some partitions like system,efs(stores modem and radio and may be your IMEI information) etc have the sensitive data. So you are mostly recommended to mark all the partition except DATA(optional).
GREAT!!! wait until getting backup.
Step 3:
Now touch on Install menu in recovery and touch on Install Image that is always in the right below of the screen upto the swipe handle.
Now browse to the root of internal sd or the folder where you have copied all the recovery images(cofface.img,alka.img and official.img). And choose the cofface.img and swipe to install.
Now get back by touching on back arrow symbol on left bottom.
Step 4:
Touch on REBOOT menu in recovery and then touch on Reboot to recovery or to recovery.
Your RN3 will reboot again to recovery(which is now cofface).
[[ If on welcome the language shows in chinese or other then simply swipe on first screen and touch on the 2nd column and 3rd row in menu and then touch on the icon(shows like earth or sphere) and choose english and then done. ]]
Now touch on reboot and thenreboot to system.
If it shows that your recovery will be
If any query shows saying your phone is not rooted just touch on Do not Install
your phone will boot to MIUI system as it was. and it has a custom recovery(currently cofface).
if you want to root your device then download superSu.zip from https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip and place it in your internal sd card of phone and then boot to recovery by pressing power key+volume up key on same time then go to install and choose to install for supersu_vx.xx.zip file and swipe to flash. Then get back and wipe cache and dalvik/ART cache or some times it also reboots automatically.
Kindly follow the on-screen instruction which shows on screen during installation.
NOTE: It may be bootloop or take too much time on first boot after installing superSu.
SuperSU app and all the applets(including busybox tools) also comes with superSU zip file. So no need to install it through PlayStore. However you can update from PlayStore.
You are strongly recommended to take the backup(whole partition backup taken by ALKA TWRP) and copy it to Your PC that is the life of your mobile. I know you can flash An official MIUI rom through PC using fastboot or EDL method but If you lost your EFS partition then You will lost your IMEI which is unique to each and every devices. In Qualcomm Snapdragon based phone It is hard to recover IMEI. I say hard not impossible. Their are many forum that give solution to this but It is highly recommended to have this backup copy to your PC. You can find your backup in the /sdcard/TWRP/Backup/ OR open Internal SD then go to TWRP folder then open BACKUP and then a folder like 5exxxye. just copy this folder to your PC and keep it safe or you can save it to other places also that will be more good and also show your smartness.
How to install custom ROM or OSs in RN3Snapdragon?? Hmm come here
NOTE: Always flash all custom ROM(Except MIUI) through official TWRP. But when you have made your mood to install custom ROM you have to flash official twrp through either with TWRP(currently cofface in your device) or with fastboot command using same method that I have explained above when we have flashed coffaceTWRP in your device or use this commandfastboot flash recovery official.img
I have tested many ROMs but I found most stable Resuurection Remix(based on Marshmallow) and CyanogenMod 13(based on Marshmallow) yet. Everything is working fine except VoLTE. Their are many available ROms that supports VoLTE based on Nougat(Android 7.0 or 7.1) but have some bugs with camera. (The Cyanogenmod 14.1 officially is also declared but in experimental mode(nightly)(not recommended for you.))
I am going to show you the steps to flash custom ROMs without getting into any problem but you are recommended to follow each steps carefully. Thanks
Suppose you have downloaded official released Cyanogenmod 13 for your phone from here https://download.cyanogenmod.org/get/jenkins/174586/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0FI-kenzo.zip (It is recommended to download it to your PC for backup plan). Having a copy of this backup in your PC makes you free to delete it from internal SD to free the space when you are in a Stable Rom or in a ROM you loved and want to be always with it.
then place it to your internal SD. now follow these steps... Check out your device battery is 50+ % charged.
Step 1:
Reboot to recovery. Go to install and choose install image. Now choose official.img(officialTWRP) and then swipe to flash/install it.
Step 2:
Now reboot again to recovery by choosing REBOOT in recovery menu and then RECOVERY
your phone will be rebooted to official TWRP recovery which is not supported by MIUI. I mean official recovery doesn't have the ability to patch the boot image., that is why I said it is not supported.
Step 3:
Now go to wipe/format menu in TWRP recovery(I am supposing you have the back up with alka twrp before and have copied it to your PC also.). Choose 'advanced wipe' and Mark these partition System,Data,Cache,Dalvik/ART cache. Do not choose Internal SD, Micro SD or USB OTG. and swipe to wipe.
Step 4:
After wiping now you have not any Operating System installed. Just touch INSTALL in RECOVERY MENU and choose the ROM ZIP file which is cm-13.0-20160816-SNAPSHOT-ZNH5YAO0FI-kenzo.zip (for example). Always use the ROM that is build for Your Device. Since above zip file's name shows it is for kenzo that is your RedmiNote3 Quallcomm Snapdragon.(just check the underlined word in zip file.)
and swipe to flash and wait no matter how much time it takes. Just wait don't try to reboot.
if you want to flash google apps(GApps) like play store and play store services you have to install it also after flashing the ROM zip file. to download GoogleApps go to opengapps.org and choose arm64 from architecture menu and choose android version for this ROM(Cyanogenmod 13) choose 6.0. choose which package you want I recommend you to use pico it will only install play store and services and you can also install other google apps through Play Store later.
If you want all google apps then choose 'aroma' it has a built-in file explorer to choose particular app in recovery.
Step 5:
After installing cyanogenmod and GApps wipe cache and Dalvik/ART cache again. Do not wipe anything else.
Now its time to reboot to the system.
first time it will take atleast 2 to 10 mins (depends on the open GApps package type) for optimization of apps.
After that go and enjoy..
Any problem comment below.
To revert back to MIUI again.
just copy the backup folder you have taken before, to the folder /sdcard/TWRP/BACKUP/ and reboot to recovery(currently official).
and choose to install image in recovery menu and then choose alka.img and then reboot to recovery again(using recovery menu).
You will again reboot to recovery (currently ALKA).
In alka recovery menu choose to WIPE and wipe these partition SYSTEM,DATA,CACHE,DALVIK/ART CACHE.
then choose RESTORE from recovery menu and select your backup folder and it will show the list of all the partition you have made backup. Mark all and swipe to restore.
Note:sometimes it shows an error during restore that it can't restore firmware partition. If it show this error kindly choose to restore again and mark all partition except firmware partition then swipe to restore.
After restoring backup(MIUI) do not reboot just. choose to install image and install cofface.img again because this recovery works with MIUI.(Cofface twrp paches boot image automatically which is required to make custom recoveries to work with MIUI ROMs ) after installing cofface.img. Reboot to recovery again and then reboot to system.
Now wait if it takes too much time (may be 15 to 20 mins).
Now you are come back to your MIUI ROM.
MUST READ:
1.Always check your bootloader status after and before flashing any ROMs(boot to fastboot mode connect USB to PC and type the command in command window fastboot oem device-info.
2.If any time it shows bootloader unlocked: false then use Mi Unlock tool to unlock the bootloader again. You have to use same user-name/mobile number/e-mail and password to sign-in the UnlockTool which you have sihned in your phone.
3.No matter how many ROM you have flashed or which OS you currently using. MiUnlock-tools always recognises your phone.
4. During unlocking the phone your PC must have an internet connection from other sources.
5.You can't use your phone's wi-fi hotspot to unlock its bootloader because it should be in fastboot mode.
6.Always make back up and store them in safe place.
Credit
to the respective developer,manufacturer.
OPTION 2
Now you can use zcx recovery which is Universal to flash custom/stock/miui ROM without any problem. So unlock your bootloader and flash ZC-X twrp recovery, and follow the instruction comes with it, you don't need to follow the long procedure given above. You should use it with Marshmallow based MIUI ROM too which comes with by default DATA partition encryption. It can automatically decrypt DATA partition. So go for it here https://www.google.co.in/url?sa=t&r...DwoAzQEtfzPxp4Shw&sig2=SOZcDMBpgO_teBIK6lNnhw
Thanks any problem comment below. Enjoy

can't i use zc-x rom ? for all purpose ?

You can.. but must use alka twrp for backup and restore

jangid said:
can't i use zc-x rom ? for all purpose ?
Click to expand...
Click to collapse
What do you mean by zc-x rom? If you want to say zcx recovery then yes You can.. but must use alka twrp for backup and restore always

If i want to flash custom MiUi rom like miui.eu or epic miui ROM, should I use cofface recovery or official twrp ?
Sent from my Redmi Note 3 using XDA-Developers mobile app

This tut has been pretty clear but I have a typical doubt! If I unlock my phone using mi flash tool by using the miui7.1.8 fastboot rom and flash twrp and if I later how do I update my miui? If I would be able to update it in some way doesent the bootloader get locked again? If it gets locked and I need to downgrade to older miui version! Pls help!

If I use offical twrp and take my unrooted miui backup and flashed cm14.1 and then latter restore my unrooted miui i wouldn't work?
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
Also we can't flash cm14.1 rom using any other recoveries like Alka zcx coaffe ?

gaurav1322 said:
What do you mean by zc-x rom? If you want to say zcx recovery then yes You can.. but must use alka twrp for backup and restore always
Click to expand...
Click to collapse
Seriously dude , zcx supports all partition backup like alka twrp+6.0 encryption problem is also solved ,inbuilt boot image patcher + miui ota support
This guide just made procedure to flash ROMs more hectic and uneasy and long process.
I Recommend user to just flash zcx twrp and do all the stuff you want,flash any roms including miui.

NVDX11 said:
Seriously dude , zcx supports all partition backup like alka twrp+6.0 encryption problem is also solved ,inbuilt boot image patcher + miui ota support
This guide just made procedure to flash ROMs more hectic and uneasy and long process.
I Recommend user to just flash zcx twrp and do all the stuff you want,flash any roms including miui.
Click to expand...
Click to collapse
Can i restore miui backup after flashing cm14.1 in zcx recovery ?

a.broken.star said:
If i want to flash custom MiUi rom like miui.eu or epic miui ROM, should I use cofface recovery or official twrp ?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then must use cofface because MIUI based custom rom like
Xiaomi.eu etc. Are also need boot image patching..but 1st
Take full nandroid backup through alka and copy it to pc
Before flashing it. After flashing MIUI based custom rom use
Check your bootloader status because some of them locks your Bootloader again..

ckflash09 said:
This tut has been pretty clear but I have a typical doubt! If I unlock my phone using mi flash tool by using the miui7.1.8 fastboot rom and flash twrp and if I later how do I update my miui? If I would be able to update it in some way doesent the bootloader get locked again? If it gets locked and I need to downgrade to older miui version! Pls help!
Click to expand...
Click to collapse
1st of all the bootloader status(lock/unlock) get changed
From rom to rom. So everytime if you wanna flash something
Like any rom(official/stock/custom) or any recovery you need to check your bootloader status 1st. I have told in post that if u wanna flash Miui rom or wanna update it,just flash through cofface recovery. And one thing to remember, never downgrade miui version through cofface (for example Miui8 to miui7). But if u want to upgrade(for ex. Miui7 to miui8) or want to update(ex.- miui 8.0.1 to miui 8.1.1 or something like this) then you can use cofface twrp recovery and also zcx twrp recovery. Before flashing make sure you have full backup through alka twrp. You should read the post again.

vikasb32 said:
If I use offical twrp and take my unrooted miui backup and flashed cm14.1 and then latter restore my unrooted miui i wouldn't work?
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
Also we can't flash cm14.1 rom using any other recoveries like Alka zcx coaffe ?
Click to expand...
Click to collapse
It will work if your miui backup from official twrp contains backup of firmware partition. Since official twrp doesn't supports all partition backup. So you need to flash a miui based fastboot rom then unlock bootloader again if it get locked and then flash alka to take all partition backup then save this backup to pc. And after that check the post again for what you want.

vikasb32 said:
Can i restore miui backup after flashing cm14.1 in zcx recovery ?
Click to expand...
Click to collapse
Yep sure! No prob.

NVDX11 said:
Seriously dude , zcx supports all partition backup like alka twrp+6.0 encryption problem is also solved ,inbuilt boot image patcher + miui ota support
This guide just made procedure to flash ROMs more hectic and uneasy and long process.
I Recommend user to just flash zcx twrp and do all the stuff you want,flash any roms including miui.
Click to expand...
Click to collapse
you are right but zcx doesn't support all about 40 partitions. Maybe it comes with all features that we get in all other twrp recoveries like cofface,alka etc. but for whole partitions backup alka is necessary.
But it is true that ZCX supports important partitions that are more important while ALKA twrp supports whole with important and not important
This post is not so long or uneasy. It is for noobies to understand. This is not for PROs. Thank you!

gaurav1322 said:
you are right but zcx doesn't support all about 40 partitions. Maybe it comes with all features that we get in all other twrp recoveries like cofface,alka etc. but for whole partitions backup alka is necessary.
Click to expand...
Click to collapse
Zcx supports all partitions backup,i am using it for long time,never faced a single prob and i am not shooting arrows in dark bruh,i have tested and its my experience,if you dont believe try it by urself.
But just dont post like it doesnt support partition backup like alka.

NVDX11 said:
Zcx supports all partitions backup,i am using it for long time,never faced a single prob and i am not shooting arrows in dark bruh,i have tested and its my experience,if you dont believe try it by urself.
But just dont post like it doesnt support partition backup like alka.
Click to expand...
Click to collapse
okk bro I am wrong. I am also using it and thanks for the info. I will add it in the tutorial. Thanks

No problem bro, i know you have made guide for new comers( i wont call them noobies) & it's a good one.
But i am just in favor of "if we can do things on easiest way,no need to choose harder ones"
I will try to suggest if some steps need to be included and what other things which we can short doing the flashing procedures.

NVDX11 said:
No problem bro, i know you have made guide for new comers( i wont call them noobies) & it's a good one.
But i am just in favor of "if we can do things on easiest way,no need to choose harder ones"
I will try to suggest if some steps need to be included and what other things which we can short doing the flashing procedures.
Click to expand...
Click to collapse
Thats the good idea bro actually i haven't any knowledge about zcx recovery till the post was submitted. And I have seen somewhere that it comes with few bugs but I think now it gets updated.
Now I am going to re-post the tutorial by editing it and at last thank you so much..

Flashed miui globle dev rom in unofficially unlocked bootloader
even flashed lazy flasher script
disabled dm verify
yet bootloader got locked
now how to flash rom without loosing data

Trustzone error 7
Hello,
currently i am on MIUI 8.2 and when i try to flash any custom ROM based on android N like Lineage OS or Resurrection Remix ROM using official TWRP, I always get trustzone error 7 with following messege:
Checking for TZ version TZ.BF.4.0.1-77307
assert failed: xiaomi.verify_trustzone("TZ.BF.4.0.1-77307") == "1"
Updater process ended with ERROR: 7
which prevents me to flash any of the ROMs. Please help me out....

Probably soft bricked my OP5, is this fixable?

Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard

can you reboot to bootloader?
if yes, you can flash original or custom recovery...

---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
len.asdf said:
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
Click to expand...
Click to collapse
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.

canteo said:
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
Click to expand...
Click to collapse
I can go into fastboot and managed to install TWRP with the comment below!
Zohair.ul.hasan said:
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
Click to expand...
Click to collapse
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help

len.asdf said:
I can go into fastboot and managed to install TWRP with the comment below!
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
Click to expand...
Click to collapse
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!

Zohair.ul.hasan said:
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Click to expand...
Click to collapse
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help

len.asdf said:
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
Click to expand...
Click to collapse
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it

Zohair.ul.hasan said:
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Click to expand...
Click to collapse
Haha thanks! Just in time. Was still downloading the latest CNP .

Whew! Update me after flashing.

Zohair.ul.hasan said:
Whew! Update me after flashing.
Click to expand...
Click to collapse
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted

len.asdf said:
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
Click to expand...
Click to collapse
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it

Zohair.ul.hasan said:
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Click to expand...
Click to collapse
YES! It work. Many thanks

len.asdf said:
YES! It work. Many thanks
Click to expand...
Click to collapse
Congrats! Please like my replies if you don't mind

Zohair.ul.hasan said:
Congrats! Please like my replies if you don't mind
Click to expand...
Click to collapse
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?

len.asdf said:
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
Click to expand...
Click to collapse
Yes it should but that's okay

Zohair.ul.hasan said:
Yes it should but that's okay
Click to expand...
Click to collapse
installed the xda app and there I could give you a 'thanks'

TWRP can't decrypt

Hi all!
I've been using the 6T for a while (great phone, veeeery slippery!), I've rooted it without any problem (twrp-3.2.3-x_blu_spark_v9.86_op6).
Now, before doing the OTA updates, I want to do a nandroid backup, but it always fails with the message:
Code:
I:Error adding file '/data/data/tcTMGKoV3DJi2BtFo,DVwA/NdOFCMKtKQfG60hOSGJXIB/utPFuENU2UMyfeNmcGVBFC' to '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.info'
[B]createTarFork() process ended with ERROR: 255[/B]
Backup Failed. Cleaning Backup Folder.
When TWRP starts it doesn't ask for the password (I've a password, no patern).
I've tried to decrypt in the terminal
Code:
~ # twrp decrypt PASSWORD
Attempting to decrypt data partition via command line.
Failed to decrypt data
The log:
Code:
I:Command 'decrypt PASSWORD' received
I:Set page: 'singleaction_page'
I:operation_start: 'TWRP CLI Command'
Attempting to decrypt data partition via command line.
get_crypt_ftr_info crypto key location: ''
Unexpected value for crypto key location
Error getting crypt footer and key
Failed to decrypt data.
Am I the only one having this problem?
How can I solve it?
Thanks!

The only reason I know of to use the BluSpark recovery is if you want to use OP6 roms? Why aren't you using one of the OP6T TWRP?
Right now there are problems with backup and recovery anyways, so you maybe out of luck even if you did have a backup. I've had zero issues updating my phone flashing the full package. Just make you flash the TWRP installer again after you flash the the full ROM, reboot to recovery again, flash Magisk again. Reboot to the system finally. Instructions for TWRP users are in this post.

OhioYJ said:
The only reason I know of to use the BluSpark recovery is if you want to use OP6 roms? Why aren't you using one of the OP6T TWRP?
Click to expand...
Click to collapse
Because I've followed this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ and right now I want to stay on OxygenOS. I've been on LineageOS for years and I love all the settings that it has, but I'm tired of unstable ROMS!
Right now there are problems with backup and recovery anyways, so you maybe out of luck even if you did have a backup. I've had zero issues updating my phone flashing the full package. Just make you flash the TWRP installer again after you flash the the full ROM, reboot to recovery again, flash Magisk again. Reboot to the system finally. Instructions for TWRP users are in this post.
Click to expand...
Click to collapse
Well...I'll try without a backup... :fingers-crossed:

andrea_x said:
Because I've followed this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ and right now I want to stay on OxygenOS. I've been on LineageOS for years and I love all the settings that it has, but I'm tired of unstable ROMS!
Well...I'll try without a backup... :fingers-crossed:
Click to expand...
Click to collapse
The guide you are following is over a month old now and development has progressed since then. The principals are the same, just use one of the newer TWRP, specifically for the OP6T. Though currently unofficial, most of the features now work, including decryption. I believe one of the test versions supports full backup and restore also now, though I haven't tested it myself. Great work from XDA developers as usual.

I can confirm, both of the new, unofficial twrps's are fully functional. As far as the necessities go. Not sure about aroma, as I don't use any of those. But, backup and restore, function perfectly. As well as decryption, obviously

Nandroid backup
andrea_x said:
Hi all!
I've been using the 6T for a while (great phone, veeeery slippery!), I've rooted it without any problem (twrp-3.2.3-x_blu_spark_v9.86_op6).
Now, before doing the OTA updates, I want to do a nandroid backup, but it always fails with the message:
Code:
I:Error adding file '/data/data/tcTMGKoV3DJi2BtFo,DVwA/NdOFCMKtKQfG60hOSGJXIB/utPFuENU2UMyfeNmcGVBFC' to '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.info'
[B]createTarFork() process ended with ERROR: 255[/B]
Backup Failed. Cleaning Backup Folder.
When TWRP starts it doesn't ask for the password (I've a password, no patern).
I've tried to decrypt in the terminal
Code:
~ # twrp decrypt PASSWORD
Attempting to decrypt data partition via command line.
Failed to decrypt data
The log:
Code:
I:Command 'decrypt PASSWORD' received
I:Set page: 'singleaction_page'
I:operation_start: 'TWRP CLI Command'
Attempting to decrypt data partition via command line.
get_crypt_ftr_info crypto key location: ''
Unexpected value for crypto key location
Error getting crypt footer and key
Failed to decrypt data.
Am I the only one having this problem?
How can I solve it?
Thanks!
Click to expand...
Click to collapse
Hey were you able to solve the problem? If yes, please tell how?

I'm using twrp-fajita-3.2.3-8-installer.zip and it works.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482

ZeRoZeRoRaZ said:
I'm using twrp-fajita-3.2.3-8-installer.zip and it works.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
It says backup still having some problem and I already have installed twrp blu spark version. I think this problem is due to encrypted phone.

I'm running into this issue, too. I just flashed the latest OP zip as well as TWRP installer, and after flashing a ROM and TWRP installer, I rebooted to TWRP. I was about to flash Magisk and gapps, however I discovered my filenames were all scrambled.

sabrdawg said:
I'm running into this issue, too. I just flashed the latest OP zip as well as TWRP installer, and after flashing a ROM and TWRP installer, I rebooted to TWRP. I was about to flash Magisk and gapps, however I discovered my filenames were all scrambled.
Click to expand...
Click to collapse
This means your phone is encrypted, decrypt it first.

mansi0312 said:
This means your phone is encrypted, decrypt it first.
Click to expand...
Click to collapse
Do you mean by formatting data via TWRP? I can do that, once I get home and can copy all my files to my computer.

sabrdawg said:
Do you mean by formatting data via TWRP? I can do that, once I get home and can copy all my files to my computer.
Click to expand...
Click to collapse
If you have a oneplus 6t it won't work, decryption is still an issue on oneplus 6t. If you want to decrypt this badly you can follow this thread. I haven't tried it yet but you can give it a go. Do tell how did it go.
https://forum.xda-developers.com/one...overy-t3861482
Meanwhile or if you don't want to decrypt your phone, you can install magisk and gapps via adb sideload or using an otg. It has nothing to do with encryption. Encrypted phone will not let you make nandroid backups on the phone's internal storage and you will have to flash zip files using adb sideload or otg storage.
I have installed zips with this method without decrypting the phone.

sabrdawg said:
I'm running into this issue, too. I just flashed the latest OP zip as well as TWRP installer, and after flashing a ROM and TWRP installer, I rebooted to TWRP. I was about to flash Magisk and gapps, however I discovered my filenames were all scrambled.
Click to expand...
Click to collapse
Latest OnePlus Zip and Gapps? Why would you flash Gapps?
In my experiences this is caused by:
1. TWRP did not ask for a PIN, which can be corrected by another reboot (typically).
2. You are trying to use a OP6 recovery and a OP6T ROM, or vice versa. In that case, use the correct recovery for the ROM you are trying to use and your data will become readable. Even if you only need it to be temporary to pull it.
3. You ran AOSP rom and now your DATA partition is formatted for that. It will have to be formatted before OP6T recovery will read it. A OP6 recovery will read it.
There are no problems with OP6T recovery that I've found decrypting anything if you are aware of the caveats. So far the only issue really seems to be backing up / restoring still. Hopefully this helps.
*edit* I should add that OP6 recoveries would read AOSP data partitions before, I haven't tested this since the release of "dedicated" OP6T AOSP roms. So let us know what you find. *edit*

I ran across the same problem with my OnePlus 6.
Just do this:
- Download official twrp.
- Reboot to fastboot mode
- boot with it (fastboot boot ***.img)
Now it will temporarily boot and ask for decrypt password. Hola!

mansi0312 said:
Hey were you able to solve the problem? If yes, please tell how?
Click to expand...
Click to collapse
I've flashed twrp-fajita-3.2.3-8-installer

andrea_x said:
I've flashed twrp-fajita-3.2.3-8-installer
Click to expand...
Click to collapse
Hey,
Isn't fajita recovery for OP6?

mansi0312 said:
Hey,
Isn't fajita recovery for OP6?
Click to expand...
Click to collapse
No, fajita is the name code of op6t, didn't you notice that there are a lot of fajitas in threads names ?
---------- Post added at 07:13 AM ---------- Previous post was at 07:12 AM ----------
andrea_x said:
I've flashed twrp-fajita-3.2.3-8-installer
Click to expand...
Click to collapse
Try the latest version, -28

Striatum_bdr said:
No, fajita is the name code of op6t, didn't you notice that there are a lot of fajitas in threads names ?
---------- Post added at 07:13 AM ---------- Previous post was at 07:12 AM ----------
Try the latest version, -28
Click to expand...
Click to collapse
Is this a stable version?

mansi0312 said:
Is this a stable version?
Click to expand...
Click to collapse
Yes

I'm having the same issue and flashing the latest TWRP didn't solve it. Can't boot into system either, it just loops me back to TWRP.

why installing ROM encrypted my recovery function

so, my phone was MIUI 10 , i decided to go 11, so i downloaded and installed via recovery.
thing is, when i rebooted and tried to flash magisk the recovery - TWRP - asked for a password, which i didn't put..
why is that?
is any ROM installation does that? is it the recovery's fault?

U read this?
https://forum.xda-developers.com/re...ngefox-recovery-project-t3941822/post79771468

joke19 said:
U read this?
https://forum.xda-developers.com/re...ngefox-recovery-project-t3941822/post79771468
Click to expand...
Click to collapse
i guess you meant for this?
11. If you experience a situation where you have set a PIN, but the recovery asks for a password (or vice versa, etc), then you must ask your ROM devs to fix their ROM by applying this patch. This is not a recovery issue, so please do not ask us to "fix" it. Alternatively, you can always open a terminal in the recovery (or via "adb shell") and run "twrp decrypt password".
1. thank you.
2. i dont have orangeFox though i guess it's the same

arik100 said:
i guess you meant for this?
11. If you experience a situation where you have set a PIN, but the recovery asks for a password (or vice versa, etc), then you must ask your ROM devs to fix their ROM by applying this patch. This is not a recovery issue, so please do not ask us to "fix" it. Alternatively, you can always open a terminal in the recovery (or via "adb shell") and run "twrp decrypt password".
1. thank you.
2. i dont have orangeFox though i guess it's the same
Click to expand...
Click to collapse
No, I am sure he was referring to points #6, #7, and #8.

i was at stock rooted miui, with custom recovery.
just flashed the eu miui via recovery , of course i did format data and got to this state.
now i just did format data, and instead of installing rom rebooting and then root, i did install rom and root in the same session.
probably if i enter the recovery it will still give me the encrypt message? dunno, maybe because i didn't re-install the recovery..

arik100 said:
i was at stock rooted miui, with custom recovery.
just flashed the eu miui via recovery , of course i did format data and got to this state.
now i just did format data, and instead of installing rom rebooting and then root, i did install rom and root in the same session.
probably if i enter the recovery it will still give me the encrypt message? dunno, maybe because i didn't re-install the recovery..
Click to expand...
Click to collapse
Same happened with me. Whatever you do your recovery is not gonna decrypt, i tried everything that i can found but nothing worked.
This is only when you flash 10.0 roms no 9.0 rom is gonna cause problem, still searching for a fix. Dont even know what causing this, maybe because it is indian variant or i dont know. Anybody....???

Same issue with an Android 10 Rom.

mr.badman said:
Same happened with me. Whatever you do your recovery is not gonna decrypt...
Click to expand...
Click to collapse
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Roster42 said:
Same issue with an Android 10 Rom.
Click to expand...
Click to collapse
Did you use OrangeFox recovery?

DarthJabba9 said:
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Did you use OrangeFox recovery?
Click to expand...
Click to collapse
i used TWRP
why?

arik100 said:
i used TWRP
why?
Click to expand...
Click to collapse
Because OrangeFox recovery can decrypt quite fine.

DarthJabba9 said:
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Did you use OrangeFox recovery?
Click to expand...
Click to collapse
I have tried everything, si yes I have tried with orangeFox

Roster42 said:
I have tried everything, si yes I have tried with orangeFox
Click to expand...
Click to collapse
I should like to see the OrangeFox logs (they will be in the /sdcard/Fox/logs/ folder), because I am yet to see a single situation where OrangeFox cannot decrypt (especially if you formatted data).

Thank you for your answer. I will provide this tonight sir.
The thing is, if I format /data of course I can use my internal storage, but if I re flash the ROM, it will encrypt again. It's like a loop.
I heard it's an issue with android 10, recovery don't know how to manage it.

Roster42 said:
Thank you for your answer. I will provide this tonight sir.
The thing is, if I format /data of course I can use my internal storage, but if I re flash the ROM, it will encrypt again. It's like a loop.
I heard it's an issue with android 10, recovery don't know how to manage it.
Click to expand...
Click to collapse
Yes, the ROM will encrypt again, unless you disable forced-encryption before flashing it (there is a setting in OrangeFox for that). However, lavender has serious issues if it is not encrypted (pin/password/fingerprint will not work). So I do not recommend disabling forced-encryption.
The point is that OrangeFox will automatically decrypt when you boot it up, so that the recovery has full access to internal storage and the data partition. Since 99.9% of lavender devices are encrypted, there is absolutely no problem running OrangeFox on them. This is the best you can hope for. What else would you want?
But if you really insist on running the device unencrypted (you will be running your device with absolutely no security if you do this), then you need to do the following;
1. Format (not just wipe) the data partition;
2. Reboot OrangeFox;
3. Go to the OTA settings, and tick "Disable Forced-Encryption";
4. Flash the ROM;
5. Boot the ROM.
All things being equal, the ROM will remain unencrypted - but you can kiss goodbye to any possibility of having any security on your ROM. If anybody gets a hold of your phone, he will have full access to everything on it, without any restriction of any kind. Clearly, you really don't want this situation, so I am not sure why you would want the phone to be unencrytped.
Note: some ROMs will simply ignore all efforts to disable forced-encryption, and will happily encrypt anyway. If you have such a ROM, then I would add "4A" to the above list - "Flash magisk before booting the ROM"

DarthJabba9 said:
Yes, the ROM will encrypt again, unless you disable forced-encryption before flashing it (there is a setting in OrangeFox for that). However, lavender has serious issues if it is not encrypted (pin/password/fingerprint will not work). So I do not recommend disabling forced-encryption.
The point is that OrangeFox will automatically decrypt when you boot it up, so that the recovery has full access to internal storage and the data partition. Since 99.9% of lavender devices are encrypted, there is absolutely no problem running OrangeFox on them. This is the best you can hope for. What else would you want?
But if you really insist on running the device unencrypted (you will be running your device with absolutely no security if you do this), then you need to do the following;
1. Format (not just wipe) the data partition;
2. Reboot OrangeFox;
3. Go to the OTA settings, and tick "Disable Forced-Encryption";
4. Flash the ROM;
5. Boot the ROM.
All things being equal, the ROM will remain unencrypted - but you can kiss goodbye to any possibility of having any security on your ROM. If anybody gets a hold of your phone, he will have full access to everything on it, without any restriction of any kind. Clearly, you really don't want this situation, so I am not sure why you would want the phone to be unencrytped.
Note: some ROMs will simply ignore all efforts to disable forced-encryption, and will happily encrypt anyway. If you have such a ROM, then I would add "4A" to the above list - "Flash magisk before booting the ROM"
Click to expand...
Click to collapse
I just saw the option OTA -*> disable forced-encryption. I will try that if I have some time this week, if I don't find other work around.
And just to be clear, yes I want my phone encrypted. Yes I know security is important.
But what I prefer is to have up to date ROM with security patchs and new features.
Because my recovery (OrangeFox and TWP) wasn't able to decrypt my phone I wasn't able to wipe cache and delvik and to do updates.
The thing is there is a unknown password asked when I boot in recovery (I tried every operations I have found on every forums).
Will give some updates later on this thread.
Again, thanks for your answers.

Roster42 said:
I just saw the option OTA -*> disable forced-encryption. I will try that if I have some time this week, if I don't find other work around.
And just to be clear, yes I want my phone encrypted. Yes I know security is important.
But what I prefer is to have up to date ROM with security patchs and new features.
Because my recovery (OrangeFox and TWP) wasn't able to decrypt my phone I wasn't able to wipe cache and delvik and to do updates.
The thing is there is a unknown password asked when I boot in recovery (I tried every operations I have found on every forums).
Will give some updates later on this thread.
Again, thanks for your answers.
Click to expand...
Click to collapse
As I have said, OrangeFox is most definitely able to decrypt. I am yet to come across a single lavender ROM where OrangeFox has not been able to decrypt (and I have tested on virtually all Q ROMs out there) - unless there is something that you are doing (or not doing) , or (which would be very strange indeed) there is something about your own specific phone that makes it particularly impervious to OrangeFox decryption in a way that the phones of several thousands of OrangeFox lavender users are not.

delete

I tried yesturday a clean install, still having the same issue with this ROM : https://forum.xda-developers.com/redmi-note-7/development/rom-havoc-os-2-6-t3938288
I have tried to :
- Format data
- Reboot Recovery
- Wipe all
- Reboot Recovery
- Flash ROM
- Boot ROM (encryption done)
- Reboot recovery OrangeFox : Still asking a password
I tried also to disable forced-encryption with the same step and it's not changing anything.
Is that an issue with the ROM (HavocOS 3.0) ?

Roster42 said:
I tried yesturday a clean install, still having the same issue with this ROM : https://forum.xda-developers.com/redmi-note-7/development/rom-havoc-os-2-6-t3938288
I have tried to :
- Format data
- Reboot Recovery
- Wipe all
- Reboot Recovery
- Flash ROM
- Boot ROM (encryption done)
- Reboot recovery OrangeFox : Still asking a password
I tried also to disable forced-encryption with the same step and it's not changing anything.
Is that an issue with the ROM (HavocOS 3.0) ?
Click to expand...
Click to collapse
Did do you anything else between these two steps ;
- Boot ROM (encryption done)
[ ??? ]
- Reboot recovery OrangeFox : Still asking a password
If you did nothing in-between those two steps, then I would imagine that the issue is with the ROM (probably its device tree).
BTW: I should also like to see the recovery logs.

DarthJabba9 said:
Did do you anything else between these two steps ;
- Boot ROM (encryption done)
[ ??? ]
- Reboot recovery OrangeFox : Still asking a password
If you did nothing in-between those two steps, then I would imagine that the issue is with the ROM (probably its device tree).
BTW: I should also like to see the recovery logs.
Click to expand...
Click to collapse
When ROM boot for the first time it get encrypted, when the encryption process is finished the phone reboot to system and then the android startup process is starting like a new fresh phone. So I just press volume up + shutdown to go in recovery mode and then it asking me a password.
So no I havn't done anything more, I think.
Thank you anyway for your answers.
I think I will go on others ROM, this one seems broken.
I am not the only one havn't this issue.