Related
ANNOUNCEMENT:
Official version that support most (including our) device has been released. See HERE
Hi All.
Here are the modified version of Online Android Backup from ORIGINAL THREAD. I've changed some codes to make it works for our HTC Legend.
How To Install:
Through CWM
1. Download from attachment onandroidv3.7_cwm.zip
2. Copy it to your sdcard
3. Reboot into recovery
4. Flash the file
Manual
1. Extract onandroid.zip attached and use adb/root explorer to push/copy the file onandroid to your /system/bin
2. change permission to rwxr-xr-x
How To use:
From PC:
1. Open terminal/command prompt
2. type adb shell
- if using CM9, type su to gain root access after step 2.
3. type onandroid
From your phone:
1. open terminal emulator, type su
2. type onandroid
UPDATE:
If you use ogo2's ROM HERE, please download SENSE_fix_tool.zip from attachment and flash it. Mediafire link are HERE
Changes:
12.06.2012: Initial modification from original version
13.06.2012: Power checking corrected
14.06.2012: Added CWM flashable file
20.06.2012: Update v3.7 from original developer. confirm to work in cm9
Changelogs from original developer:
:: Latest onandroid fixes from v3.7
:: Made "dd" not spit results.
:: Added partition detection for boot and recovery partitions.
02.07.2012: Fix for sense ROM
screenshots and file are attached.
Credits:
ameer1234567890 Original Developer
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
vriz27 said:
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
Click to expand...
Click to collapse
Yes, download the file from attachment (onandroid_CWM.zip)
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
smithchipz said:
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
Click to expand...
Click to collapse
Thanks. I just do some simple modification to the original version, praise to ameer1234567890 for the great tools.
Restoring is working fine with me but make sure you check the backup folder after onandroid is finish running and check if all required files is there especially if you do something else during the backup process.
Fix for sense ROM attached in 1st post.
feed3 said:
Fix for sense ROM attached in 1st post.
Click to expand...
Click to collapse
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
alligator_asl said:
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
Click to expand...
Click to collapse
That is due to an issue in XDA (one of the servers crashed). Should be fixed in a couple of days!
Sense fix
Sense fix tool uploaded to mediafire. Link in the post #1.
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type 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)
/dev/block/vold/179:1 on /mnt/secure/asec type 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Click to expand...
Click to collapse
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
ameer1234567890 said:
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
Click to expand...
Click to collapse
Here is it:
Code:
# mount
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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /mnt/asec/sd ext3 rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback 0 0
/dev/block/vold/179:1 /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:1 /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
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/nadsoft.physicscheatsheetsfree-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/jwtc.android.chess-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
How did you partition your sdcard? Which app2sd or link2sd version do you use?
Also, post output from below command!
Code:
echo $SD_EXT_DIREECTORY
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
alligator_asl said:
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
Click to expand...
Click to collapse
Thank you for the information. I am working on a fix.
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type 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)
/dev/block/vold/179:1 on /mnt/secure/asec type 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
Click to expand...
Click to collapse
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
feed3 said:
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
Click to expand...
Click to collapse
I have fixed this in the next version. Shall be releasing soon.
ameer1234567890 said:
I have fixed this in the next version. Shall be releasing soon.
Click to expand...
Click to collapse
Thanks ameer..
After 1000 forum pages later I setup a small script under init.d for the storage swap under 4.2.2 which works more or less:
sleep 3
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
chown system /data/media/0
chgrp sdcard_rw /data/media/0
chmod 0075 /data/media/0
mount -o remount, ro /
But now I do not know how to progress further,it looks good under x-plorer and Root explorer (storage swapped), but under the normal menue the primary storage is shown as the internal one. (However, programme files are installed on the ext. SD card correctly) Anyone having a good idea?
For those who are interested in giving it a try (this is at your own risk!), until it is completely fixed and there is a more comprehensive description, it is more for people with some background, at least:
DO A BACKUP FIRST! (e.g. with TWRP, if you end up in a boot loop, you can at least go back to the latest running system)
1) create a script, e.g. with SMmanager ads under /etc/init.d and copy text from above into it and save
2) activate boot, su and executable for the script
3) save file/script
4) reboot, swap (of the mounts) will be done
5) do a manual transfer, of the files and folders from one storage to the other.
That means that you should transfer at least the files under /data/media/0 to mnt/shell/emulated/0 (I used root explorer), same for legacy and obb.
Note that under 4.2.2 the obb folder under android has been moved due to the multiuser capability under the same level as the user folders (0, 10, 11 e.g. if you have three users), so if you have (after the transfer from /data/media/0) files under mnt/shell/emulated/0/android/obb transfer the files to avoid a redownload and waste of storage to mnt/shell/emulated/obb e.g. using roor explorer.
After that you will see the external SDcard folder mnt/shell/emulated/0 as internal storage (using an explorer, works also if you connected to windows via USB, but, again, not in the internal menue)
and /data/media/0 as external storage.
TWRP folder can/should be found under mnt/shell/emulated.
6) Keep a copy of the script on your ext. sdcard, after an update the file will be lost and you can copy it back to init.d (e.g. using root explorer)
7) In case you want to revert to normal mount delete script from init.d and reboot (and copy back files manually)
That is in principle all and again it works, but not flawless (indication under menue, rights of files from internal sd under multiuser), so I would appreciate some constructive comments to improve it. Again, I am at the end of my (limited) knowledge...
As it works, it seems to be primary an indication issue...
Mount is delivering the following (pre swap):
[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 none /dev/cpuctl cgroup rw,relatime,cpu 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 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
/dev/block/dm-0 /mnt/asec/com.DefiantDev.SkiSafari-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,bar rier=1 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p24 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1, data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0022,codepage=cp437,i ocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p20 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p22 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1, data=ordered 0 0
/dev/block/mmcblk0p23 /tmpdata ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,d ata=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p21 /persist ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,d ata=ordered 0 0
/dev/block/mmcblk0p27 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,d ata=ordered,noauto_da_alloc 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=102 3,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=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=102 3,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=102 3,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=102 3,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=102 3,default_permissions,allow_other 0 0
[email protected]:/ $
Mount post-swap delivers in principle (after the last changes in the script some right(s) should be different):
[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
none /dev/cpuctl cgroup rw,relatime,cpu 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
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
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.zeptolab.ctrexperiments.google.paid-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.twodboy.worldofgoofull-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p24 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p20 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p22 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p23 /tmpdata ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p21 /persist ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 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/block/vold/179:97 /mnt/shell/emulated vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/mmcblk0p27 /storage/sdcard1 ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:97 /storage/emulated/0 vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/emulated/0/Android/obb vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/emulated/legacy vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/emulated/legacy/Android/obb vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
[email protected]:/ $
Update 13.04
What does the script do?
-mounts your user data to the external SDcard
-ext. SDcard will be used as your internal storage
-internal storage will show up as external storage (sdcard1) can be used, too
What does not work?
-storage swap is not correctly displayed under the system menue, -this seems to be merely an indication issue
What you need before you can start?
-Root
-TWRP (or equivalent)
-Root explorer (or equivalent)
-SMmanager ads (or equivalent
How to do it?
1) DO A BACKUP OF THE SYSTEM FIRST! (e.g. with TWRP, if you end up in a boot loop, you can at least go back to the latest running system)
2) copy folder "emulated" from /mnt/shell to your ext. SDcard, /storage/sdcard1 (use root explorer),- you will delete the redundant data from your internal storage later after the reboot
3) create a script, e.g. with SMmanager ads under /etc/init.d and copy text from above into it and save:
sleep 5
mount -o remount,rw /
mkdir /data/newext_sd
mkdir /data/newext_sd/myfolder
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /mnt/shell
mount -o bind /data/newext_sd /storage/sdcard1
chmod 0075 /data/newext_sd
chown system /data/newext_sd
chgrp sdcard_rw /data/newext_sd
chmod 0777 /data/newext_sd/myfolder
chown root /data/newext_sd/myfolder
chgrp root /data/newext_sd/myfolder
mount -o remount,ro /
4) activate boot, su and executable for the script
5) save script, again
6) reboot, swap (of the mounts) will be done
7) if you get a message that system process do not run properly, press wait and it should not reappear (you may also delete the caches, again, with TWRP)
8) delete redundant data, all folders under /data/media, use root explorer
9) keep a copy of the script on your ext. sdcard, after a rom update the file will be lost and you can copy it back to init.d (e.g. using root explorer) (and reboot)
10) in case you want to revert to normal mount delete script from /etc/init.d and reboot (and copy back files manually)
11) in case you want to reintegrate already existing data from your ext. SDcard to your new user folder structure go with the root launcher to /mnt/shell to access the root of your card and copy any content under your user folder /mnt/shell/emulated/0.
Enjoy...
AS BEFORE, YOU TINKER AT YOUR OWN RISK
Sorry... but storage swapping works in the latest JB's.
Greets Gunnar
No reason to be sorry ,guess where the script came from?
But sharing was the intention.
PS: a few more thanks would have been nice, anyway...
OK, just misunderstood it.
If this is the methodm, which was used in the ROMs of after_silence and zyr3x... it works very well!
Greets Gunnar
Just so I understand:
- please confirm this is already part of the ROM and there is no need to use the scripts...if so, where is the option menu?
- this swaps the internal and external memory so that the internal memory is mapped to the sd card that is removable and the external memory is mapped to the built-in memory which is not removable?
- For the Tmobile Springboard, the built-in memory would be 16GB and for the Mediapad 8GB, I believe. Is that correct?
Advantages and disadvantages, as I see them or understand them.
Advantage:
- I believe this means that the device would see 32GB or 64GB if that was the size of the sd card. Not sure if a 64GB card would work. Why is this an advantage?
Disadvantage:
- That would also mean that you could never remove the sd card. That seems like a disadvantage, but I don't think most people would remove their sd card anyway.
- Sd cards are slower than built-in memory. Is this true?
If anyone wants to add their opinion or comments, please do. If there are any other things to consider, please add them.
Also, don't know how this compares to other methods like Link2SD or those kind of apps.
Thanks all.
mastrv said:
Just so I understand:
- please confirm this is already part of the ROM and there is no need to use the scripts...if so, where is the option menu?
- this swaps the internal and external memory so that the internal memory is mapped to the sd card that is removable and the external memory is mapped to the built-in memory which is not removable?
- For the Tmobile Springboard, the built-in memory would be 16GB and for the Mediapad 8GB, I believe. Is that correct?
Advantages and disadvantages, as I see them or understand them.
Advantage:
- I believe this means that the device would see 32GB or 64GB if that was the size of the sd card. Not sure if a 64GB card would work. Why is this an advantage?
Disadvantage:
- That would also mean that you could never remove the sd card. That seems like a disadvantage, but I don't think most people would remove their sd card anyway.
- Sd cards are slower than built-in memory. Is this true?
If anyone wants to add their opinion or comments, please do. If there are any other things to consider, please add them.
Also, don't know how this compares to other methods like Link2SD or those kind of apps.
Thanks all.
Click to expand...
Click to collapse
Thanks to zyr3x and after_silence the first script is integrated in the last AOPK JB and CM10.1, -so no need for mediapad users with those Roms to pick up the script and we can considered this thread closed
Nevertheless, I do not want to delete it for the time being, as it may be of use for information also for other 4.2.2 Roms, however with different mounting points and adaptation to be made.
Other methods like Link2SD do not work on 4.2.2, unless there is a new development?
As you say, advantage is that you have additional space for games, nav, etc.
Disadvantage is indeed a performance loss and you need the sd card, -at least for certain apps.
@Maja
Please don't delete this Thread!
Before reading this, I thought this possibility for JB comes from the other developers.
But the thank for this point of development goes to you...
And this could be very helpful for other developers, trying to port JB (4.2.x).
I try to answer directly to the questions...
mastrv said:
Just so I understand:
Click to expand...
Click to collapse
- please confirm this is already part of the ROM and there is no need to use the scripts...if so, where is the option menu?
-> Settings > extended (or such) -> Swap internal und external storages
- this swaps the internal and external memory so that the internal memory is mapped to the sd card that is removable and the external memory is mapped to the built-in memory which is not removable?
-> Thats not this simple... for example: the "sdcard" shows to the card as before, so apps don't use internal memory for storing huge data
- For the Tmobile Springboard, the built-in memory would be 16GB and for the Mediapad 8GB, I believe. Is that correct?
-> don't know the Springboard, but yes, MediaPads internal memory is 8GB, 6GB for data
Advantage:
- I believe this means that the device would see 32GB or 64GB if that was the size of the sd card. Not sure if a 64GB card would work. Why is this an advantage?
-> as described before... not that simple at all - and yes, 64GB Fat32 formatted "MobilUltra" from SanDisk works like a charm!
Disadvantage:
- That would also mean that you could never remove the sd card. That seems like a disadvantage, but I don't think most people would remove their sd card anyway.
-> some apps may not work, the system will boot and work normally. This comes from the fact, that "/data" ist still mapped to the internal memory
(this means, that all App-APKs,-Libs,-Data and the Dalvik-Cache stays in internal memory)
- Sd cards are slower than built-in memory. Is this true?
-> not always, but mostly Just put in a fast card and you'll feel no difference
Also, don't know how this compares to other methods like Link2SD or those kind of apps.
-> forget about such things with JB 4.2.x
Hope this helps.
Greets Gunnar
P.S.: mainly it works like it does with ICS... as far as it could
Sounds good. I'll have to get a 64gb card then. FYI, FAT and FAT32 are still the best bets for interoperability. There are utilties that will format drives in FAT32 even though they are larger than 32GB. The 32GB limit was imposed by Microsoft.
FYI, the Tmobile Springboard is a variant of the Mediapad. It does come with 16GB of memory.
Thanks!
In case you have problems with the
[CM10.1][16.08.2013] CM10.1 for Huawei Mediapad 7" [S7-30Xx] [not for Lite or 10 HD]
version of after_silence, means swap does not work, you can revise the script "02extsd" under /etc/init.d to the following by removing the "if-term" as a temporary fix:
#!/system/bin/sh
sleep 3
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
chown system /data/media/0
chgrp sdcard_rw /data/media/0
chmod 0075 /data/media/0
mount -o remount, ro /
Regardless of the "tick" in the system menue, the swap is performed, anyway. (or you wait for an update...)
I assume there is a problem of the used variable of the "if-term", which should not be too difficult to be changed in the code by zyr3x.
HEllo
Just installed JellyBam 8.2 and loving it!
Having one small issues with how the extSdCard permissions
On my internal memory (eg /sdcard) i can see directories as 775 permission with user "root" and group "sdcard_rw". These files are fine to read from all apps.
I am using isyncr wifi to sync my mp3s to the external sd card and in the directory it creates (/mnt/fuse/scard1/syncr) all the directories are created as 644 (ie not executable) with user "u0_a152" and group "u0_a152"
Hence my music player app (player pro) cant see the files. Only root explorer can.
I've tried the permission fix mentioned where you edit platform.xml and adding media_rw permissions for WRITE_EXTERNAL_STORAGE
http://forum.xda-developers.com/showthread.php?t=1458021
So any clues?
Many thanks
axelnormand said:
HEllo
Just installed JellyBam 8.2 and loving it!
Having one small issues with how the extSdCard permissions
On my internal memory (eg /sdcard) i can see directories as 775 permission with user "root" and group "sdcard_rw". These files are fine to read from all apps.
I am using isyncr wifi to sync my mp3s to the external sd card and in the directory it creates (/mnt/fuse/scard1/syncr) all the directories are created as 644 (ie not executable) with user "u0_a152" and group "u0_a152"
Hence my music player app (player pro) cant see the files. Only root explorer can.
I've tried the permission fix mentioned where you edit platform.xml and adding media_rw permissions for WRITE_EXTERNAL_STORAGE
http://forum.xda-developers.com/showthread.php?t=1458021
So any clues?
Many thanks
Click to expand...
Click to collapse
You say /mnt/fuse/sdcard1, but you're not going to the directory using that path are you?
Couple of notes
1) please post questions in the q&a section. General is not for questions (You can report your thread and ask it to be moved using the /!\ button.
2) JellyBam discussion is banned on XDA
Sorry posted this in the wrong place, and thank you for the reply
The isyncr wifi program i assume just writes to the external sd card using the path provided to it by the OS?
I dont actually choose the absoulte path in isyncr, rather just select internal or external sd card and then the directory name to sync to.
Should i try to force it to use /mnt/extSdCard then?
Thanks
axelnormand said:
Sorry posted this in the wrong place, and thank you for the reply
The isyncr wifi program i assume just writes to the external sd card using the path provided to it by the OS?
I dont actually choose the absoulte path in isyncr, rather just select internal or external sd card and then the directory name to sync to.
Should i try to force it to use /mnt/extSdCard then?
Thanks
Click to expand...
Click to collapse
/storage/extSdCard would be where I imagined the app reads it from. Do you have a normal (Non-root) file manager that you can use to browse that location and confirm you can get to the files?
rootSU said:
/storage/extSdCard would be where I imagined the app reads it from. Do you have a normal (Non-root) file manager that you can use to browse that location and confirm you can get to the files?
Click to expand...
Click to collapse
Using normal non-root file manager i can browse to other directories on extSdCard fine (eg TitaniumBackup directory)
However the syncr directory is returned as empty
axelnormand said:
Using normal non-root file manager i can browse to other directories on extSdCard fine (eg TitaniumBackup directory)
However the syncr directory is returned as empty
Click to expand...
Click to collapse
I really don't know what is going on here. The /extSdCard is mounted with a single set of permissions and nothing should be able to change those permissions except at boot.
Have you tried removing the folder with RE, reboot then try sync again?
In terminal emulator, what is teh output of "mount" command please?
it is strange isnt it!
anywho thanks again for reply
I have tried deleting folder in Root Explorer and re-sync. But will try that again
Here is the mount command output
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
none /dev/cpuctl cgroup rw,relatime,cpu 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
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 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
/dev/block/dm-0 /mnt/asec/com.fatattitude.buschecker-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/net.dinglisch.android.taskerm-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.touchtype.swiftkey-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.kodek.pebbletasker-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/ptc.jp-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.twentyfivesquares.press-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.corecoders.skitracks-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.koushikdutta.rommanager.license-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.melodis.midomiMusicIdentifier-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.jrtstudio.iSyncr4Mac-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/hyperfine.hftunes.release-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-11 /mnt/asec/com.annabelkarmel.android-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-12 /mnt/asec/org.mots.haxsync-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-13 /mnt/asec/com.makariolewis.gifinatorplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-14 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-15 /mnt/asec/nz.intelx.send.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-16 /mnt/asec/com.tbig.playerpro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-17 /mnt/asec/com.mdjsoftware.download.paid-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-18 /mnt/asec/com.ttxapps.dropsync.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-19 /mnt/asec/net.hubalek.android.apps.reborn.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/vold/179:17 /mnt/fuse/sdcard1 ext4 rw,dirsync,nosuid,nodev,noexec,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 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/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
JellyBAM is a forbidden rom here
Sent from my GT-I9505 using Tapatalk 4 Beta
Look, this is really weird....
Code:
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/vold/179:17 /mnt/fuse/sdcard1 ext4 rw,dirsync,nosuid,nodev,noexec,noatime,barrier=1,data=ordered 0 0
and...
Why is he mounting sdcard1 as ext4 within fuse? That's just odd.
Here is mine from RootBox (which I just installed)...truncated...
Code:
/dev/block/vold/179:17 on /storage/sdcard1 type vfat (rw,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702)
These above permissions are pretty standard amongst AOSP roms. I've tested my script with many and had to remoutn sdcard to get it to work correctly with permissions below, like Samsung use...
And this is mine after I remount my sdcard (so my script works)
Code:
/dev/block/vold/179:17 on /storage/sdcard1 type vfat (rw,relatime,uid=1023,gid=1023,fmask=0002,dmask=0002)
Actually with the latter, I also have the media_rw added to platforms.xml
I just don't understand what he is doing mounting the sdcard1 like that, using fuse
I'm goign to have to recommend you change your ROM really, cause it's weird.
---------- Post added at 11:12 AM ---------- Previous post was at 11:11 AM ----------
Theshawty said:
JellyBAM is a forbidden rom here
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you, Yes I have already said that
rootSU said:
Thank you, Yes I have already said that
Click to expand...
Click to collapse
Have you also told him that iGio is no real dev and just straight up kangs everything? He probably doesn't have a single clue how to fix this issue his users have.
Sent from my GT-I9505 using Tapatalk 4 Beta
Theshawty said:
Have you also told him that iGio is no real dev and just straight up kangs everything? He probably doesn't have a single clue how to fix this issue his users have.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I haven't. Because I don't know that to be true. That said I have told him that I don't know why the "dev" is mounting like that and recommended changing roms, so hopefully we're good.
thanks everyone for your help
Had no idea about the controversy around jellybam
maybe time to change roms.
pacman or paranoid think ill try next
axelnormand said:
thanks everyone for your help
Had no idea about the controversy around jellybam
maybe time to change roms.
pacman or paranoid think ill try next
Click to expand...
Click to collapse
Both good ROMs. There's rootbox too if you like that whole combined AOKP/CM/PA thing.
JellyBam discussions aren't allowed on XDA {as two members already pointed out before me}
Closed.
Hi,
No matter what I do, I can't remount "/system" and "/" to RW. :crying:
Does anyone know how to resolve this issue?
I am running on KK 4.4.2 version 14.3.A.0.757.
My Current File System Status
[email protected]:/ # mount
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 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
tmpfs /tmp tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apps_log /mnt/idd ext4 rw,seclabel,nosuid,nodev,noexec,noatime,discard,nobarrier,data=ordered 0 0
tmpfs /storage/remote tmpfs rw,seclabel,relatime,size=1024k,nr_inodes=256,mode=750,gid=1028 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,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,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
[email protected]:/ #
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
LordManhattan said:
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
Click to expand...
Click to collapse
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
[email protected] said:
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What kernel are you on?
How did you get root?
Bootloader unlocked?
blueether said:
What kernel are you on?
How did you get root?
Bootloader unlocked?
Click to expand...
Click to collapse
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
[email protected] said:
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
Click to expand...
Click to collapse
I would try to reflash supersu and see if that fixes it
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Any updates ??
EvilMember said:
Any updates ??
Click to expand...
Click to collapse
Strange I'm using this rom: http://forum.xda-developers.com/xpe...14-4-0-118-t2859660/post56113642#post56113642
And I can't mount system to RW, had same issue before on stock but Super SU reflash fixed it...now no way to moint system to RW
MidnightHarvester said:
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Click to expand...
Click to collapse
FAIL:
this doing nothing.
mount -o remount ro /system
[email protected]:/ # mount | grep /system
mount | grep /system
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,noatime,nodiratime,noauto_da_alloc,data=ordered)
dmesg
<6>EXT4-fs (mmcblk0p30): re-mounted. Opts: (null)
kernel ignoring your command. problem is with some service open file for writing in /system and not letting go.
find the service! kill it, mount as RO.
I was able to install lollipop on my phone. But I couldn't get root. I lost some information. So I went back to my backup 4.3 within TWRP and that's when it all went to ****. HWuserdata can't be mounted and sometimes internal_sd can't be mounted either.
What I can do:
-Install new roms
-Install backups [restore them]
-Access to adb
-Can push out img through through adb/fastboot
What I can't do:
-with all of the above, the internal sd doesn't mount in ANY of the roms [both 4.3 and 5.1]
-Can't remove /hwuserdata in TWRP
-Can't remove /internal_sd in TWRP [Error message: E: Unable to mount '/internal_sd']
More Error Messages:
E: Block device not present, cannot wipe internal storage.
E: Unknown MTP message type: 1
E: Unable to wipe 'internal_sd'
Updating partition details...
E: Update to mount 'internal_sd'
Available Partitions as in the Wape menu within TWRP 2.8.7.1
-Dalvik Cache
-Cache
-data
-Internal Storage 11975MB
-System
-Custom Storage
-Internal Storage 0MB [There is actually two of these partition.]
-External Storage
-USB OTG
My best guess is delete the internal sd some how. And/or remove /hwuserdata as well. Or completely return it to stock. Then install 4.3, install TWRP 2.8.7.1, install 5.1, and finally install root. I can't find the img file to push out through adb in "Fastboot&Rescue Mode".
Can someone point me to stock img? This didn't fix my issue within TWRP. I tried installing "MT2L03_B148_Stock_ROM.zip" within TWRP.
All advice would greatly be appreciated.
Thanks!
UPDATE 7/2:
sdcard0 / internal_sd is still broken after applying the downgrade and the b309 rom. Does anyone have the stock rom in an img file format?
Download the public preview of B309 from the blog.
Install it as instructed in the blog post. (You will lose your data, so backup.)
To root and get TWRP, do the below.
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks for the reply. But I am still stuck with a broken sdcard0 / internal_sd partition. Does anyone have a stock rom in an img file format? Applying the B309.zip and downgrading to 4.3 provided by Huawei still hasn't fixed my problem.
Oh my God...... Which version of TWRP did you use when you restored using your 4.3 backup???
Please, tell me you did not use TWRP 2.8.7.1-L or 2.8.7.0-L for that matter???
in current state, maybe you can try use parted to print your current partition table, and paste here
adb within twrp, it has parted builtin, under OS, you need install the binary.
parted /dev/blk/mmcblk0
unit b
print
I'm posting here for public view.
DO NOT USE TWRP-L IF YOU ARE ON JELLYBEAN 4.3. IT IS MEANT ONLY FOR LOLLIPOP.
SHM said:
I'm posting here for public view.
DO NOT USE TWRP-L IF YOU ARE ON JELLYBEAN 4.3. IT IS MEANT ONLY FOR LOLLIPOP.
Click to expand...
Click to collapse
I installed 4.3 with the huawei files and went over to 5.1. I am not sure if I am in the clear yet. I have a "emulated 0" partition for my sdcard0/internal_sd. When I open ES file browser, it says "no sdcard can be found". But I can write to this "emulated 0" partition. I am guessing this is still broken? I am on TWRP 2.8.7.0 with 5.1.
lowao said:
I installed 4.3 with the huawei files and went over to 5.1. I am not sure if I am in the clear yet. I have a "emulated 0" partition for my sdcard0/internal_sd. When I open ES file browser, it says "no sdcard can be found". But I can write to this "emulated 0" partition. I am guessing this is still broken? I am on TWRP 2.8.7.0 with 5.1.
Click to expand...
Click to collapse
Open terminal, type and enter, su, then type and enter, mount. Share with me what mount says.
That's the same as mine
lowao said:
I installed 4.3 with the huawei files and went over to 5.1. I am not sure if I am in the clear yet. I have a "emulated 0" partition for my sdcard0/internal_sd. When I open ES file browser, it says "no sdcard can be found". But I can write to this "emulated 0" partition. I am guessing this is still broken? I am on TWRP 2.8.7.0 with 5.1.
Click to expand...
Click to collapse
The emulated 0 partition is the same as I have. That should be your internal memory.
robertbarber said:
The emulated 0 partition is the same as I have. That should be your internal memory.
Click to expand...
Click to collapse
Still, to be sure he didn't screw something up since he did use TWRP-L while on 4.3 JellyBean, I still want to see what, mount, displays for him on his terminal.
Emulated partition
I'm using X-plore file manager and I'm not seeing internal_sd but rather getting the internal SD drive showing up under Root/Storage/Emulated/0
I've tried reverting back to 4.3 and associated TWRP, but X-plore still doesn't show internal_sd properly. I'm pretty sure it used to show it properly...or am I imagining it
CromDubh said:
I'm using X-plore file manager and I'm not seeing internal_sd but rather getting the internal SD drive showing up under Root/Storage/Emulated/0
I've tried reverting back to 4.3 and associated TWRP, but X-plore still doesn't show internal_sd properly. I'm pretty sure it used to show it properly...or am I imagining it
Click to expand...
Click to collapse
On 4.3 yes, on 5.1 yes, but on 5.1 it's main location is /data/media/0
You can check by opening terminal and typing then entering, mount.
so as long as it accessible by going to /data/media/0 then its all okay, even though it doesn't show up as an actual drive under X-Plore?
Thanks for your time and help.
Terminal Emulator output
SHM said:
Open terminal, type and enter, su, then type and enter, mount. Share with me what mount says.
Click to expand...
Click to collapse
Mine is also screwed up after the upgrade and I cannot get back to stock, nor can I get TWRP back. Yes, I've reflashed supersu etc. Here's my dump.
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,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
none /dev/frz cgroup rw,relatime,freezer 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 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 /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
[email protected]:/ #
tomlogan1 said:
Mine is also screwed up after the upgrade and I cannot get back to stock, nor can I get TWRP back. Yes, I've reflashed supersu etc. Here's my dump.
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,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
none /dev/frz cgroup rw,relatime,freezer 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 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 /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
[email protected]:/ #
Click to expand...
Click to collapse
Define screwed up? Everything looks normal for your mount points.
Screwed up
SHM said:
Define screwed up? Everything looks normal for your mount points.
Click to expand...
Click to collapse
Updated to 5.1 (was a beta tester). After the upgrade, root, but no TWRP. Tried numerous times to reflash TWRP-L but still the stock EMUI 3 persists. Have verified I can fastboot TWRP to restore previous backups and create new backups but cannot make TWRP permanent.
Have tried the reinstall of SuperSI 2.4x and all the steps multiple times with no success. Tried the Huawei downgrade to B148 and that fails as well.
Regarding trying to install TWRP, that is because of the 5.1 Rom. It checks to see if the recovery is stock. If it isn't then it will overwrite the custom recovery. TWRP has to be booted and system has to be mounted as read/write, not read only, in order for it to patch the Rom so TWRP will stick.
I can't help regarding the beta test Rom though. I was not a tester. So I cannot say specifically what changes there were between the beta Rom and official released Rom. Maybe @xordos, @kimtyson, @Iguanadon, @ScoobSTi or someone else can assist regarding your current dilemma.
tomlogan1 said:
Updated to 5.1 (was a beta tester). After the upgrade, root, but no TWRP. Tried numerous times to reflash TWRP-L but still the stock EMUI 3 persists. Have verified I can fastboot TWRP to restore previous backups and create new backups but cannot make TWRP permanent.
Have tried the reinstall of SuperSI 2.4x and all the steps multiple times with no success. Tried the Huawei downgrade to B148 and that fails as well.
Click to expand...
Click to collapse
Try removing anything related to twrp on internal and/or external sd. Backup if needed. Then fastboot boot twrp. You should get the prompt about read/write.
Edit: remember to use 2.8.0 L
Sent from my MT2L03 using XDA Free mobile app
I am also new to the 5.1 fused internal storage. following is what I noticed.
/sdcard is soft link to /storage/emulated/legacy, which in turn is link to /storage/emulated/0, which again is link to /mnt/shell/emulated/0, which is the internal storage fused to /data: /data/media/0.
But some how ES file explorer can not handle it. In ESFileExplorer in my B309, it show /sdcard as a *file* with a tiny link icon, instead of others normal one (like /vendor) which showed as a *folder* with a tiny link. And every time, when I open ESFileExplorer, it also report error, "/sdcard can not find" something like that. I have to go to its settings page, Directory Settings, and set "Home Directory" to "/storage/emulated/0", then the error is gone. For me, I changed it to /storage/sdcard1, which is my external sdcard.
Another side notes, if sometime your app (that requires root) complains can not write to storage, goto SuperSU settings, and disable "Mount namespace separation", this may help resolve lots of problem.
These is more info from the command line, I can not tell the different between /sdcard and /vendor, but ESFileExplorer can not open /sdcard
(when run these "ls" as non-root user, the result is same)
Code:
[email protected]:/ # ls -l sdcard
ls -l sdcard
lrwxrwxrwx root root 1970-01-01 00:20 sdcard -> /storage/emulated/legacy
[email protected]:/ # ls -l vendor
ls -l vendor
lrwxrwxrwx root root 1970-01-01 00:20 vendor -> /system/vendor
[email protected]:/ # ls -l sdcard/
ls -l sdcard/
drwxrwx--- root sdcard_r 2008-12-31 18:48 Alarms
drwxrwx--x root sdcard_r 2015-07-03 03:36 Android
...
[email protected]:/ # ls -l vendor/
ls -l vendor/
drwxr-xr-x root shell 2015-06-24 13:09 etc
drwxr-xr-x root shell 2015-06-24 13:09 firmware
...
PS, Just realized in the phone setting-storage, I can set default storage to "External", then after that /sdcard become normal as it is not link to fused FS anymore:
Code:
[email protected]:/ # ls -l /sdcard
ls -l /sdcard
lrwxrwxrwx root root 1970-01-01 04:15 sdcard -> /storage/sdcard1
[email protected]:/ # ls -l /storage
ls -l /storage
dr-xr-xr-x root root 1970-01-01 04:15 emulated
lrwxrwxrwx root root 1970-01-01 04:15 sdcard0 -> /storage/emulated/0
drwxrwxr-x root sdcard_rw 2015-07-03 12:50 sdcard1
drwx------ root root 1970-01-01 04:15 uicc0
drwx------ root root 1970-01-01 04:15 usbotg
Why did I not have any problems booting into fastboot, flashing TWRP-L through fastboot, booting directly into TWRP, enabling the read/write dialog option, then flashing SuperSu? TWRP survives, root worked, etc
Couldn't have been a more standard way of going about it.
Also, I had a problem with my external SD card being read only after lollipop update, but I think I fixed it by going to settings and changing default storage to external sd card and rebooting. Now both internal and external can be written to.