Actions
Issue #2281
closedFix boot (due missing libart.so?)
Start date:
09/28/2021
Due date:
% Done:
0%
Estimated time:
Resolution:
fixed
Device:
Galaxy Nexus (GT-I9250), Galaxy Note (GT-N7000), Galaxy Note 2 (GT-N7100), Galaxy Note 8.0 (N51xx), Galaxy S 2 (I9100), Galaxy S 3 (I9300), Galaxy S 3 4G (I9305), Galaxy Tab 2 10.1 (P51xx), Galaxy Tab 2 7.0 (P31xx)
Grant:
Type of work:
Build system integration
Updated by Denis 'GNUtoo' Carikli over 3 years ago
At boot, the device is stuck on the Replicant logo and when we add root to the boot.img we have (with adblogcat -b main):
01-01 00:53:47.795 26651 26651 D AndroidRuntime: >>>>>> START com.android.internal.os.ZygoteInit uid 0 <<<<<< 01-01 00:53:47.795 26651 26651 E JniInvocation: Failed to dlopen libart.so: dlopen failed: library "libart.so" not found 01-01 00:53:47.795 26651 26651 D AndroidRuntime: CheckJNI is OFF 01-01 00:53:47.795 26651 26651 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 26651 (zygote) 01-01 00:53:47.795 1926 1926 I DEBUG : property debug.db.uid not set; NOT waiting for gdb. 01-01 00:53:47.795 1926 1926 I DEBUG : HINT: adb shell setprop debug.db.uid 100000 01-01 00:53:47.795 1926 1926 I DEBUG : HINT: adb forward tcp:5039 tcp:5039 01-01 00:53:47.895 1926 1926 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 01-01 00:53:47.895 1926 1926 F DEBUG : Replicant Version: 'replicant-6.0' 01-01 00:53:47.900 1926 1926 F DEBUG : Build fingerprint: 'samsung/m0xx/m0:4.3/JSS15J/I9300XXUGMJ9:user/release-keys' 01-01 00:53:47.900 1926 1926 F DEBUG : Revision: '0' 01-01 00:53:47.900 1926 1926 F DEBUG : ABI: 'arm' 01-01 00:53:47.900 1926 1926 F DEBUG : pid: 26651, tid: 26651, name: zygote >>> zygote <<< 01-01 00:53:47.900 1926 1926 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 01-01 00:53:47.905 1926 1926 F DEBUG : r0 40407494 r1 beb4d8ac r2 beb4c550 r3 00000000 01-01 00:53:47.905 1926 1926 F DEBUG : r4 0000002b r5 ffffff8c r6 00000000 r7 beb4cd4c 01-01 00:53:47.905 1926 1926 F DEBUG : r8 beb4c550 r9 beb4c71c sl 403dad52 fp 403db6f5 01-01 00:53:47.905 1926 1926 F DEBUG : ip ffffffec sp beb4c530 lr 40371f7b pc 00000000 cpsr a00e0010 01-01 00:53:47.910 1926 1926 F DEBUG : 01-01 00:53:47.910 1926 1926 F DEBUG : backtrace: 01-01 00:53:47.910 1926 1926 F DEBUG : #00 pc 00000000 <unknown> 01-01 00:53:47.910 1926 1926 F DEBUG : #01 pc 00062f77 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime7startVmEPP7_JavaVMPP7_JNIEnvb+2386) 01-01 00:53:47.910 1926 1926 F DEBUG : #02 pc 000633ab /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEEb+334) 01-01 00:53:47.910 1926 1926 F DEBUG : #03 pc 00001729 /system/bin/app_process32 01-01 00:53:47.910 1926 1926 F DEBUG : #04 pc 00016699 /system/lib/libc.so (__libc_init+44) 01-01 00:53:47.910 1926 1926 F DEBUG : #05 pc 00001870 /system/bin/app_process32 01-01 00:53:48.170 1926 1926 F DEBUG : 01-01 00:53:48.170 1926 1926 F DEBUG : Tombstone written to: /data/tombstones/tombstone_02
Updated by Denis 'GNUtoo' Carikli over 3 years ago
- Device Galaxy Nexus (GT-I9250), Galaxy Note (GT-N7000), Galaxy Note 2 (GT-N7100), Galaxy Note 8.0 (N51xx), Galaxy S 2 (I9100), Galaxy S 3 4G (I9305), Galaxy Tab 2 10.1 (P51xx), Galaxy Tab 2 7.0 (P31xx) added
It probably affects all devices as libart probably got accidentally removed while trying to make Replicant 6 compile on Trisquel 9.
If I recall well I removed some host tools that removed libart to avoid fixing some host headers incompatibility but It might have removed target code as well.
Updated by Denis 'GNUtoo' Carikli over 3 years ago
- Status changed from New to Resolved
- Resolution set to fixed
This is now fixed: the patches that broke it were reverted.
Actions