Development [RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support

[der_akinator]

I'm on Paranoid android 13 Tobaz beta 2 ( an unofficial buildnot by op)

I don't know where to find it. If you provide a link, I will see what I can do. Maybe it has something to do with with the changes to their kernel module, which are now build inline. And did you use latest 12-01-23 build.

Edit: It could be possible that I'm missing to load a kernel module. Could you provide the output of the command "lsmod". Or they are installed to a non standard path.

 

[IamTheBRAVE]

I don't know where to find it. If you provide a link, I will see what I can do. Maybe it has something to do with with the changes to their kernel module, which are now build inline. And did you use latest 12-01-23 build.

I used the 05-01 i think. The rom link was posted on telegram.

aospa-topaz-unofficial-oneplus9pro-20230116.zip

drive.google.com

The official build is still not out due to display issues. This build works.
I'll keep trying later. Thanks for taking the time to look into this

 

[der_akinator]

I used the 05-01 i think. The rom link was posted on telegram.

aospa-topaz-unofficial-oneplus9pro-20230116.zip

drive.google.com

The official build is still not out due to display issues. This build works.
I'll keep trying later. Thanks for taking the time to look into this

I've read that there are some display issues with the kernel. Stock AOSPA recovery also have some issues and just shows random noise when I try to use it. I think the best thing is to wait for an official build. But with their current kernel, it is probably only possible to install TWRP via zip installer.

 

[NAGARAJU02]

Hi, everyone. I recently updated my rom and flashed the twrp installer via magisk. After rebooting, twrp always shows static screen, i can't access anything there. Tried using Fastboot to boot it but no luck. I must be doing something wrong. Can anyone help?

Are you using new 13/01/2023 twrp
And which rom update bro

 

[Andsie]

updating in TWRP preferred`?

 

[TheSayaMan]

updating in TWRP preferred`?

No, not if you want boot errors. Update by either custom recovery or built in system updater. You can always restore twrp after that with zip if you retain root with magisk or booting twrp again. Guess it depends on the ROM. If you are using one that requires gapps than definitely NO!!!

 

[Andsie]

I meant updating the new version TWRP from this thread of the dear host itself

 

[der_akinator]

I meant updating the new version TWRP from this thread of the dear host itself

There aren't any major changes, but if you want to use adb in fastbootd mode you should use the latest version.

 

[Aballamis]

@der_akinator

Hey, it's been a while but I wanted to update you. If you remember I was having severe problems with getting my 9 pro going, especially with TWRP. Well, I got profit. I used the crDroid c63 fw flasher instead of TheSayaMan's c66 flasher which apparently doesn't work for my variant, to get fw on both slots. That crDroid flasher installs their LOS style recovery, I believe I saw a post in the crDroid 9.1 thread from you about the kernel on the 20230113 build so I think you already know. But I used that recovery to flash WatchDogs & Magisk, but was getting hella glitches. Seemed like a copy&paste ROM w/different boot animation anyways. So I switched to crDroid. BTW, that comment on the crDroid thread saved my butt again - couldn't figure why Magisk wouldn't go.

Anyways, got crDroid working, flashed your updated TWRP v3 and it's working great. Magisk too, after they updated the boot.img for the 20230113 build - thanks to your comment.

However, when I try to flash blu_spark 120 in TWRP, I get an error: vendor_dlkm larger than vendor_dlkm partition: aborting. But I guess that's a question for the blu_spark thread.

Also, I had meant to say thanks and let you know everything has been working out, but right when I got things going, I got an error on the app/site "oops, someone call neo. We broke the matrix" that my account had been BANNED! I never get in pissing matches or solicit or participate in solicitations or anything, so I dunno. It mentions being hijacked and I hadn't noticed any unusual activity, but now that I got it back (finally), I went to my account info and there was some weird stuff. Said I was in Sweden and an associated account id never heard of. The error msg says "allow 72 hours for response" - took 10 days. But that's still better than starting over from a new account. Kinda sad, but I'd prolly cry if I lost my "senior" status, which is probably just due to membership time. DroidNerd 4 life.

Thanks again.

 

[brandon79]

So maybe I'm confused or maybe I'm doing something wrong. IDK. So one plus 9 pro bliss custom ROM. Android 13 based on 12.1. kinda new to 9 pro my last was a 6t. Anyway i had ROM installed flashed TWRP reboot recovery flash magisk again. Reboot system. Decided to reboot to recovery to check it out farther and TWRP is no longer there. It's back to LOS recovery again. So am I doing something wrong or is TWRP not suppose to retain.


Edit: figured out my problem. After I flashed TWRP I rebooted to system. Installed magisk again, select file and patch, with TWRP installed. Then reboot to recovery and flash the magisk patched img. That had TWRP flashed and that did it.

 

[der_akinator]

@der_akinator

Hey, it's been a while but I wanted to update you. If you remember I was having severe problems with getting my 9 pro going, especially with TWRP. Well, I got profit. I used the crDroid c63 fw flasher instead of TheSayaMan's c66 flasher which apparently doesn't work for my variant, to get fw on both slots. That crDroid flasher installs their LOS style recovery, I believe I saw a post in the crDroid 9.1 thread from you about the kernel on the 20230113 build so I think you already know. But I used that recovery to flash WatchDogs & Magisk, but was getting hella glitches. Seemed like a copy&paste ROM w/different boot animation anyways. So I switched to crDroid. BTW, that comment on the crDroid thread saved my butt again - couldn't figure why Magisk wouldn't go.

Anyways, got crDroid working, flashed your updated TWRP v3 and it's working great. Magisk too, after they updated the boot.img for the 20230113 build - thanks to your comment.

However, when I try to flash blu_spark 120 in TWRP, I get an error: vendor_dlkm larger than vendor_dlkm partition: aborting. But I guess that's a question for the blu_spark thread.

Also, I had meant to say thanks and let you know everything has been working out, but right when I got things going, I got an error on the app/site "oops, someone call neo. We broke the matrix" that my account had been BANNED! I never get in pissing matches or solicit or participate in solicitations or anything, so I dunno. It mentions being hijacked and I hadn't noticed any unusual activity, but now that I got it back (finally), I went to my account info and there was some weird stuff. Said I was in Sweden and an associated account id never heard of. The error msg says "allow 72 hours for response" - took 10 days. But that's still better than starting over from a new account. Kinda sad, but I'd prolly cry if I lost my "senior" status, which is probably just due to membership time. DroidNerd 4 life.

Thanks again.

I installed blu_spark on top of crdroid 20230113 build because of the magisk issues, but everything went fine for me. Maybe try the latest r123 blu_spark release.

 

[der_akinator]

So maybe I'm confused or maybe I'm doing something wrong. IDK. So one plus 9 pro bliss custom ROM. Android 13 based on 12.1. kinda new to 9 pro my last was a 6t. Anyway i had ROM installed flashed TWRP reboot recovery flash magisk again. Reboot system. Decided to reboot to recovery to check it out farther and TWRP is no longer there. It's back to LOS recovery again. So am I doing something wrong or is TWRP not suppose to retain.


Edit: figured out my problem. After I flashed TWRP I rebooted to system. Installed magisk again, select file and patch, with TWRP installed. Then reboot to recovery and flash the magisk patched img. That had TWRP flashed and that did it.

You can also flash the Magisk.apk directly in TWRP like a zip. That's a bit more comfortable.
On this device it's also a bit more complicated to keep TWRP installed, because every time the boot partition is overwritten it is gone.

 

[Aballamis]

I installed blu_spark on top of crdroid 20230113 build because of the magisk issues, but everything went fine for me. Maybe try the latest r123 blu_spark release.

I used FKM to install r123 and it went off without a hitch. This was also recommended by a few in that thread.

Thanks for the help and the v3 TWRP.

 

[Mr.Conkel]

Anyone know if I should use the OOS13 boot.img for oos13 based custom roms?

 

[der_akinator]

Anyone know if I should use the OOS13 boot.img for oos13 based custom roms?

Yes, it's for roms with OOS13 based firmware. For the zip installer it doesn't matter.

 

[A6ekAK]

Hello, I'm on CrDroid 9.1 and I wanted to go back to OOS 13 but while trying to flash the oos zip in twrp i get error 23 (kdownloadmanifestparseerror), can someone help me?

 

[der_akinator]

Hello, I'm on CrDroid 9.1 and I wanted to go back to OOS 13 but while trying to flash the oos zip in twrp i get error 23 (kdownloadmanifestparseerror), can someone help me?

The easiest way is to use the MSM tool for your phone version. You can also try to manually create and flash logical partitions within super.

 

[A6ekAK]

The easiest way is to use the MSM tool for your phone version. You can also try to manually create and flash logical partitions within super.

And that's what I did, thanks for help.

 

[osm0sis]

@der_akinator, could you add vendor_boot and dtbo to the list of partitions available on the Backup page? It'll cover everything important for custom kernels and recoveries in a backup/restore that way.

 

[der_akinator]

@der_akinator, could you add vendor_boot and dtbo to the list of partitions available on the Backup page? It'll cover everything important for custom kernels and recoveries in a backup/restore that way.

Yes, I can upload a new build in a couple of hours.