Database Info

[RECOVERY] [F1f-Spectrum] [TWRP-3.1.1-0] For Project Spectrum Bootloader ONLY!

This is an unofficial port of TWRP Recovery for the Oppo F1F on Project Spectrum Bootloader. Much Thanks and credit goes to the TWRP team, Lineage team, and brinleyaus for making this possible. This will allow flashing of modification zips (eg. supersu, magisk, xposed, etc) over the top of Project Spectrum or flashing spectrum based ROMS.
Instructions:
Already running Project Spectrum
- If you haven't already unlocked you bootloader you will need to go into SETTINGS > ABOUT PHONE and tap BUILD NUMBER 7 times to unlock DEVELOPER OPTIONS, Then go into SETTINGS > DEVELOPER OPTIONS and enable them, also enable ADB DEBUGGING and OEM UNLOCK. Now reboot into fastboot (adb reboot bootloader) and run fastboot oem unlock.
- Install this image file through fastboot (If you are unsure of this step follow one of the many tutorials about installing TWRP through fastboot)
On ColourOs with TWRP
- Do a full wipe first or the install will fail. (In TWRP hit WIPE then swipe to factory reset.) Do a backup first as you will lose data.
- Flash this zip file through twrp and then hit "wipe dalvic and cache", then hit HOME then REBOOT then RECOVERY. (rebooting to the new recovery will ensure the recovery sticks) then Flash any Spectrum based rom or restore any Spectrum based backup. NOTE the ColorOs system and boot.img will still be there but wont boot so you MUST flash or restore a Spectrum based rom before you reboot to system.

Reserved.

MiniBlu said:
Reserved.
Click to expand...
Click to collapse
Battery can't charge full!! Help ?

Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.

Thank.link from androidfilehost is slowly. I using wifi
Sent from my F1w using XDA-Developers Legacy app

MiniBlu said:
Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.
Click to expand...
Click to collapse
The TWRP is not the 3.1.1
It is the 3.0.1

khannz7 said:
The TWRP is not the 3.1.1
It is the 3.0.1
Click to expand...
Click to collapse
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?

MiniBlu said:
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?
Click to expand...
Click to collapse
The PS 1
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work

khannz7 said:
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work
Click to expand...
Click to collapse
Which ps1 g or zip?
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.

MiniBlu said:
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.
Click to expand...
Click to collapse
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
+
Maybe I could help you somewhere with the port

I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up

khannz7 said:
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
Click to expand...
Click to collapse
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.

MiniBlu said:
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.
Click to expand...
Click to collapse
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:

Phucan2017 said:
I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up
Click to expand...
Click to collapse
No one. If you don't like it stick with ColorOs or Lineage.
khannz7 said:
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:
Click to expand...
Click to collapse
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.

MiniBlu said:
No one. If you don't like it stick with ColorOs or Lineage.
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.
Click to expand...
Click to collapse
Cool

I did that. But for oppo f1 this rom is not finished yet but there are still many bugs. I return coloros

Just used the spectrum zip and worked flawlessly.(from other thread oops) Thanks alot.

How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs

the_reds2000 said:
How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs
Click to expand...
Click to collapse
No, Read the OP of this thread. There is a zip (and instructions) to return to ColorOs Bootloader,firmware and TWRP. From there you can flash any TWRP flashable ColourOs based Rom (ColorOs or LineageOS) or restore backups from them.

Which root method will be used for this?

Noob guide to install GSI on whyred

Today I flashed Pixel Experience GSI on my whyred after much trouble so here is a guide to make things clear.
if you are coming from MIUI you have to format data from twrp. this is a must to disable encryption.
after you are done formatting data. just do factory reset from twrp and then go to advanced wipe and then do the regular dalvik, cache, system, data and then swipe to wipe.
now the thing is whyred officially supports treble but the implementation is shoddy according to XDA folks. so if you flash GSI over miui's vendor there will be many bugs. like brightness slider not working and many things. so they(all credit goes to them) created a vendor zip which makes things really good. there are no bugs and it also supports volte. here is the download link .
https://www.androidfilehost.com/?w=files&flid=273660
now flash this zip file in twrp.
after that download the GSI of your choice from here.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
remember to download arm64 A only system image.
here is pixel experience GSI which I prefer:
https://download.pixelexperience.org/treble_gsi/
now extract the zip and you will get a single .IMG file which is your system image. now go to twrp and then go to install then go to select install image downward. (don't flash directly, it's an .IMG file) then select the extracted .IMG file and then choose system and then flash.
then reboot system. that's it. you should boot fine.
download latest official twrp from here: https://dl.twrp.me/whyred
if you want root you will have to flash magisk beta 16.6 which works better on GSI. download here.
https://github.com/topjohnwu/Magisk/releases/download/v16.6/Magisk-v16.6.zip
to use Google camera you will have to enable camera2api. arnova's gcam doesn't work on this build. you will have to use BSG's gcam. here is the link. enable nexus style and active portrait mode from settings.
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_5.2.022.apk
few tips: if your device is not booting and going to fastboot, flash magisk. it will definitely boot up.
if your device shows decryption failed, just format data from twrp. it will delete all user data btw.
no need to flash lazyflasher.
there are no uncertified device pop up from Google. so no need to worry.
playstore shows uncertified btw and magisk shows CTS false.
all the links that I have linked here, the credit goes to the creators. I am a normal user of XDA. thanks to them.
happy flashing and all hail the XDA lords.

How is Pixel experience gsi though?....faced any bugs till now?

it's good but there where few bugs. anyway pixel experience rom specifically for whyred has been released. you can flash that. it's great and bug free. download it here. it's not GSI though. normal ROM.
https://download.pixelexperience.org/whyred/
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse

mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.

I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
goofball2k said:
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
Click to expand...
Click to collapse

mearjunsha said:
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
Click to expand...
Click to collapse
So should I flash the ROM or the gsi?....are there any differences?

you should flash the ROM as it's specifically for whyred. its flashing instruction is different than GSI. but easy. just wipe and then flash the ROM. and reboot. that's it.
you may have to format data to disable encryption.
here is the forum discussion: https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3816099
mr._.nobody said:
So should I flash the ROM or the gsi?....are there any differences?
Click to expand...
Click to collapse

Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?

remove all security like fingerprint, pattern etc.
go to twrp
go to wipe
do factory reset
go to advanced wipe
select dalvik, cache, system and data and then wipe
go to install
flash the pixel experience rom
reboot to system
that's it
if you get a prompt to enter password to start android then you will have to go back to twrp and go to wipe and format data and type yes. it will delete all your files btw. so backup everything. then reboot it will boot up fine.
after you have done booting and set up, go back to twrp and flash magisk v16. reboot to system. all done.
I have already given details of gcam in my OP. Kindly check that. The same works great on this ROM.
ask me if you face any problem. happy to help ?
trazalca said:
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
Click to expand...
Click to collapse

You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!

I understand your excitement but do check your build whether you are on Anti rollback. if you are on 9.5.19 you should absolutely not proceed right now.
read about it on XDA.
trazalca said:
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
Click to expand...
Click to collapse

I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?

you can go ahead. happy flashing! ?
trazalca said:
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
Click to expand...
Click to collapse

[dupe sorry]

You should by all means read about antirollback to be sure, but my understanding is that the antirollback refers to the firmware, not the rom. MIUI roms all include different firmware, so you can't rollback a MIUI rom (unless it's been modded to be firmwareless). But as far as I know, no custom roms include firmware, so you should be fine even if your firmware is ARB triggered if all you're doing is installing custom roms.

Hi, someone flashed latest Pie Phh GSI? I tried with PE CAF, AOSIP, and Mokee vendors but doesn't boot, always stuck at the Mi logo, even I flashed the permissiver patch without luck.

Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?

ShadowFax said:
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
Click to expand...
Click to collapse
Nope.

Disable Force Encryption Explained And With Benefits

I'll get straight into the matter at hand.
DFE basically disables all the encryption the phone uses. Now that is explained let's get into the benefits of disabling it.
-Battery Life Improvement
-Slighty Better Response Times
So from looking at this you can say that it hardly does anything in terms of making your life easier.
Let's get to the verdict:
If you don't care about security and you trust yourself then i encourage you to disable it
Any mods that will make your experience better is a plus in my book.
P.s: If you are installing any type of gsi then you don't have any choice but to disable it.
Hope this helped you in someway or another.

It's more convenient. Everything else is a bonus.

Does my phone get re-encrypted when i flash a new rom build (pixel experiance) or a new firmware ? I dont get that part.

KabalLV said:
Does my phone get re-encrypted when i flash a new rom build (pixel experiance) or a new firmware ? I dont get that part.
Click to expand...
Click to collapse
DFE patches vendor.

Martensite said:
DFE patches vendor.
Click to expand...
Click to collapse
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.

MechaNarutoSucks said:
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.
Click to expand...
Click to collapse
I find fix.sh in the dfe.zip. I think this is how magic happen.
#!/sbin/sh
find /vendor/etc -name "fstab.*" -exec sed -i 's/forceencrypt/encryptable/g' {} +
find /vendor/etc -name "fstab.*" -exec sed -i 's/forcefdeorfbe/encryptable/g' {} +
find /vendor/etc -name "fstab.*" -exec sed -i 's/fileencryption/encryptable/g' {} +
And it was fine when I forget to flash dfe with already patched vendor.

MechaNarutoSucks said:
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.
Click to expand...
Click to collapse
No.
Encryption is defined in late-stage fstab, and on treble devices that fstab is at /vendor/etc/

CosmicDan said:
No.
Encryption is defined in late-stage fstab, and on treble devices that fstab is at /vendor/etc/
Click to expand...
Click to collapse
Encryption happens in vendor/etc partition thats why when you try to update your device's vendor/firmware, the patch (DFE) will be overwritten with the new files thus enabling the encryption again. But updating only the system (like dirty flashing new LineageOS Rom like OTA update via TWRP [old build > new build]) it won't overwrite vendor/firmware thus the encryption stays the same (if enabled or disabled via patch)

Darklouis said:
Encryption happens in vendor/etc partition thats why when you try to update your device's vendor/firmware, the patch (DFE) will be overwritten with the new files thus enabling the encryption again. But updating only the system (like dirty flashing new LineageOS Rom like OTA update via TWRP [old build > new build]) it won't overwrite vendor/firmware thus the encryption stays the same (if enabled or disabled via patch)
Click to expand...
Click to collapse
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Sent from my POCOPHONE F1 using Tapatalk

CosmicDan said:
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Just giving out additional info.. Hahahaha

CosmicDan said:
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Click to expand...
Click to collapse
That may be true but everytime i reflash the encryption turns on. So i don't know the exact answer but that's the out outcome of reflashing at least for me.

after flashing each update via twrp, should i flash DFE then magisk or it is needed once?

MechaNarutoSucks said:
That may be true but everytime i reflash the encryption turns on. So i don't know the exact answer but that's the out outcome of reflashing at least for me.
Click to expand...
Click to collapse
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.
hosseinito said:
after flashing each update via twrp, should i flash DFE then magisk or it is needed once?
Click to expand...
Click to collapse
Just flash it again if in doubt, as said it can't do any harm.
Sent from my POCOPHONE F1 using Tapatalk

Is there a reason to still be using 18.0 DFE and not 18.1? Also I have magisk v19 installed. If I update this rom (10.3.4.0|9.4.1) should I flash dfe 18.1 and re-flash magisk v18.1 for the purpose? Thanks

CosmicDan said:
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.Just flash it again if in doubt, as said it can't do any harm.
Click to expand...
Click to collapse
Ok then. Thank you?

CosmicDan said:
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.Just flash it again if in doubt, as said it can't do any harm.
Click to expand...
Click to collapse
Like i said i don't know the exact idea on it so thx for the explanation.
And its true that i only update my rom when there is a new firmware update.

Can I just flash the DFE file in TWRP without wiping data or anything else? Right now I have Lineage installed with everything set up and I would not wipe everything right now just to flash DFE.

Hi i am on global 10.3.5 stable, rooted with magisk and twrp is not installed (only hot booted).
1. Can i just flash dfe?
2 what about ota update? If i just flash dfe Will it ask for any pin after doing ota update?? Or i can just update and then flash dfe again
3. Also i have one doubt. i flashed pixel rom once and i decided to revert back to miui. So i restored my twrp backup of miui and got bootloop. Then i flashed the 10.3.5 zip and vendr/firmware also. But after booting it asked me for pin. i had to fastboot flash the rom again. It wiped all my data. So what did i do wrong here. And how to restore miui twrp backup. Coz its really difficult to back up all the data in my phone every time i flash a rom. Thats holding me back from enjoying the custom roms. So any clarification would be highly appreciated. Thanks

MechaNarutoSucks said:
I'll get straight into the matter at hand.
DFE basically disables all the encryption the phone uses. Now that is explained let's get into the benefits of disabling it.
-Battery Life Improvement
-Slighty Better Response Times
So from looking at this you can say that it hardly does anything in terms of making your life easier.
Let's get to the verdict:
If you don't care about security and you trust yourself then i encourage you to disable it
Any mods that will make your experience better is a plus in my book.
P.s: If you are installing any type of gsi then you don't have any choice but to disable it.
Hope this helped you in someway or another.
Click to expand...
Click to collapse
but how do i do it? i only read dfe dfe dfe everywhere but can't find anywhere how to disable encryption

How can you tell the benefits without providing concrete proof? I am running encrypted since I got my POCO and installed LOS16. I haven't encountered any issues at all with regards to performance or battery life.

Android 10 Open Beta twrp not asking for password

So I upgraded to android 10 open beta and now viper4android keeps asking to install the drivers and twrp isnt asking for my password so I cant access storage or anything from twrp

I am on twrp 3.3.1-4

Did you try removing the password from your current rom.

Robert235 said:
Did you try removing the password from your current rom.
Click to expand...
Click to collapse
Just tried and still nothing it comes up with swipe to allow modifications and I do that but internal storage is still 0

That's Strange, I remember both on the OnePlus 6 and OnePlus 7 Pro when switching from stock ROM to AOSP having a password used to cause issues with twrp. I wonder if the new version of twrp installer will work.

I wanna try a factory reset but it wont let me

D.Va said:
I am on twrp 3.3.1-4
Click to expand...
Click to collapse
Your on the wrong twrp version.
Flash the latest unofficial twrp.

twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug

D.Va said:
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug
Click to expand...
Click to collapse
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.

twinnfamous said:
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.
Click to expand...
Click to collapse
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe

The unofficial twrp comes with a .img file and zip. Use a PC to boot into the .img with fastboot then use that booted image which should allow decryption and flash the zip.

D.Va said:
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe
Click to expand...
Click to collapse
Do you have magisk installed?
Use the twrp installer zip.

twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.

stefanaroman88 said:
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322

TWRP compatible with Android 12?

Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best

The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/

henschn3435 said:
Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best
Click to expand...
Click to collapse
3.7.0 is recovery release version and 11-0 means it's for Android 11.

BillGoss said:
The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
Click to expand...
Click to collapse
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?

Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
It works on both the 8T and the 9 9R. If you want to be sure try to boot into it before flashing.

Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
TheNewHEROBRINE said:
It works on both the 8T and the 9. If you want to be sure try to boot into it before flashing.
Click to expand...
Click to collapse
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).

BillGoss said:
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).
Click to expand...
Click to collapse
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255

Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
Can you share the full log?

TheNewHEROBRINE said:
Can you share the full log?
Click to expand...
Click to collapse
sure, give me another day ...I just deleted the Orangefox and TWRP directories

Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.

BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
Thanks all! One should perhaps forbid files under /data/fonts/files/ ... After deleting those, I could finish both (unofficial) Orangefox and (unofficial) TWRP backup just fine. Agreed, this does not 100% prove ERROR root cause but sure does consistently correlate. So now maybe one should harden custom recovery images to avoid the trap, especially since the trap seems to be a known one by some people (like @BillGoss).

BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?

Rootk1t said:
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?
Click to expand...
Click to collapse
No, I never understood what the problem was with those files.

BillGoss said:
No, I never understood what the problem was with those files.
Click to expand...
Click to collapse
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?

Rootk1t said:
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?
Click to expand...
Click to collapse
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.

BillGoss said:
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.
Click to expand...
Click to collapse
BillGoss said:
Flashing OTA zips - both full and incremental. Note: incremental OTAs need stock boot and recovery installed so make sure you flash these before starting the install, otherwise it will fail.
Click to expand...
Click to collapse
Has something changed from your post?

Rootk1t said:
Has something changed from your post?
Click to expand...
Click to collapse
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.

BillGoss said:
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.
Click to expand...
Click to collapse
Thanks for letting us know

Rootk1t said:
Thanks for letting us know
Click to expand...
Click to collapse
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
I wanted to test using TWRP to install an OTA zip on OOS 12. The first time I tried I got an error because it was expecting the current version to match those of C.33 but they didn't - even though I was on C.33. So I used `resetprop` to set the proper values and then it sort of worked, but still gave errors.
I was using the latest version (1.5 or 220827) of TWRP.
Click to expand...
Click to collapse
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.

BillGoss said:
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.
Click to expand...
Click to collapse
So as i understood correctly flashing OTAs in TWRP is broken on v1.4 and works on prior versions?