Hi I have to following problem and can't find the answer with google.
I have routed my AC100.
Code:
sudo adb shell
$
su
#
so I believe the AC100 is rooted
next
Code:
#mount
/dev/block/mmcblk3p1 /system ext2 ro,relatime 0 0
therefore I did
Code:
mount -o remount,rw -t ext2 /dev/block/mmcblk3p1 /system
mount
/dev/block/mmcblk3p1 /system ext2 rw,relatime 0 0
so I think the disk has been successfully re-mounted in re-write mode.
however whenever I do something like
Code:
sudo ./adb pish com.google.android.maps.xml /system/etc/permissions
I get
Permission denied
I would be grateful if someone could point me in the right directions.
Many thanks
Frank
Hi Guys,
I have an Blu Dash 3.5 D170, but i do not have a system android yet... i've got a little problem:
I'm trying to install a backup system.img I got here, but always fails in writing step because the lack of space in /system
when i use adb shell ls -a /system the result is:
Code:
D:\Android\sdk\platform-tools>adb shell
~ # ls -a /system
ls -a /system
. .. lost+found
~ #
other words, there is nothing inside /system...
When i use "busybox df", results is:
Code:
~ # busybox df
busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 80612 48 80564 0% /dev
/dev/block/mtdblock1 225280 148096 77184 66% /system
/dev/block/mtdblock4 179200 1216 177984 1% /data
/dev/block/mmcblk0p1 3850240 118624 3731616 3% /sdcard
/dev/block/mtdblock2 61440 1192 60248 2% /cache
~ #
I can not understand why occupies 66% of the space is has NOTHING within the directory
I tried using the command "fastboot erase system", and the command says that cleared the system, but it does not clear these 66%
what should I do to fix this?
I have a rooted HTC and need to create a custom file in /system/xbin. I execute a mount command (for read-write permission on /system), create the file, remount /system in readonly and after that my file magically disappear. Here are the commands I wrote in a su shell via adb.
Code:
[email protected]:/system/xbin # mount | grep system
/dev/block/mmcblk0p35 /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/system/xbin # mount -o rw,remount /dev/block/mmcblk0p35 /system
[email protected]:/system/xbin # cd /system/xbin
[email protected]:/system/xbin # echo test > myfile
[email protected]:/system/xbin # ls
daemonsu
dexdump
dexus
myfile <- 'myfile' is created
nc
su
[email protected]:/system/xbin # cat myfile
test
[email protected]:/system/xbin # mount -o ro,remount /dev/block/mmcblk0p35 /system
[email protected]:/system/xbin # ls
daemonsu
dexdump
dexus
nc
su
PUFF after remounted /system in readonly my file is disappeared. Any idea about this?
NOTE: If I try to re-execute the commands, my HTC restarts itself ... EDIT 2: As you could see in the 'ls' command output, in /system/xbin exist 'su' installed with a root tool. How could this root tool install 'su' permanently?
My first gen moto g is stuck in a bootloop, everything i have done so far has not worked.I have tried to flash using fastboot and mfastboot with different stock images in all I get failed to erase partition, remote failure.
The internal storage says it has 0 mb of space. I have Twrp installed and using cat /proc/partitions finds no partitions
~ # ←[6ncat /proc/partitions cat /proc/partitions major minor #blocks name
I have managed to push a Stock rom but can´t flash it with mount data error,mount sd card error, mount system error and mount cache error..
I have tried to use Adb remount but it fails
remount failed: Success
I also tried the following commands
adb shell
su
mount -o rw,remount -t yaffs2 /system
mount -o rw,remount -t yaffs2 /data
mount -o rw,remount -t yaffs2 /cache
And they give the following error
adb shell ~ # ←[6nsu su /sbin/sh: su: not found ~ # ←[6nmount -o rw,remount -t yaffs2 /system mount -o rw,remount -t yaffs2 /system mount: can't find /system in /proc/mounts ~ # ←[6nmount -o rw,remount -t yaffs2 /data mount -o rw,remount -t yaffs2 /data mount: can't find /data in /proc/mounts
In recovery mode, i went to advanced, then Terminal Command, then entered the command df and it listed
Filesystem 1K BLocks Used Available %Use
tmpfs/dev 443852 48 443804 0
tmpfs/tmp 443852 24 443828 0
I have also uploaded a recovery.log
Any help would be greatly appreciated
I have found this xda post with the partition table and sizes of the moto g. http://forum.xda-developers.com/showpost.php?p=48855450&postcount=35
I also found this xda post where they partition the emmc http://forum.xda-developers.com/showthread.php?t=2596521 , if someone could help me identify what should I put in adb.
I think the solution is to reformat using adb but i dont know how.
I have the exact same problem and would love to know if you have fixed it please.
I have rooted NSTV device with Android11, when I connect my external HDD (ext4 formatted) to it, the device notify me the HHD not supported.
I can mount the HDD successfully:
Code:
mount -w -t ext4 UUID=89087942-e2b5-4f4a-99d7-9818559c6844 /mnt/media_rw
The root privileged file manager apps can read & write to HDD (Root-Explorer or Solid-Explorer)
But I can't open my movies through the VLC, MxPlayer... apps (logcat is: Access denied), also I tried to 'chown & chmod' but I'm not success.
Can you help me to solve my problem please?!
I think the mount cmd should look like shown next if dynamic mount of an external HDD is wanted
Code:
su -c "mount -o rw,remount -t ext4 UUID=89087942-e2b5-4f4a-99d7-9818559c6844 /media"
@xXx yYy
Thank you for reply...
The path /media does not exist ! So I create it and try again mounting but not success
Code:
mdarcy:/ # mount -o rw,remount -t ext4 UUID=89087942-e2b5-4f4a-99d7-9818559c6844 /media
mount: '/media' not in /proc/mounts
#up
I'm trying to investigate... So I connect fat32 formatted USB-Flash to device, the mount result is:
Code:
/dev/block/vold/public:8,1 on /mnt/media_rw/7132-BE26 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/mnt/media_rw/7132-BE26 on /mnt/runtime/default/7132-BE26 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)
/mnt/media_rw/7132-BE26 on /mnt/runtime/read/7132-BE26 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/7132-BE26 on /mnt/runtime/write/7132-BE26 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/7132-BE26 on /mnt/runtime/full/7132-BE26 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=7)
/dev/fuse on /mnt/user/0/7132-BE26 type fuse (rw,lazytime,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /mnt/installer/0/7132-BE26 type fuse (rw,lazytime,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /mnt/androidwritable/0/7132-BE26 type fuse (rw,lazytime,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /storage/7132-BE26 type fuse (rw,lazytime,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other)
/mnt/media_rw/7132-BE26 on /mnt/pass_through/0/7132-BE26 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=7)
So it seems the /dev/block/vold/ is start point:
#ls -hal /dev/block/vold/ result is:
Code:
brw------- 1 root root 8, 0 2021-11-18 01:58 disk:8,0
brw------- 1 root root 8, 1 2021-11-18 01:58 public:8,1
So I connect my external HDD (ext4 formatted) and #ls -hal /dev/block/vold/ result is:
Code:
disk:8,16
Then I try to mount it:
Code:
mdarcy:/ # busybox mount -w -t ext4 /dev/block/vold/disk:8,16 /mnt/media_rw/ext_hdd
mount: mounting /dev/block/vold/disk:8,16 on /mnt/media_rw/ext_hdd failed: Invalid argument
HOW I CAN MOUNT /dev/block/vold/disk:8,16 ?