[ROM][UNOFFICIAL][8.1] LineageOS 15.1, AICP | Development & Discussion | 2021.04.15

[f2065]

when i try to flash the zip it gives the error "update error 7"

use latest TWRP (3.3.1-2019.10.17)
check if the ZIP is unpacked without an error (file may be damaged at download)
TWRP - Wipe - Advanced Wipe - Dalvik,System,Cache,Data…

 

[Hlaxkar]

use latest TWRP (3.3.1-2019.10.17)
check if the ZIP is unpacked without an error (file may be damaged at download)
TWRP - Wipe - Advanced Wipe - Dalvik,System,Cache,Data…

thanks! that worked!

 

[prakash09876]

no pie for this phone?

 

[f2065]

no pie for this phone?

There were experimental builds of LOS16, it works on M2 but there are minor bugs.
I don’t have enough space to build LOS16, I need to remove two other builds (LOS14, LOS15, AICP) to build LOS16.
LOS17 can also be builded, from neighboring (older and low-power models) it was builded…

 

[prakash09876]

Can i get the experimental links plz ?

There were experimental builds of LOS16, it works on M2 but there are minor bugs.
I don’t have enough space to build LOS16, I need to remove two other builds (LOS14, LOS15, AICP) to build LOS16.
LOS17 can also be builded, from neighboring (older and low-power models) it was builded…

 

[mantazzo]

There were experimental builds of LOS16, it works on M2 but there are minor bugs.
I don’t have enough space to build LOS16, I need to remove two other builds (LOS14, LOS15, AICP) to build LOS16.
LOS17 can also be builded, from neighboring (older and low-power models) it was builded…

Any specific bugs you can mention? If you can, of course.

Sent from my Xperia M2 Aqua using XDA Labs

 

[JuniorCaesar]

LOS17 can also be builded, from neighboring (older and low-power models) it was builded…

damn. a mid-range phone from 2014 is capable of getting major OS support in 2020 (thanks to the snapdragon and our amazing developers). i hope we can see some alpha or beta builds of los 16 or 17 in the future

also, is there a noticeable performance loss between 8.1 and 9 (without gapps) ? i wonder how snapdragon 400 performs on modern android versions.

 

[nowifi4u]

How does one enter TWRP after flashing this rom?
What I have:
- Sony M2303
- Latest stock .tft (just flashed)
- Updated bootloader
- Fastboot'ed TWRP 3.3.1
- This ROM (duh)

What is happening:
- After using "adb reload recovery" the phone reboots, shows the Sony logo, but after that just reboots again into system.
- Pressing either Vol+ or Vol- does the same thing as described above.

Also is there a way to have root? (I only see the "ADB only" option in Dev tools)

 

[nowifi4u]

Also is there a way to have root? (I only see the "ADB only" option in Dev tools)

I did find the additional su flashable zip on LineageOS website. Can it be used? (I'd have to reflash the phone from zero to regain the access to TWRP for one time lul -_-)

Edit: I did try flashing addonsu-15.1-arm-signed.zip, but when I type in "su" in terminal it gives the following error: "Binder driver count not be opened. Terminating."

Edit #2: su works under root user (via adb root). So uhm... Some file is not accessible to other users? strace lead me nowhere =/

Edit #3: Well I just installed su via adb root. But there is still the TWRP issue...

 

[JuniorCaesar]

I did find the additional su flashable zip on LineageOS website. Can it be used? (I'd have to reflash the phone from zero to regain the access to TWRP for one time lul -_-)

Edit: I did try flashing addonsu-15.1-arm-signed.zip, but when I type in "su" in terminal it gives the following error: "Binder driver count not be opened. Terminating."

Edit #2: su works under root user (via adb root). So uhm... Some file is not accessible to other users? strace lead me nowhere =/

Edit #3: Well I just installed su via adb root. But there is still the TWRP issue...

Your TWRP situation is weird, stock .175 + bootloader update should make your TWRP permanent (until you flash stock rom again).

How to boot into TWRP: Turn off your phone, Hold both Power and Volume Down buttons. When the phone vibrates, release the power button.

For root. You can use los14.1's addonsu, but there won't be any prompt for superuser access (which is kinda dangerous). You can;

1) Manually disable superuser access after your root involved work

Or

2) Manually patch your boot.img and use Magisk

Here is the tutorial (thanks to @basem_ym)

As I hardly remember magisk mounts /data partition after flashing.
Do not flash migisk zip, do the following:
Copy stock boot img to sdcard (the one provided with the rom)
install magisk manager on your nonrooted phone, open magisk manager and manually patch within magisk app.
Copy your patched boot img to your pc and flash it using fastboot.
If it didnt work, disable magisk hide.
If this didnt work too, then I must be forgetting something.

You can flash patched boot.img on TWRP, no need to fastboot.

Sent from my X Compact using XDA Labs

 

[f2065]

After using "adb reload recovery" the phone reboots, shows the Sony logo, but after that just reboots again into system.

This problem seems to have been fixed several months ago. What firmware was installed?

I did find the additional su flashable zip on LineageOS website. Can it be used? (I'd have to reflash the phone from zero to regain the access to TWRP for one time lul -_-)

I am using SuperSU (SR5-SuperSU-v2.82-SR5-20171001224502.zip)

2) Manually patch your boot.img and use Magisk

Magisk spoils the possibility of installing APK, it is not supported by our kernel.

 

[JuniorCaesar]

Magisk spoils the possibility of installing APK, it is not supported by our kernel.

with manual patching, i can install APK's without a problem.

 

[mantazzo]

APK install does not work with Magisk as long as MagiskHide is enabled in the Magisk Manager Settings. After disabling it and restarting the phone, APK install or installs from Google Play Store works fine (at least for me on M2 Aqua with AICP) and Magisk works fine too, just enable the MagiskHide when needed and disable it otherwise.

Regarding the Recovery access, I think I can confirm the same issue, however, it does work, but only on a clean install and on first try (I tried to reboot to recovery directly from phone). Any other time after the first try it just shows Sony logo and continues to boot into system (though Notification LED flashes some lights, usually). Any way I can help with that a bit more, let me know.

Sent from my Xperia M2 Aqua using XDA Labs

 

[zulkosaki]

There were experimental builds of LOS16, it works on M2 but there are minor bugs.
I don’t have enough space to build LOS16, I need to remove two other builds (LOS14, LOS15, AICP) to build LOS16.
LOS17 can also be builded, from neighboring (older and low-power models) it was builded…

i can help build them. i have space and 16gb ram and fast connection.. rocking linux but not yet try to compile any rom :silly: so, i dont really familiar with steps..

 

[Yatin_manjunath]

what is the gapps used
link please

 

[ectoanonymous]

Does it work for Xperia M2 D2302? What features are not working in this ROM?

Does it work for Xperia M2 D2302? What features are not working in this ROM?
Can anyone please tell how to install it in detail???

 

[DVt3]

Hi everybody great work and thanks for the effort.
I notice that transferring music files from Lenovo with windows 10 and USB3 to sd card (set as a removable one) on D2302 the phone goes a bit wobbly and doesn't want to transfer the files. It keeps switching back to charge mode. Even going to settings and setting it to transfer, the phone exhibits the same behaviour.
I switch it to USB2 port and it works with no issues. Not too bothered but thought I would share.

 

[m.tarhsaz]

Kernel requirements

First of all tanks a lot for your huge effort.

I installed that for daily use on my D2302.

I also build a kernel based on official source code and patched that for supporting MagiskHide (mount namespace added to source code):

[KERNEL][3.40][DM2] XPERIA M2 MagiskHide working kernel

I tried flashing my kernel after flashed your ROM but encountered boot loop.

I just want to know what's the reason?

Is it due to my image format is AOSP or something else?

If your ROM needs some kernel feature(s) that not exist in official kernel source code provided by Sony please let me know.

 

[f2065]

I tried flashing my kernel after flashed your ROM but encountered boot loop.
I just want to know what's the reason?

Edit ro.secure=0, ro.adb.secure=0 in prop-files to access debug without authorization, and then read dmesg/logcat via ADB.

If your ROM needs some kernel feature(s) that not exist in official kernel source code provided by Sony please let me know.

For the current versions of LOS 14/15, many different edits in the kernel are needed. It is necessary to investigate the history of commits of the kernel that I use (it is on the github), for 2015-2018.
But first, you need to look at the errors in dmesg and logcat, there is definitely something about the reasons for the bootloop.

I'm not sure if kernel 3.40 is a good idea, older kernels are faster.

 

[aallgg]

So I saw on your GitHub that you uploaded some scripts to build LOS 14/15/16/17 and TWRP. I don't know a lot about compiling ROM's, but I tried them all, but only 14/15/16 succeeded (TWRP said that the official LOS repository only has up to 13.0 because it didn't download anything to device/sony so I copied everything from device/sony from the src 141 except eagle, bc I used the one for TWRP from you GitHub and I had to delete libshims from device/sony/eagle and rootdir from vendor/cm because they were duplicated and it wouldn't build and it succeeded and 17.1 failed because I think there are some repositories missing for that branch (I've tried to put some missing files from src 160) (I've attached a screenshot)). But LOS 16 booted at least, and I've tested it:
-WiFi doesn't work
-MTP doesn't work, but ADB does
-Camera works only on first boot, quite strange
I've attached some logs/kmsg from the first and second boot and I can provide more if you want.
h ttps://drive.google.com/drive/folders/1xQ6X-Zpy3khzp9ydwhvVSrnyqkQjs3cU?usp=sharing