[OFFICIAL][zippo] LineageOS 20 (Android 13) for the Lenovo Z6 Pro - Lenovo Z6 Pro ROMs, Kernels, Recoveries, & Other D

[OFFICIAL][zippo] LineageOS 20 (Android 13) for the Lenovo Z6 Pro - Lenovo Z6 Pro ROMs, Kernels, Recoveries, & Other D

KNOWN BUGS
Currently only works with bootloader unlocked
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Fingerprint icon is too low compared to actual location of the scanner
Heyyo, allow me to introduce myself. I am Marc "ThE_MarD" Bourgoin and I maintain LineageOS and TWRP for the LeEco Le Max 2 (X2) and was crowdfunded a zippo which I will maintain LineageOS for (with selinux enforcing of course) and maybe assist with TWRP later. I also own a Motorola Edge 30 (dubai) which I maintain LineageOS for, Asus Zenfone 5z (Z01R), and I was also donated a Motorola Moto X4 (Payton) which I maintain LineageOS and TWRP for.
I'd like to take this moment to also thank anyone who donated to the crowdfunding campaign for my zippo! Without you? I wouldn't have this epic device in my hands to work on.
Also MAJOR thanks to Zhenxiang Chen (aka pasta_con_tonno, Lucchetto) for all the amazing work he has done on zippo.
Special thanks to Einar Gednochsson (aka kanstmablason, pete80pro) for organizing the crowdfunding campaign for my zippo and also a new one for KuranKaname so he can revamp our kernel.
Thanks also to hypnz, chema f, gawin and Lucky for also working in zippo and to HighwayStar who started the initial trees for heart (Lenovo z5 Pro GT) which zippo trees are based upon and Art_Chen for working on heart and zippo and also bringing us FOD Dimming and DC Dimming.
Thanks again to Zhenxiang and Chema f for figuring out and implementing the QFIL recovery and vbmeta while keeping the bootloader locked

Heyyo, LineageOS 20 official is out and the first build for zippo is up!

@ThE_MarD ,
Will you be including this commit the hardware fix/support for the camera (camera: Expose aux cameras in third party apps) from Chemas Evo build in your Lineage build? I'd rather not have google services installed to use GCAM in order to access the other lens' and the ZUI camera does not install correctly anymore for 13 (it did for 12, partially). There are other apps that don't rely on g-services that are able to access the hardware (HIDL?) switch to select which lens is used for image processing.

Heyyo @project_2501 , after checking with other devs about that commit and also how aux cameras are set up? I think for that we can just modify our props in the device tree tbh. The problem we currently have is we are limiting it to only a few app names. We could transition to an aux camera blacklist since there's probably only a handful of apps that would screw up (I can't remember if it was here or my Asus Zenfone 5z, but the Adobe Scan app would screw up and fail to initialize any camera) so we could just tackle a blacklist as crappy apps show up lol
As you can see here, we mainly expose aux cameras to a few apps and others have to essentially find out themselves like gcam mods
android_device_lenovo_sm8150-common/system.prop at lineage-20 · LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com

@ThE_MarD ,
Will the blacklist instead of a whitelist be applied on the next scheduled build? Thank you for addressing it.

@project_2501 sorry not yet as I need to test it first and I haven't had time yet

Heyyo, lineage-20.0-20230122-UNOFFICIAL-zippo test build is going up! ! It has a new rebased kernel by MikeNG. Please test all functions. It also has a change to swap the aux camera allowed list to an aux camera exclude list to keep things easier and only exclude apps that don't play well with aux cameras so please test a lot of camera apps
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo - OSDN
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo #osdn
osdn.net
@project_2501 if you could please test this build. You can swap between unofficial and official builds at any time

Switching between the camera lens' works (still don't see 48mp for the main lens' resolution); install almost hanged on patching vendor which I found odd. Camera app believes there are six cameras for some odd reason and will crash if selecting the sixth camera, I'm guessing it's also referencing the video profile because it doesn't crash in video mode when selecting the sixth camera (dual lens for video or mixed up with front lens' maybe)? Can you provide a link to the source for the kernel?

@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there

ThE_MarD said:
@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there
Click to expand...
Click to collapse
Open Camera.
I'm unfamiliar with MikeNG and kernel modifications he may have committed when looking at the source code for the kernel, just wondering since you stated it was using a different kernel (than official LOS?).

@project_2501 oh, Open Camera does things a lot differently than other camera apps so tbh I don't think there's a way to configure it... So I'd recommend just sticking with Aperture or use a gcam mod... But from what you said Open Camera is now seeing more camera apps so the change in aux camera lists commit is working then?

@ThE_MarD , yes I can switch between all the lens'. System stability has not been jeopordized, the app will just crash if trying to process from the sixth camera ID. Do you remember what modes the ZUI camera app had? Was there a dual (both front and back camera) mode? Maybe the sixth profile is for the front camera and the app doesn't switch to it when cycling through the lens' (front camera can still be accessed with a different on screen UI switch anyways). The problem in itself is app related; regardless, the commit works and should be included in the next build for others like myself who enjoy a clean minimalist build with full access to the hardware.

Hi, i'm on firmware 11.0.405 ST.
Now i'm still waiting my SN from Lenovo to unlock bootloader.
Newbie question:
After installing TWRP --> Wipe > tap "Format Data" button > type "yes" > keyboard checkbox > Flash firmware CN 12.5.332 > reboot to recovery or reboot to system ?
Thanks a lot for the rom!

Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.

ThE_MarD said:
Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.
Click to expand...
Click to collapse
@ThE_MarD , thanks for the reply. Appreciated
I'm still waiting file from Lenovo to unlock bootloader.

Finally got the file to unlock bootloader.
I flashed twrp > shut down the phone > hold Volume Up + Power > but it cannot boot to recovery, only show fastboot/bootloader.
Then I tried I flashed twrp > shut down the phone > Volume Down + Power > fastboot mode > then i select recovery mode > phone restarted > only returned to fastboot mode again.
Any help to solve this problem? failed to flash twrp recovery.
Thanks in advance.

@danz852 just to check, you're flashing it to the recovery partition?
The TWRP website has the full instructions too
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Code:
fastboot flash recovery twrp.img
Otherwise you can try first via Lineage Recovery and follow the LineageOS wiki instructions
Install LineageOS on zippo | LineageOS Wiki
wiki.lineageos.org

Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.html to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.

danz852 said:
Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.htmll to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.
Click to expand...
Click to collapse
UPDATE:
Finally it worked out:
I'm still using TWRP 3.4.0. Copy firmware L78051_CN_11_5_229_Q_Stable_recovery to internal storage then flash it. Reboot to System. It said my phone partition is corrupted .
Then i reboot the phone to Fastboot mode. I checked bootloader is Locked > proceed with fastboot flash unlock sn.img > fastboot oem unlock-go > reboot to system. After enable USB debugging in Developer Option > reboot to recovery > Wipe Dalvik, system, cache and format data > flash CN 12.5.332 and LineageOS. > reboot to system > Finally it booted to Lineage.
I'm happy. Thanks again @ThE_MarD for the rom!!!

Related

[DEPRECATED][ROM][10][Unofficial][TUCANA] LineageOS17.1

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community-built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restores the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
What's working:
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
IR camera
Camera
Camcorder
FOD
Video Playback
Audio
Sensors
Flash
GPS/GNSS
VoLTE
Known issues:
Selinux permissive
Instructions:
Make sure you have a custom recovery installed
Make sure you have miui_TUCANAGlobal_V12.0.3.0.QFDMIXM or later installed (Android 10 only)
Download LineageOS 17.1 for tucana
Boot into recovery
Perform a DATA Format
Flash LineageOS 17.1 Rom
(Flash Gapps/Magisk) (for Magisk users see below)
Wipe DALVIK/CACHE
Reboot
Magisk:
To get Magisk working: First flash Magisk 20.4 and right after that Magisk 21.1 or later
Download:
lineage-17.1-20201206-UNOFFICIAL-tucana.zip
Prebuilt kernel source:
Kernel source
Donate:
Donation URL
Special thanks to:
LineageOS
Chema
AndroidHQ254
Hlcpereira
XDA:DevDB Information
LineageOS 17.1 tucana, ROM for the Xiaomi Mi Note 10
Contributors
alibei
Source Code: https://github.com/alibei/android_device_xiaomi_tucana
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: V12.0.3.0.QFDMIXM
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-28
Last Updated 2020-11-29

Changelog:
Code:
2020-12-06 ~ fixed the FOD brightness
2020-11-29 ~ Some improvements for FOD and UI (thanks Chema)
2020-11-28 ~ Initial release

Congratulations for your work .

Nice job!!!!

WoW....miui 12.0.3 do you need full ROM or just the firmware?

Kosecki99 said:
WoW....miui 12.0.3 do you need full ROM or just the firmware?
Click to expand...
Click to collapse
Full ROM, I checked before only vendor firmware and its didn't work.
You can get full ROM here: https://xiaomifirmwareupdater.com/miui/tucana/stable/V12.0.3.0.QFDMIXM/ very fast download speed

Congratulations on having achieved the impossible. Thank you for your effort and hours of selfless work. +1000

Great job :good:

Bug detected.
When you put security for the first time, be it fingerprint, pin, or whatever, there is no problem, but when you deactivate all security measures, the options Always Active and New Notifications on Screen + Screen Lock disappear without the possibility of see them again

You fixed Donation button, sweet
Code:
Transaction ID: 20444655146528013
ADB is fixed too

veimus said:
You fixed Donation button, sweet
Code:
Transaction ID: 20444655146528013
ADB is fixed too
Click to expand...
Click to collapse
Thank you for your donation

I've tried to flash it on my Mi Note 10, but I ended up stuck on bootloop.
Here's what I've exactly done:
- Since I was on MIUI 12.0.2, I've downloaded and flashed MIUI 12.0.3 (the one linked before, recovery version). Although I did flash it, I didn't boot up the phone, nor did go through setup wizard. I just rebooted back to TWR
- Performed Data format (advanced wipe - selected only "Data")
- flashed LOS
- format Dalvik/Cache
- Reboot
Could the issue be not going through first-boot setup after flashing to MIUI 12.0.3? Also, I'm trying to boot my phone on this MIUI right now, but it is definitely stuck on MIUI logo. I guess I screwed up big time.

tryingtogitgud said:
I've tried to flash it on my Mi Note 10, but I ended up stuck on bootloop.
Here's what I've exactly done:
- Since I was on MIUI 12.0.2, I've downloaded and flashed MIUI 12.0.3 (the one linked before, recovery version). Although I did flash it, I didn't boot up the phone, nor didn't go through setup wizard. I just rebooted back to TWRP
- Performed Data format (advanced wipe - selected only "Data")
- flashed LOS
- format Dalvik/Cache
- Reboot
Could the issue be not going through first-boot setup after flashing to MIUI 12.0.3? Also, I'm trying to boot my phone on this MIUI right now, but it is definitely stuck on MIUI logo. I guess I screwed up big time.
Click to expand...
Click to collapse
MIUI should normally boot. Maybe you can try the MIUI fastboot rom.

tryingtogitgud said:
I've tried to flash it on my Mi Note 10, but I ended up stuck on bootloop.
Here's what I've exactly done:
- Since I was on MIUI 12.0.2, I've downloaded and flashed MIUI 12.0.3 (the one linked before, recovery version). Although I did flash it, I didn't boot up the phone, nor didn't go through setup wizard. I just rebooted back to TWRP
- Performed Data format (advanced wipe - selected only "Data")
- flashed LOS
- format Dalvik/Cache
- Reboot
Could the issue be not going through first-boot setup after flashing to MIUI 12.0.3? Also, I'm trying to boot my phone on this MIUI right now, but it is definitely stuck on MIUI logo. I guess I screwed up big time.
Click to expand...
Click to collapse
The thing is, you went to advanced wipe and only picked "Data" only... If you do advanced wipe... You have to also choose "Internal," both "Cache's"and "System". It's easier to just go to "Wipe" press the "Format data" option and type in "yes".
Plus.... when coming from another Miui Rom, you have to wipe everything from the wipe options written above.
So do that.. and then follow the steps below.
-Reboot to TWRP (in case your PC does not see your phone connected to load 12.0.3.0).
-Then load the 12.0.3.0 full rom, flash... "format data option", type in "yes"...
-Reboot to TWRP again.....
-And then flash Lineage, GAPPS and the latest Magisk 21.1.. and reboot "System".
Now if it doesn't come through.. flash 20.4 Magisk first, reboot to TWRP.. flash 21.1 Magisk and reboot "System".

Wmateria said:
The thing is, you went to advanced wipe and only picked "Data" only... If you do advanced wipe... You have to also choose "Internal," both "Cache's"and "System". It's easier to just go to "Wipe" press the "Format data" option and type in "yes".
Plus.... when coming from another Miui Rom, you have to wipe everything from the wipe options written above.
So do that.. and then follow the steps below.
-Reboot to TWRP (in case your PC does not see your phone connected to load 12.0.3.0).
-Then load the 12.0.3.0 full rom, flash... format data..
-Reboot to TWRP again.....
-And then flash Lineage, GAPPS and the latest Magisk 21.1.. and reboot.
Click to expand...
Click to collapse
Of course, I did wrong data format! Now I've done it properly and it works, thank you!

Great work guys! Super props

Amazing work alibei , Chema and henrique thanks for this amazing rom

Is there any way to lunch camera and take pictures without unlocking the phone ? Can't find this option

veimus said:
Is there any way to lunch camera and take pictures without unlocking the phone ? Can't find this option
Click to expand...
Click to collapse
Can you explain please? I don't know what you mean.

any Rom type RR or ZenxOS? ... thanks

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 10 II [Gcam] [Performance]

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Not tested
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Reserved

Will it work on the dual SIM version XQ-AU52?

ig2205 said:
Will it work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
Of course.

i wish we can have it for our xperia 5ii lol

Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?

dreDREb13 said:
Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?
Click to expand...
Click to collapse
Flash directly, if you don't meet any issue, there is no need to wipe the data.
flyl0 said:
i wish we can have it for our xperia 5ii lol
Click to expand...
Click to collapse
Coming.

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Coming.
Click to expand...
Click to collapse
It would be even better Resurrection Remix
But I'm glad LOS 18.1 is coming, can't wait to try it!

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Click to expand...
Click to collapse
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?

erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?

dreDREb13 said:
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?
Click to expand...
Click to collapse
OTA package will remove vendor partition, I will provide OTA package until building vendor image Then we will go LineageOS official.
ig2205 said:
erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?
Click to expand...
Click to collapse
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.

Will this rom be rebased on the Android 11 stock ROM sources once we have them?

You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?

KriiXOne said:
Will this rom be rebased on the Android 11 stock ROM sources once we have them?
Click to expand...
Click to collapse
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
ig2205 said:
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?
Click to expand...
Click to collapse
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.

Just wondering, how's the camera performance (in terms of start-up and focus speeds) in these custom ROM's compared to stock? Getting rather annoyed by the performance of the stock ROM / camera app.

Sjll said:
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.
Click to expand...
Click to collapse
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.

ig2205 said:
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Post the result here plz.

Sjll said:
Run
Code:
fastboot getvar all
Post the result here plz.
Click to expand...
Click to collapse
Is that the point?

So I installed and everything booted up fine, but I hit a couple snags.
One, it looks like Open GApps hasn't officially released Android 11.0 builds yet, so I had to find test versions through their sourceforge to run.
Two, upon booting I'm having trouble using a third party launcher (KISS Launcher) with gesture navigation. For some reason it won't recognize the multitasking/return to home feature along the bottom, though the side gestures work fine. Not sure if that's something to do with the test builds of GApps or not. I made sure all gestures were turned off to check if maybe it's a conflict but it still didn't work. And the launcher ran just fine on my 17.1 install, so not sure what the issue is.
Three, my wallpaper that I have set to the correct resolution of the phone is now zoomed in slightly. It looks like this is a feature of the new notification shade, as when I pull it down it zooms out my wallpaper to the correct size. However, I can't seem to find a way of turning this feature off or getting my wallpaper to fit properly.
EDIT: I rebooted again after first boot and my issues with the third party launcher and gesture navigation went away. After looking into it more it looks like that wallpaper zoom feature is apparently baked in to Android 11, so no way of disabling that at the moment. Hopefully there's a change that can come in to remove that feature...
All looks good otherwise and this is turning out great!

[ROM] [12.1] [OFFICIAL] AICP 17.1 [OOS12] [kebab]

{
"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-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. 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:
LineageOS & CM (R.I.P.) team
Evolution X Team & @AnierinB
GZOSP 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 17.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
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:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: Download from HERE
Due to new light sensor autobrightness is a mess for now. But will be fixed soon I hope.
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 the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
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 how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: 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 perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform 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 lose 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 lose root. Now swipe to flash and reboot afterward.
Using the ROM:
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. 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 on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android S. 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 zip file.
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!)16.08.2022 Weeklies were the last builds based on OOS11 base.Starting with 23.08.2022 Builds, we are switching to OOS12 Base.BE ADVISED !!!!DO NOT FLASH NEW WEEKLY OVER 16.08.2022 Builds via OTA. Please follow the instructions in the 2nd post for FW update first, then you can flash New Weeklies.
If you are flashing using adb sideload, GAPPS needs to be flashed on every dirty flash as it's mentioned above.
If you are flashing using OTA, no need to flash GAPPS, .
Currently supported Root Solution:
Magisk versions >= feel free to report. Didn't tested myself.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
Using on board recovery will be enough mostly for your operations.
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_oneplus_kebab
Contribute to AICP/device_oneplus_kebab development by creating an account on GitHub.
github.com
Follow this guide if you want to extract the vendor blobs
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:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:
ROM OS Version: 12.1
Kernel: Linux 4.19.11-perf
ROM {Firmware|Vendor} required: Latest OOS 12 (At least C20/21 firmware)
Status: STABLE
Release Date: 23-08-2022
You want to see a "normal" night at the "DEV office", click here!!

For further support you can visit our TG Channel:
AICP Support Channel for OnePlus 8 Devices
PLEASE BE ADVISED - YOU MUST UPDATE TO OOS12 FIRMWARE BEFORE INSTALLING THE 8/23 UPDATE.

If you are on OOS11 based Stock or Custom ROM:
Best approach is to flash stock OOS11 and update to the latest for your device OOS12 OTA.
While it's done, you can follow the flashing instructions over stock OOS12 given below.
Click to expand...
Click to collapse
The current firmware upgrade path is available here as found on the Op8 series Telegram support group:
Spoiler
1. Boot up AICP recovery
2. Go to "Advanced" -> "Enable ADB"
3. Check your DDR type using the following command:
adb shell getprop ro.boot.ddr_type
or in case getprop returns an empty value, use:
adb shell cat /proc/devinfo/ddr_type
4. Download firmware (C33 recommended, minimum C20/21 required) from here:
FirmWares - Google Drive
drive.google.com
5. Go to "Advanced" -> "Enter fastbootd"
6. Execute following commands after opening a command line in the fw directory:
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
7. Flash correct XBL files
* For DDR type 0 (DDR4):
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
* For DDR type 1 (DDR5):
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img
8. Boot your recovery from here and then install the new update:
Android12L - Google Drive
drive.google.com
9. Now, you can update via OTA safely.
IF YOU ARE ON STOCK OOS12
These instructions are for you:
Spoiler
Thanks to @Anierin_Bliss
First Time Install / Clean Flash
1. Have an unlocked bootloader & OOS 12 (C20 - C33) flashed to both slots.
2. Download vbmeta, recovery, ROM and GAPPS (optional) for your device from here: https://drive.google.com/drive/folders/1A2SeD6YFKJ2S-iiAKmyfgnrEeJz8zjNm
3. Reboot to bootloader
4.
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip
7. Format data, reboot to system & Enjoy !

bessss

Installed in the early afternoon,
Everything works perfectly for the moment
Pleased to see aicp on A12.
Good work guys !

great work

Flashed and works super smooth

NICE, love these ROMS.'
my 1+8t updated to 12 about 2wks ago, i know i let that slip thru...will have to backflash to 11 prior to flashing this ROM?
OR could i perform a factory reset and follow prompts to install?
Thanks much,
Richard K

racenrich said:
NICE, love these ROMS.'
my 1+8t updated to 12 about 2wks ago, i know i let that slip thru...will have to backflash to 11 prior to flashing this ROM?
OR could i perform a factory reset and follow prompts to install?
Thanks much,
Richard K
Click to expand...
Click to collapse
You gotta be on the oos11 firmware as a base before you can flash any custom a12 roms on the 8t at the moment.

Thanks for the confirmation, looks like im going backwards before forwards!

racenrich said:
Thanks for the confirmation, looks like im going backwards before forwards!
Click to expand...
Click to collapse
Haha yeah. A bit of a pain.

Hi,
AICP on Oneplus 7T pro for a while and now on Oneplus 8T.
What happiness with this ROM on these 2 phones. No bug discovered yet.
There is only the July patches to receive and everything will be perfect (I am aware that the ROM on 8T is recent and that the developers are doing their best -a big thank you to you-).

Hi! Installed AICP 17.1 (latest)today with MindTheGapps 12.1.0 arm64 and any Google service is not working ie. Contacts, Downloading from store (Stucks at pending...). I came from latest OOS as instructed. I noticed that in Play Store's and Play Serveices' Mobile data & Wifi settings there were Setting "Allow network access" toggled off, but didn't help to turn them on
Tried fresh install without Gapps and other Points of Interest (thse are working in fresh install without gapps):
- Developer options not working
- Opening settings/AICP Extras -> "Not rooted ..." Message
- Android notification bar not expanding
- Mobile data not working
Have I missed something?

vezkari said:
Hi! Installed AICP 17.1 (latest)today with MindTheGapps 12.1.0 arm64 and any Google service is not working ie. Contacts, Downloading from store (Stucks at pending...). I came from latest OOS as instructed. I noticed that in Play Store's and Play Serveices' Mobile data & Wifi settings there were Setting "Allow network access" toggled off, but didn't help to turn them on
Tried fresh install without Gapps and other Points of Interest (thse are working in fresh install without gapps):
- Developer options not working
- Opening settings/AICP Extras -> "Not rooted ..." Message
- Android notification bar not expanding
- Mobile data not working
Have I missed something?
Click to expand...
Click to collapse
I have the same problem. And there is no first setup like adding google account and so on. Phone just boot to system and all is messed up...

Zeezala said:
I have the same problem. And there is no first setup like adding google account and so on. Phone just boot to system and all is messed up...
Click to expand...
Click to collapse
I managed to recover from this with these steps:
1) Flash ROM again without Gapps to get access to Developer options and ADB
2) Download MSM Tool for your device from HERE. I used latest European version.
3) Follow precisely THESE instructions to get stock ROM
+) I installed PixelExperience 12 Recovery and ROM and now working device

vezkari said:
I managed to recover from this with these steps:
1) Flash ROM again without Gapps to get access to Developer options and ADB
2) Download MSM Tool for your device from HERE. I used latest European version.
3) Follow precisely THESE instructions to get stock ROM
+) I installed PixelExperience 12 Recovery and ROM and now working device
Click to expand...
Click to collapse
Ahhhh, ok, thanks. Good job.
I use MSM tool everytime I install new rom. So I think there isn't problem in my case. But another recovery is good point. I will try this in the future. Thanks.

Hi, does this ROM has SafetyNet built-in?
Thanks

Great rom thanks for your great work!
Just a small knit pick...
The font for 5G seems really small compared to LTE. Just wondering if that can be tweaked to match the LTE font size.

The night light feature seems a bit too strong even when set at minimum. Can that be tweaked?

i use signal for sms, etc.
when receiving a txt, i dont get the notification banner pop-ups. upon review of settings, everything is proper, but still no pop-ups.
the issue seems to be described per this link:
Android 12 Beta 4: Most notification banner pop-ups are not appearing due to bug
Google is "moving into the final phase" of Android 12. However, a bug in Android 12 Beta 4 sees most notification banners not pop up...
9to5google.com

Newbie question. I have not flashed a rom in a very long time! I just paid off my T-Mobile OnePlus 8t and want to flash this custom rom. I am just on the stock android 11 software from T-Mobile. I understand how to unlock my bootloader and I should be able to follow the provided instructions in the first post. My question is is there anything else I should know before hand. I only ask cause I jumped the gun on my 7T McLaren and the finger print scanner never worked again! Is that the same with the 8t. Or can I simply follow the above instructions and enjoy the rom? Thanks

[ROM][12.1.0][Bonito/Sargo] Android Ice Cold Project 17.1 [Official]

{
"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-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. 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 17.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
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:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
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 the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
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 how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: 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 perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform 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 lose 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 lose root. Now swipe to flash and reboot afterward.
Using the ROM:
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. 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 on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android S. 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 zip file.
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 is recommended, the lineage recovery is a great alternative however, it will not decrypt the internal storage so you will have to flash the rom with adb sideload or usb OTG or with an external sdcard).
3. Wipe the System (DO NOT WIPE THE SYSTEM ON A/B DEVICES!), Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file (reboot to recovery before flashing anything else if you have an "A/B" device).
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. You can then reboot to recovery and flash the root solution of your choice if you want to, and then boot back to the system.
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 A/B Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 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.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
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.
Open the updater app, download the update, then press install, press reboot when prompted, you will be taken to TWRP, there isn't any need to flash GApps separately
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to 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/AICP/kernel_google_msm-4.9
Device tree source:
https://github.com/AICP/device_google_bonito
Vendor source:
Follow this guide if you want to extract the vendor blobs
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:
@Siluxsept
Information:
ROM OS Version: 12.1
Kernel: Linux 4.9
ROM {Firmware|Vendor} required: 11
Status: STABLE
Release Date: 07-06-2022
You want to see a "normal" night at the "DEV office", click here!!

Reserved

Reserved

Here we goooo

I can't seem to get Visible service to work, APN's can't be edited either. I would assume there is another way to get service working, just need to be pointed to the correct location.
Thanks!
-edit-
enabling DSDS in phone menu got me up and running. weird.

hi. thanks for all your work! quick question, i have a pixel 3a xl. that is an a/b device, right? was reading your instructions and dont wanna mess up. also, if its an a/b device, will this be a clean install if we can't wipe device?

MikeW14 said:
hi. thanks for all your work! quick question, i have a pixel 3a xl. that is an a/b device, right? was reading your instructions and dont wanna mess up. also, if its an a/b device, will this be a clean install if we can't wipe device?
Click to expand...
Click to collapse
Correct, its A/B. Normal data + cache wipe is okay, just don't wipe system partition.

got it. thanks. one more thing....when rooting, would we still do the same process as before, where we patch the boot image and then flash the patched boot image, etc?

MikeW14 said:
got it. thanks. one more thing....when rooting, would we still do the same process as before, where we patch the boot image and then flash the patched boot image, etc?
Click to expand...
Click to collapse
You can simply use Magisk v23 flashable zip - install or sideload from TWRP / LOS recovery.

Siluxsept said:
You can simply use Magisk v23 flashable zip - install or sideload from TWRP / LOS recovery.
Click to expand...
Click to collapse
Tried to sideload that file and got verification failure something about the footer.
While a little more cumbersome I have always found the following to be the most reliable method to root...
download the latest kernel/recovery file
download the latest magisk.apk from github and load on phone
In the magisk app click on install next to the magisk entry
patch the file you just downloaded
move the file to a pc for fastbooting
reboot the phone into bootloader mode
fastboot flash boot the file you just patched
profit

im open to all suggestions. you guys are the experts. im just appreciative for all the work done and time put into making the rom great.

So which firmware do I need? Do I keep A11 or flash A12 first?

JasonB96 said:
So which firmware do I need? Do I keep A11 or flash A12 first?
Click to expand...
Click to collapse
If you never upgraded to 12 stock firmware do it first.

how is battery in this update?

so wait, im currently on aicp 11. can i just DL aicp 12 onto my phone and update, or do i need to install android 12 stock rom stock rom and then install aicp 12 after?

Hey guys, please scratch 12 firmware requirement. Update from 11 to 12 working fine without flashing 12 stock first. Just clean flash latest weekly.

had trouble getting this rooted. it just got stuck in a bootloop (tried it twice).

MikeW14 said:
had trouble getting this rooted. it just got stuck in a bootloop (tried it twice).
Click to expand...
Click to collapse
Hmm initial root works fine for me with Magisk 23 zip file and LOS/AICP recovery. Can you provide more details? Did you sideload from LOS recovery?
Try attached boot image. I just patched it old fashioned for bonito. Should work.

Patching the boot img for root always worked for me. Something about being able to just boot the img to see if it works first before flashing is appealing to me.

esjames said:
Patching the boot img for root always worked for me. Something about being able to just boot the img to see if it works first before flashing is appealing to me.
Click to expand...
Click to collapse
fastboot boot <image name>?

Development [ROM][Unofficial][pdx225][13] Lineage 20 For SONY XPERIA 10IV

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_pdx225
https://github.com/XperiaBrickers-10IV/vendor_sony_murray
https://github.com/XperiaBrickers-10IV/hardware_sony
Current Bugs:
None
Many thanks to:
@clfbbn
@loipuru
@WindowsDev0
@dylanneve1
@Sakuu
Special thanks to
Sony
@jerpelea
For sending me the device

If some moderator could make us a device forum that would be lovely

King081 said:
View attachment 5856369
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
http://GDrive
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
Device Trees will be public soon
Current Bugs:
Sound does not work
screen flickers black
vibration does not work
USB doesn't work in recovery
takes about 3 buttton presses to get out of deep sleep
ENG build so you will get a red border
Many thanks to:
@clfbbn
@lolipuru
@WindowsDev0
@dylanneve1
Click to expand...
Click to collapse
What device is this ROM for?

TheWorldYT said:
What device is this ROM for?
Click to expand...
Click to collapse
pdx225 Xperia 10IV

Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.

litelinux said:
Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.
Click to expand...
Click to collapse
It's not sodp based, it's stock based

Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yeah, don't worry it's my development device, so don't need testers, this is for those that like Trying stuff and mainly to get a forum

Join my telegram group for now https://t.me/Xperia007

King081 said:
It's not sodp based, it's stock based
Click to expand...
Click to collapse
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid

litelinux said:
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid
Click to expand...
Click to collapse
SODP tries to open source all the blobs, while stock based doesn't, due to the difficulty sodp is not really stable compared to stock base

Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yup, it's the closest thing to my previous phone (xz5c) I can fond on the market! Even the outer frame feels similar.

Could Be Anyone said:
I miss the xperia compacts.
Got small hands and the compacts were perfect.
10 IV is all right but I wish the width was smaller, 65mm would be amazing.
I guess I should be thankful it's just 67mm and not 77mm like the newer google pixels
Click to expand...
Click to collapse
Lol me with the Google Pixel 7

Update available
Changelog:
Sound and Mic now working
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR

Update available
Changelog:
Vibration and SDM work so screen does not flicker anymore and does not take 3 button presses to wake display
Current Bugs:
camera
ENG build
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR
it is now a usable device,
device trees will be public today

Device Tree are now public link available on first post

Could Be Anyone said:
Thanks so much.
Will install and provide feedback.
Is there lineageos recovery? I couldn't find one.
Click to expand...
Click to collapse
You'd have to extract the payload.bin file and flash boot vendor_boot and dtbo in fastbootD then reboot to recovery and flash rom.zip

Could Be Anyone said:
Keep getting an error.
E:Signature verification failed
E:error: 21
Install from SD card completed with status 2
Installation aborted
Click to expand...
Click to collapse
That's weird never happened to me before

Could Be Anyone said:
Well that's weird since I followed your instructions to a T.
Could you port lineageos recovery as well? It'll fix this problem since the stock recovery doesn't have the option to bypass signature verification.
Click to expand...
Click to collapse
You didn't listen then, extract ROM zip extract payload.bin, then flash vendor_boot boot and dtbo then reboot to recovery (Los one) then flash rom zip

Could Be Anyone said:
I couldn't find the los recovery on the first page.
Click to expand...
Click to collapse
I just said to extract it

Could Be Anyone said:
Ah, I my bad, I thought it was just a normal zip you meant to install, sorry about that.
Click to expand...
Click to collapse
No worries lol

Database Develop

welcome