Related
I have a Huawei T-Mobile Mytouch 4G Q slider (U8730) and i have successfully rooted it. I havent flashed any ROM's or anything like that and i have browsed through alot of the forums and Google and havent found what i need to know. I need to know how to use the "mount a filesytem read-write" command, i know the syntax:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
i just dont know what information to input in the command.
i know i can use:
# mount
and that will give me a lot of info but im not too sure what im looking for.
if theres another thread about this, i apologize, im new to this forum and not 100% how to navigate.
heres what it says when i do # mount
im not sure what im looking for here
please help O:
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
/dev/block/mmcblk0p14 /HWUserData vfat rw,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /.cust_backup vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/loop0 /cust ext3 ro,relatime,barrier=0,data=writeback 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered 0 0
hwvefs /data/huawei_hwvefs fuse.hwvefs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:33 /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:33 /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,er
rors=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.ultimateguitar.tabs-1 vfat ro,dirsync,nosuid,nodev,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.ovelin.guitartuna-1 vfat ro,dirsync,nosuid,nodev,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/net.andchat-1 vfat ro,dirsync,nosuid,nodev,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.ddm.iptools-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
Which specific partition do you want to mount read write?
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
Which specific partition do you want to mount read write?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
oh man!! im not sure what that means! just need to mount rw for apps
orionsfl said:
oh man!! im not sure what that means! just need to mount rw for apps
Click to expand...
Click to collapse
Partition refers to a specific file system. For example the /boot partition contains the kernel and ramdisk for booting up your device (Note: /boot partition and bootloader partition are not the same thing), the /cache partition contains cache files, the /system partitions contains your system apps and other system folder such as bin and xbin and other. What apps are you trying to use that you need to mount rw for? But if you wanted to modify your /system partition for example you would run the following command from ADB shell or terminal emulator to mount it rw (Read/write):
Code:
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p12 /system
Let me know if you still have questions about this.
Try this:
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Hit thanks if I helped.
Sent from my Nexus 4 using Tapatalk 2
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.
Anyone had any luck? Tried a flash drive I use on other Androids and the Am2 won't register it. I'm not yet rooted or anything for what it's worth.
JJ2525 said:
Anyone had any luck? Tried a flash drive I use on other Androids and the Am2 won't register it. I'm not yet rooted or anything for what it's worth.
Click to expand...
Click to collapse
It may be your otg cable. My ham 2 worked unrooted and rooted with a 1tb external and a 16gb flash drive. It almost worked with my Ps4 gold headset but the audio cuts in and out.
aragon257 said:
It may be your otg cable. My ham 2 worked unrooted and rooted with a 1tb external and a 16gb flash drive. It almost worked with my Ps4 gold headset but the audio cuts in and out.
Click to expand...
Click to collapse
Hmm. It's a 2-way drive (with a micro usb plug on one side and usb on the other). I tried plugging directly into AM2 with the micro, then tried plugging the usb side into an otg cable that plugged into the AM2. Neither worked. The drive works flawlessly on my Z2 and Tab S.
I've now tried 2 drives, both in FAT format, and the AM2 does not recognize either, but each drive works perfectly on other devices. I've also tried the device on both mine and my friend's AM2's, same result. Perplexing.
Instead of referring to your device as the HAM2 it may be more proficient to actually specify which one you have so it doesn't cause confusion for other readers who are still learning the basics. For example, the MT2-L05 has OTG support but the MT2-L03 does not.
My apologies, I did not realize there was a discrepancy in USB support between the two models.
Yes, I have the L03. So there is no way to use a USB drive with my device?
JJ2525 said:
My apologies, I did not realize there was a discrepancy in USB support between the two models.
Yes, I have the L03. So there is no way to use a USB drive with my device?
Click to expand...
Click to collapse
OTG support would have to be built in to the MT2-L03 by modifying the kernel source and the ramdisk from your boot.img. It's a very difficult task. I have tried to do this on my daily device and wasn't successful, but came very close to it lol. However, I gave up on that project for my phone a while back. I'm currently working on making my device F2FS compatible to replace ext4 for system, data, and cache.
Modding.MyMind said:
Instead of referring to your device as the HAM2 it may be more proficient to actually specify which one you have so it doesn't cause confusion for other readers who are still learning the basics. For example, the MT2-L05 has OTG support but the MT2-L03 does not.
Click to expand...
Click to collapse
I have the MT2-L03 and OTG works fine. I have used both a Sony 2-way flash drive and a regular flash drive with an OTG cable. I can read, stream and write to and from the drives. I am rooted, but it also worked before rooting. I use ES File Explorer to access the drives.
gale2000 said:
I have the MT2-L03 and OTG works fine. I have used both a Sony 2-way flash drive and a regular flash drive with an OTG cable. I can read, stream and write to and from the drives. I am rooted, but it also worked before rooting. I use ES File Explorer to access the drives.
Click to expand...
Click to collapse
If this is true then maybe you can inform me of the directory path which would be mounted for OTG? I can add this to TWRP. However, I must admit, I did not see any evidence of OTG support for the MT2-L03, but I did see it with the MT2-L05.
Modding.MyMind said:
If this is true then maybe you can inform me of the directory path which would be mounted for OTG? I can add this to TWRP. However, I must admit, I did not see any evidence of OTG support for the MT2-L03, but I did see it with the MT2-L05.
Click to expand...
Click to collapse
I don't know how to find the path, but I am attaching a screen shot from ES file explorer. The device is USB1002. Any instructions as to how to find the path.
gale2000 said:
I don't know how to find the path, but I am attaching a screen shot from ES file explorer. The device is USB1002. Any instructions as to how to find the path.
Click to expand...
Click to collapse
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Modding.MyMind said:
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Click to expand...
Click to collapse
I have to go now, but will do this tomorrow morning.
Modding.MyMind said:
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Click to expand...
Click to collapse
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[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
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/log /log ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,nosuid,nodev,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/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/vold/179:25 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /storage/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
[email protected]:/ $
Sent from my MT2L03 using Tapatalk
---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------
I have an otg cable connected to a cf card reader and able to access the files.
Sent from my MT2L03 using Tapatalk
"mount" didn't show any results for OTG. Were you plugged up before you ran the mount command?
Modding.MyMind said:
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Click to expand...
Click to collapse
Here's my results. OTG is plugged in:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[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
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/log /log ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,nosuid,nodev,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/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/vold/179:65 /storage/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:25 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
The full path given in properties for the USB device is: usb://1002/SANDISKBLUE
Will have to look deeper on my end. Mount isn't showing what I need.
Modding.MyMind said:
Will have to look deeper on my end. Mount isn't showing what I need.
Click to expand...
Click to collapse
I've tried OTG previously and I thought that OTG was not working. After seeing gale2000's screenshot, I gave it another try. After a reboot, I can see the SD card reader ONLY in ES File Explorer. It doesn't appear anywhere else in ES either. (It only appears in the LOCAL section as shown on gale2000's screen. ) I can't find it in 3c Toolbox. It doesn't appear in mount report. It doesn't appear in Huawei's own supplied file manager and it doesn't even appear in the settings screen. So there is no graceful way of disconnecting the reader without rebooting or powering down.
At the top of the screen ES normally has a box for the parent folder but for the USB reader, it is blank and ES reports the device as USB://1002/
After seeing these posts I tried my own 2-way drive. Sure enough, it shows up in ES under local/usb 1002. Fully functional, did not have to reboot before/after plugging it in, able to xfer files to/from drive flawlessly. Awesome
I was looking through build.prop and noticed the line
ro.config.hw_otg_support=false
I changed it to
ro.config.hw_otg_support=true
Now otg works without having to use ES File Explorer.
This is all perplexing! I too have the L03 and was surprised that it wouldn't read my flash drive. But I knew SOMETHING was happening, because the light on the drive lit up, but I couldn't find the directory anywhere in the stock explorer or in Total Commander. I'll have to try ES as well now :good:
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.
Hi all
I have in my hands a Samsung YP G70 with this problem: I need to format it, clean it COMPLETELY.
I tried the following things:
1-Using the stock recovery, clean data and cache
2-Flash via Odin (different processes): his original firmware (same version), another firmware, a Kernel that should included the CWM Recovery
3-Root with Kingo
4-Tried to flash the TWRP flashable version into his stock recovery
5-Restore at factory default from the player
No one worked
After the reboot I will always have the same data (same accounts, same photos, same apps)
If I add a file, after a reboot, the file disappear; if I delete a file, after a reboot, the file re-appear.
So: how can I completely clean it? Or should I trash cause the memory allocator gone crazy?
Thanks a lot
GeniusJack said:
Hi all
I have in my hands a Samsung YP G70 with this problem: I need to format it, clean it COMPLETELY.
I tried the following things:
1-Using the stock recovery, clean data and cache
2-Flash via Odin (different processes): his original firmware (same version), another firmware, a Kernel that should included the CWM Recovery
3-Root with Kingo
4-Tried to flash the TWRP flashable version into his stock recovery
5-Restore at factory default from the player
No one worked
After the reboot I will always have the same data (same accounts, same photos, same apps)
If I add a file, after a reboot, the file disappear; if I delete a file, after a reboot, the file re-appear.
So: how can I completely clean it? Or should I trash cause the memory allocator gone crazy?
Thanks a lot
Click to expand...
Click to collapse
Please post the output of "mount" after a normal boot ( not in recovery )
You can do this in adb by doing:
adb shell
su
mount
or in a terminal app
su
mount
Then copy the output here or a screenshot with the info is fine...
$ su
su: not found
$ 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
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/u
id/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid
/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/
uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,no
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Is it ok?
GeniusJack said:
$ ...
Click to expand...
Click to collapse
If you have the USA variant try flashing this with Odin:
http://www.4shared.com/zip/hFJmoXTiba/YP-G70-UEKI8-Stock-USA-Meticul.html?
Flashed via Odin3 v1.87 into PDA but after the reboot I have the same data as before, so not worked...
GeniusJack said:
Flashed via Odin3 v1.87 into PDA but after the reboot I have the same data as before, so not worked...
Click to expand...
Click to collapse
Hmm.. Not sure whats goin' on.... When did this start???
I really don't know
A friend gave it to me asking for a check because he noticed that when installed an application, after a reboot the app disappears.. He thought about a virus so he asked to clean it...
GeniusJack said:
I really don't know
A friend gave it to me asking for a check because he noticed that when installed an application, after a reboot the app disappears.. He thought about a virus so he asked to clean it...
Click to expand...
Click to collapse
You could try the "getto lagfix":
This converts your file systems from rfs to ext4...
It's been a long time since I messed with stock GB so read and understand carefully before attempting...
http://forum.xda-developers.com/showthread.php?t=1445840&page=9
But I don't have a CWM, everything is stock, without root etc...
GeniusJack said:
But I don't have a CWM, everything is stock, without root etc...
Click to expand...
Click to collapse
So even if you flash a kernel it does not change?
Nope... Tried but not works... Same kernel after the reboot from Odin
GeniusJack said:
Nope... Tried but not works... Same kernel after the reboot from Odin
Click to expand...
Click to collapse
Seems like a hardware issue. Check dmesg/kmsg for errors...
Noob question coming.....
How?