Database Develop

[OFFICIAL] LineageOS 15.1 for ZTE Axon 7

{
"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"
}
Lineage OS​About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Any failure in this process could lead to an unrecoverable bricked device.
Instructions:
Attention! The bootloader needs to be unlocked!
1. Install the Universal O bootloader and your model specific modem. Download
2. Update your version of TWRP. Download
3. Perform a backup of your current ROM. (optional)
4. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
5. Install the ROM. Download or Download Unofficial builds
6. Install GApps. (optional) [Recommended -> Open GApps (arm64) (8.1)]
7. Reboot.
What is CAF?
Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Credits:
@Unjustified Dev
@DrakenFX
XDA:DevDB Information
[OFFICIAL] LineageOS 15.1 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
OrdenKrieger, Unjustified Dev, DrakenFX, tdm
Source Code: https://github.com/LineageOS/android_kernel_zte_msm8996/tree/lineage-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: O bootloader + region modem
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-06-05
Last Updated 2018-10-14

Reserved
If anyone gets the red warning at the start, this over TWRP or with adb debugging enabled, should fix it. This is also only needs to be done once.
Code:
[COLOR="Red"]THIS MAY WIPE YOUR DATA![/COLOR]
adb reboot "dm-verity enforcing"
* Alternative you can short/once press the power button to continue the boot process.

Holy moly, this comes out of nowhere, is this fantasy

omg. ♥

This supports dual Sim?
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
OrdenKrieger said:
If anyone gets the red warning at the start, this over TWRP or with adb debugging enabled, should fix it. This is also only needs to be done once.
Code:
[COLOR="Red"]WARNING THIS MAY WIPE YOUR DATA![/COLOR]
adb reboot "dm-verity enforcing"
Click to expand...
Click to collapse
Do not get how you do this over TWRP?

Raffikie said:
This supports dual Sim?
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
Do not get how you do this over TWRP?
Click to expand...
Click to collapse
Open an adb terminal on your pc, connect an usb cable and paste
Code:
adb reboot "dm-verity enforcing"
Dual sim should work but I couldn't test since I only use 1 sim card.

Maybe in Terminal in TWRP

Hille2001 said:
Maybe in Terminal in TWRP
Click to expand...
Click to collapse
That would be just
Code:
reboot "dm-verity enforcing"

Don't know why but my phone just bricked after flashing this. I flashed it the same way like I did with all Oreo roms. My steps:
_Wipe data/system/cache/dalvik.
_Flash the Universal bootloader and A2017G modem from the link in OP.
_Flash Lineage OS 15.1
_Flash micro Gapps
_Wipe dalvik/cache
_Reboot
My phone stuck at the screen saying that my device is corrupted, I cannot boot back into TWRP also. Any idea ?
*Edit: I got it back to TWRP, will try again

ortolan said:
Don't know why but my phone just bricked after flashing this. I flashed it the same way like I did with all Oreo roms. My steps:
_Wipe data/system/cache/dalvik.
_Flash the Universal bootloader and A2017G modem from the link in OP.
_Flash Lineage OS 15.1
_Flash micro Gapps
_Wipe dalvik/cache
_Reboot
My phone stuck at the screen saying that my device is corrupted, I cannot boot back into TWRP also. Any idea ?
*Edit: I got it back to TWRP, will try again
Click to expand...
Click to collapse
This over pc adb terminal
Code:
adb reboot "dm-verity enforcing"
or this inside of TWRP
Code:
reboot "dm-verity enforcing"

OrdenKrieger said:
If anyone gets the red warning at the start, this over TWRP or with adb debugging enabled, should fix it. This is also only needs to be done once.
Code:
[COLOR="Red"]WARNING THIS MAY WIPE YOUR DATA![/COLOR]
adb reboot "dm-verity enforcing"
Click to expand...
Click to collapse
Is there an instance where this has to be applied again? If you reinstall the bootloader, for example?

Cablespider said:
Is there an instance where this has to be applied again? If you reinstall the bootloader, for example?
Click to expand...
Click to collapse
Probably or if you install stock again, I think that will be enabled again, but any other ROM shouldn't touch that state.

The "in call audio/speakerphone" bug has been fixed by the way, if anyone wonders.

I have flashed it successfully and am running it now. I will add all my apps and what not and see how it goes.

Really excited for your experiences with this ROM and if you would prefer it over the ZTE Oreo Beta by Nfound in case some.of you are running that rn. ?

Can someone tell me if HDR+ on the modded Google cam works or not? Also the AKM DAC?

Hi I have a2017 Chinese model running v3.0b11, MiFavor 5.2 should I still install the Universal bootloader and modem to be on the safe side

jungle35 said:
Can someone tell me if HDR+ on the modded Google cam works or not? Also the AKM DAC?
Click to expand...
Click to collapse
HDR+ works and the DAC always worked in headphone use case. Even on 14.1.

FuzzyDunlop9 said:
Hi I have a2017 Chinese model running v3.0b11, MiFavor 5.2 should I still install the Universal bootloader and modem to be on the safe side
Click to expand...
Click to collapse
Yes.

So I was having FC issues with just the Google App. I downloaded Gapps again and reinstalled Gapps. Now I get stuck at the LOS boot animation. I am trying to get back into TWRP but I am not sure of the key combo since the whole "press the power key in 30secs" thing at the bootloader screen. Thank you.
-EDIT-
Got back into TWRP. I hit the volume keys after the power button message. Then I picked recovery from the bootloader menu. Then I have to hit the power button on the next go around and it goes into TWRP.

[RECOVERY][RMX1971][UNOFFICIAL] TWRP 3.3.x for Realme 5 Pro / Realme Q

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- Sdcard works
Download:
TWRP
To Flash the TWRP:
Code:
fastboot flash recovery twrp-RMX1971-20191017.img
Then reboot in TWRP manually.
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/thesprintster/device_realme_RMX1971/commits/android-9.0
Precompiled Stock Kernel in use
Credits:
Thanks to other testers for the tests and the support
Created 2019-10-17
{
"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"
}
XDA:DevDB Information
[RECOVERY][3.3.1-14][RMX1971]Unofficial TWRP for Realme 5 Pro (Stable), Tool/Utility for the Realme 5 Pro
Contributors
thesprintster, mauronofrio
Source Code: https://github.com/thesprintster/device_realme_RMX1971/commits/android-9.0
Version Information
Status: Stable
Created 2019-10-17
Last Updated 2019-10-17

Reserved

Why is there 3.3.1-9 in the download and 3.3.1-14 in the title? Did you share accidentally an older version or mistake in title?

greenys' said:
Why is there 3.3.1-9 in the download and 3.3.1-14 in the title? Did you share accidentally an older version or mistake in title?
Click to expand...
Click to collapse
mistake in title

thesprintster said:
mistake in title
Click to expand...
Click to collapse
Ah, I see. Thank you.
Edit.: You accidentally edited the title wrong. Noe it's 3.3.1-19 instead of 3.3.1-9.

Thanks dev for recovery. My phone has been trapped in bootloop after flashing magisk 20.0 . I have twrp back-up in my sd card and I'm restoring backup again. I was flashing to install titanium plus and vanced YouTube

Amot00 said:
Thanks dev for recovery. My phone has been trapped in bootloop after flashing magisk 20.0 . I have twrp back-up in my sd card and I'm restoring backup again. I was flashing to install titanium plus and vanced YouTube
Click to expand...
Click to collapse
How did you flash magisk? I mean first you gotta unlock bootloader. Did you successfully use in-depth test.

will try it soon..
On screen shot its lineage os.. ?

How to unlock the bootloader on Realme 5 Pro?
I mean there's no any tutorial to unlock it yet.. I found some tutorials on google but it doesn't look trusted..
Mustn't we unlock it first then eventually can install twrp ?

jijoejoe123 said:
will try it soon..
On screen shot its lineage os.. ?
Click to expand...
Click to collapse
Yes! I definitely need it!

New build guyz, fixed external sd card mounting. Link in 1st post.

Aizenmas said:
How to unlock the bootloader on Realme 5 Pro?
I mean there's no any tutorial to unlock it yet.. I found some tutorials on google but it doesn't look trusted..
Mustn't we unlock it first then eventually can install twrp ?
Click to expand...
Click to collapse
Go through : https://www.youtube.com/watch?v=FyEEmaaQZh8

Finally , a good news

Failed backup system image (size 5GB).. how to do?

thesprintster said:
New build guyz, fixed external sd card mounting. Link in 1st post.
View attachment 4847759
Click to expand...
Click to collapse
After bootloader unlock and following instructions it says failed to mount system_root and can't flash anything. Especially not lineage os, opengapps and magisk.

greenys' said:
After bootloader unlock and following instructions it says failed to mount system_root and can't flash anything. Especially not lineage os, opengapps and magisk.
Click to expand...
Click to collapse
Yes, this twrp is junk
i can not flash rom lg16 or stock rom ( stock rom convert opzip to zip) ,devices bug mount system_root

I got bootloop after install Rom Lineage, how to fix it?

29y6145 said:
Yes, this twrp is junk
i can not flash rom lg16 or stock rom ( stock rom convert opzip to zip) ,devices bug mount system_root
Click to expand...
Click to collapse
-----------------------------
TWRP flashing and LenageOS installation REALME 5 pro/Q
1)make sure that your bootloader is unlocked.
you can vist this link https://c.realme.com/in/post-details/1184734239149522944 OR
this youtube video
for referance
2)after you have a unlocked bootloader, download the neccessory files required in your PC
===>platform tools (fastboot files) link: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
===>TWRP recovery img . link: https://drive.google.com/drive/folders/1_pRUK4bj74N6xErkpFLr--2GoKyGxUtl
===> vbmeta img . link: https://drive.google.com/file/d/1kq9rV3eF8rYAUwmUvXo-8vttYIhVcQCb/view
===>Leneage OS for realme 5 pro . link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
3) once you have all the files
flash the vbmeta.img with fastboot..
COMMAND : fastboot flash vbmeta vbmeta.img
4) after that flash the recovery
COMMAND: fastboot flash recovery twrp-RMX1971-20191018.img
5) after that reboot into recovery by pressing the volume button on your phone and see " reboot recovery" in a red font
and press power button when u see that.
--.OPTIANAL AND RISKY step {IF YOU WANT TO BOOT INTO COLOROS AFTER INSTALLING TWRP, FLASH THE TWRP RECOVERY IMG AS BOOT ,i dont know this work in new twrp.but worked for me(fastboot flash boot twrp-RMX1971-20191018.img )}
6)after u successfully get the twrp menu make a backup of your whole system(all partitions) in case something goes wrong and move the backup into a lap or memory card
7)install the LenageOS and gapps . and reboot into fastboot mode and do step 3 again but this time flash vbmeta.img from this link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
8) wipe the whole data partition
9) reboot normally.
IN CASE YOU ARE STUCK IN THE RECOVERY MODE OR FASTBOOT MODE FEEL FREE TO CONTACT ME @azharsalim135
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
DnZX said:
I got bootloop after install Rom Lineage, how to fix it?
Click to expand...
Click to collapse
For non indian version Need seperate twrp to flash lineage.. It will be available soon. Dev working on it

working instal magisk in stock rom?

puturaya20 said:
working instal magisk in stock rom?
Click to expand...
Click to collapse
Dont try to install in stock rom.. I heard ita giving problems.. Backup stock before trying..

[GSI][ROM][10.0][AOSP+GAPPS][04/08/20]

Code:
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
{
"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"
}
What is this?
An AOSP based ROM, with gapps included and gesture support (pocket, hand wave, pickup).
Based on Android 10.0
Bugs:
voLTE - currently broken, working with Phh to get it up and running, absolutely no ETA, if you need voLTE, use any of the other roms
Steps:
1. Use latest CosmicDan treble TWRP
2. Re-partition to treble layout if you haven't done so yet
3. Flash vendor.img, system.img and a treble supported kernel (you can use mine or any of the other treble kernels on tissot xda)
4. Wipe data if coming from any other rom(!)
5. Flash Rom (No need for gapps, do not flash them, they are included!)
6. Reboot and wait for setup wizard to come up (may take 2-3 minutes)
7. Reboot to twrp and flash magisk (optional)
8. Reboot
Downloads: Link
Thanks to @Ranjan for IMS.apk
@phhusson for his work on GSI (donate to this man, he works on dozens of devices)
@flex1911 for his help bringing 9.0 kernel source for tissot
Oreo team (you all know who you are,@cosmicdan for twrp, @ghpranav for treble vendor source)
Enjoy!
P.S.
I am not going to add any custom features from other roms so please don't comment about that, feel free to flash any other GSI with this vendor/kernel if you want other features.
Source: https://github.com/aosp-tissot
kernel source: https://github.com/aosp-tissot/android_kernel_xiaomi_msm8953-1
Credit to @flex1911 for the original work on the kernel
XDA:DevDB Information
[GSI][ROM][10.0][AOSP+GAPPS][04/08/20], ROM for the Xiaomi Mi A1
Contributors
sooti, phhusson, flex1911, Ranjan
Source Code: https://github.com/aosp-tissot
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Treble
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2020-05-07
Created 2019-11-05
Last Updated 2020-08-04​

Changelog:
04/08/20:
* Added option to close annoying suggestions in settings (like we could in pie)
* August security patch
08/07/20:
* Fixed voLTE, no more crashes from SMS
07/07/20:
* July Security patch
28/06/20:
* Remove voLTE apk being installed by default, caused crashes for some users
21/06/20:
* Added voLTE support for all qcom devices
02/06/20:
* Rebased device tree and changed gapps to GMSEXPRESS (what OEMs get from google)
* June security patch
* Small other fixes
07/05/20:
* May security update
* Some Phh treble fixes and settings
* Updated kernel to 4.9.222
09/02/20:
* Feb security patch
25/01/20:
* Jan security patch
* Updated to latest 4.9 source for kernel
07/11/19:
* Fixed DRM
06/11/19:
* Fixed bootloop by disabling forced FDE encryption
* Fixed secure adb not being enabled
05/11/19:
* Initial release
* November security patch
* Up-streamed latest 4.9 kernel source from android

sooti said:
Changelog:
05/11/19:
* Initial release
* November security patch
* Up-streamed latest 4.9 kernel source from android
Click to expand...
Click to collapse
TUTORIAL WITH NO SENSE, what to flash, when? I flashed 1.boot 2.vendor 3.system image 4.kernel, reboot and bootlop
How to flash this?

GabiML said:
TUTORIAL WITH NO SENSE, what to flash, when? I flashed 1.boot 2.vendor 3.system image 4.kernel, reboot and bootlop
How to flash this?
Click to expand...
Click to collapse
There's no order.
EDIT: BOOT IMG is the Kernel

zurik said:
There's no order.
EDIT: BOOT IMG is the Kernel
Click to expand...
Click to collapse
And at step with FLASH ROM, what to flash because before it said to flash vendor sistem and boot.
Now, i flashed vendor then system then boot and reboot, again bootlop. Is it working at all?

GabiML said:
And at step with FLASH ROM, what to flash because before it said to flash vendor sistem and boot.
Click to expand...
Click to collapse
Wipe Data, System, Dalvik and Vendor (Be sure your phone repartitioned to support treble).
Flash System, Vendor and Boot.
After the 1st boot, you can flash Magisk too (Optional)

zurik said:
Wipe Data, System, Dalvik and Vendor (Be sure your phone repartitioned to support treble).
Flash System, Vendor and Boot.
After the 1st boot, you can flash Magisk too (Optional)
Click to expand...
Click to collapse
NOT WORKING, i did it. Bootlop. Have you some screenshots with it?

GabiML said:
NOT WORKING, i did it. Bootlop. Have you some screenshots with it?
Click to expand...
Click to collapse
Format Data tried?

GabiML said:
NOT WORKING, i did it. Bootlop. Have you some screenshots with it?
Click to expand...
Click to collapse
What do you mean "bootlooped"?
It might reboot the first time to encrypt data

Here it begins. Thanks sooti

I'm from AOSPExtended Pie..
Step i do :
1. Trebelized with CosmicDan TWRP
2. Wipe System, Data, Internal, Vendor.
3. Flash Vendor.img
4. Flash System.img
5. Flash Boot.img
6. Format Data then Yes
7. Reboot TWRP
8. Flash System.img again..
9. Reboot System
First boot it's make reboot when showing mi logo then second boot i'm stuck at mi Logo..
Any step i miss? or i do wrong step?
Please advice.. Thanks..

donnebanget said:
I'm from AOSPExtended Pie..
Step i do :
1. Trebelized with CosmicDan TWRP
2. Wipe System, Data, Internal, Vendor.
3. Flash Vendor.img
4. Flash System.img
5. Flash Boot.img
6. Format Data then Yes
7. Reboot TWRP
8. Flash System.img again..
9. Reboot System
First boot it's make reboot when showing mi logo then second boot i'm stuck at mi Logo..
Any step i miss? or i do wrong step?
Please advice.. Thanks..
Click to expand...
Click to collapse
Do you have logs? Did you wait long enough?

sooti said:
Do you have logs? Did you wait long enough?
Click to expand...
Click to collapse
i Thinks i wait 10 to 15 minutes..
I am not sure how to get logs..
But that a correct step i do?

donnebanget said:
i Thinks i wait 10 to 15 minutes..
I am not sure how to get logs..
But that a correct step i do?
Click to expand...
Click to collapse
Did you follow 6th. step?
just in case, "wipe" and "format" data aren't the same thing.
Some ROMs show "Enter code" screen (i.e.PixelExperience), while others just bootloop (i.e. EvolutionX), both for the same reason, an encrypted device.
However, try to do all steps again to be sure.

KaaMyA said:
Did you follow 6th. step?
just in case, "wipe" and "format" data aren't the same thing.
Some ROMs show "Enter code" screen (i.e.PixelExperience), while others just bootloop (i.e. EvolutionX), both for the same reason, an encrypted device.
However, try to do all steps again to be sure.
Click to expand...
Click to collapse
Thanks for advice, i'll try again..
Update : Using Flex Vendor and boot normaly but SIM Card not detected forgot my room have bad signal.. :laugh::laugh:

Is the look and feel the same as the 9.0 version? Like same camera etc?

donnebanget said:
Thanks for advice, i'll try again..
Update : Using Flex Vendor and boot normaly but SIM Card not detected forgot my room have bad signal.. :laugh::laugh:
Click to expand...
Click to collapse
Weird, maybe encryption has issues? I'll test it tomorrow and upload a change if needed, flex vendor is missing some commits

sooti said:
Weird, maybe encryption has issues? I'll test it tomorrow and upload a change if needed, flex vendor is missing some commits
Click to expand...
Click to collapse
And when starting phone have warning "There's an internal problem with your device. Contact your manufacturer for details."
- Google Play Device not certified
- Chrome sometimes freeze

donnebanget said:
And when starting phone have warning "There's an internal problem with your device. Contact your manufacturer for details."
- Google Play Device not certified
- Chrome sometimes freeze
Click to expand...
Click to collapse
Ya that's because your on flex vendor, if you flash other people's vendor I can't help you

sooti said:
Ya that's because your on flex vendor, if you flash other people's vendor I can't help you
Click to expand...
Click to collapse
Aaah, okaay my bad..

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 1 II

{
"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 18.1
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 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
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.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM is for testing purposes only and may contain unexpected bugs
2. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
3. This ROM will never work with any versions of Google Camera (GCam)!
4. You need to flash Stock Android 10 before flashing this ROM.
5. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
6. If you came from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
Downloads Links
AFH
Google Applications (optional):
NikGApps: https://nikgapps.com/
Information: Flash the GApps before first boot. If not, a clean flash is recommended
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 boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Flash the recovery.img in the zip file
Flash and boot into Recovery then choose Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
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 CatLog for example
Also thanks to:
Shion Sjll
The LineageOS Team
The CyanogenMod Team
Source Code:
hellobbn/android_device_sony_pdx203
Contribute to hellobbn/android_device_sony_pdx203 development by creating an account on GitHub.
github.com
hellobbn/android_vendor_sony_pdx203
Contribute to hellobbn/android_vendor_sony_pdx203 development by creating an account on GitHub.
github.com
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-01-20
Last Updated 2020-01-20

Important note
1. This Lineage build is based on official Android 10, not Android 11 (since AT72 hasn't been updated yet)
2. This build is highly experimental and for testing purpose only
3. This ROM may not be able to pass SafetyNet check
What works:
- Boot
- Bluetooth (LDAC might have problems, I am not sure)
- WiFi
- WiFi Hotspot
- RIL - Phone - Data
- GPS
- Camera
- Lights
- Touchscreen
- Fingerprint
- Microphone
- Audio & music
- Bluetooth audio
- NFC
- Clock
- USB
- SEPolicies: Enforcing
What does not work:
Always On Display does not seem to work properly

Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.

james194zt said:
Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.
Click to expand...
Click to collapse
Are you on stock android 10 before flashing? Have you erased the userdata?
I tried to flash it again and it boots successfully.

Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).

james194zt said:
Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).
Click to expand...
Click to collapse
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?

I was on the built in fastbootd not Lineage OS, I used Lineageos recovery after to see what was going on, will try the above though

clfbbn said:
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?
Click to expand...
Click to collapse
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.

james194zt said:
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.
Click to expand...
Click to collapse
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....

clfbbn said:
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....
Click to expand...
Click to collapse
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change

james194zt said:
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change
Click to expand...
Click to collapse
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?

clfbbn said:
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?
Click to expand...
Click to collapse
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!

james194zt said:
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!
Click to expand...
Click to collapse
Interesting, did you booted at least once when you downgraded to Android 10 because that might be the problem too?
I am also assuming this problem to be related to the vendor partition. If that is the case, I need to pull the blobs from AT51 and rebuild the ROM.
Edit: Would you mind we talking using telegram? I have PMed you my username.

I have an AT51 if I can help somehow. I'm having a different issue, but maybe its related. https://forum.xda-developers.com/t/...os-17-1-for-xperia-1-ii.4199059/post-84512259

Hi! this is awsome!
I just tried it out and everything seems to be working!
I am wondering it it is possible to get the camera pro and cinema pro working like for xperia 5 II
[EXTRA] Stock Camera && Cinema Pro && Photo Pro For AOSP
You MUST satisfy following condition: * My Device Tree Based ROM (Not SODP) * A PDX206 (Xperia 5 II ) User Download Link: Stock Camera if (ANDROID_VERSION == 10 && STOCK_VENDOR == 10) Using 52_RHE Cinema Pro [52_RHE] Photo Pro [52_RHE] if...
forum.xda-developers.com
Does anyone know how to do it?

@clfbbn, any reason for not making this build official? I'm willing to support.

ShionKagurazaka said:
Not easy to do, I think Bbn and me both are students, we don't have many times.
And then, if we need something like Sony Camera, Sony Photo Pro and so on in ROMs, we can't be offical
So why not Unoffical ?
Click to expand...
Click to collapse
I would like to make it Official because I would like to be able to get OTA updates. But I think you're right about the camera. The alternative is to not provide them and just share them separately as you share them.
I just build mine but I am thinking that not everyone has the patience to do it.

I noticed that extFAT does work on this build. Do you know how to fix it? I formatted the sd card to fat32 but the file size is limited to 4GB...

XQ-AT52 device said cannot find "system" partition" when trying "fastboot flash system system.img" . Please advise.

ShionKagurazaka said:
fastboot reboot fastboot at first
Click to expand...
Click to collapse
tried but "fastboot: usage: unknown reboot target fastboot" message appears

[ROM][UNOFFICIAL] LineageOS 18.1 for Moto G8/G Fast [RAV]

{
"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 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
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.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Read Guidance carefully, Or you will fail at flashing.
The LineageOS 18.1 is based on stock Android 10 this time, Make sure you are running stock Android 10 before flashing this ROM !!!!!!
Important Information
1 You need to flash Stock Android 10 before flashing this ROM.
2. For VoLTE, you might need to boot into stock firmware and enable it before flashing this ROM!
Downloads Links
LineageOS 18.1:
Unofficial-build: Link
Google Applications (optional):
OpenGapps: http://opengapps.org/ (ARM64->Android 11.0->Pico, Nano or Micro)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Moto
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Download Lineage Recovery: AFH
3. Put your device into fastboot mode
4. Type the following command to flash the recovery:
Code:
fastboot flash recovery recovery.img
5. Enter fastbootd:
Code:
fastboot reboot fastboot
6. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash:raw boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
7. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
Gapps:
After flashed images in fastbootd, choose Enter recovery - Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
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 CatLog for example
Also thanks to:
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-18.1 for Moto G8/G Fast, ROM for the Moto G8/G Fast
Contributors
Sjll
Source Code:
GitHub - sjllls/android_kernel_motorola_sm6125
Contribute to sjllls/android_kernel_motorola_sm6125 development by creating an account on GitHub.
github.com
GitHub - sjllls/android_device_motorola_rav
Contribute to sjllls/android_device_motorola_rav development by creating an account on GitHub.
github.com
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
Version Information
Status: Stable
Created 2021-01-26
Last Updated 2021-01-27

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
- 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

Sjll said:
- FM Radio: NA
Click to expand...
Click to collapse
Is it not possible to use the FM radio on custom ROMs?

Tried flashing this tonight but got stuck on:
fastboot flash system system.img
Getting this error " (bootloader) Invalid partition name system" Apparently the system partition doesn't exist on my phone (XT2045-3)
Similar error occurs with product partition.
The Super partition does and I tried to flash to that but the phone immediately booted into fastboot.
Anyone have an idea?

I just finished flashing and everything is working good, i had lost my wifi connection on a custom rom about two moths ago, it only worked with stock rom. this fixed it, anyways, the screen might be broken? notifications show under notch, also when i was trying to flash gapps, it kept giving error for wrong android version, i booted up again, checked the device info and apparently im running on android 11, so had tho get gapps 11 from cynanogen. magisk installed correctly also gapps, im gonna test it tonight see how it goes.

mbrewski said:
Tried flashing this tonight but got stuck on:
fastboot flash system system.img
Getting this error " (bootloader) Invalid partition name system" Apparently the system partition doesn't exist on my phone (XT2045-3)
Similar error occurs with product partition.
The Super partition does and I tried to flash to that but the phone immediately booted into fastboot.
Anyone have an idea?
Click to expand...
Click to collapse
so something like this happened to me, but it my error said: not enough space to resize partition... something like it, while trying to flash the system img, here is what i did, got the error, skipped system, flashed product, went back and flash system img. continued with the command list, and booted right up.

Thanks for the tip! It worked like a charm.
Csrtek said:
so something like this happened to me, but it my error said: not enough space to resize partition... something like it, while trying to flash the system img, here is what i did, got the error, skipped system, flashed product, went back and flash system img. continued with the command list, and booted right up.
Click to expand...
Click to collapse

Csrtek said:
also when i was trying to flash gapps, it kept giving error for wrong android version, i booted up again, checked the device info and apparently im running on android 11, so had tho get gapps 11 from cynanogen. magisk installed correctly also gapps, im gonna test it tonight see how it goes.
Click to expand...
Click to collapse
NikGapps-core-arm64-11-20210124-signed.zip
ffff2 said:
Is it not possible to use the FM radio on custom ROMs?
Click to expand...
Click to collapse
Do we have it on stock?
mbrewski said:
Tried flashing this tonight but got stuck on:
fastboot flash system system.img
Getting this error " (bootloader) Invalid partition name system" Apparently the system partition doesn't exist on my phone (XT2045-3)
Anyone have an idea?
Click to expand...
Click to collapse
Read OPs carefully, FastbootD mode.

Sjll said:
Do we have it on stock?
Click to expand...
Click to collapse
Yeah I had it on stock eu version, but I haven't seen it on any custom ROMs

Is there a command to fix the screen overlay? Notifications and carrier label show under the notch/front camera, I tried the command listed on other threads but doesn't work. Its the only problem I've encountered so far.

Csrtek said:
Is there a command to fix the screen overlay? Notifications and carrier label show under the notch/front camera, I tried the command listed on other threads but doesn't work. Its the only problem I've encountered so far.
Click to expand...
Click to collapse
Because I didn't build the overlay. I will consider about it.
ffff2 said:
Yeah I had it on stock eu version, but I haven't seen it on any custom ROMs
Click to expand...
Click to collapse
I will check it.

Will this work on the moto g stylus - us version.?

MaxyPanther said:
Will this work on the moto g stylus - us version.?
Click to expand...
Click to collapse
It should.

What about Moto g8 Power?

TheOnlyRealChosenOne said:
What about Moto g8 Power?
Click to expand...
Click to collapse
The odds of it working are fairly high because we both have the same gpu and chipset. I would expect a bootloop at worst. Give it a go and let us know!

MaxyPanther said:
Will this work on the moto g stylus - us version.?
Click to expand...
Click to collapse
TheOnlyRealChosenOne said:
What about Moto g8 Power?
Click to expand...
Click to collapse
Some kernel modules of other Moto sm6125 devices are not included, so some hardware doesn't work.

Csrtek said:
Is there a command to fix the screen overlay? Notifications and carrier label show under the notch/front camera, I tried the command listed on other threads but doesn't work. Its the only problem I've encountered so far.
Click to expand...
Click to collapse
Look for the Display Cutout option in Developer Options. I have that on my G7, and my G6 which doesn't even have a cutout, so I assume it's in all models.
MaxyPanther said:
Will this work on the moto g stylus - us version.?
Click to expand...
Click to collapse
Sjll said:
Some kernel modules of other Moto sm6125 devices are not included, so some hardware doesn't work.
Click to expand...
Click to collapse
Can you provide any more detail on what would be missing on the Stylus, and if support will be added for those things in this LOS rom, or if it'll take someone creating a Stylus based LOS rom for better support?

Okay, now I'm a little confused. I just flashed my stock moto g with the 20210127 build. Didn't run into any trouble except the resize error Csrtek described above, and solved it the same way (flash product partition first). Didn't try to load the gapps at the time (they were too big to download over LTE).
Now I'd like to install the gapps, but there is no Android 11 version on the opengapps.org site linked above, although the instructions say to use them. I tried the Android 10 version, but the installer chokes when I try to sideload them.
So, are version 11 gapps available yet? Or am I missing something? Do I need to downgrade back to stock version 10, then reflash Lineage, then sideload the version 10 gapps before booting? I would have tried it, but none of the stock images are available right now.
Thanks for doing this port, Sjll! And the overlay would be nice if you can do it! ;-)

Guru Meditation No. 42 said:
Okay, now I'm a little confused. I just flashed my stock moto g with the 20210127 build. Didn't run into any trouble except the resize error Csrtek described above, and solved it the same way (flash product partition first). Didn't try to load the gapps at the time (they were too big to download over LTE).
Now I'd like to install the gapps, but there is no Android 11 version on the opengapps.org site linked above, although the instructions say to use them. I tried the Android 10 version, but the installer chokes when I try to sideload them.
So, are version 11 gapps available yet? Or am I missing something? Do I need to downgrade back to stock version 10, then reflash Lineage, then sideload the version 10 gapps before booting? I would have tried it, but none of the stock images are available right now.
Thanks for doing this port, Sjll! And the overlay would be nice if you can do it! ;-)
Click to expand...
Click to collapse
I think you want Nik Gapps.