Hey everyone, I'm new to the forum, and am in need of great help
A few days ago, I bought a new tablet, the Prestigio PMP5080C Pro. It's actually a very good tablet for the price you're paying. I've only had 2 problems:
1)They don't have any settings to enable proxy (Can't connect to internet at campus).
2)Many of the 3D games show only white textures (Apparently Chainfire 3D fixes this issue).
Now to fix both of them, I need root access. And that's the biggest problem I've been having.
The device uses Android ICS (4.0.3). At first I had many problems trying to get the device recognised as anything other than a USB Mass Storage Device, but eventually got it working. After that, I tried using SuperOneClick 2.3.3, it got past step 2, but then froze on step 7. No matter what I tried, it froze there everytime. After that, I tried using UnlockRoot, and it just showed the steps (completed in like 15 seconds) and didn't give me any completed messages. After that failed, I tried using RootThat, and got this log:
Code:
adbd cannot run as root in production builds
List of devices attached
ASBSM805HCZ01234 device
adbd cannot run as root in production builds
remount failed: Operation not permitted
failed to copy 'C:\RootThat\su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
failed to copy 'C:\RootThat\Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
::Success!!::
After that failed, I read up about using Wendal's RK29xxImageTools_v2.1 to unpack and repack the firmware with superuser access. It managed to unpack the firmware file (Can see the system.img, etc) but when it tries to add the root, it gives the following error towards the end:
Code:
cramfsck: superblock magic not found
Enable root permission
The system cannot find the path specified.
The system cannot find the path specified.
chmod: cannot access `system/*': No such file or directory
chmod: cannot access `system/bin/su': No such file or directory
chmod: cannot access `system/app/Superuser.apk': No such file or directory
Unpack -- All Done
Pls input: 1-Unpack 2-Pack 3-Exit
Okay, so my first question. How do I know what filesystem /system is using? I typed in "mount" in adb shell, and I get the following:
Code:
C:\Users\Xenonification>adb shell
[email protected]:/ $ mount
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/mtdblock8 /system ext3 ro,noatime,nodiratime,barrier=0,data=ordered 0
0
/dev/block/mtdblock6 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=contin
ue,barrier=0,data=ordered 0 0
/dev/block/mtdblock5 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=conti
nue,barrier=0,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/31:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch****t=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relati
me,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocha
rset=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.polarbit.rthunderlite-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,ioch****t=iso8859-1,sh
ortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/org.vudroid-1 vfat ro,dirsync,nosuid,nodev,relatime,ui
d=1000,fmask=0222,dmask=0222,codepage=cp437,ioch****t=iso8859-1,shortname=mixed,
utf8,errors=remount-ro 0 0
[email protected]:/ $ mount
C:\Users\Xenonification>
"/dev/block/mtdblock8 /system ext3 ro,noatime,nodiratime,barrier=0,data=ordered 0 0" Does that mean it's using the ext3? Because elsewhere I've heard that it uses cramfs, so i'm not sure
And secondly, does anyone know any other methods to root this device? I was thinking about mounting the system.img, adding the files needed for root, and then repacking the firmware. But I have no idea how to do this.
Thanks guys!
Rooted roms there: http://forum.xda-developers.com/showthread.php?t=1796067
yes it's using ext3 mount output is "device mountpoint filesystem options", you can mount it in any standard (or user-friendly if you want) linux distribution by "mount image mountpoint -o loop" as root
Btw I've tried chainfire and device didn't boot, it's very probable I did something wrong but do chainfire support opengl1.1-only devices?
Related
Hello xda hackers,first off I'd like to say this is my first post here but your forums (and forum members work) has helped a lot.
I've recently been experimenting with xfs for my "sd card" on my nexus s.
(just to see the performance difference between xfs,fat32 and ext4 on my nexus s)
I've successfully compiled mkfs.xfs for arm and I’ve successfully formatted my sdcard storage with xfs. I’ve even gotten it to mount fine in android (btw, i use a custom kernel based on netarchy's git repo). i can verify it's mounted(i've even gotten it to mount at boot because vold.fstab just wasn't working). and i can even access files on it using some file browser apps.
the problem I'm having is that all of my apps think i don't have "external storage".
I've even done setprop EXTERNAL_STORAGE_STATE mounted
camera,music,etc.... all the apps say i don't have usb/external storage.
so i just wanted your help in finding out how exactly android tells if a mount-point is external storage or not.
FYI: my nexus s doesn't really have an sd card it's an internal storage (i think nand).
here is the output of some commands in case you need it:
adb shell mount:
Code:
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /efs yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw,noatime,barrier=0,nobh,data=ordered 0 0
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=0,nobh,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p3 /mnt/sdcard xfs rw,noatime,attr2,noquota 0 0
none /sys/kernel/debug debugfs rw,noatime 0 0
adb echo $EXTERNAL STORAGE :
# echo $EXTERNAL_STORAGE
/mnt/sdcard
feel free to ask me for more info. and yes I’ve googled it all over and plenty of people have tried helping me on irc. all the topics that come up is about people having their sd cards not detected.
mkfs.xfs in case anyone wants it.
oh, and I’ve attached mkfs.xfs for those of you who want to run it from your phones but don't want to compile it from the source(it took me a few hours to get around some of the compilation/cross-compilation issues).
it's 1.8Mb because it's statically linked.
nvm, i got is solved by hacking around vold. thanks for all the help...Not.
i cant mount sdcard storage
hi i have samsung galaxy 3 i5800
end i instaled on my phone kyrilos v9.4 rom
end now i want to mount sdard storage bat wen i go to the recovery
i choice mount sdcard storage,mount sdcard ext end reboot nothing hapen
i go back to recovery end i have agen option mount sdcard that mean my card is not mounted
pleace i need som healp this is my first android phone
sory for my english
i have a phone here from china, the name is KATA iDROID. i was trying to root it using different types of methods, such as doomlord, superoneclick, EPRJ_EasyRoot, zopo zp100 4.0ROOT, z4root, androot, universalandroot, etc.... but i get one respond from all of these. it says failed.
i tried mounting the system manually, but it gives me permission denied.
these are the steps that i tried:
adb shell
mount -o remount,rw --t yaffs2 /dev/block/mtdblock11 /system
mount: Operation not permitted
adb shell
$ mount
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
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/mtdblock11 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock13 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock12 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock7 /system/secro yaffs2 ro,relatime 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
=iso8859-1,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=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-1 /mnt/asec/com.corner23.android.universalandroot-1 vfat ro,dirsyn
c,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$ ^C
the phone is MT6516, android version: 2.3.5, Dual sim from china.
can anyone help me to mount the system as r/w so i can push the files that i need. thanks in advance guys
What happens when you try to use super1click? Do you have a log for that?
The adb command you are trying will work if your phone is rooted only. I mean you should have super user permission to run the command!
Try to install all the drivers of your mobile on your pc or re-install the drivers, restart the pc and try with super one click!
Super one click will prompt you to install any missing drivers during the process. Accept all and proceed.
If you still get error try
http://unlockroot.com/download.html
I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
In adb I tried to cd into /sdcard and the directory is missing entirely
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
same thing here
Code:
[email protected]:/ $ cd /storage/emulated/legacy
/system/bin/sh: cd: /storage/emulated/legacy: No such file or directory
My mountpoinits show no sign of sdcard anywhere
Code:
127|[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,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,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/dm-0 /mnt/asec/com.trueaxis.jetcarstunts-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.tribok.android.livewallpaper.nightflare.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.robbers.clock-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
If anyone has any suggestions I would appreciate them. I would really like to be able to recover my data from the device before I wipe it.
Alias.TDP said:
I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
.
Click to expand...
Click to collapse
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)
GUGUITOMTG4 said:
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)
Click to expand...
Click to collapse
Thanks dude that worked
Alias.TDP said:
Thanks dude that worked
Click to expand...
Click to collapse
Glad it's fixed. Keep that thread in the first aid kit:cyclops:
Remember - NEVER reboot your phone when it's trying to wipe. Some of these phones take an exceptionally long time to wipe depending on your recovery.
Hey guys,
I'm having some strange trouble with my Iconia A510 that came out of the blue. It boots up normally but after about 95 sec when just everything looks nice'n ready to use, it reboots. Except for the CWM-based recovery 6.0.1.9 and a 16 GB external µSD-card the tablet is in stock condition.
So thought, no big deal and restored the full backup, created on the very day CWM-based recovery was installed some weeks ago. But it failed!
Config says:
Error while restoring /data!
I:Can't partition non-fat: datamedia
I:Can't format unknown volume: /emmc
Does this point to some defective memory cell on the internal SD? How can it be diagnosed?
Thanks!
josmarlangner said:
Hey guys,
I'm having some strange trouble with my Iconia A510 that came out of the blue. It boots up normally but after about 95 sec when just everything looks nice'n ready to use, it reboots. Except for the CWM-based recovery 6.0.1.9 and a 16 GB external µSD-card the tablet is in stock condition.
So thought, no big deal and restored the full backup, created on the very day CWM-based recovery was installed some weeks ago. But it failed!
Config says:
Error while restoring /data!
I:Can't partition non-fat: datamedia
I:Can't format unknown volume: /emmc
Does this point to some defective memory cell on the internal SD? How can it be diagnosed?
Thanks!
Click to expand...
Click to collapse
I had corruption in /data filesystem that produced similar behavior. A file system check and repair, followed by nandroid restore got me running again. The exact process for filesystem check and repair is a blurred memory, but it involved running adb commands (fsck?) on /dev/ something. Probably had to unmount the filesystem first.
SyncingFeeling said:
I had corruption in /data filesystem that produced similar behavior. A file system check and repair, followed by nandroid restore got me running again. The exact process for filesystem check and repair is a blurred memory, but it involved running adb commands (fsck?) on /dev/ something. Probably had to unmount the filesystem first.
Click to expand...
Click to collapse
Thanks. But the thing is and please correct me if I'm wrong:
To use ADB and to do what you suggest I need the Android up and running on my tablet. Otherwise the Win7 system I connect it to does not even see it. Mine is only up for like 10 sec before it reboots ... What do I do?
Thanks
josmarlangner said:
Thanks. But the thing is and please correct me if I'm wrong:
To use ADB and to do what you suggest I need the Android up and running on my tablet. Otherwise the Win7 system I connect it to does not even see it. Mine is only up for like 10 sec before it reboots ... What do I do?
Thanks
Click to expand...
Click to collapse
Boot into recovery and adb should work.
SyncingFeeling said:
Boot into recovery and adb should work.
Click to expand...
Click to collapse
No! I did just that. Windows 7 itself only sees it with an exclamation mark, i.e no drivers installed. And w/o drivers ADB does not see the tablet.
josmarlangner said:
No! I did just that. Windows 7 itself only sees it with an exclamation mark, i.e no drivers installed. And w/o drivers ADB does not see the tablet.
Click to expand...
Click to collapse
I used twrp recovery but don't know if that works differently. I suggest searching to solve the adb issue. Seems solvable.
SyncingFeeling said:
I used twrp recovery but don't know if that works differently. I suggest searching to solve the adb issue. Seems solvable.
Click to expand...
Click to collapse
Solvable? But how? I'm a newbie to Android/Linux but I'm pretty good with Windows. Windows will not work properly with any device w/o the proper drivers installed. Drivers for the A510 (that come wih the SDK package) need Android to be operational. That leaves me with a time window of 10-20 seconds before the A510 reboots. This is a f___ing bind!
OK, making progress: Different Windows 7 system (64bit this time) sees A510 when booted to CMV-based recovery.
But which one is the data partition I need to unmount before running e2fsck?
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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/platform/sdhci-tegra.3/by-name/CAC on /cache type ext4 (rw,nodev,noat
ime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
/dev #
josmarlangner said:
OK, making progress: Different Windows 7 system (64bit this time) sees A510 when booted to CMV-based recovery.
But which one is the data partition I need to unmount before running e2fsck?
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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/platform/sdhci-tegra.3/by-name/CAC on /cache type ext4 (rw,nodev,noat
ime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
/dev #
Click to expand...
Click to collapse
I'm sorry I can't give step-by-step instructions, but I encourage you to keep at it and you'll solve it.
I don't have my tablet with me to compare. But it's odd that you don't appear to have a /data filesystem. Maybe /data doesn't get mounted in recovery mode. I'd want to run mount during a successful boot to be sure to get the correct partition info, but that may be very hard to do. There must be other ways to get the info, such as the Linux /etc/fstab file, but on a quick search that Linux feature doesn't seem to translate to Android.
Some googling got me here, which shows what I would otherwise expect you to be seeing.
http://www.arturaz.net/2014/09/adventures-in-reviving-acer-a510.html
It seems to me it's a little dangerous to assume the same block name (UDA) applies to your device, but in desperation, you could try it.
More googling shows an alternative approach.
http://www.acertabletforum.com/foru...able-mount-format-data-solution-included.html
This seems to operate on the mounted filesystem, so you don't need to unmount and find the raw blocks.
SyncingFeeling said:
I don't have my tablet with me to compare. But it's odd that you don't appear to have a /data filesystem. Maybe /data doesn't get mounted in recovery mode. I'd want to run mount during a successful boot to be sure to get the correct partition info, but that may be very hard to do.
Click to expand...
Click to collapse
20 secs were more than enough time to get the mount infomation. There's indeed some panicking going on!
[email protected]:/ $ mount
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /mnt/usb_storage tmpfs rw,relatime,mode=755,gid=1000 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/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xatt
r,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatim
e,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,noauto_da_
alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime
,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,noauto_da_a
lloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/FLX /system/vendor ext4 ro,relatime,us
er_xattr,acl,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=1013,group_id=1000,allow_other 0 0
[email protected]:/ $
josmarlangner said:
20 secs were more than enough time to get the mount infomation. There's indeed some panicking going on!
[email protected]:/ $ mount
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /mnt/usb_storage tmpfs rw,relatime,mode=755,gid=1000 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/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xatt
r,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatim
e,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,noauto_da_
alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime
,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,noauto_da_a
lloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/FLX /system/vendor ext4 ro,relatime,us
er_xattr,acl,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=1013,group_id=1000,allow_other 0 0
[email protected]:/ $
Click to expand...
Click to collapse
Ok great. The.device name was different on my A700.
Now Reboot recovery, double check that it's not mounted and run e2fsck on the UDA file. It ran for several minutes when I did it. Then try your restore again.
SyncingFeeling said:
Ok great. The.device name was different on my A700.
Now Reboot recovery, double check that it's not mounted and run e2fsck on the UDA file. It ran for several minutes when I did it. Then try your restore again.
Click to expand...
Click to collapse
OK, here's what happens: I boot into recovery, unmount
/dev/block/platform/sdhci-tegra.3/by-name/CAC on /cache
(the one file that causes panic)
and nothing to be done on
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data
(which is not even mounted in recovery)
I run
~ # e2fsck -f -y /dev/block/platform/sdhci-tegra.3/by-name/CAC
e2fsck -f -y /dev/block/platform/sdhci-tegra.3/by-name/CAC
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/CAC: 16/78400 files (0.0% non-contiguo
us), 10310/313344 blocks
~ #
No errors found.
But then I run
e2fsck -f -y /dev/block/platform/sdhci-tegra.3/by-name/UDA
and there's literally hundreds of thousands of things like these:
File /data/com.google.android.googlequicksearchbox/cache/cronet-async/d8f7b05402
4f6aa9_0 (inode #532665, mod time Wed Nov 11 18:39:59 2015)
has 2 multiply-claimed block(s), shared with 1 file(s):
... (inode #1667252, mod time Mon Jun 24 20:50:42 2013)
Clone multiply-claimed blocks? yes
File /data/org.mozilla.firefox/files/mozilla/rh91vmis.default/safebrowsing-backu
p/goog-malware-shavar.sbstore (inode #532636, mod time Mon Oct 12 05:27:19 2015)
has 357 multiply-claimed block(s), shared with 1 file(s):
... (inode #1666649, mod time Tue May 14 22:26:47 2013)
... and this goes until after 6 and a half hours the battery is empty and the tablet switches off.
What do I do?
josmarlangner said:
... and this goes until after 6 and a half hours the battery is empty and the tablet switches off.
What do I do?
Click to expand...
Click to collapse
Hmmm.... Charge the battery and repeat? That's what I'd do, but please realize I am no longer speaking from experience.
SyncingFeeling said:
Hmmm.... Charge the battery and repeat?
Click to expand...
Click to collapse
2nd run is ongoing. But from the number of files being processed per battery-charge I might have to repeat this over and over again.
Isn't there another way, like formatting something to get rid of logical errors and more important to get defectice clusters (yey I know, no clusters on an SSD!) marked as such? Or delete everything in /dev/block/platform/sdhci-tegra.3/by-name/UDA?
Doesn't all this point to some erroneous SSD hardware?
josmarlangner said:
2nd run is ongoing. But from the number of files being processed per battery-charge I might have to repeat this over and over again.
Isn't there another way, like formatting something to get rid of logical errors and more important to get defectice clusters (yey I know, no clusters on an SSD!) marked as such? Or delete everything in /dev/block/platform/sdhci-tegra.3/by-name/UDA?
Doesn't all this point to some erroneous SSD hardware?
Click to expand...
Click to collapse
How did you make out? I've been thinking and googling and learned the UDA "file" is a symbolic link to the memory blocks at /dev/block/mmcblk0p10, which is what I ran fsck on directly. If you are still stuck, try that (run -- maybe the symlink slows fsck down.
There probably is another way to solve this, but I don't know it. It would seem that laying down a new filesystem on the memory blocks would solve the problem (using mkfs or its variants) but I can't guide you there. I found one web posting where someone tried that and failed.
I still wonder what happened during my repair, e.g., are there bad memory blocks waiting to surface again, or did they get marked "bad" as in your hard drive analogy.
Has anyone had any luck applying Substratum themes? I read a post 2 months ago from a user that said he was succesful but that's about it. I've tried various themes and none of them have worked. Do I have to delete Theme Editor, go back to the stock theme of EMIUI and then try substratum? I'm confused. I'm rooted, obviously.
I would think you need the substratum framework in place for it to work. In aosp roms they usually bake the framework in for it to work.
sent from my rotary phone
jr313 said:
I would think you need the substratum framework in place for it to work. In aosp roms they usually bake the framework in for it to work.
sent from my rotary phone
Click to expand...
Click to collapse
nope. it's running compatible to hwdesigns. I applied a sub theme ( see pictures attached )
on some FW it's quite tricky to mount the vendor partition rw. I mounted it manually via es file explorer, installed substratum, installed the theme and applied it. everything needs root of course
WieserZ1C said:
nope. it's running compatible to hwdesigns. I applied a sub theme ( see pictures attached )
on some FW it's quite tricky to mount the vendor partition rw. I mounted it manually via es file explorer, installed substratum, installed the theme and applied it. everything needs root of course
Click to expand...
Click to collapse
Hmmm. That didn't work for me. Looking inside SuperSU, it seems that substratum doesn't even ask for root permissions. All I have inside SuperSU is Rom Control and Viper. When I go into setting inside substratum, it says "rooted mode (certified)" but I can't apply any themes. I checked and everything in my root folder has drw permissions, including vendor. Any tips?
try delete App data, then uninstall, flash your choice of root ( as I guess SuperSU ) again, reboot, then reinstall ... it has to ask for root privilege, otherwise it won't perform. The last chance I could advise if it doesn't work after previous steps is to delete SuperSU app data too.
WieserZ1C said:
nope. it's running compatible to hwdesigns. I applied a sub theme ( see pictures attached )
on some FW it's quite tricky to mount the vendor partition rw. I mounted it manually via es file explorer, installed substratum, installed the theme and applied it. everything needs root of course
Click to expand...
Click to collapse
Please help me too. my overlay folder is also read only and I don't have es file explorer option because it doesn't work (with root) on my device after marshmallow update.
CheifX said:
Please help me too. my overlay folder is also read only and I don't have es file explorer option because it doesn't work (with root) on my device after marshmallow update.
Click to expand...
Click to collapse
Couldn't you just mount it from a terminal?
Code:
su
mount -o rw,remount /vendor
I am super noob
ante0 said:
Couldn't you just mount it from a terminal?
Code:
su
mount -o rw,remount /vendor
Click to expand...
Click to collapse
Please click on image
CheifX said:
Please click on image
Click to expand...
Click to collapse
What happens if you type
mount -o remount,rw /vendor
?
You might have have to type just "mount" to check which device /vendor is at and what fs it uses
Example: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /vendor
Yaffs2=fs, /dev/block/mtdblock3=device in this example. Type mount to find out where vendor is located and replace device and fs with the ones you find. I take it you're not using a Mate 9?
I also want to apply this
ante0 said:
What happens if you type
mount -o remount,rw /vendor
?
You might have have to type just "mount" to check which device /vendor is at and what fs it uses
Example: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /vendor
Yaffs2=fs, /dev/block/mtdblock3=device in this example. Type mount to find out where vendor is located and replace device and fs with the ones you find. I take it you're not using a Mate 9?
Click to expand...
Click to collapse
unfortunately, I can't found vendor in these commands.
[email protected]_4G:/ # mount
mount
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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 /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/expand/760fbce2-4992-4d33-879e-8458ca5696c1 ext4 rw,dirsync
,seclabel,nosuid,nodev,noatime 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user
_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id
=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_i
d=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/default/self/primary fuse rw,nosuid,nodev,noexec,noatime,
user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/sdio_emmc/by-name/system /system ext4 ro,seclabel,noatime,da
ta=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/userdata /data ext4 rw,seclabel,nosuid,nod
ev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev
,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/prodnv /productinfo ext4 rw,seclabel,nosui
d,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,gro
up_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/self/primary fuse rw,nosuid,nodev,noexec,noatime,user_id=1023
,group_id=1023,default_permissions,allow_other 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
/dev/block/loop1 /su ext4 rw,seclabel,noatime,data=ordered 0 0
[email protected]_4G:/ #
CheifX said:
unfortunately, I can't found vendor in these commands.
[email protected]_4G:/ # mount
mount
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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 /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/expand/760fbce2-4992-4d33-879e-8458ca5696c1 ext4 rw,dirsync
,seclabel,nosuid,nodev,noatime 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user
_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id
=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_i
d=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/default/self/primary fuse rw,nosuid,nodev,noexec,noatime,
user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/sdio_emmc/by-name/system /system ext4 ro,seclabel,noatime,da
ta=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/userdata /data ext4 rw,seclabel,nosuid,nod
ev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev
,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/prodnv /productinfo ext4 rw,seclabel,nosui
d,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,gro
up_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/self/primary fuse rw,nosuid,nodev,noexec,noatime,user_id=1023
,group_id=1023,default_permissions,allow_other 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
/dev/block/loop1 /su ext4 rw,seclabel,noatime,data=ordered 0 0
[email protected]_4G:/ #
Click to expand...
Click to collapse
Ah. Try mounting /system as rw.
'mount -o rw,remount /system' or remount,rw, whichever works. I thought /vendor was the problem, but it's probably /system/vendor/overlay.
All Black
ante0 said:
Ah. Try mounting /system as rw.
'mount -o rw,remount /system' or remount,rw, whichever works. I thought /vendor was the problem, but it's probably /system/vendor/overlay.
Click to expand...
Click to collapse
Hahaha changed theme prity easily by changing vendor,overlay to RW with X-Plore (a file manager). Anyway thanks to everyone for replying