Database Info

[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][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][OFFICIAL][kirin][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/kirin
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][kirin][10] LineageOS 17.1, ROM for the Sony Xperia 10
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-02-16
Last Updated 2020-04-01

oh btw you might want to use this TWRP for flashing my builds.

LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
I didn't expect you here mr Luk. I'm gonna test it when I will be at home. I'm glad that Kirin got such a developer

Problem Resolved.
Problem Resolved.

AlexDaBoii said:
Hello! So I tried to install a custom rom called Lineage OS, version 17.1 unofficial for my SOny Xperia 10 through TWRP custom recovery. I then tried installing the GApps and then rebooted the system. Then it came up with a prompt saying that the OS was corrupted and then to factory reset it. I did just that, and then LineageOS booted up just fine. However no Google Apps could be seen. I then tried to boot in to TWRP custom recovery, however it came up with the LineageOS recovery instead. I then tried to flash TWRP and managed to get it up and running, but when I rebnooted the phone, it just brought me in a boot loop.
I tried for hours to fix it and the I finally managed to flash TWRP again, however all of my save files were gone. I then tried to flash the Stock ROM for the Xperia 10 to the "system" folder and then my device powered off. I tried to power it on again and then it came up with a prompt saying "Your device is corrupt. It can't be trusted and will not boot. Powering off in 5 sec.". I got really freaked out at this point and did not know what to do. I know that I am an idiot for doing this, but if there is any fix at all for this that anybody can tell me, then I would be very thankful.
Click to expand...
Click to collapse
If you join irc I may be able to help you:
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev

Flawless on I3123 so far. Really appreciate the work on this device.

Has somebody tried this on I3113?
Are all components working fine?

xXqepXx said:
Has somebody tried this on I3113?
Are all components working fine?
Click to expand...
Click to collapse
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.

LuK1337 said:
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.
Click to expand...
Click to collapse
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!

thesandroid said:
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!
Click to expand...
Click to collapse
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).

What gapps do you recommend? I have an i3113 and after i flashed opengapps, i always get this weird "Android setup isn't responding" "System UI Keeps crashing" thing. What can i do?

LuK1337 said:
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).
Click to expand...
Click to collapse
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.

thesandroid said:
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.
Click to expand...
Click to collapse
Yeah that doesn't sound fun. Not going to bother.
On a sidenote, next build will fix Netflix Widevine L1.

Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.

zzz00072 said:
Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.
Click to expand...
Click to collapse
You build it exactly the same you'd be building an official device.

Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
LuK1337 said:
You build it exactly the same you'd be building an official device.
Click to expand...
Click to collapse

After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
zzz00072 said:
Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
Click to expand...
Click to collapse

zzz00072 said:
After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
Click to expand...
Click to collapse
hint: themuppets.

Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
LuK1337 said:
hint: themuppets.
Click to expand...
Click to collapse

zzz00072 said:
Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
Click to expand...
Click to collapse
Yikes, you're doing so much stupid stuff...
Msg me on irc if you want it done anytime soon.

[ROM][OFFICIAL][discovery][11] LineageOS 18.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 11, 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 :
https://wiki.lineageos.org/devices/discovery
Downloads :
https://download.lineageos.org/discovery
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:

[ 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 #2​It'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 #2​It'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][10.0.0][Hima] crDroid 6.16 [Unofficial]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/AICP/kernel_htc_msm8994
Download:
ROM https://www.mediafire.com/folder/gvfujacrh306y/crDroid_10
Version 6.12 is Claymore style version, 6.16 is my style, maybe more performance on cost of battery.
Known issues:
None, tell me
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2020-11-23
Last Updated 2021-05-13

The download link of suggested twrp is here.

tombbb said:
The download link of suggested twrp is here.
Click to expand...
Click to collapse
Its already included in flashing instructions

I clean installed your ROM on my M9, and it's nice!! Thank you!

May I ask will there be build 6.1.3 for m9?

tombbb said:
May I ask will there be build 6.1.3 for m9?
Click to expand...
Click to collapse
I think yes , i will build lastest release and then iam aiminng for Crdroid 7. But for now i have to wait to get my Notebook fixed...

Hi, I try the rom and it's great, all works but signal operator. My broadband comapny is Fastweb (Italy) and the sim is ok, not broken (tested on another HTC One M9). What can it be? Any suggestion?
Thanks in advance
Update (15 Feb 2021)
weird is when I run the phone it ask me for the SIM passoword, so it seems that it seeing by the system but, if I try make a call it say: cellular broadband network not available

Marko Indaco said:
Hi, I try the rom and it's great, all works but signal operator. My broadband comapny is Fastweb (Italy) and the sim is ok, not broken (tested on another HTC One M9). What can it be? Any suggestion?
Thanks in advance
Update (15 Feb 2021)
weird is when I run the phone it ask me for the SIM passoword, so it seems that it seeing by the system but, if I try make a call it say: cellular broadband network not available
Click to expand...
Click to collapse
Ah bro when you want sigal go to APN write something save it , and then it work , its a bug in generell

platinumthis said:
Ah bro when you want sigal go to APN write something save it , and then it work , its a bug in generell
Click to expand...
Click to collapse
I already try it without success. I'll try again in a few hours but I'm feeling that dont works. I wonder what could be. I mean, I use ViperOneM9 on another HTC OneM9 and it's always works fine. No need to set APN or whatever. Even after flash/dirty flash, changing roms and then reisntall ViperOne... the signal always works perfect in this case.
Thank you for reply anyway

Changelog
* Updated to lastest Crdroid and Lineage base
* Tweaked some Performance
* ViperFX Works Out of the Box

Such a good news ! Thank you !
Is dirty flash from 6.12 to 6.16 suggested ?

It has to work when you flash

tombbb said:
Such a good news ! Thank you !
Is dirty flash from 6.12 to 6.16 suggested ?
Click to expand...
Click to collapse
Indeed

platinumthis said:
Indeed
Click to expand...
Click to collapse
I upgraded to 6.16, it is great and stable.

platinumthis said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/AICP/kernel_htc_msm8994
Download:
ROM https://www.mediafire.com/file/gcpqv6fou03pag9/crDroidAndroid-10.0-20210512-hima-v6.18.zip/file
Known issues:
None, tell me
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2020-11-23
Last Updated 2021-05-13
Click to expand...
Click to collapse
Hello, i want revert back version 6.16. It is possible?
6.18 is doing random restarts.

Sure its possible, i wil invetigate and will make a new one when i have time, lets say 10 Days

platinumthis said:
Sure its possible, i wil invetigate and will make a new one when i have time, lets say 10 Days
Click to expand...
Click to collapse
Or use only 6.16 and get there security updates. This version was really crazy in battery life. I remember also some little graphics glitches, mostly with recents, but in overall BEST custom rom for this device.

tombbb said:
I upgraded to 6.16, it is great and stable.
Click to expand...
Click to collapse
Hi Do you have v6.16 of this ROM? If yes, could you please share with us? Thanks

Arsenik013 said:
Hi Do you have v6.16 of this ROM? If yes, could you please share with us? Thanks
Click to expand...
Click to collapse
I once checked last time someone asked, but I don't have it anymore...
I don't see any bad of 7.12, maybe you try sometime?