Develop Bugs

i lost all hope pls help

hi i am a noob and i downgraded from the crc1 to the rc29
and i get in the recovery menu E:Can't mount CACHE:recovery/log
i fallowed the http://forum.xda-developers.com/showthread.php?t=538456&highlight=crc1
and got to this part "If you are coming from another Apps2SD ROM. In order to guarantee you won't have any issues with the install you should remove all directories starting with "app" and the dalvik-cache directory on your /system/sd (ext2/ext3) partition. If you backed up your whole SDcard, this shouldn't be a huge issue. - Yes you'll have to reinstall your apps. You can try to skip this step, but if the install fails, rinse, wash, repeat and don't skip this step." and did not understand what i needed to do
i tried to complete the guide and now all that i have is the E:Can't mount CACHE:recovery/log and i cant load any update.zip.
i really dont know what to do pls help

To resolve this error, you must wipe in the recovery mode (Alt+w) and then try installing

thanks i did it and it worked, but now i have a different problem
when i try to mount the g1 the pc doesn't recognizes the phone, what should i do?

[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] How screwed am I?

I only loaded a new rom on the incredible successfully once, last summer when the signed 2.2 rom came out early and I couldn't wait for the OTA.
I had this problem crop up that said my storage was full when I had gobs of space left on my internal storage and my sd card. Finally, after I did the factory reset option and still had the storage issue, I decided to try reflashing with a new rom because my phone was becoming unusable. I couldn't install apps, save contacts or even open text messages. My phone wouldn't even sync with Google.
I decided to try flashing with the redemption rom after reading some good things about it.
I managed to load it successfully, but I still had the storage error! argh!
After trying to reformat some things with the ClockworkMod Recovery partition menu, I tried to reload the redemption rom again. Something went wrong.
Now I get messages saying(on the ClockworkMod recovery screen):
_______
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)
When I choose the option to install the redemption rom off my sd card in the clockworkmod, it fails after giving me similar error messages.
I'm stumped. Can anyone point me towards the right thread to deal with this? I can't boot to install any other software onto my phone. Practically everything I try gives me can't mount error messages.
I was hungry and in a hurry and never made a nandroid backup I HAVE tried reformatting the sd card, but I got no different results from that.
So am I A) totally screwed, B) somewhat screwed, or C) not screwed at all, just an idiot?
Help?

im in the same boat. i have no idea how to fix it. ive tried every fic i can find on google and NOTHING works. someone HALP

forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 the site wont let me post a link, but this is what i used. i can now mount data and cache. working on booting now.

Have you tried a different SD card? Your SD card could have failed or become corrupt in some way.
I doubt you are totally messed up. You may need to get a brand new factory ROM (on your new SD Card) and start from there. Just Google it. As for an SD Card, there will be a few on sale Friday.
As for the full memory, I had that same problem, it's a cache issue with the HTC software (HTC Mail, Facebook, Peep and such). Once you get back up and running make sure you root (unrEVOked is working on a work around for the latest mid Nov OTA but there are other ways to root) and get a Cache Cleaner. It's not a permanent fix, but it does work.
Good luck!

Thanks for the response. I have yet to try Barbee's solution, but I did try another SD Card. I reformatted both cards to Fat32 and had the same error message on both. I'm going to go grab my phone and try Barbee's solution next.

it might be that version of CWM recovery is just retarded. what version are you on

I take no credit for this but try this its on Adrynalyne's blog http://adrynalyne.us/
"There have been a few cases where /cache has been corrupting on the DI."
"To fix this, you must be in clockwork recovery.
First, unmount cache from partitions menu.
Then, mount system from the same menu.
adb shell
system/bin/e2fsck -p /dev/block/mmcblk0p2
exit"
That should fix the issue you guys are having.

Thanks Barbee, I was able to unbrick with your solution! Pretty muh all of that was way over my head, but the instructions were clear and they worked. Now I just need to get that Redemption rom to work with the *228 option1 programming on the phone... that doesn't work now lol.

That's easy, go into settings sounds and turn the touch tones to long. This is common in custom roms.
Sent from my ADR6300 using XDA App

what happened was you trashed your internal partitions using cwm partitioner......the method on cyanogen's forum shows how to properly reformat the internal partitions to ext2 and gets you back to having a usable phone.

Glad to hear it helped you. But all the credit goes to the guys in the link post. It was a little over my head too lol. I've used adb before but not for a life or death situation lol
Sent from my ADR6300 using XDA App

[Q] help E: Can't mount /dev/block/mmcblk0p2

ok so i've searched around and cant find a definite answer on what /dev/block/mmcblk0p2 is, i believe its sdcard ext? but i do not have a partitioned sd...problem is my phone will not boot, i have been trying to use swap on my droid inc and ****ed it up by trying to use this location for it, it obviously tried creating a file and messed it up somehow...how can i fix this issue so my phone will boot?
edit: cant use recovery either, same error, also my sd card will not mount on computer but im able to back it up using the mount in clockwork recovery, im using cm6.1 too if anyone needs that

cant even wipe/factory reset...
edit: can now mount sd-ext, but not cache...phone still not booting
found this http://forum.cyanogenmod.com/topic/...mmcblk0++mkfs++ext2__fromsearch__1#entry56396
seems to have worked

Boot loops and CWM issues

Hello all,
i have been around on the site for a while reading, learning, and rooting my DInc. I have SkyRaider 3.5 w/ stock kernal. Currently running CWM 2.5.0.5. I was going to dip into the realm of setting CPU settings for different functions. I DLed SetCPU from the market and installed. i figured this would be a good time to do a backup through CWM in case i eff something up. after the backup completed, i selected the "reboot system now"
Upon rebooting, it loaded into my lock screen with the stock background and clock, not the ones i had before the backup process. when i did the slide unlock, it would just go to an all white screen with the htc green logo in the middle, and all my buttons but the power button were useless. strange i thought.....so i pulled the battery and proceeded into the CWM again to restore to a previous backup. got into CWM just fine, but now i had 5 message lines at the bottom of the CWM screen:
E:Cant mount /dev/block/mmcblk0p2
(file exists)
E:Cant mount CACHE:recovery/command
E:Cant mount /dev/block/mmcblk0p2
(File exists)
E:Cant mount CACHE:recovery/log
E:Cant mount /dev/block/mmcblk0p2
(File exists)
Then, i go into the backup and restore option, and select restore, it kicks me back to the main menu with 5 more messages:
E:Cant mount /dev/block/mmcblk1p1 (or /dev/bloc
k/mmcblk1)
(No such file or directory)
E:Cant mount /sdcard
E:Cant mount /dev/block/mmcblk0p2
(File exists)
E:Cant mount CACHE:recovery/log
E:Cant mount /dev/block/mmcblk0p2
(File exists)
I've tried doing a wipe data/factory reset, and it gives me a bunch of mounting errors and basically skips all format, then kicks me back to main menu in less than 3 seconds.
I've done a fair amount of research for this and can't find anything related to the DInc for this issue. Seen it on a few other devices (earlier droids) but not sure how much that info pertains to this device.
unfortunately i do not have a micro-sd card reader on my computer, so i have not tried re-flashing my ROM since i do not have a ROM on my SD card, not sure if it would be of any use since it sounds like my SD card is not mounting properly.
I will probably go out and buy a universal card reader (should come in handy) as well as a second SD card in case it happens to be the SD card that crapped out.
I figured I'd get this up here anyways to see if anyone can help.
Thanks so much for any advise or fixes you may be able to offer!
~Trey

update
well, i managed to do a couple hboot updates and basically return my phone to the way it was when i got it from the store. i have no idea what caused it, but the original sd card still works, albeit reformatted, and the phone is functioning perfectly so far. I'm still curious to see if anyone had any ideas about what happened. sorry i can be of service to troubleshoot since i fixed it (the long way). my phone is too vital and i have travel coming up.
Thanks,
Trey

When I tethered my incredible to my pc I would get errors. I've had to actually run defrag on my sd card. I actually have several Micro sd readers but I was lazy and did this after tethering to my pc. Seems to have fixed the problem

So, I decided to try to go back to root last night, with the help of Preludedrew. rooted using unrevoked3 and updated to CWM 3. when it was all finished, it left me in CWM recovery and i had new E: errors:
E:Can't mount /dev/recovery/log
E:Can't open /dev/recovery/log
E:Can't mount /dev/recovery/last log ?
E:Can't open /dev/recovery/last log
when i would try to mount cache or sdcard, it would still fail, and when trying to load zip from sdcard, it would error in trying to mount sdcard.
with some more help from drew, we tried using adb shell to mount/access some partitions, and the mmcblk0p2 (i think) could not be found on the device.
thankfully the phone still booted this time, but i went into the phone settings under SD & storage...and the sdcard was there showing my 15GB of total/available space.
But....under the internal phone storage section, it said "unavailable" for both total space and available space.
so the only thing we could somewhat deduce, is that the internal phone memory has crapped out, thus when i RUU'd (?) back to stock, it could not find my phone internal storage so it just reassigned my sdcard to the 0p1 block, and where the sdcard should be in the 0p2 block there is nothing. Hence why cwm cant find anything related to my sdcard since its looking in the 0p2 block.
so now that i'm back to stock, i'll take it to the verizon store today and see what they'll do about it since the internal memory seems to be crap. i have insurance, so i dont think it will be a problem getting a new phone, unless they want to try to replace the internal memory, which is fine with me.
unless anyone has any other ideas?
sorry for the noobish verbage, i'm trying to remember what i all did at 1230 last night.
Thanks,

sorry for the quick reply, but i just had the idea to try mounting my device as disk storage, since it should come up as 2 drives (internal phone and sdcard) on my computer
both drives show up under my computer, sdcard access is fine, but when i try to access the other drive, i get "please insert a disk into drive G:"
and when i switch back to charge only, it will only say "preparing sd storage" and doesnt do "preparing phone storage" like i thought i remember it doing when it was still good.
I guess just another reaffirmation that the storage space is crap.