I have darkys rom 9.1 installed and ive had this issue as ive come up the version as well, for some reason my cache wont format and i think this is causing market issues for me.
When i goto update or download a new app it says downloading for 2 seconds then just disappears.
If i try clear cache in clockworkmod it says
"formatting cache"....
e:cant mount /dev/block/st111
(file exists)
error mounting /cache/!
skipping format...
cache wipe complete
e:cant mount /dev/block/st111
(file exists)
e:cant mount cache:recover/log
e:cant open cache:recovery/log
e:cant mount /dev/block/st111
(file exists)
e:cant mount /dev/block/mmcblk1p2
(file exists)
e:cant mount /dev/block/st111
(file exists)"
Any ideas??
Ok i found a fix. Flash JPC with 512 pit with repartition on, and use the csc file provided in the folder.
Flash, and then you can install the latest roms to get back to normal!
awesomeee
Can you let me know if this works please mate as I have had same issue with the same Tom, even flashed a different Tom and same proven exists now
yep it works! send me a pm if u have any troubles. cheers
Hi guys, was on CM7 alpha for a bit, then flashed back to Darky's, long story short I believe that the data conversion somehow failed midway, and now this happens when i try to flash back to jh2 (i have an i9000m) i've tried flashing to other roms but they just go straight to boot loop
update media, please wait...
(in red)
E: can't mount /dev/block/mmcblk0p1
(no such file or directory)
E: copy_dbdata_media: Can't mount SDCARD:
E: copy_dbdata_media:format SDCARD:
(in yellow)
Formatting SDCARD...
format_root_device: /dev/block/mmcblk0p1format_rfs_device -> /dev/block/mmcblk0p1
format_vfat_device -> argv[0] : /system/bin/newfs_msdos
format_vfat_device -> argv[1] : -F
format_vfat_device -> argv[3] : -0
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcblk0p1
runprogram: child exited with status 1
(in red)
E: can't mount /dev/block/mmcblk0p1
(no such file or directory)
e: copy_dbdata_media: can't mount sdcard:
copy default media content failed.
I know it's possible that the internal sd card has failed and will be calling up samsung tomorrow about it, but i was just curious if there is a way to re-format the data partition so that my phone can recognize it again? Quite a few ppl have said that it's possible the internal sd card is not corrupted. anyways just thought i'd give it a shot and ask you guys, thanks alot
Flash darkys resurrection using Odin...
Sent from my GT-I9000 using XDA App
i've tried that, following correct instructions, phone still goes into a boot loop.
update: SUPER STRANGE
i reflashed resurrection again just to see what would happen... and it sorta worked... only problem is right now when i look at the sd cards, it doesn't show anything mounted... any ideas?
On first boot I get :
Update media, please wait
E: Can't mount / dev/block/stl10
(Invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage yet, please use UI menu for format and reboot actions
copy default media content failed
What I have to doing now???
Help me, please
Thanks!
Hi all.
I've been looking for answer for the problem that I have for a couple of days.
In short, My I9000 was fully submerged in the water I directly pulled it out (couple of second though) took out the battery and dried it. I've even managed to open the casing separate the main PCB, camera, audio jack, speaker, almost everything that I could do, in order to properly dry it. And I had put it in my camera dry box for couple of days to suck all the humidity which may still left.
As result, when I turn it on It went to boot loop Galaxy S logo on and on. The recovery console and download mode is still alive. I've tried several solution in the forum which include flashing it using odin with custom rom, stock rom, even went back as far as eclair, froyo, GB, was using initial asian rom DXJV9, flashed CSC phone etc. I've tried as far as flashed dbdata.rfs mentioned in another thread.
http://forum.xda-developers.com/showthread.php?t=984140
Also tried to copy some files using adb shell (sdparted and stuff like that), mentioned in this forum.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
Now stuck at
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. Please use UI menu for format and reboot actions.
Meida files copy failed. <<<<< is this really a typo from Recovery console
So Is there any other thing that I can do? does my internal sdcard spoiled? Is it not possible for the I9000 to boot without it's internal sdcard?
Thank you
I had my phone assessed with samsung customer service and they said that it had a hardware problem and must be replaced, first of all it cost S$279 to replace, and they will scrap the old main board. I could not get the old main board for my self, in case it revives back.
Is this true? should I just trust them that my phone was bricked?
Thanks for the response
It should not be hardware problem. I see this error before and solved with install old firmware. Install I9000XXJP1 or older from here I hope this will help you
canbas said:
It should not be hardware problem. I see this error before and solved with install old firmware. Install I9000XXJP1 or older from here I hope this will help you
Click to expand...
Click to collapse
I'll try it as soon as I get my phone back from the customer service. I'll post it as soon as I try it.
Thanks for the response.
I've always found that eclair jm9 will resurrect a soft bricked phone the best. Good luck.
Sent from my GT-I9000 using xda premium
canbas said:
It should not be hardware problem. I see this error before and solved with install old firmware. Install I9000XXJP1 or older from here I hope this will help you
Click to expand...
Click to collapse
After I install it with JP1 (with odin and repartition pit512). it came back to recovery console with this message:
update media. please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
<Trying to format internal sd card)
Formating SDCARD:...
update media. please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
After this I'll try the JP9 or is it JM9?
flashed using JM9:
It came to recovery console, again with new message:
... (too fast, didn't catch what it said)
...
...
E:copy_dbdata_media:format SDCARD:
formatting SDCARD:...
format_root_device: /dev/block/mmcblk0p1format_rfs_device -> /dev/block/mmcblk0p1
format_vfat_device -> argv[0] : /system/bin/newfs_msdos
format_vfat_device -> argv[1] : -F
format_vfat_device -> argv[2] : 32
format_vfat_device -> argv[3] : -0
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcblk0p1
run_program: child exited with status 1
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
E:Can't mount /dev/block/st111 (Invalid argument)
E:Can't mount /dev/block/st111 (Invalid argument)
Please if there is anyone that understand what it means, and what can i do about it, it will surely very helpful, even though eventually i couldn't revive the phone.
Is it possible to access sdcard content from windows while we're in recovery? mount the sdcard manually using adb shell?
I tried :
/ # mount /sdcard
but replied with
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Not sure which to choose
For your case (provided you are root) :
mount /dev/block/mmcblk0p1 /mnt/sdcard
I seem to have the same issue with you and managed to boot the phone after passing a previous version stock rom and using speedmod kernel. However my SD card shows empty after the phone starts. Through adb I did the above mount and managed to mount and see some files in that block device. The strange thing - at least for my knowledge - is the mount filesystem (j4fs) instead of vfat or rfs. Is this something you see as well?
chikiball said:
flashed using JM9:
It came to recovery console, again with new message:
... (too fast, didn't catch what it said)
...
...
E:copy_dbdata_media:format SDCARD:
formatting SDCARD:...
format_root_device: /dev/block/mmcblk0p1format_rfs_device -> /dev/block/mmcblk0p1
format_vfat_device -> argv[0] : /system/bin/newfs_msdos
format_vfat_device -> argv[1] : -F
format_vfat_device -> argv[2] : 32
format_vfat_device -> argv[3] : -0
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcblk0p1
run_program: child exited with status 1
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
E:Can't mount /dev/block/st111 (Invalid argument)
E:Can't mount /dev/block/st111 (Invalid argument)
Please if there is anyone that understand what it means, and what can i do about it, it will surely very helpful, even though eventually i couldn't revive the phone.
Click to expand...
Click to collapse
I am having the exact same issues and I have tried all the possible ROMS out there and flashed with 512.pit and 803.pit.... nothing seems to resolved the problems... I even tried to flash speed mod kernel and it also cannot format the sdcard...
How can i mount the sd card??
Any solutions????
Ok, so my basic problem is my Verizon Tablet suddenly wouldn't get past the samsung screen on bootup. This happened suddenly without me changing anything at all. Just turned it on one day and BAM.
First guess was to boot into recovery and do a wipe data/factory reset.
When I do this it just goes to the first line "formatting /data..." and hangs for a long time. Eventually it prints this out
Code:
--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.
I currently do NOT have my SD card inserted as I didn't want to to hurt it during all my messing about fixing this. FYI
I tried giving it its kernel again, and then tried other kernels i'v found around the forum with no change.
I used the Heimdall One-Click found here: http://forum.xda-developers.com/showthread.php?t=1323527 with still no change. But now that I'm running a stock kernel I get this error message as soon as I get into recovery
Code:
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
When I try a wipe data/factory reset I get this error
Code:
update application, please wait
E:Can't mount /dev/block/mmcblk0p2
(Invalid argument)
E:install_application_for_customer:Can't mount DATA:
your storage not prepared yet, please use UI menu for format a
nd reboot actions.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
After doing a bunch of searching I found this page:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partition-on-internal-storage
Post number 7 is where the good info is. I have to upgrade my kernel to one that is rooted (like clockworkmod 5.0.2.7) so I can push the files to the correct spots. From the shell using ADB I type
Code:
parted /dev/block/mmcblk0
If I type print I get this:
Code:
Number Start End Size Type File system Flags
1 32.8kB 220MB 220MB primary ext4
2 220MB 1539MB 1319MB primary ext4
3 1539MB 1959MB 419MB primary fat16
when I type mkfs ext2 I get this error message
Error: File System was not cleanly unmounted! you should run e2fsck.
When I try to run e2fsck /dev/block/mmcblk0 It says this
The superblock could not be read or does not describe a correct ext filesystem.
So Im thinking these programs cannot edit a ext4 filesystem. Since the plan is to format them anyway, I'll delete and recreate them. I did see this on a page somewhere but I cant find that one for the life of me... sorry.
parted /dev/block/mmcblk0
rm 1
rm 2
None of that gives any error messages, but when I print it still shows the same file system, both partitions I just deleted are still there.
So maybe i'm just using parted wrong or it is bugging out? So i try fdisk
Code:
fdisk /dev/block/mmcblk0
p
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 26880 215008 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26881 187904 1288192 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
Partition 3 does not end on cylinder boundary
d (to delete partition)
Partition Number (1-4): 1
d
Partition Number (1-4): 2
p (to print partition table)
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
w (to write and exit)
So that seemed to work right, I I deleted partition 1 and 2 then looked at the table and they are gone and I wrote it. Now I go back into it and BAH, nothing has changed!
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 26880 215008 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26881 187904 1288192 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
Partition 3 does not end on cylinder boundary
I'v used many diffrent Kernels and tried a few different roms (not like its loading that far anyway)
The best I'v gotten it to do is when using Heimdall One-Click it will go past the samsung screen to the Verizon screen. I'v waited at that screen for a very long time with no change...
At this point, i'm stumped. I have no idea where to go next or if I'm even on the right track.
Any help would be greatly appreciated.
Thanks!
I was getting this exact same error on my AT&T Tab. I fixed it by flashing JJ7 from samfirmware.com. Here's what I did:
http://forum.xda-developers.com/showthread.php?t=1388470
check my post there. Obviously you'll have to use a firmware compatible with your VZW Tab, but it might work for ya.
Good Luck.