OEM Unlock does not appear on the SM-A600T - Samsung Galaxy A6 Questions & Answers

Hello. When I go into Developer Settings on my Samsung Galaxy A6 (SM-A600T), OEM unlock is not displayed as an option. When I go to download mode (odin mode) to check the RMM state, the fields OEM lock and RMM state do not exist. I am running Android 8.0.0 and the software build number is R16NW.A600TUVU1ARIA. It has been more than 7 days and OEM unlock still doesn't appear. Please help me.

did you ever figure this out?

ctindell1981 said:
did you ever figure this out?
Click to expand...
Click to collapse
Nope. I am still struggling to find out what's wrong.

I went over to telegram and for a little hello. Or seems as though the bootloader is already unlocked. However we need some devs for making a proper twrp. This version of the a6 is USA only and is the only one with the exynos 7885.

Why can't I see the OEM Unlock toggle in Developer Settings if the bootloader is already unlocked?

Quick question.
ctindell1981 said:
I went over to telegram and for a little hello. Or seems as though the bootloader is already unlocked. However we need some devs for making a proper twrp. This version of the a6 is USA only and is the only one with the exynos 7885.
Click to expand...
Click to collapse
Still no luck on a proper TWRP?
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
ctindell1981 said:
I went over to telegram and for a little hello. Or seems as though the bootloader is already unlocked. However we need some devs for making a proper twrp. This version of the a6 is USA only and is the only one with the exynos 7885.
Click to expand...
Click to collapse
ctindell1981 said:
did you ever figure this out?
Click to expand...
Click to collapse
He never figured it but have you? Been trying to root this phone for months

BiHanCummings said:
Still no luck on a proper TWRP?
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
He never figured it but have you? Been trying to root this phone for months
Click to expand...
Click to collapse
So have I.

Still nothing. I apologise for such a long delayed response. I've a very chaotic life. I don't know how to build a TWRP fir the phone. The bootloader comes unlocked though. From my understanding any device with an exynos processor has the BL unlocked.

ctindell1981 said:
Still nothing. I apologise for such a long delayed response. I've a very chaotic life. I don't know how to build a TWRP fir the phone. The bootloader comes unlocked though. From my understanding any device with an exynos processor has the BL unlocked.
Click to expand...
Click to collapse
My previous phone had an exynos processor and was unlockable but it still displayed the OEM unlock option in Developer Settings. Why is the A600T different?

OEM Unlock Logcat
Here is the log that is generated when I open developer settings.
Code:
04-15 09:24:23.158 4025 6155 I vaultkeeper_service: VK 3.0.0 [Client] com.android.settings. => [Vault] RemoteLockControl. [CMD NO.] 357
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: [CMD:REGISTERED]
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: prepare done(0)
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: Don't need pre-process to access partition
04-15 09:24:23.159 4025 6155 I vaultkeeper_service: preProcessing done(0)
04-15 09:24:23.159 4025 6155 I TeeSysClient: open mode set to: 0 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:343]
04-15 09:24:23.159 4025 6155 I TeeSysClient: driver version: v6.3 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:71]
04-15 09:24:23.159 4025 6155 I TeeSysClient: driver open [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:84]
04-15 09:24:23.159 4025 6155 I TeeSysClient: Kinibi access granted by the driver [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:217]
04-15 09:24:23.200 4025 6155 I vaultkeeper_service: openSession done(session id : 3585, device id : 0)
04-15 09:24:23.200 4025 6155 I vaultkeeper_service: notify done(session id : 3585, device id : 0)
04-15 09:24:23.249 4025 6155 I vaultkeeper_service: waitNotification done(session id : 3585, device id : 0)
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: closeSession done(session id : 3585, device id : 0)
04-15 09:24:23.250 4025 6155 I TeeSysClient: driver closed [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:95]
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: cmdProcessing done(0/357)
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: int VWorker::postProcessing(client_rsp_t*): no request to access in steady
04-15 09:24:23.250 4025 6155 I vaultkeeper_service: postProcessing done(0)
04-15 09:24:23.250 4025 6155 I vaultkeeper_jni: runCommand Success.(TA ret = 0)
04-15 09:24:23.251 23997 23997 I RlcManager: query(void)
04-15 09:24:23.251 4025 6155 I vaultkeeper_service: VK 3.0.0 [Client] com.android.settings. => [Vault] RemoteLockControl. [CMD NO.] 5525
04-15 09:24:23.251 4025 6155 I vaultkeeper_service: [CMD:READ_UNSHELTERED]
04-15 09:24:23.251 4025 6155 I vaultkeeper_service: prepare done(0)
04-15 09:24:23.261 4025 6155 I vaultkeeper_service: All Zero
04-15 09:24:23.261 4025 6155 I vaultkeeper_service: preProcessing done(0)
04-15 09:24:23.261 4025 6155 I TeeSysClient: open mode set to: 0 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:343]
04-15 09:24:23.261 4025 6155 I TeeSysClient: driver version: v6.3 [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:71]
04-15 09:24:23.261 4025 6155 I TeeSysClient: driver open [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:84]
04-15 09:24:23.261 4025 6155 I TeeSysClient: Kinibi access granted by the driver [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/common.cpp:217]
04-15 09:24:23.309 4025 6155 I vaultkeeper_service: openSession done(session id : 3585, device id : 0)
04-15 09:24:23.309 4025 6155 I vaultkeeper_service: notify done(session id : 3585, device id : 0)
04-15 09:24:23.372 4025 6155 I vaultkeeper_service: waitNotification done(session id : 3585, device id : 0)
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: closeSession done(session id : 3585, device id : 0)
04-15 09:24:23.374 4025 6155 I TeeSysClient: driver closed [hardware/samsung_slsi/exynos7885/mobicore/ClientLib/src/driver.cpp:95]
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: cmdProcessing done(0/5525)
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: int VWorker::postProcessing(client_rsp_t*): no request to access in steady
04-15 09:24:23.374 4025 6155 I vaultkeeper_service: postProcessing done(0)
04-15 09:24:23.374 4025 6155 I vaultkeeper_jni: runCommand Success.(TA ret = 0)
04-15 09:24:23.375 23997 23997 D DevelopmentSettings: enableUnlock rlcState :
04-15 09:24:23.375 23997 23997 D DevelopmentSettings: enableUnlock : 1 = /dev/block/persistent / 2 = 1

Here is a picture of developer settings.

This phone is equipped with a Exynos 7884 CPU. We only need a custom recovery. When will someone be nice to make a TWRP for this phone?

So I'm starting to try to wrap my head around compiling a TWRP for our phones. Once I start to better understand I will seek out testers. If anyone wants to help me so I can get on the fasttrack and whatnot so this can come into fruition quicker. Please, PM me. I'm a single, full-time father and caregiver to my disabled father, so my life is chaotic and sometimes it takes me a while to get back to a project. Communication with me is easier through Facebook.

couldnt u just use the source from the other variants and add the files for this variant and compile for our device instead of the others??

Related

Logcat Question...

I need getting this over and over every 20-30 seconds in my logcat:
04-15 12:23:17.428: WARN/googleanalytics(3223): Problem with socket or streams.
04-15 12:23:17.428: WARN/googleanalytics(3223): java.net.ConnectException: www.google-analytics.com/127.0.0.1:80 - Connection refused
04-15 12:23:17.428: WARN/googleanalytics(3223): at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:255)
04-15 12:23:17.428: WARN/googleanalytics(3223): at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:535)
04-15 12:23:17.428: WARN/googleanalytics(3223): at java.net.Socket.connect(Socket.java:1054)
04-15 12:23:17.428: WARN/googleanalytics(3223): at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
04-15 12:23:17.428: WARN/googleanalytics(3223): at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
04-15 12:23:17.428: WARN/googleanalytics(3223): at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
04-15 12:23:17.428: WARN/googleanalytics(3223): at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingEvents(Unknown Source)
04-15 12:23:17.428: WARN/googleanalytics(3223): at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
04-15 12:23:17.428: WARN/googleanalytics(3223): at android.os.Handler.handleCallback(Handler.java:587)
04-15 12:23:17.428: WARN/googleanalytics(3223): at android.os.Handler.dispatchMessage(Handler.java:92)
04-15 12:23:17.428: WARN/googleanalytics(3223): at android.os.Looper.loop(Looper.java:123)
04-15 12:23:17.428: WARN/googleanalytics(3223): at android.os.HandlerThread.run(HandlerThread.java:60)
04-15 12:23:17.428: WARN/googleanalytics(3223): Dispatcher thinks it finished, but there were 455 failed events
Is this normal? Draining my battery? I have a good internet connection.....
Looks like that url is dead. I suspect an app with buggy ad retrieval code.
Do you have a modified hosts file or adfree installed? (this does not modify the url though)
Ad Free is installed. Think this is affecting battery at all?
Well its doing less work (network) than when it would successfully pull an ad on a schedule. So battery life should be better
kthxbye.....

[Q] Signal drops

Hi, I was having strange signal drop issues, because the signal drops from 3 or 4 bars to nothing, at any moment and I just get that when my signal drops, I have this in the logcat.
Code:
04-15 02:33:05.447 D/AT ( 964): dlc[5] atchannel: at_send_command_full() s_commandmutex[5] UNLOCKED, tid:134936, err - 0
04-15 02:33:05.447 D/AT ( 964): dlc[5] atchannel: at_send_command_full() end; err:0
04-15 02:33:05.447 D/AT ( 964): dlc[5] atchannel: at_send_command_singleline() end; err:0
04-15 02:33:05.447 D/RILC ( 964): [0604]< LGE_GET_HSDUPA_VALUES fails by E_GENERIC_FAILURE
04-15 02:33:05.447 D/RIL ( 964): dlc[5] lge-ril: requestInterface(LGE_GET_HSDUPA_VALUES) invoking *requestFunction(req:291, data: 0x00000000, len:0)...DONE
04-15 02:33:05.447 D/RIL ( 964): lge-ril: RIL_RequestDataCleanup START
04-15 02:33:05.447 D/RIL ( 964): lge-ril: RIL_RequestDataCleanup END
04-15 02:33:05.447 D/RIL ( 964): dlc[5] lge-ril: requestInterface(LGE_GET_HSDUPA_VALUES) handled
04-15 02:33:05.447 D/RIL ( 964): dlc[5]: lge-ril: waitForMessage() START. tid - 134936, head - 0x0, No of pending reqs - 0, srv state - 1
04-15 02:33:05.447 D/RIL ( 964): dlc[5] lge-ril: waitForMessage waiting for message. thread id - 134936
04-15 02:33:05.447 D/RILJ ( 2180): removeRequest() LGE_GET_HSDUPA_VALUES
04-15 02:33:05.447 D/RILJ ( 2180): [0604]< LGE_GET_HSDUPA_VALUES error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
04-15 02:33:05.447 D/GSM ( 2180): nitzName = null
04-15 02:33:05.447 E/GSM ( 2180): RIL implementation has returned an error where it must succeedcom.android.internal.telephony.CommandException: GENERIC_FAILURE
04-15 02:33:05.447 D/GSM ( 2180): Poll ServiceState done: oldSS=[0 home IntRoam: 0 VIVO VIVO 72410 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] newSS=[0 home IntRoam: 0 VIVO VIVO 72410 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] oldGprs=0 newGprs=0 oldType=EDGE newType=EDGE
04-15 02:33:05.447 E/GSM ( 2180): isRilReset = false
In this code, I think that the most important lines are the three last ones, who haves the errors, I want to know, if it's a BB problem, because I tried 725Q, 725L, 218 from CM7, and even tried CIS 20c, I tried to get back to all stock, but I have these signal drops in stock too.
Thanks in advance for help
Have you tried to match the ril with the baseband?
If not try the getril app from play store.
andresilva said:
Have you tried to match the ril with the baseband?
If not try the getril app from play store.
Click to expand...
Click to collapse
All the BB tested was matched with the corresponding RIL, now I'm using V20q BB + V20q RIL, and the problem persists.
Same BB , same RIL here and the same problem. Any fix for this ?
If you are running CM7 on your phone you should stick to V10 froyo BB and RIL for best compatibility. Depending on which mobile carrier you will get different varying results with different versions. I'm using Halebop (sweden) and for me 0725 (V10) seems to give the best results and lesser signal losses.
Skickat från min Optimus 2X via Tapatalk 2

Modules on New JB Kernel

Has anyone else tried compiling and loading kernel modules for the new ROM?
I'm getting panics like this just after returning from the module_init function, even in a "hello world" style module that does absolutely nothing.
Guessing it won't work until we get the new kernel sources. (This was from compiling against a vanilla 3.1.10 tree).
Anyone know if it's possible to run the new stock Jelly Bean ROM with the ICS kernel?
Code:
<1>[13:03:10 00:11:38.645] Unable to handle kernel paging request at virtual address e7be5484
<1>[13:03:10 00:11:38.645] pgd = d37a0000
<1>[13:03:10 00:11:38.645] [e7be5484] *pgd=a6941811, *pte=00000000, *ppte=00000000
<0>[13:03:10 00:11:38.645] Internal error: Oops: 7 [#1] PREEMPT SMP
<4>[13:03:10 00:11:38.645] Modules linked in: max8971_forcer(-) bcmdhd raw_ip_net gator
<4>[13:03:10 00:11:38.645] CPU: 1 Not tainted (3.1.10-gedcab5a #1)
<4>[13:03:10 00:11:38.645] PC is at module_put+0x50/0x128
<4>[13:03:10 00:11:38.645] LR is at sys_init_module+0x1830/0x1a18
<4>[13:03:10 00:11:38.645] pc : [<c00a0a74>] lr : [<c00a377c>] psr: a0000013
<4>[13:03:10 00:11:38.645] sp : def8ded0 ip : def8def8 fp : def8def4
<4>[13:03:10 00:11:38.645] r10: 0000001c r9 : 00000024 r8 : 00000001
<4>[13:03:10 00:11:38.645] r7 : c00a377c r6 : 00000002 r5 : bf0807f8 r4 : bf0807f8
<4>[13:03:10 00:11:38.645] r3 : def8c000 r2 : e6ac4484 r1 : 01121000 r0 : 00000001
<4>[13:03:10 00:11:38.645] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[13:03:10 00:11:38.645] Control: 10c5387d Table: 937a004a DAC: 00000015
arararagi said:
Has anyone else tried compiling and loading kernel modules for the new ROM?
I'm getting panics like this just after returning from the module_init function, even in a "hello world" style module that does absolutely nothing.
Guessing it won't work until we get the new kernel sources. (This was from compiling against a vanilla 3.1.10 tree).
Anyone know if it's possible to run the new stock Jelly Bean ROM with the ICS kernel?
Code:
<1>[13:03:10 00:11:38.645] Unable to handle kernel paging request at virtual address e7be5484
<1>[13:03:10 00:11:38.645] pgd = d37a0000
<1>[13:03:10 00:11:38.645] [e7be5484] *pgd=a6941811, *pte=00000000, *ppte=00000000
<0>[13:03:10 00:11:38.645] Internal error: Oops: 7 [#1] PREEMPT SMP
<4>[13:03:10 00:11:38.645] Modules linked in: max8971_forcer(-) bcmdhd raw_ip_net gator
<4>[13:03:10 00:11:38.645] CPU: 1 Not tainted (3.1.10-gedcab5a #1)
<4>[13:03:10 00:11:38.645] PC is at module_put+0x50/0x128
<4>[13:03:10 00:11:38.645] LR is at sys_init_module+0x1830/0x1a18
<4>[13:03:10 00:11:38.645] pc : [<c00a0a74>] lr : [<c00a377c>] psr: a0000013
<4>[13:03:10 00:11:38.645] sp : def8ded0 ip : def8def8 fp : def8def4
<4>[13:03:10 00:11:38.645] r10: 0000001c r9 : 00000024 r8 : 00000001
<4>[13:03:10 00:11:38.645] r7 : c00a377c r6 : 00000002 r5 : bf0807f8 r4 : bf0807f8
<4>[13:03:10 00:11:38.645] r3 : def8c000 r2 : e6ac4484 r1 : 01121000 r0 : 00000001
<4>[13:03:10 00:11:38.645] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[13:03:10 00:11:38.645] Control: 10c5387d Table: 937a004a DAC: 00000015
Click to expand...
Click to collapse
I red just now the problem you posted and it's interesting, but since we got the JB sources...
It may be interesting still if we have some interesting feature from old kernel to port in new one.
Anyway, just for "developer sport" is interesting to know whats was specifically the fact or the code which can't make run modules.
Pesach85 said:
I red just now the problem you posted and it's interesting, but since we got the JB sources...
It may be interesting still if we have some interesting feature from old kernel to port in new one.
Anyway, just for "developer sport" is interesting to know whats was specifically the fact or the code which can't make run modules.
Click to expand...
Click to collapse
I think it was mostly to do with the compiler or flags used.
Not really worth investigating any more now that we can just change anything in the kernel sources.
It is problem when compiling with gnueabihf modules don't load.
Sent from my LG-P880 using xda app-developers app

[Q&A] [FreeXperia Project] AOSP Android 5.x.x

Q&A for [FreeXperia Project] AOSP Android 5.x.x
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FreeXperia Project] AOSP Android 5.x.x. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Getting issues with modem from logcat:
Code:
<6>[ 224.145049] pil-q6v5-mss fc880000.qcom,mss: mba: loading from 0x0d100000 to 0x0d13a000
<4>[ 224.151677] ------------[ cut here ]------------
<4>[ 224.155406] WARNING: at kernel/irq/manage.c:428 enable_irq+0x60/0x74()
<4>[ 224.161837] Unbalanced enable for IRQ 413
<6>[ 224.165888] Modules linked in:
<6>[ 224.165915] [<c010bf04>] (unwind_backtrace+0x0/0x11c) from [<c0194c58>] (warn_slowpath_common+0x4c/0x64)
<6>[ 224.165932] [<c0194c58>] (warn_slowpath_common+0x4c/0x64) from [<c0194c9c>] (warn_slowpath_fmt+0x2c/0x3c)
<6>[ 224.165950] [<c0194c9c>] (warn_slowpath_fmt+0x2c/0x3c) from [<c01f3d7c>] (enable_irq+0x60/0x74)
<6>[ 224.165972] [<c01f3d7c>] (enable_irq+0x60/0x74) from [<c01312fc>] (pil_boot+0x7d8/0x9cc)
<6>[ 224.165990] [<c01312fc>] (pil_boot+0x7d8/0x9cc) from [<c013374c>] (mss_start+0x24/0x5c)
<6>[ 224.166009] [<c013374c>] (mss_start+0x24/0x5c) from [<c0162fc8>] (subsystem_get+0x94/0x168)
<6>[ 224.166030] [<c0162fc8>] (subsystem_get+0x94/0x168) from [<c0145094>] (msm_ipc_load_default_node+0x30/0x6c)
<6>[ 224.166047] [<c0145094>] (msm_ipc_load_default_node+0x30/0x6c) from [<c014a428>] (msm_ipc_router_ioctl+0xf0/0x2b8)
<6>[ 224.166065] [<c014a428>] (msm_ipc_router_ioctl+0xf0/0x2b8) from [<c0764cc8>] (sock_ioctl+0x228/0x278)
<6>[ 224.166086] [<c0764cc8>] (sock_ioctl+0x228/0x278) from [<c0263074>] (vfs_ioctl+0x28/0x3c)
<6>[ 224.166103] [<c0263074>] (vfs_ioctl+0x28/0x3c) from [<c0263ab8>] (do_vfs_ioctl+0x484/0x574)
<6>[ 224.166119] [<c0263ab8>] (do_vfs_ioctl+0x484/0x574) from [<c0263bf0>] (sys_ioctl+0x48/0x74)
<6>[ 224.166138] [<c0263bf0>] (sys_ioctl+0x48/0x74) from [<c0105ea0>] (ret_fast_syscall+0x0/0x30)
<4>[ 224.166149] ---[ end trace 1ffe67af4bf01ba1 ]---
<3>[ 224.205132] pil-q6v5-mss fc880000.qcom,mss: PBL returned unexpected status -284491765
<3>[ 224.212540] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to bring out of reset
<3>[ 224.219243] modem_notifier_cb: sysmon_send_event error -19
<3>[ 224.224639] M-Notify: General: 5
<3>[ 224.227804] msm_ipc_load_default_node: Failed to load modem
I reported this over in the kernel thread http://forum.xda-developers.com/showpost.php?p=57625416&postcount=23 it appears everything is still broken.
Also Wifi kills the whole system:
Code:
I/WifiHAL ( 652): Initialized Wifi HAL Successfully; vendor cmd = 103
D/wifi ( 652): Did set static halHandle = 0xafa4e040
D/wifi ( 652): halHandle = 0xafa4e040, mVM = 0xb505c280, mCls = 0x300ec6
E/wifi ( 652): getStaticLongField sWifiHalHandle 0xa06f381c
D/wifi ( 652): array field set
W/Adreno-EGL( 198): <qeglDrvAPI_eglDupNativeFenceFDANDROID:6527>: EGL_BAD_PARAMETER
W/SurfaceFlinger( 198): captureScreen: failed to dup sync khr object
E/audio_a2dp_hw( 241): adev_set_parameters: ERROR: set param called even when stream out is null
F/libc ( 652): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4300001 in tid 1595 (WifiStateMachin)
I/WifiNative-HAL( 652): Waiting for HAL events mWifiHalHandle=-1348149184
D/wifi ( 652): waitForHalEvents called, vm = 0xb505c280, obj = 0x300ec6, env = 0xafd22320
E/wifi ( 652): getStaticLongField sWifiHalHandle 0x9aa39b1c
I/DEBUG ( 238): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 238): Build fingerprint: 'Sony/aosp_d5803/aries:5.0.2/LRX22G/root12250659:userdebug/test-keys'
I/DEBUG ( 238): Revision: '0'
I/DEBUG ( 238): ABI: 'arm'
I/DEBUG ( 238): pid: 652, tid: 1595, name: WifiStateMachin >>> system_server <<<
I/DEBUG ( 238): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4300001
I/DEBUG ( 238): r0 04300001 r1 b3f279f8 r2 b3f1a885 r3 ffffffa8
I/DEBUG ( 238): r4 00000000 r5 04300001 r6 00000000 r7 b3f27dcc
I/DEBUG ( 238): r8 b3f1a885 r9 a1e4b400 sl 00000001 fp 130337c0
I/DEBUG ( 238): ip b3f27f20 sp a06f3820 lr b3f1dd4d pc b3f1dd4c cpsr 600d0030
I/DEBUG ( 238):
I/DEBUG ( 238): backtrace:
I/DEBUG ( 238): #00 pc 00007d4c /system/lib/libwifi-service.so (getWifiHandle(wifi_interface_info*)+5)
I/DEBUG ( 238): #01 pc 00007d53 /system/lib/libwifi-service.so (getHalInfo(wifi_interface_info*)+2)
I/DEBUG ( 238): #02 pc 0000b37d /system/lib/libwifi-service.so (wifi_get_link_stats+28)
I/DEBUG ( 238): #03 pc 0000421d /system/lib/libwifi-service.so
I/DEBUG ( 238): #04 pc 0003623d /data/dalvik-cache/arm/[email protected]@[email protected]
E/Sensors ( 4229): sns_smr_util.c(104):Unable to initialize service 256 with QCCI, timed out (10000 ms)
E/Sensors ( 4229): sns_sam_mr.c(1016):Unable to initialize service 0 with QCCI
E/Sensors ( 4229): sns_sam_mr.c(1111):Unable to acquire service handle 0
E/Sensors ( 4229): mag_cal.c(1603):mag_cal_sam_init: Unknown UUID(1) 00000000-0000-0000
E/Sensors ( 4229): mag_cal.c(1608):mag_cal_sam_init: Unknown UUID(2) 0000-000000000000
E/Sensors ( 4229): sns_sam.c(4432):Failed to register algorithm service 16 with SAM
I/DEBUG ( 238):
I/DEBUG ( 238): Tombstone written to: /data/tombstones/tombstone_01
I/ServiceManager( 196): service 'connectivity' died
I/ServiceManager( 196): service 'servicediscovery' died
W/Sensors ( 2552): sensorservice died [0xacc5e0c0]
I/ServiceManager( 196): service 'updatelock' died
I/ServiceManager( 196): service 'notification' died
I/ServiceManager( 196): service 'devicestoragemonitor' died
I/ServiceManager( 196): service 'location' died
I/ServiceManager( 196): service 'country_detector' died
I/ServiceManager( 196): service 'search' died
I/ServiceManager( 196): service 'dropbox' died
any reason aries isn't built ? at least not that I could find on the fxp open source repo.
https://github.com/CyanogenMod/andr...mmit/61f48baf5669c2a21b0a510515c985dec87617b5
fixes this problem
The guide for building AOSP is not clear for certain points,
For devices with Qualcomm wireless hardware, you need to build a Prima or Pronto WLAN module in order to get Wi-Fi working. Follow the instructions below to do this.
Then compile the module by entering the device specific command listed below.​Which should we follow for z3-compact, as device is not mentioned:
Prima?
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j12 -C M=$PWD CONFIG_PRIMA_WLAN=m CONFIG_PRIMA_WLAN_LFR=y KERNEL_BUILD=1 WLAN_ROOT=$PWD​
Once the compilation is finished, the wlan.ko module can be found in the prima folder.​Where do we put wlan.ko ?
Also,
the guide for AOSP has the kernel and wifi repos in the local manifest, does it build them during compilation or do we have to build them manually|separately, and then copy the kernel and wifi module before compiling ROM?
Thank you for your time,
hoping to see a fully working AOSP soon, keeping fingers crossed.
As it is a shame to see a phone with great HW and design dragging behind the rest.
I hope to see Sony advance and reach full capabilities
Any news about a working camera for 3.10 kernel and AOSP rom ?
Envoyé de mon Xperia Z3C en utilisant Tapatalk

[VNS-L31][EMUI4.1] RustyKernel [P9 Lite]

Disclaimer:
I am not responsible for the outcome of you flashing this software, please backup your current boot partition before flashing this kernel.
Click to expand...
Click to collapse
While I will take some credit for this work, I am not a Developer; I'm a hobbyist - I'll accept any help I can get to improve this kernel.
Downloads are in the download section
Source RUSTY-VNS
Credits:
@twicejr
@kwoktopus
Changes from stock:
2017-03-16 No-Root
2017-03-16 Root
3.10.102
Optimized build flags
Intelliactive CPU Governor
RustyKernel-EMUI4.1_hi6250-2017-03-17
RustyKernel-PA6.0.1_hi6250-2017-03-17 - Lockscreen bug, disable lockscreen security before flashing (PIN/Patten/Password)
Intelliplug Hotplug
Thunderplug Hotplug
PA 6.0.1 Support
Known bugs:
Kernel Adiutor:
Code:
big: Failed to load frequencies
. They're running, just not being logged.
PA version has a lockscreen bug - disable secure lockscreen before flashing
XDA:DevDB Information
P9 Lite Kernel, Kernel for the Huawei P9 Lite
Contributors
Carlyle_f
Source Code: https://github.com/carlyle-felix/RUSTY-VNS
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 2017-03-17
Beta Release Date: 2017-03-16
Created 2017-03-16
Last Updated 2017-03-17
Reserved
Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.
You can make oeminfo l31c636
pilgrim011 said:
Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.
Click to expand...
Click to collapse
Thanks man, I will look into OTG. Also, next releases will all have root
Sent from my HUAWEI VNS-L31 using Tapatalk
http://cloud.tapatalk.com/s/58cb6f4e67c55/RustyKernel_hi6250-2017-03-16.zip
Testers please leave feedback
Intelliplug and thunder plug hotplugs
Sent from my HUAWEI VNS-L31 using Tapatalk
Since this kernel supports PA, does it support LineageOS 13, or 14/RR?
dariomrk said:
Since this kernel supports PA, does it support LineageOS 13, or 14/RR?
Click to expand...
Click to collapse
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.
dady000 said:
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.
Click to expand...
Click to collapse
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
No, not yet, I will try it later. What I tried is the Avsky's kernel.
What are the advantages of using this kernel? And how do you install it? Noob here
SALVO9 said:
What are the advantages of using this kernel? And how do you install it? Noob here
Click to expand...
Click to collapse
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:
Carlyle_f said:
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:
Click to expand...
Click to collapse
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one
SALVO9 said:
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one
Click to expand...
Click to collapse
Alright, the benefits of this kernel is listed under changelog in OP
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0
Delete
dady000 said:
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0
Click to expand...
Click to collapse
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock before flashing kernel. huge security breach but should satisfy those who are okay with slide to unlock for now.
Carlyle_f said:
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock. huge security breach but should satisfy those who are okay with slide to unlock for now.
Click to expand...
Click to collapse
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.
dady000 said:
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.
Click to expand...
Click to collapse
hi can you please try the new build before i include it in OP:
https://forum.xda-developers.com/devdb/project/dl/?id=23699
Considering kernel is essential to make your device work, if you put a incompatible kernel on your device, what are the consequences?
Will the recovery still be bootable considering it has its own partition. In case the recovery is bootable, I'm willing to test on my VNS-L31.
Also in that case i could try on other roms, example CM13, Los14, etc...

Categories

Resources