yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Primokorn:
This morning I was on Tugapower rom:

• TWRP 3.0.4-0. No password required.

• a PIN code was required to unlock the device (to be entered after the sim card code). No boot PIN.

• Everything worked flawlessly but... I wanted to define a boot PIN...

So I set a boot PIN from Settings > Security. After a reboot:

• Password required into TWRP to access data

• Same ROM, same TWRP version

• No boot PIN. Unable to get the sim card code. I immediately have the 'Decryption unsuccessful' message.

At launch time I backed up my data on a PC.

From the 'Decryption unsuccessful' screen, I hit 'Reset' and I'm back into TWRP to format data. Now my internal storage is empty and I'll put my data back.

At the end, I don't understand why setting a boot PIN corrupts the data... Thanks for helping.
[OnePlus 3 & 3T Cross Device Development] Kris Chen:
I have problem here and wanna get help from forum: My ROM is CM13 built by Sultanxda.

After flashing TWRP 3.0.4-0, I backup all ROM without issue but I cannot restore backup ROM.

The problem: It finish the restore process but my phone suffered from error " com.android.phone ... " whatever I tap it off or not. The error keeps showing up. Why?

Is it ROM's problem or ... Can someone give me a hint ?
[OnePlus 3 & 3T Cross Device Development] jblanko6:
How do I check if my data is f2fs or EXT4?

Thanks
[OnePlus 3 & 3T Cross Device Development] Antsu:
[MENTION=3044422]mad-murdock[/MENTION] So is this the reason for guide to remove pins and fingerprints from your current rom if you are going to nandroid backup? Or is this just related to roms encryption, and formatting only resets the keys?
[OnePlus 3 & 3T Cross Device Development] Primokorn:
TWRP > Wipe > Advanced Wipe > Check Data > Repair or Change File System > Read the File system line in blue. Return to Home.
[OnePlus 3 & 3T Cross Device Development] 2x4:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
this sounds like an issue in your rom. you should report there, so in the future users trying the same (very normal) thing, they dont break their data. I am rather sure its not a TWRP issue.

---------- Post added at 04:31 PM ---------- Previous post was at 04:26 PM ----------

enter terminal (either in twrp or system) and enter "mount". search for the line containing "on /data" and you see it.

wait, there is also some android app... lemme see... https://play.google.com/store/apps/details?id=me.kuder.diskinfo - it also shows you in a more userfriendly way. still, a simple "mount" does it.

---------- Post added at 04:37 PM ---------- Previous post was at 04:31 PM ----------

i have done many nandroid backups and restores, while switching from f2fs to ext4 and also while switching from OOS to LaOS. I never removed fingerprints or PIN.

The only issue that CAN happen (and happened a few times to me) is that your lockscreen password - NOT your encryption password, NOT your fingerprints - does not work anymore. Why and how to solve this is easily explained here.

Note: that is also the reason you should always be encrypted. If you are not encrypted, anyone can remove your lockscreen password on an unlocked phone.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Deleting only the file /data/system/locksettings.db always helped me.

Here is a flashable ZIP that I have made:
[OnePlus 3 & 3T Cross Device Development] stephlal:
3.0.4-0 bootloop solution

After unlocking and rooting my phone for the first time yesterday I kept getting stuck in an endless TWRP bootloop after flashing a ROM / Gapps.

Solution, hold down the power button for 20s to power down. Wait 20s, power button to turn it on, success.

Didn't matter what I tried or what I flashed, kept getting stuck in a TWRP bootloop.

Hardboot got me out of TWRP.
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
I only know that issue when trying to OTA a modified OOS ROM. The way out then is to call "wipe_misc" in TWRP terminal or executing from PC via "adb shell wipe_misc".

But maybe holding down the power button 20 seconds does the same. Never heard of it. Interesting.
[OnePlus 3 & 3T Cross Device Development] no.one.writeme:
[MENTION=5672995]jcadduono[/MENTION],

So from now on twrp-3.0.4-0-oneplus3.img is a unified recovery for the op3 and op3t and it is safe for me to update my recovery by "fastboot flash recovery twrp-3.0.4-0-oneplus3.img", right?

Best regards,

Luis.
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Yes, exactly.
[OnePlus 3 & 3T Cross Device Development] Chuck Bartowski:
Same thing happened to me.
[OnePlus 3 & 3T Cross Device Development] CyberCROC:
I updated from 02 to 03 and consequently got the DM error. I updated according to the procedure but can't get rid of the DM error. Anything I missed?
[OnePlus 3 & 3T Cross Device Development] Snappiestjack:
I'm using 3.0.3 (3T) without any issue. Still recommend updating seeing as "notice 3" is possible?
[OnePlus 3 & 3T Cross Device Development] SpasilliumNexus:
https://xdaforums.com/showpost.php?p=70698410&postcount=112
[OnePlus 3 & 3T Cross Device Development] the_rooter:
Try this. Worked for me
[OnePlus 3 & 3T Cross Device Development] Ashtrix:
"Sigh" this F2Fs introduced super complication due to the Encryption / Backport / Updated / ROM crypto / Read Speed / SuperSU when paired with OP3/T - All for what ?!

Damn, I wish google had used this f2fs long back along with the sdcardfs, Hope the v8 brings this across the whole board. So far I didn't see any issues with ext4 plus I guess f2fs will take more space on /system.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
I had the same issue. After a quick conversation with [MENTION=5672995]jcadduono[/MENTION] on IRC, I tried this tip and it worked.

OP3T | Flashing a custom ROM after a format data | TWRP 3.0.4-0
[OnePlus 3 & 3T Cross Device Development] Clark789:
Without any data issues, i.e. you didn't loose your data?

Regards

Clark
[OnePlus 3 & 3T Cross Device Development] Xennet:
That confirms official twro 3.1.0.0 has problems but bluspark 3.1.0.0 has no problems.

Just try flashing t latest official update TWRP 3.1.0-1 and get back if u may please to see whether t update corrected t issue or not... Take a backup before u do ..in case it wipes..
[OnePlus 3 & 3T Cross Device Development] Joloxx9:
Ok will try in next 15 mins

3.1.0.1 works fine
[OnePlus 3 & 3T Cross Device Development] Aldideos:
3.0.1-1 is ok but OTG doesn't work
[OnePlus 3 & 3T Cross Device Development] Xennet:
So t issue of accidental wiping is corrected...

So can we decide its safe to use it...

[MENTION=4719790]droidextra[/MENTION] do confirm

---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------

Ok in t sense...Please do post t details of ROM nd phone model...

OTG doesn't work...

Can anyone else confirm dis... Unfortunately I dont have an OTG Storage...
[OnePlus 3 & 3T Cross Device Development] xpissio:
Yesterday I flashed 3.1.0-0, no problems, and now 3.1.0-1, no problems.

OnePlus 3T, Dirty Unicorns 11.2.
[OnePlus 3 & 3T Cross Device Development] Midomad:
Same here both versions work fine,OP3T on beta 3.
[OnePlus 3 & 3T Cross Device Development] Xennet:
Any problems with OTG...
[OnePlus 3 & 3T Cross Device Development] Aldideos:
Oos OB3 OP3T

With 3.1.0 OTG works fine, with 3.1.0-1 not. However with 3.1.0 backuping data doesn't work, it stuck in 98% of files idem with 3.1.0-1 (with blu spark version it works, but if I use a password not, in the official neither with password nor without.
[OnePlus 3 & 3T Cross Device Development] Xennet:
There is no problem at all backing up on official Twrp 3.1.0-1.

I in fact backed up everything including efs using no encryption and with encryption. No problem at all...

1st screenshot without encryption

2nd with encryption

U shud check once more...

Anyone else probkem with OTG???
[OnePlus 3 & 3T Cross Device Development] Aldideos:
I don't know why but I have no success with thenew two official recovery. I also tryed to use adb backup via twrp and i hadthe same problem, at some point it stucks and I can't continue.
[OnePlus 3 & 3T Cross Device Development] muschiu35bv:
Hello Guys! For oneplus 3 twrp 3.1.0-1 is not released yet or the twrp for oneplus 3T works also with oneplus 3?Thank You!
[OnePlus 3 & 3T Cross Device Development] aadityarulez:
Do not flash twrp for 3T on 3.
[OnePlus 3 & 3T Cross Device Development] muschiu35bv:
Ok.That mean latest twrp is 3.0.4-1 for the moment?
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
Not for 3 it's 3.1.0 but it has issues
[OnePlus 3 & 3T Cross Device Development] SpasilliumNexus:
OTG does not work with 3.1.0-1 on 3T.
[OnePlus 3 & 3T Cross Device Development] muschiu35bv:
Yes i know that official twrp latest release is not working properly because i installed on my device and when i boot the phone the all data was lost.This happen only when i flash custom rom but with oxygen os there is no problem.
[OnePlus 3 & 3T Cross Device Development] Carlos_Llorca:
Can I flash the dm-verity file if I have already flash a ROM (FreedomOS) and done the root?
[OnePlus 3 & 3T Cross Device Development] bhavstech:
i am facing slow boot after searching i realised its due to f2fs so is f2fs default?

1. how do i know if my partition is f2fs or not

2. i recently switched to oos from aicp so i want to know what is the default partition and what is required for custom roms.

(basically i want to know is f2fs default(i may have changed it ACCIDENTAL?!) and will i need to change it in future for custom roms?)

and any lead on how to change it to ext4 (if required)

thanks
[OnePlus 3 & 3T Cross Device Development] acultr:
flashed over multirom twrp all it's okay.

OP3T Ob3 bluspark kernel

no issues.
[OnePlus 3 & 3T Cross Device Development] aadityarulez:
Use diskInfo from play store. As to your other question, flashing roms don't change the partition.
[OnePlus 3 & 3T Cross Device Development] veroby:
Just a quick question and thx in advance. Do i need to make sure security is set to none before making a backup. Or does this not matter. thx
[OnePlus 3 & 3T Cross Device Development] Joern85:
op 3t with official RR 0903 build

Please help me, I've got a strange issue:

I flashed twrp-3.1.0-1-oneplus3t.img took a backup an restored an older one. My storage is encrypted, so I got to enter a pin while booting. After the boot process is finished and after i entered the pin to unlock my sim I'm asked to enter my pin again. I'm entering the correct one (it's the same to decrypt the storage in twrp and while booting) but my phone isn't accepting it. I tried different backups but it's always the same. My phone won't accept my pin. Even with the backup which i made with twrp-3.1.0-1 it's not accepting it.

I flashed the 3.0.4-1 version and restored a backup made with this version, same problem. I tried a dirty flash of the rom, but still no luck I'm locked out of my device :( Any advice what I could do? I'd like to avoid a clean install, as i did it 2 days ago ;)
[OnePlus 3 & 3T Cross Device Development] timobayl:
In TWRP delete data/system/locksettings.db

This is a long know problem.
[OnePlus 3 & 3T Cross Device Development] veroby:
As you are trying to restore a two day old backup id just clean wipe and flash another rom. At least you will have a working phone while you figure out whats gone wrong with your backups.
[OnePlus 3 & 3T Cross Device Development] harsh2193:
What do you mean by accidental wiping?
[OnePlus 3 & 3T Cross Device Development] Joern85:
You're my hero! It worked! Thank you! :)
[OnePlus 3 & 3T Cross Device Development] timobayl:
Everytime you flash a other rom and after that you restore a Nandroid Backup, this problem shows up.

The best is to delete pin/fingerprint befor do a Nandroid.
[OnePlus 3 & 3T Cross Device Development] Xennet:
Several posts in this thread mentioned dat their data was wiped off after flashing twrp latest version...
[OnePlus 3 & 3T Cross Device Development] harsh2193:
Yea, that happened to me too, on multiple versions of TWRP, including 3.0.4-1.
[OnePlus 3 & 3T Cross Device Development] ivano949:
OP3T 64gb

Oos 4.0.3

Ext4 data partition encrypted

Elemental kernel

Tried both TWRP 3.1.0-0 and 3.1.0-1

No loss of data or wipe

Both working with my usb OTG

Tapastalking
[OnePlus 3 & 3T Cross Device Development] the_rooter:
If people are going to report issues they need to get logs else it didn't happen. Ask these people are claiming, but not doing their part
[OnePlus 3 & 3T Cross Device Development] papzi57:
Where did this TWRP theme for you? How do I set this up?
[OnePlus 3 & 3T Cross Device Development] Aldideos:
Fat32 or exfat(fat64)?
[OnePlus 3 & 3T Cross Device Development] Midomad:
https://xdaforums.com/showthread.php?t=2915584
[OnePlus 3 & 3T Cross Device Development] evertking:
I just had this happen to me and flashed back to the previous build and all is good. I just was in recovery and wiped cache and it wiped my whole phone!!! Thought I done something wrong and set it up and done it again!! Also both times I lost data and phone acted like I didn't have a sims card.

But yes it's wiping the whole phone (not internal, thank God!)
[OnePlus 3 & 3T Cross Device Development] MrMeeseeks:
F2FS is default on the data partition only. Basically, if you haven't changed it in TWRP then it is F2FS. If you want to change it to ext4 then go into TWRP/Advanced Wipe/Change/repair filesytem. Then select the data partition and change to ext4.

Note: this WILL WIPE YOUR DATA, so back up anything important.
[OnePlus 3 & 3T Cross Device Development] flotsch1:
wholy ****, i updated twrp, too, and it wiped the phone. i should have read this thread first. thanks god i had a full nandroid from yesterday. due to the fact that i am a beginner, just one question:

i picked everything when making the nandroid. is there anything that is not covered with the nandroid and could possibly be wiped by flashing twrp 3.1.0-0? i had a quick look at the phone and everythings seems to be fine.

and :

i updated twrp because i am not able to update lineageos to the newest version. i get error 7 and thought that the new twrp would solve the issue. i alredy flashed oxygen 4.0.3 before i did the last update of lineageos, because i had the same issue with error 7, so i have new firmware/modem. why do i get error 7 again?

thanks, flotsch1
[OnePlus 3 & 3T Cross Device Development] nadejo:
Only use the recommended twrp given in the op. I dont know who thought it was a good idea to release the new twrp anyways. Now we got bunch of wiped phones, people blaming filesystems and multiple modded twrp versions flying around once again. Before releasing unstable twrp they should keep it between skilled dev members and make it stable first.

I dont think anyone who wiped his phone doing this might will make use of the adb backup function after all. Which is the only new feature. The other feature is for pixel phones only.
[OnePlus 3 & 3T Cross Device Development] the_rooter:
it is quite stable...again those having the issues where are the logs? none. I havent seen one posted. I am currently on 3.1.0-1 and guess what no wipe and runs perfect. i am f2fs encrpyted. Show the proof of a wiped phone.....everywhere i see is omg my phone got wiped. No logs no proof it didnt happen, and those of us that flashed twrp 3.1.0-1 having no issues are using our phones because the onces that are working know if something is to go wrong that there is the proper way to report it. Have a great night :)
[OnePlus 3 & 3T Cross Device Development] evertking:
Really... This place
[OnePlus 3 & 3T Cross Device Development] dmoses1969:
Is there any way possible to get rid of the password requirement "To start Android enter your password" when I reboot to twrp and also everytime I reboot my phone without having to wipe my device and start all over? Somewhere along the way I set a password, "thank God I know the password" but it's annoying to have to enter it everytime I reboot or reboot to recovery.

Thanks
[OnePlus 3 & 3T Cross Device Development] dmoses1969:
I've tried that, and just tried it again. That doesn't work. This is different. It's not the lock screen pin, it actually happens in the middle of the boot process. Phone starts the boot animation for a few seconds and then this screen shows up. I enter my password and then the boot animation continues until the phone starts. Then I have to put in my pin/pattern/ or whatever I have set for lock screen.
[OnePlus 3 & 3T Cross Device Development] the_rooter:
cant u just remove the lock screen pin and change it to just swipe? do that reboot and then reapply so that its just for the lock screen and not reboot
[OnePlus 3 & 3T Cross Device Development] dmoses1969:
Removed pattern lock and saved fingerprints. Set lock screen to swipe. Rebooted phone, was asked for password to start Android. Went back into settings and set my pattern and selected no for password after reboot. Restarted my phone again and was asked for password to Start Android. I think it is something with encryption. Not sure. It's a annoying though, even though it is just a password. Just not sure when/how I turned that on.
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
The absence of logs doesn't mean the event didn't exist. Your logic is non sense.

There is a problem with op3 ( you seem to have a 3t) with encrypted f2fs data partitions on 3.1.0 version (you use another version). There is an alternative TWRP with modifications in f2fs librairies and driver versions that works flawlessly. So there is a solution, but besides your tight vision of the scene, what is unbelievable is the total absence of reaction of OP.

And clearly knowing all issues with f2fs of the 3.0.4 official TWRP I can't understand the update process that seems to be relatively blind.
[OnePlus 3 & 3T Cross Device Development] the_rooter:
Read the very first post ......He says get logs. So yes unless there is no logs there is no proof. Far from nonesence
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
Logs to have clues to a solution. The fact, the bug, exists independently from the log (you questioned the existence of the wiping bug).

And the solution exists. I personally don't care I use eng.stk versions but it's a pity to see the management of the situation, a thread without pilot and people losing their data.
[OnePlus 3 & 3T Cross Device Development] Guihardrock:
Enter in twrp and swipe to wipe factory reset, i had also that problem it'sto protect your data if someone steal your phone and want to flash a ROM but want keep your data, it can be useful in that case if not its a pain in the ass. If that doesn't work you will have to wipe the internal memory just make a backup in your pc while you are in twrp
[OnePlus 3 & 3T Cross Device Development] foxsprout:
And some users taking control of the thread to conclude that there is no issue at all because their devices not affected.
[OnePlus 3 & 3T Cross Device Development] ivano949:
Fat32

Tapastalking
[OnePlus 3 & 3T Cross Device Development] mantff:
Try going to settings and set a pin (not pattern) to lock screen. When you do it, you'll are asked if that pin is valid for booting system; say yes.

Then, when you are in the screen of your screenshot​, that pin will be valid.

Tell me if this works.

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Anybody owning a 3t and hasn't updated to open beta or LineageOS, ie only uses oos stable, please Screenshot your baseband version in the about phone
[OnePlus 3 & 3T Cross Device Development] foxsprout:
Here
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Had reverted back to stable oos when r13 fk was released. Seems like baseband are the same. Twrp 3.1.0-1 works fine on this firmware
[OnePlus 3 & 3T Cross Device Development] Aldideos:
Try exfat, with fat32 it works, i can confirm... But exfat not
[OnePlus 3 & 3T Cross Device Development] tk8lm6:
I don't think TWRP uses the firmware.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
People with different firmwares especially from linos 7.1.1 might be facing the problems, that's what I want to rule out.
[OnePlus 3 & 3T Cross Device Development] nitz2889:
I am currently on lineageos 0903 build with OB12 firmware and twrp 3.0.4.1, device op3.

I went through last few pages and there seems a lot of confusion regarding twrp 3.1.

Can someone please let me know the current status and phone behavior after flashing latest 3.1(fastboot/twrp) on op3
[OnePlus 3 & 3T Cross Device Development] the_rooter:
works fine where with no wipe.
[OnePlus 3 & 3T Cross Device Development] evertking:
I'm on beta 12, OnePlus 3 and flashed the latest TWRP. On boot up my phone was wiped and sim card not recognized.
[OnePlus 3 & 3T Cross Device Development] Uumas:
I have a feeling the problem is the new Open Beta firmware
[OnePlus 3 & 3T Cross Device Development] beardymarrow:
Oneplus 3t 128gb, on ob3. Encrypted f2fs data partition.

Flashed twrp-3.1.0-1-oneplus3t.img through twrp app and had no problem at all.

Flashed back to twrp-3.0.3-1-oneplus3t.img and then flashed twrp-3.1.0-1-oneplus3t.img through twrp recovery. Still no problems.
[OnePlus 3 & 3T Cross Device Development] Mr_Comple:
I'm at OOS 4.0.3 and I'm using the latest twrp 3.0.4.1

Now that there is a newer version Should I update or not?
[OnePlus 3 & 3T Cross Device Development] lapapunk:
You are the brave man. Can't even imagine, how is it, to lose all yours data.. (I'm already losed my data. But not so important data. And the main reason was in "encryption"). So after this I keep my data unencrypted.

And thanks about twrp feedback.
[OnePlus 3 & 3T Cross Device Development] Xennet:
As mentioned before...

I have​ OP3T 128GB OOS 4.0.3

Data f2fs encrypted

Rest all ext4

OFFICIAL TWRP 3.1.0-1 HAVE NO PROBLEMS IN BACKING UP, OTG OR ANY PROBLEMS LIKE WIPES

Yesterday onwards we are trying to find the​ root cause of the problem​. From the​ modded bluspark twrp it was somewhat apparent that some files were actually missing in the official twrp 3.1.0.0 that was needed for the​ reading of f2fs drives.

4 questions..

1. Anyone ever had a wipe issue with the bluspark twrp 3.1.0.0. (To confirm whether the​ issue was corrected by modding by bluspark which means the​ official twrp 3.1.0.0 obviously is buggy....)

2. Anyone ever had a wipe with ext4 data on official twrp 3.1.0.0. (To confirm whether it was a f2fs read write error.)

3. Anyone ever had a wipe issue with 3.1.0-1.(To confirm whether the issue was rectified in the build 3.1.0-1

4.Anyone ever had a wipe issue in official OOS 4.0.3. NOT THE BETA..(To confirm whether it was custom os related)

I think the above questions will give the​ answer...Do post your comments...

What I am still amazed is WHY THE OP IS STILL SILENT ABOUT THE ISSUE.....
[OnePlus 3 & 3T Cross Device Development] fonix232:
EVERYONE going with unlocked bootloader and/or other tinkering should back their stuff up. Hell, I'd even shorten it to "EVERYONE should back their stuff up". Everything that is important to you should be duplicated and stored safely. I for one almost exclusively care about stuff in my Google Drive/OneDrive/Dropbox storage (mainly photos, some documents, scanned things, e.g. ID, passport, et cetera), and those are always synced, and backed up multiple levels.
[OnePlus 3 & 3T Cross Device Development] Flint2:
Can you confirm TWRP version (3.1.0-1 or 3.1.0 ?)

Please confirm if you are using F2FS or ext4, and what is flashed on system besides Beta 12.
[OnePlus 3 & 3T Cross Device Development] beardymarrow:
Hi, it would be easier for those for whom English is a second language if we refrained from t dat ur etc. and used da full wordz :) as the shorthand makes it difficult to read. Cheers.
[OnePlus 3 & 3T Cross Device Development] EdHicks:
+1

Even when not flashing I update my backup at least once a week. When flashing, I back up right before I wipe and clean flash. I also highly recommend clean flashing only. I have far fewer problems when I clean flash.
[OnePlus 3 & 3T Cross Device Development] Xennet:
Edited the post... Sorry lol always had a habit of fast typing...;)