yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Yes, from security menu inside the ROM. It says it takes some hours, but from my personal experience, it only takes about 5 Minutes. That is with a data partition about half full.

Also make a nandroid backup of your rom followed by copying everything to your PC before encrypting. Especially when on a custom ROM. Encrypting an unencrypted file system might be the least tested feature. For me it failed on a custom ROM. If it fails, you lose everything. See poor [MENTION=2970269]aehlayel[/MENTION] here.

(If you want to save some time use the fast way from the link in my signature.)

Again, you don't lose anything - you already lost it. Yes, all your media and all your applications. The only thing you can do is format, so your phone is usable again. The losing - aka destroying your data partition due to a forced reset - already happend.

You can do it on the warning screen (I guess) or under wipe -> advanced wipe in TWRP.

As I always say: Don't go unencrypted. Had you been encrypted, things would have gone smoothly.
[OnePlus 3 & 3T Cross Device Development] aehlayel:
So let let me know if I'm mistaken. I was unencrypted. The upgrade forced an encryption which prolonged the boot cycle, so I thought my phone had hung. I force restarted it. That aborted the encryption and got us to the "Encryption unsuccessful screen, which killed any data on the phone?

So, your recommendation is to remain encrypted. Would that pose any issue with being rooted on the OP3T? Upgrades? Anything else worth noting here before I go on the quest to restoring my phone? I've been an android user since the SGS1 days - and this is probably my 6th phone, never have I f'd up a phone like this; I've always been rooting and tinkering around... :S
[OnePlus 3 & 3T Cross Device Development] habylab:
Hmm, weird issue here. Using this, I keep getting an error when trying to flash the full official OOS zip to do a dirty flash. Error 7. Haven't had this before.

What am I doing wrong? The zip is correct, I checked the md5.
[OnePlus 3 & 3T Cross Device Development] aehlayel:
Wipe cache and dalvik?
[OnePlus 3 & 3T Cross Device Development] habylab:
Tried that, still won't allow me to flash sadly.
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Are you coming from an older version than 4.0.2? If so, try flashing 4.0.2 first, then 4.0.3.

You can also try to wipe system partition before installing. Even though, full ROM shouldn't trigger error 7 on modified system partitions, its worth a try.
[OnePlus 3 & 3T Cross Device Development] dmoses1969:
I am on LineageOS and have TWRP v3.0.4-0 and have tried v3.0.4-1 and when trying to create a backup and keep getting an error. (createTarFork() process ended with ERROR:255). I looked through my recovery log and at the bottom of the log and under Backing up system.....

Error opening: '/system/addon.d' (Not a directory)

I:Error in Generate_TarList!

Error creating backup.

Any ideas?

Thanks

EDIT: Dirty flashed my Rom and Gapps and backup is working again. Not sure what happened.
[OnePlus 3 & 3T Cross Device Development] DroidJay123:
So to confirm....are there currently issues with OOS 4.0.3 and TWRP 3.0.4-1? I have read some people posts about having issues? I am currently on stock OOS 4.0.3 with stock recovery. Is it safe to install TWRP 3.0.4-1 if running stock 4.0.3? Why have I read about possibly being asked for a password during the initial setup of TWRP and what you would enter of you have no such password?

To summarize, I should:

Install 3.0.4-1 via fastboot

Reboot directly into Recovery

Swipe to allow system modifications (why would one leave read only?)

After swiping to allow mods, flash either SuperSU or dm-verity zip

Reboot system

Are there also people experiencing mounting internal storage problems? When does this occur?

Thanks all
[OnePlus 3 & 3T Cross Device Development] kessaras:
just flash it in fastboot. if you want to boot to recovery you will need your encryption pass . that's all. twrp is useful if you gonna flash a custom kernel or rom or change f2fs to ext4.

if you aren't gonna make any changes and you will to remain stock forever then don't flash it
[OnePlus 3 & 3T Cross Device Development] habylab:
I actually had to completely clean install 4.0.3. That's the weird thing. Anyway, I fixed it by flashing the latest modem and firmware.
[OnePlus 3 & 3T Cross Device Development] francise:
i'm on oos OB11 stock recovery i wan't to move to exp rom, should i must download the OB11 or oos 4.0.3 will works too use this twrp? thanks for your advice :)
[OnePlus 3 & 3T Cross Device Development] _DarkKnight_:
Waiting 5-10 minutes on twrp splash screen
[OnePlus 3 & 3T Cross Device Development] inOvator71:
How I can get rid of dm-verity when I have unlocked bootloader and I have installed custom rom and latest twrp?
[OnePlus 3 & 3T Cross Device Development] the_rooter:
Follow op.
[OnePlus 3 & 3T Cross Device Development] sajed98:
Hi guys, I had some questions, can you please help me?

I'm now on OOS 4.0.3, rooted and TWRP this version. TWRP takes a long time to boot up. I'm planning to install Validus. Now, Validus has magisk built in.

My question is, if I flash the forced encryption disabler zip and then flash the ROM, everything will be fine right? TWRP won't take so much time to boot anymore? Or can I just format the data partition (not internal storage) and TWRP will become fast? I'm confused, please help me.
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
The slow booting into twrp is caused by the file system most likely. F2FS takes a while to get into twrp, if you change to ext4 it will wipe ALL internal storage
[OnePlus 3 & 3T Cross Device Development] sajed98:
On the OP, it says data partition, that's why I was confused. So to fix this, I should just flash the DM verity zip? And that's it?
[OnePlus 3 & 3T Cross Device Development] DroidJay123:
The only pass code I ever had was to get into the phone while using the fingerprint unlock. Is this the same for the encryption pass code? If I have already placed supersu on internal storage will I be able to select it after swiping to allow system modifications? I have read posts about needing to transfer via MTP or is that only if you didn't already place file on internal storage?

Thanks all!
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
Where do you think internal storage is located? You can't format a partition and spare a folder...
[OnePlus 3 & 3T Cross Device Development] sajed98:
Data partition usually means the partition where system keeps its data. I thought you have to just format that.
[OnePlus 3 & 3T Cross Device Development] kessaras:
can't go back and remember now. its the same pass that OOS asks you if you want to use while you are booting and since you only have 1 pass set, then i don't see the problem. Also its not like you won't get a 2nd chance. The phone won't blow up at wrong pass.

Just flash it. Thats all. latest doesn't have any issue.
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
You should read again about Android partitions.

/data is one of the main partitions where are located user installed applications and their data, some system settings effectively, and what is called sdcard, which is in fact a folder of /data mounted as a virtual disk.

You can't format /data without formatting sdcard.
[OnePlus 3 & 3T Cross Device Development] sajed98:
In TWRP, if I wipe data, it doesn't wipe internal storage.
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
Wiping isn't formatting, it's erasing... Words have a meaning.

On plain partitions that can be formatted, like system, wiping is usually formatting as it's faster and safer. Except for data partition.
[OnePlus 3 & 3T Cross Device Development] sajed98:
OK, so if I got to format and select data, it will wipe everything?
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
You'll have a blank empty partition.
[OnePlus 3 & 3T Cross Device Development] sajed98:
OK thanks. So is there any way to make TWRP faster without wiping internal storage?
[OnePlus 3 & 3T Cross Device Development] Abaddon:
only way is to switch to EXT4 which wipes your internal. I suggest backup it's contents on your PC first.
[OnePlus 3 & 3T Cross Device Development] sajed98:
OK thanks for your help
[OnePlus 3 & 3T Cross Device Development] Primokorn:
I flashed the dm-verity and forced encryption disabler zip when I installed TWRP for the first time but is it really required if we use Magisk? Magisk removes dm-verity and forceencrypt so it should work as easy as SuperSU.
[OnePlus 3 & 3T Cross Device Development] the_rooter:
Try it and let us know
[OnePlus 3 & 3T Cross Device Development] knpk13:
Yes, just magisk works fine.
[OnePlus 3 & 3T Cross Device Development] okie03:
help

Device - oneplus 3

Secure Boot - enabled

Device State - Unlocked

recently wanted to update my rom (Resurrection Remix-N). When I boot into TWRP, I get an error 7. I was also having issue with titanium backup (keeps crashing) so I was thinking it was the ROM since I haven't updated in a while. Since I couldn't update with TWRP and error 7, I decided to switch ROM.

I did a nand backup, then proceeded to factory reset in TWRP, reboot recovery (habit of mine).

And now I was stuck with at TWRP decrypt Data because my previous pattern is not working. Gives me a "pattern failed, please try again!")

My question, is there a way to at least get my data off the device (backup to laptop and restore later)?

I can boot into fastboot. but I can't see device storage on laptop.
[OnePlus 3 & 3T Cross Device Development] Uumas:
Could TWRP save the last used crypto libs to internal storage so that if you have no os installed, you can still boot to TWRP?
[OnePlus 3 & 3T Cross Device Development] sajed98:
Thanks bro for the clarification!
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
I am not a TWRP dev, so it's up to OP to do so.

But I would think, no. Where to save the files? You mentioned internal storage aka /data. But that's encrypted and not accessible until decrypted.

All other partitions either also get formatted when users install new operating systems, or are used for internal, hardware related stuff. So there is really no place to put those files.

I guess the fact that themes are stored on internal and only loaded after successful decryption says something.

Last not least, it's not a big thing. Just don't reboot after wiping system. If you do you can easily fix that error as written above.

Also compared to the old state, before /system was used for crypto libs, the state now is way better and yields much less issues. I like it as is.
[OnePlus 3 & 3T Cross Device Development] Uumas:
Maybe it could have them in /tmp while using it and when rebooting, if it detects no os it would put them to /system or /cache and remove them when you boot to twrp again.

I agree that this is much better than multiple different recoveries and this is by no means a high priority feature. Just something that maybe could be done.
[OnePlus 3 & 3T Cross Device Development] gmillz:
Is anybody else having issues with adb freezing in recovery? Sideload and push both hang about a quarter to half way done.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
Yes but I don't undestand why MagiskSU is not mentioned in OP... It should be highlighted like SuperSU.

No issue here with adb push/pull.
[OnePlus 3 & 3T Cross Device Development] luka1002:
I am having problems with updated twrp. My decrypt pass is wrong (it is not but that what he says). I changed password in OS but still same... I am on resurrection ROM.

I need help because i removed pin from sec. and now on reboot still asks for pin, so my phone is death untill i decypt and reflash phone.

dmesg.log

recovery.log
[OnePlus 3 & 3T Cross Device Development] Lownita:
I want to achieve the following two tasks by flashing a .zip file in recovery:

1. Open the following file:

/system/etc/permissions/handheld_core_hardware.xml​

Add in the following lines right before the </permissions> closing tag at the end:

<feature name="android.software.vr.mode" />
<feature name="android.hardware.vr.high_performance" />

2. Open

/system/build.prop

Add this line:

ro.product.device=sailfish

So how can I do it? :)
[OnePlus 3 & 3T Cross Device Development] the_rooter:
No its not wipe phone start over
[OnePlus 3 & 3T Cross Device Development] beardymarrow:
This zip should give you a good start for the build prop edits. This is off topic so best no more discussion.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Hello,

i have searched this thread with "3.2.8" "MM" "Marshmallow" but no result came up, so asking this question now.

Could anyone please let me know if the latest recovery version, 3.0.4-1, can be used to flash back to OOS 3.2.8 based on MM and if it compatible with MM?

I am really not happy with OOS 4.0.3 and would like to stay with good ol' 3.2.8 MM. The game i play the most, MC5, also works a bit bad on nougat so no special reason to stay there. I would appreciate if anyone can let me know.
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Solution: Format C:\

Seriously, it's windows. Good luck finding the source of this. Might be drivers, might be anti virus, might be not-yet-noticed maleware. The list is long. Either reinstall or use a Linux livecd to do your adb and fastboot work.

If you are very lucky, I am wrong and your usb cable has a short circuit.

My bet is on this: You have setup a pin, but on the request for "ask for password on boot?" you selected no. That way, you can change the password in your ROM all day, it doesn't change a thing. Reboot to recovery and try "default_password" without the ". Should work.

You must write a shell script. The provided build.prop script is a good start, but to achieve your .xml modification, you must extend it.

If you don't know anything about shell scripts, you either research this topic, which is very well documented, and learn your way around a shell or you cannot complete the task.

Some tips for researching:

- One main focus should lie on the sed command

- Try your shell script first on your linux installation to see if it works

- If it works, try it now in the "adb shell" on your phone. Something probably requires tweaking, since the minimalistic busybox environment doesn't support all the options a full shell offers.

- Now create or edit /META-INF/com/google/android/updater-script of a flashable .zip file. Its a shell script, just as you just learned. You can put all your commands there.

- Test flash it. If the commands worked on "adb shell", they will work with flashing, too.

- Profit. The knowledge you just acquired will probably still work in 30 years, same as it did work 30 years ago.

Yes, it will work. The days were you need a specific twrp for a specific ROM version are long gone.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
New problem after restoring a nandroid backup.

- I was on unofficial RR build (based on 4.0.2 firmware). Ext4 and unencrypted.

- I made a nandroid backup (all options are checked)

- Then I flashed 4.0.3 firmware and DU ROM

- Back to TWRP to restore my RR backup (all partitions are restored).

- I was stuck to the OnePlus splash screen.

- I flashed 4.0.2 fw. No changes.

Do you know why it happened or is a log required? (I did a clean flash to have a working device)
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Try flashing OOS 4.0.2 full rom, immediately after restore RR backup. If booting it works (i guess so), your firmware file is the cause.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
The full OOS ROM? It will overwrite the custom ROM... You've lost me there lol
[OnePlus 3 & 3T Cross Device Development] luka1002:
Nope. I had TWRP older version with pin and activated option "ask for password on boot". When flashed new twrp i could not decypt (in old ver. i could). Never mind , i have erised all and started from zero.

I have tried and that :"default_password" but no luck.
[OnePlus 3 & 3T Cross Device Development] Mata99:
Hi, I tried to flash last lineage os but i have dm-verify error
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
This is not dm verify, it's a mismatch between expected and actually present trustzone.

Update your firmware.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
I guess you should first flash the 4.0.3 firmware. Available here.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Thanks! Will try this out this weekend.
[OnePlus 3 & 3T Cross Device Development] bdorr1105:
I would wipe everything, literally wipe through advanced wipe, flash twrp 3.0.3.1 through fastboot, reboot into recovery, swipe right, flash the DM Verity zip, flash the 4.3 firmware and ROM you want. You can MTP through recovery and transfer the zips you need while in recovery, just make sure you enable MTP in recovery.

Which partitions did you restore? You do not want to do system, those are different firmware bases, just the data for the apps...Safer doing Titanium Backup.
[OnePlus 3 & 3T Cross Device Development] jhomarsn:
Error trying to intall or backup

Hi guys i need some help here i have some error when i try to install/upgrade my LOS to last version : i have LOS installed on my OP3T with TWRP 3.0.4-1 the last things i install is magisk and kernel elementalx ( the kernel is not installer right now).

the .log file is attach

Failed to mount '/system' (invalid argument)

when i try to reboot in TWRP said NO OS installed i swip and restart to my ROM normally.

thank you very mouch:good:
[OnePlus 3 & 3T Cross Device Development] gmillz:
No windows here. It literally just freezes at some random point and never moves from there. Not sure what's up. Gonna try reflashing recovery.
[OnePlus 3 & 3T Cross Device Development] jhomarsn:
Failed to mount

Failed to mount '/system' (invalid argument)

some help
[OnePlus 3 & 3T Cross Device Development] kessaras:
That's impossible. In the twrp mount menu?

If yes, did you delete the system partition and if yes how did you do that?

Do in terminal in twrp

sgdisk --print /dev/block/dm-0

Is system there?

Edit: to read it easier do

sgdisk --print /dev/block/dm-0 | tail -10
[OnePlus 3 & 3T Cross Device Development] jhomarsn:
[MENTION=5461026]kessaras[/MENTION] this is my problem thanks
[OnePlus 3 & 3T Cross Device Development] kessaras:
yea ok, did you use that command to see if you deleted the partition or not ?

if you deleted the partition , you need the .bin file that contain the gpt.

on lg another way was to flash kdz and everything is restored. here i don't know if the full firmware zip is enough to help you. try it.
[OnePlus 3 & 3T Cross Device Development] jhomarsn:
I'm using my phone very well and booted and everything the only problem is to make BK, install or reboot from recovery to OS.

I don't want happened I reinstalled the recovery via ADB and I have the same problem.
[OnePlus 3 & 3T Cross Device Development] Joloxx9:
If im going to change all partitions to f2fs do I need to flash anything Special? Thanks in advance
[OnePlus 3 & 3T Cross Device Development] kessaras:
No. And only data and cache you can.
[OnePlus 3 & 3T Cross Device Development] Joloxx9:
There is a option for f2fs for system, what gonna happen if I use it?
[OnePlus 3 & 3T Cross Device Development] Sun90:
U have to ensure the RoM supports f2fs on system for now.

If not then u will be in trouble.

It's better of if data only is f2fs for now.
[OnePlus 3 & 3T Cross Device Development] kessaras:
He can't format system to f2fs. At least official twrp has this disabled. Even if he press format /system to f2fs , it will fail to format
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
yes mate. the full oos. installing 4.0.2 firmware obviously didnt work. so flashing full 4.0.2 rom to install firmware and then your custom rom over it. should work and solve the issue.

if this doesnt work, your rom probably requires another firmware version. you should discuss that in your rom's thread.

overall make sure to have the right firmware to the right rom BEFORE trying to boot that rom.

Unfortunately you only attached one logfile. the other (kmesg) is missing. So I can see, you encountered that error, but not why.

I can say for sure that TWRP is able to access system, because you can decrypt your /data partition.

The rest is up to speculation. You could try to format /system and afterwards flash the rom again. You can try to check/uncheck system in mounts.

If you really want an answer, send the full log. Not sure, if I am qualified enough for this tough. Let's find out.

Whatever operating system you got, its probably the reason. The other is a short-circuit usb-c cable. Reflashing recovery won't fix it.

In case you have a Unix based operating system, its worth checking the system logs while the error occurs.

wow. the anti-anti-f2fs movement. *shivers*
[OnePlus 3 & 3T Cross Device Development] diegogero:
Hi there, i keep getting error 7. I tried installing another twrp downloaded from twrp which is for the oneplus 3t. i am wondering. On the file i downloaded from lineage os it is written it is for oneplus 3, not 3t. Did i chose the wrong rom?

Edit: i had forgotten to wipe dalvik and cache.
[OnePlus 3 & 3T Cross Device Development] timobayl:
Do you use the latest firmware 4.0.3?
[OnePlus 3 & 3T Cross Device Development] DroidJay123:
So I installed TWRP 3.0.4-1 and flashed the no-dm-verity zip and everything went as described it would. My question is when you first request the system to reboot, another prompt shows asking to install the Official TWRP app with 2 boxes already checked...

Prompt to install TWRP app if not installed

Install as a System App

Do I leave those checked swipe to Install TWRP App?

Please help as I got this far and don't want to F it up now.

Thanks all!
[OnePlus 3 & 3T Cross Device Development] kunal1540:
Those are just optional.

You can uncheck them if you dont want them in your system

Haven't flashed no dm verity zip so can't say anything about that
[OnePlus 3 & 3T Cross Device Development] Uumas:
Unselect them. It doesn't really matter, but if you don't know what it does, you don't need it.
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
The only thing I miss is the theme compatibility :rolleyes: besides that TWRP works as it should. :svetius:
[OnePlus 3 & 3T Cross Device Development] albe65:
Need some help

Device oneplus3t ROM : Zenity(based on RR)

My TWRP is broken, unable to start (black screen)

I tried to flash the last version 3.0.4.1

I have a message : Failed : (remote : Partition flashing is not allowed)

Thanks for your help
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Did you try flashing it via fastboot?
[OnePlus 3 & 3T Cross Device Development] albe65:
Yes i used :

fastboot flash recovery twrp.img

(twrp.img is the renamed file of the 3.4.01 file)
[OnePlus 3 & 3T Cross Device Development] eskilde:
I got a new OnePlus3t running OxygenOS 4.0.3 and I realy don't like it, I have been using LineageOS 14.1 on a S2 and was very pleased with that but it was slow and only G3 no NFC and so on..

I would like to put TWRP on and lineageOS 14.1 on my OnePlus3t but what is the best way doing so. I have been reading through the forum and it seems that nobody has luck with this action.

Is there a way that works first time or do I have to use the roulett methode and hope I hit the right way to do so. How has the right recipe ?

I'm ok deleting every thing and formating. I would like f2fs working so I don't get any camera problems.

Hope someone kan help.
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
All you have to do is to unlock your bootloader, flash twrp, decrypt and format if you want to be on f2fs and then you are free to flash any rom. I can recommend RR and Aosip to name a few

---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------

Try flashing via twrp official app
[OnePlus 3 & 3T Cross Device Development] sharath_babu:
Restored stock rom4.0.3,now stuck at lock screen ,bz its not accepting my password...but successful decrypted, using 3.0.4.

Need some light here
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Flash the attached zip in recovery, it would remove your lockscreen pin or pattern and I can set it up again.