yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
The question was about upgrading an older TWRP to the latest version. You replied he should install the correct firmware first. Where does that make sense?

FUD: Fear, uncertainty and doubt.
[OnePlus 3 & 3T Cross Device Development] vuP22:
I used "fastboot format userdata" to remove encryption, but now my internalt storage has only 24GB, how do I get back the whole 64GB?

EDIT: Solved it by formatting /data in TWRP
[OnePlus 3 & 3T Cross Device Development] Lownita:
Formatting data in trwp would've also removed encryption.
[OnePlus 3 & 3T Cross Device Development] melabones36000:
Download error for TWRP

I click on this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img, but then I get a download error.
[OnePlus 3 & 3T Cross Device Development] Antsu:
[MENTION=4164427]melabones36000[/MENTION]

Just downloaded successfully. Have you tried another browser?
[OnePlus 3 & 3T Cross Device Development] melabones36000:
Yeah it was my browser. I use Dolphin on android. I just downloaded Firefox and it worked for me. Can't understand why Dolphin didn't work.
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
It just doesn't handle correctly all modern security settings in websites.
[OnePlus 3 & 3T Cross Device Development] TheFrozen4:
All the way. What are you referring to, are you sure it is not something else? Like a f2fs problem on your device?
[OnePlus 3 & 3T Cross Device Development] SpasilliumNexus:
Is not being able to delete or update apps from the Play Store due to .obb files in /sdcard/Android/obb being write-protected due to TWRP or OxygenOS 4.0.3 on OnePlus 3T?

They download to /sdcard/Android/obb fine, but I have to go into /storage/emulated/obb to delete them in order for the Play Store to update properly. Otherwise I get an error about not being able to update.

EDIT: Fixed. I went into TWRP and deleted the obb folder in /data/media/. Now I can update apps fine.
[OnePlus 3 & 3T Cross Device Development] Lownita:
Alright guys, I'm going to do a clean install of nougat, so I have to decide which filesystem I want to use. I'm inclined to stay on ext4, don't see any profits in f2fs for normal usage besides better benchmark scores, just more potential for bugs. Anyone wants to convince me of the opposite? :silly:
[OnePlus 3 & 3T Cross Device Development] the_rooter:
I tried staying on f2fs but seen more issues than benefits.
[OnePlus 3 & 3T Cross Device Development] Uumas:
I have never had any issues with f2fs and haven't bothered to change to ext4 because of that.
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
The same. No problem with f2fs and latest twrp.
[OnePlus 3 & 3T Cross Device Development] vuP22:
superSU didn't work on custom Roms with f2fs, that's why I changed back to ext4
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
I use supersu lol.
[OnePlus 3 & 3T Cross Device Development] Lownita:
So I tried this:

adb exec-out "tar c /sdcard 2>/dev/null" > sdcard.tar

The .tar file has the appropiate size, but whenever I try to unpack it with 7zip, I only get a bunch of empty folders with an error message: "There are some data after the end of the payload data." :confused: I am just doing adb pull /sdcard/ now. Maybe I need to update 7zip.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
You're right. This new version is working flawlessly. TWRP decrypts all my data without entering my PIN.
[OnePlus 3 & 3T Cross Device Development] vl.xl:
Had some free time and wanted to see what I can do with DM verity warning on Nougat and also go back to encrypted so this is what I did:

-Flashed full 4.0.2. ROM with no root to get back to stock recovery (still DM verity warning)

- Relocked the bootloader (still DM verity warning)

- ADB sideload full 4.0.2 ROM (DM verity warning finally gone)

- unlocked bootloader again (no DM verity warning)

- flashed twrp 3.0.4.0 via fastboot (no DM verity warning)

- booted to twrp and changed data filesytem to EXT4

- flashed [MENTION=5672995]jcadduono[/MENTION] dm-verity and forced encryption disabler (don't know if needed and also don't format data again if you want to stay encrypted)

- flashed Magisk 10.2

reboot system and profit.. fully rooted on Nougat with no DM verity warning.

- flashed Elemental X (still no DM verity warning)

so happily running Nougat, encrypted, no dm verity warning with custom kernel and TWRP 3.0.4.0 working great.

Hope this helps someone.
[OnePlus 3 & 3T Cross Device Development] Clark789:
Hello,

someone can please tell me, how to solve the dm-verity-issue? I just flashed OOS 4.0.2 and after this SuperSu 2.79. No problems with TWRP 3.0.3.1. Ican enter into TWRP without any problems, but i always got the dm-verity-warning. I flashed TWRP 3.0.4.0, but this is no solution. Must i flash the est dm-verity and forced encryption disabler.zip?

Any help would be appreciated!

Cheers

Clark
[OnePlus 3 & 3T Cross Device Development] vl.xl:
I just wrote in post above yours how I solved it. Also it is not an issue, it is just annoying warning.
[OnePlus 3 & 3T Cross Device Development] Clark789:
Hi,

ye i saw your post. It's not only annoying, because my OPP3T can't switch to enforcing mode...

Didn't you loose your data, when you change to ext4? And are there any advantages in using magisk instead of SuperSu?

Regards

Clark
[OnePlus 3 & 3T Cross Device Development] vl.xl:
Yes I did loose data, but I had time so I didn't mind loosing data. You can probably backup your data then format.

I prefer Magisk wither superuser as I can hide it via app and my phone pass Safetynet.. ofc there's suhide, but I like it more this way.
[OnePlus 3 & 3T Cross Device Development] Clark789:
Would be interesting to know, what was the triggering solution for the dm-verity issue: changing to ext4 or flashing the est dm-verity and forced encryption disabler.zip??

Regards

Clark
[OnePlus 3 & 3T Cross Device Development] vl.xl:
I couldn't get rid of DM verity warning whatever I did with f2fs (I never mounted system as writeable), but I may be totally wrong about it.
[OnePlus 3 & 3T Cross Device Development] 2x4:
3.0.4 decrypted storage OK on OB11
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
[MENTION=5672995]jcadduono[/MENTION] in the OP under "changes" you mixed up 3.0.3-0 with 3.0.3-1 -> this could lead to missunderstandings.

-----------------------------

decrypts your data without entering your pin? wait, how does that work?

---------- Post added at 10:19 PM ---------- Previous post was at 10:15 PM ----------

With dm verity warning you mean the second warning screen after unlock warning? Since if your post is only about that, it seems to be a lot of effort for something very unimportant.

If it is not about that, I want to know what you are talking about.
[OnePlus 3 & 3T Cross Device Development] vl.xl:
Yeah, it is very unimportant :) I was bored, had some free time and just wanted to see how can I get rid of second warning screen.

Sorry if my boredom didn't bring much to community.

Peace,

V
[OnePlus 3 & 3T Cross Device Development] jcadduono:
actually the OP3 was on 3.0.3-0 and this is the OP3 forum, I guess I could mention 3.0.3-0 for OP3 was the same as 3.0.3-1 for OP3T...

probably set a pin without a boot password, its possible, ex. set a pin on lock screen then in terminal vdc cryptfs changepw default_password (i think something like that?)

kinda makes encryption not very useful
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Did you consider adding a warning? It's fake encryption, maybe helping for petty thiefs who can at least wipe a device before selling it, but one can never be sure his data is safe. Thats the main point of encryption, right?
[OnePlus 3 & 3T Cross Device Development] vl.xl:
So I am :confused: and n00b now :)

1) My phone is encrypted and I set PIN and fingerprint without option to enter it on boot. I go to TWRP and it decrypts my data without entering anything.

2) My phone is encrypted and I set PIN and fingerprint with the option to enter PIN on boot. I go to TWRP and it doesn't decrypt my data until I enter my PIN.

So option number 1 is no security at all, and option number to is more secure? Or I am totally wrong about all of it?

Thanks,

V
[OnePlus 3 & 3T Cross Device Development] Lownita:
I have yet to understand what triggers the dm verity warning and why it disappeared for you. Why did it still show up when bootloader was already locked?
[OnePlus 3 & 3T Cross Device Development] the_rooter:
have u tried flashing a older bootloader?
[OnePlus 3 & 3T Cross Device Development] vl.xl:
Don't know. Don't shoot the messenger. Until I flashed ROM with ADB sideload with locked bootloader dm-verity warning wouldn't go away.

As I said I am n00b and only wrote what I experienced
[OnePlus 3 & 3T Cross Device Development] jcadduono:
correct, option 1 provides no security in the event that someone physically steals your device.

option 2 prevents thieves from getting your data if they physically steal your device.

option 1 only provides a bit of security when your bootloader is locked. if it is unlocked, option 1 is no security at all.

(there are some lock screen exploits that show up once in a while, often accessible from notifications/pull down)

i very much advise having a boot password. without one, someone can simply go into twrp and remove your lock screen as well.

if your device allows, it's a good idea to use a more complicated alphanumeric/symbols password for boot. you will only have to enter it when booting your device (system and twrp).

the boot password is used to form the encryption key, so the more complicated it is, the less chance your data encryption can be brute forced (okay that's pretty darn rare) or guessed.

also, you will notice that changing your password does not change your data, ex. it does not need to re-encrypt. this suggests that your password merely encrypts some kind of master key for your data (which is tied to your device and no one else's), so it might be possible some day to exploit this. i don't know much at all about encryption to continue this conversation lol. i would assume the master key is regenerated random each time encryption process begins with an empty crypto key. (OP3/OP3T use the last 16384 bytes of data partition for this)

not sure if it is necessary to dd that out when formatting data to build a new key, because i have seen multiple partitions linked to the same key in devices so i must assume it reuses the key if it is there already.

i think twrp actually wipes the key location mentioned in the recovery.fstab when you format data, which could potentially cause you to lose any data tied to that key, ex. if you had a microSD card or OTG using your phone's encryption based on same crypto key used for /data.
[OnePlus 3 & 3T Cross Device Development] Antsu:
My device is encrypted and data is on ext4 and I had pattern unlock without secure start-up enabled. In this situation I could boot to twrp without it asking the password, it just decrypted data right away.

Don't know how it was possible to decrypt without entering the pin if it was enabled already.

Now I 've changed to pin-lock and enabled secure start-up and it asks my pin to decrypt when booting to twrp. I enter pin and then it decrypts the data.

Edit. Oh sorry, it was already discussed...
[OnePlus 3 & 3T Cross Device Development] vl.xl:
Much appreciated :svetius:
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Stay on ext4. The big advantage of f2fs is write throughput. Something we don't use a lot. I.e. when do you do bulk writes of many megabytes? Not during app loading at least.

f2fs got better in custom roms, it's a while that i read about a f2fs system breaking together and losing data because of the various f2fs kernel implementations. Still, alone the fact that TWRP loads way faster is worth ext4.

Or not use 7zip at all. Tar is a extermly old unix untility - the name TapeARchiver points to ages where people actually put tapes into drives to make backups. Its the de-facto standard for everything unix based. usually in the gzip'ed .tar.gz (or tgz) format or the bzip based tar.bz - 7zip actually is a windows bzip implementation. If windows cannot handle it, it doesn't mean your file is corrupted. I know, total commander can handle it.

BTW: Did you notice, how freakin fast that command finished - compared to just copying it?
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Can 3.0.4.1 be flashed over 3.0.4.0? I'm using F2FS-formatted data, it seems like this update was related to the issue people were having with EXT4 and F2FS formatting, I never switched to EXT4 but I wanted to make sure it would be ok to just fastboot flash 4.1 over 4.0.
[OnePlus 3 & 3T Cross Device Development] mrducnguyen:
Hi,

I'm having an issue. Coming back from Lineage OS, I have formatted my data as ext4. I was able to flash OxygenOS 4.0.3 latest release without any problems and use it for a while, before I decided to root my phone again.

I *accidentally flashed both Super Su 2.46 (chainfire) and no-verity-opt-encrypt-5.1 on TWRP 3.0.4-1. Now I've been stuck in the looping circle of Oxygen OS boot screen forever. I've tried to wipe everything except System and so far it's not working.

I have to do a clean flash of OxygenOS 4.0.3. Now gonna try the rooting process again.
[OnePlus 3 & 3T Cross Device Development] SourPower:
+1 I'm in the same boat
[OnePlus 3 & 3T Cross Device Development] Acxjet:
That issue got fixed a month ago because Arter97's help
[OnePlus 3 & 3T Cross Device Development] TeddySika:
me too, but i want to flash 3.0.4-1 over 3.0.3-1. would it be possible to flash via TWRP apps ?
[OnePlus 3 & 3T Cross Device Development] Crazy_Oni:
Sure. Flash the img file in twrp and all should be ok.

Go to install and select img flash. Then tick on recovery and flash the img file.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Yes you can install the twrp via official twrp app from Playstore..
[OnePlus 3 & 3T Cross Device Development] Joloxx9:
Guys can I set a pin number for twrp?
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Flashing both files didn't create the issue.

It's your superSU version. 2.46 is outdated. AFAIK the only version working properly is latest 2.79. Also wiping everything except system doesn't help, since the - wrong - changes the outdated superSU does is to system. Flashing 2.79 over 2.46 _MIGHT_ fix it, if not, wipe system and start over again.

No, you can't. You only can make it ask for your encryption key for data partition. This can be cancled, but at least your data is save.

If you are unencrypted, you cannot protect it with a PIN. Another reason to never be unencrypted.

A workaround might be - if you are rooted - to only install TWRP (via official app) if you need it. If you dont need it, use official app to install stock recovery or just install something not working at all like some zeros.
[OnePlus 3 & 3T Cross Device Development] RoelD92:
Ehhm, latest stable SuperSU is 2.79. just saying. I think 2.48 is the latest one chainfire released but SuperSU is still being updated
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Yes, you are right. Thanks a lot.

I meant 2.79 but somehow confused version numbers. Corrected my post.
[OnePlus 3 & 3T Cross Device Development] Mr.Crucial:
When will official version be released?
[OnePlus 3 & 3T Cross Device Development] Uumas:
This is official. 3.0.4 hasn't been released yet for other devices and that's why it's not on twrp.me yet. Just use this.
[OnePlus 3 & 3T Cross Device Development] Lownita:
I have a question regarding encryption. When you flash OOS, the phone is encrypted from the first boot. Now after formatting data and flashing a custom ROM, encryption is, of course, gone. Now if I want to encrypt my phone again, should I just do it from the security menu inside android? Would this enable a bad/slow way of encryption or would it be the same as the stock encryption?
[OnePlus 3 & 3T Cross Device Development] Michalko5896:
same
[OnePlus 3 & 3T Cross Device Development] cowbe0x004:
Sorry if this was asked, but I've been reading and still confused. I have my phone set to unlock with fingerprint+pin. Now whenever I boot to recovery I'm asked for the pin. It's able to decrypt with the correct pin. There's no way to bypass this step is there? If I remove the pin then twrp won't ask me.
[OnePlus 3 & 3T Cross Device Development] Uumas:
It's because of encryption
[OnePlus 3 & 3T Cross Device Development] Michalko5896:
No way to bypass.
[OnePlus 3 & 3T Cross Device Development] computersalat:
Thank you :)
[OnePlus 3 & 3T Cross Device Development] DrexelDragon:
Can anyone help me?

Just got my 3T. Unlocked the bootloader and flashed TWRP, it hangs on the splash screen however and doesn't let me in.

Am I doing something wrong?

Edit:

Waited 30 minutes, tried running the "adb shell wipe_misc" command, however it returns "error: device offline".

Any ideas?

Edit 2: Got the device back online by replugging in and restarting adb.. however when I run the commands nothing happens. Do they take awhile to run?
[OnePlus 3 & 3T Cross Device Development] Renosh:
If you remove the pin (selecting none or swipe) then it went ask you for it in recovery. I'd suggest you keep that pin for security reasons
[OnePlus 3 & 3T Cross Device Development] bilottag:
Me too....same exact issue

Please help
[OnePlus 3 & 3T Cross Device Development] cultofluna:
After installing through fastboot..Boot manually on twrp..

It takes a while to boot cause of f2fs filesystem...
[OnePlus 3 & 3T Cross Device Development] aehlayel:
Encryption Unsuccessful Woes

I was upgrading my OP3T from OS 4.0.2 to 4.0.3 on TWRP 3.0.3-1, Rooted. Downloaded the Full file and reloaded (from the updater).

Upgrade successful. Upon reloading after the upgrade, got stuck for about 10 minutes. Turned the phone off and on. Encryption Unsuccessful message asking me to wipe. Also got the dm-verity error on startup, never got that before.

Reluctant to wipe as I have no backup of my media (photos and videos mostly).

Downloaded OS 4.0.2 hoping things would go back to normal. Didn't work. Flashed Stock recovery. Still didn't work. Went back to TWRP 3.0.3-1, still the same. Now at 3.0.4-1. TWRP asks me for a decryption password. Data partition shows as 0MB (probably because TWRP believes its encrypted), so it cannot be backed up.

Any thoughts on how to overcome this, without losing data?
[OnePlus 3 & 3T Cross Device Development] Vanilla Pudding:
I need help please , I set up an encryption password when i was setting a rom up. When i rebooted and entered it in TWRP it worked fine. But when i tried rebooting back into system and entered my password before boot , I got wrong password error.

The encryption password works in TWRP but not in Validus rom. What should i do ?

I do not want to format my phone, This data is very important to me.
[OnePlus 3 & 3T Cross Device Development] joco1114:
Install cleaning_lock.zip.

---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------

Oh, and if you dont speak russian, here is it on my download site:

http://joco1114.synology.me/dl/cleaning_lock.zip

I hope I remember well for its address... :)
[OnePlus 3 & 3T Cross Device Development] Pumpino:
If 3.0.4 has important fixes, why hasn't it been officially released?
[OnePlus 3 & 3T Cross Device Development] Uumas:
Because they aren't as important for other devices than op3(t)
[OnePlus 3 & 3T Cross Device Development] habylab:
What critical fixes does it have?
[OnePlus 3 & 3T Cross Device Development] the_rooter:
www.google.com
[OnePlus 3 & 3T Cross Device Development] aehlayel:
Anyone? Anything? Any help would be appreciated.
[OnePlus 3 & 3T Cross Device Development] cultofluna:
" Download the full file and reloaded?...

If you are rooted with custom recovery you can't use local upgrade...

This is what you mean?....Be more specific..
[OnePlus 3 & 3T Cross Device Development] habylab:
So critical, it isn't officially released. Google yields this thread and basically nothing else. Will keep searching.
[OnePlus 3 & 3T Cross Device Development] aehlayel:
So the updater prompted me to download a 1488MB update. I believe that's the full update. Not just the OTA incremental upgrade.

I've just downloaded OnePlus3TOxygen_28_OTA_041_all_1702081824_e3a712.zip and flashed it via adb sideload on TWRP 3.0.4-1 and I still get the "encryption failed" message.

Any thoughts?
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Yes this the full zip....You have to install it on twrp...
[OnePlus 3 & 3T Cross Device Development] aehlayel:
Just sideloaded it multiple times on TWRP 3.0.3-1 and TWRP 3.0.4-1 and I still get the same issue. "Encryption Unsuccessful" upon booting up.

Am I missing anything here?
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Sideloaded or installing via twrp ?
[OnePlus 3 & 3T Cross Device Development] aehlayel:
Sideloaded via TWRP - as in adb sideload <filename>.

My phone won't let me in to Android. I get stuck at the "Encryption Unsuccessful" screen where I have no option but to "Reset Phone".
[OnePlus 3 & 3T Cross Device Development] cultofluna:
That sucks..

If didn't backup your data..
[OnePlus 3 & 3T Cross Device Development] aehlayel:
I know. Any other thoughts?
[OnePlus 3 & 3T Cross Device Development] cultofluna:
No sorry..Hope that someone else can help you...
[OnePlus 3 & 3T Cross Device Development] aehlayel:
Thanks!

Anyone have any ideas on how to save my data?
[OnePlus 3 & 3T Cross Device Development] mad-murdock:
Mainly linux capabilites support for backup and restore. If OOS gets restored without capabilites, a startup process runs wild, spamming your logcat and draining your battery in the process.

You couldn't find this here, since it was only discussed on the old 3T thread. I also doubt, a very smart google search would have helped here. So much for trolls (who obviously also didn't know the answer).

Ask in your ROM thread. Meanwhile reboot to TWRP, make a nandroid backup and copy all your data to your PC. Then format data under advanced wipe. It will remove the encryption key in the process. While I am usually a strong supporter of "don't go unencrypted", in this case, stay unencrypted until you figure out the underlying issue in your ROMs thread.

On a side note, the linked zip from the other post wont help, since it removes your lockscreen password. You clearly talk about the on-boot encryption password dialogue. That cannot be removed.

I have an idea what happend, but unfortunately, your data cannot be saved.

You flashed 4.0.3, you did not flash no-verity-opt-encrypt-5.1.zip from OP or SuperSU. So your unmodified OOS kernel had force-encryption activated. On your first boot, the encryption process started. You did reset your phone in the process. You now have a broken, semi-encrypted data partition. You can try entering "default_password" in TWRP and see, if it works, but I highly doubt it.

All you have left is formating your data partition. Your data is already lost. Sorry.
[OnePlus 3 & 3T Cross Device Development] Lownita:
If there is no forced encryption because of patched kernel, what's the right way to enable encryption? Just from the security menu inside android? If so, why does it say it would take up to an hour when forced encryption is happening instantly on first boot?
[OnePlus 3 & 3T Cross Device Development] cgibbons51:
It'll take an hour or more for the encryption to be finished. It'll be almost instant when booting and stuff etc. As in after its finished reboots and shutdowns really won't change, you definitely won't have to wait that hour again. But when you first press that button it'll be a bit for it to finish. Basically because it's encrypting every file on your phone like say a 5 Gig app or something like that.
[OnePlus 3 & 3T Cross Device Development] aehlayel:
Thank you for the elaborate explanation. Kinda makes sense.

Would formatting the data partition mean that I would lose my media (photos, videos..) or my applications? Or both?

And where should I format data from? TWRP Wipe screen, or the reset phone button from the "Encryption Unsuccessful" screen? Or does it make no difference?

Thx