Database Info

[GUIDE] Install Treble Roms on Honor 9

DISCLAIMER:
I'm not the developer of any of those Roms, so don't cry on me if your device gets bricked!
INTRODUCTION:
So, as many of you guys know, the Homor 9 is Treble compatible which means you can get any Treble Rom on it although the support of our device on XDA is really poor on our forum.
IMPORTANT ISSUES:
Since we don't even have an official TWRP for the Honor 9 but only some kind of a buggy one with missing encryption on Android 8.1 (I mean I'm thankful for what we have, but it's still sad), I was NOT able to flash Gapps afterwards, which means, either you have to get a Rom with implemented Gapps or live without them.
If anyone finds out a way to install them, please let me know!
REQUIREMENTS:
- Unlocked bootloader
- Any Android Oreo firmware installed
- Stock Recovery (as our TWRP can't wipe stuff)
INSTALLATION:
1. Look for your favorite Rom on the following link and download it:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
2. Reboot your device to bootloader
3. "fastboot flash system [downloaded img file]"
4. Reboot to stock recovery
5. Wipe cache and factory reset
6. Reboot and enjoy!
I hope I was able to get some of your hopes up for Honor 9 and custom roms!

Thank u! But i have one question about this Treble Rom's... is all working? ( BT, WLAN, Sound ect.?)

nscounter said:
Thank u! But i have one question about this Treble Rom's... is all working? ( BT, WLAN, Sound ect.?)
Click to expand...
Click to collapse
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.

Is it compulsory to wipe data for a new ROM to work, say for example i'm going form AOSP 8 to AOSP 8.1, should the data partition be compatible and not require wiping?
Iv'e always wiped /data in the past, but i cant be bothered this time since i don't want to re-install everything.

ambitiousButRubbish said:
Is it compulsory to wipe data for a new ROM to work, say for example i'm going form AOSP 8 to AOSP 8.1, should the data partition be compatible and not require wiping?
Iv'e always wiped /data in the past, but i cant be bothered this time since i don't want to re-install everything.
Click to expand...
Click to collapse
I dirty flashed a few times - even going from AOSP to RROS for example and it went fine for me. So just try it out, reboot with only wiping cache and if you experience bugs you can still do a factory reset. But just keep in mind that many developers don't support dirty flashing because bugs can happen easily when doing that and it's also not recommended.
PS: Don't dirty flash a Rom without Gapps if you're using a launcher that requires Google Play Services!

_lucx_ said:
I dirty flashed a few times - even going from AOSP to RROS for example and it went fine for me. So just try it out, reboot with only wiping cache and if you experience bugs you can still do a factory reset. But just keep in mind that many developers don't support dirty flashing because bugs can happen easily when doing that and it's also not recommended.
PS: Don't dirty flash a Rom without Gapps if you're using a launcher that requires Google Play Services!
Click to expand...
Click to collapse
Excellent, thanks, I'll give it a try, I'll make sure I disable or uninstall xposed and disable substratum beforehand, I guess the worst that can happen is a bootloop, and I can just reflash old system image if it doesn't work .

How does ADB work for you on the AOSP treble rom?

Really_Rekt said:
How does ADB work for you on the AOSP treble rom?
Click to expand...
Click to collapse
Just tested it... I don't seem to be able to get it to work. :/ I don't know what the issue is either...

Hi,
currently i have installed RRR from OpenKirin (https://forum.xda-developers.com/honor-9/development/rom-t3754856) with magisk. But i think this ROM isn't updated anymore.
My question is: Can i install Treble Roms directly over OpenKirins ROM?
---------- Post added at 09:37 ---------- Previous post was at 09:31 ----------
Really_Rekt said:
How does ADB work for you on the AOSP treble rom?
Click to expand...
Click to collapse
Hi,
there are problems with magisk and adp: https://forum.xda-developers.com/showpost.php?p=76777735&postcount=282.

Saftpresse99 said:
Hi,
currently i have installed RRR from OpenKirin (https://forum.xda-developers.com/honor-9/development/rom-t3754856) with magisk. But i think this ROM isn't updated anymore.
My question is: Can i install Treble Roms directly over OpenKirins ROM?
---------- Post added at 09:37 ---------- Previous post was at 09:31 ----------
Hi,
there are problems with magisk and adp: https://forum.xda-developers.com/showpost.php?p=76777735&postcount=282.
Click to expand...
Click to collapse
Yes, you can flash it on top of any Project Treble (Oreo) Rom or EMUI 8 (Oreo) using my guide.
Magisk is kind of working for me although it crashes quite often and I have to reinstall the Manager or reflash it entirely fron time to time.

_lucx_ said:
Yes, you can flash it on top of any Project Treble (Oreo) Rom or EMUI 8 (Oreo) using my guide.
Magisk is kind of working for me although it crashes quite often and I have to reinstall the Manager or reflash it entirely fron time to time.
Click to expand...
Click to collapse
Thank you.
I read about problems with magisk and phhusson's gsi roms. I think to uninstall magisk before installing. I flashed magisk with fastboot, because i'm on stock recovery. So i have to read howto unroot with fastboot before i update.

_lucx_ said:
Just tested it... I don't seem to be able to get it to work. :/ I don't know what the issue is either...
Click to expand...
Click to collapse
The issue is talked about on PHH threads, it's caused by Magisk.

_lucx_ said:
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Click to expand...
Click to collapse
May I ask you how battery lie is, on AOSP?

enban said:
May I ask you how battery lie is, on AOSP?
Click to expand...
Click to collapse
Battery life was pretty good during my use without Xposed. I can't give you a specific battery life time now since I've installed Xposed which obviously made it a bit worse.

_lucx_ said:
Look at the bug list of each rom. As I said, I'm not the developer of any of those roms.
But I'm using the pure AOSP rom by phhusson and it's working perfectly fine without any issues as far as I can tell.
Click to expand...
Click to collapse
Hi,
I've several question for you :
1/ I wonder about security and privacy, do you think using aosp treble is better, than stock rom for that ?
2/ i don't care about gapps (gmail...), but i need the framework and google playstore.
If i take pure aosp without gapps does it have playstore and google frameworks ?
3/ which version do you use ? can you link me the version ?
Thanks.

Aqwel said:
Hi,
I've several question for you :
1/ I wonder about security and privacy, do you think using aosp treble is better, than stock rom for that ?
2/ i don't care about gapps (gmail...), but i need the framework and google playstore.
If i take pure aosp without gapps does it have playstore and google frameworks ?
3/ which version do you use ? can you link me the version ?
Thanks.
Click to expand...
Click to collapse
1. Well you kind of get a security risk anyway by unlocking the bootloader, rooting, etc. Other than that the Roms themselves are just what Android provides in terms of security.
2. No
3. for A-Only arm64 with Gapps and SU (https://forum.xda-developers.com/pr...development/experimental-phh-treble-t3709659)

_lucx_ said:
1. Well you kind of get a security risk anyway by unlocking the bootloader, rooting, etc. Other than that the Roms themselves are just what Android provides in terms of security.
2. No
3. for A-Only arm64 with Gapps and SU (https://forum.xda-developers.com/pr...development/experimental-phh-treble-t3709659)
Click to expand...
Click to collapse
Few questions for you buddy:
Does the camera work well?
Is fingerprint working well?
Do navkeys work?
I'm talking about aosp phh Treble.
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?

Double Chin Bigot said:
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Click to expand...
Click to collapse
Yes but you may use the os you had before flashing to treble, refer to https://forum.xda-developers.com/honor-9/help/help-to-stock-treble-custom-rom-t3804064
By the way thanks @_lucx_ for you answers

Double Chin Bigot said:
Few questions for you buddy:
Does the camera work well?
Is fingerprint working well?
Do navkeys work?
I'm talking about aosp phh Treble.
And one thing, how to return to stock?
Extract system.img from stock rom with Huawei firmware extractor, flash it from fastboot like the aosp image, go to recovery and wipe cache and data, reboot and voila?
Click to expand...
Click to collapse
- Yes 4K video is working (screen recording as well)
- Fingerprint is fully working with home button gestures set to Huawei's default for one button navigation - can be tweaked by editing the fingerprint.kl tho.
- Navbar is working fine for me but might have to do with the EMUI firmware you were on previously (although there's a fix for it now but I don't know if this fix works on Android 8.1)

_lucx_ said:
- Yes 4K video is working (screen recording as well)
- Fingerprint is fully working with home button gestures set to Huawei's default for one button navigation - can be tweaked by editing the fingerprint.kl tho.
- Navbar is working fine for me but might have to do with the EMUI firmware you were on previously (although there's a fix for it now but I don't know if this fix works on Android 8.1)
Click to expand...
Click to collapse
I think there's a misunderstanding. I was talking about the physical navigation keys (the ones near the fp sensor). Do they work as intended? Is it possible to deactivate the on screen navigation keys without root(because I want only the aosp Rom without anything else added)?

Noob guide to install GSI on whyred

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

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

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

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

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

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

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

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

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

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

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

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

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

[dupe sorry]

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

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

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

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

[ROM][10-Q][OFFICIAL] LineageOS 17.1 for the LG V20 variants

Lineage dev has now opened their sources for official nightly builds of LineageOS 17.1 for the V20
@x86cpu and npjohnson are the lead maintainers for the device
You can now download the nightly build and Lineage recovery at
https://download.lineageos.org
NOTE: Tap the hamburger menu button on the left to see the device sources, scroll through LG and look for your variant
Long Live LG V20!!

please Help us for install it. and h990 users test it and report whatsapp video playing.

sajadzarepour said:
please Help us for install it. and h990 users test it and report whatsapp video playing.
Click to expand...
Click to collapse
Install it just like any other Custom ROM on TWRP

Downloading it now.. and notice there 2 files.. one is the rom and the other is the recovery... can i just install the rom using twrp or i also need to install the recovery too ? is the recovery gonna overwrite the twrp ?

dgozalie said:
Downloading it now.. and notice there 2 files.. one is the rom and the other is the recovery... can i just install the rom using twrp or i also need to install the recovery too ? is the recovery gonna overwrite the twrp ?
Click to expand...
Click to collapse
It's Lineage's own recovery, haven't tried it to be honest, and it's new, but you can use TWRP also

will this rom still have quad DAC option menu in the setting? cause i am mainly using this phone as DAP....

hello
okay i already flashing the img using twrp... reboot and the lineage logo playing... keeps going for couple minutes and then reboot again and going back to twrp menu.. restart again and lineage logo playing and in the end reboot into twrp... guess cannot using twrp flash....
the things is.. i got no idea how to use lineage recovery... i google it and still very little know guide about lineage recovery...

sajadzarepour said:
please Help us for install it. and h990 users test it and report whatsapp video playing.
Click to expand...
Click to collapse
Just because you report it on official does not mean it will be fixed any quicker. See my post in my builds for what I need for people to test if it will be fixed or not. I do not have Whatsapp so unable to test.

I install last version of this rom in h990 ds and when i left the phone in charghe phone freezing and problem is solved after reboot phone i think this is kernel problem

Easy Method to Go From Unofficial Lineage 17.1 to Official Lineage 17.1
Backup data partition using TWRP
Factory reset phone using TWRP (option is under the Wipe menu)
Install Official Lineage 17.1 rom
Install Magisk 20.4 if you wish
reboot and wait for about 10 minutes until Welcome screen shows on your phone
Power down the phone, and go back into TWRP using the manual method
Once in TWRP, restore the data partition you had just backed up
reboot and wait for another 10 minutes
That's it.

ali-nsr said:
I install last version of this rom in h990 ds and when i left the phone in charghe phone freezing and problem is solved after reboot phone i think this is kernel problem
Click to expand...
Click to collapse
Please report WhatsApp video playing and about Rom

so no need to use the lineage recovery ? just use twrp fine ? what version of twrp u using ?

scottyrick said:
Easy Method to Go From Unofficial Lineage 17.1 to Official Lineage 17.1
Backup data partition using TWRP
Factory reset phone using TWRP (option is under the Wipe menu)
Install Official Lineage 17.1 rom
Install Magisk 20.4 if you wish
reboot and wait for about 10 minutes until Welcome screen shows on your phone
Power down the phone, and go back into TWRP using the manual method
Once in TWRP, restore the data partition you had just backed up
reboot and wait for another 10 minutes
That's it.
Click to expand...
Click to collapse
I'm in Oreo stock Rom
If i want install los17.1 official version i must flash Nougat version then Rooting it and after that install 15.1 and 16 before install 17.1 Or not?

dgozalie said:
Downloading it now.. and notice there 2 files.. one is the rom and the other is the recovery... can i just install the rom using twrp or i also need to install the recovery too ? is the recovery gonna overwrite the twrp ?
Click to expand...
Click to collapse
Keep TWRP. If you try for any reason to enter lineage recovery with our button combo, it'll format your data, just letting you know.

sajadzarepour said:
I'm in Oreo stock Rom
If i want install los17.1 official version i must flash Nougat version then Rooting it and after that install 15.1 and 16 before install 17.1 Or not?
Click to expand...
Click to collapse
I agree with the process you described.. Make certain you are fully working on Unofficial 17.1 before moving to Official version.

Hello all. Brand new to XDA, created an account to join the discussion here.
Dirty flashed this over unofficial 16.0 successfully. Using Nano Gapps, no kernel or anything crazy. I'm absolutely loving it and flying along.
One issue I'm having right now is a lack of audio over bluetooth in calls, or microphone. I can't make or recieve calls over bluetooth with either my WI-1000x neckband, or my car. Calls themselves work fine (Does this have VoLTE or WiFi calling support?) but my bluetooth calling doesn't work at all.
I can listen to music fine, but when using discord or calling, no dice. I'm new, so I don't know what kind of information I need to provide to get some help - but I have tried wiping my cache/dalvik, unpairing and repairing, and turning bluetooth on and off. Nothing has worked as of yet. I can take a bug report or get a log or something if you need, don't know how.
Anyone else experiencing this issue, or are your calls over bluetooth working? What do I need to do to submit a bug report, or is it something I'm missing and an easy fix?
Thanks all!

Hello
I am successfully flash it..now how to enable the quad DAC in this rom?

Do I need to swap recoveries from twrp to lineage one to try this Lineage OS version? Do I need to use the to-x86 zip like the others require?
One last question, can I easily swap between this and Stock 7.0 if I want for ls997? No ARB issues I hope
---------- Post added at 11:25 PM ---------- Previous post was at 11:22 PM ----------
dgozalie said:
Hello
I am successfully flash it..now how to enable the quad DAC in this rom?
Click to expand...
Click to collapse
U could possibly try to add dac with an app called Lg V10 DAC FIX from playstore. I haven't tried yet myself tho, I just read something before about it.

vectorvitale said:
Hello all. Brand new to XDA, created an account to join the discussion here.
Dirty flashed this over unofficial 16.0 successfully. Using Nano Gapps, no kernel or anything crazy. I'm absolutely loving it and flying along.
One issue I'm having right now is a lack of audio over bluetooth in calls, or microphone. I can't make or recieve calls over bluetooth with either my WI-1000x neckband, or my car. Calls themselves work fine (Does this have VoLTE or WiFi calling support?) but my bluetooth calling doesn't work at all.
I can listen to music fine, but when using discord or calling, no dice. I'm new, so I don't know what kind of information I need to provide to get some help - but I have tried wiping my cache/dalvik, unpairing and repairing, and turning bluetooth on and off. Nothing has worked as of yet. I can take a bug report or get a log or something if you need, don't know how.
Anyone else experiencing this issue, or are your calls over bluetooth working? What do I need to do to submit a bug report, or is it something I'm missing and an easy fix?
Thanks all!
Click to expand...
Click to collapse
First of all. It's an official build and therefore you shouldn't dirty flash. U need to factory reset and clear cache and dalvik. Do not format your internal storage. It isn't necessary

Hello...
awesome rom.. like it so much... so here is thing that doesn't work in here
1. fingerprint sensor
2. QUAD DAC
hope the fix will be out soon..

Project Treble for Xperia X compact

Project Treble For Xperia X Compact
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards,.
Big thanks to Sjll member and his tuto to go treble
Suitable for F5321, A-ONLY GSI ROM​
Required files:
[SODP Kernel version]
All necessary files
[OEM-File]
Download Link
[SYSTEM-File]
Tested with some system gsi files, these work properly :
Pixel experience
/e/
POSP
ArrowOS
[SYSTEM-File WITH FixZygote installed via twrp]
Android Q developer preview
Find all GSI system image here and here
How to go Treble ?
First: Flash recovery
Code:
fastboot flash recovery < Path of recovery.img >
Second: Flash boot image
Code:
fastboot flash boot < Path of boot.img >
Third: Flash vendor file
Code:
fastboot flash cache < Path of vendor.img >
Fourth: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fifth: Flash a GSI compatible System image (arm64 A-ONLY) and boot !
Code:
fastboot flash system < Path of GSI-System.img >
Look here first for questions resolving Xperia X thread
Source Codes
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-05-09
Last Updated 2020-05-23

Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.

maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced

maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
Normally I set the selinux to permissive so no need to apply the permissiver patch
PS : sometimes it goes into bootloop but if you reboot it starts like a charm (test that with POSP 10)
PS2 : Mobile network does not work with Q roms, if you success to make it work please share
PS3 : POSP Pie works fine

Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.

bioshp said:
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
Click to expand...
Click to collapse
You can get twrp as recovery but do not wipe cache, as vendor img is flashed in it

Good news that /e/ is working correctly, I was about to try to build a e variant on Chippa's build.
I do have one question. Really new to trebble.
If we wanna root it, we apply usual procedure*? flash the root zip(magisk) in recovery

This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?

can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Xperia UI GSI also does not start for me. What could be?

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Try to flash userdata also

bioshp said:
Xperia UI GSI also does not start for me. What could be?
Click to expand...
Click to collapse
Q or Pie ROM ?

maluus said:
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
Click to expand...
Click to collapse
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)

betacrypt said:
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
Click to expand...
Click to collapse
To avoid SELinux policy errors and fail to boot

nervousapp said:
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
Click to expand...
Click to collapse
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.

I flashed /e/ and it's pretty stable and smooth but my device is overheating when charging and even when it's idle and the display is off. I'm getting severe battery drain from it.
EDIT: Wiping all the partitions and flashing from scratch seems to have done the trick.

I've been using Arrow OS and it's pretty stable and smooth so far. Comes with GApps built-in and Jan 2020 security patch:
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/

maluus said:
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
Click to expand...
Click to collapse
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.

mister-13x said:
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
Click to expand...
Click to collapse
I didn't anything extraordinary follow the steps in the first post. (Since android version would change I formatted data) use erfanoabdis' unofficial Q gsi which you can find a link at phhusson' gsi images link list. (You can also find the link to phussons list in the first post)

[ROM] crDroid-v8.4 Pixel 4 XL

crDroid-v8.4 android 12.1
INSTALLATION.
1. download boot image and crDroid-v8.4 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
UPDATES
unsupported device
DOWNLOADS
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=334067
GAPPS
12.1 = https://androidfilehost.com/?fid=14655340768118455581
CREDITS
crDroid devs
LineageOS Team
mroles29
Alessandro Astone
Bliss-Rom devs
SOURCE
device=https://github.com/LineageOS/android_device_google_coral
kernel=https://github.com/LineageOS/android_kernel_google_msm-4.14
vendor=https://github.com/mroles29/vendor_google_coral
BUGS
com.android.hbmsvmanager eating away at the battery

which gapps best for this ROM

debiansid10 said:
which gapps best for this ROM
Click to expand...
Click to collapse
MindTheGapps-12.1.0-arm64-20220313_181440.zip | by Alessandro Astone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

bump

setup did not complete
no bypass at face lock it is not working

wmhaganjr1013 said:
setup did not complete
no bypass at face lock it is not working
Click to expand...
Click to collapse
Any update to this question? I've tried it before it was relelased on XDA, but couldn't seem to get it working. I've noticed that the camera now works with this build.

5acrosstheeye said:
Any update to this question? I've tried it before it was relelased on XDA, but couldn't seem to get it working. I've noticed that the camera now works with this build.
Click to expand...
Click to collapse
I've managed to get it working bypassing the face lock & security at setup, and later setting up the pin. So far, so good w/ out the face lock. Thank you @putzwon for putting this together. If you need a tester please feel free to hit me up.

do i need to be on latest a12?

krabban said:
do i need to be on latest a12?
Click to expand...
Click to collapse
I would recomened it since it's a April update for 12.1

this rom seems nice, but it doesnt recognize my esim
stock android 12 recognizes it just fine, no problems with descendant either
any help?
edit:flashing gapps before booting to rom for the first time fixed it

nihilus6 said:
this rom seems nice, but it doesnt recognize my esim
stock android 12 recognizes it just fine, no problems with descendant either
any help?
edit:flashing gapps before booting to rom for the first time fixed it
Click to expand...
Click to collapse
How do you like crDroid in comparison with Descendant?

mingaldrichgan said:
How do you like crDroid in comparison with Descendant?
Click to expand...
Click to collapse
I really liked crdroid, it's a stable Rom with more customization than descendant.
I did go back to descendant because of face unlock though.

nihilus6 said:
I really liked crdroid, it's a stable Rom with more customization than descendant.
I did go back to descendant because of face unlock though.
Click to expand...
Click to collapse
Oh crDroid has no face unlock? That's a deal breaker for me.

mingaldrichgan said:
Oh crDroid has no face unlock? That's a deal breaker for me.
Click to expand...
Click to collapse
Yup same here, face unlock is too convenient to not have. It's a shame because the customization of this Rom is really good compared to other a12 roms

I'm really enjoying this rom as it has the most customization than any other current roms for the pixel. Thanks @putzwon for bringing this rom for the pixel 4 xl, I can make due with facelock as you bring this up to speed. Might want to check out what @bigmarv31 did with Bliss 11 for the pixel face unlock. Also to mention com.android.hbmsvmanager is eating away at the battery, might want to check with @albinoman887 as he fixed the issue for the pixel 6 pro.

nihilus6 said:
Yup same here, face unlock is too convenient to not have. It's a shame because the customization of this Rom is really good compared to other a12 roms
Click to expand...
Click to collapse
If your willing to downgrade to 11
face unlock works I'll start another thread
crDroid-v7.16
crDroid-v7.16 INSTALLATION. 1. download boot image and crDroid-v7.16 zip file 2. reboot bootloader 3. fastboot -w 4. fastboot flash boot boot.img --slot all 5. reboot into recovery 6. sideload zip file (adb sieload zip file) 7. reboot to...
forum.xda-developers.com

wmhaganjr1013 said:
setup did not complete
no bypass at face lock it is not working
Click to expand...
Click to collapse
face unlock works now

5acrosstheeye said:
I'm really enjoying this rom as it has the most customization than any other current roms for the pixel. Thanks @putzwon for bringing this rom for the pixel 4 xl, I can make due with facelock as you bring this up to speed. Might want to check out what @bigmarv31 did with Bliss 11 for the pixel face unlock. Also to mention com.android.hbmsvmanager is eating away at the battery, might want to check with @albinoman887 as he fixed the issue for the pixel 6 pro.
Click to expand...
Click to collapse
face unlock works now still need to fix this com.android.hbmsvmanager and thanks for pointing me in the right direction

nihilus6 said:
Yup same here, face unlock is too convenient to not have. It's a shame because the customization of this Rom is really good compared to other a12 roms
Click to expand...
Click to collapse
face unlock works now

putzwon said:
face unlock works now
Click to expand...
Click to collapse
Many thanks @putzwon, just an fyi the link on Android file host has the lastest zip at 66mb when downloaded. But the discription shows 1.1gb.