Related
I had a problem using the multitouch hack, and now the touchscreen is not working.
So basically i can't enter in CMW recovery (tenfar) and just flash the old touchpad.zip (i'm relating to this thread http://forum.xda-developers.com/showthread.php?t=1134057 )
All i need is to put the old files ( three touchpad.cfg that i've backup) in
/system/etc/touchpad/20
/system/etc/touchpad/21
/system/etc/touchpad/22
But /system is Read Only. And i really don't know how to mount it as RW (i always do it with root explorer).
So here's the question: How can i mount /system in RW via ADB?
This is my "mount"
Code:
c:\ADB>adb shell
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=o
rdered 0 0
/dev/block/mmcblk0p15 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=
ordered 0 0
/dev/block/mmcblk0p3 /pds ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
/dev/block/mmcblk0p13 /osh ext3 rw,relatime,errors=continue,data=ordered 0 0
tmpfs /osh/lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
varrun /osh/var/run tmpfs rw,nosuid,relatime,mode=755 0 0
varlock /osh/var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0
securityfs /sys/kernel/security securityfs rw,relatime 0 0
/dev/block/mmcblk0p17 /preinstall ext3 ro,noatime,nodiratime,data=ordered 0 0
/proc /osh/proc proc rw,relatime 0 0
$
theraizen said:
I had a problem using the multitouch hack, and now the touchscreen is not working.
So basically i can't enter in CMW recovery (tenfar) and just flash the old touchpad.zip (i'm relating to this thread http://forum.xda-developers.com/showthread.php?t=1134057 )
All i need is to put the old files ( three touchpad.cfg that i've backup) in
/system/etc/touchpad/20
/system/etc/touchpad/21
/system/etc/touchpad/22
But /system is Read Only. And i really don't know how to mount it as RW (i always do it with root explorer).
So here's the question: How can i mount /system in RW via ADB?
This is my "mount"
Code:
c:\ADB>adb shell
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=o
rdered 0 0
/dev/block/mmcblk0p15 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=
ordered 0 0
/dev/block/mmcblk0p3 /pds ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
/dev/block/mmcblk0p13 /osh ext3 rw,relatime,errors=continue,data=ordered 0 0
tmpfs /osh/lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
varrun /osh/var/run tmpfs rw,nosuid,relatime,mode=755 0 0
varlock /osh/var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0
securityfs /sys/kernel/security securityfs rw,relatime 0 0
/dev/block/mmcblk0p17 /preinstall ext3 ro,noatime,nodiratime,data=ordered 0 0
/proc /osh/proc proc rw,relatime 0 0
$
Click to expand...
Click to collapse
Hi,
$ su
# busybox mount -o rw,remount /system
Cheers!
Code:
c:\ADB>adb shell
$ su
su
busybox mount -o rw,remount /system
busybox mount -o rw,remount /system
Permission denied
$ mount: permission denied (are you root?)
And of course i'm root O_O
I've the gingerblur 4.5 BTW
theraizen said:
Code:
c:\ADB>adb shell
$ su
su
busybox mount -o rw,remount /system
busybox mount -o rw,remount /system
Permission denied
[B][COLOR="Red"]$[/COLOR][/B] mount: permission denied (are you root?)
And of course i'm root O_O
I've the gingerblur 4.5 BTW
Click to expand...
Click to collapse
Nope, looks like you're not root at all... the command prompt should have changed to #... Weird..
but how can i have the gingerblur working, if i'm not rooted O_O?
I've also run aRoot few minutes ago, and results i'm rooted O_O
It's ok even if i can enter into CMW via ADB!
Another solution i've think about is to run SystemRecovery app from the shell, so I can enter directly in recovery mode.. But yet, i dunno how to do this
theraizen said:
but how can i have the gingerblur working, if i'm not rooted O_O?
I've also run aRoot few minutes ago, and results i'm rooted O_O
It's ok even if i can enter into CMW via ADB!
Another solution i've think about is to run SystemRecovery app from the shell, so I can enter directly in recovery mode.. But yet, i dunno how to do this
Click to expand...
Click to collapse
Hi theraizen,
Am also facing same problem. Did you get any help? Even I tried hard reset my phone. But left with no luck. Its still not working.
Is there anyway for me to get touch pad working?
For god's sake, I dont have backup too..
Mine is Atrix 4g with 2.3.6/4.5.141.
Can you please help me out to fix this?
Thank you.
Jags.
I have no idea if this belongs here, so feel free to move this thread.
I have a Qualcomm MDP MSM8660, which, frankly, I am way too much of a noob to use. I, with the help of someone, finally managed to install gapps and am able to use the market. The problem is, the Market claims that there is no room to install apps, even though the phone says that there is 888MB free. So I presume that the market sees some other partition which is full. If this is the case, how can I make it see the other partition, or alternatively expand the partition. I don't even know how to view the partitions to see if the above theory is correct.
EDIT: I checked using Android System Information, and the Data partition is nearly a Gigabyte. So any suggestions on why the Market thinks that there is no room. When I used ADB to push the gapps to /system there also wasn't any room, so I had to clear some apps. But I believe that's a different partition.
Any ideas?
Thanks
To view the partitions on your device you should run mount through adb shell. Post the output here.
Here it is:
>adb shell 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/mmcblk0p12 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 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,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.estrongs.android.pop-1 vfat ro,dirsync,nosuid,node
v,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,utf8,errors=remount-ro 0 0
EDIT: Not really related, but I even though this is supposed to be rooted, and through ADB it does seem so , after remount, Superuser says it's not and in Terminal it shows "$" and when I type "su" it says uid 10006 not allowed to su". Any ideas?
Does anyone have any ideas? Also how to symlinks?
Thanks.
Hi,
I have very limited space on the system partition, so I can't install any apps larger than 2MB. I do have plenty of room on the data partition, so if I download the APK myself, I can install it. It appears that the Market uses the system partition as a download cache, until it installs the app. Therefore, I can install several apps summing up more than 2MB, however not a single app bigger than 2MB.
My question is, how to grow the system partition to use the space in the data partition.
Here is the output of adb mount:
>adb shell 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/mmcblk0p12 /system ext4 ro,relatime,barrier=1,data=ordered 0 0 /dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered ,noauto_da_alloc 0 0 /dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde red 0 0 /dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere d 0 0 /dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o rdered 0 0 /dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 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_utim e=0020,codepage=cp437,iocharse t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow _utime=0020,codepage=cp437,ioc harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 /dev/block/dm-0 /mnt/asec/com.estrongs.android.pop-1 vfat ro,dirsync,nosuid,node v,relatime,uid=1000,fmask=0222,dmask=0222,codepage =cp437,iocharset=iso8859-1,sho rtname=mixed,utf8,errors=remount-ro 0 0
There is a limit, but I never heard of one being so low. Have you checked to see if there were any junk files there (/cache/download)?
None that I see. There is 48MB of. so files, though.
yelped said:
None that I see. There is 48MB of. so files, though.
Click to expand...
Click to collapse
Are you sure you are in the right folder? Those files should not be there.
Those files are there. Should I provide you with a list of all the files. If so, what's the easiest way?
Thanks!
I would suggest making a nandroid backup, then deleting all the files in that folder (make sure you're the right one). It should not affect your system since that folder is usually safe to delete files from, but ".so" files are driver files, so it would be safer to make the backup (just in case).
Nothing on the device would work if I did that. I tried to remove it already. Do you have any other suggestions?
Thanks!
I've got an Acer A200 that is running the leaked version of ICS 4.0.3 from here:
http://forum.xda-developers.com/showthread.php?t=1479231
Utilizing saurik's mempodroid I am able to exploit the kernel (2.6.39.4+) and gain root, but I cannot remount /system. I've tried quite a few different mount commands and they all result in the same error "mount: Operation not permitted".
Here are the mount commands I've tried:
Code:
remount rw
mount -o remount,rw '' /system
mount -o remount,rw /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
mount -o remount,rw /dev/block/mmcblk0p3 /system
A regular mount command gives me this:
Code:
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
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/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/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1
,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p6 /system/vendor ext4 ro,relatime,user_xattr,acl,barrier=1,da
ta=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
An id command gives me this:
Code:
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),
1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw
_stats)
Anyone have any suggestions???
Offsets please?
phunk311 said:
I've got an Acer A200 that is running the leaked version of ICS 4.0.3 from here:
http://forum.xda-developers.com/showthread.php?t=1479231
Utilizing saurik's mempodroid I am able to exploit the kernel (2.6.39.4+) and gain root, but I cannot remount /system. I've tried quite a few different mount commands and they all result in the same error "mount: Operation not permitted".
Here are the mount commands I've tried:
Code:
remount rw
mount -o remount,rw '' /system
mount -o remount,rw /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
mount -o remount,rw /dev/block/mmcblk0p3 /system
A regular mount command gives me this:
Code:
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
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/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/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1
,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p6 /system/vendor ext4 ro,relatime,user_xattr,acl,barrier=1,da
ta=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
An id command gives me this:
Code:
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),
1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw
_stats)
Anyone have any suggestions???
Click to expand...
Click to collapse
I'm running the same tablet with the leak. What are the offsets you used to gain root with mempodroid. I might be able to help.
ladamich said:
I'm running the same tablet with the leak. What are the offsets you used to gain root with mempodroid. I might be able to help.
Click to expand...
Click to collapse
0xd9f0 0xaf47
---------- Post added at 07:23 PM ---------- Previous post was at 06:38 PM ----------
phunk311 said:
Utilizing saurik's mempodroid I am able to exploit the kernel (2.6.39.4+) and gain root, but I cannot remount /system. I've tried quite a few different mount commands and they all result in the same error "mount: Operation not permitted".
Click to expand...
Click to collapse
One thing phunk311 did not mention is that I had him run dmesg, and the output included the following:
Code:
<4>[13769.725090] Operation not permitted or illegal root
I've since been able to get a copy of the boot.img from one of these devices, and doing a simple strings on the kernel (hey: I'm lazy ;P) you see that the string "Operation not permitted or illegal root" is right next to "/system".
So, given that I was able to verify with someone else that /system/vendor (which is its own partition on this device) can be mounted rw (and yet /system cannot), it sounds like they have a check specifically for "/system" to disallow this.
So is there any way around this check? With a locked bootloader there is no way to modify boot.img and flash in stock recovery. I've seen the A500 get around this with some serial number tool and CWM checksum fix. Let me know if you need any info from my tab.
Sent from my A200 using Tapatalk
hello,
i have two sch-r930 phones. (samsung galaxy s aviators) and through countless forums's and googling i cannot for the life of me find the recovery partitions, among others. even tho i have attempted all possibilities (the ones i found atleast) to find these, i ask others for assistance.
anything needed as far as output's from any commands or binaries can be provided.
help?
Looks like this might do the trick:
https://play.google.com/store/apps/details?id=com.cls.partition
or if you prefer to know how manually, then there might be some helpful info on this thread:
http://forum.xda-developers.com/showthread.php?t=2377989
exhausted that
es0tericcha0s said:
Looks like this might do the trick:
https://play.google.com/store/apps/details?id=com.cls.partition
or if you prefer to know how manually, then there might be some helpful info on this thread:
http://forum.xda-developers.com/showthread.php?t=2377989
Click to expand...
Click to collapse
already attempted those. actually any app with partition in the title ive downloaded from the playstore and tried.
i have tried to ls -l /dev/block/platform and looked for a by-name in either location to no end. i have chekced the last_log from the cache/partition. i have used onandroid, romgen, romdump, flash_image, dump_image, etc to no end.
i need someone who can help me narrow it down by some other means.
is it possible that its wrapped up in with the kernel?
moar
heres my mount results
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/radio tmpfs rw,relatime 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/stl10 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/mmcblk0p1 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p4 /fota rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,
gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/
rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/u
id/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/dev/block/stl7 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179: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
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,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 /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#