Probably?
Probably?
Interested in that. LOS 20?
What sony firmware must be installed prior to lineage os? I've tried both Android9 or Android10 but... the OS always works great actually. Maybe it's better to install first latest sony rom with flash tool and then following the guide to get Lineage OS?
I don't think that anyone is working on this. On https://github.com/LineageOS/android_device_sony_kirin/branches , there is no branch for LineageOS 20.
Dont know the reason, but having the same problem after updating to lineage 12.. therefore went back zu lineage 11.Good day. There is a model I4113 with such a problem: it does not see the mobile network. The SIM card is working, it was checked on another device. The phone sees the SIM card itself, even displays the name of the operator, but does not connect to the network, in the status bar the network icon is displayed as empty (as if there is no signal) with an exclamation mark. I thought maybe the firmware was buggy, I reflashed it to linageos - the result is the same. What could be the problem?
![]()
![]()
![]()
I had this problem on the stock version of android 10, so I guess it's not the firmware's problem.Dont know the reason, but having the same problem after updating to lineage 12.. therefore went back zu lineage 11.
Caution: some settings get lost in this process. Do proper backups!
Hello. Did the phone connect to the mobile network correctly in the past? Did it work with this SIM card in the past? Is there a possibility that it is locked to the mobile carrier?Good day. There is a model I4113 with such a problem: it does not see the mobile network. The SIM card is working, it was checked on another device. The phone sees the SIM card itself, even displays the name of the operator, but does not connect to the network, in the status bar the network icon is displayed as empty (as if there is no signal) with an exclamation mark.
The problem is that the phone was bought from hand and has not been used for a long time, and there is no connection with the previous owner. How can i check is phone locked to the mobile carrier?Hello. Did the phone connect to the mobile network correctly in the past? Did it work with this SIM card in the past? Is there a possibility that it is locked to the mobile carrier?
Writes a message: "networks not found. try again".Try to change the mobile network in the phone settings:
Settings -> Network and internet (top entry) -> SIM cards -> disable "Automatically choose the network" at the bottom. This will display (after some scanning) a list of available mobile networks.
Was the phone operator-branded in the original ROM?
adb logcat -b radio
Dont know the reason, but having the same problem after updating to lineage 12.. therefore went back zu lineage 11.Good day. There is a model I4113 with such a problem: it does not see the mobile network. The SIM card is working, it was checked on another device. The phone sees the SIM card itself, even displays the name of the operator, but does not connect to the network, in the status bar the network icon is displayed as empty (as if there is no signal) with an exclamation mark. I thought maybe the firmware was buggy, I reflashed it to linageos - the result is the same. What could be the problem?
![]()
![]()
![]()
I had this problem on the stock version of android 10, so I guess it's not the firmware's problem.Dont know the reason, but having the same problem after updating to lineage 12.. therefore went back zu lineage 11.
Caution: some settings get lost in this process. Do proper backups!
adb logcat -b radio
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:
Rom worked for month, now I have no idea whats going on but my touch screen is unresponsive, almost every seccond ghost touches, figured out that it migh be something related to kernel, I can see a lot spaming dmesg lines related to NVT-ts "number of fingers to process = 0" . Is this known bug or I have problem with touch panel?
adb root
adb shell
# the 4 commands below must be executed with the display turned on
# please post on XDA the output of these two commands - to see if this helped
> cat /proc/nvt_fw_version
> cat /proc/nvt_projectinfo
# selftests
> cat /proc/nvt_preselftest
> cat /proc/nvt_selftest
> mount / -o remount,rw
> mkdir /system/etc/firmware/
> exit
adb push SM13_KM_08_PID5403.bin /system/etc/firmware
adb shell
# verify checksum
> sha256sum /system/etc/firmware/SM13_KM_08_PID5403.bin | grep 679cfb550c04601f30021d7e22d245f4b690be12b28e7ec350eea7fbc68edc71
# do not proceed and delete the file if the checksum does not match
# remount the root partition read-only
> mount / -o remount,ro
> reboot
adb root
adb shell
> dmesg | grep -i nvt
# the commands below must be executed with the display turned on
> cat /proc/nvt_fw_version
> cat /proc/nvt_projectinfo
# selftests
> cat /proc/nvt_preselftest
> cat /proc/nvt_selftest
I4113:/proc # cat nvt_fw_version
fw_ver=4, x_num=16, y_num=36, button_num=0
I4113:/proc # cat nvt_fw_version
fw_ver=23, x_num=16, y_num=36, button_num=0
[ 0.501166] [NVT-ts][info] nvt_driver_init 2516: +++
[ 0.501196] [NVT-ts][info] nvt_ts_probe 1880: probe start
[ 0.501211] [NVT-ts][info] nvt_parse_dt 1400: novatek,irq-gpio=45
[ 0.690327] [NVT-ts][info] nvt_get_fw_info 1056: +++
[ 0.691380] [NVT-ts][info] nvt_get_fw_info 1103: ---
[ 0.691386] [NVT-ts][info] nvt_ts_probe 1943: ts->nvt_pid = 0x5403
[ 1.000332] [NVT-ts][info] nvt_ts_probe 1984: mb_hw_id = 0x01 (BY36), lcd_id = 1, source = TR M 0.8mm (0x01)
[ 1.000574] input: NVTCapacitiveTouchScreen as /devices/virtual/input/input1
[ 1.000682] [NVT-ts][info] nvt_ts_probe 2095: request irq 52 succeed
[ 1.000784] [NVT-ts][info] nvt_flash_proc_init 1264: Succeeded Create /proc/NVTflash
[ 1.000823] [NVT-ts][info] nvt_extra_proc_init 944: create extra proc node Succeeded!
[ 1.000833] [NVT-ts][info] nvt_mp_proc_init 2085: create /proc/nvt_preselftest Succeeded!
[ 1.000840] [NVT-ts][info] nvt_mp_proc_init 2094: create /proc/nvt_selftest Succeeded!
[ 1.000881] [NVT-ts][info] nvt_ts_probe 2210: probe end : success
[ 1.000919] [NVT-ts][info] nvt_driver_init 2524: ---
[ 1.002681] [NVT-ts][info] Boot_Update_Firmware 1045: +++
[ 1.002688] [NVT-ts][info] update_firmware_request 55: filename is SM13_KM_08_PID5403.bin
[ 3.530643] [NVT-ts][error] Check_CheckSum 301: RD_Filechksum[0]=0x89A7
[ 3.530658] [NVT-ts][error] Check_CheckSum 303: WR_Filechksum[0]=0xEF3E
[ 3.530662] [NVT-ts][error] Check_CheckSum 304: firmware checksum not match!!
[ 3.531019] [NVT-ts][info] Check_FW_Ver 131: IC FW Ver = 0x04, FW Ver Bar = 0xFB
[ 3.531025] [NVT-ts][info] Check_FW_Ver 134: Bin FW Ver = 0x17, FW ver Bar = 0xE8
[ 3.531030] [NVT-ts][info] Boot_Update_Firmware 1079: firmware version not match
[ 3.531034] [NVT-ts][info] Update_Firmware 889: Need upgrade TP FW
[ 10.485476] [NVT-ts][warring] nvt_ts_resume 2376: Touch is already resume
[ 11.720693] [NVT-ts][info] nvt_check_flash_end_flag 1020: nvt_end_flag = NVT (4E 56 54)
[ 11.720704] [NVT-ts][info] nvt_check_flash_end_flag 1023: "NVT" end flag found!
[ 11.790455] [NVT-ts][info] Boot_Update_Firmware 1104: TP FW upgrade finish
[ 11.790499] [NVT-ts][info] Boot_Update_Firmware 1111: ---
adb logcat -b radio