been getting this error "E:cant mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1" with my g2 I cant flash from my sdcard or boot into os and when i restore a backup that I have using fast boot it just hangs when I try to boot up the system I do have clockwork recovery on the phone and adb access but cant mount the sd card please help thanks
A little punctuation please pal!? That was hard work to just read it.
OK, what are you trying to achieve? Is it just not booting under any condition?
... and you also cant restore a backup through "fastboot" or recovery?
Have you already tried a fresh flash of a ROM or is that a last resort to preserve data/apps?
Boot up into recovery > mounts and storage > Mount sd card > Flash a ROM or restore a backup.
I mean I'm just speculating, I've never had this problem before.
...and yeah wileykat's right, you can't restore from fastboot
omarsalmin said:
...and yeah wileykat's right, you can't restore from fastboot
Click to expand...
Click to collapse
Why couldn't you just use flashboot to flash the boot, system, and userdata partitions with your backup images? I thought flashing these types of partitions was the main purpose of the fastboot protocol to begin with. I hadn't heard that this doesn't work on the G2 (not sure why it wouldn't---is it something specific to the eng. hboot?).
And yeah, more details are probably needed to better understand the issue here.
I got it fixed. I had to bend the prongs on the sd card holder up to provide more contact. Thanks guys.
I am having the same error when I try to do a backup or rom upgrade. The strange part is that I can see the SD card in recovery mode......
nothing freezes on me, but EVERY single time (besides nandroid backup) I get that exact same message.
Does anyone have an actual answer? Like a workaround or something?
Or does it really matter as long as everything flashes
cheers
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
What version of cwm are you using?
Sent From My Optimized HTC Incredibly Dinc
It was the orange, but I upgraded it to see if it would work. uh, oh, as I write this, I fear worse...
Upgrading changed cwm to blue, but still same problems. It is almost as if the data directory has no write permissions.
I got impatient and used the ruu.exe from pvillecomp and now it gets stuck at the red eye droid screen and is on a reboot loop.
I can't get into recovery now, I get the phone icon with the red ! triangle. I figure cwm is gone now, so what, use unrevoked again? This would flash a new recovery, correct? Otherwise, how would I get the zip file onto the sd card now to flash via hboot? Even with a cwm, I imagine I will have the same formatting issues, unless the rom upate utility corrected those.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
Try manually mounting /data before wiping it.
EDIT: Nevermind just read your other post about loosing cw recovery. Are you still s-off?
yeah, I tried every combination of mounting and formatting and it always failed with the same message. I am still S-off, so I imagine from here I can use unrevoked to flash cwm back onto it then I can try to restore from a saved ROM I have on my card. Should I do that?
I could copy the file to flash cwm file to my card instead I guess, but my card would have to be FAT32 I assume.
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
Do you have a ext2/3/4 partition on your sdcard?
cmlusco said:
Do you have a ext2/3/4 partition on your sdcard?
Click to expand...
Click to collapse
By partition, do mean directories? I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
tiny4579 said:
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I've already tried it before. It did not touch my card but did reset my phone's programming.
The restore function in CWM only touches the internal memory, correct?
evil_elf said:
By partition, do mean directories? If so, yes. I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
Click to expand...
Click to collapse
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
cmlusco said:
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
Click to expand...
Click to collapse
I tried the Factory Reset from HBOOT and also the Wipe Data/Factory Reset from CWM. Occasionally I am getting the 5 vibrations and a black screen when trying to turn off and on; battery pull allows me to boot up into ROM or HBOOT.
CM7 is working now, but the hard button bindings are screwed up along with a bunch of other stuff. CWM is able to restore the system, but fails on data so it makes sense. I can't receive calls either. I was so hoping the ruu would have fixed this...
The card should have no bearing on flashing a ROM? Or am I not understanding this?
Oh, I also tried to restore and format data manually without the card in to no avail. The Wipe Data/Factory Reset formats the data folder without errors but not the manually method of formatting or the restore method.
Could this help? http://forum.xda-developers.com/showthread.php?p=18287267
Just tried this: http://forum.xda-developers.com/showthread.php?t=1006556
Still same error.
To return my phone under warranty to a Verizon store, do I need to make sure that the stock ROM is flashed and the phone is unrooted with S-ON again? I am starting to think this is the route I am heading down and I only have a week left on my warranty.
Very short answer.........YES!!!
A kind soul helping me at http://forum.cyanogenmod.com/topic/32272-error-formatting-data-when-restoring/
*Possible Solution* If still an issue
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Can i get those files?
i dont have a working incredible. can you post a link to the working filesystem.
Thanks.
androidi1 said:
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Click to expand...
Click to collapse
Here try this one http://dinc.does-it.net/Touch_of_Blue/filesystem.zip, im interested to see if this works for you too. It seems quite a few people have been having issues with /data latley.
I get error
Code:
push: filesystem/sys/devices/platform/android_pmem.0/power/wakeup -> /sys/devices/platform/android_pmem.0/power/wakeup
failed to copy 'filesystem/sys/devices/platform/android_pmem.0/power/wakeup' to '/sys/devices/platform/android_pmem.0/power/wakeup': Operation not permitted
i get this error trying to push the filesystem. any workaround?
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?
Phone:
GN Toro (Verizon)
no OS currently installed!
TWRP 2.3.3 (I know, needs to be updated)
Skip to the bold text for the TLDR version.
So here's the story... I was going to flash the latest AOKP and decided that this time I would do things right! In the past I had almost always dirty flashed, but this time I was going to start clean and only restore data for a handful of apps. So I booted into TWRP and wiped cache, dalvik cache, system, and ..........internal storage! I went to flash the ROM I had downloaded and that's when I learned that I had made a huge mistake :crying:
So I've been doing a TON of reading; I think I've found a solution to my problem in this thread.
I know I can either use ADB push to reload the ROM or use ODIN mode to reflash (although I was unable to get ODIN to see my phone). My concern is that if I'm going to have any chance recovering my files, I need to avoid writing to /sdcard at all costs.
So here's my question, is there a way to get a binary dump of /sdcard aka /media/data without first installing android? I need to be able to do so from TWRP or fastboot. I have the GN toolkit but I don't see any way of doing this. I also have all the drivers installed and working (or so it seems) and ADB installed.
Sorry I misread. I'm not sure how you can recover from that.
I think you should be able to adb push a ROM to it. Flash it and it won't touch the contents of the SD card.
Sent from my Galaxy Nexus
Beezer80 said:
I think you should be able to adb push a ROM to it. Flash it and it won't touch the contents of the SD card.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Actually, this is exactly what I did. The new ROM wrote a directory structure and various files to /sdcard, hopefully none of those writes overwrote the data I'm trying to recover...
16GB thumb drive and USB OTG cable. Boot into recovery and use dd to dump the user data partition to the thumb drive.
Probably too late for that, since you've already written files to the partition.
cschmitt said:
16GB thumb drive and USB OTG cable. Boot into recovery and use dd to dump the user data partition to the thumb drive.
Probably too late for that, since you've already written files to the partition.
Click to expand...
Click to collapse
Ya know, I have a huge thumb drive and a USB-OTG adapter, I never even thought of this! Thanks, if I ever need to do this again I will try that.
I was able to recover most if not all of my pics (the only thing I cared about losing) using this guide I linked above.
Glad that method worked. It's kind of scary with GN having a single data partition and no ext sd. Coming from a device with separate /data and /sdcard partitions plus and ext sd, I miss being able to back things up onto the card.