yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Sure for EFS.

In the past, I tried to do it with two Mako (Nexus 4) ... but it failed ... and I thought the Nandroid backup was "tagged".
[OnePlus 3 & 3T Cross Device Development] :
I was able with my galaxy tab 2

Another way you could back up system image via twrp, extract the backup until you found the .img files (boot/system etc), flash via fastboot
[OnePlus 3 & 3T Cross Device Development] rohitharkhani:
I am also facing same issue after installing OOS 9 for firmware update and then flash TWRP. did you got any solution?
[OnePlus 3 & 3T Cross Device Development] :
Did you try to disable "oem unlocking" in the rom's setings prior to boot to fastboot mode?
[OnePlus 3 & 3T Cross Device Development] rohitharkhani:
If i am understating correct you are talking about the developer options. We cant disable it. We have to lock bootloader and then only we can disable it. I also tried complete wipe and then install OSS, But no luck.
[OnePlus 3 & 3T Cross Device Development] Paschfire:
It's very strange.

I was experiencing the same on my 3T, having the OEM unlocking toggle greyed out stuck in the unlocked position after flashing OOS 9.0.3 over 5.0.8 w/unlocked bootloader (Following a factory reformat of /UserData)

Though, at some point during the process of reinstalling TWRP, Magisk 19.4c, Franco Kernel r48. The toggle has returned allowing me to select locking or unlocking option again.
[OnePlus 3 & 3T Cross Device Development] txyko:
About TWRP and updating to latest OS

Hi,

I have a oneplus 3T, with an old TWRP 2.0 version. I want to update to the latest Android OS, but i get an error.

Reading it seems it is because the old TWRP version, but all the information I find is for newer versions of TWRP.

If I try to update to the latest TWRP connecting the phone to the computer, with fastboot or something like that i read (sorry im not that much tech savy), would it be ok? I want to get the latest OS, but afraid to brick the phone :S

Thank you.
[OnePlus 3 & 3T Cross Device Development] Dirk:
You can fastboot flash the new build, or just flash it using the existing build. Boot into Recovery, Install Menu, select image (instead of zip), navigate to the new TWRP img file and select it, select Recovery as partition to flash to and swipe to install.
[OnePlus 3 & 3T Cross Device Development] rohitharkhani:
Finally i was able to lock. After we trigger fastboot oem lock command, screen prompt for warning warranty void and ask for yes and no then select no and OEM will be locked. Stupid bug.
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
Hello,

Quick question. I am currently on TWRP 3.2.3-10 with a Oreo custom ROM (5.0.8 firmware).

I want to upgrade to Pie OOS 9.0.3.

I'll use TWRP 3.3.1-0 to factory reset and format data before flashing OOS.

Can you please confirm that 3.3.1-0 has fixed the encryption key issues that was present in the first versions of 3.3.*?

If yes, it's now able to handle OOS 9.0.3 keymaster?

I've read all the pages since 3.3.1-0 release but couldn't find the answer. Been to the Pie OOS firmware thread too, but still am unclear.

Thanks
[OnePlus 3 & 3T Cross Device Development] :
If you format and reencrypt data, you are good to go with 9.0.3 fw and twrp-3.3.1-0.
[OnePlus 3 & 3T Cross Device Development] -CFP-:
DELETED
[OnePlus 3 & 3T Cross Device Development] iamsuperuser:
Please help

After restoring backup my screen lock pattern is not recognized.

It says wrong pattern on the lockscreen.

I'm currently locked out of my phone.

What can I do to rectify this?

I'm using latest TWRP v.3.3.1.0 on my OnePlus 3T on Havoc-OS v2.7 ROM.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Solution with script:

https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166/post79835391#post79835391

It deletes lockscreen and fingerprint files. After this the phone is unlocked and you should be able to re-lock it by pincode fingerprint etc.
[OnePlus 3 & 3T Cross Device Development] Rodger_Rulez:
hi! use older version 3.3.0-0. Restoring without problems, with 3.3.1-0 have tha same problem.
[OnePlus 3 & 3T Cross Device Development] Paschfire:
Backup/restore of /System image, instead of the /System partition option, works fine for restoring Nandroid backups created using TWRP 3.3.1-0.
[OnePlus 3 & 3T Cross Device Development] sky321:
OTA

[MENTION=5091734]dianlujitao[/MENTION]

Are you aware of this issue?

https://xdaforums.com/showpost.php?p=80009239&postcount=2970

and the discussion around that topic and the patch

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1491#issuecomment-515051968
[OnePlus 3 & 3T Cross Device Development] :
He is: https://review.lineageos.org/c/LineageOS/android_device_lineage_sepolicy/+/244801 (second last comment)
[OnePlus 3 & 3T Cross Device Development] :
Just to keep my mind sane cause i already forgot some of it after reading an old issue arise at LOS thread. Decided to re-read this thread again.

issues:

=/< 3.2.3.0 - F2FS issue, possible failure at flashing newer rom, wrong time issue, twrp app issue, not compatible with android 10 up

3.2.3.1 - broken encryption if using format data function, wrong time issue, twrp app issue, not compatible with android 10 up

unofficial 3.2.3.10 - wrong time issue, twrp app issue, Lacks features added start from +3.3.0.0 (Ex; Support booting on locked bootloader), not compatible with android 10 up

> 3.3.0.0 - 3.3.1.1 - broken backup/restore system, broken restore from previous build backup, broken flashing certain zips (mods mostly), broken automatic OTA flashing for certain rom, not compatible with android 10 up

3.4.0.0 - broken flashing certain zips (mods mostly)

Solution:

=/< 3.2.3.0 - Upgrade to newer build

3.2.3.1 - upgrade to newer build. If encryption is already broken, do fastboot format userdata.

unofficial 3.2.3.10 - Upgrade to newer build

> 3.3.0.0 - don't backup the system, rather backup the system image. Restoring backup from previous build, flashing zips and automatic OTA failure should be solved by only downgrading to unofficial 3.2.3.10, Upgrade to newer build

3.4.0.0 - Downgrade to previous build for the flash (applicable to <pie) or edit your zip

Best build: Official 3.4.0.0

General tips applied to all version:

- You have to delete password db files after restoring a backup, or else you'll stuck with incorrect password or unable to make new one
[OnePlus 3 & 3T Cross Device Development] Dirk:
Very nice! :good:

Time issue on older builds can be fixed by running newer build once and then reverting back, if it's bothering anyone.
[OnePlus 3 & 3T Cross Device Development] imago_m:
Hey guys,

Just to be sure. Are there any known Problems/Bugs with the official twrp-3.3.1-0 version (oneplus3) which is available through the TWRP APP?

cheers,

Imago
[OnePlus 3 & 3T Cross Device Development] Paschfire:
I suggest you take some time out and search/read through this thread, if you want to get up to speed on TWRP development, including any currently known issues or bugs.
[OnePlus 3 & 3T Cross Device Development] :
Follow [MENTION=5866088]Paschfire[/MENTION] 's recommendation ... or what a mystery ... read at least the 2nd post above yours ...
[OnePlus 3 & 3T Cross Device Development] imago_m:
Thank you for your warm welcome in this thread. I already read the mentioned post. Could you point out in which way this post corresponds to my question? My question is related to version 3.3.1-0.

But thanks anyways... What a wonderful community over here...
[OnePlus 3 & 3T Cross Device Development] :
Welcome!

This post refers to the twrp version you've mentioned, indeed: ">3.3.0-0" includes version 3.3.1-0 ;)
[OnePlus 3 & 3T Cross Device Development] jamames:
Which partitions to backup?

Hey everyone, I'm creating a nandroid backup of my phone and want to make sure that I'm doing it properly. I saw on the TWRP website that all that is needed are the default selected partitions - Boot, Data, and System.

I understand that Cache is meaningless to backup, but are there any advantages or disadvantages to backing up the other partitions as well? (Recovery, System Image, EFS) Or, what am I losing by not backing these up?

Thanks!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Since we mostly use TWRP to backup the running system (the partitions that get changed by a rom) the only partitions were regularly backup and restore are boot, system, and data.

In rare cases it's necessary to take a system image backup instead of the normal, file based system backup. For example, I do it for stock OOS 9.0.5 because TWRP has troubles restoring a file based backup of the system partition.

I always take a backup of EFS when I first get my phone and put it on a safe place. It's the partition that contains the phone's imeid. If this partition gets corrupted (used to be more common in older versions of Android) you can then restore it. Note: I've never needed to do this in 7 years of using Android.

Recovery you never back up because you just re-flash TWRP.
[OnePlus 3 & 3T Cross Device Development] jamames:
Thanks for the explanation! And that's good to know about EFS. I'll keep a backup of that partition just in case.
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
How to disable the boot warning that my device is not secure anymore (is this DM-Verity?)
[OnePlus 3 & 3T Cross Device Development] :
Relock the bootloader. This will earase the data partition.
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
But my Custom Rom will remain?
[OnePlus 3 & 3T Cross Device Development] SenseSei:
https://xdaforums.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324

System remains, but all data will be obviously lost
[OnePlus 3 & 3T Cross Device Development] aiamuzz:
the feature Decrypt /data ... how does this work ... is it an option that we simple choose to decrypt /data directly from the recovery ?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The wipe>format data option will decrypt the phone. But in the process of doing so it wipes /data completely which includes /sdcard. So you need to backup you phone to an external device to avoid losing all your data, backups, etc.
[OnePlus 3 & 3T Cross Device Development] :
Decrypting is the process of making use of an encrypted partition. This is done i.e. each and every time an encrypted device is booted.

Unencrypting or removing encryption means making an encrypted partition unencrypted again: this is not possible without clearing the fde encryption footer - this always implies reformating data, and therefor data loss.
[OnePlus 3 & 3T Cross Device Development] aiamuzz:
formating /data ... this option has always been there ... but as it was reported as feature i thought it had a inbuilt option which i missed that will make an encrypted device un-encrypted ...

[MENTION=2911853]BillGoss[/MENTION] ... [MENTION=4405529]nvertigo67[/MENTION] ... i am already aware of the fact that formatting an encrypted partition will destroy all data and the partition will be in a state where it is not encrypted anymore ... but in the context of the latest devices which have forced encryption by default with no option to decrypt it in a soft way ... by question was in that light hoping it was feature in the latest TWRP that allowed us to do it in a simple way !!!
[OnePlus 3 & 3T Cross Device Development] Dirk:
Decrypt means making Encrypted data readable. Unencrypt means removing Encryption or preventing Encryption in the first place.

While you're correct about modern devices Encrypting by default, and the same should apply to the OP3/t, the trend with custom ROMs has been to not force Encrypt on these devices, with the options to do so being available in Settings. I don't know why this is the case.

The only way to remove Encryption on an Encrypted OP3/T is to Format Data. You probably know this now. Then you are Unencrypted.

Probably just telling you what you already know but just adding some clarity to the terminology part.

Edit: You're also right that decrypting Data is the bare minimum of what any Recovery should be able to do and doesn't need to be listed as a 'feature'.
[OnePlus 3 & 3T Cross Device Development] :
You are so damn right! I've been quite some times just about to enforce encryption on nlos - but I've always come to the conclusion, it's better to have the freedom of choice... I'm still thinking of it now and then. This is my motivation to not enforce encryption on nlos - other rom's devs may have other reasons.

I think mentioning "decryption" as a working feature dates back to the earliest versions of twrp (before [MENTION=5091734]dianlujitao[/MENTION] was the maintainer for op3/t builds, there has been some really ugly issues with twrp and encrypted devices. Without remebering those times, mentioning "decryption" may confuse one user or another.
[OnePlus 3 & 3T Cross Device Development] Dirk:
And it should stay that way. I wish it were the same on all devices, with the option being available in Settings if wanted.
[OnePlus 3 & 3T Cross Device Development] aiamuzz:
it is pretty mad out there ... the tutorials and all ... on disabling encryption ...

[MENTION=4405529]nvertigo67[/MENTION] ... you are right ... the device manufacturers could ship devices with the default being 'encryption enabled out of the box ... but they could have also provided a switch to disable it given a users choice ... I seriously don't understand the reason why they didn't provide that switch(choice to user)

as OP has listed decrypt as a feature ... i just posted here in the hope that there could be simple way to do it ... turns out it isn't ... a patched boot image is needed ... again Magisk also works in a patched boot image way ... so for a noob like me ... its too many concepts to wrap my head around ... fragmented information with complex noob tutorials sometimes confuse more than help ...

and some googly's thrown from my device confused me all the more ... for instance

'fastboot format userdata' ... surprisingly did not clear the pattern lock i had on my device ... i tried more than once ... then i finally attempted 'fastboot erase userdata' ... only after this the pattern lock was no longer showing on twrp ... then i flashed the patched boot image and the fstab zip file from one of the threads here ... and finally when i booted ... my device for the first time was free from forced encryption ... after that i just had to restore the previously backed /data partition to carry on from where i left ...

just flashed multirom and its specific custom twrp (a couple of version low from the TWRP version that was already there) ... and device is good to go for flashing without touching the native stock OOS on my device !!!
[OnePlus 3 & 3T Cross Device Development] bwagner.ash88@gmail.com:
I just updated the oos 9.0.6 and root with magisk. When I went to make a nanoid back I noticed something that I have never seen before in all the back ups I have made. Instead of just boot, system, data checked recovery and I think something else was checked. So my question is why
[OnePlus 3 & 3T Cross Device Development] Paschfire:
What? Care to explain what else was checked? "I think something else was checked" simply doesn't explain anything.
[OnePlus 3 & 3T Cross Device Development] bwagner.ash88@gmail.com:
This is what it backed up
[OnePlus 3 & 3T Cross Device Development] :
It shows the partition you've checked when backingup. cache is not necesarry, it's rebuild by the rom if empty. recovery can easlily be reflashed. boot, system and data is the bare minimum for restoring a previous setup just from your backup. If you have the used rom, the used gapps package and all other boot or system altering packages (i.e. magisk, sec pactch date zip) at hand, you can restore a previous setup just with a data backup.

Always remember: /data/media isn't backuped. If you want to format data backup /sdcard additinally to an external medium (including your nandroids, of course).

It's important to have a backup of the efs partition! It's the place where the imei is stored, which is unique to your device and can't be restored by any unbrick tool! A dd backup of the persist partition (manually - not available through twrp menus) can be handy in some situations, too. The persist partition holds (not only) your devices hardware mac address and hardware bt address.

Read this thread to learn, why it's usefull to backup system as image (instead of the file based backup, you've choosen to do when starting your backup).
[OnePlus 3 & 3T Cross Device Development] helderfp:
no changelog available, maybe [MENTION=5091734]dianlujitao[/MENTION] can give some changelog
[OnePlus 3 & 3T Cross Device Development] OSheden:
Thanks for the help but it's still weird to get those errors, isn't it? I've never seen such errors with previous versions of TWRP.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Just ignore it, these errors show only after directly switching from blu_spark to official TWRP, nothing serious. After using backup/restore once the errors are gone...
[OnePlus 3 & 3T Cross Device Development] osrox:
Hi,

I was earlier using Blu twrp with RR-Nougat on my OP3.

Then in order to flash RR-Oreo, i flashed New Official TWRP, which gave Encryption password error.

So i again switched back to blu twrp.

The encryption password worked fine.

So i first took a nandroid backup of RR-Nougat & then clean flashed RR-Oreo.

Now when i try to boot in Recovery, blu twrp gives encryption error.

I can successfully boot to system (RR-Oreo),

So i tried Flashing Official TWRP from Flashify app.

but again boot to Official twrp, gives encryption error.

I can boot to system even now.

I just checked Disk Info app, it says all partitions are ext4.

What to do, to fix this encryption password error ?
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Wich firmware?

Using TWRP 3.2.1 from 2018?
[OnePlus 3 & 3T Cross Device Development] henningsieh:
Hey, can you give me a hint, where to disable encryption? And what does it mean in detail?

Is /system-partition fully decrypted then, or do we talk about /data? What are the consequences/differences?

Thanks and sorry for off topic! :)
[OnePlus 3 & 3T Cross Device Development] osrox:
Latest OB firmware.

tried Latest TWRP from dianlujitao.

Phone running RR-Oreo at present perfectly.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Did you flash a firmware only package? I updated full OOS before switching to latest official TWRP and flashing RR6, no issues there, or on Omni, or whatever I tried, I know that setting up a boot password should done on OOS, keep it exactly the same on custom ROM as changing it on anything else than OOS might break the encryption key which leads to TWRP decryption bug...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=5091734]dianlujitao[/MENTION] I think there's a bug in TWRP which I've come across in my Note 3 as well as in this latest version in my OnePlus 3T.

The bug is that a restore of a backup using open recovery script (ORS) always fails because TWRP says that /system is mounted read-only.

However, I've allowed /system to be writable (as seen in the screenshot) and I can manually restore /system without problems.

Note that if I tell TWRP to keep /system read-only then a manual restore will also fail - as expected.

I've even tried to mount/system as writable using a mount command, which runs successfully, yet the restore process still fails.

It seems to me that if I've previously told TWRP to make/system writable, then it shouldn't start up with /system in read-only mode. Here are a couple of lines (140-1) from the logs that seem to indicated that TWRP considers /system to be ro:

/system | /dev/block/sde20 | Size: 2913MB Used: 1383MB Free: 1529MB Backup Size: 1383MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only

Is there a way to run a restore process in ORS that works? Or is it possible to fix TWRP to start with /system as writable if it's been previously allowed?

ORS:

cmd mount -w /system
restore /sdcard/TWRP/BACKUPS/1ebc8e1b/180214-140907_la-15.1-180213-mc SM

Attached logs for manual and ORS restore.
[OnePlus 3 & 3T Cross Device Development] osrox:
i had flashed (Firmware+Modem) > RR6 > Gapps.

Also i had set the Encryption Password in OOS (Nougat) while i had originally bought in 2016 & set the phone up.

Password has been the same since then..

It took me a lot of time, in adding multiple Google accounts on RR6 & installing 220+ apps from Titanium backup Pro & setting up configuration and all.

Since i can't access TWRP even once, i can't even take a nandroid backup of RR6.

otherwise, I would have copied 40GB Internal storage to PC, & then Full formatting the phone, & installing Latest OOS beta rom, then wiping system+data then Restored the RR6 nandroid backup (which i can't do) & copying back 40GB internal storage from PC.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
There sometimes is a difference between flashing the firmware & modem packages and full OOS, that's the only obvious difference I see, I flashed full OB22 and had no issues whatsoever...

You can still backup to G-drive or another cloud service via titanium backup, then format and restore from cloud... You said system still boots, right?
[OnePlus 3 & 3T Cross Device Development] kamilmirza:
how there should be a difference between firmware-only or full firmware?

because it shouldn't, right? just curious, Sensei
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Well, technically there shouldn't be a difference but as you might have experienced yourself in the past this firmware only packages are made by humans with a likelihood of human errors, one infamous package rendered lots of devices unbootable (because newly added partitions were left out or something), recently similar stuff happened again with the firmware linked at NOS thread,

I also remember in the beginning Omni8 had VoLTE only working with flashing full OOS not with the firmware package alone..

There shouldn't but sometimes there is a difference and it wouldn't even be too far fetched to assume that there's something missing with the encryption key, etc. in certain packages but with this topic you're the Pro, all I say is flashing full OOS is by far the most reliable way to update the firmware...
[OnePlus 3 & 3T Cross Device Development] kamilmirza:
LOL yes I remember ?

yes, this can happen

not a bit, honestly

yup its far better practice, IMO too

thank you, Sensei! :good::highfive:
[OnePlus 3 & 3T Cross Device Development] theCroh:
I'm on RR 5.8.5 and official TWRP 3.0.4-1. I thought I'd upgrade to the newest TWRP before upgrading to an Oreo ROM but with official TWRP 3.2.1-0 I get the encryption error. If I flash the older TWRP back, everything works as expected. I'm quite baffled that the older TWRP is able to decrypt data but the newer isn't. Might I be doing something wrong here?
[OnePlus 3 & 3T Cross Device Development] osrox:
System still boots,

& luckily TWRP started working now.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
How that? Started working?

Incredible lucky then :good: just think about backing up to G-drive via titanium backup, this could save you a lot of trouble...
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I'm afraid it's a TWRP bug, backup/restore via ORS is seldom used so TWRP developers probably don't take good care of that.
[OnePlus 3 & 3T Cross Device Development] bilal132:
I'm currently facing an annoying issue during flashing latest stock ROM OS5.0.1 through latest twrp. Whenever i flash stock Oreo ROM and try to reboot my cell phone it start vibrating for 5 sec and then turn off and when i try to turn it on through power key its only shows blue light nothing else display remains black But it can flash nougat ROM perfectly. Can someone gives me solution to this problem? My cell ohone model is Oneplus A3010. Sorry for my bad English. :(
[OnePlus 3 & 3T Cross Device Development] :
Format (not wipe - format) data.
[OnePlus 3 & 3T Cross Device Development] osrox:
This vibration thing, happened with my OP3 too, while flashing OB31 rom.