My Samsung SM-G920F (duos) suddenly encountered general sensor failure.
Not a single sensor works except GPS and Heart Rate sensor.
When I boot into the recovery it shows me a blue screen with message "Installing system updates" shortly followed by a dead android with a yellow triangle, which I suspect is the cause of the problem.
I tried to flash it with Odin several times (using single-file and 4-files service firmware, current and the previous one) with no luck.
Recovery still tries to install something and fails.
Is this normal? How can I reset my phone to make it stop trying to install these unknown updates, which it fails to complete?
Any help would be very appreciated!
Prontiol said:
My Samsung SM-G920F (duos) suddenly encountered general sensor failure.
Not a single sensor works except GPS and Heart Rate sensor.
When I boot into the recovery it shows me a blue screen with message "Installing system updates" shortly followed by a dead android with a yellow triangle, which I suspect is the cause of the problem.
I tried to flash it with Odin several times (using single-file and 4-files service firmware, current and the previous one) with no luck.
Recovery still tries to install something and fails.
Is this normal? How can I reset my phone to make it stop trying to install these unknown updates, which it fails to complete?
Any help would be very appreciated!
Click to expand...
Click to collapse
Boot into download mode and try installing the latest Stock image through Odin. Forget about installing all the supposed updates. Then perform a full wipe. Make sure it is the latest Stock firmware, and nothing older
Snowby123 said:
Boot into download mode and try installing the latest Stock image through Odin. Forget about installing all the supposed updates. Then perform a full wipe. Make sure it is the latest Stock firmware, and nothing older
Click to expand...
Click to collapse
Did this several times, wiped cache/data, installed latest firmware available via Odin - no luck.
I tried adb logcat and there are some interesting entries in it (grepped by "sensor"):
07-04 01:16:12.960 3075 3075 D SensorHubService: nuSensorHubService starting...
07-04 01:16:12.980 3075 3075 I SensorHubService: HardwareSensorHub
07-04 01:16:12.980 3075 3075 I SensorHubService: HardwareSensorHub
07-04 01:16:12.980 3075 3075 I sensorhubservice: SensorHubService is starting now........................................
07-04 01:16:12.990 3075 3119 D SensorHubService: nuSensorHubService thread starting...
07-04 01:16:13.220 3095 3095 V lhd : SetCfgValue: LHD config "LheBbdSensor"="/dev/bbd_sensor"
07-04 01:16:13.230 3095 3095 E lhd : getCustPatchVersion: Can't open patch file /fw/SensorPatch. 2(No such file or directory)
07-04 01:16:13.230 3095 3095 D lhd : LheBbdSensor=/dev/bbd_sensor
07-04 01:16:13.230 3095 3095 D lhd : LheSensorIpc=true
07-04 01:16:17.110 3066 3066 D ExynosCameraUtils: DEBUG(getSensorIdFromFile[1920]):Sensor name is 10
07-04 01:16:17.110 3066 3066 I ExynosCamera3SensorInfo: createCamera3SensorInfo[39] sensor ID(10)
07-04 01:16:17.110 3066 3066 D ExynosCameraUtils: DEBUG(getSensorIdFromFile[1920]):Sensor name is 21
07-04 01:16:17.110 3066 3066 I ExynosCamera3SensorInfo: createCamera3SensorInfo[39] sensor ID(21)
07-04 01:16:22.120 3512 3512 D SensorService: nuSensorService starting...
07-04 01:16:22.120 3512 3512 I Sensors : getName:gyro_sensor name = MPU6500.
07-04 01:16:22.120 3512 3512 I Sensors : Proximity old sensor_state 0, new sensor_state : 128 en : 1
07-04 01:16:22.120 3512 3512 E Sensors : ProximitySensor write failed. ret = -1, sensor_state = 128
07-04 01:16:22.120 3512 3512 I Sensors : Light old sensor_state 0, new sensor_state : 512 en : 1
07-04 01:16:22.120 3512 3512 E Sensors : LightSensor write failed. ret = -1, sensor_state = 512
07-04 01:16:22.120 3512 3512 I Sensors : Light_IR old sensor_state 0, new sensor_state : 16777216 en : 1
07-04 01:16:22.120 3512 3512 E Sensors : Light_IR_Sensor write failed. ret = -1, sensor_state = 16777216
07-04 01:16:22.130 3512 3512 I Sensors : SigMotionSensor old sensor_state 0, new sensor_state : 16384 en : 1
07-04 01:16:22.130 3512 3512 E Sensors : SigMotionSensor write failed. ret = -1, sensor_state = 16384
07-04 01:16:22.130 3512 3512 I Sensors : getName:gyro_sensor name = MPU6500.
07-04 01:16:22.130 3512 3512 I Sensors : StepCounterSensor old sensor_state 0, new sensor_state : 262144 en : 1
07-04 01:16:22.130 3512 3512 E Sensors : StepCounterSensor write failed. ret = -1, sensor_state = 262144
07-04 01:16:22.130 3512 3512 I Sensors : Int.Gyro old sensor_state 0, new sensor_state : 33554432 en : 1
07-04 01:16:22.130 3512 3512 E Sensors : Int.GyroSensor write failed. ret = -1, sensor_state = 33554432
07-04 01:16:22.130 3512 3512 I Sensors : getName:gyro_sensor name = MPU6500.
07-04 01:16:22.130 3512 3512 I Sensors : HrmSpO2Sensor:: part type = 3.
07-04 01:16:22.130 3512 3512 D Sensors : HrmSpO2Sensor::type:3, prox threshold:2000
07-04 01:16:22.130 3512 3512 D Sensors : HrmSpO2Sensor::handle:0 ,en:1
07-04 01:16:22.130 3512 3512 D Sensors : HrmSpO2Sensor::HrmSpO2Sensor: Shared version Registered
07-04 01:16:22.130 3512 3512 D Sensors : HrmLedSensor enable: mEnabled 0, handle 20, en 1
07-04 01:16:22.130 3512 3512 D Sensors : HRMSensor led enabled:1, en:1
07-04 01:16:22.130 3512 3512 I Sensors : getVendor:hrm_sensor vendor = MAXIM.
07-04 01:16:22.130 3512 3512 I Sensors : HrmLedSensor: HrmLedSensor vendor = MAXIM.
07-04 01:16:22.140 3512 3512 D Sensors : HRMSensor_LED::libhr open start!!
07-04 01:16:22.140 3512 3512 I Sensors : Grip old sensor_state 0, new sensor_state : 2048 en : 1
07-04 01:16:22.140 3512 3512 E Sensors : GripSensor write failed. ret = -1, sensor_state = 2048
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::handle:19 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::isEnabled:0 ,en:0, mEn:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::handle:28 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::isEnabled:0 ,en:0, mEn:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmLedSensor enable: mEnabled 1, handle 20, en 0
07-04 01:16:22.140 3512 3512 D Sensors : HRMSensor_LED::enable
07-04 01:16:22.140 3512 3512 E Sensors : HRMSensor_LED::close_agc
07-04 01:16:22.140 3512 3512 D Sensors : HRMSensor led enabled:0, en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmLedSensor enable: mEnabled 0, handle 21, en 0
07-04 01:16:22.140 3512 3512 D Sensors : HrmLedSensor isEnabled:0 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::handle:18 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::isEnabled:0 ,en:0, mEn:0
07-04 01:16:22.140 3512 3512 D SensorService: [SO] ScreenOrientationSensor Registered!
07-04 01:16:22.140 3512 3512 D SensorService: HRMFusion :: libhr opened
07-04 01:16:22.140 3512 3512 D SensorService: HRMFusion_maxim::HRMFusion_maxim: Shared version Registered
07-04 01:16:22.140 3512 3512 D SensorService: HRMSensor::can not find Cal_HR
07-04 01:16:22.140 3512 3512 D SensorService: HRMSensor::can not find setModelNumber
07-04 01:16:22.140 3512 3512 D SensorService: HRMFusion_adi::HRMFusion_adi: Shared version Registered
07-04 01:16:22.140 3512 3512 D SensorService: OrientationSensor2 Registered!!!!
07-04 01:16:22.140 3512 3512 D SensorService: GravitySensor2 Registered!!!!
07-04 01:16:22.140 3512 3512 D SensorService: GravitySensor2 Registered!!!!
07-04 01:16:22.140 3512 3512 D SensorService: LinearAccelerationSensor2 Registered!!!!
07-04 01:16:22.140 3512 3924 D SensorService: nuSensorService thread starting...
07-04 01:16:22.140 3512 3923 D SensorService: new thread SensorEventAckReceiver
07-04 01:16:22.690 3512 3512 D SensorHubManager: sensorhubs_module_init()
07-04 01:16:22.690 3512 3512 E SensorHubManager: JNI: sensorhubs_get_next_module: getSensorHubList: count= 2
07-04 01:16:22.690 3512 3512 D SensorHubManager: Num SensorHub= 1
07-04 01:16:22.690 3512 3512 D SensorHubManager: found sensorhub= SensorHub, handle=0
07-04 01:16:22.690 3512 3512 E SensorHubManager: JNI: sensorhubs_get_next_module: getSensorHubList: count= 2
07-04 01:16:22.690 3512 3512 D SensorHubManager: Num SensorHub= 0
07-04 01:16:22.690 3512 3512 D SensorHubManager: found sensorhub= Gesture Sensor, handle=1
07-04 01:16:22.690 3512 3512 D SensorHubManager: registerListener: handle= 0 delay= 0 Listener= com.samsung.android.contex[email protected]7958a3
07-04 01:16:22.690 3512 3958 D SensorHubManager: =======>>> SensorHubManager Thread RUNNING <<<=======
07-04 01:16:22.690 3512 3512 E SensorHubManager: JNI: sensorhubs_enabledisable: delay= 0
07-04 01:16:22.690 3075 3075 D SensorHubService: SensorHubEventConnection: setEventRate : ns= 0
07-04 01:16:22.690 3075 3075 D SensorHubService: setEventRate: minDelay before ns= 0
07-04 01:16:22.690 3075 3075 D SensorHubService: setEventRate: ns= 1000000
07-04 01:16:22.740 3512 3965 E MotionRecognitionService: ASensorManager_getInstance
07-04 01:16:22.740 3512 3965 D SensorService: SensorEventConnection::SocketBufferSize, SystemSocketBufferSize - 102400, 2097152
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRM Ambient Light Canceling) without holding its required permission: com.samsung.permission.HRM_EXT
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRM Ambient Light Canceling because it requires permission com.samsung.permission.HRM_EXT and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRM Proximity detecting) without holding its required permission: com.samsung.permission.HRM_EXT
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRM Proximity detecting because it requires permission com.samsung.permission.HRM_EXT and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRMLED IR) without holding its required permission: android.permission.BODY_SENSORS
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRMLED IR because it requires permission android.permission.BODY_SENSORS and app op 56
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRMLED RED) without holding its required permission: android.permission.BODY_SENSORS
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRMLED RED because it requires permission android.permission.BODY_SENSORS and app op 56
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (MAX86900) without holding its required permission: com.samsung.permission.SSENSOR
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor MAX86900 because it requires permission com.samsung.permission.SSENSOR and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRM Sensor) without holding its required permission: com.samsung.permission.SSENSOR
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRM Sensor because it requires permission com.samsung.permission.SSENSOR and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HeartRate Sensor) without holding its required permission: android.permission.BODY_SENSORS
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HeartRate Sensor because it requires permission android.permission.BODY_SENSORS and app op 56
07-04 01:17:00.957 3095 3095 E lhd : <EswCrash Assert="C:\p4view\Zero_BRCM_M_upgrade\MCU\Project\SSP_SensorHub\SH_Main.c" line="76" Arg2="0x82838E" Arg3="0x0" Arg4="0x0" ts="1426781">
It appears that all the sensors are failing at once, according to the log cat. I am out of ideas on how to fix it. If it is still under warranty I would replace it. Maybe someone else has alternative ideas?
I am currently very far from home and can't replace it by warranty, so trying to fix it by myself somehow.
What I found out currently:
*#2663# shows:
SensorHub MCU FW Version: BRO010
SensorHUB BIN FW Version: BRO116040600
I believe they should be the same. I checked this on the brand new phone in the local store and they are the same.
There is a button "SensorHub FW Update" but it is greyed out, so I don't know, how to update it manually.
Also, looks like entering into the recovery starts SensorHub update via i2c bus, but failed with this which causes the problem.
So, looking for a way to forcibly update SensorHub Firmware via adb or secret code or whatever else I could find.
Prontiol said:
I am currently very far from home and can't replace it by warranty, so trying to fix it by myself somehow.
What I found out currently:
*#2663# shows:
SensorHub MCU FW Version: BRO010
SensorHUB BIN FW Version: BRO116040600
I believe they should be the same. I checked this on the brand new phone in the local store and they are the same.
There is a button "SensorHub FW Update" but it is greyed out, so I don't know, how to update it manually.
Also, looks like entering into the recovery starts SensorHub update via i2c bus, but failed with this which causes the problem.
So, looking for a way to forcibly update SensorHub Firmware via adb or secret code or whatever else I could find.
Click to expand...
Click to collapse
Please let me know if you managed to fix this, as I have the very same problem here
CpaoV said:
Please let me know if you managed to fix this, as I have the very same problem here
Click to expand...
Click to collapse
So, its 2018 now, and i have the same problem(exactly the same actualy) on my brand new s7, any news? did you take it to warranty service?
Prontiol said:
Did this several times, wiped cache/data, installed latest firmware available via Odin - no luck.
I tried adb logcat and there are some interesting entries in it (grepped by "sensor"):
07-04 01:16:12.960 3075 3075 D SensorHubService: nuSensorHubService starting...
07-04 01:16:12.980 3075 3075 I SensorHubService: HardwareSensorHub
07-04 01:16:12.980 3075 3075 I SensorHubService: HardwareSensorHub
07-04 01:16:12.980 3075 3075 I sensorhubservice: SensorHubService is starting now........................................
07-04 01:16:12.990 3075 3119 D SensorHubService: nuSensorHubService thread starting...
07-04 01:16:13.220 3095 3095 V lhd : SetCfgValue: LHD config "LheBbdSensor"="/dev/bbd_sensor"
07-04 01:16:13.230 3095 3095 E lhd : getCustPatchVersion: Can't open patch file /fw/SensorPatch. 2(No such file or directory)
07-04 01:16:13.230 3095 3095 D lhd : LheBbdSensor=/dev/bbd_sensor
07-04 01:16:13.230 3095 3095 D lhd : LheSensorIpc=true
07-04 01:16:17.110 3066 3066 D ExynosCameraUtils: DEBUG(getSensorIdFromFile[1920]):Sensor name is 10
07-04 01:16:17.110 3066 3066 I ExynosCamera3SensorInfo: createCamera3SensorInfo[39] sensor ID(10)
07-04 01:16:17.110 3066 3066 D ExynosCameraUtils: DEBUG(getSensorIdFromFile[1920]):Sensor name is 21
07-04 01:16:17.110 3066 3066 I ExynosCamera3SensorInfo: createCamera3SensorInfo[39] sensor ID(21)
07-04 01:16:22.120 3512 3512 D SensorService: nuSensorService starting...
07-04 01:16:22.120 3512 3512 I Sensors : getName:gyro_sensor name = MPU6500.
07-04 01:16:22.120 3512 3512 I Sensors : Proximity old sensor_state 0, new sensor_state : 128 en : 1
07-04 01:16:22.120 3512 3512 E Sensors : ProximitySensor write failed. ret = -1, sensor_state = 128
07-04 01:16:22.120 3512 3512 I Sensors : Light old sensor_state 0, new sensor_state : 512 en : 1
07-04 01:16:22.120 3512 3512 E Sensors : LightSensor write failed. ret = -1, sensor_state = 512
07-04 01:16:22.120 3512 3512 I Sensors : Light_IR old sensor_state 0, new sensor_state : 16777216 en : 1
07-04 01:16:22.120 3512 3512 E Sensors : Light_IR_Sensor write failed. ret = -1, sensor_state = 16777216
07-04 01:16:22.130 3512 3512 I Sensors : SigMotionSensor old sensor_state 0, new sensor_state : 16384 en : 1
07-04 01:16:22.130 3512 3512 E Sensors : SigMotionSensor write failed. ret = -1, sensor_state = 16384
07-04 01:16:22.130 3512 3512 I Sensors : getName:gyro_sensor name = MPU6500.
07-04 01:16:22.130 3512 3512 I Sensors : StepCounterSensor old sensor_state 0, new sensor_state : 262144 en : 1
07-04 01:16:22.130 3512 3512 E Sensors : StepCounterSensor write failed. ret = -1, sensor_state = 262144
07-04 01:16:22.130 3512 3512 I Sensors : Int.Gyro old sensor_state 0, new sensor_state : 33554432 en : 1
07-04 01:16:22.130 3512 3512 E Sensors : Int.GyroSensor write failed. ret = -1, sensor_state = 33554432
07-04 01:16:22.130 3512 3512 I Sensors : getName:gyro_sensor name = MPU6500.
07-04 01:16:22.130 3512 3512 I Sensors : HrmSpO2Sensor:: part type = 3.
07-04 01:16:22.130 3512 3512 D Sensors : HrmSpO2Sensor::type:3, prox threshold:2000
07-04 01:16:22.130 3512 3512 D Sensors : HrmSpO2Sensor::handle:0 ,en:1
07-04 01:16:22.130 3512 3512 D Sensors : HrmSpO2Sensor::HrmSpO2Sensor: Shared version Registered
07-04 01:16:22.130 3512 3512 D Sensors : HrmLedSensor enable: mEnabled 0, handle 20, en 1
07-04 01:16:22.130 3512 3512 D Sensors : HRMSensor led enabled:1, en:1
07-04 01:16:22.130 3512 3512 I Sensors : getVendor:hrm_sensor vendor = MAXIM.
07-04 01:16:22.130 3512 3512 I Sensors : HrmLedSensor: HrmLedSensor vendor = MAXIM.
07-04 01:16:22.140 3512 3512 D Sensors : HRMSensor_LED::libhr open start!!
07-04 01:16:22.140 3512 3512 I Sensors : Grip old sensor_state 0, new sensor_state : 2048 en : 1
07-04 01:16:22.140 3512 3512 E Sensors : GripSensor write failed. ret = -1, sensor_state = 2048
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::handle:19 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::isEnabled:0 ,en:0, mEn:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::handle:28 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::isEnabled:0 ,en:0, mEn:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmLedSensor enable: mEnabled 1, handle 20, en 0
07-04 01:16:22.140 3512 3512 D Sensors : HRMSensor_LED::enable
07-04 01:16:22.140 3512 3512 E Sensors : HRMSensor_LED::close_agc
07-04 01:16:22.140 3512 3512 D Sensors : HRMSensor led enabled:0, en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmLedSensor enable: mEnabled 0, handle 21, en 0
07-04 01:16:22.140 3512 3512 D Sensors : HrmLedSensor isEnabled:0 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::handle:18 ,en:0
07-04 01:16:22.140 3512 3512 D Sensors : HrmSpO2Sensor::isEnabled:0 ,en:0, mEn:0
07-04 01:16:22.140 3512 3512 D SensorService: [SO] ScreenOrientationSensor Registered!
07-04 01:16:22.140 3512 3512 D SensorService: HRMFusion :: libhr opened
07-04 01:16:22.140 3512 3512 D SensorService: HRMFusion_maxim::HRMFusion_maxim: Shared version Registered
07-04 01:16:22.140 3512 3512 D SensorService: HRMSensor::can not find Cal_HR
07-04 01:16:22.140 3512 3512 D SensorService: HRMSensor::can not find setModelNumber
07-04 01:16:22.140 3512 3512 D SensorService: HRMFusion_adi::HRMFusion_adi: Shared version Registered
07-04 01:16:22.140 3512 3512 D SensorService: OrientationSensor2 Registered!!!!
07-04 01:16:22.140 3512 3512 D SensorService: GravitySensor2 Registered!!!!
07-04 01:16:22.140 3512 3512 D SensorService: GravitySensor2 Registered!!!!
07-04 01:16:22.140 3512 3512 D SensorService: LinearAccelerationSensor2 Registered!!!!
07-04 01:16:22.140 3512 3924 D SensorService: nuSensorService thread starting...
07-04 01:16:22.140 3512 3923 D SensorService: new thread SensorEventAckReceiver
07-04 01:16:22.690 3512 3512 D SensorHubManager: sensorhubs_module_init()
07-04 01:16:22.690 3512 3512 E SensorHubManager: JNI: sensorhubs_get_next_module: getSensorHubList: count= 2
07-04 01:16:22.690 3512 3512 D SensorHubManager: Num SensorHub= 1
07-04 01:16:22.690 3512 3512 D SensorHubManager: found sensorhub= SensorHub, handle=0
07-04 01:16:22.690 3512 3512 E SensorHubManager: JNI: sensorhubs_get_next_module: getSensorHubList: count= 2
07-04 01:16:22.690 3512 3512 D SensorHubManager: Num SensorHub= 0
07-04 01:16:22.690 3512 3512 D SensorHubManager: found sensorhub= Gesture Sensor, handle=1
07-04 01:16:22.690 3512 3512 D SensorHubManager: registerListener: handle= 0 delay= 0 Listener= com.samsung.android.contex[email protected]7958a3
07-04 01:16:22.690 3512 3958 D SensorHubManager: =======>>> SensorHubManager Thread RUNNING <<<=======
07-04 01:16:22.690 3512 3512 E SensorHubManager: JNI: sensorhubs_enabledisable: delay= 0
07-04 01:16:22.690 3075 3075 D SensorHubService: SensorHubEventConnection: setEventRate : ns= 0
07-04 01:16:22.690 3075 3075 D SensorHubService: setEventRate: minDelay before ns= 0
07-04 01:16:22.690 3075 3075 D SensorHubService: setEventRate: ns= 1000000
07-04 01:16:22.740 3512 3965 E MotionRecognitionService: ASensorManager_getInstance
07-04 01:16:22.740 3512 3965 D SensorService: SensorEventConnection::SocketBufferSize, SystemSocketBufferSize - 102400, 2097152
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRM Ambient Light Canceling) without holding its required permission: com.samsung.permission.HRM_EXT
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRM Ambient Light Canceling because it requires permission com.samsung.permission.HRM_EXT and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRM Proximity detecting) without holding its required permission: com.samsung.permission.HRM_EXT
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRM Proximity detecting because it requires permission com.samsung.permission.HRM_EXT and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRMLED IR) without holding its required permission: android.permission.BODY_SENSORS
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRMLED IR because it requires permission android.permission.BODY_SENSORS and app op 56
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRMLED RED) without holding its required permission: android.permission.BODY_SENSORS
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRMLED RED because it requires permission android.permission.BODY_SENSORS and app op 56
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (MAX86900) without holding its required permission: com.samsung.permission.SSENSOR
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor MAX86900 because it requires permission com.samsung.permission.SSENSOR and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HRM Sensor) without holding its required permission: com.samsung.permission.SSENSOR
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HRM Sensor because it requires permission com.samsung.permission.SSENSOR and app op -1
07-04 01:17:00.737 3512 4555 E SensorService: getSensorList a sensor (HeartRate Sensor) without holding its required permission: android.permission.BODY_SENSORS
07-04 01:17:00.737 3512 4555 I SensorService: Skipped sensor HeartRate Sensor because it requires permission android.permission.BODY_SENSORS and app op 56
07-04 01:17:00.957 3095 3095 E lhd : <EswCrash Assert="C:\p4view\Zero_BRCM_M_upgrade\MCU\Project\SSP_SensorHub\SH_Main.c" line="76" Arg2="0x82838E" Arg3="0x0" Arg4="0x0" ts="1426781">
Click to expand...
Click to collapse
ViniciusSilvestre said:
So, its 2018 now, and i have the same problem(exactly the same actualy) on my brand new s7, any news? did you take it to warranty service?
Click to expand...
Click to collapse
That is odd that they would do that all at once though. Sounds like a bad OTA. Sounds like someone slipped in a modded FOTA. It's been known to happen, and been known to completly break devices like this as well. Very Interesting indeed. Not even the Combination Firmware Helps?
Did this start happening after an Update or after you flashed a new firmware? Or did it start just by simply entering recovery mode with no modifications done previously?
Delgoth said:
That is odd that they would do that all at once though. Sounds like a bad OTA. Sounds like someone slipped in a modded FOTA. It's been known to happen, and been known to complete break devices like this as well. Very Interesting indeed. Not even the Combination Firmware Helps?
Did this start happening after an Update or after you flashed a new firmware? Or did it start just by simply entering recovery mode with no modifications done previously?
Click to expand...
Click to collapse
In my case it was after an ota update (not so much) I updated, everything went fine until i rebooted it a few days later, the same blue screen the op described popped up, and failed to update.
When i noticed the problem, i flashed the stock firmware using odin, (it didnt trip knox since it was a bone stock firmware downloaded from sammobile) to see if the problem would go away, needless to say it didnt. After 4 hard resets, 3 firmware flashes and an oreo update (all official, trying to preserve warranty) still the same
Combination Firmware: sorry for noob, but i didint catch this one
ViniciusSilvestre said:
In my case it was after an ota update (not so much) I updated, everything went fine until i rebooted it a few days later, the same blue screen the op described popped up, and failed to update.
When i noticed the problem, i flashed the stock firmware using odin, (it didnt trip knox since it was a bone stock firmware downloaded from sammobile) to see if the problem would go away, needless to say it didnt. After 4 hard resets, 3 firmware flashes and an oreo update (all official, trying to preserve warranty) still the same
Combination Firmware: sorry for noob, but i didint catch this one
Click to expand...
Click to collapse
Combination Firmware, or Factory Binaries, are signed by the OEM, they do not trip Knox. They are official builds, albeit factory builds without all the normal phone capabilities. they are normally used in phone repairs. They can fix all kinds of DRK, DM-Verity, and APN errors. After flashing it successfully and having it boot up initially. Reinstall a stock official rom fresh. Use the repartition and nand erase all options in ODIN when flashing the factory binary if you can. In addition to F.Reset Time and Autoreboot.
PS> I would steer very clear of that OTA build, and the one before it. You don't want that OTA even if you can get it to flash successfully.
Delgoth said:
Combination Firmware, or Factory Binaries, are signed by the OEM, they do not trip Knox. They are official builds, albeit factory builds without all the normal phone capabilities. they are normally used in phone repairs. They can fix all kinds of DRK, DM-Verity, and APN errors. After flashing it successfully and having it boot up initially. Reinstall a stock official rom fresh. Use the repartition and nand erase all options in ODIN when flashing the factory binary if you can. In addition to F.Reset Time and Autoreboot.
PS> I would steer very clear of that OTA build, and the one before it. You don't want that OTA even if you can get it to flash successfully.
Click to expand...
Click to collapse
I didint even know this existed, it might actually fix it , i will try today and get back here when im done.
Yep, never flash that ota ever again
Thank's
Little update, i couldnt find a new combination firmware, and the one that i found allways spits out an error due to sboot bin, i think im just gonna send it to samsung and see what they will do
ViniciusSilvestre said:
I didint even know this existed, it might actually fix it , i will try today and get back here when im done.
Yep, never flash that ota ever again
Thank's
Little update, i couldnt find a new combination firmware, and the one that i found allways spits out an error due to sboot bin, i think im just gonna send it to samsung and see what they will do
Click to expand...
Click to collapse
What build did you have Installed before trying to flash the combination?
Delgoth said:
What build did you have Installed before trying to flash the combination?
Click to expand...
Click to collapse
Now i have G930FXXU2ERD5 (oreo from uk). I think most likely it is not alowing me because it is a downgrade, combination is 6.0
ViniciusSilvestre said:
Now i have G930FXXU2ERD5 (oreo from uk). I think most likely it is not alowing me because it is a downgrade, combination is 6.0
Click to expand...
Click to collapse
It is the bootloader version installed. you have Revision 2. That's normally the problem when it errors on the sboot.
Did you try to install The Combination Firmware: G930FXXU2ARA2?
Delgoth said:
It is the bootloader version installed. you have Revision 2. That's normally the problem when it errors on the sboot.
Did you try to install The Combination Firmware: G930FXXU2ARA2?
Click to expand...
Click to collapse
The only places i found that version, were behind a paywall, i though it wouldnt matter but i was wrong
ViniciusSilvestre said:
The only places i found that version, were behind a paywall, i though it wouldnt matter but i was wrong
Click to expand...
Click to collapse
It might be out there somewhere else still. But you will need a revision 2 factory binary, since that's what's installed right now.
EDIT: I did find it for free. Hope it helps.
Delgoth said:
It might be out there somewhere else still. But you will need a revision 2 factory binary, since that's what's installed right now.
EDIT: I did find it for free. Hope it helps.
Click to expand...
Click to collapse
Well, you deserve an update, i ended up taking it to samsung, they say they are replacing the mobo ("basicaly" a new device i guess) i didnt try the combination firmware, i think it might still work as a potential fix, but seeing that sammy themselves are going to replace the mobo i dont know
I really thank you for all your help
ViniciusSilvestre said:
Well, you deserve an update, i ended up taking it to samsung, they say they are replacing the mobo ("basicaly" a new device i guess) i didnt try the combination firmware, i think it might still work as a potential fix, but seeing that sammy themselves are going to replace the mobo i dont know
I really thank you for all your help
Click to expand...
Click to collapse
I would say sad times, but if you actually have the F version of the device, then it's actually a good thing Samsung is fixing it. At least The S6 F Versions are unlocked fully.
Delgoth said:
I would say sad times, but if you actually have the F version of the device, then it's actually a good thing Samsung is fixing it. At least The S6 F Versions are unlocked fully.
Click to expand...
Click to collapse
Thats one good thing about brazil laws, a few years ago, carriers were prohibited to lock any phone, all phones are fully unlocked, i havent seen any phone that you cant unlock the bootloader and you can pop any sim card in and it will work
Hello,
I just have a question, my Xperia 1 was unlocked and rooted (magisk) on Android 10.
Yesterday, I decided to lock the bootloader, everything was erased from the phone after that. The new Android installation was buggy so I tried to restore the phone using Xperia Companion.
After the restore using Xperia Companion, Now everything is working fine and I was really surprised, my DRM keys are back, I have "L1" using the DRM info app and I can watch Netflix HD content and Amazon Prime Video HD content.
How is that possible ? I thought that by unlocking the bootloader, the DRM keys are lost forever ?
Hmmm do you have any proof?
Hello,
Yes, please see my old messages, I succesfully unlocked ans rooted the device. Now see the screenshot below.
https://ibb.co/7RH2ZdG
Check with *#*#7378423#*#*
Then service info>security
Then see if any ........XXXXX error and share the screenshot.
Thanks
Hello, thanks for your Reply.
It seems that there is No error, but I have confirmation that thé device has already be unlocked
https://imgshare.io/image/screenshot-20200412-1650532.4yP8t
By thé way, i also recieved an OTAsoftware uppgrade. So this is now working too.
titigunner01 said:
By thé way, i also recieved an OTAsoftware uppgrade. So this is now working too.
Click to expand...
Click to collapse
You can receive OTA if you have just locked the bootloader.
But the things in Screenshot looks great. It was a previous way of checking the DRM keys and I don't know if only these things verify the DRM keys in latest versions too.
Is it a matter that the phone restores the DRM under locked bootloader again in Sony or did they remove the DRMs?
But what it matters is you are using apps and things like you have the DRM so may be thats good.:good:
So, after you restored stock ROM, also the boot message "can't be checked for corruption" is gone?
Yes, no message when booting.
Very strange, i wanted to know if everyone else noticed thé same thing.
titigunner01 said:
Yes, no message when booting.
Very strange, i wanted to know if everyone else noticed thé same thing.
Click to expand...
Click to collapse
Eventually I will try on my Xperia 10 II. Hope I have the same luck, thanks!
titigunner01 said:
Hello,
I just have a question, my Xperia 1 was unlocked and rooted (magisk) on Android 10.
Yesterday, I decided to lock the bootloader, everything was erased from the phone after that. The new Android installation was buggy so I tried to restore the phone using Xperia Companion.
After the restore using Xperia Companion, Now everything is working fine and I was really surprised, my DRM keys are back, I have "L1" using the DRM info app and I can watch Netflix HD content and Amazon Prime Video HD content.
How is that possible ? I thought that by unlocking the bootloader, the DRM keys are lost forever ?
Click to expand...
Click to collapse
did you lock the bootloader with flashtool?
I just want to do it too, but can`t I find a guide for xperia 1
No i locked the bootloader using command lines.
Maybe this will work also using Flashtool, Im not sure.
titigunner01 said:
No i locked the bootloader using command lines.
Maybe this will work also using Flashtool, Im not sure.
Click to expand...
Click to collapse
you using this commands?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
fastboot reboot
if not, can you describe step by step how you did it?
I will
thankful to you!
Hello,
Yes, if I remember well, on fastboot mode, i used fastboot oem lock.
After the reboot of the phone, everything was reased. The new installation was really buggy so after that I recovered using Xperia Companion.
interesting - I am wondering if sony still uses the device key in TA 66667 unit and if it gets erased with the first unlock or not.
Deleted
Relock the bootloader, repair with xperia companion and drm keys are back.
Only on xperia 1, 5 and up !
Beware: even though it may look all keys are back, it is still questionable if some function/feature is not permanently missing.
I did some research and it seems xperia 1 bootloader ABL does erase device key, i.e. TA 66667 (0x1046b) unit, on unlock.
So in my opinion even though you can relock and everything looks normal, the device key gets never back.
The question is what (drm) functions are connected to it.
Here more details:
Just extracted abl from J9110_10_55.1.A.0.748_PLUSPL, posted it here:
xperia-1-J9110-55.1.A.0.748-LA2_0_Q_114-ABL-LinuxLoader.zip
Just observing the strings in it, I am not trusting SONY at all with the re-lock of xperia-1:
Code:
$ strings -a LA2_0_Q_114-ABL-LinuxLoader.pe | grep -i 'device key\|[ _]dk'
Size of device key is too large (%d > %d)
Device key is not set, setting to zero
get_dk returned err=%d
Unable to delete dk
get_hwconf_dk returned err=%d
Device Key MiscTA unit size is zero
Failed to allocate memory for Device Key
Device keys not of equal length!
hwconf_x_parser_get_hwc_dk returned err=%d
Device Key length in HWConfig is zero
Failed to get size of TA_DK_NUMBER_UNIT
Failed to delete DK
This looks very similar to stuff implemented in xz1c ABL related to unlock and TA unit 66667 (0x1046b) containing the device key erased with bootloader unlock!
You may also observe if the message "Device key is not set, setting to zero" is present in bootloader log that is stored in 0x802 TA unit (and few other following units containing older boots).
It would be interesting to test TA backup, unlock, relock, TA restore, so that device key would be back.
This tells everything:
From i d a can't see 1046b but see the same function at the bottom (ghidra output)
Code:
void sub_4DDE4()
{
int v0; // w0
__int64 v1; // x3
__int64 v2; // x4
__int64 v3; // x5
__int64 v4; // x6
__int64 v5; // x7
__int64 v6; // x0
__int64 v7; // x1
const char *v8; // x0
__int64 v9; // x2
__int64 v10; // x0
char v11; // zf
int v12; // w0
__int64 v13; // x0
__int64 v14; // x0
unsigned int v15; // w1
__int64 v16; // x2
__int64 v17; // x3
_DWORD *v18; // x4
__int64 v19; // x5
__int64 v20; // x6
__int64 v21; // x7
signed int v22; // [xsp+4h] [xbp-2Ch]
sub_440B4();
if ( v0 )
{
sub_4DF70();
v7 = v6;
v8 = "[ERROR @ %s:%d]:\nFailed to get size of TA_DK_NUMBER_UNIT\n";
v9 = 303i64;
}
else
{
if ( v22 < 1 )
goto LABEL_4;
sub_44318();
if ( !v12 )
goto LABEL_4;
sub_4DF70();
v7 = v13;
v8 = "[ERROR @ %s:%d]:\nFailed to delete DK\n";
v9 = 310i64;
}
sub_589A0(v8, v7, v9, v1, v2, v3, v4, v5);
LABEL_4:
sub_4DF5C();
if ( !v11 )
{
sub_14468(v10);
sub_4DE94(v14, v15, v16, v17, v18, v19, v20, v21);
}
}
Code:
sub_4110C();
[B][COLOR="Red"]sub_4DDE4();[/COLOR][/B]
if ( v0 )
{
sub_41100();
sub_589A0("[ERROR @ %s:%d]:\nUnable to delete dk\n", v1, 1438i64, v2, v3, v4, v5, v6);
goto LABEL_10;
}
sub_3ED48();
if ( !v7 )
{
sub_41100();
sub_589A0("[ERROR @ %s:%d]:\nFailed to delete user sensitive partitions\n", v18, 1443i64, v19, v20, v21, v22, v23);
goto LABEL_10;
}
sub_3EE20();
if ( v8 )
{
sub_41100();
v15 = v14;
v16 = "[ERROR @ %s:%d]:\nFailed to reset rollback counters, error:%d\n";
v17 = 1451i64;
}
else
{
sub_3EDF0();
if ( !v24 )
goto LABEL_10;
sub_41100();
v15 = v25;
v16 = "[ERROR @ %s:%d]:\n[B][COLOR="Red"]Failed to lock the bootloader: [/COLOR][/B]%d\n";
v17 = 1457i64;
}
ghidra
Code:
ulonglong FUN_0005dde4(void)
{
bool in_ZR;
undefined uVar1;
ulonglong uVar2;
undefined8 extraout_x0;
undefined8 local_28;
undefined8 extraout_x0_00;
undefined8 uVar3;
undefined *puVar4;
undefined uVar5;
undefined8 in_x3;
undefined7 uVar6;
undefined uVar7;
undefined8 in_x4;
undefined7 uVar8;
undefined uVar9;
undefined8 in_x5;
undefined7 uVar10;
undefined uVar11;
undefined8 in_x6;
undefined7 uVar12;
undefined uVar13;
undefined8 in_x7;
undefined7 uVar14;
ulonglong uVar15;
undefined in_stack_ffffffffffffffd0;
undefined uVar16;
int local_2c;
uVar14 = (undefined7)((ulonglong)in_x7 >> 8);
uVar13 = (undefined)in_x7;
uVar12 = (undefined7)((ulonglong)in_x6 >> 8);
uVar11 = (undefined)in_x6;
uVar10 = (undefined7)((ulonglong)in_x5 >> 8);
uVar9 = (undefined)in_x5;
uVar8 = (undefined7)((ulonglong)in_x4 >> 8);
uVar7 = (undefined)in_x4;
uVar6 = (undefined7)((ulonglong)in_x3 >> 8);
uVar5 = (undefined)in_x3;
puVar4 = &stack0xffffffffffffffd4;
uVar3 = 0x1046b;
local_28 = DAT_000a90c0;
uVar2 = FUN_000540b4(2);
uVar16 = (undefined)local_2c;
uVar1 = (undefined)uVar2;
if ((int)uVar2 == 0) {
in_ZR = local_2c == 1;
if (local_2c < 1) {
uVar15 = 0;
goto LAB_0005de34;
}
[COLOR="Blue"][B] uVar3 = 0x1046b; // drm key unit[/B][/COLOR]
[COLOR="Red"] uVar2 = FUN_00054318(2); // partition 2
uVar1 = (undefined)uVar2;
uVar15 = uVar2 & 0xffffffff;
if ((int)uVar2 == 0) goto LAB_0005de34;
FUN_0005df70(uVar2,uVar3,puVar4,CONCAT71(uVar6,uVar5),CONCAT71(uVar8,uVar7),
CONCAT71(uVar10,uVar9),CONCAT71(uVar12,uVar11),CONCAT71(uVar14,uVar13));
_uVar1 = "[ERROR @ %s:%d]:\nFailed to delete DK\n";[/COLOR]
puVar4 = (undefined *)0x136;
uVar3 = extraout_x0_00;
}
else {
uVar15 = uVar2 & 0xffffffff;
FUN_0005df70(uVar2,uVar3,puVar4,CONCAT71(uVar6,uVar5),CONCAT71(uVar8,uVar7),
CONCAT71(uVar10,uVar9),CONCAT71(uVar12,uVar11),CONCAT71(uVar14,uVar13));
_uVar1 = "[ERROR @ %s:%d]:\nFailed to get size of TA_DK_NUMBER_UNIT\n";
puVar4 = (undefined *)0x12f;
uVar3 = extraout_x0;
}
uVar1 = FUN_000689a0(_uVar1,uVar3,puVar4,CONCAT71(uVar6,uVar5),CONCAT71(uVar8,uVar7),
CONCAT71(uVar10,uVar9),CONCAT71(uVar12,uVar11),CONCAT71(uVar14,uVar13));
LAB_0005de34:
local_28 = FUN_0005df5c(uVar1,(char)uVar3,(char)puVar4,uVar5,uVar7,uVar9,uVar11,uVar13,
in_stack_ffffffffffffffd0,uVar16,local_28);
if (in_ZR) {
return uVar15;
}
// WARNING: Subroutine does not return
FUN_00024468(local_28,uVar3,puVar4,CONCAT71(uVar6,uVar5),CONCAT71(uVar8,uVar7),
CONCAT71(uVar10,uVar9),CONCAT71(uVar12,uVar11),CONCAT71(uVar14,uVar13));
}
Its very evidently that function sub_4DDE4 is called at the start of lock function, I can tell that drm key is bye bye after you unlock phone, curently I'm unable to figure out what is done with oem lock command & why widevine keys is back but definitelly drm key is lost forever, indication for that is message inside service menu "is even unlocked = yes" !
So how lock is done, in short:
1. drm key bye bye
2. user sensitive partitions deleted (thats why device no more boot & must use sony pc companion in order to repair)
3. rollback counter reset
4. bootloader locked
Some good news for bootloader unlocked xperia 10 owners! I'm managed to get all back after patching secd
Code:
07-25 17:10:29.745 8470 8471 I [email protected]: start init_thread
07-25 17:10:29.745 8470 8471 I [email protected]: listeners registered
07-25 17:10:29.745 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x200
07-25 17:10:29.746 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:29.746 579 579 I SELinux : avc: received setenforce notice (enforcing=0)
07-25 17:10:29.747 579 579 W hwservicemanager: Detected instance of [email protected]::IDeviceSecurity (pid: 8470) registering over instance of or with base of [email protected]::IDeviceSecurity (pid: 879).
07-25 17:10:29.751 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.751 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:29.752 8470 8471 I libdevice_security_static: get_rooting_status.cpp:80 rooting_status 0
07-25 17:10:29.752 8470 8471 I [email protected]: the bootloader is OK, try to init suntory
07-25 17:10:29.752 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2022
07-25 17:10:29.754 8470 8471 I libsuntory_static: utils_blob.cpp:497 found blob CKB
07-25 17:10:29.754 8470 8471 I libsuntory_static: utils_blob.cpp:521 match found at index 0
07-25 17:10:29.755 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x4100
07-25 17:10:29.755 8470 8471 D QSEECOMAPI: App is not loaded in QSEE
07-25 17:10:29.755 8470 8471 D QSEECOMAPI: app_arch = 2, total_files = 9
07-25 17:10:29.788 8470 8471 D QSEECOMAPI: Loaded image: APP id = 1179652
07-25 17:10:29.789 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xc00
07-25 17:10:29.789 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:29.793 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.793 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:29.798 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.798 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 1179652
07-25 17:10:29.798 8470 8471 I libsuntory_static: utils_blob.cpp:121 blob verisfication status: Blob OK
07-25 17:10:29.798 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2023
07-25 17:10:29.801 8470 8471 I libsuntory_static: utils_blob.cpp:497 found blob WIDEVINE
07-25 17:10:29.801 8470 8471 I libsuntory_static: utils_blob.cpp:521 match found at index 1
07-25 17:10:29.801 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x4100
07-25 17:10:29.801 8470 8471 D QSEECOMAPI: App is not loaded in QSEE
07-25 17:10:29.801 8470 8471 D QSEECOMAPI: app_arch = 2, total_files = 9
07-25 17:10:29.835 8470 8471 D QSEECOMAPI: Loaded image: APP id = 1245188
07-25 17:10:29.835 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xc00
07-25 17:10:29.835 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:29.838 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.838 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:29.843 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.843 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 1245188
07-25 17:10:29.844 8470 8471 I libsuntory_static: utils_blob.cpp:121 blob verisfication status: Blob OK
07-25 17:10:29.844 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2024
07-25 17:10:29.846 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 1
07-25 17:10:29.846 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2025
07-25 17:10:29.848 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.848 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2026
07-25 17:10:29.849 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.849 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2027
07-25 17:10:29.850 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.850 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2028
07-25 17:10:29.851 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.851 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2029
07-25 17:10:29.852 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.852 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2030
07-25 17:10:29.853 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.853 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2031
07-25 17:10:29.855 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.855 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2032
07-25 17:10:29.856 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.856 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2033
07-25 17:10:29.857 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.857 8470 8471 I libsuntory_static: utils_blob.cpp:462 process miscTA unit 2034
07-25 17:10:29.858 8470 8471 E libsuntory_static: utils_blob.cpp:477 invalid blob size 0
07-25 17:10:29.858 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
07-25 17:10:29.858 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 65537
07-25 17:10:29.862 8470 8471 E KeymasterUtils: TA API Major Version: 4
07-25 17:10:29.862 8470 8471 E KeymasterUtils: TA API Minor Version: 0
07-25 17:10:29.862 8470 8471 E KeymasterUtils: TA Major Version: 4
07-25 17:10:29.862 8470 8471 E KeymasterUtils: TA Minor Version: 162
07-25 17:10:29.866 622 628 D DrmLibTime: got the req here! ret=0
07-25 17:10:29.866 622 628 D DrmLibTime: command id, time_cmd_id = 770
07-25 17:10:29.866 622 628 D DrmLibTime: time_getutcsec starts!
07-25 17:10:29.866 622 628 D DrmLibTime: QSEE Time Listener: time_getutcsec
07-25 17:10:29.866 622 628 D DrmLibTime: QSEE Time Listener: get_utc_seconds
07-25 17:10:29.866 622 628 D DrmLibTime: QSEE Time Listener: time_get_modem_time
07-25 17:10:29.866 622 628 D DrmLibTime: QSEE Time Listener: Checking if ATS_MODEM is set or not.
07-25 17:10:29.866 622 628 D QC-time-services: Lib:time_genoff_operation: pargs->base = 13
07-25 17:10:29.866 622 628 D QC-time-services: Lib:time_genoff_operation: pargs->operation = 2
07-25 17:10:29.866 622 628 D QC-time-services: Lib:time_genoff_operation: pargs->ts_val = 0
07-25 17:10:29.866 622 628 D QC-time-services: Lib:time_genoff_operation: Send to server passed!!
07-25 17:10:29.866 792 800 D QC-time-services: Daemon: Connection accepted:time_genoff
07-25 17:10:29.867 792 8472 D QC-time-services: Daemon:Received base = 13, unit = 1, operation = 2,value = 0
07-25 17:10:29.867 792 8472 D QC-time-services: Daemon:genoff_opr: Base = 13, val = 0, operation = 2
07-25 17:10:29.867 792 8472 D QC-time-services: offset is: 1 for base: 13
07-25 17:10:29.867 622 628 E QC-time-services: Receive Passed == base = 13, unit = 1, operation = 2, result = 0
07-25 17:10:29.867 622 628 D DrmLibTime: QSEE Time Listener: ATS_MODEM is set. Try to retrieve it.
07-25 17:10:29.867 792 800 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
07-25 17:10:29.867 792 800 D QC-time-services: Daemon: Connection accepted:time_genoff
07-25 17:10:29.867 792 8473 D QC-time-services: Daemon:Received base = 13, unit = 1, operation = 1,value = 0
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon:genoff_opr: Base = 13, val = 0, operation = 1
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon: genoff get for 13
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon:Value read from QTimer mseconds = 1307648
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon:Value read from RTC mseconds on boot = 48462179000
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon:Value read from QTimer mseconds = 1307648
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon:Value read from generic offset = 1547226365549
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon:Delta read on boot mseconds = 48462155118
07-25 17:10:29.868 792 8473 D QC-time-services: Daemon:Final Time = 1595689828315
07-25 17:10:29.868 622 628 D DrmLibTime: QSEE Time Listener: Time GenOff - seconds: 1595689828
07-25 17:10:29.868 622 628 D DrmLibTime: time_getutcsec returns 0, sec = 1595689828; nsec = 0
07-25 17:10:29.868 622 628 D DrmLibTime: time_getutcsec finished!
07-25 17:10:29.868 622 628 D DrmLibTime: iotcl_continue_command finished! and return 0
07-25 17:10:29.868 622 628 D DrmLibTime: before calling ioctl to read the next time_cmd
07-25 17:10:29.868 792 800 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
07-25 17:10:29.887 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x200
07-25 17:10:29.888 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:29.889 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.889 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:29.889 8470 8471 I libdevice_security_static: get_imei.cpp:180 imei STR munjeni edited, size 15
07-25 17:10:29.899 8470 8471 E KeyMasterHalDevice: Attest key send cmd failed
07-25 17:10:29.899 8470 8471 E KeyMasterHalDevice: ret: 0
07-25 17:10:29.899 8470 8471 E KeyMasterHalDevice: resp->status: -10003
07-25 17:10:29.906 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.906 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 65537
07-25 17:10:29.906 8470 8471 I [email protected]: key id ANDROID_ATTEST status PROVISIONED
07-25 17:10:29.907 587 587 I tad : MiscTA Unit 2021:
07-25 17:10:29.907 587 587 I tad : WRITTEN (Size 20)
07-25 17:10:29.930 587 587 I tad : Actual erase/write to flash done (count 4, time 1595689829).
07-25 17:10:29.930 587 587 I tad : MiscTA: Write of unit 2021 completed - OK
07-25 17:10:29.930 8470 8471 I [email protected]: suntory initialized
07-25 17:10:29.930 8470 8471 I [email protected]: wait for post_fs proprty
07-25 17:10:29.930 8470 8471 I [email protected]: post_fs property triggered
07-25 17:10:29.930 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x200
07-25 17:10:29.930 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:29.932 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.932 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:29.932 8470 8471 I libdevice_security_static: get_rooting_status.cpp:80 rooting_status 2
07-25 17:10:29.935 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x200
07-25 17:10:29.935 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:29.936 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.936 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:29.936 8470 8471 I libdevice_security_static: get_security_config.cpp:68 security configuration 1
07-25 17:10:29.936 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x83c0
07-25 17:10:29.936 8470 8471 D QSEECOMAPI: App is not loaded in QSEE
07-25 17:10:29.936 8470 8471 D QSEECOMAPI: app_arch = 2, total_files = 9
07-25 17:10:29.973 8470 8471 D QSEECOMAPI: Loaded image: APP id = 1310724
07-25 17:10:29.974 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xc00
07-25 17:10:29.974 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:29.977 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.977 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:29.980 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:29.980 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 1310724
07-25 17:10:29.982 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x83c0
07-25 17:10:29.982 8470 8471 D QSEECOMAPI: App is not loaded in QSEE
07-25 17:10:29.982 8470 8471 D QSEECOMAPI: app_arch = 2, total_files = 9
07-25 17:10:30.016 8470 8471 D QSEECOMAPI: Loaded image: APP id = 1376260
07-25 17:10:30.016 8470 8471 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xc00
07-25 17:10:30.016 8470 8471 D QSEECOMAPI: App is already loaded QSEE and app id = 131074
07-25 17:10:30.020 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:30.020 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 131074
07-25 17:10:30.023 8470 8471 D QSEECOMAPI: QSEECom_dealloc_memory
07-25 17:10:30.023 8470 8471 D QSEECOMAPI: QSEECom_shutdown_app, app_id = 1376260
07-25 17:10:30.024 8470 8471 I [email protected]: credmgr initialized
07-25 17:10:30.025 8470 8471 I [email protected]: "vendor.keyprovd.suntory.prov" property set
07-25 17:10:33.798 853 853 I [email protected]: type=1400 audit(0.0:2107): avc: denied { search } for name="kgsl" dev="sysfs" ino=28936 scontext=u:r:hal_memtrack_default:s0 tcontext=u:object_r:sysfs_kgsl:s0 tclass=dir permissive=1 ppid=1 pcomm="init" pgid=1 pgcomm="init"
07-25 17:10:36.689 8372 8372 W adbd : timeout expired while flushing socket, closing
Edit:
Now all ready https://forum.xda-developers.com/xp...m-fix-drm-fix-unlocked-bootloader-53-t4138269
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/
# LineageOS
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.
# What's working
Display/Touchscreen
LiveDisplay
Audio playback
Dolby Atmos
Headphone/Headset
Quad speakers
Video playback
HDR
Camera
Microphone
Sensors
Fingerprint sensor
GPS
LTE (SM-T825)
Hotspot
WiFi
WiFi display
Bluetooth
DRM
Widevine L1
USB ADB/MTP
Samsung Doze
S-Pen
Palm rejection
Hardware Encryption
MDFPP
SD Card
Power-off mode charging
# Untested
FBE for userdata
# What's not working
USB OTG
SELinux permissive
Please see the "Known issues" part of this post
# Downloads
## LineageOS 19.1
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
## Google Apps
NikGapps
The other Gapps will work too, but I only confirmed that NikGapps working
## TWRP Recovery
You can use mine, please visit this thread.
[RECOVERY][SM-T820][SM-T825][UNOFFICIAL] TWRP for Galaxy Tab S3
# How to install
Unlock the bootloader.
Download TWRP and flash the recovery image via Odin.
Download LineageOS 19.1 for Galaxy Tab S3.
Be aware of the board name.
Download GAPPS for Android 12L and the others you want to flash.
Enter TWRP recovery.
The first boot to TWRP might be very slow because of the unmatched file systems.
Format the whole system, data, cache partitions using the format menu.
You will type `yes` to do that.
Flash the images.
If you're going to install GApps or something, you have to install the LineageOS first.
Reboot the system.
Done.
# Known issues
Camera somewhat buggy
The built-in camera application (Camera2) is not working well. You can use another camera application like OpenCamera.
Sometimes the camera doesn't work after booting. You can fix that back by just rebooting.
After using the camera application, the Torch tile on the quick settings not working. But you can use the camera anyway.
On webcam chat apps, there is a vertical green bar and the color is not properly displayed.
Audio bugs
No sound for the microphone and speaker in voice calls, such as the regular phone call or voice chat with a meeting app.
Thank all of you for the feedback
# Sources
Device Tree
gts3l-common: https://github.com/awesometic/android_device_samsung_gts3l-common
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
Vendor: https://github.com/awesometic/proprietary_vendor_samsung
# Telegram Groups
If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.
Galaxy Tab S3 General Discussion
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
LineageOS Team
LOS17.1) @Valera1978 for his amazing previous work including his MSM8996 kernel
LOS18.1) @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
LOS18.1) @bmwdroid and @cherepanov for confirming the LTE works
LOS18.1) @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
General) @switchgott for helping me in the development discussion and creating Telegram groups
General) All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
LOS18.1) @LuK1337 for giving me a hint to fix the quad-speakers
LOS19.1) @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
LOS19.1) @masdaster for the fix of MDFPP Keystore on our device
## Changelogs
2022. 9. 23
Synced with the latest LineageOS 19.1 repositories
Security patch by September 5, 2022
2022. 8. 15
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r22
Security patch by August 5, 2022
About Keystore, switch to use MDFPP skeymast files again.
This will break your lock screen. Please remove `/data/system/locksettings.db` file using TWRP, then lock screen will be fixed and your biometric information will be removed. Please reset your biometric lock method again. Sorry for the inconvenience.
Thank you for the idea and contribution for the proper use of our MDFPP Keystore, @masdaster
2022. 7. 15
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r11
Security patch by July 5, 2022
Added support for Sony DualShock 4 gamepad
Increased headphone jack volume by about 20%
Updated USB HAL to v1.3
2022. 6. 11
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r7
Security patch by June 5, 2022
Fixed camera working
It is somewhat buggy, you can see the notes on the original post
Fixed Bluetooth/headphone jack audio working
Now it builds the AOSP audio stack from the source
Fixed arrow keys orientation on the S3 Book cover keyboard in landscape mode
Thanks to @roesja
[ROM][UNOFFICIAL][11][EAS][SM-T820][SM-T825][2022-05-08] LineageOS 18.1 for Galaxy Tab S3 | Page 24 | XDA Forums (xda-developers.com)
2022. 4. 16
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r4
Fixed the boot failure issue for some users
It is related to the Keystore of the Android system, I did a little compromise to make it work for all users
If you are using the first version (220320), you have to clean install to this version or you may fail to unlock the screen , you have to boot into TWRP and remove the file `locksettings.db` under `/data/system` directory. This will resolve the unlock failure issue after dirty-flashing it.
Thanks for this information, David Becker.
2022. 3. 20
Initial release
## Special Notes
You must do clean-install if you are willing to upgrade from another ROM such as an Android 11 based one
I have tested Magisk 24.3 working
You can fix SafetyNet using Magisk modules, SafetyNet Fix and PropsConfig
You can hide the soft nav buttons on the bottom bar. This is the workaround.
1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
2. Go to "System -> Gestures" and set "System navigation" to "Gesture navigation"
3. Go back to "System -> Buttons" and check "Enable on-screen nav bar" again to disable soft nav bar and enable hardware key.
You can hide the bottom Taskbar. This is the workaround.
1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
2. Go back using navigation bar and go to the "Buttons" menu again
3. Then we can see the "Enable taskbar" option that we couldn't see before. Disable that option.
4. And disable "Enable on-screen nav bar" option again to use the hardware buttons back.
reserved
I regret to say that the best rom produced for this tablet so far is the rom in the link below, while the others have never been fully stable.
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
SM-T825 TWEAKED 5.1 ***** PIE ***** 20JUN2020 T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928 Based on latest stock CTD1 firmware Tweaked, stable, zip aligned. SU/D Forced encryption disabled Deknoxed Debloated (GPU driver updated to latest adreno...
forum.xda-developers.com
bozkurtum said:
I regret to say that the best rom produced for this tablet so far is the rom in the link below, while the others have never been fully stable.
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
SM-T825 TWEAKED 5.1 ***** PIE ***** 20JUN2020 T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928 Based on latest stock CTD1 firmware Tweaked, stable, zip aligned. SU/D Forced encryption disabled Deknoxed Debloated (GPU driver updated to latest adreno...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes it is If you want the best stability the answer is always the stock firmware or a stock-based ROM.
Hello,
First thank very much for your work, your roms are fantastic the version of lineageos 18.1 and HAVOC,
this first version is causing a bootloop I don't know if it can help I'm adding the device boot logs:
Code:
12-12 20:39:51.806 0 0 E [0: surfaceflinger:14610] subsys-restart: __subsystem_get(): __subsystem_get: a530_zap count:0
12-12 20:39:51.812 0 0 I [0: ueventd:14611] ueventd: firmware: loading 'a530_zap.mdt' for '/devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt'
12-12 20:39:51.813 0 0 I : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: loading from 0x000000008f400000 to 0x000000008f402000
12-12 20:39:51.813 0 0 I [2: ueventd:14611] ueventd: loading /devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt took 1ms
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] scm_call failed: func id 0x42000201, ret: -1, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: Invalid firmware metadata
12-12 20:39:51.836 14606 14610 E Adreno-GSL: <ioctl_kgsl_driver_entry:873>: open(/dev/kgsl-3d0) failed: errno 5. I/O error
12-12 20:39:51.836 14606 14610 W libEGL : eglInitialize(0x75770d4530) failed (EGL_BAD_ALLOC)
12-12 20:39:51.837 14606 14610 W RenderEngine: no suitable EGLConfig found, trying a simpler query
12-12 20:39:51.837 14606 14610 F RenderEngine: no suitable EGLConfig found, giving up
12-12 20:39:51.837 14606 14610 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 14610 (surfaceflinger), pid 14606 (surfaceflinger)
12-12 20:39:51.859 14614 14614 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
12-12 20:39:51.861 633 633 I tombstoned: received crash request for pid 14610
12-12 20:39:51.861 14614 14614 I crash_dump64: performing dump of process 14606 (target tid = 14610)
12-12 20:39:51.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:51.873 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:51.875 586 14617 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:51.875 586 14617 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:51.874 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:51.928 0 0 I [3: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=8 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.934 0 0 I [2: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=1 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.947 14614 14614 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-12 20:39:51.947 14614 14614 F DEBUG : Build fingerprint: 'samsung/gts3lltekx/gts3lltekx:9/PPR1.180610.011/T825N0KOU3CTD1:user/release-keys'
12-12 20:39:51.947 14614 14614 F DEBUG : Revision: '5'
12-12 20:39:51.947 14614 14614 F DEBUG : ABI: 'arm64'
12-12 20:39:51.947 14614 14614 F DEBUG : Timestamp: 1970-12-12 20:39:51.864459376+0000
12-12 20:39:51.947 14614 14614 F DEBUG : Process uptime: 1s
12-12 20:39:51.947 14614 14614 F DEBUG : Cmdline: /system/bin/surfaceflinger
12-12 20:39:51.947 14614 14614 F DEBUG : pid: 14606, tid: 14610, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
12-12 20:39:51.947 14614 14614 F DEBUG : uid: 1000
12-12 20:39:51.947 14614 14614 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
12-12 20:39:51.947 14614 14614 F DEBUG : Abort message: 'no suitable EGLConfig found, giving up'
12-12 20:39:51.947 14614 14614 F DEBUG : x0 0000000000000000 x1 0000000000003912 x2 0000000000000006 x3 00000074b4fc9340
12-12 20:39:51.947 14614 14614 F DEBUG : x4 00000000000c4ad0 x5 00000000000c4ad0 x6 00000000000c4ad0 x7 0000000000000018
12-12 20:39:51.947 14614 14614 F DEBUG : x8 00000000000000f0 x9 e6e2a24fe5d8bd5e x10 0000000000000000 x11 ffffff80ffffffdf
12-12 20:39:51.947 14614 14614 F DEBUG : x12 0000000000000001 x13 0000000000000027 x14 00000074b4fc94d0 x15 0000000000000038
12-12 20:39:51.947 14614 14614 F DEBUG : x16 000000774718c050 x17 0000007747168d20 x18 00000074b4048000 x19 000000000000390e
12-12 20:39:51.947 14614 14614 F DEBUG : x20 0000000000003912 x21 00000000ffffffff x22 00000074b4fca000 x23 00000075770d4530
12-12 20:39:51.948 14614 14614 F DEBUG : x24 00000075670d5330 x25 00000074b4fc9cb0 x26 00000074b4fc9ff8 x27 00000074b4fc9ab0
12-12 20:39:51.948 14614 14614 F DEBUG : x28 00000074b4ed1000 x29 00000074b4fc93c0
12-12 20:39:51.948 14614 14614 F DEBUG : lr 000000774711ba14 sp 00000074b4fc9320 pc 000000774711ba40 pst 0000000000000000
12-12 20:39:51.948 14614 14614 F DEBUG : backtrace:
12-12 20:39:51.948 14614 14614 F DEBUG : #00 pc 000000000004fa40 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #01 pc 00000000000062c0 /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #02 pc 0000000000006dc8 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #03 pc 00000000002671f4 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::chooseEglConfig(void*, int, bool)+496) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #04 pc 000000000027a4d0 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+164) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #05 pc 0000000000265ce0 /system/bin/surfaceflinger (_ZNSt3__110__function6__funcIZN7android12renderengine12RenderEngine6createERKNS3_24RenderEngineCreationArgsEE3$_1NS_9allocatorIS8_EEFNS_10unique_ptrIS4_NS_14default_deleteIS4_EEEEvEEclEv$fb147fdbd0638d73632d1b87d1d565c9+40) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #06 pc 0000000000276c28 /system/bin/surfaceflinger (android::renderengine::threaded::RenderEngineThreaded::threadMain(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>)+376) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #07 pc 0000000000278f88 /system/bin/surfaceflinger (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (android::renderengine::threaded::RenderEngineThreaded::*)(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>), android::renderengine::threaded::RenderEngineThreaded*, std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()> > >(void*)+160) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #08 pc 00000000000b1780 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #09 pc 0000000000051264 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.963 14614 14614 E crash_dump64: unable to connect to activity manager: No such file or directory
12-12 20:39:51.963 633 633 E tombstoned: Tombstone written to: tombstone_15
12-12 20:39:51.966 0 0 I [3: init: 1] init: Untracked pid 14614 exited with status 0
12-12 20:39:51.972 0 0 I [3: init: 1] init: Service 'surfaceflinger' (pid 14606) received signal 6
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'surfaceflinger' (pid 14606) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 14606 in 0ms
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'zygote' (pid 14232) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 0 pid 14232 in 0ms
12-12 20:39:51.974 0 0 I [0: init: 1] init: Untracked pid 14616 exited with status 0
12-12 20:39:51.975 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.qcom.rc:920)
12-12 20:39:51.975 0 0 I [0: init: 1] init: Sending signal 9 to service 'vendor.hwcomposer-2-1' (pid 742) process group...
12-12 20:39:51.975 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 742 in 0ms
12-12 20:39:51.976 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.target.rc:459)
12-12 20:39:51.977 0 0 I [0: init: 1] init: Sending signal 9 to service 'ppd' (pid 877) process group...
12-12 20:39:51.977 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 877 in 0ms
12-12 20:39:52.089 0 0 W [0:android.hardwar:14604] scm: secure world has been busy for 1 second!
12-12 20:39:52.227 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.229 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.260 0 0 I [0: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.272 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.276 0 0 I [2: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.278 0 0 I [2: kworker/u8:0: 6] sm5705_vbatocv_check: mode change to mix RS auto mode
12-12 20:39:52.282 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 6 1 11 -1 1 6 1 9 1>, temp_fg = 363 ,p_curr_cal = 0x9b, n_curr_cal = 0xa6, curr_offset = 0x1, volt_cal = 0x8000 ,fg_delta_volcal = 0x0
12-12 20:39:52.283 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 3 0 3 1 1 2 3 2 3>, p_curr_cal = 0x9b, n_curr_cal = 0xa7, mix_factor=0x47a ,batt_temp = 286
12-12 20:39:52.286 0 0 I [2: kworker/u8:0: 6] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.291 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xA0=0x1400, 0xAC=0x20a5, 0xAD=0x211b, 0xAE=0x21f7, 0xAF=0x2399, 0x28=0x0838, 0x2F=0x021a, 0x01=0xc401, SM5705_ID=0x000b
12-12 20:39:52.298 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xB0=0x0000, 0xBC=0x255e, 0xBD=0x283f, 0xBE=0x2d0c, 0xBF=0x2d17, 0x85=0x0064, 0x86=0x0196, 0x87=0x0ec4, 0x1F=0x0080, 0x94=0x0001 , 0x13=0x000f, 0x14=0x0000
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_get_all_value: chg_h=1, chg_f=0, chg_s=1, is_chg=0, ta_exist=1, v=3790, v_avg=3786, i=-248, i_avg=-91, ocv=3779, fg_t=363, b_t=286, cycle=38, soc=327, state=0x6
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_scaled_capacity: scaled capacity (32.7)
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_atomic_capacity: NOW(32), OLD(32)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_get_battery_info:Vnow(3790mV),Inow(-248mA),Imax(500mA),SOC(32%),Tbat(286),Tchg(326),Twpc(0)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_cisd_check: cisd off.
12-12 20:39:52.311 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_time_management: Charging Time : 1340 secs
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_temperature: HLT(800) HLR(750) HT(500), HR(450), LT(0), LR(50)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_swelling_check: status(1), swell_mode(0:0:0), cv(0x10cc), temp(286)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_fullcharged_check: Charging Mode : Normal
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_set_current_event: clear current event(now=0x0, value=0x4)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_mix_temp: mix_limit(0), temp(286), chg_temp(326), input_current(500)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_afc_temp: cable_type(4), chg_limit(0)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_monitor_work: Status(Charging), mode(Normal), Health(Good), Cable(4, 4, 1, 1), level(100%), cisd.cd(0), HV(NONE), sleep_mode(0), Cycle(-1)
12-12 20:39:52.325 0 0 I [2: kworker/2:1: 33] sm5705-charger: psy_chg_get_charge_type: psy_chg_get_charge_type charge_type(5)
12-12 20:39:52.325 0 0 I : [2: kworker/2:1: 33] sec_bat_get_property cable type = 4 sleep_mode = 0
12-12 20:39:52.327 0 0 I [2: kworker/2:1: 33] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.329 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.330 0 0 W [2:[email protected]: 743] healthd: battery l=32 v=3790 t=28.6 h=2 st=2 c=-248 fc=6000000 chg=u
12-12 20:39:52.332 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.609 0 0 E : [1: msm_watchdog: 32] [pet_watchdog] last_count : 502d6, new_count : 0, bark_time : 77fd3, bite_time : 8ffca
12-12 20:39:52.662 0 0 I [2: logd.reader: 594] logd: logdr: UID=2000 GID=2000 PID=14620 n tail=0 logMask=bf pid=0 start=0ns deadline=0ns
12-12 20:39:52.754 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:52.755 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:52.755 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:52.757 0 0 I [1: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:52.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:52.875 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:52.877 586 14624 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:52.877 586 14624 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:52.876 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:53.142 0 0 I : [1: kworker/u8:0: 6] etspi_work_func_debug ldo: 0, sleep: 0, tz: 1, type: unknown
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Load image request failed ret = -1, errno = 22
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Loading image failed with ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:58) Loading app (path - /vendor/firmware_mnt/image) skeymast failed: Invalid argument, size = 82112, ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:106) Fail to open session with QSEE
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:78) KM_TZOpenConnection FAILED [-3]
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1120) can't open connection to trustlet; error: -49
12-12 20:39:53.387 14604 14604 E [email protected]: Error -1 opening keystore keymaster1 device
12-12 20:39:53.387 14604 14604 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1028) entered device_close function
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:119) There is no opened session. ref cnt = 0
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1040) can't close connection with trustlet; error: -49
12-12 20:39:53.387 14604 14604 E HidlServiceManagement: Could not find instance 'default' in library [email protected] Keeping library open.
12-12 20:39:53.387 14604 14604 E LegacySupport: Could not get passthrough implementation for [email protected]::IKeymasterDevice/default.
12-12 20:39:53.386 0 0 E : [0:android.hardwar:14604] scm_call failed: func id 0x72000101, ret: -12, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_load_app: scm_call to load app failed
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_ioctl: failed load_app request: -22
12-12 20:39:53.390 0 0 I [1: init: 1] init: Service 'vendor.keymaster-3-0' (pid 14604) exited with status 1
12-12 20:39:53.390 0 0 I [1: init: 1] init: Sending signal 9 to service 'vendor.keymaster-3-0' (pid 14604) process group...
12-12 20:39:53.390 0 0 I [1: init: 1] libprocessgroup: Successfully killed process cgroup uid 9999 pid 14604 in 0ms
12-12 20:39:53.755 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:53.756 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:53.756 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:53.757 0 0 I [0: init: 1] init: starting service 'vendor.keymaster-3-0'...
12-12 20:39:53.760 0 0 E [0: init: 1] libprocessgroup: Failed to make and chown /sys/fs/cgroup/uid_9999: Operation not permitted
12-12 20:39:53.760 0 0 E [0: init: 1] init: createProcessGroup(9999, 14626) failed for service 'vendor.keymaster-3-0': Operation not permitted
12-12 20:39:53.761 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:53.778 14626 14626 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
12-12 20:39:53.778 2 2 I [2:android.hardwar:14626] binder: 14626:14626 ioctl 40046210 7fe065faa4 returned -22
12-12 20:39:53.784 14626 14626 I [email protected]: Fetching keymaster device name default
12-12 20:39:53.786 2 2 W [2:android.hardwar:14626] QSEECOM: qseecom_load_app: App (skeymast) does'nt exist, loading apps for first time
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1057) entered device_open function
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_tc_api.c:65) Open MDFPP keymaster version 1.9.04
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_synchronization.c:27) sync init...OK
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:101) request 82112 bytes
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:45) qsc_start_app: buff_size: 82112
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x140c0
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: App is not loaded in QSEE
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: app_arch = 1, total_files = 8
12-12 20:39:53.875 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:53.876 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:53.878 586 14627 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:53.878 586 14627 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:53.877 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:54.562 0 0 I [2: kworker/2:1: 33] msm_thermal: msm_ts_print tsens[4:459][6:459][9:501][11:482][15:401]
12-12 20:39:54.756 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:54.757 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:54.757 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:54.758 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:54.876 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:54.877 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:54.878 586 14629 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:54.878 586 14629 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:54.878 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:55.086 0 0 W [0:android.hardwar:14626] scm: secure world has been busy for 1 second!
bozkurtum said:
I regret to say that the best rom produced for this tablet so far is the rom in the link below, while the others have never been fully stable.
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
SM-T825 TWEAKED 5.1 ***** PIE ***** 20JUN2020 T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928 Based on latest stock CTD1 firmware Tweaked, stable, zip aligned. SU/D Forced encryption disabled Deknoxed Debloated (GPU driver updated to latest adreno...
forum.xda-developers.com
Click to expand...
Click to collapse
I MOST regretfully say you're mistaken. I had that before @Awesometic released 18.1 and it was MUCH slower and less responsive.
The 18.1 has gotten nothing but praise from all who use it. I have a T820 and can't try the 19.1 yet but looking forward to it;
ETA on the T820?
And BRAVO!!!
Bakarios said:
Hello,
First thank very much for your work, your roms are fantastic the version of lineageos 18.1 and HAVOC,
this first version is causing a bootloop I don't know if it can help I'm adding the device boot logs:
Code:
12-12 20:39:51.806 0 0 E [0: surfaceflinger:14610] subsys-restart: __subsystem_get(): __subsystem_get: a530_zap count:0
12-12 20:39:51.812 0 0 I [0: ueventd:14611] ueventd: firmware: loading 'a530_zap.mdt' for '/devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt'
12-12 20:39:51.813 0 0 I : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: loading from 0x000000008f400000 to 0x000000008f402000
12-12 20:39:51.813 0 0 I [2: ueventd:14611] ueventd: loading /devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt took 1ms
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] scm_call failed: func id 0x42000201, ret: -1, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: Invalid firmware metadata
12-12 20:39:51.836 14606 14610 E Adreno-GSL: <ioctl_kgsl_driver_entry:873>: open(/dev/kgsl-3d0) failed: errno 5. I/O error
12-12 20:39:51.836 14606 14610 W libEGL : eglInitialize(0x75770d4530) failed (EGL_BAD_ALLOC)
12-12 20:39:51.837 14606 14610 W RenderEngine: no suitable EGLConfig found, trying a simpler query
12-12 20:39:51.837 14606 14610 F RenderEngine: no suitable EGLConfig found, giving up
12-12 20:39:51.837 14606 14610 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 14610 (surfaceflinger), pid 14606 (surfaceflinger)
12-12 20:39:51.859 14614 14614 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
12-12 20:39:51.861 633 633 I tombstoned: received crash request for pid 14610
12-12 20:39:51.861 14614 14614 I crash_dump64: performing dump of process 14606 (target tid = 14610)
12-12 20:39:51.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:51.873 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:51.875 586 14617 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:51.875 586 14617 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:51.874 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:51.928 0 0 I [3: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=8 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.934 0 0 I [2: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=1 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.947 14614 14614 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-12 20:39:51.947 14614 14614 F DEBUG : Build fingerprint: 'samsung/gts3lltekx/gts3lltekx:9/PPR1.180610.011/T825N0KOU3CTD1:user/release-keys'
12-12 20:39:51.947 14614 14614 F DEBUG : Revision: '5'
12-12 20:39:51.947 14614 14614 F DEBUG : ABI: 'arm64'
12-12 20:39:51.947 14614 14614 F DEBUG : Timestamp: 1970-12-12 20:39:51.864459376+0000
12-12 20:39:51.947 14614 14614 F DEBUG : Process uptime: 1s
12-12 20:39:51.947 14614 14614 F DEBUG : Cmdline: /system/bin/surfaceflinger
12-12 20:39:51.947 14614 14614 F DEBUG : pid: 14606, tid: 14610, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
12-12 20:39:51.947 14614 14614 F DEBUG : uid: 1000
12-12 20:39:51.947 14614 14614 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
12-12 20:39:51.947 14614 14614 F DEBUG : Abort message: 'no suitable EGLConfig found, giving up'
12-12 20:39:51.947 14614 14614 F DEBUG : x0 0000000000000000 x1 0000000000003912 x2 0000000000000006 x3 00000074b4fc9340
12-12 20:39:51.947 14614 14614 F DEBUG : x4 00000000000c4ad0 x5 00000000000c4ad0 x6 00000000000c4ad0 x7 0000000000000018
12-12 20:39:51.947 14614 14614 F DEBUG : x8 00000000000000f0 x9 e6e2a24fe5d8bd5e x10 0000000000000000 x11 ffffff80ffffffdf
12-12 20:39:51.947 14614 14614 F DEBUG : x12 0000000000000001 x13 0000000000000027 x14 00000074b4fc94d0 x15 0000000000000038
12-12 20:39:51.947 14614 14614 F DEBUG : x16 000000774718c050 x17 0000007747168d20 x18 00000074b4048000 x19 000000000000390e
12-12 20:39:51.947 14614 14614 F DEBUG : x20 0000000000003912 x21 00000000ffffffff x22 00000074b4fca000 x23 00000075770d4530
12-12 20:39:51.948 14614 14614 F DEBUG : x24 00000075670d5330 x25 00000074b4fc9cb0 x26 00000074b4fc9ff8 x27 00000074b4fc9ab0
12-12 20:39:51.948 14614 14614 F DEBUG : x28 00000074b4ed1000 x29 00000074b4fc93c0
12-12 20:39:51.948 14614 14614 F DEBUG : lr 000000774711ba14 sp 00000074b4fc9320 pc 000000774711ba40 pst 0000000000000000
12-12 20:39:51.948 14614 14614 F DEBUG : backtrace:
12-12 20:39:51.948 14614 14614 F DEBUG : #00 pc 000000000004fa40 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #01 pc 00000000000062c0 /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #02 pc 0000000000006dc8 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #03 pc 00000000002671f4 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::chooseEglConfig(void*, int, bool)+496) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #04 pc 000000000027a4d0 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+164) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #05 pc 0000000000265ce0 /system/bin/surfaceflinger (_ZNSt3__110__function6__funcIZN7android12renderengine12RenderEngine6createERKNS3_24RenderEngineCreationArgsEE3$_1NS_9allocatorIS8_EEFNS_10unique_ptrIS4_NS_14default_deleteIS4_EEEEvEEclEv$fb147fdbd0638d73632d1b87d1d565c9+40) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #06 pc 0000000000276c28 /system/bin/surfaceflinger (android::renderengine::threaded::RenderEngineThreaded::threadMain(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>)+376) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #07 pc 0000000000278f88 /system/bin/surfaceflinger (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (android::renderengine::threaded::RenderEngineThreaded::*)(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>), android::renderengine::threaded::RenderEngineThreaded*, std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()> > >(void*)+160) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #08 pc 00000000000b1780 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #09 pc 0000000000051264 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.963 14614 14614 E crash_dump64: unable to connect to activity manager: No such file or directory
12-12 20:39:51.963 633 633 E tombstoned: Tombstone written to: tombstone_15
12-12 20:39:51.966 0 0 I [3: init: 1] init: Untracked pid 14614 exited with status 0
12-12 20:39:51.972 0 0 I [3: init: 1] init: Service 'surfaceflinger' (pid 14606) received signal 6
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'surfaceflinger' (pid 14606) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 14606 in 0ms
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'zygote' (pid 14232) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 0 pid 14232 in 0ms
12-12 20:39:51.974 0 0 I [0: init: 1] init: Untracked pid 14616 exited with status 0
12-12 20:39:51.975 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.qcom.rc:920)
12-12 20:39:51.975 0 0 I [0: init: 1] init: Sending signal 9 to service 'vendor.hwcomposer-2-1' (pid 742) process group...
12-12 20:39:51.975 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 742 in 0ms
12-12 20:39:51.976 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.target.rc:459)
12-12 20:39:51.977 0 0 I [0: init: 1] init: Sending signal 9 to service 'ppd' (pid 877) process group...
12-12 20:39:51.977 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 877 in 0ms
12-12 20:39:52.089 0 0 W [0:android.hardwar:14604] scm: secure world has been busy for 1 second!
12-12 20:39:52.227 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.229 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.260 0 0 I [0: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.272 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.276 0 0 I [2: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.278 0 0 I [2: kworker/u8:0: 6] sm5705_vbatocv_check: mode change to mix RS auto mode
12-12 20:39:52.282 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 6 1 11 -1 1 6 1 9 1>, temp_fg = 363 ,p_curr_cal = 0x9b, n_curr_cal = 0xa6, curr_offset = 0x1, volt_cal = 0x8000 ,fg_delta_volcal = 0x0
12-12 20:39:52.283 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 3 0 3 1 1 2 3 2 3>, p_curr_cal = 0x9b, n_curr_cal = 0xa7, mix_factor=0x47a ,batt_temp = 286
12-12 20:39:52.286 0 0 I [2: kworker/u8:0: 6] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.291 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xA0=0x1400, 0xAC=0x20a5, 0xAD=0x211b, 0xAE=0x21f7, 0xAF=0x2399, 0x28=0x0838, 0x2F=0x021a, 0x01=0xc401, SM5705_ID=0x000b
12-12 20:39:52.298 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xB0=0x0000, 0xBC=0x255e, 0xBD=0x283f, 0xBE=0x2d0c, 0xBF=0x2d17, 0x85=0x0064, 0x86=0x0196, 0x87=0x0ec4, 0x1F=0x0080, 0x94=0x0001 , 0x13=0x000f, 0x14=0x0000
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_get_all_value: chg_h=1, chg_f=0, chg_s=1, is_chg=0, ta_exist=1, v=3790, v_avg=3786, i=-248, i_avg=-91, ocv=3779, fg_t=363, b_t=286, cycle=38, soc=327, state=0x6
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_scaled_capacity: scaled capacity (32.7)
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_atomic_capacity: NOW(32), OLD(32)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_get_battery_info:Vnow(3790mV),Inow(-248mA),Imax(500mA),SOC(32%),Tbat(286),Tchg(326),Twpc(0)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_cisd_check: cisd off.
12-12 20:39:52.311 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_time_management: Charging Time : 1340 secs
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_temperature: HLT(800) HLR(750) HT(500), HR(450), LT(0), LR(50)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_swelling_check: status(1), swell_mode(0:0:0), cv(0x10cc), temp(286)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_fullcharged_check: Charging Mode : Normal
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_set_current_event: clear current event(now=0x0, value=0x4)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_mix_temp: mix_limit(0), temp(286), chg_temp(326), input_current(500)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_afc_temp: cable_type(4), chg_limit(0)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_monitor_work: Status(Charging), mode(Normal), Health(Good), Cable(4, 4, 1, 1), level(100%), cisd.cd(0), HV(NONE), sleep_mode(0), Cycle(-1)
12-12 20:39:52.325 0 0 I [2: kworker/2:1: 33] sm5705-charger: psy_chg_get_charge_type: psy_chg_get_charge_type charge_type(5)
12-12 20:39:52.325 0 0 I : [2: kworker/2:1: 33] sec_bat_get_property cable type = 4 sleep_mode = 0
12-12 20:39:52.327 0 0 I [2: kworker/2:1: 33] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.329 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.330 0 0 W [2:[email protected]: 743] healthd: battery l=32 v=3790 t=28.6 h=2 st=2 c=-248 fc=6000000 chg=u
12-12 20:39:52.332 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.609 0 0 E : [1: msm_watchdog: 32] [pet_watchdog] last_count : 502d6, new_count : 0, bark_time : 77fd3, bite_time : 8ffca
12-12 20:39:52.662 0 0 I [2: logd.reader: 594] logd: logdr: UID=2000 GID=2000 PID=14620 n tail=0 logMask=bf pid=0 start=0ns deadline=0ns
12-12 20:39:52.754 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:52.755 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:52.755 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:52.757 0 0 I [1: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:52.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:52.875 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:52.877 586 14624 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:52.877 586 14624 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:52.876 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:53.142 0 0 I : [1: kworker/u8:0: 6] etspi_work_func_debug ldo: 0, sleep: 0, tz: 1, type: unknown
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Load image request failed ret = -1, errno = 22
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Loading image failed with ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:58) Loading app (path - /vendor/firmware_mnt/image) skeymast failed: Invalid argument, size = 82112, ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:106) Fail to open session with QSEE
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:78) KM_TZOpenConnection FAILED [-3]
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1120) can't open connection to trustlet; error: -49
12-12 20:39:53.387 14604 14604 E [email protected]: Error -1 opening keystore keymaster1 device
12-12 20:39:53.387 14604 14604 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1028) entered device_close function
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:119) There is no opened session. ref cnt = 0
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1040) can't close connection with trustlet; error: -49
12-12 20:39:53.387 14604 14604 E HidlServiceManagement: Could not find instance 'default' in library [email protected] Keeping library open.
12-12 20:39:53.387 14604 14604 E LegacySupport: Could not get passthrough implementation for [email protected]::IKeymasterDevice/default.
12-12 20:39:53.386 0 0 E : [0:android.hardwar:14604] scm_call failed: func id 0x72000101, ret: -12, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_load_app: scm_call to load app failed
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_ioctl: failed load_app request: -22
12-12 20:39:53.390 0 0 I [1: init: 1] init: Service 'vendor.keymaster-3-0' (pid 14604) exited with status 1
12-12 20:39:53.390 0 0 I [1: init: 1] init: Sending signal 9 to service 'vendor.keymaster-3-0' (pid 14604) process group...
12-12 20:39:53.390 0 0 I [1: init: 1] libprocessgroup: Successfully killed process cgroup uid 9999 pid 14604 in 0ms
12-12 20:39:53.755 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:53.756 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:53.756 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:53.757 0 0 I [0: init: 1] init: starting service 'vendor.keymaster-3-0'...
12-12 20:39:53.760 0 0 E [0: init: 1] libprocessgroup: Failed to make and chown /sys/fs/cgroup/uid_9999: Operation not permitted
12-12 20:39:53.760 0 0 E [0: init: 1] init: createProcessGroup(9999, 14626) failed for service 'vendor.keymaster-3-0': Operation not permitted
12-12 20:39:53.761 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:53.778 14626 14626 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
12-12 20:39:53.778 2 2 I [2:android.hardwar:14626] binder: 14626:14626 ioctl 40046210 7fe065faa4 returned -22
12-12 20:39:53.784 14626 14626 I [email protected]: Fetching keymaster device name default
12-12 20:39:53.786 2 2 W [2:android.hardwar:14626] QSEECOM: qseecom_load_app: App (skeymast) does'nt exist, loading apps for first time
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1057) entered device_open function
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_tc_api.c:65) Open MDFPP keymaster version 1.9.04
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_synchronization.c:27) sync init...OK
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:101) request 82112 bytes
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:45) qsc_start_app: buff_size: 82112
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x140c0
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: App is not loaded in QSEE
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: app_arch = 1, total_files = 8
12-12 20:39:53.875 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:53.876 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:53.878 586 14627 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:53.878 586 14627 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:53.877 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:54.562 0 0 I [2: kworker/2:1: 33] msm_thermal: msm_ts_print tsens[4:459][6:459][9:501][11:482][15:401]
12-12 20:39:54.756 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:54.757 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:54.757 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:54.758 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:54.876 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:54.877 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:54.878 586 14629 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:54.878 586 14629 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:54.878 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:55.086 0 0 W [0:android.hardwar:14626] scm: secure world has been busy for 1 second!
Click to expand...
Click to collapse
Hello, what version do you use? T825 or T820?
KeepingItCuttingEdge said:
ETA on the T820?
And BRAVO!!!
Click to expand...
Click to collapse
It will be uploaded soon after few tests
Good!. Very good! I installed my pad (s3 lte) and good working. lte is also working.
If someone install this OS & google service, do not reboot after finish OS install.
Before reboot, must install flamegapps and reboot.
Or else, a pad is bricking.
I tried several times..... and succeed.
Thank you so much Awesometic.
Awesometic said:
Hello, what version do you use? T825 or T820?
It will be uploaded soon after few tests
Click to expand...
Click to collapse
tested it on the T825 version
DOOOOGY said:
Good!. Very good! I installed my pad (s3 lte) and good working. lte is also working.
If someone install this OS & google service, do not reboot after finish OS install.
Before reboot, must install flamegapps and reboot.
Or else, a pad is bricking.
I tried several times..... and succeed.
Thank you so much Awesometic.
Click to expand...
Click to collapse
thanks for the tip, i'll try this later
I uploaded the new T820 image. Please test this one, wifi version users.
By the way, it seems like it is not that all the users can use my LOS 19.1 image. I need further investigation, if you are using T820/T825 and if you can't pass the boot logo screen then let me know the symptoms and your device information including the base firmware version. Logcat would be the best.
Hi there,
I have the problem that the tablet does not reconnect to the wifi when it is switched on or exits airplane mode.
Can you help me?
Regards Chris
Thanks Awesometic!!! Enjoy your coffee.
I got it working on my SM-T820 Wifi on my second try, and total time from start to finish was under an hour. I'm getting better at this...
DOOOOGY said:
If someone install this OS & google service, do not reboot after finish OS install.
Before reboot, must install flamegapps and reboot.
Or else, a pad is bricking.
Click to expand...
Click to collapse
Thanks very much for this very good advice. The reason that my first attempt failed was because I rebooted between the OS install and the GApps install, and it got stuck on the LineageOS logo after I installed FlameGApps.
Find of frustrating how the steps are inconsistent though. With LineageOS 18.1 and OpenGApps, I had to make sure I DID reboot between the OS and the GApps install, otherwise it wouldn't work. With LineageOS 19.1 and FlameGApps, I had to make sure I DID NOT reboot between the OS and GAppsInstall, otherwise it wouldn't work. Not blaming anyone; that's just the way it is when dealing with unofficial builds, but it's still nerve rattling when I think I might have bricked my device.
Thanks for the coffee
Yeah, I got some feedback about that issue. Currently, for this ROM, it is better to install the ROM and GApps at once, without rebooting between installing them.
Thanks for confirming that
ChrisHide said:
Hi there,
I have the problem that the tablet does not reconnect to the wifi when it is switched on or exits airplane mode.
Can you help me?
Regards Chris
Click to expand...
Click to collapse
Hello,
I need a logcat file while the issue occurs.
For me, I can use the WiFi after switching the airplane mode.
Awesometic said:
I uploaded the new T820 image. Please test this one, wifi version users.
By the way, it seems like it is not that all the users can use my LOS 19.1 image. I need further investigation, if you are using T820/T825 and if you can't pass the boot logo screen then let me know the symptoms and your device information including the base firmware version. Logcat would be the best.
Click to expand...
Click to collapse
Thank you for all this great work !
I installed it on my T820, I encountered no installation problem and now the rom is running perfectly and fast since yesterday.
In TWRP I formated everything before install, installed the rom, then the gapps without rebooting. Then reboot to system and voilà
Hi Awesometic. Thank you for your hard work.
I tried to flash Lineage OS 19.1 sadly couldn't get past Samsung Tab S3 logo.
Device: SM-T825
Baseband Version: T825XXU3CTA1
File system: ext4
I attached log file which I took while it was stuck on boot logo.