Hi all,
I just replace the internal memory with an 8 GB microSD, then I run the adb logcat and there is a message as follows:
EXT2-fs error (devices loop0): ext2_lookup:
deleted inode referenced: 20679
What does it mean? whether there are errors in the partition?
Hi, after you replaced the internal sdcard... i think you need a "new" Rom... flash... (Factory Reset?)
MfG
UKSheep
UKSheep said:
Hi, after you replaced the internal sdcard... i think you need a "new" Rom... flash... (Factory Reset?)
MfG
UKSheep
Click to expand...
Click to collapse
Yes, I already did flashing a new rom. But that doesnt fix it
hm, sorry...
i know no solution.
There is a thread over at MoDaCo that tells you how to do it. You will need to keep the partition sizes the same and use a modified boot.img file in order for your streak to recognise the bigger card.
I'm also pretty sure that there is the modified boot.img files for all versions of the streak roms on that thread for you to download.
I've often thought about doing it, but I'm not brave enough yet
I am intersted in this too but still no clarity, for me at least. Glad you are braver than some of us.
There is also a thread
http://android.modaco.com/content/d...6477/lcd-replacement-and-internal-sd-upgrade/
Keep us informed and I, for one, will follow. 32Gb Class 10 cards are no longer outrageous prices and that capacity will make the exercise worthwhile for me.
According to the other thread you can go to at least 4gig without any special files.
Btw, previously I have made 3 partitions for the internal memory card as follows:
-- Partition 1: 2GiB ext2
-- Partition 2: 1GiB ext3 (named cache)
-- Partition 3: 5 GiB ext4 (named Data)
Is there an error in setting up partition?
I use steve streak droid 1.7. And the system read 6,12GB for internal memory
Please help
Hello, the partitions you are showing seem to be ok...
what was the use for you to swap the internal sd ? speed, more space for apps ?
How did you manage to obtain those partitions ? did you followed the howto from modaco's forum ?
Could you provide me the output of a mount command ?
to finish, did you change the original boot.img to a modified one, provided in the same forum ?
I'm willing to help you, but you need to provide me those informations !
Good luck,
Boujou bien,
K.
kwenteen said:
Hello, the partitions you are showing seem to be ok...
what was the use for you to swap the internal sd ? speed, more space for apps ?
How did you manage to obtain those partitions ? did you followed the howto from modaco's forum ?
Could you provide me the output of a mount command ?
to finish, did you change the original boot.img to a modified one, provided in the same forum ?
I'm willing to help you, but you need to provide me those informations !
Good luck,
Boujou bien,
K.
Click to expand...
Click to collapse
Hi, my priority is the speed in running application. To obtain those partition i use gparted live via usb. honestly I didn't follow the howto from modaco forum and I didn't change the original boot.img.
What should I do now? Thanks for your support.
here is the output of mount command:
export PATH=/data/local/bin:$PATH
sh-4.1$ export PATH=/data/local/bin:$PATH
sh-4.1$ root
sh: root: command not found
sh-4.1$ su
sh-4.1# 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
/dev/block/mtdblock6 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock7 /firstboot yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/innersd0p5 /cache ext3 rw,noatime,nodiratime,errors=continue,commit=99999,data=writeback 0 0
/dev/block/innersd0p6 /data ext3 rw,noatime,nodiratime,errors=continue, commit=99999,data=writeback 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/loop0 /mnt/asec/extdata ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0 0
/dev/block/vold/179:17 /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:17 /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.ArtInGames.AirAttackHDLite-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/com.agilesoftresource-2 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/com.rovio.angrybirdsrio-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-3 /mnt/asec/com.rovio.angrybirds-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
sh-4.1#
up up please help
/dev/block/innersd0p5 /cache ext3 rw,noatime,nodiratime,errors=continue,commit=99999 ,data=writeback 0 0
/dev/block/innersd0p6 /data ext3 rw,noatime,nodiratime,errors=continue, commit=99999,data=writeback 0 0
/dev/loop0 /mnt/asec/extdata ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0 0
apparently, your /data and /cache partitions seem to be found by your device, and well mounted... which is quite weird, because you didn't changed your boot.img.
I'm wondering if you're not using a mod made to speed up the rom, by using your external sd to be used for data ? That could be related to the loop line in your mount command, that may be related to the error you see in logcat...
what are the symptoms on your phone, besides the message ? can you install apps ?
I would advise you to try a modded boot.img, you will find the file for your streakdroid version on the modaco link that someone posted earlier... it won't delete your files, and should help ! use fastboot to flash it !
I think it should solve your problem !
good luck,
Boujou bien,
K.
kwenteen said:
I'm wondering if you're not using a mod made to speed up the rom, by using your external sd to be used for data ? That could be related to the loop line in your mount command, that may be related to the error you see in logcat...
what are the symptoms on your phone, besides the message ? can you install apps ?
I would advise you to try a modded boot.img, you will find the file for your streakdroid version on the modaco link that someone posted earlier... it won't delete your files, and should help ! use fastboot to flash it !
I think it should solve your problem !
good luck,
Boujou bien,
K.
Click to expand...
Click to collapse
so the setting is still using the external card for data? how do I move it to an internal card which is certainly faster (class 10 vs class 2)?
Apart from these error messages, no problems when using the handset. I also can install the application.
I've tried boot.img and it seems an error message is gone. I'm still wondered the use of data in the internal card, please guide.
Up ul about internal sd
normally by flashing the new boot.img, you should have a "normal" setup, meaning without the loop device...
just run once more the mount command, and see if you still have this loop mounted !
And if yes, I suggest you to flash a fresh rom, that doesn t have this option, like the streakdroid 190, and be sure to replace in the update.zip file the original boot.img with the alternate one available on modaco...
And beware of the option you select with this install, some of them are incompatible with the innersd mod !
good luck !
K.
Related
I soft bricked my Vibrant after installing Bionix 1.4 w/Jacs OC/UV/Voodoo kernel. I used Odin to flash back to stock rom which was unsuccessful. It allowed me to boot to the samsung logo and then go black.
Grasping at straws I used clockwork recovery to do a nandroid restore to the vibrant9 rom I was running before (with the KingKlick kernel, but as I understand it nandroid doesnt backup or restore kernels). I thought maybe the kernel got switched back to the stock one but I'm lacking a ROM? Anyway, nandroid restored the system files but when going to restore data it gave me an error about not finding mmcblk0p2, when I go into adb shell and type mount, it tells me I have mmcblk0p3.
Is there any way for me to fix this so I can restore from my nandroid backups? I have everything in titanium and I can still access all the data on the sd card, but I'd really like to just have things back to how they were before installing the Bionix.
Thanks!
Here is a complete copy of what comes up when I hit mount if it helps. Could really use some assistance here, I try to do as much on my own as possible but I've hit a dead end.
Code:
$ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx
,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/loop0 /data/data1 j4fs rw,noatime,nodiratime 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
$ adb reboot recovery
Ok, thanks for all the help guys....
Anyway, for anyone who is having the same problem, I found my solution to be to get into download mode via instructions here: http://forum.xda-developers.com/showthread.php?t=741027&highlight=unbrick
And then follow the instructions in Fix 1 here: http://forum.xda-developers.com/showthread.php?t=782027
I had to upgrade to froyo then downgrade to get my file system back.
I'm now on stock Vibrant kernel and rom, but flashing Bionix 1.5 in a moment (NO VOODOO!!!)
Exact same thing
i had to do the exact same thing this morning. except mine would boot up fully. i couldnt get the internal memory to recognize at all so i couldnt disable the lagfix
blah blah blah... odin and fix 1 worked. i wished i had backups on my computer i should know better by now too. thats the stupid part. all that data lost.
Yea, I'm not new to this sort of thing, just this piece of hardware. I felt really confident after flashing a few ROM's and always read instructions for each new install, I was really surprised to find myself in that pickle. At least I learned something.
Going forward I'm being very dilligent about organizing a backup of my nandroid backups, different ROM's, everything needed to get back to stock, and most importantly the contents of my internal SD card! Nothing had ever messed with that partitioin before so I thought it would be fine, I also thought that nandroid or titanium would backup all my e-books since they were imported into Aldiko, WRONG-O!, it just saves the library index, gotta re-import over 600 books :O
Gotta love nothing ever being good enuf, now I'm off to fix what I broke on my car...
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
icezar1 said:
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
Click to expand...
Click to collapse
Ok, i'll try now to pack my first worlwide rom!
kawa636r said:
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Click to expand...
Click to collapse
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
winwiz said:
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
Click to expand...
Click to collapse
seems to be yes, because samsung apps stay forever in background.
I'm trying to take nexus s keyboard and port to s2, but where are keyboard files located?
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
In shell type mount and see on what stl is mounted /system. I DONT OWN A SGS 2! If you don't have some basic linux knowledge and dont know how the phone works, don't do this! I'm really serious!
But if you wanna go ahead you will need to find out your mount points. Is vital!
How i can see on what stl is mounted system? there isn't an fstab file?
kawa636r said:
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
Click to expand...
Click to collapse
SGS2 has different mount points. I see mention of RFS as well, which is wrong for the SGS2...
# mount
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
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 /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
nil /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
Somebody can help me for the commands that i must do for creating a ROM?
kawa636r said:
Somebody can help me for the commands that i must do for creating a ROM?
Click to expand...
Click to collapse
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
pulser_g2 said:
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
Click to expand...
Click to collapse
from my response of mount command you can't help me?
kawa636r said:
from my response of mount command you can't help me?
Click to expand...
Click to collapse
Nope, sorry. I need the device to figure it out really, as I've not worked with a Samsung before. And I don't know about repackaging a ROM into a tar for ODIN based on a dump.
I wouldn't want to try and help either, as I need the device to actually check it properly, and wouldn't want you or someone else to have to try reflashing after messing something up...
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
pulser_g2 said:
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
Click to expand...
Click to collapse
Yes, but stock rom come with odin files format.
If i want to cook a rom i must start from sources, from a system dump, or from a zip rom (in nexus s i remember that rom are packaged in zip)....
Me too
I have the same problem, do you have find a solution?
I don't want to ruin your mojo, the more people interested in android, the better... but I'm a bit worried if inexperienced people give other inexperienced people things to flash with Odin. Since your ROM doesn't bring anything new (all other roms have this already), why not put some more time in it, polish it a bit, and maybe you will get some original ideas to add to it, instead of rushing it like this, and possibly brick some phones?
The probleme is that i have no time to do this, i have created a system and i have modivied the cyanogenmod to work with this system, the probleme is that i should to find a better methode to install the cyanogenmod rom from a pc, it is not for me is for other simple users.
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.
I see various options for converting system apps <==> user apps and moving or linking some to SD. But I don't see a good general discussion of this. Also, I think my old phone needs a more hard core approach--probably one that trims down /system and reduces how much /system overlaps redundantly with updates on /data. So here goes...
First off, these solutions seem inadequate:
built-in apps2sd: it still fills up internal memory a lot.
s2e: an all-or-nothing approach for each category
free version of link2sd: cannot move-and-link app data, nor system apps
I've been fairly happy with link2sd, but it's still not radical enough for me. Can s2e be combined with it to reclaim even more space?
Assumptions about a stronger solution:
It will require root access.
It will break OTA (can this be turned off safely? can someone link to a good overview of problems/workarounds?)
It *might* require a fairly fast SD card (but still limited to an old phone's bus speeds, etc.) Note: I just bought a 32GB class 10 SDHC card (UHS-1 U3) for my s5360.
It might require one or two paid apps (hopefully not)
One of the most promising options I've seen is to convert system apps to user apps and then move-and-link them to SD. For the conversion step, do the following all do the same thing?
link2sd Plus (paid)
Titanium Backup Pro (paid)
System Tuner (paid) -- I've tried the free ones and move (and freeze) always fails.
app mover (free) http://forum.xda-developers.com/showthread.php?t=1999346
And are there rules of thumb for what can be safely converted?
EDIT: I just found this handy list--my guess is that any green or yellow Yes can be safely converted to a user app and even moved/linked to SD, but that red shouldn't, and think twice before uninstalling yellow :
http://wiki.cyanogenmod.org/w/Barebones#CM-10.1_App_list_.28WIP.29
Can apps that were moved to /data still be updated? I'd especially like to target outdated system apps that are have already been updated anyway and are thus running from /data anyway. My understanding is that 'moving' those to /data doesn't increase /data usage and doesn't reduce performance--just slightly reduces permissions--as long as I don't move/link them to SD.
lightningdude said:
In all seriousness, though, I'm not entirely sure the Link2SD has good implementation of this method. You might try Titanium Backup to convert system to user apps, then try linking it with Link2SD. It may still not work, but it'd be worth a shot, I suppose.
Furthermore, I always delete bloatware I'm not going to use with Titantium Backup. If I need to go back to stock for an OTA, I just flash the complete stock of whatever phone I'm on.
Click to expand...
Click to collapse
If this can all be done successfully, can the internal partitions then be resized? That is, if we safely shunt some of /system and /cache off to SD, can we then let /data steal some space from both? (My s5360 has this by default: /system 230MB, /cache 40MB, /data 197MB)
My old s5360 seems to get full almost immediately after flashing a cm11 rom (LolliKat) and minimal gapps onto it, although I plan to try again with a version of minimal gapps that installs to SD.
For that matter, can some ROMs be installed primarily to SD? I get the impression that that's how some dual-boot (multiROM) approaches work, but I don't really know.
I've also seen one guide for permanently mounting /system as read-write. I think I'd be ok with that (are the security concerns truly awful?), especially if it meant that system apps would update themselves in-place without impacting /data. But I'm guessing it's not that simple.
can't create /system/... Read-only file system
I found another cool feature of link2sd to "integrate update into system", removing it from data and eliminating the double use of space. The free version includes this feature, but unfortunately it always errors out for me:
`sh: [51]: can't create /system/app/Music.apk.t: Read-only file system`
I tried upgrading to link2sd Plus, since that's the version that includes a convert feature, which requires write access to /system:
C-Jon said:
One of the most promising options I've seen is to convert system apps to user apps and then move-and-link them to SD.
Click to expand...
Click to collapse
But that feature failed too, for the same reason. So I tried all of the following--granting each app superuser access for 10 minutes each time--and they also failed to successfully mount /system as RW:
X-plore - long press the / folder and choose System Shell, then enter `su` and `mount -o remount,rw /system /system`. It gives no error, but if I then immediately `cd system` and try to `mkdir xxzz` it gives an error: `can't create directory 'xxzz' : Read-only file system`. If I use the GUI, I can apparently create a folder under /system with no error, but if I browse up and come back, the folder is gone.
ES File Explorer (free version) - menu, Root Explorer, Mount R/W. I tried running it multiple times, setting both `/` and `/system` to RW. After doing this a couple times, `/` showed up as already RW, but `system` never did. I immediately retried link2sd Integrate--fails with same error.
mountsystemrorw - this app is dedicated to this one task, and when I click "MOUNT /system RW" it claims success ("Your system is now mounted RW!"); but it actually fails. (At least, link2sd Integrate and X-plore still give the same error/failures.)
AnExplorer - menu, Root. I don't see 'mount' options.
Has KitKat made it nearly impossible to mess with /system, even as root? Or am I doing something wrong?
Just in case, I tried re-running "recreate mount scripts" in link2sd, which had worked before, and this time it failed too! `can't create /system/etc/init.d/11link2sd: Read-only file system`. So maybe something has changed since I first installed link2sd. Hmm. I do see this in a thread on stack exchange, "Write access to the system partition is usually blocked by the kernel at boot." But "recreate mount scripts" worked before, *after* I'd flashed the current kernel (Kernel Bangprovn#1.zip) and ROM (LolliKat Stable 2.zip). That's how I got the ext4 partition working for link2sd in the first place.
I'm getting frustrated and don't want to have a big fight every time I want to integrate or convert an app. So I'm wondering just how feasible the following might be...
I've also seen one guide for permanently mounting /system as read-write. I think I'd be ok with that (are the security concerns truly awful?), especially if it meant that system apps would update themselves in-place without impacting /data.
Click to expand...
Click to collapse
I'm guessing they wouldn't simply self-update. But if I could easily run the Integrate step without this RW battle, that might be enough.
If it helps, here is my mount info:
Code:
cat /proc/mounts
rootfs / rootfs ro,noatime,nodiratime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,seclabel,noatime,nodiratime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,noatime,nodiratime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 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 /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock8 /system yaffs2 ro,seclabel,noatime,nodiratime 0 0
/dev/block/mtdblock9 /cache yaffs2 rw,seclabel,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock10 /data yaffs2 rw,seclabel,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data/sdext2 ext4 rw,seclabel,relatime,barrier=1,data=writeback 0 0
/dev/block/vold/179:1 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,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/sdcard0 fuse rw,nosuid,nodev,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
using bin/mount rather than xbin/mount
I finally found a solution: remount by explicitly using `/system/bin/mount -o ...` rather than just `mount -o ...`. I'm guessing that at some point the version in /system/xbin started taking priority and for some reason that version fails silently. More info here:
http://android.stackexchange.com/a/110883/109855
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.