[Q] E: Unable to mount /system - General Questions and Answers

Hi. I renamed a folder and the apk file inside it in system/app.
now my phone is not booting (goes to android is upgrading... then restarts). I tried to delete that apk from recovery, but both recoveries(I have CWM+Philztouch and Teamwin) say E:unable to mount /system when I try to mount system. So I can do nothing to access /system.
I need to either access /system without recoveries(maybe in fastboot) or fix the /system mount problem in recoveries.
any idea is very helping.
I have Xperia Z Lte with android 5.0.2
Thanks for reading question.

mpowend said:
Hi. I renamed a folder and the apk file inside it in system/app.
now my phone is not booting (goes to android is upgrading... then restarts). I tried to delete that apk from recovery, but both recoveries(I have CWM+Philztouch and Teamwin) say E:unable to mount /system when I try to mount system. So I can do nothing to access /system.
I need to either access /system without recoveries(maybe in fastboot) or fix the /system mount problem in recoveries.
any idea is very helping.
I have Xperia Z Lte with android 5.0.2
Thanks for reading question.
Click to expand...
Click to collapse
Have you tried a factory reset from recovery? That may clear the app data and allow you to boot.

Evolution_Tech said:
Have you tried a factory reset from recovery? That may clear the app data and allow you to boot.
Click to expand...
Click to collapse
Any type of reset will surely fix it. because the change in the name of app will be reverted to original rom's app name.
But renaming or deleting a file in system shouldn't need factory reset. there's surely a better way.
and main question is why /system not mounts?!

For anyone having this problem, I solved it.
The solution was the version of dual recovery I was using was for locked bootloaders. so I flashed the UB version and the /system now mounts fine.

mpowend said:
For anyone having this problem, I solved it.
The solution was the version of dual recovery I was using was for locked bootloaders. so I flashed the UB version and the /system now mounts fine.
Click to expand...
Click to collapse
I have the same issue. I am using TWRP 3.0.0 . I'm unable to flash any ROM. it showing Unable to mount/system
My Mobile model : Xperia M [SS]

Related

[Q] Enrcyption Support for ClockWorkMod Recovery

Hello,
i have just installed the official stock ICS 4.0.3 Rom to my Nexus S and everything was really fine... until i tried to root it. As someone who tries to take security seriously, i immediately encrypted the device using the tools provided by ics (works ok).
but unfortunatly it's now not possible anymore to mount /sdcard while in recovery, which makes rooting and installing updates impossible (or is there any other way? eg. fastboot?).
therefore my question: will clockworkmod recovery support ics encrypted devices in the (near) future? i know its gonna be a p.i.a. to type a password with only the volume buttons, but hey
i like the encryption and would like to keep it, but not beeing able to use recovery like before is a big drawback...
greetings
Georg
Same for me.
Hope to see encryption support in clockworkmod soon.
I bought Rom manager premium even if I never flash from rm just to support the developers... hope they will be able to get it sorted out
Op -- I'm interested in this for when my phone (EVO 3D) finally gets ICS. Will you post an update to this thread if you hear anything?
BTW, with TWRP getting touchscreen support, it can't be too much longer before CWM gets touchscreen since I think the guys in TWRP were going to start contributing to CWM, from what I've heard anyway. So that would solve the password typing problem.
Georg, thanks for asking this question as I've been wondering the same exact thing. Hopefully we'll get a good answer soon.
Alternatives for ClockworkMod Recovery
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
mrosensweig said:
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
Click to expand...
Click to collapse
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
I didn't read anything about encryption so did not upgraded to the touch recovery yet
you should lock the bootloader if someone is nagging you
jomir said:
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
Click to expand...
Click to collapse
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Thanks for the reply, DarkhShadow. The problem is that CWM can't wipe or format these partitions, since it can't mount /sdcard (which is encrypted). If I could only access the external sdcard from within CWM, I could just wipe everything and then install a new rom. But since it can't mount /sdcard, I can't access sd-ext. nvflash is not an option, since my TF101 is B90. Is there a way to either restore the stock recovery (overwrite CWM) or boot from the external SD so I can run a script such as "super wipe full" (http://forum.xda-developers.com/showthread.php?t=1245892)? Maybe there's a way to run the wipe script through adb? If I can just format the partitions (which is what the script does), then CWM would be able to mount /sdcard and, consequently, the external SD and I can flash a new rom (such as revolution HD 3.0.1).
Thanks,
rmsilva
Honestly idk then, try a factory reset on phone(ie booted up) and then maybe it will be unencrypted?
Sent from my ice cream powered Nexus S
The funny thing is that stock recovery on an encrypted phone can write to the disk, but only from a warm reboot (perhaps the kernel stays resident?).
When I say write to disk I say apply the leaked OTA update, 4.0.4 for the VZ Gnex. And correct me if I am wrong, it's writing and mounting the disk, no?
Anyhow, this is done from stock recovery which is open source. So you ask yourself, why can't Koush support mounting the disk from a warm recovery state reboot? Maybe he doesn't know this?
DarkhShadow said:
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
i did a factory reset (from the settings menu), installed recovery per adb/fastboot and installed cm9 from sdcard in recovery.
Use tmpfs to install a new ROM in crypted system
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
What about a nandroid backup or restore? How big is /cache?
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
Sorry I didn't try with a nandroid backup but I think it is too big to fit the device memory...
You can backup data inside the sd partiton (phone up and running, just to don't lose data...), boot into recovery, format sdcard partition, mount it, put the backup in the sdcard and after install the nandroid backup...
I think that it could work but I am not sure. If after formatting the sdcard you can mount it, the task is done. You can put the backup on it using adb push and flash using recovery.
If you try please give me some news.
Regards
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
thx1200 said:
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
Click to expand...
Click to collapse
First it formats the cache partition. Then mount the /sdcard so that you can access it from your pc. After you mount the /sdcard, you can put your rom zip into it. After the zip has been transferred into /sdcard, you can flash the zip as usual.
Since nexus s doesn't have sdcard slot, it mounts the internal storage as '/sdcard' to treat it like a sdcard, thus 'fake' sdcard. The 'fake' sdcard is around 13GB.

(SOLVED) [Q] [HELP] Motorola NOOB! Mount point information for XT925?

Hi there, I seem to have messed up my mounting partitions while trying to deodex Stock JB Central Europe. I basically used xultimate to pull the files and deodex then tried using adb shell to mount the system partition and copy them over. After I rebooted the phone, it would get stuck on unlocked bootloader warning or on the motorola logo. I hard reset into recovery and restored a nandroid backup and once booted into android found so many folders under the Storage folder such as "asec", "obb", rfs0" and so on. Now, when I try to wipe dalvik-cache in recovery, i get the following error: "E: unknown volume for path [/sd-ext]". Also, when i try flashing custom rom's and reboot, it gets stuck on the unlocked bootloader warning and wont load - while in recovery after flashing, i also get another error something like this: "E: cant load /cache/recovery.log" or similar. I also sometimes have issues mounting system, cache partitions, data and internal storage, all depending on which custom recovery i am using. I read on another site that downgrading to ics might solve mounting problems so I forced a downgrade to ics but that didnt work either and am still on ics.
Is there a way to restore the partitions correctly or are they stuck this way? Would mounting and remounting solve this problem? Any help would be much appreciated and would very much appreciate it if someone could upload their mount point info so i could use to try and fix it.
Many thanks in advance.
EDIT: Managed to flash Slim Bean 4.3 Official using OUDHS recovery without wiping cache and dalvik-cache at first. After reboot, it would bootloop so went to recovery and wiped cache and dalvik-cache then it worked. Still no sd-ext and some apps can't write or backup to external memory such as Go Backup & Restore Pro so what remains is to mount/unmount the partitions correctly.

Softbricked flashing recovery with TWRP Manager App

Hello. I seem to have softbricked my nexus 5 with the twrp manager app when flashing new recovery thinking I was taking a shortcut so I didn't have to boot my laptop up for 4.4.3. update. Guess I had to anyway because recovery did not get updated to 2.7.1.1! I was going to update to paranoidandroid 4.4.3rc1, elementalx.44 and also new radio but never got that far because recovery failed to mount /sdcard, and also /data, /cache I have no idea if the path to the recovery partition block (?) from the twrp app was correct but i assumed so because it was mentioned as a preferred way of installing the recovery.
The problem is that there is no sd card detected , no camera, crashes in google play services and general system wobbliness and no identifications and a different wifi mac address, no network signal but wifi is working. /data, /cache and /sdcard is not mountable in recovery.. can't get adb to work in other mode than ptp either but that's probably just my pc.
I was thinking about flashing the images from https://developers.google.com/android/nexus/images but I hope there is a chance to backup my sdcard please! Could I perhaps flash the images one by one and see if it gets better? perhaps flashing the kernel again? :silly:
------
oh well apparently forgot I had to still format /cache. ooops. thread closed?
StrongOneX said:
Hello. I seem to have softbricked my nexus 5 with the twrp manager app when flashing new recovery thinking I was taking a shortcut so I didn't have to boot my laptop up for 4.4.3. update. Guess I had to anyway because recovery did not get updated to 2.7.1.1! I was going to update to paranoidandroid 4.4.3rc1, elementalx.44 and also new radio but never got that far because recovery failed to mount /sdcard, and also /data, /cache I have no idea if the path to the recovery partition block (?) from the twrp app was correct but i assumed so because it was mentioned as a preferred way of installing the recovery.
The problem is that there is no sd card detected , no camera, crashes in google play services and general system wobbliness and no identifications and a different wifi mac address, no network signal but wifi is working. /data, /cache and /sdcard is not mountable in recovery.. can't get adb to work in other mode than ptp either but that's probably just my pc.
I was thinking about flashing the images from https://developers.google.com/android/nexus/images but I hope there is a chance to backup my sdcard please! Could I perhaps flash the images one by one and see if it gets better? perhaps flashing the kernel again? :silly:
------
oh well apparently forgot I had to still format /cache. ooops. thread closed?
Click to expand...
Click to collapse
Try adb to backup your sdcard or flashing the factory images EXCEPT userdata.img should do the trick.

No Data Directory

Title says it all. a lady brought me her moto g and on the screen all it had was no command and the android with the triangle !. so i booted it in to the bootloader and installed a custom recovery. tried to mount the sd card so i could recover her data off of it and it failed to mount so i tried mounting /data and it wouldnt mount and it says /data directory doesnt exist. /system would mount and several others would mount. so my question is, is this phone f***ed or is there a way to restore the /data directory through fastboot flashing?
Thanks for your time
Anthony
krypticos said:
Title says it all. a lady brought me her moto g and on the screen all it had was no command and the android with the triangle !. so i booted it in to the bootloader and installed a custom recovery. tried to mount the sd card so i could recover her data off of it and it failed to mount so i tried mounting /data and it wouldnt mount and it says /data directory doesnt exist. /system would mount and several others would mount. so my question is, is this phone f***ed or is there a way to restore the /data directory through fastboot flashing?
Thanks for your time
Anthony
Click to expand...
Click to collapse
Try and reflash the system partition and boot into android. Then look for /data. /data might be corrupted...

Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)

Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Cepillado said:
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Click to expand...
Click to collapse
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
sosukeaizen said:
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
Click to expand...
Click to collapse
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Cepillado said:
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Click to expand...
Click to collapse
try flashing a lower version of the same frimware you've already installed e.g if the latest is nougat 7.1.1 with the recent security update, try flashing with another nougat version that is lower to the recent one's security patch #

Categories

Resources