[ROM][discovery][10.0] AOSP [Sony Open Devices Project] - Sony XA2 Ultra ROMs, Kernels, Recoveries, & Other

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

Related

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's not working :
IMS
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/discovery
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][discovery][8.1] LineageOS 15.1, ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2018-11-06
Last Updated 2019-05-10
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][9] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/discovery
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][discovery][9] LineageOS 16.0, ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-03-01
Last Updated 2020-02-28
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.

[ROM][discovery][Pie][9.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, Pie flavored! 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 an initiative to build Android for phones while being as vendor binary large object (blob) free as possible. There are still a few vendor blobs used in this project, but the goal is to one day be vendor blob free. I don't know if that will ever fully happen, but it is nice to move in that direction. That said, all of my work 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.
There are two versions of the project, a vanilla AOSP without Google Apps, and a vanilla AOSP with Google Apps. I have tested both on my phone. If you want Google Apps, you cannot use the gappless version and then flash gapps, it doesn't work, you must use the gapps version if you want Google's apps.
Installation instructions: (DIFFERENT THAN NORMAL! DONE THROUGH FASTBOOT!)
- Download the zip file for AOSP 9.
- 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 Pie!
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
- Camera Button launches camera and takes photos
- MTP file transfer
etc....
What doesn't:
Code:
Gappless version:
- FM Radio does not work
- The built in Gallery app cannot play back recorded videos from camera. VLC or other apps work fine though.
- Nothing else that I know of, but let me know if you find something!
Gapps version:
- FM Radio does not work
- The built in Gallery cannot play back recorded videos from camera. VLC or other apps work fine though.
--But the Google Photos app can.
-The built in Google Camera app does not work, however, Open Camera, or other camera apps do.
- 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: 9.0 Pie
ROM Kernel: Linux 4.9.194
Based On: Android Open Source Project
Created 2019-10-03
Last Updated 2019-10-24
Changelog:
20191024
- Fixed MTP crash issue.
20191023
- Sync'd source and fresh rebuild
- Now have a "Gapps included" variant and a "Gappless" variant.
20191004
- Rebuilt kernel
- Fixed camera turning green or crashing
- Fixed general stability.
20191003
- First build, a bit unstable.
- Camera turns green.
- PTP, MTP cause crashes.
- FM Radio does not work.
Notes:
This ROM is very, very, vanilla. It is straight up AOSP. No frills, no mods, no extras. Just pure source.
I personally don't use Gapps anymore, but I did test that the gapps version boots up and connects. That's about all I test with Gapps, though.
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.
Issues/workarounds:
- Video playback from camera. Any camera videos you record work fine, but the built in player can't play them. 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/, or if you are using the Gapps included version, you can use Google Photo.
- If you are using the Gapps included variant, the built in Google Camera app does not work. However, using the playstore, I downloaded a number of camera apps, such as Open Camera, and they all worked. I'll try to look into it if I get time.
The only thing i didnt like about aosp is that you cant add features like gravitybox does. And Unfortunatly I need snapchat cause my woman uses it. lol Breaks the safety Net
Couldn't flash gapps? I'll boot into twrp and flash gapps after booting into aosp and nothing? What am I doing wrong... The is will boot and no gapps appear?
Yodasgodfather said:
Couldn't flash gapps? I'll boot into twrp and flash gapps after booting into aosp and nothing? What am I doing wrong... The is will boot and no gapps appear?
Click to expand...
Click to collapse
Good question, I'm not sure, I don't use gapps, but I could try flashing it to see tomorrow. Which gapps did you flash? Opengapps, 64 bit arm, for pie?
alaskalinuxuser said:
good question, i'm not sure, i don't use gapps, but i could try flashing it to see tomorrow. Which gapps did you flash? Opengapps, 64 bit arm, for pie?
Click to expand...
Click to collapse
64 bit nano for pie
Yodasgodfather said:
64 bit nano for pie
Click to expand...
Click to collapse
I installed AOSP, let it boot, downloaded 64 bit nano opengapps, fastbooted into TWRP, flashed the gapps via adb sideload, and rebooted. It didn't crash or hang up on me. However, I've noticed that it doesn't install the playstore app. I'm very confused. I tried this several times with pico, nano, micro, and mindthegapps.
AlaskaLinuxUser said:
I installed AOSP, let it boot, downloaded 64 bit nano opengapps, fastbooted into TWRP, flashed the gapps via adb sideload, and rebooted. It didn't crash or hang up on me. However, I've noticed that it doesn't install the playstore app. I'm very confused. I tried this several times with pico, nano, micro, and mindthegapps.
Click to expand...
Click to collapse
Thank you for looking into it? but yeah same I'm very confused as well but I believe I have found something that I'm not at all familiar with. I found this link that has someone that has a similar issue with the responder saying they can use "adb pull" command to flash Google factory images so it might be worth looking into?
https://stackoverflow.com/questions/41695566/install-google-apps-on-aosp-build
Whoo-hoo! Praise God! Good traction on Android 10! After some tinkering with XOSD source, I've got a booting version of Android 10 with the new 4.14 kernel! Certainly not a daily driver by any means yet, but I'll keep tinkering. I'll add a few teaser shots as well. :victory:
AlaskaLinuxUser said:
Whoo-hoo! Praise God! Good traction on Android 10! After some tinkering with XOSD source, I've got a booting version of Android 10 with the new 4.14 kernel! Certainly not a daily driver by any means yet, but I'll keep tinkering. I'll add a few teaser shots as well. :victory:
Click to expand...
Click to collapse
Awesome look at you go! ?
AlaskaLinuxUser said:
Whoo-hoo! Praise God! Good traction on Android 10! After some tinkering with XOSD source, I've got a booting version of Android 10 with the new 4.14 kernel! Certainly not a daily driver by any means yet, but I'll keep tinkering. I'll add a few teaser shots as well. :victory:
Click to expand...
Click to collapse
Hell yeah man. Thank God we still got one developer on the xa2 ultra threads.
So I've messed with aosp a bit and have found a way to help make things easier. I've installed nanodroid which will give you micro g and it's service and more!
https://nanolx.org/nanolx/nanodroid
I haven't been able to figure it out but it has a setup wizard as well which does give you the option to install the official play store. If any one else can't get that to work then perhaps install osm(gapps) with fdroid and install the "fakegapps" xposed module to get signiture spoofing. Hope this helps?
Yodasgodfather said:
So I've messed with aosp a bit and have found a way to help make things easier. I've installed nanodroid which will give you micro g and it's service and more!
https://nanolx.org/nanolx/nanodroid
I haven't been able to figure it out but it has a setup wizard as well which does give you the option to install the official play store. If any one else can't get that to work then perhaps install osm(gapps) with fdroid and install the "fakegapps" xposed module to get signiture spoofing. Hope this helps?
Click to expand...
Click to collapse
Great work, and good find!
I am currently building this ROM again with built in gapps ... Hopefully, I can have that and an updated version of aosp that is gappless available tomorrow or the next day (so I can test it a bit). I spoke with a few guys on the SODP telegram channel, and they make aosp with gapps built in, so I thought I'd try that to see if that helps you guys who want to use this ROM with gapps.
Good news!
I was able to build AOSP 9 with Gapps built in, and will be posing that once I get it uploaded. (It will take a long time, because I have slow internet.) I'm testing it out on my phone now, everything seems to work here. I will also be posting an update of the gappless version as well.
Thank you so much! I have been waiting for this but when do you think it will be available?
Yodasgodfather said:
Thank you so much! I have been waiting for this but when do you think it will be available?
Click to expand...
Click to collapse
Good news! It is up and posted. Be sure to fully read Post #1, and Post #2 before proceeding.
I tested both the gapps included, and the non-gapps versions on my phone, both worked. With the Gapps version I was able to connect and download several apps, my emails synced, as did photos, etc....
For this rom, the things that I am actively working on are MTP/PTP computer connections.
Also, Android 10 is still in the works, it's just giving me a few fits at the moment, but I will keep working on it. I don't want to release a "half baked" rom, I would like it to be 95%+ functional before putting it up for you to use. Hopefully, that will not take forever. :fingers-crossed:
Love it I did notice the ctsintegrity was false but I fixed it with a magisk module other than that it's great!? I understand from your last post you are working on Android 10 but any idea on when your roms will be updated to 5.0.2 version?
Great news! Praise God! With some great guidance from @MartinX3, and a post by @oshmoun, I was able to apply a patch to the kernel that fixed MTP communications for transferring files to your PC! I have the builds now, and will upload them. My internet is really slow, so it will take a while....
Great news! Praise God! With some great guidance from @MartinX3, and a post by @oshmoun, I was able to apply a patch to the kernel that fixed MTP communications for transferring files to your PC! I have the builds now, and will upload them. My internet is really slow, so it will take a while....
AlaskaLinuxUser said:
Great news! Praise God! With some great guidance from @MartinX3, and a post by @oshmoun, I was able to apply a patch to the kernel that fixed MTP communications for transferring files to your PC! I have the builds now, and will upload them. My internet is really slow, so it will take a while....
Click to expand...
Click to collapse
The new builds have been uploaded, the 20191024 builds have working MTP for file transfers, and the OP has been updated! Enjoy!

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/discovery
SemcCamera addon : https://androidfilehost.com/?w=files&flid=305730
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][discovery][10] LineageOS 17.1, ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-10-23
Last Updated 2020-04-01
[ 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][Huawei][13] LeaOS - Lineage 20.0 for Huawei device (EMUI 9.1 version)

Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"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"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage, data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update
Good news, I had just installed the 23/2/23 release and was going really good, except for the SIM card PIN request which was causing bootloop.After removed the PIN of the SIM card I was haven't any problem for the ROM which was running fine, but I could't fix a problem with mobile data which were not working even after re-set the correct APN and check with the dial number on phone info.
After all that I see the new release that I'm going to install RN.
Thanks for your work. Keep it UP!
I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?
AltairFR said:
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Click to expand...
Click to collapse
Is TWRP for Stanford (Honor 9) exist? Thanks
Smith Huang said:
Is TWRP for Stanford (Honor 9) exist? Thanks
Click to expand...
Click to collapse
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
AltairFR said:
I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?
Click to expand...
Click to collapse
Yes, It's a dual SIM phone. I have just one in it.Anyway I tried the no_gapps version and have not problem with data connection. I think is possibile it is a problem gapps related. Anyway I installed the new release with no gapps and installed LiteApp and works fine.
AltairFR said:
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks again!
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Is this project dead or is it in development
Not dead why ?
AltairFR said:
Not dead why ?
Click to expand...
Click to collapse
Oh ok cause I might install it
xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Good morning .
For partition size problems, it happens often, so I have developed a program to resize the system partition. He is on xda looking for Huawei partition tools.
For the battery I will look on my stf-l09. Have you tested with the aosp version of leaos?
For the USB problem, I did not see this problem.. thank you for the tests
Is this os pre-rooted? Cause I still wanna watch Netflix and stuff
uncognic said:
Is this os pre-rooted? Cause I still wanna watch Netflix and stuff
Click to expand...
Click to collapse
This OS have an option to pass safetynet, so you can use netflix
When i go to download recovery, im not sure which one to download between twrp-3.5.2-v1-figo-emui9.img, twrp-3.7.0_9-0-anne.img and twrp-3.7.0_9-0-anne.img. I have a Honor 9 STF-L09
With the last leaos, you can flash without twrp
Wait what. But the step-by-step giude asks me to flash twrp for a patch
uncognic said:
Wait what. But the step-by-step giude asks me to flash twrp for a patch
Click to expand...
Click to collapse
It is for drm and i don"t know if stf need
Use this twrp :
https://sourceforge.net/projects/altairfr-huawei/files/TWRP-Recovery/twrp-stf-ki960.img/download
xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Huawei Partition Kit - Enlarge system partition
Huawei Partition Kit This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls...
forum.xda-developers.com
Hi,
I gave this ROM a spin, but didn't get very far in the process documented in the FP.
First flashed TWRP from here with fastboot to recovery_ramdisk.
Code:
$ fastboot flash system LeaOS-20.0-20230304-iceows-google-stf.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/7 (460241 KB) OKAY [ 11.774s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
I also tried to flash from twrp with adb sideload, but that fails instantaneously.
And now I'm stuck with a phone that won't boot. Any suggestions how to proceed?
Btw, device is an STF-L09.

Categories

Resources