Hi,
If you're a developer, I need your help.
I am running the following:
Android 2.3.4
Baseband I9100XXKH3
Kernel 2.6.35.11-ninphetamine-2.0.5+ ninpo at titan #20
Version Lite'ning Rom v6.1 XXKH3
I would like to compile a module (usb serial driver ftdi_sio.ko). For that I need the kernel source code. I found github.com /Ninpo /ninphetamine and got as far as compiling the module and insmod it, but I got in dmesg
"ftdi_sio: version magic '2.6.35.11-ninphetamine-2.0.5 SMP preempt mod_unload ARMv7 ' should be '2.6.35.11-ninphetamine-2.0.5+ SMP preempt mod_unload ARMv7 '
My problem I assume is that the source for ninphetamine I use, Android-galaxys2-ninphetamine-2d1ffbc, is not the right one. I can't find on the web the right source code version (2.0.5+), not to mention 2.1.3.
Anyone can point to the source code for me? (on a server that is running, kernel.org is on maintenance)
I am also quite open to install another ROM, kernel or other... even if possible one that has by default ftdi_sio.ko module running by default.
Thanks in advance for your responses.
edit:
I have now figured out so much, I can hack a bit to be able to insmod the modules:
- had to manually edit .config (replace ninphetamine-2.0.5 by ninphetamine-2.0.5+)
- make menuconfig modules ARCH=arm CROSS_COMPILE=arm-linux-androideabi-
- make drivers/usb/serial/*.ko ARCH=arm CROSS_COMPILE=arm-linux-androideabi- EXTRA_CFLAGS=-fno-pic
(it seems this -fno-pic was required for that version of tools, but does not work for all modules either)
=> it would still be nice to have access to exact source/config used to compile a ROM/kernel as well as the tools used to build it.
Now both modules load, but when I plug my device I am back to start with dmesg:
- usb 2-1: new full speed USB device using s3c_otghcd and address 2
- usb 2-1: device v0403 p6001 is not supported
- host_notify: ndev name=s3c_otghcd: from state=0 -> to state=5
- otg_dbg: in otg_handle_interrupt()::00087
- => Port Interrupt
- otg_dbg: in process_port_intr()::00271
- => port enable/disable changed
- hub 2-0:1.0: unable to enumerate USB device on port 1
Hope anyone get a clue.
Bump Bump Bump
A nice piece of advice was found here:
http://forum.xda-developers.com/showthread.php?p=18081882#post18081882
I'm working on a device directory to get CM7 building for the Galaxy Player 5.0 USA. I'm using Entropy512's kernel and copying some things out of vzwtab mostly, but there's some parameters in the BoardConfig.mk that I'm not sure how to find out. The Galaxy Player 5.0 seems to be unique among the example galaxy-based devices I could find in having only mmc partitions. So does anyone know what the proper values should be for:
BOARD_KERNEL_BASE
BOARD_NAND_PAGE_SIZE
BOARD_FLASH_BLOCK_SIZE
BOARD_PAGE_SIZE
As far as I can tell the BOARD_KERNEL_BASE is supposed to be the offset into the boot.img where the kernel can be found? But Samsungs don't use the boot.img so does this paremeter make sense? The various samsung devices all define this value though, and with different values, so maybe it means something else..
I found this in the make file in arch/arm of Entrophy512's code.
I think this is what you need for BOARD_KERNEL_BASE ...
HTML:
# The byte offset of the kernel image in RAM from the start of RAM.
TEXT_OFFSET := $(textofs-y)
Above that textofs-y was defined as
HTML:
textofs-y := 0x00008000
textofs-$(CONFIG_ARCH_CLPS711X) := 0x00028000
# We don't want the htc bootloader to corrupt kernel during resume
textofs-$(CONFIG_PM_H1940) := 0x00108000
# SA1111 DMA bug: we don't want the kernel to live in precious DMA-able memory
ifeq ($(CONFIG_ARCH_SA1100),y)
textofs-$(CONFIG_SA1111) := 0x00208000
endif
I think your value should be 0x00008000 ...
Thanks for that! A bit of googling on TEXT_OFFSET led me to PHYS_OFFSET, which is defined in arch/arm/mach-*/include/mach/memory.h, I think that's the value I need, it matches up in a couple of other kernels anyway. At least it matches up for galaxys2, but for mach-s5pv210 products, the PHYS_OFFSET is 0x30000000 but the kernel base is 0x32000000, I'm not sure why they don't match but I think one of those values should be galaxy player kernel base.
A quick grep turns this up...
./mach-s5pc100/include/mach/memory.h:#define PHYS_OFFSET UL(0x20000000)
s5pc100 is the name of the board for the Galaxy Player 5.0 right?
---------- Post added at 06:50 PM ---------- Previous post was at 06:08 PM ----------
HTML:
> As long as the zImage is placed within the 256MB range from the
> start of the memory, ZRELADDR (Address where the decompressed
> kernel will be placed, usually == PHYS_OFFSET + TEXT_OFFSET)
I think I may have it. It seems like we need both values PHYS_OFFSET +TEXT OFFSET.
So if that is what the BOARD_KERNEL_BASE is supposed to be then the value should be 0x20008000.
It would be nice to find a way to get the address off of our currently running devices. I'm going to look for some command or app that will say what it is.
References
http://www.spinics.net/lists/arm-kernel/msg89507.html
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/017614.html
Meticulus said:
A quick grep turns this up...
./mach-s5pc100/include/mach/memory.h:#define PHYS_OFFSET UL(0x20000000)
s5pc100 is the name of the board for the Galaxy Player 5.0 right?
Click to expand...
Click to collapse
According to /proc/config.gz from Entropy512's kernel it's the s5pv210.
Come on Meticulous, get back in the game! We need you!
Sent from my cm_tenderloin using Tapatalk
ambrice said:
According to /proc/config.gz from Entropy512's kernel it's the s5pv210.
Click to expand...
Click to collapse
According to the build.prop (ro.build.platform) it's s5pc110. I'm betting the boards are pretty close. I'm just trying to help out. This is all new to me...
Meticulus said:
I think I may have it. It seems like we need both values PHYS_OFFSET +TEXT OFFSET.
So if that is what the BOARD_KERNEL_BASE is supposed to be then the value should be 0x20008000.
It would be nice to find a way to get the address off of our currently running devices. I'm going to look for some command or app that will say what it is.
Click to expand...
Click to collapse
The source for the unpackbootimg is at system/core/mkbootimg/unpackbootimg.c, and it has the line:
printf("BOARD_KERNEL_BASE %08x\n", header.kernel_addr - 0x00008000);
So I think in the boot.img header header.kernel_addr is the ZRELADDR and the BOARD_KERNEL_BASE is supposed to be ZRELADDR - TEXT_OFFSET, which would be the PHYS_OFFSET.
Meticulus said:
According to the build.prop (ro.build.platform) it's s5pc110. I'm betting the boards are pretty close. I'm just trying to help out. This is all new to me...
Click to expand...
Click to collapse
I definitely appreciate the help! It's all new to me too..
They are very close:
http://odroid.foros-phpbb.com/t198-differences-between-s5pc110-and-s5pv210
I downloaded the official samsung released YP-G70 sources, and the defconfig has CONFIG_ARCH_S5PV210=y. So maybe they're close enough as far as the build.prop is concerned? I'm not sure what ro.build.platform is used for..
HTML:
./unpackbootimg -i zImage
BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE e19f8000
BOARD_PAGE_SIZE 24061976
Segmentation fault
It looks like that code can not unpack Entrophy512's kernel...
Also regarding the board name, look in "/system/lib/hw/". All the filenames are like "*.s5pc110.so"
I think that "s5pv210" is also the same board as the galaxy s...
I think, but am not sure, but some of those values there are placeholders on Samsung-based devices.
I was a dumbass and accidentally nuked my device tree so I need to rebuild it. I may instead just fork ambrice's to redo it.
Looks like this week/weekend will consist of some fun decobwebbing.
I would appreciate the help. My current state is that it builds an image but an assert fails when flashing the boot.img.
I've done some updates, I have a working kernel and recovery.
When I boot CM7 system_server crashes with this error:
Code:
I/Zygote ( 165): Accepting command socket connections
I/sysproc ( 223): Entered system_init()
I/sysproc ( 223): ServiceManager: 0x76d18
I/SurfaceFlinger( 223): SurfaceFlinger is starting
I/SurfaceFlinger( 223): dithering enabled
I/SurfaceFlinger( 223): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/HAL ( 223): load: module=/system/lib/hw/gralloc.s5pc110.so
E/HAL ( 223): Cannot load library: reloc_library[1311]: 165 cannot locate '__android_log_print'...
E/FramebufferNativeWindow( 223): Couldn't get gralloc module
system_server is linked against liblog.so which defines the __android_log_print, I think maybe this error is misleading. /system/lib/hw/gralloc.s5pc110.so is a library I pulled off the stock image as part of the vendor proprietaries.
stack trace in log shows it's crashing in android:isplayHardware::init(unsigned int) in libsurfaceflinger.so
Any ideas of things to try?
I'm just throwing this stuff out there but, assuming that "gralloc.s5pc110.so" is in the location specified, perhaps the "gralloc.s5pc110.so" is trying to locate "liblog.so" and it is "liblog.so" that is in the incorrect location (from stock). If "__android_log_print" is what it can not find and that is defined in "liblog.so" then that leads me to believe that it's not loaded and may be in the wrong location. So, you could compare the location from stock and put a duplicate there and see if that gets you any further. Maybe it's the "PATH" var in init.rc does not include the path for liblog.so...?
As a last resort you could try pulling a "gralloc.aries.so" and renaming it to match since the boards are so similar and see what that gets you?
In a couple days, I may join you on your quest to get a cm7 port. This is your project and you seem to be doing quite well but maybe I can get lucky help out.
Hello everyone,
I come to ask for help because I can not root my smartphone.
This is a 4G wiko ridge.
Qualcomm quad core 1.2Ghz processor
2Gb RAM and 16GB ROM
Rear Camera 13 Mp and before 5 Mp.
Android 4.4.4
Thank you for your help
chuppito said:
Hello everyone,
I come to ask for help because I can not root my smartphone.
This is a 4G wiko ridge.
Qualcomm quad core 1.2Ghz processor
2Gb RAM and 16GB ROM
Rear Camera 13 Mp and before 5 Mp.
Android 4.4.4
Thank you for your help
Click to expand...
Click to collapse
Up please
chuppito said:
Up please
Click to expand...
Click to collapse
Hi,
Now I have one Ridge FAB 4G... Kingroot and KingrootPC don't work for rooting.
Note: To install ADB drivers you can use Universal Android USB Driver (http://adbdriver.com/) or 15 seconds ADB Installer (http://forum.xda-developers.com/showthread.php?t=2588979)
I'm searching for rooting with similar devices, like ZTE Nubia V5 MAX
Hi,
Searching for a Custom Recovery, I try several from other similar devices... The only one with minimal success (but not working) is this from Cubot Zorro: http://www.needrom.com/download/english-cwm-for-cubot-zorro-001/
If you extract the cwm.img and execute it from FASTBOOT mode with command:
Code:
$ fastboot boot cwm.img
Then you boot to this recovery... but the screen is odd, also no USB support.
WARNING: Not flash any recovery.img from other devices!
manos78 said:
Hi,
Searching for a Custom Recovery, I try several from other similar devices... The only one with minimal success (but not working) is this from Cubot Zorro: http://www.needrom.com/download/english-cwm-for-cubot-zorro-001/
If you extract the cwm.img and execute it from FASTBOOT mode with command:
Code:
$ fastboot boot cwm.img
Then you boot to this recovery... but the screen is odd, also no USB support.
WARNING: Not flash any recovery.img from other devices!
Click to expand...
Click to collapse
Hi, thank you for recovery is a good start. I mainly need to give him the superuser (root) privileges.
thank you again
chuppito said:
Hi, thank you for recovery is a good start. I mainly need to give him the superuser (root) privileges.
thank you again
Click to expand...
Click to collapse
Hi Chuppito!
This recovery DON'T works! Painting in screen is odd, and the USB port for access using ADB is disabled (or don't work). But, it really boots and executes. My objective is found one custom recovery (from other device) with sufficient functionality to mount rw the /system partition and copy SuperSU.apk to it. At time this is not done!
However this is a good start, because sources and tools from a similar devices can be useful for stating.
I hope soon an experienced developer gets this device and provides some custom recovery... wihtout root any Android device is... useless!
Hi,
Wikomobile has already released the KERNEL source code. Go to: http://www.wikogeek.com/ and select "Ridge 4G".
I hope someone can compile a custom kernel based on this! :fingers-crossed:
And waiting for stock firmware published in: http://androidxda.com/download-wiko-stock-rom-models
Hi,
The "sources" are only for "Ridge 4G". Hovewer, the config file identifies also the "Ridge Fab 4G". Internal names are:
- Ridge 4G: l5510
- Ridge Fab 4G: l5320
After some tries for compile, I can't do it! The problem is that scripts likes to compile anything in the firmware... but I need only kernel/recovery. I appreciate if someone with experience can check this sources.
I hope soon someone can found a method for rooting these devices. Without root, the device is competly useless!!! :crying:
Hi,
More info about using the recovery from another device: the fstab file from sources of Ridge 4G, and the fstab from the recovery of the Cubot Zorro are different. So perhaps the only solution is compile from scratch a custom recovery using the sources provided by Wiko. I hope soon they publish also the sources for Ridge FAB.
**
Hi,
I hope someone with sufficient experience can compile TWRP for this device.
General guide at: http://forum.xda-developers.com/showthread.php?t=1943625
Files "/android/device/qcom/l5510/BoardConfig.mk" and "/android/device/qcom/l5510/recovery.fstab" are found in the source code
http://geek.wikoplus.com/index.php?tel=14bfa6bb14875e45bba028a21ed38046
BoardConfig.mk:
Code:
# Copyright (C) 2011 The Android Open-Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# config.mk
#
# Product-specific compile-time definitions.
#
ifeq ($(TARGET_ARCH),)
TARGET_ARCH := arm
endif
BOARD_USES_GENERIC_AUDIO := true
USE_CAMERA_STUB := true
-include $(QCPATH)/common/msm8916_32/BoardConfigVendor.mk
TARGET_COMPILE_WITH_MSM_KERNEL := true
#TODO: Fix-me: Setting TARGET_HAVE_HDMI_OUT to false
# to get rid of compilation error.
TARGET_HAVE_HDMI_OUT := false
TARGET_USES_OVERLAY := true
NUM_FRAMEBUFFER_SURFACE_BUFFERS := 3
TARGET_NO_BOOTLOADER := false
TARGET_NO_KERNEL := false
TARGET_NO_RADIOIMAGE := true
TARGET_NO_RPC := true
TARGET_GLOBAL_CFLAGS += -mfpu=neon -mfloat-abi=softfp
TARGET_GLOBAL_CPPFLAGS += -mfpu=neon -mfloat-abi=softfp
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := cortex-a53
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_HARDWARE_3D := false
TARGET_BOARD_PLATFORM := msm8916
TARGET_BOARD_PLATFORM_VENDOR_COMMON := msm8916_32
TARGET_BOOTLOADER_BOARD_NAME := msm8916
BOARD_KERNEL_BASE := 0x80000000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_KERNEL_TAGS_OFFSET := 0x01E00000
BOARD_RAMDISK_OFFSET := 0x02000000
# Enables Adreno RS driver
OVERRIDE_RS_DRIVER := libRSDriver_adreno.so
# Shader cache config options
# Maximum size of the GLES Shaders that can be cached for reuse.
# Increase the size if shaders of size greater than 12KB are used.
MAX_EGL_CACHE_KEY_SIZE := 12*1024
# Maximum GLES shader cache size for each app to store the compiled shader
# binaries. Decrease the size if RAM or Flash Storage size is a limitation
# of the device.
MAX_EGL_CACHE_SIZE := 2048*1024
# Use signed boot and recovery image
#TARGET_BOOTIMG_SIGNED := true
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE := ext4
BOARD_PERSISTIMAGE_FILE_SYSTEM_TYPE := ext4
# zgm remove - console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0
#BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900
.sdhci
BOARD_KERNEL_CMDLINE := androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci
BOARD_KERNEL_SEPARATED_DT := true
BOARD_EGL_CFG := device/qcom/l5510/egl.cfg
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x02000000 #32M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x02000000 #32M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1702887424 #1G+600M
#BOARD_USERDATAIMAGE_PARTITION_SIZE := 5122795872 #8GB
BOARD_USERDATAIMAGE_PARTITION_SIZE := 12936655872 #16GB
BOARD_CACHEIMAGE_PARTITION_SIZE := 274726912 #134217728
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
# Enable suspend during charger mode
BOARD_CHARGER_ENABLE_SUSPEND := true
# Add NON-HLOS files for ota upgrade
ADD_RADIO_FILES ?= true
# Added to indicate that protobuf-c is supported in this build
PROTOBUF_SUPPORTED := true
TARGET_USE_QCOM_BIONIC_OPTIMIZATION := true
TARGET_USES_ION := true
TARGET_USES_NEW_ION_API :=true
TARGET_USES_QCOM_BSP := true
TARGET_RECOVERY_UPDATER_LIBS := librecovery_updater_msm
TARGET_INIT_VENDOR_LIB := libinit_msm
TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/
#Add support for firmare upgrade on 8916
HAVE_SYNAPTICS_I2C_RMI4_FW_UPGRADE := true
#Add By YangRujin <2014.10.10> : support for enabling diag/adb port during pwroff chg
ENABLE_ADB_DIAG_IN_PWROFF_CHARGE := true
#Add By MickyHe <2014.11.11> : support for GTS widevine DRM
BOARD_WIDEVINE_OEMCRYPTO_LEVEL := 3
PRODUCT_BOOT_JARS := $(subst $(space),:,$(PRODUCT_BOOT_JARS))
recovery.fstab:
Code:
# Copyright (c) 2013, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of The Linux Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#<FFBAKK-335><20141210><encryption>xusong
#device mount point fstype [device2] [length=]
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check,length=-16384
/dev/block/mmcblk1p1 /sdcard vfat nosuid,nodev,barrier=1,data=ordered,nodelalloc wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
Please, help us to compile a Custom Recovery! :crying:
Hi,
No experienced developer likes to help us? :crying:
Hello,
I return to the subject, I still looking but I can not find.
Is someone about to try to find a solution?
thank you
chuppito said:
Hello,
I return to the subject, I still looking but I can not find.
Is someone about to try to find a solution?
thank you
Click to expand...
Click to collapse
What is the date your kernel was made?
Sent from my A0001 using XDA Free mobile app
Kernel Version
3.10.28
[email protected]#1
Fri Mar 13 13:30:47 CST 2015
chuppito said:
Kernel Version
3.10.28
[email protected]#1
Fri Mar 13 13:30:47 CST 2015
Click to expand...
Click to collapse
Wow, that's an extremely new kernel! Lol. Anyways I was going to suggest trying Towelroot but most kernels made after June 3rd, 2013 have been patched to the futex exploit but I've had limited success on a few phones with kernels made after that date.
Good luck!
Sent from my A0001 using XDA Free mobile app
towelroot v1 and 3 do not work
Hi,
The "exploit" way ins't a solution at the moment because no new exploits have found for the last Android kernel versions.
The only valid way is a Custom Recovery. At time, we're waiting for the flashing version of the stock ROM (Wiko don't published it yet!). However, we have some source code and we need to obtain a minimal custom recovery for mount system r/w and copy to it SuperSU. This is the only way at time for rooting this device!
manos78 said:
Hi,
The "exploit" way ins't a solution at the moment because no new exploits have found for the last Android kernel versions.
The only valid way is a Custom Recovery. At time, we're waiting for the flashing version of the stock ROM (Wiko don't published it yet!). However, we have some source code and we need to obtain a minimal custom recovery for mount system r/w and copy to it SuperSU. This is the only way at time for rooting this device!
Click to expand...
Click to collapse
Thank you, i think the flashing rom of the stock wiko will be in line with the android version of L
Thank you
chuppito said:
Thank you, i think the flashing rom of the stock wiko will be in line with the android version of L
Click to expand...
Click to collapse
:crying: For this, we need to wait until the end of the summer!
I hope Wiko will publish the current ROM in his site soon. With the current stock "recovery.img" we can try to port the custom recovery from other device to the Ridge, because the sources are incomplete and don't compile. We need the help of the OEM! :angel:
Hello,
I'm trying to run an X server on my tablet, but it does not launch. The X binaries and libraries are from a 32-bit CentOS ROM I downloaded (Mirror list: http://isoredirect.centos.org/altarch/7/isos/armhfp/); I have the contents of the ROM in /data/local with symlinks to parts of it (e.g. /lib). Componenets of GNU Coreutils like Bash, among others work just fine, so I do not believe any parts of the CentOS ROM are causing problems. Running startx through an ADB shell might not work, so I've been looking for a way to run it on the tablet's screen without success.
More info:
Model: Samsung Galaxy Tab A 10.1 2019 (SM-T510)
ROM: Nexus Stock Android 11
Version of X: 1.20.4
Root status: Rooted
CPU Architecture: armv8l
Code:
Error Message:
expr: Unexpected extra input '/dev/pts/0'
xauth: file //.serverauth.8071 does not exist
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: 4.19.52-300.el7.armv7hl+lpae
Current Operating System: Linux localhost 4.4.177 #2 SMP PREEMPT Fri Mar 12 17:13:34 PST 2021 armv8l
Kernel command line: console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 rcupdate.rcu_expedited=1 androidboot.debug_level=0x4f4c androidboot.force_upload=0x0 androidboot.upload_offset=6880000 softdog.soft_margin=100 softdog.soft_panic=1 androidboot.dram_info=FF,04,10,2G sec_debug.chipidfail_cnt=0 sec_debug.lpitimeout_cnt=0 sec_debug.cache_err_cnt=0 sec_debug.codediff_cnt=0 sec_debug.pcb_offset=7343872 sec_debug.smd_offset=7344896 sec_debug.lpddr4_size=2 sec_debug.sjl=1 androidboot.muic_1k=0 androidboot.sn.param.offset=7342000 androidboot.prototype.param.offset=7345920 androidboot.recovery_offset=7347968 androidboot.fmm_lock=48 sec_debug.fmm_lock_offset=7340680 ess_setup=0x91200000 [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] s3cfb.bootloaderfb=0xec000000 lcdtype=8550668 androidboot.carrierid.param.offset=7340608 androidboot.carrierid= consoleblank=0 vmalloc=384m sec_debug.reset_reason=5 sec_reset.reset_reason=5 ehci_hcd.park=3 oops=panic pmic_info=91 ccic_info=1 fg_reset=0 androidboot.emmc_checksum=3 androidboot.sales.param.offset=7340572 sales_code=XAC androidboot.odin_download=1 androidboot.bootloader=T510XXU4BUA1 androidboot.selinux=enforcing androidboot.ucs_mode=0 [email protected] androidboot.revision=4 androidboot.hardware=exynos7904 androidboot.warranty_bit=1 androidboot.wb.hs=0e03 androidboot.wb.snapQB=CUSTOM sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=R52MA16Z2JK androidboot.ap_serial=0x45B7CD5ABEDC snd_soc_core.pmdown_time=1000 androidboot.cp_reserved_mem=off skip_initramfs rootwait ro init=/init root=/dev/mmcblk0p25 androidboot.dtbo_idx=1 androidboot.em.did=45b7cd5abedc androidboot.em.model=SM-T510 androidboot.em.status=0x0 root=PARTUUID=52444E41-494F-2044-7379-7374656D0000 androidboot.verifiedbootstate=orange androidboot.svb.ver=SVB1.0 bcm_setup=0xffffff80f8e00000 reserve-fimc=0xffffff80fa000000 firmware_class.path=/vendor/firmware ecd_setup=disable factory_mode=0 androidboot.ulcnt=5 androidboot.lassen.apfuse=8 epx_activate=true kpti=n androidboot.cpefs_wp=1
Build Date: 01 April 2020 09:37:40AM
Build ID: xorg-x11-server 1.20.4-10.el7
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 4 04:48:11 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error