[RECOVERY] TWRP Official/Unofficial v3.7.0 A12 Cheeseburger/Dumpling - 25/12/2022

[DoR3M3]

Did you change the default folder? Anyway, see if the build I posted exactly before your post solves the problem, if it doesn't, I'll need the logs.

I didn't change the default folder and twrp-3.7.0_12-1-cheeseburger_dumpling.img works!

When I see the TWRP Logo Screen this is dim, then it boots me into TWRP and the screen goes brighter, and I see all the settings stayed. Anyway to have the TWRP Logo Screen appear brighter?

I'm loosing my mind here, I thought after the main screen loads, the slider appears to slide to get into TWRP?

After flashing this, I flashed back the previous version to check something in it. Then I flashed twrp-3.7.0_12-1 over, now apps in the phone like the Settings won't open and it crashes. So I don't know if there's a problem with twrp-3.7.0_12-1 causing this, or it's because I reverted back then flashed again twrp-3.7.0_12-1. hmm

So I wiped the ROM in twrp and flashed it over, it still crashes, something's wrong with this version. hmm

 

[faoliveira]

I didn't change the default folder and twrp-3.7.0_12-1-cheeseburger_dumpling.img works!

When I see the TWRP Logo Screen this is dim, then it boots me into TWRP and the screen goes brighter, and I see all the settings stayed. Anyway to have the TWRP Logo Screen appear brighter?

I'm loosing my mind here, I thought after the main screen loads, the slider appears to slide to get into TWRP?

THANKS

Weird, there is no specific setting to make the screen brighter during boot, it should stay the same until it shuts down due to inactivity.
You only need to use slide when the settings are not saved, it should happen only after formatting the internal storage, still happening, even in this last build I posted? If that's the case and if you don't mind, I'd like to ask you to send your logs.

 

[DoR3M3]

Weird, there is no specific setting to make the screen brighter during boot, it should stay the same until it shuts down due to inactivity.
You only need to use slide when the settings are not saved, it should happen only after formatting the internal storage, still happening, even in this last build I posted? If that's the case and if you don't mind, I'd like to ask you to send your logs.

Refresh the page, I edited over my post, there's a bigger problem, it's crashes the Settings apps in the ROM now.

 

[DoR3M3]

Reverting back to the previous version twrp-3.7.0_12-0-cheeseburger_dumpling now no good. After I flash TWRP and then flash the new ROM, when the ROM boots for the first time, it's ok, but then I boot into TWRP and back into the ROM, then the Settings app won't open and crashes, and it also complains about Bluetooth crashing.

So now neither 3.7.x version works for me, and I've flashed both versions over many times, and each time, the same issue in the phone, the settings app crashes and it complains about Bluetooth.

twrp-3.6.2_9-0-cheeseburger_dumpling is working ok, it keeps the settings, but the Timezone is not correct. Does having an incorrect timezone affect anything, like does twrp timestamp anything, when you flash in it, etc..?

For now I'll stick with twrp-3.6.2_9-0 until you can figure out why it's crashing apps using twrp 3.7x

THANKS

 

[faoliveira]

Reverting back to the previous version twrp-3.7.0_12-0-cheeseburger_dumpling now no good. After I flash TWRP and then flash the new ROM, when the ROM boots for the first time, it's ok, but then I boot into TWRP and back into the ROM, then the Settings app won't open and crashes, and it also complains about Bluetooth crashing.

So now neither 3.7.x version works for me, and I've flashed both versions over many times, and each time, the same issue in the phone, the settings app crashes and it complains about Bluetooth.

twrp-3.6.2_9-0-cheeseburger_dumpling is working ok, it keeps the settings, but the Timezone is not correct. Does having an incorrect timezone affect anything, like does twrp timestamp anything, when you flash in it, etc..?

For now I'll stick with twrp-3.6.2_9-0 until you can figure out why it's crashing apps using twrp 3.7x

THANKS

Tell me what ROM you are using and what version of Android. Anyway I'm going to need your logs to try to understand what's happening on your device.

 

[DoR3M3]

I'm playing around with /e/ at the moment, I'm actually testing out ROMs, trying to figure on one.

Info about OnePlus 5T - dumpling

I'm using 'e-1.4-r-20220922220394-dev-dumpling' which is Android 11 I also tried this on e-1.4-q-20220923220853-dev-dumpling which is Android 10, same problem.

I'm using TWRP 3.6.2_9-0 at the moment and when I looked in the TWRP directory there is no log.

I've attached logcat...

 

[Ssmiles]

twrp-3.7.0_12-1-cheeseburger_dumpling_REPACK_Sskulls_Blue_v1.img

39.55 MB file on MEGA

mega.nz

 

[faoliveira]

I'm playing around with /e/ at the moment, I'm actually testing out ROMs, trying to figure on one.

Info about OnePlus 5T - dumpling

I'm using 'e-1.4-r-20220922220394-dev-dumpling' which is Android 11 I also tried this on e-1.4-q-20220923220853-dev-dumpling which is Android 10, same problem.

I'm using TWRP 3.6.2_9-0 at the moment and when I looked in the TWRP directory there is no log.

I've attached logcat...

So that's the problem, TWRP 3.7.0 12 is to be used on Roms >=A12, the recommended build for Roms <=A11 is 3.6.2_9.

 

[DoR3M3]

So that's the problem, TWRP 3.7.0 12 is to be used on Roms >=A12, the recommended build for Roms <=A11 is 3.6.2_9.

Oh my mistake, sorry about this, I wasn't paying attention.

Sometimes 3.6.2_9-0 tells me I still have an unmodified partition, also sometimes it's not saving the settings, and it doesn't display my correct time for the timezone I pick

If you can please fix this, it would be greatly appreciated, as /e/ is only Android 11 at this time.

THANKS

 

[faoliveira]

Oh my mistake, sorry about this, I wasn't paying attention.

Sometimes 3.6.2_9-0 tells me I still have an unmodified partition, also sometimes it's not saving the settings, and it doesn't display my correct time for the timezone I pick

If you can please fix this, it would be greatly appreciated, as /e/ is only Android 11 at this time.

THANKS

Have you tried twrp 3.6.2_11? https://www.androidfilehost.com/?fid=15664248565197186744

 

[DoR3M3]

Have you tried twrp 3.6.2_11? https://www.androidfilehost.com/?fid=15664248565197186744

No because I was only look at twrp.me and all I saw was 3.6.2_9-0.

Download TWRP for cheeseburger_dumpling

Download TWRP Open Recovery for cheeseburger_dumpling

dl.twrp.me

Why isn't 3.6.2_11 listed on twrp.me?

THANKS

 

[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

 

[faoliveira]

No because I was only look at twrp.me and all I saw was 3.6.2_9-0.

Download TWRP for cheeseburger_dumpling

Download TWRP Open Recovery for cheeseburger_dumpling

dl.twrp.me

Why isn't 3.6.2_11 listed on twrp.me?

THANKS

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

 

[faoliveira]

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

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

 

[DoR3M3]

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

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....

 

[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

 

[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

 

[componentchunk]

Successfully updated PixelExperience12 and reinstalled magisk from recovery twrp-3.7.0_12-1, no fastboot required!

 

[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.

 

[faoliveira]

@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.

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.