Database Info

Installing custom ROM android 10

Noob questions:
I've read that TWRP won't coming for android 10 any time soon because of the changes google made to the recovery, etc etc
Currently running Android Q and was previously rooted, but went back to factory images since I wanted Android 10 when it came out.
Now im wanting to install custom ROMs but i can't even boot into TWRP since its "outdated".
What are my options? Go back to a previous Android 9 version and run TWRP from there? And are there any good Android Q custom ROMs atm? Would really like to run Q since i love the "system wide" dark theme (yes i have used swift and substratum, but they dont compare imo) as well as the notification bubbles.
Also, correct me if im wrong but only Magisk Canary works at the moment right (for Q)? And how would you go about installing it without TWRP?

Pixel_XX said:
Also, correct me if im wrong but only Magisk Canary works at the moment right (for Q)? And how would you go about installing it without TWRP?
Click to expand...
Click to collapse
See this thread for installing Magisk. It is a bit outdated - you no longer need Magisk Canary. Stable version 20 works fine. Get the latest platform tools also.
https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
You don't need TWRP to flash ROMS. You can flash with adb.
I can't help with your other questions.

dcarvil said:
You don't need TWRP to flash ROMS. You can flash with adb.
Click to expand...
Click to collapse
go on, explain then.

sudoxd said:
go on, explain then.
Click to expand...
Click to collapse
Go down to the word procedure on the first page to see the temp solution (at least for Pixel 3 XL Havoc). He is also working on an Android 10 Havoc build for the P3.
https://forum.xda-developers.com/pixel-3-xl/development/official-havoc-os-t3960478

sliding_billy said:
Go down to the word procedure on the first page to see the temp solution (at least for Pixel 3 XL Havoc). He is also working on an Android 10 Havoc build for the P3.
https://forum.xda-developers.com/pixel-3-xl/development/official-havoc-os-t3960478
Click to expand...
Click to collapse
oh the retard way to flash roms, right.

sudoxd said:
oh the retard way to flash roms, right.
Click to expand...
Click to collapse
How so? Sideloading is essentially what a TWRP .zip flash of a custom ROM does (thus why it bounces slots). The initial instructions for flashing on Android 10 were a bit more involved until he got the sideload method working (and stayed in the active slot). Take a look at post #92 on page 10 of that thread.

Can I make android pie and android 10 coexist on the phone

We have A/B system. Can I make slotA install pie and make slotB install 10 ? Share the userdata?

alex.coffen said:
We have A/B system. Can I make slotA install pie and make slotB install 10 ? Share the userdata?
Click to expand...
Click to collapse
If there's a dual boot solution , IMHO.
Partitions A/B are ment to prevent some crash/bootloop after updating OTA's

refedit said:
If there's a dual boot solution , IMHO.
Partitions A/B are ment to prevent some crash/bootloop after updating OTA's
Click to expand...
Click to collapse
Yeah with the a/b thingy and vendor crappy partition its a headache LOL

refedit said:
If there's a dual boot solution , IMHO.
Partitions A/B are ment to prevent some crash/bootloop after updating OTA's
Click to expand...
Click to collapse
Exactly. They are not meant to run two different OS versions.
You are likely to have issues with two different OS versions. Once you boot to the later OS some files are not unique and stored in a shared area.
Normally I flash both slots to the same version to avoid any issues.

But you can't share data partition between 9 and 10, it won't work.

General Oneplus 9 and / 9 Pro TWRP

Just a reminder for people who only read the oneplus 9 forum and not oneplus 9 pro one:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
I tested it and flashed it on my oneplus 9 LE2110 and it works.
Again, as i always have to write to people.
Be careful, only do something you can undo.
Before you "Flash Current TWRP" do a full BACKUP!

Does said recovery perform full back-ups of partitions and restore features ?
Edit
I booted it up . Decrypts perfectly. Backed up modem just to see for myself. Rebooted back onto system . Booted twrp again and it found saved partition to restore. This makes life so much easier. Time to go get a full system backup !! Cool

Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.

noname122414 said:
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
Click to expand...
Click to collapse
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.

Hi there, I have a question:
When you have a new device, would the following work:
1. Unlock bootloader
In fastboot mode:
2.
Code:
fastboot boot c:\twrp.img
In TWRP
3. Install TWRP
4. Install Magisk
5. Reboot - then you have Root, TWRP?
6. Upgrades can than be done in TWRP by installing the files and than intalling again TWRP and afterwards Magisk?
Best
Axel

It appears you are asking. If I am incorrect, my apologies. With the 6t (also a a/b OP device)
The process I always used was
1) reboot to bootloader
2) boot twrp.img
3) install twro zip
4) reboot recovery
5) upon TWRP reboot, install magisk
6) profit.
Anytime I tried to go ahead and install Magisk in the same round as installing TWRP, it would install to the opposite slot making me have to do the whole process over again. Ymmv

XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !

barguybrady said:
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.

MrSteelX said:
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
Click to expand...
Click to collapse
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...

barguybrady said:
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
Click to expand...
Click to collapse
You should start a separate thread for all that. Kinda want to keep on topic to make it less confusing for everyone

Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works

mattie_49 said:
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Click to expand...
Click to collapse
Just installed it - thanks OP.
Does anyone know if I can jdirtyflash the global rom 11.2.7.7 over the EU rom which is currently on 11.2.7.7 in twrp?
I was originally on global (le2110) but flashed EU via update. Now I want to go back to global.

applyscience said:
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
Click to expand...
Click to collapse
Full system everything. User data. ? Did it work

mattie_49 said:
Full system everything. User data. ? Did it work
Click to expand...
Click to collapse
i dont know i have been bricked for 5 days ever since i attempted the lineage release

applyscience said:
i dont know i have been bricked for 5 days ever since i attempted the lineage release
Click to expand...
Click to collapse
Just lineage no kernel no special cam?

mattie_49 said:
Just lineage no kernel no special cam?
Click to expand...
Click to collapse
nah. just lineage. pretty sure i deal with support again tomorrow. fun...

Need help...
I typed Fastboot boot twrp.img instead of fastboot flash boot twrp.img
And that was to boot_a
So then i tried fastboot flash boot_b twrp.img
It wont load the recovery now. Phone wont boot up unless i
fastboot boot patched11.2.7.7DA.img
I even try to install Magisk directly and it fails.
Can I get some help. Dont even wanna restart my phone.
Thank you
All Good Now..... I Figured It Out!

How to fix this

id avoid TWRP if on 11.2.8.8 already. it can boot from fastboot and even install itself as your recovery but it will not mount data. i tried the refresh sizes trick in backup and then the default_password for password to decrypt and nothing. pretty sure twrp mishaps are what bricked my phone last too . thankfully it still boots, just the recovry section is effected
ill try and flash the OTA zip tomorrow. sick of messing with it for now lol

Are we still avoiding twrp

Question Why are custom ROMs bricking my device?

Hello everyone, I have the OP9 china varient,
I've flashed custom ROMs in some devices in the past, specially on a Poco F1 and a Mi 11 Ultra (flashed MIUI.EU in it several times). With the OnePlus 9 the process with unlocking the bootloader was a bit different but I got it to work. But when it comes to custom ROMs installation, the end result is always a bricked device and I had to use MSM from OP9 pro to unbrick and then OP9 MSM to get the device back to normal. I've downgraded everytime to OxygenOS 11 but it didn't work. Can someone help me find out what am I doing wrong?
My procedure besides unlocking the bootloader was:
1. Install boot.img
2. From fastboot to recovery
3. Wipe everything (tried not doing it with the same result)
4. Install ROM via ADB (as an update)
5. Wipe everything (tried not doing it with the same result)
6. Reboot
7. Brick..
I've considered it being an ADB drivers problem, but the device is recognized in the computer as an ADB device so I don't think it is.
As I install through ADB, the CMD window keeps the percentage going up but on the device it never shows anything ROM related as it is being installed, just the final message saying steps 2/2 had been completed.
Thanks in advance, and happy flashing guys!

Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.

EtherealRemnant said:
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
Click to expand...
Click to collapse
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.

lleonardocruzz said:
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
Click to expand...
Click to collapse
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.

EtherealRemnant said:
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
Click to expand...
Click to collapse
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.

lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
It's only mentioned in the Stag thread and I think Lineage too but it should work with every ROM since it's only a recovery script that copies the partitions.

lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue

mattie_49 said:
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
Click to expand...
Click to collapse
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this

lleonardocruzz said:
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
Click to expand...
Click to collapse
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.

Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you

lleonardocruzz said:
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
Click to expand...
Click to collapse
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.

Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.

mattie_49 said:
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Click to expand...
Click to collapse
EtherealRemnant said:
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.
Click to expand...
Click to collapse
cbrown666 said:
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
Click to expand...
Click to collapse
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help

lleonardocruzz said:
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
Click to expand...
Click to collapse
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.

EtherealRemnant said:
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
Click to expand...
Click to collapse
I have to agree with both. I'm also a global unit op9 unlocked on C-48 rooted. Anything that is usually still maintained/updated and not deserted is better than custom. Cherry picking and flashing is overrated. Stock isn't bad at all. You guys enjoy your devices.

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?