Related
Hi Guys,
I have an Blu Dash 3.5 D170, but i do not have a system android yet... i've got a little problem:
I'm trying to install a backup system.img I got here, but always fails in writing step because the lack of space in /system
when i use adb shell ls -a /system the result is:
Code:
D:\Android\sdk\platform-tools>adb shell
~ # ls -a /system
ls -a /system
. .. lost+found
~ #
other words, there is nothing inside /system...
When i use "busybox df", results is:
Code:
~ # busybox df
busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 80612 48 80564 0% /dev
/dev/block/mtdblock1 225280 148096 77184 66% /system
/dev/block/mtdblock4 179200 1216 177984 1% /data
/dev/block/mmcblk0p1 3850240 118624 3731616 3% /sdcard
/dev/block/mtdblock2 61440 1192 60248 2% /cache
~ #
I can not understand why occupies 66% of the space is has NOTHING within the directory
I tried using the command "fastboot erase system", and the command says that cleared the system, but it does not clear these 66%
what should I do to fix this?
Those of you who are trying to root the NEC Terrain, I've slapped together an ADB driver from the NEC NE-103T to help you out. Basically, I just modified the INF file. Really, we're supposed to use driver version number NA002 with the Terrain but I could only find NA001. It works though and you can get ADB shell etc. Despite the ADB access, I was unsuccessful at rooting the NEC Terrain with SuperOneClick and Root_with_Restore_by_Bin4ry etc. Hopefully, posting these drivers here will help someone else in cyberspace develop a feasible root method.
Here's what the zip file contains:
Obviously the modified ADB driver for NEC Terrain use
Not sure if this is correct but I also applied the ADB driver to the CDC Serial Driver and Windows didn't have a problem.
Here's what I need:
Root Method
Default Recovery Password - NEC password protected recovery mode. :-/
(Sigh), they weren't kidding when they said this phone was secure! I know this is not going to be a popular phone but dang it, I love blackberry keyboard-style Android phones and I really need a decent rooted phone to replace my aging Motorola Pro/Pro+.
tl;dr - I'm providing the missing drivers for the NEC Terrain. Someone please find a way to root it cause I've tried everything! Also, I'm looking for the default password to use Android Recovery 3e.
Hello, Is there anyway we can have help from other people to root this device?
I have tried with SuperOneclick also and with UnlockRoot and it didn't work.
Let me know. I am willing to do anything to make this work except of course stupid stuff.
Thanks Danik
Good news:
I found an exploit over here that gains a root shell (binary attached).
Bad news:
Unfortunately, even from there, running "mount -o remount,rw /system" fails.
Similarly, since /data is marked nosuid, you can't use any su command you install in there.
So...
I am able to remount / as rw and then drop an su command in /sbin. I also set up busybox in /data/local/tmp/xbin and mounted it over /system/xbin and included a link to /sbin/su in there. Of course, that gets overwritten on reboot but it's simple enough to do all this in a script and seems to be enough to get SuperSU and TiBu to run.
The next step is to figure out how to patch boot.img to disable ro.secure, etc. Extracting it should be easy now that we have root. We just need to find the right partition. There seem to be plenty of tools around for working with these images. Then we need someone brave enough to flash it back and try it.
Good news
This is good news...
One problem now, is that there is A LOT of partitions (+30).. It will take some time to get through them...
But it's a step in the right direction... great work...
/Martin
justDave said:
Good news:
I found an exploit over here that gains a root shell (binary attached).
Bad news:
Unfortunately, even from there, running "mount -o remount,rw /system" fails.
Similarly, since /data is marked nosuid, you can't use any su command you install in there.
So...
I am able to remount / as rw and then drop an su command in /sbin. I also set up busybox in /data/local/tmp/xbin and mounted it over /system/xbin and included a link to /sbin/su in there. Of course, that gets overwritten on reboot but it's simple enough to do all this in a script and seems to be enough to get SuperSU and TiBu to run.
The next step is to figure out how to patch boot.img to disable ro.secure, etc. Extracting it should be easy now that we have root. We just need to find the right partition. There seem to be plenty of tools around for working with these images. Then we need someone brave enough to flash it back and try it.
Click to expand...
Click to collapse
MrMEEE said:
This is good news...
One problem now, is that there is A LOT of partitions (+30).. It will take some time to get through them...
But it's a step in the right direction... great work...
/Martin
Click to expand...
Click to collapse
Look at 9 and 11.
justDave said:
Look at 9 and 11.
Click to expand...
Click to collapse
You are right.. There are some boot stuff (kernel and init's) on parts 9 and 11..
I have changed the ro.secure in the inits.. but I'm not able to reflash the two partitions..
I don't get any errors from dd, but got the following messages in dmesg:
<<mmc_write emmc lock write error 0x00097800 : 11
Besides from that, a lot of I/O errors.. so seems like the phone is EMMC locked as well..
hey folks, I managed to get an unlocked terrain. No joke, really unlocked! I just got it from ebay and I am using it on the Telus network in Canada. If it helps your effort to unlock it, let me know if there is any files or even the rom from this phone that you want to see. I just need instructions. On the side note, IMO, the phone is actually quite decent despite that it's running on slower CPU. It's more than capable of running all the most common apps on the market. My only problem is that the "system storage" only has 787M, while the "phone storage" has 4.34G. I can't install apps directly to the phone storage and that 787M is not enough for my use. It would be nice if I can re-partiion all the space and allocate all 4.5G to system.
Please let me know what I can do to help. Would love to see this phone root as well.
Cheers
MrMEEE said:
You are right.. There are some boot stuff (kernel and init's) on parts 9 and 11..
I have changed the ro.secure in the inits.. but I'm not able to reflash the two partitions..
I don't get any errors from dd, but got the following messages in dmesg:
<<mmc_write emmc lock write error 0x00097800 : 11
Besides from that, a lot of I/O errors.. so seems like the phone is EMMC locked as well..
Click to expand...
Click to collapse
Hey folks, so as I said in my previous post, my Terrain is unlocked, so I am just poking around and see if I can gain root to it. Looks like the ROM that my phone is using is the new one from NEC and maybe that's why it's already unlocked. Anyway, I need some help trying to root it. Looks like it's pretty lock down, I can't even access /data/local to put that run_root_shell in it, and so I put it to /sdcard but no good there neither, it won't let me run there.
[email protected]:/sdcard $ ls -la
ls -la
drwxrwxr-x system sdcard_rw 2014-04-29 23:50 .estrongs
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 Android
drwxrwxr-x system sdcard_rw 2014-04-29 22:58 Download
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 LOST.DIR
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 Notifications
drwxrwxr-x system sdcard_rw 2014-04-29 23:49 backups
-rwxrwxr-x system sdcard_rw 89968 2013-12-06 08:54 run_root_shell
[email protected]:/sdcard $ ./run_root_shell
./run_root_shell
/system/bin/sh: ./run_root_shell: cannot execute - Permission denied
126|[email protected]:/sdcard $
Also, there aren't 30+ partitions anymore....or I could be looking at this wrong.
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 327M 76K 327M 4096
/mnt/asec 327M 0K 327M 4096
/mnt/obb 327M 0K 327M 4096
/system 1G 480M 558M 4096
/data 787M 347M 439M 4096
/persist 7M 4M 3M 4096
/cache 354M 24M 330M 4096
/tombstones 68M 4M 64M 4096
/firmware 127M 39M 88M 16384
/data/camera_socket 327M 0K 327M 4096
/data/secure/data 327M 0K 327M 4096
/mnt/sdcard 4G 3M 4G 32768
[email protected]:/ $
Any idea and help would be appreciated. And let me know if you need me to upload any files from it that can help people here to unlock theirs.
cheers
aluminumx said:
Hey folks, so as I said in my previous post, my Terrain is unlocked, so I am just poking around and see if I can gain root to it. Looks like the ROM that my phone is using is the new one from NEC and maybe that's why it's already unlocked. Anyway, I need some help trying to root it. Looks like it's pretty lock down, I can't even access /data/local to put that run_root_shell in it, and so I put it to /sdcard but no good there neither, it won't let me run there.
Click to expand...
Click to collapse
Same thing here, also unlocked device
Code:
[email protected]:/data/local $ ls
ls
opendir failed, Permission denied
Code:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /data/camera_socket tmpfs rw,relatime,mode=775,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,nosuid,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:14 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Forgive me for this slight OT-posting, but it's not that easy to find people with this device - let alone an unlocked one. I'm located in Germany and the device works just fine - except for the fact that neither WIFI tethering works nor syncing with Gmail App (although sync works once I connect to a WIFI Hotspot). Has anyone experienced something similar?
Have a look on my postings list or search for El Grande Partition List (if I remember that right ) by @E.V.A. there's tools for reading partition info
Bashing away at my HTC Desire C
Has anyone seen this yet? Do you think we can use it? http://i.imgur.com/TXKDpOI.png
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
I'm not sure how to install these drivers (it's not an executable so I've got no idea ). Where do I copy the files? to the ADB folder?
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!
I got a strange problem on my htc Desire 200, it has been few days since the first time it happened
the free space of /data partition is used up by something that can't been seen
in settings app, on the storage page, it shows I got 1.18GB in total space(internal storage, /data), and also shows that apps already used 1.05GB
the available just has 140mb left when I'm writing this.
I also checked my /data partition with running "du -had 1 /data" in adb shell, and here's the result:
Code:
[email protected]:/ # du -had 1 /data
du -had 1 /data
4.0K /data/lost+found
0 /data/htcfs
4.0K /data/dontpanic
168.0K /data/misc
12.0K /data/local
228.9M /data/data
4.0K /data/app-private
186.4M /data/app
84.0K /data/property
4.0K /data/radio
4.0K /data/resource-cache
12.0K /data/drm
4.0K /data/secure
12.0K /data/audio
4.0K /data/user
4.0M /data/system
84.0K /data/backup
160.0K /data/anr
44.0K /data/tombstones
112.0K /data/fix_permissions.log
121.6M /data/dalvik-cache
541.6M /data
[email protected]:/ #
I think it looks like I just used 541.6MB actually, but where did the space supposed to be free been?
Edit: I had Xposed installed from long time ago, and it's generating huge log, but I delete the log regularly. however, from few days ago, I just can't seen the log generating anymore, but the free space is still decreasing
--Sorry for my bad English, and thanks for any help&reply
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.