Related
Ok, I've been trying to get an answer for days now on a problem I'm having. On my sgs2, my /system is mounted as rw at boot everytime. I noticed it with cm7 first but flashed a fairly stock"ish" ROM and had the same problem. I've formatted /system and reflashed different nightlies and no luck. Every folder is rw and I have absolutely no clue how to fix it. I can't find another instance of this problem by searching Google, but one other cm7 user reported the same in the cm7 thread. Please somebody give me some direction to either fix it or work around it. I'm usually good at finding my own answers but I'm out of ideas. Thank you for ANY help!! Here are the results of mount in terminal:
rootfs on / type rootfs (rw)
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)
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 /mnt/usb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
nil on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/dev/block/mmcblk1p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodelalloc,data=ordered)
/dev/block/vold/179:11 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:11 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,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/vold/179:17 on /mnt/emmc type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-0 on /mnt/asec/com.shootbubble.bubbledexlue-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)
/dev/block/dm-1 on /mnt/asec/com.androirc-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)
Click to expand...
Click to collapse
Ok, I finally figured out a work around. I'm using autostart to run a shell script at boot until I can find something better. What should be mounted r/o at boot other than /system? Anything?
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 a new tablet from Arnova (little brother of Archos)
Spec of the tablet
1.4 ghz msm 8255 processor
512 ram
ICS operating system
What is the case, i managed to root the tablet, and dump the system partition, but romdump is not able to dump the boot and recovery, so i asked myself why
These are some results
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
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,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,d
ata=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,
data=ordered 0 0
/dev/block/mmcblk0p17 /content ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/vold/179:20 /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:20 /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/vold/179:97 /mnt/external_sd 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
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 194M 48K 194M 4096
/mnt/asec 194M 0K 194M 4096
/mnt/obb 194M 0K 194M 4096
/system 295M 223M 71M 4096
/data 393M 73M 320M 4096
/persist 4M 1M 3M 1024
/cache 196M 4M 192M 4096
/content 17M 13M 3M 4096
/mnt/sdcard 2G 1M 2G 4096
/mnt/secure/asec 2G 1M 2G 4096
/mnt/external_sd 3G 2G 1G 32768
[email protected]:/ # ls /dev/block/mmcblk*
ls /dev/block/mmcblk*
/dev/block/mmcblk0
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p1
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p2
/dev/block/mmcblk0p20
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7
/dev/block/mmcblk0p8
/dev/block/mmcblk0p9
/dev/block/mmcblk1
/dev/block/mmcblk1p1
[email protected]:/ # cat proc/mtd
cat proc/mtd
dev: size erasesize name
I am asking for some help.
How can i dump the boot and recovery ?
It is posibile considering the fact that there is no mtd ?
I am not an expert in this, so if i got something wrong show me what i dit.
Thx for any help.
Bump
Hmmm....
Code:
cat /proc/mtd
should give you the infos you need (I can't see which MTD is the recovery). Else you may want to provide me the system image?
There is no MTD on the 7c g3 only on the 7c g2 is a mtd, on the 7c g3 it is emcc which is used also on the htc phones and samsung phones.
This is the 7C G2
mount
rootfs on / type rootfs (rw)
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)
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)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock1 on /system type yaffs2 (rw,relatime)
/dev/block/mtdblock4 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock5 on /persist type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock7 on /content type yaffs2 (rw,nosuid,nodev,relatime
And this one is the 7C G3
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
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,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,d
ata=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,
data=ordered 0 0
/dev/block/mmcblk0p17 /content ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/vold/179:20 /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:20 /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/vold/179:97 /mnt/external_sd 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
I forgot to say that the 7C G3 has also a 4gb Internal space which is showd in the first post (how is partitioned)
This is the boot image that i have just dumped using the command :
[email protected]:/ # dd if=/dev/block/mmcblk0p8 of=/sdcard/bootmmc8.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/bootmmc8.img bs=4096
2560+0 records in
2560+0 records out
10485760 bytes transferred in 0.461 secs (22745683 bytes/sec)
this was the block where i found this image
http://depositfiles.com/files/qd34j4fkl
Now i am not sure if i can flash this image without breaking the tablet, and i can not find the recovery.
basicaly those mmc blocks are similar with the mtd blocks
I see. I have such device, too. Though I never did anything around hacking it, I'll see if I can find some usefull infos and write back then.
i just tried the boot.img and it works
now i just need to find the recovery partition, it must be one from this 22 mmc blocks
i will upload the system.tar dump, maybe you can make a system.img (i don`t know how) for backup to stock rom
Done, found also the recovery it was in the block16, i can see a link, boot in block8 and recovery in block16 ,system in block12
i will try to learn now about creating a cwm
http://www.mediafire.com/?rn9uppve8569ffn
system image
had problems finding my boot and recovery blocks on my device and ran into this thread and someone mentioned that there's no mtd but emmc so i tried cat proc/emmc and boom! that got me what i needed
Hi, I am trying to swap mount points to increase internal memory on my device - HTC Legend.
I know that there is script for this purpose.
http://forum.xda-developers.com/showthread.php?t=902395 .
As I can guess here we just use /sd-ext partition to swap it with /data. But in my case I have no /sd-ext partition at all, only /sdcard.
Of course I have no device /dev/block/mmcblk0p2.
About installed firmware - Android 2.3.7 ExtremeLegendFuse_2 based on CM7.
Output of mount command.
Code:
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)
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)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,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)
#
And df -h
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 145.7M 32.0K 145.7M 0% /dev
tmpfs 145.7M 0 145.7M 0% /mnt/asec
tmpfs 145.7M 0 145.7M 0% /mnt/obb
/dev/block/mtdblock3 240.0M 160.7M 79.3M 67% /system
/dev/block/mtdblock5 185.1M 18.9M 166.3M 10% /data
/dev/block/mtdblock4 40.0M 6.6M 33.4M 16% /cache
/dev/block/vold/179:1
967.6M 194.8M 772.8M 20% /mnt/sdcard
/dev/block/vold/179:1
967.6M 194.8M 772.8M 20% /mnt/secure/asec
#
Content of /system/etc/vold.fstab
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/usb_mass_storage/lun0 /devices/platform/msm_sdcc.2/mmc_host/mmc0
I have some basic knowledge, but I need help in this case.
Please help to swap storage to increase internal storage.
Thanks everyone in advance.
The problem has been solved.
My fault was that I have partitioned my sd card incorrectly.
You can do this easily from recovery. Go to Advanced - > Partition SD card Than you can select desired amount of space and choose Swap 0M.
After that you are ready to use this script.
Just reboot your device, it will take some time to boot, because your data is been moved from internal storage to the external.
Hi, can someone help me ROOT my OT 991 alcatel?
I have instaled superoneclick and then i press "Root" and i get stuck on "Shell rooting device... -Step #7 waiting for device" What im doing wrong?
Here is "log" file.
/data/local/tmp/busybox mount > /data/local/tmp/output 2>&1
export TEMPRANDOM=32604
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
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)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock12 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock13 on /custpack type yaffs2 (rw,relatime)
/dev/block/mtdblock16 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock15 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock14 on /data/wd type yaffs2 (rw,relatime)
tmpfs on /data/local/sqlite_stmt_journals type tmpfs (rw,relatime,size=4096k)
/dev/block/mtdblock8 on /data/nvram/md/s type yaffs2 (ro,relatime)
/dev/block/vold/179:1 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:1 on /mnt/secure/asec 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
END:32604
zoranjoza said:
Hi, can someone help me ROOT my OT 991 alcatel?
I have instaled superoneclick and then i press "Root" and i get stuck on "Shell rooting device... -Step #7 waiting for device" What im doing wrong?
Here is "log" file.
/data/local/tmp/busybox mount > /data/local/tmp/output 2>&1
export TEMPRANDOM=32604
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
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)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock12 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock13 on /custpack type yaffs2 (rw,relatime)
/dev/block/mtdblock16 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock15 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock14 on /data/wd type yaffs2 (rw,relatime)
tmpfs on /data/local/sqlite_stmt_journals type tmpfs (rw,relatime,size=4096k)
/dev/block/mtdblock8 on /data/nvram/md/s type yaffs2 (ro,relatime)
/dev/block/vold/179:1 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:1 on /mnt/secure/asec 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
END:32604
Click to expand...
Click to collapse
how about kingroot or 360 security ?