[HELP!] I can't mount data. - Droid Incredible Q&A, Help & Troubleshooting

In Clockwork Recovery:
I get an error saying "cant mount dev/block/mmcblk0p1 (file exists)" when I try to wipe, mount, or advance restore the data partition.
In RA:
it says invalid argument
Mount data in adb says:
"mounting /dev/block/mmcblk0p1 on /data failed: Invalid argument"
Is this a hardware problem with my memory.
I was useing CM 6.0.1 and the last thing i did was allow windows to format the internal memory when i plugged it it.
Will using an RUU help or brick?
Any help is appreciated.

Thanks for the help guys!
Anyways, I figured it out on my own. I was afraid of flashing an RUU when DATA cant be mounted, so i decided to restore the stock RECOVERY and turn S-ON so I could call Big Red and say their OTA jacked up my phone.
To do so, I downloaded a stock nandroid backup and started to advance restore the partitions I could (boot, system, cache). Just to see what happens I booted up the phone and to my surprise.. it worked properly. I still dont know what happened or why.
Oh, also , i used Amon Ra Recovery to format the internal storage before I started restoring via nandroid. Hope my little ordeal helps someone if they come across the same problem.

Related

[Q] Cannot backup via nandroid

After I flashed this d2we (v1.5) rom http://forum.xda-developers.com/showthread.php?p=11860001 , I decided to upgrade my recovery through Rom Manager.
I succeeded, but I cannot nan backup with it.
I flash the update.zip, I start the backup, it gets stuck on "Backing up Data..." (although the bar is full), and after a long waiting it says
"Error in CACHE:recovery/log
(No space left on device)"
I don't know how much space is left in my internal memory, because I'm using d2we, but I think it's supposed to be empty due to the d2we. anyway, is it suppose to interrupt?
Maybe a wipe will help things up?
Thanks!
Recovery info? Phone info? Bootloader version?
CWM 2.5.0.7.
What do u mean by phone info? (if amoled/slcd then it's amoled)
Where can I find the Bootloader version? (is it the HBOOT? if so, then it's 0.75)
Thank you for trying to help!
Maybe your /cache partition is full. Try doing Wipe Cache in recovery.
Clear cache.
If it does not works from recovery, then can try fastboot or ADB.
But it should in 2.5.0.7.
Still the same after I wiped the cache.
Could it be that it says that the cache was wiped, but it actually wasn't?
Try it from fastboot with erase cache command: Guide here.
Just skip the first two and start form getting into fastboot.
It will need the HBoot USB drivers (the same used for Unrevoked).
It did finish the backup; however, now it says
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Could not mount sd-ext. sd-ext backup may not be supported on this device. Skipping backup of sd-ext.
Is it normal with d2we?
Anyway thank you very much, I can finally backup!
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
http://forum.xda-developers.com/showthread.php?t=809714
http://androidforums.com/incredible-all-things-root/124971-e-cant-mount-dev-block-mmcblk0p2-file-exists.html

fix "can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!.

I flashed a Leedroid 3.0 and it was just stuck in the boot screen. So tried to clear data and all thru recovery and i got this error "can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!.
I downloaded gparted to repartition my 8gb sd card. I did a ext3 partition. When i plug back the sd card, the error still comes out in recovery mode. Any rom i flash gets stuck in Bootscreen still. I tried partitioning my 4gb sd card but it also gave the same error in the recovery.
please help. Been trying the whole day and still nothing is happening
Have you tried partitioning it through recovery? (If you have that option available)
I'd begin with reflashing a cwm recovery, cause maybe the problem is not your sd. In "mounts and storage" did you try to mount/amount sd-ext ?
Sent from my Desire using LeeDrOiD 2.4.1
I cant also mount/unmount sd ext. It says the same thing. can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!. should i just buy a fresh new memory card?
What exactly is your recovery ?
Sent from my Desire using LeeDrOiD 2.4.1
flash clockworkmod recovery 2.5.0.7 . Im using a sd card now without partition. It seems to work with the rom. Using Leedroid 2.4.1 . If i use the original SD card and reboot it with it, its just stuck in HTC boot screen.
So you should just use parted again with your stock sd to make it work ...
Sent from my Desire using LeeDrOiD 2.4.1
can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/
Click to expand...
Click to collapse
Common error when card is not partitioned or wrongly partitioned. First make Fat, then make EXT.
http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3
Thanks man. I was able to repartition. I made a wrong partition in gparted. Made a fat32 primary then the second one extended partition. From your post i made it primary also the second one. Now my rom reads the sd card. Thanks again.
Hmmm I had this exact same problem with LeeDroid 3.0.2... Trying to flash without wiping, had about 80 apps on my EXT3 partition... Got stuck on the white HTC screen for about 2 hours, gave up, pulled the battery, tried to flash the alignment zip, still stuck... tried to restore nandroid backup but then started getting this same error as you.
Thankfully was able to rescue all files from my SD card, format and partition again, then flashed LeeDroid 3.0.2 and restored a Titanium backup... everything running smoothly again! Phew...
streetdaddy said:
[..]
Thankfully was able to rescue all files from my SD card, format and partition again, then flashed LeeDroid 3.0.2 and restored a Titanium backup... everything running smoothly again! Phew...
Click to expand...
Click to collapse
May I ask how did you manage to do that?
EDIT:
Ok. Apart from the backup/restore issues that depend on having a healthy ext partition as I figure, the "can't mount [..] error mounting /sd-ext/!" problem is responsible for the "green HTC logo on the white screen freeze" also. So I've been trying to make it work all evening and this is what I found:
The Error (at least in my case) and the freaking "green HTC logo" freezez were generated because the Ext partition got corrupted in some bizarre and mysterious way. I have no idea how that could have happened, but I guess a small role in this ballet got played by the ROM itself and maybe even the nandroid backup built into the CWM (ClockWorkMod). It started right after I finished installing a fresh copy of the LeeDroid 2.4.1 and all my favourite apps (which worked flawlessly), rebooted into bootloader > CWM > nandroid and made the full backup of the system. Rebooting the device afterwards got me into the above mentioned freeze.
I tried many things, among which were flashing different ROMs and Radio images (without wiping though), but none worked. I just wanted to roll back to the previous state (because i've spent quite some time configuring and installing the 2.4.1) and it seemed impossible at that point. Browsing the recovery options got me into the Mount and storage section where I noticed the listed error with the ext partition. I thought maybe formatting will help - well, it didn't. After a couple of weird things I had tried, I've decided I should delete the ext partition (leaving just the fat32 intact). Creating a new ext partition from scratch seemed to solve the error. However this didn't solve the freezing. And the reason had to be the fact that when it created the nandroid backup images, the ext was already corrupt (or however unreadable), so the relative image was not written because it didn't see the source.
I doubt there is any way to fully restore my previously installed ROM with all of it's apps in place and in a functioning order, because the ext partition had data on it and now it's missing (hence the freeze).
Therefore the question: what could have gone so badly wrong to compromise the ext partition?
And another one: is the LeeDroid 2.4.1 ROM or the 2.5.0.7 ClockworkMod Recovery the culprit?
Sorry for the looong post. I look further to hearing from Lee, if his busy schedule allows it and thank him in advance.
Cheers!
streetdaddy said:
Hmmm I had this exact same problem with LeeDroid 3.0.2... Trying to flash without wiping, had about 80 apps on my EXT3 partition... Got stuck on the white HTC screen for about 2 hours, gave up, pulled the battery, tried to flash the alignment zip, still stuck... tried to restore nandroid backup but then started getting this same error as you.
Thankfully was able to rescue all files from my SD card, format and partition again, then flashed LeeDroid 3.0.2 and restored a Titanium backup... everything running smoothly again! Phew...
Click to expand...
Click to collapse
hi! having the same exact problem right now... could you please help me how did you rescue all of your sd-card and sd-ext partitions? Thank you very much!
same problem on my N1, reparition to resolved
hi..
i got this problem too
i have clockworkmod recovery. pvt4.
cyanogenmod 7.1.
didn't make any partitions,
everything is by default as i got with cyanogenmod
s-on.
sd - 8gb, class2
yesterday my desire freezed.so i had to pull out the battery. but i couldn't turn it on till' i didn't wipe cache and dalvik cache.
When i selected wipe dalvik cache i got this
E: can't mount /dev/ block/mmcblk0p2
(file exists)
but it wiped it and my phone worked.
this appears even without sd card
it freezed after a week again but after a couple of reboots it works again but the error still exists.
i am newbie so i don't know what to do?
So I flashed a ROM which stuffed up my partitions somehow (also became S-ON, WTH?!).
I got 'can't open /dev/block/mmcblk0 (or /dev/block/mmcblk0p1) (invalid argument)' when trying to mount /sdcard.
I also got the aforementioned 'can't open /dev/block/mmcblk0p2 (file exists)' when trying to mount /sd-ext.
After literally 16 hours of head banging, I realised when I partitioned the SD card again that they were logical instead of primary. Partitioned using minitool partition wizard home edition.
Rundown:
I'm using LeeDroid v3.3.3 with clockworkmod recovery 2.5.0.7
Make sure you partition FAT32 first as primary, then ext3 as primary. LeeDroid says to partition ext3 1GB after FAT32, so e.g. my SD card is 16GB, I have ~13.8GB FAT32 | 1GB ext3
This fixed the 'can't mount /dev/block/mmcblk0' error, /sdcard is mountable.
You can now run .zip files from recovery (yay!). Throw alignment_ext3.zip on there and run it. You should now be able to mount /sd-ext.
Do a full wipe + Dalvik cache wipe (to test /sd-ext accessibility). For me it was back to normal and I'm currently doing a restore.
Always do a backup.

[Q] Can't mount SD card in recovery to flash a new rom, help!

Hi there,
I was about to flash a new rom on my Dinc, and right after I formatted /system, the sdcard became unable to mount and now I can't access the .zip for the new rom. I've tried flashing 3 versions of CWM as well as one of TWRP but none of them can access my SD card. I also reformatted it in my PC with no success. I currently don't have any operating system on it so all I can work with is hboot and recovery.
Can anyone help me fix this?
egunth said:
Hi there,
I was about to flash a new rom on my Dinc, and right after I formatted /system, the sdcard became unable to mount and now I can't access the .zip for the new rom. I've tried flashing 3 versions of CWM as well as one of TWRP but none of them can access my SD card. I also reformatted it in my PC with no success. I currently don't have any operating system on it so all I can work with is hboot and recovery.
Can anyone help me fix this?
Click to expand...
Click to collapse
Did you format it fat32 with the pc? If the cards fine (can be used by pc and fat32) and recovery and hboot still cant find it, then id venture to say the sdcard slot is damaged or went out.
Using adb in recovery, you should be able to push a rom file to emmc and flash it from there.
cmlusco said:
Did you format it fat32 with the pc? If the cards fine (can be used by pc and fat32) and recovery and hboot still cant find it, then id venture to say the sdcard slot is damaged or went out.
Using adb in recovery, you should be able to push a rom file to emmc and flash it from there.
Click to expand...
Click to collapse
I did format it FAT32, and the SD card is definitely fine. I don't think that the slot is the problem either because other things won't mount either.
Actually the only thing I can mount in recovery is /system, everything else is inaccessible. It was having mounting problems before which is why I decided to flash it with a new rom (was running Jellybean very poorly). I also tried flashing the original recovery, doing "clear storage" that way, and reflashing with CWM but it had no effect. During the storage wipe it said that /datadata doesn't even exist. It also shows errors that it can't mount the files /dev/block/mmcblk01 and /dev/blk/mmcblk0p2
This is what the log shows when I did the CLEAR STORAGE using the stock recovery
Restore factory NV setting...
Formatting DATA:...
E: format_root_device: can't find mtd partition "datadata"
Formatting EMMC:...
Formatting CACHE:...
Wipe ALL failed.
E:Can't mount DATADATA:recovery/log
E:Can't mount /dev/block/mmcblk0p2 (or /dev/block/mmcblk1)
(No such file or directory)
The same thing happened to me long back. What I did was that I cleared data, cache, and dalvik cache... Worked for me... You can try but i wont take any responsibility
Sent from my HTC Salsa C510e using XDA

[Q] I've unmounted and reset and am now stuck. Help?

I've already looked through previous posts and there seems to be no avail.
From 4.1.2. stock build, UVDMD5, (I'm assuming, that's when I bought it)
I tried to flash 4.4 ROMS onto it, Both Gummy and Beanstalk with their respective Gapps.
It wouldn't work and I wiped and reset and odin'd in the original firmware UVDMD5, so it successfully led to the beginning phone setup ONCE.
Then, from stock, I figured why not root and flash the ROMS once more? and this time, the galaxy would not have it.
I odin'd myself after the roms failed once more, but now..
Now the phone is stuck at the SAMSUNG loading boot screen.
Everytime I odin in the UVDMD5 setup, it says it's successful but constantly stuck at the boot screen.
I can get myself into recovery but no options are available to me.
If I try to progress forward, the roms will not work and I realized what might've done me in.
Once the roms in the very first trials wouldn't work, I messed with the mounting to see if it would change anything(HUGE mistake I now realize)
I think I unmounted /data and /system and pretty much everything!!!
I'm in the stock recovery so I could pull .zips from the external SD and I've tried to put in Cyanogenmod Recovery so I could get to the mounting options,
but now everytime it says that signature verification failed.
Tl;dr: I'm an idiot and unmounted everything and now it's stuck at boot screen and odin doesn't work. PLS HELP!
ps: ignore the ageold signature
First flash the very latest Recovery with ODIN. You will need to put the phone in download mode to do that. Next, flash Root66 version of UVDMD5 via odin and then flash Rom of your choice via Recovery.
I've taken the root66 and finished odin'ing it in, but no success. It's still stuck on the SAMSUNG screen.
When I boot up to (stock) recovery, the first red messages that appear is
E:failed to mount /data
can't mount '/data' (invalid argument)
and when I go into >apply update from external storage and try to apply cyanogen latest recovery,
all it gives me is E:failed to verify whole-file storage.
There is no /data, what do I do?
Please flash CWM Recovery via Odin.
First of all, thanks for sticking with me for this long.
I successfully installed Clockwork with odin and I thought this would be the end, but
It successfully mounted /system and /external_sd but,
Error mounting /data!
Error mounting /sdcard!
I don't know what to do from here. Is there a simple fix?
Did you flash latest version of CWM ? If yes then try Factory Reset in the Recovery.
I did factory reset it:
. . wiping data . .
formatting /data . . .
Error mounting /data!
Skipping format . . .
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/ .android_secure
Error mounting /sdcard/ .android_secure!
Skipping format . . .
Data Wipe Complete.
Is what shows up and still /data and /sdcard cannot be mounted. Anything else? I'm desperate.
Part 2: I tried moving past all that and tried to run the ROMS, but it goes on to tell me:
This package is for "d2tmo" devices; this is a "d2vzw"
what does that mean?
Can you manually mount SD Card in the Recovery ?
I'd not try any roms until this issue is resolved.
What do you mean by manually?
The external sd card can be mounted, I'm pretty sure it means that the internal sd can't be mounted.
How would I mount internal in recovery? the options says it can't mount /data and /sdcard
Try TWRP Recovery.

Can't restore TWRP /data backup

Hi,
Hope you guys can help me getting my data back.
I messed around with Substratum in legacy mode on OOS 4.1.0 and ended up with a bootloop (I never saw the boot animation restart, just looping endlessly). To fix, I tried the following things:
Flashed the SubstratumRecovery_legacy.zip in TWRP 3.1.0-0 without any effect.
Dirty-flashed OnePlus3Oxygen_16_OTA_047_all_1703132116_f7372e67 without any effect.
Flashed OnePlus3Oxygen_16_OTA_047_all_1703132116_f7372e67 through ADB sideload without any effect.
Wiped data partition in recovery. System started normally, all data gone (obviously).
Before wiping, I had made a backup of my /data partition (through TWRP backup tool for Mac) and saved the content of /sdcard on the computer as well.
Now when I try to restore the /data backup through the same tool, I get an error:
E:Unable to find file system (first period).
E:Unable to find file system (first period).
E:Unknown restore method for '/data'
ADB Restore failed.
So what can I do to restore my data partition? That's all I care about.
Thanks in advance
Mount data in twrp?..
ASFAIK, /data is mounted rw automatically by TWRP. It also doesn't make a difference.
Moreover, I also cannot restore my boot partition (kernel), same error.
A while ago I changed my filesystem to f2fs. Can that be the culprit?
Nevermind, I've given up and accepted the loss of data. However, it would still be interesting to find out what the problem was
I had the same problem, tried several times. Then I went back and turned of the md5 check and it worked perfect.
Do u still have ur trwp backup or did u delete it
https://forum.xda-developers.com/showpost.php?p=53913623&postcount=22
I still have it on the computer and wouldn't mind making use of it (installed official Resurrection Remix after the data loss but that just wiped my /data partition after backing up kernel in TWRP)
@Bradl79: sounds interesting, will give that a go later when I have some time.

Categories

Resources