yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] thaidroid:
I'm on Dynamic twrp but have never installed a dynamic build (currently on Alpha droid with 4,4 Kernel).

What is the procedure to go back to standard twrp-3.7.0_12-2-cheeseburger_dumpling (assuming it supports 4.4 kernel Rom's)?

Can I just flash the Image in dynamic TWRP? Do I need to factory wipe or Reformat anything(Data F2FS currently)?
[OnePlus 5 & 5T Cross Device Development] sjamie:
Just flash the new TWRP, wipe caches and reboot into the new TWRP.
[OnePlus 5 & 5T Cross Device Development] jauhari:
Thanks you this one Solve my issues
[OnePlus 5 & 5T Cross Device Development] tobby88:
*bump* it's still not possible anymore to install LineageOS with GApps on the official recommended way with latest TWRP. Any ideas?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Have you tried the latest official twrp build?

I have a Cheeseburger and I can install los20÷Mindthegapps without any problems
[OnePlus 5 & 5T Cross Device Development] tobby88:
This was referring to your latest build. And to your statement from October:
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Well, you may not have seen it, but my latest build is the official one, released in December, https://xdaforums.com/t/recovery-tw...ger-dumpling-11-12-2023.4351795/post-89213270
[OnePlus 5 & 5T Cross Device Development] tobby88:
Ahh, I'm sorry... Looks like I missed that 🤗
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Well a few days ago an official build was released, the latest updates to the device are:

- Unified build (standard/dynamic)

- Compatible with Android 14 and below (A13, A12)

- Fix for installing MindTheGapps on standard partition Roms

- Added backup option for system and vendor partitions

- Updated with the latest patches merged into the a12.1 branch

OnePlus 5/5T

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

More information can be found in the release post: https://twrp.me/site/update/2024/02/21/3.7.1-released.html

* If, after installation, you receive the error message "Failed to mount '/metadata' (invalid argument)" during backup or any other recovery action. Go to the "Wipe" menu, press "Advanced", select "Metadata" and confirm with a swipe to the right
[OnePlus 5 & 5T Cross Device Development] sjamie:
The new build works perfectly. Thank you again, kind sir! 🙏🏽
[OnePlus 5 & 5T Cross Device Development] stanleylee:
Hello, I have the original OxygenOS 10.0.1 on my phone and I would like to install LineageOS 21 for my OnePlus 5T. I don't like Lineage Recovery and I would like to use TWRP, please can you tell me if I should use the official "twrp-3.6.2_9-0-cheeseburger_dumpling.img" file since I am <A11. And once I installed LineageOS 21, I shall update the TWRP to "twrp-3.7.1_12-0-cheeseburger_dumpling.img"? Thanks in advance for your help.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Once you have the necessary files on your sdcard and you've removed the screen lock on the system (pin, password or pattern), you can install only the latest twrp (3.7.1), reboot into recovery and then install los21.
[OnePlus 5 & 5T Cross Device Development] stanleylee:
Thank you. So I can go straight and install twrp (3.7.1 A12) even though my phone is still on the original OxygenOS 10.0.1 (<=A11)?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
If you leave your device unlocked, yes

And the first step is to unlock the bootloader, otherwise you won't be able to install anything.
[OnePlus 5 & 5T Cross Device Development] stanleylee:
Thanks again. I will leave the bootloader unlocked.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
I'm talking about not using any screen lock (pin/password/pattern) while on Android 10, but after installing Los21 you can.
[OnePlus 5 & 5T Cross Device Development] stanleylee:
I see, thank you very much.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
New build released

- New kernel 4.14.314 thanks to @robertogl

- Compatibility with Roms with keymaster 3 and 4 (e.g. Evox 8.4 and 8.5)

- Removal of additional entries from "super" partitions for backup on ROMs with non-dynamic partitions.

- Data formatting will not force the use of f2fs on the /data partition, on roms that have both options.

OnePlus 5/5T

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me
[OnePlus 5 & 5T Cross Device Development] Bubble-be:
I have some strange issue. I updated to the latest version just to be sure, but I'm getting the same.

On opening I get a lot of red text with these messages:

Updating partition details...
Error opening: '/data/data/S2NA3BATPQx7yQYFTtLuwUICgpQvgzp,2Y3rpzYXwTI/2QUNnMlm2Lzsszj3jihli3bvY+qOQTan/sOA+sQ5c59i7W1T2pLryop75d8lkTLwCI0CYiD/+t,MrNGJcfPsD1RoudFUfTjb+jUauDrRcvLCyvgIO49qjJ8Z3XYmBYOKKg9SvX5Ai4kiVhwxdbt8Wq0uNF8xu1XQgaDs8o7bvXXsb,ravgHTbOrpyMfZ06wJRrprSo,LtajOgYZxPDzUQ95kgLadbcSAmRvqzqvSFd1JqaAD+lJk6aVSP7gcjYXFF8aZ942q8jpBS9JXVA6YlaAi8J6vAFhcaDomoAVBjG5WK22HhvOKkfy6loc7RByaGuFO' (No such file or directory)
I:Real error: Unable to stat

For some reason my data partition is also seen as 1061063MB, making it impossible to backup.

I have already formatted the data partition since the problem first showed up. Before I was on Derp, now on Elixir 4.1 - so same kind off base -> A14, 4.4 kernel.

Any idea?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
For some reason the decryption process is starting late on your device, in the end it decrypts and despite the red messages you shouldn't have any problems performing any function in TWRP. Did you happen to do a dirty flash between installing the different ROMs? The ideal is always to do a clean flash when changing ROMs.

You mentioned that you formatted the /data partition, in theory this should solve the problem, after the first boot. In any case, I need to investigate further, in which build of Derp is this error appearing?

Regarding the size of the /data partition being larger than 1tb, this is a KSU problem, it has nothing to do with TWRP, more information and a tip on how to make the backup are in this post.

OnePlus devices showing abnormal storage with new 1TB sparse image · Issue #1411 · tiann/KernelSU

Please check before submitting an issue I have searched the issues and haven't found anything relevant I will upload bugreport file in KernelSU Manager - Settings - Report log I know how to reprodu...

github.com
[OnePlus 5 & 5T Cross Device Development] Bubble-be:
Ah yes, I remember reading some command like that and it was the issue. It's backing up now.

I was using Apatch before, so I'll remember to run

ksud module shrink

before a backup. Got it.

To complete the story: I was running latest derp 18/04, but had some issues with maintaining a stable bluetooth connection to my Garmin Edge. I went over to AOSP14, I don't remember if I tried Xkernel directly but that did something funky to my /data partition. I was unable to mount it in recovery.

I was happy to have the most important folders backed up and wiped data, but apparently it didn't solve all the problems.

Do you think that removing/readding pin and/or wiping data again would help - although it doesn't really seem a problem in the end?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
The issue of not mounting the /data partition is due to AOSP14 which has some patches in the kernel that are not compatible with previous versions of TWRP, this was one of the reasons that led me to update the recovery. 3.7.1_12-1 should mount the partition normally.

Anyway, I'm going to test both Roms (Derp and Elixir) to see if I can reproduce your problem, in theory a /data wipe should be enough to solve them, if you only remove the pin it will still be encrypted and the messages will probably continue to appear, what should really solve it is to change the /data partition to f2fs because then it will be unencrypted and the errors won't happen, of course if you use a ROM that doesn't have encryption enabled in f2fs lol.
[OnePlus 5 & 5T Cross Device Development] Bubble-be:
Since the phone is running fine apart from those messages, I'm holding of until I feel a need to clean it up. It does take big time backing everything up and setting it up again afterwards.

I don't think I'll be going f2fs as it won't be as flexible, limiting my rom/kernel options in the future.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Ok, fair enough, just to update you, I tested both roms, with clean installs and these messages didn't appear lol. When you can, send me the logcat so I can see if I can find anything.
[OnePlus 5 & 5T Cross Device Development] Bubble-be:
Yeah, I guess it was with the excursion to AOSP and the incompatible TWRP that it/I messed it up.

I attached the recovery logcat (zipped).
[OnePlus 5 & 5T Cross Device Development] iamprashantjain:
Hi developer.

I'm using pixel experience 13 plus rom and not rooted on OnePlus 5.. which twrp should i install and do i need to root my phone before installing?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
You can use the latest official version and you don't need to root the device.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Sure, I made a test build, on the 12.1 branch. Please see if it works now.

Note: Decryption is still not working

LINK REMOVED. Note 2: I removed link because I found a bug that isn't allowing other roms to be installed
[OnePlus 5 & 5T Cross Device Development] psychoela:
I'm not use lock screen.
[OnePlus 5 & 5T Cross Device Development] metahex12:
Hi, it is not decrypting on Android 12. (ROM: LOS 19.1)

Device: OP5T

(tried with all versions, 12.1 test too)
[OnePlus 5 & 5T Cross Device Development] Exodusnick:
@metahex12​

try no-verty as in lineageos18.1 ,

maybe it works with this

Download no-verity-opt-encrypt All Versions

We may always face the encryption issues when we plan to use custom recoveries in our mobile. This is the place where no-verity-opt-encrypt helps us out.

www.androidinfotech.com
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Yeah, I forgot to replace kernel, sorry. Try it now with this version, please:

twrp_cheeseburger_dumpling_3.6.1_11-v2.img
[OnePlus 5 & 5T Cross Device Development] faoliveira:
As I wrote in the first post, you need to remove the screen lock for decryption works. None of the TWRP versions, so far, can fully decrypt Android 12.x Roms.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Apparently everything is ok with data in F2FS, so I will release a new update with that support and a test version based on the A12.1 branch, which still doesn't decrypt data, but everything else should be ok.
[OnePlus 5 & 5T Cross Device Development] js-xda:
I can confirm that your A12 cheeseburger TWRP version on works as you describe - thank you!

Just curious, is there already an idea for a full solution regarding FBE with active PIN or similar?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Thanks for feedback, but AFAIK, only pixel 3 has decryption fully working on twrp 12.1, isn't an Oneplus 5/5T specific issue . TWRP devs are working on it, but no one knows yet when it will be fixed. I've been doing some tests, but no further progress.
[OnePlus 5 & 5T Cross Device Development] kirknado18:
You have to format data
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Builds updated on 29/05/2022 (3.6.2-v1)

List of updates:

* sload_f2fs: update code for correct binary name

* release: twrp 3.6.2 a11

* MtpServer: create new ffs handle if current one fails

* openaes: fully remove from build with encrypted backups disabled

https://gerrit.twrp.me/q/project:android_bootable_recovery+branch:android-11

Fix:

* ADB Sideload

(I had no idea it was broken because I didn't use it until I tested it yesterday lol)

Note: I've uploaded a new test build to the A12.1 branch, with the sideload fixed, but decryption remains the same.
[OnePlus 5 & 5T Cross Device Development] Agret:
Tried 12.1 test3 on my OP5T running LineageOS 19, USB doesn't appear to function at all. Can't detect with adb devices or use adb sideload.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Yeah, I found a little problem, try this version please and let me know if it worked

twrp_op5_op5t_3.6.2_12.1-test-v4.img
[OnePlus 5 & 5T Cross Device Development] zagzag99:
Oops, I'm in a little trouble.

How will I flash this if adv sideload fails and otg also? ... And I can't decrypt because of MDM preventing removal of password....

Fingers crossed fastboot will work.
[OnePlus 5 & 5T Cross Device Development] zagzag99:
Flashed via fastboot.

But still sideload doesn't work.

ADB devices works in recovery until turning on sideload.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Is MTP working? can you generate logs? What appears when you type adb devices? If you can't get the logs, please send me screenshots and all the steps you're taking, including the ROM you're using.
[OnePlus 5 & 5T Cross Device Development] zagzag99:
Using LineageOS 19.1

In the end I got the sense that I can cancel decrypt attempt and flash from /data/lineage_updates

But anyway I tried sideload again.

I'm using a macbook pro (m1) and found that if I connect to port on the right side it won't do `adb devices` in recovery or `fastboot devices` in fastboot.

but if I connect to the left it did manage to do it. (using A11 3.6.2-v1).

when using A12 3.6.2-12-v4

This is what I tried, and what it produced.

❯ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
10499fc7 device

❯ adb reboot recovery

❯ adb devices
List of devices attached

❯ adb kill-server
❯ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

❯ adb sideload lineage-19.1-20220606-nightly-cheeseburger-signed.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
[OnePlus 5 & 5T Cross Device Development] Agret:
Thanks man, works great.

>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
2da47456 recovery

>adb sideload MindTheGapps-12.1.0-arm64-20220605_112439.zip
Total xfer: 1.02x

>adb sideload Lygisk-app-release.zip
Total xfer: 5.05x
[OnePlus 5 & 5T Cross Device Development] thaidroid:
Fails to mount Data on my OP5T F2FS switched to old recovery and now OK
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Probably one of your ports is USB 3.0 and the other is USB 2.0, it is always recommended to use 2.0, but I have to analyze it better because ADB works for some and not for others. For now use A11 version
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Yeah, you're right, I'm trying to figure out if it's a branch specific problem. Use A11 version instead.
[OnePlus 5 & 5T Cross Device Development] remedya:
Having run my OP5 with TWRP recovery and the PixelExperiences 12 ROM, I had the TWRP encryption issue with OTA updates and I also could not re-lock the bootloader; re-locking the bootloader bricked the OP5.

Now I have switched my OP5 to LineageOS 19.1 with the LineageOS recovery and I am able to re-lock the bootloader plus OTA updates work even with the OP5 locked with a strong password.
[OnePlus 5 & 5T Cross Device Development] raj102:
I was also facing same issue. Follow the below guide. I was able to solve the issue.

[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)

You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!

xdaforums.com
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Problem solved, if you want, you can now use version A12.1 v.5

Can you test if in this new version you can use ADB?

And for those who remain encrypted finally decryption works.

https://twrp.zulipchat.com/#narrow/stream/290970-development/topic/twrp-12/near/286723830

I don't know if or when this functionality will be ported to lower versions, so for now only TWRP A12 will be able to decrypt A12 ROMs with no need to remove pin/pattern/password.

twrp_op5_op5t_3.6.2_12.1-test-v5.img
[OnePlus 5 & 5T Cross Device Development] Nimueh:
How about encrypted A10 or 11 roms? When I tested PA (11) 2 weeks ago and wanted to go back to crDroid 7.18 (11) using the nandroid that twrp_cheeseburger_dumpling_3.6.2_11-v1.img created it flashed the backup without errors but the device only kept booting back into TWRP. After a clean flash and setting everything up again I saw a different backup method mentioned here (only backup data, boot into fresh rom then restore data or something like that) but I never tried that. I don't even use a screen lock btw, just the normal rom encryption.

Are "normal" nandroids on encrypted A10/A11 roms possible with twrp_op5_op5t_3.6.2_12.1-test-v5.img now?
[OnePlus 5 & 5T Cross Device Development] daywalk3r666:
can confirm this twrp finally decrypt my data on dumpling. thx for the port
[OnePlus 5 & 5T Cross Device Development] zagzag99:
Thanks, I confirmed ADB and Sideload working now in recovery.

Also decryption with PIN.

Perfect!
[OnePlus 5 & 5T Cross Device Development] TheVoice70:
can confirm :

it works ;-)

EVERYTHING !!! ;-)

many thanks to the dev ;-)
[OnePlus 5 & 5T Cross Device Development] Exodusnick:
I can also confirm .

thanks dev.
[OnePlus 5 & 5T Cross Device Development] SchmidtK:
Can also confirm, works fine, thank you very much!!!
[OnePlus 5 & 5T Cross Device Development] manuelschmidt785:
Sorry if it was already answered but does the decryption also work for ext4 partitions or only f2fs?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
I personally haven't tested a nandroid backup yet, I prefer to backup only data and do what you mentioned, install the old rom and restore only data, for me it works, but I always remove lockscreen before starting the backup and before restoring it.

Even so if you want nandroid, you can test with these recommendations:

- If you have changed your data file system, going back to old fs before restoring.

- If this is not the case, but you are encrypted, it is recommended to remove any lockscreen before starting the backup and before restoring it.

- Also for system and vendor restore only images (system_image and/or vendor_image).
[OnePlus 5 & 5T Cross Device Development] faoliveira:
A12 recovery works for either of the two file systems, but actually decryption is for ext4 only, f2fs is already decrypted.
[OnePlus 5 & 5T Cross Device Development] TheVoice70:
Also for ext4
[OnePlus 5 & 5T Cross Device Development] Nimueh:
I have wayyy too many apps with special permissions and change too many rom settings to risk having to start all over. For example - the covid app that has all my vaccinations saved in it. If I flash a rom and restore the app via Migrate etc, even with data and everything, it still crashes when I start it. So I end up having to clear data and scan all the certificates again. Same with my Netto shopping app, it too refuses to start when restoring from a regular Migrate backup.

That's why I want to be able to make a full nandroid of my current rom so that I can test other roms and go back easily. Pretty sure JUST restoring data wouldn't help me there. I don't use any lockscreen security so that won't be an issue, filesystem is always whatever the rom has.

If anybody has made a nandroid, restored it and was able to boot into the rom, just as he/she left it, I'd appreciate if you let me know.

Thanks in advance (y) :)
[OnePlus 5 & 5T Cross Device Development] TheVoice70:
Swift Backup – Apps bei Google Play

Eine einfache, schnelle und intelligente Sicherungslösung für Android-Smartphones

play.google.com

I use this ... it`s "safer" ;-)
[OnePlus 5 & 5T Cross Device Development] Nimueh:
Read again what I said I need - Swift also doesn't backup device settings, and no matter which app I use to backup my apps, some will NOT work on the new rom/device. ;)
[OnePlus 5 & 5T Cross Device Development] leoinj:
Flashed twrp_op5_op5t_3.6.2_12.1-test-v5.img, turned off puzzle lock and twpr successfully decrypted data allowing an upgrade from LOS 18.1 to 19.1 with gaps install. After booting into LOS 19.1, re-enabled puzzle lock and enrolled fingerprints. Now when booting twrp it fails to decrypt data:

"Failed to decrypt user 0. Unable to decyrypt with default password. You may need to perform a Format Data."

When attempting a manual decrypt from the "Advanced" menu in twrp, I'm prompted for a text password rather than presented with the puzzle lock prompt.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
I don't understand you very well, you removed pattern, upgraded it, and put pattern again and now you can't decrypt it, that's it? If it is, restart system, remove pattern and fingerprint and go back to see if TWRP recognizes your data. If it works, go back to system, put the pattern again and restart one more time for TWRP to see if it normalizes,If not, send me your logs, please.

I should have mentioned that I haven't tried upgrading a rom 11 to 12 yet, but I'll add this disclaimer now. :)
[OnePlus 5 & 5T Cross Device Development] leoinj:
That fixed it.

Removed pattern lock and fingerprint

Rebooted to twrp and got auto decrypt with default key

Booted back to system and added pattern lock only

Booted to twrp and got prompt for pattern at twrp start. Entered pattern and decrypt successful

Booted back to system and added fingerprint

Booted to twrp and confirmed decrypt still working

Thanks for walking me through the troubleshooting steps to get this fixed.
[OnePlus 5 & 5T Cross Device Development] updesh94:
Thanks for the updated twrp, now it can decrypt data in a12.1.
[OnePlus 5 & 5T Cross Device Development] lulli1:
Wow... My respect and congratulations! You finally nailed a working TWRP recovery with decryption for encrypted 12.1 roms. Thank you so much!

Glad that so many guys here around that don't get tired working on stuff for our cheese-dumplings. 👍😀
[OnePlus 5 & 5T Cross Device Development] Agret:
I just flashed the latest v5 and was able to succesfully decrypt my 12.1 pin code locked userdata. Didn't have to do the troubleshooting steps of removing the fingerprint & screen lock first, great job on this! Hopefully your work can be upstreamed to the regular twrp as you've done a great job solving the issues with 12.1.
[OnePlus 5 & 5T Cross Device Development] morfances:
-I have recovery twrp-3.5.0_9-0-cheeseburger_dumpling, can I update via twrp to twrp_op5_op5t_3.6.2_12.1-test-v5.img or do I have to do it via fastboot? p.S My device is decrypted and I currently mount derpfest A12.1
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Yes, you can install it by twrp itself, no problem
[OnePlus 5 & 5T Cross Device Development] AdamWill:
Just wanted to add another report of success and say thanks! I was waiting to this before updating to 19.1, awesome work. I dirty flashed lineage 19.1 over 18.1 with data encrypted, updated twrp to this build, and it's able to decrypt the data fine.
[OnePlus 5 & 5T Cross Device Development] thaidroid:
Just installed Looks good. Is there no way to fix the date and time issue in TWRP? At least I get 2021 here Official still gives me 1970;)
[OnePlus 5 & 5T Cross Device Development] sjamie:
I believe that forever bug is one we may have to live with. 😅
[OnePlus 5 & 5T Cross Device Development] Ssmiles:
TWRP is right on time for me
[OnePlus 5 & 5T Cross Device Development] Wagner.jr10:
Sem When I restart TWRP recovery my setting disappears so my time is wrong. How to fix this?
[OnePlus 5 & 5T Cross Device Development] Nimueh:
Time maybe - but check the year when making a backup for example. Some roms have the wrong year in TWRP, like ShapeshiftOS or crDroid up to version 7.17 while now on 7.18 I have the correct year again (at least on TWRP 3.6.2_11, I haven't tried the newer ones yet). 🤷‍♀️