HEllo
Just installed JellyBam 8.2 and loving it!
Having one small issues with how the extSdCard permissions
On my internal memory (eg /sdcard) i can see directories as 775 permission with user "root" and group "sdcard_rw". These files are fine to read from all apps.
I am using isyncr wifi to sync my mp3s to the external sd card and in the directory it creates (/mnt/fuse/scard1/syncr) all the directories are created as 644 (ie not executable) with user "u0_a152" and group "u0_a152"
Hence my music player app (player pro) cant see the files. Only root explorer can.
I've tried the permission fix mentioned where you edit platform.xml and adding media_rw permissions for WRITE_EXTERNAL_STORAGE
http://forum.xda-developers.com/showthread.php?t=1458021
So any clues?
Many thanks
axelnormand said:
HEllo
Just installed JellyBam 8.2 and loving it!
Having one small issues with how the extSdCard permissions
On my internal memory (eg /sdcard) i can see directories as 775 permission with user "root" and group "sdcard_rw". These files are fine to read from all apps.
I am using isyncr wifi to sync my mp3s to the external sd card and in the directory it creates (/mnt/fuse/scard1/syncr) all the directories are created as 644 (ie not executable) with user "u0_a152" and group "u0_a152"
Hence my music player app (player pro) cant see the files. Only root explorer can.
I've tried the permission fix mentioned where you edit platform.xml and adding media_rw permissions for WRITE_EXTERNAL_STORAGE
http://forum.xda-developers.com/showthread.php?t=1458021
So any clues?
Many thanks
Click to expand...
Click to collapse
You say /mnt/fuse/sdcard1, but you're not going to the directory using that path are you?
Couple of notes
1) please post questions in the q&a section. General is not for questions (You can report your thread and ask it to be moved using the /!\ button.
2) JellyBam discussion is banned on XDA
Sorry posted this in the wrong place, and thank you for the reply
The isyncr wifi program i assume just writes to the external sd card using the path provided to it by the OS?
I dont actually choose the absoulte path in isyncr, rather just select internal or external sd card and then the directory name to sync to.
Should i try to force it to use /mnt/extSdCard then?
Thanks
axelnormand said:
Sorry posted this in the wrong place, and thank you for the reply
The isyncr wifi program i assume just writes to the external sd card using the path provided to it by the OS?
I dont actually choose the absoulte path in isyncr, rather just select internal or external sd card and then the directory name to sync to.
Should i try to force it to use /mnt/extSdCard then?
Thanks
Click to expand...
Click to collapse
/storage/extSdCard would be where I imagined the app reads it from. Do you have a normal (Non-root) file manager that you can use to browse that location and confirm you can get to the files?
rootSU said:
/storage/extSdCard would be where I imagined the app reads it from. Do you have a normal (Non-root) file manager that you can use to browse that location and confirm you can get to the files?
Click to expand...
Click to collapse
Using normal non-root file manager i can browse to other directories on extSdCard fine (eg TitaniumBackup directory)
However the syncr directory is returned as empty
axelnormand said:
Using normal non-root file manager i can browse to other directories on extSdCard fine (eg TitaniumBackup directory)
However the syncr directory is returned as empty
Click to expand...
Click to collapse
I really don't know what is going on here. The /extSdCard is mounted with a single set of permissions and nothing should be able to change those permissions except at boot.
Have you tried removing the folder with RE, reboot then try sync again?
In terminal emulator, what is teh output of "mount" command please?
it is strange isnt it!
anywho thanks again for reply
I have tried deleting folder in Root Explorer and re-sync. But will try that again
Here is the mount command output
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.fatattitude.buschecker-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/net.dinglisch.android.taskerm-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.touchtype.swiftkey-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.kodek.pebbletasker-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/ptc.jp-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.twentyfivesquares.press-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.corecoders.skitracks-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.koushikdutta.rommanager.license-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.melodis.midomiMusicIdentifier-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.jrtstudio.iSyncr4Mac-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/hyperfine.hftunes.release-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-11 /mnt/asec/com.annabelkarmel.android-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-12 /mnt/asec/org.mots.haxsync-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-13 /mnt/asec/com.makariolewis.gifinatorplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-14 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-15 /mnt/asec/nz.intelx.send.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-16 /mnt/asec/com.tbig.playerpro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-17 /mnt/asec/com.mdjsoftware.download.paid-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-18 /mnt/asec/com.ttxapps.dropsync.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-19 /mnt/asec/net.hubalek.android.apps.reborn.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/vold/179:17 /mnt/fuse/sdcard1 ext4 rw,dirsync,nosuid,nodev,noexec,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
JellyBAM is a forbidden rom here
Sent from my GT-I9505 using Tapatalk 4 Beta
Look, this is really weird....
Code:
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/vold/179:17 /mnt/fuse/sdcard1 ext4 rw,dirsync,nosuid,nodev,noexec,noatime,barrier=1,data=ordered 0 0
and...
Why is he mounting sdcard1 as ext4 within fuse? That's just odd.
Here is mine from RootBox (which I just installed)...truncated...
Code:
/dev/block/vold/179:17 on /storage/sdcard1 type vfat (rw,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702)
These above permissions are pretty standard amongst AOSP roms. I've tested my script with many and had to remoutn sdcard to get it to work correctly with permissions below, like Samsung use...
And this is mine after I remount my sdcard (so my script works)
Code:
/dev/block/vold/179:17 on /storage/sdcard1 type vfat (rw,relatime,uid=1023,gid=1023,fmask=0002,dmask=0002)
Actually with the latter, I also have the media_rw added to platforms.xml
I just don't understand what he is doing mounting the sdcard1 like that, using fuse
I'm goign to have to recommend you change your ROM really, cause it's weird.
---------- Post added at 11:12 AM ---------- Previous post was at 11:11 AM ----------
Theshawty said:
JellyBAM is a forbidden rom here
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you, Yes I have already said that
rootSU said:
Thank you, Yes I have already said that
Click to expand...
Click to collapse
Have you also told him that iGio is no real dev and just straight up kangs everything? He probably doesn't have a single clue how to fix this issue his users have.
Sent from my GT-I9505 using Tapatalk 4 Beta
Theshawty said:
Have you also told him that iGio is no real dev and just straight up kangs everything? He probably doesn't have a single clue how to fix this issue his users have.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I haven't. Because I don't know that to be true. That said I have told him that I don't know why the "dev" is mounting like that and recommended changing roms, so hopefully we're good.
thanks everyone for your help
Had no idea about the controversy around jellybam
maybe time to change roms.
pacman or paranoid think ill try next
axelnormand said:
thanks everyone for your help
Had no idea about the controversy around jellybam
maybe time to change roms.
pacman or paranoid think ill try next
Click to expand...
Click to collapse
Both good ROMs. There's rootbox too if you like that whole combined AOKP/CM/PA thing.
JellyBam discussions aren't allowed on XDA {as two members already pointed out before me}
Closed.
Related
Hello,
I have a problem with my tablet. It's Coby Kyros 9740.
I cannot write anything to /mnt/sdcard nor /mnt/extsd.
I suspect this is a permission problem but I am not sure how to permanently fix it.
ls -l /mnt
drwxr-xr-x root system 2009-12-31 19:40 asec
d---rwxr-x system media_rw 1969-12-31 19:00 extsd
drwxr-xr-x root system 2009-12-31 19:40 obb
drwxrwxrwx root root 1969-12-31 19:00 private
d---rwxr-x system sdcard_rw 1969-12-31 19:00 sdcard
drwx------ root root 2009-12-31 19:40 secure
d--------- system system 2009-12-31 19:40 usbhost1
Click to expand...
Click to collapse
usually, I see extsd or sdcard with rwxrwxr-x permission I think.
Here's what mount function gives me.
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,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 ro,relatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal
_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journa
l_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandi /mnt/private vfat ro,relatime,fmask=0000,dmask=0000,allow_utime
=0022,codepage=cp437,iocharset=ascii,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=
ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/sdcard vfat ro,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/secure/asec vfat ro,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
Is there a way to fix this permanently?
Thank you!
the5threvolution said:
Hello,
I have a problem with my tablet. It's Coby Kyros 9740.
I cannot write anything to /mnt/sdcard nor /mnt/extsd.
I suspect this is a permission problem but I am not sure how to permanently fix it.
usually, I see extsd or sdcard with rwxrwxr-x permission I think.
Here's what mount function gives me.
Code:
/dev/block/vold/93:80 /mnt/sdcard vfat [COLOR="Red"]ro[/COLOR],dirsync,nosuid,nodev,noexec,relatime,u
Is there a way to fix this permanently?
Thank you!
Click to expand...
Click to collapse
The card is mounted read-only. This may be due to errors in the file system. Run a chkdsk or reformat the card, and it may solve the problem.
kuisma said:
The card is mounted read-only. This may be due to errors in the file system. Run a chkdsk or reformat the card, and it may solve the problem.
Click to expand...
Click to collapse
Hello,
Thank you very much for your help.
I've done chkdsk from windows and it didn't help.
I'm afraid to format it because it's the internal drive of the tablet and I don't know what's going to happpen.
But another thing is that extsd which is the external microsd card is also not accessible as seen from the permissions list.
But, from the recovery mode, it is mounted as read/write and I can read/write if I'm in recovery mode.
Is there a script that runs when android starts which could cause this?
Thank you very much for your help and time.
the5threvolution said:
But another thing is that extsd which is the external microsd card is also not accessible as seen from the permissions list.
Click to expand...
Click to collapse
The permissions are just fine. I.e. r/w only by the group media_rw, this is how it's supposed to be. You must be either root or a user in this group to write to the sdcard, that is, have the WRITE_EXTERNAL_STORAGE privilege if you are an app.
You can try running fsck on the device in i shell, but first you'll have to force vold to unmount it (killing vold?) and find out its real device id under /dev/block/something first. You may find this in the output of the "dmesg" command. Still, I'm not sure it'll help. It may be mounted r/o by some other reason unknown to me.
# fsck -y /dev/block/something
Was messin around with an old phone and saw that it had an ad card I forgot about that had the file. .android_secure. 12/31/69. On it. I remember it some sort of spy+ but just curious wtf it was?
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 tried to downgrade to 148 to get the cm install to work. Lost access to internal storage. I was using twrp 2.8.7.0 or 2.8.0, flashed the rooted stock ROM from another post here and lost access. I've tried the su command "restorecon -v -R /data/media" and now I can see the internal storage from the settings menu but not change the location from there.
Here is my terminal command "mount" result
[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
[email protected]:/ $
What do I do now? I want to install the cm preview
Thanks for your time
CM12 and all other ROMs require you update your phone to Lollipop, B3xx.
xordos said:
CM12 and all other ROMs require you update your phone to Lollipop, B3xx.
Click to expand...
Click to collapse
And I'm ready to do that but I'm stuck in 4.3 with no access to the internal storage when I try to flash a new ROM. I'm thinking about going back to the recovery and get the ota update again and trying the cm install from there. Opinions?
Update* I got back to stock 309 with no ability to ota upgrade or install cm via twrp. Twrp still reports "unable to mount internal SD" but I have been able to browse, read, and write to it through the preloaded file explorer, after the "returncon -v -R data/media/" command through terminal in twrp 2.8.7.0.
once you are in 309, follow the cm install thread, and no need to worry about internal storage, at least for now.
copy rom and gapp to sdcard, which is called external storage, and flash it in twrp.
Getting stuck still at install in twrp. Cannot post a link to a screenshot so I'm gonna try to type it out. "this package supports bootloaders ... This device has boot loader unknown." And "e: error executing binary inside of zip..." I've tried all three of the custom ROM zips, cm, carbon, and PAC ROM with the same results.
What now?
notshure said:
Getting stuck still at install in twrp. Cannot post a link to a screenshot so I'm gonna try to type it out. "this package supports bootloaders ... This device has boot loader unknown." And "e: error executing binary inside of zip..." I've tried all three of the custom ROM zips, cm, carbon, and PAC ROM with the same results.
What now?
Click to expand...
Click to collapse
Unmount in lollipop and format it. Or re run b309.
Also that unknown bootloader error, one reason is you didn't flash the twrp recovery from that CM preview thread 1st post. You have to flash that recovery image even you already have working twrp.
xordos said:
Also that unknown bootloader error, one reason is you didn't flash the twrp recovery from that CM preview thread 1st post. You have to flash that recovery image even you already have working twrp.
Click to expand...
Click to collapse
then there was cyanogen and much rejoicing. Thanks :good: