I've been trying to install custom roms for a few days. Now I finally got one to work. But There is still one mega problem. I can't install or download anything from anywhere. Reason is probably that the cache is f'ed.
When I installed rom I alway got:
E:Can't mount /dev/block/mmcblk1p24 (invalid argument)
Error mounting /cache/!
Skipping format...
Cache wipe complete.
E:Can't mount /dev/block/mmcblk1p24 (invalid argument)
.
.
.
I tried fixing permissions, wiping dalvin cache and wiping data/factory and still the cache wouldn't mount!!!
Now when a rom finaly worked, I couldn't download any apps, because of cache issue. So I went to see what permissions the cache folder had, and it had all permissions.
What should I do now???
sventibolt said:
I've been trying to install custom roms for a few days. Now I finally got one to work. But There is still one mega problem. I can't install or download anything from anywhere. Reason is probably that the cache is f'ed.
When I installed rom I alway got:
E:Can't mount /dev/block/mmcblk1p24 (invalid argument)
Error mounting /cache/!
Skipping format...
Cache wipe complete.
E:Can't mount /dev/block/mmcblk1p24 (invalid argument)
.
.
.
I tried fixing permissions, wiping dalvin cache and wiping data/factory and still the cache wouldn't mount!!!
Now when a rom finaly worked, I couldn't download any apps, because of cache issue. So I went to see what permissions the cache folder had, and it had all permissions.
What should I do now???
Click to expand...
Click to collapse
It would be interesting to see how it's trying to mount the cache partition and what argument it's invalid. On a linux system this information can usually be found in a file called fstab in the /etc folder. I looked for a similar file on my Defy but haven't found one yet (I would need to make a thorough search to find that file) but if I remember well, on android emulator I saw file with a similar name, having the same content as a normal fstab file.
When I'll get home, I'll make a more thorough analysis on my Defy and if I will find something I'll post here my findings in order to help you fix the issue you're having.
FIXED!!! I used adb shell to format the CACHE: partition. It had errors! Now all is working!
The same problem
sventibolt said:
FIXED!!! I used adb shell to format the CACHE: partition. It had errors! Now all is working!
Click to expand...
Click to collapse
Can you explain how have you solved this error? I have the same problem!!! What is the shell command? Thanks!!!
Or you can wipe the cache in recovery, either stock or custom
mys_721tx said:
Or you can wipe the cache in recovery, either stock or custom
Click to expand...
Click to collapse
I've got the same problem and that hasn't worked for me. I'd also like to know how to wipe the cache using adb shell.
I've found the solutions:
in console:
> adb shell
$ su
(press ok when ask for permission on a device)
# format CACHE:
# exit
$ exit
but for me doesn't work
when I try "format CACHE:" I receive:
Code:
blk: partition "" size 1975545856 not a multiple of io_buffer_size 524288
mke2fs -m 0 -j -L cache /dev/block/mmcblk1p24 184467440
blk_format_ext2: failed to exec "/sbin/mke2fs_static": error -1
mke2fs 1.40.8 (13-Mar-2008)
mke2fs: Filesystem larger than apparent device size.
Proceed anyway? (y,n) y
y
Warning: 256-byte inodes not usable on older systems
Filesystem label=cache
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
11534336 inodes, 46116860 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
1408 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
mke2fs: Invalid argument while zeroing block 46116832 at end of filesystem
Writing inode tables: 2/1408
Could not write 8 blocks in inode table starting at 65538: Invalid argument
blk_format_ext2: mke2fs returned 1
W:format: error formatting "CACHE:"
Any ideas? Please help
nero84 said:
I've found the solutions:
in console:
> adb shell
$ su
(press ok when ask for permission on a device)
# format CACHE:
# exit
$ exit
but for me doesn't work
when I try "format CACHE:" I receive:
Code:
blk: partition "" size 1975545856 not a multiple of io_buffer_size 524288
mke2fs -m 0 -j -L cache /dev/block/mmcblk1p24 184467440
blk_format_ext2: failed to exec "/sbin/mke2fs_static": error -1
mke2fs 1.40.8 (13-Mar-2008)
mke2fs: Filesystem larger than apparent device size.
Proceed anyway? (y,n) y
y
Warning: 256-byte inodes not usable on older systems
Filesystem label=cache
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
11534336 inodes, 46116860 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
1408 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
mke2fs: Invalid argument while zeroing block 46116832 at end of filesystem
Writing inode tables: 2/1408
Could not write 8 blocks in inode table starting at 65538: Invalid argument
blk_format_ext2: mke2fs returned 1
W:format: error formatting "CACHE:"
Any ideas? Please help
Click to expand...
Click to collapse
I did the same as you with the same result, but followed it up by booting into recovery and then wiping the cache from there. That appears to have sorted the problem out. I can use the market again and when I'm in recovery the mount error problem has disappeared.
tim440 said:
I did the same as you with the same result, but followed it up by booting into recovery and then wiping the cache from there. That appears to have sorted the problem out. I can use the market again and when I'm in recovery the mount error problem has disappeared.
Click to expand...
Click to collapse
Which version of cwm have you install?
I use the v3.0.2.8 (the last one I think), installed by 2ndInit Recovery Installer v1.7
nero84 said:
Which version of cwm have you install?
I use the v3.0.2.8 (the last one I think), installed by 2ndInit Recovery Installer v1.7
Click to expand...
Click to collapse
Older than that I think. I'll have to check later. I did it in Stock Recovery anyway.
tim440 said:
Older than that I think. I'll have to check later. I did it in Stock Recovery anyway.
Click to expand...
Click to collapse
Ok...I'll try with Stock Recovery soon. For now i've had used only the Custom Recovery
EDIT: I can't use the Stock Recovery. If I tap on the right corner of the screen nothing happen
EDIT2: just press both volume-up AND volume-down at the same time (once you are in the Stock Recovery)...wipe all...and then WORK AGAIN!!!!!! Thank you so much!!!!!
tim440 said:
I did the same as you with the same result, but followed it up by booting into recovery and then wiping the cache from there. That appears to have sorted the problem out. I can use the market again and when I'm in recovery the mount error problem has disappeared.
Click to expand...
Click to collapse
Tks mates. It solve my prob like this too.
My short problem historic:
I bought a German Defy (2.1); I upgrade it with a bad Brazilian 2.2; I fixed with a good Brazilian retail 2.2 version (that Ifound in this forum) and I just fixed my last issue formatting the CACHE, exactly the same way (including the format error and the after cache wipe)
Cheers.
Hello everyone,
I have a Desire HD (Telus) rooted with Android Revolution 5.2.6 installed and 4ext recovery mod.
Overnight my phone locked up and then after popping the battery I could get maybe 30 seconds of use before it would crawl to a halt and lock up again.
I decided to try to wipe the phone and reinstall. Except all of the processes don't complete now. I'll either get (Error 1) or (Error 255) when trying to use the SuperWipe, install the ROM or use the "Wipe all partitions" option.
Right now it's in the 4ext recovery mod and since I've tried all of the wipe options is it safe to try to reboot (back into recovery) or have I wiped 4ext off as well? I have googled this and can't find an answer.
I've noticed that there is a new version of 4ext available (I have 4.1.3 RC2) but apparently the only way to update is via the app store - which obviously I can't do right now.
When trying to format system partition the screen goes blank for a few minutes and eventually returns to the main menu with no info other than a bunch of "E: Can't mount /cache/recovery" messages. The partition list shows system/data/cache as ext4 with only "iB" in the free column.
I'm not sure what to do. Can anyone offer some suggestions?
Here are some recovery log snips:
Code:
==============================================
| Wiping Script |
| This operation will remove all your data |
| You have 10 seconds to remove the battery |
| to cancel this procedure |
==============================================
unmount of /cache failed; no such volume
about to run program [/sbin/erase_image] with 2 args
1. Erasing & formatting EXT4 *CACHE* partitionCreating filesystem with parameters:
Size: 314572288
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1200
Label:
Blocks: 76799
Block groups: 3
Reserved block group size: 23
Created filesystem with 11/19200 inodes and 2459/76799 blocks
(cache is unmounted already)
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD_Super_Wipe.zip
(Status 1)
Installation aborted.
MD5s are valid for the super wipe and the new rom:
Code:
Checking md5sum..
md5sum for this file:
89ad0a12c631e28d34d24ee3ea3d64c8
Checking md5sum..
md5sum for this file:
59531c9715527f5725cbd716dfae4549
Here's what happens when I try to flash the ROM:
Code:
===============================================
| Android Revolution HD |
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
| by mike1986 |
| Be patient - 1st boot may take a while |
===============================================
>>> Formatting partitions
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD-4G_5.2.6.zip
(Status 1)
Installation aborted.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
-- Formatting boot...
Formatting /boot...
I:Formatting unknown device.
-- Formatting system...
Formatting /system...
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
error: file_write: write: I/O error
Hmm... This is the Desire forum. Maybe posting in the Desire HD forum they would be able to help you.
Please post in the right section.
SwiftKeyed from dGB using Transparent XDA App
I have been using MMuzzy's ROMs on my Verizon Galaxy Nexux with no problems since June. I usually install with Rom Manager. The latest 10/5/12 version is failing with a symlink error.
I can recover by going back to the 9/24 version.
any advice on how to get the latest (10/5)
Here is my log file:
October 7, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/system on /system failed: Device or resource busy
-- Installing: /sdcard/toro_signed_100512_222509.zip
Finding update package...
I:Update location: /sdcard/toro_signed_100512_222509.zip
I:using /data/media for /sdcard/toro_signed_100512_222509.zip.
Opening update package...
Installing update...
installing samsung updater extensions
installing samsung updater extensions for toro
Creating filesystem with parameters:
Size: 685768704
Block size: 4096
Blocks per group: 32768
Inodes per group: 6976
Inode size: 256
Journal blocks: 2616
Label:
Blocks: 167424
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41856 inodes and 5443/167424 blocks
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.0/by-name/system at /system: Device or resource busy
minzip: Can't create containing directory for "/system/app/ApplicationsProvider.apk": Read-only file system
symlink: failed to symlink /system/vendor/firmware/hdcp.keys to /factory/hdcp.keys: No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
E:Error in /sdcard/toro_signed_100512_222509.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/toro_signed_100512_222509.zip")
I:using /data/media for /sdcard.
I've been using mmuzzy's roms for a while, I'm on the Oct 9 ROM now. I was never able to get the Oct 5 ROM to work. After sever attempts, I gave up and went back a rom .the Oct 9 ROM (4.1.2) works great
Sent from my Galaxy Nexus using xda app-developers app
Howdy all,
I recently tried to switch to CM 10.2 M1. It's not working out for me for two reasons:
Poor mobile data performance - requires frequent reboots to maintain data connection
openPDroid is not playing nice with it
So, I'm trying to restore my 10.1.3 backup. I have done a factory wipe from CWM and formatted /system (though I may have tried just restoring previous to that, I don't recall). When I try to restore the backup, the boot.img is restored successfully, it starts /system, and after some seconds it gives the following message and stops the restore process:
Code:
Error restoring /system!
The relevant excerpt of /cache/recovery/log is below. Fortunately I finally got ADB sort-of working again (won't connect from fastboot but does from CWM).
I suspect one of two things:
Somehow the size of the /system partition has changed, but I don't know why, how to verify it (what should it be?), and how to safely change it.
The backup is corrupt. I don't know how to check this. The log indicates md5s are okay for system.ext4.dup, but I don't see any indication in the logs that md5s of all of the blobs are okay or even checked.
Has anyone seen something similar or have any advice?
Thanks!!
VZW toro
CWM 6.0.1.0 used to create the backup and to attempt the restore
Using Linux, which has not always played nice with this phone (MTP not supported, udev hell), which is probably the adb issue during fastboot
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:using /data/media for /sdcard.
I:using /data/media for /sdcard/clockworkmod/backup/2013-11-02.14.40.11/.
Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
recovery.img: OK
system.ext4.dup: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-11-02.14.40.11//system.ext4.dup
Restoring system...
Creating filesystem with parameters:
Size: 685768704
Block size: 4096
Blocks per group: 32768
Inodes per group: 6976
Inode size: 256
Journal blocks: 2616
Label:
Blocks: 167424
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41856 inodes and 5443/167424 blocks
Unable to copy file ./app/Apollo.apk
system
lost+found
addon.d
50-cm.sh
blacklist
70-gapps.sh
71-gapps-faceunlock.sh
app
Apollo.apk
Error while restoring /system!
Hello,
I compiled aosp for my nexus 7 2013 works fine, but i wanted to add apps and tweak things like bootanimation.zip and remove things like email app, i don't use it why waste space. I use the the follow to allow edits
simg2img system.img system.img.raw
mkdir system
sudo mount -t ext4 -o loop system.img.raw system/
I add my edits and than use this but get and error
[email protected]:~/Downloads/imagedisassemble$ sudo ./make_ext4fs -s -l 512M -a system mesystem.img system/
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
error: do_inode_allocate_extents: Failed to allocate 3 blocks
I have tried to change 512M to 600M it will finish without error, however when I flash with fastboot flash system system.img, I get stuck on the Google screen and have to force off with power and get into bootloader to try again.
Any help would be great
Thanks
Tony