Develop Bugs

[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] Am I bricked

Ok so I was running MIUI when my phone wouldn't mount my sd card to my laptop. I formatted my card, so it deleted all of my backups.
Now when I power on my phone it gets stuck at the white "htc incredible" screen.
I can get into recovery and have wiped, but I have no backups saved. I downloaded a rom and did a factory reset, flashed the rom, and it still gets stuck at the white screen.
What can I do to actually get my phone to boot?

EDIT:
I didn't notice this the first time, but I did a wipe factory reset again and this is what it says:
-- Wiping data...
Formatting DATA...
E:Can't mount /dev/block/mmcblk0p1
(File exists)
Error mounting /data/!
Skipping format...
Formatting DATADATA...
Formatting CACHE...
Formatting SDEXT...

Go to this thread and follow part 2 from #2 on
http://forum.xda-developers.com/showthread.php?t=786436
Copy that PB31IMG file to the root of your SD card, you will be back at 2.2 stock. You can then re-root and go from there.

i agree with the above post, that should definately get you working.
An other thing you could try would be to reflash a kernel.
Sounds like you may not have a kernel to boot from, which is why its hanging at the white screen.

Thanks guys.. Yea, I had unrooted before and was hoping I wouldn't have to take it that far, but it was necessary this time and did the trick.
Thanks again.

Glad you got it working.
Another thing to note too, if you can see the HTC splash, you usually can fix the problem. It's when the phone doesn't turn on you should be worried about it being bricked.

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.

[Q] SD Card issue

Hi,
I have an International HTC One X, completely stock and locked.
This morning I came to unlock my phone and it went straight to the homescreen (bypassed lockscreen) and the message ("Unfortunately wallpaper has stopped working.") Apex launcher has completely dissapeared, and softkeys are unresponsive.
I booted into recovery and it says:
E:Failed to mount /sdcard (no such file or directory)
Of course trying a factory reset from here doesn't work, flags the message:
Formatting /data..
E:Can't open /data/data/cwtemp/cwpkg.zip and so on.
My guess is the SD card is corrupt.
Any ideas?
Thanks

You could try this or another Mount SD card app to try to remount the SD card...
https://play.google.com/store/apps/details?id=com.jrtstudio.automount&feature=search_result
Aside from that I'm not much help, sorry.

Thanks for the suggestion, I'll give that a try!

Let me know how you get on :good:

Managed to get it mounted!
Backed up my data and then did an erase and factory reset to be on the safe side. Not sure what caused it in the first place, weird!
Thank you again.

Did it mount with that App?

[Q] D-INC Won't Boot

Hi All,
I searched for this, and didn't see anything, so please forgive me if this has been covered before...
My son has an Incredible that was updated to Evervolv last month (I'd tell you the exact build, but...). The day before yesteday, it crashed with the error message saying process android.phone has stopped. The screen was unresponsive at that point, and the phone wouldn't shutdown by holding the power button down (tried holding it for over a minute, and nothing...). I pulled the battery and tried to restart the phone. Everything seemed to be booting normal, but he'd immediately get either the "process.android.phone has stopped" or "process.android.media has stopped" (or both in succession), and the phone would then freeze. Pulled the battery again and booted into recovery (CM ver. 5.0.2.0) to wipe cache and Dalvik cache, but am getting errors there as well:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did try to wipe the cache and Dalvik cache, and it seemed to do that OK (at least, doing so didn't throw any other errors), but that didn't fix the bootloop problem. Next, tried to do a factory reset from recovery. Got the following results:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /datadata...
E:format_volume: no MID partition "datadata"
Formatting /sd-ext...
No app2sd partition found. Skipping format of /sd-ext. (No problem -- no SD card installed)
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Rebooted, and still stuck in bootloop...
So, any ideas on what I should try next to get this phone up and running again? I haven't run into this much trouble with this phone before.
Thanks, and Saludos!
SPC

spcagigas said:
Hi All,
I searched for this, and didn't see anything, so please forgive me if this has been covered before...
My son has an Incredible that was updated to Evervolv last month (I'd tell you the exact build, but...). The day before yesteday, it crashed with the error message saying process android.phone has stopped. The screen was unresponsive at that point, and the phone wouldn't shutdown by holding the power button down (tried holding it for over a minute, and nothing...). I pulled the battery and tried to restart the phone. Everything seemed to be booting normal, but he'd immediately get either the "process.android.phone has stopped" or "process.android.media has stopped" (or both in succession), and the phone would then freeze. Pulled the battery again and booted into recovery (CM ver. 5.0.2.0) to wipe cache and Dalvik cache, but am getting errors there as well:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did try to wipe the cache and Dalvik cache, and it seemed to do that OK (at least, doing so didn't throw any other errors), but that didn't fix the bootloop problem. Next, tried to do a factory reset from recovery. Got the following results:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /datadata...
E:format_volume: no MID partition "datadata"
Formatting /sd-ext...
No app2sd partition found. Skipping format of /sd-ext. (No problem -- no SD card installed)
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Rebooted, and still stuck in bootloop...
So, any ideas on what I should try next to get this phone up and running again? I haven't run into this much trouble with this phone before.
Thanks, and Saludos!
SPC
Click to expand...
Click to collapse
probably need to charge it at this point. Format data (factory reset)
wipe cache and then dalvik and flash a different rom

Will try this evening and report back...

Vernox701 said:
probably need to charge it at this point. Format data (factory reset)
wipe cache and then dalvik and flash a different rom
Click to expand...
Click to collapse
Ehh... No luck. Tried copying another ROM to an external sd card, and CWM won't mount the external SD card. Tried renaming the ROM UPDATE.ZIP and got this error:
Code:
E:unknown volume for path [SDCARD:update.zip]
E:can't mount SDCARD:update.zip
Installation aborted.
any other ideas, or is this one a goner?

I'd try changing to the latest TWRP. The newer CWM never played well with my phone.

Will try that this evening. Need to configure ADB on my laptop, though, since I can't seem to mount emmc or external sd card right now.
Thanks for the advice.

spcagigas said:
Will try that this evening. Need to configure ADB on my laptop, though, since I can't seem to mount emmc or external sd card right now.
Thanks for the advice.
Click to expand...
Click to collapse
Its all a guess on my end maybe your sd card is failing.... have you tried a different sd card make sure its fat32

Vernox701 said:
Its all a guess on my end maybe your sd card is failing.... have you tried a different sd card make sure its fat32
Click to expand...
Click to collapse
Yep, tried two other SD cards with no luck. Can't get the phone to mount either of them, though they were freshly formatted. Also can't get ADB to see this phone to push anything to it. Gonna retire it, I guess...
Thanks to all for the recommendations!
Saludos,
spc

spcagigas said:
Yep, tried two other SD cards with no luck. Can't get the phone to mount either of them, though they were freshly formatted. Also can't get ADB to see this phone to push anything to it. Gonna retire it, I guess...
Thanks to all for the recommendations!
Saludos,
spc
Click to expand...
Click to collapse
I have had this happen before, RUU the phone and it should fix it

zachf714 said:
I have had this happen before, RUU the phone and it should fix it
Click to expand...
Click to collapse
Thanks. I've decided to retire this phone -- the failure to boot was really the last straw for it.