yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] danieldmm:
Are you sure? Because it's stock on TWRP for OPO

Enviado do meu ONEPLUS A3003 através de Tapatalk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
there is no new upstream structure, if you encountered an issue it might have been a flaw introduced in upstream that was probably fixed by now.

it would be insane to change the format/structure of a filesystem after it's introduced into mainline Linux (and has been since 2013)

to answer your final question, tylenol cold & sinus day/night, one tablet every 6 hrs

i recently asked OnePlus for a development device to work with, waiting on a response, franco's idea
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] 954wrecker:
You definitely deserve it for the amount you do to help the community
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MrMeeseeks:
Sorry to spam the thread but lol. ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] eng.stk:
There are new ondisk operations on mainline 4.10 backport you're using, just check what you merged. Also arter talked about this. And this new mountpoint options are default on the 4.10 backport, so they will be used automatically.

Those backports are not no kernel.org 3.18 branch.

There are no issues (beside the needed revert to fix 4.8 backport deadlock) with the backport itself, but will create issues for previous f2fs version (like the one present in OOS stock kernel which matches Linux 3.18 baseline)

This was what I encountered upon testing, but if it's not useful, carry on.

And yes, not the first time that those backports create backward compatibility issues, just check motorola devices and others.

From a time, even raised issues from the version on kernel changes that needed to match the binary mkfs, and not being also backward compatible.

This kind of stuff happens frequently on f2fs, not a new topic.

I was asking about ROM on the device, but seems like you have a cold instead ;p

Get better mate!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] myfreexp:
As the setup of my phone has almost been completed, I'd like to start again from scratch with TWRP (phone is ancrypted and not rooted yet). So which version of TWRP should I use?

Another question which nobody did answer yet in any forum where I asked this: Why should I want to have an unencrypted phone, what exactly is the benefit?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] djsubterrain:
It seems like a new version, that will fix problems existing in the device at the moment, is coming, I would wait for that, I would guess it'll be a couple of days at the most with the work rate that seems to be going on.

The encryption is apparently obligatory in all new phones now, it pissed me off too, I didn't have it by default on my OnePlus 2 and it's been a major headache on the 3T...so far.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Encrypted is good for security, even if you unlock your bootloader and mod your phone with TWRP and stuff since a thief would need your password to access your custom recovery. If it's unencrypted and bootloader unlocked, people basically have full access to your device through recovery. The problem is since encryption is a relatively new standard for Android and other things are changing too, TWRP needs to evolve to work with those changes as well. Some people are annoyed by those changes required to mod their new device, that's really it. Previously, encryption on certain Android devices (like the Nexus 6) reduced I/O performance (read/write speeds) significantly. That's not the case with newer devices like the 3T and Pixel, since the improved hardware (I think Qualcomm crypto something) means there's negligible difference in performance between encrypted and unencrypted.

Currently, the only reason to decrypt your device would be if it is needed for some special mods to work, like multirom. Some other people are more conservative and simply don't want to deal with this new fangled encryption thingy that they think makes modding harder, and if they don't need encryption, might as well disable it right? My device is decrypted right now because I use MultiROM and technically yes, it is insecure. Anyone with physical access basically owns my phone (they can even delete lockscreen files from recovery) , but I don't really care and just take extra care to not lose my phone.

So basically stay encrypted if you value security, and decrypt if you don't care about that extra hassle for security or want to use MultiROM.

Edit: Hmm I'm not sure if encrypted devices are still secure if your bootloader is unlocked, maybe you could use ADB/fastboot to still break into the device? You'll have to ask someone else for that, I haven't got a clue.

Also there are two types of encryption on Android, full disk encryption (older one) and file based encryption (newer one). Read up on them if you want to know more.

Also remember all these security stuff only makes it harder to break into your device, which deters people. Given physical access and enough determination, no security method is perfectly crackproof (atleast currently). It is often simpler to use social engineering to trick Pepe into revealing confidential info than actually defeating digital security measures.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
http://build.twrp.me/twrp/twrp-3.0.3-0-oneplus3t.img

that's actually 3.0.3-1, report back on if it's alright for you or not please, it will appear as 3.0.3-1 soon on twrp.me site if everything is good.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] myfreexp:
First of all, thanks for this comprehensive response. It's the first and only one to this issue that I got so far.

The reason I've been asking is that my previous device (Galaxy S5) got stolen and I'd have felt much more comfortable if the data would have been encrypted. Fortunately, nothing bad did happen so far.

"Multirom" is the ability to boot different OS on the same phone, right? I don't think that this is of any importance to me.

This is indeed an important question, as my bootloader is unlocked of course (otherwise I couldn't deal with TWRP at all, and even for => this procedure from OnePlus an unlocked bootloader was required).

As this is a forum and I'm not asking a specific person: Anybody here who has an answer to that...?

Because if an unlocked bootloader would give access to anything anyway, then I can as well disable it at all.

---------- Post added at 02:22 ---------- Previous post was at 02:14 ----------

Especially as the algorithm did change with each OS version (3.5.1 => 3.5.3/4 => 4.0.x), as far as could understand. Did I understand this correctly...?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MrMeeseeks:
Restore fails to boot. I can't even get into the boot sequence long enough to get a logcat.

Edit: I pulled some logs in TWRP. Don't know if there is anything useful in them but that's all i can get.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] tfae:
After testing the beta5 and beta8 everytime I reboot to recovery the phone stays on black screen with the notification LED as white.

The only way to enter TWRP is from fastboot, even after flashing this one.

EDIT: in beta8 everything worked OK, including decryption. The only issue is the one mentioned.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
adb exec-out tar cz /sys/fs/pstore > pstore.tar.gz

after failed boot, inside twrp, upload for me
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MrMeeseeks:
here you go
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
err... adb exec-out tar c /sys/fs/pstore > pstore.tar

i don't know why but exec-out is not working in twrp now, so that gzip is totally broken
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MrMeeseeks:
Ok, that makes sense because i couldn't get it to uncompress.

I had to factory reset in order to boot. I installed stock 3.5.4 in twrp but it still failed to boot. Then i tried the factory reset and it finally booted.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Why should the procedure from OnePlus require an unlocked bootloader? You can flash signed stock Roms with stock recovery. Adb sideload also doesn't require unlock as long as it's a vendor signed zip.

About encryption, if you don't have the password, you cannot access data. If the password isn't too simple or too short I don't see any way to get to your data.

Sure a thief can delete your data and use the phone from scratch, but he can do so either unlocked or locked.

About the "flash something to bypass Lockscreen" - sure you can bypass Lockscreen this way, but again, without the password for the data partition you cannot boot until Lockscreen. No matter if locked or unlocked.

I also suggest to get a theft protection app. I use Cerberus. As long as your phone is still on and has network connectivity, you can locate it, get pictures of the thief or remote wipe it. Once thief switches it off, your encryption kicks in. You cannot locate it anymore, but your data is save.

Afaik Cerberus and some other theft protections might even survive a factory reset/wipe so you can locate your phone after the thief did reset it. Never tested it looked deep into this though. Also it requires root to set this up.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.3-1-rc2-oneplus3t.img

back to beta1 f2fs.... hopefully this will fix all the problems you guys are having

for those on beta5-beta8-rc1 that are using f2fs, you might want to back it up on those twrps, copy the backup and internal storage to your pc, format data to ext4, then flash rc2, then format as f2fs from rc2 (nope nope keep it ext4, f2fs sucks :)) and restore your data and internal storage

yeah...it's a lot of work, probably not necessary but if you run into problems it might fix it

for everyone else, ex. coming from official twrp or beta1-beta4, you should be fine to just flash it no problem from:

[Install] -> [Install Image] -> twrp.img -> [x] Recovery -> [Flash] -> [Reboot] -> [Reboot Recovery]

i hate f2fs
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] sator02:
Thanks for the update

Sent from my MI 5s Plus
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Boots and decrypts.

I hope I don't have to reformat my data partition. Never really did anything with the test builds except test decryption.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Hello guys,

When I update to beta1, TWRP ask for password and me last password doesn´t work, so I must click cacncel and swipe right to enter TWRP but I can´t access iinternal storage (but USB OTG works fiine) so I can´t wipe dalvik or install a zip file....

What can I do? I don´t know what is causing this issue and is very annoying.

I found a beta RC1/RC2 (equivalent to beta8/beta9 maybe) and some users reports that it boots and decrypts. Should I test RC1 or RC2 for try to solve my issue?

Thanks in advance.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] sebfar:
I think you must format data
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] timobayl:
Try beta8 or rc2.

I had the same Problem as you. With beta8 i can enter twrp. So far all works.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Hello and thanks,

beta1 is RC1 as OP said in this post ( https://xdaforums.com/showpost.php?p=70565750&postcount=905 ) Should I try RC2 or RC1?

---------- Post added at 11:20 AM ---------- Previous post was at 11:19 AM ----------

Hello,

Format data doesn´t works for me or solve anything......
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] timobayl:
I tried only beta1 and beta8.

But i think rc2 is better than rc1.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cultofluna:
Rc2 is the latest...It works properly...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Thanks for the fast answer, preparing files in internal storage and test it ASAP (RC2).

---------- Post added at 11:47 AM ---------- Previous post was at 11:47 AM ----------

Thanks for you also going to flash RC2.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] eng.stk:
I told you...

There's nothing really wrong with f2fs, you can use the 3.18 kernel.org baseline + the couple OOS patches, it's solid.

The issue is that those backports introduce changes mainly for PFE (rather useless in our device) and new on disk operations, so it renders backward compatibility troublesome.

The real fun will start when people start to test ROMs with those updates and don't understand why they can't boot into twrp and mount data, why can't use stock ROMs etc without format their data partitions.

Honestly it would be all around better if everyone on the forum would stay away of f2f2 backports.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Ok flashing RC2 solves all my problems, now when I boot in TWRP it asks for my password, I type it and decryption works properly!!! Now it seems that i can backup, restore and install zis.

Really really thanks to all.

:D :D :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] z0rk:
TWRP stays on the splash screen, screen goes black afterwards and does nothing. Tried to reflash TWRP 3.0.3.0 and 3.0.3.1-rc2 without success. Any advice?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] matust:
How long did you leave it on the boot screen? Mine needs a long time on the twrp splash screen before it launches
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
If you provide us logs and tell us about the ROM you are using, you might get an answer and maybe help others with similar problems.

With little as what you say you cannot expect any real feedback.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] z0rk:
I cannot provide logs if I even cannot enter TWRP, afaik.

I was on RR ROM, wanted to flash something else but never succeeded in entering TWRP.

I went back to completely stock, and began again, because my internal storage seemed to have issues (showed way more in use than actualy was). So now it's back OK
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] eddy4823:
Flashed SuperSU from TWRP. It automatically booted in system but I dont have root access. Why is that ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] uaiclout:
I'm sorry I don't understand what you mean :confused:

Will the f2fs problems be solved - should/can I use f2fs again --- and what about backports

Or should I stay on ext4
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] B3501:
Because f2fs breaks Supersu?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
I've been hearing that OP3T is one of the few devices that don't break SuperSU on f2fs, is this not true?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Decryption worked fine while entering TWRP? You are using latest super su?

About f2fs, I got it running fine with super su.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] B3501:
It breaks it for me on custom Roms, with stock I got sim card failures.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] the_rooter:
Sound like user error. Works fine here as well

---------- Post added at 10:51 AM ---------- Previous post was at 10:36 AM ----------

Can't find anything on this but which of these is the device already on if no changes were made
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It's true: [MENTION=631273]Chainfire[/MENTION]'s SuperSU v2.79 is working like charme, since oos-3.5.4 (first version I rooted, properbly worked before, too); now on 4.0.1 - always with encryption on f2fs with pin as pasaphrase, if that matters in any way.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yung40oz84:
does this use F2FS backported from 4.10 kernel??
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
No, the latest RC2 build was downgraded (on purpose) to be compatible with the kernel 3.18 included in OxygenOS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yung40oz84:
OK, so there is another recovery that has 4.10 back ported, I formatted f2fs in that recovery, if I use this recovery will it still work correctly?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
No, you will not be able to boot this TWRP. The 4.10 backport is not compatible with the 3.x versions, and also not compatible with the OOS kernels. Therefore [MENTION=5672995]jcadduono[/MENTION] has pulled the 4.10 backport, as did [MENTION=3873953]eng.stk[/MENTION] of the blu_spark TWRP version.

The only way back, unfortunately, is a reformat. I've done this today, so I speak from experience. ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Sorry, I'm not an native English speaker, so this might be noob, but I'm confused:

When I read "...has pulled the 4.10 backport..." I understand, that he has fetched and merged the backport commits (since git's manpage states pull is nothing else, then fetch followed by merge). But from the context I guess, you mean he has reverted the backport commits. What should I understand? I bet the latter, didn't I?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] tdamocles:
Will I have a problem restoring a nandroid that I did with beta 1 if I'm on rc2 version?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
I mean he reverted back to the older version of f2fs. You understood correctly. :)

So, beta8/rc1 = 4.10 version, not compatible with older versions of f2fs (possible data corruption) and OOS kernel

rc2 = original version, compatible with OOS kernel, but not with 4.10 version (can't read at all)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
https://github.com/jcadduono/android_kernel_oneplus_msm8996/commits/3T-twrp-6.0

To check your kernel version, use "cat /proc/version" in TWRP's terminal or adb shell. Ex. Linux-x.x.x-twrp-oneplus3t-2.1
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Tried to resist since yesterday... ...can't any more...

If the updates merged to regular linux kernel does not only change the api, but also the fs structure itself in away that the fs is notmreadable across different versions, I would consider this as pre beta, but not ready for production use. Not to speak of mission critical usecases, like holding /data/system... ext4 on the other hand is tested and running for more then a decade, and it's still backward compatible to ext2.

If the samsung devs, want to learn how to add features without breaking fs structure and backward compatibility, they should consult the commit history of ext2 through ext3 to ext4, reiserfs or zfs (completely different approach, similar to database feature updates). Perhaps this was expectable, by an fs designed in notime (compared) to others, just to prove its supiriority in benchmarks...

I know, this is quite polemic - but I couldn't resist.

f2fs corruptz - ext4 rulez! ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] flodroidnexus:
Tommorow my New 3t is comming. I want to install ressurection remix Rom straight ahaed. Whats the steps you suggest

Gesendet von meinem Nexus 5 mit Tapatalk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] djsubterrain:
To be perfectly honest, I would really wait a week or two until the TWRP and RR versions are a lot more solid and hopefully OnePlus will have released some useful source by then too.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] weakenfalls01:
Hey guys,

I'm not really sure if this was mentioned before, it probably did and I missed reading it but currently I'm having issues restoring my backup which I did with twrp beta1 for the 3T.... I'm currently on 4.0.1 and I was trying to run tugapower ROM so I can switched between custom Roms and stock oxygen but getting error message when trying to restored it thru TWRP.....Any I deas as to why this is happening.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] the_rooter:
i am confused the way people are talking that the devices comes with ext4 format, but researching some i found a few articles stating the 3t came with f2fs unlike the 3.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Yes, F2FS is the default. What's your point? :confused:

If you want ext4, you have to manually switch to it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] the_rooter:
There really isn't a point just a question.

I formated it a few days ago and /system and /cache was changed to ext4 but /data stayed at F2FS. Per the screen shots should everything be the same?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Did you click on change filesystem in the data partition screenshot?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] the_rooter:
That's the wierd thing. I didn't do any of that. What I did was format phone then went back into recovery and completely wiped everything from my phone so it says no OS installed. Went to the part where u click on what to wipe. I clicked all but the otg and wiped. And completely cleared phone out and installed stock 3.5.4 and just now after reading this thread I found out how to change the format and that's what I found.

---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------

Should they all be the same format or will it hurt with each one different.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
The default is data f2fs and everything else ext4 for the 3T and this recovery. If you want to change data to ext4 just click on change filesystem and choose ext4.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
Won't hurt at all and what you describe is actually the factory default. I wouldn't worry about that.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] the_rooter:
Ok so last question and promise I will be out of your hair. For now lol. Right before I decrypted my device I had to flash no dm verity script made by the same developer of this twrp. I always completely clear out my device deleting everything including the os to start fresh. Now I will be flashing a new rom this weekend. Would I need to flash the dm verity again or is it only if by Chance my device gets encrypted again
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
You will now find a new section in the first post of the thread containing a zip that will flash on any device to change the default filesystem in recovery for your data partition between f2fs and ext4.

This will allow you to decrypt your filesystem of choice.

Enjoy!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Namolas:
Thank you for this! Two questions;

- Is this equivalent of us manually changing the filesystem ourselves in TWRP?

- You'll probably want to put a disclaimer that changing the file system will wipe all data. Seems obvious I know, but better safe than sorry?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I think it just changes the fstab so you can decrypt the filesystem. You still need to format the partition to whatever filesystem you want manually.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Morphine1:
I blacked-out the newest TWRP 3.0.3-1 for our threetee.

https://goo.gl/0IXlPo

The theme was edited and made by [MENTION=2231635]etoy[/MENTION], a great oldschool xda friend. I just repacked it with our original img file.

Enjoy:cool:

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Excellent! Can you release it in the form of a TWRP theme (I think there's a format like that?) so that the theme is independent of the recovery version? Because I'd like to use this theme with the multirom recovery.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Morphine1:
I will think about it.

You could also bring me to the said multirom recovery so that I can repack it with the theme for you.

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
https://xdaforums.com/oneplus-3t/development/unofficial-multirom-v33-oneplus-3t-t3511160/page31