Rooting ideas

[mudknot2005]

You can use it, but it won't allow you to R/W only R/O

 

[xaueious]

There has to be a partition in the device that is r/w. Your device needs to be able to write files without the need for elevated superuser permissions. Then upon obtaining superuser permissions (aka root), you can then remount a partition that was previously mounted as r/o/

The internal SD would not work because it is FAT/FAT32, and you cannot run executable binaries from FAT/FAT32 I believe.

You should be doing this through terminal emulator or adb shell.

 

[dave52355]

I get " property service neutered " Is that a good thing? The only directory I could find to push psneuter to was /etc. There I was able to chmod 777 giving full RW access to the file. Than I adb shell and got a $ prompt. I then typed /adb/psneuter and got the " property service neutered " I rebooted the tablet ran TI but no root.

 

[dave52355]

Typed it all again after killing droid explorer. Now in my command prompt when I type " adb shell " instead of getting the $ I get #. That should be root. Now to remount the system RW? Why can't it be a simple command like remount whole system RW? My brain hurts

 

[xaueious]

Sounds like we have root.

 

[dave52355]

But not persistant. Somehow I need to mount the system as RW. I've been reading and it appears I need to run something like this: mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 However, under /dev/block/ mmcblk0p25 is not there. Only goes to mmcblk0p4. But we are indeed closer. Thanks

 

[mudknot2005]

adb remount (not permanent)

or

mount -o rw,remount /system

both should work

also https://market.android.com/details?id=com.beansoft.mount_system

 

[dave52355]

Hey mud, no go. Make any sense out of this?

cat /proc/mounts
rootfs / rootfs rw 0 0
ubi0:rootfs / ubifs 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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /proc/bus/usb usbfs rw,relatime,devmode=666 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=utf8,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=utf8,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:9 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=
utf8,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.rovio.angrybirdsrio-1 vfat ro,dirsync,nosuid,nodev
,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=utf8,sh
ortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.angrybirdsseasons-1 vfat ro,dirsync,nosuid,n
odev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=utf
8,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=utf8,short
name=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.quoord.tapatalkat.activity-1 vfat ro,dirsync,nosui
d,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
utf8,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.scannerradio-1 vfat ro,dirsync,nosuid,nodev,noexec
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=utf8,shortname
=mixed,utf8,errors=remount-ro 0 0
#

 

[mudknot2005]

It is an error. Hmmm interesting. Not exactly sure, I bet some one over at xda would probably know.

edit: I ran the rw command on my phone here is what I got

C:\Users\David\Desktop\android-sdk-windows\tools>adb remount
remount succeeded

C:\Users\David\Desktop\android-sdk-windows\tools>adb shell
# mount -o rw,remount/system
mount -o rw,remount/system
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p25 on /system type ext3 (rw,relatime,errors=continue,barrier=
0,data=ordered)
/dev/block/mmcblk0p26 on /data type ext3 (rw,nosuid,nodev,relatime,errors=contin
ue,barrier=0,data=ordered)
/dev/block/mmcblk0p27 on /cache type ext3 (rw,nosuid,nodev,relatime,errors=conti
nue,barrier=0,data=ordered)
/dev/block/mmcblk0p28 on /devlog type ext3 (rw,nosuid,nodev,relatime,errors=cont
inue,barrier=0,data=ordered)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /app-cache type tmpfs (rw,relatime,size=8192k,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/data/d on /data/d type debugfs (rw,relatime)
htcfs on /data/htcfs type fuse.htcfs (rw,nosuid,nodev,relatime,user_id=0,group_i
d=0,allow_other)
/dev/block/vold/179:65 on /mnt/sdcard type 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)
/dev/block/vold/179:65 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.rovio.angrybirdsrio-1 type vfat (ro,dirsync,nos
uid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso88
59-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/com.rovio.angrybirdsseasons-1 type vfat (ro,dirsync
,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=i
so8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/com.rovio.angrybirds-1 type vfat (ro,dirsync,nosuid
,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro)
#

 

[mudknot2005]

Have you tried anything that requires the system to be mounted as r/w?

taking a second look at it, it seems that the system isn't showing up..

I wonder if mmcblk0p4 is the system partition..

try:
mount -o rw,remount -t auto /dev/block/mmcblk0p4 /

 

[dave52355]

I think it has to do with superuser or busybox. I reran mount -o rw,remount/system and got something similar to yours.

 

[dave52355]

I now have a rooted 7024 I'll write up the steps shortly!! Yippie!

 

[Darktan]

Kewl. Can't wait.