Database Info

[Treble][Unofficial]LineageOS 16.0 Treble for Oneplus 3/3T

LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* 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.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
{
"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"
}
-------------
Hello, I'm very excited to tell you that Project Treble is ready to run on our phone. Although it's not stable with always something broken, It's still a nice chance to undergo other ROMs that you want.
Beware that it is only a proof-of-concept try to let everyone know our device is still powerful. They are still well prepared for future Android release. However, the GSIs will never be more stable than device-specific ROMs. This Treble ROM is not suitable for daily use.
The main reason why official LineageOS of our device didn't ship with Project Treble is that we don't have fully binderized camera HALs from Oneplus. If we want to support Treble there must be a lot of compromises.
Things working:
Everything, including camera.
Things not working:
1. [A-only & A/B] SELinux is set to permissive for most GSIs.
Unnecessary and won't fix for now.
2. [A/B] Reboot and stuck at boot animation while GSI installation.
Solution: Use adb for a reboot, don't just hold the power button. After this the system will boot, at least we could get console-ramoops correctly for debugging.
The step-by-step guide on how to treblize your device:
Treble needs a partition called "Vendor", but our device does not have this device. What we need to do is to create a vendor partition by our selves.
I made a custom TWRP Treble build to do this process, here is what you should do in TWRP.
0. Warning
Our device is really old, some users may experience storage failure (Known as CRC failure), please be careful when you treblize your device. If you meet any problem, please check the 9008 unbrick guides in the forum.
1. Flash this TWRP in the download link below.
2. Boot it up and go to "Advanced" -> "Terminal", Type treblize and run.
Treblize is a shell that we could modify our partition. It basically does the same thing as the commands below.
Code:
/sbin/sgdisk --typecode=5:8300 /dev/block/sdf
/sbin/sgdisk --change-name=5:vendor /dev/block/sdf
3. Reboot your phone to your current system to check if there is storage failure.
It's very important. Some of the users report it may cause storage broken. You'd better check it first before flashing LOS Treble.
4. Reboot your phone to TWRP.
5. Flash LOS Treble in the download link below.
After these processes, you have got a treblized Oneplus3. Boot it up to check if everything works, or just trying other GSIs anyway.
The step-by-step guide on how to flash GSIs:
0. Treblize.
1. Choose and flash LOS Treble solution first for the vendor partition.
Because of the supporting of system-as-root for our device, you can now use every GSIs if possible. I personally recommend the system-as-root solution for future android standards, although they are basically the same some old recovery install scripts may be broken like opengapps will not working anymore according to the report.
2. Flash A-only or A/B GSI image according to the flag in the download section.
3. Wipe data.
Q&A:
1. Q: What are the limitations to our devices?
A: Sizes. Our device has 3154116608 bytes or 3.15G of system storage. Some GSIs may be larger than our device and due to TWRP's bug it won't be recognized. Here is a guide for linux users to make self modified GSIs images of smaller size.
Code:
sudo simg2img <system.img> system.ext4.img
sudo mount -t ext4 -o loop system.ext4.img system/
sudo chown -R <username>:<username> system/
#then enter the system/app folder and remove gmail, maps, google play music, drive, etc.
makeext4fs -T 0 filecontexts -l 3154116608 -L system -system -s flash.img system/
2. Q: Something is broken in some GSIs!
A: That may or may not be our device's fault.
3. Q: Can I install other third-party kernels?
A: You need to make sure that kernel supports mounting vendor partition, or it will brick your device.
Also, the device now is supporting system-as-root, which requires new kernel patchs. Kernels claimed that for treble previously may not work anymore.
4. Q: How to revert my treblized device?
A: Unnecessary. But you can do it yourself with the sgdisk command-line tool, or just use the 9008 tool if you are lazy.
5: Q: How do I install a non-treble ROM with my "treblized" device?
A: As normal. They won't affect each other.
Thanks:
dianlujitao and other LOS devs for current device tree
XiNGRZ for op5 treblize reference
a lot of testers
Chat Group:
https://t.me/joinchat/BrAZb0Zf9p3q7Qz_No5AUA
Join the chat group for sGSI QPR6 guide and more!
Downloads:
[New][A/B] LineageOS 16.0 Treble system-as-root: https://mega.nz/#F!UgdQRYSD!8s-_u2HJQZDEqNnFOnejxQ
[Old][A-only] LineageOS 16.0 Treble: https://mega.nz/#F!A0VmQAaC!Mc3HYZgAkxeoQwGkZyJvwg
[Deprcated][A-only] LineageOS 15.1 Treble: https://androidfilehost.com/?w=files&flid=280568
XDA:DevDB Information
LineageOS Treble, ROM for the OnePlus 3
Contributors
simonsmh, dianlujitao, chenxingyu,
Source Code: https://github.com/OP3Treble
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: OxygenOS/H2OS 9.0.x
Based On: LineageOS
Version Information
Status: Alpha
Created 2018-08-17
Last Updated 2019-08-27

Short update logs.
20190826:
Support system-as-root, flash A/B GSIs instead of A-only.
thanks to zuk-devs
20190731:
Camera fixed in Q

Reserved

Awesome work. Long live 3/3T.

Is this Android pie or Oreo? Title says 15.1

MarcoLK said:
Is this Android pie or Oreo? Title says 15.1
Click to expand...
Click to collapse
U can flash any GSI either pie or Oreo. Camera and volte is broken on pie

Good work guys, I think I'll wait for the camera issue to be fixed before risking to brick my device though

After flashing gsi system img how to make it boot ?I tried , but failed. But booted in my redmi note 4x both gsi and sGSI.

Wow.. Thanks:good:
Sent from my OnePlus3T using XDA Labs

This is incredibly exciting! I hope this also inspires OnePlus to release official treble support.
Before i dare to flash this i would like to know, what is the rollback plan for this if you want to bring the device back to factory state and does it break compatibility with for example the stock rom and stock recovery?
For those that already jumped ship and installed a GSI image, can you test if one of the following mods works?
Arnova v8.2 https://www.celsoazevedo.com/files/android/google-camera/f/GoogleCamera-Pixel2Mod-Arnova8G2-V8.2.apk
Tolyan v1.0.7 https://www.celsoazevedo.com/files/...f/MGC_5.3.015_B-S-G-based_v.1.0.7_TlnNeun.apk
Skulshady https://www.celsoazevedo.com/files/android/google-camera/f/skulshady_gcam_5.1.018_Mod_v6_fix.apk
These are various modded APK's that may contain a fix for the camera issues. No root required to flash.

henk717 said:
This is incredibly exciting! I hope this also inspires OnePlus to release official treble support.
Before i dare to flash this i would like to know, what is the rollback plan for this if you want to bring the device back to factory state and does it break compatibility with for example the stock rom and stock recovery?
Click to expand...
Click to collapse
You don't need to roll back. Just like op5, it's still working if oneplus offer us official treble support.
At least you can either modify the partition label or use 9008 tools to return stock.

Great news.
Hope fixes in future

drmuruga said:
After flashing gsi system img how to make it boot ?I tried , but failed. But booted in my redmi note 4x both gsi and sGSI.
Click to expand...
Click to collapse
What GSI did you try to flash.
---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------
henk717 said:
This is incredibly exciting! I hope this also inspires OnePlus to release official treble support.
Before i dare to flash this i would like to know, what is the rollback plan for this if you want to bring the device back to factory state and does it break compatibility with for example the stock rom and stock recovery?
For those that already jumped ship and installed a GSI image, can you test if one of the following mods works?
Arnova v8.2 https://www.celsoazevedo.com/files/android/google-camera/f/GoogleCamera-Pixel2Mod-Arnova8G2-V8.2.apk
Tolyan v1.0.7 https://www.celsoazevedo.com/files/...f/MGC_5.3.015_B-S-G-based_v.1.0.7_TlnNeun.apk
Skulshady https://www.celsoazevedo.com/files/android/google-camera/f/skulshady_gcam_5.1.018_Mod_v6_fix.apk
These are various modded APK's that may contain a fix for the camera issues. No root required to flash.
Click to expand...
Click to collapse
No, the camera does not work at all.

Does re-partitioning involve internal storage/data partition data loss?
Edit: P.S.: Could I suggest to open a dedicated thread for TWRP Treble as a guide for making our device treble-enabled? I think it could be useful and clearer.

edoardotavecchio said:
Does re-partitioning involve internal storage/data partition data loss?
Edit: P.S.: Could I suggest to open a dedicated thread for TWRP Treble as a guide for making our device treble-enabled? I think it could be useful and clearer.
Click to expand...
Click to collapse
Basically it won't. But formating /data is still suggested to avoid some problems.

Wow, excellent!
Was waiting for this since so long.
Amazing work.
Gonna try it out soon.
Some questions though,
Can I use any of the GSI or I'll have to use provided lineage GSI only?
If I want to use an android pie GSI, then which gapps should I use? I need full gapps.
Also, The camera isn't even working in third party applications such as WhatsApp also?
Which 9.0 GSI is good, is there any AOSP GSI?
Are there any other bugs?
Final thing, can someone please provide me the link for the thread for oneplus3t where 9008 unbrick recovery procedure is there?

You can use any GSI but when i tried android pie GSI wifi dont work and 4G was broken and camera was not working

MODERATOR NOTICE: YOUTUBE LINK REMOVED
From watching this video, I guess that Lineage stock camera app doesn't work, but others do, correct?

xpissio said:
From watching this video, I guess that Lineage stock camera app doesn't work, but others do, correct?
Click to expand...
Click to collapse
Yes. And camera works only on Oreo GSI's and not on pie yet.

[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO]

{
"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"
}
DISCLAIMER:​
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
INFORMATION:​
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing or rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Read more about TWRP here: https://twrp.me/about/​
NOTE : ​
This build of TWRP is based on the kernel source code and no prebuilt kernel was used for building. Because, it is the first build, testers are very welcome for providing feedback regarding the build. ​
CHANGELOG (3.2.3.0) :​
WHAT'S NEW?
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files​
CHANGELOG (3.3.0.0) :​
WHAT'S NEW?
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)​
* Also, there was a major bug with the previous build which prevented the flashing of any file because of the "digest-verification" has been fixed with this release. Enjoy!
CHANGELOG (3.3.1-0) :
WHAT'S NEW?
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff​
DOWNLOAD :​
You can download the latest build of the TWRP from the official site here:​
TWRP(Official)​
BUGS:​
Encryption (for MIUI)
INSTRUCTIONS :​
Download the recovery image and place it in some folder on your desktop and open the Terminal/Command Prompt/Powershell in the said folder.
Connect your device to the PC and boot into the fastboot mode using H/W keys or by typing :
Code:
adb reboot bootloader
Now, type :
Code:
fastboot flash recovery twrp-3.3.0-0-violet.img
OR,
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
Download the recovery image from the link.
Reboot to TWRP.
Hit Install and tap the "Images..." button in the lower right
Browse to the location of the TWRP image on your device and select it.
Select recovery from the partition list and swipe to flash.
For users who are running MIUI : ​
Thanks to Snehashis Sarkar for a short tutorial.
Your data will get wiped before flashing the recovery so take a backup of the internal storage.
Reboot to fastboot.
Wipe the Userdata via fastboot.
Flash this recovery.
Boot into the recovery and format the data (just format it, don't go for the "advanced wipe" section .
Flash this image file: Patched fstab + vbmeta + thermal configs for better performance
Reboot and enjoy.
CREDITS: ​
TwrpBuilder for trees​
Kernel Source : ​
Link: android_kernel_xiaomi_sm6150
XDA:DevDB Information
[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO], Tool/Utility for the Xiaomi Redmi Note 7 Pro
Contributors
Doomsday101
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-11
Current Beta Version: 3.3.0-0
Beta Release Date: 2019-04-03
Created 2019-04-02
Last Updated 2019-05-23

Reserved

Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.

Thank you for your build !
Do you know if someone started to work on porting ROMs ?

diamantik said:
Thank you for your build !
Do you know if someone started to work on porting ROM's ?
Click to expand...
Click to collapse
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.

Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Can you send me the logcat of the kmsg file present in the /proc directory using adb shell when the twrp is stuck on bootlogo?

Doomsday101 said:
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.
Click to expand...
Click to collapse
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive

diamantik said:
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive
Click to expand...
Click to collapse
Sure thing ?

It will boot, try fastboot erase userdata, but you can't flash any ROM (MIUI) atm, as it has encryption bug, which needs to be fixed by the OP!
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse

Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw

moriyaprateek said:
Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw
Click to expand...
Click to collapse
The recovery has the encryption bug atm as stated by @talk2indrajit in the last post. So, you will have to erase userdata via fastboot first. I suggest you take a backup, get rid of Miui and continue with the said process and flash the newly built LOS16 by @Dyneteve (if you seek to flash a custom ROM).

Can anyone update the twrp to 3.0.3?

Not able to flash vbmeta.img fastboot mode..
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..

Aj51 said:
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..
Click to expand...
Click to collapse
Download latest adb from here
https://developer.android.com/studio/releases/platform-tools

When can it decrypt /data?

Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Same problem happen with me

kishangupta009 said:
Same problem happen with me
Click to expand...
Click to collapse
Don't use this command, it was mentioned somewhere, it doesn't work for now, you need to flash it , fastboot flash recovery recname.img.

Guys this TWRP is not working , gets stuck at TWRP logo !
Try the another : https://forum.xda-developers.com/re...ficial-3-2-3-redmi-note-6-pro-violet-t3912400

ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.

kuhru said:
ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.
Click to expand...
Click to collapse
Thank you for trying it out previously. I have released a new build today with the latest TWRP version (3.3.0.0) and now the "digest-verification" bug has been fixed.

[DISCONTINUED][ROM][UNOFFICIAL][20210205] Pixel Experience Eleven for Xperia 5 II

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in 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.
*/
NOTICE:
This is the last update before i sold this phone.
[Please make sure you updated to 58.1.X (Which is Android11)]
From PE.
+ Plus Edition
+ Bluetooth SBC Dual Channel
+ Improved unlocking animations
+ Face unlock
+ March Security Patch
From Me.
+ R vendor Based
+ Assistant key fixed
+ Camera key fixed
+ 5Ghz hotspot support
About Pixel Experience
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Based on Android 11.0
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 11 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5. If you came from SODP ROMs, you need to go back to official Android 11 firmware, and boot into launcher.
6. Please make sure you are using Android 11 Stock ROM [Version > 58.1.X] before flash this.
7. Still in developing. May have some unexpected bugs.
Downloads Links:
PEP is uploading. ETA One Day.
PixelExperience_pdx206-11.0-20210205-1222-BETA-UNOFFICIAL
Unofficial-build: Link (MEGA)
Looking For CinemaPro And PhotoPro:
Click Here
Flashing and updating:
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot_a boot.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot erase metadata
fastboot flash system_a system.img
fastboot flash product_a product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Already included
Root access:
Flash Magisk in recovery.
SD CARD Notice:
Format you sdcard into 'FAT32' if your sdcard can NOT be use in this system
Issues and reports:
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Bugs:
LDAC (Not sure)
FP Not working in Third Apps
Also thanks to:
BBN Shion Sjll
nezorflame (This build won`t come out so fast without his server)
The Pixel Experience Team
Source:
Kernel Source
Device vendor
Device Tree
Feel free to donate me:
Paypal
Screenshots:
{
"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"
}

Does this mean PE recovery is available for us as well? Also thanks for building all these!

Does SD card work fine on this rom? It looks like the other two LineageOS roms have problems.

Think im gonna nut. Thank you so much OP

Boots up and runs like a dream. I used the .51 boot images and was on it before flashing

magisk patched from .51 works for magisk without having to use TWRP. Works great! Does anyone know if we can port Side Sense over to this ROM?

The only bug Ive found is that if you rotate the device to landscape, it doesnt want to rotate back to portrait without turning the screen on and off

eqbirvin said:
The only bug Ive found is that if you rotate the device to landscape, it doesnt want to rotate back to portrait without turning the screen on and off
Click to expand...
Click to collapse
Maybe it's the PE problem.
But mine is fine.

ken442266 said:
Downloads Links:
PixelExperience_pdx206-11.0-20210126-0818-BETA-UNOFFICIAL
Click to expand...
Click to collapse
I am using daily the previous build for 3 days and its PERFECT bro thank you so much. Viper4android works, battery life slightly better than stock, no bugs or issues and the most important: It fixed my proximity sensor issues. It started "blinking" about a month ago, making calls and listening to voice messages very annoying (screen would be blinking randomly). After I flashed the stock 11 version and it wasnt fixed, I was sure it was a hardware issue with many reports of it being faulty on 5 ii and 1 ii on forums and reddit, but now I suspect its a combination of proximity/light sensor calibration. The automatic brightness on your rom works much better than stock and I suspect the proximity sensor uses the light sensor at the same time. I tried all root solutions on the market claiming to recalibrate the sensor but no luck. Now its working as intended with your rom!
Is it safe to dirty flash the updated version? Will I need to wipe data?
Thanks again for single handedly creating so many ROMs for the best phone (in hardware) in the market. I was really considering to sell my 5ii because of the issues and software bugs, but now I have hope again it will be great using Lineage/Pixel Experience.

ken442266 said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in 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.
*/
About Pixel Experience
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Based on Android 11.0
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 10 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5. If you came from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
6. YOU MUST USE Q VENDOR in order to be able to boot.
7. Still in developing. May have some unexpected bugs.
Changelog:
Downloads Links:
PixelExperience_pdx206-11.0-20210126-0818-BETA-UNOFFICIAL
Unofficial-build: Link (AFH)
Looking For CinemaPro And PhotoPro:
Click Here
Flashing and updating:
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot_a boot.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot erase metadata
fastboot flash system_a system.img
fastboot flash product_a product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Already included
Root access:
Flash Magisk in recovery.
SD CARD Notice:
If your SD card can NOT use in this system
Just format it into 'FAT32' (On PC)
It will works
DO NOT format by android
(Android will format it into 'ExFat' and seems to be some 'reading' issue)
Issues and reports:
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Bugs:
LDAC (Not sure)
Also thanks to:
BBN Shion Sjll
The Pixel Experience Team
Source:
Kernel Source
Device vendor
Device Tree
Feel free to donate me:
Paypal
Screenshots:
View attachment 5194965View attachment 5194967View attachment 5194969
Click to expand...
Click to collapse
I can confirm LDAC is NOT working currently, It doesn't broadcast song information to my car stereo when hooked to bluetooth.

Flashed my device with latest build and works great. No flaws and runs smoothly. Thanks for your great job. Awesome!!!

RODJAN71 said:
Flashed my device with latest build and works great. No flaws and runs smoothly. Thanks for your great job. Awesome!!!
Click to expand...
Click to collapse
Hello! Is it possible to reduce haptic feedback (touch vibration) with this rom? Can you please check?

schjor said:
Hello! Is it possible to reduce haptic feedback (touch vibration) with this rom? Can you please check?
Click to expand...
Click to collapse
No, it is not possible. It just have the option to enable/disable touch vibration but not the chance to reduce vibration when enabled.

two minor issues.
1) nowhere to disable one sim card out of the two.
2) there is no option for 5GHz in the settings of hotspot.
overall it runs smoothly. thank you!

Would really love to use this officially from the PE server without having to flash odm. How did you get the stock camera as well @ken442266 ? I thought there is only paclages to flash for photo pro and cinema pro? Could you maybe link a working version of the normals stock cam as well? Would really appreciate that? Also, is safetynet working?
It would also be great to have exfat support since that is just a few kernel tweaks

churchner420 said:
Would really love to use this officially from the PE server without having to flash odm. How did you get the stock camera as well @ken442266 ? I thought there is only paclages to flash for photo pro and cinema pro? Could you maybe link a working version of the normals stock cam as well? Would really appreciate that? Also, is safetynet working?
It would also be great to have exfat support since that is just a few kernel tweaks
Click to expand...
Click to collapse
All camera needs some hack to make it work. And I will post a stock camera next month when I update PE, Along with R photo pro && cinema pro .And about the exfat problem have to wait for official to release the kernel source.

ken442266 said:
All camera needs some hack to make it work. And I will post a stock camera next month when I update PE, Along with R photo pro && cinema pro .And about the exfat problem have to wait for official to release the kernel source.
Click to expand...
Click to collapse
Hey man thanks for your reply
That is nice, so this will become official without SODP base? Would really love to see that happen.
Does safetynet work on this ROM to install Netflix and Google Pay and stuff like that? And how is the battery life @120hz compared to stock @120hz?
Sorry for asking that much but I am really interested in this ROM and appreciate your hard work on it
And I am really looking forward to stock Dolby Atmos thanks for implementing that as well
One last one: is 21w fast charging supported and if H.S. is on board as well are you going to implement the Game Enhancer too and how is the camera performance with the stock apps compared to the stock ROM itself?

churchner420 said:
Hey man thanks for your reply
That is nice, so this will become official without SODP base? Would really love to see that happen.
Does safetynet work on this ROM to install Netflix and Google Pay and stuff like that? And how is the battery life @120hz compared to stock @120hz?
Sorry for asking that much but I am really interested in this ROM and appreciate your hard work on it
And I am really looking forward to stock Dolby Atmos thanks for implementing that as well
One last one: is 21w fast charging supported and if H.S. is on board as well are you going to implement the Game Enhancer too and how is the camera performance with the stock apps compared to the stock ROM itself?
Click to expand...
Click to collapse
It will always be UNOFFICIAL. I'm still a student and will have less time to update it when I go to school. And about safetynet . idk. Cause I don't use it. battery life is fine (60hz up to 10h screen on time, Which is same as stock based on my usage). Everything you expect is almost the same as stock.

churchner420 said:
Hey man thanks for your reply
That is nice, so this will become official without SODP base? Would really love to see that happen.
Does safetynet work on this ROM to install Netflix and Google Pay and stuff like that? And how is the battery life @120hz compared to stock @120hz?
Sorry for asking that much but I am really interested in this ROM and appreciate your hard work on it
And I am really looking forward to stock Dolby Atmos thanks for implementing that as well
One last one: is 21w fast charging supported and if H.S. is on board as well are you going to implement the Game Enhancer too and how is the camera performance with the stock apps compared to the stock ROM itself?
Click to expand...
Click to collapse
btw. only H.S in game enhancer can be using in the rom.

ken442266 said:
It will always be UNOFFICIAL. I'm still a student and will have less time to update it when I go to school. And about safetynet . idk. Cause I don't use it. battery life is fine (60hz up to 10h screen on time, Which is same as stock based on my usage). Everything you expect is almost the same as stock.
Click to expand...
Click to collapse
All of that is really great to hear, thanks a lot. If you have not touched anything sfetynet related the nit will very likely not work since it has to be fixed manually. That should not be too hard and if you like and have got the time some day you can have a look into it

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

{
"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
Whole Android 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:
AICP/device_oneplus_instantnoodle
Device tree for OnePlus 8. Contribute to AICP/device_oneplus_instantnoodle 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 !

Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?

adsxlnc said:
Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?
Click to expand...
Click to collapse
We are preparing OOS 12 based trees. Till then, yes - please go back to latest OOS 11 then flash AICP. 12.1

What a pleasant surprise, love your work semdoc, can't wait to get home and flash this.

Wow great rom, I was looking for one with the built in adblock and no gapps. Fast, smooth, and very light weight. I also love the custom work you did on the QS <3

Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.

Issilar said:
Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.
Click to expand...
Click to collapse
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened

Hiya! I've turned on the always-on display, and have noticed that i have to turn the screen on to get the fingerprint sensor to work (most of the time. I think it's active a few seconds after screen lock?)! Is there any way around this? OxygenOS seemed to turn the sensor on with a finger press no matter the AOD state
cheers!

Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?

ditomathew said:
Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?
Click to expand...
Click to collapse
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation

RogueVisual said:
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation
Click to expand...
Click to collapse
Thanks I did that, and now I reinstalled.

allen-evan said:
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened
Click to expand...
Click to collapse
Nameless works just fine on my device, TMO OP8

Small but IMPORTANT note for anybody experiencing issues coming from OOS and trying this for the first time. I could not get the ROM to boot until I flashed the "copy partitions" zip from Lineage. (https://wiki.lineageos.org/devices/...suring-all-firmware-partitions-are-consistent).
Until I flashed this I would install the ROM and then try to reboot to recovery and it would go straight to the bootloader. If I switched back to the other slot I could get back to recovery but could not proceed further.
So my install instructions looked like this: (because I was doing some trial and error I had installed the ROM a few times hence it being here twice)
adb sideload ROM.zip (I believe you can skip this one but cannot say for certain) -> adb sideload copy-partitions.zip -> adb sideload ROM.zip -> reboot to recovery -> adb sideload GAPPS.zip -> reboot to system
If you get stuck on the bootloader you can use fastboot to check your active slot and then switch back to the previous slot to get back into recovery.
Check current slot:
Code:
fastboot getvar all
Look for the line that says:
Code:
(bootloader) current-slot
The two options are "a" or "b". Then switch to the other slot with:
Code:
fastboot --set-active=a
OR
Code:
fastboot --set-active=b
Another small note, "Apply Update > Install from ADB" (terms are from memory, should be close enough) inside of the Lineage Recovery is what you are looking for to enter adb sideload mode. I had used TWRP previously and didn't know how to get this working at first in Lineage Recovery.

is it possible
to install with official twrp recovery ??

Does this rom works with OnePlus 8 Verizon 5G UW (IN2019)? Does the SIM work?

I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.

graycorgi said:
I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.
Click to expand...
Click to collapse
ROM {Firmware|Vendor} required: Latest OOS 11

Larkin24 said:
ROM {Firmware|Vendor} required: Latest OOS 11
Click to expand...
Click to collapse
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.

graycorgi said:
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.
Click to expand...
Click to collapse
SORRY NO OOS 11
I have the same phone OOS 11 Firmware.
Latest tmoble Firmware
OnePlus Updates Tracker
An automated channel that tracks OnePlus Oxygen and Hydrogen OS ROMs releases. https://github.com/androidtrackers/oneplus-updates-tracker More automated channels that you may like: @yshalsager_projects Developed by: @yshalsager
t.me

[ROM][UNOFFICIAL][13] LineageOS 20 for Xperia X Compact

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in 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.
*/
About LineageOS
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 organization.​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.​​Official LineageOS website : http://lineageos.org​About LineageOS Legal : http://lineageos.org/legal​
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.​2. This ROM does not intended to support Google Camera, but you can try to play with some mods.​
About FDE and FBE​Full-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).​​FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.​​To make it a bit clear:​- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.​- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the same​​Moreover, to work with new encryption you need a recovery with appropriate support.​​Downloads Links
LineageOS 20:​Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/kugo​​Google Applications (optional):​MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)​XDA post about GApps: https://xda-developers.com/download-google-apps-gapps​​Recommended Recovery (optional):​TWRP 3.x: https://forum.xda-developers.com/-/-t3793837​
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.​​LineageOS clean install:​
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:​
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)​
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956​
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta

FEATURES AND ISSUES
Boot: Ok
Bluetooth: Unknown
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Unknown
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing

It's amazing bro, i can't bealive my device got A13

It seems the device is working again - post removed

soomon said:
I installed this system, and at the 2nd reboot my phone is dead. completely dead. seems it has been bricked before I even could log into my google account.
It doesnt even react to power any more.
Of course the phone is old and wasnt used for a long time, so I dont know if it got bricked by the OS or the hardware.
but it's dead.
be careful people!
Click to expand...
Click to collapse
It's almost impossible to brick this device completely just by ROM, unless you're doing something very unusual or developer-related.
This ROM has been tested by user for more than two weeks and everything was fine. It also been tested by Xperia X users since March, there was nothing like that either... and there never was actually.
Anyway, there is no specific in your message, except "It doesnt even react to power any more". Try to get adb/fastboot modes, charge or flash stock firmware. If no luck, I'm pretty sure it's a hardware issue, probably battery or something else.

I was also thinking about this and it was hard for me to believe the custom OS could actually damage the hardware.
I am happy to report it seems to be the device itself that caused the issue and not the rom. Today it was working Since it is an old device I'm assuming it was a hardware issue, so I deleted my old post.
It's working perfectly now. thank you so much!

I'll install this asap. Cant belive that this device is live again. Im using it as main phone. Gonna post my experience with rom here. Cheers
Edit: Cant seems to make it work . i was on latest stock, did full wipe , installed clean los20 , no gapps no additional zipps . it goes past sony logo shows black screen and immediately restarts on that black screen . Any suggestions ?
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?

After install this rom i found bugs on this rom A13 LOS 20:
-WIFI
-HOTSPOT
-TAP TO WAKE NOT WORK
- GPS can't lock
- NFC
Edit : after reinstall from Lineage 19 to Lineage 20 , Wifi , hotspot , Gps , working fine
Thanks for @Chippa_a and team , share and build rom for x compact

Deep sleep pretty good , keep it up

shandu98 said:
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
Click to expand...
Click to collapse
Do you have the latest TWRP offered on the other thread? If you get a boot loop back into TWRP you can try tapping restart to system which is an option within TWRP. If you still have problems after with a boot loop try a clean install by wiping dalvik, cache, system, internal storage, followed by formatting data, then reboot to TWRP flash the build and tap restart to system when finished.

my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo

Tri Akbar Fitriana said:
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Click to expand...
Click to collapse
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.

Asta01 said:
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Click to expand...
Click to collapse
if I flash it to stockrom, does it need a TA file? because my TA file is missing.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
I flash Stockrom with flashtool. I dont need TA file.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
No.
Try lineage recovery it works for me, with twrp i get black screen

Chippa_a said:
Moreover, to work with new encryption you need a recovery with appropriate support.
Click to expand...
Click to collapse
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!

Chippa_a said:
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Click to expand...
Click to collapse
Thanks,with twrp 3.7.0_12 is twrp working.

Thank you chippa _a. The rom is amazing. I haven't found any bugs so far, and it's incredibly fast. A new life for the Xperia x compact. Thanks alot.

Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because my phone is rooted, is there a solution for that?

SietZ said:
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because NY phone is rooted, is there a solution for that?
Click to expand...
Click to collapse
For me is Google cam port "MGC_8.2.204_Parrot043_V1" working perfect.