yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] swat4samp:
I too started facing this after I changed file system of /data partition from f2fs to ext4. I wiped everything and flashed aosip rom fine, but after rebooting to recovery, it shows internal memory as 0mb and doesn't mount internal storage. I'll have to give official twrp a shot.
[OnePlus 3 & 3T Cross Device Development] :
2 month. We will survive, folks. :good:

Almost a month with nobody even reviewed it is flawed or not yet

Just built it by yourself if you can and have some free time, then let everybody test it for you, dude.

================

Let me summarize the current build flaws:

- Encryption problems

- Formatting problems

- Nougat problems

- ( ............? )

It's just a rant, a SPAM that doesn't worth to be read.

Just ignore it.

/s
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Different scenario. I didn't change the filesystem type at all. My old data was still there after changing recovery, nothing lost. Even my password was the same. I was using multiple ROMs before, all on eng.stk's TWRP, and suddenly can't decrypt. Changing to "stock TWRP" fixed it, yet nothing should have changed on the /data partition that I can think of.
[OnePlus 3 & 3T Cross Device Development] swat4samp:
Oh okay. I thought I had similar issue but it's different. And I solved mine by flashing this TWRP.
[OnePlus 3 & 3T Cross Device Development] Pagozzi:
OP3t with unlocked bootloader and open beta, not rooted yet.

I've flashed the last version of the TWRP and then, after re-entering the recovery, I swiped to allow modifications.

Immediately after, I flashed the superSU zip previously copied into phone memory.

All good, process done...after the 2-3 consequential reboots( separated by the dm-verity screen), the boot process had stucked at the static oneplus logo screen with the "powered by android" label.

What's happened? I hope I'm not ended with a bricked phone.

I'm suspecting(but maybe I'm wrong since I'm not expert about dm-verity) this could be related with the steps involving the dm-verity zip, but I've meant those were optionals steps to follow.

What could I do now?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Flash magisk instead of supersu (end of life).

Boot twrp, flash rom, flash magisk, reboot system.
[OnePlus 3 & 3T Cross Device Development] Pagozzi:
Since the phone doesn't run, I guess I'll use adb push command to send rom zip into memory, right?

Does flashing stock oneplus rom, overwrite the actual TWRP with stock rom?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Yes, adb is a good choice (or use a toolkit). You can try adb sideload to flash stock rom (you need to flash and boot recovery (stock or twrp)).

And yes, when you will boot on stock kernel you will have stock recovery.

Edit.

That's why you need to flash magisk after the rom and before booting to system (to patch the stock kernel)
[OnePlus 3 & 3T Cross Device Development] :
Since magisk patches your boot partition you need to flash the bootimage before magisk. Flashing the bootimage is part of flashing the rom.

If you dirty flash and havn't flashed magisk before, you can flash magisk after rom. It doesn't matter if you reboot in between or not.

If you dirty flash and magisk was installed before, it will be there after the dirty flash without any further action (due to a backup/restore script addon.d.

If you clean flash, you need to flash gapps BEFORE rebooting, but you need to boot system and run through initial setup before booting twrp again to flash magisk, otherwise you'll end up in bootloops.

Bottom line: if you want to flash magisk the first time, you NEED to have booted system at least once: either on a already setup and running system (if it's currently running, it must have been booted before), or on a clean flash after running initial setup!
[OnePlus 3 & 3T Cross Device Development] lauralbaby:
1. Yes, reboot into recovery again.

2. If you are flashing stock, afterwards reboot into recovery once more before you reboot into system.

And if you don't want to trigger dm-verity, you will need the boot image and zip file posted on the dm-verity thread around the forums. If it's not stock then you do not have to worry about it.
[OnePlus 3 & 3T Cross Device Development] laupuy:
Thanks, but my answer was for [MENTION=5560816]Pagozzi[/MENTION] on stock rom.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I just had something odd happen. I ran a backup script to backup my system and instead of being prompted for my on-boot password, TWRP just started making the backup!

It seems that somehow the on-boot password got reset to the default (see attached TWRP log). I've had the startup password set for weeks and haven't changed it. My previous backup taken 4 days ago when I installed a ROM update (NOS 180518) needed the password as did rebooting after the backup.

I've not made any system changes, password changes, or flashed anything since then.

So what could have reset the startup password? The only previous time I've seen this happen is upgrading Magisk using the Magisk Manager. But I've not made any changes to Magisk since my last backup.

Or is this a TWRP bug?

Like I said, this is very odd!
[OnePlus 3 & 3T Cross Device Development] knpk13:
Never had anything like that happen. I'm using NLOS too. What filesystem are you using?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
All my partitions are stock. So data is f2fs, encrypted as shipped.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Really? :eek: AFAIK, the official TWRP version is unified since the update of 2017-06-09T09: 52: 52Z :silly:

---------- Post added at 04:07 PM ---------- Previous post was at 03:47 PM ----------

Something similar happens to me: For a couple of days a flashed succesfully the official twrp-3.2.1-0-oneplus3.img 22.1M 2018-02-01 09:05:26 EST directly afterwards I booted my Op3 into recovery mode without troubles... when TWRP booted, it asked me for a password to unlock my /data partition -?- I ignored that question and enabled the modifications. TWRP can't decrypt my /data partition, so no fun :( I'm not using a password or a lock-pattern, I always use swipe option to unlock the screen. I tried to flash it again but the message persisted, so I flashed twrp-3.2.1-x_blu_spark_v8.61-op3_op3t TWRP booted the first without problems, able to decrypt my partition / data.

ROM:

Official Oreo 5.0.3 Stock ROM, OTA updated, no rooted, no custom kernel, default Oreo filesystem, no MODs, just pure stock
[OnePlus 3 & 3T Cross Device Development] :
There are two different 3.2.1-0 around: the original one, which is non unified with working f2fs format, butnwith issues with Oreo, dating from December. Then there is the new 3.2.1-0, unified, oreo ready, but with broken f2fs format option. Both versions are official and both have the very same version string. "official 3.2.1-0" is ambigous.

If someone needs the original 3.2.1-0, he needs either the 3 or the 3t version, if someone needs the new 3.2.1-0 he doesn't need to care, because it's unified.

"official 3.2.1-0" is ambigous.

BTW: this has been mentioned many times (not only in this thread), you are not the only one left behind in confusion... Haveing two different versions with different code with the same version string is not the best of all solutions... ;)

The official archive (the old versions) has been overwritten with all unified versions. So the very same "not the best solution" has been applied to previous versions, too. But the official first version of 3.2.1-0 wasn't unified!
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Good to know ;) , but I'm meaning the twrp-3.2.1-0-oneplus3.img 22.1M 2018-02-01 09:05:26 EST version from the official site, so unified :good:
[OnePlus 3 & 3T Cross Device Development] BlackSoldierB:
I am seeing this message in the logcat during boot.

How can I fix this? It seems that something is wrong with my permissions the data structure.

I am trying to update to 5.0.3 from 5.0.1
[OnePlus 3 & 3T Cross Device Development] :
Would you please give us sufficient information to help you:

which twrp version do you use? Which exact steps do you take to update? Listing of the permissions on /data and / data/dalvik-cache (including the sepolicy labels "ls -laZ")? Complete logcat and dmesg from a freshly booted system, is also needed (maybe these are errors following some difderent error). Which fs is /data? Do you use the default encryption password or some custom password/pin/pattern? And a twrp log after wiping caches and dalvik would give some usefull information to help you with this issue.

EDIT: I'm assuming wiping caches and dalvik was the first thing you've tried after your findings.
[OnePlus 3 & 3T Cross Device Development] BlackSoldierB:
I have a one plus 3.

I am using the "twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img" recovery.

I had magisk 15.3 installed, therefore I always flash the full .zip file.

I am using a pattern. (Not sure if my phone is encrypted)

Steps

1. Backup system and data

2. Flash the "OnePlus3Oxygen_16_OTA_064_all_1805171653_0307a587cae84205.zip" on with twrp (Normally I use the stock recovery but this time it took a lot of time to boot it).

3. Wipe cache and dalvik using the button that appears after flashing a .zip (I always do this).

4. Reboot (got stuck here)

5. Also tried "Fix Contexts" after issues, but did not help.

6. (Normally) After successful boot, then I would flash twrp back and boot into recovery and flash magisk.

Data is ext4 (if that is what you mean with fs)

Output of ls -laZ in the root directory https://1drv.ms/t/s!AuU_vXaldxFViYxrAaliCcQ75tALfQ.

Note that this is the output after restoring my backup.

Logcat after upgrade during the first boot. https://1drv.ms/t/s!AuU_vXaldxFViYxs4w8h4AE2r6Xgtw

I restored my system and data backup and my system booted again, but I noticed that the time is incorrect (1970).

Maybe this is somehow related because the ls command also lists 1970.

Otherwise I will just have to wipe my data partition and hope that fixes it.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5995658]BlackSoldierB[/MENTION]:

I would have needed the directory listings from /data and /data/dalvik-cache. The logcat you shared does not have the entries in question...

I doubt it's a recovery issue.

Before wiping data (which is always a good idea...) I would try deleting /data/dalvik-cache/arm*.

BTW: this is the official twrp thread, I don't know where blu spark twrp is supported, I only found the keenel thread. Maybe there.
[OnePlus 3 & 3T Cross Device Development] BlackSoldierB:
[MENTION=4405529]nvertigo67[/MENTION]

I have also installed the official twrp (twrp-3.2.1-0-oneplus3.img). But I will doubt that it makes a difference.

I removed my lock-pattern and am currently making an new backup.

Here are the output of the data and data/dalvik-cache listings.

https://1drv.ms/t/s!AuU_vXaldxFViYxtTRMxxY_SQGJ7MA

https://1drv.ms/t/s!AuU_vXaldxFViYxuptt60ByNdFFGbw

I will try to wipe the caches again (using twrp) and boot into system (without update) and see if I run into the same problem again.

Edit: Wiping and booting without update seems to work

Edit2: Flashed the updated zip. But now twrp asks for an password. I tried default_password but it does not seem to work.

Weirdly enough bluespark does not ask for a password. And I am 100% sure I removed pattern.
[OnePlus 3 & 3T Cross Device Development] :
Permissions as well as sepolicy labels are ok.

Please read my conversation on different 3.2.1-0 versions. The new one sometimes shows incompatibility with encrypted filesystems generated with the original version. If you don't want to stick with blu spark (which is filesystem- and encryption-wise compatible with the original version), the onlymway to fix this is formating (not wiping) data.
[OnePlus 3 & 3T Cross Device Development] BlackSoldierB:
What do you mean with "this"?

Is that twrp thinks that the data is encrypted or the boot issue? And how do i format my data with out wiping it?

I don't mind switching over to the official twrp if I can fix the encryption issue.

I have read the difference between the twrp versions somewhere not sure where exactly though.
[OnePlus 3 & 3T Cross Device Development] :
"this": the issue with passphrase.

data is ALWAYS encrypted with OxygenOS!!! But if you choose to have an unproteced boot, the encryption passphrase is set to "default_password". twrp as well as OOS know that. For reference: https://xdaforums.com/showpost.php?p=76733214&postcount=2737 (last two paragraphs)

Formating is making a new file system - this always wipes all data in the fs.

It's one page back... thread search is your friend... I really appriciate not to be used as thread reader or search engine...

https://xdaforums.com/search/thread/3742894?query=original (second or third posting in the list)
[OnePlus 3 & 3T Cross Device Development] BlackSoldierB:
Ah I was confused by this line "to fix this is formating (not wiping) data". So I thought you could format it without wiping :).

I have read your post(s), only I did not know it was this thread (and google wasn't really helpful when searching for "twrp 3.2.1-0 oneplus 3")

So the only solution to both problems is wiping data?

Thanks for helping me.
[OnePlus 3 & 3T Cross Device Development] :
Or:

You can stick with your solution, because this

is no issue: some files originating to the rom are unix time 0, which is 1/1 1970.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
That IS weird. The two should be compatible since they use LUKS and the ROMs can decrypt just fine.

Maybe a maintainer can tell us?

---------- Post added at 02:38 AM ---------- Previous post was at 02:34 AM ----------

It's possible there is data corruption. There should be an option to check/repair filesystem. This will run fsck, the Linux equivalent of chkdisk. If corruption is detected, the partition will be mounted read-only to prevent further damage and running fsck will fix you up. Are you able to save anything at all?

If you can still write to the /data partition when the ROM boots, then its a weird ROM issue.
[OnePlus 3 & 3T Cross Device Development] :
If you look at the directory listings, you'll find /data is NOT a ro fs (otherwise there wouldn't be any write bit). I guess the "ro fs"-error message is a follow up error of something else. Sadly the supplied logcat does not contain that origin error. Though there is the possibility of a corrupted fs, I doubt that, because there should be much more errors...

Anyway, without a log containing the "fs-ro"-error, all we can do is reasonable guessing.
[OnePlus 3 & 3T Cross Device Development] BlackSoldierB:
The weird thing is, if I flash the OOS 5.0.3 then I will get the problems. If I flash the OOS 5.0.1 back, then the problems disappear.

If it was a data problem then I would expect that neither roms work.

Here is the logcat with the read only error. https://1drv.ms/t/s!AuU_vXaldxFViYxs4w8h4AE2r6Xgtw

I will also try to get the dmesg log during the first boot after the update.
[OnePlus 3 & 3T Cross Device Development] fayf86:
I just upgraded to 5.0.3 today from OOS 5.0.1 with Magisk (thus prompting a full download). Tried flashing TWRP (obtained from the unified Oneplus 3/3T page on the TWRP website), and it couldn't decrypt the FS no matter what security settings I used (tried no password, PIN, and alphanumeric password - all without fingerprints) in Android. I flashed back to 5.0.1 and TWRP is working fine.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I realize its not normally RO. If Linux senses a problem of any kind, it will remount it RO automatically
[OnePlus 3 & 3T Cross Device Development] paiktaras:
The apk always crash to my device after 5.0.3 update
[OnePlus 3 & 3T Cross Device Development] BillGoss:
What apk?
[OnePlus 3 & 3T Cross Device Development] paiktaras:
https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=en_US
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Ah, I never use that. I just go directly to TWRP.
[OnePlus 3 & 3T Cross Device Development] josephcsible:
I just ran into the apparently quite common problem where I updated from LineageOS 14.1 (Sultanxda's) to 15.1 (official LOS), and then I couldn't see /data in recovery anymore. I did some investigation, and here's what I found:

The "old" TWRPs (blu_spark and jcadduono's) won't mount /data anymore, because Android Oreo turns on quotas, which they don't understand.

The "new" TWRP won't mount /data anymore, because they only understand the new /data encryption, and I was still using the old /data encryption (since I dirty flashed).

Note that the quota problem only affects you if your /data was ext4. If it was f2fs and even the "old" TWRP can't mount it anymore, then your problem is something different, and the rest of this post isn't relevant to you.

There's two ways you can fix this, the easy way and the right way. Both start like this:

Boot up blu_spark's TWRP

Decrypt data. It will successfully decrypt but won't mount

Run "LD_LIBRARY_PATH=/system/lib64/ /system/bin/tune2fs -O^quota /dev/block/dm-0"

Run "LD_LIBRARY_PATH=/system/lib64/ /system/bin/tune2fs -Q^usrquota,^grpquota /dev/block/dm-0"

At this point, "old" TWRP will be able to mount /data, but if you boot Android, it will undo the changes you just made.

Now you need to decide which way you're going to do.

The easy way has the upside of being easy and fast, but the downside of losing the benefit of quotas, and never being able to upgrade TWRP.

Delete or rename /system/bin/tune2fs. This keeps Android from turning quotas back on.

The right way has the downside of taking much longer, but means that you'll get to keep the benefit of quotas, and you'll be able to keep upgrading TWRP. Here's how you do it:

Back up all of your data (including /sdcard) to somewhere other than your phone

Reboot into the "new" TWRP

Format data

Restore all of your backed up data
[OnePlus 3 & 3T Cross Device Development] visceralpsyche:
This came too late for me, but thank you! Yours is the first real helpful advice on this problem, with a clear explanation and a solution to the problem. Awesome stuff :)
[OnePlus 3 & 3T Cross Device Development] :
Can you confirm:

If going the second way, you end up with ext4 on /data, aren't you?
[OnePlus 3 & 3T Cross Device Development] josephcsible:
When formatting data, you can choose whether to format it as ext4 or f2fs.
[OnePlus 3 & 3T Cross Device Development] :
Really? I doubt that.

But my question was a brain fart, and should have been

"this is only confirmed to work, if you start from ext4 on data"

or something like this... I'm asking because I'm wondering what tune2fs (name origins to ext2, the base tools for ext2/3/4) will return, if pointed to an f2fs partition.
[OnePlus 3 & 3T Cross Device Development] josephcsible:
No, tune2fs absolutely will not work on f2fs. But, it looks like Android only turns on quotas on ext4 in the first place: https://github.com/aosp-mirror/platform_system_core/blob/master/fs_mgr/fs_mgr.cpp#L421-L434

If your /data is f2fs and you can't decrypt on either "old" or "new" TWRPs, your problem is something different. Do you see anything relevant at the bottom of the output in "dmesg" in either case?
[OnePlus 3 & 3T Cross Device Development] :
You are right, it's the same for los. Also: los (most probable aosp, too) activates quota for fsck but isn't using it activly in the rom. Anyway: I had an issue with decrypting f2fs, which looks very similar months ago. But is in fact something different.

Thank you very much! I appriciate that very much! Sadly, after reformating data with the new 3.2.1-0 I was never able to reproduce it - or: fortunately formating fixed it.
[OnePlus 3 & 3T Cross Device Development] :
changing fs on /data to f2fs is broken

[MENTION=5091734]dianlujitao[/MENTION]:

Symptom: if you try to change /data to f2fs, mkfs.f2fs returns "-r" unknown (recovery.log).

The standard code for mkfs.f2fs doesn't know of "-r", so either the command issued needs to be changed (giving the device size -16384) or "-r" needs to be ported from android-7.1 to android-8.1 in the omni sources:

https://github.com/omnirom/android_...mmit/bf53b3a5a470916a1b5f2e6300a14b9645c04372

I don't understand that other devices then op3/t seems to be not effected.
[OnePlus 3 & 3T Cross Device Development] osrox:
Hi,

the official twrp on my OnePlus 3, running RR rom, is having some problem.

it fails to recognize the "encryption password", (i think this happened because, i dirty flashed open beta 37 firmware+modem, during last dirty flash of RR rom update).

so i cannot access the memory & flash rom updates.

if i boot phone normally, the encryption password works fine.

i still have magisk root on my phone, so i can flash other recovery using Flashify app.

& i tried flashing bluespark recovery, but it too did not accept the encryption password.

Kindly help.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
I guess its a firmware issue. Try the 5.0.3 firmware for oneplus 3. Works on encrypted device too
[OnePlus 3 & 3T Cross Device Development] osrox:
How do i flash it,

from Flashify app ?
[OnePlus 3 & 3T Cross Device Development] :
fastboot flash stock recovery, reboot recovery, sideload the rom
[OnePlus 3 & 3T Cross Device Development] :
How to change data's fs to f2fs with current twrp-3.2.1-0?
[OnePlus 3 & 3T Cross Device Development] osrox:
stock recovery as in OOS recovery ?

i guess i can flash that from Flashify app too.

but even if i boot into OOS recovery, will it let me flash "OOS 5.0.3 Firmware" zip ?

i guess not.

& what do you mean by "sideload the rom" ?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Use the firmware file from here https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166/post74203821

And just flash it in TWRP.
[OnePlus 3 & 3T Cross Device Development] osrox:
The Recovery (twrp official/bluestark/OOS) doesn't accept my encryption password.

so i can't access the memory or flash anything.

Yesterday I changed the Lockscreen lock from PIN to Password,

& now the phone doesn't even accept the new password.

So i'm locked out of my phone too.

& i didn't even have a backup of my Phone.

I'm trying to flash different recovery via fastboot.

but nothing's working.
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
If your phone is booting, the best is to save everything on your computer, including the titanium backup files, and to format your whole data partition (to ext4 would be a good idea) to remove encryption.

If your phone is not booting and not accepting firmwares through fastboot you're screwed as I was some weeks ago and no choice but to format. My photos are all backed up on two clouds so nothing really loosed. And by chance I had a 2 weeks old titanium backup on my computer.

I didn't try to encrypt again and will probably not try it even if I think it should work.
[OnePlus 3 & 3T Cross Device Development] Striatum_bdr:
Great, sad it didn't exist for me 2 months ago.

Just to know did you try also Dragon modded Recovery (see Omnidragonthread) ?
[OnePlus 3 & 3T Cross Device Development] osrox:
No
[OnePlus 3 & 3T Cross Device Development] theCroh:
Did you check if the TWRP recovery now works with the 5.0.3 firmware?
[OnePlus 3 & 3T Cross Device Development] mk_1996:
I dont know about the official twrp recovery but the bluespark one works fine with 5.0.3. i am encrypted and i came from oos to nitrogen os with no encryption problems.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Sure, official TWRP works, the problem he had happened by upgrading OOS (firmware) from an old version of the most current one, at some point there where changes made to the source code, on how the encryption is handled by OOS Oreo iirc, this can potentially mess up the decryption process but once you're on latest or at least current OOS Oreo firmware there shouldn't be an issue - I never had a problem of this sort, I flashed OOS Oreo with "Nougat TWRP" and updated to "Oreo TWRP" later on while already running Oreo, I flashed each and every OOS firmware version, again no problem, this is a specific flaw under specific circumstances, typically when you jump firmware versions - at least that's what I observed...