Database Users

Problem with LineageOS

Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi

possi.rodrigo said:
Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi
Click to expand...
Click to collapse
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.

echo92 said:
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.
Click to expand...
Click to collapse
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!

possi.rodrigo said:
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!
Click to expand...
Click to collapse
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.

echo92 said:
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.
Click to expand...
Click to collapse
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?

possi.rodrigo said:
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?
Click to expand...
Click to collapse
I recall from what Silesh has mentioned is that the commits from ElementalX are present in his kernel, thus the benefits should be seen in the unofficial stock Lineage OS kernel and so you don't necessarily need the ElementalX kernel. If you wish to use the ElementalX kernel with the latest builds of Lineage OS-OMS, and there is nothing stopping you doing so, you need to flash the sensorhub firmware, else you'll lose sensors like your fingerprint sensor (if you have a G4 Plus, that is - I don't know if other sensors are affected on non-Plus models as well if you don't flash this). The firmware can be found here https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2723
To install said firmware if you need it (credit to rahulsnair for the procedure https://forum.xda-developers.com/showpost.php?p=70716729&postcount=170):
Download the zip and extract, you should get a sensorhubfw.bin file. Copy this .bin file to your adb directory.
Connect your device to your computer and check adb can detect your device using 'adb devices'
Staying in adb, execute the command 'adb push sensorhubfw.bin /etc/firmware' (without the quotation marks). This will copy the sensorhub file to the /etc/firmware directory on your phone.
Reboot and hopefully you should have sensors back.

[DISCUSSION] Encryption Thread

First things first:
1. This is not a thread about how to flash ROMs, recoveries or use Android SDK and ABD or fastboot commands. If you have questions about the basics, please keep them in @Funk Wizard's excellent thread created for that purpose:
OnePlus 5T: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!
2. This thread is not the place to discuss the merits of encryption or decryption.
3. I'm not responsible for what you do to your own device. Read, think, read more, re-think, wipe, flash in that order.
4. This OP and the following posts will be updated as the discussion develops, so please check back here from time to time.
Now on to the discussion
There has been a lot of talk lately about encryption, decryption and the benefits and liabilities of each. Obviously having your device encrypted is a gain for security, something we should try to keep if possible. But encryption methods can vary, which is a problem for flashaholics like myself. When you flash a new ROM that cannot read the encryption of the previous ROM, /data must be formatted, causing the loss of /sdcard - pictures, music, files, etc.
Understanding the Problem
The issue seems to revolve around Qualcomm's "KeyMaster" encryption keys. While both Nougat and Oreo use FBE (File Based Encryption), by default they use different encryption keys, as pointed out by dev @codeworkx -- Nougat and Oreo 8.0 use KeyMaster 1 while Oreo 8.1 uses KeyMaster 3. So when an Oreo 8.1 ROM is flashed, it either can't access /data (requires decryption or formatting /data) or the ROM reformats /data itself, like early beta Lineage 15.1 builds. Likewise, reverting to a Nougat or Oreo 8.0 build will cause the same problem. Apparently, moving to KeyMaster 1 to 3 works (ie, flashing from OOS to Omni/Lineage) but reverting from Keymaster 3 back to 1 doesn't. When this happens, OOS can still decrypt with your PIN/password but TWRP can't.
One solution is to run unencyrpted, for which you may find threads in the How-To section. This discussion is about how to stay encrypted and flash back & forth between ROMs without loosing all of your data.
Links on the subject:
https://source.android.com/security/encryption/file-based
I look forward to your contribution to this discussion! :good:

Reserved

Just dropping this here:
mad-murdock said:
If only someone would be advanced in linux FBE, used tools and libraries. There surely is a way to remove encryption with a flashable .zip. _IF_ current TWRP has the needed tools onboard.
I hope one day we get encrypt/decrypt options in TWRP - where it belongs.
Click to expand...
Click to collapse

Yes, NOW I have seen this thread. Thanks for mentioning.
Seems useful.
After a bit of google kicking, I found this: https://source.android.com/security/encryption/file-based
Seems a good start on the topic. Maybe add it to a list of (hopefully growing) links?

Wow. Seems like this didn't work out that well.

mad-murdock said:
Wow. Seems like this didn't work out that well.
Click to expand...
Click to collapse
1. Rather than understand and deal with it, lots of people decrypt.
2. The issue hasn't gone away. Give it time.

Great information to those who recently owned an OP even if they have knowledge how to flash ROMs. (Including me)
Thanks!

I've stumbled across another issue for investigation. While experimenting yesterday, I discovered that @codeworkx TWRP 3.2.1-0 for Oreo (8.0 and 8.1) is able to read stock OOS/OOS B1 encryption until it is backed up in TWRP, an Oreo 8.1 ROM is flashed (eg, Omni, Lineage), and OOS is restored. After that, TWRP cannot decrypt /data with the correct PIN/password of the restored OOS ROM or "default_password". It doesn't matter if the nandroid was taken with or without a PIN/password, if the PIN/password is removed from the Oreo 8.1 ROM before restoring the nandroid, etc. Codeworkx suspects it has to do with how the passwords are being stored between 8.0 and 8.1.
And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password.
Also, I've left recovery systemless. That means my nandroid backups are only of data, and I restore by flashing the stock OOS ROM and only restoring the data nandroid. So zero changes have been made to system.

the Doctor said:
I've stumbled across another issue for investigation. While experimenting yesterday, I discovered that @codeworkx TWRP 3.2.1-0 for Oreo (8.0 and 8.1) is able to read stock OOS/OOS B1 encryption until it is backed up in TWRP, an Oreo 8.1 ROM is flashed (eg, Omni, Lineage), and OOS is restored. After that, TWRP cannot decrypt /data with the correct PIN/password of the restored OOS ROM or "default_password". It doesn't matter if the nandroid was taken with or without a PIN/password, if the PIN/password is removed from the Oreo 8.1 ROM before restoring the nandroid, etc. Codeworkx suspects it has to do with how the passwords are being stored between 8.0 and 8.1.
And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password.
Also, I've left recovery systemless. That means my nandroid backups are only of data, and I restore by flashing the stock OOS ROM and only restoring the data nandroid. So zero changes have been made to system.
Click to expand...
Click to collapse
""And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password""
So Do you mean to say I can revert back to OOS OB-1 by flashing it over Omni/LOS/etc via TWRP without formatting Data, and later on restoring Nandroid data of OOS OB-1.

shail139 said:
""And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password""
So Do you mean to say I can revert back to OOS OB-1 by flashing it over Omni/LOS/etc via TWRP without formatting Data, and later on restoring Nandroid data of OOS OB-1.
Click to expand...
Click to collapse
Yes, but obviously TWRP would not be able to decrypt with a PIN/password set by OOS. That just means you would have to disable lockscreen protection in the ROM before going into TWRP.

the Doctor said:
Yes, but obviously TWRP would not be able to decrypt with a PIN/password set by OOS. That just means you would have to disable lockscreen protection in the ROM before going into TWRP.
Click to expand...
Click to collapse
By that way the steps to restore should be...
1. Backup of OOS OB-1 in TWRP should be taken post removal all securities PIN/PASSWORD/etc (On external drive/OTG)
2. Flash OOS OB-1 normally, clean flash, boot to system, no security should be set
3. Boot to TWRP, restore OOS OB-1 Backup Only "Data" should be checked via OTG drive
4. Reboot to system
"twrp-3.2.1-0-universal-codeworkx-dumpling" will be the TWRP to be used
Correct me if I am wrong in steps

so in this case, am i right to say that, so long i dont do nandroid restore, i wouldnt have problem with encryption/decryption regardless of what rom i'm flashing using codeworkx's universal TWRP?
usually i always clean flash new roms and i'm ok to go through the 'hassle' of reinstalling stuffs. if i want to go back to the previous rom, i'll just do a clean flash of the previous rom instead of reverting back via nandroid.
so technically so long i'm on the right TWRP, i'm fine with switching roms am i right?
thanks for sharing the findings as well!

gorillaCF said:
so in this case, am i right to say that, so long i dont do nandroid restore, i wouldnt have problem with encryption/decryption regardless of what rom i'm flashing using codeworkx's universal TWRP?
usually i always clean flash new roms and i'm ok to go through the 'hassle' of reinstalling stuffs. if i want to go back to the previous rom, i'll just do a clean flash of the previous rom instead of reverting back via nandroid.
so technically so long i'm on the right TWRP, i'm fine with switching roms am i right?
thanks for sharing the findings as well!
Click to expand...
Click to collapse
I tried a clean flash of OOS from TWRP as well, but even that didn't work. I think you'd have to restore factory encryption per this guide to get TWRP to be able to decrypt OOS again:
[How To] Revert to 100% stock OOS from Oreo 8.1 | Restore factory encryption
Again, you can flash, backup and restore in TWRP even if you don't. It just won't be able to decrypt /data with your OOS PIN/password, so you'd have to remove lockscreen security first.

the Doctor said:
I tried a clean flash of OOS from TWRP as well, but even that didn't work. I think you'd have to restore factory encryption per this guide to get TWRP to be able to decrypt OOS again:
[How To] Revert to 100% stock OOS from Oreo 8.1 | Restore factory encryption
Again, you can flash, backup and restore in TWRP even if you don't. It just won't be able to decrypt /data with your OOS PIN/password, so you'd have to remove lockscreen security first.
Click to expand...
Click to collapse
Formating /data is the only way to go back to 8.0 crypto (after booting fully stock) and then you can use you Nandroids from OOS to restore /data with PIN, face unlock all ON.
Been there, done that from 8.1 custom to OOS N.
Didn't use stock recovery, didn't use revert builds, there actually were none at the time, but I think they are unneeded anyway.
It's a cumbersome process because backing up internal storage and restoring it is a pain when you have a lot of data to carry around.
But it's pretty straight forward.
All this done on blu_spark TWRP.

The problem I noted above wasn't that OOS couldn't read or encrypt /data properly after the nandroid backup--TWRP couldn't read OOS's PIN/password. I had no problems restoring and running OOS after running Omni/Lineage. After I restored OOS, on first boot I entered the PIN and found that my fingerprints and face unlock still worked. But when I booted back into Codeworkx TWRP neither the PIN or "default_password" worked. I didn't try Blu_Spark.
IMO, what we ultimately want is an official TWRP that can decrypt without workarounds so we can avoid the cumbersome process or formatting /data and moving everything back to /sdcard.
Edit: Here is the exact sequence of what happened:
I came from OOS OB1 with /data formatted by the stock recovery, encrypted, with PIN/fingerprints/face unlock.
I booted Codeworkx recovery, entered the PIN, it decrypted properly, I did a nandroid backup of the Data partition.
Still in recovery, I wiped Dalvik-Art/Cache/System/Data, then flashed Omni, gapps, Magisk.
I ran Omni for a while, moved to Lineage using the same process as above. I never removed the PIN, and Codeworkx TWRP had no problems decrypting with it in Omni or Lineage.
After running Lineage for a while, I went back into Codeworkx TWRP, decrypted with my PIN (it worked), wiped as above, flashed OOS OB1 with the factory zip, wiped the Data partition, restored Data from nandroid, flashed Magisk, rebooted.
On first boot OOS asked for a PIN. I entered my PIN and found my fingerprints & face unlock still working.
VVV HERE IS THE PROBLEM STARTED VVV
When I booted back into Codeworkx TWRP it could not decrypt with my PIN. I booted back into OOS and removed my PIN, set lockscreen protection to "None". TWRP still could not decrypt /data. I tried "default_password" but no dice.
Revert back to Omni, remove PIN, reboot TWRP, still can't decrypt.
So something changed between when I restored OOS OB1 (TWRP could decrypt with the PIN) and after first boot (TWRP couldn't decrypt with the PIN). Also, why could TWRP decrypt with OOS OB1's PIN to do the nandroid backup from a clean flash and to restore the same backup after being on Omni/Lineage, but couldn't decrypt with it after the first boot of the OOS nandroid backup?
Again, formatting /data again is not an acceptable workaround. I think we want to understand what changed and solve the problem.

the Doctor said:
Again, formatting /data again is not an acceptable workaround. I think we want to understand what changed and solve the problem.
Click to expand...
Click to collapse
The mentioned /data format is not a workaround per se, it's the only working workflow to get things going once you find the need to get back to OOS for the time being.
Accepting that is part of the process!
Users should know this upfront so they don't find out the hard way.

I'm currently running OxygenOS 5.0.3 and my understanding is that it uses Keymaster1. If I'm now upgrading to LineageOS 15.1 it'd change to Keymaster3 but without the need of formatting.
However, if I'd want to revert to OxygenOS 5.0.3 with Keymaster1 I would have to format /data. Is my understanding correct?

Macusercom said:
I'm currently running OxygenOS 5.0.3 and my understanding is that it uses Keymaster1. If I'm now upgrading to LineageOS 15.1 it'd change to Keymaster3 but without the need of formatting.
However, if I'd want to revert to OxygenOS 5.0.3 with Keymaster1 I would have to format /data. Is my understanding correct?
Click to expand...
Click to collapse
My experience has been that the ROM can decrypt without any issues, but TWRP can't decrypt without formatting /data with the stock recovery.

the Doctor said:
My experience has been that the ROM can decrypt without any issues, but TWRP can't decrypt without formatting /data with the stock recovery.
Click to expand...
Click to collapse
As previous posters have alluded to, use "twrp-3.2.1-0-universal-codeworkx-dumpling.img". This is able to decrypt 5.0.3.

wunderdrug said:
As previous posters have alluded to, use "twrp-3.2.1-0-universal-codeworkx-dumpling.img". This is able to decrypt 5.0.3.
Click to expand...
Click to collapse
Right. Flash Omni or Lineage, then go back OOS and try it again as Macusercom says in the post I quoted.

[FIX][8.1][Treble]Decryption Unsuccessful and TWRP Internal Storage 0MB

As the tittle says, this is my current workaround for issues that happened after most people update their AOSP based ROMs after 3rd July 2018.
Decryption Unsuccessful
Q: Why does this happens ?
A: There's some weird issues with the latest AOSP based ROM that makes encrypted ext4 based data partition unable to be decrypted in both system and older version of TWRP if you're encrypted before (intentionally or unintentionally). This however doesn't apply to F2FS and unencrypted ext4 data partition.
Q: How do I solve this ?
A: There's 2 ways you can do to solve this issue.
The best way and the most recommended way is to repartition your data into F2FS. However it does require you to do a backup beforehand since this will wipe everything in your internal storage.
1. Backup your internal storage from TWRP (either to a SD card or PC via ABD)
2. Format it by going into TWRP and select Format and choose "wipe data"
3. Type "yes" and let the process end.
4. Flash your ROM and GApps.
5. Finish the setup without setting any screen lock so that it doesn't encrypt your data partition.
-Or-
The other way does is to install a custom kernel is made after 20 July 2018
List of kernel that can boot successfully without the need to wipe /data :
-Xenial b25x or newer
-Revolt EAS-R13
(Got kernel that works and doesn't show up here? TELL ME, I'll add it to my list for everyone's reference)
Link for the working TWRP that can detect Internal Storage :
Jairus' modded TWRP
https://androidfilehost.com/?fid=5862345805528049168
Or you can look up Orange Fox recovery
(link will be added soon)

Good Stuff Also This Happened to me while i was using the Android P DP3 i tried twrp and redwolf and was the same i flashed the Orange Fox and it worked

Does this twrp can flash both treble and non treble ROM?

eko_epe said:
Does this twrp can flash both treble and non treble ROM?
Click to expand...
Click to collapse
Yes, it does

AkmalWarrior said:
Yes, it does
Click to expand...
Click to collapse
Ok i'll try. Thanks

As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.

DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
TWRP and redwolf too (find on telegram)
Envoyé de mon Redmi Note 4 en utilisant Tapatalk

DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
*Only in recovery, not in boot. The only way to fix decryption unsuccessful on boot is to either repartition data to F2FS or flash a custom kernel that's made after 20 July. List on working kernels is on main thread.

First I tried orange fox beta and it showed my internal storage
Then I flashed the RR endless
But the encryption was still there
Then I tried the twrp from this thread and flashed rom with latest xenial
And it worked no problem
Thank you

How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1

DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk

antony felix said:
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk
Click to expand...
Click to collapse
Thanks,So i must format internal too,. It's ok but how if i want to comeback use nougat..? I hear who's downgrade after using oreo will get "encryption was interrupted" on any nougat los/aosp base rom,should be format internal for working back the devices..
I think by this thread shared we get solution for who's want to downgrade from oreo without facing encryption issue enytime for oreo back to nougat or vice

DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.

What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?

AkmalWarrior said:
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.
Click to expand...
Click to collapse
Finally i can confirm for fixed "encryption was interrupted" by changing data partition into F2FS, yes i think it's only way to get free from that, i'v been test it back to back from oreo down to nougat or vice, no worry anymore
Below screenshot for oreo left side and nougat in right

ngydna said:
What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?
Click to expand...
Click to collapse
Read the OP, the recovery only help you boot into recovery and format your data partition or flash a custom kernel to allow you to boot into system as this issue does affect some older version of TWRP recovery. The recovery alone can't help you boot into system.

I took out my sdcard and did format data on the internal storage and now i can't mount my sdcard. Didn't think about the fact that removing the encryption on the internal storage would make it unable to recognize the encryption on the sdcard afterwards. Is there any way to fix this? Or did I just screw myself?
---------- Post added at 01:53 PM ---------- Previous post was at 01:00 PM ----------
When I reinstalled the rom and tried to boot it still asks me for my password which still works even though I can't boot because it says that the data is corrupted. But the encryption key should still be stored somewhere apparently. There must be a way to use it to decrypt the sdcard.

How to install TWRP and custom rom?

Please give me instruction!
What I have done to there:
1. Unlocked bootloader
2. Boot TWRP .img file
3. Install recovery ram disk from the same .img file
4. Reboot to TWRP
5. Install TWRP installer .zip file
6. Reboot to TWRP
7. Wipe system, data, dalvik partitions
8. Flash Havoc and TWRP installer
9. Reboot to TWRP
10. PARTITIONS ENCRYPTED/UNABLE TO FLASH GAPPS
I'm using TWRP UNOFFICIAL BY MAURONOFRIO.
What to do now?
I'm tired! Give me instruction!

You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.

Maybe this thread will help.

dj_ooms said:
You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.
Click to expand...
Click to collapse
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION

ALYSKY said:
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION
Click to expand...
Click to collapse
Its the third post (link) in the thread I linked to....

Actual custom rom flashing instructions ??

This is my first Oneplus device and I just realized that in this device, in order to flash Custom Roms, you need to have a OOS installed beforehand plus not wiping /System partition.
So I was wondering which one is the best and quickest way to do a clean and fresh install from scratch, with the less amount of stuff from previous roms since wiping /System will end up on a bootloop.
Would it be something like this:
Starting from fresh and clean OOS latest version:
-Wipe /Data /Cache /Internal
-Flash Rom + kernel (optional) + TWRP
-Reboot recovery
-Flash Gapps + Magisk.
-Reboot System.
Is this the cleanest way to do it ?
I've seen @Koogly 's video but I dont know if theres a better way to do it.
Thank you all.

dirtyl0lharry said:
This is my first Oneplus device and I just realized that in this device, in order to flash Custom Roms, you need to have a OOS installed beforehand plus not wiping /System partition.
So I was wondering which one is the best and quickest way to do a clean and fresh install from scratch, with the less amount of stuff from previous roms since wiping /System will end up on a bootloop.
Would it be something like this:
Starting from fresh and clean OOS latest version:
-Wipe /Data /Cache /Internal
-Flash Rom + kernel (optional) + TWRP
-Reboot recovery
-Flash Gapps + Magisk.
-Reboot System.
Is this the cleanest way to do it ?
I've seen @Koogly 's video but I dont know if theres a better way to do it.
Thank you all.
Click to expand...
Click to collapse
First time from oos zip
Flash latest stock rom oos
Flash twrp zip
Wipe data and cache
Reboot to recovery
Flash latest stock rom oos zip
Flash twrp zip
Wipe data and cache
Flash custom rom zip
Flash twrp zip
Flash gapps zip
Flash magisk zip if you want root
Reboot to system
If you are already on custom
Flash lastest stock oos zip
Wipe data and cache
Flash custom rom zip
Flash twrp zip
Flash gapps zip
Flash magisk zip if you want root
Reboot to system
If going from custom to oos
Back up all your internal storage pictures videos music etc
Wipe data internal storage and cache
Flash latest stock oos zip
Flash twrp zip if you still want to customize
Reboot to recovery
Flash latest stock oos zip
Flash twrp zip if you still want to customize
Flash magisk zip if you want root
Reboot to system
If you want a custom kernel on any of these methods I would recommend booting the rim first and going through setup process the rebooting back to to twrp after and flashing the kernel
Also you will want a USB c otg port bc after the first flash your data will be encoded. You can select the otg storage via twrp to make the process easier.
If you don't have an otg cable you will need to sideload each zip via cmd prompt with fastboot tools and sideload in twrp
After all flashes are complete and you boot the rom the encrypted data will no longer be encrypted on custom rom flashing if going back to stock oos rom you lose all internal data

Most ROMs threads have instructions in main thread and those should be followed first. Some ROMs may require some bits and pieces from original oxygen rom prior to custom install
Asoip for example

Is flashing oos necessary if we unlock bootloader?
I see instructions for lineage os dont mention flashing of oos bit they have the first step as unlocking the bootloader

mustafabakrolwala said:
Is flashing oos necessary if we unlock bootloader?
I see instructions for lineage os dont mention flashing of oos bit they have the first step as unlocking the bootloader
Click to expand...
Click to collapse
You flash oos first so you have the correct vender and up to date files etc before flashing. Some ROMs require you to flash old oos versions bc their rom was based on that oos vender