Related
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
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.
unable to mount /data
No idea what happened.
Woke up today.. phone seemed off .. tried to charge and reboot and could not.
Got into recovery, and tried to wipe caches etc.. could not..
This is the message I get in logs from TWRP.
I read in another forum about going into the console and typing a manual command to reformat the partition.
I have no idea if that command would be the same here..
ANYONE??? please?
You didn't post the command, but just from common knowledge I'd say the Linux command would be the same, but the partition you need to format might be/probably is named differently on this phone.
Incidentally, there is always the possibility of partial or full emmc failure. Your description of the symptoms sound consistent with hardware failure, so I wouldn't rule out that possibility.
I just had the same thing happen. Can't find the command to manually reformat as well. My external SD card was wiped as well, apparently. Or it won't read it. TWRP also says internal storage is 0 mb.
Hello everyone,
I have a little problem with TWRP on my LG G3 (D855, 32 GB).
I installed TWRP two months ago and flashed CyanogenMod 12.1.
Now I've noticed that TWRP (2.8.6.0) shows the Internal Storage with 0MB.
When I tap the middle Icon on the bottom of the TWRP Main screen, I get an (maybe helpful?) output:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
...done
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
I'm a bit confused. Could this be, because I used CyanogenMod's Device Encryption?
I'm planning on reverting to Stock Rom (...i quite liked it. And considering the camera quality, CM isn't really any better), but i fear this (or flashing anything different) could brick my phone, since there seems to be something strange.
Is there any way to debug or even fix this?
Is it safe to revert to Stock, when TWRP doesn't even detect the Internal Storage? (following this Guide: http://forum.xda-developers.com/showthread.php?t=2785089)
I'd be glad about any help oder hint, about how to proceed. Thanks in advance!
First, update your TWRP version to 2.8.7.0 (available here: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129 )
Then, boot into TWRP, go to Wipe and choose "Format Data".
After done that, reboot your device into recovery again.
Thank you very much. I will try this.
i had that , but dont remember what i did ,, but i do know you need to format , by fastboot or twrp and repair partitions
It happens often to me when I upgrade.
I use 3 phones: Xperia Z2, LG G3, Samsung Galaxy S2 and when I've updated to Lollipop it happened all three times.
Recently I noticed that also on the S2 happened this and I suppose it's because partitions are not initialized.
I was unable to write to internal partition (0 MB) and I've solve this way:
I've flashed CyanogenMod, mounted the internal memory as flashdrive under windows and simply formated it.
When I've disconnected the phone from the pc, Android was able to write normally to the internal storage and everything worked like a charm.
I know it's not possible (AFAIK) to mount internal memory on stock roms as Mass Storage, but perhaps someone will point you on how to correctly fix partitions without using my method.
Looks like Kill Switch Wiped
Did you find any solution, even i am struggling with same problem. I think LG G3 has kill switch that wiped out everything, but not sure just guess.
Have same problem any help?
Complete Android newbie/dummy. Sophisticated Linux user.
Samsung Galaxy S2 T-Mobile version (SGH-T989). I think it's called "Hercules" -- it's the S2 without a home button. I previously installed CWM with Odin and rooted it by placing an su package on the sdcard. Didn't use the phone for a couple of years. Gave it to my wife after her phone was stolen. Seems to be stuck in the boot process. It boots to where I see "Samsung" logo, but the OS never comes up. Here's what I've done so far:
Reformatted the SD card on Linux using mkdosfs -F 32 -I /dev/sdf1. The SD card is 64GB, which is technically unsupported, but when the phone worked, it was able to use the SD card with no problems.
Installed a bootloader named TWRP 2.8.7.0. I can get into TWRP's environment, but not everything works as I expect it to.
Mount
The "Select Partitions to Mount" section is empty, which is unexpected since I have an FAT32 formatted SD card installed. Furthermore, when I press the "Mount USB Storage" button, I see the following error messages on the console:
E: Mount: Unable to find partition for path '/cache'
E: Mount: Unable to find storage partition to mount to USB
Install
At the top I see: "Storage: ( MB)", and underneath I see what looks to be a Unix filesystem. Obviously / is mounted (and I assume the partition is on the phone's internal memory), but the size isn't being detected by TWRP since the storage size is undefined. When I press "Storage" it asks me to select the storage, but the list is completely empty. Again, the SD card doesn't show up. Normally I'd "blame" my unsupported SD card size, but: a) it previously worked, and b) TWRP can't detect the storage size of the root partition, so something funny is happening.
Bootup
This might be the heart of the matter. When the phone boots into TWRP, there are some very ominous looking error messages:
E: Invalid block device on '/dev/block/mmcblk0p3
/boot
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p22
/recovery
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p24
/system
ext4 ro,errors=panic
wait
', 'ext4', 42
If this were a Linux system, I would suspect one of the following:
Perhaps /etc/fstab is referencing the wrong /dev/ files.
Perhaps the block device in question (e.g. hard drive) is failing.
Perhaps udev is not populating /dev/ properly.
As a last comment, when I poke around using TWRP's file manager, /boot is empty. The kernel should be in there, yes? OK, if so, then that's a very, very big problem. /recovery is empty. Interestingly, /system contains a single directory, /bin, which is empty. /sbin contains what you'd expect. /etc has an fstab, mtab, mke2fs.conf, and recovery.fstab.
Interestingly, /dev/block/mmcblk0p24, /dev/block/mmcblk0p24, and /dev/block/mmcblk0p3 all exist. This seems to indicate that udev is doing its job correctly (and I think also that /etc/fstab is ok). So maybe this is a hardware problem?
This is very strange because although I'm very comfortable with Linux, I'm feeling particularly helpless, and like I'm going around in circles.
Can some kind soul help me find my way?
I'm having the same type of problem with my E:\ not being mounted when I go into twrp. I can't even see a directory for me to run the wipe command on.
Will you try restoring back to Factory ROM ?
peterNYC said:
Complete Android newbie/dummy. Sophisticated Linux user.
Samsung Galaxy S2 T-Mobile version (SGH-T989). I think it's called "Hercules" -- it's the S2 without a home button. I previously installed CWM with Odin and rooted it by placing an su package on the sdcard. Didn't use the phone for a couple of years. Gave it to my wife after her phone was stolen. Seems to be stuck in the boot process. It boots to where I see "Samsung" logo, but the OS never comes up. Here's what I've done so far:
Reformatted the SD card on Linux using mkdosfs -F 32 -I /dev/sdf1. The SD card is 64GB, which is technically unsupported, but when the phone worked, it was able to use the SD card with no problems.
Installed a bootloader named TWRP 2.8.7.0. I can get into TWRP's environment, but not everything works as I expect it to.
Mount
The "Select Partitions to Mount" section is empty, which is unexpected since I have an FAT32 formatted SD card installed. Furthermore, when I press the "Mount USB Storage" button, I see the following error messages on the console:
E: Mount: Unable to find partition for path '/cache'
E: Mount: Unable to find storage partition to mount to USB
Install
At the top I see: "Storage: ( MB)", and underneath I see what looks to be a Unix filesystem. Obviously / is mounted (and I assume the partition is on the phone's internal memory), but the size isn't being detected by TWRP since the storage size is undefined. When I press "Storage" it asks me to select the storage, but the list is completely empty. Again, the SD card doesn't show up. Normally I'd "blame" my unsupported SD card size, but: a) it previously worked, and b) TWRP can't detect the storage size of the root partition, so something funny is happening.
Bootup
This might be the heart of the matter. When the phone boots into TWRP, there are some very ominous looking error messages:
E: Invalid block device on '/dev/block/mmcblk0p3
/boot
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p22
/recovery
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p24
/system
ext4 ro,errors=panic
wait
', 'ext4', 42
If this were a Linux system, I would suspect one of the following:
Perhaps /etc/fstab is referencing the wrong /dev/ files.
Perhaps the block device in question (e.g. hard drive) is failing.
Perhaps udev is not populating /dev/ properly.
As a last comment, when I poke around using TWRP's file manager, /boot is empty. The kernel should be in there, yes? OK, if so, then that's a very, very big problem. /recovery is empty. Interestingly, /system contains a single directory, /bin, which is empty. /sbin contains what you'd expect. /etc has an fstab, mtab, mke2fs.conf, and recovery.fstab.
Interestingly, /dev/block/mmcblk0p24, /dev/block/mmcblk0p24, and /dev/block/mmcblk0p3 all exist. This seems to indicate that udev is doing its job correctly (and I think also that /etc/fstab is ok). So maybe this is a hardware problem?
This is very strange because although I'm very comfortable with Linux, I'm feeling particularly helpless, and like I'm going around in circles.
Can some kind soul help me find my way?
Click to expand...
Click to collapse
Do you have root access ?
Anyone have a fix for this? I'm having the same issue with my SGS2X (hercules). Thanks
Odin back to stock or try a different recovery, might I suggest CWM
fattest said:
Anyone have a fix for this? I'm having the same issue with my SGS2X (hercules). Thanks
Click to expand...
Click to collapse
Your best bet is to odin back to Stock, mine is a bit weird, I can't install JB via no method, always stuck at samsung logo, but ICS seems to go ok, you should try it.