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

[javi2246]

@MENINBLK had the exact same problem also with google fonts. Maybe he found a solution for that. I will try to replicate for myself and search for a solution.

A few weeks ago I was gossiping on zulip (twrp) and they were talking about this problem. But I don't know if it was in the general, dev or where.
The truth is I have a ****ty memory, so you better ask them directly if you want fix the problem , maybe @osm0sis remember.

I would try to lend a hand, but I have no idea about programming :/

Edit: It doesn't pose any problem to me, you just have to delete those fonts... The OS continues to function well without them.

 

[patkoz16]

po aktualizacji do Androida 12.1 na powłoce fastboot boot boot.img wyświetlacz utknął w najbliższym fastboot? masz rozwiazanie??

spróbuj fastboot flash boot boot.img?

 

[der_akinator]

after update to android 12.1 on shell fastboot boot boot.img display stuck in fastboot mode ? you have solution ??

Please read Option 3 of the installation instruction. If you are not using root or any other custom recovery you have to first flash vendor_boot.img before fastboot boot boot.img. But at first get the vendor_boot.img of your current system.

 

[osm0sis]

A few weeks ago I was gossiping on zulip (twrp) and they were talking about this problem. But I don't know if it was in the general, dev or where.
The truth is I have a ****ty memory, so you better ask them directly if you want fix the problem , maybe @osm0sis remember.

I would try to lend a hand, but I have no idea about programming :/

Edit: It doesn't pose any problem to me, you just have to delete those fonts... The OS continues to function well without them.

I seem to recall @BillGoss reporting that deleting the offending font files had no negative effect, and maybe that the ROM recreates the files after restore and some uptime. Not sure if a general fix was proposed to exclude/fix the issue on the Gerrit or anything, however.

 

[patkoz16]

Przeczytaj opcję 3 instrukcji instalacji. Jeśli nie używasz roota ani żadnego innego niestandardowego odzyskiwania, musisz najpierw sflashować vendor_boot.img przed fastboot boot boot.img. Ale najpierw pobierz vendor_boot.img swojego obecnego systemu.

flash vendor boot to boot or to recovery ? vendor boot.img from my telephone or vendor boot from link this topic ?

 

[osm0sis]

Please read Option 3 of the installation instruction. If you are not using root or any other custom recovery you have to first flash vendor_boot.img before fastboot boot boot.img. But at first get the vendor_boot.img of your current system.

One update you should add to Option 1 is that after flashing the TWRP zip in Magisk you don't need to reboot to recovery, you can immediately reflash Magisk with Direct Install in the app, and then any custom kernel from any kernel flasher app before rebooting.

 

[der_akinator]

I noticed a similar error when rebooting into fastbootd. Even on Lineage. Not sure what's up there.

I believe there is no twrp-12 branch in effect, only 12.1, so 3.7.0_12 is correct and matches mainline TWRP. Best to leave it alone.

Would be nice if you could adjust the status header to be below the holepunch when you get the chance! Awesome (and rapid!) work here!

Edit: Oh wait, you just meant the build iteration from -0 to -1!

Strange los is using vendor_dlkm but same error on my device too. Any ideas how to pull logs? ADB in fastbootd mode seems to be broken.

 

[BillGoss]

I seem to recall @BillGoss reporting that deleting the offending font files had no negative effect, and maybe that the ROM recreates the files after restore and some uptime. Not sure if a general fix was proposed to exclude/fix the issue on the Gerrit or anything, however.

The backup will fail if there are files (directories are ok) under /data/fonts and /data/nandswap
There was some discussion at the time about excluding them, but it never came to a resolution.

I've never had issues after deleting the files, though they sometimes come back and I've never worked what causes them to reappear.

The problem also affects Orange Fox as it's based on TWRP.

 

[der_akinator]

flash vendor boot to boot or to recovery ? vendor boot.img from my telephone or vendor boot from link this topic ?

Use "fastboot flash vendor_boot vendor_boot.img" with TWRP vendor_boot. Get a copy of your ROM vendor_boot.img. At the last step use "fastboot flash vendor_boot vendor_boot.img" with your ROM vendor_boot.img.

 

[osm0sis]

Strange los is using vendor_dlkm but same error on my device too. Any ideas how to pull logs? ADB in fastbootd mode seems to be broken.

I believe adb is tied to MTP Enabled for some reason with the current USB config on this device, but of course there's no data decryption or MTP in fastbootd mode, so no adb.

I'm not sure if @Nebrassy ever figured out how to fix it, but you might want to pick his or other maintainers' brains about it on Zulip.

 

[_MartyMan_]

Working perfectly on OnePlus 9 with latest Nameless ROM. Thank you guys!

 

[patkoz16]

Użyj „fastboot flash vendor_boot vendor_boot.img” z TWRP vendor_boot. Uzyskaj dostęp do ROM vendor_boot.img. W ostatnim kroku procesu „fastboot flash vendor_boot vendor_boot.img” z ROM vendor_boot.img.

możesz krok po kroku? dla laika nie jestes

i download f72 with oxygen updater how to extract vendor_boot ?

 

[der_akinator]

możesz krok po kroku? dla laika nie jestes

i download f72 with oxygen updater how to extract vendor_boot ?

You can use payload-dumper-go to extract vendor_boot from the payload.bin inside your OOS zip.

Here is the link to it:

GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go

an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.

github.com

 

[patkoz16]

Możesz użyć payload-dumper-go, aby wyodrębnić vendor_boot z payload.bin wewnątrz ZIP OOS.

Oto link do niego:

GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go

an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.

github.com

Dziękuję. Następny krok . jak korzystać z tego programu? Nie mogę znaleźć pliku exe

 

[der_akinator]

Working perfectly on OnePlus 9 with latest Nameless ROM. Thank you guys!

So you are using it on OP9 not pro? Maybe I should update the thread and mark it as unified.

 

[der_akinator]

Dziękuję. Następny krok . jak korzystać z tego programu? Nie mogę znaleźć pliku exe

I send you a PM. I think it's better to write there. You find it at the envelope icon on the top right of the page.

 

[_MartyMan_]

So you are using it on OP9 not pro? Maybe I should update the thread and mark it as unified.

Yes, i'm using the 9 not the 9 Pro

 

[TheSayaMan]

flash vendor boot to boot or to recovery ? vendor boot.img from my telephone or vendor boot from link this topic ?

Do not flash it through twrp, you will end up with a crash dump. I made that mistake. Reboot to bootloader and fastboot flash vendor_boot vendor_boot.img

 

[Steve0007]

@der_akinator
FYI
Currently on latest OOS 13
Flashing twrp thru Magisk, and directly Flasing back magisk works fine
But trying to backup data dont work (error 255).
Also asked for user 10 (company profil) decryption code... Which we don't have.

 

[der_akinator]

@der_akinator
FYI
Currently on latest OOS 13
Flashing twrp thru Magisk, and directly Flasing back magisk works fine
But trying to backup data dont work (error 255).
Also asked for user 10 (company profil) decryption code... Which we don't have.

Is the user 10 profile specific to you or is this a default profile setup by OOS? I might install OOS13 myself and see whats going on there. Multi user system seem to be a common problem in TWRP. I will try to look into the backup code but it will probably take a bit longer to find a workaround for that. If I can find a solution at all for this...