Related
It seems google released the device tree for the Nexus 5X!
Code:
git clone https://android.googlesource.com/device/lge/bullhead
Let the development begin!
Started porting the device tree to work with Cyanogenmod
THIS DOESNT WORK AT ALL YET, PLS DON'T TRY!
https://github.com/drsn0w/android_device_lge_bullhead
It was about time! May the developers be with us!
Now if only the proprietary binaries were posted...
is correct !
yes
Started porting the device tree to work with Cyanogenmod
you very geek forum but is good .
I was thinking of contributing to our community for long time..
Thanks to @erfanoabdi for his helps and encouraging me to build this rom.
here is my first TWRP flashable rom for Moto Z based on Android Nougat on Moto Z (All Unlocked Versions) cooked with SuperR's Kitchen
Its a work in progress so dont expect too much ...
Download Link : Google Drive
After flashing it with TWRP you need to use adb sideload (TWRP -> Advanced -> ADB Sideload) and flash UPDATE-AnyKernel2.zip (will remove this step in next build)
ROOT : (OPTIONAL)
Use adb sideload (TWRP -> Advanced -> ADB Sideload) and flash superuser-r259.zip to get systemless Root access.
Reboot
Install phh's SuperUser From PlayStore if you rooted with superuser-r259
I tested it on my Moto Z XT1650-03 GRIFFIN RETMX 7.0 NPL25.86-15 and upgraded it to XT1650-03 GRIFFIN TELUS 7.0 NPL25.86-30
Moto Display and Moto Actions may not work, will look into it soon.
XDA:DevDB Information
Android Nougat on Moto Z, ROM for the Moto Z
Contributors
papampi, erfanoabdi, SoulDJ673
ROM OS Version: 7.x Nougat
Based On: Stock
Version Information
Status: Stable
Stable Release Date: 2017-02-07
Created 2017-02-07
Last Updated 2017-02-07
Reserved
Reserved ...2
Thanks for your great work, best wishes, hope to make your rom more wonderful than stock
:good:
Thanks a lot. Im not sure what is wrong, but now doesnt work moto actions (gesture and display)
Seems like I have the same problem
Hopefully @erfanoabdi can help
papampi said:
Seems like I have the same problem
Hopefully @erfanoabdi can help
Click to expand...
Click to collapse
I'm not in this ROM right now.
Could you please give me some logs (logcat and dmesg)
And more details, is it force stops? Or just not working?
Thanks
erfanoabdi said:
I'm not in this ROM right now.
Could you please give me some logs (logcat and dmesg)
And more details, is it force stops? Or just not working?
No error msgs..everything looks OK, I can switch it on/off but but nothing happens..
Click to expand...
Click to collapse
I just tried adb method to see if all ok or not ...
all ok with adb method
Will flash it again tomorrow to check logs.
As mentioned by Dusha40, all seems ok and no fc,
But Moto display and Moto Actions not working
papampi said:
I just tried adb method to see if all ok or not ...
all ok with adb method
Will flash it again tomorrow to check logs.
As mentioned by Dusha40, all seems ok and no fc,
But Moto display and Moto Actions not working
Click to expand...
Click to collapse
Mmm that's strange everything seems to work properly for me.
Does this ROM have dual SIM support? Thanks.
kwongwt said:
Does this ROM have dual SIM support? Thanks.
Click to expand...
Click to collapse
Have not tested, But it should.
Sensors not working.
Dear host, if you have the version of EU retail 7.0, could you please give me the url to download?
Can anybody provide build.prop from original Nougat firmware?
Thanks
Sensors/Moto Actions aren't working for me either.
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
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Victoria power profile and it's compatible with P!
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your VTR over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a VTR-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have VTR, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay [/URL]
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-VTR.apk
XDA:DevDB Information
[Overlay] Dil3mm4's Overlays for Huawei Victoria Series devices (all variants), Tool/Utility for the Huawei P10
Contributors
Dil3mm4
Version Information
Status: Stable
Created 2018-08-28
Last Updated 2018-08-28
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.