[RECOVERY] TWRP Official/Unofficial v3.7.0 A12 Cheeseburger/Dumpling - 2022-10-06

Search This thread

psychoela

Senior Member
Dec 21, 2014
389
162
OnePlus 7 Pro
Sudah tentu, saya membuat binaan ujian, pada cawangan 12.1. Sila lihat jika ia berfungsi sekarang.
Nota: Penyahsulitan masih tidak berfungsi
TWRP OP5_OP5T_ A12.1_test binaan
I'm not use lock screen.
Screenshot_2022-04-29-14-43-57.png
 

Attachments

  • Log.zip
    43.8 KB · Views: 11

metahex12

Senior Member
Jun 15, 2014
566
537
Istanbul
Hi, it is not decrypting on Android 12. (ROM: LOS 19.1)
Device: OP5T
(tried with all versions, 12.1 test too)
 
Last edited:

faoliveira

Senior Member
May 28, 2013
125
216
Aracaju
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.
 

js-xda

Senior Member
Aug 20, 2018
328
139
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.
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?
 

faoliveira

Senior Member
May 28, 2013
125
216
Aracaju
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?
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.
 

faoliveira

Senior Member
May 28, 2013
125
216
Aracaju
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.
 

Agret

Senior Member
Jun 9, 2010
100
22
Melbourne
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.
 

zagzag99

Senior Member
Nov 3, 2008
1,565
1,489
Google Nexus 4
Google Nexus 5
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.
 

zagzag99

Senior Member
Nov 3, 2008
1,565
1,489
Google Nexus 4
Google Nexus 5
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.

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.

Code:
❯ 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
 

Agret

Senior Member
Jun 9, 2010
100
22
Melbourne
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

Thanks man, works great.

Code:
>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
 

faoliveira

Senior Member
May 28, 2013
125
216
Aracaju
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.

Code:
❯ 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

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
 

Top Liked Posts