Develop Bugs

[Q] Problem with Clockwork

I just used Amon Ra recovery to create an ext4 partition on my sd. Went fine, but now I've switched back to Clockworkmod recovery and every time it starts/I go back to main menu I get this error:
"E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/command
E: Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/log
E: Can't mount /dev/block/mmcblk0p2 (File exists)
That first line shows up as well whenever I've tried to wipe dalvik cache for the last few months.
This whole error shows up when I try to create a backup as well right when it starts to backup cache, then just stops. doesn't backup cache or ext partition and doesn't generate md5 sum.

mb02 said:
I just used Amon Ra recovery to create an ext4 partition on my sd. Went fine, but now I've switched back to Clockworkmod recovery and every time it starts/I go back to main menu I get this error:
"E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/command
E: Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/log
E: Can't mount /dev/block/mmcblk0p2 (File exists)
That first line shows up as well whenever I've tried to wipe dalvik cache for the last few months.
This whole error shows up when I try to create a backup as well right when it starts to backup cache, then just stops. doesn't backup cache or ext partition and doesn't generate md5 sum.
Click to expand...
Click to collapse
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=8632182

PonsAsinorem said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=8632182
Click to expand...
Click to collapse
I tried that fix twice, but I keep getting this:
/dev/block/mmcblk0p2 has unsupported feature<s>: extents gdt_checksum
e2sfck:Get a newer version of e2sfck!
and clockwork continues with the same errors at the main menu.
EDIT: Upon typing "e2fsck /dev/block/mmcblk0p2" in adb shell, I get the error "/sbin/sh: e2fsck: not found".

mb02 said:
I just used Amon Ra recovery to create an ext4 partition on my sd. Went fine, but now I've switched back to Clockworkmod recovery and every time it starts/I go back to main menu I get this error:
"E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/command
E: Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/log
E: Can't mount /dev/block/mmcblk0p2 (File exists)
That first line shows up as well whenever I've tried to wipe dalvik cache for the last few months.
This whole error shows up when I try to create a backup as well right when it starts to backup cache, then just stops. doesn't backup cache or ext partition and doesn't generate md5 sum.
Click to expand...
Click to collapse
sounds like you trashed your internal EXT2 partitions.....I did the same with amon recovery..........here is the post I used to fix the situation:
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
after I did this procedure, I had to unroot back to stock, then unrevoked again.

wwjdd44 said:
sounds like you trashed your internal EXT2 partitions.....I did the same with amon recovery..........here is the post I used to fix the situation:
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
after I did this procedure, I had to unroot back to stock, then unrevoked again.
Click to expand...
Click to collapse
WTH man that sucks. all just because of retarded Amon ra ext partitioning for an sd card.

mb02 said:
WTH man that sucks. all just because of retarded Amon ra ext partitioning for an sd card.
Click to expand...
Click to collapse
I thought I was changing my sd card from ext2 to ext4, too...... and somehow ended up changing the internal to ext4........took a little research to get it fixed.

mb02 said:
WTH man that sucks. all just because of retarded Amon ra ext partitioning for an sd card.
Click to expand...
Click to collapse
That's odd. I used it just the other day to partition my SD card with 512mb sd-ext, 32mb swap, and the rest as FAT32 and it worked flawlessly. Something that clockwork couldn't do, mind you.
Sent from my ADR6300 using XDA App

PonsAsinorem said:
That's odd. I used it just the other day to partition my SD card with 512mb sd-ext, 32mb swap, and the rest as FAT32 and it worked flawlessly. Something that clockwork couldn't do, mind you.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I worked, perfectly, to do that for me............it went awry when I tried to change the partition from ext2 to ext4. The new clockwork has the ability to partition your sd card in it..........but now I am gun shy to try.

I knew clockwork has problems partitioning sd, so I stayed away from it. That's why I used Amon Ra to get it done. did partition sd, then did ext2 to ext3 then to ext4. Then flashed back to Clockwork and next thing I know this problem comes up.

I had this same problem last night. I fixed it by going into ROM manager and reflashing clockwork

I tried reflashing recoveries, but that didn't work. I went through the process that was posted above and it fixed it, although I didn't have to RUU back or anything. I just formatted everything on my phone, pushed the 6 files and ran the parted program, then all was fine. Did the partition on my sd again to ext4 and now it works

mb02 said:
I just used Amon Ra recovery to create an ext4 partition on my sd. Went fine, but now I've switched back to Clockworkmod recovery and every time it starts/I go back to main menu I get this error:
"E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/command
E: Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount CACHE:recovery/log
E: Can't mount /dev/block/mmcblk0p2 (File exists)
That first line shows up as well whenever I've tried to wipe dalvik cache for the last few months.
This whole error shows up when I try to create a backup as well right when it starts to backup cache, then just stops. doesn't backup cache or ext partition and doesn't generate md5 sum.
Click to expand...
Click to collapse
clockworkmod, at least 2.5.0.5, can't handle ext4 partitions.

tdiman said:
clockworkmod, at least 2.5.0.5, can't handle ext4 partitions.
Click to expand...
Click to collapse
I'm on 2.5.0.5 and have an ext4 (that works now) and it seems fine.

mb02 said:
I'm on 2.5.0.5 and have an ext4 (that works now) and it seems fine.
Click to expand...
Click to collapse
Interesting. When I created an sd-ext partition ext4 clockwork wouldn't recognize it, giving me the same errors above. Switching it to ext2 worked fine.

[Q] can't wipe htc desire

I did a root to my HTC desire using unrevoked v3.21 and than v3.22 and now i can't wipe data, can't wipe cache and can't install roms. I have HBOOT v.0.93.0001
as soon as i go to recovery i get:
clockworkmod recovery v2.5.0.7
E:can't find MISC:
E:can't mount CACHE:recovery/command
E:can't find MISC:
E:can't mount CACHE:recovery/log
E:can't find MISC:
when try to wpe data/factory reset I get:
Formatting DATA...
....
No app2sd partition found. skipping format of /sd-ext.
formatting SDCARD:/.android_secure...
Data wipe complete.
E:can't mount CACHE:recovery/log
E:can't find MISC:
and when i flash a rom it starts and than i get an error status 7 or something else for other roms.
where did it all go wrong????

why did you root twice??

shaigiv said:
I did a root to my HTC desire using unrevoked v3.21 and than v3.22 and now i can't wipe data, can't wipe cache and can't install roms. I have HBOOT v.0.93.0001
as soon as i go to recovery i get:
clockworkmod recovery v2.5.0.7
E:can't find MISC:
E:can't mount CACHE:recovery/command
E:can't find MISC:
E:can't mount CACHE:recovery/log
E:can't find MISC:
when try to wpe data/factory reset I get:
Formatting DATA...
....
No app2sd partition found. skipping format of /sd-ext.
formatting SDCARD:/.android_secure...
Data wipe complete.
E:can't mount CACHE:recovery/log
E:can't find MISC:
and when i flash a rom it starts and than i get an error status 7 or something else for other roms.
where did it all go wrong????
Click to expand...
Click to collapse
The MISC partition is where certain important things (such as USB mount settings (this is where USB Bricking occurs) and location settings) live. I'm not sure how this happened, but i destinctly remember 3.21 being pulled because it caused this exact problem. I'm not sure how you can proceed from here, perhaps someone more knowledgeable will be able to help.
Though, I also wonder. Why did you root twice?

I didn't know what else to do and I thought maybe another root will make it better. and I saw somewhere that v3.22 is the first version compatiable to HBOOT 0.93 (saw it too late...)

if I'll de-grade to 2.1 with HBOOT 0.83, will it help?

Try to flash an RUU while in fastboot.

Really stuck here help please

Hoping someone might have a min to help me generally with an issue I am having..Ok here is the problem I am having... A few days ago I went into recovery to do a backup (using clockwork 2.5.1.0 with busybox 1.16.0) and I have never had any problems with it but got an error not allowing me to wipe got this.
Formatting DATA...
Formatting DATADATA...
E:Can't mount /dev/block/stl10
(File exists)
Error Mounting /datadata/!
Skipping format...
Formatting CACHE...
Formatting SDEXT...
No app2sd partitiion found. Skipping format of /sd-ext.
Formatting SDCARD:/.android_secure...
Data wipe complete.
E:Can't mount /dev/block/stl11
(file exists)
E:Can't mount CACHE:recovery/log
E:Can't mount /dev/block/stl11
(file exists)
so I figured Oh well will just roll back to a prior backup one I did maybe 3 weeks prior, tried to do a restore and also go this
Checking MD5 sums... it waits for a while nothing going on the bar and then
Restoring system...
E:Can't mount /dev/block/stl11
(file exists)
Error mounting /system/!
Skipping format...
E:Can't mount /dev/block/stl11
(file exists)
E:Can't mount Cache:recovery/log
E:Can't mount /dev/block/stl11
(file exists)
I don't know what to do
I was running Skyraider semi current version with uncommon sense overlay.
Any thoughts or suggestions on how to get back to being able to run a backup?

perhaps a corrupted sd card.... take everything off of it then format to fat32, put stuff back on and see if it works

The data/data fail is what bothers me. And I've never seen that dev/block error on the Incredible either. Did you do anything else in Clockwork or otherwise prior to this that could lend clues? Was your SD or internal memory approaching full? And perhaps most importantly...did you reformat prior to this?
Also just to be clear, are you still up and running other than the backup/restore issue or are you only able to access recovery at this point?

I've gotten that data/data fail error on some of the newer clockworkmod recoveries, always end up going back to 2.5.0.5 and it works great

Recovery Issues

Issue started after a nandroid backup (using clockwork 2.5.0.5). Backup froze, i ended up pulling the battery. When i go back into clockwork to try the backup again i now get the following:
clockwork recovery v2.5.0.5
e:can't mount /dev/block/mmcblk0p2 (file exists)
e:can't mount CACHE:recovery/command
e:can't mount /dev/block/mmcblk0p2 (file exists)
e:can't mount CACHE:recovery/command
e:can't mount /dev/block/mmcblk0p2 (file exists)
I wiped cache, factory reset, wiped dalvik. Even tried formatting boot system, system, data and cache. Was able to reload stock 2.1 through hboot, re-rooted, but get same error and cannot get clockwork to mount sd-card to go any higher.
When I try to mount sd-card through clockwork the following appears:
e:Can't mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1) (no such file or directory)
Any help is greatly appreciated.

Is the SD card full?
Absent that, perhaps make a copy of the SD card on PC, reformat FAT32, place last known working backup on SD and see if you can restore that backup.
If that fails, perhaps d/l another ROM on PC, transfer to SD card, flash, see what you get.

I tried two different sdcards. Both were formatted as fat32. From the articles i have looked at i think i may have screwed up the internal storage. Followed this article:
h t t p://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage
They say to run "parted /dev/block/mmcblk0 mkfs ext2". When i do that it formats the sdcard to ext2. Still have the same issue. Doesn't appear to see the internal at all.
What command can i run from adb shell to display all the storage, volumes or partitions the system i can see?
Again any help is greatly appreciated!

I think just typing command 'mount' will list all mounts.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

Motorola Defy Market Issue

Hello!
I had 3.4.2 stock ROM on my Defy and everything worked well.
My mate tried to install the older 2.51 stock ROM, it failed.
I've successfuly instelled the 3.4.2 back, but unfortunately my market does not work. When I try to install an app, it go to a downloading loop.
"Downloading... Paused... Downloading... Download unsuccessful."
It is only 3 seconds.
I've tried to do these things:
Flashed 3 different kind of 3.4.2 - Market does not work.
Flashed with 2.3.3 latest Stock ROM - Market does not work.
I've tried to delete market cache files, tried with different google account.
If anyone could help, please reply!
Thank you!

Have you wiped data/factory reset, wiped cache and dalvik cache before flashing the back the 3.4.2?

Yes, I've tried, but is it normal tthat in CWM Recovery cant mount things:
E:Can't mount /dev/block/mmcblk1p24
(invalid argument)
E:Can't mount CACHE: recovery/command
E:Can't mount /dev/block/mmcblk1p24
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/mmcblk1p24
When I try to wipe everything the same lines appear, but it says Wipe done!.
Here are the lines:
-- Wiping data...
Formatting DATA: ...
Formatting CACHE:...
E:Can't mount /dev/block/mmcblk1p24
Error mounting /cache/!
Skipping format...
Formatting SDEXT:...
No app2sd partition found. Skipping format of /sd-ext.
Formatting SDCARD:/.android_secure...
Data wipe complete.
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/mmcblk1p24
It's pretty annoying.
Thanks for your reply

did you manage to solve this issue?
I'm having the same issues are you are.

wifi or not
tuxx42 said:
did you manage to solve this issue?
I'm having the same issues are you are.
Click to expand...
Click to collapse
check to see in settings if downloads are only allowed when wifi is on ..