Develop Bugs

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] 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] mounting errors (cant boot anything)

flashed an update to a ROM earlier (which i believe was just coincidental timing) but it stock on splash screen, pulled the battery, booted back into recovery, got tons of e:mount/cache/recovery/ errors which were followed by ending destinations like lastlog, log, etc. cant mount emmc, sd card will not mount so i am stuck. i tried the sd card in the desktop which said it had to be formatted before using which i believe may be because of ext4 partition. so i used a old card which still would not mount in device, put a fresh copy of CWM5 (PB image) on the sd card, it saw and flashed it (so the problem isnt hardware related) but i still had the same issues. i am considering attempting a stock image. hoping that will get me running, root again and be back on tract in an hour. however before i make any steps i was hoping to get some input cause search feature turned up little on this except in forums for some other device (dont remember which). i dont feel their issues was mine. thanks in advance.
edit: decided to go ahead with the RUU, felt sure that would work. well it didnt. phone boots up and runs just fine with my stock ROM. no way of flashing mods, no custom ROMs, cant clear cash, mount emmc, something has to give or i will be having to trade phones sooner than later.

So now that you ruu'ed you flashed cw again and it still wont let you clear or flash anything?

cmlusco said:
So now that you ruu'ed you flashed cw again and it still wont let you clear or flash anything?
Click to expand...
Click to collapse
Correct. I did the ruu. Ran revoked, booted into recovery(which was the old 2.?.?, which had the same issues as before this ever happened. Saw somewhere about a freak error that has happened when attempting to flash ROMs that somehow deletes the main factory partitions. Kinda sounded like mine. But I can not mount, data, cache, SD card, emmc, datadata. I can mount system tho, which does no good. Bootloader sees SD card files so I don't have a issue with corrupt card. I am on stock now which is rooted but nothing is working right cause whatever is going on is infecting it across the board. Apps say installed but don't, not getting messages but can call. Very strange. I know I am too spoiled to live with this tho. Lol.

bump. cant believe nobody has even a suggestion.

shorty1993 said:
bump. cant believe nobody has even a suggestion.
Click to expand...
Click to collapse
What version of hboot are you on?
Have you tried flashing the newest clockwork thru hboot?
When you ruued did you use the PB31IMG.zip method or the exe pc method?
From what i understand your phone does boot but then things dont work right. You say that you cant mount anything but system, but that is only in recovery right? Obviously those partitions are being mounted when booting otherwise it wouldnt boot, so your partitions are probably fine. I would try flashing the latest cw thru hboot, and then see if you can mount and wipe the partitions. If that still dosent work i would then try flashing amon ra recovery thru hboot and see if the wipe and mount options work there.

cmlusco said:
What version of hboot are you on?
Have you tried flashing the newest clockwork thru hboot?
When you ruued did you use the PB31IMG.zip method or the exe pc method?
From what i understand your phone does boot but then things dont work right. You say that you cant mount anything but system, but that is only in recovery right? Obviously those partitions are being mounted when booting otherwise it wouldnt boot, so your partitions are probably fine. I would try flashing the latest cw thru hboot, and then see if you can mount and wipe the partitions. If that still dosent work i would then try flashing amon ra recovery thru hboot and see if the wipe and mount options work there.
Click to expand...
Click to collapse
i am hboot .92. i cant remember for sure what method i used for the RUU but i am abou to try both methods again to be sure no changes depending on which is used.
yes it will boot but only with the stock rom. using file explorers i cant see any contents of data (except lost & found folder), nothing under emmc, datadata, etc. the sd card wont mount in recovery (along with anything else) but will recognize in hboot. cache wont even mount. i had entertained the idea that since different partitions were saying cant mount, it may explain the reason the things arent running just right. i sure shouldnt see barely usable performance on a stock rooted ROM. i have got to figure this out cause new device isnt possible at the time and i cant pay a bill for this thing.
EDIT: i have also swapped over to amon RA recovery with the same results so its not a CWM issue.

just did the PB31IMG RUU. booted as normal (obviously didnt try many functions), ran unrevoked and when it booted into recovery i got the following automatically.
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)
this is just a message right out of the gate. going into mounts will not allow any of these items to be mounted. if attempting to mount CACHE simple "error mounting cache" appears.
system will mount
data shows mounted (but not datadata)
sd card mounting error give the following
E:Cant mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1)
(no such file or directory)
error mounting sd card
i will attempt to run the RUU with the exe but dont expect different results. any thoughts would be great at this point cause i am all out.

no changes regardless of which method of applying RUU is used.

I got your message bud, buy unfortunately i don't have good news for you... Ive had the same thing happen to 2 of my dincs and it is a hardware problem. The only thing you can do is send it in for a refurb or insurance... Good thing is you can run the the stock ruu in the mean time but fixing it isn't going to happen... Sorry man wish I had better news for you good luck

Check this thread out.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
Try going to page 3 as that's when your error starts.
Alternatively, let's try it this way first.
1. Go into recovery,use adb shell to shell into your phone.
2. Type parted /dev/block/mmcblk0
3. Type print.
4. Post output.
It should look like below:
Code:
(parted) print
print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 8095MB 7088MB primary fat32 lba
Let me know from there so we can proceed.

tiny4579 said:
Check this thread out.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
Try going to page 3 as that's when your error starts.
Alternatively, let's try it this way first.
1. Go into recovery,use adb shell to shell into your phone.
2. Type parted /dev/block/mmcblk0
3. Type print.
4. Post output.
It should look like below:
Code:
(parted) print
print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 8095MB 7088MB primary fat32 lba
Let me know from there so we can proceed.
Click to expand...
Click to collapse
i will get this soon as i can steal the laptop charger back from my oldest girl. something i believe got jacked up on my desktop in the path environment so i have never been able to run ADB. guess it will be a long night of learning something new. thanks alot. verizon isnt willing to send me another device, already had 2 without an warranty. which is stupid to void my warranty over a account change only.
bad time of year for things to break.

shorty1993 said:
flashed an update to a ROM earlier (which i believe was just coincidental timing) but it stock on splash screen, pulled the battery, booted back into recovery, got tons of e:mount/cache/recovery/ errors which were followed by ending destinations like lastlog, log, etc. cant mount emmc, sd card will not mount so i am stuck. i tried the sd card in the desktop which said it had to be formatted before using which i believe may be because of ext4 partition. so i used a old card which still would not mount in device, put a fresh copy of CWM5 (PB image) on the sd card, it saw and flashed it (so the problem isnt hardware related) but i still had the same issues. i am considering attempting a stock image. hoping that will get me running, root again and be back on tract in an hour. however before i make any steps i was hoping to get some input cause search feature turned up little on this except in forums for some other device (dont remember which). i dont feel their issues was mine. thanks in advance.
edit: decided to go ahead with the RUU, felt sure that would work. well it didnt. phone boots up and runs just fine with my stock ROM. no way of flashing mods, no custom ROMs, cant clear cash, mount emmc, something has to give or i will be having to trade phones sooner than later.
Click to expand...
Click to collapse
because I use MIUI,I have no idea,I come here to learn lol.

tiny4579 said:
Check this thread out.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
Try going to page 3 as that's when your error starts.
Alternatively, let's try it this way first.
1. Go into recovery,use adb shell to shell into your phone.
2. Type parted /dev/block/mmcblk0
3. Type print.
4. Post output.
It should look like below:
Code:
(parted) print
print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 8095MB 7088MB primary fat32 lba
Let me know from there so we can proceed.
Click to expand...
Click to collapse
Model: SD SA08G (sd/mmc)
Disk /dev/block/mmcblk0: 7973MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 7973MB 7972MB primary fat32 boot, lba
(parted)
from the standpoint of someone far less knowledgeable than i would like to be,,,,,,,,,,,,it appears i have some things missing.

can someone please offer any idea why when doing a push of six files, five show up and one wont regardless of how many attempts. i have also went ahead and done a ruu and fresh root before i started the process of attempting the fix the partitions via the link in this thread. any opinions will be great.

excuse me for bringing this back from the dead but hoping possibly that at this point somebody can shed some additional light on the subject. in desperate need of getting this device running for the wife. where i stand currently is:
*the device is rooted but does not seem to have busy box installed.
*when sd card is inserted it immediately notifies that sd card is safe for removal (can not be mounted thru system menu either)
*in SD and storage info device does not recognize that there is internal memory available either.
all i am need of making this thing do basic functions. as of now files have no where to save (even temps) in order to update or almost anything productive useful. space is not even available to save contacts. this thread above includes all that i have attempted and the outcomes thus far. i would so very appreciative for any and all advice.
thanks in advance
chris

[SOLVED] Unable to mount '/data'

I have a KF1 v6.x (I believe since it was stock). Installed KFU 1.4a. Installed TWRP. Following a post in the [ROM-AOSP] Stock Jelly Bean 4.2.2_r1 for the Kindle Fire [02-12 4.2.2_r1] thread I wiped factory reset then wiped system PRIOR to moving the ROM to the sdcard. Now, there is no OS. I was able to put the ROM.zip on the root of the SD card but when attempting to install it I get "Unable to mount '/data'". I've tried several commands for adb to do partition stuff but didn't get anywhere with that. Not sure if FastBoot is working via KFU due to the following message.
hxxp://imageshack.us/photo/my-images/547/37437819.png/
What's my first step here? I can get into TWRP so hoping this KF isn't totally hosed

Looks like Fastboot is working?
hxxp://imageshack.us/photo/my-images/14/75434412.png/

http://forum.xda-developers.com/showthread.php?t=1949372

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
SUCCESS! :victory: Thanks soupmagnet! Pic of partition table attached showing /data is not mounted. When doing umount cmd received message "can't umount /data: invalid argument" which I guess is good since /data is not mounted in the partition table.
After removing, making, then naming the partion and quitting I received a message: Information: You may need to update /etc/fstab. 2nd pic shows /data correctly mounted.
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?

AnotherBrickedDroid said:
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
Click to expand...
Click to collapse
1) It's hard to say really. For the sdcard, I always assumed it was from not "ejecting" it before unmounting, but I think that would be kind of hard to recreate with the data partition. If I were to speculate at this point, I would say it had to do with how certain versions of TWRP format those partitions, but I'm not sure. In either case it's pretty rare for it to happen.
2) From what I understand, you can't. Recovery is unpacked and run from active memory so any changes you make to fstab will be lost every time you reboot. But the filesystem should still be automatically checked every Nth mount.
3) Three guesses? The first two don't count?

Method for checking emmc integrity?

Hi my phone decided to end itself during election night (google play services crashed, I rebooted, nothing worked anymore). I've gone through a bunch of steps in recovery and fastboot but I still have the same problem, "unable to mount storage". I even get the error when trying to do "Format Data" which is what everyone seems to suggest for the mounting problems I'm getting. In recovery, all the main partitions (/data /cache /system /carrier etc.) won't mount and some if not all of them show a 0mb size. I'm at my wits end here and I'm leaning towards emmc failure, is there any way to check this through adb so that I can be sure that my phone is as good as a paperweight before dropping the cash on a new one?