Related
hi all xrecovery released by zdzihu !!!!!!!! Thank you
for now you must go here http://forum.xda-developers.com/showthread.php?p=9913723#post9913723
thanks for all who have testet and postet here
now for me here is closed
I would like to have xrecovery on my X10mini, so i tried to make some edits in that, but no success.
I already posted my finding to xrecovery X10 thread, so i post it here again:
For x10 mini, i think, there should be event1 instead of event2 i "chargemon" file
Tried with "getevent" in adb
I see then some feedback on the "Sony Ericsson" boot screen while i keep pressing "back"
When i stop pressing, then goes logo, then reboot and booting normally
I think "mtdblocks" are different from X10 - this is for x10 mini:
dev: size erasesize name
mtd0: 0ce00000 00020000 "system"
mtd1: 03200000 00020000 "cache"
mtd2: 00040000 00020000 "appslog"
mtd3: 0d3c0000 00020000 "userdata"
P.S. sorry for bad English
x10 big one
Code:
dev: size erasesize name
mtd0: 00440000 00020000 "appslog"
mtd1: 06f40000 00020000 "cache"
mtd2: 160a0000 00020000 "system"
mtd3: 1d100000 00020000 "userdata"
x10 mini
Code:
dev: size erasesize name
mtd0: 0ce00000 00020000 "system"
mtd1: 03200000 00020000 "cache"
mtd2: 00040000 00020000 "appslog"
mtd3: 0d3c0000 00020000 "userdata"
x10 mini pro
Code:
dev: size erasesize name
mtd0: 0ce00000 00020000 "system"
mtd1: 0d3c0000 00020000 "userdata"
mtd2: 03200000 00020000 "cache"
mtd3: 00040000 00020000 "appslog"
I have also tried several times to make it work on my mini (E10i) just by changing blocks, but no luck.
I always get an error ine this line:
mount -o rw -t yaffs2 /dev/block/mtdblock2 /data/local/tmp/xrecovery
Invalid argument.
Hope this works..
peetr_ said:
I would like to have xrecovery on my X10mini, so i tried to make some edits in that, but no success.
I already posted my finding to xrecovery X10 thread, so i post it here again:
For x10 mini, i think, there should be event1 instead of event2 i "chargemon" file
Tried with "getevent" in adb
I see then some feedback on the "Sony Ericsson" boot screen while i keep pressing "back"
When i stop pressing, then goes logo, then reboot and booting normally
I think "mtdblocks" are different from X10 - this is for x10 mini:
dev: size erasesize name
mtd0: 0ce00000 00020000 "system"
mtd1: 03200000 00020000 "cache"
mtd2: 00040000 00020000 "appslog"
mtd3: 0d3c0000 00020000 "userdata"
P.S. sorry for bad English
Click to expand...
Click to collapse
ok thanks here the output from getevent in adb
- from x10i big
C:\android-sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# getevent
getevent
add device 1: /dev/input/event5
name: "qwerty"
add device 2: /dev/input/event4
name: "8k_handset"
add device 3: /dev/input/event3
name: "compass"
add device 4: /dev/input/event2
name: "es209ra_keypad"
add device 5: /dev/input/event0
name: "es209ra_keypad"
add device 6: /dev/input/event1
name: "es209ra_touch"
-fom x10 mini pro
C:\android-sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# getevent
getevent
add device 1: /dev/input/event4
name: "systemconnector"
add device 2: /dev/input/event3
name: "qwerty"
add device 3: /dev/input/event2
name: "cy8ctma300_ser"
add device 4: /dev/input/event1
name: "compass"
add device 5: /dev/input/event0
name: "mimmi_keypad"
Hmm, ok see the difference in the chargemon
cat /dev/input/event2 > /dev/keycheck& -think here to change the event2 to event0 for pressing keypad
i will try it and report later
Zocker Tko said:
ok thanks here the output from getevent in adb
- from x10i big
C:\android-sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# getevent
getevent
add device 1: /dev/input/event5
name: "qwerty"
add device 2: /dev/input/event4
name: "8k_handset"
add device 3: /dev/input/event3
name: "compass"
add device 4: /dev/input/event2
name: "es209ra_keypad"
add device 5: /dev/input/event0
name: "es209ra_keypad"
add device 6: /dev/input/event1
name: "es209ra_touch"
-fom x10 mini pro
C:\android-sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# getevent
getevent
add device 1: /dev/input/event4
name: "systemconnector"
add device 2: /dev/input/event3
name: "qwerty"
add device 3: /dev/input/event2
name: "cy8ctma300_ser"
add device 4: /dev/input/event1
name: "compass"
add device 5: /dev/input/event0
name: "mimmi_keypad"
Hmm, ok see the difference in the chargemon
cat /dev/input/event2 > /dev/keycheck& -think here to change the event2 to event0 for pressing keypad
i will try it and report later
Click to expand...
Click to collapse
Just in case you could also check mini:
Code:
C:\Users\The Fear Itself>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# getevent
getevent
add device 1: /dev/input/event4
name: "systemconnector"
add device 2: /dev/input/event3
name: "qwerty"
add device 3: /dev/input/event2
name: "compass"
add device 4: /dev/input/event1
name: "robyn_keypad"
add device 5: /dev/input/event0
name: "synaptics-rmi-touchscreen"
Thank you in advance
ok first !!!warning for the x10 mini users!!!, because i think you cant remove your akku, is it right? Maybe you can brick your phone!
My Tests are only for the X10 mini pro
ok why
i have changed in the chargemon for my x10 mini pro!!!
cat /dev/input/event0 > /dev/keycheck&
so i installed the xrecovery make a reboot and press the menu back button after SE logo screen. In the first mom i thougt i have bricked my phone, because it was still on the SE logo, so i removed my akku and started again my phone and it booted normally
but the good thing is, my phone will do something, think it will go into the xrecovery but it cant.
sry for bad english
Zocker Tko said:
ok first !!!warning for the x10 mini users!!!, because i think you cant remove your akku, is it right? Maybe you can brick your phone!
My Tests are only for the X10 mini pro
ok why
i have changed in the chargemon for my x10 mini pro!!!
cat /dev/input/event0 > /dev/keycheck&
so i installed the xrecovery make a reboot and press the menu back button after SE logo screen. In the first mom i thougt i have bricked my phone, because it was still on the SE logo, so i removed my akku and started again my phone and it booted normally
but the good thing is, my phone will do something, think it will go into the xrecovery but it cant.
sry for bad english
Click to expand...
Click to collapse
You dont need to remove the battery in mini, i've got "other" methods.
But anyway, if you find the proper sequence of events, please post it here so maybe we could do something for mini too!
So i tried almost everything with mtdblocks and still no success.
I figured out, there is no way to mount mtdblock2 into anything else then /system or /data or /cache and maybe something else, but not into the folder with xrecovery.tar only
My last try was copying busybox and chargemon to /system/bin,
made the directory /xrecovery, copied there xrecovery.tar, changed some permissions,
mounted mtdblock0 to /xrecovery (also changed in chargemon),now there was system folder together with xrecovery.tar then restarted.
On back pressing, something happend - i think xrecovery.tar decompressed, then was logo, restart, normal boot (longer), but phone partially bricked (i think busybox) - malfunctions - bad root, no app2sd, bad adb shell, cannot reinstall busybox - but maybe all of this because of bad permissons.
Then with ESfile explorer i saw the /xrecovery folder disappeared.
I don´t have no idea what else to try. And i am tired of this now
P.S. Sorry for bad English
peetr_ said:
So i tried almost everything with mtdblocks and still no success.
I figured out, there is no way to mount mtdblock2 into anything else then /system or /data or /cache and maybe something else, but not into the folder with xrecovery.tar only
My last try was copying busybox and chargemon to /system/bin,
made the directory /xrecovery, copied there xrecovery.tar, changed some permissions,
mounted mtdblock0 to /xrecovery (also changed in chargemon),now there was system folder together with xrecovery.tar then restarted.
On back pressing, something happend - i think xrecovery.tar decompressed, then was logo, restart, normal boot (longer), but phone partially bricked (i think busybox) - malfunctions - bad root, no app2sd, bad adb shell, cannot reinstall busybox - but maybe all of this because of bad permissons.
Then with ESfile explorer i saw the /xrecovery folder disappeared.
I don´t have no idea what else to try. And i am tired of this now
P.S. Sorry for bad English
Click to expand...
Click to collapse
hi, bad to hear
maybe you can root your phone again with the z4root app from market or search here for it, i believe z4root installs busybox too with right permissions
or you can try with rootexplorer, when it works to set the right permissions for busybox for group r-,w-,e- and others r-,e-
hope it will help you
have you tried using the "init" files from your phone i.e replace the ones in xrecovery.tar ??
the only other thing I'd suggest is copying the busybox scripts in sbin to the /system/bin folder. from what I can see the above script just places the busybox file into system/bin. It doesn't actually unpack it.
Contrarian said:
have you tried using the "init" files from your phone i.e replace the ones in xrecovery.tar ??
the only other thing I'd suggest is copying the busybox scripts in sbin to the /system/bin folder. from what I can see the above script just places the busybox file into system/bin. It doesn't actually unpack it.
Click to expand...
Click to collapse
thanks, hope i understand you right
i have look into the xrecovery.tar
i saw the default.prop and the init and init.rc, hmm think i can change the "inits" with the from my phone, i will try it.
hmm, and about busybox, yes busybox goes to sytem/bin folder and is working.
check with busyboxinstaller it is v.1.15.3, or what did you mean with actually unpack it?
edit: ok changed the "inits" but no luck
another thing, test for mounting with adb
on my x10i big (xrecovery work)
-#mount -o rw -t yaffs2 /dev/block/mtdblock0 /data/local/tmp/xrecovery --works
on my x10i pro
-#mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount: Invalid argument
Zocker Tko said:
thanks, hope i understand you right
i have look into the xrecovery.tar
i saw the default.prop and the init and init.rc, hmm think i can change the "inits" with the from my phone, i will try it.
hmm, and about busybox, yes busybox goes to sytem/bin folder and is working.
check with busyboxinstaller it is v.1.15.3, or what did you mean with actually unpack it?
edit: ok changed the "inits" but no luck
another thing, test for mounting with adb
on my x10i big (xrecovery work)
-#mount -o rw -t yaffs2 /dev/block/mtdblock0 /data/local/tmp/xrecovery --works
on my x10i pro
-#mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount: Invalid argument
Click to expand...
Click to collapse
if you mount system
/data gets mounted to...
weird
changed inits here events and mtdblocks
no succes
i hangs on boot when i press buttons
i did the root explorer methode g script methode and adb shell methode
ok at first thanks for helping and testing
ok what have we done
-changed the mtdblocks to the right paths in the chargemon and xrecovery.sh
-changed the event in the chargemon for pressing the menu back button
-changed the "inits" in the xrecovery.tar with our owns from phone
ok all these changes, i think are korrekt.
but i believe this is the point why we cant get it to work, because we cant mount the mtdblock for "appslog".
on my x10i pro
-#mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount: Invalid argument
on the mini the same with mtdblock2
on my x10i (big) i can mount it
so any ideas for mounting the mtdblock for "appslog" in an other way/command?
Zocker Tko said:
on my x10i pro
-#mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount -o rw -t yaffs2 /dev/block/mtdblock3 /data/local/tmp/xrecovery
mount: Invalid argument
on the mini the same with mtdblock2
on my x10i (big) i can mount it
so any ideas for mounting the mtdblock for "appslog" in an other way/command?
Click to expand...
Click to collapse
I believe in it. In my opinion is the key.
That's defintely where the error occurs. For some reason it won't recognize the mount point when booting.
Just an observation I've made - you can't write to /dev directory (partition). can you see if it's possible on the X10. Can you even chmod 777 this.
Sorry about the long post but us x10 mini/pro owners need to use more bandwidth on this site anyhow. This is from init.rc if anyone can see an attack point.
on pre-init
# /sbin/fotainit is part of fota. If the system is running a fota upgrade, then fota will
# reboot the system when finished.
exec /sbin/fotainit
on init
sysclktz 0
loglevel 3
# start master reset
exec /sbin/mr
# Check if flash was aborted.
exec /sbin/checkabortedflash
# setup the global environment
export PATH /sbin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d
# create mountpoints and mount tmpfs on sqlite_stmt_journals
mkdir /sdcard 0000 system system
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /config 0500 root root
mkdir /sqlite_stmt_journals 01777 root root
mount tmpfs tmpfs /sqlite_stmt_journals size=4m
mount rootfs rootfs / ro remount
write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0
# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown sytem system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0777 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024
mkdir /dev/cpuctl/fg_boost
chown system system /dev/cpuctl/fg_boost/tasks
chmod 0777 /dev/cpuctl/fg_boost/tasks
write /dev/cpuctl/fg_boost/cpu.shares 1024
mkdir /dev/cpuctl/bg_non_interactive
chown system system /dev/cpuctl/bg_non_interactive/tasks
chmod 0777 /dev/cpuctl/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/bg_non_interactive/cpu.shares 52
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
# We chown/chmod /data again so because mount is run as root + defaults
mount yaffs2 [email protected] /data nosuid nodev
chown system system /data
chmod 0771 /data
# Divert into charge-only mode if started by the charger.
# Chargemon will simply exit if the system was started normally.
exec /system/bin/chargemon
# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.
mkdir /data/dontpanic
chown root log /data/dontpanic
chmod 0750 /data/dontpanic
# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console
copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads
write /proc/apanic_console 1
# Same reason as /data above
mount yaffs2 [email protected] /cache nosuid nodev
chown system cache /cache
chmod 0770 /cache
# This may have been created by the recovery system with odd permissions
chown system system /cache/recovery
chmod 0770 /cache/recovery
#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo
# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/vpn 0770 system system
mkdir /data/misc/vpn/profiles 0770 system system
# give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
chmod 0770 /data/misc/wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
mkdir /data/local 0771 shell shell
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770
mkdir /cache/lost+found 0770
# double check the perms, in case lost+found already exists, and set owner
chown root root /data/lost+found
chmod 0770 /data/lost+found
chown root root /cache/lost+found
chmod 0770 /cache/lost+found
# SEMC: Discretix DRM change start
mkdir /data/DxDrm 0777
mkdir /data/DxDrm/fuse
# SEMC: Discretix DRM change end
on boot
exec /system/bin/verify_odex
# basic network init
ifup lo
hostname localhost
domainname localdomain
# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40
# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.SECONDARY_SERVER_ADJ 2
setprop ro.BACKUP_APP_ADJ 2
setprop ro.HOME_APP_ADJ 4
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.CONTENT_PROVIDER_ADJ 14
setprop ro.EMPTY_APP_ADJ 15
# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 1536
setprop ro.VISIBLE_APP_MEM 2048
setprop ro.SECONDARY_SERVER_MEM 4096
setprop ro.BACKUP_APP_MEM 4096
setprop ro.HOME_APP_MEM 4096
setprop ro.HIDDEN_APP_MEM 5120
setprop ro.CONTENT_PROVIDER_MEM 5632
setprop ro.EMPTY_APP_MEM 15360
# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have HOME_APP at the
# same memory level as services.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,15360
# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16
# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5
# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown radio system /sys/power/state
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
chown root radio /proc/cmdline
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.wifi 4095,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
class_start default
## Daemon processes to be run by init.
##
service console /system/bin/sh
console
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
on propertyersist.service.adb.enable=1
start adbd
on propertyersist.service.adb.enable=0
stop adbd
service servicemanager /system/bin/servicemanager
user system
critical
onrestart restart zygote
onrestart restart media
service vold /system/bin/vold
socket vold stream 0660 root mount
service nexus /system/bin/nexus
socket nexus stream 0660 root system
disabled
#service mountd /system/bin/mountd
# socket mountd stream 0660 root mount
service debuggerd /system/bin/debuggerd
service ril-daemon /system/bin/rild
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio system
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
service media /system/bin/mediaserver
user root
group system audio camera graphics inet net_bt net_bt_admin
service bootsound /system/bin/playmp3
user media
group audio
oneshot
service bootanim /system/bin/bootanimation
user graphics
group graphics
disabled
oneshot
service dbus /system/bin/dbus-daemon --system --nofork
socket dbus stream 660 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin
service bluetoothd /system/bin/bluetoothd -n
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service hfag /system/bin/sdptool add --channel=10 HFAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service hsag /system/bin/sdptool add --channel=11 HSAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service opush /system/bin/sdptool add --channel=12 OPUSH
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service pbap /system/bin/sdptool add --channel=19 PBAP
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service installd /system/bin/installd
socket installd stream 600 system system
service flash_recovery /system/etc/install-recovery.sh
oneshot
# SEMC: Discretix DRM change start
service dx_drm_server /system/bin/DxDrmServerIpc -f -o allow_other /data/DxDrm/fuse
service drmbackup /system/bin/drmdbbackup
user system
oneshot
# SEMC: Discretix DRM change end
service racoon /system/bin/racoon
socket racoon stream 600 system system
# racoon will setuid to vpn after getting necessary resources.
group net_admin
disabled
oneshot
service mtpd /system/bin/mtpd
socket mtpd stream 600 system system
user vpn
group vpn net_admin net_raw
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
user keystore
group keystore
socket keystore stream 666
service dumpstate /system/bin/dumpstate -s
socket dumpstate stream 0660 shell log
disabled
oneshot
# Set the startup flag to boot complete, run on property change
service setssflagbc /system/bin/startupflag bootcomplete
user root
oneshot
disabled
on property:dev.bootcomplete=1
start setssflagbc
Contrarian said:
That's defintely where the error occurs. For some reason it won't recognize the mount point when booting.
Just an observation I've made - you can't write to /dev directory (partition). can you see if it's possible on the X10. Can you even chmod 777 this.
Click to expand...
Click to collapse
hi, thanks how can i do that?
and to change the init.rc in Xrecovery.tar with our own from phone, think that will not work, because thy are different. You see the post of init.rc from Contrarian
and this is the init.rc from xrecovery.tar
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
on boot
ifup lo
hostname localhost
domainname localdomain
class_start default
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
what about the init from our phone and in xrecovery.tar, its too much for me when i opend in notepad++, to see any differences. I will post later the init.rc from my x10i (Big),so we can see evtl. differences.
ok here are my init.rc from my x10i (big) at first view i saw no differences.
on pre-init
# /sbin/fotainit is part of fota. If the system is running a fota upgrade, then fota will
# reboot the system when finished.
exec /sbin/fotainit
on init
sysclktz 0
loglevel 3
# start master reset
exec /sbin/mr
# Check if flash was aborted.
exec /sbin/checkabortedflash
# setup the global environment
export PATH /sbin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d
# create mountpoints and mount tmpfs on sqlite_stmt_journals
mkdir /sdcard 0000 system system
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /config 0500 root root
mkdir /sqlite_stmt_journals 01777 root root
mount tmpfs tmpfs /sqlite_stmt_journals size=4m
mount rootfs rootfs / ro remount
write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0
# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown system system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0777 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024
mkdir /dev/cpuctl/fg_boost
chown system system /dev/cpuctl/fg_boost/tasks
chmod 0777 /dev/cpuctl/fg_boost/tasks
write /dev/cpuctl/fg_boost/cpu.shares 1024
mkdir /dev/cpuctl/bg_non_interactive
chown system system /dev/cpuctl/bg_non_interactive/tasks
chmod 0777 /dev/cpuctl/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/bg_non_interactive/cpu.shares 52
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
# We chown/chmod /data again so because mount is run as root + defaults
mount yaffs2 [email protected] /data nosuid nodev
chown system system /data
chmod 0771 /data
# Divert into charge-only mode if started by the charger.
# Chargemon will simply exit if the system was started normally.
exec /system/bin/chargemon
# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.
mkdir /data/dontpanic
chown root log /data/dontpanic
chmod 0750 /data/dontpanic
# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console
copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads
write /proc/apanic_console 1
# Collect ramconsole data
copy /proc/last_kmsg /data/dontpanic/last_kmsg
chown root log /data/dontpanic/last_kmsg
chmod 0640 /data/dontpanic/last_kmsg
# Same reason as /data above
mount yaffs2 [email protected] /cache nosuid nodev
chown system cache /cache
chmod 0770 /cache
# This may have been created by the recovery system with odd permissions
chown system system /cache/recovery
chmod 0770 /cache/recovery
#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo
# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/vpn 0770 system system
mkdir /data/misc/vpn/profiles 0770 system system
mkdir /data/misc/dhcp 0770 dhcp dhcp
mkdir /data/misc/wifi 0770 wifi wifi
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/system 0775 system system
mkdir /data/system/wpa_supplicant 0770 wifi wifi
# give system access to wpa_supplicant.conf for backup and restore
chmod 0770 /data/misc/wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
chown wifi wifi /data/misc/wifi/wpa_supplicant.conf
mkdir /data/local 0771 shell shell
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/radio 0770 radio radio
# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770
mkdir /cache/lost+found 0770
# double check the perms, in case lost+found already exists, and set owner
chown root root /data/lost+found
chmod 0770 /data/lost+found
chown root root /cache/lost+found
chmod 0770 /cache/lost+found
# In Device Diagnostics (IDD)
mkdir /data/idd 0755 idd idd
mkdir /data/semc-checkin 0773 system system
mkdir /data/semc-checkin/int 0773 system system
mkdir /data/tombstones 0755 system system
mkdir /data/crashsms 0777 system system
mkdir /data/crashsms/crashes 0777 system system
# SEMC: Discretix DRM change start
mkdir /data/DxDrm 0777
mkdir /data/DxDrm/fuse
# SEMC: Discretix DRM change end
# Semc Discretix change start
service drmbackup /system/bin/drmdbbackup
user system
oneshot
# Semc Discretix change end
on boot
exec /system/bin/verify_odex
# basic network init
ifup lo
hostname localhost
domainname localdomain
# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40
# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.SECONDARY_SERVER_ADJ 2
setprop ro.BACKUP_APP_ADJ 2
setprop ro.HOME_APP_ADJ 4
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.CONTENT_PROVIDER_ADJ 14
setprop ro.EMPTY_APP_ADJ 15
# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 1536
setprop ro.VISIBLE_APP_MEM 2048
setprop ro.SECONDARY_SERVER_MEM 4096
setprop ro.BACKUP_APP_MEM 4096
setprop ro.HOME_APP_MEM 4096
setprop ro.HIDDEN_APP_MEM 5120
setprop ro.CONTENT_PROVIDER_MEM 5120
setprop ro.EMPTY_APP_MEM 23040
# Define the resolution for OHD Camera Application
setprop ro.media.enc.hprof.vid.width 320
setprop ro.media.enc.hprof.vid.height 240
setprop ro.media.enc.lprof.vid.width 320
setprop ro.media.enc.lprof.vid.height 240
# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have HOME_APP at the
# same memory level as services.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5120,23040
# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16
# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5
# Adjust socket buffer to enlarge TCP receive window for high bandwidth
write /proc/sys/net/ipv4/tcp_adv_win_scale 1
# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown radio system /sys/power/state
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
# USB Function framework
# chown system system /sys/devices/platform/msm_hsusb_periphera/composition
# USB Gadget framework
chown system system /sys/devices/platform/android_usb/composition
chown root radio /proc/cmdline
chmod 0666 /dev/msm_snd
# SEMC:LC: Have LC added following items?
mkdir /dev/socket/sensors 0777 system system
chmod 0666 /sys/devices/platform/msm_sdcc.2/polling
# SEMC:LC: end
#write access to sysrq-trigger
chown root system /proc/sysrq-trigger
chmod 0220 /proc/sysrq-trigger
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.wifi 4095,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
class_start default
## Daemon processes to be run by init.
##
service console /system/bin/sh
console
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
on propertyersist.service.adb.enable=1
start adbd
on propertyersist.service.adb.enable=0
stop adbd
# Enabled port-bridge for 'eng' builds
service esheep-sh /system/bin/sh /init.esheep.sh
user root
oneshot
service servicemanager /system/bin/servicemanager
user system
critical
onrestart restart zygote
onrestart restart media
service vold /system/bin/vold
socket vold stream 0660 root mount
service nexus /system/bin/nexus
socket nexus stream 0660 root system
disabled
#service mountd /system/bin/mountd
# socket mountd stream 0660 root mount
service debuggerd /system/bin/debuggerd
service ril-daemon /system/bin/rild
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio system
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
service media /system/bin/mediaserver
user root
group system audio camera graphics inet net_bt net_bt_admin
service bootsound /system/bin/playmp3
user media
group audio
oneshot
service bootanim /system/bin/bootanimation
user graphics
group graphics
disabled
oneshot
service dbus /system/bin/dbus-daemon --system --nofork
socket dbus stream 660 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin
service bluetoothd /system/bin/bluetoothd -n
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service hfag /system/bin/sdptool add --channel=10 HFAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service hsag /system/bin/sdptool add --channel=11 HSAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service opush /system/bin/sdptool add --channel=12 OPUSH
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service pbap /system/bin/sdptool add --channel=19 PBAP
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service installd /system/bin/installd
socket installd stream 600 system system
service flash_recovery /system/etc/install-recovery.sh
oneshot
# SEMC: Discretix DRM change start
service dx_drm_server /system/bin/DxDrmServerIpc -f -o allow_other /data/DxDrm/fuse
# SEMC: Discretix DRM change end
service racoon /system/bin/racoon
socket racoon stream 600 system system
# racoon will setuid to vpn after getting necessary resources.
group net_admin
disabled
oneshot
service mtpd /system/bin/mtpd
socket mtpd stream 600 system system
user vpn
group vpn net_admin net_raw
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
user keystore
group keystore
socket keystore stream 666
service dumpstate /system/bin/dumpstate -s
socket dumpstate stream 0660 shell log
disabled
oneshot
# Set the startup flag to boot complete, run on property change
service setssflagbc /system/bin/startupflag bootcomplete
user root
oneshot
disabled
service iddd /system/bin/iddd
user idd
group idd log
on property:dev.bootcomplete=1
start setssflagbc
# SEMC: DRM key activation
service suntrolkac /system/bin/suntrolkac
user root
oneshot
# SEMC: DRM key activation
Hello everyone, i was looking on the net for things about wifi etc. And found this wall of text about wifi. I just copied the text. Maybe its helpfull for the devs i saw some things which my int.rc dont have etc. Here it is.
0. Understand how Android WiFi works. 1. Enable building of wpa_supplicant in your BoardConfig.mk 2. (Optional) Enable debug for wpa_supplicant. 3. Provide a proper wpa_supplicant.conf for your device 4. Have the correct paths and permissions created from init.rc 5. Make sure your wpa_supplicant and dhcpcd (optional) are starting from init.rc 6. Provide your driver either as a module or built in kernel and proper kernel support for it and modify Android source code accordingly. 7. Provide a firmware if your module needs it. 8. Make your driver work with Android custom wpa_supplicant commands and SIOCSIWPRIV ioctl
Now onto details.
0. Understand how Android WiFi works. Android uses a modified wpa_supplicant ( external/wpa_supplicant ) daemon for wifi support which is controlled through a socket by hardware/libhardware_legacy/wifi/wifi.c (WiFiHW) that gets controlled from Android UI through android.net.wifi package from frameworks/base/wifi/java/android/net/wifi/ and it's corresponding jni implementation in frameworks/base/core/jni/android_net_wifi_Wifi.cpp Higher level network management is done in frameworks/base/core/java/android/net
1. Enable building of wpa_supplicant in your BoardConfig.mk This is by simply adding: BOARD_WPA_SUPPLICANT_DRIVER := WEXT to your BoardConfig.mk . This will set WPA_BUILD_SUPPLICANT to true in external/wpa_supplicant/Android.mk enabling building of driver_wext.c If you have a custom wpa_supplicant driver (like madwifi or my custom android private commands emulation - see last paragraph) you can replace WEXT with AWEXT or your driver name (MADWIFI, PRISM etc).
2. (Optional) Enable debug for wpa_supplicant. By default wpa_supplicant is set to MSG_INFO that doesn't tell much. To enable more messages: 2.1 modify common.c and set wpa_debug_level = MSG_DEBUG 2.2 modify common.h and change #define wpa_printf from if ((level) >= MSG_INFO) to if ((level) >= MSG_DEBUG)
3. Provide a proper wpa_supplicant.conf for your device Providing a wpa_supplicant.conf it's important because the control socket for android is specified in this file (ctrl_interface= ). This file should be copied by your AndroidBoard.mk to $(TARGET_OUT_ETC)/wifi (usually /system/etc/wifi/wpa_supplicant.conf ). This location will be used on wpa_supplicant service from init.rc. There are two different ways in which wpa_supplicant can be configured, one is to use a "private" socket in android namespace, created by socket_local_client_connect() function in wpa_ctrl.c and another is by using a standard unix socket.
Minimum required config options in wpa_supplicant.conf : - Android private socket
ctrl_interface=wlan0 update_config=1
- Unix standard socket
ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi update_config=1
Depending on your driver you might also want to add: ap_scan=1
If you have AP association problems with should change to ap_scan=0 to let the driver do the association instead of wpa_supplicant. If you want to let wpa_supplicant connect to non-WPA or open wireless networks (by default it skips these kind) add:
network={ key_mgmt=NONE }
4. Have the correct permissions and paths created from init.rc Incorrect permisions will result in wpa_supplicant not being able to create/open the control socket and libhardware_legacy/wifi/wifi.c won't connect. Since Google modified wpa_supplicant to run as wifi user/group the directory structure and file ownership should belong to wifi user/group (see os_program_init() function in wpa_supplicant/os_unix.c ).
Otherwise errors like: E/WifiHW ( ): Unable to open connection to supplicant on "/data/system/wpa_supplicant/wlan0": No such file or directory will appear.
Also wpa_supplicant.conf should belong to wifi user/group because wpa_supplicant will want to modify this file. If your system has /system as read-only use a location like /data/misc/wifi/wpa_supplicant.conf and modify wpa_supplicant service in init.rc with new location. Make sure the paths are correctly created in init.rc:
mkdir /system/etc/wifi 0770 wifi wifi chmod 0770 /system/etc/wifi chmod 0660 /system/etc/wifi/wpa_supplicant.conf chown wifi wifi /system/etc/wifi/wpa_supplicant.conf #wpa_supplicant control socket for android wifi.c (android private socket) mkdir /data/misc/wifi 0770 wifi wifi mkdir /data/misc/wifi/sockets 0770 wifi wifi chmod 0770 /data/misc/wifi chmod 0660 /data/misc/wifi/wpa_supplicant.conf chown wifi wifi /data/misc/wifi chown wifi wifi /data/misc/wifi/wpa_supplicant.conf
If you use a Unix standard socket in wpa_supplicant.conf (see above) add:
# wpa_supplicant socket (unix socket mode) mkdir /data/system/wpa_supplicant 0771 wifi wifi chmod 0771 /data/system/wpa_supplicant chown wifi wifi /data/system/wpa_supplicant
Do not add these if you use Android private socket because it will make wpa_supplicant non-functional, because hardware/libhardware_legacy/wifi/wifi.c check for existence of the /data/system/wpa_supplicant folder and will pass a wrong interface name to wpa_ctrl_open() function.
5. Make sure your wpa_supplicant and dhcpcd are starting from init.rc
For wpa_supplicant the init.rc startup like should be depending on which path you chosen: - Android private socket:
service wpa_supplicant /system/bin/wpa_supplicant -dd -Dwext -iwlan0 -c /system/etc/wifi/wpa_supplicant.conf socket wpa_wlan0 dgram 660 wifi wifi group system wifi inet disabled oneshot
- Unix standard socket:
service wpa_supplicant /system/bin/wpa_supplicant -dd -Dwext -iwlan0 -c /system/etc/wifi/wpa_supplicant.conf group system wifi inet disabled oneshot
If your wifi driver creates a wifi interface with other name than wlan0 you will have to modify the above line accordingly. You also should have dhcpcd starting from init.rc
service dhcpcd /system/bin/dhcpcd wlan0 group system dhcp disabled oneshot
Newer AOSP versions after Gingerbread use dhcpcd_wlan0 as service name.
6. Provide your driver either as a module or built in kernel and proper kernel support for it. First make sure that CONFIG_PACKET and CONFIG_NET_RADIO (wireless extensions) are enabled in your kernel. The driver can be built as module (default android way) or built in kernel (if you want to rely in kernel auto probing to support multiple driver eg. USB wifi) but will require source code modifications (see below). - As kernel module: Define in your BoardConfig.mk : 1. WIFI_DRIVER_MODULE_PATH := path to the module to be loaded You need to specify module name in that path too, usually should look something like /system/lib/modules/wlan.ko 2. WIFI_DRIVER_MODULE_NAME:= the name of the network interface that the driver creates, for example wlan0 3. WIFI_DRIVER_MODULE_ARG:= any arguments that you want to pass to the driver on insmod, for example nohwcrypt
Make sure you copy your kernel module when building android to the correct location. - As built in kernel: - First init.rc needs to be modified to inform hardware/libhardware_legacy/wifi/wifi.c about the name of the interface, that the driver is already loaded and set the status of wpa_supplicant to running:
setprop wifi.interface "wlan0" setprop wlan.driver.status "ok"
Do NOT add setprop init.svc.wpa_supplicant "running" as I previously mentioned as it will prevent wpa_supplicant from starting from init. - Secondly hardware/libhardware_legacy/wifi/wifi.c need to be modified so the functions insmod() and rmmod() return 0 (simply add return 0; as the first line in functions since they are not needed when driver is built in kernel) and return before checking for /proc/modules in check_driver_loaded() function. You might encounter problems with WifiHW module not being able to connect to wpa_supplicant socket even with the correct permisions. Try to turn off / turn on Wifi from the GUI.
7. Provide a firmware if your driver needs it
If your driver needs a firmware you will have to copy this firmware file to /etc/firmware on your android build. Android doesn't use a standard hotplug binary (although there is an implementation available on android-x86 system/code/toolbox/hotplug.c ) instead the init process takes care of firmware events and loads the firmware file from /etc/firmware (see: system/core/init/devices.c handle_firmware_event() function). Firmware file name is defined by the driver and might also contain a folder like: RTL8192SU/rtl8192sfw.bin, entire file path should be available in /etc/firmware
8. Make your driver work with Android custom wpa_supplicant commands and SIOCSIWPRIV ioctl.
Android uses SIOCSIWPRIV ioctl to send commands to modify driver behaviour and receive information like signal strength, mac address of the AP, link speed etc. This ioctl is usually not implemented in any known wireless drivers except bcm4329 which is in google msm kernel branch . The errors from not having this ioctl implemented will look like: E/wpa_supplicant( ): wpa_driver_priv_driver_cmd failed wpa_driver_priv_driver_cmd RSSI len = 4096 E/wpa_supplicant( ): wpa_driver_priv_driver_cmd failed D/wpa_supplicant( ): wpa_driver_priv_driver_cmd LINKSPEED len = 4096 E/wpa_supplicant( ): wpa_driver_priv_driver_cmd failed I/wpa_supplicant( ): CTRL-EVENT-DRIVER-STATE HANGED
After 4, WEXT_NUMBER_SEQUENTIAL_ERRORS errors, android will abort using the device.
To quickly test your wifi from interface you can disable error checking in external/wpa_supplicant/driver_wext.c by simply making ret = 0; in wpa_driver_priv_driver_cmd() function after the SIOCSIWPRIV ioctl call. This will make all access points in android UI appear without signal or MAC address. To proper implement the ioctl you will need to modify your kernel driver to reply to SIOCSIWPRIV ioctl with RSSI (signal strength) and MACADDR commands being the most important. A better way is to add a custom driver_xxx.c to google external/wpa_supplicant/ implementing wpa_driver_priv_driver_cmd() function that will take care of RSSI, MACADDR and others, through calls to SIOCGIWSTATS, SIOCGIFHWADDR ioctls, with the rest of the functions being called from driver_wext.c.
I hope that this post is usefull to anyone. Greets Danny
Sent from my Xperia X10 using xda app-developers app
Well open this thread for the reason is I need help to make proper ramdisk to use on CM10 in Locked bootloaders.
* I compiled CM10 from CM sources and extract ramdisk but need some help to make full and functionality ramdisk
FOR NOW ONLY HAVE BLACK SCREEN AFTER BOOTLOGO OF KERNEL
Download or add into my github
init.rc
Code:
#changed some redirections
import /system/etc/init.${ro.hardware}.rc
import /system/etc/init.usb.rc
import /system/etc/init.trace.rc
on early-init
# Set init and its forked children's oom_adj.
write /proc/1/oom_adj -16
start ueventd
# create mountpoints
mkdir /mnt 0775 root system
on init
sysclktz 0
loglevel 3
# setup the global environment
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib:/lib:/usr/lib:/system/lib/ste_omxcomponents
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d
# Right now vendor lives on the same filesystem as system,
# but someday that may change.
symlink /system/vendor /vendor
# Create cgroup mount point for cpu accounting
mkdir /acct
mount cgroup none /acct cpuacct
mkdir /acct/uid
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0771 system cache
mkdir /config 0500 root root
# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root
# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root
# Directory-target for where the secure container
# imagefile directory will be bind-mounted
mkdir /mnt/secure/asec 0700 root root
# Secure container public mount points.
mkdir /mnt/asec 0700 root system
mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000
# Filesystem image public mount points.
mkdir /mnt/obb 0700 root system
mount tmpfs tmpfs /mnt/obb mode=0755,gid=1000
write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0
write /proc/sys/kernel/randomize_va_space 2
write /proc/sys/kernel/kptr_restrict 2
write /proc/sys/kernel/dmesg_restrict 1
write /proc/sys/vm/mmap_min_addr 32768
write /proc/sys/kernel/sched_rt_runtime_us 950000
write /proc/sys/kernel/sched_rt_period_us 1000000
# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown system system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0660 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024
write /dev/cpuctl/cpu.rt_runtime_us 950000
write /dev/cpuctl/cpu.rt_period_us 1000000
mkdir /dev/cpuctl/apps
chown system system /dev/cpuctl/apps/tasks
chmod 0666 /dev/cpuctl/apps/tasks
write /dev/cpuctl/apps/cpu.shares 1024
write /dev/cpuctl/apps/cpu.rt_runtime_us 800000
write /dev/cpuctl/apps/cpu.rt_period_us 1000000
mkdir /dev/cpuctl/apps/bg_non_interactive
chown system system /dev/cpuctl/apps/bg_non_interactive/tasks
chmod 0666 /dev/cpuctl/apps/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/apps/bg_non_interactive/cpu.shares 52
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_runtime_us 700000
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_period_us 1000000
# Allow everybody to read the xt_qtaguid resource tracking misc dev.
# This is needed by any process that uses socket tagging.
chmod 0644 /dev/xt_qtaguid
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
mount yaffs2 [email protected] /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
on post-fs
# once everything is setup, no need to modify /
mount rootfs rootfs / ro remount
# We chown/chmod /cache again so because mount is run as root + defaults
chown system cache /cache
chmod 0771 /cache
# This may have been created by the recovery system with odd permissions
chown system cache /cache/recovery
chmod 0770 /cache/recovery
#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo
#change permissions on kmsg & sysrq-trigger so bugreports can grab kthread stacks
chown root system /proc/kmsg
chmod 0440 /proc/kmsg
chown root system /proc/sysrq-trigger
chmod 0220 /proc/sysrq-trigger
# create the lost+found directories, so as to enforce our permissions
mkdir /cache/lost+found 0770 root root
on post-fs-data
# We chown/chmod /data again so because mount is run as root + defaults
chown system system /data
chmod 0771 /data
# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.
mkdir /data/dontpanic 0750 root log
# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console
copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads
write /proc/apanic_console 1
# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/keychain 0771 system system
mkdir /data/misc/vpn 0770 system vpn
mkdir /data/misc/systemkeys 0700 system system
# give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
mkdir /data/local 0751 root root
# For security reasons, /data/local/tmp should always be empty.
# Do not place files or directories in /data/local/tmp
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app-asec 0700 root root
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/ssh 0750 root shell
mkdir /data/ssh/empty 0700 root root
mkdir /data/radio 0770 radio radio
# create dalvik-cache and double-check the perms, so as to enforce our permissions
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create resource-cache and double-check the perms
mkdir /data/resource-cache 0771 system system
chown system system /data/resource-cache
chmod 0771 /data/resource-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770 root root
# create directory for DRM plug-ins - give drm the read/write access to
# the following directory.
mkdir /data/drm 0770 drm drm
# If there is no fs-post-data action in the init.<device>.rc file, you
# must uncomment this line, otherwise encrypted filesystems
# won't work.
# Set indication (checked by vold) that we have finished this action
#setprop vold.post_fs_data_done 1
# Include extra init file and Change redirection into system made by klozz
import /system/etc/init.cm.rc
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40
# Memory management. Basic kernel parameters, and allow the high
# level system server to be able to adjust the kernel OOM driver
# parameters to match how it is managing things.
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
chown root system /sys/module/lowmemorykiller/parameters/adj
chmod 0664 /sys/module/lowmemorykiller/parameters/adj
chown root system /sys/module/lowmemorykiller/parameters/minfree
chmod 0664 /sys/module/lowmemorykiller/parameters/minfree
# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5
# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown system system /sys/power/state
chown system system /sys/power/wakeup_count
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
chown system system /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chown system system /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chown system system /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chown system system /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chown system system /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chown system system /sys/devices/system/cpu/cpufreq/interactive/boost
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/boost
chown system system /sys/devices/system/cpu/cpufreq/interactive/boostpulse
chown system system /sys/devices/system/cpu/cpufreq/interactive/input_boost
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/input_boost
# Assume SMP uses shared cpufreq policy for all CPUs
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 0664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 0664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 0664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
chown root radio /proc/cmdline
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,704512,4096,16384,110208
setprop net.tcp.buffersize.wifi 524288,1048576,2097152,262144,524288,1048576
setprop net.tcp.buffersize.lte 4096,87380,1220608,4096,16384,563200
setprop net.tcp.buffersize.umts 4096,87380,563200,4096,16384,110208
setprop net.tcp.buffersize.hspa 4096,87380,704512,4096,16384,110208
setprop net.tcp.buffersize.hsupa 4096,87380,704512,4096,16384,262144
setprop net.tcp.buffersize.hsdpa 4096,87380,704512,4096,16384,262144
setprop net.tcp.buffersize.hspap 4096,87380,1220608,4096,16384,393216
setprop net.tcp.buffersize.edge 4096,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4096,8760,11680,4096,8760,11680
setprop net.tcp.buffersize.evdo 4096,87380,563200,4096,16384,262144
setprop net.tcp.buffersize.evdo_b 4096,87380,704512,4096,16384,262144
# Set this property so surfaceflinger is not started by system_init
setprop system_init.startsurfaceflinger 0
# Run sysinit
exec /system/bin/sysinit
class_start core
class_start main
on nonencrypted
class_start late_start
on charger
class_start charger
on property:vold.decrypt=trigger_reset_main
class_reset main
on property:vold.decrypt=trigger_load_persist_props
load_persist_props
on property:vold.decrypt=trigger_post_fs_data
trigger post-fs-data
on property:vold.decrypt=trigger_restart_min_framework
class_start main
on property:vold.decrypt=trigger_restart_framework
class_start main
class_start late_start
on property:vold.decrypt=trigger_shutdown_framework
class_reset late_start
class_reset main
## Daemon processes to be run by init.
##
service ueventd /sbin/ueventd
class core
critical
service console /system/bin/sh
class core
console
disabled
user shell
group log
on property:ro.debuggable=1
start console
# adbd is controlled via property triggers in init.<platform>.usb.rc
service adbd /sbin/adbd
class core
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
# This property trigger has added to imitiate the previous behavior of "adb root".
# The adb gadget driver used to reset the USB bus when the adbd daemon exited,
# and the host side adb relied on this behavior to force it to reconnect with the
# new adbd instance after init relaunches it. So now we force the USB bus to reset
# here when adbd sets the service.adb.root property to 1. We also restart adbd here
# rather than waiting for init to notice its death and restarting it so the timing
# of USB resetting and adb restarting more closely matches the previous behavior.
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
service servicemanager /system/bin/servicemanager
class core
user system
group system
critical
onrestart restart zygote
onrestart restart media
onrestart restart surfaceflinger
onrestart restart drm
service vold /system/bin/vold
class core
socket vold stream 0660 root mount
ioprio be 2
service netd /system/bin/netd
class main
socket netd stream 0660 root system dbus_access
socket dnsproxyd stream 0660 root inet
socket mdns stream 0660 root system
service debuggerd /system/bin/debuggerd
class main
service ril-daemon /system/bin/rild
class main
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio sdcard_r sdcard_rw log dbus_access
service surfaceflinger /system/bin/surfaceflinger
class main
user system
group graphics
onrestart restart zygote
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
class main
socket zygote stream 660 root system
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
onrestart restart netd
service drm /system/bin/drmserver
class main
user drm
group drm system inet drmrpc sdcard_r
service bootanim /system/bin/bootanimation
class main
user graphics
group graphics
disabled
oneshot
service dbus /system/bin/dbus-daemon --system --nofork
class main
socket dbus stream 660 bluetooth bluetooth
socket dbus_ste stream 666 bluetooth dbus_access
user bluetooth
group bluetooth net_bt_admin dbus_access
service bluetoothd /system/bin/bluetoothd -n
class main
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service installd /system/bin/installd
class main
socket installd stream 600 system system
service flash_recovery /system/etc/install-recovery.sh
class main
oneshot
service racoon /system/bin/racoon
class main
socket racoon stream 600 system system
# IKE uses UDP port 500. Racoon will setuid to vpn after binding the port.
group vpn net_admin inet
disabled
oneshot
service mtpd /system/bin/mtpd
class main
socket mtpd stream 600 system system
user vpn
group vpn net_admin inet net_raw
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
class main
user keystore
group keystore drmrpc
socket keystore stream 666
service dumpstate /system/bin/dumpstate -s
class main
socket dumpstate stream 0660 shell log
disabled
oneshot
service sshd /system/bin/start-ssh
class main
disabled
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
init.cm.rc
Code:
# CyanogenMod Extras
on init
export ANDROID_CACHE /cache
export TERMINFO /system/etc/terminfo
export TERM linux
on post-fs-data
mkdir /cache/dalvik-cache 0771 system system
chown system system /cache/dalvik-cache
chmod 0771 /cache/dalvik-cache
# Import custom storage configuration
chmod 0644 /data/system/storage.rc
export_rc /data/system/storage.rc
on boot
chown system system /sys/block/mmcblk0/queue/scheduler
chmod 0664 /sys/block/mmcblk0/queue/scheduler
# allow system to modify ksm control files
chown root system /sys/kernel/mm/ksm/pages_to_scan
chmod 0664 /sys/kernel/mm/ksm/pages_to_scan
chown root system /sys/kernel/mm/ksm/sleep_millisecs
chmod 0664 /sys/kernel/mm/ksm/sleep_millisecs
chown root system /sys/kernel/mm/ksm/run
chmod 0664 /sys/kernel/mm/ksm/run
write /sys/kernel/mm/ksm/sleep_millisecs 1500
write /sys/kernel/mm/ksm/pages_to_scan 256
# adb over network
on property:service.adb.tcp.port=5555
stop adbd
start adbd
on property:service.adb.tcp.port=-1
stop adbd
start adbd
# Compcache - handle at boot
service compcache /system/bin/handle_compcache
class main
user root
group root
oneshot
Source code on:
https://github.com/Klozz/XGO_CM10
https://github.com/Klozz/XGO_CM10/tree/master/ramdisk_combined
https://github.com/Klozz/XGO_CM10/tree/master/recovery_combined
All Help are allowed
Without new kernel you can't boot jellybean but you have official JB so it's possible good luck!
try comparing atris cm9 patch with ICS official kernel ramdisk
DevSwift1 said:
Without new kernel you can't boot jellybean but you have official JB so it's possible good luck!
Click to expand...
Click to collapse
yep but only have black screen maybe bad compilation =S
work on kernels ICS .54 and JB .0.400 and 1.100 but after sony logo have a black screen
Well need more help u.u
percy_g2 said:
try comparing atris cm9 patch with ICS official kernel ramdisk
Click to expand...
Click to collapse
Atris patch?
can you provideme this patch?
TeamMex said:
Atris patch?
can you provideme this patch?
Click to expand...
Click to collapse
Search in general section .
Sent from my Xperia P using Tapatalk 4 Beta
percy_g2 said:
Search in general section .
Sent from my Xperia P using Tapatalk 4 Beta
Click to expand...
Click to collapse
hahah maybe u say patch of atis112?
Hi,
I am trying to fix a faulty device, which bootloop very frequently, due to a faulty kernel / audio driver. I've found the problem checking logcats, as well as logcats during the boot sequence.
If anyone know how to fix the audio driver, here's the thread: http://forum.xda-developers.com/showthread.php?p=50961786
I would like to access ADB from this device, this might help, but I cannot get the device detected at all.
USB debugging is definitely enabled, and the device driver is also installed (Not even sure if I had to install a driver for this 2011 device in first place. Device is detected by computer without a problem).
If I type:
Code:
adb devices
The output is just: "List of devices attached" with a blank line.
If I try:
Code:
adb shell
This show up:
Code:
error: device not found
I can tell that ADB is working for another device - I had a LG-P500, and ADB is succesfully working for this phone.
The faulty device is a Creative ZEN Touch 2, but the name won't be of any help. Let's just pretend it's a generic Android device (Even thought no such Android exists) and forget about the name. The ROM installed on it (Froyo, 2.2.1) was customized by Creative, the manufacturer, since it's not a phone, just a multimedia device.
I was wondering if Creative "blocked" any access to ADB, if that's possible. I do know that Creative "does not encourage self-repair", according to the forums.
I also tried ADB wireless, I pressed the grey button that turned green, and then typed adb connect xxx.xxx.x.108 (IP). On the shell, I got the error:
Code:
unable to connect to xxx.xxx.x.108:5555
Altought I wasn't able to connect wirelessly to ADB using my LG phone, neither.
On the ZEN Touch 2, I found the file default.prop, which contain this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
I honnestly don't know what the default.prop file is about, but I was wondering if the line "persist.service.adb.enable" being equal to 0 / false, could block the access to ADB shell, in some way (if that's possible).
I've read that this file is hard to modify, other than flash a new boot image.
What could I do to access ADB on this device ? Yes, the device is rooted.
EDIT: I have access to a Linux operating system, if that can make the detection easier. Although I do not have ADB installed on this OS, yet.
Thank you
GameX2 said:
Altought I wasn't able to connect wirelessly to ADB using my LG phone, neither.
On the ZEN Touch 2, I found the file default.prop, which contain this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
I honnestly don't know what the default.prop file is about, but I was wondering if the line "persist.service.adb.enable" being equal to 0 / false, could block the access to ADB shell, in some way (if that's possible).
I've read that this file is hard to modify, other than flash a new boot image.
What could I do to access ADB on this device ? Yes, the device is rooted.
EDIT: I have access to a Linux operating system, if that can make the detection easier. Although I do not have ADB installed on this OS, yet.
Thank you
Click to expand...
Click to collapse
You should edit default.prop in this way
Code:
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
Also you should look through your /init.rc for lines like this
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 1
start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
And also you should have adbd binary in /sbin
Code:
C:\1\MtkDroidTools2.5.3\adb>adb shell
[email protected]:/ # ls -al /sbin/adbd
ls -al /sbin/adbd
-rwxr-x--- root root 141212 2013-09-27 14:37 adbd
[email protected]:/ #
lion567 said:
You should edit default.prop in this way
Code:
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
Also you should look through your /init.rc for lines like this
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 1
start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
And also you should have adbd binary in /sbin
Code:
C:\1\MtkDroidTools2.5.3\adb>adb shell
[email protected]:/ # ls -al /sbin/adbd
ls -al /sbin/adbd
-rwxr-x--- root root 141212 2013-09-27 14:37 adbd
[email protected]:/ #
Click to expand...
Click to collapse
Hi,
Thanks for the reply;
I've checked, and adbd does exists in /sbin, with the correct permissions.
Here's the contain of my init.rc file. I don't see the lines you've mentionned, althought there are a few lines related to ADB. Where should I paste your lines ?
Code:
on init
sysclktz 0
loglevel 3
# setup the global environment
export PATH /sbin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export EXTERNAL_STORAGE /mnt/sdcard
export EXTERNAL_STORAGE_SD /mnt/sdcard
export EXTERNAL_STORAGE_UDISK /mnt/udisk
export EXTERNAL_STORAGE_EXTSD /mnt/extsd
export ASEC_MOUNTPOINT /mnt/asec
export SHM_MOUNTPOINT /mnt/shm
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
export BACKLIGHT_PATH /sys/class/backlight/tps60250/brightness
export MAX_BACKLIGHT_PATH /sys/class/backlight/tps60250/max_brightness
export VPU_FW_PATH /system/lib/firmware/vpu
export CODEC_SHM_PATH /mnt/shm
export GST_PLUGIN_PATH /system/lib/gst_plugins
export CORE_REGISTER_FILE /system/etc/core_register
export COMPONENT_REGISTER_FILE /system/etc/component_register
export CONTENTPIPE_REGISTER_FILE /system/etc/contentpipe_register
export BUILD_TARGET earlgrey
export LOG_LEVEL 0
# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d
# create mountpoints
# mkdir /mnt 0775 root system
# mkdir /mnt/sdcard 0000 system system
# mkdir /mnt/udisk 0000 system system
# mkdir /mnt/extsd 0000 system system
# Create cgroup mount point for cpu accounting
mkdir /acct
mount cgroup none /acct cpuacct
mkdir /acct/uid
# Backwards Compat - XXX: Going away in G*
symlink /mnt/sdcard /sdcard
symlink /mnt/extsd /extsd
symlink /mnt/udisk /udisk
# mkdir /system
# mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /config 0500 root root
# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root
# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root
# Directory-target for where the secure container
# imagefile directory will be bind-mounted
mkdir /mnt/secure/asec 0700 root root
# Secure container public mount points.
mkdir /mnt/asec 0700 root system
mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000
# shared memory used by middleware
mkdir /mnt/shm 0777 system graphics
mount tmpfs tmpfs /mnt/shm mode=0777,uid=1000,gid=1003,size=1m
#mount rootfs rootfs / ro remount
#mkdir /factory 0751 system system
mount tmpfs tmpfs /factory size=131072
write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0
# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown system system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0777 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024
mkdir /dev/cpuctl/fg_boost
chown system system /dev/cpuctl/fg_boost/tasks
chmod 0777 /dev/cpuctl/fg_boost/tasks
write /dev/cpuctl/fg_boost/cpu.shares 1024
mkdir /dev/cpuctl/bg_non_interactive
chown system system /dev/cpuctl/bg_non_interactive/tasks
chmod 0777 /dev/cpuctl/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/bg_non_interactive/cpu.shares 52
# Set permission for FSL device node
chmod 0777 /dev/mxc_vpu
# allow access to uart port for gps module
chmod 0777 /dev/ttymxc0
chmod 0777 /dev/ttymxc1
chmod 0777 /dev/ttymxc2
# for lcd driver work mode control
chown system system /dev/ili9481
chmod 0771 /dev/ili9481
# mount ext4 partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount ext4 /dev/block/mmcblk0p2 /system
mount ext4 /dev/block/mmcblk0p2 /system rw remount
chmod 0555 /system/etc/install-recovery.sh
mount ext4 /dev/block/mmcblk0p5 /data nosuid nodev
chown system system /data
chmod 0771 /data
exec /system/etc/init.first_time.sh
mount ext4 /dev/block/mmcblk0p2 /system ro remount
# We chown/chmod /data again so because mount is run as root + defaults
mount ext4 /dev/block/mmcblk0p5 /data nosuid nodev
chown system system /data
chmod 0771 /data
# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.
mkdir /data/dontpanic
chown root log /data/dontpanic
chmod 0750 /data/dontpanic
mkdir /data/synergy
chown root log /data/synergy
chmod 0777 /data/synergy
# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console
copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads
write /proc/apanic_console 1
# Same reason as /data above
mount ext4 /dev/block/mmcblk0p6 /cache nosuid nodev
chown system cache /cache
chmod 0770 /cache
# This may have been created by the recovery system with odd permissions
chown system cache /cache/recovery
chmod 0770 /cache/recovery
#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo
#change permissions on kmsg & sysrq-trigger so bugreports can grab kthread stacks
chown root system /proc/kmsg
chmod 0400 /proc/kmsg
chown root system /proc/sysrq-trigger
chmod 0220 /proc/sysrq-trigger
# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/vpn 0770 system system
mkdir /data/misc/systemkeys 0700 system system
mkdir /data/misc/vpn/profiles 0770 system system
# give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
chmod 0770 /data/misc/wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
mkdir /data/local 0771 shell shell
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/version 0770 root root
# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770
mkdir /cache/lost+found 0770
# double check the perms, in case lost+found already exists, and set owner
chown root root /data/lost+found
chmod 0770 /data/lost+found
chown root root /cache/lost+found
chmod 0770 /cache/lost+found
# change permission for keymap file temporarily
# should be removed when working out keymap later
chmod 0777 /system/usr/keychars/qwerty.kcm.bin
chmod 0777 /system/usr/keychars/Dell_Dell_USB_Keyboard.kcm.bin
chmod 0777 /system/usr/keychars/mxckpd.kcm.bin
chmod 0777 /system/usr/keychars/gpio-keys.kcm.bin
chmod 0777 /system/usr/keychars/mxc_ts-keypad.kcm.bin
chmod 0777 /system/usr/keychars/mxc_power_key.kcm.bin
chmod 0777 /system/usr/keychars/AVRCP.kcm.bin
chmod 0777 /sys/class/graphics/fb0/fsl_disp_property
chmod 0777 /sys/class/graphics/fb1/fsl_disp_property
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
mkdir /data/system 0775 system system
#exec /sbin/ts_calibrator
exec system/xbin/flash.dump.sh
# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40
# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.SECONDARY_SERVER_ADJ 2
setprop ro.BACKUP_APP_ADJ 2
setprop ro.HOME_APP_ADJ 4
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.CONTENT_PROVIDER_ADJ 14
setprop ro.EMPTY_APP_ADJ 15
# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 1536
setprop ro.VISIBLE_APP_MEM 2048
setprop ro.SECONDARY_SERVER_MEM 4096
setprop ro.BACKUP_APP_MEM 4096
setprop ro.HOME_APP_MEM 4096
setprop ro.HIDDEN_APP_MEM 5120
setprop ro.CONTENT_PROVIDER_MEM 5632
setprop ro.EMPTY_APP_MEM 6144
# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have HOME_APP at the
# same memory level as services.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15
write /proc/sys/vm/lowmem_reserve_ratio 1
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144
# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16
# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5
# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown radio system /sys/power/state
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
#chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
#chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/haptic/oneshot
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
chown root radio /proc/cmdline
# Chmod/chown FSL specific sys entry
chown radio system /sys/devices/platform/mxc_dvfs_core.0/enable
chown radio system /sys/devices/platform/busfreq.0/enable
chown system system /sys/class/backlight/tps60250/brightness
chmod 0660 /sys/devices/platform/mxc_dvfs_core.0/enable
chmod 0660 /sys/devices/platform/busfreq.0/enable
chmod 0660 /sys/class/backlight/tps60250/brightness
write /sys/devices/platform/busfreq.0/enable 1
write /sys/devices/platform/mxc_dvfs_core.0/enable 1
# allow control power for ecompass and gsensor
chown system system /sys/class/i2c-adapter/i2c-0/0-001c/akm8973_ctl
chmod 0777 /sys/class/i2c-adapter/i2c-0/0-001c/akm8973_ctl
#chown system system /sys/class/i2c-adapter/i2c-0/0-001d/power_ctl
#chmod 0777 /sys/class/i2c-adapter/i2c-0/0-001d/power_ctl
# for GPS gpio driver for gps power and bootmode control
chown system system /dev/gps_gpio
chown system system /sys/devices/virtual/gps/gps_gpio/gps_power
chown system system /sys/devices/virtual/gps/gps_gpio/gps_bootmode
chmod 0771 /dev/gps_gpio
chmod 0660 /sys/devices/virtual/gps/gps_gpio/gps_power
chmod 0771 /sys/devices/virtual/gps/gps_gpio/gps_bootmode
# for Sensor HAL
chown system system /dev/accel
chown system system /dev/akm8973_dev
chown system system /dev/akm8973_aot
chmod 0777 /dev/accel
chmod 0777 /dev/akm8973_dev
chmod 0777 /dev/akm8973_aot
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.wifi 4095,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
# Set property for FSL specific feature
# Init second display connection state
setprop rw.SECOND_DISPLAY_CONNECTED 0
# Define gst player property
setprop media.gstreamer.enable-player 0
# Comment the usage of stageflight media framework
setprop media.stagefright.enable-scan 0
setprop media.stagefright.enable-player 0
setprop media.stagefright.enable-record 0
setprop media.stagefright.enable-http 0
setprop media.stagefright.enable-meta 0
# Define fsl avi/aac/asf/mkv/flv/flac format support
setprop ro.FSL_AVI_PARSER 1
setprop ro.FSL_AAC_PARSER 1
setprop ro.FSL_ASF_PARSER 1
setprop ro.FSL_FLV_PARSER 1
setprop ro.FSL_MKV_PARSER 1
setprop ro.FSL_FLAC_PARSER 1
# Define fsl display init mode
setprop ro.FSL_LANDSCAPE_MODE 1
# Define fsl xec mode
setprop xec.dls.enabled 1
setprop xec.aa.enabled 1
setprop xec.dls.rate 0
setprop xec.aa.rate 100
# Define fsl dvfs property
setprop ro.dvfs.enabled 1
# Define UI to TVOUT,change this setting to 1 and uncomment below write commands
setprop ro.UI_TVOUT_DISPLAY 0
#write /sys/class/graphics/fb0/blank 1
#write /sys/class/graphics/fb1/blank 1
#write /sys/class/graphics/fb2/blank 1
#write /sys/class/graphics/fb0/fsl_disp_property 1-layer-fb
#write /sys/class/graphics/fb1/mode U:720x480i-60\n
#write /sys/class/graphics/fb1/blank 0
chown system system /sys/class/graphics/fb1/blank
chmod 0644 /sys/class/graphics/fb1/blank
chown system system /sys/class/graphics/fb1/mode
chmod 0644 /sys/class/graphics/fb1/mode
#chown system system /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
#chmod 0644 /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
# Define default notification_sound
setprop ro.config.notification_sound OnTheHunt.ogg
# for switch on/off framebuffer
chown system system /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
chown system system /sys/devices/platform/mxc_sdc_fb.1/graphics/fb1/blank
chown system system /sys/devices/platform/mxc_sdc_fb.2/graphics/fb2/blank
chmod 0644 /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
chmod 0644 /sys/devices/platform/mxc_sdc_fb.1/graphics/fb1/blank
chmod 0644 /sys/devices/platform/mxc_sdc_fb.2/graphics/fb2/blank
# ALSA mixer naming define
setprop alsa.mixer.playback.master Playback
setprop alsa.mixer.capture.master Capture
setprop alsa.mixer.playback.speaker Playback
setprop alsa.mixer.playback.headset Headphone
setprop alsa.mixer.capture.headset Capture
# Prepare for wifi
setprop wifi.interface wlan0
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
chown dhcp dhcp /data/misc/dhcp
# DD partitions for diversity and ECD key region for access
chmod 0751 /factory
chown system system /factory
chmod 0777 /dev/block/mmcblk0
chmod 6777 /system/bin/dd
chown system system /system/bin/toolbox
exec /system/xbin/init.diversity.ecd.sh
# mount calibration data region
chown system system /dev/block/mmcblk0
chmod 0777 /dev/block/mmcblk0
chmod 0777 /sys/module/pd_ts13892/parameters/calibration
exec /system/xbin/init.calibration.sh
exec /system/bin/ts13892_calibrator
chmod 751 /system/xbin/flash_sync
# Prepare for bluetooth
# chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
# chmod 666 /sys/class/rfkill/rfkill0/state
# chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
# write /sys/class/rfkill/rfkill0/state 0
# Enable USB host1'remote wakeup event wakeup android system
# write /sys/bus/platform/drivers/fsl-ehci/fsl-ehci.1/power/wakeup enabled
# Prepare for RIL
setprop gsm.ril.delay 15
#change file permission for synergy
chown root shell /system/etc/synergy_fts.sh
chmod 0550 /system/etc/synergy_fts.sh
class_start default
## Daemon processes to be run by init.
##
service console /system/bin/sh
console
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
user root
group root
disabled
# adbd on at boot in emulator
#on property:ro.kernel.qemu=1
# start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
service servicemanager /system/bin/servicemanager
user system
critical
onrestart restart zygote
onrestart restart media
service vold /system/bin/vold
socket vold stream 0660 root mount
ioprio be 2
service netd /system/bin/netd
socket netd stream 0660 root system
service dispd /system/bin/dispd
socket dispd stream 0660 root system
service debuggerd /system/bin/debuggerd
service ril-daemon /system/bin/rild -l /system/lib/libreference-ril.so -- -d /dev/ttyUSB3 -u /dev/ttyUSB0
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw
ioprio rt 4
service bootanim /system/bin/bootanimation
user graphics
group graphics
disabled
oneshot
service dbus /system/bin/dbus-daemon --system --nofork
socket dbus stream 666 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin
service bluetoothd /system/bin/bluetoothd -n
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let hcid drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service hciattach /system/bin/logwrapper /system/bin/sh /system/etc/mxc_bt.sh
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service hfag /system/bin/sdptool add --channel=10 HFAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service hsag /system/bin/sdptool add --channel=11 HSAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service opush /system/bin/sdptool add --channel=12 OPUSH
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service pbap /system/bin/sdptool add --channel=19 PBAP
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service synergy_fts_init /system/etc/synergy_fts.sh
user root
group sdcard_rw
oneshot
service synergysdpops /system/etc/synergy_sdptool.sh 12 0x1105 ReservedOPPS
user root
disabled
oneshot
#service hidloopback /system/etc/insert-hiddrv.sh
# user root
# oneshot
service installd /system/bin/installd
socket installd stream 600 system system
service flash_recovery /system/etc/install-recovery.sh
oneshot
service racoon /system/bin/racoon
socket racoon stream 600 system system
# racoon will setuid to vpn after getting necessary resources.
group net_admin
disabled
oneshot
service mtpd /system/bin/mtpd
socket mtpd stream 600 system system
user vpn
group vpn net_admin net_raw
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
user keystore
group keystore
socket keystore stream 666
service dumpstate /system/bin/dumpstate -s
socket dumpstate stream 0660 shell log
disabled
oneshot
#service dhcpcd /system/bin/logwrapper /system/bin/dhcpcd -d -B wlan0
service dhcpcd /system/bin/dhcpcd -d -B wlan0
disabled
oneshot
service wpa_supplicant /system/bin/logwrapper /system/bin/wpa_supplicant \
-Dwext -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf
user root
group wifi inet
socket wpa_wlan0 dgram 660 wifi wifi
oneshot
#service pppd_gprs /etc/init.gprs-pppd
#user root
#group radio cache inet misc
#disabled
#oneshot
service akmd2 /system/bin/akmd2
user system
group system
oneshot
# save diversity.bin from memory to emmc
service div_restore_m /system/bin/dd if=/factory/diversity.bin of=/dev/block/mmcblk0 obs=512 seek=14337 count=1
user root
group system
disabled
oneshot
# restore diversity.bin from diversity data
service div_restore_w /system/bin/dd if=/factory/diversity.master of=/dev/block/mmcblk0 obs=512 seek=14336 count=1
user root
group system
disabled
oneshot
# flash sync
service flash_sync /system/xbin/flash_sync
user root
group system
service synergy_exe /system/xbin/synergy_exe
user root
service a2dp_adapter /system/bin/csr_liba2dp_process
user root
group system audio camera graphics inet net_bt net_bt_admin
service flash_wifi /system/xbin/flash_wifi
disabled
oneshot
service wlan0_check /system/xbin/wlan0_check
disabled
oneshot
As for the default.prop file, should I just delete the contain, and simply replace it by yours? The file will save properly? Additionally, may I ask what defaut.prop is used for ?
Thank you
GameX2 said:
Hi,
Thanks for the reply;
I've checked, and adbd does exists in /sbin, with the correct permissions.
Here's the contain of my init.rc file. I don't see the lines you've mentionned, althought there are a few lines related to ADB. Where should I paste your lines ?
Code:
on init
sysclktz 0
loglevel 3
# setup the global environment
export PATH /sbin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export EXTERNAL_STORAGE /mnt/sdcard
export EXTERNAL_STORAGE_SD /mnt/sdcard
export EXTERNAL_STORAGE_UDISK /mnt/udisk
export EXTERNAL_STORAGE_EXTSD /mnt/extsd
export ASEC_MOUNTPOINT /mnt/asec
export SHM_MOUNTPOINT /mnt/shm
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
export BACKLIGHT_PATH /sys/class/backlight/tps60250/brightness
export MAX_BACKLIGHT_PATH /sys/class/backlight/tps60250/max_brightness
export VPU_FW_PATH /system/lib/firmware/vpu
export CODEC_SHM_PATH /mnt/shm
export GST_PLUGIN_PATH /system/lib/gst_plugins
export CORE_REGISTER_FILE /system/etc/core_register
export COMPONENT_REGISTER_FILE /system/etc/component_register
export CONTENTPIPE_REGISTER_FILE /system/etc/contentpipe_register
export BUILD_TARGET earlgrey
export LOG_LEVEL 0
# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d
# create mountpoints
# mkdir /mnt 0775 root system
# mkdir /mnt/sdcard 0000 system system
# mkdir /mnt/udisk 0000 system system
# mkdir /mnt/extsd 0000 system system
# Create cgroup mount point for cpu accounting
mkdir /acct
mount cgroup none /acct cpuacct
mkdir /acct/uid
# Backwards Compat - XXX: Going away in G*
symlink /mnt/sdcard /sdcard
symlink /mnt/extsd /extsd
symlink /mnt/udisk /udisk
# mkdir /system
# mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /config 0500 root root
# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root
# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root
# Directory-target for where the secure container
# imagefile directory will be bind-mounted
mkdir /mnt/secure/asec 0700 root root
# Secure container public mount points.
mkdir /mnt/asec 0700 root system
mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000
# shared memory used by middleware
mkdir /mnt/shm 0777 system graphics
mount tmpfs tmpfs /mnt/shm mode=0777,uid=1000,gid=1003,size=1m
#mount rootfs rootfs / ro remount
#mkdir /factory 0751 system system
mount tmpfs tmpfs /factory size=131072
write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0
# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown system system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0777 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024
mkdir /dev/cpuctl/fg_boost
chown system system /dev/cpuctl/fg_boost/tasks
chmod 0777 /dev/cpuctl/fg_boost/tasks
write /dev/cpuctl/fg_boost/cpu.shares 1024
mkdir /dev/cpuctl/bg_non_interactive
chown system system /dev/cpuctl/bg_non_interactive/tasks
chmod 0777 /dev/cpuctl/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/bg_non_interactive/cpu.shares 52
# Set permission for FSL device node
chmod 0777 /dev/mxc_vpu
# allow access to uart port for gps module
chmod 0777 /dev/ttymxc0
chmod 0777 /dev/ttymxc1
chmod 0777 /dev/ttymxc2
# for lcd driver work mode control
chown system system /dev/ili9481
chmod 0771 /dev/ili9481
# mount ext4 partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount ext4 /dev/block/mmcblk0p2 /system
mount ext4 /dev/block/mmcblk0p2 /system rw remount
chmod 0555 /system/etc/install-recovery.sh
mount ext4 /dev/block/mmcblk0p5 /data nosuid nodev
chown system system /data
chmod 0771 /data
exec /system/etc/init.first_time.sh
mount ext4 /dev/block/mmcblk0p2 /system ro remount
# We chown/chmod /data again so because mount is run as root + defaults
mount ext4 /dev/block/mmcblk0p5 /data nosuid nodev
chown system system /data
chmod 0771 /data
# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.
mkdir /data/dontpanic
chown root log /data/dontpanic
chmod 0750 /data/dontpanic
mkdir /data/synergy
chown root log /data/synergy
chmod 0777 /data/synergy
# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console
copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads
write /proc/apanic_console 1
# Same reason as /data above
mount ext4 /dev/block/mmcblk0p6 /cache nosuid nodev
chown system cache /cache
chmod 0770 /cache
# This may have been created by the recovery system with odd permissions
chown system cache /cache/recovery
chmod 0770 /cache/recovery
#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo
#change permissions on kmsg & sysrq-trigger so bugreports can grab kthread stacks
chown root system /proc/kmsg
chmod 0400 /proc/kmsg
chown root system /proc/sysrq-trigger
chmod 0220 /proc/sysrq-trigger
# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/vpn 0770 system system
mkdir /data/misc/systemkeys 0700 system system
mkdir /data/misc/vpn/profiles 0770 system system
# give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
chmod 0770 /data/misc/wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
mkdir /data/local 0771 shell shell
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/version 0770 root root
# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770
mkdir /cache/lost+found 0770
# double check the perms, in case lost+found already exists, and set owner
chown root root /data/lost+found
chmod 0770 /data/lost+found
chown root root /cache/lost+found
chmod 0770 /cache/lost+found
# change permission for keymap file temporarily
# should be removed when working out keymap later
chmod 0777 /system/usr/keychars/qwerty.kcm.bin
chmod 0777 /system/usr/keychars/Dell_Dell_USB_Keyboard.kcm.bin
chmod 0777 /system/usr/keychars/mxckpd.kcm.bin
chmod 0777 /system/usr/keychars/gpio-keys.kcm.bin
chmod 0777 /system/usr/keychars/mxc_ts-keypad.kcm.bin
chmod 0777 /system/usr/keychars/mxc_power_key.kcm.bin
chmod 0777 /system/usr/keychars/AVRCP.kcm.bin
chmod 0777 /sys/class/graphics/fb0/fsl_disp_property
chmod 0777 /sys/class/graphics/fb1/fsl_disp_property
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
mkdir /data/system 0775 system system
#exec /sbin/ts_calibrator
exec system/xbin/flash.dump.sh
# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40
# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.SECONDARY_SERVER_ADJ 2
setprop ro.BACKUP_APP_ADJ 2
setprop ro.HOME_APP_ADJ 4
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.CONTENT_PROVIDER_ADJ 14
setprop ro.EMPTY_APP_ADJ 15
# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 1536
setprop ro.VISIBLE_APP_MEM 2048
setprop ro.SECONDARY_SERVER_MEM 4096
setprop ro.BACKUP_APP_MEM 4096
setprop ro.HOME_APP_MEM 4096
setprop ro.HIDDEN_APP_MEM 5120
setprop ro.CONTENT_PROVIDER_MEM 5632
setprop ro.EMPTY_APP_MEM 6144
# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have HOME_APP at the
# same memory level as services.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15
write /proc/sys/vm/lowmem_reserve_ratio 1
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144
# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16
# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5
# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown radio system /sys/power/state
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
#chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
#chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/haptic/oneshot
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
chown root radio /proc/cmdline
# Chmod/chown FSL specific sys entry
chown radio system /sys/devices/platform/mxc_dvfs_core.0/enable
chown radio system /sys/devices/platform/busfreq.0/enable
chown system system /sys/class/backlight/tps60250/brightness
chmod 0660 /sys/devices/platform/mxc_dvfs_core.0/enable
chmod 0660 /sys/devices/platform/busfreq.0/enable
chmod 0660 /sys/class/backlight/tps60250/brightness
write /sys/devices/platform/busfreq.0/enable 1
write /sys/devices/platform/mxc_dvfs_core.0/enable 1
# allow control power for ecompass and gsensor
chown system system /sys/class/i2c-adapter/i2c-0/0-001c/akm8973_ctl
chmod 0777 /sys/class/i2c-adapter/i2c-0/0-001c/akm8973_ctl
#chown system system /sys/class/i2c-adapter/i2c-0/0-001d/power_ctl
#chmod 0777 /sys/class/i2c-adapter/i2c-0/0-001d/power_ctl
# for GPS gpio driver for gps power and bootmode control
chown system system /dev/gps_gpio
chown system system /sys/devices/virtual/gps/gps_gpio/gps_power
chown system system /sys/devices/virtual/gps/gps_gpio/gps_bootmode
chmod 0771 /dev/gps_gpio
chmod 0660 /sys/devices/virtual/gps/gps_gpio/gps_power
chmod 0771 /sys/devices/virtual/gps/gps_gpio/gps_bootmode
# for Sensor HAL
chown system system /dev/accel
chown system system /dev/akm8973_dev
chown system system /dev/akm8973_aot
chmod 0777 /dev/accel
chmod 0777 /dev/akm8973_dev
chmod 0777 /dev/akm8973_aot
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.wifi 4095,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
# Set property for FSL specific feature
# Init second display connection state
setprop rw.SECOND_DISPLAY_CONNECTED 0
# Define gst player property
setprop media.gstreamer.enable-player 0
# Comment the usage of stageflight media framework
setprop media.stagefright.enable-scan 0
setprop media.stagefright.enable-player 0
setprop media.stagefright.enable-record 0
setprop media.stagefright.enable-http 0
setprop media.stagefright.enable-meta 0
# Define fsl avi/aac/asf/mkv/flv/flac format support
setprop ro.FSL_AVI_PARSER 1
setprop ro.FSL_AAC_PARSER 1
setprop ro.FSL_ASF_PARSER 1
setprop ro.FSL_FLV_PARSER 1
setprop ro.FSL_MKV_PARSER 1
setprop ro.FSL_FLAC_PARSER 1
# Define fsl display init mode
setprop ro.FSL_LANDSCAPE_MODE 1
# Define fsl xec mode
setprop xec.dls.enabled 1
setprop xec.aa.enabled 1
setprop xec.dls.rate 0
setprop xec.aa.rate 100
# Define fsl dvfs property
setprop ro.dvfs.enabled 1
# Define UI to TVOUT,change this setting to 1 and uncomment below write commands
setprop ro.UI_TVOUT_DISPLAY 0
#write /sys/class/graphics/fb0/blank 1
#write /sys/class/graphics/fb1/blank 1
#write /sys/class/graphics/fb2/blank 1
#write /sys/class/graphics/fb0/fsl_disp_property 1-layer-fb
#write /sys/class/graphics/fb1/mode U:720x480i-60\n
#write /sys/class/graphics/fb1/blank 0
chown system system /sys/class/graphics/fb1/blank
chmod 0644 /sys/class/graphics/fb1/blank
chown system system /sys/class/graphics/fb1/mode
chmod 0644 /sys/class/graphics/fb1/mode
#chown system system /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
#chmod 0644 /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
# Define default notification_sound
setprop ro.config.notification_sound OnTheHunt.ogg
# for switch on/off framebuffer
chown system system /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
chown system system /sys/devices/platform/mxc_sdc_fb.1/graphics/fb1/blank
chown system system /sys/devices/platform/mxc_sdc_fb.2/graphics/fb2/blank
chmod 0644 /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/blank
chmod 0644 /sys/devices/platform/mxc_sdc_fb.1/graphics/fb1/blank
chmod 0644 /sys/devices/platform/mxc_sdc_fb.2/graphics/fb2/blank
# ALSA mixer naming define
setprop alsa.mixer.playback.master Playback
setprop alsa.mixer.capture.master Capture
setprop alsa.mixer.playback.speaker Playback
setprop alsa.mixer.playback.headset Headphone
setprop alsa.mixer.capture.headset Capture
# Prepare for wifi
setprop wifi.interface wlan0
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
chown dhcp dhcp /data/misc/dhcp
# DD partitions for diversity and ECD key region for access
chmod 0751 /factory
chown system system /factory
chmod 0777 /dev/block/mmcblk0
chmod 6777 /system/bin/dd
chown system system /system/bin/toolbox
exec /system/xbin/init.diversity.ecd.sh
# mount calibration data region
chown system system /dev/block/mmcblk0
chmod 0777 /dev/block/mmcblk0
chmod 0777 /sys/module/pd_ts13892/parameters/calibration
exec /system/xbin/init.calibration.sh
exec /system/bin/ts13892_calibrator
chmod 751 /system/xbin/flash_sync
# Prepare for bluetooth
# chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
# chmod 666 /sys/class/rfkill/rfkill0/state
# chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
# write /sys/class/rfkill/rfkill0/state 0
# Enable USB host1'remote wakeup event wakeup android system
# write /sys/bus/platform/drivers/fsl-ehci/fsl-ehci.1/power/wakeup enabled
# Prepare for RIL
setprop gsm.ril.delay 15
#change file permission for synergy
chown root shell /system/etc/synergy_fts.sh
chmod 0550 /system/etc/synergy_fts.sh
class_start default
## Daemon processes to be run by init.
##
service console /system/bin/sh
console
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
user root
group root
disabled
# adbd on at boot in emulator
#on property:ro.kernel.qemu=1
# start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
service servicemanager /system/bin/servicemanager
user system
critical
onrestart restart zygote
onrestart restart media
service vold /system/bin/vold
socket vold stream 0660 root mount
ioprio be 2
service netd /system/bin/netd
socket netd stream 0660 root system
service dispd /system/bin/dispd
socket dispd stream 0660 root system
service debuggerd /system/bin/debuggerd
service ril-daemon /system/bin/rild -l /system/lib/libreference-ril.so -- -d /dev/ttyUSB3 -u /dev/ttyUSB0
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw
ioprio rt 4
service bootanim /system/bin/bootanimation
user graphics
group graphics
disabled
oneshot
service dbus /system/bin/dbus-daemon --system --nofork
socket dbus stream 666 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin
service bluetoothd /system/bin/bluetoothd -n
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let hcid drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service hciattach /system/bin/logwrapper /system/bin/sh /system/etc/mxc_bt.sh
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service hfag /system/bin/sdptool add --channel=10 HFAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service hsag /system/bin/sdptool add --channel=11 HSAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service opush /system/bin/sdptool add --channel=12 OPUSH
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service pbap /system/bin/sdptool add --channel=19 PBAP
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service synergy_fts_init /system/etc/synergy_fts.sh
user root
group sdcard_rw
oneshot
service synergysdpops /system/etc/synergy_sdptool.sh 12 0x1105 ReservedOPPS
user root
disabled
oneshot
#service hidloopback /system/etc/insert-hiddrv.sh
# user root
# oneshot
service installd /system/bin/installd
socket installd stream 600 system system
service flash_recovery /system/etc/install-recovery.sh
oneshot
service racoon /system/bin/racoon
socket racoon stream 600 system system
# racoon will setuid to vpn after getting necessary resources.
group net_admin
disabled
oneshot
service mtpd /system/bin/mtpd
socket mtpd stream 600 system system
user vpn
group vpn net_admin net_raw
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
user keystore
group keystore
socket keystore stream 666
service dumpstate /system/bin/dumpstate -s
socket dumpstate stream 0660 shell log
disabled
oneshot
#service dhcpcd /system/bin/logwrapper /system/bin/dhcpcd -d -B wlan0
service dhcpcd /system/bin/dhcpcd -d -B wlan0
disabled
oneshot
service wpa_supplicant /system/bin/logwrapper /system/bin/wpa_supplicant \
-Dwext -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf
user root
group wifi inet
socket wpa_wlan0 dgram 660 wifi wifi
oneshot
#service pppd_gprs /etc/init.gprs-pppd
#user root
#group radio cache inet misc
#disabled
#oneshot
service akmd2 /system/bin/akmd2
user system
group system
oneshot
# save diversity.bin from memory to emmc
service div_restore_m /system/bin/dd if=/factory/diversity.bin of=/dev/block/mmcblk0 obs=512 seek=14337 count=1
user root
group system
disabled
oneshot
# restore diversity.bin from diversity data
service div_restore_w /system/bin/dd if=/factory/diversity.master of=/dev/block/mmcblk0 obs=512 seek=14336 count=1
user root
group system
disabled
oneshot
# flash sync
service flash_sync /system/xbin/flash_sync
user root
group system
service synergy_exe /system/xbin/synergy_exe
user root
service a2dp_adapter /system/bin/csr_liba2dp_process
user root
group system audio camera graphics inet net_bt net_bt_admin
service flash_wifi /system/xbin/flash_wifi
disabled
oneshot
service wlan0_check /system/xbin/wlan0_check
disabled
oneshot
As for the default.prop file, should I just delete the contain, and simply replace it by yours? The file will save properly? Additionally, may I ask what defaut.prop is used for ?
Thank you
Click to expand...
Click to collapse
You does already have commands for starting adbd in your init.rc. Here they are.
Code:
# adbd is controlled by the [B]persist.service.adb.enable[/B] system property
service adbd /sbin/adbd
user root
group root
disabled
# adbd on at boot in emulator
#on property:ro.kernel.qemu=1
# start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
You have to change
Code:
persist.service.adb.enable=1
in your deafult.prop and add (or change if alredy exist) for USB adb connection
Code:
persist.sys.usb.config=mass_storage,adb
And yes, to modify your default.prop file you have to unpack your boot.img, edit the file, then pack it back and flash modified boot.img to your device.
lion567 said:
You does already have commands for starting adbd in your init.rc. Here they are.
Code:
# adbd is controlled by the [B]persist.service.adb.enable[/B] system property
service adbd /sbin/adbd
user root
group root
disabled
# adbd on at boot in emulator
#on property:ro.kernel.qemu=1
# start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
You have to change
Code:
persist.service.adb.enable=1
in your deafult.prop and add (or change if alredy exist) for USB adb connection
Code:
persist.sys.usb.config=mass_storage,adb
And yes, to modify your default.prop file you have to unpack your boot.img, edit the file, then pack it back and flash modified boot.img to your device.
Click to expand...
Click to collapse
Thank you, I will do that.
I already dumped my ROM with romdump, but I don't have my boot.img yet. I will do ressearch on how to back it up.
I have a problem related to this, I'm not sure if I'll be able to restore it, as it's currently impossible to flash ClockworkMod to this device (No image exist. Same for custom ROMs).
The only thing I have, is Android Recovery 3e, which does not support by default flashing unsigned update.zip. I did applied a patch here, which is supposed to bypass this limitation, but have not tested it yet.
So I should have my boot.img packed as a update.zip, I believe, then give it a try, and flash it through Android Recovery 3e ?
GameX2 said:
Thank you, I will do that.
I already dumped my ROM with romdump, but I don't have my boot.img yet. I will do ressearch on how to back it up.
I have a problem related to this, I'm not sure if I'll be able to restore it, as it's currently impossible to flash ClockworkMod to this device (No image exist. Same for custom ROMs).
Click to expand...
Click to collapse
Different devices have different ROM layout, you shoud try to find more infirmation about it.
IMHO the easiest way to get image of your boot partition is via dd. You should have busybox and terminal emulator installed on device to do this:
Code:
[email protected]:/ # dd if=/dev/bootimg of=/mnt/sdcard/boot.img bs=<your boot size> count=1
GameX2 said:
The only thing I have, is Android Recovery 3e, which does not support by default flashing unsigned update.zip. I did applied a patch here, which is supposed to bypass this limitation, but have not tested it yet.
So I should have my boot.img packed as a update.zip, I believe, then give it a try, and flash it through Android Recovery 3e ?
Click to expand...
Click to collapse
Yes of course you may create update.zip for flashing new boot.img, but you have to sing it, AFAIK stock recovery check update.zip signature before flashing it.
lion567 said:
Different devices have different ROM layout, you shoud try to find more infirmation about it.
IMHO the easiest way to get image of your boot partition is via dd. You should have busybox and terminal emulator installed on device to do this:
Code:
[email protected]:/ # dd if=/dev/bootimg of=/mnt/sdcard/boot.img bs=<your boot size> count=1
Yes of course you may create update.zip for flashing new boot.img, but you have to sing it, AFAIK stock recovery check update.zip signature before flashing it.
Click to expand...
Click to collapse
There is hardly any way to get more information/help on this device, that's the sad thing. You just have to try according to your Android experience, without relying much on external help.
I will check for dd to dump the partition, as well as the boot size (Boot size of boot.img, most probably), the device is rooted so has busybox and a terminal emulator as well.
Creating an update.zip might be the only way I have to flash it back in, tell me if I'm wrong. Since I can't install CWM without compiling a custom one for my device (Never done that before), I just have access to Android Recovery 3e. You're right, I does check the signature, and block it for most of the files.
I've done this, which is supposed to bypass the signature check. I have not tested the flashing, but Android Recovery 3e was not damaged and is still accessible.
http://forum.xda-developers.com/showthread.php?p=10624454#post10624454
Will keep you updated, thanks.
GameX2 said:
There is hardly any way to get more information/help on this device, that's the sad thing. You just have to try according to your Android experience, without relying much on external help.
I will check for dd to dump the partition, as well as the boot size (Boot size of boot.img, most probably), the device is rooted so has busybox and a terminal emulator as well.
Creating an update.zip might be the only way I have to flash it back in, tell me if I'm wrong. Since I can't install CWM without compiled a custom one for my device (Never done that before), I just have access to Android Recovery 3e. You're right, I does check the signature, and block it for most of the files.
I've done this, which is supposed to bypass the signature check. I have not tested the flashing, but Android Recovery 3e was not damaged and is still accessible.
http://forum.xda-developers.com/showthread.php?p=10624454#post10624454
Will keep you updated, thanks.
Click to expand...
Click to collapse
For dd command you should use full size of boot partition or partition, where boot ramdisk lives (on some devices it can live separately from kernel). And corresponding device file (eg /dev/bootimg in my example).
If you succeed with boot.img dump via dd, you could use the same dd command, swapping if = and of= files, like this
Code:
dd if=/mnt/sdcard/new-boot.img of=/dev/bootimg bs=<size of boot partition> count=1
In this case "bs=<size of boot partition> count=1" protect you from overwriting data in partition next to bootimg in case new-boot.img exceeds the size of boot partition.
By the way, you can look in /system/build.prop file to find some information about device.
Does any ROM flashing tool exist for this device, like ODIN for Samsung, NVFlash for Tegra devices and SP FlashTool for MTK devices?
lion567 said:
For dd command you should use full size of boot partition or partition, where boot ramdisk lives (on some devices it can live separately from kernel). And corresponding device file (eg /dev/bootimg in my example).
If you succeed with boot.img dump via dd, you could use the same dd command, swapping if = and of= files, like this
Code:
dd if=/mnt/sdcard/new-boot.img of=/dev/bootimg bs=<size of boot partition> count=1
In this case "bs=<size of boot partition> count=1" protect you from overwriting data in partition next to bootimg in case new-boot.img exceeds the size of boot partition.
By the way, you can look in /system/build.prop file to find some information about device.
Does any ROM flashing tool exist for this device, like ODIN for Samsung, NVFlash for Tegra devices and SP FlashTool for MTK devices?
Click to expand...
Click to collapse
Thanks;
I'm trying to find the size of my /Boot partition, for now. Here's the terminal output of cat /proc/partitions:
Code:
$cat /proc/mtd
dev: size erasesize name
$cat /proc/partitions
major minor #blocks name
179 0 7815168 mmcblk0
179 1 4309200 mmcblk0p1
179 2 154035 mmcblk0p2
179 3 1 mmcblk0p3
179 4 10395 mmcblk0p4
179 5 3145873 mmcblk0p5
179 6 41076 mmcblk0p6
$
According to the app "Storage Analyser", I would have these partitions visibles:
/sdcard : 4.1 GB total (Internal storage);
/system: 128.68 MB total;
/data: 2.95GB total;
/cache (No info, but I assume there is one!);
And /boot, which I don't know where it's located yet.
Just a guess, the partitition 179 3 1 mmcblk0p3 might refer to /extsd. Note that the ZEN Touch 2 has an internal storage, which is /sdcard, and also an external slot for a microSD card (being /extsd). Which I believe, would make sense that the 1MB partition would be /extsd (I have no external SD card inserted at this point).
I noted a few SPECs from the device, in Elixir, myself:
ARMv7 Processor rev 5 )v7l) 800MHz (200 MHz-800 MHz)
Android ID : 65d3e923b8b46272
Model number: Creative Earlgrey 2.2.1
Kernel: SDK 8 Linux Version 2.6.31
Here's the build.prop file:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF85B
ro.build.display.id=FRF85B
ro.build.version.incremental=eng.20110408.110506
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Fri Apr 8 11:15:22 HKT 2011
ro.build.date.utc=1302232522
ro.build.type=user
ro.build.user=Creative
ro.build.host=localhost.localdomain
ro.build.tags=test-keys
ro.product.model=earlgrey
ro.product.brand=Creative
ro.product.name=earlgrey
ro.product.device=earlgrey
ro.product.board=earlgrey
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Creative
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=earlgrey
# ro.build.product is obsolete; use ro.product.device
ro.build.product=earlgrey
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=earlgrey-user 2.2.1 FRF85B eng.20110408.110506 test-keys
ro.build.fingerprint=Creative/earlgrey/earlgrey/earlgrey:2.2.1/FRF85B/eng.20110408.110506:user/test-keys
# end build properties
#
# system.prop for ZEN Touch 2
#
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
#
# ADDITIONAL_BUILD_PROPERTIES
#
dalvik.vm.heapsize=32m
dalvik.vm.checkjni=false
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Does any ROM flashing tool exist for this device, like ODIN for Samsung, NVFlash for Tegra devices and SP FlashTool for MTK devices?
Click to expand...
Click to collapse
I never used ODIN, but I can tell that ROM Manager is useless, because the device is unlisted - officially, no ROM flashing tool was developped at all, for this specific device. I've checked, usually all those who ask these questions never got replies.
Thank for the help, I appreciate it.
GameX2 said:
Thanks;
I'm trying to find the size of my /Boot partition, for now. Here's the terminal output of cat /proc/partitions:
Code:
$cat /proc/mtd
dev: size erasesize name
$cat /proc/partitions
major minor #blocks name
179 0 7815168 mmcblk0
179 1 4309200 mmcblk0p1
179 2 154035 mmcblk0p2
179 3 1 mmcblk0p3
179 4 10395 mmcblk0p4
179 5 3145873 mmcblk0p5
179 6 41076 mmcblk0p6
$
According to the app "Storage Analyser", I would have these partitions visibles:
/sdcard : 4.1 GB total (Internal storage);
/system: 128.68 MB total;
/data: 2.95GB total;
/cache (No info, but I assume there is one!);
And /boot, which I don't know where it's located yet.
Just a guess, the partitition 179 3 1 mmcblk0p3 might refer to /extsd. Note that the ZEN Touch 2 has an internal storage, which is /sdcard, and also an external slot for a microSD card (being /extsd). Which I believe, would make sense that the 1MB partition would be /extsd (I have no external SD card inserted at this point).
I noted a few SPECs from the device, in Elixir, myself:
ARMv7 Processor rev 5 )v7l) 800MHz (200 MHz-800 MHz)
Android ID : 65d3e923b8b46272
Model number: Creative Earlgrey 2.2.1
Kernel: SDK 8 Linux Version 2.6.31
Here's the build.prop file:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF85B
ro.build.display.id=FRF85B
ro.build.version.incremental=eng.20110408.110506
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Fri Apr 8 11:15:22 HKT 2011
ro.build.date.utc=1302232522
ro.build.type=user
ro.build.user=Creative
ro.build.host=localhost.localdomain
ro.build.tags=test-keys
ro.product.model=earlgrey
ro.product.brand=Creative
ro.product.name=earlgrey
ro.product.device=earlgrey
ro.product.board=earlgrey
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Creative
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=earlgrey
# ro.build.product is obsolete; use ro.product.device
ro.build.product=earlgrey
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=earlgrey-user 2.2.1 FRF85B eng.20110408.110506 test-keys
ro.build.fingerprint=Creative/earlgrey/earlgrey/earlgrey:2.2.1/FRF85B/eng.20110408.110506:user/test-keys
# end build properties
#
# system.prop for ZEN Touch 2
#
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
#
# ADDITIONAL_BUILD_PROPERTIES
#
dalvik.vm.heapsize=32m
dalvik.vm.checkjni=false
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
I never used ODIN, but I can tell that ROM Manager is useless, because the device is unlisted - officially, no ROM flashing tool was developped at all, for this specific device. I've checked, usually all those who ask these questions never got replies.
Thank for the help, I appreciate it.
Click to expand...
Click to collapse
Try to look for /proc/dumchar_info file. If it exist, you coud find useful information in it about partitions on device. But it specific to MTK platform. If you don't find it, look for /proc/emmc.
Also look in /proc/cpuinfo for CPU information.
As for ODINand others - i asked about desktop flash tool for Windows, which can be used to flash device via USB cabel. And ROM Manager is Android tool.
lion567 said:
Try to look for /proc/dumchar_info file. If it exist, you coud find useful information in it about partitions on device. But it specific to MTK platform. If you don't find it, look for /proc/emmc.
Also look in /proc/cpuinfo for CPU information.
As for ODINand others - i asked about desktop flash tool for Windows, which can be used to flash device via USB cabel. And ROM Manager is Android tool.
Click to expand...
Click to collapse
Both the files /proc/dumchar_info and /proc/emmc doesn't exists - but here's the contain of /proc/cpuinfo:
Code:
Processor : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 799.53
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 5
Hardware : ZEN Touch 2
Revision : 51030
Serial : 0000000000000000
Using the app "DiskInfo", I believe I've found which partition was /Boot. Here's what I see:
SD Card:
Mount points: /mnt/sdcard, /mnt/secure/asec
Partition name: mmcblk0p1
Total Space: 4.1GB
System:
Mount point: /system (ext4)
Partition Name: mmcblk0p2
Total Space: 128MB (17,8MB free. Is that too low for a normal device usage?)
???: (I assume this is /sdext)
Not mounted;
Partition name: mmcblk0p3
Total space: 1KB
???: (Is this /Boot ? )
Not mounted;
Partition name: mmcblk0p4
Total space: 10,2MB
Data:
Mount point: /data (ext4)
Partition name: mmcblk0p5
Total space: 3GB (2,6GB free)
Cache:
Mount point: /cache (ext4)
Partition name: mmcblk0p6
Total space: 38,7MB (32,3 MB free)
TMPFS MOUNT POINTS:
/dev: Total space: 91,6MB, 12KB used
/mnt/asec: Total space: 91,6MB, 0KB used
/mnt/shm: Total space: 1MB, used: 20KB
/factory: Total space: 128KB, used: 64KB
/mnt/sdcard/.android_secure: Unknow size
***
Using this information, I guess /Boot is mmcblk0p4 ?
GameX2 said:
Both the files /proc/dumchar_info and /proc/emmc doesn't exists - but here's the contain of /proc/cpuinfo:
Code:
Processor : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 799.53
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 5
Hardware : ZEN Touch 2
Revision : 51030
Serial : 0000000000000000
Using the app "DiskInfo", I believe I've found which partition was /Boot. Here's what I see:
SD Card:
Mount points: /mnt/sdcard, /mnt/secure/asec
Partition name: mmcblk0p1
Total Space: 4.1GB
System:
Mount point: /system (ext4)
Partition Name: mmcblk0p2
Total Space: 128MB (17,8MB free. Is that too low for a normal device usage?)
???: (I assume this is /sdext)
Not mounted;
Partition name: mmcblk0p3
Total space: 1KB
???: (Is this /Boot ? )
Not mounted;
Partition name: mmcblk0p4
Total space: 10,2MB
Data:
Mount point: /data (ext4)
Partition name: mmcblk0p5
Total space: 3GB (2,6GB free)
Cache:
Mount point: /cache (ext4)
Partition name: mmcblk0p6
Total space: 38,7MB (32,3 MB free)
TMPFS MOUNT POINTS:
/dev: Total space: 91,6MB, 12KB used
/mnt/asec: Total space: 91,6MB, 0KB used
/mnt/shm: Total space: 1MB, used: 20KB
/factory: Total space: 128KB, used: 64KB
/mnt/sdcard/.android_secure: Unknow size
***
Using this information, I guess /Boot is mmcblk0p4 ?
Click to expand...
Click to collapse
May be yes. Try to dump it and unpack. If you succeded - then you are right.
But there can be different varianrs, some SoC manufactures put all non-mountable partitions, such as preloader, nvram, uboot, boot and recovery, in single partition mmcblk0p0.
It seems, that your device built on Creative's own SoC with non-standart NAND partitioning.
Here you can find info about unpacking
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
or here together with scripts
http://forum.xda-developers.com/showthread.php?t=443994
Hi, can someone who understands root shed us some light here? This tablet runs jelly bean 4.1, and still vulnerable to master key 8219321 bug. Device thread here: http://forum.xda-developers.com/showthread.php?t=2216390
Root is already available but not on latest firmware. I have tried cydia impactor, it works but only until reboot. After reboot, SuperSU or any other superuser app cannot gain root although su binary is already in /system/xbin. I will post necessary files and info if needed.
init.rc:
Spoiler
Code:
# Copyright (C) 2012 The Android Open Source Project
#
# IMPORTANT: Do not create world writable files or directories.
# This is a common source of Android security bugs.
#
import /init.${ro.hardware}.rc
import /init.usb.rc
import /init.trace.rc
on early-init
# Set init and its forked children's oom_adj.
write /proc/1/oom_adj -16
start ueventd
# create mountpoints
mkdir /mnt 0775 root system
# EXTERNAL_STORAGE and SECONDARY_STORAGE are needed for sqlite3 _DELETE_FILE trigger
export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /Removable/MicroSD
export THIRD_STORAGE /Removable/USBdisk1
#export SECONDARY_STORAGE /storage/sdcard1
#export THIRD_STORAGE /storage/udisk
mkdir /storage 0550 system sdcard_r
mkdir /storage/sdcard0 0000 system system
#mkdir /storage/sdcard1 0000 system system
#mkdir /storage/udisk 0000 system system
# for asus storage functions
mkdir /Removable 0775 root system
mount tmpfs tmpfs /Removable mode=0755,gid=1000
mkdir /Removable/MicroSD 0000 system system
mkdir /Removable/USBdisk1 0000 system system
# for backwards compatibility
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
#symlink /storage/sdcard1 /mnt/extsdcard
#symlink /storage/sdcard1 /extsdcard
#symlink /storage/udisk /mnt/udisk
#symlink /storage/udisk /udisk
symlink /Removable/MicroSD /storage/sdcard1
symlink /Removable/MicroSD /mnt/extsdcard
symlink /Removable/MicroSD /extsdcard
symlink /Removable/USBdisk1 /storage/udisk
symlink /Removable/USBdisk1 /mnt/udisk
symlink /Removable/USBdisk1 /udisk
on init
sysclktz 0
loglevel 3
# setup the global environment
export PATH /sbin:/bin:/vendor/bin:/system/sbin:/system/bin:/system/xbin:/usr/bin:/usr/sbin:/busybox/bin:/busybox/sbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib:/system/lib/arm
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework-ext.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
export HOME /
# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d
# Generic Memory Provider
chmod 0666 /dev/gmp
# MALI-400
start flat_mem
insmod /lib/modules/ump.ko ump_debug_level=0 ump_backend=1 ump_memory_size=83886080
insmod /lib/modules/mali.ko mali_debug_level=0 mali_l2_enable=0
# insmod media video driver module
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/g_wmt_vd_com.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/g_wmt_lock.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/mpeg4/g_wmt_vd_mpeg4.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/divx/g_wmt_vd_divx.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/rv/g_wmt_vd_rv.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/mpeg2/g_wmt_vd_mpeg2.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/h264/g_wmt_vd_h264.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/h263/g_wmt_vd_h263.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/jpeg/g_wmt_vd_jdec.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/vc1/g_wmt_vd_vc1.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/vpx/g_wmt_vd_vpx.ko
# insmod media video encoder driver module
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/encode/g_wmt_ve_com.ko
insmod /lib/modules/3.0.8/extra/drivers/media/video/wmt/encode/h264/g_wmt_ve_h264.ko
# insmod v4l2 cmos driver module
insmod /lib/modules/3.0.8/kernel/drivers/media/video/wmt_v4l2/g_wmt_v4l2.ko
insmod /lib/modules/3.0.8/kernel/drivers/media/video/wmt_v4l2/g_wmt_v4l2_cmos.ko
insmod /lib/modules/3.0.8/kernel/drivers/media/video/g_wmt_cmoscam.ko
# insmod cipher driver module
insmod /lib/modules/3.0.8/extra/drivers/crypto/g_crypto.ko
# insmod wmt_env module
insmod /lib/modules/3.0.8/extra/drivers/misc/wmt_env/wmt_env.ko
# insmod tuxera module
insmod /lib/modules/tntfs.ko
insmod /lib/modules/texfat.ko
# Right now vendor lives on the same filesystem as system,
# but someday that may change.
symlink /system/vendor /vendor
# Create cgroup mount point for cpu accounting
mkdir /acct
mount cgroup none /acct cpuacct
mkdir /acct/uid
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /config 0500 root root
# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root
# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root
# Directory-target for where the secure container
# imagefile directory will be bind-mounted
mkdir /mnt/secure/asec 0700 root root
# Secure container public mount points.
mkdir /mnt/asec 0700 root system
mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000
# Filesystem image public mount points.
mkdir /mnt/obb 0700 root system
mount tmpfs tmpfs /mnt/obb mode=0755,gid=1000
write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0
write /proc/sys/kernel/randomize_va_space 2
write /proc/sys/kernel/kptr_restrict 2
write /proc/sys/kernel/dmesg_restrict 1
write /proc/sys/vm/mmap_min_addr 32768
write /proc/sys/kernel/sched_rt_runtime_us 950000
write /proc/sys/kernel/sched_rt_period_us 1000000
# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown system system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0660 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024
write /dev/cpuctl/cpu.rt_runtime_us 950000
write /dev/cpuctl/cpu.rt_period_us 1000000
mkdir /dev/cpuctl/apps
chown system system /dev/cpuctl/apps/tasks
chmod 0666 /dev/cpuctl/apps/tasks
write /dev/cpuctl/apps/cpu.shares 1024
write /dev/cpuctl/apps/cpu.rt_runtime_us 800000
write /dev/cpuctl/apps/cpu.rt_period_us 1000000
mkdir /dev/cpuctl/apps/bg_non_interactive
chown system system /dev/cpuctl/apps/bg_non_interactive/tasks
chmod 0666 /dev/cpuctl/apps/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/apps/bg_non_interactive/cpu.shares 52
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_runtime_us 700000
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_period_us 1000000
# Camera device node
chmod 0666 /dev/video0
chmod 0666 /dev/video1
# Allow everybody to read the xt_qtaguid resource tracking misc dev.
# This is needed by any process that uses socket tagging.
chmod 0644 /dev/xt_qtaguid
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
# mount yaffs2 [email protected] /system
# mount yaffs2 [email protected] /system rw remount
# #mount yaffs2 [email protected] /data nosuid nodev
# mount yaffs2 [email protected] /cache nosuid nodev
# emmc support
#wait /dev/block/mmcblk1p1
#wait /dev/block/mmcblk1p5
#wait /dev/block/mmcblk1p13
#mount ext4 /dev/block/mmcblk1p1 /system
#mount ext4 /dev/block/mmcblk1p5 /cache nosuid nodev
#mount ext4 /dev/block/mmcblk1p13 /data nosuid nodev
# setprop ro.crypto.fuse_sdcard true
on post-fs
# once everything is setup, no need to modify /
mount rootfs rootfs / ro remount
# We chown/chmod /cache again so because mount is run as root + defaults
chown system cache /cache
chmod 0770 /cache
# This may have been created by the recovery system with odd permissions
chown system cache /cache/recovery
chmod 0770 /cache/recovery
#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo
#change permissions on kmsg & sysrq-trigger so bugreports can grab kthread stacks
chown root system /proc/kmsg
chmod 0440 /proc/kmsg
chown root system /proc/sysrq-trigger
chmod 0220 /proc/sysrq-trigger
# create the lost+found directories, so as to enforce our permissions
mkdir /cache/lost+found 0770 root root
on post-fs-data
# We chown/chmod /data again so because mount is run as root + defaults
chown system system /data
chmod 0771 /data
# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.
mkdir /data/dontpanic 0750 root log
# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console
copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads
write /proc/apanic_console 1
# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/keychain 0771 system system
mkdir /data/misc/vpn 0770 system vpn
mkdir /data/misc/systemkeys 0700 system system
# give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
mkdir /data/local 0751 root root
chmod 0755 /system/etc/wmt/sdio_wifi_pwron.sh
chmod 0755 /system/etc/wmt/sdio_wifi_pwroff.sh
chown root system /system/etc/cpu1.sh
chown root system /system/etc/cpu2.sh
chown root system /system/etc/cpu3.sh
chmod 0775 /system/etc/cpu1.sh
chmod 0775 /system/etc/cpu2.sh
chmod 0775 /system/etc/cpu3.sh
# For security reasons, /data/local/tmp should always be empty.
# Do not place files or directories in /data/local/tmp
# give system access to rfkill for bluetooth
chmod 0666 /sys/class/rfkill/rfkill0/state
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app-asec 0700 root root
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/ssh 0750 root shell
mkdir /data/ssh/empty 0700 root root
# create dalvik-cache, so as to enforce our permissions
mkdir /data/dalvik-cache 0771 system system
# create resource-cache and double-check the perms
mkdir /data/resource-cache 0771 system system
chown system system /data/resource-cache
chmod 0771 /data/resource-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770 root root
# create directory for DRM plug-ins - give drm the read/write access to
# the following directory.
mkdir /data/drm 0770 drm drm
mknod /dev/cipher c 238 0
# we will remap this as /storage/sdcard0 with the sdcard fuse tool
mkdir /data/media 0770 media_rw media_rw
chown media_rw media_rw /data/media
chmod 0666 /dev/wmtts
chmod 0666 /dev/wmtgpio
chmod 0666 /dev/mtd/mtd0
chmod 0666 /dev/graphics/fb0
chmod 0666 /dev/fb0
chmod 0666 /dev/graphics/fb1
chmod 0666 /dev/fb1
chmod 0666 /dev/mbdev
chmod 0666 /dev/ump
chmod 0666 /dev/mali
chmod 0666 /system/etc/wmt/pm.sh
chmod 0755 /sys/mmc0/state
chmod 0666 /dev/wmt-lock
chmod 0666 /dev/wmt-vd
chmod 0666 /dev/jdec
chmod 0666 /dev/mpeg2
chmod 0666 /dev/mpeg4
chmod 0666 /dev/divx
chmod 0666 /dev/h264
chmod 0666 /dev/rv
chmod 0666 /dev/vc1
chmod 0666 /dev/h263
chmod 0666 /dev/vpx
chmod 0666 /dev/h264enc
# If there is no fs-post-data action in the init..rc file, you
# must uncomment this line, otherwise encrypted filesystems
# won't work.
# Set indication (checked by vold) that we have finished this action
setprop vold.post_fs_data_done 1
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40
# support ALSA
setprop alsa.mixer.playback.master Master
setprop alsa.mixer.capture.master Capture
setprop alsa.mixer.playback.earpiece Master
setprop alsa.mixer.capture.earpiece Capture
setprop alsa.mixer.playback.headset Master
setprop alsa.mixer.playback.speaker Master
symlink /dev/snd/pcmC0D0c /dev/pcmC0D0c
symlink /dev/snd/pcmC0D0p /dev/pcmC0D0p
symlink /dev/snd/controlC0 /dev/controlC0
symlink /dev/snd/timer /dev/timer
chmod 0666 /dev/pcmC0D0c
chmod 0666 /dev/pcmC0D0p
chmod 0666 /dev/controlC0
chmod 0666 /dev/timer
chown root audio /dev/snd/controlC0
chown root audio /dev/snd/pcmC0D0c
chown root audio /dev/snd/pcmC0D0p
chown root audio /dev/snd/timer
# Memory management. Basic kernel parameters, and allow the high
# level system server to be able to adjust the kernel OOM driver
# parameters to match how it is managing things.
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
chown root system /sys/module/lowmemorykiller/parameters/adj
chmod 0664 /sys/module/lowmemorykiller/parameters/adj
chown root system /sys/module/lowmemorykiller/parameters/minfree
chmod 0664 /sys/module/lowmemorykiller/parameters/minfree
# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5
# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown system system /sys/power/state
chown system system /sys/power/wakeup_count
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
chown system system /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chown system system /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chown system system /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chown system system /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chown system system /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chown system system /sys/devices/system/cpu/cpufreq/interactive/boost
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/boost
chown system system /sys/devices/system/cpu/cpufreq/interactive/boostpulse
chown system system /sys/devices/system/cpu/cpufreq/interactive/input_boost
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/input_boost
# Assume SMP uses shared cpufreq policy for all CPUs
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 0660 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
chown root radio /proc/cmdline
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.wifi 524288,1048576,2097152,262144,524288,1048576
setprop net.tcp.buffersize.lte 524288,1048576,2097152,262144,524288,1048576
setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.hspa 4094,87380,262144,4096,16384,262144
setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
# Set this property so surfaceflinger is not started by system_init
setprop system_init.startsurfaceflinger 0
class_start core
class_start main
# create virtual SD card at /storage/sdcard0, based on the /data/media directory
# daemon will drop to user/group system/media_rw after initializing
# underlying files in /data/media will be created with user and group media_rw (1023)
service sdcard /system/bin/sdcard /data/media 1023 1023
class late_start
on nonencrypted
class_start late_start
service batteryserver /charger
class charger
on charger
class_start charger
on property:vold.decrypt=trigger_reset_main
class_reset main
on property:vold.decrypt=trigger_load_persist_props
load_persist_props
on property:vold.decrypt=trigger_post_fs_data
trigger post-fs-data
on property:vold.decrypt=trigger_restart_min_framework
class_start main
on property:vold.decrypt=trigger_restart_framework
class_start main
class_start late_start
on property:vold.decrypt=trigger_shutdown_framework
class_reset late_start
class_reset main
## Daemon processes to be run by init.
##
service ueventd /sbin/ueventd
class core
critical
##service console /system/bin/sh
#service console /bin/sh
# class core
# console
# disabled
## user shell
# group log
on property:ro.debuggable=1
start console
on property:ro.debuggable=0
start console
service getserialno /sbin/getserialno
class core
oneshot
# adbd is controlled via property triggers in init..usb.rc
service adbd /sbin/adbd
class core
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
service servicemanager /system/bin/servicemanager
class core
user system
group system
critical
onrestart restart zygote
onrestart restart media
onrestart restart surfaceflinger
onrestart restart drm
service vold /system/bin/vold
class core
socket vold stream 0660 root mount
ioprio be 2
service netd /system/bin/netd
class main
socket netd stream 0660 root system
socket dnsproxyd stream 0660 root inet
socket mdns stream 0660 root system
service debuggerd /system/bin/debuggerd
class main
#service ril-daemon /system/bin/rild
# class main
# socket rild stream 660 root radio
# socket rild-debug stream 660 radio system
# user root
# group radio cache inet misc audio sdcard_r sdcard_rw log
service surfaceflinger /system/bin/surfaceflinger
class main
user system
group graphics
onrestart restart zygote
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
class main
socket zygote stream 660 root system
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
onrestart restart netd
service drm /system/bin/drmserver
class main
user drm
group drm system inet drmrpc sdcard_r
service media /system/bin/mediaserver
class main
user media
group audio camera inet net_bt net_bt_admin net_bw_acct drmrpc
ioprio rt 4
service bootanim /system/bin/bootanimation
class main
user graphics
group graphics
disabled
oneshot
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL
class main
disabled
oneshot
service set_static_ip /system/bin/sh /system/etc/wmt/script/run_staticip.sh
class main
disabled
oneshot
#add to set IP, netmask
service set_ip_info /system/bin/sh /system/etc/wmt/script/set_ip_info.sh
class main
disabled
oneshot
service dhcpcd_eth1 /system/bin/dhcpcd -ABKL eth1
class main
oneshot
service wmt_vt1609 /system/bin/sh /system/etc/wmt/script/init_vt1609dual.sh
class main
oneshot
service poweroff /system/bin/sh /system/etc/wmt/poweroff.sh
class main
disabled
group system
oneshot
service dbus /system/bin/dbus-daemon --system --nofork
class main
socket dbus stream 660 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin
service bluetoothd /system/bin/bluetoothd -n
class main
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service installd /system/bin/installd
class main
socket installd stream 600 system system
service flash_recovery /system/etc/install-recovery.sh
class main
oneshot
service racoon /system/bin/racoon
class main
socket racoon stream 600 system system
# IKE uses UDP port 500. Racoon will setuid to vpn after binding the port.
group vpn net_admin inet
disabled
oneshot
service mtpd /system/bin/mtpd
class main
socket mtpd stream 600 system system
user vpn
group vpn net_admin inet net_raw
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
class main
user keystore
group keystore drmrpc
socket keystore stream 666
service dumpstate /system/bin/dumpstate -s
class main
socket dumpstate stream 0660 shell log
disabled
oneshot
service sshd /system/bin/start-ssh
class main
disabled
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
service initrdscript /system/etc/rc.d/rcS.d/S06speedup
class main
oneshot
service myserver-daemon /system/bin/asuskeystore
class main
socket asuskeystore stream 0666 root system
# import PC2TV script
import /system/etc/wmtnd/wmtnd.rc
Thanks! Any help would be appreciated
What firmware version are talking about?
Because I thought I had the latest firmware (asus-ME172V-US_user_4.5.4.41647906_20140110) and I have root through the rooting instructions on the memo pad thread. FYI mine is a 32gig version.
pueblo01 said:
What firmware version are talking about?
Because I thought I had the latest firmware (asus-ME172V-US_user_4.5.4.41647906_20140110) and I have root through the rooting instructions on the memo pad thread. FYI mine is a 32gig version.
Click to expand...
Click to collapse
What? Asus released an update on 2014? Mine is still on 20130910. 8gig version. Are you in the US?
Well I'm quoting this guy:
crazykiddo said:
yes the root would work but it uses an old kernel so
- there might be issues because of that.
- updates for related to the kernel will not be there.
so you will be using updated OS but with "old" kernel and bootloader.
FYI
Click to expand...
Click to collapse
So I'm looking for some guy who could find a new method for newer firmware (asus-ME172V-WW_user_4.5.4.31116393_20130910 in my case, I think WW stands for worldwide) or maybe update the root utility.
Anyway here is the link for recovery: http://forum.xda-developers.com/showthread.php?p=42080337
and root utility: http://forum.xda-developers.com/showpost.php?p=42047570&postcount=261
if someone would take a look at that
Yes I'm in the US I wish I could say I'm a coder but I am not. I am struggling through documentation just to try and update to the newest clockworkmod recovery. I hope someone can help with the rooting issue.