Database Info

[Q] how to tell android to detect my sd card storage as external storage

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

[Q]Prestigio PMP5080C PRO - Rooting

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?

Testing for A.I

Thread now changed to testing for a.i
http://sourceforge.net/projects/team...r.zip/download
test on any rom, buildprop and init.d tweaks ONLY!

Ok, now that we are talking about time management, you are wasting mine. If this is not something that you can provide OP, then don't respond.
Thread Cleaned. Let's try this again.

Here's what I sent you back in October. I'll validate my current ICS (AOKPm6r5) mounts when I get home in an hour or two and give you that in another post.
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/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/void/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/void/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=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
The part the was problematic was that the sdcard mount wasn't the last... 179:1 is the sdcard, but there's a 179:2, per this:
[email protected]:/etc/init.d $ ls /dev/block/vold/*
ls /dev/block/vold/*
/dev/block/vold/179:0
/dev/block/vold/179:1
/dev/block/vold/179:2
Click to expand...
Click to collapse
Anyways, I'll check both of those again in another hour or two. If I remember.

Re: Need your mount ARGGGGHHHH
What exactly is this storage swap that you speak of.
Sent from my Nexus 4 using xda app-developers app

During boot:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,nosuid,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/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,noatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,noatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
Click to expand...
Click to collapse
After boot is completed:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,nosuid,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/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,noatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,noatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard 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 0 0
/dev/block/vold/179:1 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
Apparently wiping my sdcard yesterday fixed the extra partition issue though.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls /dev/block/vold/*
/dev/block/vold/179:0
/dev/block/vold/179:1
Click to expand...
Click to collapse
But that doesn't mean other people (like my wife) might not still have issues with an extra partition at the end.

Theraze said:
During boot:After boot is completed:Apparently wiping my sdcard yesterday fixed the extra partition issue though.But that doesn't mean other people (like my wife) might not still have issues with an extra partition at the end.
Click to expand...
Click to collapse
Thanks!!! what is the rom your using?

anoymonos said:
What exactly is this storage swap that you speak of.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
when your on ICS or JB your apps will automatically go to internal storage and it will fill internal up real quick
this script will make your phone think the sdcard is your internal storage and your internal storage your sdcard. problem solved
however because JB is moving onto multiuser devices i have to redo the script which is what im working

dsexton702 said:
Thanks!!! what is the rom your using?
Click to expand...
Click to collapse
That's AOKP milestone 6 revision 5.

wanna test the new tweaks from a.i for me? just select buildprop and init.d tweaks for this test
URL will be back up in 5 min
more than welcome to describe any details in this thread

dsexton702 said:
wanna test the new tweaks from a.i for me? just select buildprop and init.d tweaks for this test
http://sourceforge.net/projects/teamacid/files/dsexton702/A.I/Adrenaline-Injector.zip/download
more than welcome to describe any details in this thread
Click to expand...
Click to collapse
I see a multi core tweak in etc. Is this cross platform yet or still for the 4g only?

hechoen said:
I see a multi core tweak in etc. Is this cross platform yet or still for the 4g only?
Click to expand...
Click to collapse
its not only for the 4g, the multi core will be rebuilt in the next day or so to work for all multi core devices
as for the test package download the new link i post because its the real test package lol

Ok this link is the zip i need you to test http://sourceforge.net/projects/teamacid/files/dsexton702/A.I/Adrenaline-Injector.zip/download
remember just init.d and buildprop for now

Just flashed over CM 10.1. It boots and seems to be running fine. No problems with aroma either. Not the best ROM to run a full test on as wifi is borked, it doesn't deep sleep and my sim card is in my other phone . lol I'm most likely gonna flash the internal2sd just to see what it does. If that's a bad idea it's on me. Just to curious not too. When you get the multicore done let me know I'd be happy to flash it on my Skyrocket for you.

hechoen said:
Just flashed over CM 10.1. It boots and seems to be running fine. No problems with aroma either. Not the best ROM to run a full test on as wifi is borked, it doesn't deep sleep and my sim card is in my other phone . lol I'm most likely gonna flash the internal2sd just to see what it does. If that's a bad idea it's on me. Just to curious not too. When you get the multicore done let me know I'd be happy to flash it on my Skyrocket for you.
Click to expand...
Click to collapse
lol you can try the internal2external but because of the multi user options now the it will just output that its not a real file or directory
it will be fixed soon though and you will be the first i tell about the multi core, speaking of that, could you send me all the .txt files in /system/etc for me on your skyrocket

dsexton702 said:
lol you can try the internal2external but because of the multi user options now the it will just output that its not a real file or directory
it will be fixed soon though and you will be the first i tell about the multi core, speaking of that, could you send me all the .txt files in /system/etc for me on your skyrocket
Click to expand...
Click to collapse
Sub folders as well or just the two in system/etc ?

hechoen said:
Sub folders as well or just the two in system/etc ?
Click to expand...
Click to collapse
whatever .sh or .txt files in your etc folder i wanna look at please no folders just scripts in the etc folder

dsexton702 said:
whatever .sh or .txt files in your etc folder i wanna look at please no folders just scripts in the etc folder
Click to expand...
Click to collapse
PM sent.

Direction for this thread has changed refer to OP

[Q] Wiped /cache now unable to access /sdcard

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.

Substratum not applying themes

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