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
Guyz i am not a noob,but this is really like a noob question... please help me...
I started using a Ext. partition's just one month after i purchased my phone on my free 2GB memory card which cum along with MINI....and there were no prob. using it though.Then i purchased 4GB SD card and again i applied Ext. 3 partition on it and used app2sd.dc2sd....and it ran over 8 months without a prob.
Then i Used MINI-CM 6.0-RC1 and deleted my ext.3 partition to make it larger than it previous condition,watever when i created it and again and when i unmounted my SD my phone said "The SD card Is Empty or Corrupt"....and thats it....it prompts me to formate it....So i did so....but when i plug the phone to USB and connected the phone to computer....it again refreshed it to 4GB and my ext. partition gone for hell.
I thought that it worths another chance so i again created ext. partition in xRecovery Mode.....And i sum how got success.....But when i tries to install App2sd.dc2sd it says
"E:Can't chown/mod /system/etc/bluez
(No such file or directory)
E:Failure at Line 7:
set_perm_recursive 1002 1002 0755 0440 ,SYSTEM:etc/bluez
installation Aborted"
I tried many times to solve it,even every method but no results.....i think my card got corrupted,but it shows and runs other media files...I am so confused....
Please Help Me Guyz!!!!
this >> set_perm_recursive 1002 1002 0755 0440 ,SYSTEM:etc/bluez should look like this set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluez
and if that doesn't do trick check is folder bluez exist.
Chumby_666 said:
this >> set_perm_recursive 1002 1002 0755 0440 ,SYSTEM:etc/bluez should look like this set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluez
and if that doesn't do trick check is folder bluez exist.
Click to expand...
Click to collapse
Yeahh bro. there is a folder at /system /lib/bluez-plugin ........And it got two files "audio.so and "input.so"".So Basically what i have to do with this....pls explain....!!!
pratyush_gamer said:
Yeahh bro. there is a folder at /system /lib/bluez-plugin ........And it got two files "audio.so and "input.so"".So Basically what i have to do with this....pls explain....!!!
Click to expand...
Click to collapse
edit META-INF/...../update-script and fix this line set_perm_recursive 1002 1002 0755 0440 ,SYSTEM:etc/bluez. you can open update-script with notepad++
Chumby_666 said:
edit META-INF/...../update-script and fix this line set_perm_recursive 1002 1002 0755 0440 ,SYSTEM:etc/bluez. you can open update-script with notepad++
Click to expand...
Click to collapse
Thanks for concentrating on my problem(Thats so kind of you).....But bro. i just solved it before reading your post........I used SEUS and go back to original FW and from there i created my partitions again.....And WOW now i can able to use Ap2SD.Dc2SD.........BTW thanks for all your efforts......And also i am a Big FAN of you & your works(ROM)...I really Appreciate your work.
THANKS!!!!
I am a newbye and don't have right to post into http://forum.xda-developers.com/showthread.php?t=1136699
I want to delete logo.jpg into /dev/block/stl6 and I am unable to delete it...
Here what I did:
Code:
[alpha] adb shell
$ su
# mount -o remount,rw /dev/block/stl6 /mnt/.lfs
# cd /mnt/.lfs
# cp /mnt/sdcard/logo.jpg /mnt/.lfs/logo.jpg
cp: can't create '/mnt/.lfs/logo.jpg': File exists
# cp /mnt/sdcard/logo.jpg /mnt/.lfs/logo0.jpg
# ls -l logo0.jpg
-rwxrwxrwx 1 root root 75573 Jan 1 1970 /mnt/.lfs/logo0.jpg
# cp logo0.jpg logo.jpg
cp: can't create 'logo.jpg': File exists
# cp -f logo0.jpg logo.jpg
cp: can't create 'logo.jpg': File exists
# rm logo.jpg
rm: can't remove 'logo.jpg': Operation not permitted
# rm -f logo.jpg
rm: can't remove 'logo.jpg': Operation not permitted
# cp /mnt/sdcard/logo.jpg /mnt/.lfs/logo1.jpg
# ls -l /mnt/.lfs/logo1.jpg
-rwxrwxrwx 1 root root 75573 Oct 26 22:14 /mnt/.lfs/logo1.jpg
# rm logo1.jpg
rm: can't remove 'logo1.jpg': Operation not permitted
# exit
$ exit
[alpha] echo "what's the **** ?"
what's the **** ?
[alpha] adb shell
$ su
# mount -o remount,rw /dev/block/stl6 /mnt/.lfs
# cd /mnt/.lfs
# chattr -i logo.jpg
chattr: reading flags on logo.jpg: Not a typewriter
# rm logo.jpg
rm: can't remove 'logo.jpg': Operation not permitted
# exit
$ exit
[alpha] echo "what's the **** ???"
what's the **** ???
Any help would be appreciated.
That file system is not well supported as such we don't currently have the ability to replace or modify any existing files. Only create new ones.
If you did the all steps in that thread you would end up with a empty partition so that you can create the logo.jpg. If you want to change the logo later you have to re-flash the empty partition again.
shadowofdarkness said:
That file system is not well supported as such we don't currently have the ability to replace or modify any existing files. Only create new ones.
If you did the all steps in that thread you would end up with a empty partition so that you can create the logo.jpg. If you want to change the logo later you have to re-flash the empty partition again.
Click to expand...
Click to collapse
So strange to read that: now I know and I thank you for information.
I will read the tuto but I think about about some adb commands...
As I found:
- in /init.rc "mount j4fs /dev/block/mmcblk0p4 /mnt/.lfs"
- in /sbin/ "mke2fs mkfifo mkfs.ext2 mknod mkswap mktemp mkyaffs2image "
- in /system/xbin/ "mkdosfs mke2fs mkfifo mkfs.ext2 mkfs.minix mkfs.reiser mkfs.vfat mknod mkpasswd mkswap mktemp"
- /sbin/parted
I wondering if it is possible to :
case A.
- umount /dev/block/mmcblk0p4
- mkfs.ext2 /dev/block/mmcblk0p4
- modify /init.rc to have "mount ext2 /dev/block/mmcblk0p4 /mnt/.lfs" in a way I have to find out : maybe a 'sed -i "s/mount j4fs \/dev\/block\/mmcblk0p4/mount ext2 \/dev\/block\/mmcblk0p4/"' into the image I have to reflash?
- a backup could be 'dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096'
- and do what I want without the overwritting problem on /mnt/.lfs?
case B.
- umount /dev/block/mmcblk0p4
- do a "dd if=/dev/null of=/dev/block/mmcblk0p4 bs=4096 count=2048" as param.lfs size is 8388608
- mount j4fs -w /dev/block/mmcblk0p4 /mnt/.lfs
- copy what I backuped with the good logo.jpg
- and have the good logo.jpg on this nasty j4fs filesystem
Maybe a C case could be to use gparted ?
As it is my first step as an android newbye, any advice would be appreciated...
I have been tryying to get the Nabi 2 to mount micro sd card/sdcard2 as internal storage/sdcard. I have altered the vold file on AN7G3 Arnova 7" tablet so as to have 32 gig internal instead of 4 gig, works really well. Also know many have done this for other devices and works on GB 3.2 and ICS 4.03. Nabi2 has ICS 4.0.3 but can not get them to switch. when i change sdcard and sdcard2 and reboot, device can not reconize micro sdcard/sdcard2 and openning settings/storage on the device cause the storage to force close. ES File Exployer does not reconize sdcard2. Is there a way to achieve this with the vold file or does this have to be done thru adb. If adb could someone help me with the commands. This device IS rooted and Google Play installed. I will include a copy of the vold.fstab as a vold.txt. TIA as several folks need this info and i will relay your info or you can on the Nabi 2 thread.
i don`t see the internal storage defined in the vold.fstab
can you put the output from mount ?
globula_neagra said:
i don`t see the internal storage defined in the vold.fstab
can you put the output from mount ?
Click to expand...
Click to collapse
Not really sure what you want. The internal storage is named sdcard and micro sdcard is named sdcard2. In settings/storage they are listed as internal storage and sdcard. Es File explorer sees them as sdcard and sdcard2. If I know what you need, I will get it for you.Need
dev_mount sdcard /mnt/sdcard2 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2 (this is the external sd card)
dev_mount usbdrive /mnt/usbdrive auto /devices/platform/tegra-ehci.0/usb2 (this is the host where you can connect a mouse, etc.)
this what apears in your vold.fstab
so, the line for the internal storage is missing
on my tablet it looks like this
dev_mount sdcard /mnt/sdcard 20 /devices/platform/msm_sdcc.2/mmc_host (internal storage)
dev_mount sdcard1 /mnt/external_sd auto /devices/platform/msm_sdcc.4/mmc_host (external sd)
dev_mount udisk /mnt/udisk auto /devices/platform/msm_hsusb_host.0/usb1 (host for mouse, keyboards, etc)
This is the "mount" in adb shell
C:\Android\android-sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
sh-3.2# su
su
sh-3.2# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,d
ata=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,
data=ordered 0 0
/dev/block/mmcblk0p17 /content ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/vold/179:97 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
sh-3.2#
I agree, this vold is different from what I have delt with in my limited experience. Here is a screen shot of mount on terminal emulator. Does this give you the info that you requested.
well, in the mount the internal storage it appears, is strange that it does not appear in the vold.fstab
i think the internal storage is triggered by the boot.img, or a .rc from the /etc
you could have a look on a nexus tablet, or acer iconia110 to see how is defined there the internal storage in vold.fstab. (since all are having tegra 3, you should have a corect image)
globula_neagra said:
well, in the mount the internal storage it appears, is strange that it does not appear in the vold.fstab
i think the internal storage is triggered by the boot.img, or a .rc from the /etc
you could have a look on a nexus tablet, or acer iconia110 to see how is defined there the internal storage in vold.fstab. (since all are having tegra 3, you should have a corect image)
Click to expand...
Click to collapse
That's a good thought as Nabi2 is very close to the nexus 7 . Will try and run those down. Thanks
I have just spent the last 2 hours attempting to mod the Vold file in like 4-5 different ways and nothing worked I took the moded Vold file off my LG Esteem Smart phone which has a moded Vold file that makes my extsdcard the Internal Memory and studied it to find there is only like 2 sets of 2 words and numbers that are switched from one line of code to another and THATS IT!! The rest of the code is letter for letter number for number the same!... So I tried applying the same technique to my Nabi 2's Vold file and no matter what it just makes the extsdcard (sdcard2) appear not there anymore and has the following message in the storage status tab.. "Insert an SD card for mounting" Someone's gotta tackle this!!
It was suggested that I/we as clarkiss run an su file with script manager and alter the vold. We did this and still force close when openning settings/storage. Used original vold and ran script, when opened settings/storage, I see my micro sdcard listed as internal storage and sdcard2. Es File explorer sees micro sdcard as sdcard and sdcard2, nothing sees the internal storage but any programs or games still install to the unseen internal storage.
Anyone have any idea on this? I have included the sdcard_switch.su that we ran with script manager, in hope that with the vold posted above someone might have an idea to help us. There are quite a few folks looking for this and will be more as they by these for christmas.
Thanks.
I figured I would post the original Vold.fstab to see if anyone has any ideas or suggestions... If you need me to post anymore files let me know and I will quickly get posted!! The below code is the entire contents of the Vold.fstab... I also have included a link to download (Hosted by my Box account) the Vold.fstab file at the bottom of this post after the code as well incase anyone wanted to help us play with it :silly: Help with this on any level is more then welcome!!
Contents of Vold.fstab file (Code)
## Vold 2.0 fstab for kai
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard2 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2
dev_mount usbdrive /mnt/usbdrive auto /devices/platform/tegra-ehci.0/usb2
https://www.box.com/s/2az7hod00g9fbenn3j14
If anyone has a vold.fstab from a nexus tablet, or acer iconia110 tablet that they could share. I would like to see them to compare with the nabi 2.
as i said, on you guys, the vold does not trigger the internal storage (have a look here on this lines )
/dev/block/vold/179:97 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow _utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharse
As you can see this line: /dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime, is the internal storage, on your vold, this line is missing
therefore you should start and search when the internal storage is mounted
the line that defines the internal storage is
dev/fuse mnt/sdcard
you should look maybe in the boot.img ?
it should look like this
dev_fuse sdcard /mnt/sdcard fuse
---------- Post added at 02:02 PM ---------- Previous post was at 01:58 PM ----------
this is the vold from HTC one x, tegra version.
## Vold 2.0 fstab for endeavor
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1
dev_mount sdcard /mnt/sdcard 14 /devices/platform/sdhci-tegra.3/mmc_host/mmc0
As you can see the internal storage is trigered by the vold.
globula_neagra said:
as i said, on you guys, the vold does not trigger the internal storage you should look maybe in the boot.img ?
Click to expand...
Click to collapse
Sounds good...How do I look in the boot.img? Is there a program or something of that sort to use? Could you give me a quick guide on the steps to take to look in the boot.img?
globula_neagra said:
as i said, on you guys,
it should look
As you can see the internal storage is trigered by the vold.
Click to expand...
Click to collapse
I also don't know where to start. Sorry to be so lost but really don't know what to do from here. Any help pointing us to what we need to do would be great. We are learning and follow direction. I have looked for the info but no luck.
We are noob's but trying. Lol
Located the boot.img
I think I located the boot.img... After reading and jumping from link to link forum to forum I came across "bootanimation.zip" in /system/media. Im going to unpack it and study it via HowTo: Unpack/Edit/Repack Boot Images website
---------- Post added at 07:23 PM ---------- Previous post was at 07:17 PM ----------
Clarkiss said:
I think I located the boot.img... After reading and jumping from link to link forum to forum I came across "bootanimation.zip" in /system/media. Im going to unpack it and study it via HowTo: Unpack/Edit/Repack Boot Images website
Click to expand...
Click to collapse
Scratch that lol its just the god damn boot animation in the beganning damn it!!!!!:crying:
Clarkiss said:
I think I located the boot.img... After reading and jumping from link to link forum to forum I came across "bootanimation.zip" in /system/media. Im going to unpack it and study it via HowTo: Unpack/Edit/Repack Boot Images website
---------- Post added at 07:23 PM ---------- Previous post was at 07:17 PM ----------
Scratch that lol its just the god damn boot animation in the beganning damn it!!!!!:crying:
Click to expand...
Click to collapse
You know, jmztaylor has img files at
http://androidfiles.org/uploads/?dir=Nabi2
I just don't know how to unpack it?
ALD3 said:
You know, jmztaylor has img files at
http://androidfiles.org/uploads/?dir=Nabi2
I just don't know how to unpack it?
Click to expand...
Click to collapse
Ok im starting to get deeper and deeper into this lol I have unpacked the ROM we are running on which of course is from jmz with Android Kitchen/Cygwin and I am looking at Working Folder Information in the Kitchen and I see something I kinda dont like... Of course there is like 10-15 lines of information like Android OS version: 4.0.4 and ROM Name: JmzStockNabi and so on but this is what is bothering me... One of the lines reads as follows.. Apps2SD <Apps to EXT> enabled: NO .... I wonder what would happen if that were changed? anyone have any suggestions?
stripped Nabi 2 ROM
After extracting the BOOT.img and opening the "BOOT- EXTRACTED" folder it created I found another folder in that folder called "boot.img-ramdisk" and inside it was the following:
[folder called] data
[folder called] dev
[folder called] proc
[folder called] sbin
[folder called] sys
[folder called] system
[PROP file called] default.prop
[file called] init
[RC file called] init.goldfish.rc
[RC file called] init.mt799.rc
[RC file called] init.nv_dev_board.usb.rc
[RC file called] init.rc
[RC file called] init.tf.rc
[RC file called] ueventd.goldfish.rc
[RC file called] ueventd.mt799.rc
[RC file called] ueventd.rc
I started studying all the files and the one that looked most interesting to me and what im trying to do is the "init.mt799.rc" file!:laugh: It seemed to reference quite often the sdcard, sdcard2, and external storage so that got me a little happy haha! Seems like I might be starting to get to the bottom of this riddle :fingers-crossed: So I copied and pasted the entire contents of the "init.mt799.rc" file code below to see what you guys think! And if you guys want me to post/attach any one of those other files let me know which and I will immediately
"init.mt799.rc" file contents
#Copyright (c) 2012, NVIDIA CORPORATION. All rights reserved.
import init.nv_dev_board.usb.rc
on early-init
mount debugfs debugfs /sys/kernel/debug
# for backwards compatibility
export EXTERNAL_STORAGE /mnt/sdcard
export EXTERNAL_STORAGE2 /mnt/sdcard2
mkdir /mnt/sdcard 0000 system system
symlink /mnt/sdcard /sdcard
mkdir /forever 0644 system system
mkdir /sct 0644 system system
mkdir /mnt/sdcard2 0000 system system
# create directory for mounting usb drives
mkdir /mnt/usbdrive 0666 system system
symlink /mnt/usbdrive /usbdrive
on fs
# Mount system to allow checkpoint and set NVSI symlink
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system rw
# Create NVSI filter symlink
symlink /data/data/com.nvidia.NvCPLSvc/files/com.nvidia.nvsiutilv1.xml /system/etc/permissions/com.nvidia.nvsiutilv1.xml
# Remount system read-only
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system wait ro remount
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
setprop ro.crypto.umount_sd false
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA /data wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc,errors=panic
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC /cache wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc,errors=panic
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDD /forever wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc,
#mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/SCT /sct wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc
on post-fs-data
mkdir /data/addon_res 0770 system system
mkdir /sct 0644 system system
mkdir /data/misc/wifi 0770 wifi wifi
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
mkdir /data/nvcam 0700 media camera
chown dhcp dhcp /data/misc/dhcp
chown wifi wifi /data/misc/wifi
chown wifi wifi /data/misc/wifi/wpa_supplicant.conf
chown wifi wifi /data/misc/wifi/hostapd.conf
mkdir /data/misc/wminput 0776 system system
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0775 media_rw media_rw
chown media_rw media_rw /data/media
# Set indication (checked by vold) that we have finished this action
setprop vold.post_fs_data_done 1
chown system system /forever
mkdir /forever/misc 0774 system system
mkdir /forever/misc/dmt 0777 system system
chown system system /sys/class/accelemeter/dmard06/enable_acc
chown system system /sys/class/accelemeter/dmard06/delay_acc
on boot
#reboot_flag
chmod 0666 /dev/block/platform/sdhci-tegra.3/by-name/UDE
# bluetooth
# bluetooth MAC address programming
chown bluetooth bluetooth ro.bt.bdaddr_path
chown bluetooth bluetooth /system/etc/bluetooth
#setprop ro.bt.bdaddr_path "/system/etc/bluetooth/bdaddr"
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
# bluetooth
# bluetooth MAC address programming
chmod 0660 /sys/class/rfkill/rfkill0/state
chmod 0660 /sys/class/rfkill/rfkill0/type
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
# NFC
#setprop ro.nfc.port "I2C"
# backlight
chown system system /sys/class/backlight/pwm-backlight/brightness
# didim
chown system system /sys/class/graphics/fb0/device/smartdimmer/enable
chown system system /sys/class/graphics/fb0/device/smartdimmer/aggressiveness
# power
chown system system /sys/kernel/tegra_cap/core_cap_level
chown system system /sys/kernel/tegra_cap/core_cap_state
chown system system /sys/module/cpu_tegra/parameters/cpu_user_cap
# Power management settings
write /sys/module/cpu_tegra3/parameters/no_lp 0
#write /sys/module/tegra3_emc/parameters/emc_enable 0
#write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 1000000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpufreq/conservative/up_threshold 95
write /sys/devices/system/cpu/cpufreq/conservative/down_threshold 75
write /sys/devices/system/cpu/cpufreq/conservative/freq_step 3
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpufreq/interactive/boost_factor 2
write /sys/devices/system/cpu/cpufreq/interactive/sustain_load 80
write /sys/module/cpu_tegra3/parameters/auto_hotplug 1
#write /sys/module/cpuidle_t3/parameters/lp2_0_in_idle 0
write /sys/module/cpuidle/parameters/lp2_in_idle 1
chown system system /sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load
chown system system /sys/devices/system/cpu/cpufreq/interactive/max_boost
# Default Read Ahead value for sdcards
write /sys/block/mmcblk0/queue/read_ahead_kb 2048
write /sys/block/mmcblk1/queue/read_ahead_kb 2048
# Wiimote connect status
write /data/misc/wminput/connected 0
chmod 0666 /data/misc/wminput/connected
# GPS init
#write /sys/class/gpio/export 162
#write /sys/class/gpio/gpio162/value 0
#write /sys/class/gpio/gpio162/direction out
#chown root system /sys/class/gpio/gpio162/value
#chmod 0664 /sys/class/gpio/gpio162/value
#write /sys/class/gpio/export 163
#write /sys/class/gpio/gpio163/direction out
#write /sys/class/gpio/gpio163/value 1
#chown root system /sys/class/gpio/gpio163/value
#chmod 0664 /sys/class/gpio/gpio163/value
# Load WiFi driver
insmod /system/lib/modules/bcmdhd.ko
# BB mapping symbolic name to the logging ttyACM port
symlink /dev/ttyACM2 /dev/log_modem
on property:ro.debuggable=1
# EMC debug interface
chmod 666 /sys/kernel/debug/tegra_emc/eack_state
service wpa_supplicant /system/bin/wpa_supplicant \
-Dnl80211 -puse_p2p_group_interface=1 -e/data/misc/wifi/entropy.bin -dd
# we will start as root and wpa_supplicant will switch to user wifi
# after setting up the capabilities required for WEXT
# user wifi
# group wifi inet keystore
class main
socket wpa_wlan0 dgram 660 wifi wifi
disabled
oneshot
#TI-ST
service uim /system/bin/uim-sysfs
class core
user root
group root
oneshot
service dhcpcd_wlan0 /system/bin/dhcpcd -ABKL
class main
disabled
oneshot
service dhcpcd_p2p /system/bin/dhcpcd -aABKL
class main
disabled
oneshot
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL -f/system/etc/dhcpcd/dhcpcd.conf
class main
disabled
oneshot
service dhcpcd_bnep0 /system/bin/dhcpcd -ABKL
class main
disabled
oneshot
service iprenew_wlan0 /system/bin/dhcpcd -n
class main
disabled
oneshot
service iprenew_p2p /system/bin/dhcpcd -n
class main
disabled
oneshot
service iprenew_eth0 /system/bin/dhcpcd -n
class main
disabled
oneshot
# create virtual SD card at /mnt/sdcard, based on the /data/media directory
# deamon will drop to user/group system/media_rw after initializing
# underlying files in /data/media wil be created with user and group media_rw (1023)
service sdcard /system/bin/sdcard /data/media 1023 1023
class late_start
# bugreport is triggered by the VOLUME-DOWN and VOLUME-UP keys
service bugreport /system/bin/dumpstate -d -v -o /data/storage/bugreports/bugreport
class main
disabled
oneshot
keycodes 115 114
#BCM
service hciattach /system/bin/brcm_patchram_plus --enable_hci --scopcm=0,2,0,0,0,0,0,0,0,0 \
--baudrate 3000000 --patchramdir /etc/firmware --enable_lpm --tosleep=5000 --create_bdaddr /dev/ttyHS2
user bluetooth
group bluetooth net_bt_admin
disabled
# Mount usb drives as /usbdrive. Generally usb drives are formatted with FAT
# filesystem, so we support FAT as of now.
on device-added-/sys/block/sda
mount vfat /dev/block/sda /mnt/usbdrive
on device-removed-/sys/block/sda
umount /mnt/usbdrive
# Prepare TF service
import init.tf.rc
# Enable NvCpuD, and set it to never poll config again
on boot
setprop nvcpud.enabled true
setprop nvcpud.config_refresh_ms -1
service nvcpud /system/bin/nvcpud
class main
user root
group root
#Raydium touch setting
#service rm_ts_service /system/bin/rm_ts_server
# class main
#Synaptics touch, allow low power mode
#on boot
# write /sys/devices/sensor00/fn01/nosleep 0
# create filesystems if necessary
service setup_fs /system/bin/setup_fs \
/dev/block/platform/sdhci-tegra.3/by-name/UDA \
/dev/block/platform/sdhci-tegra.3/by-name/CAC \
/dev/block/platform/sdhci-tegra.3/by-name/UDD
class core
user root
group root
oneshot
service pm_service_check /system/bin/pm_service check
class core
user root
group root
oneshot
service pm_service_clear /system/bin/pm_service clear
user root
group root
disabled
oneshot
on property:sys.kh.addon.mount=true
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDB /data/addon_res wait rw ,data=writeback,nodelalloc
chown system system /data/addon_res
setprop sys.kh.addon.mount_state true
i will have a look on this for you.
you will need dxixda kitchen to unpack the system.img and boot/recovery.img
if someone can tell which is exactly the boot.img and the system.img from here http://androidfiles.org/uploads/?dir=Nabi2
http://androidfiles.org/uploads/?dir=Nabi2/stockimages
what mmblock is the system and boot.
---------- Post added at 12:27 PM ---------- Previous post was at 12:09 PM ----------
till now i noticed the fallowing values
# Default Read Ahead value for sdcards
write /sys/block/mmcblk0/queue/read_ahead_kb 2048
write /sys/block/mmcblk1/queue/read_ahead_kb 2048
# for backwards compatibility
export EXTERNAL_STORAGE /mnt/sdcard
export EXTERNAL_STORAGE2 /mnt/sdcard2
mkdir /mnt/sdcard 0000 system system
symlink /mnt/sdcard /sdcard
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0775 media_rw media_rw
chown media_rw media_rw /data/media
globula_neagra said:
i will have a look on this for you.
you will need dxixda kitchen to unpack the system.img and boot/recovery.img
if someone can tell which is exactly the boot.img and the system.img from here http://androidfiles.org/uploads/?dir=Nabi2
Click to expand...
Click to collapse
The boot.img (and the system.img i think) is in the jmzrootpackage.zip. Because anyone trying to do what we are would have that boot.img flashed or at least thats the one I have because I used that files contents to gain root access and it has a new boot.img that it flashed to my Nabi 2...
well hello everybody .... I´m from Argentina and I will try to explain the best who I can this problem....
I have a galaxy s3, in the beninning I can install custom roms without any problem, I'm not sure when, but after my external sdcard broke, I could not install custom roms anymore.
I can flash stock firmwares without a problem but not custom roms.
Even turned to Android 4.0.4, updating it to 4.1.2 did full wipes and yet I still can´t do it.
When I put the custom rom in the ext sdcard show me this
installing kernel....
installing modem....
assert failed. package_extract_file("modem.bin"."/tmp/modem.bin")
E:Error in / external_sd/dev/EP-XXEMD3-v2.zip
(Status 7)
Instalation aborted
and when I try to install from internal sdcard, seems to be installed correctly, but the installation takes no more than 1 minute and when restart the phone gets stuck at the samsung logo.
I really don´t know what else I can do.... I hope someone knows how to help me because I do not know what more I can do to fix it.
thank you very much to all and I hope you understand my bad English
juan272 said:
I Will.... But really I download about a 20 different roms and the same happend
Click to expand...
Click to collapse
Wipe phone flash stock rom root and install custom rom .
status 7 is error doing by wrong recovery. flash good kernel on stock with cwm 6 then put your rom. mayby u flashing rom without kernel so u got error
Sent from my GT-I9100 using xda app-developers app
JJEgan said:
Wipe phone flash stock rom root and install custom rom .
Click to expand...
Click to collapse
I did a full wipe, format system, data, caché and preload..... I install 2 or 3 differents stock roms..... I go back to Android 4.0 and upgrade to 4.1.2 I clean the kernel..... The same happend over and over
Are you using a custom recovery?
slaphead20 said:
Are you using a custom recovery?
Click to expand...
Click to collapse
The Last cmw and I try with Philz recovery to..... Where información can find The Last stock kernel????
zalukajonet said:
status 7 is error doing by wrong recovery. flash good kernel on stock with cwm 6 then put your rom. mayby u flashing rom without kernel so u got error
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I install this kernel "Kernel: XXEMD2" over EMD3, I put the rom in the ext sdcard, and the recovery showme
backup efs....
Formatting...
installing...
system links...
permissions....
installing kernel....
installing modem....
installation succesful !!!
install from sdcard complete.
(the installation take no more than 1 minute,,,,,)
and when I reboot stuck in samsung i9300 logo
--------------------------
well at least now the recovery don´t show me installing modem error .....:victory::victory::victory:
:crying::crying::crying:
there is one more thing I don´t know if this is important but anyway..... before I´m using " Yank555.lu-SGS3-JB-kernel-v3.3i-aroma " then I use "Ultimate_Kernel_Cleaning_Script_v1.0_en_SGS3" to clean my kernel and finally install the stock kernel... the question is..... this kernel cleaner is enough to clean that kernel or I will nedd something more???
juan272 said:
I install this kernel "Kernel: XXEMD2" over EMD3, I put the rom in the ext sdcard, and the recovery showme
backup efs....
Formatting...
installing...
system links...
permissions....
installing kernel....
installing modem....
installation succesful !!!
install from sdcard complete.
(the installation take no more than 1 minute,,,,,)
and when I reboot stuck in samsung i9300 logo
--------------------------
well at least now the recovery don´t show me installing modem error .....:victory::victory::victory:
:crying::crying::crying:
there is one more thing I don´t know if this is important but anyway..... before I´m using " Yank555.lu-SGS3-JB-kernel-v3.3i-aroma " then I use "Ultimate_Kernel_Cleaning_Script_v1.0_en_SGS3" to clean my kernel and finally install the stock kernel... the question is..... this kernel cleaner is enough to clean that kernel or I will nedd something more???
Click to expand...
Click to collapse
Factory reset .
jje
JJEgan said:
Factory reset .
jje
Click to expand...
Click to collapse
well..... I do a factory reset, full wipe, format system, data, cache pre load, and install again the firmware " I9300XXEMD3_I9300OJVEMC1_I9300XXEMA5_HOME.tar ", and try with Revolution HD rom..... with the same results....
I really dont know what more I can do
I try to instsal Revolution HD rom (takes no more than 1 minute to finish instalation) and this is the changelog of the instalation.... I´m losing the hope to solve this.... please someone help me!!!! what the hell is happening to my phone??????
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Android Revolution HD
ROM Version : 27.0
ROM Author : mike1986
Device : Samsung Galaxy S3
Start at : Tue Jun 25 05:59:12 2013
=================================
Android Revolution HD by mike1986
=================================
>>> Formatting partitions
unmount of /system failed; no such volume
(system is unmounted already)
Creating filesystem with parameters:
Size: 1610612736
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 6144
Label:
Blocks: 393216
Block groups: 12
Reserved block group size: 0
Created filesystem with 11/98304 inodes and 12326/393216 blocks
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 0
Created filesystem with 11/65536 inodes and 8220/262144 blocks
unmount of /preload failed; no such volume
(preload is unmounted already)
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35840 inodes and 4498/143360 blocks
mount: failed to mount /dev/block/mmcblk0p12 at /data: Device or resource busy
(data is mounted already)
about to run program [/tmp/wipe.sh] with 1 args
about to run program [/tmp/efs_backup.sh] with 1 args
mount: mounting /dev/block/mmcblk0p12 on /data failed: Device or resource busy
tar: removing leading '/' from member names
efs/
efs/drm/
efs/drm/playready/
efs/drm/playready/00002.PRV
efs/drm/playready/DxDeviceKey
efs/drm/playready/DxSecureDB
efs/drm/playready/DxSecureDB_secondary
efs/drm/playready/NVS
efs/.files/
efs/.files/.dx1/
efs/.files/.dm33/
efs/.files/.mp301/
efs/wifi/
efs/wifi/.mac.info
efs/bluetooth/
efs/bluetooth/bt_addr
efs/imei/
efs/imei/mps_code.dat
efs/nv.log
efs/nv_data.bin
efs/.nv_state
efs/.nv_core.bak
efs/.nv_core.bak.md5
efs/.nv_data.bak
efs/.nv_data.bak.md5
efs/FactoryApp/
efs/FactoryApp/hw_ver
efs/FactoryApp/serial_no
efs/FactoryApp/factorymode
efs/FactoryApp/keystr
efs/FactoryApp/baro_delta
efs/nv_data.bin.md5
efs/gyro_cal_data
efs/00000000.authtokcont
efs/lost+found/
efs/wv.keys
efs/h2k.dat
/tmp/efs_backup.sh: line 14: unmount: not found
/tmp/efs_backup.sh: line 15: unmount: not found
/tmp/efs_backup.sh: line 16: unmount: not found
run_program: child exited with status 10
>>> Mounting partitions
mount: failed to mount /dev/block/mmcblk0p9 at /system: Device or resource busy
(system is mounted already)
mount: failed to mount /dev/block/mmcblk0p12 at /data: Device or resource busy
(data is mounted already)
>>> Cleaning process
about to run program [/tmp/clean.sh] with 1 args
rm: can't remove '/data/app/eu.chainfire.supersu*.apk': No such file or directory
rm: can't remove '/data/app/eu.chainfire.supersu.pro*.apk': No such file or directory
>>> Writing Data & System
Extract: /system/app/AccuweatherDaemon.apk
Extract: /system/app/Gmail.apk
Extract: /system/app/GmsCore.apk
Extract: /system/app/Phonesky.apk
Extract: /system/app/Superuser.apk
Extract: /system/bin/sysro
Extract: /system/bin/sysrw
Extract: /system/bin/zipalign
Extract: /system/etc/enforcecopyinglibpackages.txt
Extract: /system/etc/init.d/93zipalign
Extract: /system/etc/init.d/99complete
Extract: /system/etc/init.post_boot.sh
Extract: /system/etc/ondemand
Extract: /system/etc/sysctl.conf
Extract: /system/lib/libAppDataSearch.so
Extract: /system/xbin/busybox
Extract: /system/xbin/su
about to run program [/sbin/sync] with 1 args
>>> Installing Google Chrome
Extract: /data/app/com.android.chrome-1.apk
>>> Installing Google Maps & Google Street
Extract: /data/app/com.google.android.apps.maps-1.apk
Extract: /data/app/com.google.android.street-1.apk
>>> Installing Google YouTube
Extract: /data/app/com.google.android.youtube-1.apk
>>> Installing Dropbox
Extract: /data/app/com.dropbox.android-1.apk
>>> Installing Facebook
Extract: /data/app/com.facebook.katana-1.apk
>>> Installing Adobe Flash Player
Extract: /data/app/com.adobe.flashplayer-1.apk
>>> Installing Adobe Reader
>>> Installing EXT4 Performance Tweak
about to run program [/tmp/ext4] with 1 args
tune2fs 1.41.12 (17-May-2010)
Usage: /tmp/tune2fs [-c max_mounts_count] [-e errors_behavior] [-g group]
[-i interval[d|m|w]] [-j] [-J journal_options] [-l]
[-m reserved_blocks_percent] [-o [^]mount_options[,...]]
[-r reserved_blocks_count] [-u user] [-C mount_count] [-L volume_label]
[-M last_mounted_dir] [-O [^]feature[,...]]
[-E extended-option[,...]] [-T last_check_time] [-U UUID]
[ -I new_inode_size ] device
tune2fs 1.41.12 (17-May-2010)
tune2fs 1.41.12 (17-May-2010)
>>> Installing build.prop Tweaks
about to run program [/tmp/tweaks.sh] with 1 args
Extract: /system/app/Superuser.apk
Extract: /system/xbin/su
>>> Creating toolbox symlinks
>>> Creating additional symlinks
symlink: failed to symlink /system/fonts/DroidSans.ttf to /system/fonts/Roboto-Regular.ttf: No such file or directory
symlink: failed to symlink /system/fonts/DroidSans-Bold.ttf to /system/fonts/Roboto-Bold.ttf: No such file or directory
>>> Installing busybox
about to run program [/system/xbin/busybox] with 4 args
>>> Flashing CSC content
Extract: /system/CSCVersion.txt
Extract: /system/SW_Configuration.xml
Extract: /system/csc/BTU/system/csc/contents.db
Extract: /system/csc/BTU/system/csc/customer.xml
Extract: /system/csc/BTU/system/csc/feature.xml
Extract: /system/csc/BTU/system/csc/others.xml
Extract: /system/csc/BTU/system/csc/sales_code.dat
Extract: /system/csc/CPW/system/csc/contents.db
Extract: /system/csc/CPW/system/csc/customer.xml
Extract: /system/csc/CPW/system/csc/feature.xml
Extract: /system/csc/CPW/system/csc/others.xml
Extract: /system/csc/CPW/system/csc/sales_code.dat
Extract: /system/csc/DBT/system/csc/contents.db
Extract: /system/csc/DBT/system/csc/customer.xml
Extract: /system/csc/DBT/system/csc/feature.xml
Extract: /system/csc/DBT/system/csc/others.xml
Extract: /system/csc/DBT/system/csc/sales_code.dat
Extract: /system/csc/ITV/system/csc/contents.db
Extract: /system/csc/ITV/system/csc/customer.xml
Extract: /system/csc/ITV/system/csc/feature.xml
Extract: /system/csc/ITV/system/csc/others.xml
Extract: /system/csc/ITV/system/csc/sales_code.dat
Extract: /system/csc/KOR/system/csc/contents.db
Extract: /system/csc/KOR/system/csc/customer.xml
Extract: /system/csc/KOR/system/csc/feature.xml
Extract: /system/csc/KOR/system/csc/others.xml
Extract: /system/csc/KOR/system/csc/sales_code.dat
Extract: /system/csc/XEF/system/csc/contents.db
Extract: /system/csc/XEF/system/csc/customer.xml
Extract: /system/csc/XEF/system/csc/feature.xml
Extract: /system/csc/XEF/system/csc/others.xml
Extract: /system/csc/XEF/system/csc/sales_code.dat
Extract: /system/csc/XEO/system/csc/contents.db
Extract: /system/csc/XEO/system/csc/customer.xml
Extract: /system/csc/XEO/system/csc/feature.xml
Extract: /system/csc/XEO/system/csc/others.xml
Extract: /system/csc/XEO/system/csc/sales_code.dat
Extract: /system/csc/common/system/csc/language.xml
Extract: /system/csc/common/system/csc/others.xml
Extract: /system/csc/contents.db
Extract: /system/csc/customer.xml
Extract: /system/csc/feature.xml
Extract: /system/csc/others.xml
Extract: /system/csc/sales_code.dat
Extract: /system/sipdb/de_DE.zip
Extract: /system/sipdb/en_GB.zip
Extract: /system/sipdb/en_US.zip
Extract: /system/sipdb/fr_FR.zip
Extract: /system/sipdb/it_IT.zip
Extract: /system/sipdb/ko_KR.zip
Extract: /system/sipdb/pl_PL.zip
>>> Setting permissions
set_perm: chown of /system/bin/netcfg to 0 3003 failed: No such file or directory
set_perm: chmod of /system/bin/netcfg to 2750 failed: No such file or directory
set_perm: chown of /system/bin/ping to 0 3004 failed: No such file or directory
set_perm: chmod of /system/bin/ping to 2755 failed: No such file or directory
set_perm: chown of /system/bin/run-as to 0 2000 failed: No such file or directory
set_perm: chmod of /system/bin/run-as to 6750 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth to 755 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/auto_pairing.conf to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/auto_pairing.conf to 640 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/blacklist.conf to 3002 3002 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/blacklist.conf to 444 failed: No such file or directory
set_perm: chown of /system/etc/dbus.conf to 1002 1002 failed: No such file or directory
set_perm: chmod of /system/etc/dbus.conf to 440 failed: No such file or directory
set_perm: chown of /system/etc/dhcpcd/dhcpcd-run-hooks to 1014 2000 failed: No such file or directory
set_perm: chmod of /system/etc/dhcpcd/dhcpcd-run-hooks to 550 failed: No such file or directory
set_perm: chown of /system/vendor to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor to 755 failed: No such file or directory
set_perm: chown of /system/vendor/etc to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/etc to 755 failed: No such file or directory
set_perm: chown of /system/vendor/etc/nxp to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/etc/nxp to 755 failed: No such file or directory
set_perm: chown of /system/vendor/etc/nxp/BargeIn to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/etc/nxp/BargeIn to 755 failed: No such file or directory
set_perm: chown of /system/vendor/etc/nxp/mVoIP to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/etc/nxp/mVoIP to 755 failed: No such file or directory
set_perm: chown of /system/vendor/etc/nxp/mVoIPSec to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/etc/nxp/mVoIPSec to 755 failed: No such file or directory
set_perm: chown of /system/vendor/firmware to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/firmware to 755 failed: No such file or directory
set_perm: chown of /system/vendor/lib to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/lib to 755 failed: No such file or directory
set_perm: chown of /system/vendor/lib/drm/libdrmwvmplugin.so to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/lib/drm/libdrmwvmplugin.so to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7/left_eye-y0-yi45-p0-pi45-r0-ri20.lg_32/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7/left_eye-y0-yi45-p0-pi45-r0-ri20.lg_32/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7/nose_base-y0-yi45-p0-pi45-r0-ri20.lg_32/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7/nose_base-y0-yi45-p0-pi45-r0-ri20.lg_32/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7/right_eye-y0-yi45-p0-pi45-r0-ri20.lg_32-2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7/right_eye-y0-yi45-p0-pi45-r0-ri20.lg_32-2/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6/head-y0-yi45-p0-pi45-r0-ri30.4a-v24/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6/head-y0-yi45-p0-pi45-r0-ri30.4a-v24/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6/head-y0-yi45-p0-pi45-rn30-ri30.5-v24/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6/head-y0-yi45-p0-pi45-rn30-ri30.5-v24/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6/head-y0-yi45-p0-pi45-rp30-ri30.5-v24/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6/head-y0-yi45-p0-pi45-rp30-ri30.5-v24/full_model.bin to 644 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N/full_model.bin to 644 failed: No such file or directory
>>> Flashing kernel
>>> Flashing modem
about to run program [/tmp/flash_image] with 3 args
>>> Unmounting partitions
===================================
New ROM flashed successfully!
Please share your experience on XDA
===================================
about to run program [/sbin/busybox] with 4 args
script result was [1.0]
Installer Sucessfull (Status 0)
End at : Tue Jun 25 05:59:36 2013
edit: I download two times the rom....
Please can you wrap large errors / code in code tags (the button that looks like [#] )
Code:
That would need to be an advanced edit now...
JJEgan said:
Factory reset .
jje
Click to expand...
Click to collapse
I remember all this trouble started after installing JKay framework, this may have brought some inconvenience for flashing roms?