Hey everyone,
Ok, so first off I am using JAC's OC/UV Voodoo kernel with Frankin Twiz update 3. That said, voodoo is currently disabled. My question is I went into Terminal Emulator and mounted my device and it shot back this huge bit of code. Same thing happened with voodoo installed with the exception of it saying "mmcblk0p4" and "ext4" (obviously). Is this suppose to happen? Or does this mean there is something wrong? If there is something wrong, what do I need to do to fix it? OR is everything OK and I'm just a complete noob? Here is the code:
$mount
rootfs / rootfs rw 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Thanks for your time and help!
When you run "mount" without any other options, it just lists the current partitions and mount points. Everything is normal.
Saiboogu said:
When you run "mount" without any other options, it just lists the current partitions and mount points. Everything is normal.
Click to expand...
Click to collapse
Thank you Saiboogu for clearing this up for me. I suspected everything was fine, but just wanted to be sure.
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.
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
CWM 5.0.2.7 Touch Recovery
This is a port of CWM touch recovery modded by Team UtterChaos.
Installation is same as the 5.0.2.6 recovery.
Changelog:
3)Changed icons and layout.
2)Changed icon layout to vertical alignment as recovery text merges with icons.
1)Initial release
Credit:
All credit goes to koush and members of Team UtterChaos
Note:Im not sure if this will work for ITE devices but you can try.
good to see any new tool for our veiwpad thx hero, and it's funny to see ics icon on recovery, hehe.
My Vpad7 with ITE hardware was running 5.0.2.6 so I used Terminal to flash this, it rebooted but I can't get into the Advanced submenu and at least one other submenu - Go Back doesn't work for me either. The nice icon/graphic just sitting there in the center screen, so I've reverted back to older one as I need to use its feature to format/setup ext3 and/or ext4.
Anyone else having luck & success with this, it could be just me - tried it twice.
Would this work for viewpad 7e?
Sent from my LG-P500 using xda premium
hellodzulz said:
Would this work for viewpad 7e?
Click to expand...
Click to collapse
No, this is all for the Viewpad 7, not the Viewpad 7e. The 7e is basically a new product and we just need to wait until Viewsonic sells enough of these 170$ tablets to warrant someone elses interest in creating a mod for it.
Not sure how a bounty would work, but I would put in 30$. Once Clockwork Recovery works, then it should be easy for someone else to provide a stock ROM for it that lets Marketplace work better.
elister said:
No, this is all for the Viewpad 7, not the Viewpad 7e. The 7e is basically a new product and we just need to wait until Viewsonic sells enough of these 170$ tablets to warrant someone elses interest in creating a mod for it.
Not sure how a bounty would work, but I would put in 30$. Once Clockwork Recovery works, then it should be easy for someone else to provide a stock ROM for it that lets Marketplace work better.
Click to expand...
Click to collapse
I could help you with that.
just pm me the following stuff:
Boot.img
Partition table
mb-14 said:
I could help you with that.
just pm me the following stuff:
Boot.img
Partition table
Click to expand...
Click to collapse
Im pretty sure I would need ADB Shell in order to do that, but ADB Shell cannot find the 7e as a device.
elister said:
Im pretty sure I would need ADB Shell in order to do that, but ADB Shell cannot find the 7e as a device.
Click to expand...
Click to collapse
ADB shell is not necessary.Just download a terminal emulator from the market.
mb-14 said:
ADB shell is not necessary.Just download a terminal emulator from the market.
Click to expand...
Click to collapse
What commands would I need to execute to create the image and display the partitions?
elister said:
What commands would I need to execute to create the image and display the partitions?
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
mb-14 said:
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
Using the terminal emulator version, I got the romdump installed, but the folder it created contained no files.
-----------------------------------------------------------
#/system/bin/romdump
Android ROM dumper v0.72b
(c)2010 Sebastian404
Device : ViewPad7e 2.3.1 GINGERBREAD 2011.11.01
[2] Segmentation fault /system/bin/romdump
[1] Segmentation fault /data/local/install
#
-----------------------------------------------------------
Yes I remember to toggle wifi on, then off. I'll try a few more times when im not drunk.
elister said:
Using the terminal emulator version, I got the romdump installed, but the folder it created contained no files.
-----------------------------------------------------------
#/system/bin/romdump
Android ROM dumper v0.72b
(c)2010 Sebastian404
Device : ViewPad7e 2.3.1 GINGERBREAD 2011.11.01
[2] Segmentation fault /system/bin/romdump
[1] Segmentation fault /data/local/install
#
-----------------------------------------------------------
Yes I remember to toggle wifi on, then off. I'll try a few more times when im not drunk.
Click to expand...
Click to collapse
Try the alternative method given in the link.
mb-14 said:
Try the alternative method given in the link.
Click to expand...
Click to collapse
You mean ADB Shell? Nah, that never worked. Could never get the USB drivers from the SDK to work. Shows up in Unknown Devices as ViewPad 7e, unless theres some device drivers im not aware of. Searching for them brings up countless Vewsonic 7e Monitor drivers, not tablet ones.
No problem getting my android phone rooted with ICS, but this tablet is just too new I guess.
elister said:
You mean ADB Shell? Nah, that never worked. Could never get the USB drivers from the SDK to work. Shows up in Unknown Devices as ViewPad 7e, unless theres some device drivers im not aware of. Searching for them brings up countless Vewsonic 7e Monitor drivers, not tablet ones.
No problem getting my android phone rooted with ICS, but this tablet is just too new I guess.
Click to expand...
Click to collapse
Adb shell is not necessary.The commands will also work on your terminal emulator on the phone.Skip the first instruction "adb shell"
I was unable to get the romdump to work, so I tried looking at the mounts (seen below). I am not sure if it helps, but if there is something I can do, please let me know. I'd love to get a nandroid backup of the the 7e
Thanks.
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
/dev/block/mmcblk0p2 /system ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,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,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,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
mmarsman said:
I was unable to get the romdump to work, so I tried looking at the mounts (seen below). I am not sure if it helps, but if there is something I can do, please let me know. I'd love to get a nandroid backup of the the 7e
Thanks.
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
/dev/block/mmcblk0p2 /system ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,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,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,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
Click to expand...
Click to collapse
I need the partition names and their sizes.This is not going to help.What command did you run?
Try this from the terminal emulator:
su
cat /proc/mtd
and post me the output
mb-14 said:
I need the partition names and their sizes.This is not going to help.What command did you run?
Try this from the terminal emulator:
su
cat /proc/mtd
and post me the output
Click to expand...
Click to collapse
It doesn't show anything, just the headers:
dev: size erasesize name
is there another option instead of mtd that it could be?
---------- Post added at 03:28 PM ---------- Previous post was at 02:32 PM ----------
mb-14 said:
I need the partition names and their sizes.This is not going to help.What command did you run?
Try this from the terminal emulator:
su
cat /proc/mtd
and post me the output
Click to expand...
Click to collapse
I also tried running: cat /proc/partitions
It returned the following:
major minor #blocks name
179 0 3772416 mmcblk0
179 1 2605798 mmcblk0p1
179 2 209901 mmcblk0p2
179 3 525698 mmcblk0p3
179 4 115351 mmcblk0p4
179 8 16186368 mmcblk1
179 9 16185344 mmcblk1p1
Still not right, but I will keep trying
Finally people interested in the ViewPad 7e, I will try to get the partitions info and the img files tonight wish me luck
Viewpad 7e Info
This is going to be a little long, but I have been searching for days and I am not sure where things are going wrong. When I run cat /proc/mtd it will only return the headers. I found another forum posting that had a sequence of commands that my reveal some useful information. Below I am showing the commands and their results. If anyone has a suggestion of where to go from here I'm all ears.
cat proc/mtd
Code:
dev: size erasesize name
cat proc/mounts
Code:
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
/dev/block/mmcblk0p2 /system ext3 ro,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
ls /dev/block/mmcblk*
Code:
/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
mount
Code:
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
/dev/block/mmcblk0p2 /system ext3 ro,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
df
Code:
Filesystem Size Used Free Blksize
/dev 163M 32K 163M 4096
/mnt/asec 163M 0K 163M 4096
/mnt/obb 163M 0K 163M 4096
/system 198M 171M 26M 1024
/data 503M 130M 373M 4096
/cache 109M 103M 5M 1024
/mnt/ViewPad_7e 2G 100M 2G 4096
/mnt/secure/asec 2G 100M 2G 4096
The 7e seems to have emmc partitions instead of mtd.
Try this:
cat /proc/emmc
How did I end up here?
1. Installed CM 12.1 Beta 4 from our friendly user forumber via TWRP
2. As GPS and camera didn't work, tried to get back to stock
3. Tried to flash 5 different roms (2 custom & 3 officials) but "error executing updater binary" just wouldn't let me
4. I don't know how but I finally managed to flash Yoigo stock one (Actualizacion_Blade_Vec_4G_Yoigo_V1.0.0B04.zip)
5. TWRP & Root went off. The entire internal memory is now on read-only memory.
Can't download a single file from the phone but somehow I can install apps via Play Store (pretty much the only thing I can do).
The only progress I made so far is to get root back again via Windows Kingroot.
Adb is working properly but mount command tells me operation not permitted
What should I do now? Replace Kingroot with Supersu? Change ro.secure parameter modding boot.img?
And most important: giving the circumstances, how could I do what you suggest me?
I should point out that I know nothing about programming and having got so far surprised me.
Thank you everybody in advance.
P.D. I don't know if the code I'll post will tell you something, but this is what cat /proc/mounts tells me:
Code:
[email protected]:/ $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=419008k,nr_inodes=104752,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=419008k,nr_inodes=104752,mod
e=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=419008k,nr_inodes=104752,mode=75
5,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=419008k,nr_inodes=104752,mode=755
,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,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/userdata /data ext4 rw,seclabel,nosuid,no
dev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,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=low
er,errors=remount-ro 0 0