Boot loops and CWM issues - Droid Incredible Q&A, Help & Troubleshooting

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.

Related

[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

Everything just broke...

Whilst attempting to install MIUI 1.14 I got an error that the zip was invalid or something along those lines. I then rebooted but the Desire got stuck in a boot loop. After wiping the phone and formatting the SD card it booted fine, however the SD card is still not recognised, ADB doesn't work and the USB debugging icon keeps coming up as though it keeps getting reconnected. When I try to mount it in recovery, I get:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0 (no such file or directory)
and
E:Can't mount SDCARD:/nandroid/
Any help much appreciated.
Oh, and the memory card works fine on an old Hero I have lying around so the problem isn't there. Is there anyway I can restore it to stock over USB? It boots fine and is recognised in fastboot, as well as showing up in device manager.
mejogid said:
Whilst attempting to install MIUI 1.14 I got an error that the zip was invalid or something along those lines. I then rebooted but the Desire got stuck in a boot loop. After wiping the phone and formatting the SD card it booted fine, however the SD card is still not recognised, ADB doesn't work and the USB debugging icon keeps coming up as though it keeps getting reconnected. When I try to mount it in recovery, I get:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0 (no such file or directory)
and
E:Can't mount SDCARD:/nandroid/
Any help much appreciated.
Oh, and the memory card works fine on an old Hero I have lying around so the problem isn't there. Is there anyway I can restore it to stock over USB? It boots fine and is recognised in fastboot, as well as showing up in device manager.
Click to expand...
Click to collapse
forget the hero
the problem IS the sdcard if recovery cannot mount it as well as the rom
these are two seperate os's
if the zip file was not intact then it would point to there being sdcard corruption and the bootloop will also happen due to faulty SD
If i were you i would put it in a card reader and use h2testw to check the integrity of the card
if that is successful then format the card from the device itself in settings>sdcard & storage
Thanks for the advice. I don't currently have a micro SD card reader (only an SD card one), although I can get one tomorrow fairly easily.
However, given I formatted the card from the Hero's recovery would it not make more sense to go straight to a new SD card? I might be able to borrow one to confirm, regardless. Oh, and how is the ADB issue likely to tie into all of this?

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

[Q] Internal Storage Unavailable

I am having problems with clockwork recovery.
When I open I get:
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/log
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
I am running stock un-rooted, s-off. I ran OTA.
I know exactly what the problem is. My internal storage of my phone wont mount.
I have read a lot of things on how to mount your internal storage. A lot of people say you just have to reboot your phone.
That didn't work.
I know the problem is defiantly not the SD card. I tried 5 different ones.
I read somewhere to remount internal storage you have to take phone apart and put internal storage chip back in.
I can't format internal storage, because it is grayed out in the option under SD card setting.
What can I do. I think I have tried everything?
Please help.
cubusmybro said:
I am having problems with clockwork recovery.
When I open I get:
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/log/block/mmcb1k0p2
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
I am running stock un-rooted, s-off. I ran OTA.
I know exactly what the problem is. My internal storage of my phone wont mount.
I have read a lot of things on how to mount your internal storage. A lot of people say you just have to reboot your phone.
That didn't work.
I know the problem is defiantly not the SD card. I tried 5 different ones.
I read somewhere to remount internal storage you have to take phone apart and put internal storage chip back in.
I can't format internal storage, because it is grayed out in the option under SD card setting.
What can I do. I think I have tried everything?
Please help.
Click to expand...
Click to collapse
Hi,
I don't understand how you can be running unrooted but using cwm?
But I'll guess you are rooted and having problems mounting /cache (dev: /dev/block/mmcb1k0p2) which is an ext3 fs.
I had same messages for the /emmc fs, but that is msdos/fat32, so a slightly different 'cure'.
I used adb shell (or you could use term emulator) to do something like this:
su ; fsck /dev/block/mmcb1k0p2 // look up the correct qualifiers, but I think it'll default to something acceptable. Tell it to repair as needed. Reboot.
For my case I used "fsck_msdos /dev/{whateverThePathWas} and it repaired it and it mounted.
Note: Replacing , replugging the internal storage sounds iffy because all of it is on a single chip which is soldered onto the board. /dev/block/mtd* are only offsets into flash, not anything separate. It seems like more of a format issue or bad blocks.
Good luck
Hashi
PS: Depending on ROMs (I baked my own) , you might not have fsck* but I think you will. Also, some ROMs may use init.d to force an fsck already and this won't work if it did that. Worth a shot.
hachamacha said:
Hi,
I don't understand how you can be running unrooted but using cwm?
But I'll guess you are rooted and having problems mounting /cache (dev: /dev/block/mmcb1k0p2) which is an ext3 fs.
I had same messages for the /emmc fs, but that is msdos/fat32, so a slightly different 'cure'.
I used adb shell (or you could use term emulator) to do something like this:
su ; fsck /dev/block/mmcb1k0p2 // look up the correct qualifiers, but I think it'll default to something acceptable. Tell it to repair as needed. Reboot.
For my case I used "fsck_msdos /dev/{whateverThePathWas} and it repaired it and it mounted.
Note: Replacing , replugging the internal storage sounds iffy because all of it is on a single chip which is soldered onto the board. /dev/block/mtd* are only offsets into flash, not anything separate. It seems like more of a format issue or bad blocks.
Good luck
Hashi
PS: Depending on ROMs (I baked my own) , you might not have fsck* but I think you will. Also, some ROMs may use init.d to force an fsck already and this won't work if it did that. Worth a shot.
Click to expand...
Click to collapse
I kind of have an idea what you mean, but I am just rooted on stock ROM, and I don't think that has fsck, but I don't even know what that is.
I punched in that command into terminal emulator as follows:
#su ; fsck /dev/block/mmcb1k0p2 //
#
All I got in return was a hash, I rebooted, and problem wasn't fixed yet.
I am also not sure what you mean by, "look up the correct qualifiers."
fsck: permission denied is what I get when I just type that in.
Thank you. I think that I am on the right track.

[Q]{FIXED!} E:Can't mount /dev/block/mmcblk0p2 {FIXED!}

Hi all. Got a bit of a problem. I have been using InsertCoinGB S2.1 ROMs for a while now and went to flash v22 this morning. Decided I would also take the step of updating my CWM to 3.0.2.8, as well as ext3 alignment, at the same time.
So, steps taken were Nandroid backup, apply update.zip, flash alignment_ext3.zip, flash ROM. All seemed to go well, but got stuck at splash screen. Pulled battery and got back into Recovery, then tried to restore Nandroid...
Ended up with
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /sd-ext/!
Skipping format...
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /sd-ext/!
Help!! I am pretty sure I have stuffed my SD, but hopefully not the whole phone. I have an 8gig at home that I was using prior to current 16g...I might be able to swap that in, just means I will lose all data from past week, which is not so bad...
I have done a fair bit of googling and searching here, but most remedies seem to rely on being able to boot into ROM and repair thru ROM Manager or GParted etc, but I am unable to get past Recovery or splash screen. I am S-On, btw and had 996mB Ext3/13.xFAT32...
Any ideas??
Cheers.
EDIT: Fixed. Phew! Was able to run home at lunch and thanks to clunky old Dell laptop, I found that my SD was not dead, just wounded. Had a GParted disk ready to go, so was able to format Ext3, boot up and flash Recovery. Will try to flash v22 again later...

Categories

Resources