yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] DoR3M3:
I've been having some problems with GCam messing up my camera, so I down graded to Oreo, and then when I tried to upgrade twrp I flashed a cheesburger version by mistake instead of dumpling, so now when I trie to upgrade to a newer dumping version, the screen just goes black.

How I can fix this?

THANKS
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Because I was not the official maintainer until recently and the team only maintains one official version for each device, now it is 12.1, but there is an official test version which is a copy of the above file and is on the official server if you prefer https://build.twrp.me/twrp-3.6.2_11-0-cheeseburger_dumpling.img
[OnePlus 5 & 5T Cross Device Development] faoliveira:
flash via fastboot, turn on the phone by holding the power and volume up buttons to enter fastboot mode, if you can't even access fastboot the way is to use the msm tool to unbrick your phone
[OnePlus 5 & 5T Cross Device Development] DoR3M3:
The screen was going black, because I was flashing a Pie version of twrp with Oreo firmware on the phone, my bad... :(

Fastboot works just fine, I can flash twrp.

It's been a while since I've done all this, I thought in order to flash a later version of twrp as an example you need that firmware on the phone, like it's my understanding, you can't flash twrp for pie if you have oreo firmware on the phone.

So for the moment, I can only flash Oreo versions of twrp, I can't flash Pie versions.

So all I can think is, I have to install Oreo, then do an OTA update to Pie, then I can flash a Pie version of twrp.

THANKS

P.S. 3.2.3.0 is all I can flash up to since I installed Oreo....
[OnePlus 5 & 5T Cross Device Development] DoR3M3:
YEAH I'm back.... LOL

Flashed Oreo, then did OTA Local Storage to Pie, now I have twrp_cheeseburger_dumpling_3.6.2_11-v2 back in and running....

THANKS
[OnePlus 5 & 5T Cross Device Development] thaidroid:
Just installed TWRP 3.7.0 12-1 and magically the Date and Time is Correct!! It's been wrong for five years!

You have made Magic here(y)(y)(y)🙏🙏🙏🙏
[OnePlus 5 & 5T Cross Device Development] componentchunk:
Successfully updated PixelExperience12 and reinstalled magisk from recovery twrp-3.7.0_12-1, no fastboot required!
[OnePlus 5 & 5T Cross Device Development] robertogl:
@faoliveira I didn't have time to check the source code, however I found an issue on the twrp 3.7.x downloaded here (I didn't try the official one). This issue is not present in twrp 3.6.2.

When generating OTA zip from AOSP, the first line in the updater-script is something like:

(!less_than_int(1666905863, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Thu Oct 27 23:24:23 CEST 2022) over newer build (" + getprop("ro.build.date") + ").");

On TWRP 3.7.x, this error is always returned when an update is flashed:

script aborted: E3003: Can't install this package (Thu Oct 27 23:24:23 CEST 2022) over newer build (Thu Oct 20 00:48:43 UTC 2022).
E3003: Can't install this package (Thu Oct 27 23:24:23 CEST 2022) over newer build (Thu Oct 20 00:48:43 UTC 2022).error: 3003

Of course, Oct 27 comes after Oct 20 :)

Not sure of why it's failing, but the only way to apply the update is to use TWRP 3.6.2 (or remove the check on the OTA zip).

Let me know if you need more information.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
In my tree there is a function that uses this prop to overwrite other dates, but I'll check what could be causing this malfunction. thanks for letting me know.
[OnePlus 5 & 5T Cross Device Development] robertogl:
edit
[OnePlus 5 & 5T Cross Device Development] faoliveira:
@robertogl Sorry for the delay, I already had a build without the function to overwrite dates, but first I wanted to test it and I didn't have time all week.

TWRP and any other recovery sets the ro.build.date.utc prop every time a new build is created and I won't do anything to change that. My last build is from 19/11/22 20:29:05. I used your last rom from 07/12 and it installed normally, then I manually changed the check in the script to 19/11/22 20:29:04, in this case the process stops as expected and I also tested it with 19/11/22 20:29 :06 and the rom is installed.

But if you can test it, I would appreciate it, remembering that it needs to be a date greater than (1668889745, Sat Nov 19 20:29:05 CET 2022).
[OnePlus 5 & 5T Cross Device Development] robertogl:
Ok, thanks for checking this.

I see where the confusion may be. With the latest TWRP you just provided, everything seems fine. However, with previous images, let's take 'twrp-3.7.0_12-1-cheeseburger_dumpling.img', when I boot it:

$ adb shell
cheeseburger:/ # getprop | grep -i ro.build.date
[ro.build.date]: [Thu Oct 20 00:48:43 UTC 2022]
[ro.build.date.utc]: [1670437819]

The UTC date actually is taken from the ROM (December 7 is indeed the date of my latest OS release).

The same with 'twrp-3.7.0_12-0-cheeseburger_dumpling.img':

$ adb shell
cheeseburger:/ # getprop | grep -i ro.build.date
[ro.build.date]: [Thu Oct 6 23:25:47 UTC 2022]
[ro.build.date.utc]: [1670437819]

But with 'twrp-3.7.0_12-2-cheeseburger_dumpling.img':

$ adb shell
cheeseburger:/ # getprop | grep -i ro.build.date
[ro.build.date]: [Sat Nov 19 17:29:05 -03 2022]
[ro.build.date.utc]: [1668889745]

That is indeed correct.

So, my OTA zip was checking the date using 'ro.build.date.utc' but it was printing the date using 'ro.build.date' that for some reason was different. The error was confusing for this reason.

Let me know if you need more info. The latest TWRP seems indeed to be working as expected.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Exactly, initially I thought it would be a good idea to leave the rom and the recovery dates the same, then I realized that in fact it wouldn't bring much gain and it was just delaying the recovery loading and I decided to remove everything, but I didn't have time to test lol.

As you mentioned that it was giving an error, I thought I had done something else wrong, but I really didn't realize that I forgot to put the ro.build.date in the initial function and that's what was causing the confusion lol, but now everything is ok , thanks again.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Yeah, I think that using the rom date for both properties (ro.build.date and ro.build.date.utc) is actually a good idea though.

In the latest image you are using the TWRP build dates, correct?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Yes, the recovery one, but as far as I know, only AOSP uses this prop as a check, so which would be the best scenario for you, using the rom date or the recovery date? For TWRP it would be indifferent and changing these two props I believe will not bring any significant delay. Remembering that if we use the rom date, which is how it is in the official build, whoever is in a rom with the most recent date will not be able to install AOSP, unless he edit the script.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Well, the same issue is present now: whoever tries to flash a ROM with an earlier date compared to TWRP, cannot flash the ROM, even if the ROM has a most recent date compared to the flashed OS -> even upgrades may be not possible in this situation.

By default, on AOSP, the recovery uses the same date as the currently flashed ROM (because it was built at the same time, of course) so that's why I think this behavior should be kept.

Of course, I understand your point of view: most ROMs do not have this check so at the end it is your choice :)

I may even remove the check from the ROM OTA, but I'm not sure about this yet.

Thank you for the discussion anyway.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Actually you're right, it makes more sense that the recovery date follows the date of the installed rom, regardless of the user's decision, so I'll put the two props synchronized that way.

thanks for the support

https://sourceforge.net/projects/op5-5t/files/Android-12/TWRP/twrp-3.7.0_12-2-cheeseburger_dumpling.img/download
[OnePlus 5 & 5T Cross Device Development] robertogl:
Great, thanks!

I didn't test this latest image yet, I'll try by the end of the week (very busy week :) ).
[OnePlus 5 & 5T Cross Device Development] Ssmiles:
twrp-3.7.0_12-2-cheeseburger_dumpling_REPACK_Sskulls_Blue_v1.img

File on MEGA

mega.nz
[OnePlus 5 & 5T Cross Device Development] robertogl:
This version works fine (y)
[OnePlus 5 & 5T Cross Device Development] faoliveira:
New official build has been released. This build is compatible with A12 or A13 Roms, including LOS20, AOSP A13, etc. Please do not use on Roms <=A11. https://dl.twrp.me/cheeseburger_dumpling/

However, if you are using the unofficial build 3.7.0_12-2 you don't need to switch to the official one, believe me.
[OnePlus 5 & 5T Cross Device Development] Ssmiles:
twrp-3.7.0_12-2-cheeseburger_dumpling_REPACK_Sskulls_Blue_v2.img

File on MEGA

mega.nz

Change color in blue in terminal keyboard ;-)

Merry Christmas to everyone ;-)

If you want a specific color let me know.
[OnePlus 5 & 5T Cross Device Development] AlexMirrors:
Tried this on cheeseburger flahsed to LOS20 and It worked like a charm. Many thanks
[OnePlus 5 & 5T Cross Device Development] IXI Mo IXI:
I made the same mistake as @DoR3M3 and installed TWRP 3.7.0_12-1 alongside Android 11 (LineageOS 18.1 20220516). After the upgrade from TWRP 3.6.x to 3.7.0_12-1 I booted LineageOS and now Bluetooth doesn't work anymore. Bluetooth won't turn on and the Bluetooth App keeps crashing. Additionally, the Bluetooth Adress is no longer visible in the settings.

Steps I already tried to fix the issue:

clear the App Data of the Bluetooth Settings App

downgrade TWRP to 3.6.2_9-0

dirty flashing LineageOS 18.1

reflashing Firmware & Modem

Does anyone have an idea how i can fix the error?

Thank you and best regards

IXI Mo IXI
[OnePlus 5 & 5T Cross Device Development] faoliveira:
if you can, I think the best thing would be to do a clean flash, if that doesn't work, go back to stock with msmtool and start all over again. If you can't do that, try installing another kernel, like xkernel.
[OnePlus 5 & 5T Cross Device Development] IXI Mo IXI:
A clean flash fixed the Bluetooth issues.

Lesson learned: read the instructions before flashing - even if it's "just" an update.

Thanks for your help!
[OnePlus 5 & 5T Cross Device Development] scruffy1:
will twrp-3.7.0_12-0-cheeseburger_dumpling work to update to android 13 / lineage 20 cleanly ?

i had issues previously, but later discovered my sim card was defective, and the rom may have been good to go anyway
[OnePlus 5 & 5T Cross Device Development] faoliveira:
For Lineage 20, use the latest builds, official (3.7.0_12-1) or unofficial (3.7.0_12-2)
[OnePlus 5 & 5T Cross Device Development] scruffy1:
thx, i'll give it a go perhaps, although lineage recovery is pretty coherent to use, just lacks the embellishments
[OnePlus 5 & 5T Cross Device Development] anlyldz27:
Hi. I have previously installed TWRP 3.6.1 and PE12+. I want to install the latest TWRP and LOS 20. But in TWRP ı got random name folders and cant find install images. its encrypted. How can i fix this? format data?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
On the system, remove the lock screen (pw, pin, pattern) and reboot to recovery (3.6.1) and see if the files appear, if that doesn't work you would have to format data.

But, there is a much simpler way, install the new build of TWRP via PC using fastboot.

- Reboot to bootloader

- fastboot flash recovery twrp-3.7.0...

- Reboot to recovery

- Your files should appear after you use your decryption key (pw,pin,pattern)
[OnePlus 5 & 5T Cross Device Development] giddie:
This seems to suggest that Android 13 decryption (e.g. LineageOS 20) should work with the latest TWRP. Can anyone confirm?

op5_t: update readme · TeamWin/android_device_oneplus_cheeseburger_dumpling@3860526

Signed-off-by: Fernando Oliveira <fernandoaju78@gmail.com> Change-Id: I106530274c366dfa58624ce504f23ea19f04dacf

github.com
[OnePlus 5 & 5T Cross Device Development] daywalk3r666:
Yes last official/unofficial twrp works without any problems with a13 roms
[OnePlus 5 & 5T Cross Device Development] S2_fa_007:
Hello

With an attached usb cable to a pc twrp (3.7.0_12-1 & 12-0) boots fine, without it, it stays at the splash screen.

I attached logs of a successful boot, sadly I don't know how to provide logs from an unsuccessful one.

Thanks for any help.

Kind regards
[OnePlus 5 & 5T Cross Device Development] faoliveira:
It’s a very strange error, which ROM are you using? Another question, if while you are stuck you connect the phone to the PC does the boot complete or remain stuck? I would like a log in this situation, regardless of the result to see if anything different appears, since nothing seemed strange to me in the log sent.
[OnePlus 5 & 5T Cross Device Development] Nimueh:
Make sure adb/your PC is authorized to access your device.

Then adb logcat > logcat.txt when your are stuck booting. It'll create the file in c:/adb.

At least that works if the device is in a bootloop, I'm not 100% sure if it also works when it's simply "stuck". Can't hurt to try though ;)
[OnePlus 5 & 5T Cross Device Development] S2_fa_007:
I'm running AICP 17.1 (Android 12.1).

When I connect to the PC while stuck it remains stuck, and I don't get a "usb device connected" sound from Windows.

Sometimes the screen goes black and after some time the notification LED is blue (maybe from charging).

Sadly I don't get a connection/device in adb unless it's connected when booting twrp.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Yeah, I honestly don’t know what’s going on, it’s an error that doesn’t make sense to me, I tested the Rom and can’t reproduce your problem, I also have a cheeseburger and it’s working normally with AICP 17.1 and twrp_3.7.0_12. Do you remember when this error started appearing for you? Because boot slowness is usually due to the data partition being too full or some encryption problem, but only completing the boot when connected to the PC doesn’t make sense to me, have you tested with the phone charging instead of connected to the computer to see if it completes the boot? If possible, I suggest that you do some tests: remove your lockscreen in the system and restart to recovery to see if it completes the boot, if it doesn’t work I ask that you test with another ROM, and as a last resort and if possible, I suggest that you do a clean installation, formatting the internal storage to see what happens.
[OnePlus 5 & 5T Cross Device Development] S2_fa_007:
I agree with you, it doesn't make much sense..

It started right after updating from AICP 16.1 (and TWRP 3.5.2_9-0) to 17.1.

I forgot to update TWRP, hence it was stuck, after flashing 3.7.0_12-1 it worked, but it was still attached to the PC.

(And yes, I did a dirty flash, too lazy to redo the whole setup - shame on me - but appart from Bluetooth crashing, which only needed a data clear, everything works so far).

Sadly it seems only a connection to the PC results in a successful boot, charger doesn't work.

Guess it has something to do with the data partition, and since there's no possibility to debug in this state (and I don't expect any support for dirty flashing (even if it doesn't make sense that a PC connection allows TWRP to boot)) seems I'll have to live with it :/.
[OnePlus 5 & 5T Cross Device Development] jt12345:
Could someone please tell me which twrp is recommended for A11 roms? I've tried twrp-3.6.2_9-0, twrp-3.6.1_9-0, twrp-3.6.0_9-0 and twrp-3.5.2_9-0, but I get segfaults ("SEGV_MAPERR") when I try to use the find command from the twrp terminal, I can't use twrp-3.7.0_12-0-{0,1} because of the warning ("Do not use TWRP12 for Roms <=A11), and the usual download location appears to have had all the A11 TWRPs removed. TIA, J.
[OnePlus 5 & 5T Cross Device Development] Nimueh:
No idea idea which other versions work but I'm still using "my" blue version from here and it works fine on A10 and A11 custom roms :)
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Hello guys with the release of the official build of Pixel Experience with dynamic partitions fo cheese and after some requests I decided to make available a compatible test version.

Everything should work except fastbootd, I'm still working on it.

An important message, although it works with dynamic partitions this version also works with Roms with "standard" partitions, so if you do not want to test the PE and want an updated version of the recovery can use normally.

Donwload Link: twrp-3.7.0_12-3-dyn-cheeseburger_dumpling

Flash Instructions (Copied from [RECOVERY] [UNOFFICIAL] [TWRP] [Realme 5/5i/5s] [RETROFIT DYNAMIC ROMS ONLY])

(Please Ignore recovery errors at the first installation, these errors are normal)

First installation of Retrofit Dynamic Partitions ROMs:
1. Flash TWRP recovery with Retrofit Dynamic Partitions support
1.1. If you intend to install RisingOs(*), you will need to flash the super_empty.img (**).
Go to fastboot and enter the following command:
fastboot wipe-super super_empty.img
2. Enter the newly flashed recovery
3. Untoggle "Unmount System before installing a ZIP" in Settings
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy

Update ROM from Retrofit Dynamic Partitions to Retrofit Dynamic Partitions:
1. Enter recovery
2. Flash the update
3. Reboot and Enjoy

Switch to another Retrofit Dynamic Partitions ROM:
1. Enter recovery
2. Flash the ROM
3. Factory Reset (Format data is recommended)
4. Reboot and Enjoy

Revert back to standard partition ROM:
1. Enter recovery
2. Untick "Settings > Unmount System before installing a ZIP"
3. Do "Advanced > Unmap Super Devices"
4. Flash the ROM
5. Factory Reset (Format data is recommended)
6. Reboot and Enjoy

* https://dl.nkeor.me/droid/?dir=risingOS

** If you are encountering errors while using the 'wipe-super' command, I recommend updating your fastboot.

https://developer.android.com/tools/releases/platform-tools

*** If you are switching from a dynamic rom to a non-dynamic vanilla rom or vice versa and want to install a gapps package, you'll have to reboot to recovery after installing the rom and, after reboot, you will have to install the rom and gapps again.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
And that's not all. I decided to release a version for those who are testing the kernel 4.14, this version does not support dynamic partitions. If I don't see a lot of weird bugs, when I manage to implement fastbootd, I'll release a build with the 4.14 kernel and dynamic partition support

Download Link twrp-3.7.0_12-4.14-cheeseburger_dumpling.img
[OnePlus 5 & 5T Cross Device Development] faoliveira:
I finally managed to get fastbootd working, so here’s a new version without errors, I hope.

Donwload Link: twrp-3.7.0_12-3.1-dyn-cheeseburger_dumpling.img
[OnePlus 5 & 5T Cross Device Development] Murphyung:
I just flashed this recovery now on my oneplus 5 and it is stcuk on the twrp logo.

Note: I previously had the PE recovery installed
[OnePlus 5 & 5T Cross Device Development] faoliveira:
To try to find out what’s happening on your device I need you to send me the logs
[OnePlus 5 & 5T Cross Device Development] Murphyung:
How can I do that?
[OnePlus 5 & 5T Cross Device Development] Murphyung:
So i had to flash the previous version before that that doesn't have fastbootd and it is working well for me.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Connect your device to a PC and run the following commands in a prompt

Recovery.log

adb pull /tmp/recovery.log

Dmesg

adb shell dmesg > dmesg.log

Logcat

adb logcat -d > logcat.txt
[OnePlus 5 & 5T Cross Device Development] faoliveira:
"So, was your problem solved?"
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Hello everyone, here's a new build with dynamic partitions and 4.14 kernel. The installation recommendations are the same as in the post

Dynamic instructions

twrp-3.7.0_12-4.14-dyn-cheeseburger_dumpling.img
[OnePlus 5 & 5T Cross Device Development] thaidroid:
What do I need to pick in Dynamic TWRP to get a Bootable Backup?
[OnePlus 5 & 5T Cross Device Development] faoliveira:
If it's a dynamic ROM: boot, data and super.

For a non-dynamic one: boot, data, system_image and vendor_image.
[OnePlus 5 & 5T Cross Device Development] tobby88:
Non-dynamic 3.7.0_12-2 works well for me, but dynamic ones like 3.7.0_12-4.14 not. Can't install Gapps, they fail to mount /system.

Logs attached.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Before installing Los+Mindthegapps, which Rom were you using?
[OnePlus 5 & 5T Cross Device Development] tobby88:
The same, just updating LOS 20 with Mindthegapps to a newer build.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
@tobby88 you're right, I checked more carefully and it's not possible to install Mindthegapps with dynamic recovery, sorry for the confusion. However LiteGapps and NikGapps install without errors, but as I mentioned yesterday if you're just updating LOS you don't need to flash Gapps again. I'm looking for a solution and as soon as I have one I'll post a new build here.
[OnePlus 5 & 5T Cross Device Development] sjamie:
Why don't you recommend also backing up System Image and Vendor Image for a dynamic ROM? 🤔
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Because the system and vendor partitions no longer have a fixed size, there is now a dynamic "super" partition which is a group of 5 other partitions with indeterminate sizes and impossible to generate separate images, so there is no system_image and vendor_image after you install a dynamic rom.
[OnePlus 5 & 5T Cross Device Development] sjamie:
That explanation makes a ton of sense. Thank you!

I guess my backup is probably broken now. lol
[OnePlus 5 & 5T Cross Device Development] faoliveira:
If you have a backup of a standard (non-dynamic) Rom, just install the Rom again to restore the fixed partitions and then you'll be able to restore your backup normally.
[OnePlus 5 & 5T Cross Device Development] sjamie:
That I can do. Thank you!
[OnePlus 5 & 5T Cross Device Development] faoliveira:
Here's the first A14-compatible build

This build decrypts dynamic and non-dynamic A12+ Roms

twrp-3.7.0_12-5-dyn-cheeseburger_dumpling.img
[OnePlus 5 & 5T Cross Device Development] sjamie:
Dude, you're amazing. Thank you! 🔥
[OnePlus 5 & 5T Cross Device Development] TheVoice70:
Tested with LOS 20 on 5 / 5T. Works fine. Awesome work. Many thanks @faoliveira
[OnePlus 5 & 5T Cross Device Development] tobby88:
Since Mindthegapps is the recommended one for LineageOS it would be great if it's installable by your TWRP :)
[OnePlus 5 & 5T Cross Device Development] slickw:
Edit:

works good

thanks
[OnePlus 5 & 5T Cross Device Development] corumuk:
Hi,

Currently running:

Stock rom - rooted with Magisk 26.4

Blu_Spark TWRP 3.3.1.x

Is it safe to flash faoliveira TWRP 3.6.2 over the top of the existing recovery, from within recovery?

Thanks.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
New official build has been released. https://dl.twrp.me/cheeseburger_dumpling/twrp-3.7.0_12-2-cheeseburger_dumpling.img.html

It's compatible with Android 14 and below (A13, A12).

It should not be installed on Roms of previous versions <=A11

It's only suitable for Roms with standard partitions.

If you're using a Rom with dynamic partitions, stick to unofficial 5-dyn build.

* No more Mindthegapps errors and no more "Failed to mount /metadata..." ;)
[OnePlus 5 & 5T Cross Device Development] francis1947:
How to flash non-dynamic rom on dynamic twrp.
[OnePlus 5 & 5T Cross Device Development] faoliveira:
If you are on a rom with standard partitions, the procedure is the same as with standard twrp

1 - Flash the Rom

2 - Factory reset or format data, if you are changing Roms

3 - Reboot

If you're on a rom with dynamic partitions, just follow the steps in the post: https://xdaforums.com/t/recovery-tw...ger-dumpling-11-12-2023.4351795/post-88449043