Related
Looking for some help with the modification of the kernel from the Sero 7 Pro
Below is the kernel stock values to show location of sdcard and external sd card
Code:
on init
mkdir /mnt/shell/emulated 0700 shell shell
mkdir /storage/emulated 0555 root root
mkdir /storage/sdcard1 0555 root root
export SECONDARY_STORAGE /storage/sdcard1
export EXTERNAL_STORAGE /storage/emulated/legacy
export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
export EMULATED_STORAGE_TARGET /storage/emulated
# Support legacy paths
symlink /storage/emulated/legacy /sdcard
symlink /storage/emulated/legacy /mnt/sdcard
symlink /storage/emulated/legacy /storage/sdcard0
symlink /mnt/shell/emulated/0 /storage/emulated/legacy
symlink /storage/sdcard1 /sdcard2
symlink /storage/sdcard1 /mnt/sdcard2
I would like to swap storage locations. Anyone want to assist? Post your edits I will compile, flash and post results.
xboxexpert said:
Looking for some help with the modification of the kernel from the Sero 7 Pro
Below is the kernel stock values to show location of sdcard and external sd card
Code:
on init
mkdir /mnt/shell/emulated 0700 shell shell
mkdir /storage/emulated 0555 root root
mkdir /storage/sdcard1 0555 root root
export SECONDARY_STORAGE /storage/sdcard1
export EXTERNAL_STORAGE /storage/emulated/legacy
export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
export EMULATED_STORAGE_TARGET /storage/emulated
# Support legacy paths
symlink /storage/emulated/legacy /sdcard
symlink /storage/emulated/legacy /mnt/sdcard
symlink /storage/emulated/legacy /storage/sdcard0
symlink /mnt/shell/emulated/0 /storage/emulated/legacy
symlink /storage/sdcard1 /sdcard2
symlink /storage/sdcard1 /mnt/sdcard2
I would like to swap storage locations. Anyone want to assist? Post your edits I will compile, flash and post results.
Click to expand...
Click to collapse
Could you please try this?
symlink /storage/emulated/legacy /sdcard2
symlink /storage/emulated/legacy /mnt/sdcard2
symlink /storage/emulated/legacy /storage/sdcard0
symlink /mnt/shell/emulated/0 /storage/emulated/legacy
symlink /storage/sdcard1 /sdcard
symlink /storage/sdcard1 /mnt/sdcard
angellsl said:
Could you please try this?
symlink /storage/emulated/legacy /sdcard2
symlink /storage/emulated/legacy /mnt/sdcard2
symlink /storage/emulated/legacy /storage/sdcard0
symlink /mnt/shell/emulated/0 /storage/emulated/legacy
symlink /storage/sdcard1 /sdcard
symlink /storage/sdcard1 /mnt/sdcard
Click to expand...
Click to collapse
I did that and then flashed yet it had no effect on the storage of the device. Still the same.
xboxexpert said:
I did that and then flashed yet it had no effect on the storage of the device. Still the same.
Click to expand...
Click to collapse
Thanks!
It seems that Sero 7 Pro uses emulation in init.m470.rc to mount the internal storage at /mnt/shell/emulated (line 341)
And it uses /etc/vold.fstab to mount the external storage (SD card) at /storage/sdcard1
Here is a link for Android storage management http://source.android.com/tech/storage/
I think it's feasible to remove the emulation at init.m470.rc and put both internal/external mounting in /etc/vold.fstab (to make the internal storage mounted at /sdcard2 while SD card mounted at internal (/sdcard) ), but we have to make sure the symlinks are updated accordingly.
Or, we can also keep the emulation at line 341, but mount it at /storage/sdcard1.
I don't know how to build the rootfs yet. So I didn't try...
Hope it helps
angellsl said:
Thanks!
It seems that Sero 7 Pro uses emulation in init.m470.rc to mount the internal storage at /mnt/shell/emulated (line 341)
And it uses /etc/vold.fstab to mount the external storage (SD card) at /storage/sdcard1
Here is a link for Android storage management http://source.android.com/tech/storage/
I think it's feasible to remove the emulation at init.m470.rc and put both internal/external mounting in /etc/vold.fstab (to make the internal storage mounted at /sdcard2 while SD card mounted at internal (/sdcard) ), but we have to make sure the symlinks are updated accordingly.
Or, we can also keep the emulation at line 341, but mount it at /storage/sdcard1.
I don't know how to build the rootfs yet. So I didn't try...
Hope it helps
Click to expand...
Click to collapse
You could edit the file accordingly and if you want to send it over I'll recompile and flash.
xboxexpert said:
You could edit the file accordingly and if you want to send it over I'll recompile and flash.
Click to expand...
Click to collapse
I was able to enable init.d first, and then I can swap the cards using the same trick I did for my note 2. But the storage in settings cannot see the change. The emulated internal storage on sero 7 has a slight different file hierarchy, probably because of the android version difference (4.1.2 vs 4.2.1)? I felt I'm almost there, just not sure what labels/mounts the storage in settings reads (/sdcard? others?)
Keep up the great work guys I'm following eagerly to see what you all come up with. We may have a Dev soon Unjustified Developer is talking about purchasing this tab!
Not that you're not doing a great job Xbox making the headlines everyday! Great work appreciate everything you're doing! Can't wait till father's day when my wife allows me to play with it Lol
Sent from my SCH-R530U using Tapatalk 4 Beta
angellsl said:
I was able to enable init.d first, and then I can swap the cards using the same trick I did for my note 2. But the storage in settings cannot see the change. The emulated internal storage on sero 7 has a slight different file hierarchy, probably because of the android version difference (4.1.2 vs 4.2.1)? I felt I'm almost there, just not sure what labels/mounts the storage in settings reads (/sdcard? others?)
Click to expand...
Click to collapse
Storage and settings is controlled by the vold.fstab in /system/etc I think.
trvbone said:
Can't wait till father's day when my wife allows me to play with it Lol
Click to expand...
Click to collapse
I laughed...I have the same issues only my toys are Corvettes
I give up for now. Fall back to folder mount,it works great, installed over 10GB of games.
Sent from my M470BSA using Tapatalk 2
No further progress on this issue?
Hi everyone,
During a manipulation I accidentally type "rm /sdcard" via adb...
After that, I tried to clean the sdcard (via Settings panel), wipe the cache, and made a reset factory to fix my error, but without success.
Finally :
- some directories have been re-created (Alarms, Android, DCIM, Download, LOST.DIR, Movies, Music, Notifications, Pictures, Podcasts, Ringtones),
- when I try to install an app, I got the INSTALL_FAILED_INSUFFICIENT_STORAGE error (but my sdcard is technically empty)
- in the Storage tab (in Settings Panel) I see Total space=0.00B
Is there a problem with the partitioning? Have you any idea to fix this issue?
Model : a Chinese prototype, can't share the name
OS : Android 4.1.1
No backup, no original ROM
Root access via ADB.
Thank you!
kikiwa said:
Hi everyone,
During a manipulation I accidentally type "rm /sdcard" via adb...
After that, I tried to clean the sdcard (via Settings panel), wipe the cache, and made a reset factory to fix my error, but without success.
Finally :
- some directories have been re-created (Alarms, Android, DCIM, Download, LOST.DIR, Movies, Music, Notifications, Pictures, Podcasts, Ringtones),
- when I try to install an app, I got the INSTALL_FAILED_INSUFFICIENT_STORAGE error (but my sdcard is technically empty)
- in the Storage tab (in Settings Panel) I see Total space=0.00B
Is there a problem with the partitioning? Have you any idea to fix this issue?
Model : a Chinese prototype, can't share the name
OS : Android 4.1.1
No backup, no original ROM
Root access via ADB.
Thank you!
Click to expand...
Click to collapse
Well... First of all, you should always (yes, always) make a nandroid backup... If you can't use CWM, there's always the adb backup option
Have you tried the SD card in a computer? Does it read? Have you tried formatting the sdcard again through android?
El_Dark said:
Have you tried the SD card in a computer? Does it read? Have you tried formatting the sdcard again through android?
Click to expand...
Click to collapse
It's the internal SD card, I cannot take out of the tablet.
The SDcard is readable, I can use adb to load some files on it, like an apk for example. It's just Android cannot detect free memory to install a new app.
And yes, I tried to "erase SDCard" via Android (that I called "Settings panel" in my first post).
Do you need more details ?
kikiwa said:
It's the internal SD card, I cannot take out of the tablet.
The SDcard is readable, I can use adb to load some files on it, like an apk for example. It's just Android cannot detect free memory to install a new app.
And yes, I tried to "erase SDCard" via Android (that I called "Settings panel" in my first post).
Do you need more details ?
Click to expand...
Click to collapse
have you tried adb shell then mkdir /sdcard and after that reboot the device ?
SirRaul said:
have you tried adb shell then mkdir /sdcard and after that reboot the device ?
Click to expand...
Click to collapse
This is a good idea... Also, would be good trying to Data erase/factory reset from recovery (if any available)
Another good one would be to, if supported by the Kernel, add an init.d script like S01FixSDCard like this:
Code:
#!/system/bin/sh
#I'm a bit outdated in what means bash scripting, but with a little reading you can get the idea :)
#The script must be ran at system start, also make sure it's chowned to 0.0 and with 755 and that it'll be ran as root
if [-d /mnt/sdcard] then
rmdir /mnt/sdcard
fi
mkdir /mnt/sdcard
chown 0.0 /mnt/sdcard
#Some legacy apps/scripts call the sdcard this way (I'm not sure though how it is when it's an internal sdcard, my S5830i has only external SD
ln -s /mnt/sdcard /sdcard
#This line was taken "as is" from my "mount" command, you should adapt many parameters here, to begin with, the UID of your GUI user
#it should be 1000 by default, but you never know... Also, check the GID which corresponds to the group of your GUI user, in my case it's
#1015. If you can get how your sdcard is mounted by default, awesome ;)
mount -t vfat -o rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp347,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro /dev/block/vold/179:1 /mnt/sdcard
Hope that helps, corrections and contributions are welcome
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
Also, can you share a screenshot of your settings panel in the storage option?
One more suggestion: Use "aParted" look for it on the Play Store, and as for data recovery matters (if you need) you might want to try CamRec from Cristophe Grenier.. http://www.cgsecurity.org/
Thank you for your ideas !!
have you tried adb shell then mkdir /sdcard and after that reboot the device ?
Click to expand...
Click to collapse
It just recreate some directories (Alarms, Android, DCIM, Download, ...) but impossible to install anything.
Also, would be good trying to Data erase/factory reset from recovery
Click to expand...
Click to collapse
No recovery available.
add an init.d script like S01FixSDCard
Click to expand...
Click to collapse
I tried to adapt the script (with vold/93:72 the only available), but no changes.
Use "aParted" look for it on the Play Store
Click to expand...
Click to collapse
Looks again like a good idea but ... my problem is I can't install anything
So, I'm always blocked
Do you know how to re-partition the sdcard from an android command line (with busybox) ?
Finally a screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to format it, you need to know in what format was before, since it's the internal memory, maybe was fat maybe was ext2, ext3, ext4. When you connected your device to the pc, did you had access to the internal sdcard ?
try this
adb shell, and after you're in the phone's shell, check if you're root with id command, rm /sdcard and symlink /mnt/sdcard /sdcard
if you're not root, use su to become one, but since you managed to delete /sdcard folder, I think you have root permissions already when you're in shell.
Can you tell us what device do you have ?
P.S.: you didn't posted the screenshot. It doesn't appear.
SirRaul said:
to format it, you need to know in what format was before, since it's the internal memory, maybe was fat maybe was ext2, ext3, ext4. When you connected your device to the pc, did you had access to the internal sdcard ?
Click to expand...
Click to collapse
I have an access to the phone via adb, andif I change the connection as Media device (MTP), I see my internal storage from my PC explorer (Windows 7). Is there a way to know the partition type ?
SirRaul said:
adb shell, and after you're in the phone's shell, check if you're root with id command, rm /sdcard and symlink /mnt/sdcard /sdcard
if you're not root, use su to become one, but since you managed to delete /sdcard folder, I think you have root permissions already when you're in shell.
Can you tell us what device do you have ?
P.S.: you didn't posted the screenshot. It doesn't appear.
Click to expand...
Click to collapse
id => uid=0(root) gid=0(root)
I have already remove sdcard 5 times in different context, the symbolic link is automatically recreated from /mnt/sdcard so I think it's not enough to fix my issue.
And I can't tell you what is my device (see first post).
For the screenshot, I can't share external links since I'm too "young" for that ^^. But try to follow the link (right click), it would show you the picture (tell me if it's not good and I will change it).
First of all, check where's the sdcard's path:
ls /dev/block/mmc*
You should have 2 paths. First mmcblk0 - not sure tho and I can't check it right now, we don't need that anyway. And the second mmcblk0p1.
If you have it, use busybox mkfs.vfat /dev/block/mmcblk0p1 to format it in fat32 and reboot
Sent from my Perfect HTC ChaCha - 32Gb Unique Model
SirRaul said:
First of all, check where's the sdcard's path:
ls /dev/block/mmc*
You should have 2 paths. First mmcblk0 - not sure tho and I can't check it right now, we don't need that anyway. And the second mmcblk0p1.
If you have it, use busybox mkfs.vfat /dev/block/mmcblk0p1 to format it in fat32 and reboot
Click to expand...
Click to collapse
Code:
ls /dev/block
dm-0
dm-1
dm-2
dm-3
dm-4
dm-5
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
nanda
nandb
nandc
nandd
nande
nandf
nandg
nandh
nandi
nandj
vold
I just test a debugging option :
Code:
pm set-install-location 2
The documentation said it's used to install on external media, and there is no external media ... but I tried and it works just enough to install an other app. But apps are no more available after reboot, like all user settings. On each reboot, it's just like I swipe my cache (but downloaded data are always on the /sdcard/)...
use adb pull /init.rc and open it with a text editor. it's the first file which runs before android will boot. Check it and if it doesn't make any sense what you'll find there, just upload it here and I'll take a look
SirRaul said:
use adb pull /init.rc and open it with a text editor. it's the first file which runs before android will boot. Check it and if it doesn't make any sense what you'll find there, just upload it here and I'll take a look
Click to expand...
Click to collapse
Thank you for the help !
My init.rc :
# 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.trace.rc
import /init.usb.rc
import /init.${ro.hardware}.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
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
insmod /nand.ko
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 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/vm/legacy_va_layout 1
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 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
mkdir /cache/dsbackup
mkdir /cache/dsbackup/logfile
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 0777 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
chown system wifi /data/misc/wifi/wpa_supplicant.conf
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
chown dhcp dhcp /data/misc/dhcp
mkdir /data/local 0751 root root
# star add for camera recorder
mkdir /data/camera 0751 media media
# 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
# 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
# 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
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
# su root
chown root root /system/xbin/su
chmod 6755 /system/xbin/su
# 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
chown system system /sys/class/android_usb/android0/iSerial
chmod 0660 /sys/class/android_usb/android0/iSerial
# 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/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 0660 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 0660 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chown system system /sys/devices/system/cpu/cpufreq/fantasys/max_power
chmod 0660 /sys/devices/system/cpu/cpufreq/fantasys/max_power
chown system system /sys/devices/system/cpu/cpufreq/fantasys/pulse
chmod 0660 /sys/devices/system/cpu/cpufreq/fantasys/pulse
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
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
service console /system/bin/sh /dev/ttyS0
class core
console
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
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 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 sdcard_rw media_rw
ioprio rt 4
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
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 dhcpcd_wlan0 /system/bin/dhcpcd -aABKL
class main
disabled
oneshot
service dhcpcd_p2p /system/bin/dhcpcd -aABKL
class main
disabled
oneshot
service dhcpcd_bnep0 /system/bin/dhcpcd -ABKL
class main
disabled
oneshot
service dhcpcd_eth /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_bnep0 /system/bin/dhcpcd -n
class main
disabled
oneshot
service iprenew_eth /system/bin/dhcpcd -n
class main
disabled
oneshot
service preinstall /system/bin/busybox sh /system/bin/preinstall.sh
user root
group root
disabled
oneshot
on property:sys.boot_completed=1
start preinstall
# datarestore b
on property:sys.restoresystem=1
# exec /system/bin/stop
# datarestore l
# datarestore r
# exec /system/bin/reboot
An other point I just find, I see on internet that the mount command have an entry for /data, but I see nothing in my case :
Code:
rootfs / rootfs rw 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
debugfs /sys/kernel/debug debugfs rw,relatime 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/nandd /system ext4 ro,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437
,iocharset=ascii,shortname=mixed,utf8,errors=continue 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=ascii,shortname=mixed,utf8,errors=continue 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
That explains why you can't install apps. When you install an application on android, it's installed in /data, which is a mount point of the internal memory. I think you have a problem with that, not just with the sdcard. and as I can see from the log you pasted, the sdcard is mounted here /dev/block/vold/93:72 /mnt/sdcard ...
And
/dev/block/nandd /system ext4 ro,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
it seems that one partition in /dev/block/* is the data partition. you can find out if you check the sizes with the df -h command.
I don't see anywhere in init.rc the mount command for the /data partition, I'm sure it's in another file. check the files from main directory, where init.rc is. Just the files, don't check in any directory. Maybe we'll get at the bottom of this!
Elephone P6000 Recovery
SPFlashtool Video is now removed due to possible confusion. I will make a new more concise video for making backup's of specific partitions very soon
Here is a couple of tut's for those who have windows 8.1 64bit problems Drivers etc.
Uninstall any previous attempts to install drivers then reboot the PC do not insert your phone yet!!
Follow these guides step by step.
This first Driver Signature Verification
Then follow this down to step 9 Installing Vcom Drivers windows 8.1
Thanks to the authors of these tuts
Note: If you do not name your readback eg boot.img and leave the ROM_0 the flashtool will just do a complete ROM dump of your entire phone 12.8gb which cannot be processed by droid tools :silly:
PLEASE READ and post in the Q&A Tab which is above my name over < there also hit the THANKS Button bottom Left corner if I helped it costs you no money but cost me many hours
Recommended Viewing
See @rnovino more detailed and excellent general SPFlashTool TuTs with all the mtk drivers links . Thanks to him for these.
Here and Here
Please NO NOOBS asking how to install drivers etc just use google as these questions have been answered a million times over and I really don't have the time to spoon feed everyone :crying: You will probably brick your phone if you don't know what you're doing so read read and read again. :silly:
Recovery
UPDATE: bigrammy CWM port is now retired. Good news is that @carliv has compiled a CWM Recovery Specifically for the P6000 :victory: Dont be just a Leech and please show him your respect and appreciation by visiting his thread and hitting his THANKS button HERE at the very least.
a bigammy Thanks to all the dev's and testers involved with this project :highfive:
Offcial: Compiled recovery-CWM-Modd-P6000 Download here
HERE
Thanks to @carliv for the recovery module to fix this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All the menu screenshots are HERE They are of the version before the font was fixed. I will update these when I get the time.
Credits To.
@carliv Without whom the Recovery would not have been possible so hit his THANKS button at the very least or better still buy him a coffee Here
@yuweng For his continued support and Advice Thanks bro :highfive:
@rua1 For his awesome DroidTools that saves everyone this headache if their device is lucky enough to be supported Please come back!! :laugh:
There are so many more people that should be mentioned but I would run out of thread so to all who have helped and educated MANY THANKS
It should go without saying all is at your own risk and I take No, None, Zero, Nada, Zip, Responsibility.
SPFlashtool and Recovey are powerful tools and can either revive your phones or kill them forever so you have been warned. !!!!!
Regards bigrammy.
Guys PLEASE!! do not post my links on other websites or forums This is only so that the proper people get the credit and support is available for the user. It is just as easy to post a link to this thread HERE My links are spam free and I earn zero money from them so why do it :silly:
TWRP LOLLIPOP VERSION v2.8.7.0
HERE
Hit Thanks before you leave.
Recovery
New CWM Recovery is now ported to the p6000.
It's the None Touch Versions and I ported it over from the mt6595 version made by carliv :angel: over Here so full credit goes to him for his Awesome work.
The recovery supports Aroma File Manager also so get over to carliv's thread for the Aroma File Manager zip and hit his THANKS button because without him we would still be stuck with zero support. Link to Aroma FM and all information about how to use it and install Aroma FM is in the thread there so read it please. Again Here
Use google first then ask if not sure.
Post any questions in the Q&A's at the top of this thread.
Here is the recovery Removed see OP
Use the normal ways to install it. adb, spflashtool, If rooted just get the flashify.apk https://play.google.com/store/apps/details?id=com.cgollner.flashify
Thanks and enjoy!!!
TWRP is HERE!!!! YEEEHAAA
Well at long last we have working TOUCH Recovery
First we must thank all the dev's who have spent many many many Hours and Days trying to fix this problem thats confounded the best of us @carliv @yuweng @codelover @Santhosh M @BachMinuetInG @HypoTurtle
The eventual fix came by way of @NiksSkersts and @yuweng who are working on the P6000 sister/rebranded phone the "Just5 Blaster" Thread Here Please visit and hit his thanks button Also Go HERE and Hit yuweng's Thanks Button for all his work he never gave up trying to fix our problem
All those listed need to be Thanked at the very least EVERYONE!!!
In the end the problem was with the KERNEL or the drivers for the kernel anyway the Just5 Kernel works fine for our recovery needs :good:
I have used a Early carliv TWRP test build for the first release I have had to make quite a lot of changes to the init.rc fstab etc as it was just a test build carliv made to see if the touch could be made to work So go over to @carliv thread and hit his THANKS Button or buy him a coffee because as said none of this would be possible without him :angel:
Quick Note: These are all based on KK so far Android L is still a work in progress
TWRP V2 Now added:
Fixes:
1, Added Custom Partition to Mounts/Backup :good:
Tips:
1. To prevent problems when data_sd and external_sd are mounted to the PC goto TWRP settings/screen and uncheck the sleep function so the screen does not sleep this will ensure a stable connections
2. To view your Internal_SD on device using the TWRP File Manager in Advanced make sure Data is Mounted then got to /data/media/0 you will now see all your internal_sd files so can edit copy etc on device.
3. Performing Backups with TWRPV2 . When you backup large partitions like Data or System PLEASE make sure to only select 1 one partition at a time to backup. You can select multipule small ones like boot, recovery, nvram and they will all backup fine but for some reason System and Data must be done one at a time on their own!!
Please verify any previous backups you have made.
You can double check them by moving the system/data.ext4.win file to your pc then rename it system/data.tar and use winrar to view the files inside. Rename it back to the ext4.win to use with twrp again.
TWRPV2 HERE
More Choice bigrammy I hear you say Well here you go all in one HIT!!
These are all the work of @carliv and have been compiled by him for the P6000 so make sure you thank him PLEASE!!!
I have not had time to test them all to destruction but I am sure they will be fine Enjoy!!
Carliv Touch Recovery V3.0 HERE
PhilzP6000 by Carliv Here
Carliv CWM V2 Touch Kernel Here Same as in the OP but with touch working
TWRP V2 Screenies
Here is the PhilzJust5 made by @yuweng and @NiksSkersts I confirm it works on our phone too but again not fully test by me Philz Recovery Here
TWRP Screenies here HAPPY BACKUPS EVERYONE!! & Dont forget hit the thanks button for all involved and me too
Ok, i m a noob with Mtk devices..but i've experience on modding with other android phone..... proc/partinfo give me the same result on partion size ecc...
but
Only one thing I did not understand,
I have to connect the device without a battery, right?
Connecting the device without battery, despite having installed the drivers Vcom, I see that the device is recognized for 2 seconds then disconnects automatically, then again recognized .. is this normal behavior?
thx for your work :good::good:
enr88 said:
Ok, i m a noob with Mtk devices..but i've experience on modding with other android phone..... proc/partinfo give me the same result on partion size ecc...
but
Only one thing I did not understand,
I have to connect the device without a battery, right?
Connecting the device without battery, despite having installed the drivers Vcom, I see that the device is recognized for 2 seconds then disconnects automatically, then again recognized .. is this normal behavior?
thx for your work :good::good:
Click to expand...
Click to collapse
I Missed your post
In Future please use the Q&A bro just read the OP above.
To answer your question: When the progress bar in flashtool turns red put in your battery quickly I have mine ready and just slightly away from the contacts.
When done it will now hold it on until the end of the read backs.
I will copy this to the Q&A HERE
New ft rom available, r. 8.4 9th january
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=2026#lastpost
bigrammy, i note that backup from cwm creates file size of boot, recovery of about 12Mb , have you tried to restore?
also another issue is that the backup folder is not in external sd, but in internal memory!
Thanks
megthebest said:
New ft rom available, r. 8.4 9th january
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=2026#lastpost
bigrammy, i note that backup from cwm creates file size of boot, recovery of about 12Mb , have you tried to restore?
also another issue is that the backup folder is not in external sd, but in internal memory!
Thanks
Click to expand...
Click to collapse
12MB? sure it's not 16MB (full partition size)...
@bigrammy in int.rc of the Carliv recovery doing this:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard1
export SECONDARY_STORAGE /storage/sdcard0
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0should switch it so that internal sdcard (/data/media/0) and external sd card switch places so that backup is added to removable card - only downside being it may not boot if there's no sdcard present.
HypoTurtle said:
12MB? sure it's not 16MB (full partition size)...
@bigrammy in int.rc of the Carliv recovery doing this:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard1
export SECONDARY_STORAGE /storage/sdcard0
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0should switch it so that internal sdcard (/data/media/0) and external sd card switch places so that backup is added to removable card - only downside being it may not boot if there's no sdcard present.
Click to expand...
Click to collapse
My boot.img backup size is 16mb (16,777,216 bytes) to be exact bro so not sure what's happened with yours
Did you use the stock scatter for a backup or flash? maybe double check your partition sizes on the phone /proc/partinfo
As for the storage problem i am working on this right now
I am full of cold so I don't think my brain is working properly :crying:
We have some strange paths for the cards and I am struggling to define them correctly so all works as it should.
In recovery we should be able to view our sdcard when plugged into the PC with the USB cable
I am not 100% sure if we have emulated or none emulated internal sdcard even.
This Elephone ROM is very poor with none existant files :crying: making my job even harder eg: the stock fstab's says the internal sd card is at [email protected] which does not exist
Even the paths are not correctly defined so it's a process of trial and error.
I don't wish to bother @carliv until I am 100% sure I can go no further .
For now the recovery does what it's supposed to do which is backup and flash all though it's to and from the internal sd
I am back at work tomorrow so no further debugging for 4 days from me.
You're more than welcome to have a go at fixing it if you wish just be sure to give carliv the credit :good:
bigrammy said:
This Elephone ROM is very poor with none existant files :crying: making my job even harder eg: the stock fstab's says the internal sd card is at [email protected] which does not exist
Even the paths are not correctly defined so it's a process of trial and error.
Click to expand...
Click to collapse
Ah, thought the fstab was taken from the boot.img, my mistake... Still waiting on mine to arrive (3 weeks and counting), will wait til then before attempting anything. Regarding the fstab it's actually /devices/mtk-msdc.0/11230000.MSDC0 that is claimed to be the internal sdcard, not quite sure how it can be it's own partition though, anyone care to post the outcome of mount and df?
Edit. The internal sdcard is set by the service sdcard in init.ssd_nomuser.rc
service sdcard /system/bin/sdcard -u 1023 -g 1023 -d /data/media /storage/sdcard0
class late_startnot sure if the fstab lines are an error or are used while in (adv)meta mode or something.
HypoTurtle said:
Ah, thought the fstab was taken from the boot.img, my mistake... Still waiting on mine to arrive (3 weeks and counting), will wait til then before attempting anything. Regarding the fstab it's actually /devices/mtk-msdc.0/11230000.MSDC0 that is claimed to be the internal sdcard, not quite sure how it can be it's own partition though, anyone care to post the outcome of mount and df?
Edit. The internal sdcard is set by the service sdcard in init.ssd_nomuser.rc
service sdcard /system/bin/sdcard -u 1023 -g 1023 -d /data/media /storage/sdcard0
class late_startnot sure if the fstab lines are an error or are used while in (adv)meta mode or something.
Click to expand...
Click to collapse
:laugh: Yeah thats what I thought too
/devices/mtk-msdc.0/11230000.MSDC0 the path seems not to be correct according to what I have on the phone itself which is /sys/devices/mtk-msdc.0/11230000.MSDC0/
and for the other card is /sys/devices/mtk-msdc.0/11240000.MSDC1/ ?/??? maybe we need to drill down further as I see in some of carliv examples it goes to /mmc_host/mmc0 1 for MSDC1
I have drilled all the way down and can confirm on 11230000.MSDC0 = Type = MMC and for 11240000.MSDC1 = Type = SD so I guess these are the correct ones
Your Thoughts Welcome.
bigrammy said:
:laugh: Yeah thats what I thought too
/devices/mtk-msdc.0/11230000.MSDC0 the path seems not to be correct according to what I have on the phone itself which is /sys/devices/mtk-msdc.0/11230000.MSDC0/
and for the other card is /sys/devices/mtk-msdc.0/11240000.MSDC1/ ?/??? maybe we need to drill down further as I see in some of carliv examples it goes to /mmc_host/mmc0 1 for MSDC1
I have drilled all the way down and can confirm on 11230000.MSDC0 = Type = MMC and for 11240000.MSDC1 = Type = SD so I guess these are the correct ones
Your Thoughts Welcome.
Click to expand...
Click to collapse
TCL Meme da 3N M2M MT6752
Cofface recovery
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
Recovery here
hanuma said:
TCL Meme da 3N M2M MT6752
Cofface recovery
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
Recovery here
Click to expand...
Click to collapse
Thanks bro I will check how he has defined things. Is it in english do you know? It maybe easier to port this. :laugh:
bigrammy said:
:laugh: Yeah thats what I thought too
/devices/mtk-msdc.0/11230000.MSDC0 the path seems not to be correct according to what I have on the phone itself which is /sys/devices/mtk-msdc.0/11230000.MSDC0/
and for the other card is /sys/devices/mtk-msdc.0/11240000.MSDC1/ ?/??? maybe we need to drill down further as I see in some of carliv examples it goes to /mmc_host/mmc0 1 for MSDC1
I have drilled all the way down and can confirm on 11230000.MSDC0 = Type = MMC and for 11240000.MSDC1 = Type = SD so I guess these are the correct ones
Your Thoughts Welcome.
Click to expand...
Click to collapse
My thinking is that perhaps the /devices/mtk-msdc.0/11230000.MSDC0 is for use with META mode as it points to a device rather than a partition, i.e. the whole NAND memory. Not 100% about that... it doesn't make much sense that META mode is controlled by boot.img but that seems to be the case (~ half the .rc's are for meta mode (factory and meta ones)), which would mean that a bad boot.img flash (and recovery.img), would result in a true brick - there isn't a mask mode/drivers for
MTK afaik.
HypoTurtle said:
My thinking is that perhaps the /devices/mtk-msdc.0/11230000.MSDC0 is for use with META mode as it points to a device rather than a partition, i.e. the whole NAND memory. Not 100% about that... it doesn't make much sense that META mode is controlled by boot.img but that seems to be the case (~ half the .rc's are for meta mode (factory and meta ones)), which would mean that a bad boot.img flash (and recovery.img), would result in a true brick - there isn't a mask mode/drivers for
MTK afaik.
Click to expand...
Click to collapse
@hanuma
The cofface recovery is a e3 recovery and yes it seems that a lot of meta stuff is in there too.
The meta stuff is probably to accommodate OTA updates maybe (Just a guess )
I think we should be able to define things how we want.......
cofface has this for one of the volds.
Code:
/devices/platform/mt_usb auto auto defaults voldmanaged=usbdisk:auto
Here are the full readouts. mount, df, etc for your info.
Code:
[email protected]_e:/ # mount
mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered
0 0
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0
0
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,comm
it=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,comm
it=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/customimg /custom ext4 rw,seclabel,relatime,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:129 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=00
07,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:129 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,al
low_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]_e:/ #
[email protected]_e:/ # ls -la /dev/block/mmcblk*
ls -la /dev/block/mmcblk*
brw-rw---- root system 179, 0 2015-01-26 17:24 mmcblk0
brw-rw---- root system 179, 32 2015-01-26 17:24 mmcblk0boot0
brw------- root root 179, 64 2015-01-26 17:24 mmcblk0boot1
brw-rw---- root system 179, 1 2015-01-26 17:24 mmcblk0p1
brw-rw---- root system 179, 10 2015-01-26 17:24 mmcblk0p10
brw-rw---- root system 179, 11 2015-01-26 17:24 mmcblk0p11
brw------- root root 179, 12 2015-01-26 17:24 mmcblk0p12
brw------- root root 179, 13 2015-01-26 17:24 mmcblk0p13
brw------- root root 179, 14 2015-01-26 17:24 mmcblk0p14
brw------- root root 179, 15 2015-01-26 17:24 mmcblk0p15
brw------- root root 179, 16 2015-01-26 17:24 mmcblk0p16
brw------- root root 179, 17 2015-01-26 17:24 mmcblk0p17
brw------- root root 179, 18 2015-01-26 17:24 mmcblk0p18
brw------- root root 179, 19 2015-01-26 17:24 mmcblk0p19
brw-rw---- root system 179, 2 2015-01-26 17:24 mmcblk0p2
brw------- root root 179, 20 2015-01-26 17:24 mmcblk0p20
brw------- root root 179, 3 2015-01-26 17:24 mmcblk0p3
brw------- root root 179, 4 2015-01-26 17:24 mmcblk0p4
brw-rw---- root system 179, 5 2015-01-26 17:24 mmcblk0p5
brw------- root root 179, 6 2015-01-26 17:24 mmcblk0p6
brw-r----- root system 179, 7 2015-01-26 17:24 mmcblk0p7
brw-rw---- root system 179, 8 2015-01-26 17:24 mmcblk0p8
brw-r----- root system 179, 9 2015-01-26 17:24 mmcblk0p9
brw------- root root 179, 96 2015-01-26 17:24 mmcblk0rpmb
brw------- root root 179, 128 2015-01-26 17:24 mmcblk1
brw------- root root 179, 129 2015-01-26 17:24 mmcblk1p1
brw------- root root 179, 130 2015-01-26 17:24 mmcblk1p2
[email protected]_e:/ #
[email protected]_e:/ # df
df
Filesystem Size Used Free Blksize
/dev 958.1M 128.0K 958.0M 4096
/sys/fs/cgroup 958.1M 12.0K 958.1M 4096
/mnt/secure 958.1M 0.0K 958.1M 4096
/mnt/asec 958.1M 0.0K 958.1M 4096
/mnt/obb 958.1M 0.0K 958.1M 4096
/system 1.2G 951.9M 318.9M 4096
/data 12.5G 1.8G 10.7G 4096
/cache 105.3M 712.0K 104.6M 4096
/protect_f 4.8M 56.0K 4.8M 4096
/protect_s 4.8M 116.0K 4.7M 4096
/mnt/cd-rom 1.2M 1.2M 0.0K 2048
/custom 290.6M 45.5M 245.1M 4096
/storage/sdcard1 12.5G 1.8G 10.6G 4096
/mnt/media_rw/sdcard0 25.0G 4.2G 20.8G 32768
/mnt/secure/asec 25.0G 4.2G 20.8G 32768
/storage/sdcard0 25.0G 4.2G 20.8G 32768
[email protected]_e:/ #
[email protected]_e:/ # ls -al /dev/block/platform/mtk-msdc.0/by-name
ls -al /dev/block/platform/mtk-msdc.0/by-name
lrwxrwxrwx root root 2010-01-01 08:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2010-01-01 08:03 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2010-01-01 08:03 custom -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2010-01-01 08:03 expdb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2010-01-01 08:03 flashinfo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2010-01-01 08:03 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2010-01-01 08:03 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2010-01-01 08:03 metadata -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2010-01-01 08:03 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2010-01-01 08:03 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2010-01-01 08:03 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2010-01-01 08:03 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2010-01-01 08:03 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2010-01-01 08:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2010-01-01 08:03 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2010-01-01 08:03 secro -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2010-01-01 08:03 system -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2010-01-01 08:03 tee1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2010-01-01 08:03 tee2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2010-01-01 08:03 userdata -> /dev/block/mmcblk0p19
Things to do:
1. Make external_sd = mmcblk1p1 = sdcard0 default for the backups.
2. add sd_ext = mmcblk1p2 to backup options
3. Get sdcard1 defined as internal_sd
4. Mount Both if possible to upon connection to PC . (If only one then external_sd is preferred by me) Thoughts welcome on this.
5. I really need sleep !!!! lol
bigrammy said:
@hanuma
The cofface recovery is a e3 recovery and yes it seems that a lot of meta stuff is in there too.
The meta stuff is probably to accommodate OTA updates maybe (Just a guess )
Things to do:
1. Make external_sd = mmcblk1p1 = sdcard0 default for the backups.
2. add sd_ext = mmcblk1p2 to backup options
3. Get sdcard1 defined as internal_sd
4. Mount Both if possible to upon connection to PC . (If only one then external_sd is preferred by me) Thoughts welcome on this.
5. I really need sleep !!!! lol
Click to expand...
Click to collapse
Could be for FOTA I suppose... tried to look though /system/bin/fotabinder; but couldn't see much other than a reboot call.
/devices/platform/mt_usb is a usb device I believe (usb drive attached to microusb).
So for reference.
From boot.img
External SDcard
/dev/block/vold/179:129 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=00
/mnt/media_rw/sdcard0 25.0G 4.2G 20.8G 32768
/storage/sdcard0 25.0G 4.2G 20.8G 32768
Internal SDcard (data/media)
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/data 12.5G 1.8G 10.7G 4096
/storage/sdcard1 12.5G 1.8G 10.6G 4096
These are set in ramdisk.
fstab (unsure if used for normal boot - but might be used by vold)
Code:
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
Bits and pieces from .rc's
Code:
on post-fs-data
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0770 media_rw media_rw
chown media_rw media_rw /data/media
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib:/custom/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ANDROID_STORAGE /storage
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-tablet.jar:/system/framework/dolby_ds.jar
export BOOTCLASSPATH_EX /system/framework/mediatek-op.jar
mkdir /mnt/media_rw/sdcard0 0700 media_rw media_rw
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard0 0700 root root
mkdir /storage/sdcard1 0700 root root
export EXTERNAL_STORAGE /storage/sdcard0
# Support legacy paths
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
symlink /storage/sdcard1 /mnt/sdcard2
on fs
mount_all /fstab
setprop ro.crypto.fuse_sdcard true
service sdcard /system/bin/sdcard -u 1023 -g 1023 -d /data/media /storage/sdcard0
class late_start
service fuse_sdcard0 /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/sdcard0 /storage/sdcard0 <<<
class late_start <<<
disabled <<<
<<< These two are disabled
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1 <<<
class late_start <<<
disabled <<<
on boot
chown root /remount.sh <<<
chmod 700 /remount.sh <<< Not sure why this is here
exec /remount.sh <<<
service met_log_d /system/bin/met_log_d
class main
# Refer to http://source.android.com/devices/tech/storage/index.html
# It said, "Starting in Android 4.4, multiple external storage devices are surfaced to developers through
# Context.getExternalFilesDirs(), Context.getExternalCacheDirs(), and Context.getObbDirs().
# External storage devices surfaced through these APIs must be a semi-permanent part of the device (such as an SD card slot in a battery compartment).
# Developers expect data stored in these locations to be available over long periods of time."
# Therefore, if the target has the SD card slot in a battery compartment, we need to specify SECONDARY_STORAGE (*** UN-Comment the following command ***)
#
# export SECONDARY_STORAGE /storage/sdcard1
From recovery.img
init.rc
Code:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /storage/sdcard1
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard1 0700 root root
symlink /storage/sdcard1 /mnt/sdcard2
on boot
service vold /sbin/minivold
socket vold stream 0660 root mount
ioprio be 2
seclabel u:r:recovery:s0
# virtual sdcard daemon running as media_rw (1023)
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled
fstab (line probably not used by recovery)
Code:
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
Well, I came here by chance and saw you've ported a recovery
Good to see this. Bad that those guys from taiwan101 or so, didn't keep my credential in recovery.
I helped SevenMaxs to solve mounting both sdcards in his device (a mt6752) and that one has same sdcard paths. So if you replace this:
Code:
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
with this:
Code:
/devices/mtk-msdc.0/11240000.MSDC1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
in fstab and recovery.fstab it will work (both sdcards not only the internal).
No change in init.rc. I mean on this (which is my solution for mt6595 taken by those guys):
Code:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /storage/sdcard1
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard1 0700 root root
symlink /storage/sdcard1 /mnt/sdcard2
on boot
service vold /sbin/minivold
socket vold stream 0660 root mount
ioprio be 2
seclabel u:r:recovery:s0
# virtual sdcard daemon running as media_rw (1023)
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled
And you should know that you can't switch sdcard0 with sdcard1 (internal with external) in CWM if internal is emulated. As you saw it doesn't have to be defined on fstab at all (if you define it as in stock recovery it won't work), and by default CWM will asign it to sdcard0, and you can't change that. If you want to place backups in external sdcard, just select "backup to /storage/sdcard1" from menu. I guess you are too much used with the "old" cwm, jellybean version with sftab1 Well things are changed now for kitkat using fstab2, and to be honest I don't understand why they did it. Twrp still uses fstab1 and is doing just fine
Later edit: Guys you can't relay on stock recovery or other one based on stock. The CWM works different (no fstab or init.rc from stock recovery will help you). One other thing you should know, if you define the usbdisk or otg or whatever its name is in CWM fstabs, you will loose the USB Mass Storage mounting to PC function, because CWM only allow one USB connection. All these are already explained by me in my thread for porting recoveries, and more exactly in the new guide composed of only with pictures.
carliv said:
Well, I came here by chance and saw you've ported a recovery
in fstab and recovery.fstab it will work (both sdcards not only the internal).
No change in init.rc. I mean on this (which is my solution for mt6595 taken by those guys):
And you should know that you can't switch sdcard0 with sdcard1 (internal with external) in CWM if internal is emulated. As you saw it doesn't have to be defined on fstab at all (if you define it as in stock recovery it won't work), and by default CWM will asign it to sdcard0, and you can't change that. If you want to place backups in external sdcard, just select "backup to /storage/sdcard1" from menu. I guess you are too much used with the "old" cwm, jellybean version with sftab1 Well things are changed now for kitkat using fstab2, and to be honest I don't understand why they did it. Twrp still uses fstab1 and is doing just fine
Later edit: Guys you can't relay on stock recovery or other one based on stock. The CWM works different (no fstab or init.rc from stock recovery will help you). One other thing you should know, if you define the usbdisk or otg or whatever its name is in CWM fstabs, you will loose the USB Mass Storage mounting to PC function, because CWM only allow one USB connection. All these are already explained by me in my thread for porting recoveries, and more exactly in the new guide composed of only with pictures.
Click to expand...
Click to collapse
Thanks for that @carliv ... still waiting for my device to run this recovery was wasn't sure what version CWM it was.
I'm guessing minivold is why you can't simply switch SECONDARY_STORAGE with EXTERNAL_STORAGE... It is a moot point though if as you say "backup to /storage/sdcard1" is there as an option.
Edit. @carliv is the symlink /storage/sdcard1 /mnt/sdcard2 bit right? Or should it be /mnt/sdcard1 ?
HypoTurtle said:
Thanks for that @carliv ... still waiting for my device to run this recovery was wasn't sure what version CWM it was.
I'm guessing minivold is why you can't simply switch SECONDARY_STORAGE with EXTERNAL_STORAGE... It is a moot point though if as you say "backup to /storage/sdcard1" is there as an option.
Edit. @carliv is the symlink /storage/sdcard1 /mnt/sdcard2 bit right? Or should it be /mnt/sdcard1 ?
Click to expand...
Click to collapse
First CWM will check for sdcard0 on fstab to see if matches any defined voldmanaged entry and if it's not it will assume is a data/media sdcard and assign it sdcard (aka storage/sdcard0) path. To change that you need to build the recovery and to do that in source code. I guess all this fuss was started by google when they designed kitkat for their devices without external sdcard.
Yes, /mn/sdcard2 is right for /storage/sdcard1 because /mnt/sdcard (<<<no 0 here) is for /storage/sdcard0 - at least that's in all the phones I saw, but maybe yours is different. If you open the mnt folder with a root explorer do you see any sdcard1 there? That will be a first for me to hear such thing.
carliv said:
First CWM will check for sdcard0 on fstab to see if matches any defined voldmanaged entry and if it's not it will assume is a data/media sdcard and assign it sdcard (aka storage/sdcard0) path. To change that you need to build the recovery and to do that in source code. I guess all this fuss was started by google when they designed kitkat for their devices without external sdcard.
Yes, /mn/sdcard2 is right for /storage/sdcard1 because /mnt/sdcard (<<<no 0 here) is for /storage/sdcard0 - at least that's in all the phones I saw, but maybe yours is different. If you open the mnt folder with a root explorer do you see any sdcard1 there? That will be a first for me to hear such thing.
Click to expand...
Click to collapse
Would I be right in thinking then that the backup location is hardcoded in the recovery to something like /storage/sdcard0? I was thinking that it might have been backup => $EXTERNAL_STORAGE (if that's even possible) so that a simple switch external/secondary in init.rc would point the backup to /storage/sdcard1 instead, it's been a while since I've compiled anything, might poke through the code though.
HypoTurtle said:
Would I be right in thinking then that the backup location is hardcoded in the recovery to something like /storage/sdcard0? I was thinking that it might have been backup => $EXTERNAL_STORAGE (if that's even possible) so that a simple switch external/secondary in init.rc would point the backup to /storage/sdcard1 instead, it's been a while since I've compiled anything, might poke through the code though.
Click to expand...
Click to collapse
This is only for phones with internal sdcard on data/media. If you have a phone with internal sdcard as a "fat" partition (as I do) you can switch them as much as you like, but not from EXTERNAL and SECONDARY storage; it has to be done in fstabs switching voldmanaged:sdcard0 to external and sdcard1 to internal. In kitkat cwm those defines EXTERNAL and SECONDARY STORAGE can be removed and the recovery will work, or you can let only EXTERNAL to sdcard as in CWM official init.rc. The reason I added those modifications, including mnt/sdcards and other from init.rc was for USB Mass Storage mount to PC. Stock CWM init.rc will work with right fstabs but on connecting to PC it will mount only the external sdcard; my modds make it possible to mount both sdcards.
In this thread, i will explain how to get a fully working fastboot mode to be able to flash any unsigned rom, recovery....
This device rooting method its, kinda particular, Boot.img has some files that need to be modified in order to get permanent root on the device.
Here i will show you what i mean.
Inside boot.img:
fstab.qcom
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,check,encryptable=footer
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 nosuid,nodev,barrier=1 wait,check
/devices/msm_sdcc.2/mmc_host /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto
#/dev/block/mmcblk0p11 /system ext4 ro,barrier=1 wait
#/dev/block/mmcblk0p12 /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,check,encryptable=footer
init.qcom.rc:
import init.qcom.usb.rc
import init.target.rc
on early-init
mount debugfs debugfs /sys/kernel/debug
on init
# Set permissions for persist partition
mkdir /persist 0771 system system
# See storage config details at http://source.android.com/tech/storage/
mkdir /mnt/shell/emulated 0700 shell shell
#mkdir /storage 0050 system sdcard_r
mkdir /storage 0755 system sdcard_r
mkdir /storage/emulated 0555 root root
#mkdir /storage/emulated/legacy 0555 root root
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard0 0555 root root
mkdir /storage/sdcard1 0700 root root
#export EXTERNAL_STORAGE /storage/emulated/legacy
export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /storage/sdcard1
export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
export EMULATED_STORAGE_TARGET /storage/emulated
# Support legacy paths
#symlink /storage/emulated/legacy /sdcard
#symlink /storage/emulated/legacy /mnt/sdcard
#symlink /storage/emulated/legacy /storage/sdcard0
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
on early-boot
# set RLIMIT_MEMLOCK to 64MB
setrlimit 8 67108864 67108864
# Allow subsystem (modem etc) debugging
write /sys/module/subsystem_restart/parameters/enable_debug ${persist.sys.ssr.enable_debug}
write /sys/kernel/boot_adsp/boot 1
exec /system/bin/sh /init.qcom.early_boot.sh ${ro.board.platform}
exec /system/bin/sh /init.qcom.syspart_fixup.sh ${ro.board.platform} ${ro.serialno}
on boot
chown bluetooth bluetooth /sys/module/bluetooth_power/parameters/power
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
chown bluetooth bluetooth /proc/bluetooth/sleep/proto
chown bluetooth bluetooth /sys/module/hci_uart/parameters/ath_lpm
chown bluetooth bluetooth /sys/module/hci_uart/parameters/ath_btwrite
chown system system /sys/module/sco/parameters/disable_esco
chown bluetooth bluetooth /sys/module/hci_smd/parameters/hcismd_set
chmod 0660 /sys/module/bluetooth_power/parameters/power
chmod 0660 /sys/module/hci_smd/parameters/hcismd_set
chmod 0660 /sys/class/rfkill/rfkill0/state
chmod 0660 /proc/bluetooth/sleep/proto
chown bluetooth bluetooth /dev/ttyHS0
chmod 0660 /sys/module/hci_uart/parameters/ath_lpm
chmod 0660 /sys/module/hci_uart/parameters/ath_btwrite
chmod 0660 /dev/ttyHS0
chown bluetooth bluetooth /sys/devices/platform/msm_serial_hs.0/clock
chmod 0660 /sys/devices/platform/msm_serial_hs.0/clock
chmod 0660 /dev/ttyHS2
chown bluetooth bluetooth /dev/ttyHS2
#Create QMUX deamon socket area
mkdir /dev/socket/qmux_radio 0770 radio radio
chmod 2770 /dev/socket/qmux_radio
mkdir /dev/socket/qmux_audio 0770 media audio
chmod 2770 /dev/socket/qmux_audio
mkdir /dev/socket/qmux_bluetooth 0770 bluetooth bluetooth
chmod 2770 /dev/socket/qmux_bluetooth
mkdir /dev/socket/qmux_gps 0770 gps gps
chmod 2770 /dev/socket/qmux_gps
setprop wifi.interface wlan0
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.wifi 524288,2097152,4194304,262144,524288,1048576
setprop ro.telephony.call_ring.multiple false
#Set SUID bit for usbhub
chmod 4755 /system/bin/usbhub
chmod 755 /system/bin/usbhub_init
#Remove SUID bit for iproute2 ip tool
chmod 0755 /system/bin/ip
chmod 0444 /sys/devices/platform/msm_hsusb/gadget/usb_state
#For bridgemgr daemon to inform the USB driver of the correct transport
chown radio radio /sys/class/android_usb/f_rmnet_smd_sdio/transport
# 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.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,1220608,4096,16384,1220608
setprop net.tcp.buffersize.hsupa 4094,87380,1220608,4096,16384,1220608
setprop net.tcp.buffersize.hsdpa 4094,87380,1220608,4096,16384,1220608
setprop net.tcp.buffersize.hspap 4094,87380,1220608,4096,16384,1220608
setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
setprop net.tcp.buffersize.evdo 4094,87380,262144,4096,16384,262144
# Assign TCP buffer thresholds to be ceiling value of technology maximums
# Increased technology maximums should be reflected here.
write /proc/sys/net/core/rmem_max 2097152
write /proc/sys/net/core/wmem_max 2097152
#To allow interfaces to get v6 address when tethering is enabled
write /proc/sys/net/ipv6/conf/rmnet0/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet1/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet2/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet3/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet4/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet5/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet6/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet7/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio0/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio1/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio2/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio3/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio4/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio5/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio6/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_sdio7/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_usb0/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_usb1/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_usb2/accept_ra 2
write /proc/sys/net/ipv6/conf/rmnet_usb3/accept_ra 2
# To prevent out of order acknowledgements from making
# connection tracking to treat them as not belonging to
# the connection they belong to.
# Otherwise, a weird issue happens in which some long
# connections on high-throughput links get dropped when
# an ack packet comes out of order
write /proc/sys/net/netfilter/nf_conntrack_tcp_be_liberal 1
# NFC local data and nfcee xml storage
mkdir /data/nfc 0770 nfc nfc
mkdir /data/nfc/param 0770 nfc nfc
# Set the console loglevel to < KERN_INFO
# Set the default message loglevel to KERN_INFO
write /proc/sys/kernel/printk "6 6 1 7"
# msm specific files that need to be created on /data
on post-fs-data
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0770 media_rw media_rw
chown media_rw media_rw /data/media
mkdir /data/misc/bluetooth 0770 bluetooth bluetooth
# Create the directories used by the Wireless subsystem
mkdir /data/misc/wifi 0770 wifi wifi
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/wifi/wpa_supplicant 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
chown dhcp dhcp /data/misc/dhcp
# Create the directories used by CnE subsystem
mkdir /data/connectivity 0771 system system
chown system system /data/connectivity
mkdir /data/connectivity/nsrm 0771 system system
chown system system /data/connectivity/nsrm
# Create directory used by audio subsystem
mkdir /data/misc/audio 0770 audio audio
# Mounting of persist is moved to 'on emmc-fs' and 'on fs' sections
# We chown/chmod /persist again so because mount is run as root + defaults
chown system system /persist
chmod 0771 /persist
chmod 0664 /sys/devices/platform/msm_sdcc.1/polling
chmod 0664 /sys/devices/platform/msm_sdcc.2/polling
chmod 0664 /sys/devices/platform/msm_sdcc.3/polling
chmod 0664 /sys/devices/platform/msm_sdcc.4/polling
# Chown polling nodes as needed from UI running on system server
chown system system /sys/devices/platform/msm_sdcc.1/polling
chown system system /sys/devices/platform/msm_sdcc.2/polling
chown system system /sys/devices/platform/msm_sdcc.3/polling
chown system system /sys/devices/platform/msm_sdcc.4/polling
#Create the symlink to qcn wpa_supplicant folder for ar6000 wpa_supplicant
mkdir /data/system 0775 system system
#symlink /data/misc/wifi/wpa_supplicant /data/system/wpa_supplicant
#Create directories for gpsone_daemon services
mkdir /data/misc/gpsone_d 0770 system gps
#Create directories for QuIPS
mkdir /data/misc/quipc 0770 gps system
#Create directories for Location services
mkdir /data/misc/location 0770 gps gps
mkdir /data/misc/location/mq 0770 gps gps
mkdir /data/misc/location/xtwifi 0770 gps gps
#Create directory from IMS services
mkdir /data/shared 0755
chown system system /data/shared
#Create directory for FOTA
mkdir /data/fota 0771
chown system system /data/fota
#Create directory for hostapd
mkdir /data/hostapd 0770 system wifi
# Create /data/time folder for time-services
mkdir /data/time/ 0700 system system
mkdir /data/audio/ 0770 media audio
setprop vold.post_fs_data_done 1
#Create a folder for SRS to be able to create a usercfg file
mkdir /data/data/media 0770 media media
# Export GPIO56 for fusion targets to enable/disable hub
service usbhub_init /system/bin/usbhub_init
class late_start
user root
disabled
oneshot
service qcomsysd /system/bin/qcom-system-daemon
class main
on propertyersist.radio.atfwd.start=false
stop atfwd
# corefile limit and ETB enabling
on propertyersist.debug.trace=1
mkdir /data/core 0777 root root
write /proc/sys/kernel/core_pattern "/data/core/%E.%p.%e"
write /sys/devices/system/cpu/cpu1/online 1
write /sys/devices/system/cpu/cpu2/online 1
write /sys/devices/system/cpu/cpu3/online 1
write /sys/bus/coresight/devices/coresight-etm0/enable 0
write /sys/bus/coresight/devices/coresight-etm1/enable 0
write /sys/bus/coresight/devices/coresight-etm2/enable 0
write /sys/bus/coresight/devices/coresight-etm3/enable 0
write /sys/bus/coresight/devices/coresight-etm0/reset 1
write /sys/bus/coresight/devices/coresight-etm1/reset 1
write /sys/bus/coresight/devices/coresight-etm2/reset 1
write /sys/bus/coresight/devices/coresight-etm3/reset 1
write /sys/bus/coresight/devices/coresight-etm0/enable 1
write /sys/bus/coresight/devices/coresight-etm1/enable 1
write /sys/bus/coresight/devices/coresight-etm2/enable 1
write /sys/bus/coresight/devices/coresight-etm3/enable 1
on property:ro.board.platform=msm7630_fusion
start usbhub_init
on property:init.svc.wpa_supplicant=stopped
stop dhcpcd
on property:bluetooth.isEnabled=true
start btwlancoex
write /sys/class/bluetooth/hci0/idle_timeout 7000
on property:bluetooth.sap.status=running
start bt-sap
on property:bluetooth.sap.status=stopped
stop bt-sap
on property:bluetooth.dun.status=running
start bt-dun
on property:bluetooth.dun.status=stopped
stop bt-dun
on property:ro.bluetooth.ftm_enabled=true
start ftmd
service qcom-c_core-sh /system/bin/sh /init.qcom.class_core.sh
class core
user root
oneshot
service qcom-c_main-sh /system/bin/sh /init.class_main.sh
class main
user root
oneshot
service ril-qmi /system/bin/sh /init.qcom.ril.sh
class main
user root
oneshot
on property:vold.decrypt=trigger_restart_framework
start qcom-c_main-sh
start config_bluetooth
on propertyersist.env.fastdorm.enabled=true
setprop persist.radio.data_no_toggle 1
service cnd /system/bin/cnd
class late_start
socket cnd stream 660 root inet
service irsc_util /system/bin/logwrapper /system/bin/irsc_util "/etc/sec_config"
class main
user root
oneshot
service rmt_storage /system/bin/rmt_storage
class core
user root
disabled
on property:ro.boot.emmc=true
start rmt_storage
service rfs_access /system/bin/rfs_access
class core
user system
group system net_raw
on property:ro.boot.emmc=true
start rfs_access
on property:bluetooth.start_hci=true
start start_hci_filter
on property:bluetooth.start_hci=false
stop start_hci_filter
service start_hci_filter /system/bin/wcnss_filter
class late_start
user bluetooth
group bluetooth
disabled
service config_bluetooth /system/bin/sh /system/etc/init.qcom.bt.sh "onboot"
class core
user root
oneshot
service hciattach /system/bin/sh /system/etc/init.qcom.bt.sh
class late_start
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot
service bttestmode /system/bin/sh /system/bin/bt_testmode_new.sh
class late_start
user root
oneshot
disabled
on property:bluetooth.hciattach=true
start hciattach
on property:bluetooth.hciattach=false
setprop bluetooth.status off
service hciattach_ath3k /system/bin/sh /system/etc/init.ath3k.bt.sh
class late_start
user bluetooth
group system bluetooth net_bt_admin misc
disabled
oneshot
service bt-dun /system/bin/dun-server /dev/smd7 /dev/rfcomm0
class late_start
user bluetooth
group bluetooth net_bt_admin inet
disabled
oneshot
service bt-sap /system/bin/sapd 15
user bluetooth
group bluetooth net_bt_admin
class late_start
disabled
oneshot
service ftmd /system/bin/logwrapper /system/bin/ftmdaemon
class late_start
user root
group bluetooth net_bt_admin misc net_bt_stack qcom_diag
disabled
oneshot
service bridgemgrd /system/bin/bridgemgrd
class late_start
user radio
group radio qcom_diag
disabled
service port-bridge /system/bin/port-bridge /dev/smd0 /dev/ttyGS0
class late_start
user system
group system inet
disabled
service qmiproxy /system/bin/qmiproxy
class main
user radio
group radio qcom_diag
disabled
# QMUX must be in multiple groups to support external process connections
service qmuxd /system/bin/qmuxd
class main
user radio
group radio audio bluetooth gps qcom_diag
disabled
service netmgrd /system/bin/netmgrd
class main
disabled
#added by zte_chenhui for sensor reg_begin
#service sensor-sh /system/bin/sh /init.sensor.reg.sh
# class late_start
# oneshot
#added by chenhui for sensor reg_end
service sensors /system/bin/sensors.qcom
class late_start
user root
group root
disabled
on property:ro.use_data_netmgrd=false
# netmgr not supported on specific target
stop netmgrd
# Adjust socket buffer to enlarge TCP receive window for high bandwidth
# but only if ro.data.large_tcp_window_size property is set.
on property:ro.data.large_tcp_window_size=true
write /proc/sys/net/ipv4/tcp_adv_win_scale 2
service btwlancoex /system/bin/sh /system/etc/init.qcom.coex.sh
class late_start
user bluetooth
group bluetooth net_bt_admin inet net_admin net_raw
disabled
oneshot
service amp_init /system/bin/amploader -i
class late_start
user root
disabled
oneshot
service amp_load /system/bin/amploader -l 7000
class late_start
user root
disabled
oneshot
service amp_unload /system/bin/amploader -u
class late_start
user root
disabled
oneshot
service p2p_supplicant /system/bin/wpa_supplicant \
-ip2p0 -Dnl80211 -c/data/misc/wifi/p2p_supplicant.conf \
-I/system/etc/wifi/p2p_supplicant_overlay.conf -N \
-iwlan0 -Dnl80211 -c/data/misc/wifi/wpa_supplicant.conf \
-I/system/etc/wifi/wpa_supplicant_overlay.conf \
-O/data/misc/wifi/sockets -puse_p2p_group_interface=1 -dddd \
-e/data/misc/wifi/entropy.bin [email protected]:wpa_wlan0
# 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
service wpa_supplicant /system/bin/wpa_supplicant \
-iwlan0 -Dnl80211 -c/data/misc/wifi/wpa_supplicant.conf \
-I/system/etc/wifi/wpa_supplicant_overlay.conf \
-O/data/misc/wifi/sockets -dddd \
-e/data/misc/wifi/entropy.bin [email protected]:wpa_wlan0
# 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
service dhcpcd_wlan0 /system/bin/dhcpcd -ABKLG
class late_start
disabled
oneshot
service dhcpcd_p2p /system/bin/dhcpcd -ABKLG
class late_start
disabled
oneshot
service iprenew_wlan0 /system/bin/dhcpcd -n
class late_start
disabled
oneshot
service iprenew_p2p /system/bin/dhcpcd -n
class late_start
disabled
oneshot
# zte_modify by zhangqingli for wifi FTM test 20140217 start
service ptt_socket_app /system/bin/ptt_socket_app -d
#class main
user root
group root
disabled
oneshot
service ptt_ffbm /system/bin/ptt_socket_app -f -d
#class main
user root
group root
disabled
oneshot
# zte_modify by zhangqingli for wifi FTM test 20140217 end
service dhcpcd_bt-pan /system/bin/dhcpcd -BKLG
class late_start
disabled
oneshot
service iprenew_bt-pan /system/bin/dhcpcd -n
class late_start
disabled
oneshot
service dhcpcd_bnep0 /system/bin/dhcpcd -BKLG
disabled
oneshot
service dhcpcd_bnep1 /system/bin/dhcpcd -BKLG
disabled
oneshot
service dhcpcd_bnep2 /system/bin/dhcpcd -BKLG
disabled
oneshot
service dhcpcd_bnep3 /system/bin/dhcpcd -BKLG
disabled
oneshot
service dhcpcd_bnep4 /system/bin/dhcpcd -BKLG
disabled
oneshot
service gpsone_daemon /system/bin/gpsone_daemon
class late_start
user gps
group gps inet net_raw
disabled
service quipc_igsn /system/bin/quipc_igsn
class late_start
user gps
group inet gps qcom_diag
disabled
service quipc_main /system/bin/quipc_main
class late_start
user gps
group gps net_admin wifi inet qcom_diag
disabled
service location_mq /system/bin/location-mq
class late_start
user gps
group gps
disabled
service xtwifi_inet /system/bin/xtwifi-inet-agent
class late_start
user gps
group inet gps
disabled
service xtwifi_client /system/bin/xtwifi-client
class late_start
user gps
group net_admin wifi inet gps
disabled
service lowi-server /system/bin/lowi-server
class late_start
user gps
group gps net_admin wifi inet qcom_diag
disabled
service fm_dl /system/bin/sh /system/etc/init.qcom.fm.sh
class late_start
user root
group system fm_radio
disabled
oneshot
on property:crypto.driver.load=1
insmod /system/lib/modules/qce.ko
insmod /system/lib/modules/qcedev.ko
on property:crypto.driver.load=0
exec /system/bin/rmmod qcedev.ko
exec /system/bin/rmmod qce.ko
service drmdiag /system/bin/drmdiagapp
class late_start
user root
disabled
oneshot
on property:drmdiag.load=1
start drmdiag
on property:drmdiag.load=0
stop drmdiag
service qcom-sh /system/bin/sh /init.qcom.sh
class late_start
user root
oneshot
service qcom-post-boot /system/bin/sh /system/etc/init.qcom.post_boot.sh
class late_start
user root
disabled
oneshot
service wifi-sdio-on /system/bin/sh /system/etc/init.qcom.sdio.sh
class late_start
group wifi inet
disabled
oneshot
service wifi-crda /system/bin/sh /system/etc/init.crda.sh
class late_start
user root
disabled
oneshot
on property:sys.boot_completed=1
start qcom-post-boot
service atfwd /system/bin/ATFWD-daemon
class late_start
user system
group system radio
service hdmid /system/bin/hdmid
class late_start
socket hdmid stream 0660 root system graphics
disabled
service ppd /system/bin/mm-pp-daemon
class late_start
user system
socket pps stream 0660 system system graphics
group system graphics
# modify the dir to /data/misc/wifi/hostapd.conf in hostapd in code
#service hostapd /system/bin/hostapd -dddd /data/hostapd/hostapd.conf
# class late_start
# user root
# group root
# oneshot
# disabled
service ds_fmc_appd /system/bin/ds_fmc_appd -p "rmnet0" -D
class late_start
group radio wifi inet
disabled
oneshot
on propertyersist.data.ds_fmc_app.mode=1
start ds_fmc_appd
service ims_regmanager /system/bin/exe-ims-regmanagerprocessnative
class late_start
group net_bt_admin inet radio wifi
disabled
on propertyersist.ims.regmanager.mode=1
start ims_regmanager
on property:ro.data.large_tcp_window_size=true
# Adjust socket buffer to enlarge TCP receive window for high bandwidth (e.g. DO-RevB)
write /proc/sys/net/ipv4/tcp_adv_win_scale 2
service battery_monitor /system/bin/battery_monitor
user system
group system
disabled
service ril-daemon1 /system/bin/rild -c 1
class main
socket rild1 stream 660 root radio
socket rild-debug1 stream 660 radio system
user root
disabled
group radio cache inet misc audio sdcard_r sdcard_rw diag qcom_diag log
service ril-daemon2 /system/bin/rild -c 2
class main
socket rild2 stream 660 root radio
socket rild-debug2 stream 660 radio system
user root
disabled
group radio cache inet misc audio sdcard_r sdcard_rw diag qcom_diag log
service profiler_daemon /system/bin/profiler_daemon
class late_start
user root
group root
disabled
service sdcard /system/bin/sdcard -l /data/media /mnt/shell/emulated 1023 1023
class late_start
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled
# Binding fuse mount point to /storage/emulated/legacy
#on property:init.svc.sdcard=running
# modified by xiongping to bind fuse mount point to /storage/edmulated/legacy when emulated sdcard is mounted
on property:init.emulated.sdcard=1
wait /mnt/shell/emulated/0
#mount none /mnt/shell/emulated/0 /storage/emulated/legacy bind
mount none /mnt/shell/emulated/0 /storage/sdcard0 bind
service hcidump /system/bin/sh /system/etc/hcidump.sh
user bluetooth
group bluetooth system net_bt_admin net_admin
disabled
oneshot
service charger /charger
class charger
service ssr_diag /system/bin/ssr_diag
class late_start
user system
group system
# SSR setting
on propertyersist.sys.ssr.restart_level=*
exec /system/bin/sh /init.qcom.ssr.sh ${persist.sys.ssr.restart_level}
# Define fastmmi
service fastmmi /system/bin/mmi
user root
group root
disabled
service fastmmisrv /system/bin/sh /init.qcom.factory.sh
user root
disabled
oneshot
on ffbm
start fastmmisrv
service hvdcp /system/bin/hvdcp
class core
user root
disabled
on propertyersist.usb.hvdcp.detect=true
start hvdcp
on propertyersist.usb.hvdcp.detect=false
stop hvdcp
service charger_monitor /system/bin/charger_monitor
user system
group system
disabled
service diag_mdlog_start /system/bin/diag_mdlog
class late_start
user sdcard_rw
group system qcom_diag sdcard_rw sdcard_r media_rw
disabled
oneshot
service diag_mdlog_stop /system/bin/diag_mdlog -k
class late_start
user sdcard_rw
group system qcom_diag sdcard_rw sdcard_r media_rw
disabled
oneshot
service qlogd /system/xbin/qlogd
class main
disabled
on propertyersist.sys.qlogd=1
start qlogd
on propertyersist.sys.qlogd=0
stop qlogd
service rootagent /system/bin/sh /system/etc/init.qcom.rootagent.sh
disabled
oneshot
on propertyersist.sys.rootagent=1
start rootagent
on propertyersist.sys.rootagent=0
stop rootagent
This files (and some more) are rewriten everytime the device is restarted, so this boot.img has to be modified in order to get a permanent root.
USE IT AT YOUR OWN RISK, IM NOT RESPONSIBLE FOR ANY POSSIBLE DAMAGE ON YOUR DEVICE.
Let's get to fastboot mode:
I will publish in bottom of the post, links to all the files mentioned here, so everyone can download it.
First of all, we need a temporary root, so we will use Baidu Superroot (Thanks to Investigador Android for tip and link).
After we have root our device (yes, it will be unrooted after reboot), we will install FLASHIFY from Play Store (i will put a link too on bottom).
Now using Flashify we will flash a recovery.img that i posted the link down here.
Dont try to flash CWM, TWRP and PHILZ from flashify, THEY'RE NOT COMPATIBLE WITH OUR DEVICE.
Now, make a full backup of all data in the device, in order to get root again after reboot, you WILL NEED to reflash the original firmware (unless someone makes a custom recovery, and perma-root).
When you're done, power off your device and keep pressed VOL UP + POWER, in order to get to recovery.
You will notice that the red led stands lighted and the splash screen keeps on screen (Recovery menu will not show), your phone is in Fastboot mode now, bootloader is factory unlocked, so you may flash whatever you want using the well-known fastboot commands.
I will put the original recovery.img, unless you know what you're doing, FLASH the ORIGINAL recovery.img in fastboot mode BEFORE restarting the phone, or you will get fastboot mode everytime you try to start the recovery menu.
Hopes any developer put any interest in this phone now that we can get inside fastboot mode.
DOWNLOADS:
Recovery.img ORIGINAL: https://mega.co.nz/#!p8sGlCQR!GZL71Oi32Zh91JJKtf4oKmGuJDoB7CWwc2fUf4rv_y0
BOOT.img Original: https://mega.co.nz/#!I8EmHbwL!TPEwaTwCECg7Sx0aUouLr6n2NdLkbVxluyhOV_3vkOc
FASTBOOT.IMG: https://mega.co.nz/#!ModilZLL!LaNXonF69XOZvpnUQOlHVSZHjd34jLnJLeWwunuS3aM
Baidu Super root: https://yadi.sk/d/iQlZl0cFeFguR
Flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=es
This research was made based on firmware 7.4 of Orange Hi 4G, here's the link to download it:
https://mega.co.nz/#!ZhlV1ZDZ!WOu0zs_mmG3fD15c5Ko3F73nLfafuiWqsbb3O3OiRE0
Added Perma-root (By Megamejo)
First root app: https://mega.co.nz/#!9ExyEIbL!hnym2y4OhCEd0ugxKXMR7ExwPpDFSm1q-RcrP3Hw3JQ
Second root app : https://mega.co.nz/#!8Yw1HTgL!jwO1Zb7SDTzcYq1gClzXXghs-ck8lhv0sVZmThADPY0
Root with First root app, then uninstall that app from app manager, then install second root BEFORE rebooting the device.
Have fun!
Yours
Algesat.
Thanks for your helpful information
Hopefully some developer do this
Hello!
I've got this device too, it's very difficult root it!!! If any developer help us....
Thanks.
FieldsMA said:
I've got this device too, it's very difficult root it!!! If any developer help us....
Thanks.
Click to expand...
Click to collapse
Actually there's no way to root the device permanently, we only have a temporary root, when you reboots the device the root is gone, and you're forced to reflash the phone in order to get again the temporary root.
Hopes any developer can compile a custom recovery to disable the signature verification (there's no any compatible custom recovery for this phone), and that way we can do something to root this device.
Also, send mails to ZTE to make public the sources of the kernel, like they did in alot of other devices, so we can cook our custom rom.
Permanente root finaly
FieldsMA said:
I've got this device too, it's very difficult root it!!! If any developer help us....
Thanks.
Click to expand...
Click to collapse
I have a permanente root method if someone want i will do a step by step guide.
megamejo said:
I have a permanente root method if someone want i will do a step by step guide.
Click to expand...
Click to collapse
Post it
megamejo said:
I have a permanente root method if someone want i will do a step by step guide.
Click to expand...
Click to collapse
Ok!! Post it!!
Permanent root finaly
We need to root with the first root app and then uninstall when root success, after that we need to root with the second root app in the link below and in order, to get a permanent root.
First root app: https://mega.co.nz/#!9ExyEIbL!hnym2y4OhCEd0ugxKXMR7ExwPpDFSm1q-RcrP3Hw3JQ
Second root app : https://mega.co.nz/#!8Yw1HTgL!jwO1Zb7SDTzcYq1gClzXXghs-ck8lhv0sVZmThADPY0
megamejo said:
We need to root with the first root app and then uninstall when root success, after that we need to root with the second root app in the link below and in order, to get a permanent root.
First root app: https://mega.co.nz/#!9ExyEIbL!hnym2y4OhCEd0ugxKXMR7ExwPpDFSm1q-RcrP3Hw3JQ
Second root app : https://mega.co.nz/#!8Yw1HTgL!jwO1Zb7SDTzcYq1gClzXXghs-ck8lhv0sVZmThADPY0
Click to expand...
Click to collapse
I add the info to the first post, and modify the title, so anyone can get the info easily.
Algesat said:
I add the info to the first post, and modify the title, so anyone can get the info easily.
Click to expand...
Click to collapse
There is a thing, if you reboot after install the first root app you'll can't uninstall the Chinese root app is not important restart the phone, you must not restart; after you root with the first root app uninstall it and, without restart, install the second root app and reroot. After this you must have a permanent root.
megamejo said:
There is a thing, if you reboot after install the first root app you'll can't uninstall the Chinese root app is not important restart the phone, you must not restart; after you root with the first root app uninstall it and, without restart, install the second root app and reroot. After this you must have a permanent root.
Click to expand...
Click to collapse
I have rebooted and it's happened this!there is a solution?
I think there is any solutions try this program and post if work
Sent from my Orange Hi 4G using XDA
---------- Post added at 08:01 PM ---------- Previous post was at 07:52 PM ----------
bubboo said:
I have rebooted and it's happened this!there is a solution?
Click to expand...
Click to collapse
Try this app and post if work
http://gdown.baidu.com/data/wisegame/3fba97063bb4544e/chaojiRootdashi_7.apk
Sent from my Orange Hi 4G using XDA Free mobile app
megamejo said:
I think there is any solutions try this program and post if work
Sent from my Orange Hi 4G using XDA
---------- Post added at 08:01 PM ---------- Previous post was at 07:52 PM ----------
Try this app and post if work
http://gdown.baidu.com/data/wisegame/3fba97063bb4544e/chaojiRootdashi_7.apk
Sent from my Orange Hi 4G using XDA Free mobile app
Click to expand...
Click to collapse
it doesn'work! say me: app not installed !
bubboo said:
it doesn'work! say me: app not installed !
Click to expand...
Click to collapse
In order of that you need to reinstall the firmware of the phone
Sent from my Orange Hi 4G using XDA Free mobile app
megamejo said:
In order of that you need to reinstall the firmware of the phone
Sent from my Orange Hi 4G using XDA Free mobile app
Click to expand...
Click to collapse
i haven't this.when I try install from recovery the upddate.zip in the first post ,say me installation aborted!
bubboo said:
i haven't this.when I try install from recovery the upddate.zip in the first post ,say me installation aborted!
Click to expand...
Click to collapse
Try to download and extract the update.Zip from that link and put it in the root of SD card http://download.ztedevice.com/UpLoadFiles/product/550/4567/soft/2014103116351723.zip
And flash it in the recovery.
Sent from my Orange Hi 4G using XDA Free mobile app
megamejo said:
Try to download and extract the update.Zip from that link and put it in the root of SD card http://download.ztedevice.com/UpLoadFiles/product/550/4567/soft/2014103116351723.zip
And flash it in the recovery.
Sent from my Orange Hi 4G using XDA Free mobile app
Click to expand...
Click to collapse
is this for orange hi 4g or zte b(ade apex2 specificatly?
bubboo said:
is this for orange hi 4g or zte b(ade apex2 specificatly?
Click to expand...
Click to collapse
Yes
Sent from my Orange Hi 4G using XDA Free mobile app
megamejo said:
Yes
Sent from my Orange Hi 4G using XDA Free mobile app
Click to expand...
Click to collapse
because i have a zte blade apex 2, and not orange hi 4g.i try to flash and i can't.i see that in the updater script there are a verification ,and i modified this in way
to not say: "this update is for orange hi 4g ", and proceed to install.after that modification the recovery say me that the file it's not signed.
bubboo said:
because i have a zte blade apex 2, and not orange hi 4g.i try to flash and i can't.i see that in the updater script there are a verification ,and i modified this in way
to not say: "this update is for orange hi 4g ", and proceed to install.after that modification the recovery say me that the file it's not signed.
Click to expand...
Click to collapse
Try to find your firmware here http://www.ztedevice.com/support/selectproduct.html?type=software
Sent from my Orange Hi 4G using XDA Free mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[COLOR="333333"]This is the Bug fix thread for all MTK 6592 & 6582 running CM12.1[/COLOR]
[COLOR="cc3366"]
I need the help off all the porters, to make a full Bug fix list. Just post your fix and i will add it to the list.
Special thanks to CM Team, fire855 and of course to all the supporters.[/COLOR]
-Open Bug fixes-
Gps
Sensors
Or tell me what is missing.
[COLOR="cc3366"]-Network Drop-[/COLOR]
system/bin/rild
system/bin/rildmd2
system/etc/ril/oper.lis
system/lib/libreference-ril.so
system/lib/libril.so
system/lib/librilmtk.so
system/lib/librilmtkmd2.so
system/lib/librilutils.so
system/lib/mtk-ril.so
system/lib/mtk-rilmd2.so
system/etc/firmware <---(Only replace from stock to Cm12.1 Don´t delet the folder in Cm12.1)
[COLOR="cc3366"]-Offline charging-[/COLOR]
system/bin/ipod
system/bin/boot_logo_updater
system/bin/factory
system/lib/libipod.so
system/lib/libshowlogo.so
(From stock to --> Cm12.1 Boot.img)
init.charging.rc
all init.rc files with factory in the file name (factory_init.rc; factory_init.project.rc)
all init.rc files with meta in the file name (meta_init.rc; meta_init.modem.rc; meta_init.project.rc)
[COLOR="cc3366"]-Camera-[/COLOR]
system/lib/libcameracustom.so
system/lib/libdpframework.so (Fix Green Camera)
system/lib/libfeatureio.so
system/lib/libcam.paramsmgr.so (Fix Megapixel)
system/lib/libjpeg.so
system/lib/libcamalgo.so
system/lib/libcamdrv.so
[COLOR="cc3366"]-Bluetooth-[/COLOR]
[(bluetooth.default.so)] <---(If Bluetooth dosen´t work after this fix dont copy this file)
system/lib/libbluetooth_mtk.so
system/lib/libbluetoothem_mtk.so
[COLOR="cc3366"]-You Tube reload after 5 sec & Netflix stucked at loading screen-[/COLOR]
delet the folder vendor/lib <-- DELET
Copy this files in the folder vendor/lib
MEGA
[COLOR="cc3366"]-GPU Bugs-[/COLOR]
system/lib/egl/libEGL_mali.so
system/lib/egl/libGLES_android.so
system/lib/egl/libGLESv1_CM_mali.so
system/lib/egl/libGLESv2_mali.so
system/lib/libMali.so
system/lib/hw/hwcomposer.mt65xx.so
system/lib/hw/gralloc.mt65xx.so
system/lib/hw/gralloc.default.so
[COLOR="cc3366"]-Notifications lights-[/COLOR]
system/lib/hw/lights.default.so
[COLOR="cc3366"]-Bootloop-[/COLOR]
(From stock to --> Cm12.1 Boot.img)
ueventd.rc
[COLOR="cc3366"]-Audio-[/COLOR]
system/lib/libaudio.primary.default.so
system/lib/libaudiocompensationfilter.so
system/lib/libaudiocustparam.so
system/lib/libaudiosetting.so
system/lib/libaudioutils.so
[COLOR="cc3366"]- Internal and external storage-[/COLOR]
(In Cm12.1 Boot.img)
-Stock init.mt65xx.rc-
Code:
on init
export LD_PRELOAD /system/lib/libxlog.so
[COLOR="red"] export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /storage/sdcard1
mkdir /storage/sdcard0 0700 root root
mkdir /storage/sdcard1 0700 root root
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
mkdir /mnt/media_rw/sdcard0 0700 media_rw media_rw
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw[/COLOR]
.....
on fs
.....
[COLOR="red"] #setprop ro.crypto.fuse_sdcard true[/COLOR]
.....
# virtual sdcard daemon running as media_rw (1023)
[COLOR="red"]service fuse_sdcard0 /system/bin/sdcard -u 1023 -g 1023 /mnt/media_rw/sdcard0 /storage/sdcard0
class late_start
disabled
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled[/COLOR]
service fuse_usbotg /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/usbotg /storage/usbotg
class late_start
disabled
Change red marked lines to
-Modified init.mt65xx.rc-
Code:
[COLOR="blue"]on init
mkdir /mnt/shell/emulated 0700 shell shell
mkdir /storage/emulated 0555 root root
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard1 0700 root root
export EXTERNAL_STORAGE /storage/emulated/legacy
export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
export EMULATED_STORAGE_TARGET /storage/emulated
export SECONDARY_STORAGE /storage/sdcard1[/COLOR]
[COLOR="DimGray"] export LD_PRELOAD /system/lib/libxlog.so[/COLOR]
[COLOR="blue"] mount tmpfs tmpfs /storage/emulated mode=0755,uid=1023,gid=1023
# Support legacy paths
symlink /storage/emulated/legacy /sdcard
symlink /storage/emulated/legacy /mnt/sdcard
symlink /storage/emulated/legacy /storage/sdcard0
symlink /storage/sdcard1 /mnt/sdcard2[/COLOR]
.....
on fs
.....
[COLOR="blue"] setprop ro.crypto.fuse_sdcard true[/COLOR]
.....
# virtual sdcard daemon running as media_rw (1023)
[COLOR="blue"] service sdcard /system/bin/sdcard -u 1023 -g 1023 -l /data/media /mnt/shell/emulated
class late_start
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled[/COLOR]
service fuse_usbotg /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/usbotg /storage/usbotg
class late_start
disabled
-Stock fstab.mt65xx-
Code:
[COLOR="red"]# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/[email protected] /system ext4 ro,commit=1,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/[email protected]_f /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/[email protected]_s /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0 auto auto defaults voldmanaged=sdcard0:8,nonremovable,noemulatedsd
/devices/platform/mtk-msdc.1/mmc_host/mmc1/mmc1 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/mt_usb auto auto defaults voldmanaged=usbotg:auto[/COLOR]
Change to
-Modified fstab.mt65xx-
Code:
[COLOR="blue"]# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/[email protected] /system ext4 ro,commit=1,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/[email protected]_f /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/[email protected]_s /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0 auto vfat defaults voldmanaged=sdcard0:auto
/devices/platform/mtk-msdc.1/mmc_host/mmc1/mmc1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/platform/mt_usb auto auto defaults voldmanaged=usbotg:auto[/COLOR]
framework-res.apk (framework-res.apkresxmlstorage_list.xml)
-Stock storage_list.xml-
Code:
[COLOR="red"]<?xml version="1.0" encoding="utf-8"?>
<StorageList
xmlns:android="http://schemas.android.com/apk/res/android">
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_internal" android:primary="true" android:removable="false" android:allowMassStorage="true" />
<storage android:mountPoint="/storage/sdcard1" android:storageDescription="@string/storage_sd_card" android:primary="false" android:removable="true" android:allowMassStorage="true" />
<storage android:mountPoint="/storage/usbotg" android:storageDescription="@string/storage_usb" android:removable="true" />
</StorageList>[/COLOR]
Change to
-Modified storage_list.xml-
Code:
[COLOR="blue"]<?xml version="1.0" encoding="utf-8"?>
<StorageList
xmlns:android="http://schemas.android.com/apk/res/android">
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_internal" android:primary="true" android:emulated="true" android:allowMassStorage="true" />
<storage android:mountPoint="/storage/sdcard1" android:storageDescription="@string/storage_sd_card" android:primary="false" android:removable="true" android:allowMassStorage="true" />
<storage android:mountPoint="/storage/usbotg" android:storageDescription="@string/storage_usb" android:removable="true" />
</StorageList>[/COLOR]
XDA:DevDB Information
Cyanogenmod 12.1 [MTK fix all Bugs], ROM for all devices (see above for details)
Contributors
OrdenKrieger, fire855
Source Code: https://github.com/cyanogenmod
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Testing
Created 2016-02-05
Last Updated 2016-05-11
Reserved
Pablito2020 said:
Do you know if this guide Works for other roms for mtk6582 based on cm12.1? like octOS rom or Blisspop rom Thank you!
Click to expand...
Click to collapse
Its for all the same.
OrdenKrieger said:
-You Tube reload after 5 sec & Netflix stucked at loading screen-
delet the folder vendor/lib <-- DELET
Copy this files in the folder vendor/lib
MEGA
Version Information
Status: Testing
Created 2016-02-05
Last Updated 2016-02-07
Click to expand...
Click to collapse
Pls Re-Upload the file the link is broken
[email protected] said:
Pls Re-Upload the file the link is broken
Click to expand...
Click to collapse
FIXED :good:
Is there any way I can flash the storage issue.for much easy step
OrdenKrieger said:
FIXED :good:
Click to expand...
Click to collapse
bro mega is not working plzz upload on some other website google or dropbox or box
sagar.singh said:
bro mega is not working plzz upload on some other website google or dropbox or box
Click to expand...
Click to collapse
I just test it working on v2
Enabling Boot Sound...
Hello there... I have only one question here. How can I enabling boot sound on mediatek CM 12.1? Thank you.
here solve of your issue
Add bootaudio file from stock ( i preferred stock) put in media (same location as stock)
Location - system/ media/
Or u can add any Audio
Just a question: Do you know how to fix auto rotation and no SIM card? I tried to restore my IMEI with MTK droid tools but still not working :/
Trillian_123 said:
Just a question: Do you know how to fix auto rotation and no SIM card? I tried to restore my IMEI with MTK droid tools but still not working :/
Click to expand...
Click to collapse
If i was flashed without sim sometimes imei lost. After that i make a factory reset inserted sim and imei come back. Try it. Maybe helps.
I have Alcatel pop c7. I have tried many cm 12.1 and all have the same problem: system memory takes any ram in one day and slow down. Solution for this?
Vijayjaiswal.vj said:
Add bootaudio file from stock ( i preferred stock) put in media (same location as stock)
Location - system/ media/
Or u can add any Audio
Click to expand...
Click to collapse
I've done with it. But the result is just the same.... Still no boot sound. Anyway thanks for your answer, bro
app2sd
any way to fix app2sd? the error is no enough space
youtube limited resolution fix
you can play only 720p&144p or 1080p&144p in latest version
install this file via custom recovery (but first you must download latest version of youtube)
https://drive.google.com/file/d/0B-kc3wRWQk0vU3dPLTVrRFRzOHM/view?usp=sharing
issue1: twitch tv -streaming freezes after 1/2 second s... sound working
issue2:snapchat crashes whenever I try to send recorded video(with blank/black preview)
any solution??
Need fix for MTP and tethering bug.
I have a ported cm12.1 rom for MTK 6753(device: Coopad note 3)..
But MTP and Tethering are not working on them,....
Need a fix for it.....
THanks in advance
i plugged my phone in computer and i switched to charging only mode over usb, i can't now switch back to mtp :'(
i'm using resurrection remix rom
trueange said:
i plugged my phone in computer and i switched to charging only mode over usb, i can't now switch back to mtp :'(
i'm using resurrection remix rom
Click to expand...
Click to collapse
Use xperia sd card mounter to mount storage again.
storage is fine, i dont think storage is the problem