Database Info

Havoc Pie downgrade to Havoc Oreo doesnt work

Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.

RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.

i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led

RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.

thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.

RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).

do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.

RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.

hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now

RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.

i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom

RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.

i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year

[Delay Touch in PUBG Mobo] - Solution !!

Hello guys !
I've a poco with nvt panel and its has delay touch issue for long times. I flash many custom rom and custom kernel but its still there.
Now delay issue has gone away after i do those steps. I had tested on my poco and my friend, we have nvt panel both.
You should unlock bootloader and twrp installed, i used 3.3.0.0. Download xiaomi eu stable 10.3.8.0 (android 9) and xiaomi eu weekly 8.10.25 (android 8.1) to your storage, and download kernel Arter97 r11 from xda.
Do this at your own risk!
1. Flash and settings up xiaomi eu 10.3.8.0 rom completely (Android 9 stable). Then reboot to recovery.
2. Backup boot, system, vendor, data partitions.
3. Wipe boot, system, vendor, data then reboot to recovery.
4. Flash xiaomi eu 8.10.25 with DFE and magisk. After that you can reboot to system or simply reboot to recovery without setting up new rom.
5. In recovery, choose restore boot, system, vendor, data from step 2. Remember that just restore and dont flash 10.3.8.0 again.
6. Flash Magisk, DFE, custom kernel Arter97 r11.
7. Reboot to system and enjoy.
I dont know how its work so dont ask me why. Dont use Android 10, bootloop. Pubg mobo is now smooth and dont make you angry anymore.

module?

spindlygaming said:
module?
Click to expand...
Click to collapse
I dont use any module except systemless host. Module is not affects my solution.

Summary :
- Flash your favor rom, kernel, module.... I call A. Dont use Android 10, doesn't work.
- Boot to system and optimize yourself.
- Backup A including Data in TWRP 3.3.0.0.
- Flash xiaomi eu 8.10.25 with DFE, after that reboot to recovery (dont need to reboot to system).
- Dont wipe anything, just restore A and reboot to system. Enjoy!

thithi1983 said:
I dont use any module except systemless host. Module is not affects my solution.
Click to expand...
Click to collapse
even thermal mod
---------- Post added at 09:08 AM ---------- Previous post was at 08:52 AM ----------
thithi1983 said:
Summary :
- Flash your favor rom, kernel, module.... I call A. Dont use Android 10, doesn't work.
- Boot to system and optimize yourself.
- Backup A including Data in TWRP 3.3.0.0.
- Flash xiaomi eu 8.10.25 with DFE, after that reboot to recovery (dont need to reboot to system).
- Dont wipe anything, just restore A and reboot to system. Enjoy!
Click to expand...
Click to collapse
why not flash firmware 8.10.25
than flash rom

You don't have to do all this to fix touch issues on nvt... Just flash your favorite kernel with the 9.1.24 touch drivers and that's it. And that's regardless of the Android version (not sure about Oreo tho but I guess at this point everyone is either on Pie or Q anyway). I use arter97 r9 in every ROM I flash because it's very stable and uses the 9.1.24 touch drivers which are the best for nvt panels. This firmware has almost no touch delay and scrolling is perfect.

mario123m said:
You don't have to do all this to fix touch issues on nvt... Just flash your favorite kernel with the 9.1.24 touch drivers and that's it. And that's regardless of the Android version (not sure about Oreo tho but I guess at this point everyone is either on Pie or Q anyway). I use arter97 r9 in every ROM I flash because it's very stable and uses the 9.1.24 touch drivers which are the best for nvt panels. This firmware has almost no touch delay and scrolling is perfect.
Click to expand...
Click to collapse
r9 is very old

spindlygaming said:
r9 is very old
Click to expand...
Click to collapse
I don't see how this is a problem if everything works perfectly fine.

spindlygaming said:
module?
Click to expand...
Click to collapse
mario123m said:
You don't have to do all this to fix touch issues on nvt... Just flash your favorite kernel with the 9.1.24 touch drivers and that's it. And that's regardless of the Android version (not sure about Oreo tho but I guess at this point everyone is either on Pie or Q anyway). I use arter97 r9 in every ROM I flash because it's very stable and uses the 9.1.24 touch drivers which are the best for nvt panels. This firmware has almost no touch delay and scrolling is perfect.
Click to expand...
Click to collapse
Have you play PUBGm on poco f1? I try many kernel including arter97 r9 and twisted prime 9.1.24 touch driver. Delay touch still happen when i play with 4 fingers claw. Only solution i wrote solved the problem.

spindlygaming said:
even thermal mod
---------- Post added at 09:08 AM ---------- Previous post was at 08:52 AM ----------
why not flash firmware 8.10.25
than flash rom
Click to expand...
Click to collapse
I want to flash only vendor but i dont know how to convert vendor.new.dat.br to vendor.img

Flash rom then backup vendor IMG in twrp

JV Spartacus said:
Flash rom then backup vendor IMG in twrp
Click to expand...
Click to collapse
Thanks! You open my mind!

thithi1983 said:
Thanks! You open my mind!
Click to expand...
Click to collapse
Will you share it here so that noobs like me can get it easily.

zip file error problem
thithi1983 said:
Hello guys !
I've a poco with nvt panel and its has delay touch issue for long times. I flash many custom rom and custom kernel but its still there.
Now delay issue has gone away after i do those steps. I had tested on my poco and my friend, we have nvt panel both.
You should unlock bootloader and twrp installed, i used 3.3.0.0. Download xiaomi eu stable 10.3.8.0 (android 9) and xiaomi eu weekly 8.10.25 (android 8.1) to your storage, and download kernel Arter97 r11 from xda.
Do this at your own risk!
1. Flash and settings up xiaomi eu 10.3.8.0 rom completely (Android 9 stable). Then reboot to recovery.
2. Backup boot, system, vendor, data partitions.
3. Wipe boot, system, vendor, data then reboot to recovery.
4. Flash xiaomi eu 8.10.25 with DFE and magisk. After that you can reboot to system or simply reboot to recovery without setting up new rom.
5. In recovery, choose restore boot, system, vendor, data from step 2. Remember that just restore and dont flash 10.3.8.0 again.
6. Flash Magisk, DFE, custom kernel Arter97 r11.
7. Reboot to system and enjoy.
I dont know how its work so dont ask me why. Dont use Android 10, bootloop. Pubg mobo is now smooth and dont make you angry anymore.
Click to expand...
Click to collapse
pleaseeeee help meeeeeeee
please give me a link for arter 97 kernel for poco f1
when i flash the kernel it error zip file pleaseeeeee

mahdih78 said:
pleaseeeee help meeeeeeee
please give me a link for arter 97 kernel for poco f1
when i flash the kernel it error zip file pleaseeeeee
Click to expand...
Click to collapse
Dont save zip file in sd card, error in some case.
Store it on internal storage and flash it.

how???
thithi1983 said:
Dont save zip file in sd card, error in some case.
Store it on internal storage and flash it.
Click to expand...
Click to collapse
i dont know how to flash it without zip file
i cant find the link of that kernel you said
please give me the link and please help me how to install that kernel
i installed the 8.25.10 eu but i couldnt install the kernel you said
help pleaseeeeee

mahdih78 said:
i dont know how to flash it without zip file
i cant find the link of that kernel you said
please give me the link and please help me how to install that kernel
i installed the 8.25.10 eu but i couldnt install the kernel you said
help pleaseeeeee
Click to expand...
Click to collapse
Ok there you go.
https://forum.xda-developers.com/poco-f1/development/arter97-kernel-poco-f1-t3919127

thithi1983 said:
Ok there you go.
https://forum.xda-developers.com/poco-f1/development/arter97-kernel-poco-f1-t3919127
Click to expand...
Click to collapse
Arter97 has made it paid I can't download it from this thread

how to install it and made it paid
ThePrathamesh said:
Arter97 has made it paid I can't download it from this thread
Click to expand...
Click to collapse
yeah he is right
i dont know how to install it without zip file
help please man
is your pubg mobile working good know or still have touch delay with this kernel ???

arter kernel download link.
t.me/s/PocoRomNews/2565?q=%23arter

CUstom ROM installation problem, please help

Hi to everyone. I have a european version of the op7 pro. The device produces an issue when using android auto, which I use daily (the bottom bar is rarely responsive to my touches whereas the rest of android auto works fine). So I wanted to try a custom ROM and see if the problem persists.
I tried multiple roms like havoc, aosip and lineage following the respective guides of installation, but regardless of the ROM, I always get stuck at the startup animation when I first try to reboot to system after installing twrp, magisk, gapps etc.
The only rom that seems to work is any version of OOS.
Any help would be greatly appreciated!

Exact what steps you do when installing a custom ROM?

U need to explain how you flash those OS; from my experience on OP6 -> flashing a third party rom need to update it' firmware to match the rom u try to flash, or else it cannot go into system definitely!

Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps

Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system

pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
What oos do I flash? Would you mind linking me to it?:good:

Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
Latest android 10 stable rom available for your phone.

pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.

c3drik 67 said:
Latest android 10 stable rom available for your phone.
Click to expand...
Click to collapse
Is that the same as going back to stock with the MSM tool?
Like this one: https://androidfilehost.com/?fid=4349826312261732239

poulidis said:
Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps
Click to expand...
Click to collapse
You must Format internal storage before booting into Custom ROM.
Also, when you flash a Custom Rom, when it's done flashing, reboot once more to recovery and then flash the rest like Gapps, Magisk, etc... (Keep in mind that some custom ROMs require once time boot before flashing Magisk).

Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
GöğüstekiDövme said:
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.
Click to expand...
Click to collapse
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?

pranacrockz said:
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?
Click to expand...
Click to collapse
Oos O2 Beta 11 now. Back when I try, it was oos beta 10. None of custom roms sensors were not working. Like Pixel exp, havoc, lineage
Sent from my OnePlus7Pro using XDA Labs

Never use beta. Always use stable

pranacrockz said:
Never use beta. Always use stable
Click to expand...
Click to collapse
I'll try one more time later. Thanks.

Can't install Pixel Experience Custom Android 12

I have been struggling to install Pixel Experience Android 12 on my Poxo X3 NFC.
I had PE Android 11 before. When I tried to flash Android 12 I get following error
assert failed: update_dynamic_partition(package_extract_file("dynamic_partition_op_list"))
Updater process ended with ERROR: 1
Error installing zip file ...
What I tried
1, Install latest firmware
2. Format Data
3. Wipe data, dalvik, cache
3. Sideloading Custom Rom
Can someone help me to revive my device please?
Thanks a lot

Hello, on my wife's X3NFC I had to flash the latest Full ROM (12.5.7) via Fastboot.
Then I was able to install the lA12 PE. I don't know why I had to do this, but it worked.
She didn't like A12 PE and now A11 PE is running again on her Phone
Maybe (I heard about that) it works too, if you only flash the super.img from latest Fastboot-Image via Recovery.

SmartJuwel said:
Hello, on my wife's X3NFC I had to flash the latest Full ROM (12.5.7) via Fastboot.
Then I was able to install the lA12 PE. I don't know why I had to do this, but it worked.
She didn't like A12 PE and now A11 PE is running again on her Phone
Maybe (I heard about that) it works too, if you only flash the super.img from latest Fastboot-Image via Recovery.
Click to expand...
Click to collapse
I installed MIUI fastboot rom. Then I tried to flash PE A12 rom without any issues. But after successful completion, phone reboots to bootloader (Fastboot). Can you tell me what I am doing wrong?
Can you please give me steps to install PE after you've installed MIUI fastboot rom?

1st installed latest MIUI via MiFlash
Booting successful into MIUI
Flashing TWRP in Fastboot-Mode
Booting into TWRP, install ROM, wipe Caches and format data.
Reboot Phone

i'm in this very predicament. Still on PE11 Plus Edition and can't flash PE12 giving me the very same ERROR. Can someone pls post the sure way to get this done properly? Links to roms that must be flashed first would be very appreciated...

Snakeatermgs said:
i'm in this very predicament. Still on PE11 Plus Edition and can't flash PE12 giving me the very same ERROR. Can someone pls post the sure way to get this done properly? Links to roms that must be flashed first would be very appreciated...
Click to expand...
Click to collapse
SmartJewel (Post above you) told you how to do it

Development OP9-LEMONADE-A13-ROM-WATCHDOGS-JUNE 25, 2023

I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.

Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.

I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!

Telegram group please

lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.

I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with

lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!

I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.

incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.

TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro

TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.

lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.

incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.

I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?

Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.

screenshots?

pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it

MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip

Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img

You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.