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

[ROM] LineageOS 15.0 Unofficial Rom

<code>
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
</code>
Starting Development on Lineage 15.0. This will hopefully track my progress
Prerequisites:
TWRP
Unlock Bootloader
What Works?
- Don't Know Yet
What's broken ?
Probably Everything
Download Links
ROM:
Coming Soon
Trello:
https://trello.com/b/K9fXDV9L/lineageos-zenfone3
TWRP:
https://drive.google.com/drive/folde...zNmTmpzSWthMTQ
GAPPS:
http://opengapps.org/
Source Code:
https://github.com/LineageOS-Zenfone3
XDA:DevDB Information
Lineage 15.0, ROM for the Asus ZenFone 3
Contributors
mdigiacomi, mdigiacomi
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Testing
Created 2017-10-06
Last Updated 2017-10-06

Reserved for stuff

Fun Fact: Lineage 15.0 is 85,000+ source files.

Great!!!

Nice!!

Reserve hahahhaha nice

Oreo yeah :victory:

WoooW !!! Nice. Good Work !!!!!

Hello,
Do you think in this new version the "roaming bug" will be fixed ?
I have tried all custom roms available (lineage 14.1, ViperOS and RR) and any is working for data in roaming.

Niteshakee said:
Hello,
Do you think in this new version the "roaming bug" will be fixed ?
I have tried all custom roms available (lineage 14.1, ViperOS and RR) and any is working for data in roaming.
Click to expand...
Click to collapse
To solve data roaming issues you just have to flash the latest stock rom using the stock recovery, start it up, then reinstall your custom rom of choice. Backup your data first!
At least this has worked for me with LineageOS 14.1 (using the stock rom version "WW-14.2020.1708.56").
I've had a hard time figuring this out - I even compiled the ROM myself, trying anything I could imagine to solve this.
By flashing the stock rom properly all the special firmware partitions the phone has get updated too - the bug is in one of them, not the rom itself.
A custom rom installation normally doesn't touch those partitions.

planet9 said:
To solve data roaming issues you just have to flash the latest stock rom using the stock recovery, start it up, then reinstall your custom rom of choice. Backup your data first!
At least this has worked for me with LineageOS 14.1 (using the stock rom version "WW-14.2020.1708.56").
I've had a hard time figuring this out - I even compiled the ROM myself, trying anything I could imagine to solve this.
By flashing the stock rom properly all the special firmware partitions the phone has get updated too - the bug is in one of them, not the rom itself.
A custom rom installation normally doesn't touch those partitions.
Click to expand...
Click to collapse
Thanks a lot.
It's true I upgraded from stock 6.0.1 to lineage 7.1.2
Now i flashed back to latest stock (7.0) but with twrp recovery: it's work fine ( i have only a weird message about dm-verify on boot.)
So if now if I flash lineage with twrp you think the bug disappear ?

Niteshakee said:
Thanks a lot.
It's true I upgraded from stock 6.0.1 to lineage 7.1.2
Now i flashed back to latest stock (7.0) but with twrp recovery: it's work fine ( i have only a weird message about dm-verify on boot.)
So if now if I flash lineage with twrp you think the bug disappear ?
Click to expand...
Click to collapse
I'm not sure if TWRP updated those partitions so it's possible it doesn't work...
I think you should reflash the latest stock rom with the right stock recovery, then reinstall the latest TWRP and Lineage.

planet9 said:
I'm not sure if TWRP updated those partitions so it's possible it doesn't work...
I think you should reflash the latest stock rom with the right stock recovery, then reinstall the latest TWRP and Lineage.
Click to expand...
Click to collapse
Yes right , i am doing his right now :good:

Hello,
you mention the "data" issue on roaming. Do you mean to unlock Band 20?
I have a ZE520KL TW version and rooted it, now I try to make Band 20 working,
but without success. Should i try LineageOS15.0 and will it help or not at all?
Thank you.

Does this work on the ZC520TL X008D? I don't mind testing I just want to make sure it doesn't brick my phone before a blind flash.

Please make rom for ZC551KL. We haven't a custom rom or kernel. i'm so unhappy.

Is the project stopped? No new activity on trello

Any development for Zenfone 3 Laser ? I'm tired it's problems and system.

MoNgoLHİMİK said:
Any development for Zenfone 3 Laser ? I'm tired it's problems and system.
Click to expand...
Click to collapse
oreo

OreoBooyah said:
oreo
Click to expand...
Click to collapse
Asus's firmware or Custom Firmware ? If Asus's firmware , i don't want. Me and A lot of Z3 Laser users need Custom Firmware.

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.

[PATCH] Post-install patch for GSI ROMs 2.0.0

Hello XDA, this patch is intended to fix issues that arise from using phh-based Treble GSIs. This patch aims to make
life bearable on these ROMs and to add the functions that are missing from EMUI 8 and the OpenKirin ROMs. With
this patch you can use any working Pie or 10 GSI and have a complete experience, having to do as few manual tweaks as
possible.
What this patch does:
- Restores offline charging functionality
- Fixes crash on Bluetooth/NFC section in settings
- Fixes headphone jack detection
- Fixes the missing apps in Play Store
- Fixes battery stats behavior by supplying a correct power profile
- Fixes the lack of Night Light in AOSP-based ROMs
Tested P GSI ROMs:
- AOSP 9
- LineageOS 16.0 (AndyYan)
Tested Q GSI ROMs:
- AOSP 10
- LineageOS 17.1 (AndyYan)
Tested R GSI ROMs:
none
Installation:
1 - Flash eva_amend_x.y.z.zip on TWRP
2 - Wipe cache
3 - Reboot
Download:
here
Source:
You can analyze the patch to see the source code.
Credits:
lo_ol, hi6250 community, Wattsensi

Changelog
Code:
2.0.0
- Removed redundant fixes
- NFC is now responsibility of the GSI. This NFC fix was wrong on so many levels I can't even begin to describe.
- All prior versions removed from Google Drive
1.1.0
- Add HWComposer fixes
1.0.0
- Initial release

This looks really promissing - thanks a lot! How about fixing the issue with wifi hotspot for P9? Would that be doable as well?

@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone. On my (much newer) Nubia RM3, I unlocked the bootloader, flashed recovery, flashed the GSI and tadaaa.
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you

Nightwish1976 said:
@Wattsensi The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Click to expand...
Click to collapse
Basically you shall first rebrand and upgrade to Oreo to get treble support, here is how:
https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2

@xaweryp Thanks a lot for the input, now I'm downloading the files necessary to rebrand and update to Oreo.
LE: just finished updating to Oreo.
Can I just flash an A only Arm64 GSI, or are there another steps? I have that new recovery (Pretorianos80 v4), but I think it cannot access the internal storage...

Nightwish1976 said:
@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone. On my (much newer) Nubia RM3, I unlocked the bootloader, flashed recovery, flashed the GSI and tadaaa.
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you
Click to expand...
Click to collapse
Nightwish1976 said:
@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone.
Click to expand...
Click to collapse
Hello. This device is abandoned, we're pretty much 1 or 2 developers working here. Yeah, I agree about the phone being complicated. It has so many quirks compared to my Galaxy S7 where everything just works out of the box.
This phone is not newcomer friendly, but with effort you can get through.
You can indeed install an Android 10 GSI but it's a poor user experience. Your choices are limited with this device, right now we have no working camera or NFC on 10. If you don't care running an older version of Android but still secure you can try @MSe1969's LineageOS 16.0 builds which incorporate the latest security patches and are updated monthly.
That ROM is designed to be used without GApps so keep that in mind.
Nightwish1976 said:
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you
Click to expand...
Click to collapse
First of all, do you have your unlock code in hand? You will need it when you perform the needed rebranding procedure. This will reflash your phone with a Chinese ROM so you can OTA-update to Oreo, which introduces Treble functionality into the device. Rebrand, update to Oreo and flash the latest (as of 09/2020) 8.0.0.550 firmware. Then flash the needed network patches to make your radio work, and then decrypt and install TWRP.
First, go there:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
The second post contains upgrade instructions and be careful. Cheers!

Updated the patch. Now NFC functionality is responsibility of the GSI and removed useless stuff.

[UNOFFICIAL] [TWRP] [PDX206] twrp for sony xperia 5 ii [FBEv2]

Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Working :
Basic twrp features
partially dual boot (different rom can be boot on both slots but still share same userdata, recommend to use fastboot method)
Decryption only support for fbev2 rom (example is some older rom, and kyasu lineageos)
otg / sdcard
Issues / Notes :
vibration is really wonky (which only happened on twrp, not orange fox) not quite fix, but it's stable enough to confirm
you might need to reflash rom "once" after you boot into recovery (flash twrp > boot to twrp > reboot to system (you'll see system corrupt) then reflash same rom that you currently using (via fastboot or twrp if rom support), after that it'll be fine. only on custom rom, stock is fine)
doesn't works with kyasu lineage due to using device model as ota assert (different than twrp ota assert, which is pdx206) fixed in latest build
doesn't support stock, due to different decryption key
ext4 only, no erofs and other models for now (1 ii and pro might release later, busy working new device tree for kumano)
format data, before flashing any rom (unless you doing a dirty flash)
For Stock users, use THIS TWRP instread this one
Big thanks :
most users on telegram for testing
christopher, for send me the device
clfbbn for kernel source
skkk (sekaiacg) for base device tree
Download : Link
device tree :
https://github.com/lolipuru/twrp_sony_pdx206
https://github.com/lolipuru/kernel_sony_sm8250
donation :
contact me via pm due to paypal is no longer able to receive money here

Nice work dude finally some development

I tested and it works on kyasu lineageos...

Nightmare_19 said:
I tested and it works on kyasu lineageos...
Click to expand...
Click to collapse
OTA probably won't work

The Xperia5ii PDX206 doesn't have an official LineageOS, so OTAs don't do much.

Nightmare_19 said:
I tested and it works on kyasu lineageos...
Click to expand...
Click to collapse
there's some problem on some roms for missing ota assert (tested on ricedroid), but if it works. no problem

Cannot install .zip files, neither slot A nor B work.

Nightmare_19 said:
Cannot install .zip files, neither slot A nor B work.
Click to expand...
Click to collapse
lineageos zip?
if lineageos zip, no it don't works. (different ota name)

Can install in au(Japan) version?

rifzan said:
Can install in au(Japan) version?
Click to expand...
Click to collapse
none of my tester (including me) have au devices, but if custom rom works then twrp should be fine

Sorry, but I didn't understand with which ROM(s) and version does this TWRP works.

And any OrangeFox would possibly be developed?
Well, thqnks for your replies

Yoannjap said:
And any OrangeFox would possibly be developed?
Well, thqnks for your replies
Click to expand...
Click to collapse
join xperia group on telegram you will find what you need there

Yoannjap said:
Sorry, but I didn't understand with which ROM(s) and version does this TWRP works.
Click to expand...
Click to collapse
tl;dr
- twrp works on android 12 (but decryption doesn't works on stock)
- twrp can't install lineageos (due to different device target, mine use pdx206 and lineage uase xq-as72)
(we're already discussed about device ota on dev group, so i'll use pdx206 for now, more custom rom in future will use pdx206 as target device)

Ok then, I am a real noob, I don't understand what does mean "PDX206".
I don't understand what you mean saying ‘due to different device target, mine use pdx206 and lineage uase xq-as72’.
To me, the XQ-AS72 is the code of the South Asian variant of Xperia 5 ii, whereas XQ-AS62/52/42 other variants.
Whereas PDX206 is just a codename meaning Xperia 5 ii (whatever variant of XQ-ASXX it is) used by I dunno who.
Am I wrong?

Yoannjap said:
Ok then, I am a real noob, I don't understand what does mean "PDX206".
I don't understand what you mean saying ‘due to different device target, mine use pdx206 and lineage uase xq-as72’.
To me, the XQ-AS72 is the code of the South Asian variant of Xperia 5 ii, whereas XQ-AS62/52/42 other variants.
Whereas PDX206 is just a codename meaning Xperia 5 ii (whatever variant of XQ-ASXX it is) used by I dunno who.
Am I wrong?
Click to expand...
Click to collapse
it's ota assert (in this case, target_device) that custom rom is set when flashing (to avoid flashing into wrong device)
lineage has been set for xq-as72 as default (don't confuse with device variants, ota assert or target_device doesn't affect with device variant that you use)
and twrp have been set to pdx206 (which is device codename for 5ii) so that's main reasons why it can't flash lineageos (but you can still access data normally)

Ok
Thank you loipuru, I got it now.

update,
- add xq-xx72 for lineageos flashing
the rest like /oem (for japanese variant) ltalabel and ta will come out later