Hello everyone!
Yesterday I flashed kernel to my P900. (And I'm actually happy)
I have root access on tablet and permissive SELinux mode.
Trying to start Debian on my tablet. Android version: >5.0 (I do not remember exactly)
Here's log:
Code:
Checking loop device... MISSING
Creating loop device... OK
No user defined mount points
net.ipv4.ip_forward = 1
ERROR: ld.so: object 'libsigchain.so' from LD_PRELOAD cannot be preloaded: ignored.
Config file not found, using defaults!(/root/cfg/debian.img.config)
Starting first boot setup.......
ERROR: ld.so: object 'libsigchain.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object 'libsigchain.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object 'libsigchain.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object 'libsigchain.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object 'libsigchain.so' from LD_PRELOAD cannot be preloaded: ignored.
Creating User account (named debian)
ERROR: ld.so: object 'libsigchain.so' from LD_PRELOAD cannot be preloaded: ignored.
And that's it. It stucks every time. I'm already waiting 8-10 minutes. Maybe more.
Can anyone help?
P.S. Executing script under root through ADB
Related
It seems that prelink error when compile. How to fixed it? Need prelink-linux-ds.map?
~/dream_sapphire $ adb logcat |grep prelink
- waiting for device -
E/HAL ( 143): Cannot load library: link_image[1962]: 104 could not load needed library 'libgps.so' for 'gps.sapphire.so' (reserve_mem_region[831]: OOPS: 104 prelinked library 'libgps.so' mapped at 0x45fb8000, not at 0xa9700000)
E/QualcommCameraHardware( 105): FATAL ERROR: could not dlopen liboemcamera.so: Cannot load library: reserve_mem_region[831]: OOPS: 105 prelinked library 'liboemcamera.so' mapped at 0x40c0c000, not at 0xa9400000
hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
hi
i build a rom and it doesn't boot
i get a logcat and show these errors
E/NetlinkEvent( 152): NetlinkEvent::FindParam(): Parameter 'SWITCH_NAME' not found
E/Trace ( 1056): error opening trace file: No such file or directory (2)
E/HTC Acoustic( 1056): Fail to open /system/etc/AudioPara_HTC-GCC.csv -1.
E/BandwidthController( 1057): runIptablesCmd(): failed /system/bin/iptables -t raw -N bw_raw_PREROUTING res=256
E/AudioHardwareMSM76XXA( 1056): AudioStreamOutMSM72xx: Setting up correct values
E/dalvikvm( 1196): ERROR: couldn't find native method
E/dalvikvm( 1196): Requested: Ljava/lang/Daemons;.isShippingRom)Z
E/JNIHelp ( 1196): RegisterNatives failed for 'java/lang/Daemons', aborting
Click to expand...
Click to collapse
ok
These are my questions:
1.wich error is must intresting? and wich can be The main cause?
2.is these errors goes from kernel? how can i fix these?
devs please help me
tnx:crying:
INITIAL COMMUNIQUE:
...
"Samsung GALAXY CORE Prime"
("POWERED by android")
"metroPCS" ("t-mobile network")
"bong bong bong laa laa"
"buzz-buzz-buzz buzzzzzz"
(via usb cable to slackware--porteus variant: "Unable to open MTP device '[usb:001,013]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,014]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,015]'")
"buzz-buzz-buzz buzzzzzz"
("Unable to open MTP device '[usb:001,016]'")
"buzz-buzz-buzz" ...
...
System Recovery <3rd edition?> (up vol+pwr+home) appears normal for an os 5.1.1 Android.
(note: subject does not appreciate being called a "lollipop")
TRANSLATORS NOTES:
Android SM-G360T1, lmy47x.g360t1uvu1aofa, (unique s/n classified) not responding to Heimdall protocol...
Dreams of Replicant status wanning...
Suspect it (she?) is showing early stages of depression...
Z768G not so jealous now...suspect foul play ... >.> ... <.< ...
---
Heimdall output:
Code:
[email protected]:/mnt/sda3/.../prime# heimdall flash --RECOVERY /mnt/sda3/.../prime/TWRP/recovery.img --verbose
it's 3.0.2.0 i think
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
www glassechidna com au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
www glassechidna com au/donate
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[email protected]:/mnt/sda3/.../prime#
...
worth noting:
Code:
Manufacturer: "Sasmsung"
S/N: 0
Code:
ERROR: libusb...
Code:
MTP device '[usb:...
Code:
gingerbread man in spotlight...again...
...
any helpful tips for a more fruitful communication with this 'droid?
I'm getting this error. which I assume I am missing a few library/hal that is needed. Where can I find these files?
[971/971] including vendor/qcom/opensource/interfaces/wifi/supplicant/1.0/Androi
device/oneplus/oneplus2/camera/QCamera2/Android.mk: error: camera.msm8994 (SHARED_LIBRARIES android-arm) missing libqdMetaData (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
device/oneplus/oneplus2/camera/QCamera2/Android.mk: error: camera.msm8994 (SHARED_LIBRARIES android-arm) missing libqdutils (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:833: error: exiting from previous errors.
01:35:39 ckati failed with: exit status 1
#### failed to build some targets (03:06 (mm:ss)) ####