I am a newbie into this rooting and upgrading stuffs on my android phone. Iv rooted, installed custom ROMs etc etc and tinkered with my phone a lot of times. I am also a curious learner. could anyone please tell me what exactly mounting storage, mounting data or mounting cache mean. Iv mounted and unmounted them alot of times going by the guidelines provided for the specific installations. Would be nice if i actually know why i am doing it Also Kindly let me on what actions can be performed or not performed when.they are mounted/ unmounted thank you.
#wannabeDeveloper
if you want to install a custom rom, sometimes a procedure for mounting tell you, it's like you open a permission to install that rom to your device
Sorry for my bad english
Achesh97 said:
I am a newbie into this rooting and upgrading stuffs on my android phone. Iv rooted, installed custom ROMs etc etc and tinkered with my phone a lot of times. I am also a curious learner. could anyone please tell me what exactly mounting storage, mounting data or mounting cache mean. Iv mounted and unmounted them alot of times going by the guidelines provided for the specific installations. Would be nice if i actually know why i am doing it Also Kindly let me on what actions can be performed or not performed when.they are mounted/ unmounted thank you.
#wannabeDeveloper
Click to expand...
Click to collapse
Mounting is the point where you can edit the files in the folder that you mount, it similar to that of mounting drives.
Similarly there are mounting such as when you use root explorers you can mount them as read/write or read only.
A Linux user can explain you in the best way, coz they usually mount their partitions as drives to work on them.
Hit thanks rather than typing it now Free
zipperX said:
if you want to install a custom rom, sometimes a procedure for mounting tell you, it's like you open a permission to install that rom to your device
Sorry for my bad english
Click to expand...
Click to collapse
your English is fine
so everytime you have to perform an update or flashing anything, you have to make sure that all the three are mounted? rigjt?
parkourkarthik said:
Mounting is the point where you can edit the files in the folder that you mount, it similar to that of mounting drives.
Similarly there are mounting such as when you use root explorers you can mount them as read/write or read only.
A Linux user can explain you in the best way, coz they usually mount their partitions as drives to work on them.
Hit thanks rather than typing it
Click to expand...
Click to collapse
Thank You there so whenever i have to flash a zip file or particularly an update, i have to mount everything? and what should be their states before rebooting? like mounted or unmounted?
Achesh97 said:
Thank You there so whenever i have to flash a zip file or particularly an update, i have to mount everything? and what should be their states before rebooting? like mounted or unmounted?
Click to expand...
Click to collapse
No need of mounting everytime you flash.
Mostly the zip files itself contains scripts to mount your partition, they do the job theirself.
In rare cases the developer of the flashable zip file would recommend you to mount the partitions required, in those cases only you need to mount through CWM
Hit thanks rather than typing it now Free
Related
Caution, ROM flashing newbie.
Hey,
I'm currently considering to flash a ROM on my S5830 (running Cyanogen 7.2 Stable currently) and one of the steps is to mount /data, which I thought could be done in mounts&storage in CWM recovery. My question is what the purpose of this is. Maybe because ROM related data is stored there? Thanks!
P.S. Yes, I have searched the answer for this and no, I couldn't find it.
I'm asking this, so I'll know what its use is, so I'll hopefully can solve related problems elsewhen.
The /data partition contains much of the data pertaining to user settings, contacts, applications, etc. If you were to perform a factory reset, this is the partition in your phone's internal storage that gets wiped clean.
Hmm, okay, but why is /data completely empty when I open it with ES File Explorer (hidden files shown)? And why is this unmounted by default if it's this important? Thanks in advance!
Sent from my GT-S5830 using xda app-developers app
That's because your file manager needs root permission to list the contents. In Terminal Emulator, run "su root" followed by "ls /data", and you'll see lots of stuff in there.
Sent from my SPH-D710
YellowApple said:
That's because your file manager needs root permission to list the contents. In Terminal Emulator, run "su root" followed by "ls /data", and you'll see lots of stuff in there.
Sent from my SPH-D710
Click to expand...
Click to collapse
Many thanks for your quick and clear help, appreciate it.
Only one more thing: why is it unmounted by default, and if it's unmounted, why can I still view it? I think I misunderstand what mounted is.
Currently playing with my Ace S5830 running Cyanogen 7.2 Stable
Remcotjuuh said:
Many thanks for your quick and clear help, appreciate it.
Only one more thing: why is it unmounted by default, and if it's unmounted, why can I still view it? I think I misunderstand what mounted is.
Currently playing with my Ace S5830 running Cyanogen 7.2 Stable
Click to expand...
Click to collapse
Good question. Do you have a link to the directions you're trying to follow for reference? The flashing directions are likely referring to mounting the /data folder/partition outside of the normal Android OS (i.e. via ClockworkMod or from a computer). By default /data should be mounted and accessible from Android (assuming you're using root privileges with your file manager or the "ls" command), else you won't have access to most of your contacts, settings, etc.
YellowApple said:
Good question. Do you have a link to the directions you're trying to follow for reference? The flashing directions are likely referring to mounting the /data folder/partition outside of the normal Android OS (i.e. via ClockworkMod or from a computer). By default /data should be mounted and accessible from Android (assuming you're using root privileges with your file manager or the "ls" command), else you won't have access to most of your contacts, settings, etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1808856
Here's it. The installation procedure can be found under Installation procedure, and mount data really is emphasized. And yes, I can mount /data in CWM recovery under mounts and storage, which gives me the impression it's unmounted now. Actually, the only thing which I CAN unmount is /cache. The others, /data, /system, /sdcard and/ sd-ext, all have the option to be mounted.
And after enabling root access in ES file explorer I indeed could view /data
Yup. Since Droid Ace v2 has files that go in /data (you can tell by the presence of a "data" folder in the root of the ROM's zip if you open it up with a file manager), it needs /data to be explicitly mounted prior to install, since it has to put stuff in there. Most ROMs I've used (like CyanogenMod) only use the /system partition (unless you install gapps).
Not sure why the update script doesn't do the mounting, but since I'm no developer (yet), there might be a very legitimate reason for that.
Sent from my SPH-D710
YellowApple said:
Yup. Since Droid Ace v2 has files that go in /data (you can tell by the presence of a "data" folder in the root of the ROM's zip if you open it up with a file manager), it needs /data to be explicitly mounted prior to install, since it has to put stuff in there. Most ROMs I've used (like CyanogenMod) only use the /system partition (unless you install gapps).
Not sure why the update script doesn't do the mounting, but since I'm no developer (yet), there might be a very legitimate reason for that.
Sent from my SPH-D710
Click to expand...
Click to collapse
That makes sence. One more thing then. As my previous ROM was Cyanogen, I also installed gapps, but I can't remember I mounted /data at that time, and installation simply succeeded. Any thoughts? Maybe because I installed gapps after flashing Cyanogen.
Sorry for the late response. It's possible that the Google Apps update package *does* mount /data in its scripts; I have yet to look into it. Or perhaps it does some intermediate thing where they plop some temp installer somewhere and have Android run said installer. I'll have to find that out
Sent from my SPH-D710
I think I got it. I thought that when flashing the ROM one of the lines said mounting /data, so that could have been part of the scripts.
Sent from my GT-S5830 using xda app-developers app
Hi Guys,
After installing the Jellybean version of Resurrection Remix using a clean install like I'd done a million times before, I came across the problem where now the internal "/sdcard" won't mount. I've read a lot of different threads on the web about this but no one seems to have a fix, except for a similar thread from Android Stack Exchange (I can't post it yet).
However, that doesn't work (when I use the ADB shell, I can detect the device, reboot it, remount the /system but not remount the /sdcard). I thought it might possibly be because I tried to fix it a few days ago by formatting the "phone" drive when it popped up on my after connecting it, and the page I referred to talks about the internal SD card being FAT formatted (not NTFS which WIn7 does automatically!).
I've also used Odin to reflash a stock ROM thinking that would fix it, done the whole "format", "factory reset", wiped partitions, caches and delvik caches etc etc to no avail. Now, even when I use recovery to try to mount the /sdcard I get an error, and if I try to format the /sdcard from the recovery menu that doesn't work either.
Problem started with Clockwork Mod 6.6 and so I've downgraded to 5.5 and ICS stock ROM. Still no good.
It's affecting a lot of apps (for example, I can't restore by backup password file to awallet, and it has all my banking details on there!) and I really need to fix it ASAP.
Any ideas?
I'm absolutely desperate and have spent days trying to figure this one out, but I am beat. I need some serious help here and you guys are the ones I think who could help. Anyone??
Cheers,
CJ.
:crying:
Hello!
Is there actually a way to mode Apps to SD Card without ROOT the phone? I'm new on Android system.
Thank's for the support!
Simon
Link2SD does not require root, and has a GUI, too.
Edit: ^That's not true!
Hello!
Thank you for the answer. On the description of the app it's written:
"Link2SD is an application that makes it easy for Android 1.6+ users with root privileges on their phone to move applications to the SD card."
Doesn't it mean I need a ROOTed phone? I know, could test it before to ask, but haven't the phone with me.
Thank's
Simon
Um, actually, yes. I'm not sure what I was thinking yesterday. All those *2sd methods are scripts, which are intended to execute upon startup, and tell the system to mount another partition. So, yes, you definitely need root.
post-mortem said:
Um, actually, yes. I'm not sure what I was thinking yesterday. All those *2sd methods are scripts, which are intended to execute upon startup, and tell the system to mount another partition. So, yes, you definitely need root.
Click to expand...
Click to collapse
Sorry for interrupting but did you mean that all those *2sd function will work after rooting? Because they don't work on my phone now without root.
The *2sd scripts are intended to run during the startup process, like in Windows you can set some programs to run automatically every time you start the computer. in this case, these scripts are only a couple lines, and they typically tell the system to mount a certain partition on the SD card as a folder. For example, if you move everything in /data/data to a partition on the SD card (i.e., /sd-ext/data), then mount the /sd-ext partition as /data/data, then every time the device tries to read or write to /data/data, it will actually be accessing /sd-ext/data. You need root authority to mount and unmount partitions.
post-mortem said:
The *2sd scripts are intended to run during the startup process, like in Windows you can set some programs to run automatically every time you start the computer. in this case, these scripts are only a couple lines, and they typically tell the system to mount a certain partition on the SD card as a folder. For example, if you move everything in /data/data to a partition on the SD card (i.e., /sd-ext/data), then mount the /sd-ext partition as /data/data, then every time the device tries to read or write to /data/data, it will actually be accessing /sd-ext/data. You need root authority to mount and unmount partitions.
Click to expand...
Click to collapse
Thanks, I'll try to do this way...
Can you tell me the exact folder which I have to redact, please.
Hii
I need clear answer and solution...
I. Is it dose all *2sd need root or no.. cause as above people said it's not working ??
II. If it's possible without root please share the app name or the steps to do that simply please...
Sent from my GT-S7562 using xda app-developers app
about kyle open rom
hi all,
This is my first post.
I am using galaxy s duos s7562(india) from last 7 months. i tried to install kyle open rom updated v2.0 to my mobile but it shows network issues. installed perfectly but only network issues i faced. In installation process cheatman said that first install XXALJ4 as base ROM, but i am not able to find that rom for my country. Please solve my issue. Thanks in advance
First of all, by sdcard I'm talking about Internal Memory, not external.
Dudes, I know, I've googled a lot about this, but it's for flashing a ROM, but that's not my case, please reply, advices or anything will be appreciated.
Ok, I got a phone from a friend and she wants it rooted, fine, got it, installed CWM, copy the root package in memory root and everything's fine!
The only problem is when I'm trying to flash the package, it can't mount the sdcard and I can't locate the package to flash. I would do it by sideload but there's no option to it.
Tried by deleting the SDcard content but no solution.
Please need help, advices, anything.
If there's no solution, I'll buy a 2GB sdcard.
By the way, the phone boots normally, can enter fastboot, adb, CWM, no problem. I can see the files in the sdcard in Android.
It's a Huawei Ascend Y210, with GB 2.3.
I have the exact same issue with my Moto G GPE
manudo said:
First of all, by sdcard I'm talking about Internal Memory, not external.
Dudes, I know, I've googled a lot about this, but it's for flashing a ROM, but that's not my case, please reply, advices or anything will be appreciated.
Ok, I got a phone from a friend and she wants it rooted, fine, got it, installed CWM, copy the root package in memory root and everything's fine!
The only problem is when I'm trying to flash the package, it can't mount the sdcard and I can't locate the package to flash. I would do it by sideload but there's no option to it.
Tried by deleting the SDcard content but no solution.
Please need help, advices, anything.
If there's no solution, I'll buy a 2GB sdcard.
By the way, the phone boots normally, can enter fastboot, adb, CWM, no problem. I can see the files in the sdcard in Android.
It's a Huawei Ascend Y210, with GB 2.3.
Click to expand...
Click to collapse
_________________________________________________
I'm basically bricked right now, really need an answer to this.
TexanProtagonist said:
_________________________________________________
I'm basically bricked right now, really need an answer to this.
Click to expand...
Click to collapse
Well, I gave up but there's something you can do, remake Android system partitions.
I don't know how but if you do that with adb shell parted then you'll have the mmcblk0 file that you need to mount the sdcard in CWM.
manudo said:
Well, I gave up but there's something you can do, remake Android system partitions.
I don't know how but if you do that with adb shell parted then you'll have the mmcblk0 file that you need to mount the sdcard in CWM.
Click to expand...
Click to collapse
I didn't know that, I'll look into it.
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Michael B.N. said:
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Click to expand...
Click to collapse
The problem occurs when you use a ROM which encrypts the software or the ROM your flashing has an encrypted kernal. The only way out is to flash a ROM which doesn't encrypt. It is a known problem with TWRP and we have to wait for the TWRP team to update TWRP to handle quota allocation.
It seems the problem is solved for me. I flashed the TWRP version from this link: https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
First I tried from Odin but it didn't work. Then I installed the TWRP app from Google Play and flashed the other file, rebooted to recovery, and it seems to work. I can mount my internal storage, make a backup etc. So this is the solution for me.
I had also similar problem of internal storage 0mb and i was not be able to mount my data
so when i flash color recovery by nobody
It's gone because it's allready patch by him
I think it's issue of encrypt data so just flash this recovery from nobody post
https://forum.xda-developers.com/galaxy-s7/themes/recovery-twrps-colored-t3859323
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
i think you must try with different file mngr, that one have no ability or permission to read system files
noniboyba said:
i think you must try with different file mngr, that one have no ability or permission to read system files
Click to expand...
Click to collapse
I'll re flash later and try a different file manager. Otherwise I'll install treble or re flash stock and start over
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
same problem, have you found solution ? please help me
TWRP sometimes can't mount the storage, the storage is encrypted, but don't worry. You can still flash your files and rewrite system partion. But in order to show the Storage, you have to use a different version of TWRP. Why am I saying this is mentioned following:
I installed the latest version of twrp, It didn't ask for any password patter to decrypt my storage. So , different XDA posts made me understand that , formatting everything, factory reset will decrypt my storage. And trust me, I have done it several time, several times my brother but it didn't decrypt my storage. I couldn't backup my ROM and without backing up my ROM, I didn't take the risk of flashing new ROM. I waited. This twrp couldn't even mount my system partion. So I seeked knowledge from different person. It took a lot of effort.
Then I learned that, I should change this version of TWRP. I changed to an older version and it didn't decrypt my internal storage after formatting, but it mounted my system partion. Since, it couldn't decrypt my internal storage, I couldn't take backup of my rom and save it to internal storage. so I inserted a pendrive in my phone, and saved the backup of my rom there.
Permanent Solution
Flashing DM Verity Force Encryption Disabler will decrypt your storage instantly. But in my case, it aroused another problem, None of the security measures of my phone worked afterwards. FOD, pin, password, pattern none of them worked. I don't know the reason but I don't suggest it with my little knowledge. but almost every rom flasher use them, so I thing I have to study about them to know how they work.
second and best option: start trying older version of TWRP, the good one will be the one to ask the password the recovery in the beginning. It will decrypt your internal storage.
I was brief here, if anyone doesn't understand these things, let me know, I will explain them step by step because I know the pain of being NEWB.