Develop Bugs

[Q] [REQUEST] S2E Scripts or App2Sd+Dalvik-Cache Working

I'm using the MerrukTechnology Kernel 2.0 PRE-FINAL (2.6.35.7 [email protected]), Android Version: 2.3.6, Base Version: S5360BUTLC1, ext4 partitions, tried Darktremor app2sd, custom made (http://forum.xda-developers.com/showthread.php?t=832799), and etc.
Nothing works right, i used this custom on my G5 and works Just fine.
But on SGY not works well, sometimes works, sometimes not, sometime works and on next reboot stop, even can mount ok but apps not works.
Sometimes works perfect, but when i restore my Titanium backups, on next restart stop working.
This is the Script i'm trying:
/system/etc/init.d/02app2sd:
PHP:
#!/system/bin/sh
LOG=/data/app2sd.log
echo "$(date) mounting..." > $LOG
mount -o rw -t ext4 /dev/block/vold/179:2 /sd-ext 1>>$LOG 2>>$LOG
mount -o rw -t ext4 /dev/block/mmcblk0p2 /sd-ext 1>>$LOG 2>>$LOG
mount -o bind /sd-ext/app /data/app 1>>$LOG 2>>$LOG
mount -o bind /sd-ext/dalvik-cache /data/dalvik-cache 1>>$LOG 2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
I already tried almost everything, somebody know some working script?

and what your log said?

irfanbagus said:
and what your log said?
Click to expand...
Click to collapse
pastebin.com/bih8vtiU
I wipe, i put script, restore backup and next restart stop all stop work even logcat said waiting device!
And app2sd.log:
# cat /data/app2sd.log
cat /data/app2sd.log
Tue May 15 15:40:26 BRT 2012 mounting...
mount: Device or resource busy
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437
0 0
/dev/block/stl11 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=or
dered,noauto_da_alloc 0 0
/dev/block/stl10 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=o
rdered,noauto_da_alloc 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /merruk tmpfs rw,relatime,size=32k 0 0
/dev/block/vold/179:2 /sd-ext ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:2 /data/app ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:2 /data/dalvik-cache ext4 rw,relatime,barrier=1,data=ordered
0 0
Tue May 15 15:40:29 BRT 2012 mount finished
Click to expand...
Click to collapse

you can try repencis. it has a2sd support but you'll need to change your partition into ext2.

kurotsugi said:
you can try repencis. it has a2sd support but you'll need to change your partition into ext2.
Click to expand...
Click to collapse
I don't like custom themes

I tried the DarkTremor too, but stops working too.

you can replace the theme with stock one. the one you need is the a2sd script in /system/bin and /system/xbin. everything else could be replaced with stock rom.

Not works anyway, even i tried the ChobitsDigitalis and i wipe, flash and when reboot it show the stock room not the custom rom

nexbr said:
I don't like custom themes
Click to expand...
Click to collapse
Try terma kernel but make sure a2sd script install 1st b4 the kernel.
Actually u can custmz ur stok kernel so can run a2sd.

[Q] Where do I find a 2nd SDcard partition?

Hi,
I formatted my external SDCard with 2 partitions, so I could use it with Link2SD. Since I am on a Mac I only could format the first one, which is FAT32. Now I need to format the 2nd with ext4 but I can only do this from inside the phone. Which is no problem, except I do not understand where I can find the device, I need to format. So, to sum it up: I have already a 'linux' type partition on the SDCard, unformatted, however. And I have a FAT32 partition on it, which gets mounted by Android already. What do I need to issue to the mke2fs command as input?
This is what I get, when issuing 'mount'.
Code:
[email protected]:/ $ 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
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p29 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 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
tmpfs /data/secure/data tmpfs rw,relatime,mode=771,uid=1000,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=755,gid=1000 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:32 /mnt/emmc vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:66 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:66 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ $ ls /mnt
asec
emmc
obb
sdcard
secure
[email protected]:/ $ ls /dev/block/vold/
179:0
179:1
179:10
179:11
179:12
179:13
179:14
179:15
179:16
179:17
179:18
179:19
179:2
179:20
179:21
179:22
179:23
179:24
179:25
179:26
179:27
179:28
179:29
179:3
179:30
179:31
179:32
179:4
179:5
179:6
179:64
179:65
179:66
179:7
179:8
179:9
[email protected]:/ $

In the recovery under mounts or advanced
Sent from my One V using Tapatalk 2

Thank you, I tried that first. But that does not help, since I have cwm5 installed, and that only formats up to 4GB. I need to know where I can find it in the /dev directory, so I can issue the path to mke2fs from 'adb shell'.

zmix said:
Thank you, I tried that first. But that does not help, since I have cwm5 installed, and that only formats up to 4GB. I need to know where I can find it in the /dev directory, so I can issue the path to mke2fs from 'adb shell'.
Click to expand...
Click to collapse
you sure??? i've formated my 8GB one with CWM5 before.....try TWRP or CWM6

Could be, that it offers 8 GB as well. I don't remember. But this is a 32GB card I have in use. What I'd need is two primary partitions, one around 6-8GB/ext4, the other one takes the rest as FAT32.
Can I install a different recovery mod, without resetting/erasing the phone? Is it as simple?

Ok, I updated CWM to v6 and re-checked. The max size is still 4096. Also I noted this:
After I left "advanced/partition" and turned on the log this shows up each time I select "show log"
Code:
When opening the log I get I: Can't format unknown volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblkp1
and the "advanced/partitions" menu item is gone. "parted" in normal boot said, that I have overlapping partitions on the sdcard, which I doubt, since I did the partitioning with a special partitioning utility. Anyways, going to boot up a Linux VM now, should have done so much earlier It's just always so messed up with getting external volumes on USB to recognized.

I'll sort this ASAP thank you for bringing it to my attention
Sent from my One V using Tapatalk 2

Thanks for trying so hard. Greatly appreciated
On a side-note... I tried with a VM, but whatever way I tried to connect the SD card to the Linux guest, I did not succeed. So I am here again, no way to create an ext4 filesystem from inside the phone. Currently I play with the thought about installing a minimal, chrooted debia in my phone. But then I still have the problem with parted moaning about "overlapping partitions", which must be invisible to me, since I just checked the partition table with OS X' fdisk and all numbers seem in sequence. Okay, going to the other thread

data2sd: Can't umount /data: Device or resource is busy

Hello,
I want to use data2sd for my WFS but it doesn't work. It hangs on the white HTC bootscreen.
Over the ADB shell I saw the problem that the internal /data-partition is still mounted. But the external /data-partition is mounted too!
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,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
/sys/kernel/debug /sys/kernel/debug debugfs 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
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /devlog yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /system/data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nouser_xattr,commit=50,barrier=0,data=ordered,noauto_da_alloc 0 0
In this configuration ls /data lists the files moved from the data2sd installer script. After umount /data only the intertnal /data-partition is mountet and ls /data lists only the things the data2sd installer script leave like "dalvik-cache".
So the data2sd script should work. But the problem is that the internal /data partition isn't unmounted while booting I think.
How can I fix this?
Bye Markus
PS: I use the chucky-ROM (now links allowed for new users).

Chickenmarkus said:
Hello,
I want to use data2sd for my WFS but it doesn't work. It hangs on the white HTC bootscreen.
Over the ADB shell I saw the problem that the internal /data-partition is still mounted. But the external /data-partition is mounted too!
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,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
/sys/kernel/debug /sys/kernel/debug debugfs 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
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /devlog yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /system/data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nouser_xattr,commit=50,barrier=0,data=ordered,noauto_da_alloc 0 0
In this configuration ls /data lists the files moved from the data2sd installer script. After umount /data only the intertnal /data-partition is mountet and ls /data lists only the things the data2sd installer script leave like "dalvik-cache".
So the data2sd script should work. But the problem is that the internal /data partition isn't unmounted while booting I think.
How can I fix this?
Bye Markus
PS: I use the chucky-ROM (now links allowed for new users).
Click to expand...
Click to collapse
which rom you exactly use?is it based on stock ? and you can try with ext3 partition.

crossfire77 said:
which rom you exactly use?is it based on stock ? and you can try with ext3 partition.
Click to expand...
Click to collapse
I try to masquerade the link that the forum software doesn't detect it as link: www . htcmania . com/showthread.php?t=460658
This one works fine for other devices of other persons - also with data2sd.
If I mount the Ext4-partition on another point I can use it without any problems.
With another data2sd script based on ext3 there is the same issue.

Chickenmarkus said:
I try to masquerade the link that the forum software doesn't detect it as link: www . htcmania . com/showthread.php?t=460658
This one works fine for other devices of other persons - also with data2sd.
If I mount the Ext4-partition on another point I can use it without any problems.
With another data2sd script based on ext3 there is the same issue.
Click to expand...
Click to collapse
Im not sure about data2sd scripts but you can try alternate scripts like int2ext+,int2ext4+ or a2sd+
These all are pretty new and fast..
Sent from my HTC Wildfire S A510e using Tapatalk 2

crossfire77 said:
Im not sure about data2sd scripts but you can try alternate scripts like int2ext+,int2ext4+ or a2sd+
These all are pretty new and fast..
Click to expand...
Click to collapse
A2sd work how it should but is not that one I want. The same with Link2SD.
I didn't try the int2ext4 script but it had a good idea: Instead of unmounting the internal /data (where it hangs because of business) and mount it somewhere else, the better way is to move it with "mount --move" directly to the new place. After changing this in the data2sd script everthing works great now!
Thanks for this hint. :good:

Chickenmarkus said:
A2sd work how it should but is not that one I want. The same with Link2SD.
I didn't try the int2ext4 script but it had a good idea: Instead of unmounting the internal /data (where it hangs because of business) and mount it somewhere else, the better way is to move it with "mount --move" directly to the new place. After changing this in the data2sd script everthing works great now!
Thanks for this hint. :good:
Click to expand...
Click to collapse
i guess a2sd+ works same as link2sd.it will mount downloaded apps,dalvik cache and cache to sd-ext.system will remain untouchable.
read this here

Easy way to swap external to internal Xperia M and install apps to sd

Easy way to swap external to internal Xperia M and install apps to sd
​
Follow The steps and enjoy
1: download Root External 2 Internal SD
2: open it and grant root access
3: go to settings
4: check the three check boxes
{
"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"
}
5. click on the option which says "The orignal external mounting point"
and change extsdcard to ext_card and press ok
6. then click on the option "The ext. sdcard device acess"
and change 179:49 to 179:33 and press ok
7. go back to the main page and click "External > Internal* "
that its now u can install apps on ur sd card directly from google play
Try this
http://forum.xda-developers.com/showthread.php?t=2711280
thread its better then my thread and even works on cm11
P.S. remember to click the "External> Internal* " button everytime u restart ur phone

Thanks for share.
Is it working for M Dual?
Anyone, Please conform.
Sent from my C1905 using XDA Premium 4 mobile app

Doesn't work on XMD
Any idea?

It's so interesting but in my Xperia M, SD-Card is in /dev/block/vold/179:32, no /dev/block/vold/179:33 as in this (and other) instructions.
When i set to program 179:32 all works good.
Thanks

Pacjonek said:
It's so interesting but in my Xperia M, SD-Card is in /dev/block/vold/179:32, no /dev/block/vold/179:33 as in this (and other) instructions.
When i set to program 179:32 all works good.
Thanks
Click to expand...
Click to collapse
You talking bout M Dual?
Sent from my C2005 using XDA Premium 4 mobile app

StraightEdgeKid said:
You talking bout M Dual?
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Xperia M Single but you should go to /dev/block/vold/ (Root Explorer) and check where has been adressed your SD-CARD
P.S This metod is not great beacause this program not swap, only set sd-card as intrenal memory. Propetly internal memmory is dissapear so better is using other method.

Pacjonek said:
Xperia M Single but you should go to /dev/block/vold/ (Root Explorer) and check where has been adressed your SD-CARD
P.S This metod is not great beacause this program not swap, only set sd-card as intrenal memory. Propetly internal memmory is dissapear so better is using other method.
Click to expand...
Click to collapse
other ways not working :crying::crying::crying::crying::crying:

horamankurdish said:
other ways not working :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I see no reason why that would't work.
Have you checked where is adressed your SD card?

Pacjonek said:
I see no reason why that would't work.
Have you checked where is adressed your SD card?
Click to expand...
Click to collapse
It's 179:32.
I'd tried with other options too, with this, unfortunately not working, and reason is unknown.
Sent from my C2005 using XDA Premium 4 mobile app

StraightEdgeKid said:
It's 179:32.
I'd tried with other options too, with this, unfortunately not working, and reason is unknown.
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Download Terminal Emulator and run it.
Type:
vold
mount -t vfat -o umask=0000 /dev/block/vold/179:32 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Click to expand...
Click to collapse
Pay attention to 179:32 or 179:33 !
Tell me if there are any errors

Pacjonek said:
Download Terminal Emulator and run it.
Type:
Pay attention to 179:32 or 179:33 !
Tell me if there are any errors
Click to expand...
Click to collapse
on dual sim not working bro i tried

horamankurdish said:
on dual sim not working bro i tried
Click to expand...
Click to collapse
But what does appear?
I don't have this phone but i try help you so what does appear (if anything) after type this?
Then reboot phone (important!), go to Terminal Emulator, type:
mount >> /storage/sdcard1/tablica.txt
Click to expand...
Click to collapse
Connect your phone to PC, open your SD Card in Windows, open tablica.txt file and copy all text to your next forum post

works, but when I go to install an application from google play says there is no space

Pacjonek said:
But what does appear?
I don't have this phone but i try help you so what does appear (if anything) after type this?
Then reboot phone (important!), go to Terminal Emulator, type:
Connect your phone to PC, open your SD Card in Windows, open tablica.txt file and copy all text to your next forum post
Click to expand...
Click to collapse
It says "no such file or directory vold /179:32"
Also tried with 179:32!
No luck at all
Sent from my C2005 using XDA Premium 4 mobile app

StraightEdgeKid said:
It says "no such file or directory vold /179:32"
Also tried with 179:32!
No luck at all
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, so please reboot device, go to Terminal Emulator and type:
mount << ext_sdcard/tablica.txt
Click to expand...
Click to collapse
It will create file tablica.txt on your SD CARD.
Please put content of this file to your next post.

Pacjonek said:
Ok, so please reboot device, go to Terminal Emulator and type:
It will create file tablica.txt on your SD CARD.
Please put content of this file to your next post.
Click to expand...
Click to collapse
Here you go.
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 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/secure tmpfs rw,relatime,mode=700 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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Sent from my C2005 using XDA Premium 4 mobile app
---------- Post added at 07:42 PM ---------- Previous post was at 07:42 PM ----------
Sorry for just pasting them, that's because im logged in from my phone.
Sent from my C2005 using XDA Premium 4 mobile app

StraightEdgeKid said:
Here you go.
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 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/secure tmpfs rw,relatime,mode=700 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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Sent from my C2005 using XDA Premium 4 mobile app
---------- Post added at 07:42 PM ---------- Previous post was at 07:42 PM ----------
Sorry for just pasting them, that's because im logged in from my phone.
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Android 4.2 has introduced a changes in addressing the memory card. That explains all.
Please try this:
su
mount -t vfat -o umask=0000 /dev/block/vold/179:33 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
Click to expand...
Click to collapse

Pacjonek said:
Android 4.2 has introduced a changes in addressing the memory card. That explains all.
Please try this:
Click to expand...
Click to collapse
Tried till emulated, it says mount:device is busy.
And when tried all the script, it say like.
"ld/179:33 /mnt/shell/emulated <
mount: Device or resource busy
ted mount -o bind/data/media/0/storage/sdcard1 <
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Sent from my C2005 using XDA Premium 4 mobile app

StraightEdgeKid said:
Tried till emulated, it says mount:device is busy.
And when tried all the script, it say like.
"ld/179:33 /mnt/shell/emulated <
mount: Device or resource busy
ted mount -o bind/data/media/0/storage/sdcard1 <
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try:
su
vold
mount -t vfat -o umask=0000 /dev/block/vold/179:33 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
Click to expand...
Click to collapse
In the second line there is a space! ...media/0 SPACE /storage...

its required to do root my device
or it will work only uprooted device

CWM Touch v6.0.4.7

delete thread please!

great work thank you munjeni:good:

Great! Thanks, munjeni

Thanks! Works great but saved the backup has a date 1970.02.07 ... just like in the previous version. Maybe it is how to backup wrote in the current date?

Never had internal srorage emulated so our phone is my first phone which have emulated storage. Does anyone have idea where is block device for internal sdcard??? I thinking its (in) mmcblk0p25 ? More info about internal sdcard is welcome!

New version is out! http://forum.xda-developers.com/attachment.php?attachmentid=2594573&d=1393093417

1jkan said:
Thanks! Works great but saved the backup has a date 1970.02.07 ... just like in the previous version. Maybe it is how to backup wrote in the current date?
Click to expand...
Click to collapse
Tnx for feedback, I will use date and time from kernel (time which is displayed on main screen) for backup name... :good:

munjeni said:
Never had internal srorage emulated so our phone is my first phone which have emulated storage. Does anyone have idea where is block device for internal sdcard??? I thinking its (in) mmcblk0p25 ? More info about internal sdcard is welcome!
Click to expand...
Click to collapse
it's look like XZ1c uses unified storage.
unified storage = intenal storage(/mnt/sdcard0/) --> /data/media
Code:
[email protected]:/storage/sdcard0 # df
Filesystem Size Used Free Blksize
/dev 343.1M 72.0K 343.0M 4096
/mnt/asec 343.1M 0.0K 343.1M 4096
/mnt/obb 343.1M 0.0K 343.1M 4096
/system 1009.3M 877.7M 131.6M 4096
[COLOR="Red"]/data 3.9G 1.3G 2.6G 4096[/COLOR]
/cache 246.2M 4.3M 241.9M 4096
/data/idd 7.5M 1.1M 6.4M 1024
[COLOR="red"]/storage/sdcard0 3.9G 1.3G 2.6G 4096[/COLOR]
/mnt/asec/com.keramidas.TitaniumBackupPro-1 2.0M 80.0K 1.9M 4096
/mnt/asec/com.mobisystems.editor.office_registered-1 50.0M 48.7M 1.3M 4096
/mnt/asec/com.quoord.tapatalkHD-2 31.0M 29.2M 1.9M 4096
/storage/sdcard1 29.7G 27.8G 1.9G 32768
[email protected]:/storage/sdcard0 #
mounts :
Code:
[email protected]:/storage/sdcard0 # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-num/p12 /system ext4 ro,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p14 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p13 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p10 /data/idd ext4 rw,nosuid,nodev,noatime,nobarrier,data=ordered 0 0
[COLOR="Red"]/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0[/COLOR]
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/dm-1 /mnt/asec/com.mobisystems.editor.office_registered-1 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.quoord.tapatalkHD-2 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
from /system/build.prop
Code:
# It is changed to true in msm8660_surf
# Change it back to false according to blue
#
# Simulate sdcard on /data/media
#
[B][COLOR="Red"]persist.fuse_sdcard=false[/COLOR][/B]
this example i take from lt26w build.prop the value should be true for XZ1c.
/init.semc.rc
Code:
# 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 0775 media_rw media_rw
chown media_rw media_rw /data/media
mkdir /data/media/Download 0775 media_rw media_rw
chown media_rw media_rw /data/media/Download
/init.sony-device.rc
Code:
# User 2800: sdcardd
service sdcardd /system/bin/sdcard /mnt/int_storage 2800 2800
user root
group sdcard_rw
disabled
/system/bin/sdcard --> binary to fuse mount /data/media to /mnt/int_storage
i have managed to enable unified storage on lt26w by editing the build.prop and vold.fstab.hopefully this could help with internal storage mounts on XZ1c.

Do you have idea how we can mount them to loop device? I had no time to play with them but block device is reguired for mounting them to pc. Idea is to mount them somehow to loop device -> than mount loop to the an folder -> than echo loop device to lun file. I have no tried to mount them manualy using sdcard tool. Maybe better solution is repartitioning emmc and making vfat partition for internal sdcard since it will be easy for mounting (ramdisk will need modification).

munjeni said:
Do you have idea how we can mount them to loop device? I had no time to play with them but block device is reguired for mounting them to pc. Idea is to mount them somehow to loop device -> than mount loop to the an folder -> than echo loop device to lun file. I have no tried to mount them manualy using sdcard tool. Maybe better solution is repartitioning emmc and making vfat partition for internal sdcard since it will be easy for mounting (ramdisk will need modification).
Click to expand...
Click to collapse
http://teamw.in/DataMedia
Because the "internal sdcard" is not a true FAT file system, you can't mount it via USB storage. Well, that's not technically true, but the vast majority of people use Windows computers and Windows doesn't recognize ext4. If we were to allow you to mount the data partition via USB storage, Windows would claim that the device wasn't formatted and offer to format it for you, which, as you can imagine, would be a disaster. The whole ext4 setup is another reason that Android switched to using MTP for transferring files. Most of these devices don't have the necessary kernel configuration to even support USB storage mode, so it's not very easy to enable USB storage if we even wanted to try. Unfortunately at this time, MTP isn't available in recovery, so if you have no other option, you will have to use adb to push and pull files to/from your device.
Click to expand...
Click to collapse

Yes, you are right, thats not posible since partition is not fat, only in linux we can see mounted storage, but thats not what we want. Will remove internal sd in mount storage menu.

any other download link for the boot.img ? thanks

munjeni said:
Hi, here is my version of the recovery, almost full working.
{
"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"
}
What working what not working:
Working:
- everything including adb and external sdcard
Not working:
- can not mount internal sdcard, but I will try to get them working soon
New feature:
- increased brightness of the recovery
- battery level (icon!) in real time
- clock (icon!) in real time
- battery charging led indicator
Changelog 22.Feb.2014 :
- redesigned
- special menu (will make them soon!)
- new font (lucida console)
How to install:
1. for locked bootloaders only:
- Our recovery is replacement for not working Philz recovery from post -> http://forum.xda-developers.com/showthread.php?t=2647480
- download zip from these post (Z1C-lockeddualrecovery[VERSION]-BETA.installer.zip), download ramdisk-recovery.cpio.lzma -> http://munjeni.homeunix.com/ramdisk-recovery.cpio.lzma, rename ramdisk-recovery.cpio.lzma to recovery.philz.cpio.lzma, copy them to Z1C-lockeddualrecovery[VERSION]-BETA.installer.zip by replacing file recovery.philz.cpio.lzma in zip
2. for unlocked bootloaders only:
- download boot.img from http://munjeni.homeunix.com/z1c_boot.img , reboot to fastboot, flash boot.img with fastboot, go to http://forum.xda-developers.com/showthread.php?t=2620794 and give thanks to author of the ramdisk! Thanks man! My work is only on CWM, everything other is extracted from his boot image! Boot image contain CWM + stock rom ramdisk + stock rom kernel = for stock rom 14.2.A.1.114 only!
If something is not working please let me know! Enjoy!
Click to expand...
Click to collapse
Hi, the link under 1 for downloading /ramdisk-recovery.cpio.lzma is not working, server seems to be down

Server is up again, sorry

This CWM is great. I had some issues with the other (dual boot TWRP) and installing a ROM. I have installed a ROM and run backups. Haven't had time to test restore. Well done!

munjeni said:
Tnx for feedback, I will use date and time from kernel (time which is displayed on main screen) for backup name... :good:
Click to expand...
Click to collapse
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.

dhchris said:
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris View attachment 2721115
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.
Click to expand...
Click to collapse
Thats a known isue on CWM recovery ! I don't think if these bug will be solved soon since recovery have no internet access to sinchronise time, so recovery can not know actual date! Maybe we can implement something for getting time from radio (not sure if it is possible).

If that's the reason, then where does TWRP get the correct date and time from because there it works?

Iruwen said:
If that's the reason, then where does TWRP get the correct date and time from because there it works?
Click to expand...
Click to collapse
Sorry I dont know, but I will look into twrp source code to get idea, have no free time for cwm, but maybe later.

dhchris said:
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris View attachment 2721115
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.
Click to expand...
Click to collapse
Excuse me for interfering...
This date format is to sort the backups. First is year, next month and last for day.
If you are using a "normal" datestamp, your files are not listed in sequence.
So, in this case your files are always listed in a way, that latest backup is the last in row.