[ROM][OFFICIAL][discovery][9] LineageOS 16.0 - Sony XA2 Ultra ROMs, Kernels, Recoveries, & Other

[ROM][OFFICIAL][discovery][9] LineageOS 16.0 - Sony XA2 Ultra ROMs, Kernels, Recoveries, & Other

How to flash latest firmware
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261769960 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?

Flashed this morning and it works beautifully. Fast, sweet pie. Thanks @LuK1337!

newbie here. Just wondering after flash custom firmware, is it still possible to restore the xa2 ultra to stock ota?
Thanks.

WangYcca said:
newbie here. Just wondering after flash custom firmware, is it still possible to restore the xa2 ultra to stock ota?
Thanks.
Click to expand...
Click to collapse
Yes.

great work thanks you i have flash the rom 1/3/19 and test now all items so is fast and stable whith root magisk work su work my only problems is 2 now i dont know how to install in phone twrp and second big problem is how to hide in start phone the black boot logo of sony unlocking bootloader screen ,( if iknow any body please tell me how to fix this thanks a lot ) . thanks again for great work guys save my phone respect.
sorry for my bad english
install os in my xperia xa2 ultra 4213

the system works well. However the 15.1 root addon seems not working on 16.
In the developer options, I do see root access option for apps/adb, but doesn't matter which one is chosen, still no root access.

WangYcca said:
the system works well. However the 15.1 root addon seems not working on 16.
In the developer options, I do see root access option for apps/adb, but doesn't matter which one is chosen, still no root access.
Click to expand...
Click to collapse
Who'd have thought that something meant to be used with 15.1 won't work with 16.0.

I can't seem to get the radio working after following these instructions. I downloaded the latest firmware for my phone. H223 Customized US. Flash seemed to go fine. When typing the fastboot command I get the following error: Setting current slot to '`' FAILED (remote: 'Invalid Slot Suffix')
Finished. Total time: 0.004s
I tried setting it manually to both A and B but neither worked. I have no idea what I'm doing wrong

GhostCow said:
I can't seem to get the radio working after following these instructions. I downloaded the latest firmware for my phone. H223 Customized US. Flash seemed to go fine. When typing the fastboot command I get the following error: Setting current slot to '`' FAILED (remote: 'Invalid Slot Suffix')
Finished. Total time: 0.004s
I tried setting it manually to both A and B but neither worked. I have no idea what I'm doing wrong
Click to expand...
Click to collapse
Join my irc channel?
(see my signature)

Anyone else getting bad screen freeze? Like the touches dont read right?

Scruffdog1978 said:
Anyone else getting bad screen freeze? Like the touches dont read right?
Click to expand...
Click to collapse
In my case, while an app is launching, the screen will freeze about a second. Once it is launched, it runs smoothly.

Many thanks for your outstanding contribution. I have flashed build 02.03.2019, gapps nano, rooted with magisk 18.1 and it is working pretty much good exept few things. Every time after instaling any magisk module phone is going to bootloop right after restarting, volume up and power 2,3 times fix the restart. Fingerprint reader stop working and it's menu disapper sometimes from settings/securitym,restart helps. Button recent sometimes does not show recent apps, restart helps. Chrome FC after attemt to instal any apk downloaded. No downloaded galery app is allowed to delete any picture from storage. Radio FM is working really well, much better than stock one.

Update to 20190304 with "updater" (OTA) gives a bootloop? Can i download new build, flash using TWRP and Keep user data?

jnappert said:
Update to 20190304 with "updater" (OTA) gives a bootloop? Can i download new build, flash using TWRP and Keep user data?
Click to expand...
Click to collapse
You probably have mismatched firmware between A and B if that's a thing. Follow #2.

LuK1337 said:
You probably have mismatched firmware between A and B if that's a thing. Follow #2.
Click to expand...
Click to collapse
But is there a way to flash the update in twrp or the lineage recovery?

Aklenz07 said:
But is there a way to flash the update in twrp or the lineage recovery?
Click to expand...
Click to collapse
What update?

LuK1337 said:
What update?
Click to expand...
Click to collapse
The ROM update?

Aklenz07 said:
The ROM update?
Click to expand...
Click to collapse
Why would you do that?

LuK1337 said:
Why would you do that?
Click to expand...
Click to collapse
Because I get a bootloop if I do the normal way and I don't have time to do #2 to get it working.

Related

[ROM][OFFICIAL][discovery][8.1] LineageOS 15.1

How to flash latest firmware
[ protip: Currently Lineage builds depend on latest 8.0 firmware (50.1.A.13.123), they will not boot up on 50.2.A.0.* or newer ]
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- kernel_X-FLASH-ALL-18AE_0x00.hash
- kernel_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?

Do we download arm or arm64 for su and gapps?

Aklenz07 said:
Do we download arm or arm64 for su and gapps?
Click to expand...
Click to collapse
arm64.

this device will be upgrad to pie?.
By the way tnx for hard work.

Echo MsK said:
this device will be upgrad to pie?.
By the way tnx for hard work.
Click to expand...
Click to collapse
I could release 16.0 builds too but I'm being lazy for time being.

LuK1337 said:
I could release 16.0 builds too but I'm being lazy for time being.
Click to expand...
Click to collapse
plz take your time enjoy your life and then spend sometimes here your valuable time.
We can wait for awesome dev.:highfive:

I installed the ROM and had everything work but it won't read my SD card. If I go into recovery I can view my SD card and files but when I am on the phone it can't read it

HaxUrMom69 said:
I installed the ROM and had everything work but it won't read my SD card. If I go into recovery I can view my SD card and files but when I am on the phone it can't read it
Click to expand...
Click to collapse
Pull a kernel log (adb shell dmesg after adb root).
[ actually I think i know what it's caused by, add me on hangouts/discord whenever it's not 4am in my timezone ]

If someone wants to be helpful, let me know if flashing this kernel https://kremowka.xyz/files/b767d5e5d4817b0530914d929f7611d315afd233.img ( fastboot flash boot b767d5e5d4817b0530914d929f7611d315afd233.img ; fastboot reboot ) fixes external sdcard ^.^
Once I get a confirmation that it actually fixes the issue I'll merge changes in repos and next official build will have working ext SD.
[ someone else already confirmed it works thus I merged required change ]

LuK1337 said:
If someone wants to be helpful, let me know if flashing this kernel https://kremowka.xyz/files/b767d5e5d4817b0530914d929f7611d315afd233.img ( fastboot flash boot b767d5e5d4817b0530914d929f7611d315afd233.img ; fastboot reboot ) fixes external sdcard ^.^
Once I get a confirmation that it actually fixes the issue I'll merge changes in repos and next official build will have working ext SD.
[ someone else already confirmed it works thus I merged required change ]
Click to expand...
Click to collapse
Can it be flashed from internal storage or do I need a working SD card to flash i
Edit: sorry Im retarded I flashed it and now it reads my SD card. Thank you for this fix . I was still trying to figure out how to pull a log for you

HaxUrMom69 said:
Can it be flashed from internal storage or do I need a working SD card to flash i
Edit: sorry Im retarded I flashed it and now it reads my SD card. Thank you for this fix . I was still trying to figure out how to pull a log for you
Click to expand...
Click to collapse
I don't need a log anymore. I literally just fixed it.

LuK1337 said:
I don't need a log anymore. I literally just fixed it.
Click to expand...
Click to collapse
I know... I was trying to say you were fast. You got a fix before I could give a log

Windows 8 mobile? LOL I'll wait for the external storage fix, possibly linage 16 release. Hopefully we can format as internal since the stock Sony ROM can't.

Ricktor said:
Windows 8 mobile? LOL I'll wait for the external storage fix, possibly linage 16 release. Hopefully we can format as internal since the stock Sony ROM can't.
Click to expand...
Click to collapse
You can flash the boot image located a few posts before for the external storage fix, I'm sure it will come officially in the next build.

Now that today's build is out I disabled downloading of kernel image from page #1 so that less smart people won't think they need to flash it on newer builds.

Any news about the dual sim support?

Kirrr said:
Any news about the dual sim support?
Click to expand...
Click to collapse
I don't have a dual sim device therefore I can't fix it myself. Feel free to fix it and submit patches onto our gerrit~!

LuK1337 said:
I don't have a dual sim device therefore I can't fix it myself. Feel free to fix it and submit patches onto our gerrit~!
Click to expand...
Click to collapse
I'm not a developer so I can not do that. Can this brick my H4213 if I try to flash it?

Kirrr said:
I'm not a developer so I can not do that. Can this brick my H4213 if I try to flash it?
Click to expand...
Click to collapse
No, but dual sim feature won't work properly. You can keep using it as a single sim device tho.

[ROM][OFFICIAL][discovery][10] LineageOS 17.1

[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261769960 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?

Where do I get gapps for 10? Opengapps only says something about a patched rom because blah blah webview whenever I click on "10" but doesn't actually let me download anything
Answer: https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500

Sourceforge under "beta" folder
---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------
Here's the link
https://sourceforge.net/projects/opengapps/files/arm64/
---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------
Another thing I would like to mention is the "nano" packets was give me issues it would freeze when I tried typing the pin to the fingerprint part of the setup. I am running Pico now and I have had no issues?

OK so far the only issue I've seen is not being able to set the dark mode to black, it just reverts back to normal dark mode, other than that no issues here! Great work man!
Update: If I try connecting to a public WiFi that requires a login, when I click "sign in to network" that function just crashes, however regular WiFi at home works great.
Also, expanded desktop crashes the settings app when you try going into it
I'll be able to send you a logcat when I get home(about 8hrs from now)

appleknight said:
OK so far the only issue I've seen is not being able to set the dark mode to black, it just reverts back to normal dark mode, other than that no issues here! Great work man!
Update: If I try connecting to a public WiFi that requires a login, when I click "sign in to network" that function just crashes, however regular WiFi at home works great.
Also, expanded desktop crashes the settings app when you try going into it
I'll be able to send you a logcat when I get home(about 8hrs from now)
Click to expand...
Click to collapse
Don't bother sending a logcat for expanded desktop.

Great Job @LuK1337! As always, well done!

So, basically we can instal this straigth over the 50.2.A.0.400 build ?

kamyk70 said:
So, basically we can instal this straigth over the 50.2.A.0.400 build ?
Click to expand...
Click to collapse
If you have any 50.2.* on both slots then sure.

LuK1337 said:
If you have any 50.2.* on both slots then sure.
Click to expand...
Click to collapse
Sorry for bothering, I'm just not really sure.
If I flashed recent Sony full stock 50.2 firmware with Newflasher, does it mean I am on both slots with it?

kamyk70 said:
Sorry for bothering, I'm just not really sure.
If I flashed recent Sony full stock 50.2 firmware with Newflasher, does it mean I am on both slots with it?
Click to expand...
Click to collapse
It depends how you flashed it. You can do `strings /dev/block/bootdevice/by-name/modem_* | grep Daily` in TWRP. If you see both dates starting with 2019 then you probably have some kind of 50.2 on both slots.

Any word on what is supported/not working in this build? Is it safe to say this is fairly Beta and we can expect a decent amount of glitches along the way?

kamyk70 said:
Sorry for bothering, I'm just not really sure.
If I flashed recent Sony full stock 50.2 firmware with Newflasher, does it mean I am on both slots with it?
Click to expand...
Click to collapse
Yes

I'm sure I either did something wrong or I misread but I currently have no fingerprint.
Also things I noticed which are not concerns
Exposed is wonky
Pin will crash ui and then give u blank unknown pin
Not important but substratum cause lag
Only things I've notice

lonewolfbtown said:
I'm sure I either did something wrong or I misread but I currently have no fingerprint.
Also things I noticed which are not concerns
Exposed is wonky
Pin will crash ui and then give u blank unknown pin
Not important but substratum cause lag
Only things I've notice
Click to expand...
Click to collapse
Consider reading #2 post.

LuK1337 said:
Consider reading #2 post.
Click to expand...
Click to collapse
Yup I'm an idiot. I misread that post. Thanks man

Siemano.
My question is: what kind of gapps is recommended for this build?
Since it says its android 10 I thought it should be this one:
opengapps/files/arm64/beta/
But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28). Which one should I pick?

razider said:
Siemano.
My question is: what kind of gapps is recommended for this build?
Since it says its android 10 I thought it should be this one:
opengapps/files/arm64/beta/
But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28). Which one should I pick?
Click to expand...
Click to collapse
>But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28).
re-boot twrp.

And the gapps should be arm64. Is that true?
When I tried to to install gapps for LOS 16.1 it said I should go with "arm", I'm assuming instead of arm64.
(I tried to reboot TWRP after flashing rom)
LuK1337 said:
>But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28).
re-boot twrp.
Click to expand...
Click to collapse

razider said:
And the gapps should be arm64. Is that true?
When I tried to to install gapps for LOS 16.1 it said I should go with "arm", I'm assuming instead of arm64.
(I tried to reboot TWRP after flashing rom)
Click to expand...
Click to collapse
Something tells me that you didn't do it.
Install lineage, boot twrp again, install gapps.
Also yes, use ARM64.

[ROM][discovery][10.0] AOSP [Sony Open Devices Project]

{
"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"
}
To God be the glory, a working AOSP ROM for those on both the 50.1 and the 50.2 firmware, now based on Android 10! This is a fully functional ROM, but there may still be a few bugs here and there, please read this entire post before using!
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
WARNING: This build SHOULD work on both the H3213 and H3223, but I could only test on a H3223.
Disclaimer: I am not responsible for any damages to your device.
A huge thanks to the Android Open Source Project and Sony Open Devices Project!
The Sony Open Devices Project (SODP) is, in Sony's own words:
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
Click to expand...
Click to collapse
That said, any and all of my work relating to this project is completely available for any who wish to use or modify it. I didn't make AOSP, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
This Unofficial AOSP ROM was built for the H3223 (discovery), but may work on some of the other variants, please try at your own risk. However, if you do try it on another variant, please be sure to let me know in the comments how well it worked.
Downloads:
Rom Download link:
Note: This is designed to work with any firmware version of the XA2 Ultra, because you flash a custom OEM partition. I've tested this on 50.1 and 50.2 firmware phones.
http://www.mediafire.com/folder/dl8dcra6ojog5/Sony Open Device Project
IF there is an ENG build, it is marked "ENG" for testing purposes only. It's your phone, you can install anything you want, but I do not recommend installing the ENG build. Use the "USER" or "USERDEBUG" builds.
Currently, Open Gapps is still in beta form for Android 10. This ROM does not include Gapps, and my attempt to flash gapps failed, but your mileage may vary.
Installation instructions: (DIFFERENT THAN NORMAL! DONE THROUGH FASTBOOT!)
- Download the zip file for AOSP 10.
- Unzip the zip file, and you will find 5 images.
- If using Windows, put these in your folder you use for fastboot, if using Linux, you can do this from any folder.
- Reboot the phone into bootloader/fastboot mode.
- Flash them to your phone, like so (example for Linux)
Code:
$ fastboot flash boot ./boot.img
$ fastboot flash oem ./oem.img
$ fastboot flash system ./system.img
$ fastboot flash userdata ./userdata.img
$ fastboot flash vendor ./vendor.img
$ fastboot reboot
Your phone will now boot into AOSP 10!
If you plan to install magisk, then let the rom boot once, then go back to TWRP and flash magisk. I recommend making a backup of at least the boot partition first. Magisk is optional, of course. And you do so at your own risk!
What works:
Code:
So far these things that I have tried work, such as
- Display/touch
- Camera (front and back) for pictures and video!
- Phone calls
- Data 3g/LTE
- Bluetooth
- WiFi
- Sound in system, in calls, over bluetooth devices
- MicroSD card (external SD card).
- GPS
- Fingerprint sensor
- MTP file transfer
etc....
What doesn't:
Code:
- FM Radio does not work
- The built in Gallery app can play back recorded videos from camera, however, sometimes has a green screen first.
---> VLC or other apps work fine for video playback, though.
- Camera button does not launch camera.
- Nothing else that I know of, but let me know if you find something!
Source Code: https://source.android.com/
Device, kernel, and vendor trees: https://github.com/sonyxperiadev
My GitLab: https://gitlab.com/alaskalinuxuser/
ROM OS Version: 10.0
ROM Kernel: Linux 4.9.194
Based On: Android Open Source Project
Created 2019-11-13
Last Updated 2019-11-13

Changelog:
20191112
- Fixed MTP crash issue.
- Rebuilt kernel 4.9 with gcc instead of clang
- Fixed camera
- Bootup time much faster
20191111
- Rebased kernel to 4.9
- No video recording
- Camera turns green
- MTP/PTP still not working
20191028
- Rebuilt kernel (4.14)
- Long boot up time.
- Random reboots fixed.
- Still no camera.
- Can't use MTP/PTP to transfer files.
20191024
- First build, a bit laggy.
- Random reboots.
- Camera doesn't work at all.
- Can't use MTP/PTP to transfer files.
Notes:
This ROM is very, very, vanilla. It is straight up AOSP. No frills, no mods, no extras. Just pure source.
Currently, Open Gapps is still in beta form for Android 10. This ROM does not include Gapps, and my attempt to flash gapps failed, but your mileage may vary.
I also don't use social media except XDA, so I don't know how well every app works. But if you have issues and have logs, perhaps I can look at them and see what is wrong.
Can I flash back to firmware 50.x.xxxx after flashing this?
Yes, you can. I flashed this and then flashed back to the 50.2 firmware several times while testing. As always, you assume full responsibility for your device, but it worked for me.
Can I install Magisk on this ROM?
Yes, I have successfully installed Magisk through TWRP.
Issues/workarounds:
- Video playback from camera. Any camera videos you record work fine, and the built in player can play them, however, the built in player often shows a "green" screen at the beginning of the video. The video itself is fine. I downloaded and used VLC app to play them and they work just fine. You can get VLC or other apps from the play store, or here: https://www.f-droid.org/en/packages/org.videolan.vlc/.

By chance anyone know how to get cts integrity to pass on aosp the correct way? I've installed some xposed modules but my bank app still does work with or without gapps

Yodasgodfather said:
By chance anyone know how to get cts integrity to pass on aosp the correct way? I've installed some xposed modules but my bank app still does work with or without gapps
Click to expand...
Click to collapse
The only way I know of to do this is outlined here:
https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
Under the section of:
Spoofing device fingerprint
Hope that helps! :fingers-crossed:

Thank you will try it as soon as I get the chance

So, some good news, work on the 4.14 kernel is progressing from the SODP, so hopefully a build with that kernel will be coming soon. This build has the 4.9 kernel, which is working very solid, as it has been my daily driver for about 10 days now.

What have I missed?
Code:
C:\Flashtool\x10flasher_native>fastboot flash boot boot.img
< waiting for any device >
Sending 'boot__a' (24045 KB) OKAY [ 0.577s]
Writing 'boot__a' FAILED (remote: 'No such partition.')
Finished. Total time: 0.587s
C:\Flashtool\x10flasher_native>fastboot flash oem oem.img
Sending 'oem' (219820 KB) OKAY [ 5.288s]
Writing 'oem' OKAY [ 0.002s]
Finished. Total time: 5.295s
C:\Flashtool\x10flasher_native>fastboot flash system system.img
Sending sparse 'system__a' 1/3 (515804 KB) OKAY [ 12.805s]
Writing sparse 'system__a' 1/3 FAILED (remote: 'No such partition.')
Finished. Total time: 15.204s
C:\Flashtool\x10flasher_native>fastboot flash userdata userdata.img
Sending 'userdata' (4272 KB) OKAY [ 0.106s]
Writing 'userdata' OKAY [ 0.003s]
Finished. Total time: 0.112s
C:\Flashtool\x10flasher_native>fastboot flash vendor vendor.img
Sending 'vendor' (48188 KB) OKAY [ 1.167s]
Writing 'vendor' OKAY [ 0.002s]
Finished. Total time: 1.173s
C:\Flashtool\x10flasher_native>fastboot reboot
Rebooting
I think my device might be on Slot B, should I switch it in TWRP?

Nevermind. I figured it out. Was on stock rom with TWRP but TWRP was not flashed to Ramdisk. Went to Lineage 9, then used fastboot and all is well. Thank you for compiling this!

the right way to install Aosp 10 is
first in fastboot (SW_binaries) in A And B then flash the rom in fastboot
fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6a_nile.img
fastboot flash oem_b SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6a_nile.img
downlod (SW_binaries) from here
https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-nile/
take a note
only BitGapps working with Aosp 10 for xa2 ultra

Asop 10 working also in My H4213
Asop 10 working also in My H4213 '
i try LineageOS 17.1 and PixelExperience_Plus
but My opinion is Aosp 10 is the best so I can install pixel camera with main camera I could not do it with LineageOS 17.1 or PixelExperience_Plus 10
Because not working i try all virsion of gcamera and pixel camera
only in Aosp 10 working good
the best for is Xa2 ultra

Just for my understanding: Is this ROM able to run stock Sony Apps such as Camera, Album, Mail, Live-Wallpapers without the need to convert/port them to "universal apps" first?

no but you dont need Aosp camera already Installed and the best for ever you can install google or pixel camera

hi, i am new, i have installed lineage 17 in my xa2 ultra, and i have the problem that the microphone audio goes out from time to time, install a zip but it doesn't work either, does this rom work well? Could someone tell me the steps to install it? I have the fastboot in windows, I speak Spanish and my English is bad, I use a translator. thank you. another query this rom is updated?

maximdq said:
hi, i am new, i have installed lineage 17 in my xa2 ultra, and i have the problem that the microphone audio goes out from time to time, install a zip but it doesn't work either, does this rom work well? Could someone tell me the steps to install it? I have the fastboot in windows, I speak Spanish and my English is bad, I use a translator. thank you. another query this rom is updated?
Click to expand...
Click to collapse
I have not updated this ROM in several months, but it was fully functional. You can find the instructions in the first post.
Sent from my Sony Xperia XA2 Ultra with Android 10

AlaskaLinuxUser said:
I have not updated this ROM in several months, but it was fully functional. You can find the instructions in the first post.
Sent from my Sony Xperia XA2 Ultra with Android 10
Click to expand...
Click to collapse
ok, the commands are 1 by 1 or all together they are put in fastboot ?, and another important thing the gapps can i install the ones for android 10? through twrp? because otherwise google wouldn't work for me. I wait for a response, thank you
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
ahh another question, how do I uninstall lineage 17? I go into twrp and delete everything? or do I just do the aosp installation steps? Thank you

I already installed aosp, but how do I install the gapps now? Thank you

maximdq said:
I already installed aosp, but how do I install the gapps now? Thank you
Click to expand...
Click to collapse
Great! I don't use Gapps any more, but usually you download the opengapps zip and install it with TWRP.
Sent from my Sony Xperia XA2 Ultra with Android 10

AlaskaLinuxUser said:
Great! I don't use Gapps any more, but usually you download the opengapps zip and install it with TWRP.
Sent from my Sony Xperia XA2 Ultra with Android 10
Click to expand...
Click to collapse
I already did, but it doesn't work. Some in particular must be installed ?.

someone who has installed the gapps? I have tried mini and nano by twrp and it doesn't work. some help?? Thank you

maximdq said:
someone who has installed the gapps? I have tried mini and nano by twrp and it doesn't work. some help?? Thank you
Click to expand...
Click to collapse
I'm not sure, I don't use gapps myself.
Sent from my Sony Xperia XA2 Ultra with Android 10

[ROM][OFFICIAL][discovery][11] LineageOS 18.1

[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261769960 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?

banbenggengxin
Hello, I started to use this ROM for my H4233 on October 1st. At present, I mainly use the WeChat camera and there will be problems. Seeing that the download address has been updated to the 20201011 version, can I post a change log on this page after the version is updated? Thanks for the above from Google Translate
你好 我10月1日左右开始给我的H4233 使用该ROM 目前主要是使用微信相机会有问题，看到下载地址已经更新到了20201011版本能否在版本更新后在该页面 发布一个更新日志呢 ，谢谢

Hi, someone did install the rom? Any benefits compare to the 17.1

so i installed it, but it shows me LOS 17.1 and not 18.1.. whats the point??

ok, forget it, it was the problem of the internal recovery of LOS. It shows the sideload, but it has strange effects, or no effect. With TWRP it works. But now i try E os

there are no opengapps available for android 11, what gapps to get (similar to opengapps micro) please?

found nikgapps .
but theres another problem
after wiping everything from recovery, installing gapps - it boots in OS everything is okay, then I install magisk (21.00) from recovery but I cant boot anymore, I get bootloop?
Any ideas please?

maxis123 said:
found nikgapps .
but theres another problem
after wiping everything from recovery, installing gapps - it boots in OS everything is okay, then I install magisk (21.00) from recovery but I cant boot anymore, I get bootloop?
Any ideas please?
Click to expand...
Click to collapse
yeah you need a modded version for 11. Theres a modded magisk floating around the oneplus 7 pro forums somehwere

sorry for double post but heres the magisk link
[ROM][Android 12L][OP7Pro] crDroid v8.12 [19.12.2022]
Does anyone have the magisk download links from the third post? They're not showing up on the new website.
forum.xda-developers.com
should be second post

I upgraded my phone H3223 from Android 9 to this version. Using TWRP. Before update I applied Sony AOSP 11 https://developer.sony.com/file/download/software-binaries-for-aosp-android-11-0-kernel-4-14-nile/
I used NIKgapp.
NikGapps - Browse /Releases/NikGapps-R at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
I didn't wipe my data , after installing this version and NIKgapp , I rebooted and I have version lineage_discovery-userdebug 11 RQ1A.201205.008 eng.luk.20201212.191949 dev-keys
All existing apps are working after update.
Camera is working , only problem that I have is microphone . Randomly mic is so low or does not work for some applications. I have to reboot to fix this and this problem happens everyday.
Also up and down audio volume keys sometime donot work .
I noticed after upgrade to this Android version I have a program called AudioFX . I turn it off and on but the problem with microphone happens .

Hi!
I installed LOS 18.1 on my sony XA2 ultra H4213, but i have the following problems that i could not solve, even after deleting the cache:
- no sound for media (videos, music, telegram ...) the rest of the sound works well (buzzer, call ...)
- and all videos stuck.
Do somebody has an idea?
Thanks!

I reflashed android pie and the sound / videos work well again, but i can not install LOS now
no possibility to get to recovery mode and no fastboot drivers for the H4213. I even forgot how could I install it in the past... maby the recovery mode was working.

HowTo upgrade from 17.1 (make sure your computer has working "adb" (setup instructions can be found here):
1. Download the latest Lineage build and Lineage recovery from here. Optional, if you need Google apps, it can be obtained from here.
2. Run "adb reboot sideload"
3. Run "adb sideload /path/to/zip" (inserting the path to your LineageOS package).
4. If you need Google apps: Advanced -> Reboot to Recovery -> [when the device reboots] -> Apply Update -> Apply from ADB, then sideload gapps "adb sideload /path/to/zip". Reboot.
5. Start your device with new installed LineageOS, set the minimal startup settings. Open developer options (to unlock it: "Settings" -> "About phone" -> tap 7 times on "Build number") and enable ADB interface ("Settings" -> "System" -> "Developer options" -> "Android debugging").
6. Download Magisk from here, and install it "adb install Magisk.apk" (replace Magisk.apk with the appropriate filename).
7. Copy Lineage recovery file to your device (for example, to the Download folder).
8. Open Magisk app on the device and tap "Install" button in the Magisk card. Choose “Select and Patch a File” in method, and select the Lineage recovery file you copied previous step.
9. The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img
10. Copy the patched image to your PC with ADB "adb pull /sdcard/Download/magisk_patched_[random_strings].img"
11. Power off device. With the device powered off, hold "Volume Up" and connect the USB cable - the notification light should turn blue (you are in the 'fastboot mode').
12. Flash patched image "fastboot flash boot /path/to/magisk_patched.img". Reboot.
13. Open Magisk app and enable 'MagiskHide'.
14. ...
15. You have root and Google's SafetyNet passes.

What is your--
LineageOS version: lineage-18.1-20210401-nightly-discovery-
LineageOS Download url:https://download.lineageos.org/discovery/changes/#!
Gapps version: NikGapps-basic-arm64-11-20210404-signed
Did you--
wipe: fresh install
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer:no
a non-stock kernel: no
other modifications: no
Navigation with gesture is bugged, has dead touch on the edges of the screen

An other bug, my phone need to reboot to charge it, cuz otherwise it won't. In battery menu say can't be charged right now.

Just upgraded from 17.1. Looks fine, everything working to this moment. Good job man, thanks for the hard work!

LuK1337, update the #2It's mandatory to remove simlock.ta file. Earlier, Newflasher did ignore (didn't flash) that file automatically. As for now - it doesn't. I just flashed my phone by your guide and now I have phone, which doesn't see simcards
I can't even imagine what to do now ...

Vlackrs said:
An other bug, my phone need to reboot to charge it, cuz otherwise it won't. In battery menu say can't be charged right now.
Click to expand...
Click to collapse
Hm. Exact same problem here :/

Dear developer
Does GPS navigation and positioning do not work?
Is there a way to improve it?

AndreyAleks said:
LuK1337, update the #2It's mandatory to remove simlock.ta file. Earlier, Newflasher did ignore (didn't flash) that file automatically. As for now - it doesn't. I just flashed my phone by your guide and now I have phone, which doesn't see simcards
I can't even imagine what to do now ...
Click to expand...
Click to collapse
False alarm. The simlock.ta is ignored just as earlier (details here). I've flashed whole stock firmware and simcards are working.

[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

reserved

reserved

What is different between this build and your previous one ?

Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available

Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.

builds have been removed from the lineage os website?

Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week

Does the build support hardware encryption or software encryption?

You should put what models this is for as to avoid confusion

just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch

Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.

CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)

First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?

Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)

is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before

Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine

Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with

Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else

Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!

Database Info

welcome