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.
Related
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Unofficial build: aicp_santoni_q-15.0-WEEKLY-20200430.zip
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work), GApps are already included for some a/b devices.
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/hemantbeast/android_kernel_xiaomi_santoni
Device tree source:
https://github.com/AICP/device_xiaomi_santoni
Vendor source:
https://github.com/AICP/proprietary_vendor_xiaomi
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
rainforce279, nichcream, nathanchance
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
AICP 15.0, ROM for the Xiaomi Redmi 4X
Contributors
hemantbeast, wartomato
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: MIUI 9 v30+
Based On: GZOSP, LineageOS
Version Information
Status: Beta
Created 2018-02-19
Last Updated 2020-05-01
Reserved
MIUI Firmware:
Latest : fw_santoni_miui_HM4XGlobal_V11.0.2.0.NAMMIXM_eae1390b46_7.1.zip
Flash this zip file first if you are coming from MIUI 8.
Then flash the rest of the zips like Rom, Gapps, etc.
Aicp 16.1 build
aicp_santoni_r-16.1-WEEKLY-20210515.zip
Hi,
does this ROM support MicroG/signature spoofing?
Cool man, a separate thread for 13.1 finally.
Exited to try
Which thread is the main one now? I'm seeing two of them!
wow nice sir
nur Fitrianto said:
wow nice sir
Click to expand...
Click to collapse
if i happens to flash the ROM 8.1.x can i still degrade my phone into nougat 7.1.2 ?
---------- Post added at 07:37 PM ---------- Previous post was at 07:35 PM ----------
if i happens to flash the ROM 8.1.x can i still degrade my phone into nougat 7.1.2 ?
please add the function of hiding the roaming icon, and the vibration when connecting a call.
plsssssssss
very much needed
I was very much waiting for your official assembly and frustrated that there are no these functions. but in general the firmware is beautiful, I advise everyone
are you part of TEAM GHOST?
criticallife said:
if i happens to flash the ROM 8.1.x can i still degrade my phone into nougat 7.1.2 ?
---------- Post added at 07:37 PM ---------- Previous post was at 07:35 PM ----------
if i happens to flash the ROM 8.1.x can i still degrade my phone into nougat 7.1.2 ?
Click to expand...
Click to collapse
Yes, you can downgrade any time
When we turn on navigation bar it shows force stopping but it works..
battery drain is so fast,overnight **10%**.
On other oreos there is not even single %..
Please improve battery.noticed that system needs to be handle operations like pro I mean better ram management..When we click on choosing wallpapers it takes 2sec time Wallpapers app to open and others are also like only some time
Thanks Dev..
here logs
saikumar parate said:
When we turn on navigation bar it shows force stopping but it works..
battery drain is so fast,overnight **10%**.
On other oreos there is not even single %..
Please improve battery.noticed that system needs to be handle operations like pro I mean better ram management..When we click on choosing wallpapers it takes 2sec time Wallpapers app to open and others are also like only some time
Thanks Dev..
here logs
Click to expand...
Click to collapse
Man this rom is amazing. Im getting perfect sot. Tomorrow i will post some screens right here, when reaches low levels. You even thinked re flash? (Clean!) Rom and gapps. Both. (8.1, nano)
Thank you for your hard work!
You're quite probably the only dev that updates at fixed intervals, and I appreciate that.
For me all Oreo ROMs are still buggy, but when the time comes I'll be sure to jump in the AICP wagon.
saikumar parate said:
When we turn on navigation bar it shows force stopping but it works..
battery drain is so fast,overnight **10%**.
On other oreos there is not even single %..
Please improve battery.noticed that system needs to be handle operations like pro I mean better ram management..When we click on choosing wallpapers it takes 2sec time Wallpapers app to open and others are also like only some time
Thanks Dev..
here logs
Click to expand...
Click to collapse
I lost about 5% over night, too.. usually there is 0% drain in other ROMs. Maybe it's because of the missing "Disable Wifi when Screen is turned off" function. Is it an Oreo "feature" at all or ROM related?
Got reboot over the night. Other Oreo roms reboots too from time to time.
Tim1909 said:
I lost about 5% over night, too.. usually there is 0% drain in other ROMs. Maybe it's because of the missing "Disable Wifi when Screen is turned off" function. Is it an Oreo "feature" at all or ROM related?
Click to expand...
Click to collapse
Let's wait for update
OK, I've installed magisk and lost phone signal. Can we use SuperSU?
Edit, no problem with SuperSU.
This temperature is way of chart, I think
What is this topic about?
I've spent quite some time writing fixes for GSIs to work properly on our Mi Max 3.
As part of that, we now have a list of easily flashable fully working Mi Max 3 ROMs to pick from.
This topic will be used to keep track of all fully working ROMs and of course to host the latest set of GSI patches / flash templates.
Available ROMs:
These have been tested and confirmed fully working (sans ROM-specific bugs).
AOSiP
Build date: 2019-05-14
Patch date: 2019-05-17
Flashing guide:
Unlock your device's bootloader.
Flash nijel8's modded TWRP recovery.
Pick and download one of the available ROMs.
Reboot into TWRP recovery and flash your ROM of choice.
Go into TWRP's wipe menu and "factory reset" your device (aka. slide the bar).
Flash Gapps (Opengapps / Bitgapps) if your ROM of choice requires / you want it.
Reboot your phone and set it up to your liking.
How can I get my ROM of choice listed here?
Download the TWRP package template from here!
Grab a GSI of your choice and unpack the system image (if it is compressed).
Rename the unpacked system image to system.img and place it inside the system folder inside the template zip file.
Rename the resulting zip file accordingly, flash it, test it, and after you've confirmed everything's working fine, upload and share it.
How do I enable DT2W (double-tap to wake)?
Create a file named "enable_dt2w" (without the quotes) in your device's internal storage.
Reboot your device.
Changelog:
2019-05-17
Changed cpusets to 0-7 (UX gains)
Set rendering thread to schedule as FIFO (UX gains)
Updated AOSiP to its latest (2019-05-14) build
2019-05-10
Swapped firmware & vendor base to stable 10.3.1.0
Updated AOSiP to its latest (2019-05-07) build
2019-05-01
Added two touchscreen-related properties to build.prop
2019-04-30
Updated the kernel to ResurrectedKernel 5.0 (brings a whole bunch of new governors)
Changed default little core governor to alucard
Changed default big core governor to darknessv5
Updated AOSiP to its latest (2019-04-29) build
2019-04-22
Fixed a mistake on my end that made the screen flicker on brightness changes (sorry guys)
Updated the kernel to ResurrectedKernel 4.1 (kcal support!)
Updated AOSiP to its latest (2019-04-22) build
2019-04-21
Fixed the device fingerprint issue (Magisk users should now be CTS-verified by default again)
Added AptX & AptX HD Bluetooth support
Removed DotOS & PixelExperience from the rooster because the WiFi HotSpot function wasn't working properly in them
2019-04-12
Added addon.d support (which means dirty-flashes won't lose their Gapps, Magisk, etc. anymore)
Tested and added Pixel Experience to the roster
2019-04-10
Added ResurrectedKernel (Unlocks 1.8GHz on Little Core / 2.0GHz on Big Core)
Tweaked Governor to utilize ResurrectedKernel's frequency range fully
Updated DotOS bundle to latest build
Repacked all bundles with latest patch
Dropped "Minimal Package" support as its no longer maintainable in tandem with ResurrectedKernel
It ended up with the lags (AOSIP).
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Germano1980 said:
It ended up with the lags (AOSIP).
Click to expand...
Click to collapse
Where's the lag Germano? Works fine for me.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
Stuck how? If you have "unlock" trouble, as in, your PIN won't let you in, use the "Remove lockscreen" option inside TWRP to remove your previous lockscreen data.
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
MrColdbird said:
Where's the lag Germano? Works fine for me.
Click to expand...
Click to collapse
Before installing their zip, they had some lags in screen transitions and to slide and open apps. Now, everything got more fluid and faster. It was great ... until voLTE is working (and my operator informed me that my device was not compatible with haha).
---------- Post added at 19:14 ---------- Previous post was at 19:07 ----------
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
What vendor is your device on? Many GSI's only start at a particular vendor (Oreo or Pie).
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
Make sure the GSI you picked supports Pie vendors.
Not every GSI does... and the ones that are still stuck on Oreo vendors are... troublesome, to say the least.
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
The last time I had problems in booting the GSI roms I did the following:
1- I reinstalled the latest global version of Miui Oreo via miflash (Beware of ARB)
2- Logged in the Mi account, enabled the USB debugging and installation by ADB settings to install the TWRP
3- I installed TWRP (nijel8's modded), formatted the data and then installed xiaomi.eu
4- I configured the device and made a backup of xiaomi.eu
5- As I already had the files, I installed AOSIP, without deleting the system, just cleaning the data of xiaomi.eu
6- After the boot, I installed the gapps and magisk.
I never had any problems installing GSI's on my device.
When I was in Miui Oreo, I tested some roms that only boot the Oreo vendor (Bootleggers, PixelDust among others), but I think with the Oreo vendor they spend a little more battery life.
(hope this helps you)
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Masacci0 said:
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Click to expand...
Click to collapse
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Skyllery said:
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Click to expand...
Click to collapse
So if i install this rom https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ i'm ok and without arb? I get confused because on the image they say mi max 3 has arb, if they mean the official 10.2 has arb, why even put the image in the .eu version? It just confuses people.
So i go with this rom reach setup screen, recovery and install the gsi rom?
Jesenican said:
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Click to expand...
Click to collapse
Try the xiaomi.eu versions from last month based on installing AOSiP. Today I tried with the versions of this month and did not boot.
I am having the exact same issue. I followed the guide and installed the latest xiaomi.eu 9.3.7 beta and boot no problem then i flash gsi .img and it gets stuck at MI Logo and wont go any further. I have tried latest xiaomi.eu beta, stable, last months, month before that. All xiaomi.eu boot fine without issue but as soon as I flash any gsi .img it gets stuck at MI Logo screen? Am I doing something wrong?
Also the gsi i am using is latest pixel experience arm64 A only.
Any help would be greatly appreciated.
Same. I tried 3 different GSI roms and kept being stuck on the mi logo... :'(
only aosp gsi works, still getting android.process.media and bluetooth crashes
Edit: instead of com.android.media it was android.process.media
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
jngiag said:
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
Click to expand...
Click to collapse
You're my hero! That did the trick. ;D
So can i normaly flash older xiaomi.eu version without fear of ARB?
OP post updated with a new package.
Changelog:
Tweaked the governor to boost properly and use the 1.6 / 1.8GHz maximum little / big frequencies. (Everything's even smoother now~)
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 14.0
Download link: https://www.androidfilehost.com/?w=files&flid=291290
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
GApps from opengapps.org is almost always a good choice
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 28.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure might vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
The root solution can be flashed together with every OTA update (= ROM Update).
Currently supported Root Solution:
Magisk stable
Magisk versions >= 17.2 don't usually require to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time.
Unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
To be able to flash using the built-in OTA app, TWRP recovery is needed.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/icxj1/android_kernel_htc_msm8960/tree/p9.0
Device tree source:
N/A
Vendor source:
https://github.com/icxj1/proprietary_vendor_htc/tree/p9.0
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
Contributors:
@icxj1
The following informations are ONLY needed, when you are not opening up a devdb thread on XDA!
ROM OS Version: 9.0.x Pie
Kernel: Linux 3.4.x
Version Information:
Status: Development
Release Date: 03-10-2019
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
HTC ONE M7ul,wlv,wls Pie testing, ROM for the HTC One (m7)
Contributors
icxj1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
ROM Firmware Required: latest GPE
Based On: GZOSP
Version Information
Status: Testing
Current Stable Version: N/A
Current Beta Version: UNOFFICIAL
Beta Release Date: 2019-03-10
Created 2019-03-12
Last Updated 2019-03-12
reserved
reserved again
reserved 1 more
thx for the build.i will try it when the files are up
Android 9 on the 2013 HTC One? This cannot be real?!!
daywalk3r666 said:
thx for the build.i will try it when the files are up
Click to expand...
Click to collapse
I will get test build up soon guys having trouble with uploads past 2 days. Keep dropping out at 65%.
clarkgable said:
Android 9 on the 2013 HTC One? This cannot be real?!!
Click to expand...
Click to collapse
Hello nice news,i want test android P,please give me link for downloading, thanks
Great!
Looking forward to test the rom.
Here is the sneak peak test build as promised, i am sure it will have plenty of bugs to work through. Make sure yo have a good backup of whatever rom you use as a daily driver. i will update thread with screenshots & bug list as we go. This build is for m7u-ul only, no vzw or sprint for now.
m7 += https://www.androidfilehost.com/?fid=1395089523397918526
I've tried out the test ROM, with:
- OpenGAPPS (ARM, 9.0, stock)
- Magisk 17.1
- TWRP 3.2.1.0
So far I've been having difficulty even trying to get through the Setup Manager.
There has been multiple reboots, the lag can definitely be noticed, and the overheating is there.
I hope most of these bugs can be fixed and patched soon.
[UPDATE]
Got through the Setup Manager, however the reboots are still occurring.
Also I remembered that icxj1 created TWRP 3.2.3.0 that supports the 9.0 device tree so I'll try flashing that and then reflashing the ROM.
I had the same problems so what I did was install the ROM and magisk without gapps. It booted normally but it was laggy. So I installed the LKT module and choose the performance profile to give me better experience ( less lag). After that I installed the gapps (pico) and everything is fine. No reboots so far.
vincenzo697 said:
I had the same problems so what I did was install the ROM and magisk without gapps. It booted normally but it was laggy. So I installed the LKT module and choose the performance profile to give me better experience ( less lag). After that I installed the gapps (pico) and everything is fine. No reboots so far.
Click to expand...
Click to collapse
I'll try doing it that way, If it still doesn't work well then I guess I'll go back to my daily driver of Lineage OS 14.1 for a while.
---------- Post added at 05:22 AM ---------- Previous post was at 04:57 AM ----------
There might be a reason as to why it keeps rebooting, and it might be the D2TW function which ruins the performance, it overheats a lot and the reboots do occur. icxj1 can you please make a flashable zip to disable D2TW?
---------- Post added at 05:59 AM ---------- Previous post was at 05:22 AM ----------
AICP - 14.0: First impressions
Problems with this ROM:
- The main issue with this ROM is the random reboots that occurs when you stress it (possibly RAM management).
- Very laggy / slow start: shown in the bootanimation, no wallpaper shown on lockscreen and home until it blanks out and wallpaper suddenly works again.
- The quick tiles shows 6 which overlaps the width of the taskbar.
- UI is usually very slow and laggy and touch response isn't too great.
- Wi-Fi problems occur, my network didn't save after a random reboot.
But even still, it's lovely to see some of that sweet, sweet Pie on my M7.
Don't waist time with root and gapps. Should have know from dealing with you guys on Oreo that the word testing goes in one ear & out the other. And not even a single log.
icxj1 said:
Don't waist time with root and gapps. Should have know from dealing with you guys on Oreo that the word testing goes in one ear & out the other. And not even a single log.
Click to expand...
Click to collapse
Sorry buddy. We are excited about pie!!!
Last but not least
For now didn't manage to make it to the launcher. Reboots at welcome and choose language screen. If I can help some way on this step, guide me to log it
Hi, are you planning to compile to sprint and verizon, and when? I have both, so i can test it
P.S.Good job, you are awesome
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
(click on xiaomi, then click on the phone picture and just click download on the zip with the lastest date)
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery.
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into your recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary on system updates!
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/Blacksuan19/kernel_dark_ages_vince
Device tree source:
https://github.com/ender1324/android_device_xiaomi_vince
Vendor source:
https://github.com/ender1324/vendor_xiaomi_vince
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
XDA:DevDB Information
[ROM][10/Q][OFFICIAL][2020/05/29] AICP 15.0 for the redmi 5 plus, ROM for the Xiaomi Redmi Note 5 / 5 Plus
Contributors
ender1324, @KenHV, Blacksuan19
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Lastest stock firmware
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 15.0
Stable Release Date: 2020-05-18
Created 2020-05-19
Last Updated 2020-05-30
reserved
Es la pole?
Awesome !! This has been my fav rom from old days...
We're official now
ender1324 said:
We're official now
Click to expand...
Click to collapse
ok zoomer
ender1324 said:
We're official now
Click to expand...
Click to collapse
Can you tell me what is the difference between official and un official roms ,I am new to this stuff
Sent from my Redmi Note 5 / 5 Plus using XDA Labs
PlayStore certified?
Shivaprasad.G.I said:
Can you tell me what is the difference between official and un official roms ,I am new to this stuff
Sent from my Redmi Note 5 / 5 Plus using XDA Labs
Click to expand...
Click to collapse
well one is supported by the official aicp team and yeah its unmodified aicp source
when unofficial is either unmodified or modified, its not supported by the official team
luistro said:
PlayStore certified?
Click to expand...
Click to collapse
it passes safetynet by default
new ota is pushed
I really love this rom and its the most stable of the Android 10 ROMs ive tried so far, but I am having a weird problem with calls on it. My voice starts not going through to the other end mid call sometimes and i have to recall or just the call ends randomly etc. I was on the latest version of the firmware when this happened, im not sure what it can be caused by if not ROM and the firmware.
I changed back to EU MIUI to avoid having this problems but I was totally satisfied with AICP other than that, I just want to know if its fixed so I can flash the ROM again. Or maybe understand what its caused by if its not the ROM.
Devs please look problem with DATA and two SIM cards. Data of SIM 1 not working , when switch Data to SIM 2 - all is fine.
If replace SIM slots - same story, SIM 1 data not work, SIM 2 - work.
Dont know why but all android 10 builds have this problem, only in Nitrogen OS - all is fine.
Thank you
AlienCreature7 said:
I really love this rom and its the most stable of the Android 10 ROMs ive tried so far, but I am having a weird problem with calls on it. My voice starts not going through to the other end mid call sometimes and i have to recall or just the call ends randomly etc. I was on the latest version of the firmware when this happened, im not sure what it can be caused by if not ROM and the firmware.
I changed back to EU MIUI to avoid having this problems but I was totally satisfied with AICP other than that, I just want to know if its fixed so I can flash the ROM again. Or maybe understand what its caused by if its not the ROM.
Click to expand...
Click to collapse
Hey!, We're working on a fix with the developers
oddi541 said:
Devs please look problem with DATA and two SIM cards. Data of SIM 1 not working , when switch Data to SIM 2 - all is fine.
If replace SIM slots - same story, SIM 1 data not work, SIM 2 - work.
Dont know why but all android 10 builds have this problem, only in Nitrogen OS - all is fine.
Thank you
Click to expand...
Click to collapse
Its a tree bug, we're working on a fix for that too
ender1324 said:
Hey!, We're working on a fix with the developers
Click to expand...
Click to collapse
Great to hear that, I assume its fixed now? Just saw the ROM has been getting weekly updates so I am going to try it again now!
Just flashed the latest version and it already rebooted 2 times in the middle of setup.
{
"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"
}
Welcome to Project Kebab Treble For Galaxy J3 2017 and 7570 Devices
Some information you should know..
This is a full Treble ARM A64 Vendor/Kernel Based on J4 and J6 for Exynos 7570
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
I am not responsible for bricked devices, dead SD cards,
You are not allowed to use anything from this ROM without permission, if you wanna port my project PM me.
Any sort of file kanging will be reported without hesitation.
General features:
- based on J600F a bit with extra Blob and HAL.
- Support most of 7570 Device: G570X, J400X,J260X,J330X.
- Support Q,R GSIs.
- It's system as root.
- More performance compared to stock.
- Nitrogen Kernel V5 With treble support
- Pixel Live Wallpaper added in AROMA
- HK Tweaks features added in AROMA
- Kebab ?
NitrogenKernel Features:
Based on J400MUBU9CTGO source
Linux 3.18.140 under samsung Q kernel
Compiled with Google 4.9 Toolchain
Permessive SELinux
Optimized for Performance
GPU Driver: r29p0 driver
Custom Voltage Control
Dynamic FSync
Boeffla Wakelock blocker
Powersuspend
Charging boosted
SecBatteryControl
CPU Overclock up to 1.69 GHz
CPU Underclock go to 345 MHz ( For battery life )
Reduced spam on log for more RAM
GPU OC up to 1001 Mhz
Optimized Video Rendering
Changelog KEBAB 2.0:
- V2.2.1 Changelog:
- Rebased On Android 10 Vendor
- Add USB and Thermal HAL from stock
- Add support for more device
- Fixed Video Encoder/Decoder
- Add new wallpaper
- Fixed lag on some point
- Update props
Click to expand...
Click to collapse
Changelog KEBAB 1.0:
- V1.5 Changelog :
- General Optimization.
- Fixed some issues
- Add support for J3 2017 and J4 2018.
- New props
- Nitrogen Kernel V3.5
- And others ...
- V1.1 Changelog:
- Full 7570 libs.
- Thermal hw from stock.
-Add support for other variant.
- OMX from stock Pie.
- Update props.
Click to expand...
Click to collapse
Bugs
Selinux is permissive
Stretched camera in some apps
Delay Lockscreen on some GSI (GSI issues)
Offline Charging
Report Bug on Telegram Group
- How to Install ?:
if you are on old Create_vendor please revert it
- Flash `Exynos7570_CreateVendor 2.0` Or The new repartition script for J2 Core use this script and reboot recovery, (the new repartition will wipe all data also internal storage but will increase system partition and vendor and you have to wipe system, cache, vendor and format data).
- Flash `KEBAB 2.0_EXYNOS7570`
- Flash your desired A64 A/B GSI (ARM32_Binder64) : "a64_bvn"
- Reboot and enjoy GSI
- Flash Audio_fix after booting
- After boot flash any Gapps Arm (Pico recommended) if GSI didn't have.
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7570_RevertVendor 2.0` if you are on Kebab 2.0 and "Exynos7570_RevertVendor " if you are on old kebab Only if you flashed Create vendor, With the new repartition you should flash stock firmware with stock CSC (CSC_OMC...xxxxxxxxxx.md5)
- Reboot recovery
- It's recommended to flash stock pit
- Flash any non treble rom or restore your previous twrp backup
Download :
Second Post
Press thanks button if you liked my work!!
Credit :
@ananjaser1211
@soulr344
@asarre (me the main developper)
XDA:DevDB Information
Treble project For J5 Prime , ROM for the Samsung Galaxy J5
Contributors
asarre, soulr344, ananjaser1211
ROM OS Version: 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest Firmware
source code: [url]https://github.com/asarr22/Nitrogen[/URL]
Version Information
Status: Stable
Current Stable Version: 2.2.1
Stable Release Date: 2020-04-30
Created 2020-04-30
Last Updated 2020-04-30
XDA:DevDB Information
Treble project For J3 2017, ROM for the Samsung Galaxy J3 (2017)
Contributors
asarre, soulr344, ananjaser1211
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest Firmware
Version Information
Status: Stable
Current Stable Version: 2.2.1
Stable Release Date: 2020-10-27
Created 2020-10-27
Last Updated 2020-10-27
Download | Changelog | ContactTelegram
News channel: Telegram
---------------------------------------------------------
Download:
KEBAB 2.0 Q
V2.2.1 Link: Here
KEBAB 1.0 PIE
V1.5 Mega Folder: Here
If you liked my rom please press thanks button
------------------------------------------------
Donation : PayPal
!!:good::good:
F.A.Q
Q: Device requirements ?
A : you MUST be on latest PIE firmware.
Q : Do i need to format internal storage ?
A : No
Q : Do i need to wipe Data?
A : Yes, If you come from other rom.
Q : Do i need to wipe Data if GSI has an update ?
A : No
Q : Do i need to re-flash Project Kebab if I change my GSI ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : Any GSI that is A64_AONLY is supported [10/11]
wow so amazing, can't wait to try it!
hello, is it a problem if the phone is on OneUI 9?
In the F.A.Q it's wriiten that we must have oreo bootloader.
And in the OP it's witten that we must flash A/B GSI but in the F.A.Q it's witten A_ONLY, whitch GSI must we flash?
Edit : there is also 2 "system image" when i select the gsi img
Edit 2 : I finally made it! We must effectivly have Oreo bootloader, flash a A/B GSI on the 2nd "system image" partition. The only issue now is that the audio is broken, even with the "Audio_Fix" provide in the OP. Thanks for your work!
Lilobast said:
hello, is it a problem if the phone is on OneUI 9?
In the F.A.Q it's wriiten that we must have oreo bootloader.
And in the OP it's witten that we must flash A/B GSI but in the F.A.Q it's witten A_ONLY, whitch GSI must we flash?
Edit : there is also 2 "system image" when i select the gsi img
Edit 2 : I finally made it! We must effectivly have Oreo bootloader, flash a A/B GSI on the 2nd "system image" partition. The only issue now is that the audio is broken, even with the "Audio_Fix" provide in the OP. Thanks for your work!
Click to expand...
Click to collapse
Oreo bootloader is not required on J330, also please try to get a log for audio
asarre said:
Oreo bootloader is not required on J330, also please try to get a log for audio
Click to expand...
Click to collapse
how do i get a log for this?
I will also retry with pie bootloader, maybe with that audio work
thanks
Edit: I try to get log, i attach it to my message
http://www.mediafire.com/file/9teu36rcon0fsz5/dmesg.log/file
Edit 2: even with pie bootloader Audio is broken
Lilobast said:
how do i get a log for this?
I will also retry with pie bootloader, maybe with that audio work
thanks
Edit: I try to get log, i attach it to my message
http://www.mediafire.com/file/9teu36rcon0fsz5/dmesg.log/file
Edit 2: even with pie bootloader Audio is broken
Click to expand...
Click to collapse
Thanks, I will check it
hello, after a while i retry this vendor.
I retry audio fix but i can't get the audio working.
After testing i also discovered that camera is broken.
I attach a logcat
I realy appreciate your work in this device, keep up and thanks
I have been trying to use this for J330F (J3 2017 SM-J330F/DS) and each time everything installs fine, The vendor script, the kebab install and the GSI rom to the second system partition. (Tried first partition as well)
But I always end up unable to boot and the phone defaults to download mode when I reboot.
Im assuming I have missunderstood a step in the process or something becouse its over 10 GSI A only A64 binder I have tried.
Steps I have taken:
Booted to TWRP.
Flashed `Exynos7570_CreateVendor 2.0 (Ive also tried Universal7570_repartitioner .zip in some reinstalll attempts
3.Wiped System, Cache, Vendor and formated data.
A. When coming from stock I have tried both RMM_Bypass_v3 by Corsicanu and Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019 by ashyt16
When not on stock and those bypasses are already flashed I have installed Kebab 2.0 (and 1.5)
GSI Rom installation.
Tried almost all GSI A only - A64 Roms i could find, as well as a bunch I know is the wrong versions (Like Arm64) just in case I missunderstood what version is meant for this device.
RadicalQuackV2 works and all normal roms for the device installs just fine, and Im no expert but I have flashed roms for many years so I think I have followed the instructions correctly...but obviously I F*cked up somewhere.
Heelp please
Emaildotcom said:
I have been trying to use this for J330F (J3 2017 SM-J330F/DS) and each time everything installs fine, The vendor script, the kebab install and the GSI rom to the second system partition. (Tried first partition as well)
But I always end up unable to boot and the phone defaults to download mode when I reboot.
Im assuming I have missunderstood a step in the process or something becouse its over 10 GSI A only A64 binder I have tried.
Steps I have taken:
Booted to TWRP.
Flashed `Exynos7570_CreateVendor 2.0 (Ive also tried Universal7570_repartitioner .zip in some reinstalll attempts
3.Wiped System, Cache, Vendor and formated data.
A. When coming from stock I have tried both RMM_Bypass_v3 by Corsicanu and Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019 by ashyt16
When not on stock and those bypasses are already flashed I have installed Kebab 2.0 (and 1.5)
GSI Rom installation.
Tried almost all GSI A only - A64 Roms i could find, as well as a bunch I know is the wrong versions (Like Arm64) just in case I missunderstood what version is meant for this device.
RadicalQuackV2 works and all normal roms for the device installs just fine, and Im no expert but I have flashed roms for many years so I think I have followed the instructions correctly...but obviously I F*cked up somewhere.
Heelp please
Click to expand...
Click to collapse
exactly the same for me...all A64Aonly GSI I've tried did not work (blank screen after flash gsi). Moreover, RadicalQuackV2 works but i've micro sd and audio bugs
exactly the same for me...all A64Aonly GSI I've tried did not work (blank screen after flash gsi). Moreover, RadicalQuackV2 works but i've micro sd and audio bugs
Click to expand...
Click to collapse
Try to flash a64_AB gsi
Lilobast said:
Try to flash a64_AB gsi
Click to expand...
Click to collapse
thanks. now I was able to install Havos OS 3.8....however still there is the audio bug (even is I installed the audio fix) and some screen mislight :[email protected]
Anyone test erfangsi Android 11 arm64 ab with this vendor?
Erfan GSIs Updates
Channel of ported OEM firmwares to GSI Group: @ErfanGSIs Download links: https://mirrors.lolinet.com/firmware/gsi/ XDA: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/pie-erfan-gsi-ports-t3906486
t.me
Will not be quite stable, but possible?
hi, thanks for the work you have made on this project. i have been trying to solve the audio bug, but i can t find a way to. i have tried multiple GSI and in all of them the system build.prop the audio and camera entries are missing, beside this, the audio related services wont run or crash.
i have questioning in diverse places and the majority say that the "no audio bug" is due to audio driver in kernel or audio Hal. i hope that the the solution is near and pardon if i am wrong in any aspect.
if you need any kind of help just ask. keep up and thanks again
fowedi said:
hi, thanks for the work you have made on this project. i have been trying to solve the audio bug, but i can t find a way to. i have tried multiple GSI and in all of them the system build.prop the audio and camera entries are missing, beside this, the audio related services wont run or crash.
i have questioning in diverse places and the majority say that the "no audio bug" is due to audio driver in kernel or audio Hal. i hope that the the solution is near and pardon if i am wrong in any aspect.
if you need any kind of help just ask. keep up and thanks again
Click to expand...
Click to collapse
Hi, I have just installed the GSI of LineageOS 18.1 on my SM-J330FN and the only no working things are the microphone and the audio and the camera, have you solved the audio bug and mic bug ?
Any fixes for audio?