This thread described the main steps to port a P Preview image into semi-GSI .This is only a reference that points out the key files you may need to deal with, but not a step to step guide.Also I can only lead you to make it boot,and I'm not promising anything.
Things you need to prepare:
1.An Android device with official / unofficial 8.1 Treble support and a PC.
2.P DP3 semi-GSI image(most OEM P are working with DP3)
3.A *Qualcomm OEM P Preview image you want to port.
4.Better have a recent Android kitchen.
*Seems that there's only Qualcomm based devices received official P Preview builds. I'm not sure if someone has early access to P images for Kirin processors (e.g. for Huawei Mate 10) or Exynos.
In theory ,P images can be ported between chipsets from the same vendor.(If anyone have these images feel free to share it)
Also you need to prepare for (in case)bricks,if something goes wrong.
So let's start.
Unpack P semiGSI and the ROM you want to port.
*the lib&lib64 below means there are to files you need to replace,one in lib and one in lib64 folder.
Replace /system/lib&lib64/libselinux.so from semiGSI to your port.
Look for a txt file start with ld.config in your /system/etc of port image, then replace it with /system/etc/ld.configs.txt from semiGSI.
Remove /system/etc/permissions/qti-permissions.jar
Modify /system/etc/prop.default to disable adb secure and enable all debug props for debugging.
Unpack /vendor from port, try to find out services added by OEM in manifest.xml.
The manifest can be in /vendor or /vendor/etc/vintf
Pick out all /vendor HALs related to services you found in manifest.
Basically they are located in:
/vendor/bin/hw
/vendor/etc/init
/vendor/lib&lib64/
/vendor/lib&lib64/hw
Also look for some additional files related to OEM rom.(framework, overlays etc.)
Then pack your /system into img.
Flash 8.1 vendor & P semi-GSI boot & vendor patches.
Flash your port.
Add all additional thing you found in vendor.
You need to modify your device's manifest.xml and add OEM related.
Flash FBE Disabler and permissiver to disable FBE and SELinux.
Format /data ,push adb keys into system for debug
& reboot.
If you're lucky then you can get into bootanimation.If not, try to check everything.
Use adb logcat >logcat.txt and get logs.
Open the log, search 'died' and you will get to lines near system crash. Here you need some ROM porting skills,try to find out what's going wrong.
Reserved
Some frequently bug's solutions:
'dumplicate permission : XXX'
Find the XXX permission in files in /system/etc/permissions . Delete lines for that permission.
'fail to make lockscreen ready'
Add libpuresoftkeymasterdevice.so from P semi GSI to your /system.
Reboot or black screen after enter system
(Most SDM845 ports)
Replace
/system/bin/surfaceflinger
/system/lib&lib64/libsurfaceflinger.so and libtimestats_pronto.so
Great job, OP. My question is, does this mean that in the future we may be able to trebelize most, if not all, OEM roms?
dustmalik said:
Great job, OP. My question is, does this mean that in the future we may be able to trebelize most, if not all, OEM roms?
Click to expand...
Click to collapse
The answer is ,'yes it should be'.In theory ,ported sGSI should work on the same platform ,e.g. Qcom sGSI,Exynos sGSI.But these OEM roms usually intend to specific hardware, so there may always bugs exist.As we know developers of O GSIs did a lot of hacks ,try to enable the maximum compatibility.But porting makes this not possible cuz no source code.
Also, the port I do is only on OEM without too much modification to original P, what about Samsung with their own hals and Huawei EMUI with the *** OEMINFO partition ? These roms are not possible to port in the near past,I think nor in the near future.
The problem with exynos device that is with s9+ we dont have android 8.1 vendor image.
Note: Tested not working on latest P miui of MI MIX 2S .
EDIT: Because of SELinux
fxsheep said:
Note: Tested not working on latest P miui of MI MIX 2S .
EDIT: Because of SELinux
Click to expand...
Click to collapse
did you manage to boot a miui10 GSI?
meltbanana said:
did you manage to boot a miui10 GSI?
Click to expand...
Click to collapse
No
fxsheep said:
Note: Tested not working on latest P miui of MI MIX 2S .
EDIT: Because of SELinux
Click to expand...
Click to collapse
Do you plan on porting the new HydrogenOS Beta 1 android pie for OnePlus 6?
https://forum.xda-developers.com/oneplus-6/how-to/android-pie-9-0-public-beta-version-t3829394
Surprising Update : I got leaked EMUI 9 rom of Huawei Mate 20 (powered by Kirin 980) and followed this method on a Qualcomm Trebled device. What surprised me is that I already got bootanimation ,end up with the same SELinux error when I port MIX2S MIUI P.
This may means that in the future we can even port roms between platforms ,and make real GSI.
fxsheep said:
Surprising Update : I got leaked EMUI 9 rom of Huawei Mate 20 (powered by Kirin 980) and followed this method on a Qualcomm Trebled device. What surprised me is that I already got bootanimation ,end up with the same SELinux error when I port MIX2S MIUI P.
This may means that in the future we can even port roms between platforms ,and make real GSI.
Click to expand...
Click to collapse
If anyone can give me the way to get this firmware https://www.xda-developers.com/huawei-mate-10-pro-android-p/amp/
Then I can prove it
fxsheep said:
If anyone can give me the way to get this firmware https://www.xda-developers.com/huawei-mate-10-pro-android-p/amp/
Then I can prove it
Click to expand...
Click to collapse
I think this isn't the one you want. But I hope it will help you. BTW, can you boot it on HUAWEI vndk26 devices?
http://update.hicloud.com:8180/TDS/...50/g1750/v152588/f1/full/update_full_base.zip
麦麦观 said:
I think this isn't the one you want. But I hope it will help you. BTW, can you boot it on HUAWEI vndk26 devices?
http://update.hicloud.com:8180/TDS/...50/g1750/v152588/f1/full/update_full_base.zip
Click to expand...
Click to collapse
This one isn't.In theory it can boot on vndk26 but lack selinux fixes.I don't have treble vndk26 device though.
fxsheep said:
Surprising Update : I got leaked EMUI 9 rom of Huawei Mate 20 (powered by Kirin 980) and followed this method on a Qualcomm Trebled device. What surprised me is that I already got bootanimation ,end up with the same SELinux error when I port MIX2S MIUI P.
This may means that in the future we can even port roms between platforms ,and make real GSI.
Click to expand...
Click to collapse
Do you think is it possible to port oppo color os into gsi ?
Update:This guide does not support P Release versions.i.e.If you port any P roms which is marked as "release" not "beta" by OEM then probably this won't work.It can only boot on 9.0 vendor.
Better is make script same as my cd C:\Users\MAREK\Desktop\BASE\system
echo FAZA 1 ld.config.txt
pause
COPY C:\Users\MAREK\Desktop\BASE\system\etc\ld.config.txt C:\Users\MAREK\Desktop\skrypt\BASE\system\etc\
pause
echo FAZA 2 libselinux.so
pause
COPY C:\Users\MAREK\Desktop\BASE\system\lib\libselinux.so C:\Users\MAREK\Desktop\skrypt\BASE\system\lib\
pause
COPY C:\Users\MAREK\Desktop\BASE\system\lib64\libselinux.so C:\Users\MAREK\Desktop\skrypt\BASE\system\lib64\
pause
Related
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 it
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
What is Project Treble
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition.
About
Weijianism did not build any verdor image of new version because he does not own this device. Although I am not familiar with android source and android build, I am very happy to learn it so that we natrium owners can use project treble.
So I message to Weijianism to know how to do it and have learnt it for a few weeks. Now I am trying to build vendors. Cause I still know a few about it, It is really very hard for me to solve problems in myself. So if you have any advice, please tell me or push you code in github. THANK YOU!
What is NOT WORKING
Camera
Let's test it together.
Download
ALPHA 0815 (boot.img + vendor.img)
How to
1. wipe everything using TWRP
2. flash boot.img + vendor.img
3. flash system.img
4. reboot to system
Sources
Kernel for msm8996 (lineage-15.1)
Configuration for natrium (lineage-15.1)
Configuration for msm8996 (lineage-15.1) (Minor patches)
Proprietary vendor (lineage-15.1) (Minor patches, forked from Weijianism , credits MZO)
XDA: DevDB Information
Project Treble for Mi 5s Plus
Contributors
Justin_hill
Weijianism
Thanks to
LineageOS
Mi 5s Plus devs
@Weijianism
ROM OS Version: 8.x Oreo
Rom Kernel: Linux 3.x
Version Information
Status: Testing
Created: 2018-08-13
Last Updated: 2018-08-16
Anyone try ?
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
1. bootloop problem solved when using rr gsi. (code from hacker1024)
2. bluetooth service stoped problem solved.
QuiseShampe said:
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Click to expand...
Click to collapse
The camera's problem seems very hard, I will try to use GCam later. Now I do have no idea about how to solve it.
You may help me solve it if you like!
pote2639 said:
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
Click to expand...
Click to collapse
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
justin_hill said:
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
Click to expand...
Click to collapse
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
pote2639 said:
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Click to expand...
Click to collapse
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
justin_hill said:
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
Click to expand...
Click to collapse
I guess I'll wait for android p stable sgsi build then.
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
rhp_engcoy said:
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
Click to expand...
Click to collapse
Hope for me get a new natrium and I'll do for capricorn and natrium too.
Ofc, as justin did for natrium already, I'm gonna just ship it on my custom ROMs projects, not separated things like capricorn should get it too.
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
theOriginalSuperl2 said:
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
Click to expand...
Click to collapse
Yeah, your code have inspired me a lot when I saw your repositories.
Maybe I fixed the bluetooth problem when I add back the libbtnv.so to /vendor/lib/ since it was deleted in this commit.
For the camera problem, I don't know how vendor module relates to kernel. But I will try it afterwards.
Actually I almost know nothing about lineage source code, system build skills and things like this. If you can help, it will be grateful!
any news on the development?
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
About treble support I can tell that I'm gonna include in my ROMs, and maybe I'll give some vendor zips too, if @justin_hill doesn't care about that.
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
Sorry, I am trying to do something about Treble for Android Pie, But there are still several problems unsolved. Cause I'm not familiar with those code, so maybe I can't solve it by myself. It will be so grateful if anyone can contribute to it.
So we will expect @Hlcpereira WORK, Thank you so much!
Hey, is the camera problem solved?
It can't be booting on any sgsi so what should i
do
Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.
I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^
Awesome!
I'm eager to hear about your endeavors in this!
L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant
L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.
@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule
Here is the screenshot I mentioned in my previous post.
I forgot to include it ...
Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?
I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first
31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Xperia z1 has carbon Android pie and gapps link
This may help you.
Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.
No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning
Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.
Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?
I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.
Guys why there is no developer here working on a treble project enable tool to our phone
Since we have a stable oreo rom and have all the libs and files in vendor to make oreo boot successfully without bugs there is a possible way to make our klte project treble i'm sure >
but i can't lonely make this project alive we need to work with our devs to make this happens
since the creation of vendor partition is not that hard thing but i'm didn't know anything about editing the kernel and the device tree to boot from new vendor partition.
Thank you if you reach that point of the thread
@phhusson i really appreciate your work for the project treble forum
Can you help me with making this thing happens ?
mhmdalsfaf said:
Guys why there is no developer here working on a treble project enable tool to our phone
Since we have a stable oreo rom and have all the libs and files in vendor to make oreo boot successfully without bugs there is a possible way to make our klte project treble i'm sure >
but i can't lonely make this project alive we need to work with our devs to make this happens
since the creation of vendor partition is not that hard thing but i'm didn't know anything about editing the kernel and the device tree to boot from new vendor partition.
Thank you if you reach that point of the thread
Click to expand...
Click to collapse
treble is not only bound to partitioning , its also a kernel version as well which we not even near it , the required kernel version is 3.18 (as the bare-minimum ) and up , the S5 is stuck at 3.4.113 so no treble for the S5.
Hi guys! This is a compilation of working and non-booting Treble Oreo ROMs for Huawei Y6 (2018). Full list of Treble Project ROMs is here. This list is still incomplete as I have not tested all ROMs listed in the link above. Therefore, if anyone tried a custom ROM not listed on this thread, please post it here so I can update this thread.
Please do note that I am not a ROM developer, you can still post bugs here so others will know and also on the ROM thread so we can hope for fixes.
We should thank @phhusson for all the works he's done to Project Treble
Project Treble ROMs are ROMs that are built to support as many devices as possible that support Treble. Treble devices, usually ship with Android Oreo pre-installed, therefore, our Huawei Y6 (2018) should technically boot any GSI/Treble ROM. But still, custom GSI ROMs are still not perfect and some devices may have bugs and some devices may not be unable to boot a particular ROM at all
Please read the wiki here about Y6 first
Prerequisites:
unlocked bootloader
adb and fastboot installed on your computer
How to flash ROMs for our device?
Before flashing, follow my guide HERE so you can always go back to stock ROM just in case. Also, make sure you downloaded an ARM64 A only image. This procedure erases your files so have a backup of your important files
Some ROM threads provide downloads in .zip file or in tar.xz file instead of .img files to save internet usage. Install 7-zip on Windows, open the file and extract the flashable .img file
1. Plug your device to the computer and reboot to download mode using this command:
Code:
adb reboot bootloader
2. Flash your desired ROM using this command:
Code:
fastboot flash system <ROM file here, should be a .img file>
3. Reboot!
Code:
fastboot reboot
4. When you see the warning "Your device has been unlocked and can't be trusted", press the Volume up button and your device will go to erecovery. There, you can select Factory Reset
Usually, custom ROMs come with 2 variants:
Vanilla - this is a plain ROM with no GApps and su (root access)
GApps - a ROM with Google Apps (Play Store, etc.). Usually comes with root access too!
Here is the list of ROMs that are tested. Feel free to post ROMs that are working for our device
1. CrDroid by @Dil3mm4
2. LineageOS by @phhusson
3. OmniROM Treskmod by @Letzen
4. Resurrection Remix by @mracar
5. Pixel Experience by @jhenrique09
6.AOSP 8.1 - older than v25 ONLY!! by @phhusson Download the old version here
7.Bootleggers ROM by @Dil3mm4
8. Havoc OS 08/19 build by @
EnesSastim
9.Descendants threedotzero by @Dil3mm4
Tested not working:
1. AOSP Extended by @AryanPatidar - I only tried the latest version v5. 8, older versions may/may not work
2. AOKP by @sixohtew - I only tried the latest version, older versions may/may not work
3.AOSP v25 and later(?) by @phhusson
Ai ai ai, mine (OmniROM Treskmod) was meant to be work on Huawei anyway so it should work fine. Good luck, everyone.
pascua28 said:
Hi guys! This is a compilation of working and non-booting Treble Oreo ROMs for Huawei Y6 (2018). Full list of Treble Project ROMs is here. Feel free to test so that this list may be updated
We should thank @phhusson for all the works he's done to Project Treble
Project Treble ROMs are ROMs that are built to support as many devices as possible that support Treble. Treble devices, usually ship with Android Oreo pre-installed, therefore, our Huawei Y6 (2018) should technically boot any GSI/Treble ROM. But still, custom GSI ROMs are still not perfect and some devices may have bugs and some devices may not be unable to boot a particular ROM at all
The bugs for Y6 (2018) is found here :
Bootloop for all Android 9.0 ROM's
Bootloop for the latest AOSP 8.1 v25
Signal bar stays empty on h/h+ but works on e
GPS isn't working.
Prerequisites:
unlocked bootloader
adb and fastboot installed on your computer
How to flash ROMs for our device?
Before flashing, follow my guide HERE so you can always go back to stock ROM just in case. Also, make sure you downloaded an ARM64 A only image. This procedure erases your files so have a backup of your important files
1. Plug your device to the computer and reboot to download mode using this command:
Code:
adb reboot bootloader
2. Flash your desired ROM using this command:
Code:
fastboot flash system <ROM file here>
3. Reboot!
Code:
fastboot reboot
4. When you see the warning "Your device has been unlocked and can't be trusted", press the Volume up button and your device will go to recovery mode. There, you can select Factory Reset
Usually, custom ROMs come with 2 variants:
Vanilla - this is a plain ROM with no GApps and su (root access)
GApps - a ROM with Google Apps (Play Store, etc.). Usually comes with root access too!
Here is the list of ROMs that are tested. Feel free to post ROMs that are working for our device
1. CrDroid by @Dil3mm4
2. LineageOS by @phhusson
3. OmniROM Treskmod by @Letzen
4. Resurrection Remix by @mracar
5. Pixel Experience by @jhenrique09
Tested not working:
1. AOSP Extended by @AryanPatidar - I only tried the latest version v5. 8, older versions may/may not work
2. AOKP by @sixohtew - I only tried the latest version, older versions may/may not work
Click to expand...
Click to collapse
Try Aosp extended v5.4 and see if it boots up
AryanPatidar said:
Hi guys! This is a compilation of working and non-booting Treble Oreo ROMs for Huawei Y6 (2018). Full list of Treble Project ROMs is here. Feel free to test so that this list may be updated
We should thank @phhusson for all the works he's done to Project Treble
Project Treble ROMs are ROMs that are built to support as many devices as possible that support Treble. Treble devices, usually ship with Android Oreo pre-installed, therefore, our Huawei Y6 (2018) should technically boot any GSI/Treble ROM. But still, custom GSI ROMs are still not perfect and some devices may have bugs and some devices may not be unable to boot a particular ROM at all
The bugs for Y6 (2018) is found here :
Bootloop for all Android 9.0 ROM's
Bootloop for the latest AOSP 8.1 v25
Signal bar stays empty on h/h+ but works on e
GPS isn't working.
Prerequisites:
unlocked bootloader
adb and fastboot installed on your computer
How to flash ROMs for our device?
Before flashing, follow my guide HERE so you can always go back to stock ROM just in case. Also, make sure you downloaded an ARM64 A only image. This procedure erases your files so have a backup of your important files
1. Plug your device to the computer and reboot to download mode using this command:
2. Flash your desired ROM using this command:
3. Reboot!
Try Aosp extended v5.4 and see if it boots up
Click to expand...
Click to collapse
Have you tried? If so, I will add it to the list
pascua28 said:
Hi guys! This is a compilation of working and non-booting Treble Oreo ROMs for Huawei Y6 (2018). Full list of Treble Project ROMs is here. Feel free to test so that this list may be updated
We should thank @phhusson for all the works he's done to Project Treble
Project Treble ROMs are ROMs that are built to support as many devices as possible that support Treble. Treble devices, usually ship with Android Oreo pre-installed, therefore, our Huawei Y6 (2018) should technically boot any GSI/Treble ROM. But still, custom GSI ROMs are still not perfect and some devices may have bugs and some devices may not be unable to boot a particular ROM at all
The bugs for Y6 (2018) is found here :
Bootloop for all Android 9.0 ROM's
Bootloop for the latest AOSP 8.1 v25
Signal bar stays empty on h/h+ but works on e
GPS isn't working.
Prerequisites:
unlocked bootloader
adb and fastboot installed on your computer
How to flash ROMs for our device?
Before flashing, follow my guide HERE so you can always go back to stock ROM just in case. Also, make sure you downloaded an ARM64 A only image. This procedure erases your files so have a backup of your important files
1. Plug your device to the computer and reboot to download mode using this command:
Code:
adb reboot bootloader
2. Flash your desired ROM using this command:
Code:
fastboot flash system <ROM file here>
3. Reboot!
Code:
fastboot reboot
4. When you see the warning "Your device has been unlocked and can't be trusted", press the Volume up button and your device will go to recovery mode. There, you can select Factory Reset
Usually, custom ROMs come with 2 variants:
Vanilla - this is a plain ROM with no GApps and su (root access)
GApps - a ROM with Google Apps (Play Store, etc.). Usually comes with root access too!
Here is the list of ROMs that are tested. Feel free to post ROMs that are working for our device
1. CrDroid by @Dil3mm4
2. LineageOS by @phhusson
3. OmniROM Treskmod by @Letzen
4. Resurrection Remix by @mracar
5. Pixel Experience by @jhenrique09
Tested not working:
1. AOSP Extended by @AryanPatidar - I only tried the latest version v5. 8, older versions may/may not work
2. AOKP by @sixohtew - I only tried the latest version, older versions may/may not work
Click to expand...
Click to collapse
can u give me a list that in which devices u tested those roms? like atu-lxx?
nafis5566 said:
can u give me a list that in which devices u tested those roms? like atu-lxx?
Click to expand...
Click to collapse
I tested this on my ATU-L22 but the ROMs should work with any Y6 (2018) ATU-Lxx
pascua28 said:
I tested this on my ATU-L22 but the ROMs should work with any Y6 (2018) ATU-Lxx
Click to expand...
Click to collapse
was thinking about to go for the pixel experience but gps is really important thing. any suggestion? and what about the battery life?
nafis5566 said:
was thinking about to go for the pixel experience but gps is really important thing. any suggestion? and what about the battery life?
Click to expand...
Click to collapse
Nothing I can do about GPS as I'm not a ROM developer. Battery life is a bit less compared to stock
Thread updated!
Added Bootleggers and AOSP 8.1 to the list
Updated instruction for non img downloads
pascua28 said:
Nothing I can do about GPS as I'm not a ROM developer. Battery life is a bit less compared to stock
Click to expand...
Click to collapse
ok and should i download the generic version of pixel experience? ( https://download.pixelexperience.org/treble_gsi/ ) from here? and do u think those issues can be fixed in next updates?
nafis5566 said:
ok and should i download the generic version of pixel experience? ( https://download.pixelexperience.org/treble_gsi/ ) from here? and do u think those issues can be fixed in next updates?
Click to expand...
Click to collapse
Yes arm64 a. Maybe
pascua28 said:
Yes arm64 a. Maybe
Click to expand...
Click to collapse
ok thanx. will let you know if i face any issues.
GPS works perfectly in my device (ATU-L42)
I've tried pixel experience and lineage 15.1
In pixel experience signal bar works on all connection types but not in lineage 15.1
Only bug I found in pixel experience is auto brightness isn't working
vihanga123 said:
GPS works perfectly in my device (ATU-L42)
I've tried pixel experience and lineage 15.1
In pixel experience signal bar works on all connection types but not in lineage 15.1
Only bug I found in pixel experience is auto brightness isn't working
Click to expand...
Click to collapse
does the pixel experience has gcam build in?
pascua28 said:
Hi guys! This is a compilation of working and non-booting Treble Oreo ROMs for Huawei Y6 (2018). Full list of Treble Project ROMs is here. This list is still incomplete as I have not tested all ROMs listed in the link above. Therefore, if anyone tried a custom ROM not listed on this thread, please post it here so I can update this thread.
Please do note that I am not a ROM developer, you can still post bugs here so others will know and also on the ROM thread so we can hope for fixes.
We should thank @phhusson for all the works he's done to Project Treble
Project Treble ROMs are ROMs that are built to support as many devices as possible that support Treble. Treble devices, usually ship with Android Oreo pre-installed, therefore, our Huawei Y6 (2018) should technically boot any GSI/Treble ROM. But still, custom GSI ROMs are still not perfect and some devices may have bugs and some devices may not be unable to boot a particular ROM at all
The bugs for Y6 (2018) is found here :
Bootloop for all Android 9.0 ROM's
Bootloop for the latest AOSP 8.1 v25
Signal bar stays empty on h/h+ but works on e
GPS isn't working.
Prerequisites:
unlocked bootloader
adb and fastboot installed on your computer
How to flash ROMs for our device?
Before flashing, follow my guide HERE so you can always go back to stock ROM just in case. Also, make sure you downloaded an ARM64 A only image. This procedure erases your files so have a backup of your important files
Some ROM threads provide downloads in .zip file or in tar.xz file instead of .img files to save internet usage. Install 7-zip on Windows, open the file and extract the flashable .img file
1. Plug your device to the computer and reboot to download mode using this command:
Code:
adb reboot bootloader
2. Flash your desired ROM using this command:
Code:
fastboot flash system <ROM file here, should be a .img file>
3. Reboot!
Code:
fastboot reboot
4. When you see the warning "Your device has been unlocked and can't be trusted", press the Volume up button and your device will go to erecovery. There, you can select Factory Reset
Usually, custom ROMs come with 2 variants:
Vanilla - this is a plain ROM with no GApps and su (root access)
GApps - a ROM with Google Apps (Play Store, etc.). Usually comes with root access too!
Here is the list of ROMs that are tested. Feel free to post ROMs that are working for our device
1. CrDroid by @Dil3mm4
2. LineageOS by @phhusson
3. OmniROM Treskmod by @Letzen
4. Resurrection Remix by @mracar
5. Pixel Experience by @jhenrique09
6.AOSP 8.1 - older than v25 ONLY!! by @phhusson Download the old version here
7.Bootleggers ROM by @Dil3mm4
Tested not working:
1. AOSP Extended by @AryanPatidar - I only tried the latest version v5. 8, older versions may/may not work
2. AOKP by @sixohtew - I only tried the latest version, older versions may/may not work
3.AOSP v25 and later(?) by @phhusson
Click to expand...
Click to collapse
Getting this wired error both in pixel experience and crdroid. device-atu-l42
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nafis5566 said:
Getting this wired error both in pixel experience and crdroid. device-atu-l42
Click to expand...
Click to collapse
You have to certify your device
Use the last link and follow this guide https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
For the navigation bar issue you just have to go settings>systrm>buttons>Manage navigation bar and choose a layout
nafis5566 said:
does the pixel experience has gcam build in?
Click to expand...
Click to collapse
Nope. The same cam in lineage os
vihanga123 said:
You have to certify your device
Use the last link and follow this guide https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
For the navigation bar issue you just have to go settings>systrm>buttons>Manage navigation bar and choose a layout
Nope. The same cam in lineage os
Click to expand...
Click to collapse
i certified following that threat. registration was successful. but still getting that error. then rolled back to rros.
and wasnt asking about the navigation bar.
nafis5566 said:
i certified following that threat. registration was successful. but still getting that error. then rolled back to rros.
and wasnt asking about the navigation bar.
Click to expand...
Click to collapse
For me it took like 10 mins to certify.. it doesn't work instantly
vihanga123 said:
For me it took like 10 mins to certify.. it doesn't work instantly
Click to expand...
Click to collapse
actually i waited more than 10 min.
vihanga123 said:
For me it took like 10 mins to certify.. it doesn't work instantly
Click to expand...
Click to collapse
actually i tried it again and now its working. thanx mate.