Hey
I'm trying to change from Prime to Revolution ROMs, but during wiping, I seem to be hitting a problem. When coming to wipe /data, it says it can't remove bootanimation.zip. I'm trying to go in via adb and do this manually, but it won't seem to let me mount /data as read write.
I'm using adb shell while in recovery, and it isn't giving an error message, just constantly staying as ro. This is using clockword recovery 3.2.0.1.
Anyone know what else I can try?
Thanks for your help.
Do you want to give it a try with root explorer?
Forgot to mention, since I've tried wiping, it now just bootloops. Recovery is all I can get into.
edit:
Just to make it clearer what's happening, I'll do it step by step:
- Load recovery, and open adb shell on my PC
-Mount data in recovery, check it in adb shell and it shows it as read/write
-Go to delete a directory or file, and it say's it's read only, check mounts and it's gone back to ro
-If I unmount and remount, it will go back to being RW, but then the same as above happens.
-My problem is when I try to wipe or format in recovery, it gives an error saying it can't delete a certain file
Managed to fix it now. It appears that while using the Superwipe Full script for Revolution ROM, the file table got completely messed up. I used parted to reformat the data partition as ext2, and I can boot now.
I've managed to get that awful Rom (Destroyer) Manager off of my TF101G and have got Rogue on via PERI and now I'm trying to flash the stock ASUS ICS Rom but can't delete the Dalvik Cache because I'm unable to mount /data
Code:
- - Wiping all user data - -
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure
Cache wipe complete.
Formatting /cache...
Cache wipe complete.
Wiping dalvik-cache...
Error mounting /data!
I'm assuming that /data is stuck on read only?
Manually fixing permissions and then mounting /data also shows the same error.
HELP :crying:
Related
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
UPDATE WITH MORE INFO:
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log
I've managed to get that awful Rom (Destroyer) Manager off of my TF101G and have got Rogue on via PERI and now I'm trying to flash the stock ASUS ICS Rom but can't delete the Dalvik Cache because I'm unable to mount /data
Code:
- - Wiping all user data - -
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure
Cache wipe complete.
Formatting /cache...
Cache wipe complete.
Wiping dalvik-cache...
Error mounting /data!
I'm assuming that /data is stuck on read only?
Manually fixing permissions and then mounting /data also shows the same error.
HELP :crying:
I have the same problem. I know what lead me to it.
Its an Asus SL101
I have cyanogenmod correctly installed. In order to install a megatron rom I downloaded their app called megatron apps. Trying to download a rom from them I got validation error at end of download and I make the stupidity of change the download dir from /mnt/sdcard to /sdcard and then when I restart again it doesn´t load and CWM recovery give me the same errors (unable to mount /data or unable to mount /sdcard when cleaning cache or trying to restore a backup ).
The only thing I have been able to do its to install Rogue XM Recovery 1.5.0 instead of CWM 6.x ) but the problem to apply an update or restore a backup persists.
Any idea ?
Aaargh.
After a year and a half of heavy CWM and TWRP usage, this has suddenly happened to me too, possibly after flashing the updated TWRP blob from Goo Manager (although that's conjecture at best). My ROM (RaymanFX' CM10 v6) is fine in everyday use - no problems whatsoever, but now I want to update, and my recovery won't let me.
In the hope that something simply went wrong during recovery blob flash, I successfully deleted TWRP and flashed a different recovery (latest CWM) from ROM Manager, but the new recovery can't mount anything either - neither sd card, data, or cache. The error messages are more or less identical to TWRP's errors. My system MAY be readable, but I can't backup or restore or flash anything anyway, so I don't dare format it.
I don't have a Windows PC, so I haven't tried Easy Flasher. I could try it on my work computer if there's no way around it and if neither OSX or Ubuntu can help.
Any suggestions?
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.
Pardon me but i cannot find the right place where to post my problem.
After failing horribly to instal zombie over crombi and failing also to restore a nandroid, I tried to do a factory format but now it says unable to mount /cache twfunc::copy logcant open dest log file /cachemkfs.f2fs binary not found, using rm -rf to wipe
wiping data without wiping /data/media... Done.updating part details...
E"unable to mount ,' /cache
I really feel at a loss as when it happened the last time on the other tablet it came round fine after a full format, but this one doesn't want to know..
Please help thanks
evimarn said:
Pardon me but i cannot find the right place where to post my problem.
After failing horribly to instal zombie over crombi and failing also to restore a nandroid, I tried to do a factory format but now it says unable to mount /cache twfunc::copy logcant open dest log file /cachemkfs.f2fs binary not found, using rm -rf to wipe
wiping data without wiping /data/media... Done.updating part details...
E"unable to mount ,' /cache
I really feel at a loss as when it happened the last time on the other tablet it came round fine after a full format, but this one doesn't want to know..
Please help thanks
Click to expand...
Click to collapse
Hey mate ....
Sounds like you got yourself into a pickle .......
Give this a try .... Boot into recovery and ........
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
This should format /data, You will need to use the hardware button to force reboot......
reboot back into recovery and see if /data can be mounted now ......
Thx Josh
Thanks for the quick reply do you think this will fix cache mount and dalvik mount problems as the system can wipe date but not dalvik and cache.
Fixed
evimarn said:
Thanks for the quick reply do you think this will fix cache mount and dalvik mount problems as the system can wipe date but not dalvik and cache.
Click to expand...
Click to collapse
After much formats it appears to be that twrp was corrupt as after using a fresh recovery blob every thing seems to be in place and cache and dalviki can be mounted.
The only quirk is that no matter how I try to instal Zombie after the message to restart and enjoy it just hangs on the droid animation for more than an hour, so for the time being I went back to crombi-kk until someone knocks some ideas into me.
Thanks
evimarn said:
After much formats it appears to be that twrp was corrupt as after using a fresh recovery blob every thing seems to be in place and cache and dalviki can be mounted.
The only quirk is that no matter how I try to instal Zombie after the message to restart and enjoy it just hangs on the droid animation for more than an hour, so for the time being I went back to crombi-kk until someone knocks some ideas into me.
Thanks
Click to expand...
Click to collapse
Are you on the 10.6.1.14.10 bootloader?
Yes exactly that. Thanks
at first im just failing at wiping cache.
now i cant even restore my TWRP backup.
it is saying "Failed to unmount '/cache' (Device or resource busy)
now my phone got no OS :crying::crying::crying:
I was facing the same problem.recovery twrp>wipe>advance wipe and then select system>repare or change size>change file system>select FAT
after doing it try to restore your backup and if you get error the only way flash your phone to the last build number(avalaible for your phone) and then install twrp recovery(last version).
restoring backup should be work with this method.
you can try this method
Mount>select partitions to mount : cache
select cache and after doing it go for restoring.
R3yN said:
at first im just failing at wiping cache.
now i cant even restore my TWRP backup.
it is saying "Failed to unmount '/cache' (Device or resource busy)
now my phone got no OS :crying::crying::crying:
Click to expand...
Click to collapse
No need to restore /cache partition, exclude it The partition is used by TWRP that's why you can't unmount it.
I still have the same problem persisted. Can't wipe cache with this TWRP recovery. It says can't mount/unmont cache device or resource busy. Restore of the backup was impossible as well. Even when cache was excluded. Changing file types and repairing it also didn' work. In Mount cache is ticked permanently and it can't be unticked.
rrvuhpg said:
No need to restore /cache partition, exclude it The partition is used by TWRP that's why you can't unmount it.
Click to expand...
Click to collapse
Thanks man, i was having the same problem and for some reason, it didnt occur me to exclude the cache
omg i got that eror now, do u have new idea to fix it:crying: ?