Database Info

[ELITE KERNEL][Honor 8] For Build CxxB36x by HassanMirza01

DESCRIPTION:
Hey guyz..... Me Hassan Mirza from Pakistan
Today am here with a new thread and I Have a good news for you....
As you know, The other methods are old now and also, in Nougat, there is root which needs to mount system each time you need to use it,,, so Today, your system mount and root problem solved... Phh or Magisk, you choose
Releasing Elite Kernel v2 ported from P9 Lite
Its PreRooted, System RW available for all time, Titanium backup works perfectly and Magisk work too for it to hide root
With this you can flash anything and see in SYSTEM ! VIPER...adaway no systemless...etc...
DISCLAIMER:
I will Provide correct info and help......All This you are gonna do is At your Own Risk... Damage to your device of any type is at your Own Responsibility,,, Don't point finger at me or I will Just Laugh at you...
Install:
1.) Download this Elite Kernel for Honor 8 CxxB36x v2
2.) Put in Root of SD Card.
3.) Flash this in Latest Recovery for Nougat.
4.) See if Superuser app installed, if not install Phh Superuser from google play.
5.) And you are ROOTED.
The file it's boot.img is based upon L04-C567B360, modded and signed for boot.
Its Adviced to remove pattern Lock and Fingerprint Lock before installing.... just adviced,,,
If you like, donate
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
Changelog in 2nd post...
This is Based on Stock Huawei Kernel, Not compiled by Me...
Contributors:
@HassanMirza01 for doing all this
@phhusson for his wonderful work of making Phh superuser
@Telperion as he got my attention for doing this
Status:
Status: Stable
Stable Release Date: 2017-04-27
Created on: 2017-04-04
Last Updated on: 2017-04-27

CHANGELOG:
2017-04-04 Elite Kernel for B3xx by [email protected] v1: Initial release,
2017-04-27 Elite Kernel for B3xx by [email protected] v2: The Most wanted MagiskSU released with Proper Support,,, Use with Cautions...

This is all really good stuff.
Thank you for sharing your work
John

Guyz if this kernel didnot working, booting for you or crashing your settings app,,, send me the boot.img file of your own variant of Honor 8... I will see into it...

awesome! Thanks for your hard work on this! Will this work with the LineageOS build that @surdu_petru and team have been working on?

I think no.... Like Lineage 14.1 for P9 lite,,, we need to go to MM to install it... So lineage kernel according to my guess, works on MM based roms so Elite Kernel wont work with it :/

HassanMirza01 said:
I think no.... Like Lineage 14.1 for P9 lite,,, we need to go to MM to install it... So lineage kernel according to my guess, works on MM based roms so Elite Kernel wont work with it :/
Click to expand...
Click to collapse
So this doesn't work on nougat? I guess the support for magisk tells me it doesn't. Bummer.

If the kernel is based on B360 then it should work with N and not MM. The Lineage rom right now is using the stock N kernel with no changes to it. They are not building a N kernel inline with Lineage as there's no source code out for it.
I guess my question is, would it be possible to flash Lineage, and then flash this kernel over it?

my Kernel is on Nougat based ROM not on MM but someone should try it on lineage too.....and tell the result...

@HassanMirza01 -- kernel works and PHH SU works and can R/W /system/. One issue I noticed however is that "Revoke USB Debugging Authorizations" has disappeared from my Developer menu. On the Honor 8 with Nougat I frequently have to revoke and reset authorizations to get it to work properly. I was able to get it working again by flashing the stock boot and rooting with the linked zip.
Magisk, however, crashes the phone on installation attempt, even with SELinux set to permissive. It causes a reboot when 'setting up the environment' either through Magisk Manager or TWRP. It appears that the P9 Lite kernel must have proper loop support whereas the Honor 8 still doesn't even with tweaks. It was speculated that since on the P9 Lite Magisk wouldn't work on Nougat, but on the P9 Lite after flashing this kernel and flashing Magisk in permissive SELinux mode, it installed successfully, that a similar path might work on the Honor 8. Then again, perhaps something is workable.
Either way, thanks for looking into this. :good:
https://drive.google.com/file/d/0B0zE1Kk8sIB6eVplODFjaTh4Q0U/view?usp=drivesdk

i will release a next build soon for some bugs fixes.... also, magisk proper support is coming soon,,,

Here's a log of what happens when I try to flash Magisk.

bro send me recovery log,,, i cant understand the one you send above...

Here is a zipped boot.img for honor 8 frd-l19 C432b360

HassanMirza01 said:
bro send me recovery log,,, i cant understand the one you send above...
Click to expand...
Click to collapse
Unfortunately Recovery crashes before it can write what happened to the log. That kernel crash log up above is the closest info we can probably get.
I attached the TWRP log though anyway.

Telperion said:
Unfortunately Recovery crashes before it can write what happened to the log. That kernel crash log up above is the closest info we can probably get.
I attached the TWRP log though anyway.
Click to expand...
Click to collapse
Also another log, this one shows the beginning stages of the flash and where the crash happens. (Search Magisk in the text file)

Expected release date: when kernel source comes out.
Just to makes this clear, we have no proper loop support and thats why magisk will not work (just take the dmesg from the user above as example, it tries to create a new loop volume and directly crashes ..)
Regards

svardman said:
Here is a zipped boot.img for honor 8 frd-l19 C432b360
Click to expand...
Click to collapse
Bro i didnot find the boot.img in your provided zip... Just check the size of your uploaded zip...

HassanMirza01 said:
Bro i didnot find the boot.img in your provided zip... Just check the size of your uploaded zip...
Click to expand...
Click to collapse
My Bad, gonna fix it later on today,

Does the new version of TWRP thats released help this ?
I know i was finnaly able to just Flash TWRP > flash SUPERSU 2.79 to root and thats it ! no pre modfiied boot.img needed . perfectly working now

android oreo 8.1 firmware leak for alldocube power m3

android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
a offical oreo 8.1 firmware with google play for power m3:http://www.mediafire.com/file/qev79...2B32.Neutral.8.1.V01.01.20190118user.zip/file

The firmware is working. One problem: after installation in TWRP package OpenGapps the system crashes. I couldn't find the replacement option (arm64, 8.1). Energy saving is good. Root access - Magisk.
P.S.: Build OpenGapps UNOFFICIAL is suitable for installation and works after components are updated (for example, with Yalp Store or Aurora App Store, F-Droid & etc.)
P.P.S.: If someone decides to install the firmware - must first make a backup of the NVRAM!!! Because the firmware will have to be installed with formatting and the nvram section will die. After flashing the firmware, it must be restored from the saved backup.

For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179

Hai_Duong said:
For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179
Click to expand...
Click to collapse
Take my version TWRP specifically for Oreo (the same in Russian how to install and patched Magisk boot.img to obtain root-rights): hire.
The saturation of the screen is comfortable for me, Occasionally settings of installed programs fly off.
TWRP Oreo
patched boot

config.gz in /proc fs
wangyiling said:
android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
Click to expand...
Click to collapse
running linux kernel was configured to have /proc/config.gz. The configuration for this is found in
General setup
[*] Kernel .config support
[*] Enable access to .config through /proc/config.gz

with oreo 8.1...
treble checker reports device to be supported by Project - only with A-partition.
did anyone tried out to switch to GSI image?

cmarxmeier said:
tried out to switch to GSI image
Click to expand...
Click to collapse
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.

https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .

wangyiling said:
also some one can try this new power m3 8.1 firmware
Click to expand...
Click to collapse
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH

ViAlexSt said:
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.
Click to expand...
Click to collapse
ViAlexSt said:
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH
Click to expand...
Click to collapse
nice

wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.

cmarxmeier said:
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.
Click to expand...
Click to collapse
for imei restore ,i think mtk sn write tool will do some help

wangyiling said:
for imei restore ,i think mtk sn write tool will do some help
Click to expand...
Click to collapse
mtk sn write tool did the job. - shows up with correct IMEI and VoLTE 4G.
patched boot.img with magisk
- works like a charm so far.
Looking forward to check USB-C Port with Icy Box to get Ethernet/HDMI device listed on USB-Bus.

wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...

fraddy91 said:
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...
Click to expand...
Click to collapse
Compile yourself by adding the lines:
# TWRP
......
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
Or Phils recovery.

Latest LineageOS ROM 15.1 20180625

Since it appears to be quite some trouble to obtain the last release of Lineage 15.1 for the A9 I share a copy of it
Flashable ZIP
484,78 MB
hiae
LINK (expires 01-12-2019)
(direct download from dropbox)
https://ea1.eu/LOS-hiae-20180625
ALTERNATIVE LINK
(Tresorit)
https://ea1.eu/LOS15-1_signed
Make sure you're on the last firmware and TWRP versions
Obtain GApps from www.opengapps.org (Android 8.1 arm64+)
Good luck and I salute our dead device

This is for hiaeuhl, right?

15.1 should be universal, u can use it on both versions

Is rom stable?

depends on what u mean by "stable" yeah it works and runs fine, but the main issue with Los 16 is u don't have any audio while call

Do I need to be on nougat firmware before I can flash this rom?
Sent from my 2PQ93 using XDA-Developers Legacy app

you should have the latest stock firmware + bootloader etc. installed before u flash it ( i think )

solved said:
you should have the latest stock firmware + bootloader etc. installed before u flash it ( i think )
Click to expand...
Click to collapse
True. Flash the latest stock firmware and boot all the way to setup. This way all partitions will be correctly mounted. Then flash TWRP followed by the ROM and GApps

Installation Package Error
I have an hiaeul phone, and i found an error in the update-script file. It attempts to mount a directory that does not exist. To correct, open the file and replace all occurrences of "/dev/block/platform/soc.0/7824900.sdhci/by-name/system" with "/dev/block/platform/7824900.sdhci/by-name/system".
NOTE: I am not sure if this holds true for other variations of HTC One A9, only edit if you get an error.

I found the problem
After installing Google framework service , have problems

All the links is dead, can you update the links

Cicada_3301 said:
All the links is dead, can you update the links
Click to expand...
Click to collapse
I would like to download because I flashed twrp and wiped data but did not backup and am on version 2

I don't know if it works but I found a download link for Lineage 15.1 "lineage-15.1-20190724-UNOFFICIAL-hiae.zip" https://androidfilehost.com/?fid=6006931924117923121

LineageOS 17.1 BETA TESTING

Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
EDIT: Join telegram group @clarkdev for beta testing or see development

Hi, i'm in!

DarkDroidDev said:
Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
Click to expand...
Click to collapse
Link?

i 'm in too..

Link?

@DarkDroidDev already sent the DM from telegram

Выложите пожалуйста √17

Development resumed, who want to see progress or help with testing, feel free to join telegram group
@clarkdev

Any chance you could provide links without telegram?
Not looking to add another messenger that I'll forget I have in 6 months lol

Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .

I'd also be interested but don't use Telegram

ac2323 said:
I'd also be interested but don't use Telegram
Click to expand...
Click to collapse
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.

Nice.

Wheels564 said:
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Click to expand...
Click to collapse
Yes, working nice.

@DarkDroidDev Hey, how did you extract the proprietary blobs? The instruction says that one needs to have an installable zip of LineageOS for clark, or already have the device runnning the LOS. I tried to extract it just from my stock Moto X Style with the script and it did something, but I'm not sure if it's going to work.
Edit: I'm also interested in testing the 17.1 build, since the one I'm trying to build following the instruction is 14.1 and actually it fails because of lack of some vendor files :/ But I'm also not interested in joining Telegram
Edit: Oh, I missed the @chrmhoffmann post!

hi, chrmhoffmann. thank you for your work.
chrmhoffmann said:
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
Click to expand...
Click to collapse
Hi, chrmhoffmann. Thank you for your work. I previously tested your 20200718 upgrade. I have installed the same date recovery and the latest magisk20.4. Unfortunately the system will not start. I also tried wipe system wipe cache wipe data and reinstalled it again, but it still didn't work.

I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.

kb8no said:
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
Click to expand...
Click to collapse
From what I've seed Darkdroiddev removed Clark from his Github so I assume he is no longer working on this phone and this thread is probably dead. Randomblame hasn't posted since February. chrmhoffmann's thread https://forum.xda-developers.com/mo...opment/unofficial-lineage-17-1-clark-t4123077 actually has a link to official Lineage gerrit which means we are well on our way to becoming official Lineage again. Meanwhile I'll keep posting LOS 14.1 for MMBL until we get there.

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.